Nastran Errors List

MD Nastran/MSC.
Nastran Current Error List

Current Update: February 12, 2009
-------------------------------------This section includes a description of all known errors and general
limitations in all releases of MSC.Nastran and MD Nastran
The field next to the error
number indicates the version that the error is corrected. The "version
is the version on the f06 title page". Recent versions are sometimes
referred to by the CD id as follows:
MSC.Nastran 2005R3 = 2005.5.0
MSC.Nastran 2005R3b = 20005.5.2
MD Nastran R1 = 2006.0.0
MSC.Nastran 2007r1 = 2007.0.0
MD Nastran R2.1 = 2007.1.0
Note that intermediate patches (point releases) may be found at:
http://www.mscsoftware.com/support/software_updates/
"GL" in this
field stands for a General Limitation which indicates a fix is not planned.
Continuous updates to the error list are available to
MSC.Nastran clients on the MSC web page at http://www.mscsoftware.com.
The site may be located by clicking on "Services" and "Support".
Major Capabilities
A list of major capabilities is provided to assist the analyst in
choosing key-words to search for to locate error that may impact
their current project.
Error Description
Each error has a heading with as many as three entries. The first
entry identifies the major capability affected and is also listed in
the major capabilities index. The second entry identifies either the
name of the module in which an abnormal exit occurs or the card type
affected if computed results are not satisfactory. (For abnormal
exits, the last module name that appears in the Performance Summary
Table is usually the module where the exit occurs.) The third entry
gives the symptoms of the error, such as, the MSC.Nastran system or
user message number printed just prior to termination or a description
of a "machine-dependent error". Other symptoms might be missing
output or wrong answers. Error reports are updated when more facts or
better avoidance techniques become known.
Knowledge Base
The error list may be queried through a relational database at:
http://www.mscsoftware.com/products/nastran_support.cfm
A list of the major categories follows:
Accounting
Acoustic Analysis
Aeroelastic Analysis
Authorization
Axisymmetric Fluid Elements
Beam Library
Buckling Analysis
Buckling & Differential Stiffness
Case Control
Complex Eigenvalues
Component Mode Synthesis
Composites
Cyclic Symmetry
DBC/TRANS/ACCESS
DMAP
Database
Design Sensitivity
Documentation
Dynamic Reduction
Dynamic Response Analysis
Eigenvalue Analysis
Element Strain Energy
Elements
Estimate
Executive
Executive Limits
Exterior Acoustics
External Superelements
File Management Section
Frequency Response
Frequency Response and Random Analysis
Gap Constraints
Geometric Nonlinearity
Grid Point Force
Grid Point Stress
Grid Point Stress Discontinuities
Heat Transfer Analysis
Hydroelastic Analysis
Hyperelastic Nonlinear Analysis
Inertia Relief
Installation
Interface Elements
Iterative Solver
Limitation on Problem Size
Loads
MSC/ACCESS
MSGMESH, MSGSTRESS, MSGVIEW
Material Nonlinear Analysis
Materials
Matrix Methods
Method Selection
Miscellaneous
Modal Augmentation
Nonlinear Analysis
Nonlinear Eigenvalue Analysis
Nonlinear Slide-Line Analysis
Nonlinear Static Analysis
Nonlinear Superelement Analysis
Nonlinear Transient Analysis
Nonlinear Transient Heat Transfer
Old Design Sensitivity
Online Documentation
Optimization/Design Sensitivity
P-Elements
Parallel
Performance
Plotting
Postprocessing
Response Spectra
Restarts
Rigid Elements
SSSALTERS
Security
Sequencer
Single Point Constraints
SOL 400 (Advanced Nonlinear)
SOL 600 (Implicit Nonlinear - marc solver)
SOL 700 (Explicit Nonlinear)
Static Aeroelastic Analysis
Static Analysis
Submittal
Superelements
Thermal Stress Analysis
Timing Estimate
Topology
Transient Nonlinear Analysis
Transient Response Analysis
Utilities
Virtual Mass
399
70.5
ted Normalization
Eigenvalue Analysis - CEAD, QRG - Unexpec
Complex eigenvalue analysis with

extraction will always normalize
ignored. The Version 70.5 Quick
that point normalization is only
785
69
AG 29 - Infinite CPU Loop
the inverse power method of eigenvalue

to MAX. POINT normalization requests are
Reference Guide has been updated to indicate
available for the det method.
MSGMESH, MSGSTRESS, MSGVIEW - MSGMESH, DI
If MSGMESH is used with the link specification update feature, an infinite loop
occurs. An infinite loop no longer occurs; UFM 53 will be issued indicating an
incorrect format for the mesh entries.
868
70.7
Miscellaneous - PUNCH - Incorrect Format
STRESS(PUNCH) will not properly output the HEXA, PENTA, BEND, BEAM, TRIA6, or
QUAD8 elements. Element margins of safety (ROD, CONROD, TUBE, and BAR
elements) will produce poor punched formats if stress allowables are not given
on the referenced MATi entries.
890
GL
Grid Point Force - GPFDR - UFM 3008
The open core requirement for the GPFDR module can be as large as (6 X
BUFFSIZE + 14 X number of grids) if the grids use a nonrectangular displacement
coordinate system. For problems in basic coordinates, the grid requirement
drops to 8 X number of grids.
1103
UFM 3005
GL
Dynamic Response - TRD, TRD1, FRRD, FRR -
If the MGIV method of real eigenvalue extraction computes modes for

massless DOF with uncoupled stiffness
terms, the eigenvalue is large (1.E+35) as it should be, but the generalized
stiffness is 0.0 (it should also be
1.E+35). Null eigenvectors may be produced.
An avoidance is to use PARAM,HFREQ or PARAM,LMODES to discard these bad
modes in dynamics.
1357
70.5
Aeroelastic Analysis - GI - Poor Accuracy
The linear splines used to connect structural and aerodynamic degrees of

freedom are sensitive to modeling techniques, particularly on short-word
machines. This included all machines except CRAY, CDC and NEC. It is good
practice to have the spline axis coincide with the structural grid points, and
to avoid discontinuities in the lines joining structural grid points by using
separate splines on each side of the discontinuity.
1575
69
Dynamic Response - VDR - No Output
If an OUTPUT(XYPLOT) command is in case control, but there are no other

XYPLOT commands, all printed output requests are ignored.
An avoidance is to put in XYPLOT requests or remove the OUTPUT(XYPLOT)
command.
1679
66
Elements - QUAD4,TRIA3 - Wrong Answers
When the MID4 option of the PSHELL card is used to simulate offset of the
element centerline from the grid

point plane, the element is somewhat too stiff. The error increases with the
ratio of offset to element width.
An avoidance is to use RBAR elements to model the offsets .
1712
GL
M 3002, UWM 979
Frequency Response Analysis - RANDOM - SW
If a non-existent point is referenced in an output request when there are

multiple subcases, the RANDOM module will cease processing at that point and
issue SYSTEM WARNING MESSAGE 3002. The following user warning message is now
issued:
0*** USER WARNING MESSAGE 979, AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID
2000
-ACCE- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA
BLOCK
102
1738
66
Grid Point Stress - Preface - UFM 603
If the SURFACE Case Control card has a continuation card, and the first
words that appear on this card are
OUTPUT SYSTEM, the error occurs.
An avoidance is to start the continuation with another word.
1739
66
DMAP - DIAG 4 - Addressing ERROR
If DIAG 4 is used on restart, the program may exit abnormally at the start
of the run.
The DIAG 4 cross reference output for Label Names will be incorrect if no
labels exist in the DMAP, and the
parameter section of the cross reference will not contain any parameters
although parameters are present.
An avoidance is to put a label in the DMAP.
1758
GL
Cyclic Symmetry - Restarts - Various
In superelement static cyclic symmetry (SOL 81), some restart paths do not
function well. The following
restart paths have been demonstrated to work, using the indicated input and
DMAP Alters. Other types of
restarts can be made, using these techniques.
A. Conventional Superelement Restarts.
Use the same techniques applicable to noncyclic symmetry superelement
analysis.
1. Exit during Phase I.
2. Structural Changes in a Superelement.
3. Load Change Restart
B. Time Limit in a Harmonic Loop
SET N = 0, residual only

SEMG = N
PARAM,RESDUAL,-1 (bulk data)
Input all bulk data, or use PARAM,NODATA,-1 and delete all the bulk data
except PARAM entries.
C. Loads Change in One Tip Superelement, Same Number of Loading Conditions, Sam
1759
Labels
69
Plotting - RF24D20, Superelement - Wrong
If SPC labels at grid points are requested for plotting ("GSPC") and
resequencing is requested, the SPC labels are attached to the wrong components.
An avoidance is to make a separate run for these plots without
resequencing, and insert an EXIT after the RFAlter, or not request the SEKR
operation in superelements.
1765
70.5
4319, UWM 4359
Cyclic Symmetry - CYCLIC2 - UFM 3005, UFM
There are two errors related to the use of the CYSUP Bulk Data entry when
rotational symmetry is applied to a model with three or more segments.
1. If the rigid body rotations are to be supported, but there exists no
stiffness at the components specified on the CYSUP entry, then UFM 3005 may be
issued. But, if components 4 and 5 (out-of-plane rotations) are then
constrained by an SPCi card or a GRID card, in order to avoid UFM 3005, then
UFM 4319 will be issued.
For components 4 and 5, an avoidance of UFM 4319 is to define rotational
springs to ground (e.g., CELAS2).
For component 6 (in-plane rotation), an avoidance of UFM 3005 is to apply a
single-point constraint (e.g., SPCi), which is contrary to Remark 1 under the
CYSUP Bulk Data entry description.
b. The specif
1801
66
Plotting - PLOT - SFM 4276
If modern plate elements are present, and SHRINK or DIAG 34 are requested,
the error may occur.
1802
66
Miscellaneous - Preface - CPU Loop
If the THRU range on an input card is larger than 131,071 for CDC/7600 and
CYBER computers, or 8,388,608 for
CRAY computers, the error may occur. It has been observed on a PLOAD2 card
with a larger range. (Cyber,CDC
7600,CRAY only)
An avoidance is to split the THRU range into smaller sets, so that none
exceeds the limit.
1803
66
Elements - PQUAD4 - UFM 2010
If both PQUAD4 and PSHELL (and/or PCOMP) cards exist in the same deck, the
misleading message references
PSHELL cards. The PQUAD4 card is obsolete, and is removed from current
documentation. It should be replaced with
the PSHELL card. The PQUAD4 card will be deleted from the code on a future
system.
An avoidance is to replace PQUAD4 card with PSHELL cards wherever they
exist as they cause various confusing
errors.
1804
66
Superelements - SELA - Wrong Answers
For large problems, if the first several upstream load vectors are null,
the remaining upstream load vectors
may be ignored. This can be detected with DIAG 20.
An avoidance is to place a token load on all upstream superelements.
1805
66
Elements - PCOMP - Wrong Answers
For layered composite materials with an unsymmetric layup, the generated

transverse shear matrix MID3 is
incorrect.
1806
66
Database - LOAD/UNLOAD - Wrong Answers
If a database is unloaded to a sequential file using the DBMGR //3

command, then restored to a direct access
file using the load command, any keywords stored in the database dictionary
will be lost. Most keywords are only
for diagnostic use (i.e., "SEMGDONE"), and will cause no further errors. The
one exception at present is the
keyword "NOSETRUE", which appears when all grid points are in the residual
structure. This will cause the fatal
message above on PARAM,NODATA or PARAM,DLOAD restarts.
An avoidance is to use the following alter for this type of restart:
ALTER 10 $ MSC/61B, AFTER DBMGR //11
SETVAL //V,N,NOSE/-1 $
1807
swers
66
Matrix Methods - FBS, Method 2 - Wrong An
If a passive group appears within the first 20 columns of a matrix, some

terms may be dropped. The error was first observed on a large static
reduction.
An avoidance is to block Method 2 by using the NASTRAN card entry
FBSOPT=-1, when passive columns occur.
1808
66
Database - DBSTORE - DBM 288
This error occurs when more than 32,768 GINO blocks are stored in a single
database, and a store of an
equivalenced file is attempted. (IBM only)
An avoidance is to use several databases, none larger than 32,000 GINO
blocks.
1809
66
Heat Transfer - HBDY - Wrong Answers
SOL 74 gives wrong answers for nonlinear HBDY types AREA3 and AREA4.
An avoidance is to use the POINT option instead.
1810
66
Elements - Midside Nodes - Wrong Answers
The QUAD8, TRIA6, and HBDY elements use an incorrect average temperature
for material properties when the
number of active grid points is not the same for all elements of the same type.
(Deleted midside grid points are
not active grid points; all connected grid points are active.)
An avoidance is to delete the same number of nodes on all elements of the
same type in the model.
1811
69
Dynamic Response - SDR3 - UFM 4605
If DISP, VELO, or ACCE are requested for a set of grid points and the set
is empty, USER FATAL MESSAGE 4605 occurs.
An avoidance is to remove output requests for empty sets.
1812
11
66
Miscellaneous - Multiple Runs - ITRENT 11
If two or more MSC/NASTRAN executions are made in the same job, the error
may occur. (Univac only)
An avoidance is to submit each run as a separate job.
1813
Response Spectra - PARAM,RSPECTRA,0 - Wrong Answers
The response spectra option provided in transient analysis gives wrong answers
for acceleration spectra at high frequencies. The peak accelerations for high
frequency oscillators will not match the results of a transient analysis where
a stiff spring and small mass have been attached to the structure to directly
represent the oscillator. The displacement and velocity from the response
spectra results will match those of the oscillator represented with spring and
mass.
Avoidance: The user should set the value of delta t on the TSTEP input such
that 10 time steps occur during one cycle of oscillation for the highest
frequency of interest.
1814
66
Matrix Methods - MPYAD - Overflow
If incompatible matrices are input to the MPYAD module, and one is of form
3, an unclear diagnostic results.
A good practice is not to input form 3 matrices to MPYAD, as this
capability will be removed in a future
system. The form 3 matrix [A] can be changed to form 6 by the following steps:
ADD
A, /A6 $ ADD WILL GENERATE PROPER MATRIX
EQUIV A6,A/ALWAYS $ A6 REPLACES A
1815
ut
66
Dynamic Response - XYPUNCH - Missing Outp
The PCHRESP parameter described on p. 4.3-23 (2/15/82) of the MSC/NASTRAN

User's Manual is not implemented.
The function it was to perform (punch TABLED1 cards based on output data) can
be performed with a DMAP Alter.
Delete the XYTRAN module statements, and replace them with an identical
statement except for the sixth parameter.
Set it to S,Y,PCHRESP=0. (MSC/62 only)
1816
swers
66
Material Nonlinearity - SOL 66 - Wrong An
If the large displacement option is used, and more than one rotation is
enforced at a grid point with SPCD
cards, the transformations are incorrect when increments are specified on the
NLPARM card.
An avoidance is to use separate subcases, each with a single increment,
rather than many increments on a
single subcase. (MSC/62 only)
1817
66
Transient Response - TRD1 - UFM 3050
If an IC card is selected in case control in SOL 31, which is illegal, the

wrong fatal message ("insufficient
time") is printed. The correct text can be found under UFM 3051, listed in
Section 6 of the U.M.
1819
66
Elements - EMG - EMGPOM
If HEX8 and HEX20 elements are used with other elements, and there is
insufficient memory available, unclear
diagnostics may result. (IBM, Cyber, CDC/7600, CRAY, Univac only)
An avoidance is to request more memory.
1820
66
Database - DBSTORE - SFM 4167
The maximum number of database dictionary entries is influenced by the

fourth input parameter for the DBMGR
command when creating the database. The default value will almost always
result in more than one GINO block being
used for the dictionary. If the dictionary has only one block, the database
will be unusable. (Univac only)
An avoidance is to insure that the dictionary is assigned more than one
block. This can be determined from
SIM 4162, under the "WRITTEN" entry. This number should be greater than 1 when
the database is created. If it is
not, increase the fourth input parameter to at least twice the value printed
under the "NUMBER OF ENTRIES MAXIMUM" for SIM 4162.
1821
wers
66
Superelements - Documentation - Wrong Ans
The DMAP Alter described in the Application Note of January 1982 titled
"Inertia Relief in Superelement
Analysis" has a typographical error that causes inertia loads of the wrong
sign. The second to last statement on

page 7 should be changed from
SOLVE QRR,QR/CRX/ $ etc.
to
SOLVE QRR,QR/CRX//-1 $
Update pages for the application note will be delivered with the next
newsletter.
1822
ers
66
Material Nonlinearity - MID3 - Wrong Answ
In SOL 66, the values output for transverse shear forces for the QUAD4 and
TRIA3 elements are incorrect if
MID3 (field 7 on the PSHELL card) is nonzero.
An avoidance is to leave MID3 blank.
1823
NOT FOUND
66
Miscellaneous - 1VARY - UFM, CARD TO VARY
Multiple 1VARY cards for the same type of data card may not sort correctly.
1824
Messages
66
Matrix Routines - Method 3 - Various GINO
If Method 3 matrix multiplication is selected, and there is not sufficient

memory available, various system
errors may occur. The method selected can be determined by DIAG 19.
Avoidances are to increase memory, or block Method 3.
1825
66
Elements - Punched Output - Extra Output
If output is requested in punched format, elements whose printed formats

include more than one element per
line will also print the last few elements, if they do not fill the line.
1826
t
69
Cyclic Symmetry - SOL 77 - Parameter Prin
If illegal loads are requested in buckling analysis using cyclic symmetry,

the program branches from the
CYCLIC1 module to the PRTPARM module, then prints all parameters. This
condition can be detected by noting that parameter GEOM3C has the value minus
one. One such case was observed when GRAV entries were selected. This user
error now results in a meaningful fatal message:
0*** USER FATAL MESSAGE 4342,
THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED
ANALYSIS HARMONICS OR SEGMENTS OR
SYMMETRY TYPE.
An avoidance is to check the load entry types against the limitations described
in Section 3.2 of the
Application Manual.
1827
ong Answers
66
Grid Point Stress - Branched Surface - Wr
When requesting stresses for a surface with branches using geometric

interpolation without a value for
tolerance, some stresses at branch points may be incorrect.
An avoidance is to use the BRANCH option.
1828
66
Heat Transfer - CFTUBE - Wrong Answers
If the CFTUBE is used in SOLs 24, 61, or 62, which is illegal, SOL 24
produces wrong answers, and the others
fatal error message GETSTB ERROR CODE 1604 or some equivalent message in the
SSG3 module.
CFTUBE elements are supported only in SOL 74.
1829
1203
66
Database - DBMGR, DBSTORE - IO6600 F.E.
Any database file longer than 262, 143 PRUs may fail with this error on
restart.
An avoidance is to restrict all database files to be under this size. The
size of a database is specified in
GINO blocks. A good approximation of the maximum allowable number is one
million/SYSBUF. (SYSBUF is the size of
the GINO buffer, which has a default of 1792.) Thus with default buffer size,
limit database files to about 8900
blocks. (CDC/Cyber running under NOS only.)
1830
s
66
Aeroelastic Analysis - FA1 - Wrong Answer
The ATEIG subroutine for eigenvalue solution has a limit of 30 iterations.

If convergence is not achieved,
the subroutine continues with intermediate results without giving a warning
message. This yields incorrect
eigenvalues for that condition. This has been detected when implausible real
eigenvalues were produced when
complex eigenvalues were expected.
1831
66
Superelements - UMERGE - SFM 3007
In SOL 62, if a data recovery restart is made while performing no Phase I

operations, the error will occur.
An avoidance is to add PARAM,NORSET,-1 above the subcase level.
1832
66
Static Analysis - RF24D13B - SFM 4275
The error occurs when the RF Alter is used for restarts where only output
requests are changed, but not
loading conditions.
The RF Alter should not be used for this condition. A standard restart
may be used.
1833
66
Material Nonlinearity - SOL 66 - UFM 1105
If CHKPNT YES appears in the Executive Deck, the error may occur at random
places.
If checkpointing is required, use the alter:
ALTER 1 $
PARAM //DIAGOFF//47 $
In general, it is more efficient to recover the input data from the
database rather than use checkpointing.
1834
66
Elements - ROD,HEXA - Wrong Answers
In SOLS. 64, 66, and 99 the following errors occur:

A. ROD elements give wrong answers if they have torsion properties
(J>0.), and the element changes direction,
even slightly, due to large deflection effects.
B. HEXA elements give wrong answers when two of the axes X,Y, or Z (see
U.M. p. 2.4-70) are of nearly equal
length (that is, the element has almost square faces) and are not
perpendicular. (Part B fixed in Version 62A)
1835
66
Plotting - XYPLOT - Poor Efficiency
If a plot is made of a constant function, such that the maximum and

minimum y values are the same, the
automatic scaling algorithm may converge very slowly. This problem has been
observed only on CYBER computers,
where it appeared to be a CP loop.
An avoidance is to set one of the scales manually with the plotting
commands YMIN=0.0; YTMIN=0.0; YBMIN=0.0.
1836
66
Restarts - Preface - IO66RD F.E. 314
For CYBER computers using the SCOPE 3.4 operating system, the error will
occur if the buffer size is greater
than 512 words, and the NPTP is sent directly to TAPE.
An avoidance is to use the "L" parameter on the "REQUEST, NPTP..." card.
1837
66
Executive - SOL 76 - SFM 14
All of the solution sequences will compile in the recommended default

region of 200K octal except SOL 76. It
will compile with an RFL of 205K octal. (CYBER only)
1839
66
Heat Transfer - SPCD - Wrong Answers
If an enforced temperature is input on SPC or SPCD cards in SOL 74, wrong

answers result.
An avoidance is to place the degree of freedom on a SPC1 card, and set its
value with a TEMP Bulk Data card.
1840
t
66
Dynamic Response - OLOADs - Missing Outpu
If plots or print of OLOADs are requested in SOLs 70-72, 75, or 76, and
there are no extra points, the error
occurs.
An avoidance is to place the following alter before the DMAP statement
DBSTORE PGD, etc. For SOL 72, for
example, the alter is:
ALTER
EQUIV
1841
974 $ MSC/62
PP, PGD/NOUE $
66
Matrix Methods - DECOMP - LOGIC ERROR 582
For unsymmetric decomposition with spill, the error may occur. (CYBER
only)
Changes in region size sometime eliminates the problem.
1842
66
Sequencing - SEQP - Various System Errors
If the resequencing module spills in the SEQMR subroutine, various system

errors occur. (CRAY, VAX, UNIVAC
only).
Avoidances are to:
A. Increase the memory request, or
B. Use PARAM, MPCX, -1.
1843
66
Elements - BEND - Wrong Answers
The BEND element produces incorrect element forces and stresses when
thermal loads are applied to them.
1844
66
Elements - PCOMP - Wrong Answers
The interlaminate shear stresses are incorrect for laminae that have
nonzero orientations.
1845
ut
69
Virtual Mass - XYPLOT - Missing Plot Outp
XYPLOT requests for MPRES output are ignored. An avoidance for SOL 31 is:
ALTER 548 $ AFTER MDATA MSC/61, MSC/62
SDR3
OEP,,,,,/OEP2,,,,,/ $
XYTRAN XYCDB,,,,OEP2,/XYPPLOT/SOLTYPE/DSET/S,N,PFILE/
S,N,CARDNO/S,N,NOPLOT $
COND NOPPLOT,NOPLOT $
XYPLOT XYPPLOT // $
LABEL NOPPLOT $
Other solution sequences may also use this alter if appropriate changes
are made to the alter line number.
This error is fixed in the sss solution sequences; however the xyplot request
is pres not mpres.
1846
69
Transient Nonlinear Analysis - XYPLOT - M
issing Plot Output

In SOL 99, an XYPLOT requests may be ignored when there is no printed output
requested.
An avoidance is to request at least one grid point for printed output.
1847
nswers
66
Material Nonlinearity - TABLES1 - Wrong A
In solutions 66 and 99, if the stress-strain curve does not pass through
the origin for FORM=1 the data is
accepted, producing unrealistic answers. On future systems, such input will
cause a fatal error.
1848
66
Superelements - SEP2 - UFM 4222
If SEUSETi cards reference interior points, the error occurs. They may be
applied to exterior points. In
future systems they may also be applied to interior points.
1849
66
Superelements - SEUSET - UFM 315
The card description of this card in Section 2.4 of the User's Manual has
fields 2 and 3 interchanged. The
correct format is:
SEUSET, (SEID), (SNAME), ...
1850
66
Cyclic Symmetry - GPFDR - UWM 2342,2354
In SOL's 81 through 83, the message results when GPF0RCE or ESE output is
requested.
An avoidance is to delete the DMAP line number for the GPFDR module, and
change the APP parameter to APP1.
For example,
ALTER 822,822 $ SOL 81, MSC/62
GPFDR CASEDR,UGVS,KELM,KDICT,ECTS,EQEXINS,
GPECT,PG,QGS,BGPDTS,SILS,CSTMS,VELEM/ONRGY1,
OGPFB1/APP1/V,Y, TINY $
1851
by zero
66
Matrix Routines - MPYTIM - Integer divide
If large problems are run with small memory requests, the error may occur.
An avoidance is to increase the memory request.
1852
66
Restart - Dynamics - No Damping
If a restart is made from SOL 24 to a dynamics solution sequence, any

damping cards present in SOL 24 (i.e.
CVISC) may be ignored.
An avoidance is to delete one damping card on restart and reinsert it.

1853
66
stem Errors (21OCT82)
Executive - 3380 Disk Drives - Various Sy
Users may not run any version of MSC/NASTRAN prior to MSC/62 on an IBM
configuration that references 3380 disk
drives. A variety of I/O related fatal messages may result from the earlier
version's inability to compute
blocksize correctly on these drives. The most likely messages are one or more
of the SFM 4212 codes. Some users
have had limited success by using half-track blocking with Version 61B.
However, use of Version 62 is the
recommended procedure. Furthermore, users may not copy (using IBM utilities) a
MSC/NASTRAN database existing on
non 3380 disks to a file usable by MSC/NASTRAN on a 3380 disk. (IBM only)
This procedure may be accomplished however, by using a short MSC/NASTRAN
DMAP sequence to read the existing
file from the non 3380 disk and then write a
1854
66
Material Nonlinearity - EMG - SFM 3007
If a SOL 66 run restarts from a prior run which had no updates of the
stiffness matrix, the recovered
stiffness matrix may be incorrect.
An avoidance is to restart the run from the beginning.
1855
FM 4276
66
Material Nonlinearity - Contour Plots - S
In SOL 66, when contour plots are requested for both linear and nonlinear
elements, SFM 4276 will occur.
Also, if all elements are linear, SFM 3002 might occur.
An avoidance is to make linear elements into nonlinear elements by setting
the yield stress very high.
1856
66
rge of Upstream database
Superelements - Multiple File databa - Pu
If PARAM, DBSET1 is set to a value greater than zero, the entire upstream
database will be purged during the
SEKR operation.
An avoidance is to repair two database purge statements that are in error.
For SOLUTION 61, the fixes are:
ALTER 440,440 $ MSC/62
DBMGR //5/MODEL/SEID/0/DBSET1//GO$
ALTER 452,452 $
DBMGR //5/MODEL/SEID/0/DBSET1//KTT$
The change involves inserting a "0" parameter before DBSET1, and reducing
the number of slashes after DBSET1
from three to two. Two similar statements will be found in all the
superelement solution sequences, at different
line numbers. They can be found by use of DIAG 14, followed by a search for
statements of the form:
DBMGR //5... GO $, and
DBMGR //5..... KTT $
This error does not affect superelement run

1857
66
essages or Wrong Answers
Miscellaneous - RF24D40 - Various Fatal M
If a user-supplied DMAP loop is provided around this alter, and the FBS
module is within this loop it will
result in various fatal messages or wrong answer after the first pass.
An avoidance is to copy and modify the alter by inserting the following
two DMAP statements;
After the first ALTER statement insert: PARAM //STSR/V,N,SAVE74/74 $
Just after the third occurrence of the SDR2 module insert: PARAM
//STSR/V,N,SAVE74/-74 $
1858
GE 202
66
Miscellaneous - Demand Runs - FATAL MESSA
If two or more MSC/NASTRAN executions are made in the same demand session,
the error may occur. (Univac only)
An avoidance is to free all MSC/NASTRAN files (i.e. PRIXX, and SECXX's)
between executions in demand mode.
1859
66
Miscellaneous - IBM - Compilation Errors
The UTIL data set which is the third data set on the IBM deliverable tape
was incorrectly blocked at 13030
bytes. This is acceptable except for installations having only DASD devices
which support shorter maximum
blocksizes (i.e. 3340 devices). At these sites the UTIL data set, as issued,
cannot be restored. The most
heavily used programs in the UTIL data set are DECKEDIT, NASTPLOT and TECKPLT.
Of these, DECKEDIT and NASTPLOT are
available in the NASTRAN data set which is the second file on the deliverable
tape. TECKPLT is identical with the
program as issued in Version 61 and could be obtained from that source. If any
other programs are required from
the UTIL data set, or any of the above solutions are unacceptable, please
contact MSC. (IBM only)
An avoidance, i
1860
rs or Overflow
66
Material Nonlinearity - TA1 - Wrong Answe
In SOL 66 and 99, Orthotropic Materials defined by MAT2 or MAT9 do not

work in SOL 66 or SOL 99 for any type
of elements.
1861
66
Geometric Nonlinearity - EMA - Overflow
In SOL 64, 66, or 99, if the static displacement vector provided to the
second subcase for differential
stiffness calculations is null, the results of the second subcase may be
implausibly large, or the EMA module may
first terminate due to overflow.
An avoidance is to request loads in the first subcase that will produce a
nonnull displacement vector.

1863
66
Superelements - Dynamics - No Damping
The Application Note of May 1981 describes a method for obtaining

differential stiffness effects in dynamic
analysis by performing a static analysis in SOL 64, followed by a special
restart into SOL 63, or SOL's 67 through
72. At present, damping is not computed in SOL 64, and may not be computed on
the restart run without erasing the
differential stiffness matrix.
The following alter will provide damping:
Alter for damping in SOL 64 /61B or /62
ALTER 62,62 $ MSC/61B/62, SOL 64
EMG EST1,GCSTMS,GMPT,GDIT,GGEOM2,,,/
KELM1,KDICT1,MELM,MDICT,BELM,BDICT/
S,N,NOKGG=1/S,N,NOMGG=1/S,N,NOBGG=1///
V,Y,COUPMASS=-1 $
ALTER 68 $
EMA GPECT,BDICT,BELM,GBGPDT,GSILS,
GCSTMS/BJJ, / $
DBSTORE BJJ//MODEL/0 $
1864
66
Superelements - Documentation - H/SEA
The following errors have been found in the Handbook for Superelement
Analysis, for Version 61.
1. Appendix J, page 3 Deck SEH616A
Add after "DBSTORE EQEXINS..."
DBMGR //7/////-2/UGVS/ULV $
This statement is needed to provide the presence of ULV for the next run,
Deck SEH617. Its absence causes the
data recovery run for the external superelement to terminate without producing
output.
2. Appendix J, pages 4 and 5
Several decks use the DBMGR //3 and DBMGR //4 commands. They use the
default values for the third parameter,
used for "search control". The default value allows several blocks with the
same name to appear in the data base,
which can lead to baffling fatal errors or wrong answers.
It is good practice to set the third parameter
1865
g Answers
66
Geometric Nonlinearity - SOL 66,99 - Wron
If SOL 66 or 99 is used with only LGDISP, the beam element has incorrect
stress recovery output, if I1 does
not equal I2. Output (recovered) stresses are only affected, and the solution
is still correct.
An avoidance is to either:
1. Make a "Dummy" material nonlinear group (w/yield stress set to a high
value)
2. Run only with I1 equal to I2.
1866
g Answers
66
Material Nonlinearity - SOL 66, 99 - Wron
In SOL 66 or 99, a beam element with thermal loads and nonbasic

coordinates used by its end grid points gives
incorrect results.
An avoidance is to use the basic coordinate system to define the beam
element grid points.
1867
69
l Deformation Plots
Cyclic Symmetry - Restarts - Missing Moda
In SOL 48 restarts, requests for modal deformation plots are ignored

unless the requests were also made in the cold start.
The following alter is an avoidance:
ALTER 197 $
MODTRL FCASEBK1 /////1// $
1868
ers
66
Grid Point Stress - Subcases - Wrong Answ
When there are multiple subcases in a run and in a particular subcase

there is a stress request but not a grid
point stress request then the subsequent subcase grid point stress results will
be wrong. This is a stress
recovery error only and does not effect the solution.
An avoidance is to put grid point stress requests (even if for only one
element) in every subcase.
1869
l Message 3029
69
Geometric Nonlinearity - SSG1 - GINO Fata
In SOL 64, if only GRAV Loading is being used, GINO Fatal 3029 will occur
in Subcase 2.
An avoidance is to include a dummy load.
1870
66
correct Resutlsts
Miscellaneous - Composite Element wi - In
Thermal loading at grid points (using TEMP or TEMPD) gives wrong

temperature gradients and corresponding
incorrect results in composite elements.
An avoidance is to apply TEMP loads directly to elements.
1871
66
nswers or UFM 4587
Cyclic Symmetry - Thermal Loads - Wrong A
Temperature load cases, i.e., TEMP(LOAD)=j in SOL 81, combined with other
types of loads will provide
incorrect force and stress output because the thermal strains are not correctly
handled. If temperature loading
only is requested, then UFM 4587 will occur. This situation arises because the
identification number of the
temperature load "j" is not included in the CASEDR data block output by the
SEDR module.
An avoidance is to utilize the following alter:
ALTER
642 $ MSC/63
$ALTER
653 $ MSC/62
TABEDIT CASEDR, CONT,,,/A1 $
EQUIV
A1, CASEDR/ALWAYS $
in the Executive Control Deck, and to include the following DTI cards in the
Bulk Data Deck:
DTI, CONT, 1, CR, [1] , DW, 7, 7, 1, DTI1
+TI1, "j" ENDREC
DTI, CONT, 2, ER, ENDREC
The number in brackets, i
1872
66
Matrix Methods - MPYAD - Mode Error 1
This error condition may occur when multiplying large matrices. It is

further characterized by aborting with
a "P address" between 36000 and 37400. The P address is printed out in the
dump on the line that starts "P =").
This error was reported to be fixed in Version 62A, in a prior report. Field
usage of Versions 62A shows that the
fix was not fully effective. (CYBER, CDC/7600 only)
Avoidances are to:
1. RFL up or down by about half of the largest dimension of any input
matrix.
2. Set the REAL parameter on the NASTRAN card to core size minus the
largest dimension of any input matrix.
Core size may be determined from DIAG 13.
3. Deselect Method 1 and Method 1T. This should be done locally using a
DMAP Alter statement, rather than on
the NASTRAN c
1873
RMs
66
Miscellaneous - PARM Field - Incorrect PA
The PARM option provided in the PROC delivered with NASTRAN allows up to
100 characters of input, based on
inherent JCL limits. (See Section 7.6.2.1 of the A.M.) Submitting more data
results in JCL fatal error messages.
MSC/NASTRAN will process less data than this, however, with the remaining data
set to unpredictable values. The
equation for the limit of data properly processed by MSC/NASTRAN is
4S*7+(OTHERS)*4<41 WORDS, where "S" is the
number of S(I) type parameters, and "OTHERS" is the number of conventional
symbolic parameters. (IBM only)
An avoidance is to stay beneath this limit, and set any remaining
parameters on the NASTRAN card.
1874
66
ing IO6600 1203,1204
Database - COPY to TAPE - Various, includ
For CYBER computers, Section 7.6 of the Application Manual gives examples
of Control Language cards used to
copy databases from disk to tape, then back to disk. The CDC utility program
COPYBF is listed to perform this
task.
Most data centers have had better results when using the COPY utility
program, particularly when the errors
above are encountered. The best advice for individual users is to contact
their data center personnel when

developing these Control Language cards, because each data center may have
modified utilities. The MSC
documentation will be changed to from COPYBF to the COPY utility, after
testing. For example, the line in the
example of page 7.6-345 (April 1981) would be changed from
COPYBF(TAPE,DB01)
to
COPY(TAPE,DB01)
1875
66
Cyclic Symmetry - SOL 81 - Wrong Answers
LOADSET and LSEQ cards may not be used in this solution sequence.
An avoidance is to use the LOADCYi cards, which provide most of the same
functions. In Version 67 UFM 6229
will be issued to inform the user that these commands are not supported in
static analysis with cyclic symmetry.
1876
g Answers
66
Transient Response - Modal Damping - Wron
In modal transient response solution sequences, results for modes with

more than critical damping are
incorrect when the uncoupled method is used. (TABDMP1 input only for damping
results in use of the uncoupled
method.)
An avoidance is to force the coupled method by adding an insignificantly
small damping value to the existing
damping by use of a B2PP DMIG matrix.
1877
66
In modal frequency response, using the DDRMM method (which is now the
default), stresses for end B appear in
the wrong output position.
1878
66
If the input describing BEND elements results in negative radius R-sub-B

or arc angle THETA B greater than 180
degrees, both of which are illegal, a user fatal message is not produced.
Implausible answers result.
1879
66
Restarts - Version 61B to Versi - SFM 41
On restarts between different versions, new features may cause restart

errors. One example is the element
strain energy density feature introduced in Version 62. It requires a file
named VELEM, which contains element
volumes.
One avoidance is to force execution of the module which generates the
file. For example:
ALTER
ALTER
ELTPRT
1881
43, 43 $ SOL 24, OR

50, 50 $ SOL 3
,,,,,EST/VELEM/V,Y,EST=2$ DELETE, REINSERT FORCE RESTART
66
Superelements - DMIG - Continue on Error
If PARAM, ERROR, is used, the design intent is that fatal errors in Phase
I will cause termination of
processing for one superelement, then branching to the next superelement.
Termination of the run should occur
after all Phase I operations have been attempted.
It has been found that certain Phase II or Phase III user fatal errors may
not cause termination of the run.
An example is input of conflicting data for one or more elements of a P type
matrix. If PARAM, ERROR, 0 is used,
all pages of output should be scanned for error messages.
1883
66
Database - Store or Fetch - SFM 4212
ERROR CODE 41, or IO 370 FATAL MESSAGE 600 (30NOV82)

This error occurs when more than one block is stored per track. An
avoidance is to use full track blocking,
that is, adjust BUFFSIZE on the NASTRAN card to be equal to the value given for
the device being used as given on
page 7.6-8 of the Application Manual. Note that this implies that old data
with smaller buffsizes must be
discarded, and that the REGION parameter may need to be increased, as described
in the reference. (IBM only)
If an old database has encountered this problem, and it is required to
restart from it, rather than discard
it, the following strategy may work:
a. Purge enough files at the end of the database to release the last [M]
blocks written on, where [M] is the
number of blocks per track
1884
2)
66
Executive - Installation - Various (5OCT8
MSC/62 will not operate on VS1 operating systems or older operating

systems because of the absence of code for
modulo storage devices.
An avoidance is to install the PTF which supports modulo devices. It is
not necessary to have these devices
available, merely to have provisions for them in the operating system.
1885
utput
66
Frequency Response - Subcases - Missing O
In SOL 30, if looping occurs, output requests after the first subcase will
be ignored. Looping is caused by
changes of FREQ, SDAMP, TFL, or P type DMIG's cards between subcases.
An avoidance is put in the DMAP Alter:
ALTER 622 $
FILE IQG1=SAVE/IPHIG1=SAVE/
IES1=SAVE/IEF1=SAVE $
FILE IQG2=SAVE/IPHIG2=SAVE/
IES2=SAVE/IEF2=SAVE $
TABPT
TABPT
IQG1,IPHIG1,IES1,IEF1//$
IQG2,IPHIG2,IES2,IEF2//$
1886
ut (12OCT82)
66
Dynamic Response - Restart - Missing outp
If no output results on a data recovery restart in SOL 30 or SOL 31, or

some requested items are not present,
the cause is usually because the modal output files were retrieved from the
OPTP. Only data selected on the prior
run may be selected on the restart run. The modules that generate this output
(SDR1, SDR2) can be scheduled for
reexecution by deleting any PARAM,DDRMM,(N) cards that exist, and reinserting
them. If there are none, insert the
default value (0) for N, that is, add PARAM, DDRMM, 0 to the bulk data.
1887
66
o Loads Available
Material Nonlinearity - Documentation - N
The example problem shown on pp. 2.14-111,-112 (April 1982) is missing

two cards, and will not run to
completion. The cards needed are:
FORCE,175,10000,10,50.0,-1.0
FORCE,175,10001,10,50.0,-1.0
1888
66
nt System Errors
Superelements - Preface - Machine Depende
For XYPLOT requests, if there are no cards between OUTPUT(XYPLOT) and

SEPLOT (N), the error may occur. For
example SFM 4276 GREAD ERROR CODE 3002 appears on VAX computers.
An avoidance is to insert a card between the two listed. For example,
PLOTTER NAST is adequate.
1889
4)
66
Aeroelasticity - AMG - Divide by zero (0C
Some aeroelastic models using CAER02 cards cause divide check error in
Subroutine AMGPFS on IBM Version 62 due
to a compiler error. (IBM only)
A super-zap avoidance is available from MSC.
1890
ds
69
Superelements - Restart - No Inertial Loa
If PARAM,SOLID is changed on restart, the mass matrix must be regenerated

by the SEMG operation. If it is
not, inertial loads in static analysis will be null (GRAV, RFORCE) and
superelements will be massless in
dynamic analysis.
A less costly avoidance then reexecution of the SEMG operation is to add
another name to the stored mass
matrices by use of the database equivalence statement:
BEGIN $ STANDALONE DMAP PROGRAM
DBMGR //7/C,Y,OLDSOLID=0/C,Y,SEID/
C,Y,NEWSOLID/C,Y,SEID//MJJ/MJJ $
END $
CEND
...
...
BEGIN BULK
PARAM,NEWSOLID,2
PARAM,SEID,10
ENDDATA
This is a stand-alone run which restarts from a run which used the default
for PARAM,SOLID (which is zero). It is run in
1891
66
Aeroelasticity - Bodies - UFM 2025
When SOL 75 or 76 has bodies and interference groups combined in the bulk
data a UFM 2025 will occur during
execution of the GI module. This is probably caused by having bodies in the
first group.
An avoidance is to try to keep all bodies in last group.
1892
66
Sequencing - Preface - UFM 316
If the SEQP module is requested to punch SEQGP cards, and these cards are
used on a subsequent run, some SEQID
numbers may not be unique, which causes the preface error, referencing the
SEQGP cards. This has been observed on
models where some grid points are not connected by elements.
Avoidances are to:
1. Discard the SEQGP cards and rerun the sequencer. The module that
processes these card images performs
correctly when duplicate SEQID's are present, or
2. Delete the cards in error, and replace one of the illegal SEQID's by
adding .1 to it. That is, change
10002 to 10002.1
1893
66
FATAL ERROR 201 (21OCT82)
Matrix Methods - Decomposition - I/O 6600
If spill occurs during matrix decomposition, the error may occur. (CYBER
and CDC/7600 only)
Avoidances sometimes are to:
1. Place the following Executable code Patch on
the NASTRAN card. Note that the character in
front of decimal points is an O, not a zero:
SYSTEM
(O.6251)=O.04000221510400022151 $ CYBER, /62
or
SYSTEM
(O.6014)=O.04000074530400007453 $ CDC/7600, /62
or
2. Increase or decrease core by twice the order of the matrix,
or
3. Change the BUFFSIZE

1894
OR CODE 3002
66
Superelements - SEMA - SFM 4276 FREAD ERR
This error has been observed when there are more than 10 superelements. A
machine-dependent error message
results. Usually, the message number is SFM 4276 FREAD ERROR CODE 3002.
An avoidance is to increase the memory request.
1895
66
Restarts - SOL 24,Heat - Restart Failure
On UNIVAC 1100/80, Version 61B will fail with a contingency type=2 message
when a restart, with plot requests
is made in SOL 24,HEAT and module GP2 is not executed.
An avoidance is to run Version 62 or include the following alter to
Version 61B:
ALTER 15
TABPT PSIL // $
1896
ng Results
66
Material Nonlinearity - Gap Element - Wro
In Solutions 66 and 99, the shear force is incorrect for GAP elements with
tension (i.e. open). If shear
force is not required, set KT=0 on the PGAP data card. If shear force is
desired, the following avoidance will
assure that open gaps have a tiny compression: Set F0 on the PGAP data card to
KB*(maximum expected opening), with
KB tiny.
1897
M 2025
66
Aeroelasticity - Interference Groups - UF
Whenever interference groups are used in conjunction with bodies on the

first interference group, the GI
module will produce UFM 2025. This is caused by APD preparing an incorrect
CSTMA data block.
1898
66
Cyclic Symmetry - CYCLIC4 - SFM 3007
If the size of the matrices after the

than 65,536, SWM ****, "BAD TRAILER FOR
FILE ****" will appear several times, then
trailers will indicate that the
number of rows or columns of some matrices
above.
An avoidance is to put ASETi cards on
1899
66
cyclic transformation is greater

the run will eventually fail. The
will be greater than the limit shown
boundary points.
DMAP - OUTPUT4 - Wrong Answers
For the BCD option, if the first column in a matrix to be output contains
null columns, the matrix output may

be missing columns. If there are more than one matrix output per DMAP call,
the matrix produced by OUTPUT4 will
produce a "CONVERSION ERROR" if processed by INPUTT4.
Avoidances are to:
1. Put one small number in null columns,
2. Output only one matrix per OUTPUT4 DMAP call.
1900
66
Wrong Answers (22OCT82)
Matrix Methods - MPYAD Method 1 - 0C4 or
If large regions are used, the error may occur. This error has been
observed when using Method 1 on a
multiply of a 300 row square matrix times, a 300 row by 10 column matrix. The
first column of the answer was
correct, with other columns missing many numbers. (IBM only)
Avoidances are to:
1. Decrease the region to 800K Bytes, or
2. Deselect Method 1
1901
66
DMAP - INPUTT4 - Wrong Answers
1. If the input matrix is in a different precision than the output

matrix,the matrix trailers will be
calculated incorrectly, leading to wrong answers or various system errors in
modules which use these files.
2. The binary output format, using the dense matrix option, produces bad
trailers on short work machines.
Again, modules which use these files will have unpredictable behavior.
An avoidance is to request the sparse matrix option on short word machines.
1903
7777
66
Database - DBSTORE - SFM 4276 ERROR CODE
This error occurs when more than 32,768 GINO blocks are stored in a single
database. (VAX only)
An avoidance is to use several databases, none larger than 32000 GINO
blocks.
1904
Alters
66
Miscellaneous - VAX/VMS 3.0 - Multiple RF
When using multiple RF Alters, the plus symbol, (+) in the NASTRAN command
is illegal under VAX/VMS 3.0
operating system.
An avoidance is to change the NASTRAN procedure so the reference to RFA in
the SUBMIT command is "RFA".
1905
66
Restart - SOL 30, 31 - Poor Efficiency
For restarts from SOL 3 to SOL 30 or SOL 31, the default value of
parameter DDRMM may not be set properly,
leading to use of a more expensive data recovery method. There have been a
series of such DMAP errors over the
last few systems, which occur in different paths through the program.
A good practice is to place PARAM,DDRMM,0 in the deck in SOL 30 and 31,

and not rely on defaults.
1906
66
Miscellaneous - Preface - UFM 327
Large Bulk Data Decks may fail with UFM 327, especially when there exists
a large number of cards of one type;
such as, DMIG. Symptoms of the error appear after the bulk data has been
sorted. Two symptoms are: (1) data
appearing in different fields than the unsorted input or (2) cards sorted in
the wrong order. (IBM only)
For DMIG cards, a possible avoidance is to use the INPUTT4 module as an
alternative to matrix input.
The error exists in load module LINKNS01 and can be corrected with the
SUPERZAP program. The following data
should be supplied to SUPERZAP to make the fix: CSECT=DEFFLD, OFFSET=006A,
VER=95F93000, and REP=95F92000.
1907
66
Eigenvalue Analysis - READ - GINO 1409
If the F1-F2 option is used on the EIGR card using the GIV method, a
SUPORT card is used, and F1 is below the
frequency of the first flexible mode, the error may occur.
An avoidance is to use the ND field instead of the F1- F2 fields.
1908
66
Aeroelasticity - AMP - 0C1
This error has been observed in Version 62. (IBM only)

An avoidance is:
ALTER
982
PRTPARM //$
1909
DE 3012
66
Superelements - INREL - SFM 4276 ERROR CO
This error may occur if dynamic reduction or component mode synthesis is

used.
An avoidance is to deselect Method 4 transpose matrix multiplication on
the NASTRAN card.
1910
66
Elements - MAT2 - Input data ignored
If a pair of MAT1 and MAT2 cards have the same ID (which is illegal), the
MAT1 card is used, and the MAT2 card
is ignored.
1911
66
Executive - XCEI - Gino 1102
If DTI or DMI cards are present, and data pool housekeeping occurs, the
error may occur. This condition is
most likely to occur when there is extensive looping, such as in superelement
or cyclic symmetry processing.
An avoidance is to store the DTI and DMI cards in the database on a
seperate run, and perform the runs where
looping occurs by fetching these files from the database. This function is
performed automatically in the
superelement sequences for the DTI cards SETREE, ESTDATA, SPECSEL, and SPSEL.
That is, if they are present on a
run, they may be deleted on subsequent runs, where they will be automatically
fetched from the database.
1912
66
Elements - IFP - UFM 4384
The error occurs with PCOMP cards when unsymmetric ply orientations of
exactly plus or minus 45 degrees are
used, and the MAT8 card has a thermal coefficient of expansion.
An avoidance is to input the orientations at plus or minus 46 degrees.
1913
rs or Overflow
66
Material Nonlinearity - TA1 - Wrong Answe
In SOLs 66 and 99 with large displacements, anisotropic linear materials

produce incorrect results when the
material orientation is nonzero or MID2 is not equal to MID1 in shells. Use
only MID2=MID1 and THETA = 0.0 on
QUAD4, TRIA elements.
This error is related to error 1860, which was partially fixed for
MSC/62A. See error reports for MSC/62 for
behavior in that version.
1914
66
Elements - HEXA - Wrong Answers
Wrong Loads occur with the HEXA element under thermal loads when using the
integration method 2 (default) and
the element geometry has taper (i.e. when the Gauss point Jacobians are
unequal).
An avoidance is to use the new integration method 0.
1915
66
Elements - SDR2 - Floating Point Overflow
A plate element (QUAD4, QUAD8, TRIA3 OR TRIA6) with a very small thickness
may fail in SDR2 if the thickness
cubed underflows to zero, even if membrane analysis is only requested.
1916
66
Matrix Methods - FBS - Poor Efficiency
Method 2 FBS time estimates are overly conservative, and can lead to
"insufficient time" fatal errors or use
of Method 1 when Method 2 would be cheaper.
A rule of thumb is that if Method 1 requires more than five passes, Method
2 is probably cheaper. Method 2
can be forced with the FBSOPT Keyword on the NASTRAN card. The insufficient
time exits can be prevented by placing
a large value for time limits on the executive control card TIME.
1917
UWM 4420
66
Heat Transfer - PENTA - Wrong Answers or
UWM 4420 or "NEGATIVE TERMS ON THE FACTOR DIAGONAL" or other messages can
occur when left handed PENTA
elements are used in Heat Transfer.
An avoidance is to use right handed numbering convention.
1918
estarts
66
Material Nonlinearity - Superelements - R
In SOL 66, multiple file databases and usage of PARAM,RESDUAL will not
work.
1919
estart Failure
66
Material Nonlinearity - Superelements - R
In SOL 66, with tip superelements, if the SEID is less than or equal to
the number of nonlinear loops, the
superelement data may be purged thus crippling the restart capability.
An avoidance is to use large SEID numbers (larger than the DMAP loop
indices).
1920
66
Material Nonlinearity - SOL 66 - SFM 3081
In SOL 66 when MPC's are used in a subcase and then removed in a later
subcase, SFM 3081 and SFM 3007
(subroutine NLMAPS) will occur.
An avoidance is to include a dummy MPC in the subcase where the real MPC
had been removed.
1921
n
66
Static Analysis - SSG1 - Illegal Operatio
If a METHOD card is present, but a LOAD Case Control card is not present,
an error may occur. On IBM, for
instance, an 0C1 message appears.
An avoidance is to add a LOAD Case Control card.
1922
66
Sequencing - PARAM,START - CPU Loop
The PARAM,START card, used to influence the starting point used by the
sequencer, may cause an endless loop in
the SEQP module. This parameter should not be used.
1923
66
Aeroelasticity - UMERGE1 - SFM 3007
This error occurs in SOL's 75 and 76 when PARAM,OPPHIPA,1 is used.

An avoidance is to add the following alter:
ALTER
968,968 $ MSC/62, SOL 76
ALTER
905,905 $ MSC/62, SOL 75
EQUIV
PHIKA,PHIKH/NOUE
COND
SKPPKH,NOUE $
PARAML PHIDH//TRAILER/1/V,N,NOMDS $
PARAM
//C,N,SUB/V,N,NOIS/NOMDS/NOUE $
MATGEN /PHIDV/6/NOMDS/NOIS/NOUE $
MERGE
PHIKA,,,,PHIPV,/PHIKH/1
LABEL
1924
Various
SKPPKH $
66
Superelements - PARAM,NODATA - SFM 3001,
The DYNAMICS data block is not properly recovered from the database for
data recovery restarts. This may lead to errors for modules which require it
for input, such as RANDOM.
An avoidance for this type of restart is:
ALTER
1100 $ BEFORE DPD MSC/62, SOL 71
DBFETCH /DYNAMICS,,,,/ $
1925
utput
66
Aeroelastic Analysis - SOL 75 - Missing O
Flutter Analysis with the KE-method does not loop in the FA1 module as
described in the Aeroelastic
Supplement. The FLUTTER card selects a list of density ratios, Mach numbers
and reduced frequencies for the
KE-method.
When the KE-method is used, the first Mach number on the referenced FLFACT
card will use all the density
ratios and all the reduced frequencies on their respective FLFACT cards. The
remaining Mach numbers will use only the first density ratio. The printed
flutter summaries are correct, but not all of the requested output will be
computed. It is recommended that only one Mach number appear on the FLFACT
card per run. The remaining output can be obtained by a restart, while
referring to only one Mach number.
1926
FM 3007
66
Differential Stiffness and Buc - READ - S
In SOL 65, if superelements are present, the differential stiffness matrix

is not stored in the database,
leading to the above error, or perhaps others.
An avoidance is to add the following alter. It also eliminates the use of
PARAM,SOLID1. The DMAP will be
changed in a similar manner for MSC/63, so that this alter will provide a
database that will be upward compatible
with MSC/63.
ALTER 203,203 $ REPLACE FETCH ON UGVS. MSC/62A. SOL 65
DBMGR //11/SOLID/SEID/DBSET3/S,N,NP//UGVSTAT
$ TEST FOR PRESENCE
COND LBLREST,NP $
DBMGR //9/SOLID/SEID/SOLID/SEID/DBSET3/UGVS/UGVSTAT
$ RENAME
LABEL LBLREST $ AVOID RENAME ON SOL65-SOL65 RESTART
DBFETCH /UGVSTAT,ETT,,,/SOLID/SEID//DBSET3 $
ALTER 209,209 $
EMG EST,CSTMS,MPT,DIT,GEOM2S,UGVSTAT,ETT,EDT
/KDELM,KDDICT,,,,/1/0/0/
1928
66
Elements - Thermal Loads - Wrong Results
In SOL 66 or SOL 99 with thermal loads on solid elements, if some subcases

do not have thermal loads, wrong
results will occur. Run may also crash in subroutine NHEXD or NPEND.
An avoidance is to include a thermal load that has no delta temperature in
subcases where thermal loads are
not wanted.
1929
66
Elements - Thermal Loads - Wrong Results
In SOL 66 and SOL 99, nonlinear HEXA and PENTA elements give wrong results
when thermal loading is present.
(CDC and CRAY only)
1930
66
Executive - SOL TRANSIENT - UFM 4372
If the solution sequence request SOL TRANSIENT etc. is used, SOL 99 will
always be selected, regardless of
whether words such as DIRECT or MODAL are present. This
includes the words that should select SOL's 27, 31, 69, 72, or 89. For
nonsuperelement solution sequences,
the run will terminate after the sequencer, without diagnostics. In
superelement solution sequences, UFM 4372
occurs.
An avoidance is to use a solution number rather than words for all
transient analysis solution sequences.
1931
66
Superelements - SEP2 - Illegal Operation
If no SUPER cards are present in the Case Control Deck, and

exist, the error may occur. The error
actually occurs in the PARAML module, after the SEP2 module, but
module does not cause messages in the
Performance Summary Table. For example, "MODE ERROR" appears on
computers.
An avoidance is to place a SUPER=ALL card above the subcase
1932
66
SET cards
the PARAML
Cyber
level.
Elements - SOL 99 - Wrong Results
Stress output for the HEXA and PENTA elements in SOL 99 is wrong. This is
a back-end recovery error only.
1933
M 3002
66
Frequency Response Analysis - MODACC - SF
If there is insufficient time available to compute all solutions requested

in the FRRDI module in SOL 26, UWM
3045 appears, followed by SFM 3002.
An avoidance is to reduce the numbers of frequencies on the FREQi cards,
and/or increase the value on the TIME
card. On restarts, it is necessary to force the FRRDI module to execute. A
new, unreferenced FREQ card added to
the Bulk Data Deck will cause this type of restart.
1934
66
fficient Privilege
Miscellaneous - Checkpoint to Tape - Insu
For Version 3.0 Operating Systems, MSC/NASTRAN does not recognize tapes.
(VAX only)
An avoidance may be to use the following .COM file: ASSIGN "MTA0" NPTP or
ASSIGN "_MTA0" NPTP
1935
66
Miscellaneous - Preface - Various
Imbedded blanks are not allowed on most Bulk Data card fields, and will
usually cause preface errors.
However, fields starting with zero (i.e. "0 1") will not cause the error to be
detected.
This error will be fixed in Version 63. It will also cause fatal error
messages for other illegal cards that
may be accepted on earlier versions. One such example is a real number input
as - 1.0. The blank after the minus
sign is illegal.
1936
66
Eigenvalue Analysis - CEAD - SFM 3011
For the complex inverse power method, if the search region contains no
roots at all, the noninformative
diagnostic may occur.
An avoidance is to move the search region nearer to the roots. Their
imaginary part may be estimated by
finding the real roots of the system in SOL 3.
1937
66
Elements - HEXA and PENTA - Wrong Results
For Version 62, the default for IN on the PSOLID card was changed from
IN=0 to IN=2. If a HEXA or PENTA
element has mid-side nodes the default IN=2 will give questionable results.
An avoidance is to set IN=3 for those particular elements.
1938
66
Matrix Methods - MPYAD - Wrong Answers
If Method 1 is used when multiplying complex double precision matrices,

wrong answers may be produced. This
has been observed in an aeroelasticity problem, where the QHH matrix output
from the AMP module had null columns
where there should be full columns. The relevant input to the AMP module is
usually single precision here, but was
changed to double precision with a DMAP Alter. (IBM only)
An avoidance is to block Method 1 on the NASTRAN card.
1939
66
Dynamic Reduction - READ - UFM 3005
Generalized Dynamic Reduction sometimes produces singular MXX matrices.

Typical model characteristics for
this error include large masses for enforced displacement and/or uncoupled
modes (for example, some modes dominated
by plate bending, with other modes dominated by plate extension). The problem
appears most often on long-word
machines. (CRAY, CYBER, CDC/7600 only.)
An avoidance is to reduce PARAM,EPSBIG from its default value of 1.E12.
One deck that failed with UFM 3005
produced good modes when PARAM,EPSBIG,1.E8 was used. This parameter controls
the number of raw eigenvectors
discarded when they are not orthogonal to other vectors. A lower value of the
parameter results in discarding of
more vectors.
1941
66
ELEMENTS - QUAD4,TRIA3 - WRONG ANSWERS
The stress output is incorrect for the subcase with no thermal loads when
that subcase follows another subcase
where a TEMPP1 card is referenced.
An avoidance is to add a TEMP(LOAD) request that references a zero
temperature rise.
1942
66
umentation Error
Material Nonlinearity - GAP Element - Doc
The documentation of shear force on the GAP element is incorrect. UM

p.2.4-284c, figure 4 should have Fo
replaced with zeros on all the given equations.
1943
66
Elements - CNGRNT - SFM EMGPOM
The use of the CNGRNT Bulk Data card when referencing HEXA or PENTA
elements may fail.
MSC is considering deletion of the CNGRNT card in future versions.
Clients who may experience hardships
because of this should contact Client Service at MSC.
1944
66
Plotting - Contour Plots - Wrong Answers
Contour plots which use the "MID" option do not provide correct answers
for principal stresses and Hencky-Von
Mises Stress.
1945
66
Cyclic Symmetry - LOADCYH - Wrong Answers
If the scale factor S1 (field 6) in a LOADCYH card is different from 1.0,

and L1 (field 7) of the same card
refers to a GRAV or RFORCE type load, erroneous results will occur.
An avoidance is to use the desired scale factor value in Field 3 of the
same card.
1946
66
Superelements - SEP2 - Wrong Answers
If an SPC1 card uses the THRU option, and the range is within the range of
exterior plus interior points of a
superelement, but there are no grid points in the range of the THRU, one grid
point below the THRU range and one
grid point above the range will be incorrectly placed in the SPC set. This can
either cause set conflicts in the
GP4 module, or unintended constraints to ground. (All computers but VAX)
An avoidance is to use an explicit set of grid points on the SPC1 card,
rather than on the THRU option.
1947
66
Superelements - SEP2 - CPU Loop
If a superelement has illegal subcases an endless loop may occur in the

SEP2 module. This has been observed
on VAX computers, for an image superelement with no subcases at all.
An avoidance is to use the partially expanded subcase structure explained
in Section 5.3.5 of the Handbook for
Superelement Analysis. This method places a SUPER=ALL card above the subcase
structure.
1948
66
Elements - Transverse Shear - UWM 3103
Composite elements fail to generate correct MAT2 cards if three or more

layers are identical.
An avoidance is to make a slight variation for each ply's thickness or
material orientation.
1949
66
Superelements - SEMA - UFM 4156
If generalized dynamic reduction is requested for several superelements,

then one superelement performs
dynamic reduction, but a subsequent one does not, the error occurs downstream.
This happens because there are no
natural frequencies below FMAX, and the KLAA matrix for the first superelement
is erroneously reused for the second
superelement.
An avoidance for SOL 63 is:
ALTER 712,703 $ MSC/62A. DELETE
$
THAT ALSO HAS KLAA
DBSTORE MLAA//SOLID/SEID/DBSET2
ALTER 660 $ AFTER LABEL CARL6
DBSTORE KLAA//SOLID/SEID/DBSET2
DBSTORE GOAQ//SOLID/SEID/DBSET1
Then, rerun the SEMR operation
fatal message.
1950
66
SIMILAR STORE
$
$
$
for the upstream superelement named in the
Superelements - SEDR - SEDR FATAL ERROR
If PARAM,SOLID is changed on restart, but the SEMG operation is not

reexecuted, the error occurs. This
happens on load change restarts.
Avoidances are to:
1. Also rerun SEMG - it is relatively
cheap, or
2. Use the following alter to move a
DMAP statement. The line numbers
here are based on SOL 61.
ALTER 206,206 $ DELETE HERE. MSC/62A
ALTER 219 $ MOVE IT HERE
DBMGR //7/MODEL/PEID/SOLID/SEID/DBSET1/
EQEXINS/EQEXINS $ EQUIV
1951
s
66
Grid Point Stress - GPSTR2 - Wrong Answer
If DIAG 33 (request for Von Mises Stress) is used, the MAX SHEAR stress
printed in the grid point stress
output is wrong; it is the Von Mises Stress.
1952
66
Elements - CBEAM - Wrong Answers
The BEAM element mass matrix is not correct when neutral axis and
nonstructural mass axis offsets are
simultaneously used on the y and z element coordinate system. The resulting
mass matrix is negative definite and
results in negative eigenvalues that are neither computational zeros nor
machine infinities.
An avoidance is to set the mass density to zero on the MAT1 card, and
input the beam element masses on CONM2
cards. Another avoidance is to use only a y or z offset (but not both) by
transforming the element coordinate
system.
1953
66
DMAP - DIAGONAL - Wrong Answers
The WHOLE option in conjunction with the identity option for the DIAGONAL
module produces an identity matrix
instead of a whole matrix of ones.
1954
66
Elements - SSGHT - UFM 2157
The following elements, QUAD4, TRIA3, HEXA, and PENTA are likely to
encounter this overlay error in nonlinear
heat transfer (SSGHT module) whenever TEMP(MATE) and/or coordinate systems are
used. (IBM only)
1955
nswers
66
Material Nonlinearity - NLELAST - Wrong A
The NLELAST type material nonlinearity identified on a MATS1 card in Field

4 does not work for three
dimensional (solid) elements in Version 62A.
1956
GL
, GAP Element - SFM 4202
Differential Stiffness and Buckling - QRG
The GAP element has no differential stiffness and produces SFM 4202 when used
in conjunction with Solution 64 or SOL 4.
1957
66
Superelements - INREL - 0C1
This error has been observed in Versions 62 and 62A. It is an overlay

error that occurs when the GOA data
block is purged, i.e. no omitted degrees of freedom. (IBM only)
An avoidance is to put a physical degree of freedom in the a-set. This
will cause formation of GOA.
1958
66
Database - DBMGR - Wrong Answers
The DBSTORE operation will not purge superseded versions of data blocks on
restarts when multiple database
files (e.g., DB01, DB02, etc.) are present in the database subset.
Subsequent fetch operations may fetch the superseded data block. Any one
of a number of errors may occur
depending on the type of restart and input data deck changes made.
A sure avoidance is to hand purge all data blocks to be regenerated.
Another avoidance is to number the most
empty database file first, that is, name it DBO1.
1959
66
Material Nonlinearity - NLCOMB - SFM 3007
Solution 66 (Material Nonlinearity) will produce the System Fatal Message

3007 when two subcases request the
same TEMP(LOAD)=XX selecting only a TEMPD card (no TEMP or TEMP1, etc.) and the
second subcase has an additional
applied load.
An avoidance is to avoid repeating the same temperature set
identification, by supplying the same data with a
different set identification number.
1960
66
Erroneou - No Message
Limitations on Problem Size - Missing and
Whenever large output files (OFP records) and PLOAD1 cards are used,
output problems may occur.
An avoidance is to increase memory or reduce the output request. Another
avoidance is to use an ALTER to
directly OFP the SDR2 output and avoid the SDRX module which causes the error.
1961
66
Aeroelasticity - FA1 - 0C4
When the KE-method is used with two Mach numbers on the FLFACT card
referenced by Field 5 of the FLUTTER an
0C4 error is produced on IBM versions 61B, 62, and 62A. It is caused by an
overlay error in the FA1 module.
An avoidance is to use only one Mach number on the referenced FLFACT card.
1963
66
RNL - Wrong Answers
Material Nonlinearity - NLITER, NLTRD, SD
Wrong answers for SOL 66 or 99 are obtained when shear stress exists in 3
dimensional elements with Tresca,
Mohr-Coulomb, and Drucker-Prager yield criteria.
An avoidance is to use Von Mises criterion with 3-dimensional elements.
1964
66
RNL - Wrong Answers
Material Nonlinearity - NLITER, NLTRD, SD
A wrong stress solution for SOL 66 or 99 can occur when a TABLES1 card is
used to define more than two
piecewise linear curves for plastic material properties of a one dimensional

element.
An avoidance is to define plastic properties of one dimensional elements
on MATS1 card without using TABLES1.
1965
69
Miscellaneous - SOL 5 - SFM 3007
Boundary condition changes in SOL 5 are allowed with the RF5D65 rigid
format alter. However, when rigid
elements are present in the model without an MPC request, the SFM 3007 is
obtained from the SCE1 module.
An avoidance is to include an MPC request in the case control as indicated
by the comments in the description
of the RF5D65 in the User Manual, Section 3.5.
1966
ong Answers
66
Transient Nonlinear Analysis - O set - Wr
If an O-set degree of freedom is connected to nonlinear elements, which is

a modeling error, wrong answers are
obtained with no message. The user is cautioned to be careful with the use of
ASET and OMIT cards in SOL 99.
1967
66
Matrix Methods - MPYAD - Wrong Answers
Wrong answers occur for Method 4 Transpose (4T) when a complex double
precision matrix is post multiplied by a
complex double precision matrix which has multiple strings in one column or the
column is longer than the buffer
size. (VAX only)
An avoidance is to deselect method 4T (see UM section 2.1).
1968
66
Miscellaneous - SDRXD - UFM 3200
Selection of PLOAD1 cards in the dynamics solution sequences by more than

one LSEQ card requires that the LSEQ
cards be in sorted order in the SORTED Bulk Data Deck. Otherwise a User Fatal
Message 3200 is obtained that reads
"Logic error detected by subroutines TBLEDT 90=Locate code or value".
An avoidance is to change the order of the input cards so the sorted LSEQ
cards are in sort.
1969
66
Miscellaneous - IFP - Wrong Answers
Matrices built with DMI input data cards will not be generated correctly
if the THRU option is used to fill
with zero.
An avoidance is to not input zeros since they are not needed.
1970
66
Matrix Methods - DFBS - SFM 2198
If SYSTEM(60) = (large number) on the NASTRAN card, and the matrix

contains mechanisms, UIM 4158 will state that row 0 has a maximum ratio in the
DECOMP module, then the FBS module will fail with a purged first input data
block.
The error occurs because this system cell is used for two purposes. It
blocks the passive column logic, and also causes the module to terminate at the
first mechanism encountered if 10**(-large number) underflows, as this is the
number used to replace a zero on the factor diagonal.
An avoidance is to remove SYSTEM(60) from the NASTRAN card.
1972
ero
66
Elements - Beam Volumes - Calculated as z
The module ELTPRT used by RF24D32 computes a zero volume for the BEAM
element when there is no continuation
card defining other stations. It does not affect the solution, except that
strain energy densities are set to zero
also.
An avoidance is to include a continuation card with YESA in the BCD field,
and 1.0 in the station location
field.
1973
nt Overflow
66
Eigenvalue Analysis - READ - Floating Poi
Models with very large eigenvalues have been observed to terminate in the
READ module, when using the GIV
method. This is usually caused by a deficient degree of freedom in the mass
matrix that is approaching
singularity.
An avoidance is to use the MGIV method.
1975
66
Dynamic Response - Extra Points - Various
An extra point that has the same identification number as a grid

identification number has been observed to
fail in TRD1 with a User Fatal Message 3005, ATTEMPT TO OPERATE ON THE SINGULAR
MATRIX (NONE) IN SUBROUTINE INITL.
An avoidance is to change the identification number of the grid or extra
point so that it is unique.
1976
66
nswers or May Fail
Database - Restarts - DMAP Error, Wrong A
If a previous run has created and stored a K4JJ matrix and the subsequent
run tries to eliminate the
structural damping matrix by recreating all matrices (e.g. with SEALL = ALL),
the prior K4JJ matrix will be
fetched from the database. This will cause wrong answers to be generated. It
may also fail with SFM 3007 in the
MATREDU module if the USET table is incompatible with the K4JJ matrix.
An avoidance is to start with a clean database, or prepurge K4JJ with the
DBMGR //5 command. See Appendix D
of the Handbook for Superelement Analysis.
1977
ergence
66
Material Nonlinearity - NLTRD - Poor Conv
When extra points (EPOINT) are used in SOL 99, poor convergence and large
unbalanced errors may occur.
Nonlinear loads on extra points are not initialized to zero. It is suggested
that you try to avoid the use of
extra points with SOL 99 for Version 62A.
1978
vergence
66
Material Nonlinearity - NLITER - Poor Con
The material nonlinear solutions (SOL 66 and SOL 99) have an incorrect
scale factor on the error scalar test
variables in the nonlinear iteration module output. (Apollo and CDC only)
No avoidance is known. However, the solution usually converges.
1979
g Answers
66
Dynamic Reduction - SUPORT or CSET - Wron
When generalized dynamic reduction is used and there are no r-set or c-set
degrees of freedom, some or all of
the generalized coordinates may be erroneously discarded.
An avoidance is to use PARAM,EPSRC,1.E-30 in the Bulk Data Deck.
1980
66
Loads - SSG1 - No Load Vector
When a gravity load is combined with another load the gravity load will be
ignored under the following
condition; the GRAV load identification number is lower than the other load
identification number and the CID on
the GRAV card is not blank or zero. This is a UNIVAC only error, caused by
improper overlay.
An avoidance is to put the GRAV identification number higher than the
other load identification numbers.
1981
r 3012
66
Dynamic Response - GKAD - GINO Fatal Erro
The GKAD module fails when m-set (MPCS RBAR etc.) and o-set (omit) and no
s-set (SPCs) are used in a dynamic
solution. This error will occur only when a K2PP, B2PP, M2PP or Transfer
Function is requested. It was observed
that a GINO Fatal Error 3012 was generated by the GKAD module on a CYBER 750.
An avoidance is to input an SPC on an unused degree of freedom.
1982
66
Miscellaneous - IFP - Card Replication
Bulk Data card generation by replication described on page 2.4-4 of the

User's Manual will not increment real
fields that contain the E format real numbers (e.g. 1.E-4, 1.333-6).
1983
66
Miscellaneous - IFP - Card Replication
Bulk Data card generation by replication described on Page 2.4-4 of the

User's Manual will not index the
fields properly unless parentheses enclose the incremental number. This is not
the case for the MSG/MESH
replicator.
1984
66
Bad Format of Messages
Cyclic Symmetry - CYCLIC1, CYCLIC2, UI -
User Information Message 4326 has been observed to output LOADCYH and GRAV
card input data with improper
formats.
User Fatal Message 4316 has the leading three asterisks missing from the
message.
1985
66
rom - Missing Output
Geometric Nonlinearity - Restart Sol 63 f
Restart of SOL 63 from SOL 64 with an Element Strain Energy request will
not output the strain energy density.
This is caused by SOL 64 not storing the element volumes on the database.
An avoidance is to input an Alter to SOL 63 to generate the element
volumes:
ALTER 114 $ MSC/62A
ELTPRT ,,,,,EST/VELEM/EST L$
1986
66
Miscellaneous - Replication - CP Loop
Use of the replicator Bulk Data card = (0), which is not legal, causes the
program to run until stopped.
The replicator in MESH causes a proper fatal error.
1987
66
Elements - SSGHT - Wrong Answers
The TRIARG element produces wrong answers for the nonlinear heat transfer
analysis.
There is no known avoidance.
1988
66
Material Nonlinearity - NLITER - SFM 4276
The large displacements for SOL 66 with the KMETHOD set to LSQN and KSTEP
set to unity on the NLPARM card will
cause the NLITER module to issue a System Fatal Message 4276.
An avoidance is to use KMETHOD of SEMIQN instead of LSQN in Field 5 of the
NLPARM card.
1989
66
Cyclic Symmetry - SSG3 - Divide by zero
If a NOUTPUT or HOUTPUT card is not present in the case control, i.e. no

cyclic output request, the SSG3
module will encounter a divide by zero.
An avoidance is to place a NOUTPUT or HOUTPUT card in the Case Control
Deck.
1990
66
Cyclic Symmetry - GRAV,RFORCE - Wrong Ans
wers
The request of GRAV or RFORCE loads with a LOADCYH card will have the S1
load factor on the LOADCYH ignored
and a unit value will be used.
A possible avoidance is, use the S load factor to change the scale.
1991
66
Miscellaneous - IFP1 - Missing output
The use of the "NONE" for output requests will cause the remaining
subcases to have no output generated even
when requested. For example, the following case control
CEND
.
.
STRESS=ALL
SUBCASE 1
STRESS=NONE
SUBCASE 2
STRESS=ALL
BEGIN BULK
will not generate any stress output.
An avoidance is, do not use NONE as an output request.
1992
66
DMAP - DMI, Form 3 - Wrong Answers
If the special diagonal matrix form, known as FORM 3 on DMI cards, is

input to the ADD module, and the matrix
contains a zero on the diagonal, wrong answers will result.
If the ADD mdule is used to convert a vector to a diagonal matrix, as is
done in some DMAP Alters in
conjunction with the MODTRL module, and a term of the input matrix is null,
then the output matrix will be null.
An avoidance is to replace all zero terms with very small numbers, or use
FORM 2 instead.
1993
66
DMAP - DMI,Form 7 - Wrong Answers
If the special row vector form, known as FORM 7 on DMI cards, is input to
the ADD module, and the vector
contains a zero entry, wrong answers will result.
An avoidance is to replace all zero terms with small numbers. A better
avoidance is to change FORM 7 to FORM
2, which will produce a column vector. The column vector can be changed to a
row vector with the TRNSP module.
1994
66
Dynamic Response - BAR - SFM 3007
BAR element force or stress data recovery in the dynamic solution

sequences with distributed loads (PLOAD1)
may cause a System Fatal Message 3007, ILLEGAL INPUT TO SUBROUTINE SDRXE5.
This error is caused by having a set
request in case control which does not include the highest numbered BAR element
ID.
An avoidance is to include the highest numbered BAR element ID in the
output request.
1995
66
Elements - SHEAR - Miscellaneous Errors
If the differential stiffness matrix for a CSHEAR element has a nonbasic

displacement coordinate system on any
associated grid points, it may generate an unpredictable error such as a Mode
Error or SFM 3007, ILLEGAL INPUT TO
SUBROUTINE REIG on buckling problems, or wrong answers. (CDC, 7600, and CRAY
only)
An avoidance is to use the basic coordinate system for the displacement
coordinate sytem for the associated
grid points, or replace the SHEAR element with a QUAD4 element.
1996
66
Missing Plot Output
Transient Nonlinear Analysis - Plotting -
SOL 99 does not allow plotting of the stress data for the ROD element.
No known avoidance.
1997
66
Material Nonlinearity - NLCOMB - SFM 3007
If all nonlinear elements become perfectly plastic, even though linear

elements are present, then a System
Fatal Message 3007, ILLEGAL INPUT TO SUBROUTINE NLCINT< will occur. This is
caused by an empty KDICT data block
being input to the NLCOMB module.
An avoidance is to use a small but finite value for the work hardening
slope.
1998
66
Material Nonlinearity - NLITER - SFM 4547
A one dimensional nonlinear element can not be modeled as a

perfectly-plastic element. A finite value of the
work hardening slope has to be used otherwise a System Fatal Message 4547
occurs, NO ELEMENT STIFFNESS CAN BE FOUND
FOR ELEMENT XXX. The run terminates with a SFM 3007, ILLEGAL INPUT TO
SUBROUTINE NKUPTD.
An avoidance is to use a small but finite value for the work hardening
slope.
1999
66
Eigenvalue Analysis - READ - SFM 3001
The READ module used in an APPROACH DMAP with the third output (MI) purged
can cause a System Fatal Message
3001.
An avoidance is to supply the third output data block in the DMAP calling
sequence.
2000
ng Answers
66
Superelements - Image Superelements - Wro
If identical or mirror image superelements have scalar points as exterior

points, they will produce wrong
answers, unless these scalar points meet the conditions described in the
avoidances below. This type of error can
be detected by applying enforced deflections (SPCD cards) that should result in
null internal loads ("rigid body
checks").
Avoidances are to do any or all of the following.
1. Make the number of scalar points attached
to each superelement an integer multiple
of six, and/or
2. Number the scalar point IDs to be larger
than any exterior grid point ID, for both
the primary and image superelements, or
3. Replace the scalar points with grid points.
(See the H/SEA, Section 4.1.5.)
2001
66
Static Analysis - STRSORT - S1 Default
The documentation in Section 3.1.3 of the User's Manual states that the S1
parameter defaults to 0. This is
the default for V-61B. In Version 62 and 62A, the default was changed to -1.
2002
s
66
Response Spectra - MODACC - OFREQ Request
The case control OFREQ request does not select the modes for response
spectra analysis. Its presence is
ignored in SOL 63.
2003
66
Miscellaneous - SCALAR - Wrong Defaults
The SCALAR module default values for the first and second parameters as
documented in the User's Manual are
not consistent with the MPL (Module Property List) default values. The U.M.
indicates unity values whereas the
MPL sets the values to 0. The SCALAR module obtains a value of zero for the
matrix term using the default values.
An avoidance is to not use the default values.
2004
GL
Cyclic Symmetry - GPFDR - CPU Loop
Using SUBCOM/SUBSEQ commands in Cyclic Symmetry will result in a CPU loop

in the GPFDR module. Cyclic Symmetry does not support the use of SUBCOM/SUBSEQ
commands in the case control.
An avoidance is to replace the SUBCOM with an appropriate SUBCASE and
combine loads by using the LOAD Bulk
Data card.
2005
swers
66
Miscellaneous - CDC 800 Series - Wrong An
The CDC 800 Series computer will run only with the extended purge enabled.
This is sometimes referred to as
the slow mode. If the external purge is disabled then wrong answers or
miscellaneous aborts may occur. If for
example at your site the JCL card, MACHINE, EP=ON, then you are running with
extended purge enabled.
A binary patch has been made to Version 62B and a tape with the patched
executable will be sent to all CDC
clients currently authorized to use 800 series computers.
2006
L MESSAGE 1409
66
Material Nonlinearity - NLTRD - GINO FATA
TSTEPNL
Material nonlinear transient solution (SOL 99) may obtain a GINO Fatal
Message 1409 when the total number of
time steps on the TSTEPNL card is not a multiple of the output interval.
An avoidance is to use an even multiple of total number of time steps for
the output interval.
2007
66
Material Nonlinearity - UMERGE - SFM 3007
In SOL 66 and 99 if the S-, O-, M- and R- sets are empty, a SFM 3007 will
occur in UMERGE (V65) or UPARTN
(V64).
Avoidance: An avoidance is to include a dummy grid point that is totally
constrained.
2008
66
Time Information
Miscellaneous - FACOM Timing Data - Wrong
The timing messages are wrong for the FACOM M/180 and M/200 models because
the timing data block is not
correct for these two models. It is suggested that users specify the "CFG"
keyword on the "PARM" field, see page
7.6-4 of IBM Application Manual. "CFG" whould be set to 5 or 6 for M/180 or
M/200, respectively. It should be
noted that the model printed on the title page will be blank. (IBM 62A only)
2009
66
th - Divide by zero
Aeroelastic Analysis - Doublet Lattice Me
The description of the CAER01 card indicates that the chord dimension X12
or X43 may be zero but not both to
obtain triangular surfaces. If X12 is set to zero but not X43 then the APD
module obtains a divide by zero.
An avoidance is to interchange the geometry on the CAER01 card to have X43
zero.
2010
ers
66
Material Nonlinearity - SDR2 - Wrong Answ
The TRIA3 element force output for the bending moments is wrong and is
often output as zero in SOL 66 and 99.
The stress output is correct.
2011
66
Heat Transfer - VIEW - Wrong Answers
If AREA4 type CHBDY elements are not rectangular, the VIEW printed output
is incorrect. However, the punched
output is correct. This error is related to error 1715.
An avoidance is to punch RADMTX and RADLST cards, then use them as input.
2012
swers
66
Material Nonlinearity - NLITER - Wrong An
The PENTA element will yield wrong answers when used in SOL 66 or 99,
unless the SIGMA-yz is zero.
2013
69
Miscellaneous - GPSP1, AUTOSPC - SFM 4276
If all degrees of freedom in a model are constrained by AUTOSPC, the USET

trailer is not reset, causing SFM 4276.
An avoidance is to include a dummy disjoint problem with a nonconstrained
degree of freedom.
2014
66
Elements - SDRX - Missing Output
A combination of BAR, BEAM, and BEND elements has been found that does not
generate any output. A combination
that causes this to happen is as follows: if PLOAD1 or CBARAO cards exist and
element forces and stresses are
requested and BAR and BEAM elements exist, but element stress or force output
is requested for the BEAM and not the
BAR, then the BEAM output data may possibly not be obtained. Other
combinations of the BAR, BEAM, and BEND
elements and similar output requests may have missing output.
An avoidance is to use sets in the case control that include one each of
the other elements. For example, if
BEAMs and BARs exist, and only the BEAM stresses are requested, but forces are
requested for the BAR and BEAM
element, then ask for one BAR element in the output s
2015
wers
66
Material Nonlinearity - NLTRD - Wrong Ans
Large damping and multiple subcases will produce wrong answers in SOL 99.
An avoidance is to not use subcases that have large damping changes.
2016
66
Database - DBMGR - SFM 4165
The block amount check on a DBMGR//4 call fails if the allocated disk
space for the database is completely
filled up.
An avoidance is to increase the allocation of the number of blocks for a
database on a DBMGR//4 DMAP
statement.
2017
66
Elements - Composites - Wrong Answers
If a nonzero ply orientation angle is used with a MAT8 card that has G1,z
not equal to G2,z the resulting
transverse shear terms [G3] will have a sign error on the off-diagonal terms.
An Avoidance is to set G1,z and G2,z equal.
2020
66
Elements - Composites - Wrong Answers
When several plies are identical (i.e. equal thickness, material and
angle), the stress recovery for
interlamina shear stress may give wrong results.
An avoidance is to change ply angles slightly so that identical plies
become unique.
2021
M 614
66
Miscellaneous - Case Control SET Car - UF
The SET card on the Case Control Deck must satisfy the following rule: An
EXCEPT list may not include a THRU
list.
An avoidance is to remove the THRU that is intended for the EXCEPT.
2022
SSAGE 9876
66
Miscellaneous - CHKPNT - NASTRAN FATAL ME
If the CHKPNT module is used to checkpoint a data block in Link 8 an 0C4

fatal error will be encountered.
This error is caused by an overlay error. (IBM only).
An avoidance would be to force a link switch before the CHKPNT module.
2023
ong Answers
66
Frequency Response Analysis - RANDOM - Wr
A RANDOM request for AUTO correlation functions with the coupled

formulation will generate wrong answers
except for zero values for the lag constants on the RANDT1 card.
2024
Thermal Loads
66
Elements - Composites - Wrong Answers for
When a composite plate is not symmetric about its grid plane, the
resulting alpha terms are incorrect, thus
causing poor results in thermal analysis.
A possible avoidance for some applications is to use a plate that is
symmetric about its grid plane (i.e.,
zero G-4 terms).
2025
PCFORCES
68
Geometric Nonlinear Analysis - SOL 64 - S
The SPCFORCE request in SOL 64 produces different output than the other
solution sequences. The output
represents the difference between the element forces and applied loads which
includes the forces of multi-point constraints and nonconvergence errors at
free points, in addition to forces of single point constraint. In Version 68

this limitation has been removed by adding a new feature. The new feature is
governed by the bulk data parameter SPCFOPT as follows:
SPCFOPT = -1 capability disabled; old SOL 64 results
= 0 (default) SPC forces computed correctly
= +1 same as 0, adds MPC and residual force
output using MATGPR
An avoidance is to use SOL 66 to perform the geometric nonlinear analysis.
2028
ing Output
69
Dynamic Response - Element Dampers - Miss
For modal frequency and transient response, element force output requests
for CVISC and CDAMPi elements are ignored if the matrix method of data recovery
is used.
Avoidance: An avoidance for frequency response is to request the mode
displacement method of data recovery by setting PARAM,DDRMM,-1. For transient
response it is recommended that an MPC relationship be developed such that the
motion of an added SPOINT is equivalent to the relative motion between the end
point of the damper element. The velocity output for the SPOINT can then be
made to equal the force in the viscous damper. The following would be an
example for SPOINT id 1001, where grid ids 11 and 12 are the ends of the damper
and B is the damping value.
MPC,1,1001,1,1.,10,1,B
,,11,1,-B
2038
GL
ulus Limitations
Elements - Composite Transverse Shear Mod
The transverse shear flexibility terms for composite plate elements calculated
from the PCOMP and MAT8 entries assume that primary bending occurs in the
overall material coordinate system defined by the angle on the CQUAD4 (CTRIA3,
etc.) entries. Transverse shear flexibility and stresses may have poor
accuracy if transverse shear bending loads are not in the direction of the
material X and Y axes, or if significant twist loads are present.
This is a general limitation in all general purpose finite element programs due
to the plate having insufficient degrees of freedom to account completely for
stresses caused by both transverse shear bending loads and twist loads. This
is documented in other words in the MSC/NASTRAN V68 Reference Manual, Chapter 6
- Material Properties, Section 6.5 2043
69
Cyclic Symmetry - SOL 78 - Fatal Error
Whenever applied loads are placed on degrees of freedom in the s-set, the
SDR1 module will encounter the fatal
error, ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES. The PSF data block output by
the FRLG module has not been made
compatible with the displacement vector.
Avoidances are to remove the offending loads or not request SPCFORCES.
Another avoidance is to use SOL 88.
2049
69
Documentation - H/DA - UWM 4312
The page describing the CONM2 Bulk Data entry in the Handbook for Dynamic
Analysis is in error. The fields identified for mass moments of inertia are
incorrect. See the User's Manual description of this entry for the correct
format. This also applies to the TF Bulk Data entry. This error is considered
fixed because this manual has been superseded by the Dynamic User's Guide.
2053
70
Elements - IFP - Poor Format, UFM 316
Bulk Data entries which have noninteger values in Field 2 will yield a poor
message if there is an input error on the entry. This may occur on input data
entries such as: AXSLOT, BDYLIST, FSLIST, and VARIAN. Version 70 issues the
following clear message, thus the error is considered fixed:
USER FATAL MESSAGE 313 (IFPDRV)
ILLEGAL NUMBER OF WORDS ON BULK DATA ENTRY AXSLOT ********
ENTRY COUNT =
1
SORTED
There is no known avoidance. However, the sorted "Card Count" will indicate
the offending entry.
2057
M 3005
69
Documentation - Handbook of Dynamic - UF
If the Lagrange Multiplier method described in Section 3.5.4.3 of the Handbook

of Dynamic Analysis is used, a
fatal message of the form "Attempt to operate on the singular matrix (NONE) in
subroutine INITL" will result.
An avoidance is to add very small numbers on the diagonal terms of the
stiffness matrix for the Lagrange
Multiplier variables. Numbers of the size of 1.E-30 have been adequate for
cases tested by MSC. In addition,
extra points used with Lagrange Multipliers should be sequenced after the grid
points, which can be done by
defining extra points with identification numbers greater than 1000.
2064
68
ssing Subsections
Documentation - Handbook of Dynamic - Mi
On page 7.3-8 of the Handbook of Dynamic Analysis, subsections 7.3.6 and 7.3.7
are referenced. However, they are not present. They will be delivered as
Application Notes in a future newsletter.
2066
70
or Poor Efficiency
Superelements - SESET - Insufficient Core
Use of large THRU ranges on SESET Bulk Data entries in superelement analysis
may cause excessive run time (or apparent core requirements) if the range
contains only a few grid points. This has also been observed in cases where
there are no grids in the range specified on the SESET entry. The cause is
under investigation.
An avoidance is to use THRU ranges that are densely filled with grids, or to
explicitly define each grid on the SESET entry. Another avoidance is to place
each grid into the appropriate superelement on Field 9 of the GRID entry.
2090
GL
R 3012, UFM 5423
Dynamic Response - DDR2 - GINO FATAL ERRO
When the modal acceleration data recovery method is used in SOL 31 or SOL 72
and a SUPORT entry is present, SFE 3012 may result in the DDR2 module. Since
in most conditions the SUPORT entry must be present in a modal transient
response with rigid body modes, the mode acceleration method may not be used on
a structure having rigid body modes.
2095
67
Elements - BEAM - GINO FATAL MESSAGE 3012
Follower forces for the BEAM element are ignored in SOL 66. Attempted use
of follower forces (on the PLOAD1 Bulk Data card) may result in GINO FATAL
MESSAGE 3012 during data recovery (in module SDRX).
2101
32A
65
Elements - RBE3 - Poor Diagnostic, UFM 23
When duplicate grid ID and component numbers are specified on an RBE3 Bulk
Data card, UFM 2332A, INDEPENDENT
MPC COMPONENT (SIL) XX IS ALSO THE DEPENDENT COMPONENT, may result. This
message is misleading in that the error
has nothing to do with independent MPC components. This message is also poor
in that the Scalar Index List (SIL)
is referenced, and not the offending duplicate grid ID.
2113
al Error
GL
MSGMESH, MSGSTRESS, MSGVIEW - MAREA - Fat
When the MAREA entry is used to equivalence parallel generator lines to a

single active line, MSGMESH may
incorrectly equivalence end points of the parallel generator lines.
An avoidance is to use MLINE entries after the offending MAREA entries to
equivalence end points of the generator line to single active points.
2117
67
Design Sensitivity - SET2 - SFM 5042
If a SET2 entry references a SET entry which in turn lists element or grid
point identification numbers greater than 131,071 and also uses the THRU
option, then the program will issue SFM 5042. This error has been marked fixed
in 67 because we have not ported to CDC since Version 66. (CDC only)
An avoidance is to reduce the element or grid point identification numbers.
Another avoidance is to specify each identification number separately and not
use the THRU option.
2125
70
Static Analysis - SOL 24 - UFM 4574
UFM 4574 occurs if all displacement vectors for a boundary condition loop
are null. This also occurs for a
nonlooping solution with a null load vector.
An avoidance is to create a nonnull load (and displacement) vector by
applying a small, nonzero load.
2141
70
Sequencer - SEQP - No Message
Whenever any of the superelement solution sequences uses only external

superelements, the SEQP module output indicates that the residual structure is
sequenced and no message is given to indicate that the sequencing output will
be discarded.
An avoidance that allows resequencing of the residual structure is to input the
external superelement matrices as INPUTT4, DMI or DMIG input and not use CSUPER
entries to indicate the external superelement. Another avoidance is to place
most of the residual structure in an internal superelement.
Note that when internal superelements are present in the input data, the
SEQP module does not output any statistics about the residual structure.
2150
66
Database - DBMGR - SFM 4212, SFM 4276
If a database or multiple databases are to be unloaded to a single device,

then the total number of blocks
cannot exceed 65,535. This is an MSC/NASTRAN internal I/O limit and applies to
any output file such as an NPTP.
Avoidance: Multiple databases may be unloaded to separate units.
Increasing the BUFFSIZE will allow fewer blocks to be written and thus may also
help avoiding this error.
2152
69
ram - UFM 5225, SFM 3007
Material Nonlinearity - SOL 66 Restart Pa
A SOL 66 cold start with parameters that are intended for use in restarts;
such as, SUBID, LOOPID, and
LOADINC, will produce fatal message 5225 and, in some cases, 3007.
An avoidance is to assure that the above parameters do not appear in the
Bulk Data Deck of a cold start.
2187
69
Superelements - UMERGE - SFM 3007
This error occurs in the operation on the YS vector immediately after the
GP4 module if all the degrees of
freedom in the residual structure are in the s-set.
An avoidance is to have at least one degree of freedom in the residual
structure, that is free to move and
nonsingular.
2206
GL
Response Spectra - SDR2 - Missing Output
A request for acceleration or velocity output at a given set of points in

a response spectra run will not be
honored unless a displacement request for the same set of points is also
present.
An avoidance is to include a displacement request for the same set of
points where accelerations or velocities
are requested. For example:
SET 28 = 1,7,9,12,56,83
DISP(PLOT) = 28
ACCEL = 28
VELO = 28
2217
67
Executive - Solution Sequences - SFM 3001
On some machines, an insufficient number of files may be allocated during

the processing of solution sequences which may result in the unintentional
purging of data blocks. This error was observed in SOL 89 in the VDR module.
The EQDYN data block, which is a required input data block for the VDR module
has been unintentionally purged in a prior operation. (APOLLO, IBM, CDC 7600
only)
On the Apollo and IBM machines, an avoidance is to increase the MAXFILES
system cell on the NASTRAN command from the default of 40 to 60. On the CDC
7600 machine, an avoidance is to insert a DMAP Alter that would circumvent the
unintentional purging. In the particular error described above, the avoidance
is to insert the following alter:
ALTER 817 $ MSC/64
PARAML
GOA//PRES////V,N,NPP $
2230
GL
correct Description
Documentation - MSC/NASTRAN Primer, - In
In section 9.10.1.2 of the MSC/NASTRAN Primer by Harry Schaeffer, it states for

the CHEXA element that the "nodes G1 through G4 must define a face having an
inward normal." This is not an actual requirement. The normal may point
outward also.
2251
estarts
GL
Aeroelastic Analysis - SOLs 75 and 76 - R
To perform efficient restarts with aeroelastic solution sequences, one may

be required to possess knowledge of the manner in which the DMAP handles the
looping over the Mach number and reduced frequency pairs. This DMAP knowledge
is only required when a run is terminated during the aerodynamic matrix
generation loop. A typical termination may be caused by exceeding the allowed
CPU time. Another case may occur when the user wishes to switch from SOL 75
and restart in SOL 76, but has not included the entry PARAM,GUSTAERO,-1 in the
SOL 75 run. The DMAP loop which includes the AMG and AMP modules was written
expressly to perform efficient restarts for generation of the aerodynamic
matrices. However, this efficiency comes with an associated cost. The
decomposition factors of the ae
2262
69
Static Analysis - RF24D32 - No Message
If Rigid Format alter RF24D32 is used, then SOL 24 may not detect errors
related to stiffness matrix
generation. For example, if a PBAR entry improperly references a MAT2 card,
then no message will appear. Whereas, without the alter, SOL 24 will issue UFM
2113.
The error occurs because the stiffness matrix generation steps, in which
UFM 2113 would be issued, are skipped in RF24D32 in order to reduce the CPU
time.
On CRAY machines the run may terminate with a Floating Point Exception.
An avoidance is to modify the EMG statement in the alter so that it will
generate the KELM and KDICT data
blocks. See below:
EMG
EST,CSTM,MPT,DIT,GEOM2,,,/KELM,KDICT,MELM,MDICT,,/
-1/S,N,NOMGGX/0///C,Y,COUPMASS $
However, this modification will increase
2295
69
nfinite CPU Loop
Nonlinear Analysis - BEAM - UIM 4550 or I
A beam element with geometric nonlinearity may not allow solution convergence
if the distortion is such that
the elemental x-axis crosses the updated orientation vector. In SOL 66 or 99,
UIM 4550 will be issued and, in SOL 64, an infinite CPU loop may occur.
An avoidance is to specify an orientation vector that is perpendicular to the
element.
2296
swers
2004
Miscellaneous - Punched Output - Wrong An
Punched output may contain seemingly meaningless numbers intermixed with the
correct output. This will occur for element strain energy punched output
(ESE(PUNCH)=n) and other output that has alpha strings intermixed with the real
numbers. It can also happen with any punch if the punch thinks a certain
number is real when it is really integer, or the reverse.
The DEC Alpha is particularly sensitive to this in that it will crash when it
occurs with no message and no "end of job" in the .f06. In the .log file you
get:
time: command terminated abnormally
The punch file will be missing data and a large file named "core" will be in
the JID directory.
Avoidance: As an avoidance in Version 68, setting system(210)=1 will cure the
crash. Unfortunately, it will also occasionally cau
2312
65
recognized Qualifier
Miscellaneous - MSC/NASTRAN Applicat - Un
The command procedure described in Section 7.6.8 in the Application Manual

will issue the message
"~'NASEXE0'EXTRACT - %DCL-W-IVQUAL Unrecongnized Qualifier" in VAX VMS Version
4 and up. Consequently, the
procedure will not function properly. (VAX VMS 4, MSC/64 only)
The avoidance is to replace three lines in the procedure which invoke the
SOS editor with equivalent commands
from the EDT editor.
After: $LIBR/TEXT/LIST=TEMPFILE.XYZ 'P1''P2'
Insert: $EDIT TEMPFILE.XYZ
D 1 THRU 8
EXIT
Delete the next 3 lines which invoke the SOS editor.
2319
g Answers
69
Static Analysis - PLOAD1 and SORT2 - Wron
In SOL 24, the effects of distributed loading with PLOAD1 are not
reflected in the element stress and force
output in the SORT2 format. The fix to this error requires changes to the SOL
24 DMAP which would necessitate all
user DMAPs to be modified. Since there are several possible avoidances it has
been decided that it is in the
user's best interest to maintain the upward compatibility of the user's DMAPs
and leave this error as a general
limitation.
One avoidance is to use SOL 61 or SOL 101. An alternate avoidance is to
apply the following DMAP alter.
compile sol24 souin=mscsou noref nolist
alter 176
SDRX
CASECC,OEF1,OES1,GEOM2,GEOM3,EST,CSTM,MPT,DIT/
OEF1X,OES1X/S,N,NOX $
alter 178,178
SDR3
OUGV1,OPG1,OQG1,OEF1X,OES1X,/OUGV2,OPG2,OQG2,OEF2,OES
2322
GL
correct Documentation
Documentation - MSGMESH Analyst's Gu - In
On page 3-3 in the MSGVIEW portion of the MSGMESH Analyst's Guide, it states
that MSGVIEW plot sets are
printed in the the MSGMESH output. This print option was removed prior to the
release of MSC/NASTRAN Version 64.
2330
69
002, Missing Output
Random Response Analysis - RANDPS - SWM 3
If multiple RANDPS entries appear in the Bulk Data with the same set
identification number (SID) and the
same subcases specified for J and K, then SWM 3002 will be issued and random
analysis data recovery will not be completed. A correction to this error was
integrated into Version 65B and later systems but the fix is incorrect. The
incorrect fix results in UFM 5418 whenever duplication of fields J, K and X is
encountered on any RANDPS entry. The code should check for duplication of SID,
J, and K.
This error has been corrected in Version 69.
Avoidance: An avoidance for
SIDs for each RANDPS entry.
to modify the X value (field
are duplicates across fields
systems prior to Version 65B is to specify unique

In Version 65B and later systems the avoidance is
5) whenever there
3,4,
2341
GL
Forces, SPC - Wrong Answers
Geometric Nonlinearity (SOL 64 - Follower
In SOL 64, follower forces are computed using the load requests of the
present iteration and the geometry of the previous iteration. However, the
geometric effects on follower forces, implied by a SPCD request, is not
reflected until the next iteration.
2375
69
ssing Plot Output
Documentation - XYPLOT, CDAMPi,CVISC - Mi
In the documentation for XYPLOTS, User's Manual Section 4, it implies the

CDAMPi AND CVISCi elements are
treated exactly the same as CELASi AND CONROD elements, respectively for plot
requests. However, General

Limitation 2028 states: "For modal formulations, element force output requests
for CVISCi and CDAMPi elements are
ignored, if the matrix method of data recovery is used." An avoidance is given
for this General Limitation and is
applicable for XYPLOT output requests.
Avoidance: An avoidance is to request the mode displacement method by
including PARAM,DDRMM,-1 in the Bulk
Data Deck. The XY output for damping and elastic elements must be requested by
separate commands.
2377
ong Answers
66
Nonlinear Analysis - Follower Forces - Wr
This error is related to Error 2237 but it occurs for all follower force
type loads, including thermal loads, in SOL 66. Wrong answers are produced
when a stiffness matrix update and new load factor are computed
simultaneously. This is likely to happen with the ITER (LSQN) and SEMI
(SEMIQN) methods, since stiffness matrix updates are prescribed by these
methods.
Avoidance: A possible avoidance is to use the AUTO method (with a large
KSTEP, e.g., 20) to prevent any
stiffness matrix updates from occurring.
2378
GL
able User Message
Eigenvalue Analysis - Lanczos - Unexplain
If the Lanczos method is used for an eigenvalue analysis, the following

termination message may be issued in
the eigenvalue analysis summary: NOT ALL EIGENVALUES FOUND IN RANGE. This
message is given when three consecutive shifts have failed to produce any new
eigenvalues. (V65 only)
Avoidance: There is no known avoidance. The user should try rerunning the
problem with a different frequency range in order to force the shift algorithm
to select a different series of shift values. Please refer to Error 2571 for a
related error.
2383
68
Heat Transfer - GP1 - UFM 2012
Superelement solution sequences 74 and 89 fail to accept upstream

superelements when an SPOINT entry exists.
Avoidance: The avoidance is to change all SPOINT type entries to GRIDS
entries.
2388
te
66
Documentation - - NASTRAN Will Not Execu
VAX must have VMS 4.0 Operating System or greater in order to run MSC/65.
Avoidance: If clients have VMS 3.X Operating System installed and want to
leave it at 3.X, they should use MSC/64. (VAX V65 only)
2393
69
TR2 - Divide by zero
Differential Stiffness and Buckling - GPS
If in SOL 5 a grid point stress output request is made above the subcase level,
a machine dependent error
indicating divide by zero will be issued. (V65 only)
Avoidance: Grid point stress output requests should be placed within the first
subcase only. In Version 66,
the user should use SOL 105.
2406
70.5
rong Answers, Missing Messages
Dynamic Response Analysis - SDAMPING - W
The SDAMPING Case Control command can select only one entry in the superelement
sequences. No warning
messages are issued that any subsequent SDAMP requests are being ignored. The
solution uses the initial SDAMP
request and produces plausible but wrong results. UM 2.3 description of the
command has a qualified remark
directing the user to include multiple FREQ requests which needs a further
qualification to indicate that it
applies only to the Rigid Formats. MSC/NASTRAN Version 68 will be enhanced to
support multiple SDAMP entries.
Avoidance: If the user wishes to use multiple SDAMP requests in the Solution
Sequences Unstructured or
Structured, then multiple restarts must be employed.
2414
69
,112 - SORT1 Output Unavailable
Transient Analysis - SOLs 27,31,69,72,109
When performing either Direct Transient Response, SOL 27, or Modal

Transient Response, SOL 31, if SORT1 output is requested SORT2 output will be
obtained.
Avoidance: Either SOL 69 or 109 with PARAM,CURVPLOT,1 or SOL 72 or 112
with PARAM,CURVPLOT,1 and
PARAM,DDRMM,-1 may be substituted for SOL 27 and SOL 31 respectively. Else one
of the following alters must be included depending on the solution and
PARAM,DDRMM option requested:
2432
M 4276
ALTER
JUMP
ALTER
ALTER
449 $ SOL 27
LSORT1 $
477,478 $
481,481 $
ALTER
JUMP
ALTER
ALTER
557 $ SOL 31 WITH DDRMM=-1

LSORT1 $
586,586
588,588
ALTER
JUMP
ALTER
ALTER
524 $ SOL 31 WITH DDRMM=0 (DEFAULT)

LBLDRM1 $
586,586 $
588,588 $
70
Hydroelastic Analysis - VECPLOT/PLOT - SF
If determination of the differential stiffness matrix is desired in a SOL

64 run with hydroelastic elements
present in the model, SFM 4276, Recovery Code 7777 will occur in the VECPLOT
and PLOT modules.
Avoidance: The following alter must be included to avert this problem.
$ -------------------- FOR MSC/64 & MSC/65 ------------------$ MODIFIES THE SIL AND BDPDT TABLE FOR HYDROELASTIC
ALTER 44,44 $ UNDEFORMED SHAPE PLOT
PLTTRAN GBGPDT,GSILS/BGPDP,SIP/V,N,LUSET/S,N,LUSEP $
TABPT
BGPDP,SIP,GBGPDT,GSILS, // $
PLOT
PLTPAR,GPSETS,ELSETS,CASECC,BGPDP,GEQEXINS,SIP,, GECTS,,/
PLOTX1/NSILS/LUSEP/S,N,JUMPPLOT/1/S,N,PFILE $
$
ALTER 163,163 $ FOR VECPLOT
PL
2443
SFM 3002
69
Frequency Response and Random - RANDOM -
If in Random Analysis the referenced RANDPS entry references subcases that

do not exist, SFM 3002 will be
issued indicating an EOF has been reached.
Avoidance: The user should check his input to insure the referenced
subcases exist. If the user is using
superelements or attempting random analysis of the solution set, please refer
to error numbers 2431 and 2471 for additional information.
2452
66
Miscellaneous - MCE1 - UFM 5303
In MSC/NASTRAN II, if the [Rmm] matrix which defines the multipoint

constraint equations is not diagonal, the
UDCOMP subroutine which is not available in MSC/NASTRAN II will be called
resulting in UFM 5303.
Avoidance: In the coding of rigid elements the user can avoid off
diagonal terms in the [Rmm] matrix by not
specifying degrees of freedom as dependent on one rigid element and independent
on another. In most practical
applications, this error cannot be avoided for the RBE3 element.
2462
68
Analysis - Comp. Mode Synthesis
Documentation - Handbook for Superelement
The Handbook for Superelement analysis, Section 3.1.10, references an MSC

"internal document" on component
mode synthesis. This document is now available as MSR-71, and may be ordered
in the same manner as other user
documentation. The decks for the examples referred to in Section 4.1 and 4.2
of MSR-71 will be included on the
delivery tape in Version 67.5 and later systems and will be named COMP4P1*.DAT
and COMP42*.DAT. However, the
method described in MSR-71 which utilizes SOL 41, 42, and 43 is no longer the
preferred approach for component mode synthesis. These solutions are no longer
maintained. The preferred approach is documented in a paper presented at the
1990 World User's Conference entitled "Creation of and use of "Craig-Bampton"
Models using MSC/NASTRAN" written b
2471
Wrong Answers
GL
Frequency Response and Random - RANDOM -
Error 2423 and General Limitation 1602 instruct the user to duplicate requests
for random analysis of the solution set in SOL 71, once as a solution set
request, ie. SDISP, and once as a nonsolution set request, ie. DISP. However,
when more than one subcase is involved on the related RANDPS Bulk Data entry,
the PSDF results will incorrectly be that of only one subcase.
Avoidance: To get proper results the user must strictly adhere to the
following procedure:
1. You
set
the
not
must make a case control request for the solution

variables desired, SDISP, SVELO or SACCE, with
SORT2 modifier. Physical output requests should
be included within the same run.
2. The XYPLOT requests for random output should be for

the ph
2496
Poor Answers
70
Documentation - HBDA, Dynamic Reduction -
Documentation for the use of GDR, section 4.1 of the Handbook for Dynamic
Analysis, instructs the user to use the defaults for NQDES, NIRV, and NIT, else
accuracy or efficiency penalties will be experienced. It assures the user that
all vibration modes below FMAX will be computed accurately if these procedures
are followed. Although these recommendations are valid for most models,
investigations have revealed models where these defaults are not adequate.
This topic is discussed further in Section 5.1 of the Handbook for Dynamic
Analysis. Models with many closely spaced roots and/or a large number of roots
requested are particularly susceptible to missed roots and loss of accuracy.
The user should be aware that there are limitations to the method and the
number of accurate roots is dep
2503
67.5
Aeroelastic Analysis - FA2 - SFM 3003
In SOL 75 using the KE flutter method, piston theory aerodynamics, SFM

3003 will be encountered in the FA2
module. (IBM only)
Avoidance: No known avoidance is available.
2515
69
If the alternate form of the PBEND card is used and FSI is set to 2 or 3,
incorrect answers will result.
FSI=2 will produce incorrect stresses. Whereas, FSI=3 applies a flexibility
correction factor for a curved pipe under pressure rather than an equivalent
straight pipe. This leads to poor answers for displacements.
Furthermore, the location of the four points chosen for stress output as
documented in Section 1.3 of the User's Manual may not be the maximum stress
locations.
Avoidance: Other than using FSI set to 1, there is no known avoidance.
2554
275, SFM 4276
67
Geometric Nonlinearity (SOL 64 - - SFM 4
Requests for displacements output only in a SOL 64 run may result in "SFM
4275 DURING A DB READ OPERATION"
followed by "SFM 4276 IONAST EC 1302". (Apollo V65, CRAY X-MP/COS V65A only)
Avoidance: This problem is not yet fully understood. However, a request
for additional output such as
SPCFORCE and ELFORCE in conjunction with the DISP request has averted the
problem on both machines where the
problem has been discovered.
2583
GL
, UFM 4553, 4542
Material Nonlinearity - NLITER - UWM 5409
If in material nonlinear analysis the structure is not subjected to any

mechanical loads but is subjected to thermal loads, UFM 4542: NO LOAD INCREMENT
EXISTS FOR NONLINEAR SUBCASE may be output. This is a limitation of the design
and will happen whenever the temperature loads cause no loads to be passed down
to the l-set. For example, a symmetric flat plate supported on all sides or a
simple beam supported on both ends subjected to only thermal loads will produce
the fatal message.
A possible alternative to UFM 4542 is some noise loads get passed down to the
l-set and job will fail with
maximum number of bisections or minimum load step has been reach.
Avoidance:
If the fatal message is obtained, a small dummy mechanical load
will have to be applied.
2588
Elements - BAR,BEAM - Poor Answers
If the orientation vector for a BAR or BEAM element is defined nearly

parallel with the elements axis, UFM 2026 may fail to appear. The resulting
element coordinate system may be randomly defined, which may result in poor
answers depending on the section properties of the element.
Avoidance: The user should ensure that the orientation vectors are at an
angle of at least one degree from the element axis so as not to introduce
numerical difficulties in the problem. In Version 66 this error message has
been changed to UWM 5464 or 5487 which will be issued whenever the orientation
angle is less than one degree. In Version 66 if the orientation angle is
exactly zero, then the job will eventually fail. Some machines may issue SFM
4276 EC 7777 in the output, however, other may
2609
211
69
Plotting - PLTVEC,SEUPPLOT - PACKUNPK FM
The SEUPPLOT feature may not be reliable for large models and multi-level
superelement decks. Observed
problems include: PACKUNPK FATAL MESSAGE 211 in the PLTVEC module, missing
plot output, and incorrect deformed plots. In most cases the aforementioned
fatal message will occur as the result of an improper restart. The problem is
not yet fully understood and users are request to forward problem data decks to
MSC.
Avoidance: The user may be able to avoid difficulties by plotting one
superelement at a time using SEPLOT.
The scale information output by the PLOT module may be useful in obtaining
plots of individual superelements that are to a compatible scale.
2612
70
Documentation - Application Manual,S - UW
M 4591
The MSC/NASTRAN Application Manual page 2.2-13 illustrates the SURFACE command
format. The OUTPUT parameter shown in field four is not a legal parameter.
Use of this parameter on the SURFACE command will result in UWM 4591, ILLEGAL
PARAMETER SPECIFICATION ON A SURFACE OR VOLUME CARD. This documentaion has
been superseded by the Quick Reference Guide. The SURFACE command as well as
all other plot commands are now documented in the QRG.
Avoidance: Remove the OUTPUT parameter from the SURFACE command format
description in the Application Manual.
2623
70
ynamic Reduction
Documentation - A.M. 2.4 - Generalized D
Section 2.4 of the Application Manual documents the algorithm used in the
DYCNTR Module to determine the
DYNRED parameters when the auto select feature is used. This documentation
incorrectly states that the solution for the equations in brackets are rounded
up to the next integer value when in actuality they are truncated to the next
lowest integer value. Furthermore, the documentation does not list two of the
criteria used in the algorithm. The first is that the LCSET cannot be greater
than the number of non null mass columns and the second is that the LCSET will
be adjusted up such that Nr, the number of initial random vectors calculated
within the module, will
divide evenly into LCSET.
Avoidance: The differences should be noted in the A.M.
2627
67.5
e Wall Clock Time
Material Nonlinearity - NLITER - Excessiv
When running SOL 66 on Version 64 for the IBM VM/CMS, excessive elapsed time
may be encountered. The ratio of elapsed time to CPU time may be
as great as 50:1 (IBM VM/CMS V64 and V65C only)
Avoidance: The problem is the result of the overhead involved
with link switching. This error is considered corrected by offering a single
link version of the IBM VM/CMS system in Version 67.5. A possible
avoidance is to try to decrease DMAP looping by selecting appropriate
parameters on the NLPARM card. For example, avoid using ITER or LSQN
with KSTEP=1. In other words, make the problem converge as fast
as possible by minimizing stiffness updates.
2641
GL
SFM 3001, SFM 3007, UFM 5423
Material Nonlinearity - NLITER, MPYAD -
CLOAD entries must be used to apply load to upstream superelements in SOL 66.
If loads are applied upstream and CLOAD entries are not used, SFM 3001 and SFM
3007 will be output from the NLITER module.
Avoidance: Input the required CLOAD Case Control and Bulk Data entries to
avoid this error. See Application note dated June 1990 for proper application
of CLOAD input.
2643
66
Documentation - RBE3 - SFM 2038
Internally, the [Rm] matrix formed by the RBE3 element is always of the
order of six by six. Thus, if less
than six degrees of freedom are specified for the independent degrees of
freedom, the [Rm] matrix may be singular
causing the run to fail with SFM 2038 SINGULAR MATRIX FOR ELEMENT being output.
Avoidance: It is required that six independent degrees of freedom always
be specified. An Application Note
on the proper selection of the independent degrees of freedom, published in
June of 1985, should be referred to.
SOL 60 should be used to test the numerical stability of MPC's and rigid
elements.
2648
68
Output Coordinate System
Documentation - HBT, TRIARG,TRAPRG - Flux
The Handbook for Thermal Analysis, page 3.3-18, incorrectly states that
the thermal gradient and heat flux is
output in the radial and axial directions. In fact, these quantities are
output in an element coordinate system as
described in the Handbook for Thermal Analysis page 3.3-19 and the MSC/NASTRAN
User's Manual page 1.3-26.
2664
ERROR 9358
GL
Documentation - MSGMESH, EDGER - MSGMESH
On page 14-31 of the MSGMESH manual, Remark 3

that: "Thirty triplets of entries Di, Gi and
logical EDGER card." In fact, if more than 16
single logical EDGER entry MSGMESH ERROR 9358
2665
68
Damping M - Poor Answers
under the EDGER entry states

Gi+1 may be entered on a single
triplets are specified on a
will result.
Transient Nonlinear Analysis - Structural
In SOL 99, the structural damping matrix is not updated. This may lead to
poor answers in large deflection problems. Nonlinear damping generation will
be implemented in SOL 129 and SOL 99 in MSC/NASTRAN Version 68.
Avoidance: No known avoidance exists
2677
or Message
66
Single and Multipoint Constrai - GP4 - Po
An RBE3 element coded with the same grid point component twice may result
in UFM 5289: MPC COMPONENT WITH
EXTERNAL ID = *** APPEARS MORE THAN ONCE ON THE SAME MPC CARD. For an RBE3
element, the indicated grid ID will
always be that of the REFGRID specified in field four of the Bulk Data card,
not that of the repeated grid ID.
Avoidance: Although the message does not lead the user to the exact
duplicated field, it does indicate the
incorrectly coded rigid body element. The user should inspect the indicated
element and remove duplicated
components.
2684
67.5
Superelements - COMIFP - Wrong Results
In SOL 60 and SOLs 101-200, with PARAM,CHECKOUT,YES, PARAM,COMPARE

produces wrong results for the comparison
of databases at the superelement level. The results will show that every Bulk
Data entry in the GEOM1S file for

the superelement has been "ADDED". The GEOM1S file contains the Bulk Data
entries related to geometry definition;
e.g., GRID, CORDij, etc. For a complete list see Section 2.3.2.1 in the
Programmer's Manual.
Avoidance: Insert the following DMAP Alter for SOL 60.
alter 364
if ( pnchdb>0 ) then $
alter 366
endif $
Insert the following DMAP Alter for SOLs 101-200:
compile phase0 souin=mscsou noref nolist
alter 334
if ( pnchdb>0 ) then $
alter 336
endif $
2698
GL
Miscellaneous - PREFACE - O/S Error
The scratch files, NSTNxx, on the IBM MVS-SP and IBM MVS/XA systems cannot be
allocated using the block option on the space parameter. If the block option
is used as a space request for these files, the following message may appear in
the JES-LOG: AB002I STOP NO SCRATCH UNITS ASSIGNED(NSTNXX). (IBM MVS and IBM
MVS/XA only)
Avoidance: The avoidance is to specify space requests using cylinders or
tracks. The delivered MSC/NASTRAN Procedure allocates the NSTNxx files with
cylinders, therefore, if the user wishes to change these requests, he must use
tracks. This limitation applies to temporary files only. Hence, permanent
files, such as the DB01 and NPTP, can be allocated using the block option.
2699
Errors
67
Dynamic Response - DDRMM - Various Vector
Dynamic stress data recovery for elements which have Margin of Safety
factors in the stress output (i.e.,
CBEAM, CBEND, CBAR, CROD, CONROD, CSHEAR, CTUBE), performed by the DDRMM module
on the IBM MVS/XA version of
MSC/NASTRAN using the Vector Facility may result in various vector errors being
output to the JES-LOG. The errors
include vector unnormalized operand and vector misalignment errors in the DDRMM
module. This error may also occur
on the HITACHI VOSES 810/820 and NEC vector versions of MSC/NASTRAN. (IBM
MVS/XA VF, HITACHI VOSES, NEC only)
Avoidance: Set PARAM,DDRMM,-1 in the bulk data to avoid execution of the
DDRMM and thus the error. This
avoidance will cause data recovery by the mode displacement method which
performs data recovery on the entire g-set
and
2744
67
Database - - SFM 4276 EC 923
SFM 4276 EC 923, database SIZE LIMIT EXCEEDED, was encountered on a CRAY
X-MP/COS V65A system even though

adequate space had been allocated. (CRAY X-MP/COS V65A only)
Avoidance: It has been reported that the order of the specification of
SYSTEM Cells on the NASTRAN card
influences this error. In the error deck, placing SYSTEM(34) before, instead
of after, SYSTEM(105) on the NASTRAN
card alleviated the problem.
2750
cumentation
68
Documentation - Handbook for Thermal - Do
On page 4.4-1 of the Handbook for Thermal Analysis equation 1 incorrectly has
[K(u)] multiplied by the time
derivative of u, du/dt, this should simply be u.
2765
67.5
,MODACC - Wrong Answers
Transient Response Analysis - DDR2,PARAM
If the mode acceleration method of data recovery is specified in V65 and

latter versions of MSC/NASTRAN and
the structure is free-free, supported only by a SUPORT card specification, the
displacements will be calculated
relative to the SUPORT point. In Version 67 this error report has been
replaced by E3575. Please see error 3575
before preceding. (V65+ only)
Avoidance: The element forces and stresses will be correct. To obtain
the free-free displacement the
PARAM,MODACC should be removed.
2766
67
Plotting - PLOT, SWRITE - SFM 9876 OC4
A system abend OC4 error will occur in the PLOT module on the IBM VM/CMS
operating system with HPO Version
5.0. (IBM VM/CMS V64 and V65C only.)
Avoidance: There is no known avoidance.
2772
GL
Geometric Nonlinearity - - Poor Answers
Analysis of structures including the effects of prestress (differential

stiffness) assumes that the loads remain constant in direction. If SOL 64 or
66 is used to form a stiffness matrix, and the matrix is used in another
solution sequence (like 63 or 69) , and there are follower force effects (like
thermal or pressure loads), then some terms are missing in the equations. The
effects are sometimes small, and can be neglected. An error will show up as an
effective rotation spring for free body motions.
Avoidance: The differential stiffness approximation used in MSC/NASTRAN does
not account for follower force effects such as thermal loads. Thus, there is
no known avoidance.
2784
67.5
ceback Messages
Aeroelastic Analysis - ADG - SWM, IBM Tra
If a SOL 21 run, static aeroelasticity, runs through the ADG Module on IBM
MVS/XA V65C or V65E, a system
warning message will appear in the Performance Summary Table and traceback
messages will be printed in the output.
In very large problems, bad answers may result. (IBM MVS/XA V65C and V65E
only)
2805
GL
Eigenvalue Analysis - CEAD - Poor Answers
For numerically difficult complex eigenvalue problems, such as those that have
large gaps between eigenvalues, the accuracy of the Hessenberg Method of
complex eigenvalue extraction is sensitive to the number of bits utilized by
the machine to represent a number's mantissa. The fewer bits used, the more
likely significant error will occur.
Avoidance: Difficult problems as described above should be broken up into
smaller search regions.
2822
GL
DBC/TRANS/ACCESS - DBC - Missing Output
Although PARAM,POST,0 is supported in most solution sequences in Version 66,

the MSC/GRASP or MSC/XL databases thus created may not be correct. Data blocks
may be missing, the headers may be nonstandard, or the content of the data
blocks may be incorrectly formatted. This affects all programs which later
access these databases, including MSC/GRASP, MSC/XL and user written programs.
The solution types that are affected are Complex Eigenvalues, Heat Transfer,
Aeroelastic Analysis, Cyclic Symmetry, Buckling and Design Optimization. The
specific solution sequence are affected are:
67,70,74,75,76,81,82,83,88,89,105,107,110,
114,115,118,144,145,146,153,159,200
This error can sometimes be recognized by the issuance of "*** SYSTEM WARNING
MESSAGE 6065 (DBC), *** DBCMSG ERROR
2844
tput, UFM 9058
68.2
Superelements - PARAM,FIXEDB - Missing Ou
In SOL 101 and 103 with PARAM,FIXEDB,-1 it is not possible to obtain data
recovery on an upstream superelement without first performing some SE-type
command like SEMG on the residual structure. This error is fixed in Version 67
as long as the run is not using the multi-Master technique. This error is
fixed in Version 67.5 but the fix has not been applied to Version 68.
Avoidance: The following DMAP Alter will allow the desired data recovery
without solving the residual:
COMPILE SUPER3 SOUIN=MSCSOU $ V66
ALTER 85,85 $
JUMP NODRSE $
COMPILE SUPER3 SOUIN=MSCSOU $ V67
ALTER 39
FIXEDB=-1 $
2897
Documentation - Programmer's Manual - CASEDR
Section 2.3.109 of the Programmer's Manual incorrectly describes the

format of the CASEDR table to be the same as the CASECC table. However, word
176 of record 1 of the CASEDR table is not the superelement ID, and may take on
various integer values. This is the only difference between the content of the
CASEDR and CASECC tables.

2907
ault, UFM 6011
66
Documentation - PARAM,CKi - Incorrect Def
The parameters CKi, CPi, and ALPHAi are defined as complex single precision in
the NDDL. However, the Quick Reference Guide documents the default as 1.0. If
the parameter is specified as a real numberon the PARAM Bulk Data entry; i.e.,
field 4 is blank, then the job will fail with UFM 6011.
Avoidance: Specify a 0. in field 4 of the PARAM entry.
2910
69
Documentation - - Programmer's Manual
Section 2.3.2.6 of the Programmer's Manual indicates that each MAT9 entry is
represented by 34 words in the
MPT table. Each MAT9 record of the MPT table in fact contains 38 words, the
last four words always being integer zeros. This information is now documented
on the MSC Web page in the Developer's Guide.
2915
67
Frequency Response - - Divide by Zero
In modal frequency response a divide by zero message followed by a

"standard fix-up taken" message will be
issued once for each rigid body mode when a response is calculated for a
frequency of zero. The answers will be
unaffected. (Hitachi VOSES V65C only)
Avoidance: Calculate the response for a very small frequency, for
example, 0.001.
2925
Miscellaneous - XSORT - SFM 3008, Insufficient Core Available
The bulk data sort module requires that all continuation entries fit in
real memory. If they do not, the XSORT module will fail with SFM 3008
"Insufficient Core Available for Subroutine XSOPIV".
Avoidance: Having deck in sorted order and increasing core are the only
known avoidances.
2934
GL
- Wrong Answers
Optimization/Design Sensitivity - ELTPRT
The contribution of concentrated mass elements and non-structural mass to the

weight and volume of the design model is not accounted for in SOL 200. Both
the weight and volume responses will be incorrect if these elements are
present. This error also effects the design sensitivity calculation in SOLs
51, 53 and 55.
Avoidance: No known avoidance exists.
2972
Documentation - DMAP Programmer's Guide, - Incorrect Format
Programmers Manual Sec. 2.3.2.2 GEOM2 input type format descriptions do not
explain how the TH field for
CQUAD4 is to be interpreted when an integer CID is input in the bulk data.
When the input is a CID, TH is coded by the formula TH=512.0*(CID+1). Whenever
GEOM2 has TH greater than 360.0, it refers to a coded CID.
2973
rs
69
Material Nonlinearity - MPC - Wrong Answe
If in a nonlinear analysis (SOL 66, 106, 99, 129) a linear element connects to
degrees of freedom in the M-set, the Forces of Single Point Constraint will be
wrong. Note, that an attempt was made to correct this error in MSC/NASTRAN
Version 67 but the change was incorrect. The change in Version 67 results in
the contribution to the Forces of Single Point Constraint from the rigid
element having the wrong sign. Thus, if only rigid elements connect to a
constrained degree of freedom, then the Force of Single Point Constraint will
simply have an incorrect sign. However, if flexible elements attach to the
point, then the magnitude will also be incorrect. This error has been
corrected for the structured solution sequences only (SOL 106 and 129) in
MSC/NASTRAN Version 67.5.
Avoidance
2982
66
Dynamic Response - GPFDR - Wrong Answers
The Grid Point Force output of the GPFDR Module may be overwritten by the
execution of the next link on the IBM 386 Version 65C with the Xenix operating
system. (IBM 386 Xenix only)
Avoidance: The type of output requested will determine whether or not the
error is encountered. The simplest avoidance is to request Grid Point Force
Output in a separate run.
3016
67.5
DBC/TRANS/ACCESS - DBC - Wrong Answers
The CSTM data block created by the DBC module is incorrect when the data
block is used to describe coordinate systems that are defined using three
vectors (such as CORD2R, CORD2C, etc.). Only the data defined by these inputs
will be incorrect, all other data in the CSTM data block will be unaffected.
This DBC error will only affect MSC/XL users who attempt to create a new
MSC/NASTRAN data deck from these
databases. This error will result in the
coordinate system definitions
written to the data deck being
incorrect. Furthermore, grid points defined within MSC/XL using these
coordinate systems will be created
incorrectly. MSC/XL
post-processing is unaffected. (MSC/NASTRAN Version 66
, MSC/DBC Level 4).
Avoidance: MSC/XL users can avoid this error's effec
3035
GL
Eigenvalue Analysis - REIGL - SFM 5299
Models with two or more widely separated groups of repeated roots may fail with
SFM 5299: UNRECOVERABLE
TERMINATION FROM LANCZOS ITERATION, INTERNAL ERROR CODE -3, USER RETURN CODE
-33. This error was encountered for a model with two groups of roots separated
by 1.E+8 rad/sec, each group contained eight identical roots.
Avoidance: Either use the SINV method or search the separate regions in
different runs.
3039
GL
ordinate Systems
Documentation - MSC/NASTRAN Primer, - Co
MSC/NASTRAN Primer, Harry Schaefer, 2nd Ed., Section 9.9.1.1.1 items 1 and 4
for the local coordinate system of QUAD4 are wrong. As shown by Fig 9-13b, the
cited statements should read:
1. Having a unique orientation within multiples of 90

degrees, independent of the starting grid point number.
4. Having the x-axis nearly parallel to the G1-G2 edge
in the general case.
Also, in the MSC/NASTRAN Primer in Section 9.9.1.2 defaults for PSHELL
Z1,Z2 should read Z1 = -Z2 = T/2.
3042
70
Documentation - DBMGR, HSEA - UFM 4566
Section 5.2 of the Handbook for Superelement Analysis indicates the procedure
for setting up multiple
databases. In the examples, the DBMGR step that defines the second database is
ALTERed after statement 1. This alteration may lead to UFM 4566, indicating
that a data block can not be found on the database. It is better practice to
place this step immediately following the DBMGR step in the solution sequence
that defines DB01. Depending on the solution sequence, this placement will
result in the alter statement being placed at statement 7 or 8.
This documentation is considered obsolete. It is recommended to use the
Superelement Course notes and the new Superelement User's
Guide when it is released.
3043
sing Output
67
Transient Nonlinear Analysis - SDR2 - Mis
Element force output is not available in SOL 99 for elements which

reference nonlinear material properties
(such as MATS1), or if the input contains PARAM,LGDISP,1. This limitation is
documented on page 1.12-6 of the
User's Manual.
3046
tus of DBsetS
67.5
File Management System - - Incorrect sta
If a new DBset member is initialized for an existing database, the status

of the new DBset member may be
indicated incorrectly as "OLD" in the F04 file. Furthermore, the status of a
pre-existing DBset member may be
indicated incorrectly as "NEW". This error is in the F04 printout only and
will not result in incorrect answers. This error has been observed when the
DBALL DBset is EXPANDed with the initialization of a new DBALL DBset member.
(Version 66+ only)
Avoidance: No known avoidance.
3048
G 14
67
Database Converter - DBC - SWM 6065 DBCMS
For some unstructured solution sequences, PARAM,POST,0 may give incomplete

output on restart. The exact cause of the error is unknown, but it is
suspected that the missing output results from data blocks needed by DBC not
being regenerated on restart. This error effects both MSC/GRASP and MSC/XL
style databases. One symptom of this error is "*** SYSTEM WARNING MESSAGE 6065
(DBC), *** DBSMSG ERROR MESSAGE 14 FROM SUBROUTINE xxx, UNABLE TO OPEN INPUT
RELATION EQUIXENE RETURN CODE = 1". The error is repeatable and occurs for
solution sequences which are fully supported by DBC. (Version 66+ only)
Avoidance: One possible avoidance is to assign the DBC database on
restart to the DBC database of the cold start. For Example:
ASSIGN DBC = cold_start.XDB, STATUS = OLD
3055
2001
se Specification
Miscellaneous - REPCASE - Incorrect Subca
The SUBCASE identification in the Element Strain Energy (ESE) and/or Grid Point
Force (GPFORCE) output is incorrect if the SUBCASE in which the ESE or GPFORCE
is requested is preceded by a REPCASE, or if the ESE or GPFORCE is requested
within a REPCASE. The incorrect SUBCASE identification will be present in both
PRINT and PUNCH output. The incorrect labels have been corrected in the
printed F06 file in Version 67, however, the error with the punch file remains.
3074
ssage
67
Miscellaneous - - SFM 4276 EC 4, Poor Me
On the CRAY X-MP/COS Version 66 release of MSC/NASTRAN if insufficient

memory is specified, the run will fail
with SFM 4276 EC 4. (CRAY X-MP/COS V66 only)
Avoidance: Increase MFL and MEM and rerun.
3080
cumentation
68
Documentation - Handbook for Dynamic - Do
The expression given for the damped natural frequency on the last line on page
2.2-7 of the Handbook for
Dynamic Analysis is missing a negative sign under the radical and in front of
the term alpha-squared.
3103
69
Documentation - RF63D89 - Wrong Answers
RF63D89 was first delivered in V66 and its use is documented in the January,
1986 Application Note on
Nonlinear Normal Mode Analysis. However if the LOOPID parameter is specified
as documented in the Application Note, wrong answers may result. For instance,
in the first example of this Application Note, using the documented value of
LOOPID=2 will give correct answers in V65 but wrong answers in V66. Correct
answers in V66 are obtained with LOOPID=1. The wrong answers in Version 66 are
the result of a dummy subcase being included. The dummy subcase was sometimes
required in Version 65C but is no longer required in Version 66. (Version 66+
only)
Avoidance: The correct action is to never use a dummy subcase in Version
66 and use LOOPID=1. See also Error 3102 regarding DMAP erro
3108
mentation
GL
Documentation - MSC/NASTRAN PRIMER - Docu
Equations 9.63 and 9.66 in the MSC/NASTRAN PRIMER contain typographical errors.
Equation 9.63 should state (e - zk) not (e + zk). Equation 9.66 should state
(2/3)(t**3) not (tc**2) and should state (1/2)(tc**2) not (1/3)(t**3).
3120
67
TER - Wrong Answers
Material Nonlinear Analysis - RFORCE, NLI
The updated load vector associated with RFORCE input method 1 will
incorrectly apply all the load to the first grid point in the problem when
follower forces are requested with PARAM,LGDISP,1. (Version 66+ only)
Avoidance: Specify method 2 on the RFORCE input.
3121
2001
Documentation - CRAC3D - UWM YYY4A
UWM YYY4A which states "GRIDS *** AND *** ARE GENERATED INTERNALLY IN CRAC3D
ELEMENT NO. ***" is unnumbered and undocumented.
3126
67
Elements - SDR2, QUAD8 - Wrong Answers
If an integer theta is used for the material angle orientation on the

CQUAD8 input, the material orientation
will not be the projection of the coordinate system at every point as implied
under the CQUAD8 description in the
User's Manual documentation. It is evaluated at the center of the element and
rotates as the lines of constant n
(eta) over the element surface (see figure under the QUAD8 documentation).
Avoidance: No avoidance is available. Try to model so lines of constant
n (eta) are parallel.
3132
76 EC 7777
67
Parallel Matrix Methods - PDCOMP - SFM 42
Parallel processing does not function reliably on the CRAY X-MP/COS

version 66A of MSC/NASTRAN. The use of
SYSTEM(107) to invoke parallel processing should be avoided. By default,
parallel processing is not invoked. The
following failures were experienced during parallel processing tests on this
system:
1. "DEAD LOCK -- ALL USER TASKS WAITING FOR LOCKS, EVENTS, OR TASKS" may
be issued from the CRAY COS if
SYSTEM(107) is set to equal the maximum available processors. This error
causes the run to hang, while
accumulating CPU time.
CPU time will accumulate until time expiration occurs.
2. It is very likely that "SFM 4276 ERROR CODE 7777" indicating a numeric
overflow, will be issued in PDCOMP
if the "DEAD LOCK" message above is not issued.
Only very s
3145
Documentation - A.M. 2.6 - Documentation
Equation 4 of Section 2.6 of the Application Manual has the wrong sign in
the expression for the shear relief
of a tapered beam.
3200
76 EC 1044
66B
Sequencer - SEQP, PARAM,NEWSEQ,6 - SFM 42
An error has been observed in the SEQP Module when using PARAM,NEWSEQ,6,
the Nested Disection option. The error could occur on any release Version 65E
or later, although to date it has only been observed on IBM MVS/XA. The error
will result in excessive time spent in the SEQP module (infinite CPU loop) or
in an I/O crash (SFM 4276 GINO error). The error occurs under very specific,
unlikely circumstances which are difficult to translate to modeling conditions.
However, the user can be assured that if neither of the two symptoms of this
error are present, the results are safe. Although this error has been
corrected in Version 66B and later system, error 4529 which has virtually
identical symptoms is not corrected until Version 67.7. Please see error 4529
before preceding. (Versi
3205
66B
Elements - EMG - Endless CPU Loop
On some installations of the IBM 386/ix V65C release of MSC/NASTRAN, a

hardware error has resulted in models with QUAD4 elements referencing PSHELL
with MID2 (bending membrane stiffness) encountering an endless CPU loop.
(IBM 386/ix V65C only)
Avoidance: All installations that have encountered this error contained a
386 chip with "DX" in the chip's serial number. The serial number is printed
on the chip. While awaiting for a new chip to be installed, the only avoidance
is to use TRIA3 or QUAD8 elements.
3207
orting
67
Miscellaneous - CRAY XMP - No Royalty Rep
No royalty reporting will occur in the event of an exceeded time limit on

CRAY X-MP COS V66 and V66A
MSC/NASTRAN. (CRAY X-MP V66, V66A only)
This report is for internal use only.
3256
68
Aeroelastic Analysis - APD - UFM 2330
When a SET1 Case Control input references a grid point that does not
exist, the APD module stops with the
message "USER FATAL MESSAGE 2330, SET1 CARD NO. **** REFERENCES EXTERNAL ID
NO. **** WHICH DOES NOT EXIST". The module should only check the SET1 inputs
referenced by SPLINE1 or SPLINE2 entries. Other SET1 entries may be used for
XY plot output and the grids are not required to exist.
Avoidance: Remove the reference to the missing grid points from the SET1
input.
3259
tart
68
Superelements - RESTART - Inefficient Res
In the structured solutions (SOLs 101-200), if an EIGR, EIGRL, and/or

DYNRED entry is changed, added, or
deleted on a restart run, then MSC/NASTRAN will unnecessarily recompute the
component and GDR modes for ALL
upstream superelements and GDR modes for the residual structure. (Version 66+
only)
Avoidance: Make an intermediate restart run, which contains only the
changes, additions, or deletions to the EIGR, EIGRL, and/or DYNRED entries,
with the following DMAP Alter and Case Control additions. This run deletes the
appropriate data blocks from the database but will not recompute the component
modes or perform any analysis. After this restart, the user then should
proceed with the desired restart, without the avoidance and no changes to the
entries above. The component m
3263
70.5
Complex Eigenvalue - CEAD - SFE 4276
If a complex eigenvalue solution sequence is used and the CMETHOD input is

missing in the case control, the message "SYSTEM FATAL MESSAGE 4276 - FREAD
ERROR CODE 3002" will be issued. In Version 67 a meaningful fatal message will
be issued.
Avoidance: Include a CMETHOD entry in the case control
3273
501
GL
Documentation - Verification Problem - V0
The theoretical values given for Ncr in equation 2 are wrong and should be:
Ncr= +/-4.013, +/-10.246, +/-16.516
The theoretical values given for Pcr are correct nonetheless.
3275
s
67
Aeroelastic Analysis - AMG - Wrong Answer
If an aerodynamic model has a vertical surface and/or a y-body on the

centerline, and a symmetric boundary
condition is specified, AMG will generate a nearly singular matrix. A near
singularity will also occur with a
centerline z-body in the antisymmetric case. DECOMP will decompose the matrix
without issuing any warning
messages. However, the answers will be incorrect. In the case of static
aeroelastic analysis, in most cases it
will be obvious to the user that the answers are wrong. However, in the case
of flutter and dynamic aeroelastic
analysis, it may not be obvious that the answers are incorrect.
Avoidance: Make the aerodynamic model consistent with the SYMXZ field of
the AERO and AEROS entries, i.e.,
comment out aero entries for centerline vertical surfaces
3276
101S
GL
Documentation - Verification Problem - V6
Page 3.6101s-2 of the Verification Problem Manual shows the solution for
displacements as -.4444. This should be -0.0444 as mentioned on page
3.6101s-1.
3277
nt Restart
GL
Restarts - Automatic Restarts - Inefficie
In SOL 101, if an automatic restart is performed in which an additional subcase

with only a TEMP(LOAD) is added, and the associated TEMPi Bulk Data entries are
also added on restart, then SEMG and SEKR are incorrectly re-executed.
(Version 66+ only)
Avoidance: Possible avoidances include:
1. Use SOL 61 and do a manual restart.
2. Put the TEMPi Bulk Data entries for the restart into the cold start Bulk
Data. MSC/NASTRAN will not re-execute SEKR and SEMG if no new TEMPi Bulk
Data entries are added on restart.
In SOL 106, the following messages are received:

UWM 4424
ESTNL IS PURGED. CHECK YOUR DATABASE OR PARAM, LOOPID.
.
.
UIM 4425,
ONE OR MORE FATAL ERRORS HAVE OCCURRED.
The run then dies.
3323
d Selection
69
Method Selection - MPYAD/FBS - Poor Metho
The method selection for MPYAD and FBS is based on the lowest total
estimated time (CPU+I/O) for all the methods which have not been deselected.
If the I/O time estimate is inaccurate, the wrong method may be chosen and
hence may cause an increase in CPU time. Timing constants which effect the CPU
estimate on all known machines models are built into all Version 65 systems and
can be generated by the user for any machine model in Version 66 and later
systems. However, an I/O rate for all machines and devices is not generated.
The default I/O rate on the NEC SX series is extremely inappropriate and this
has resulted in poor method selection.
The I/O rate in MSC/NASTRAN Version 69 is much closer to the actual
effective rate of the machines. The rate is calculated based on the m
3327
67
Documentation - AM 7.6 - Renamed Files
For UNIX-based systems, any MSC/NASTRAN output files already present prior
to job submittal are handled as
follows: In V65 all files with the same name as the JID, except for the ".dat"
and ".asg" files, are renamed to have the additional extension ".old". This
applies to any file even if it is not created in the current
MSC/NASTRAN job such as ".XDB" files. In V66 the renaming is controlled by the
submittal parameter "old", as described in Section 7.6. However, the fact that
the "old" parameter also applies to the ".pch" and ".plt" files is not stated
in the Section 7.6 for all UNIX machines. The user should be aware that other
files may be overwritten by MSC/NASTRAN even when the "old" option is turned on.
3351
70.5
gpstress, guass, uwm 4607
The MSC/NASTRAN Quick Reference Guide does not warn the user that the Gauss
point stresses instead of grid point stresses are for grid point stress
analysis when gauss is selected on the psolid or plsolid entries. This error
occurs in all solutions. In nonlinear analysis, this may result in significant
error.
Avoidance: This is a general limitation that should be documented. A new
warning message, 4607, now tells the user of questionable stress formulations
3384
ers
67.5
Aeroelastic Analysis - FA2 - Wrong Answ
When the K-Method of flutter analysis is used with viscous damping and the
HESS method of complex eigenvalues is specified on the EIGC input Bulk Data
entry, the FA2 module will incorrectly process roots that have a negative
imaginary part which will lead to wrong answers.

Avoidance: Use a different flutter method (KE or PK) or use a different
EIGC method and extract only positive imaginary roots to avoid this error.
3387
t
70.5
Cyclic Symmetry - RESTART - Missing Outpu
In Solution 83, a request for additional output in a restart run will be

ignored.
Avoidance: Insert the following DMAP Alters in the restart run.
$FOR V65 SYSTEMS:
ALTER 726 $ V65
DBFETCH /GEOM4S,DIT,,,/SOLID/0//DBSET3 $
CYCLIC1 CASES,,GEOM4S,DIT,/TKVALS,,,THARMS,,CASEBKS,GBACKS/
S,N,NSEG/S,N,CTYPE/S,N,RFNAME/S,N,NOGEOM3C/S,N,
NFREQ/S,N,TOTALK1 $
ALTER 892,893 $
DBSTORE CASEBKS//SOLID/0/DBSET2 $
EQUIV CASEBKS,CASEDR/ALWAYS $
$FOR V67 SYSTEMS:
ALTER 916
CYCLIC1 CASES,,GEOM4S,DIT,/TKVALS,,,THARMS,,CASEBKS,GBACKS/
S,N,NSEG/S,N,CTYPE/S,N,RFNAME/S,N,NOGEOM3C/S,N,
NFREQ/S,N,TOTALK1 $
ALTER 1107,1108
EQUIV CASEBKS,CASEDR/ALWAYS $
Other possible avoidances (which wouldn't need this alter) would be:
1.) In
3407
5423
70
Grid Point Weight Generator - GPWG - UFM
The GPWG module is limited to structural type degrees of freedom and will not
process the hydroelastic RINGFL harmonic degrees of freedom. If attempted,
"UFM 5423 ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES" will result.
Avoidance: The UFM may be avoided by removing PARAM,GRDPNT from the input
Bulk Data.
3425
69
In SOL 51, if the set

Case Control entry is
"SYSTEM FATAL MESSAGE
WHICH WAS NOT DEFINED
Design Sensitivity - DSMA - SFM 3001

which defines the sensitivity coefficients on the SET2
too large, then the job may abort and issue the message
3001 - ATTEMPT TO OPEN DATA SET 101 IN SUBROUTINE LMATPT,
IN THE FIST".
Avoidance: Reduce the set definition for the single SET2 to a series of
restart runs with smaller SET2 definitions.
3437
ts
67.5
Aeroelastic Analysis - FA2 - Missing Roo
In SOL 75 using the PK flutter method, the complex eigenvalues which have
only a nonzero real part are not
sorted reliably. The flutter summary tables are designed to only present the
positive conjugates of complex
eigenvalues. This oversight allows only half of the real roots to be printed.
This may lead to the largest valued roots not being output.
Avoidance: The user can input negative velocities on the FLFACT input,
which will cause all real roots to be printed along with the associated complex
modal eigenvectors or specify DIAG 39 to output all the intermediate
eigenvalues from the FA1's modules PK iterations. The user is cautioned that
either avoidance produces voluminous output.
3445
nswers
67.5
Loads/Cyclic Symmetry - RFORCE - Wrong A
In Version 66 rotational acceleration was added to the RFORCE Bulk Data

entry. This input is ignored for
cyclic symmetry problems. No additional load will be generated. In Version 67
the input is not ignored but
incorrect loads will be generated. All subsequent data recovery will be
incorrect
Avoidance: Other than explicitly defining the desired load, there is no
avoidance in Cyclic Symmetry. To use the RFORCE entry the entire structure
must be modeled. Image superelements is the easiest way to convert the cyclic
symmetry model to a full model.
3447
GL
Elements - BEAM - Wrong Answers
If warping is specified along with variable shear center offsets and the
neutral axis is offset from the shear
center on the BEAM element, then the element force output may be incorrect.
Avoidance: BEAM elements with large changes of shear center and neutral
axis locations between ends, such as
those used to transition between different sections, should not be used. Model
the length with one element for
each major cross section.
3462
67.5
Plotting - XYPLOT - Missing Plot Output
If a user requests response plots for a set of points that include

nonexistent grid IDs in a multiple input
random analysis, then "UWM 3002 EOF ENCOUNTERED READING DATA SET OUGV2" will be
issued and no plots will be
generated. For the single input case, plots are generated for the existing
points and UWM 979 is correctly issued
for the nonexistent points.
3466
Wrong answers
68
Optimization/Design Sensitivity - DOM5 -
When performing dynamic sensitivity response (SOL 108,111,112), and the

objective function is defined via a synthetic response (DRESP2), wrong answers
may occur. (Version 66+ only)
Avoidance: Use DRESP1 entry as the objective function. This is not a
restrictive limitation since optimization is not performed in dynamic
sensitivity in V67.
3472
68
- Unexpected Results
Optimization/Design Sensitivity - DOPTPRM
For SOL 200,108,111, and 112, modifying DELBM (field 14 on the DOPTPRM
Bulk Data entry) has no effect on the calculation of the sensitivity
coefficients. This input is ignored by the code which uses an "effective"
DELBM of 1.0E-5. (Version 66+ only)
Avoidance: None. This limitation should not create serious difficulties
for the user. This value has been chosen to avoid numerical ill-conditioning.
3475
67
Elements - SDR2 - UFM 4658
If a PENTA element is highly distorted and stress output is requested for

this element, the run may terminate
in the SDR2 Module and will print the message "UFM 4658 "DIFFICULT GEOMETRY
PREVENTS FURTHER COMPUTATIONS FOR
ELEMENT WITH ID=XXX".
Avoidance: Remodel to correct element shape or do not select stress
output for this element.
3476
t
67
Superelement - VECPLOT - Extraneous outpu
In V66+ system, if PARAM,POST,-1 is requested in a SOLution 101 run, an

extra output called "VECTOR RESULTANT" will be printed. This quantity is the
summation of all the displacements and has no physical significance. This
output has no effect on other results and can be ignored. (Version 66+ only)
Avoidance: None
3479
le of Contents
GL
Documentation - Verification Manual - Tab
The Table of Contents of the MSC/NASTRAN Verification Problem Manual does not
have the correct titles for two
sections. The title for Section 1.1 in the Table of Contents should read:
"PURPOSE OF MANUAL." The title for
Section 2.0 should read: "ORGANIZATION OF VERIFICATION OF PROBLEMS."
3484
67.5
4275, BLOCK NUMBER CHECK CONDITION
Limitation on Problems Size - SDR1 - SFM
On the DECstation, and other releases of MSC/NASTRAN with a default

BUFFSIZE of 1025, SFM 4275 may be
encountered in the SDR1 module indicating "A BLOCK NUMBER CHECK CONDITION
OCCURRED". The error appears to be
problem size and output dependent. However, the exact cause of the error is
currently unknown.
Avoidance: The error may be avoided by increasing the BUFFSIZE to 2049
and rerunning.
3486
68
Documentation - RBE3, MCE1 - SFM 4255
If an indeterminate set is defined for UM on an RBE3, then the job will

end in the MCE1 module and will issue the message "SFM 4255 UNSYMMETRIC
DECOMPOSITION OF DATA BLOCK SCRATCH FAILS AT ROW 'i', UNABLE TO PIVOT.
UII/MAXUIJ = 0.000E+00" and "UFM 3005 - ATTEMPT TO OPERATE ON THE SINGULAR
MATRIX SCRATCH IN SUBROUTINE MCE1.",
where 'i' is the first redundant degree of freedom (in the internal sequence)
in the UM set that is encountered. If the model is run with PARAM CHECKOUT or
in SOL 60 the redundant degree(s) of freedom are identified (in external sort)
as having a bad ratio, but the cause of the bad ratio is not stated. The SOL
60 and PARAM CHECKOUT output is described in the MSC/NASTRAN User's Manual
Section 3.3.22 but it is unclear. Remark 3c under the RBE3 MSC/NASTRAN User
3491
69
- Wrong Answers
Material Nonlinear Analysis - TEMP(INIT)
If the temperature varies from grid point to grid point within an element,
and there is no MATTi entry
associated with the element; the initial average temperature will be computed
incorrectly. (Version 66+ only)
Avoidance: Input a dummy MATTi entry with constant property for the full
temperature range.
3494
67
Misleading printout
Design Sensitivity/Optimizatio - DESVAR -
If the initial value of a design variable is outside of the bounds as

defined on the DESVAR entry, no
information messages are output until the optimizer level is reached. This
situation should be interpreted as a
user input error, and as such, IFP should check the design variable bounds and
terminate execution immediately with
an appropriate UFM when this situation is encountered. (Version 66+ only)
Avoidance: Ensure that initial design variable values are between their
stated upper and lower bounds.
Although no fatal errors will occur if this is not adhered to, the results may
be misleading.
3496
68
Miscellaneous - W2 - IO 370 FATAL 305
If the secondary space for NSTN07 and NSTN08 is set to a nonzero value
using the W2 parameter in the JCL, then
the Fujitsu 65C Version of MSC/NASTRAN may fail with the above fatal message.
(FUJITSU Version 65C only)
Avoidance: Set W2=0 in the JCL.
3500
GL
QUAD8, TRIA3, TRIA6 - Wrong Answers
Optimization/Design Sensitivity - QUAD4,
If corner thicknesses exist on the plate element connectivity entry (CQUAD4,

CQUAD8, CTRIA3, CTRIA6 ) and the corresponding thicknesses are used as design
variables, then wrong answers will occur. This general limitation only applies
to sizing sensitivity/optimization. The user can still use the taper plates
and shells for shape sensitivity. (Version 66+ only)
Avoidance: Do not specify thicknesses on the plate/shell element connectivity
entry if the corresponding thicknesses are to be used as design variables for
sizing sensitivity/optimization analysis.
3501
68
T - Wrong Answers
Optimization/Design Sensitivity - DOM9/DO
In Solution 200, if the design variables are zero or very near zero, wrong
answers may occur.

Avoidance: Increase the magnitude of the design variable.
3502
67.5
Cyclic Symmetry - SOL 81 - UFM 4342
The use of a single Case Control LOADSET command which references a set of
LOADCYT entries, resulted in UFM
4342 "LOAD IS INCONSISTENT WITH SPECIFIED ANALYSIS HARMONICS". The fatal
occurred with three LOADCYT entries with
two load conditions per entry.
Avoidance: In the conditions cited, specifying six LOADCYT entries each
referencing a different load
condition avoided the error. In general it is recommended that only one load
condition be specified on each
LOADCYT entry.
3504
67
t Conversion of Database
DBC/TRANS/ACCESS - TRANS, MAT3 - Incorrec
Version 4A of TRANS will not convert orthotropic material property

relations specified on the MAT3 Bulk Data input. If attempted, a fatal error
will result.
Avoidance: The avoidance is dependent upon the intent of the user. If
the user needs only the results from the MSC/NASTRAN run, then the run may be
RESTARTed with PARAM,GEOMU,40 and a PARAM,POSTU,41 in the Bulk Data input and
the following ASSIGN definitions in the FMS:
ASSIGN DBC='GEOM.XDB',UNIT=40
ASSIGN DBC='RESU.XDB',UNIT=41
The Transmitter may then be run on the results, RESU.XDB, file.
3508
67.5
M 4275, SFM 4276
Transient Nonlinear Analysis - NLTRD - SF
A client was running a model successfully with GAP and ELAS elements. The
spring rate was varied
parametrically, and an upper limit was found which resulted in a divergent
solution. Instead of some indication of a bad numerical solution, the job
abended with "SFM 4275 DURING A DB READ OPERATION, UNIT = 12, DATA BLOCK=MFDV"
followed by "A BLOCK BEYOND EOD CONDITION OCCURED, ( IONAST EC 1302)". This
occured on both CRAY/UNICOS V65C2 and IBM MVS/XA V65E.
Avoidance: A successful solution was achieved by reducing the time step size.
Another possible solution is
to reduce the ratio of the GAP element's closed versus open spring rates. The
user was taking the default of open stiffness equal to 10E-10 times the closed
gap spring rate. The new gap element introduced in Version 67.5 so
3512
03, SFM 6235
68
Nonlinear Analysis - PBCOMP, IFP - SFM 30
In nonlinear analysis, if the SECTION field is set to zero on a PBCOMP

property entry and there are less than 4 stress output points specified, then
the run may fail with the following error messages - SFM 3003 ATTEMPT TO READ
PAST THE END OF A LOGICAL RECORD IN DATA SET SCRATCH (FILE 302) IN SUBROUTINE
IFP7 - SFM 6235 (IFP7) PBCOMP ENTRY=***** IS MISSING THE SPECIFICATION OF

LUMPED AREAS FOR THE BEAM CROSS SECTION.
Avoidance: Specify all four stress output locations or use the PBEAM
property entry instead of PBCOMP.
3513
Elements - CBAR - Inconsistent Output
When a BAR element is subjected to both tensile and compressive forces, then
the margin of safety outputs for
both tension and compression should be printed. However, if only tension
exists in the BAR, then the margin of safety for tension should be printed
while the margin of safety for compression should be left blank. Also if the
BAR is subjected to compression only, then the margin of safety for tension
should be blank while the margin of safety for compression should be printed.
Furthermore, the margin of safety output should be blank for any intermediate
stations. When a subcase exists in which PLOAD1 loads are applied to BAR
elements, then margin of safety outputs which should be blank may contain
meaningless numbers for all subcases including those subcases which do not have
P
3515
ient Restart
68
Restarts - K6ROT, AUTOSPC, BETA - Ineffic
In Version 66, the default parameter values for AUTOSPC, K6ROT, and BETA were
stored in the NDDL. In Version 67, it was necessary to move these parameter
defaults into the main subDMAPs of each structured solution sequence since the
default values for these parameters were different in the nonlinear structured
solution sequences which were added for Version 67. If upon restart, a user
specifies one of these parameters with a value equal to the default used in the
cold start, MSC/NASTRAN will act as if the parameter value were changed, and
will restart inefficiently. (Version 67 Only)
Avoidance: Do not specify any parameters upon restart unless the values of the
parameters specified are being changed from their default values or from the
values specified in the cold start.
3517
estart
69
Restarts - SEQP - Inefficient Automatic R
When a change is made to a model on restart, which does not affect the
connectivity MSC/NASTRAN re-sequences the model.
Avoidance: MSC/NASTRAN does not resequence the model by default anymore, so
this error is considered fixed in Version 69.
3520
69
Elements - PENTA(6) - Poor Answers
The 6 noded PENTA element is not invariant to the connection order if the
bubble functions (IN=0 on PSOLID
entry) are used. This error results in small differences (approximately 10%)
for thermal loads and stiffness.
Avoidance: Specify full integration by setting ISOP=1 on the PSOLID entry and
set IN to either 2 or 3.
3522
swers
68
External Superelement - CSUPER - Wrong An
If the grids and scalar points on the CSUPER entry for an external
superelement are not in ascending order, then the connectivity may be incorrect
which will lead to wrong answers. This is a design limitation and is
documented under the CSUPER description in the User's Manual; however, it is
inconsistent with the normal MSC/NASTRAN practice which allows ID numbers to be
order independent. Furthermore, in this case, wrong answers are given without
issuing a fatal message.
Avoidance: Renumber the grids and/or scalar points so that they will
appear in ascending order on the CSUPER entry or extra grid points may be added
that are in the correct sequence, and referenced on the CSUPER entry. They
should be coincident with the grid points to which the external SE is
connected, an
3527
67
Heat Transfer - APP HEAT, EMG - UFM 2016
If APP HEAT is specified in the Executive Section of a run that COMPILEs

SOLution 101, then the job will fail
with UFM 2016 - No material properties exist. (Version 66+ only)
Avoidance: Replace APP HEAT with the NASTRAN HEAT=1.
3536
67.5
Executive - XEQUIV - Increased Resources
The XEQUIV module when used to copy datablock to data block will increase
the size of the data block by one
record with each copy. This results in an unneccesary size increase for the
DBset.
There is no avoidance.
3537
1019, UFM 754
67.5
File Management Section - INCLUDE - UFM
The dynamic file allocation capability that is invoked by

command recognizes the INCLUDE keyword
of the plot SET definition entry when it is encountered at the
continuation line. This results in a
failed attempt to allocate a non-existent and probably illegal
gives UFM 1019 and UFM 754. (Version
66+ only)
Avoidance: The user must relocate the continuation point
definition entry so that no line
begins with the optional keyword INCLUDE.
3538
Wrong Answers
68
the INCLUDE
beginning of a
filename and
in the plot SET
If the value specified on the PMIN field of the DVPREL1 entry is less than
-.99E+34, the program will
automatically reset this value to .001. This may lead to wrong answers.
(Version 66+ only)
Avoidance: Do not specify PMIN values that are less than -.99E+34.
3539
ite Loop
67.5
Elements - EMG - SFM 4276 EC 7777, Infin
If an implausible geometry is defined for the CBEND element, the run may
fail in the EMG module by issuing SFM
4276 - EC 7777 or a Floating Point Exception. However, on the IBM RS/6000 an

infinite loop may occur. Please also
see error 2588 which describes a similar error for the CBAR and CBEAM element.
Error 2588 may also lead to an
infinite loop on the IBM RS/6000 Version 66B release of MSC/NASTRAN. The
infinite loop error on the IBM RS/6000
has been corrected in Version 67 on the IBM RS/6000.
Avoidance: Make sure that the defined geometry is valid on the CBEND
entry.
3543
69
DRESP1 - Poor Message
Optimization/Design Sensitivity - DSAD1,
The design sensitivity analysis in SOL 200 requires DRESP1 inputs with valid
RTYPE, PTYPE combinations.
However, the code inspects the validity of the RTYPE and PTYPE separately
without regard to the acceptability with respect to each other. For example,
since STRAIN output is only supported for plate and solid elements, the case of
RTYPE = STRAIN and PTYPE = PROD is invalid. This user input error will result
in the run failing in the DSAD1 module with SFM 3001 ATTEMPT TO OPEN DATA SET
*** IN SUBROUTINE **** WHICH WAS NOT DEFINED IN THE FIST. (Version 66+ only)
Avoidance: The user is responsible for inputting valid combinations of RTYPE
and PTYPE on the DRESP1 entry.
3544
68
Case Control - GPSTR1 - Poor Message
If the "SET n" Case Control input is entered as "SETn" in the OUTPUT(POST)
section of the Case Control,
MSC/NASTRAN will not flag the input as an illegal or misspelled keyword. If
the ill-defined set is subsequently referenced in the OUTPUT(POST) section,
then the run will fail in the GPSTR1 module with the message SFM 3001, "ATTEMPT
TO OPEN DATA SET *** IN SUBROUTINE ***, WHICH WAS NOT DEFINED IN THE FIST"
because no SET is defined for the SURFACE or VOLUME.
Avoidance: Define the set correctly. Also if the database was saved, execute
a data recovery restart.
3547
rs
67.5
Transient Response - TSTEP - Wrong Answe
When multiple time step groups are specified on the TSTEP Bulk Data entry
with a skip factor greater than 1 in
an uncoupled modal transient response analysis, the response quantities will be
shifted. This error will occur
even for pseudo time step changes. This error has been corrected for all but
the CRAY Version 67 systems.
(Version 66+ only)
Avoidance: If multiple time step groups are necessary, a unit output skip
factor must be used. On the other
hand, if the desired skip factor for the output request is other than one, make
sure that there is only one time
step group on the TSTEP entry, i.e. there should be no continuation entry for
the TSTEP entry.
3550
67.5
ESOBJ - UFM 7182, Poor Message
Optimization/Design Sensitivi - DOM2I, D
The text of the message "USER FATAL MESSAGE 7182, DOM2I. A 2ND LEVEL
RESPONSE IS DEFINED AS THE OBJECTIVE
FUNCTION BUT RDTS2 TABLE IS NOT FOUND (NO DRESP2 DEFINED)" should read "THE RID
LISTED ON THE DESOBJ BULK DATA
ENTRY CANNOT BE FOUND ON A DRESP1 OR DRESP2 ENTRY." (Version 66+ only)
3551
67
FM 4276 GETSTR E.C. 1409
Optimization/Design Sensitivit - DSAG - S
If the analysis model properties and stress recovery locations are

specified in the design model using DVPREL1
relations, the job will abort with the above fatal message. (Version 66+ only)
Avoidance: If any design variable is related to an analysis model
property as well as to a stress recovery
location, use a DVPREL2 to describe one of these relations. Do not use DVPREL1
for both.
3554
67
, SWM 6065 Error Message
Database Converter - DBC - Missing Output
MSC/NASTRAN Version 65C2 for the IBM 386/IX was delivered with DBC as a
separate program. The dbc shell script renames the existing .xdb database to
.xdb.old instead of copying the database to .xdb.old. This causes the restart
database output to be put into a new .xdb instead of being appended to the
existing .xdb. This is also a problem when using multiple NASTRAN databases
(i.e. DB01 and DB02) when DBC is used to create an .xdb with the contents of
more than one database. This is related to Current Error 3327.
The avoidance is to modify the dbc execution shell script to copy instead
of rename .xdb as follows:
change:
to:
3555
FM 5531
if [ -f "$nxdb" ] ; then mv "$nxdb" "$nxdb.old" ; fi

if [ -f "$nxdb" ] ; then cp "$nxdb" "$nxdb.old" ; fi
67.5
Optimization/Design Sensitivi - DSAL - U
When all the responses in an optimization analysis are zero, UFM 5531 is
issued and the run is terminated.
Since there are cases where all zero responses are expected, a fatal message
should not be issued. (Version 66+
only)
Avoidance: Set a response to a nonzero value.
3557
FM 5532
67.5
Optimization/Design Sensitivi - MATi - U
If a zero mass density is input on a MATi Bulk Data entry in a Design

Optimization (SOL 200) analysis, the run will fail and the USER FATAL MESSAGE
5532 RHO OF MAT CARD IS LESS THAN OR EQUAL TO ZERO will be issued. (Version
66+ only)
Avoidance: Input a small value of RHO on the MATi entry. In Version 67.5
this message has been changed to a warning.
3560
69
Incorrect Heading
Cyclic Symmetry - SOL 48, 83, 115, ESE -
The header for the element strain energy output in all cyclic mode solution
sequences will put an incorrect value for the mode number. This value will not
be incremented. Other output such as element forces and stresses are
identified by stating the eigenvalue not the mode number. This error is
corrected in MSC/NASTRAN Version 68.0.0 and 68.0.1. Unfortunately, the
correction resulted in missing labels for element strain energy output in modal
solutions. Thus, the correction has been removed in MSC/NASTRAN Version
68.0.2. Please see error numbers 3841, 5444, 5462, and 5541.
Avoidance: There is no avoidance.
3563
68
Nonlinear Analysis - CLOAD - UFM 3055
If the same CLOAD Bulk Data entry is referenced in two different subcases,
then UFM 3055, "ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES" will be issued.
This is error is addressed in MSC/NASTRAN Version 68 by updating the
MSC/NASTRAN Quick Reference Guide documentation for the LOADSET command. The
LOADSET command must be placed above all subcases in nonlinear analysis.
Avoidance: This error is a clarification of existing General Limitation
2548. The avoidance is to include multiple CLOAD Bulk Data entries with
different CIDs that reference the same IDV. This contradicts Remark 5 under
the MSC/NASTRAN User's Manual description of the CLOAD Bulk Data entry which
indicates that a CLOAD entry may not reference an IDV that is defined on
another CLOAD entry.
3565
69
3, Wrong Default, Incorrect Docu
Acoustic Analysis - PARAM,HFREQ - UFM 614
When a modal frequency response analysis is executed with the new acoustic
capability introduced in Version 67, PARAM,HFREQ will not be recognized. The
capability to truncate modes is not supported for acoustics. Therefore, the
value of PARAM,HFREQ has been fixed in the acoustic path of the DMAP. The
failure to document this limitation is an error. This limitation has been
removed in Version 69. New parameters for the acoustic model have been added
that parallel the structural parameters. These new parameters allow control of
the acoustic eigenvalues used in the response. Please see the Version 69
Release Notes. (Version 67 only)
Avoidance: In addition to recognizing the limitation, the following text
documents the fixed default for this
application, the effect of trunca
3567
Response Spectra - RSPEC, TSTEP - Wrong Answers
The response spectra will be wrong if multiple time step sizes are used in
the transient response solution of
a response spectra analysis.
Avoidance: Use a single time-step increment.
3569
tify Message
67
Miscellaneous - Shell Script - Missing No
It has been observed that the NOTify option for MSC/NASTRAN Version 66A on
the Apollo with Version 10.2 of the operating system does not work. (Apollo
68020 Version 66A only)
Avoidance: Use the NOTify option with OS 10.1.
3570
69
ssing Element Force Output
Documentation - SDR2, CDAMPi, CVISCi - Mi
A FORCE Case Control request for damping elements (CVISCi or CDAMPi) in a

transient solution will result in missing output. Element force data recovery
in a transient solution is limited to forces which are a function of
displacement. This limitation is contrary to the documentation for the FORCE
Case Control command which states that to request force output for damping
elements, the mode displacement method (PARAM,DDRMM,-1) must be selected. This
remark is the avoidance for general limitation 2028 and is only applicable to
frequency response solutions.
Avoidance: Two avoidances exist. If only one damping element is connected to
a point and no rigid elements are attached to the point, the inbalance of force
output from a GPFORCE Case Control request will be equal to the load in
3571
67.5
12B - No Feasible Solutions
Optimization/Design Sensitivi - IFP, DOM
The DCONSTR Bulk Data entry should require that the LALLOWi field be less
than or equal to UALLOWi. That is the upper bound should be greater than the
lower bound. If this condition is violated, the design is poorly posed and the
run will terminate with the message "***** NO FEASIBLE SOLUTIONS ARE FOUND
*****". In a related error, if the user specifies a DCONSTR entry that has an
absolute value that is less than E-03, the DOM12 and DOM9 modules apply
different scale factors. This latter error will result in the hard and soft
convergence prints yielding different values for the maximum constrain
violation. (Version 66+ only)
Avoidance: Input meaningful data on the DCONSTR Bulk Data entry. Avoid
LALLOWi and UALLOWi values that are less than E-03.
3572
67.5
DOM2D - SFM 7127,
Optimization/Design Sensitivi - DVPREL,
SFM 7127 states "PTYPE xxxx PID xxxx IS NOT DEFINED IN THE ANALYSIS
MODEL". This message does not mean that
the PID is not in the input data. The message is intended to indicate that a
PID that has been referenced by a
design variable is not referenced by any structural element. The message
should be changed to read, "PTYPE xxxx
PID xxxx IS NOT REFERENCED IN THE ANALYSIS MODEL". (Version 66+ only)
Avoidance: Remove any DVPREL entries that refer to PIDs that are not
referenced by the structural model.
3575
rong Answers
67.5
Dynamic Response - PARAM,MODACC, DDR2 - W
If the mode acceleration method of data recovery is specified in Version

67 of MSC/NASTRAN and the structure
is free-free, constrained only by a SUPORT Bulk Data entry, the displacements
will be incorrect for all degrees of
freedom except the r-set (the supported degrees of freedom). This will result
in wrong answers for all subsequent

data recovery including element stresses. This error has been corrected on all
Version 67 systems except those
explicitly noted below. (VAX/VMS SCALAR, CRAY X-MP, CRAY Y-MP, CONVEX, and
SUN4 Version 67 only)
Avoidance: Do not use the mode acceleration method of data recovery for a
free-free structure. If the
analysis requires the additional accuracy of the mode acceleration method of
data recovery, a direct analysis must
be executed.
3576
ng Answers
2001
Case Control - GPSTRESS - UWM 4594, Missi
If the 'SURFACE' definition in the case control is misspelled, then the

corresponding GPSTRESS output request will not be satisfied. The expected
fatal message *** USER FATAL MESSAGE 601 THE KEYWORD ON THE ABOVE CARD TYPE IS
ILLEGAL OR MISSPELLED *** will not be issued. The following warning message
will not be issued until postprocessing is attempted "*** USER WARNING MESSAGE
4594. THE POSTCDB CONTAINS NO LEGITIMATE SURFACE OR VOLUME DEFINITIONS."
Avoidance: Make certain that SURFACE is spelled correctly in the OUTPUT
section of the Case Control.
3577
67.5
SFM 4276 EC 7777, Wrong Answers
Transient Heat Transfer - SDRHT, TLOAD2 -
If the Bulk Data entry TLOAD2 is used to define loads in a transient heat
transfer analysis, the results
printed for the "APPLIED-LOAD" (requested by the FLUX Case Control command) of
the HBDY elements will be wrong or a SFM 4276 indicating a machine overflow in
the SDRHT module may occur. The temperature and all other results are
unaffected by this error. This error is the result of the coefficients B and C
being inadvertently swapped in the data recovery area of the code.
Avoidance: It is important to emphasize that the temperature results are
unaffected by this error. If
correct fluxes are needed, then the TLOAD1 Bulk Data entry must be used.
Inputting B for C and C for B will not avoid the error since their meaning has
not been confused in all areas of the code.
3578
Answers
68
Transient Heat Transfer - RESTART - Poor
The results from a transient heat transfer analysis at a specific time

step that are obtained by executing a
cold start and then restarting are slightly different from those obtained in a
single execution. This difference
is observed even though the time steps taken to get to the specific time of
comparison are exactly the same.
Avoidance: Although this difference indicates a possible error in the
initial condition RESTART logic for
transient heat transfer, the observed differences have been less than 1 percent
and thus should not be cause for
concern. Since this difference is insignificant for engineering purposes, this
error report is issued for internal
purposes only so that the difference can be investigated further.
3580
67.5
Elements - BEAM - ERROR 11022, Invalid Fo
rmatted Write
If a user specifies a BEAM element with zero torsional stiffness, and
non-zero warping, a User Fatal Message should be issued identifying the illegal
BEAM entry. Instead of the UFM, V65C3 under INTERACTIVE UNIX on 386 machines
ends with the following I/O error in the log file:
ERROR 11022 detected near PC xxx
Occurred during formatted Write on unit 6 file "jid.f06".
Invalid format specifier for REAL (or COMPLEX) item.}
Avoidance: Input a legal BEAM entry.
3581
ACC - SFM 3001
67.5
Cyclic Frequency Response - SOL 118, MOD
In Version 67, if SOL 118 (cyclic symmetry frequency response) is used,

then the run may fail with the
following message "*** SYSTEM FATAL MESSAGE 3001 ATTEMPT TO OPEN DATA SET 101
IN SUBROUTINE GOPEN, WHICH WAS NOT
DEFINED IN THE FIST", when output is requested for anything other than the
boundary point responses. (Version 67
only)
Avoidance: Insert the following DMAP alters or use SOL 88.
COMPILE SUPER3 SOUIN=MSCSOU NOREF NOLIST
ALTER 3,3
TYPE DB CASEX,ESTN,GEOM3BK,GEOM3X,OLB2,PJ1,ULS,ULS1 $
3582
M 5225
67.5
Matrix Methods - DECOMP,DCMP SPARSE - UF
If during a multiple superelement run SPARSE DECOMP is selected by setting

SYSTEM(69)=256 and there is not
adequate memory for SPARSE DECOMP causing the code to revert to conventional
decomposition methods, then DECOMP
will issue the message "USER FATAL MESSAGE 5225 ATTEMPT TO OPERATE ON THE
SINGULAR MATRIX KOO IN SUBROUTINE DCMP."
for all subsequent superelements. (VAX/VMS, CONVEX, CRAY X-MP UNICOS, CRAY
Y-MP UNICOS Version 67 only)
Avoidance: The avoidance is to either provide adequate memory for all
superelements or run the larger
superelements in a separate non-SPARSE run.
3583
tation
67
Documentation - UM/NASTRAN - Poor Documen
The installation instructions for User-Modifiable (UM) MSC/NASTRAN in

Section 7.6.7 of the MSC/NASTRAN
Application Manual do not explicitly indicate that the delivery contains only
the necessary object code and that it
is assumed that standard MSC/NASTRAN has already been installed. The submittal
procedure and delivery database
must be utilized from the standard installation of MSC/NASTRAN. An update to
the Version 67 Application Manual
will be published which will clarify this requirement. (Version 67 UMN only)
3584
D
67.5
Miscellaneous - REPCASE - Wrong Subcase I
If REPCASE is used in a static analysis, output generated from VECPLOT

module such as "MAXIMUM DISPLACEMENT",
"MAXIMUM APPLIED LOADS", and "OLOAD RESULTANTS" will have incorrect subcase ID
references. All other output is
correct and in the correct output order relative to the subcase sequence.
Avoidance: No avoidance exist.
3585
68
SFM 3001, Wrong Answers
Shape optimization is not supported for Version 67 of MSC/NASTRAN. If only

shape design variables are
specified, then the run will fail and issue the message "SFM 3001 ATTEMPT TO
OPEN DATA SET 104 IN SUBROUTINE GOPEN, WHICH WAS NOT DEFINED IN THE FIST". If
a combination of shape and size variables are specified, then wrong answers
will result.
Avoidance: Either remove shape design variables or input PARAM,OPTEXIT,4 in
the Bulk Data.
3586
Response Spectra - RSPEC, IC/TIC - Wrong Answers
The evaluation of response spectra in the RSPEC module uses an uncoupled

transient solution which assumes all
initial initial conditions to be zero. Therefore, a non zero initial condition
at the output locations is ignored and causes an erroneous high frequency peak
in the output spectra.
Avoidance: An avoidance is to recover the acceleration time histories of the
desired output locations and
perform enforced acceleration solutions. If the acceleration time history at
the output location can be reproduced in an enforced motion problem, then the
resulting response spectra should be correct.
3587
mentation
68
Documentation - GPSTRESS - Incorrect Docu
Remark 4 under the MSC/NASTRAN User's Manual description of the GPSTRESS

Case Control command incorrectly
states that PARAM,LGDISP must be set to -1 for "nonlinear static" analysis.
This is only a requirement for
nonlinear transient analysis. (Version 67 only)
3588
ssing Pages
67
Documentation - MSC/NASTRAN User's M - Mi
The MSC/NASTRAN User's Manual for Version 66 may be missing some pages.
Avoidance: A copy of the missing pages may be obtained from your local
MSC representative. (Version 66 only)
3589
readable
67
Documentation - NASTRAN Theoretical - Un
Page 10.4-39 of the NASTRAN Theoretical Manual may be too light to read.
Avoidance: A clearer copy of the page may be obtained from your local MSC
representative.
3590
rong Answers
67.5
Frequency Response Analysis - RF26D88 - W
The alter statement number for RF26D88 which provides the capability to
include Rayleigh damping is incorrect. The error results in the Rayleigh
damping not being included in the analysis. (Version 66+ only)
Avoidance: Replace the "ALTER 420" line with "ALTER 427" in the RFALTER
library.
3592
67.5
CSTRESS, CF - Wrong Answers
Optimization/Design Sensitivi - CSTRAIN,
If an optimization/design sensitivity problem contains CSTRAIN, CSTRESS,

and/or CFAILURE responses specified
on the DRESP1 Bulk Data entry, multiple subcases, and the first subcase
contains no retained responses, then wrong
answers will result. (Version 66+ only)
Avoidance: The avoidance is to retain at least one response in the first
subcase.
3593
67
UFM 4658, UFM 2025
Geometric Nonlinearity (SOL 64 - TETRA -
If the TETRA element is used in SOL 64 on the Cray X-MP/UNICOS V66 release
of MSC/NASTRAN, the job will fail
and will issue UFM 4658 or UFM 2025 indicating that a DIFFICULT GEOMETRY or an
UNDEFINED COORDINATE SYSTEM has been
encountered. (Version 66+ only)
Avoidance: Use SOL 66 or re-mesh the model without TETRA elements.
3594
g Answers
67.5
Heat Transfer - VIEW, PARAM,VIEW3D - Wron
If the REV option is selected on the CHBDY Bulk Data entry, wrong answers
for the view factors for the elements with the REV option will be output.
Since it is clearly documented that the REV option is not supported for view
factor calculations, this error is considered corrected n MSC/NASTRAN Version
67.5 by simply not outputting the view factor for CHBDY elements with the REV
option. The error is only addressed for the new view capability introduced in
MSC/NASTRAN Version 67. The new view capability is selected by setting
PARAM,VIEW3D,1 in the bulk data.
Avoidance: Other than not selecting this option, there is no avoidance.
3595
67.5
9, UWM 4410, UFM 2109, UFM 4512
Database - PARAM,DBALL,SCRATCH - UWM 522
If PARAM,DBALL,SCRATCH is specified in solutions 101-200, then the run may

fail with one of the above error
messages depending on the solution sequence,.
Avoidance: Remove "PARAM,DBALL,SCRATCH" from the run. This feature is

only documented in the "INTRODUCTION
TO MSC/NASTRAN VERSION 67" Guide. The feature allows for reduced disk space
usage and has no effect on the
results. If this feature is desired, then an extensive DMAP avoidance will be
provided upon request.
3597
67.5
T - Incomplete Documentation
Optimization/Design Sensitivit - DOM9, DO
If the optimizer routine has insufficient opencore available, the routine

will print "DISASTER ERROR
OPTIMIZATION TERMINATED DIMENSION SIZE OF WK OR IWK IS TOO SMALL" in the output
file then return with a normal end. MSC/NASTRAN will continue with the next
iteration instead of issuing SFM 3008. (Version 66+ only)
Avoidance: The user must ensure that enough open core is available. It
is recommended that before running a large problem, that a single iteration be
run to verify the minimum memory requirement is satisfied.
3598
ciency
67.5
Eigenvalue Analysis - SOL 103 - Poor Effi
If there is no q-set in a SOL 103, 110-112, 145, 146, or 200 execution,

then certain modules which need only
be executed if a q-set exists are unnecessarily executed. This error occurs
because the NOQSET parameter is not
passed to the proper SUBDMAP. This inefficiency does not affect the quality of
the results. (Version 66+ only)
Avoidance: Insert the following DMAP alters:
COMPILE MODERS SOUIN=MSCSOU NOREF NOLIST
ALTER 1
PARAM USET//'USET'///////'Q'/S,N,NOQSET $
3601
67
Plotting - NASPLT - Missing Plot File
The JCL symbolic NPDISP in the delivered runtime procedure for MSC/NASTRAN
Version 66B on the IBM MVS/SP and MVS/XA is set to (OLD,DELETE). This will
cause the plot file created by NASPLT in the NP step to be deleted. (IBM
MVS/SP and MVS/XA Version 66B only.)
Avoidance: In order to save the plot file, NPDISP should be changed to
(OLD,KEEP) as documented in the NASPLT section, Section 7.6.6.4, of the
MSC/NASTRAN Application Manual.
3603
67.5
SUN4 Version 67
Miscellaneous - NOTIFY - Shell Script for
Even though the NOTIFY parameter has been set to YES, the user will not be
notified at the completion of a job
executed on the SUN4 Version 67 release of MSC/NASTRAN. (SUN4 Version 67 only)
Avoidance: Insert the following line between line numbers 369 and 370 of
the shell script as described on
page 7.7-14 of the Version 67 MSC/NASTRAN Application Manual, for the SUN.
echo "echo \"MSC/NASTRAN job ${name} complete

3604
ng Output
67
\" > `tty`"
Miscellaneous - DIAG 64/USER DMAP - Missi
Due to an error in one of the utility subroutines in Version 66B, if there

is an error in the USER DMAP, it is
conceivable that the buffer may not be "flushed" properly on some machines
which will lead to missing output. This
has been observed on the CRAY X-MP/UNICOS when a USER DMAP with DIAG 64 was
executed. (Version 66B only)
Avoidance: In this instance, removing DIAG 64 rectified the problem.
3605
67.5
essive Space Requirements
DBC/TRANS/ACCESS - DBC, PARAM,POST - Exc
The size of an .xdb file that DBC produces can be increased unnecessarily by
the use of the THRU option on Bulk Data entries such as SPC1. A client
generated an .xdb file 10 times larger than the .dball file by using an SPC1
entry that specified GRID IDs 1000 THRU 999999.
The only known avoidance is not to use THRU options with large embedded
gaps.
3606
ation
68
Documentation - SMPYAD - Missing Document
Remark 3 of the SMPYAD entry on page 5.4-204 of the MSC/NASTRAN User's Manual
states how multiplication of incompatible matrices is accomplished. There is
no statement of how addition is accomplished. If two incompatible matrices are
to be added then UFM 5423 "ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES" is
issued. In Version 68, SMPYAD no longer accepts incompatible matrices. The
Version 68 DMAP Module Dictionary documenation has been updated to reflect this
change so the error is considered corrected in Version 68. (Version 67 only)
3607
67.5
R2 - SFM 4276, SFM SDR2RD
Material Nonlinear Analysis - APPEND, SD
When running SOL 66 with a medium - to - large size problem, it has been
observed that the run may fail with
one of the following error messages: SFM 4276 GETSTR ERROR CODE 1404, APPEND
MODULE or SFM SDR2RD-1 - INCORRECT
NUMBER WORDS BEING REQUESTED FOR TRANSMISSION TO AND BY PHASE-2 ROUTINE. The
error may not be repeatable and the
same problem has been observed to fail in either manner on the same machine.
Avoidance: Increasing the buffsize should alleviate the problem.
3608
67.5
M MVS/XA ABEND 0E0
Miscellaneous - Floating Point Overf - IB
If an OPNCOR request is made which exceeds the amount of memory available

(based upon the REGION requested
less the size of the MSC/NASTRAN executable), the job may fail with a floating
point overflow and a system ABEND
0E0. (IBM only).
Avoidance: Increase the amount of REGION requested for the job or

decrease the amount of OPNCOR requested.
It is generally recommended that users not specify OPNCOR, HICORE or REAL for
MSC/NASTRAN on the IBM MVS/XA system,
but control the amount of working area through the REGION request. The
MSC/NASTRAN Application Manual Section
7.6.3.2 describes the relationship between REGION, HICORE, OPNCOR, REAL and
memory resident MSC/NASTRAN files.
3609
wers
67.5
Aeroelastic Analysis - FA1 - Missing Ans
Prior to Version 67, if the PK flutter method (SOL 75, 145) failed to converge,
then a warning was issued and the method would proceed to iterate on the next
aeroelastic root. In Version 67 the method will not proceed to the next root
but re-processes the current root. This action by the code results in
unconverged solutions for all modes after the first unconverged root within the
current loop. (Version 67 only)
Avoidance: No avoidance exists.
3610
01
68
Dynamic Response Analysis - GKAM - SFM 30
For the dynamic structured modal solutions (SOLs 110,111 and 112 only), if
the METHOD command is missing in the Case Control, the following unclear
message will be issued: *** SYSTEM FATAL MESSAGE 3001 - ATTEMPT TO OPEN DATA
SET 104 IN SUBROUTINE GKAM, WHICH WAS NOT DEFINED IN THE FIST. UFM 3031 should
have been issued instead. (Version 67 only)
Avoidance: Include the METHOD command in the Case Control.
3611
67.5
Composites - MAT2/DBC - Missing Data
If there are no MAT2 Bulk Data entries, then the MAT2 entries generated by
the PCOMP Bulk Data entries will
not be stored in the graphical database (XDB). (Version 66+ only)
Avoidance: Include a dummy MAT2 entry in the Bulk Data.
3612
67.5
Output, Wrong Answers
Composites - DBC,TRIA3,QUAD8 - Missing
If a model contains TRIA3 and/or QUAD8 elements which reference a PCOMP

Bulk Data entry (composites), the
stress/strain lamina data will not be stored correctly on the graphical
database. TRIA3 elements will be
mis-labeled as QUAD8, and QUAD8 elements will be completely ignored. (Version
66+ only)
Avoidance: Since this output is not currently plotted by MSC/XL V3, no
avoidance is necessary for MSC/XL.
For user written programs and other post-processing programs which require the
lamina data for these elements no
avoidance exists.
3613
67.5
DOM9 - Wrong Answers
Optimization/Design Sensitivi - DVPRELi,
Absolute values of initial design variable properties are checked but are
not treated consistently when the
absolute value is in the range of 1.E-4 to 1.E-6. This is irrespective of the
values set for PMIN on the DVPRELi
bulk data entry and may result in computed design responses which are
incorrect.
In one routine an error in the code will result in properties which are
less than 1.E-6 being incorrectly set
to 1.E-4 regardless of the value set for PMIN. Furthermore, properties which
are between 1.E-6 and 1.E-4 will not
be reset. This may result in unexpected results for the computation of the
initial design response. Another
symptom of this error is that the initial objective function is incorrect.
(Version 66+ only)
Avoidance: This error only occurs if the a
3614
4276 EC 7777
67.5
Nonlinear Analysis - PGAP, NLITER - SFM
The default value for the coefficient of static friction MU2 on the PGAP
Bulk Data entry is zero and not MU1 as documented. This may result in a
singular stiffness matrix and the message SFM 4276 EC 7777 being output from
the NLITER module indicating a numerical overflow. (Version 67 only)
Avoidance: Explicitly set MU2 on the PGAP Bulk Data entry.
3615
67.5
y Addressing Violations
DBC/TRANS/ACCESS - ACCESS, DBCXXX - Memor
The labeled COMMON block name was inadvertently changed in some Version 6
releases of MSC/ACCESS from /DBCXXX/
to /XNSTRN/. Note, that MSC/ACCESS Version 6 is the system available with
Version 67 of MSC/NASTRAN. (VAX and
CRAY Version 67 only)
Avoidance: All interface programs must be modified to use the /XNSTRN/
labeled COMMON.
3616
67.5
Acoustics - PARAM,PREFDB - Wrong Answers
If the value for the PARAM,PREFDB is set to less than 1.0E-10, then the DB
value will be automatically set to
zero in order to avoid numeric overflow. (Version 67 only)
Avoidance: Use a PARAM,PREFDB value of greater than 1.0E-10. If
necessary, a different sets of units may be
necessary.
3617
68
uate Documentation, Missing Docum
Acoustic Analysis - PARAM,PREFDB - Inadeq
The documentation for PARAM,PREFDB is missing from Section 3.1 of the

MSC/NASTRAN User's Manual. The
documentation in Section 1.16.8 of the MSC/NASTRAN User's Manual is inadequate.
The documentation does not define limits or defaults and does not adequately
define the purpose of this entry. (Version 67 only)
Avoidance: The following changes should be made to Section 1.16.8 of the
MSC/NASTRAN User's Manual. The
first sentence of item 3. which currently states that PARAM,PREFDB "must be

specified" should be changed to read; "The default value for PARAM,PREFDB is
1.0, a physically meaningless value. Therefore, an appropriate peak value for
PARAM,PREFDB must be specified for the element sound pressure level in dB and
dBA to be meaningful." Section 3.1 of the MSC/NASTRAN U
3618
UFM 7124
67.5
Optimization/Design Sensitiv - DOMCO2 -
For design optimization/sensitivity analysis, if both PSHELL and PCOMP

Bulk Data entries are present in the
model, then the run may fail with the following misleading USER FATAL MESSAGE
7124 - "PTYPE 2302 23 ON DRESP1
ID=XXX IS NOT DEFINED IN THE ANALYSIS MODEL". (Version 66+ only)
Avoidance: The only avoidance is to use the "ELEM" option for the PTYPE
field on all DRESP1 Bulk Data entries
that refer to the PCOMP or PSHELL property input. This avoidance requires that
a separate DRESP1 entry be prepared
for each element.
3619
67.5
Composites - IFP - SFM 4276 EC 1044
If a model contains a PCOMP Bulk Data entry without a corresponding MAT8

entry, then the run will fail and
will issue SFM 4276 EC 1044 which indicates that an end of data has been
encountered.
Avoidance: Include the necessary MAT8 entry.
3620
Size Limits
GL
Executive Limits - MSC/NASTRAN Version -
This error (general limitation) number has been set aside to be used for
tracking of changes for removal or
modification of any "Executive System Limit in MSC/NASTRAN" as documented on
page 6.3-16 to 6.3-18 of the MSC/NASTRAN Application Manual.
Executive System Limits in MSC/NASTRAN:
1.
Maximum number of DMAP/NDDL compilations allowed per run
is 50.
2.
Maximum number of NDDL compilations is 1 per database.
3.
Maximum number of SUBDMAP calls per DMAP solution sequence
is 90.
4.
Maximum number of DMAP/NDDL linkage edits (links) allowed
per run is 1.
5.
The recommended minimum space allocation (via FMS INIT
command) for a DBset is 100 blocks.
6.
Maximum number of DBsets assignable per run is 100.

H
3621
67.5
ly One Processor
Parallel Methods - PDCOMP - Utilizes On
Parallel decomposition on the CONVEX Version 67 release of MSC/NASTRAN can

utilize only one CPU regardless of
what is available or specified. If more than one CPU is requested, the
"SUBPROCESS CPU INFORMATION" reported in
the Execution Summary (F04) will falsely indicate that time has been spent in
the decomposition subprocess.
(CONVEX Version 67 only)
Avoidance: To fix the executable to allow more than one CPU the system
administrator or user with superuser
privelege should locate the MSC/NASTRAN executable (usually /usr/msc/nast67)
and apply the following script:
#
chmod 777 NAST67
adb -w NAST67 << EOF
0x807446b4+4?=w_convex_
pdfblk_+0x404?=w 0x80f31f88
EOF
chmod 755 NAST67
#end of script
3623
67
DMAP - MATMOD - SFM 4276
Jobs that contain user DMAP with MATMOD options 4 or 5 specified may fail
on the HP 9000/800 Version 66B
release of MSC/NASTRAN. (HP 9000/800 Version 66B only)
Avoidance: Other than manually generating the necessary DMI matrix, no
avoidance exists.
3624
136
67.5
Documentation - SPARSE - UWM 6132, UWM 6
Documentation on the Sparse Decomposition option available in MSC/NASTRAN

Version 67 may be found in "The
Introduction to Version 67 User's Guide", Section 6.4 New Capabilities List of
the MSC/NASTRAN Version 67
Application Manual, and in Section 2.2 and 5.4 of the Version 67 MSC/NASTRAN
User's Manual. Additional information
will be available in the new Numerical Methods User's Guide, to be published in
March, 1992. Each document has a
different intent and contains different information. Thus, users should review
all documents before attempting to
utilize this new capability.
In Section 6.4 the new capabilities list is currently the only document
which attempts to document limitations
of this capability. However other than stating that this method is intended
for "sp
3626
ing Pages
67
Documentation - Application Manual - Miss
Pages 6.3-21 through 6.3-31 were missing from the September 1991 the Version 67
Application Manual update
package.
Avoidance: These pages have been delivered in the November 1991 update
package.
3627
67
dinate System Description
Documentation - UM, HEXA - Incorrect Coor
The description of the element coordinate system for the HEXA element under
remark 6 of the MSC/NASTRAN User's Manual description of the HEXA entry is not
consistent with the accompanying diagram. (Version 67 only)
Avoidance: The remark is incorrect. The diagram is correct.
3629
67.5
DBC/TRANS/ACCESS - ACCESS - Extra Output
For the user-supplied control file, some data relations are output to the
neutral file when they should have
been filtered.
Avoidance: This is an undocumented capability, this error report is
written for internal tracking purposes
only.
3630
68
Miscellaneous - TPL - Modeling Error
There is a modeling error in test problem AC11102 delivered in the TPL.

This problem is intended to
demonstrate the interaction between an acoustic element and a structural panel
(a QUAD8 element). In the model the CELAS elements are connected to the
structural elements in the X3 direction instead of the X2 direction and the X2
direction is constrained by SPCs instead of the X3. This situation results in
the QUAD8 element being unloaded by the acoustic elements. (Version 67 only)
Avoidance: To correct the model change the constrain field on GRID
entries 31 thru 38 from 12456 to 13456, and change the component attached by
the CELAS elements for GRIDs 31 thru 38 from the 3 direction to the 2
direction.
3631
67
Documentation - MSC/NASTRAN Applicat -
Differential Stiffness Plate Elements

Section 6.2 of the June/July/August 1991 Application Manual Update package
included a report of "highlights"
to the 1991 Specialist's Technical Forum. This section reported that the
conclusion of a "simple buckling study"
performed by a user was that the "differential stiffness formulation for the
BAR and plate elements is missing some
terms. Consequently, buckling results were very poor." That report was in
error, and this error report is intended
to set the record straight.
First, the only case study of a "simple buckling" problem performed was
for the BAR element in MSC/NASTRAN.
Second, the client who expressed concern for the accuracy of the differential
stiffness of MSC/NASTRAN's plate
elements was specifically concerned about
3632
67.5
FM 4276 EC 1404
Material Nonlinear Analysis - NLITER - S
Large nonlinear problems may encounter an error in core allocation which

will result in the issuance of SFM
4276 EC 1404 from the NLITER module.
Avoidance: Increase the BUFFSIZE.
3633
67.5
PCI - SFM 4276 FILPOS EC 1102
Material Nonlinear Analysis - NLITER, NL
Large nonlinear static problems which specify the arc length method
(Crisfield or Modified Crisfield on the
NLPCI entry) that require spill logic in the NLITER module may fail with the
above error message. (Version 67
only)
Avoidance: Use the Riks method on the NLPCI entry or set MAXQN to 0 on
the NLPARM entry.
3635
ssing Pages
67
Pages 1.2-3 thru 1.2-12 are missing from the MSC/NASTRAN Version 67 User's
Manuals. (Version 67 only)
Avoidance: Until these pages can be shipped, if you have a copy of a
Version 66 User's Manual, retain these
pages as they have not changed. The missing pages will be shipped as part of
the second quarter Application Manual
update package.
3636
er Overflow
68
Plotting - PLOT - SFM 4276 EC 7777, Integ
If plot labels are requested for the acoustic HEXA elements, then the job
will fail with an integer overflow.
(Version 67 only)
Avoidance: Do not request plot labels.
3637
ct Return Code
67.5
Superelement Analysis - IBM MVS - Incorre
Prior to Version 66 of MSC/NASTRAN on the IBM MVS/XA computer, if a fatal

error is encountered in the NS step on the IBM MVS/XA system, then a return
code of 20 or 21 would be issued. However, in Version 66 and beyond, for
superelement solution sequences, a return code of 0 will be issued. For non
superelement solution sequence, depending on where the error is occurring,
different return code will be issued. If the error occurs in IFP, then a
return code of 0 will be issued. This is generally accompanied by UFM 315 or
UFM 316 and a DMAP FATAL MESSAGE. If the error occurs other than in the IFP
Module, then a return code of 20 or 21 will likely be issued.
Avoidance: Ignore the return code and check to see if there is fatal
message in the F06 output file. This message has
3638
68
Differential Stiffness and Buckling - SOL
105, SOL 65 - Wrong Answers

If no output requests are made in SOL 105 ( or SOL 61 for restart into
65), then the differential stiffness is not computed and negative eigenvalues
may be generated. This error has been corrected in Version 68, SOL 105.
(Version 67 only)
Avoidance: Include a DISP(PLOT) output request in the static subcase.
3639
67.5
Restarts - MAT1 - Wrong Answers
On automatic restart, if the GE field which defines material damping on

the MAT1 entry is altered, the damping
matrices will not be updated correctly. The BJJ matrix will be deleted and
K4JJ is not regenerated. (Version 66+
only)
Avoidance: Modify the NDDL as follows:
Change the following DEPEN statements (line number is given):
3999
4000
4136
4144
4145
4147
DEPEN MPTSB(VP) / MPTS:MAT1::GE,MPTS:MAT2::GE,MPTS:MAT3::GE,

MPTS:MAT8::GE,MPTS:MAT9::GE,MPTMID(VP) $
DEPEN BELM / CSTMS,GEOM2S:CNGRNT,MPTSB(VP),EPTSB(VP),EST1(VP) $
DEPEN K4JJ / ECT1(VP),KDICT,KELM,BGPDTS,SILS,CSTMS,NOK4GG(P) $
DEPEN KJJZ / K4JJ $
DEPEN BJJX / ECT1(VP),BDICT,BELM,BGPDTS,SILS,CSTMS $
to the following DEPEN statements:

3999
DEPEN MPTSK4(VP) / MPTS:MAT1::GE,MPTS:M
3641
e Run Time
68
Miscellaneous - GENTIM, COMTIM - Excessiv
There is a known problem in running GENTIM on the VAX VECTOR Version 67

release of MSC/NASTRAN which may
result in excessive run time or the job ending with a SFM. (Version 67 only)
Avoidance: This error was known at release time; however, the problem
could not be fixed. The release of the
system was held to include the timing constants for all VAX VECTOR machines
that we anticipated that we would have
VAX VECTOR clients. This includes the VAX 9010 VECTOR/SCALAR machine as well
as the VAX 6410 and 6510
VECTOR/SCALAR machine. Thus, for these machines the clients should not need to
generate timing constants.
Unfortunately other models of the 6400, 6500, and 9000 series machines exist
and although from a timing constant
perspective any machine within a series is nearly
3642
SFM 6036
68
If a DRESP2 Bulk Data entry references a WEIGHT, VOLUME, EIGN or LAMA DRESP1
entry and there are multiple
subcases, then the run may fail in the DOM5 module with SFM 6036 ATTEMPT TO
DIVIDE BY A REAL SINGLE PRECISION ZERO. (Version 66+ only)
Avoidance: There is no avoidance. However, this error is highly unlikely and
could only be demonstrated with contrived examples.

3643
70.5
Cyclic Symmetry - EIGR, EIGRL, - UIM 4425
If no eigenvalues are found in the prescribed frequency range on the EIGR or

EIGRL entry for the current harmonic, the run will not continue to the next
harmonic. Instead the run will exit issuing the following message "UIM 4425 ONE OR MORE FATAL ERRORS HAVE OCCURRED. THERE MAY BE MORE ERROR MESSAGES IN
THE PRECEDING OUTPUT".
Avoidance: Instead of selecting a frequency range, input the number of modes
desired on the EIGR or EIGRL entry.
3645
67.5
stallation SUN4
Documentation - MSC/NASTRAN Applicat - In
There is a documentation error in Section 7.7 of the Version 67

MSC/NASTRAN Application Manual for the SUN4.
(Version 67 SUN4 only)
In the startup Section (7.7.3.1) the following line:
ln /msc/bin/nastran
/usr/bin/nastran
should be replaced by
ln -s /msc/bin/nast67 /usr/bin/nastran
3647
70.6
Elements - BEAM, Offsets - UWM 4648
If the neutral axis to shear center offset on the BEAM element is excessive
such that the offset is significant as compared to the length of the beam, then
the job may fail in a dynamic analysis using the tridiagonal eigensoluitons
with the following error message: USER WARNING MESSAGE 4648 ---- THE MODAL
MASS MATRIX IS NOT POSITIVE DEFINITE. The Lanczos method may fail due to an
overflow-type of system message, or may produce numerically unstable results
for some modes, which may change greatly when small changes are made to the
model. A non positive definite mass matrix is most likely to occur when the
offset is large and coupled mass (PARAM,COUPMASS) has been selected.
Avoidance: The amount of offset should not be excessive. If this amount of
offset is indeed necessary, then one
3648
015
67.5
File Management Section - EXPAND - SFM 1
If the File Management Section EXPAND statement is used on a restart to

expand two or more physical files
which ran out of space in a previous run and the restart run also runs out of
space, then the restart run will fail
with SFM 1015 rather than the expected SFM 1012. The database will be
corrupted and will not be able to be
EXPANDed further. (Version 66+ only)
Avoidance: ASSIGN and EXPAND files one at a time.
3649
ng Output
67.5
Acoustics - STRUCTMP,FLUIDMP,PAN - Missi
For a SOLution 111 run which contains acoustic elements, if modal

participation output is requested and there is more than one DLOAD subcase,
then only the modal participation output for the first subcase will be printed.
[Version 67 only)
Avoidance: Include the following DMAP avoidance:
COMPILE SEMFREQ SOUIN=MSCSOU NOREF NOLIST
ALTER 167
TYPE PARM,,I,N,ILOAD,NOLOAD,COLNO $
PARAML FOL1//'TRAILER'/1/S,N,NOFREQ $
PARAML UHF1//'TRAILER'/1/S,N,NOUCOL $
NOLOAD=NOUCOL/NOFREQ $
ILOAD=1 $
DO WHILE ( ILOAD<=NOLOAD AND FLUIDMP>0 ) $
PARAML CASES//'DTI'/ILOAD/13 //S,N,DLOADID $
ALTER 170,170
COLNO=(ILOAD-1)*NOFREQ+IFREQ $
MATMOD UHFF,,,,,/UHFFI,/1/colno $ EXTRACT A COLUMN (FREQUENCY)
ALTER 177,177
MESSAGE //' DMAP INFORMATION MESSAGE 9054 (SEMFREQ) -'/
' FLUID MO
3650
67.5
TIM,NO - SFM 3001
Optimization/Design Sensitivit - PARAM,OP
If "PARAM,OPTIM,NO" is specified in a SOLution 200 run which contains

superelements and there is no design
model, then the run will fail with SFM 3001. (Version 66+ only)
Avoidance: Insert a dummy design model, execute SOL 101, 103 and/or 105
separately as needed or insert the
following DMAP Alters:
COMPILE DESOPT SOUIN=MSCSOU NOREF NOLIST
ALTER
155,155
IF ( NOT(RSONLY) AND NOEDOM>-1 ) SDSB,
SLIST,EDOMF,CASEXX/DSLIST/S,N,DMRESD/
S,N,NOSEDV/S,N,NOSERESP $
COMPILE PHASE1DR SOUIN=MSCSOU NOREF NOLIST
ALTER
47,47
IF ( APP<>'DESOPT ' OR ( DESITER<=1 OR SEID=0 ) ) THEN $
3651
68.2
Reduction - Wrong Answers
Optimization/Design Sensitivity - Dynamic
A restart from a dynamic solution sequence (e.g. 63, 67 thru 72, or 103, 107
thru 112, etc) into a static solution sequence (e.g. 61 or 101) when the
residual structure has been reduced by generalized dynamic reduction (DYNRED
entry) will produce wrong answers in the static solution. Similarly, as in a
restart, this error can also occur in SOL 200 when executing with
ANALYSIS=MODES and ANALYSIS=STATICS. This error can also occur in a
superelement if it was reduced by component modes (EIGR or EIGRL entry) and/or
generalized dynamic redution. This was fixed in Version 67.5 but not in
Version 68.
Avoidance: Apply the following DMAP avoidance.
COMPILE SEDISP SOUIN=MSCSOU NOREF NOLIST

ALTER 109, 109 $ V68
IF ( NOT(NLHEAT) ) SDR1,
USET,,ULS,UOOX,YSX,GOAt,
3652
12, UFM 423
GL
File Management Section - ASSIGN - UFM 10
The IBM MVS/XA Version 67 (and all previous releases) MSC/NASTRAN system
was knowingly released with a potential problem. Although this potential
problem area has been mentioned in Section 7.6 of the MSC/NASTRAN Application
Manual, it is documented here to assist the user and client support. If a FREE
or RLSE is performed on an MSC/NASTRAN database file (or allocated space is
otherwise released following completion of a job), the maximum size of the file
may be permanently reduced but the MSC/NASTRAN GINO block count will not be
adjusted. This could potentially cause problems on restart jobs from such
databases since MSC/NASTRAN will expect additional space to be available, when
in fact the file is full. This could result in the message "UFM
1012(GALLOC)DBSET IS FULL AND NEEDS T
3654
67.5
Error Code 97000000
File Management Section - ASSIGN - SVC 99
An error exists in IBM's Storage Management Software (SMS) which may cause
MSC/NASTRAN jobs which use dynamic allocation to fail with SVC 99 error code
97000000.
Avoidance: This is an error with IBM's software and may be corrected by
applying corrective patches to the SMS software. The following APARs may be
obtained from IBM to correct this error:
OY4772 (primary), OY44547,OY42898,OY41248,OY42704
3655
wers
67.5
Geometric Nonlinearity - SDR2 - Wrong Ans
Wrong answers for element forces can be produced in SOL 66 when QUAD4
and/or TRIA3 elements are used with
PARAM,LGDISP,1 without any material nonlinearity. Errors were introduced in
SDR2 when fixes were incorporated for Error 3071. The stress output is
unaffected by this error.
Avoidance: If the QUAD4/TRIA3 elements reference MAT1 data, then
inputting an associated MATS1 Bulk Data
entry which is defined such that the material properties remain in the linear
range will avoid the error. There is no avoidance for composite elements which
specify PCOMP/MAT8 Bulk Data.
3657
cessive Output
68.2
Documentation - SOL 66, SOL 106, STR - Ex
In material nonlinear analysis (SOL 66, 106), a STRESS(PLOT) request will

result in the NONLINEAR STRESS
output being printed. This is an undocumented intentional feature which allows
users the option to reduce printed output by suppressing the linear stress
output while printing the SDRNL output. MSC/NASTRAN Version 68.2 has been
enhanced by adding the new NLSTRESS case control command which gives the user
complete control over the output. A request for NLSTRESS(PLOT) without a
STRESS request will not produce any linear or nonlinear printed stress output.
Avoidance: Other than deleting the DMAP call for the OFP module that prints
the undesired datablock, no known avoidance exists. In the short term MSC will
document this behavior under the User Manual description of the STRESS C
3658
Aeroelastic Analysis - WKK, RESTART - Wrong Answers
Automatic restarts in SOL 144 which include new DMI entries for the WKK matrix,
will not update the WKK
datablock.
Avoidance: Apply the following DMAP avoidance in the restart run.
COMPILE AESTATRS SOUIN=MSCSOU NOLIST NOREF
ALTER 44 $
ENDIF $ NOQAX=-1
DELETE /WSKJ,QAA,QAX , , / $
PUTSYS (1,109) $
ALTER 54,54 $
PUTSYS (0,109)
3659
67.5
M - Wrong Answers
Aeroelastic Analysis - Case Control, PARA
In Version 67, SOL 145 was extended to allow multiple subcases. This
modification resulted in PARAM entries
placed in the Case Control Section not being honored. No warning messages are
issued. This error will result in
wrong (i.e., unexpected) answers if the user's intent was to set PARAM,VREF to
a value other than 1.0.
COMPILE SEFLUTTR SOUIN=MSCSOU NOLIST NOREF
ALTER 55 $
PVT PVTS,CASE1 // $
3660
ong Answers
67.5
Aeroelastic Analysis - APD, SPLINE2 - Wr
Error 2455, which stated that if a SPLINE2 references a nonexistant

coordinate system the run will proceed, no
message would be issued, and wrong answers could result, was claimed to be
fixed in Version 66. However, it has
been discovered that the error has not been fixed for all situations.
Avoidance: Make certain that all referenced coordinate systems exist.
3661
ut
67.5
Miscellaneous - PARAM,POST - Missing Outp
In SOL 106, setting PARAM,POST will not result in the combined linear and
nonlinear element data (OSES1X and
OEF1X datablocks) being output by the OUTPUT2 module for post processing.
Avoidance: Include the following alter.
COMPILE SEDRCVR SOUIN=MSCSOU NOLIST NOREF
ALTER 218 $
IF( POST<0 AND OES='YES' ) THEN $
OUTPUT2 OES1X//OTAPE2/OUNIT2//OMAXR $
OTAPE2=0 $
ENDIF $
IF(POST<0 AND OEF='YES') THEN
OUTPUT2 OEF1X//OTAPE2/OUNIT2//OMAXR $
OTAPE2=0 $
ENDIF $
3662
67.5
Restarts - NDDL - Wrong Answers
Due to an error in the NDDL dependency check, if additional modes are

desired for the superelements in the restart run with new EIGR/EIGRL entries,
the additional component modes will be calculated; however, they will not be
passed down to the residual structure. The same component modes from the
coldstart run will be passed down to the residual structure instead.
Avoidance: Add a dummy DYNRED Bulk Data entry in the restart run.
3663
67.5
DMAP - RFAlters - UFM 779
On the CRAY UNICOS system and possibly other UNIX systems, if more than
one member of the RF alter library is
requested, then the run may fail with UFM 779 - "RFALTER RFXXDYY CANNOT BE
FOUND". This error will only occur when
the RF alter names being included are of different length. Thus, the error is
most likely to occur when a user's
alter is added to the MSC/NASTRAN RF alter library and it contains a different
number of characters as compared to
the standard member(s) being requested.
Avoidance: Make sure that all members of the RFAlter library requested
for a particular solution sequence
have the same number of characters. As an example, if RF24D81 is requested, an
acceptable user-added member would
be RF24D6X, and an unacceptable member would be RF24D66X. If di
3665
67.5
Cyclic Symmetry - RFORCE - Wrong Answers
If the ROTation option is used in cyclic symmetry, and the structure

consists of 3 segments and the RFORCE
rotation vector is not parallel to the axis of symmetry in the basic coordinate
system, then the answers will be
incorrect.
Avoidance: Modify the model so that it does not have 3 segments.
3666
68
Documentation - MAT8 - Missing Remark
The STRN field on the MAT8 Bulk Data entry indicates whether Xr, Xc, Yt,
Yc and S are stress or strain
allowables (real=1.0 for strain allowables and is blank(default for stress
allowables) for failure criteria
calculations. It should be further stipulated that strain allowables can be
specified only if the user selects the maximum strain theory (STRN for FT on
the PCOMP Bulk Data entry). For all other failure criteria, the program
assumes Xt, Xc, etc., are stress allowables irrespective of what is specified
for STRN on the MAT8 Bulk Data entry.
3668
68
Documentation - FMS, INIT - SFM 446
The examples on page 2.2-14 of the Version 67 MSC/NASTRAN User's Manual

which illustrate the use of the INIT statement contain an extra "=" sign within
the parentheses. If used as show SYSTEM FATAL MESSAGE 446 (DBCRT) ERROR
ATTEMPTING TO CREATE A FILE (LOGICAL= = ) " will be issued.
Avoidance: The correct example is as follows:
INIT MASTER(RAM) LOGICAL=(MASTER(5000))
INIT OBJSCR LOGICAL=(OBJSCR(5000))
3669
777
67.5
Restarts - RESTART, PCOMP - SFM 4276 EC7
A restart run of a model which contains PCOMP Bulk Data entries using the
SYM option may fail with SFM 4276
EC7777 in the RESTART module or perform inefficient restarts.
Avoidance: The error is the result of an inadequate description in the
NDDL for the PCOMP entry. The only
avoidances are not to use the SYM option of the PCOMP entry, execute a cold
start, or if no changes are being made
to any properties in the model then apply the following alter:
COMPILE IFPL, SOUIN=MSCSOU
ALTER 83,83 $ DON'T CHECK EPT
COMPILE PHASE0, SOUIN=MSCSOU
ALTER 256,256 $ DON'T CHECK EPTS
3671
stem Error
67.5
Miscellaneous - MSC/NASTRAN Applicat - Sy
The default block size (512 or 1024) for tar tape formats on the IBM
RS/6000 is dependent on the version of the AIX OS. If a user attempts to read
a tape with the incorrect default, the following message is obtained:
"0511-193 AN ERROR HAS OCCURRED WITH INPUT OR OUTPUT". This error has been
misidentified as a media problem. (IBM RS/6000 Version 67 only)
Avoidance: If a client encounters this problem, the block size may be
specified during the installation. For AIX this is easily accomplished through
'smit', a menu-driven system management. The path to change the block size is
smit/devices/Tape Drive/Change characteristics. The 'Change Characteristics'
panel for the tape device in question has block size as a parameter. The
client can use the 'tab' key to change the
3672
Answers
67.5
Acoustics - PARAM,PANELMP,STRUCT - Wrong
If modal participation factors are requested for panels in acoustics and

the request is for a selected sets of grids, then the panel participation
factors will be wrong.
The new acoustic capability in Version 67 uses PARAM's instead of Case
Control entries to control output selection of Modal Participation Factors. It
was intended that the PARAM's would be used in combination with OFREQ requests,
where OFREQ would control the frequencies and the PARAMs would control the
number of modes at which factors would be calculated and printed. This is
documented correctly in the MSC/NASTRAN User's Manual Section 1.16, however SOL
108 uses the PARAMs to control the frequency selection. The factors that are
printed are correct but a subset of modes cannot be selected.
Avoidance:
3674
Wrong Answers
67.5
Optimization/Design Sensitivi - DRESP2 -
The sensitivities of second-level responses (DRESP2) may be incorrect if

both of the following conditions are
met:
1. The response is a function of first-level responses (DRESP1) .
2. One of the DRESP1 responses is on the order of 1.0E-2 or smaller.
Avoidance: If possible, try to constrain the small DRESP1 responses
directly rather than using them in DRESP2 relations. Other avoidances require
rescaling the model or specifying an MPC relation which rescales the specific
response.
Users of design optimization should be aware that there are inherent
difficulties in numerical differentiation of dimensional quantities. These
difficulties are that responses of widely different magnitudes can be expected
(i.e. stress versus displacement). With an understan
3675
67.5
Matrix Methods - FBS - Poor Performance
FBS Method 2 was not compiled to take advantage of vectorization on the

IBM MVS/XA Version 67 release of
MSC/NASTRAN. If FBS Method 2 is selected on a vector machine, a performance
degradation of 3 to 4 times may be
experienced in the FBS module versus Version 66B. (IBM MVS/XA Vector Version
67 only)
Avoidance: FBS Method 2 is selected based on the performance estimate
only when the number of right-hand
sides approaches the order of the left-hand side. In typical problems where
the FBS operation is significant to
the total run time, this situation only arises when solving for GOAT in
superelement analysis. In superelement
problems where the number of degrees of freedom on the boundary of a
superelement is less than 10 percent of the
number of degrees of freedom in t
3676
67.5
rect File Assignments
File Management Section - ASSIGN - Incor
On the IBM MVS/XA Version 67 release of MSC/NASTRAN, the default filename

or filename prefix may be determined
from several sources. The sources are the JCL DD statements, the default file
prefixes, the file prefixes
specified in an RC file or from the PARM field. An error may occur if any part
of the filename specification
contains a dollar sign ($).
If a filename is derived from a JCL DD statement or built from keywords
specified in the PARM field, then the
filename has all characters to the right of and including the "$" removed from
the filename specification.
Note also that if an ASSIGN, INCLUDE, or RC file keyword specifies a
filename or prefix containing a "$" and
the specification is not enclosed with 'quotes', then all data to the right of
and including t
3677
67.5
Nonlinear Analysis - COPY - UFM 1126
When the iterations for the current subcase have been terminated without
convergence, a fatal error is
encountered when erroneously attempting to store the last (unconverged)
solution in place of the previous converged
solution. (Version 66+ only)
Avoidance: Apply the following DMAP avoidances to SOL 66 and 106
respectively:
SOL
66 $
COMPILE SOL66 SOUIN=MSCSOU NOLIST NOREF
ALTER 1109,1109
IF ( SOLCURI <> SOLCUR AND SOLCUR <> SOLPRE ) THEN $
ENDALTER
SOL 106 $
COMPILE NLSTATIC SOUIN=MSCSOU LIST NOREF
ALTER 303,303
IF (SOLCURI<> SOLCUR AND SOLCUR <> SOLPRE ) THEN $
ALTER 328
PRTPARM //0/'SOLPRE' $
3678
68
Superelements - Restarts - UFM 5423
Automatic Restarts in SOL 101 will fail with UFM 5423 whenever the applied
load condition (other than SPCDs) is modified and the SPCD enforced deformation
condition in the previous run is left unmodified for the restart. (Version 66+
only)
Avoidance: The proper matrices will be updated if a dummy (unreferenced)
SPCD Bulk Data entry is included in the restart run.
3679
ssing Plots
67.5
Plotting - NEUPS - Overwritten Plots, Mi
If a multi-page plot file generated by the NEUPS utility is displayed

using the SUN PageView utility, all
pages in the file will overwrite one another in the display and the PageView
will indicate that only one page is
present in the plot file.
While investigating this problem, an error was found when specifying a pen
number greater than 3. As a result
of this error, pages may not be printed or lines may be drawn incorrectly.
Since this error occurs in all versions
of the NEUPS utility, the following changes should be made by all users of the
NEUPS utility.
In subroutine NPLT, remove the following line:
if (c .gt. 3) ipen = 3
In subroutine PLOTS, replace the line:
write (unit=ips ,fmt=10) '%!-----PS picture-----'
with:
write (unit=ips
3680
67.5
Matrix Methods - FBS - SFM 4276 EC 7777
FBS method 2 will fail with the FREAD GINO error SFM 4276 EC 7777 when it
attempts to write a solution where

the first string of a column is longer than the BUFFSIZE. Note that FBS method
2 operates on the transpose matrix,
thus the number of terms in a column is the number of right-hand sides being
solved.
Avoidance: Increase the BUFFSIZE or force Method 1 or 1A by setting the
NASTRAN keyword FBSOPT to either -2
or -1.
3681
6 EC 7777
67.5
Matrix Methods - SPARSE, MPYAD - SFM 427
SPARSE MPYAD may fail with SFM 4276 EC 7777 (integer overflow) when
multiple passes are used and the A matrix
has a large deviation in the density of its columns.
Avoidance: Deselect SPARSE MPYAD by setting the SPARSE NASTRAN keyword to
0. Other values of the SPARSE
NASTRAN keyword are possible which will allow SPARSE DECOMP and FBS while
deselecting SPARSE MPYAD. Please refer
to the description of the DECOMP module in Section 5.4 of the MSC/NASTRAN
User's Manual.
3682
276 EC 923
67.5
Parallel Matrix Methods - DECOMP - SFM 4
If the maximum bandwidth of the matrix to be decomposed exceeds 65,535,

then an integer overflow will occur in
the parallel decomposition subroutine that determines the core size. SFM 4276
EC 923 will be output from the
DECOMP module. This error will occur on all short-word (32 bit) machines.
Avoidance: The only avoidance is to revert to standard decomposition,
which is the default.
3684
67.5
ing Point Exception
Aeroelastic Analysis - AMG, PSTA - Float
If the user requests a leading edge sweep correction (NTHRY=2) to a Piston

Theory aerodynamics model that has
a subsonic leading edge, a machine dependent error message indicating a
floating point exception will result.
Avoidance: The user must only specify a leading edge sweep correction
when the leading edge is supersonic
(Mach number must be greater than the secant of the leading sweep angle)
3685
67.5
Elements - HEXA, TETRA - Wrong Answers
In MSC/NASTRAN Version 67 a new method was introduced to define the

element coordinate system for solid
elements. This was done to correct Error 2839. An error may result in an
improper basic transformation matrix.
If this error occurs, the resulting stiffness matrix will not pass a rigid body
test and incorrect displacements and stresses will result. The worst errors
will occur when "long-almost-square" HEXA or TETRA elements are used.
"Long-almost-square" is defined as an element with an aspect ratio greater than
20 with a cross-section-aspect
ratio of less than 1.5. Smaller errors occur for shorter elements if the
cross-section is nearly square. If the element edges are parallel to the basic
coordinate axes, the error will not occur. (Version 67 only)
Avoidance:
3686
67.5
Miscellaneous - PSHELL/MAT2 - UFM 5199
If free field format is used for the PSHELL/MAT2 and possibly other
entries and the number of characters on a
line exceed 72, then the job may fail with UFM 5199 indicating that the entry
has an integer/BCD field with more
than 8 characters even though it may not. Furthermore, the automatic
continuation feature does not work in this
case. Values in columns greater than 72 will be converted to blanks. This may
potentially lead to unexpected
answers.
Avoidance: When using free format, do not exceed 72 characters. The
delimiter "comma" is considered a
character.
3687
GL
DMAP - MERGE - Infinite Loop
If the partitioning vector used in the matrix MERGE operation is double

precision, then the problem may get into an infinite loop. This error is most
likely to occur when a user's DMAP is involved.
Avoidance: Make sure that the partitioning vector is single precision.
3688
Files
67.5
Miscellaneous - Demo Library - Truncated
The files delivered on the IBM MVS/XA Version 67 system have a fixed
record length of 80. Consequently, the
portion of the Demo Library file "error67.lis" that is longer than 80 columns
is truncated.
Avoidance: Only the general limitation section of the file exceeds 80
characters. The file is meant to be
used as a tool and is still useful for searching for errors and limitations of
concern. Since the file is not
updated by MSC once the system is built, it is recommended that the user always
refer to the bulletin board or
Section 6.4 of the MSC/NASTRAN Application Manual to ensure that the latest
status of the error is being
referenced.
3690
67.5
DBC/TRANS/ACCESS - TRANS - SFM T10 (XMIT)
If a STRESS output request is made that includes gap elements (note, a

STRESS request is made to obtain GAP
element force output), then a subsequent TRANS of the database will fail with
the message SFM T10 (XMIT). (Version
67 only)
Avoidance: Do not request STRESS output for GAP elements.
3691
ffness Update
67.5
Nonlinear Analysis - GAP - Excessive Sti
Models with a large number of GAP elements utilizing the new adaptive gap
option in Version 67 may perform
unnecessary stiffness updates when the adaptive penalty adjustment is used.
(Version 67 only)
Avoidance: There is no avoidance; however, the final results are correct.
3692
s
GL
Design Sensitivity - DVSET - Wrong Answer
In the old design sensitivity capability SOL 51 or 101 if a design

variable references a non-existing PID, then the sensitivity coefficient for
the offending design variable will be incorrect. The sensitivity coefficients
for design variables with existing PIDs are correct. The old eigenvalue
sensitivity solutions will ignore the design variable without warning.
Avoidance: Make sure that the DVSET entry references an existing PID or
use the new design sensitivity
capability.
3693
67.5
Composites - IFP6 - Extra Output
When the ECHO=PUNCH option is specified in the case control of a data deck
containing PCOMP entries the
equivalent PSHELL/MAT2 entries are printed in the punch file. However, if
echo=none is specified along with any punch output request, e.g.,
DISP(PUNCH)=xxx, then a copy of the equivalent PSHELL/MAT2 output will
incorrectly be sent to the punch file.
Avoidance: An echo=sort or echo=sort(yyy) will eliminate the extra output
in the punch file at the expense of creating possibly unwanted output in the
F06 file.
3696
ssing Output
67.5
Superelements - PARAM,POST, DBLOCATE - Mi
If PARAM,POST is specified in a superelement run that uses multi-MASTER

and DBLOCATE statements, the OUTPUT2 and XDB output will contain results for
the residual only. (Version 66+ only)
Avoidance: To obtain results for postprocessing of the upstream
superelements, apply the following alter:
COMPILE SUPER3, SOUIN=MSCSOU,NOLIST,NOREF
ALTER 90,90 $
ALTER 104 $
TYPE DB,PVT $
PVT PVT,CASEDR/PVTX $
Also, for XDB output you must first submit a run which creates the XDB
file with the geometry. Use the recommended input file below. Only the
"SEMAP" data base has to be DBLOCATE'd and the database created by this run may
be deleted.
NASTRAN SYSTEM(143)=1
ASSI SEMAP=
ASSI DBC=
$Insert filename of SEMAP MASTER DBset

$De
3697
67.5
PLOADi, - Wrong Answers
Material Nonlinear Analysis - TEMP(LOAD),
In SOL 106, element loadings may produce wrong answers when superelements are
used. The SPC force results for any superelements which have member loadings
applied will not include the reaction induced by the member loads. Example
loadings are temperature, any PLOADi entries, and GRAV entries. Please see
related error 7015.
Avoidance: Use SOL 66 or apply the following alter to SOL 106:
compile sedisp souin=mscsou nolist noref
alter 87,87
mpyad pss,crx,/pssx $
3698
67.5
Loads - TEMP, TREF, BEAM - Wrong Answers
If TEMP(INIT) is specified along with a nonzero TREF, the results from

models with BEAM elements will be
wrong. The BEAM element's thermal expansion is generated incorrectly using
TREF instead of TEMP(INIT). In data
recovery when the thermal strain is removed, TEMP(INIT) is used.
Avoidance: The MATi's TREF entry must be left blank.
3699
67.5
Grid Point Force - GPFDR - Wrong Answers
If grid point force balance output (GPFORCE) is requested with a selective

set and there is TEMP(LOAD) or
DEFORM loads, then wrong answers may occur.
Avoidance: Do not use a selective set, use GPFORCE=ALL instead.
3700
Wrong Answers
68
Optimization/Design Sensitivity - PACAB -
The effect of perturbing the acoustic damping element CHACAB/PACAB is not

accounted for in design sensitivity analysis. This may lead to wrong answers
if the acoustic damping element is part of the design model. (Version 67 only)
3701
Elements - CTRIA6 - Wrong Answers
When specifying the element thickness of the corner nodes on the CTRIA6 Bulk
Data entry, the volume of the
element will be incorrect in the PARAM, EST, 1 output. All other answers
including the mass are unaffected by this error.
Avoidance: If varying thickness of the element is desired, there is no
avoidance. In the case of constant
thickness, specify the thickness on the PSHELL entry.
3702
1114
68
Superelements - INIT MASTER(NORAM) - SFM
When specifying INIT MASTER(NORAM) in a run with superelements, the

message SFM 1114 (XREMOV), "POTENTIAL
INFINITE-LOOP PROBLEM EXISTS IN DBENTRY TABLE FOR DATA BLOCK = GOA" may occur.
(Version 67 only)
Avoidance: Remove the INIT MASTER(NORAM) FMS statement.
3703
67
consistent Property
The example input on Page 2.14-64 of the MSC/NASTRAN Application Manual

specifies the cross-sectional area of the PBEAM entry as 4.0. To be consistent
with Figure 19 on page 2.14-62, the area should be 1.732. This section of the
Application Manual discusses Material and Geometric Nonlinear Analysis, it has
been superseded by the Handbook for Nonlinear Analysis.
3704
ALLOC FAILED
67.5
Documentation - MSC/NASTRAN Applicat - HP
Section 7.6.2.11 of the Version 67 MSC/NASTRAN Cray Unicos Application

Manual states that the "lm" parameter
on the "qsub" command must be greater by at least 900,000 words, which is the
memory required to load MSC/NASTRAN.
If this value is used, the error "HPALLOC failed in SUBROUTINE FIELDLN" is
issued. This error is documented in
Section 7.6.5.1. (CRAY Unicos only).
Avoidance: The avoidance is to increase the difference between the "lm"
and "mem" parameters to at least 1.2
megawords, by increasing the "lm" parameter or decreasing the "mem" parameter.
The appropriate differential is
machine and user-dependent depending on the environment variables used. If the
user sets environment variables,
the differential should be increased. The value of 900,000 words for th
3705
6136
67.5
Matrix Methods - DECOMP, SYSTEM(69) - UFM
If SYSTEM(69) is set via the NASTRAN input, it may not be passed to the
decomposition module. In the case of sparse decomposition, if SYSTEM(69)=256,
then UFM 6136 (DFMSA), "INSUFFICIENT CORE FOR SYMBOLIC PHASE OF SPARSE
DECOMPOSITION. USER ACTION: INCREASE CORE BY *** WORDS" is issued, and the
DECOMP module does not proceed with the non sparse method, as documented in the
MSC/NASTRAN User's Manual Section 5.
Avoidance: The avoidance for the Structured Solution Sequences, in
Version 67 is to apply the following
alter.
COMPILE DMAP=SEKRRS, SOUIN=MSCSOU $
ALTER 19 $ BEFORE DCMP MODULE
TYPE PARM,,I,N,MVAL $
MVAL = GETSYS(MVAL,69)
DECOMP = DECOMP + MVAL
ENDALTER
For the Unstructured Solution Sequences and previous versions, the same
alter must be inserted directly
3706
GL
- Wrong Answers
Optimization/Design Sensitivity - DRESPi
MSC/NASTRAN's implementation of modal frequency sensitivity analysis yields

wrong answers for sensitivity responses when massless degrees of freedom are
present. This includes stresses, forces, and rotational displacements affected
by the massless degrees of freedom. (Version 67+)

Avoidance: Use a direct approach.
3707
67.5
Miscellaneous - TPL - Missing Data Decks
A decision was made for MSC/NASTRAN Version 67 to not deliver data decks
which were not executed during system testing. While these test decks may have
been useful for demonstration purposes, they were found to be insignificant or
redundant from a code coverage-testing perspective. Since many of the decks
may have been incompatible with the current system requiring DMAP alter
maintenance or demonstrating a superseded capability, it was decided not to
deliver them.
Avoidance: Most problems may be accessed from a prior version's TPL. In
Version 68, these demonstration problems will be delivered in a separate
directory. Application note problems will remain consistent with the original
application note. That is, decks that contain DMAP'S or any other non-upward
compatibilit
3708
276
67.5
Parallel Matrix Methods - PDCOMP - SFM 4
If more than 2 processors are available on a DEC VAX/VMS computer and more
than 2 processors are requested by
setting SYSTEM(107)=n, then the job may fail in various ways due to
insufficient resources. (DEC VAX/VMS Version
67 only)
Avoidance: The system will try to create (n-1)**2 +1 processes. The only
avoidance is request 2 or fewer
processes.
3709
Nonlinear Analysis - TABLES1 - Unreasonable Resources
Dave, If this is still true then we should just document it in the QRG.
--Mike
It has been observed that for certain problems if the stress-strain values
specified on the TABLES1 Bulk Data entry are defined from a positive to a
negative range, then a slower convergence rate may be encountered.
Avoidance: Specify the stress-strain values in ascending order.
3710
sults
68
Grid Point Force - SOL 114 - Incorrect Re
If a grid point force balance is requested in SOL 114, Version 67, the
output will not include the applied loads.
Avoidance: Apply the following DMAP alter in SOL 114 for Version 67 Only:
COMPILE SEDRCVR SOUIN=MSCSOU NOREF NOLIST
ALTER 249,249 $
TYPE DB PJ,FORE $
MPYAD PJ,FORE,/PG1 $
3711
GL
- Wrong Answers
Material Nonlinear Analysis - TEMP(LOAD)
Currently, the thermal strain is not proportioned for the linear elements
in a multiple-step subcase. Thus, the intermediate data recovery is incorrect
for all linear elements when thermal loads are applied.
Avoidance: Use elements that are potentially nonlinear and user
PARAM,LGDISP,1
3713
68
- UFM 4511, SFM 3007
Nonlinear Analysis - SOL 106, PARAM,SERST
If the multiple master technique is used in SOL 106 and upstream

superelements are processed in a run without processing the residual, then UFM
4511 "SUBCASE *** DOES NOT REFERENCE AN NLPARM BULK DATA CARD" will be issued
at the end of the run. This error has no effect on the results and can be
ignored. The job can be restarted and the residual processed. However if
PARAM,SERST,SEDR is used in a data recovery restart run, then the job will exit
without performing data recovery.
Avoidance: Apply the following DMAP alter in all upstream superelement
runs:
COMPILE NLSTATIC SOUIN=MSCSOU NOLIST,NOREF
ALTER 23 $
EXIT $
Apply the following DMAP alter in the data recovery restart run:
COMPILE SUPER1 SOUIN=MSCSOU NOLIST NOREF
ALTER 34,34
3714
le
68
Documentation - VECPLOT - Incorrect Examp
Example 2. under the MSC/NASTRAN User's Manual description of the VECPLOT

module contains an error in the MATGPR DMAP statement. The example is
corrected in Version 68 of the MSC/NASTRAN DMAP Module Dictionary.
Avoidance: The correct DMAP statement is as follows:
MATGPR GPL,USET,SIL,UGVBASIC//'H'/'G' $
3716
ut
67.5
Miscellaneous - PARAM,POST - Missing Outp
Even if PARAM,OGEOM,YES is specified in conjunction with PARAM,POST,-1 the

geometry information will be
missing from the OUTPUT2 file. This information is required for Version 3 of
PATRAN. Version 2 or earlier does
not require this output. An enhancement in the latest version of SDRC/IDEAS
results in deficient data when
PARAM,POST,-2 is used with RF66D66.
Avoidance: If the geometry information is desired in the PATRAN OUTPUT2
file, replace the following DMAP
statements in the RFXXD66 alter:
IF ( POST=-2 AND (OGEOM='YES' OR OGEOM=' ')) THEN $
with
IF (OGEOM='YES' OR OGEOM=' ') THEN $
For the SSS:
COMPILE SUPER3 SOUIN=MSCSOU $
ALTER 72,72
IF (OGEOM='YES' OR OGEOM=' ') THEN $
If the OQG1 data is required for the SDRC/IDEAS OUTPUT2 file, then replace
3717
ect Keyword
67.5
DBC/TRANS/ACCESS - TRANS/RECEIVE - Incorr
The wrong keyword, 'GDB', is used in the TRANS and RECEIVE PROC delivered
with the IBM MVS/XA MSC/NASTRAN
Version 67 system. The keyword 'XDB' should have been used instead. (IBM
MVS/XA Version 67 only)
Avoidance: Modify the procedure to be consistent with the
machine-dependent documentation in Section 7.6 of the MSC/NASTRAN Application
Manual.
3718
68.2
Loads - RFORCE - Wrong Answers
Remark 5 under the MSC/NASTRAN User's Manual description of the RFORCE

Bulk Data entry states that METHOD=2 must be used when computing the forces
resulting from the angular acceleration and that coupling terms are not
computed. In fact, the CONM2s I11, I22, and I33 terms are ignored as well.
The only forces calculated are those due to translational mass terms on the
diagonal.
Avoidance: There is no avoidance. MSC/NASTRAN Version 68.2 has been
enhanced to include the angular acceleration terms.
3719
69
DMAP - MATMOD - Wrong Answers
MATMOD option 3 is supposed to zero out rows and columns of specified degree of
freedom. However, if the first term to be zeroed out in a column is null, then
subsequently incorrect terms will be zeroed out.
Avoidance: There is no simple avoidance.
3720
68
Restarts - RESTART - UFM 1215
In Version 67, due to an inconsistent formatting of the title page version

number, a restart run using a
MSC/NASTRAN database from a binary-compatible machine may fail with UFM 1215.
Avoidance: Adding the following NASTRAN statement will result in the
title page compatibility check being
ignored.
3721
67.5
- Missing Message, Wrong Answers
Superelements - PARAM,FIXEDB PARAM,SERST
When using the multi-master technique with external superelements, it is

possible that the results for the
superelements will be the fixed boundary solution. This error occurs when
PARAM,FIXEDB,-1 is specified and the
user fails to specify PARAM,SERST,SEDR during data recovery of the external
superelement. Note that if external superelements are not present and the user
fails to specify PARAM,SERST,SEDR, then DMAP FATAL MESSAGE 9058 would be
issued.
Avoidance: Specify PARAM,SERST,SEDR as documented in the MSC/NASTRAN
User's Manual Section 3.1.3 during the data recovery of the external
superelement and apply the following DMAP in Version 67 when using the
multi-master method with PARAM,FIXEDB,-1.
COMPILE SUPER1, SOUIN=MSCSOU, NOLIST, NOREF
ALTER 34,34 $
3722
Allocation
67.5
Miscellaneous - NASTRC - Incorrect Space
On the IBM MVS/XA Version 67 system, all the space parameters, e.g.,
SDBALL, defined in the user's nastrc file
are ignored. (IBM MVS/XA Version 67 only)
Avoidance: Specify the desired space values in the File Management
Section of the input data.
3723
67.5
DMAP - PARAM,POST - Missing Output
Contrary to the MSC/NASTRAN User's Manual documentation for the

PARAM,POST,-2 Bulk Data entry, the grid point
stress results are not written to the OUTPUT2 file when using "PARAM,POST,-2".
Furthermore, the parameter name for
the GPSTRESS should be OGPS instead of OGS as documented in Section 3.1 of the
MSC/NASTRAN User's Manual.
Avoidance: If grid point stress results are desired in the PARAM,POST,-2
OUTPUT2 file, then insert the
following DMAP alter avoidance:
COMPILE SEDRCVR,SOUIN=MSCSOU,NOLIST,NOREF
ALTER 136,136 $
IF (POST<0 AND OGPS='YES') THEN $
3724
68
Miscellaneous - GENTIM - Machine Crash
In Version 67, it has been observed on some HP 9000/750 machines that when
GENTIM is executed, the system may lock out all users, crash, and then
automatically reboot itself. This behavior has only been observed for this
machine with non-HP chips. (HP 9000/750 Version 67 only)
Avoidance: This behavior is believed to be a hardware problem. Contact
your HP representative to have the chips replaced.
3725
67.5
Loads - SPCD - Wrong Answers
In Version 67, when specifying an enforced displacement with an SPCD Bulk

Data entry with no other static
loads (i.e., FORCE,SLOAD, etc.), UWM 3204 is supposed to be issued and ignored.
Not only is the message not issued
but all the requested output is null. (Version 67 only)
Avoidance: Add a corresponding dummy FORCE Bulk Data entry.
3727
utput
70.7
Eigenvalue Analysis - REPCASE - Missing O
If REPCASE is used to request additional output in an eigenvalue analysis,

and the total number of REPCASEs equals the number of modes calculated in the
run, then the data recovery requested for the last eigenvalue will be missing.
This error is corrected in Version 67.5 but the error is re-occurring in
Version 68.
Avoidance: Request an additional eigenvector to be calculated.
3731
XXXX. FNDPID
67.5
File Management Section - DBLOCATE - UFM
On IBM MVS/XA machines, if the physical filename referenced by the

DBLOCATE statement does not contain a
period, then the job may fail with the above error message. (IBM MVS/XA
Version 67 only)
Avoidance: Make certain that the physical filename referenced by the
DBLOCATE statement contains a period.
An example of a valid physical filename is 'USER01.PROB01.MASTER'. An invalid
physical file name is '&XMSTR'.
3732
M 1251 CHKNAM
67
Miscellaneous - IBM Dynamic File All - SF
On IBM MVS/XA machines, if a temporary filename exceeds 8 characters, then

MSC/NASTRAN will reject the name as
an incorrect dataset name specification and the job will end with a system
fatal message.
The MVS operating system, however, will accept temporary dataset names
that begin with a single '&' followed
by 8 characters for a total of 9 characters. MVS will also accept temporary
dataset names the begin with '&&'
followed by 8 characters for a total of 10 characters.
Avoidance: Only specify temporary dataset names that are 8 characters or
less including the leading '&'s.
3733
68
P/TEMP(MAT - SFM 3007
Transient Nonlinear Analysis - NLITER, GA
SOL 129 models with initially closed

the ADAPT method on the TSTEPNL entry
may fail with the message 'LOGIC ERROR IN
ILLEGAL INPUT TO NAGAPD'. The exact
conditions that cause the error are under
Avoidance: The error may be avoided
TSTEPNL entry or starting with an
initially open GAP (UO>0.0).
GAP elements (U0<0.0) that specify

NAGAPD : DELU = 0' and 'SFM 3007
investigation.
by requesting the AUTO method on the
3734
22
68
Documentation - DTI,INDTA, RF24D41 - UFM
The MSC/NASTRAN User's Manual does not document the requirement that a
DMAP statement is necessary to utilize the DTI,INDTA Bulk Data entry that is
used for stress sorting in conjunction with RF24D41.
Avoidance: Include the following line with the DMAP alter shown in Remark
1 of the RF24D41 description and a remark under the description of the
DTI,INDTA Bulk Data description indicating that the alter is required.
DTIIN DTI,DTINDX/INDTA,,,,,,,,,/ $
3735
67.5
Very large problems may fail in the FBS module's timing equations with the
integer overflow message SFM 4276
EC 7777. The error is machine dependent and problem size dependent. The
problem size that will cause the error is
a function of several model characteristics and not simply the number of
degrees of freedom.
Avoidance: The only avoidance is to break the model up into
superelements.
3736
67.5
rong Answers, No Message
Optimization/Design Sensitivi - DOM1 - W
Remark 4 under the MSC/NASTRAN User's Manual description of the DLINK

entry states that an independent IDV
must not appear more than once on the same DLINK entry. There is no check in
the code against this violation. In some instances the contributions are
summed and in others, such as the optimization process, the last occurrence of
the IDV is used, and earlier references are ignored. In Version 67.5 the
message "USER FATAL MESSAGE 6321 (DOM1A) INDEPENDENT DESIGN VARIABLE ID **
APPEARS MORE THAN ONE ON THE DLINK ENTRY ASSOCIATED WITH DEPENDENT DESIGN
VARIABLE ID **" will be issued.
Avoidance: There is no avoidance. The responsibility to satisfy Remark 4
rests on the user.
3737
3003, SFM 3003
68
Nonlinear Analysis - NLPCI - SFM 4276 EC
The enhancements to the ARC methods in Version 67 prevent changes to the L-set
between subcases. That is,
changes to the SPC or MPC sets are not allowed between subcases. This
limitation prevents the analyst from
restraining an unstable structure in the first subcase and removing the
restraint in later subcases. If this
action is attempted, the run will fail and will issue the message SFM 4276 EC
3003, SFM 3003 ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA SET
DUGVMO (FILE 209)".
Avoidance: The use of ARC methods is not recommended for enforced displacement
type problems. SUBCASEs which involve changes in the L-set must not refer to
an NLPCI Bulk Data entry.
3738
tabase Size
67.5
Documentation - SDBALL, SSOU, SOBJ, - Da
Section 7.6 of MSC/NASTRAN Application Manual for the IBM MVS/XA Version
67 computer describes five RC file keywords (SDBALL, SSOU, SOBJ, SSCR, and
SMASTER) that are intended to allow the local installation to change the
default number of blocks assigned to the database files through the RC file.
These keywords are inoperable. The user can only change the number of blocks
assigned to a database file using JCL or ASSIGN statements. (IBM MVS/XA
Version 67 only)
3739
DB - UIM 2318,
68
Aeroelastic Analysis - RESTART, DBTRANS,
SFM 4276 EC 1604

SOL 144, 145 and 146 restarts regenerate data blocks unnecessarily even
for data recovery only restarts.
Furthermore, a SOL 144, 145 or 146 restart from a database that was processed
by DBTRANS will have aerodynamic
matrices tables stored incorrectly. Subsequent restarts will fail with the
message "SFM 4276 GETSTB ERROR CODE
1604". This is due to improper storing of LSALL, USALL, LAJJ and UAJJ. This
error occurs for UDECOMP output(upper triangular matrices) because string
trailers are not regenerated by DBLOAD.
Avoidance: An avoidance for SOL 144 data recovery only restarts is shown
below:
$FOR THE DBLOAD STEP ON A SOL 144 DATABASE.
$NOTE: DBLOAD STEP FOR SOL 145 AND 146 REQUIRES NO ALTER
COMPILE DBTRANS SOUIN=MSCSOU
ALTER 159,159 $
APD
EDT,
3740
ing Output
68
Grid Point Stress - PARAM,HEATSTAT - Miss
PARAM,HEATSTAT,YES is used in SOLution 101 to execute a linear steady

state heat transfer analysis so that the thermal loads can be used in a
subsequent thermal stress analysis. In an effort to reduce disk space usage,
certain data blocks are assigned to scratch in MSC/NASTRAN Version 67.
Unfortunately, some of the data blocks written to scratch are required for
GPSTRESS output. Other data blocks written to scratch are required for
deformed and stress plots as well as x-y plots. Therefore, a GPSTRESS output
request or any of the aforementioned plot requests will not be honored.
Avoidance: Use SOLution 61 with RF61D01 or apply the following DMAP alter
in SOLution 101.
COMPILE SESTATIC SOUIN=MSCSOU NOLIST NOREF
ALTER 14
FILE POSTCDB=SAVE/PCDB=SAVE/XYCDB=SAVE $
ENDAL
3742
t Restart
67.5
Restarts - MAXRATIO, BAILOUT - Inefficien
If a job is RESTARTed after 'DMAP FATAL MESSAGE 9050 RUN TERMINATED DUE TO
EXCESSIVE PIVOT RATIOS, USER
PARAMETER BAILOUT MAY BE USED TO CONTINUE THE RUN' has been encountered in the
cold start and PARAM,BAILOUT is
included in the RESTART to allow processing to continue past the fatal message,
then previous DECOMP results will be deleted. Specifically the KLL, ULL, LLL
and DM datablocks are deleted causing the matrix reduction and
decomposition phases to be reexecuted.
Avoidance: An avoidance for SOL 101 is to apply a DMAP Alter to remove
line 231 from PHASE0 and line 89 from the IFPL subDMAPs. Another avoidance is
to modify the NDDL accordingly: But this has to be done in the cold start run
or in the delivery data base.
Line No.
Version 67
4226 DEPEN LV
3743
67.5
DBLOCATE - UFM 1124 GNFIST
Optimization/Design Sensitivit - RESTART,
An attempt to DBLOCATE data blocks in a SOL 200 RESTART for superelement

design sensitivity analysis from an
initial SOL 101 run will fail with the message "UFM 1124 GNFIST, AN APPENDABLE
OUTPUT FILE PVTS CANNOT BE ACCESSED
WITH THE DBLOCATE COMMAND".
Avoidance: Recompile the subDMAP where the failure occurs.
3747
67.5
e All - UFM 1242
File Management Section - IBM Dynamic Fil
On IBM MVS/XA machines, DBUNLOADs (or DBLOADs) performed directly to (or

from) tape will result in the message
"UFM 1242" whenever the corresponding JCL DD statement used to allocate the
tape does not specify the tape volume
serial number.
Avoidance: This message may be safely ignored as the DBUNLOAD will work
regardless. Likewise, the DBLOAD
will work regardless if the user specifies STATUS=OLD on the DBLOAD FMS ASSIGN
statement. (IBM MVS/XA Version 67
only)
3748
67.5
Documentation - MSC/NASTRAN Applicat -
Incorrect Documentation
There are several errors in Section 7.6.3.4 of the MSC/NASTRAN Application
Manual for the IBM MVS/XA Versions
66B and 67. The errors are as follows:
1. There is no "DELINC" library. It should specify "DEL" for the
library.
2. The SEDRCVR DMAP must be copied out of the DEL PDS member CCMMN. This
member contains input to compile
several distinct DMAPs. Most IBM users would infer from the documentation that
the DMAP resides in a PDS member
named SEDRCVR.
3. The JCL referenced in Step 5 at the top of page 7.6-51 should read as
follows:
//BLDSEDCV JOB (job info)
//*
//SEDRCVR EXEC NAST66B,USER='?user',
//
DBS=MYSSS,JID=SEDRCVR
//D.SYSIN DD DISP=SHR,DSN=?user.SEDCVR
//NS.NEWSOU DD DISP=SHR,DSN=?user.MYSSS.MSCSOU
//NS.NEW
3750
correct
67.5
Documentation
Page 7.7-4 of the MSC/NASTRAN Application Manual for all UNIX machines
(CONVEX, SUN4, SGI, IBM RS 6000, HP
9000/700) states that a symbolic link should be established connecting the
repository directory to the installation
directory by typing the following command:
ln /msc/bin/nastran/ usr/bin/nastran
This statement is incorrect and should read:
ln -s /msc/bin/nastran/ usr/bin/nastran
The "-s" indicates a symbolic link instead of a hard link. If the command
is typed as indicated, then the
link is not established and the subsequent specification of the "nastran"
execution command will lead to a message
indicating that the command is undefined.
3751
67.5
correct Maximum MEM
Documentation - Section 7.6 Applicat - In
Page 7.6-3 of the MSC/NASTRAN Application Manual for the CRAY Y-MP
incorrectly states that the maximum value of MEM is 63 megabytes. This should
state the maximum value for MEM is 127 megabytes. (Version 67 CRAY Y-MP only)
3754
Composites - Mislabeled Output
The individual ply stress and strain results output for a composite element are
labeled as "STRESS/STRAIN IN
FIBRE AND MATRIX DIRECTIONS". The in-plane stress and strain are output in the
fiber and matrix directions;
however, the interlaminar stress and strain output are output in the element
coordinate system.
3755
67.5
Cyclic Symmetry - MPYAD, MPC - UFM 3055
If the model in a cyclic symmetry analysis contains mpc relationships and

only the zero harmonic is requested,
then the run will fail and issue the following error messages:
*** USER FATAL
MESSAGE 3055
AN ATTEMPT TO MULTIPLY OR MULTIPLY AND ADD NON-CONFORMABLE
MATRICES TOGETHER WAS MADE IN MODULE MPYAD
Avoidance: Request an additional harmonic in the Case Control Section.
For example:
SET 10 = 0,1
HARMONIC = 10
3758
68
defined Symbols Detected
Documentation - User Modifiable NAST - Un
There is a documentation error in the Section 7.6 of the Version 67

MSC/NASTRAN Application Manual for the IBM RS 6000 computer which pertains to
User-Modifiable NASTRAN. The following line:

xlf -qextname mainal.o xmplbd.f *bd.o nastobj.a -o NAST67
should be replaced with the following:
link.com
3759
68
Dyna - VOL Keyword Inoperative
File Management Section - ASSIGN, IBM MVS
The VOL keyword of the SYS parameter for the ASSIGN statement, which is
exclusive to Version 67 of MSC/NASTRAN on the IBM MVS/XA computer, is
inoperative for database files and is ignored if specified. (IBM MVS/XA
Version 67 only)
Avoidance: The ZAP to correct this is shown below.
//JOB....
//ZAP
EXEC PGM=AMASPZAP
//SYSPRINT DD YSSOUT=*
//* THE FOLLOWING DD STATEMENT SPECIFIES THE
//* MSC/NASTRAN EXECUTABLE LIBRARY
//SYSLIB DD DISP=SHR,DSN=NAST67.NASTRAN
//SYSIN
DD *
NAME NASTRAN BIOXXX
IDRDATA FXVOLKYD
VER 1D34 0000,E904,0000,E87C
REP 1D34 0000,E854,0000E7C4
3760
67.5
Miscellaneous - RF66D66 - Extra Output
If "PARAM,POST,-2" is used in conjunction with RF66D66 and

"PARAM,OGEOM,YES", then the geometry is output
multiple times to the OUTPUT2 file whenever multiple subcases exist. The
result are correct, however.
Avoidance: Use one subcase with multiple load increments specified on the
NLPARM entry or modify RF66D66 as
indicated below.
CHANGE THE FOLLOWING SECTION OF RF66D66 FROM:
$
ALTER 1230,1230 $ SDR2 /OESNL1S
IF ( POST=-2 AND (OGEOM='YES' OR OGEOM=' ') ) THEN $
$ IF GEOMETRY DATA BLOCKS ARE REQUESTED THEN OUNIT1 AND
$
OUNIT2 ARE THE SAME UNIT.
OUNIT1=OUNIT2 $
OUTPUT2 CSTM,GPL,GPDT,EPT,MPT//0/OUNIT1//OMAXR $
OUTPUT2 GEOM2,GEOM3,GEOM4,,//0/OUNIT1//OMAXR $
ENDIF $
TO:
$
ALTER 1207 $
IF ( POST=-2 AND (OGEOM='YES' OR OGEOM=' ') ) THEN $
$
3761
67.5
Restarts - OUTPUT2 - SFM 1128 (GNLOC)
If an initial SOLution 61 run ends with a SYSTEM ABEND D37 or other

message indicating insufficient space
available for an OUTPUT2 file, a subsequent restart will fail and issue the
message "SYSTEM FATAL MESSAGE 1128
(GNLOC) A LOCATION PARAMETER HAS AN INCORRECT TYPE AND/OR LENGTH." (IBM MVS/XA
Version 66+ only)
Avoidance: The avoidance requires two restarts. In the first restart,
specify RESTART VERS=1 KEEP. This
first restart will fail with the aforementioned fatal message, but subsequent
restarts will execute successfully.
3762
67.5
Superelements - SEP1 - Poor Message
In any superelement solution sequence (SOLs 60-200), if the model contains

scalar points (SPOINT) without any
physical grid (GRID) points, then the run will fail and issue the DMAP fatal
message "UFM - NO GRID POINTS DEFINED
FOR SEP1".
Avoidance: Either add a dummy grid point or use a non-superelement
solution sequence (SOLs 1-31, 47, 48).
Another avoidance is to apply the following DMAP alter to the appropriate
solution.
$
$ alter for structured solutions
$
compile phase0 souin=mscsou noref nolist
alter 30,30 $
type parm,,i,n,nose=-1 $
$
$ alter for unstructured solutions
sol xx $ where xx is any sol 60 thru 99
compile solxx souin=mscsou noref nolist
$
alter yyy,yyy $ statement number of SEP1 module
$
for SOL 61 yyy=290
3763
67.5
CF,YES - Wrong Answers
Single and Multipoint Constrai - PARAM,MP
If "PARAM,MPCF,YES" is used in Version 67 and there are upstream

superelements in the model, then the
constraint forces for the rigid elements will be incorrect. (Version 67 only)
Avoidance: Insert the following DMAP alters:
COMPILE SEDRCVR SOUIN=MSCSOU NOREF $ V67
ALTER 53,53$ BEFORE SDR2
TYPE DB KGG $ FIX ERROR (?) ON MPCF
MPYAD KGG,UGVS,PQ/QGM///-1 $ FIX ERROR. REPLACE KJJ WITH KGG
3764
002
69
Documentation - IFP,PGAP - SFM 316, UFM 9
If the value for Kt is larger than Ka on the PGAP entry or if MU1/MU2 is

greater than 1.0, then the run will fail and issue the message SFM 316, UFM
9002. These limits are not documented and may not be necessary.
Avoidance: Make certain that the Kt value is smaller than the Ka value and
that MU1/MU2 is less than 1.0.
3765
70.6
/LSEQ - Missing Output
Optimization/Design Sensitivity - LOADSET
The sensitivities of dynamic responses may not be computed for some subcases if
the following conditions occur:
1. Loads are defined via the LOADSET Case Control command and LSEQ Bulk
Data entry.
2. There are fewer LOADSET/LSEQ load vectors (DAREA sets) than subcases.
Avoidance: Ensure that each subcase with a LOADSET command references a
LSEQ-DAREA load vector combination.
3768
's Manual
68
Documentation - PSOLID - MSC/NASTRAN User
The table contained in remark 8 PSOLID entry description in the

MSC/NASTRAN User's Manual Version 67 contains incorrect information for the IN
data field. This error has been corrected in the Version 67 Quick Reference
Guide. Subsequent documentation is to be appropriately updated. (Version 67
only)
Avoidance: The corrections to the table are as follows:
HEXA
Integration
IN
8 Node 3x3x3 Reduced Shear Only
THREE or 3
3x3x3 Standard Isoparametric
PENTA
Integration
IN
6 Node 3x7 Reduced Shear Only
THREE or 3
3x7 Standard Isoparametric
TETRA
Integration
IN
4 Node 5-Point Standard Isoparametric THREE or 3
3769
70.5
AGE 9050 (SEKRRS)
Elements - CRAC3D, MAT9 - DMAP FATAL MESS
If the symmetric option is used for the CRAC3D element and the boundary
condition is defined at the symmetric plane, then the job may fail and issue
the message "DMAP FATAL MESSAGE 9050 (SEKRRS) - RUN TERMINATED DUE TO EXCESSIVE
PIVOT RATIOS".
Avoidance: Do not use the symmetric option with anisotropic material
properties.
3770
68
ted Database, SFM 4276 EC 7777
Superelements - DBLOCATE, CSUPER - Corrup
If a CSUPER entry references a non-existant GRID entry, then the correct

UFM 4188 will be correctly issued. However, the database is not properly closed
and this can lead to to various problems with DBLOCATE.
3771
67.5
Documentation - GPFDR, GNFM - UWM 2354
When a user DMAP is used in the nonlinear solutions, UWM 2354 may occur if
the GPFDR module is used in the
DMAP. If this warning message occurs, the execution of the GPFDR module will
be terminated, but the run will
continue. The cause of the problem occurs in the GNFM module, which (on shortword machines) will overwrite the
element ID in the output element dictionary when one of the input element
dictionaries is purged. This error can
only occur for elements with an odd number of words (TRIA3 and PENTA) in the
KDICT data block; however, the user
should be aware that grid point force data recovery is not available in the
nonlinear solution sequences because
the results for nonlinear elements will be based on an incorrect stiffness
matrix. This error will be considered
c
3772
GL
Restarts - CORD2 - Inefficient Restart
If a CORD2i entry is added or changed on restart, then all the upstream

superelement will be reprocessed. This is a general limitation. While it is
relatively simple to keep track of the superelement dependencies for the CORD1
entries since the entry is associated with only one superelement. Keeping
track of which superelements reference a CORD2 entry is more difficult.
Avoidance: Use a CORD1 entry.
3773
67.5
GIC ERROR IN NAGAPD: DELU=0
Geometric Nonlinear Analysis - PGAP - LO
In the new GAP element introduced in MSC/NASTRAN Version 67, when the U0
and F0 fields have a negative value on the PGAP Bulk Data entry, then the fatal
message "LOGIC ERROR IN NAGAPD: DELU=0" may be issued. (Version 67 only)
Avoidance: There is no need to use F0 in order to create a preload in a
closed GAP. If a nonzero force is specified to F0, then the solution is either
erroneous or difficult to interpret. A negative U0 is all that is required to
create an initial compression and the physical interpretation is clear when F0
is zero. This error will be corrected by rejecting negative values for F0 in
IFP.
3774
68
DMAP - - UFM 227 UNMATCHED SINGLE QUOTE
If a DMAP statement is followed by a "$" sign to denote a comment, and the

comment contains an unmatched
single tick, then the job will fail with the following error message:
UFM 227 UNMATCHED SINGLE QUOTE "'" DETECTED IN SUBDMAP
Avoidance: Remove the offending single quote "'" from the comment.
3775
67.5
Nonlinear Analysis - ASET - UWM 4698
A DMAP error in SOL 106 may result in improper processing of models with ASET
entries. If ASET entries are
defined and singularities exist in the KOOL matrix, then UWM 4698 will be
correctly issued from the DECOMP module identifying the singular degrees.
However rather than terminate, processing will continue until a machine
overflow stops execution or poor answers result. If the model does not contain
singularities in the KOOL matrix, then the execution will stop and no message
will be printed.
Avoidance: The DMAP correction is as follows.
COMPILE NLSTATIC, SOUIN=MSCSOU
ALTER 107,107
IF ( SINGL<0 ) CALL ERRPH2 //SUBDMAP/0 $
3776
67.5
- Wrong Answers
Transient Response Analysis - PARAM,INRLM
"PARAM,INRLM,-1" is ignored in Solution 112. Thus, inertia relief mode shapes

will not be appended to the generalized dynamic modes.
Avoidance: Use Solution 72 or insert the following DMAP Alters for Solution
112.
COMPILE PHASE1DR SOUIN=MSCSOU NOLIST NOREF
ALTER 44 $
INRLM = INRLM $
3777
67.5
Elements - PSOLID - Poor Message
If the CORDM field on the PSOLID entry references an undefined coordinate

system, then the job should fail and issue the message "USER FATAL MESSAGE
2025, UNDEFINED COORDINATE SYSTEM x". However, on the IBM RS/6000 and possibly
other machines, the job will fail and issue the following unclear messages in
the LOG file. There is no messages in the f06 file. (IBM RS/6000 only)
Trap encountered, Traceback:Offset
Offset
1ef0 in procedure ehexd_
Offset
b1c in procedure emgpro_
Offset
1b0 in procedure emg_
Offset
14c in procedure xsem09_
Offset
150 in procedure mainal
Offset
0 in procedure start
98 in procedure transd_
--- End of call chain --Avoidance: Make sure that the CORDM field on the PSOLID entry references
3779
70
sing Documentation, Wrong Answers
Case Control - DLOAD, LOADSET, SPC, - Mis
Limitations regarding the LOADSET, SPC, DLOAD, and MPC Case Control commands
are not properly documented under the appropriate MSC/NASTRAN Quick Reference
Guide description and if these limitations are not followed carefully by the
user then appropriate warning messages will not be issued and unexpected
answers will result.
Avoidance: The following remarks should be added to the MSC/NASTRAN Quick
Reference Guide descriptions of the following Case Control commands:
DLOAD: The DLOAD command will be ignored if specified for upstream
superelements in dynamic analysis. To apply loads to upstream superelements,
please see the LOADSET command.
LOADSET: Only one LOADSET ID may be specified per superelement (including the
residual). If more than one set ID is specified,
3780
ong Answers
68
Miscellaneous - MATMOD, DMIG, MTRXIN - Wr
If a rectangular matrix is written to DMIG entries using MATMOD option 16, the
NCOL header record will be
blank. This error may cause the MTRXIN module to misread the DMIG entries, and
this may result in wrong answers. Fatal messages are sometimes issued. If
NCOL is blank, the MTRXIN module assumes that the matrix has as many columns as
there are DMIG entries. Blank columns are ignored.
Avoidance: Add the NCOL value on the header entry manually.
3781
67.5
TER, MAT9 - Wrong Answers
Material Nonlinear Analysis - CREEP, NLI
The formulation for creep is based on isotropic materials. If anisotropic

material properties are used, then approximations exist in the material tangent
matrix and stresses. The error in the stresses accumulates with each time
step. Thus, creep with anisotropic material properties, may cause
instabilities as the number of time steps increase. This error was considered
fixed in MSC/NASTRAN Version 67.5 by issuing the message "USER FATAL MESSAGE
6359 (PREMAT) MAT2 OR MAT9 ENTRY IS COMBINED WITH A CREEP ENTRY" if anisotropic
materials are combined in a creep analysis. In Version 68 this message was
changed to a warning allowing the user to perform the analysis and judge for
themselves the accuracy of the solution.
Avoidance: Other than not using anisotropic material with creep,
3782
2004
DMAP - TYPE - UFM 404
In a TYPE DMAP statement, if the default value of a real or complex parameter

is specified to be a letter,
then the job will fail with the following misleading error message:
0*** USER FATAL MESSAGE 404 (CTYPE)
136
A NON-SINGLE QUOTE DELIMITER WAS DETECTED WHERE A SINGLE QUOTE
DELIMITER IS REQUIRED
The most common form of this error, which is difficult to detect, occurs when
the letter "O" has been incorrectly
substituted for the numeric "0".
Avoidance: The message will correctly identify the line in error.
Correct the offending character.
3783
9002
67.5
Miscellaneous - IFP - DMAP FATAL MESSAGE
If there is illegal data in any field of the PGAP entry and a continuation
entry is explicitly defined (even
if all the fields on the continuation entry are left blank), then the job will
fail with the following DMAP error
message:
DMAP FATAL MESSAGE 9002 (PREFSE) - ERROR ENCOUNTERED IN MODULE IFP
The IFP fatal messages UFM 316 or 313 which should identify the specific entry
in error will not be issued.

Avoidance: If this error is encountered, review the data on the PGAP
entries or remove all the continuation
entries from the PGAP entries and resubmit them to identify the incorrect
entries.
3784
67.5
DBC/TRANS/ACCESS - DBC, SORT2 - SWM 6065
SORT2 output is not supported for static solutions in DBC. If this output
option is requested in the job,
then the proper results are printed in the MSC/NASTRAN output file. However,
the following error message will be issued and the .XDB will not contain the
appropriate postprocessing information.
*** DBCMSG ERROR MESSAGE 24 FROM SUBROUTINE GRIDBK
SORT-2 STATIC LONGSOLUTION RECOVERY IS NOT SUPPORTED
0*** SYSTEM WARNING MESSAGE 6065 (DBC)
Avoidance: Insert the following DMAP:
$ - FOR SOL 61 COMPILE SOL61 SOUIN=MSCSOU NOLIST NOREF
$ alter for Version 67
alter 879,880
DBC
OPG1,OUGV1,OEF1X,OES1X,OQG1,,,,,,,,,,,,,,,//
'OPG'/'OUG'/'OEF'/'OES'/'OQG'////////////////
-1/DBCPATH/S,N,CP/APP1
/
/V,Y,GEOMU/V,Y,LOADU/
3785
67.5
Heat Transfer - VIEW - Missing Output
If the VIEW module is used along with "PARAM,PRTPCH,x" where "x" is not
the default value, then the view
factors will not be calculated.
Avoidance: Use the default value of x=0 for "PARAM,PRTPCH,x"
3786
67.5
CFAILURE - Wrong Answers
Optimization/Design Sensitivi - DRESP1,
If a CFAILURE response is requested on a DRESP1 entry and the

corresponding PCOMP and/or MATi entries do not
contain all the information required for the calculation of the failure theory,
then unpredictable results can
occur including wrong answers. This error is related to Error 3449.
Avoidance: Make certain that the associated PCOMP and MATi entries
contain all the information necessary for
the calculation of failure indices.
3787
DU - SFM 4276
69
Frequency Response Analysis - K2PP, MATRE
In SOL 30, if SUBCASEs are defined that reference different K2PP and/or
TFL entries, then the run will fail
with the message SFM 4276 in the MATREDU module.
Avoidance: Run each SUBCASE independently, preferably using SOL 111 with
restarts.
3788
67.5
ing Displacement Output
DBC/TRANS/ACCESS - PARAM,POST, DBC - Miss
If a user requests a large number of eigenvectors in SORT1 format, then

there may be missing displacement data in the graphics database. A symptom of
this error is that grids that have non-zero displacements will appear fixed
during animation of in deformed plots.
Avoidance: Perform a RESTART and request data recovery on a smaller set
or request SORT2 format. Running the database through TRANS/RECEIVE will also
correct the problem.
3790
ct Labels
67.5
Dynamic Response - DRMS2, QUADR - Incorre
If the DRMS2 module is used to perform dynamic data recovery, incorrect

grid IDs and fiber distances will be printed for QUADR elements.
Avoidance: Other than using the DDRMM module, no avoidance exists.
3792
ror Message
67
Aeroelastic Analysis - APD - Incorrect Er
If there is more than one SET1 entry defined in the input and one of the
entries references a grid point that
does not exist, the error message will always reference the first SET1 ID.
Avoidance: Review all the SET1 entries to determine the one in error.
3793
ge
67
Aeroelastic Analysis - MKAERO2 - No Messa
The MSC/NASTRAN User's Manual indicates that the Mach number data on the
MKAERO1 and MKAERO2 Bulk Data entries
must be greater than or equal to zero. However, MSC/NASTRAN does not enforce
this requirement in IFP. Thus, this
user error will not show up until significant CPU time has been expended.
Avoidance: Input a positive value for the Mach number.
3794
M 727
67.5
Miscellaneous - Dynamic File Allocat - UW
If no space is requested for a logical name, then the message "UWM 727 NO SPACE WAS REQUESTED FOR LOGICAL
NAME XXX, A DEFAULT VALUE OF YYY IS USED" will be issued. This is true for all
machines except for the IBM MVS/XA.
For this particular machine, the value is either taken from the ASSIGN
statement, the default set in the delivered
JCL procedure, or the user JCL assignment. The NASTRAN default value is
ignored.
Avoidance: The user must specifically assign the desired disk space by
either using the ASSIGN statement or
JCL.
3795
)
70
Documentation - COMPILE - UFM 709 (PRCMPL
"UFM 709 (PRCMPL)" is issued while trying to COMPILE a user DMAP with
SOUIN=USRSOU if the previous run did not
compile an NDDL, or ACQUIRE and NDDL.
Avoidance: When creating a database, use the acquire NDDL FMS statement
or SOL xxx, NOEXE to attach the data
paths.
3798
68
E, OMIT, ASET - Wrong Answers
Optimization/Design Sensitivity - MPC, RB
If a model contains MPCs, RBEs, or contains an O-set and is using the

multi-master technique, then SOL 200
will produce incorrect answers.
Avoidance: Apply the following alter or do not use the multi-master technique.
COMPILE SEMFREQ,NOLIST,NOREF,SOUIN=MSCSOU
ALTER 56,56
ALTER 73
IF (NOT NOPH2) THEN
ENDALTER
3799
ct Data
67.5
DBC/TRANS/ACCESS - DBC, ACCESS - Incorre
The "vector key" data for the strain energy data block written to the graphics
database is incorrect. This causes crashes in MSC/TRANS receiver for versions
6 and 7.
Avoidance: MSC/XL does not use this information. Thus, the error will only
cause a problem if a user routine
attempts to read and process the information with MSC/ACCESS.
3800
67.5
Miscellaneous - DBDIR - SFM 4275 EC 304
A large job that results in the expansion of the database directory,

DBDIR, may cause a data block to be
overwritten which will result in the job failing and issuing the message "SFM
4275 IONAST EC 304 BLOCK NUMBER CHECK
CONDITION".
3801
olution
Nonlinear Analysis - NLPCI - Solution Regressed to Previous S
If an ARC LENGTH method is used in a nonlinear analysis and the unloading is

performed in more than one
subcase, then the job will terminate in the second subcase and the following
error message will be printed: "SOLUTION REGRESSED TO PREVIOUS SOLUTION"
Avoidance: Define the unloading in a single subcase.
3802
67.5
DMAP - Expressions and Oper - UFM 234
If both the real and imaginary parts of a complex, single-precision

constant are equal to a number that
contains 10 or more characters including signs, decimal points, and
leading/trailing blanks, then the job will fail
and issue the message "USER FATAL MESSAGE 234".
Avoidance: Make certain that each component of the complex number is less
than 10 characters.
3803
68
correct CPU Reporting
Miscellaneous - Unix Accounting Scri - In
Script modifications supplied with Version 67 for performing accounting

may not record the correct time for long running job. This is most likely to
occur if the run exceeds 99,999 cpu seconds.
Avoidance: Replace the following lines in the nast67 script
echo
echo
echo
echo
echo
echo
echo
echo
"if [ -f ${out}.f04 ] ; then"

"{"
"echo -n `date` "User:"${log_name} "PID:"${out}"
"awk ' BEGIN { cpu = 0 }"
'
/~ ..:..:../ { if ( cpu < $5 ) {cpu = $5} } '
'
END { print " MSC/NASTRAN CPU USAGE: "cpu }' "' ${out}.f04"
"} >> ${MSC_BASE}/nastact"
"fi"
with:
echo
echo
echo
echo
echo
3804
"if [ -f ${out}.f04 ] ; then"

"{"
"echo -n `date` "User:"${log_name} "PID:"${out}"
"grep -v '#' ${out}.f04 | awk ' BEGIN { cpu = 0 }"
'
67.5
Nonlinear Analysis - GAP - Wrong Answers
If a GAP element connects two non-coincidental points, then the SLIP-V

values may be wrong. The amount of
error is proportional to the physical distance between the two grids.
Avoidance: Make certain that the distance between the two grids is small.
In general, as long as the
distance between the two grids is smaller than several orders of magnitude when
compared to the overall dimension
of the structure, the error should be negligible.
3805
2001
Alters - Wrong Answers
Documentation - DMAP Dictionary, SubDMAP
If an alter to a subDMAP introduces a datablock that uses the name of a data

block that already was defined in another subDMAP, then the outcome of the
result is unpredictable. In most instances, nothing detrimental will occur.
However, in some instances, the module that attempts to output a datablock with
this name may produce no output without any warning messages which could
possibly lead to wrong answers. The association of the CALL and subDMAP
argument lists are described under remark 5b of the CALL DMAP statement
description in Section 5.4 of the MSC/NASTRAN User's Manual.
Avoidance: If a new data block is introduced to a subDMAP, inspect the data
block cross reference to ensure that there are no conflicts with existing data
blocks.
3806
67.5
Nonlinear Analysis - GAP - Wrong Answers
In Version 67 of MSC/NASTRAN If the Kb value of the GAP element is set to zero

and the initial status of the GAP is open, then the GAP element will be
ignored.
Avoidance: This is a user error. The MSC/NASTRAN User's Manual states that Kb
should be set to a value greater than 0.
3807
67.5
DMAP - Expressions and Oper - UFM 207
If either component of a complex number is input with a decimal point

immediately following the sign, then the
job will fail with UFM 207.
Avoidance: Enter a zero between the "sign" and the decimal point.
3808
UFM 1126
67.5
Cyclic Symmetry Analysis - DYNRED, ADD5 -
In MSC/NASTRAN Version 67, if Generalized Dynamic Reduction is used in a

SOLution 115 run along with any
output request (e.g., displacement), then the job will fail and the following
error message will be issued:
0*** USER
DMAP
NAME
USER
FATAL MESSAGE 1126 (GNFIST)

MODULE ADD5
IS ATTEMPTING TO OUTPUT DATABLOCK
201
= GOA, WHICH ALREADY EXISTS.
ACTION: DELETE THE DATABLOCK, OR USE FILE GOA
=OVRWRT
Avoidance: Insert the following DMAP alter avoidance:

COMPILE SEGOA SOUIN=MSCSOU NOLIST NOREF
ALTER 2
FILE GOA=OVRWRT $
ENDALTER
3809
ct JCL Cards
67
Miscellaneous - MSC/OPTIONS - IBM,Incorre
The JCL provided with the MSC/OPTIONS Version 3 for the IBM MVS/XA is
incorrect. The override for
ALLOCATE.ALL does not specify a unit.
3810
68.2
SOL47, CURV - Excessive CPU
Static Analysis - PARAM,NINTPTS, RF24D40,
PARAM,NINTPTS controls the number of elements used to interpolate grid

point stress and/or strain data
calculated in the CURV module. The default for this parameter is 10 except in
RF24D40 and SOL 47. The default value of 0 in will result in interpolation
over all elements which may result in excessive CPU.
Avoidance: The MSC/NASTRAN Reference Manual documentation for RFalter
RF24D40 warns the user that the default value of this parameter should not be
used. However, to remove the burden from the user, the default value of the
parameter in this RF alter and SOL 47 should be set to 10 in future systems.
3811
t
68
DBC/TRANS/ACCESS - DBC, SPOINT - No Outpu
If a model is defined exclusively of scalar points (SPOINT) without grid

points, no usable DBC file is
produced.
Avoidance: Add a token grid point to the model.
3812
s
67.5
Virtual Mass - MFLUID, GDR - Wrong Answer
An DMAP error in the structured solution sequences will result in wrong

answers whenever generalized dynamic reduction is used on a model which has
virtual mass defined.
Avoidance: Use LANCZOS, an unstructured solution sequence or apply the
following alter:
COMPILE SEMRM SOUIN=MSCSOU NOREF NOLIST
ALTER 56 $ FOR V67, FOR VERSION 66 ALTER 52
CALL SEGOA GOAT/GOA/NOOSET/NOQSET/NOTSET $
ENDALTER $
3813
a Data Blocks
67.5
File Management Section - DBLOCATE - Extr
If a DBLOCATE statement contains a WHERE clause of the form: WHERE(SEID=*

AND VERSION=1), then all data
blocks in VERSION=1 including data blocks which do not have seid as part of
their path will be located.
Avoidance: Change the WHERE clause that contains the "*" for the SEID
qualifier to:
WHERE(SEID>0 AND VERSION=1)
3814
70
Elements - SDR2, CELASi - Poor Answers
Element force data recovery for the CELAS elements is calculated in single
precision. On short-word machines (i.e., all machines except CRAY, CDC, and
NEC), the lack of precision may result in poor answers for the CELAS element
force results in models that have a maximum factor to diagonal ratio that is
greater than 1.E+4.
Avoidance: The CELAS data recovery performed in the GPFDR module for grid
point force output (GPFORCE) is
performed in double precision. Note that in the model where this behavior was
observed, CELAS elements were
effectively used as a rigid link. To avoid numerical conditioning problems,
this modeling practice should be
avoided. A structure that is effectively rigid with respect to the surrounding
structure should be modeled with rigid elements. RF alter RF2
3815
ong Answers
67.5
Heat Transfer - RF61D01, PARAM,HEATS - Wr
If no load is defined in the Bulk Data of a static heat transfer analysis

followed by a static analysis, wrong answers will occur for the static analysis
subcase. This error is related to Error 3483.
Avoidance: Include a dummy TEMPD or FORCE input record. It does not need
to be referenced.
3817
GL
If FBS method 2 is executed with insufficient scratch space, then the job
will fail and issue the message
"BIOMSG: ERROR 3002 HAS OCCURRED IN ROUTINE FREAD" followed by "SYSTEM FATAL
MESSAGE 4276.FREAD ERROR CODE 3002".
Avoidance: Increase the scratch space by increasing the BUFFSIZE or by
including an appropriate INIT
statement. FBS method 2 requires more scratch space than method 1. Thus,
forcing either FBS method 1 or 1A by
setting the FBSOPT keyword on the NASTRAN statement to either -1 or -2,
respectively, may also avoid the problem.
3818
67.5
Superelements - GPFDR - UFM 6219
On Version 67 of MSC/NASTRAN a large problem with thermal loads using the

the multi-master method failed in the GPFDR module when grid point force
balance data recover (GPFORCE) was requested. The job issued the message
"SYSTEM FATAL MESSAGE 6219 (GPFDR2), BISLOC FAIL, PERHAPS THE DATA IS NOT
SORTED".
Avoidance: MSC is attempting to locate the cause of the problem. At this
time there is no known avoidance.
3823
70
Documentation - IFP - UFM 316 (IFPDRV)
In Version 67 of MSC/NASTRAN if a Bulk Data entry is input using the wide field
format and the continuation entry is not explicitly specified, the job may fail
and issue the message "USER FATAL MESSAGE 316 (IFPDRV) ILLEGAL DATA ON BULK
DATA CARD" followed by the message "DMAP FATAL MESSAGE 9002 (IFPL)". Prior
versions of MSC/NASTRAN may have allowed this input. The current action is
necessary to ensure correct processing of continuation entries. A note will be
added to Section 2.4.1 of the MSC/NASTRAN User's Manual clarifying this
requirement.
Avoidance: Explicitly specify the continuation entry even when defaults are
desired for all fields.
3824
67.5
MP - Poor Default
Transient Nonlinear Analysis - PARAM,NDA
The parameter NDAMP was implemented in Version 67 for nonlinear transient

analysis to stabilize the
integration scheme for adaptive time stepping using one-step direct time
integration. The default value was set to
.025 in Version 67 based on limited test cases. Subsequent use of this feature
has revealed that the value .025
causes excessive damping in some cases.

Avoidance: A value of .01 is suggested and the default value will be
changed in Version 67.5 and later
systems.
3826
68
W - Wrong Answers
File Management Section - DBLOCATE, DBVIE
Datablocks may be deleted incorrectly when using DBLOCATEs into the

current database (that is, locating from a previous version of the same
database you are running in) if a DBVIEW statement in the DMAP also references
the same datablocks. The error occurs because DBLOCATE does not correctly
update DBDIR(20) to reflect an equivalence between the versions.
Avoidance: Use DBVIEW in place of DBLOCATE.
3827
68
458, SFM 4276 EC 7777
File Management Section - DBLOCATE - SFM
If the user attempts to locate a database and incorrectly points to the

DBALL instead of the MASTER dbset, then the run will fail and either the
message SFM 458 or SFM 4276 EC 7777 will be output. In either case the message
will not give any indication of the error.
Avoidance: The DBLOCATE must point to the MASTER dbset.
3828
114
68
Limitation on Problem Size - NDDL - SFM 1
The number of individually qualified datablocks that

can be stored under a single NDDL name was set to 1000
datablocks in Version 66 of MSC/NASTRAN. An attempt was
made to remove this limit in Version 67 but a routine was
missed. This limitation is most likely to be encountered
in a nonlinear analysis that is encountering difficulties
converging.
Avoidance: Apply the appropriate DMAP avoidance
dependent on the Version of MSC/NASTRAN being used. Note
that the alter for Version 67 does not work on the CRAY
MSC/NASTRAN Version 67 system; however, the alter will work
on the CRAY 67R2 release.
$ FOR VERSION 67
COMPILE NLSTATIC SOUIN=MSCSOU
ALTER 2,2
TYPE DB KJJ,MJJ,BJJ,USET,GOAT,KAA,DYNAMICS,KGG,AGG,
GPLS,SILS,SLT,DM,CASES,EQEXINS,
3829
69
Case Control - TEMP - Poor Documentation
Remark 7. under the MSC/NASTRAN User's Manual description of the TEMP

Case Control command does not clearly define the precedence of the TEMP(INIT)
and TEMP(MATERIAL) Case Control specifications versus the TREF specification on
the MATi bulk data entry. Furthermore, the statement that
"TEMPERATURE(MATERIAL) is provided only for upward compatibility with Version
65" is misleading.
Avoidance: The documentation should indicate the following:
1. Specification of TEMP(MATERIAL) and TEMP(INIT) will result in UFM 631

followed by DMAP FATAL MESSAGE 9002.
2. If TREF is specified in conjunction with TEMP(MATERIAL), then TREF
will be used for the initial
temperature for load calculations and TEMP(MATERIAL) will be used for the
material temperature dependence.
3.
3830
9032
69
Superelements - PARAM,BAILOUT - UFM 9050,
The user can not force the program to continue processing a superelement
that contains a pure singularity by setting PARAM,BAILOUT. PARAM, BAILOUT does
not work with pure singularities. If PARAM,BAILOUT,-1 is set, the DMAP FATAL
MESSAGE 9032 that indicates that processing of a superelement will continue
despite near singularities will be incorrectly output when a pure singularity
exists.
This was fixed in Version 67.5 but is not fixed in Version 68.
Avoidance: Ignore the DMAP FATAL MESSAGE 9032. Correct the singularities
and perform a restart.
3831
68
, SFM 4276 EC 7777
Acoustic Analysis - DISP - Missing Output
If fluid and structural GRID points are combined in a SET that is referenced by
the DISP Case Control command, then the complex displacement output results
will only contain the fluid points, and the structural points will be ignored.
Some systems such as the VAX VMS may fail and SFM 4276 ERROR CODE 7777 may be
output.
Avoidance: Set DISP=ALL or perform a restart and define a SET that contains
only the missing structural grid points.
3832
70.7
DMAP - ECHOOFF, ECHOON - UFM 13
The ECHOOFF and ECHOON commands may be used in DMAP alters of existing
solutions. However, when used within a complete user written subDMAP "UFM 13
ERROR IN DMAP INSTRUCTION" followed by SYSTEM INFORMATION MESSAGE 480 was
encountered.
Avoidance: Other than removing the offending commands there is no avoidance.
3833
67
K6ROT - Wrong Answers
When
of a flat
loadings,
incorrect
Nonlinear Analysis - QUAD4, TRIA3, PARAM,
using a nonlinear solution to perform a large displacement analysis

plate with pressure
it is possible that the solution may diverge, or may converge to an
but reasonable solution.
Avoidance: Use PARAM, K6ROT to add in-plane rotational stiffness to the

TRIA3 and QUAD4 elements. The
recommended value for PARAM,K6ROT is model and unit dependent, but a value of
1.E2 to 1.E4 is appropriate for most cases. In Version 67, a default value of
1.E2 has been implemented in the nonlinear solutions to correct this problem.
3834
68
PPC,MODES - Missing Output
Optimization/Design Sensitivity - PARAM,A
In MSC/NASTRAN Version 67 sensitivities can be calculated for the upstream

superelements, however,
optimization can only be performed on the residual structure. If the model
defines a response in an upstream superelement while attempting eigenvalue
optimization of the residual structure within the same run, an error in the
program logic will assume that since a response has been defined for an
upstream superelement that the run is intended to calculate sensitivities only.
Thus, no optimization will be performed and since PARAM,OPTEXIT is not set to
4 calculated sensitivities will not be output.
Avoidance: Add the following ALTER to superelement model that calculate
eigenvalue responses:
COMPILE DESOPT,NOLIST,NOREF,SOUIN=MSCSOU
ALTER 155
DMRESD= -1 $
ENDALTER
3835
68
correct Elapsed Time
Miscellaneous - SYSTEM(34), SYSTEM(3 - In
The definition of SYSTEM(34) and SYSTEM(36) has been changed in

MSC/NASTRAN Version 66 and later systems.
Prior to Version 66 these SYSTEM cells were used for various machine dependent
control on IBM, CRAY COS, UNIVAC and CDC. Beginning with Version 66, if
SYSTEM(34) or SYSTEM(36) is changed during a run, then the CPU and wall-clock
time reported in the F04 Execution Summary will be incorrect. In addition, the
program actions based on the CPU time may also be affected. This behavior will
occur on all platforms, however, it is most likely to occur on older decks
migrated from the above mentioned systems.
Avoidance: The only Version 66 systems that reference these system cells
are the CRAY COS EMA and NOEMA
releases. The CRAY COS MSC/NASTRAN Version 66 Application Manual
3836
- SFM 4390
68
Dynamic Response Analysis - LOADSET, SSG1
If a LOADSET command references a nonexistent LSEQ entry, then UFM 4390

will be appropriately issued, however, the run will continue until SSG1 fails
and issues the message SYSTEM FATAL MESSAGE 3001, ATTEMPT TO OPEN DATA SET
WHICH WAS NOT DEFINED IN THE FIST.
Avoidance: Reference an LSEQ entry that exists.
3837
67.5
ge, SFM 4276 EC 1044
DMAP - COMPILE, DO WHILE, E - Poor Messa
If a DMAP contains more DO WHILE statements than ENDDO statements the

compile will fail and issue SFM 4276 EC
1044.
Avoidance: The only avoidance is to correct the DMAP to have an equal
number of DO WHILE and ENDDO
statements.
3838
69
ng Punch Output
Composites - PCOMP, STRESS(PUNCH) - Missi
A STRESS(PUNCH) request in solutions 101, 103, 61, 63 or 24 (where SOL 24
requires RF24D79) for composite

elements will produce no PUNCH output.
Avoidance: A DMAP avoidance to PUNCH stress output is given below for v68.2.
There is no way to PUNCH the failure indicies.
COMPILE DMAP=SEDRCVR, SOUIN=MSCSOU, NOLIST, NOREF
ALTER 185 $ FOR V66A
ALTER 209 FOR V67.5
$ table print the composite failure indicies
TABPT OEFIT// $
$ PUNCH THE COMPOSITE STRESS DATA RECOVERY
OFP OES1C//S,N,CARDNO/4 $
For Version 68.2:
$ table print the composite failure indicies
TABPT OEFIT// $
$ PUNCH THE COMPOSITE STRESS DATA RECOVERY
ALTER 235 $ VERSION 68.2
OFP OES1C,,,,//S,N,CARDNO/4 $
3839
68
DMAP - COMPILE - UWM 141, UFM 146
A run that COMPILEs a single subDMAP for SOL 60-99 may fail and issue the
messages "USER WARNING MESSAGE 141 (LINKND) NDDL 'PARAMETER' DEFINITION TABLE
NOT FOUND" followed by "USER FATAL MESSAGE 146".
Avoidance: Include the statement ACQUIRE NDDLOLD in the FMS Section of
the deck.
3840
Wrong Answers
67.5
Grid Point Force - GPFORCE, BEAM, TEMP -
In MSC/NASTRAN Version 67, the grid point force balance will be incorrect
for BEAM elements with thermal
loads.
Avoidance: Use a BAR element.
3841
2001
Miscellaneous - ESE - Incorrect Labels
If ESE output is requested in any modal solution and the case control has a
SUBCASE ID that is greater than 1, then the element strain energy output
associated with the first eigenvalue of SUBCASE will be labeled with the
SUBCASE ID and subsequent eigenvalues will be incremented by 1. To be
consistent with other element output the label for element strain energy output
should contain the mode number and eigenvalue. The SPCFORCE RESULTANT, MAXIMUM
SPCFORCES, and MAXIMUM DISPLACEMENTS are similarly mislabeled.
Avoidance: An avoidance for non-superelement runs is to remove the SUBCASE
entry or change the ID to 1.
Please see related error 3560.
3842
67.5
Security - GENTIM, COMTIM - UFM 3060
The GENTIM and COMTIM jobs that are required to install timing constants
require that the authorization for the DMAP option be activated. If the client
does not have the DMAP option these runs will fail and will issue the message
"UFM 3060 OPTION DMAP NOT IN APPROVED LIST".
Avoidance: The only avoidance is to obtain an authorization code that

allows temporary access to the DMAP
option. This error will be corrected in Version 67.5 by delivering two new
solution sequences that perform the job of GENTIM and COMTIM.
3843
tput
70.5
Acoustic Analysis - METHOD(FLUID) - No ou
In the residual structure case control, the METHOD(FLUID) and METHOD(STRUCTURE)

commands are used to
calculate uncoupled modes of the fluid and structure respectively. If an
upstream superelement consists of only fluid elements, then use of
METHOD(FLUID) will result in no eigenvalue output for the superelement.
Avoidance: Instead of requesting METHOD(FLUID) in the Case Control for the
superelement request METHOD only.
3844
6143
2001
Dynamic Response Analysis - METHOD - UFM
If the METHOD command is missing from the residual structure subcase in any
modal response structured solution for a model with superelements, then the run
will fail and issue the message "USER FATAL MESSAGE 6143, (MERGE1) INPUT
MATRICES AND VECTORS ARE INCOMPATIBLE."
Avoidance: Include a METHOD request in the residual subcase.
3845
68
DMAP - VECPLOT - SFM 4276 E.C. 7777
If the input value of the PLOTFORM parameter for the VECPLOT module is set to 3
and the input data for INVECT is purged, then the job may fail and issue the
message "SFM 4276 EC 7777". The User's Manual states that the INVECT may be
purged if PLOTFORM=4 or 6. The program should also allow INVECT to be purged
for PLOTFORM=3.
Avoidance: Generate a null matrix for INVECT.
3847
67.5
Such File or Directory
Miscellaneous - PUNCH, Shell Script - No
Line 273 of the nastran shell script for MSC/NASTRAN Version 67 on the
Cray Unicos is missing the '$'
character for the .pch file. As a result of this error, a standard Unix error
message indicating "No such file or directory" may be issued whenever a job is
submitted with old=no. Since any new punch output will overwrite the old punch
output and the desired action of old=no is to delete the old output, in most
cases this error will have no affect on a jobs outcome. (Cray Unicos V67 only)
Avoidance: The shell script can be corrected by adding a '$' character to
the command line just before
{out}.pch, e.g., ${out}.pch.
3848
ion
68
Elements - QUADR, TRIAR - Poor Documentat
The New Capabilities list description of the QUADR and TRIAR elements
indicates that the bending formulation for these elements are exactly the same
as the QUAD4 and TRIA3 respectively. The documentation did not clarify the
fact that the corner forces and stresses output for the QUADR and TRIAR due to
bending are the forces and stresses at the element's centroid. Only the
membrane forces and stresses are calculated at the corners.
3849
Answers
67.5
Response Spectra Analysis - OFREQ - Wrong
The OFREQ Case Control command and its associated SET may be used to
select the modes to be used in the
response spectrum analysis. This capability is broken in SOL 103.
Avoidance: If appropriate to the user's needs PARAM LMODES, LFREQ, or
HFREQ may be used to limit the modes
used in the analysis. Alternatively, the user may use SOL 63 or apply the
following alter to SOL 103:
COMPILE POSTREIG SOUIN=MSCSOU NOREF NOLIST
ALTER 25,25
TYPE DB PHA $
MODACC CASEDR,OLB,PHa,,,/OLB1,PHILS1,,,/'REIG' $
ALTER 59,59
CALL GMA CASEDR,MATPOOL,EQDYN,TFPOOL,,,,
MMAA,GOD,GMD,USETD,MKAA,BAA,K4DD,PHILS1,OLB1,DIT,,,,,/
,,MDD,K2DD,B2DD,MHH,BHH,KHH,PHIDH,/
LUSETD/'MODAL'/'TRANRESP'/NOUE/NOA/G/W3/W4/FALSE/
0/LMODES/LFREQ/HFREQ/1/1/FALSE/FALSE/FALSE $
3850
68
Aeroelastic Analysis - SDR1 - UFM 1126
If multiple flutter subcases are being processed and at least two of the
subcases have flutter eigenvector requests, then the job will fail and the
message "USER FATAL MESSAGE 1126 (GNFIST) DMAP MODULE SDR1 IS ATTEMPTING TO
OUTPUT DATABLOCK 201 NAME =FPHP, WHICH ALREADY EXISTS. USER ACTION: DELETE
THE DATABLOCK, OR USE FILE FPHP=OVRWRT" will be output.
Avoidance: One avoidance is to remove the eigenvector request. Flutter
Summary results will still be
printed. An alternative avoidance is to specify a unique CMETHOD request in
each flutter subcase. The PK and KE methods will ignore the request but the
eigenvectors will be deemed unique. (Version 67 only)
3851
M 227
67.5
DMAP - DO WHILE, ELSE IF, I - UFM 16, UF
If a DMAP DO WHILE, ELSE IF or IF THEN statement continues past one

continuation line, then the job will fail
and the message "USER FATAL MESSAGE 16, ERROR IN DMAP INSTRUCTION G" will be
issued followed by the message "USER
FATAL MESSAGE 227".
Avoidance: Split the statement into multiple statements. An alternate
avoidance is to use an assignment
statement to set lengthy expressions to a variable. The variable can then be
referenced in DMAP statement in
error.
3852
68
, MAT2 - Missing UFM 2113
Documentation - PBAR, PBEAM, PSHEAR, PROD
The MSC/NASTRAN User's Manual description for the PBAR, PBEAM, PROD, and PSHEAR
entry state that only a MAT1 entry may be referenced. However, beginning in
Version 67 if a MAT2 entry is referenced by any of these entries, then G11 and
G12 will be used to determine the isotropic material properties E and G used by
the element. All other fields on the MAT2 entry will be ignored. A PBAR
reference to a MAT2 entry in prior versions of MSC/NASTRAN resulted in UFM
2113.
3853
swers
67.5
Elements - HEXA, PSOLID, MATTi - Wrong An
When the HEXA element's material properties are defined to be temperature

dependent by referencing a MATTi
entry, the resulting corner stresses may be in error. The center stress and
Gauss stresses will be correct. This error only occurs for the eight noded
element with the default integration order specified on the PSOLID entry.
Avoidance: Remove the temperature dependency for the material properties.
3854
4669
69
Material Nonlinear Analysis - CLOAD - UFM
When the CLOAD entry is used to apply the upstream superelement loads to the
residual structure in a nonlinear analysis, the job will fail and will issue
the message "UFM 4669, "NO LOAD DATA EXISTS FOR VECTOR = ***".
Avoidance: In addition to the CLOAD request in the first residual subcase, a
dummy load request must be
included which references a LSEQ bulk data entry which in turn references the
same DAREA as the upstream loads. There must also be LSEQ and dummy load
requests included for unloaded superelements if data recovery on the unloaded
superelement is desired. This procedure is demonstrated under Error 2549 and
in an application note dated June 1990. This error is similar to Error 3041
which was corrected for the single residual subcase condition in Version 67.
3855
68
correct Documentation
Documentation - MSC/NASTRAN User's M - In
Section 3.5 of the MSC/NASTRAN User's Manual describes the RF Alter

Library and instructs users on how to
include a single as well as multiple RF Alters in the deck. This section
should warn the user that not all RF
Alters are compatible. Specifically, RF24D20 and RF24D32 can not be combined
in the same deck.
Avoidance: Use RF24D20 prior to RF24D32.
3856
69
Sequencer - SEQP - SEP1C LOGIC ERROR
If spill operations are performed during the resequencing of a model on an

IBM MVS/XA Version of MSC/NASTRAN, then the job may fail in the SEQP module and
the message "FATAL ERROR SEP1C LOGIC ERROR 19832" will be issued.
Avoidance: Increase the region size to avoid spill.
3857
Documentation
68
Documentation - SPARSE, OUTPUT4 - Missing
Currently the OUTPUT4 module can not output sparse decomposition factors. In
MSC/NASTRAN Version 68 "USER WARNING MESSAGE 6475 (OUTPT4)" will be issued to
inform the user that the sparse factor matrix is not supported in ASCII or
neutral format.
Avoidance: Use standard decomposition.
3867
69
- NO MASS MATRIX
Static Analysis - SUPORT, Inertia Relief
SOL 1 and 24 treats the presence of a SUPORTi entry as a request for inertia
relief. It then requires that a mass matrix be present.
Avoidance: The following SOL 24 ALTER allows a SUPORTi entry without a mass
matrix.
compile
ALTER
ALTER
EQUIV
COND
3869
Names
sol24 souin=mscsou noref nolist

137,137
151
PL,PLI/NOMGG/PO,POI/NOMGG $
LBL12,NOMGG $
69
Documentation - ACCESS - Wrong Data Block
Version 6 of the MSC/ACCESS User's Manual incorrectly documents the title of

the SESDPR and SESDTR data blocks as the "Grid Point Stress Discontinuity
Pointer Table" and the "Grid Point Stress Discontinuity Value Table"
respectively. The correct titles of these data blocks are the "Element Stress
Discontinuity Table" and the "Element Stress Discontinuity Value Table"
respectively.
3870
ation
69
Documentation - NLPARM - Missing Document
Beginning with MSC/NASTRAN Version 67, it is documented that the value entered
for the MAXITER field on the NLPARM entry must be a positive integer. The
documentation fails to mention that any negative integer value will be
converted to a positive value. This action is taken to maintain upward
compatibility with pre Version 67 systems.
3871
Error
68
Documentation - PARAM,POST - FORTRAN I/O
When PARAM,POST,-1 or -2 is used in the Bulk Data without an explicit

ASSIGN statement for UNIT 12 in the File Management section, some machines will
fail and will issue a FORTRAN I/O error message.
Avoidance: Enter an ASSIGN statement for UNIT 12 as follows:
ASSIGN OUTPUT2='for12' UNIT=12
3872
g Output
67.5
DBC, TRANS, ACCESS - DBC, PLOAD1 - Missin
When a PLOAD1 entry is applied to CBAR elements, the results are not
converted by DBC. This will cause
missing results in the XDB for the CBAR elements.
Avoidance: Use the CBEAM element instead of the CBAR.
3873
67
Grid Point Stress - GPSTRESS, PSHELL - Wr
ong Answers
The grid point stress results for shell elements that are defined in a
coordinate system other than the basic
coordinate system will be incorrect if the SYSTEM parameter of the SURFACE
command is set to BASIC or CORDi.
Avoidance: Set the SYSTEM parameter to ELEMENT on the SURFACE command.
3874
46
68
Acoustic Analysis - ACMODL,IDENT - SFM 61
If the user selects the IDENT option on the ACMODL entry without
specifying FSET or SSET, then the program will fail and the message "SYSTEM
FATAL MESSAGE 6146(GPTABD) ELEMENT TYPE =******* IS NOT SUPPORTED IN ACOUSTIC
ANALYSIS" will be issued.
Avoidance: Specifying FSET and SSET will resolve the problem.
3875
68
Miscellaneous - ID - UFM 300, UFM 3060
If one of the two alphanumeric words on the ID entry in

Control Section begins with a numeral, then the program will
message "UFM 300" followed by "UFM 3060" will be issued. An
the NASTRAN statement also produces "USER FATAL MESSAGE 3060
APPROVED LIST".
the Executive
fail and the
invalid keyword on
OPTION NOT IN
Avoidance: Start both words on the ID entry with an alphabetic character.

Note that the ID entry is optional
in MSC/NASTRAN Verson 66 and beyond and can be deleted.
3876
67.5
AT8 - Different Answers
Optimization/Design Sensitivit - PCOMP, M
If the coefficients of thermal expansion are specified on the MAT8 entry

that is referenced by a PCOMP entry,
an MID4 coupling matrix will be created unnecessarily. This will lead to
slightly different results for
sensitivity coefficients even though a temperature load has not been specified.
Avoidance: The difference in answers is insignificant, no avoidance is
necessary.
3877
67.5
Negative Terms on Factor
Optimization/Design Sensitivit - DOM11 -
If the value specified on the property entry is less than the minimum
value specified on the DVPRELi, then the
program may fail and issue a message indicating that negative terms on the
factor diagonal exist.
Avoidance: This is a user input error. Modify the property entry of
DVPRELi as necessary. This error will
be addressed in Version 67.5 by issuing USER FATAL MESSAGE 6421. This message
will clearly identify the
conflicting property and DVPRELi entries.
3879
69
Miscellaneous - GP2 - UFM 2007, UFM 5466
If a large model is run with a small amount of memory, then one of the
following misleading messages may be issued:
USER FATAL MESSAGE 2007, ELEMENT xxx REFERENCES UNDEFINED GRID POINT yyy
or
USER FATAL MESSAGE 5466, ELEMENT xxx HAS NO PSOLID CARD. CHECK MATERIAL
PROPERTIES.
Avoidance: Increase the memory and rerun the job.
3880
7
67.5
Matrix Methods - MPYAD - SFM 4276, EC 777
Large models may fail due to an integer overflow and issue the message
"SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777". This error occurs when converting
a large real number to an integer. The job is most likely to fail in the MPYAD
module but the cause of the error is an incorrect matrix trailer; therefore,
the job may fail in other modules. This error is dependent on the machines
representation of integer and real numbers and is not encountered easily. So
far, this error has only been observed on the DEC VAX.
Avoidance: Possible avoidances are to split the model up into
superelements or to run the job on another
machine.
3881
68
Composites - MAT8 - Unexpected Answers
Fields 5 through 10 on the second continuation entry for the MAT8 entry
are empty fields. If a BCD value is inadvertently placed in any of these
fields, MSC/NASTRAN will terminate the run and correctly issue a UFM.
However, if a real number is entered in one of these fields the run will
continue and no fatal message is issued. Depending on the intent of the user,
this may lead to unexpected results.
Avoidance: Other than putting data in correct fields, there is no
avoidance.
3882
68
Acoustic Analysis - MAT10 - UFM 316
If the MAT10 entry contains data for the bulk modulus and the speed of
sound, then the job will fail and the message "USER FATAL MESSAGE 316 (IFPDRV)
ILLEGAL DATA ON BULK DATA MAT10" will be issued. The bulk modules, mass
density, and speed of sound are related by the following equation: BULK=
C**2*RHO.
Avoidance: As documented in the MSC/NASTRAN User's Manual description of
the MAT10 entry, the bulk modulus, mass density, and speed of sound are related
by the equation: BULK=C**2*RHO. Thus, the avoidance is to enter the bulk
modulus and mass density or the mass density and the speed of sound. Note that
the documentation fails to clarify that it is a user input error to specify
values for the bulk modulus, mass density and speed of sound. If all three
values are explicit
3883
M 2113
68
Documentation - Handbook for Thermal - UF
The Handbook for Thermal Analysis, page 3.5-10, incorrectly recommends that an
SPOINT be used to represent an enclosure by defining a CHBDY to reference an

SPOINT. Following this recommendation will result in the job
failing, and the message "USER FATAL MESSAGE 2131 NON SCALAR ELEMENT REFERENCES
A SCALAR POINT" being issued. This documentation has been superseded by the
Thermal Analysis User's Guide.
Avoidance: CHBDY may only reference to a GRID point.
3884
68
correct Documentation.
Documentation - Handbook for Thermal - In
If the RADMTX and VIEW entries are both present in the Bulk Data Section, then
the VIEW entries will be
ignored. MSC/NASTRAN uses the input RADMTX information to calculate the
temperature distributions. This action is contrary to page 6.3.18 of the
Handbook for Thermal Analysis where it is stated that the RADMTX will be
ignored when a VIEW entry is present. This documentation has been superseded
by the Thermal Analysis User's Guide.
Avoidance: If you want the VIEW module to calculate the radiation matrix, then
comment out or remove the
RADMTX entries.
3885
68
Version in Database
File Management Section - ENDJOB - Extra
If an ENDJOB command is used in the restart run, a new version should not
be created in the database.
However, in some instances, a non-restartable new version is created.
Avoidance: There is no avoidance to the new version being created in the
database. If this error is
encountered, the user must explicitly specify a restartable version ID.
3886
67.5
- Wrong Answers
Nonlinear Static Analysis - PARARM,NMLOOP
In Solution 106, if there are multiple boundary conditions, and the loop
identification number specified on
the "PARAM,NMLOOP,x" falls within a subcase which has a different boundary
condition than the first subcase, then
the nonlinear normal modes calculation will be wrong.
Avoidance: Insert the following DMAP alter.
compile nlstatic souin=mscsou noref nolist
alter 447
type parm,,rs,n,fact $
type parm,,i,n,recno $
paraml estnl//'dti'/0/3/s,n,efact $ get load factor
$ convert load factor to record no. of CASES.
fact=real(int(efact)) $
recno=int(fact)+1 $
if ( fact<>0. and abs(efact-fact)<=1.e-4 ) recno=int(fact) $
$ get appropiate record
CASE
CASES,/CASEi/'TRAN'/recno $
equivx casei/cases/-1 $
CALL SETQ CASES//SEID/PEID/S,MTEMP/S,K2GG/S,M2GG/S,B2GG/S
3887
68.2
Restarts - CELAS2, CDMAPi, CVIS - Ineffic
ient Restart
When performing an automatic restart in a modal frequency or transient response
analysis and a damping
property value or stress coefficient is changed on a CELAS2, CDAMPi, or CVISCi
element, then the modes will be recomputed. This inefficient action is due to
an error in the NDDL dependency check.
Avoidance: There is no avoidance; however, by utilizing superelements and
placing the offending scalar
element in the residual structure, the cost of recalculating the modes can be
reduced.
3888
normal Exit
67.5
Grid Point Stress - GPSTRESS, PSOLID - Ab
When the CORDM field on the PSOLID entry is left blank or set equal to -1,
the program will terminate in the
GPSTRESS module. No NASTRAN fatal messages are generated. This error occurs
in MSC/NASTRAN Version 67R2 running
on UNIX machines only.
Avoidance: Change all blank or -1 CORDM fields on the PSOLID entry to 0.
3889
Acoustic Analysis - EMA - SFM 4276 EC 211
If fluid grids (CD=-1) are used for structural elements, such as QUAD4,
then MSC/NASTRAN will fail in the EMA
module with SFM 4276 EC 211.
Avoidance: Structural elements must only reference structural grids where
CD does not equal -1 on the GRID
entry.
3890
68
Aeroelastic Analysis - FA2 - FREAD Error
On IBM MVS systems poor convergence in the eigenvalue analysis routine of

the KE flutter analysis method may
result in roots being missed and the job failing in the FA2 module with the
message "SYSTEM FATAL MESSAGE 4276 EC
3002" being output.
Avoidance: A Superzap is available which increases the number of
iterations performed during the eigenvalue
analysis used by the KE flutter method. If it is desired, please contact your
local MSC representative.
3891
FM 7119
67.5
Optimization/Design Sensitivit - PGAP - U
If a DVPREL1 or DVPREL2 entry references a PGAP entry, UFM 7119 "Incorrect

entry length at PTYPE 2102 21,
PID=0 " is output. Since GAP elements are intended to act as a linear spring
in linear analysis, this is a code
error.
Avoidance: Use spring elements in place of the GAP elements.
3892
67.5
Composites - TEMP - Wrong Answers
If the maximum strain failure theory is used when using composites, then
the failure indices calculation uses the total strain instead of the elastic
strain. This error only occurs if the run contains thermal load since the
total and elastic strains are the same in the case without thermal load.
3893
M 3060
68
Documentation - MSC/NASTRAN Applicat - UF
Section 7.6 of the MSC/NASTRAN User's Manual which describes the

installation instructions should state that
the authorization file AUTH.DAT must have read and write privileges for all
users. (All machines except VAX/VMS,
CRAY, IBM MVS/XA, HITACHI, FUJITSU MSP/EX)
3894
References
68
Documentation - NLPCI - Incorrect Remark
The description of the MINALR, MAXALR, DESITER and MAXINC fields of the
NLPCI Bulk Data entry in the
MSC/NASTRAN User's Manual refer to Remarks 4, 5, and 6. The descriptions
should refer to Remarks 3, 4, and 5,
respectively.
3895
315
68
Heat Transfer Analysis - QVOL, IFP - UFM
If the a QVOL Bulk Data entry is entered in large-field format, then the
program fails in the IFP module and the message "USER FATAL MESSAGE 315
(IFPDRV)FORMAT ERROR ON BULK DATA CARD QVOL" is output.
Avoidance: Use small-field or free-field format.
3896
3001
GL
Design Sensitivity - DSTA, SENSITY - SFM
If a job is submitted using the old design sensitivity capability and

there are no material properties defined in the model, then the job fails and
issues the message "SYSTEM FATAL MESSAGE 3001 ATTEMPT TO OPEN DATA SET 110 IN
SUBROUTINE DST96B, WHICH WAS NOT DEFINED IN THE FIST". Note that this error is
only possible when the model consists entirely of scalar elements. Any other
model that has no properties defined will fail with appropriate messages in
IFP.
Avoidance: Add a dummy MAT1 entry to the Bulk Data.
3897
67.5
Restarts - Superelements - Wrong Answers
If there are no Bulk Data changes on a restart run but a referenced SPC
and/or an MPC set ID is changed in the Case Control, then the KGG matrix for
the downstream superelements does not reflect the change of the upstream
superelements. It is important to note that the results will change from the
previous run, and thus the user may believe the program performed the correct
action.
Avoidance: An avoidance is to make changes to the Bulk Data so that the
automatic restart feature reacts
correctly. For example, adding a disjoint structural element or grid point or

making a very small stiffness change
to an existing element will cause the automatic restart feature to perform the
correct updates.
3898
ment
68
Documentation - INPUTT4 - Missing Require
When a matrix is read using INPUTT4, there is an undocumented requirement

that the columns must be in
ascending order. If the input file does not have the columns in ascending
order, any columns which are out of
sequence is ignored, and no warning is given.
Avoidance: Make sure that all terms are in the correct order. This
documentation error is correction in Version 68 of the MSC/NASTRAN DMAP Module
Dictionary.
3899
lt
68
DMAP - SOL 111, COMPILE - Incorrect Defau
The default for the COMPILE command in Solution 111 is NOLIST instead of LIST.
Avoidance: The user must explicitly specify LIST,REF on the COMPILE command to
obtain the DMAP listing of SOL 111.
3900
68.2
ATMOD(24) - UFM 4422
Nonlinear Transient Analysis - SOL 129, M
SOL 129 may fail with the message " USER FATAL MESSAGE 4422 NUMBER OF NULL ROWS
IN THE DYNAMIC MATRICES IS NOT EQUAL TO THE NUMBER OF NULL COLUMNS". This
error occurs because Option 24 of the MATMOD module does not recognize strings
that are null. The null strings are created by the ADD5 module.
Avoidance: Use SOL 99 or insert the following DMAP alter:
COMPILE NLTRAN SOUIN=MSCSOU LIST NOREF
$ALTER 244,246 $ V67.5 MATMOD AM1,,,,,/VDXW,/24/S,N,NODRED/1/S,N,NP $
ALTER 304,306 $ V68
DIAGONAL AM1/VDXW/'SQUARE'/0. $ IDENTITY MATRIX SIZE OF AM1
$ALTER 248,248 $ V67.5 ADD5
AM1,VDXW,,,/AM1X $
alter 308,308 $ v68
ADD VDXW,AM1/AM1X///3 $ am1x(i,j)=vdxw(i,j) if am1(i,j)=0.
$ALTER 250,250 $ v67.5 ENDIF $ NODRED>-1
alter 310,310 $ v68
3901
76 EC 301
68
File Management Section - ASSIGN - SFM 42
If the AUTOASGN parameter is set to 2 on the NASTRAN entry which selects

only the Delivery Database to be
autoassigned, an incorrect logical name is given to a database, the program
will fail and will issue the message "SYSTEM FATAL MESSAGE 4276 EC 301".
Avoidance: Specify a correct logical name.
3902
6
68
Miscellaneous - DBINIT, BUFFSIZE - SFM 44
On the VAX/VMS if the buffsize is set larger than the maximum allowable
size , then the job will fail in
DBINIT and a misleading message will be output. In Version 67, the message
"SYSTEM FATAL MESSAGE 446 (DBCRT) ERROR ATTEMPTING TO CREATE A FILE (LOGICAL=
MASTER ) FOR DBSET MASTER WITH READ AND WRITE PRIVILEGES. USER ACTION: CHECK
THE AVAILABLE/ALLOCATED SPACE AND THE PRIVILEGES GRANTED THIS ACCOUNT." will be
output.
Avoidance: The maximum recommended buffsize for the MSC/NASTRAN Version
67 on the VAX/VMS is 8065. Version
67.5 and the VAX/VECTOR will except a maximum BUFFSIZE of 16385.
3904
rs
67.5
Elements - TEMP(LOAD), QUADR - Poor Answe
The QUADR corner stresses are incorrect when temperature loads are applied
the nodes. The element uses the
average temperature over the element rather than the temperatures at the
corners.
Avoidance: There is no avoidance; however, a finer mesh will reduce the
error.
3913
lation
68
DMAP - SOLVE - SFM 1115, Segmentation Vio
If the SOLVE module is used with option SYM=3 in a user DMAP to compute
the inverse of a matrix and the "B" matrix is not specified, then the program
fails and the message "SYSTEM FATAL MESSAGE 1115" or a message indicating a
segmentation violation is output. Since a "B" should not be required to
perform an inverse, this is a code error. Note, that Remark 3a. and Example
2. in the MSC/NASTRAN User's Manual Version 67 documentation for the SOLVE
module indicate that the "B" matrix is not required.
Avoidance: Explicitly define an identity matrix for the "B" input and use
option 1. The DIAGONAL module may be used to create an identity matrix.
3914
rsion
67.5
DBC, TRANS, ACCESS - TRANS - Incorrect Ve
TRANSmit Version 6 delivered with MSC/NASTRAN Version 67R2 and MSC/EMAS

Version 2 contained changes to support
EMAS. Therefore, the TRANSmit version identifier should be changed from the
identifier used for the TRANSmit
delivered with MSC/NASTRAN Version 67.
Avoidance: Unless a site has both MSC/NASTRAN Version 67 and MSC/EMAS
Version 2 installed at the same site,
no avoidance is necessary. If both products are installed, then TRANSmit
delivered with EMAS should be used since
it is compatible with MSC/NASTRAN Version 67, 67R2 and MSC/EMAS Version 2.
TRANSmit Version 7 will be delivered
with MSC/NASTRAN Version 67.5.
3915
67.5
ssing Parameters
The parameters used in SOL 0 are not documented in Section 3.1.3 of the
Avoidance: The parameter descriptions are as follows and should be
included in the MSC/NASTRAN User's Manual.

MAXRANGE Default = 0
MINRANGE Default = 0
In an old database (Version 65 and older) that was created with SOL 64,
66, or 99, these parameters are
required for use in SOL 0 when migrating a database from Version 65C to Version
67.5.
The value of MAXRANGE and MINRANGE is used to set the maximum and minimum
iteration values, respectively, for
a range of data blocks for the migration of iterations between MINRANGE and
MAXRANGE.
If all iterations are desired, the default values should be used.
SOL21 Default = NO
In an old (Version 6
3916
ce
67.5
Acoustic Analysis - ACMG - Poor Performan
In a coupled fluid/structure analysis, if any of the structural grids have

a global direction specified for the output coordinate system (i.e., nondefault
coordinate system specified in field 7 of any GRID Bulk Data entry), then the
ACMG module may use excessive CPU time for large problems.
Avoidance: If possible remove all CD specification on GRID entries or
increase memory to reduce spill operations.
3917
76 EC 1044
67.5
Aeroelastic Analysis - AMP, AMPC - SFM 42
If multiple aerodynamic methods are used in MSC/NASTRAN Version 66 and one

of the methods selected is the
doublet lattice method, then the job will fail and issue the message "SYSTEM
FATAL MESSAGE 4276 ERROR CODE 1044".
Avoidance: The double lattice method must be selected in a separate run.
3918
ID
67.5
Case Control - SUBCOM - Incorrect SUBCASE
When a SUBCOM Case Control command is embedded among SUBCASEs, the OLOAD,
MAXIMUM DISPLACEMENT, and MAXIMUM APPLIED LOAD output will be identified with
an incorrect subcase ID.
3919
67.5
EIGR - Wrong Answers
Optimization/Design Sensitivit - DRESP1,
When a mode ID requested on the DRESP1 entry for either an eigenvalue or

buckling mode does not exist, then the program fails to trap this condition and
wrong answers result. In MSC/NASTRAN Version 67.5 this condition will be
trapped and UFM 6458 "THE REQUESTED EIGENVALUE OR BUCKLING LOAD ID *** IS
GREATER THAN THE NUMBER OF MODES THAT WERE COMPUTED" will be output.
Avoidance: Make sure that all referenced eigenvalues are extracted.
3920
68.2
E - DMAP FATAL MESSAGE 9015
Optimization/Design Sensitivity - DBLOCAT
If the multi-master technique is used in a modal frequency restart run

(Solution 111), the modes are
unnecessarily recalculated. Furthermore, if the run attempts to calculate
dynamic sensitivities, then the run fails and the message "DMAP FATAL MESSAGE
9015 - THE USET TABLE IS NOT PRESENT" is output.
Avoidance: There are three possible avoidances:
1. Use the conventional single-master technique along with automatic
restart.
or
2. Insert the following DMAP Alter in the multi-master dynamic
sensitivity run.
compile semfreq souin=mscsou nolist,noref
alter 24 $
avoids DFM 9015
desiter = 0 $
$
alter 74,74 $ avoids recalculations of modes
$
or
3. Use multi-master technique in all the mode runs. Use the automatic
3921
68
alysi - Wrong Answers
Nonlinear Heat Transfer - Superelement An
If superelements are defined in a nonlinear heat transfer analysis (SOL

153 or SOL 74), the answers for the interior points of the upstream
superelements will be incorrect.
Avoidance: There are two avoidances for this problem:
1. Do not use superelements; define the entire structure to be in the
residual.
2. Use the following alter:
$ For SOL 153
compile sedisp souin=mscsou,nolist,noref
alter 101,101 $ for version 67
if (seid=0) then $
cend
3924
ng Answers
68
Material Nonlinear Analysis - MATS1 - Wro
Remark 3b under the MATS1 bulk data entry description in the MSC/NASTRAN
User's Manual description of the
MATS1 entry states that "If TYPE is NLELAST" and the curve is "defined only in
the first quadrant, then the curve must start at the origin and the compression
properties will be assumed identical to tension properties." This specification
leads to wrong answers.
Avoidance: Explicitly specify the compression properties for the negative
region for the stress-strain curve.
3925
68
M 4249, SFM 4252
Documentation - PARAM,DBALL(SCRATCH) - UF
The limitations for PARAM,DBALL(SCRATCH) documented in the Introduction To

MSC/NASTRAN Version 67 notes should state that this capability can not be used
in the unstructured solution sequences when upstream superelements exist. If
attempted, then the run will fail with one of the following messages:
USER FATAL MESSAGE 4249. SUPERELEMENT PROCESSING REQUESTED BUT SEMAP DATA
BLOCK IS MISSING. or
SYSTEM FATAL MESSAGE 4252. DATA BLOCK (NONE) FOR UPSTREAM SUPERELEMENT
NOT FOUND IN DATABASE.
3926
68
- Missing Connection Data
Miscellaneous - SEQUENCE PROCESSOR OUTPUT
The "SEQUENCE PROCESSOR OUTPUT" which lists the number of each element
type can not output a number more than 5 digits.
3927
67.5
t Processing of RBEs
DBC, TRANS, ACCESS - DBC, RBEs - Incorrec
DBC does not process rigid elements (RBE1, RBE2, or RBE3) correctly when
they connect to more than 12 grid
points. DBC has been corrected in MSC/NASTRAN Version 67.5 to correctly
process the RBE2 and RBE3 element.
3928
68
Installation - CRAY Y-MP - UFM 3090
There is an installation problem that affects CRAY Y-MP systems. This

error will be encountered any time a
client reports a machine serial number of 5101 or 5102, as these serial numbers
are incorrect.
To install the proper serial number, the system installer must delete the
file "/usr/src/uts/cf. /lib/conf.o"
where the " " in the filename represents the correct serial number. The source
for this file is in
"/usr/src/uts/cl/cf/conf. .c" Once this file has been deleted the kernel must
be rebuilt. This problem has been
reported as Cray Software Problem Report (SPR 58019, Call 21997). Clients
should contact Cray's North American
Support Center at 1-800-950-CRAY or send email to "support@crayamid.cray.com".
4004
67.5
,POST - Wrong Answers
Postprocessing - ELSDCON, STRFIELD, PARAM
Element stress discontinuities in a mixed-element model (for example,

QUAD4/TRIA3s or QUAD8/TRIA6s) will be incorrectly stored on the .xdb.
Avoidance: Request grid point stress discontinuities. These results should be
close to the Element results.
4018
68
Stresses in BEAM Elements
DBC/TRANS/ACCESS - DBC, BEAM - Incorrect
If a transient response analysis incorrectly requests STRESS(PHASE) output,

then BEAM stress data is written incorrectly to the XDB. The incorrect data
only affects xy plots in MSC/XL.
Avoidance: This is a user error. Phase output is not a valid request for a
transient run.
4028
68.2
Miscellaneous - MTRXIN - SFM 4276 FREAD E
C 3002
A logic error in module MTRXIN results in SYSTEM FATAL MESSAGE FREAD ERROR CODE
3002 when the following conditions are met:
1. A MTRXIN (rather than a Case Control request) exist in the DMAP to convert
matrices input on DMIG entries
to NASTRAN DMAP datablocks.
2. No DMIG input records exist.
3. Table MATPOOL exists due to MFLUID, ELIST, RADLST, RADMTX, RADCAV, or
RADSET bulk data entries.
If any of entries cited in item 3 exist in the bulk data, the error may be
encountered in SOL 101 with PARAM,INREL,-1 and no DMIG,UACCEL bulk data entry.
Avoidance: Remove the bulk data entries specified in item 3 above, or add an
unreferenced DMIG such as:
DMIG,ABC,0,6,1
4029
68
HELL, QUAD4, TRIA3 - Poor Answers
Differential Stiffness and Buckling - PS
The MSC/NASTRAN User's Manual documentation for the PSHELL entry should be
amended to state that when modeling curved shells with QUAD4 or TRIA3 elements
in a solution that uses differential stiffness (buckling or nonlinear with
PARAM,LGDISP), results may include spurious modes or difficult convergence in
Version 67.7 and earlier versions.
Avoidance: For linear buckling only, spurious modes can be avoided if every
element is replaced by two overlapping elements. One has only membrane
properties (MID2 and MID3 are blank on the PSHELL entry). The other has only
bending properties (MID1 is blank on the PSHELL entry). Unfortunately this
avoidance can not be applied to nonlinear problems since "USER FATAL MESSAGE
4295" results when MID1 does not equal MID2 on the PSHELL entry (see error 5
4035
-MP Only
67.5
Miscellaneous - Submittal Script - CRAY Y
The submittal script provided for the MSC/NASTRAN Version 67 on the CRAY Y-MP
UNICOS hard wires the "lt" parameter to 300 seconds. This parameter, which
controls the CPU limit for the job, should be adjustable. A new parameter has
been added to Version 67.5 to allow the user to specify the CPU limit at run
time.
4036
68.2
id Point Force Output
Nonlinear Analysis - GPFORCE - Missing Gr
A GPFORCE request in a nonlinear solution sequence is ignored in

MSC/NASTRAN Version 68.
Avoidance: The following DMAP avoidance allows for GPFORECE data
recovery
for the linear elements in SOL 106:
compile nlstatic souin=mscsou nolist noref $
alter 1 $
putsys(0,192) $
$
COMPILE SEDISP SOUIN=MSCSOU NOLIST NOREF
$ALTER 55 $
ALTER 54 $ after output of pj1
PARAML CRX//'PRESENCE'////S,N,NOCRX $
IF ( NOCRX = -1 ) EQUIVX PJ/PJ1/ALWAYS $
$
ALTER 265,265 $
TYPE DB,CASES $
TYPE PARM,NDDL,I,Y,HIGHQUAL $
TYPE PARM,NDDL,I,N,PEID,MTEMP,NLOOP $
TYPE PARM,NDDL,CHAR8,N,APRCH $
TYPE PARM,,I,N,LOAD,
4048
67.5
sleading Message, SWM 2072
Miscellaneous - SESET, SEELT, SEQGP, - Mi
"SYSTEM WARNING MESSAGE 2072, CARD TYPE **** NOT FOUND ON DATA BLOCK" may
be output if SESET, SEELT, SEQGP or SEQSEP Bulk Data entries are present. If
there are no acoustic grid points in the model and this message is output from
the RESTART or SEP2 module, then this message can be ignored.
4055
01
68
Cyclic Symmetry - RANDPS - SFM 4276 EC 30
Random analysis cannot be performed in cyclic frequency response (SOL 118

or SOL 78) with harmonic output. If attempted, the message "SYSTEM FATAL
MESSAGE FREAD ERROR CODE 3001" is output.
Avoidance: Specify segmented output instead of harmonic output in the
Case Control.
4068
68
ERT Option Fails
File Management Section - DBLOCATE - CONV
When the convert option is used on a DBLOCATE statement to alter the

PROJECT name of the database created by the prior run, MSC/NASTRAN fails to
recognize the new project ID. Therefore, subsequent operations on the
database, such as a DBVIEW statement, fail. In the following example, DBVIEW
fails to view the data blocks
specified.
Example:
ASSIGN MODE2=build2.MASTER
DBLOCATE DB=* WHERE(PROJECT='MODES',VERSION=1),
CONVERT(PROJECT='ASET', VERSION=1) LOGICAL=MODE2
DBVIEW MGGF=MGG (WHERE PROJECT='ASET' AND VERSION=1 AND WILDCARD=TRUE)
Avoidance: The project ID and version ID parameters must be explicitly
defined as follows:
TYPE PARM,,I,,PROJECT2=2,VERSION=1 $
If the file management section contains the DBVIEW statements, it should
be mod
4071
68
- Wrong Answers
Grid Point Stress - ELSDCON, GPSDCON, FI
The stress discontinuity results are incorrect if FIBRE=MID or Z2 on the

SURFACE command. The grid point stress results are also incorrect.
Avoidance: The avoidance is to set FIBRE=ALL on the SURFACE command,
which is the default.
4074
ong Answers
68
Material Nonlinear Analysis - PSHELL - Wr
Wrong answers occur in a material nonlinear analysis whenever the 12I/T3

(bending stiffness parameter) on the PSHELL entry is not equal to 1. To
prevent wrong answers from occuring, MSC/NASTRAN Version 68 will issue a user
fatal message when this condition is encountered.
Avoidance: There is no avoidance. Note that since material nonlinear
analysis requires that MID1 be the same as MID2 on the PSHELL entry, the
desired effect may not be simulated by referencing different material entries
for MID1 and MID2.
4093
nce
68
Miscellaneous - SET, SDR2 - Poor Performa
If the user requests displacement output for a SET that defines a large
range of grid points using the "THRU"option (for example SET 2= 1 THRU
999,999), then the SDR2 module may spend considerably more CPU time versus the
equivalent DISP=ALL request. This performance degradation will only occur when
there is at least one grid point ID outside the range. An aeroelastic analysis
is more likely to encounter this error because the internal degrees of freedom
are generated and differentiated from the physical degrees of freedom by adding
very large numbers to them.
4094
Answers
68
Nonlinear Analysis - GAP - Unpredictable
If a GAP element is defined between coincident nodes, the element coordinate

system is unpredictable.
Avoidance: Round-off error may result in the location of any two points being
viewed by the code as noncoincident. Therefore, the user should separate the
points being connected by at least 1.E-2 units so
that the element coordinate system is determined by the vector connecting the
grid points. This error has been corrected in MSC/NASTRAN Version 68 by
implementing the following changes to the GAP element interface:
1. The tolerance used to determine whether nodes are not coincident has been
increased from 1.E-10 to 1.E-3.
2. If a coordinate system is not specified in field 9 of the CGAP entry and
the connected grids are closer than 1.E-3, then UFM 6459 is issued.
3.
4122
GL
PLOADi - Effect Not Included
Optimization/Shape Sensitivity - RFORCE,
The effects of changes in pressure loads or followers loads that result from
changes in the underlying grid location are ignored when computing
sensitivities. Changes in gravity and thermal loads are included during shape
sensitivity calculations.
4136
dices
67.5
Composites - LSTRN - Incorrect Failure In
If the values in the THETA field of the PCOMP entry vary between plies,
the failure indices may be incorrect for the varying plies when PARAM,LSTRN is
set to 0. (Version 66 and Version 67 only).
Avoidance: The avoidance is to set PARAM,LSTRN to 1.
4151
67.5
Acoustic Analysis - METHOD - SFM 3001
In a coupled fluid-structural analysis using the modal method if the user

fails to specify a METHOD entry for the structure, then the run fails and the
message "SYSTEM FATAL MESSAGE 3001 ATTEMPT TO OPEN DATA SET 104 IN SUBROUTINE
GKAM, WHICH WAS NOT DEFINED IN THE FIST" is output. This problem is identical
to Error 3610. The only difference is that a method entry may have been
included for the fluid.
Avoidance: Specify a METHOD entry for the fluid and the structure.
4158
Answers
68
Heat Transfer Analysis - VECPLOT - Wrong
If the user specifies an output coordinate system on the GRID entry other
than the default basic coordinate system, then the OLOAD RESULTANT, MAXIMUM
DISPLACEMENTS and MAXIMUM APPLIED LOADS output are incorrect. All other
results are unaffected by this error. This error is corrected on latter
MSC/NASTRAN Version 67.5 systems. The systems include DEC ALPHA, INTEL 386/IX,
and HITACHI S3600.
4179
70.5
Case Control - PCOMP, ECHO - UIM 4379
According to the text of UIM 4379 the internally generated PSHELL and MAT2
entries are only output when a sorted echo is requested. Contrary to this,
using ECHO=NONE does not result in the removal of this output.
Avoidance: ECHO=UNSORT must be explicitly specified to disable UIM 4379
output. If the user does not desire an unsorted echo, then specifying
ECHO=UNSORT(****) where "****" indicates any Bulk Data entry that is not
contained in the input Bulk Data, has the same effect.
4187
tar - SFM 3007
68
Material Nonlinearity - Data Recovery Res
If a SOL 106 model does not contain SPCs and is restarted for data
recovery, SFM 3007 "Illegal Input to
Subroutine CALCV" is issued from the UPARTN module.
Avoidance: The avoidance is to use the following alter:
$ FOR VERSION 67+ IN SOL 106
COMPILE DMAP=NLSTATIC,SOUIN=MSCSOU,NOLIST,NOREF $
ALTER 434 $ AFTER EQUIVX
PARAML USETNL//'USET'//////'A'/S,N,NOASET/'G'/S,N,NOGSET $
NOA = LTOI ( NOGSET = NOASET ) $
ENDALTER $
4194
68
Rigid Elements - DBC - Missing Data
THE PROBLEM
DBC will incorrectly store multiple RBE's having more than 12 Grids
(independent or dependent, depending on RBE type) to the .xdb. In particular,
the RBEPOOL is built incorrectly. Data is overwritten.
THE AVOIDANCE
Break up the RBE's into smaller elements.
4197
ct Labels
67.5
Elements - STRAIN(FIBER), QUAD4 - Incorre
The grid point labels for the QUAD4 and QUADR STRAIN(FIBER) output are
incorrect.
4198
68
s Manual - Incorrect Documentation
Documentation - CHACAB, MSC/NASTRAN User'
Remark 6 of the MSC/NASTRAN CHACAB Bulk Data description should be

changed. Currently, the remark states that "The face consisting of grid points
G1 through G4 and G9 through G12 is assumed to be in contact with the fluid."
The remark should state that "The face consisting of grid points G5 through G8
and G17 through G20 is assumed to be in contact with the fluid".
4211
68
correct Documention
Documentation - MSC/NASTRAN User's M - In
The MSC/NASTRAN User's Manual and Quick Reference Guide description of the
PARAM,KDIAG is incorrect. The
current documentation states that KDIAG specifies a stiffness value to be
applied to all degrees of freedom. The documentation should be changed to
state that KDIAG specifies a stiffness value to be applied to the null column
of the nonlinear stiffness matrix.
4223
2001
table Eigensolutions
Virtual Mass - MFLUID, CORDiS, CORD - Uns
Virtual fluid mass is regarded as an improvement to structural mass, but not as

a replacement for structural mass. When a structure is modeled to enclose or
be enclosed by a virtual fluid the mass properties of the structure should be
included in the model, even when the fluid is many times heavier than the
structure. The reason is that the fluid mass is uni-directional, and may not
contribute to overall inertia properties of the model. This can lead to high
maxratio messages in eigenvalue analysis, and missing or unstable rigid body
modes. These modes are stabilized by the addition of structural mass, even
when it is relatively small.
4235
67.7
Elements - PENTA, GPSTRESS - UFM 5146
If a PENTA element's dimensions are small compared to the element's distance

from the basic coordinate system's origin and grid point stress output
(GPSTRESS) has been requested, the job may fail in the GPSTR1 module and the
message "USER FATAL MESSAGE 5146" is output.
Avoidance: If possible, the coordinates of the GRID entries in the model should
be translated so that the PENTA elements are closer to the basic coordinate
system's origin. In the case where the entire model has been defined a large
distance from the basic coordinate system's origin, changing all GRID entries
to reference a CORDRi entry that is defined parallel to but translated from the
basic coordinate system may simply accomplish the necessary translation.
4236
Does Not Work
68
Plotting - NEUPS - Wallpaper Plot Option
Increasing the scale factor to a size greater that 1.0 in the NEUPS
control file to create "wallpaper" plots does not work. The scale of the plot
is increased, but only a segment of the plot is printed on a single page.
Avoidance: There is no avoidance to the problem.
4241
Answers
70
Static Analysis - PLOAD1, REPCASE - Wrong
If a PLOAD1 entry is used to apply load to a BEAM or BAR element and REPCASE is
used to request additional
output, then the load request must also appear within the REPCASE; otherwise,
the results from the REPCASE will be
wrong.
Avoidance: Include the appropriate load request in the REPCASE.
4243
0
68
File Management Section - ASSIGN - UFM 47
If a continuation entry is specified for the ASSIGN statement as follows:

assign XXXX= ,
dbs/yyyy.MASTER'
The database name is converted to uppercase (in the example 'DBS/YYYY.MASTER')
and MSC/NASTRAN fails to locate the database even though it exists. This
probably occurs on all unix machines.
Avoidance: Do not split the line after the logical name.
database name on the same line as the logical name.
4251
68
s - Wrong Answers
Supply the
Aeroelastic Analysis - ZONA51 Aerodynamic
If the AERO II option (ZONA 51 AERO) is used with anti-symmetric matrices

where SYMXZ=-1 on the AERO or AEROS Bulk Data entry and there is a lifting
surface on the XZ plane of symmetry, then wrong answers result.
Avoidances: Weighting factors can be applied to the aero matrices to get
correct answers. For Solutions 21 and 144, WKK is input on a DMI entry. This
is a diagonal matrix that has 1.0 for the boxes for which no error correction
is required and 0.5 for the boxes that are on the plane of symmetry. For
Solutions 75, 76, 145, and 146 a similar technique is available using WIFACT as
the matrix name on the DMI entry.
4262
Acoustic Analysis - TEMP(LOAD) - UWM 6008
If thermal loads are applied in a coupled fluid-structure analysis, the

job issues the message "USER WARNING MESSAGE 6008, THERMAL OR DEFORM LOAD SET
XXX IS NOT APPLICABLE FOR THIS ELEMENT". The message correctly warns the user
that thermal loads are not applicable to acoustic elements; however, the
program incorrectly ignores thermal loads for all elements.
4263
- No Output
2001
Acoustic Analysis - METHOD(FLUID) Missing
A fluid only model will not run in SOL 111 unless a METHOD(FLUID)=n case
control is present. The run completes to "END OF JOB" in the f06 and "EXIT" in
the f04 but virtually the only output in the f06 is UIM 302 indicating to the
user that GRID ENTRIES HAVE DISPLACEMENT COORDINATE SYSTEM ID OF -1 which is
the coordinate system ID of fluid points.
4271
Results
70
Static Analysis - TEMP(INIT) - Unexpected
If TEMP(INIT) is used to define the initial temperature and this initial

temperature definition specifies a different temperature at each of the
connecting grids of a plate element (e.g., QUAD4, QUAD8, TRIA3, etc.), then the
average temperature of the connecting grids for that element is used as the
initial temperature for all the grids that are connected to that element.
Avoidance: There are two possible avoidances:
1. Specify a constant initial temperature throughout the model and adjust the
final temperature to reflect the proper delta temperature. If
temperature-dependent materials are used, then they also need to be properly
adjusted to reflect the initial temperature modification.
2. Replace the plate elements with solid elements. Using a linear solution
(e.g., SOL
4310
g Answers
69
Static Analysis - TEMP(INIT), SDR2 - Wron
If TEMP(INIT) is used to define the initial temperature in a linear static

analysis and a different initial temperature is specified at each of the
connecting grids for a solid element, then the stresses will be wrong.
Avoidance: Use a nonlinear solution instead.
4316
M 3001
69
Documentation - Acoustic Analysis, R - SW
Section 1.16 of the MSC/NASTRAN User's Manual states that coupled

fluid-structural analysis is available using the modal method in SOLs 110
through 112. The documentation does not, but should, explicitly exclude the
calculation of modes for a coupled fluid-structural analysis in SOL 103 or SOL
106 to be used for a restart in SOLs 110 through 112. If the user attempts to
calculate coupled modes in SOL 103, then the program may fail and the message
"SYSTEM WARNING MESSAGE 3001 ATTEMPT TO OPEN DATA SET 105 IN SUBROUTINE REIG
WHICH WAS NOT DEFINED IN THE FIST" is output.
The MSC/NASTRAN Version 69 Reference Manual, Section 15.4.2 adds the requested
documentation.
4317
pected Answers
2001
Acoustic Analysis - CHACAB, PACABS - Unex
If the user supplies data on the tables that are referenced by the PACABS
entry and this data results in
negative terms in the equivalent structural model for the acoustic absorber
element, then these terms are set to zero. Negative terms in the equivalent
structural model may result from data where the user is attempting to model an
infinite, perfectly absorbing domain. MSC/NASTRAN does not support this
capability.
Avoidance: The user should inspect the USER INFORMATION 6232 output which
provides the calculated acoustic absorber properties to be sure that negative
terms do not exist.
4320
Acoustic Analysis - CHACAB, PACABS - SFM 4276 EC 211
If the frequency specified on the

the TID1 field of the PACABS Bulk
the message "SYSTEM FATAL MESSAGE
occurs because the equations that
frequency of zero.
TABLEDi Bulk Data entry that is referenced by

Data entry is zero, then the job fails and
4276 ERROR CODE 211"is output. The failure
define the resistance are singular at a
Avoidance: Define the properties for the absorber element at a frequency other
than zero.
4351
ntation
68
Documentation - DSCONS - Incorrect Docume
The value of psi when the "LIMIT" field is 0.0, equal (-response) not the
(response) as documented.
4352
tion
68
Documentation - CONM2 - Incorrect Descrip
In the Version 67 MSC/NASTRAN User's Manual and MSC/NASTRAN Quick Refere

nce
Guide, the Bulk Data description for the CONM2 entry specifies that Iij must be
a real number that is greater than or equal to 0.0; however, IFP allows
negative values for Iij.
4357
67.7
Miscellaneous - DIAG 2 - SFM 1032(X10)
Large jobs with DIAG 2 may fail and issue the message "SYSTEM FATAL MESSAGE
1032(X10)".
Avoidance: Remove the DIAG 2 request
Error report:
System Fatal Message 1032(X10) using DIAG 2 in a large SE job.
4361
70.5
1.+30 not Allowed, UFM 224
Documentation - DMAP Dictionary - Format
Using format 1.+30 in a DMAP expression is not allowed. The run will fail with
USER FATAL MESSAGE 224 stating that mixed mode usage by the arithmetic operator
+ is invalid during subdmap. The Version 69 DMAP User's Guide will be updated
to state this restriction.
Avoidance: Use 1.E+30 instead
4366
68
ficient Documentation
Documentation - Acoustic Analysis - Insuf
The following remark should be added to the description of the absorber

element (CHACAB):
7. The mass is lumped to the face in contact with the fluid. This face
consists of grid points G5 through G8 and G17 through G20 (see Error 4198). The
opposite face (the face connecting grid points G1 through G4 and G9 through
G12) has no mass contribution due to the absorber element. The only mass
contribution is from the structural elements that are connected to this face.
The following remark should be added to the description of both the
absorber element (CHACAB) and barrier element (CHACBR).
8. The face in contact with the fluid has only translational stiffness in the
direction normal to this face.
4367
70.5.2
Elements - CBEND, PLOAD1 - Wrong Answers.
When PLOAD1 is used to apply forces with load TYPE in the Basic coordinate
system (FX, FY, FZ, MX, MY and MZ) on the CBEND element, incorrect applied
loads are generated. Consequently, SPCFORCE, displacements and element
stresses are not correct.
Avoidance: Field 4 of the PLOAD1 entry allows loads to be applied either in
the basic or element coordinate system. Use the element coordinate system
option.
4397
4423
69
Documentation - ASET, ASET1, OMIT - UFM
The restriction that degrees of freedom attached to nonlinear elements in

nonlinear solutions cannot be omitted is not clearly stated in any of our
documentation. The following documentation changes should be made:
In the MSC/NASTRAN Reference Manual, Section 15.3 Nonlinear Analysis, Nonlinear
Characteristics and General Recommendations, add the following bullet to the
end of the section:
- Reducing the size of the analysis set by omitting degrees of freedom can
significantly reduce computation times in nonlinear analysis, but degrees of
freedom attached to nonlinear elements cannot be omitted. Elements are
nonlinear if they have nonlinear capabilities (see table 1) and either
PARAM,LGDISP,1 is used or they reference a nonlinear material. Degrees of
freedom attached only to linear
4409
M 3008
68
Matrix Methods - DECOMP, FBS, SPARSE - SF
There is an error in the memory estimate for SPARSE FBS when the matrix is
dense. This error may result in "SYSTEM FATAL MESSAGE 3008" being output which
indicates insufficient memory. For example, a single solid element test, which
generates a fully populated matrix, may encounter this error. This error is
highly unlikely for typical models that produce less than a fully populated
matrix. This error can also occur in nonlinear analysis where FBS is called
from within another module.
Avoidance: The memory estimation error can be avoided by setting
SYSTEM(146)=2 on the NASTRAN statement; that is, set "NASTRAN
SPARSE=25,SYSTEM(146)=2".
4423
nswers
68
Elements - CBEAM, CBAR, Offsets - Wrong A
A remark should be added under the MSC/NASTRAN User's Manual description of the
CBAR and CBEAM entry that using the BAR and BEAM with offsets in any solution
sequence which uses differential stiffness is not recommended. Furthermore,
the message "USER FATAL MESSAGE 6174. BEAM ELEMENTS WITH OFFSETS ARE NOT
SUPPORTED IN DIFFERENTIAL STIFFNESS" is encountered if BEAMs with offsets are
included in a model with differential stiffness.
4424
68
SP, QUAD4, TRIA3 - Wrong Answers
Geometric Nonlinear Analysis - PARAM,LGDI
A nonlinear analysis with PARAM,LGDISP produces incorrect results for the

transverse shear forces for the QUAD4 and TRIA3 elements.
Avoidance: The following DMAP alter will give correct transverse shear
results for QUAD4 and TRIA3 elements in a nonlinear analysis with large
displacements (LGDISP). The DTIIN and TABEDIT are only necessary if the user
wants to postprocess the correct results in MSC/XL. The DTIIN and TABEDIT
assume that only QUAD4 elements are present. If other elements are present, you
will be unable to postprocess the element forces in MSC/XL unless you modify
the Bulk Data DTI entries to account for the different element types. The EQUIV
statement ensures that the correct FORCE results will be output to the .F06
file regardless of element types present in the model
4425
put
2001
Documentation/QRG - REPCASE - Missing Out
When a REPCASE Case Control command is used in a normal modes analysis, only
data for the first mode is printed. This needs to be clarified in the Quick
Reference Guide where remark 3 claims repcase is supported in normal modes.
Avoidance: The REPCASE command is used because multiple output requests of the
same type are not allowed within a subcase. The only avoidance is to define a
single SET that combines all the output desired and select this SET with the
original SUBCASE.
4426
- UFM 2025
67.5
Optimization/Design Sensitivity - DVGRID
If a DVGRID entry references a GRID point connected to elements which do not

have a property entry associated with them (e.g., CONM1, CONM2 etc.), then the
job fails and issues the message "USER FATAL MESSAGE 2025 UNDEFINED COORDINATE
SYSTEM".
Avoidance: Replace the elements with equivalent elements that reference a
property entry. For example, replace CONM2s with CMASS and PMASS entries.
4427
68
Documentation - PBCOMP - SFM 6236
The MSC/NASTRAN User's Manual documentation for the PBCOMP entry should
include a remark warning that a SFM 6236 will occur if SECTION=5 and all the Y
stations are 0.0 or all the Z stations are 0.0. This information should also
be included in the expanded explanation of SFM 6236 in Section 6 of the
4429
g answers
67.5
Lagrange Multiplier Method - RFLAG - Wron
The RFLAG alter that was delivered with Version 67.5 of MSC/NASTRAN in the
misc/sssalter directory contains an error that may result in wrong answers.
Wrong answers will occur whenever material type damping is included. This
includes damping specified by PARAM,G and damping specified through the ge on a
MATi entry. This error has been corrected in later releases of Version 67.5
MSC/NASTRAN. The error exists in the VAX/VMS, CRAY Y-MP, CONVEX, IBM RS6000
and SUN4 releases.
Avoidance: The client should modify the RFLAG.V675 file as indicated. The
lines in error are shown commented out with a "$" symbol and are upper case.
The necessary replacement lines follow and are typed in lower case.
$ ALTER 96,96 $
alter 95,96 $
partn b2ydd,v12g,/,,,b2ygg/-1 $ Reduce from 1-set siz
4435
69
ata Sorted Incorrectly
Dynamic Analysis - Multimaster, SORT1 - D
In a Solution 111 or 112 run using multiple masters, if SORT1 output is

requested, then SORT1 output is given for the resdiual structure, but SORT2
output is given for the upstream superelements.
Avoidance: Use the following DMAP alter in V68
ALTER 90,90 $
ALTER 104 $
TYPE DB,PVT $
PVT PVT,CASEDR/PVTX $
4436
68
Documentation - DMAP - SFM 14
The maximum number of data blocks allowed in each subDMAP is 500 NDDL an
d 500
non-NDDL. SFM 14 is issued when this limit is exceeded. General Limitation
3620, which documents all executive limits, will be updated to reflect this
limit.
Avoidance: Divide DMAP into subDMAPs.
4443
67.5
Documentation - Application Manual Sectio
n 7.7,GENTIM2 - Incorrect Documentation
The documentation for GENTIM2 in Section 7.7 of the MSC/NASTRAN Application
Manual is incorrect. In the listed printout of the Bulk Data GENTIM2, the
documentation indicates "SOL GENTIM2". It should be "SOL GENTIM". The
documentation also indicates "NASTRAN MESH SYSTEM(124)=-10". The documentation

should indicate "NASTRAN MESH SYSTEM(124)=-1". The documentation also
indicates that PARAM,PARAM in the Bulk Data section of the GENTIM2.DAT file is
to be modified; however, this line must be added by the client. This error is
corrected in all releases of MSC/NASTRAN Version 67.5 except the CRAY Y-MP,
CONVEX and DEC VAX/VMS.
4447
70.5
stem Cells for DMAPers
Documentation/DMAP Module Dictionary - Sy
Beginning in Version 70.5 system cell numbers 252 through 262 have been set
aside for the user DMAPs.
4450
68
CDAMP, CMASS - Wrong Answers
Optimization/Design Sensitivity - CELAS,
Incorrect design sensitivities are computed for CMASS1, CELAS1, and CDAMP1,
element types if either connectivity point is a scalar point. The avoidance is
to use CMASS3, CELAS3 and CDAMP3 elements. A second error causes the avoidance
to work only if there are no coordinate systems defined in the model. The
following table summarizes the error for CELASi elements, the table can be
replicated for CDAMPi and CMASSi elements:
Element
Type
GRID/SCALAR
CELAS1
CELAS1
CELAS1
CELAS1
CELAS3
CELAS3
GRID
GRID
SCALAR
SCALAR
SCALAR
SCALAR
4454
67.5
COORDINATE
SYSTEMS
YES
NO
YES
NO
YES
NO
SENSITIVITY
COEFFICIENTS
CORRECT
CORRECT
WRONG
WRONG
WRONG
CORRECT
Plotting - NEUPS - Bad Plot Files
The postscript files generated by the NEUPS utility on the IBM MVS/XA Version
67 release of MSC/NASTRAN are incomplete and produce plots with missing
information.
Avoidance: The avoidance is to obtain a new copy of the NEUPS program from
your local MSC representative.
4457
69
oor Message, Infinite CPU Loop.
Material Nonlinear Analysis - PLSOLID - P
When an ill-defined model with hyperelastic (PLSOLID) elements is analyzed, the

model may be unstable and very large numbers may be produced. The run may fail
due to machine overflow, fail to converge, or become caught in an infinite
loop. This behavior may also occur for models with solid elements (CHEXA,
CPENTA, and CTETRA) that do not reference hyperelastic material.
Avoidance: "USER WARNING MESSAGE 4698" indicating the degrees of freedom that
have factor diagonal ratios greater than 1.E5 is output. The messages "USER
INFORMATION MESSAGE 4158" and "USER WARNING MESSAGE 2053" may also be evidence
of this problem. UWM 2053 notifies the user that a referenced SPC set could
not be found. Thus, the model may not be constrained as the user intended.
The only avoidance is to examine the output.
4458
68
PLSOLID, - UWM 6008, SFM 3003
Nonlinear Analysis - NLCOMB, TEMP(LOAD),
According to the MSC/NASTRAN Release Notes for Version 67.5, thermal loads and
temperature-dependent material properties are not supported for the
hyperelastic elements; however, if a nonlinear model contains both hyperelastic
elements (PLSOLID) and non-hyperelastic elements (PSOLID), thermal effects
should be calculated for the non-hyperelastic elements and the job should
continue. This occurs if the thermal loads are applied with TEMPD entries.
Any nonlinear analysis that contains thermal loads and hyperelastic elements
fails with the following messages if the thermal loads are applied using
anything other than the TEMPD entries (e.g., TEMP entry) :
USER WARNING MESSAGE 6008, THERMAL OR DEFORM LOAD SET
FOR THIS ELEMENT.
SYSTEM FATAL
MESSAGE 3003 MODULE
4459
FM 3008
67.7
x IS NOT APPLICABLE
Optimization/Design Sensitivity - DOT - S
The DOT algorithm that performs optimization computes the amount of memory it
requires for an internal integer array. Under certain circumstances, this
computation is performed incorrectly and this may lead to "SYSTEM FATAL MESSAGE
3008" that indicates insufficient memory. Failure occurs whenever 2 * (NAVC +
NASIPE) > NGMAX
where
NGMAX =
NCON + NDV
NAVC =
# of active and violated constraints considered

by the DOT algorithm
and
NASIPE = # of active side constraints

NCON
= # of retained constraints passed to the optimizer
NDV
= # of design variables
Generally, DOT selects a small set of NCON for NAVC. In the case that
encountered the failure, there were a large number of properties an
4469
ess Sorting
68
Data Recovery - DTI,INDTA - Composite Str
Composite ply results processing does not support the DTI,INDTA Bulk Data
entry.
Avoidance: The following DMAP statement needs to be modified in each
applicable Unstructured Solution Sequence and in the subDMAP SEDRCVR as
follows:
(old)
STRSORT ES1C,/OES1C/V,Y,NUMOUT1=-2/V,Y,BIGER1=0.0 $
STRSORT EFIT,/OEFIT/V,Y,NUMOUT2=-2/V,Y,BIGER2=0.0 $
(corrected)
STRSORT ES1C,INDTA/OES1C/V,Y,NUMOUT1=-2/V,Y,BIGER1=0.0 $
STRSORT EFIT,INDTA/OEFIT/V,Y,NUMOUT2=-2/V,Y,BIGER2=0.0 $
Alternatively, the analyst may use the default ply sorting with parameters
NUMOUT1,NUMOUT2,BIGER1, and BIGER2. This gives sorting on the ply stresses and
strains.
4476
Elements - PSOLID - UWM 5460
If the standard isoparametric integration (ISOP=FULL) is desired for the CHEXA

or CPENTA element with midside nodes, and the IN field is blank on the PSOLID
entry, then MSC/NASTRAN assumes that the user wants to use bubble functions.
"USER WARNING MESSAGE 5460, ILLEGAL OPTION ON PSOLID ID = ***, FOR BUBBLE
FUNCTION. ONLY REDUCED INTEGRATION IS ALLOWED" is issued, and the run will
proceed using reduced integration. The same warning message is issued for
CTETRA elements if the IN field is blank even though bubble functions and
reduced integration are not supported by this element. The run will continue
with the default integration options.
Avoidance: To perform standard isoparametric integration on CHEXA and CPENTA
elements with midside nodes, IN must be set to 3 or THREE. To avoid
4482
68
e Input Filenames
Miscellaneous - CONVEX Only - Unacceptabl
MSC/NASTRAN on the CONVEX will not accept the following filenames:

t.dat
at.dat
dat.dat
Avoidance: Do not use the above names.
4484
67.5
1, FILE 108 NOT IN FIST
Cyclic Symmetry - GPFORCE, GPFDR -SFM 300
Grid point force output is not available in upstream superelements in cyclic

symmetry statics (SOLs 81 and 114). A GPFORCE request results in the message
"SYSTEM FATAL MESSAGE 3001 FILE 108 NOT IN FIST" being issued from the GPFDR
Module.
Avoidance: A DMAP avoidance is under investigation.
4486
onvergence
Nonlinear Analysis - Hyperelastic, PLSOLID, FORM=MIXED - No C
When a displacement coordinate system (CD) is specified on any of the grid

entries connecting a HEXA hyperelastic (PLSOLID) element, results may either
converge slowly or no convergence occurs when FORM=MIXED is selected.
Avoidance: Use the default FORM=ISOP.
4491
70
DMAP - DRMS1 - SFM 4276, EC 7777
The message "SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777" may occur during
data recovery of eigenvalues analysis in the DRMS1 module. This error is due
to numerical underflow or overflow and is highly machine dependent. This error
has only been observed on the DEC VAX(VMS) release of MSC/NASTRAN.
Avoidance: Run the job on another machine.
4494
401
GL
Acoustic Analysis - Wrong Answers - SFM 5
When the surfaces of the fluid cavity are connected to a structural surface
containing two or more distinct elements (i.e. the fluid is interfacing with
HEXA elements on one surface and QUAD elements on the other surface ) then
wrong answers may be produced for the FL./STR. INTERFACE CHECK and/or SFM 5401
may occur.
Avoidance : This is a general limitation of MSC/NASTRAN. The acoustic cavity
must be surrounded by plate or solid elements but not both.
4496
GL
M 4276 EC 7777, Wrong Answers
Acoustic Analysis - CHACAB - UFM 4422, SF
If the table input features of the PACABS Bulk Data entry (TIDi fields) are
used to define the reactance for the CHACAB absorber element then, depending on
the machine, the job may fail and issue either the message "USER FATAL MESSAGE
4422, NUMBER OF NULL ROWS IN THE DYNAMIC MATRICES IS NOT EQUAL TO THE NUMBER OF
NULL COLUMNS" or "SYSTEM FATAL MESSAGE 4276 EC 7777". Incorrect DB pressure
values may also be produced.
Avoidance: Instead of using the TABLEDi features to calculate the stiffness
and mass values for the absorber element, specify the k, m and b values
explicitly on the PACABS Bulk Data entry.
4498
70
Documentation - LINE, MAXLINES - SFM 3019
The message "SYSTEM FATAL MESSAGE 3019 MAXIMUM LINE COUNT EXCEEDED IN
SUBROUTINE PAGER LINE COUNT EQUALS ****" is misleading, because the code is
actually counting the pages. If the user specifies LINE=X and MAXLINES=Y,
then the max number of pages that will be output is Y/X, regardless of how many
lines are actually on each page. When the code counts more pages than Y/X, it
will issue the message above. If the user specifies a value for LINE that is
greater than the actual number of lines per page, then the job fails at a lower
line count than MAXLINES.
Avoidance: Specify a correct value for LINE.
4503
68
Case Control - SDR2, MODES - SFM 3002
In MSC/NASTRAN Version 67.5 if the MODES command references an eigenvector

that does not exist, the run fails and the message "SYSTEM FATAL MESSAGE 3002
MODULE=SDR2 EOF ENCOUNTERED WHILE READING DATA SET PHG" is output from the SDR2
module. Prior versions of MSC/NASTRAN correctly ignore a MODES command that is
beyond the number of eigenvectors calculated.
Avoidance: Remove the additional subcase and MODES command.
4506
67.5
- SFM 4276, EC 1409.
Optimization/Design Sensitivity - UMERGE1
If an optimization or design sensitivity analysis contains EPOINTs as is

required for the Lagrange multiplier large mass method, then the execution
fails in the UMERGE1 module and the message "SYSTEM FATAL MESSAGE 4276 ERROR
CODE 1409" is output.
Avoidance: The UMERGE1 DMAP statements at lines 65, 66, and 67 of subDMAP
DYNSEN must be ALTERed to set the IOPT parameter to 1 as follows:
from:
to:
UMERGE USETD,EGMG,,,/EGMP/'P'/'G'/'E' $
UMERGE USETD,EGMG,,,/EGMP/'P'/'G'/'E'/1 $
4525
70.5
M 201, SFM 217, UFM 224, UFM 5199
Documentation/Optimization - DEQATN - UF
Input errors on the DEQATN Bulk Data entry often result in poor messages. The
following messages have been encountered when invalid symbols such as a "[" are
used or the restriction against large field format is violated on the DEQATN
entry: "USER FATAL MESSAGE 215 (PRER2O) BINARY OPERATORS CANNOT BE THE FIRST
SYMBOL FOUND IN AN ARITHMETIC LOGICAL EXPRESSION" or "SYSTEM FATAL MESSAGE 233
(PRSPOP) UNDERFLOW OCCURRED DURING PROCESSING OF OPERAND STACK" or "USER FATAL
MESSAGE 5199. ON THE ABOVE BULK DATA FREE FIELD CARD AN INTEGER OR A BCD FIELD
HAD MORE THAN EIGHT CHARACTERS".
Avoidance: Review the requirements of the DEQATN entry documented in the
MSC/NASTRAN User's Manual and modify the DEQATN entries as necessary.
4528
68
L - Segmentation Fault
Parallel Matrix Methods - SPARSE, PARALLE
In Version 67.5 of MSC/NASTRAN on the CONVEX C3800 computer, if parallel

sparse decomposition is selected, the job fails and no message is printed to
the F06 output file. The log file indicates a "Segmentation Fault" error in
the routine relcpuu.
Avoidance: Presently the only avoidance is to run MSC/NASTRAN within csh and
specify the csh command "limit concurrency 4" before execution. The error will
be fixed for Version 68 by limiting the maximum number of CPUs to 4 when using
parallel sparse decomposition.
4529
67.7
276 FILPOS EC 1044
Sequencer - SEQP, PARAM,NEWSEQ,6 - SFM 4
An error exists in the nested dissection option of the sequencer module. This
option is selected by setting PARAM,NEWSEQ,6 in Version 65E, 66, 66A, 66B, 67,
or 67.5 of MSC/NASTRAN. The option is also available by setting PARAM,NEWSEQ,8
in Version 67.5 whenever sparse decomposition is also selected. This error
causes the job to fail in the SEQP module and the message "SYSTEM FATAL MESSAGE
4276 FILPOS ERROR CODE 1044" to be output. The error occurs only when
superelement groups exist in the model and when the number of grid points in
any group is more than 1/4 or less than 1/3 of the total number of grids.
Avoidance: Other than selecting another sequencer option, there is no
avoidance.
4536
68
ELR for datablock FPS (output-twice)
DMAP - EQUIV, EQUIVX - UFM 1126 in CALL S
If the EQUIV or EQUIVX statement appears immediately after a CALL statement

then the message "USER FATAL MESSAGE 1126" may be incorrectly issued in the
subsequent loop. This is an error in the Last-Time-Used (LTU) logic.
(Version 67, 67.5 and 67.7 only)
Avoidance: An avoidance is to specify the PARAML module for the offending
datablock after the EQUIV (or EQUIVX statement). For example, if UFM 1126 is
issued for datablock PS then insert the PARAML DMAP statement as in the
following example.
CALL XXXX PG/PA,PS $
EQUIVX PA/PA1/-1 $
PARAML PS//'PRES' $
4538
68.0.0
Message, SFM 2199, UWM 4698
Nonlinear Analysis - ASETi, OMITi - Poor
If ASETi or OMITi entries are specified in SOL 66 or 106 and there are no
elements with linear material properties, then SFM 2199 and UWM 4698 are
issued. This error has been corrected in MSC/NASTRAN Version 68
by issuing the meaninful user fatal message 4423.
Avoidance: This is a user error. The avoidance is to remove all ASETi and
OMITi entries since nonlinear degrees of freedom can not be omitted. The
correction to SOL 66 and SOL 106 DMAPs results in the meaningful message "USER
FATAL MESSAGE 4423 A NONLINEAR ELEMENT IS ATTACHED TO AN OMITTED DEGREE OF
FREEDOM" being output.
4539
tack Error
68
Plotting - NEUPS - Missing Plot Output, S
If a plot file generated by the NEUPS utility can be displayed using the
SUN
PageView utility or other utilities, but is not able to be printed, then the
Postscript file contains too many data points in a single curve and the data
overflows the printer's memory.
Avoidance: Possible resolutions include:
1.
Increase the printer's memory (may not be feasible); or try on other
printers,
2.
Break a single long curve into a number of curves,
3.
Modify the NEUPS utility with the following changes.
In subroutine PLOT, change the following lines:
After
subroutine plot(x,y,i)
Add
save strkln
After
write (unit=ips,fmt=20) x, y,' lineto'
Add
strkln = strkln + 1
if( strkln.gt.50) then
write(unit=ips, fmt=10) 'stroke'
write(unit=ips, fmt=10) 'newpath'
4543
GL
Uniform Thickness
Elements - QUADR - Wrong Answers for Non-
The corner stress output for the QUADR and TRIAR elements due to membrane
forces are calculated and output for the average thickness. Thus the corner
stress output for non-uniform thickness elements is wrong.
Avoidance: In MSC/NASTRAN Version 67.5, the STRESS(CORNER) option for the
QUAD4 element may be used.
4545
68
CR300- UFM 4275
File Management Section - INIT SCRATCH, S
Logical names and their reference to physical files must be unique across all
INIT statements. Thus, if both SCRATCH and SCR300 are assigned to the same
physical file, then the job may fail and the message "USER FATAL MESSAGE 4275"
may be issued.
Avoidance: ASSIGN SCRATCH and SCR300 to different files.
4549
ocumentation
68
Documentation - CTRIAX6, GPWG - Missing D
For the axisymmetric TRIAX6 element, the Grid Point Weight Generator outputs
the c.g. for the modeled structure only . The calculated mass is the mass for
the entire structure of revolution. This is design intent. This error has been
addressed by including a comment under the description of the PARAM,GRDPNT
entry in the 2nd printing of the MSC/NASTRAN Version 68 Quick Reference Guide.
4551
68
on 7.7 - Installation Errors
Documentation - Application Manual, Secti
The following documentation errors exist in the Version 67.5 Section 7.7 of
the CRAY(UNICOS), CONVEX, and VAX(VMS) MSC/NASTRAN Application Manuals:
1) CRAY(UNICOS)
p. 7.7-5
p. 7.7-7
2) CONVEX
p. 7.7-5
p. 7.7-9
nastran.man file
n67ins should be n675ins.

%1f should be %1d.
n67ins should be n675ins.

The documentation should say move the nastran.p file and the
into the
/usr/man/catp directory.
p. 7.7-20 nast67 should be nast675.
3) DEC VAX/VMS
p. 7.7-14 The documentation on p. 7.7-14 should show "PRT=NO !" inste
ad of
"PRT=NO $".
p. 7.7-36 5 should be 4 on the Step 5 line.
p. 7.7-37 In the Step 7 section, "Steps 2 through 7" should read "Steps
2
through 6" and "Step 4"
should be "Step 3"
4555
68
Manual Documentation
Documentation - DTIIN - Incorrect User's
The MSC/NASTRAN User's Manual documentation for the DTIIN entry is incorrect.
The documentation currently indicates:
DTIIN DTI,DTINDX/DTI1,DTI2,DTI3,DTI4,DTI5,DTI6,DTI7,DTI8,DTI9,DTI10/
PARM1/PARM2/PARM3,PARM4,PARM5,PARM6,PARM7,PARM8,PARM9/PARM10 $
This should be changed to:
DTIIN DTI,DTINDX/DTI1,DTI2,DTI3,DTI4,DTI5,DTI6,DTI7,DTI8,DTI9,DTI10/
PARM1/PARM2/PARM3/PARM4/PARM5/PARM6/PARM7/PARM8/PARM9/PARM10 $
This error has been corrected in the Version 68 DMAP Module Dictionary.
4559
69
Documentation, UWM 4605
Miscellaneous - GPSTR1, MODAC2 - Missing
The following two user messages have the same number:

"USER WARNING MESSAGE 4605. MAXIMUM NUMBER OF MESSAGES HAVE BEEN ISSUED BY
GPSTR1 MODULE."
"USER FATAL MESSAGE 4605, INPUT MATRIX **** IS INCOMPATIBLE WITH ITS ASSOCIATED
OUTPUT LIST (I.E., TOL, FOL, LAMA, CLAMA)."
The latter message is correct since it is the one that is documented in the
4561
68
Documentation - OFP - Missing Output
Remark 2 of the MSC/NASTRAN User's Manual description of the OFP DMAP statement
states that data blocks can be output by OFP. However, parameter OP1 does not
honor data blocks LAMA, OEIGS, LAMX, CLAMA, and OGPWG. This error has been
corrected in the Version 68 DMAP Module Dictionary.
4563
starts
68
Restarts - SUBCOM, CBEAM - Inefficient Re
When the SUBCOM Case Control command is added to a Structured Solution

Sequence (SOL 101 through 200) data recovery restart, and the model contains
CBEAM elements, the SEKRRS subDMAP is unnecessarily re-executed in the
restart. (V67+ only).
Avoidance: The error may be avoided by using one of the following actions:
1) Use PARAM,SERST,SEDR in the restart run,
2) Replace the SUBCOM with a SUBCASE that references an equivalent
load.
3) Use an Unstructured Solution Sequence and perform a manual restart.
4566
Composites - GPSTRESS, PCOMP - Wrong Answers
Grid point stress output is not supported for composite elements. If grid
point stress output is requested for a SURFACE containing composite elements
meaningless answers (i.e., 1.E+30) are output for the grid points attached to
composite elements.
4572
68
Accounting file
Miscellaneous - ACCT - Incorrect label in
The header of the last field of the MSC accounting file (created by the "acct"
keyword) should indicate "Min" not "Sec".
Avoidance: The MSC/NASTRAN Version 67.5 script should be changed as follows
Original definition (line 521 on Sun):
echo ' ACC3="Monthly-Total-CPU-Sec"'
Change to:
echo ' ACC3="Monthly-Total-CPU-Min"'
4573
ent Restart
68
Aeroelastic Analysis - RESTART - Ineffici
If an M, K aero pair is added to a restart run in Solution 145 or 146, then

the existing aerodynamic matrices are unnecessarily recomputed.
4574
utput
68
Nonlinear Analysis - DBC, ESE - Missing O
On the CONVEX Version 67.5 release of MSC/NASTRAN if a nonlinear analysis

contains a request for element strain energy output, then no data recovery
output is written to the .XDB file.
Avoidance: Remove the ESE request.
4575
wers
70
Documentation - CQUAD4, PSHELL - Poor Ans
A remark should be added to the MSC/NASTRAN User's Manual description of the

PSHELL entry. If transverse shear flexibility is specified for a model with
curved shells where the loading is dominated by twist, the results for a coarse
to medium mesh model may be inaccurate and the results will diverge as the mesh
is refined.
Avoidance: MSC/NASTRAN Version 68.2 and later releases include "Shell Normals"
an enhancement which corrects this deficiency. This enhancement is documented
in the Version 69 Release Guide. Note that by default shell normals are not
activated they must be explicitly requested. The Quick Reference Guide
description of the CQUAD4 and PSHELL entries should be updated to provide
guidance for the above situation. Permanent documentation, not release guides,
should
4576
Material Nonlinear Analysis - NLPCI, RIKS, MRIKS - UWM 6195
When either the RIKS or MRIKS method is used in MSC/NASTRAN Version 67 and
later systems, the message "USER WARNING MESSAGE 6195 SOLUTION HAS REGRESSED TO
AN EARLIER LOAD STEP" may be issued and the solution will not adapt.
Avoidance: Specify the CRIS method on the NLPCI entry.
4582
Elements - CMASSi, SEQP- Poor Message, UFM 2012
If a CMASSi entry (and possibly other scalar elements) specify the "0" degree
of freedom of a grid point, the job fails and the message "USER FATAL MESSAGE
2012 GRID POINT *** SAME AS SCALAR POINT" is issued.
Avoidance: Specify a valid degree of freedom on the CMASSi entry.
4584
67.5.0.1
gmentation Violation
Postprocessing - OUTPUT2, PARAM,POST - Se
Depending on the machine and operating system level, an error may be

encountered when writing very large unformatted OUTPUT2 and OUTPUT4 files.
This error causes the message "Segmentation Violation = Signal 11 Code 3" to
appear in the log file, with the result that the OUTPUTi files are incorrect.
This error has been corrected in Version 67.5.01. Version 67.5.01 is delivered
to all new Sun clients and is available on request to all existing clients.
This error has been observed on the following hardware/software combinations:
MSC/NASTRAN
Version
SunOS
Version
Machine
Status
V67.5
4.1.3 Ver. 3
4586
- UFM 505
68
SparcStation 2
Sparcstation 10
Sparc server
Fails
Fails
File Management Section - ASSIGN, INIT,
If an FMS statement begins with any blank space, then the job fails and
the
message "USER FATAL MESSAGE 505 (XCSA) CONTROL CARD 'FMS STATEMENT' IS ILLEGAL"
is output.
Avoidance: Enter the FMS statement beginning in field 1.
4606
Postprocessing - OUTPUT2 - SFM 1222
If an OUTPUT2 neutral file is created and the ITAPE=-9 option is not used to
write an EOF, then the following messages appear in the RCOUT2 job print when
converting the file back to binary form:
*** SYSTEM FATAL MESSAGE 1222 (LDRTRN) AN UNEXPECTED END OF FILE WAS DETECTED
ON A NEUTRAL FILE DURING A DBLOAD OPERATION
USER INFORMATION: THIS ERROR TERMINATES PROGRAM EXECUTION AND GENERALLY OCCURS
WHEN THE DBUNLOAD JOB FAILS DURING NEUTRAL FILE CREATION
USER ACTION: REVIEW NEUTRAL FILE CREATION JOB FOR FATAL MESSAGES
*** SYSTEM INFORMATION MESSAGE RC0008 (RCOUT2)
THE END-OF-FILE FATAL MESSAGE WRITTEN ABOVE OCCURRED DURING DATA BLOCK NAME
PROCESSING.
PROGRAMMER INFORMATION:
1. THIS ERROR GENERALLY INDICATES THAT THE LAST OUTPUT2 OPTION USED WAS NOT
-9
2. THE OUTPU
4609
GL
ESTARTS - Wrong Answers
Superelements - TEMP(LOAD), TEMP(INIT), R
The following error with thermal loads may occur in restarts with the
superelement unstructured Solution Sequences (61-99) or restarts with
PARAM,SERST,SEMI (or SEDR) in Solutions 101-200. If the initial temperature is
not specified (i.e., TEMP(INIT) is not present) in the initial run (cold start)
loads are not generated (i.e., SELG and SELR are not requested), and in the
restart run TEMP(LOAD), TEMP(BOTH) or TEMP is specified but no SEMG requests
are made (for the superelements processed in the cold start), then the thermal
loads are incorrect. This error occurs because the EST data block, which is
used in generating thermal loads and depends on the TEMP(INIT), is not
regenerated in the restart. It is only generated if SEMG is requested.
Avoidance: Specify the same TEMP(INIT) in th
4610
- UFM 3055
68
Static Analysis - PARAM,MPCF, PARAM,INREL
If inertia relief is requested in SOL 101 (PARAM,INREL,-1) in conjunction

with "PARAM,MPCF,YES" in MSC/NASTRAN Version 67.5, then the job fails and the
message "USER FATAL MESSAGE 3055 AN ATTEMPT TO MULTIPLY OR MULTIPLY AND ADD
NON-CONFORMABLE MATRICES TOGETHER WAS MADE IN MODULE MPYAD". This is a
version 67.5+ error only.
Avoidance: If the model does not contain superelements (i.e., residual only),
the following DMAP Alter may be applied to avoid this error:
COMPILE SEDRCVR SOUIN=MSCSOU LIST NOREF
ALTER 16,16 $ CHANGE PG TO PJ1
UPARTN USET,PJ1/PM,,,/'G'/'M'/'N'/1 $
A DMAP avoidance is under investigation for models that contain superelements.
4611
67.7
UWM 6444, SFM 1208, SFM 1214
DMAP - OUTPUT2, INPUTT2 - Neutral Format,
Using the NEUTRAL FORMAT option of OUTPUT2 and INPUTT2 in DMAP may cause the
run to fail and issue the following warning and fatal messages: "UWM 6444
(INPTYP) - THE FILE ASSIGNED TO UNIT = CONTAINS DATA THAT IS INCONSISTENT WITH
FORM = FORMATTED", "SFM 1208 (LDSTR) - ERROR SETTING UP TRANSLATE TABLE AT LOC
= " and "SFM 1214 (LDRTRN) - ERROR TRANSLATING DATA FROM NEUTRAL FILE READ FOR
SUBROUTINE LDSTR".
Avoidance: Encountering this error is very unlikely and there is no a priori
avoidance. If the error is encountered, some possible ways to workaround this
problem are as follows:
1. Use the RCOUT2 utility to convert the neutral file to a binary file. Then
use the binary option of INPUTT2 to read the file.
2. Rerun the initial OUTPUT2 job with a different neutral record le
4612
67.7
444, SFM 1208, SFM 1214, SFM 2190
Postprocessing - OUTPUT2, INPUTT2 - UWM 6
The INPUTT2 module may fail when attempting to read an input file formatted
with the new neutral option in MSC/NASTRAN Version 67.5. Messages that are
evidence of this error include "USER WARNING MESSAGE 6444", "SYSTEM FATAL
MESSAGE 1208", "SYSTEM FATAL MESSAGE 1214", and "SYSTEM FATAL MESSAGE 2190
(INPTN2) ILLEGAL VALUE FOR KEY".
Avoidance: Use the RCOUT2 utility to convert the neutral file to a binary
file. Then use the binary option of the INPUTT2 module to read the file.
4617
e and Date
68
Miscellaneous - - Missing Completion Tim
The date and time that MSC/NASTRAN finishes is not printed to the .log file on
the DECstation ULTRIX Version 67R2 system.
Avoidance: Line 331 in the ".shl" should be modified.
command and replace as follows:
Remove the "exec "
echo "/bin/time ${LOC_EXE}/${EXE_NAME} ${asgf} {$mem}"

4618
69
BS - Wrong Answers, Missing Output
Acoustic Analysis - ACSRCE, CHACAB, PACA
If an ACSRCE Bulk Data entry has the same DAREA ID (field 3) for loads applied
to structural grid points then wrong answers or missing output may result.
Avoidance: Define a RLOADi or TLOADi Bulk Data entry with an SID (field 2) and
DAREA ID (field 3) which is unique with respect to the ACSRCE entry. Then
define a DLOAD Bulk Data entry which is referenced by the DLOAD Case Control
command and combines the RLOADi (or TLOADi) and ACSRCE entries.
4619
ng Answers
68
Matrix Methods - SPARSE DECOMP, FBS - Wro
If the sparse solver and FBS are run more than once and 2 by 2 pivots are
necessary for some of the FBS operations, there may be wrong answers. Positive
definite matrices do not require pivoting operations. Thus, this error is
unlikely in the delivered solution sequences. The DMAP alter RFLAG.V675
delivered with Version 67.5 does not encounter this problem if superelements
are not present.
Avoidance: Do not use sparse decomposition with alters such as the Lagrange
multiplier method that may produce indefinite matrices.
4620
67.7.0.1
Divide By Zero, Missing Data Blocks
Aeroelastic Analysis - AMG, UFBS, ZONA -
The supersonic aerodynamic code (ZONA) contained in the Aero II option can
fail when the inverse Mach line emanating from a control point of one bax is
almost perfectly aligned with the leading edge of another box. On some
machines, the error is evidenced by a divide by zero check in the AMG module.
On others, it produces missing datablocks in the UFBS module.
Avoidance: Experience has shown that a slight change in the requested Mach
number (e.g., from M=2.4 to M=2.41) causes the error to go away and good
answers result.
4621
Plotting - AERO1 - No Plottable Structural Elements Exist
If the user desires a plot of only the aerodynamic model and specifies SET
1=AERO1, the following message appears:
NO PLOTTABLE STRUCTURAL ELEMENTS EXIST IN SET 1
Avoidance: Adding any other element to the SET, such as SET 1=AERO1,QUAD4,
results in a plot of the aerodynamic model and the elements specified.
4623
70.5.2
45, Poor Message
Dynamic Response Analysis - TRD1 - UWM 30
If a job fails in the TRD1 module due to insufficient time the message "USER
WARNING MESSAGE 3045 INSUFFICIENT TIME TO COMPLETE THE REMAINING ** SOLUTION(S)
IN MODULE TRD1" is output. This message gives no indication of the amount of
time necessary to complete the module. This message is also output by modules
AMP, CEAD, FA2, FRRD1, and TRD2.
Avoidance: Increase the amount of time on the TIME command.
4626
68
Documentation - LOAD - Limitation Removed
Remark 6 under the MSC/NASTRAN User's Manual and Quick Reference Guide
description of the LOAD entry is no longer applicable. In MSC/NASTRAN Version
66 the limit of 300 Si, Li pairs was removed.
4627
M 5429
67.7
Eigenvalue Analysis - EIGRL, LANCZOS - UF
The time estimated to complete a LANCZOS iteration may be very conservative
for large problems. Thus, a run where ample time is specified may
inappropriately encounter the message "USER FATAL MESSAGE 5429, INSUFFICIENT
TIME TO START LANCZOS ITERATION".
Avoidance: Specify a very large value on the TIME entry.
4629
68
on 7.7.2 - Installation
Documentation - Application Manual, Secti
The command "dd if=/dev/extape of=/tmp/MSC675 bs=8b" (documented on page 7.7-2

of the MSC/NASTRAN Application Manual, Version 67.5 for CRAY UNICOS computers)
which is to load the file from the delivery tape when an expander tape drive is
used, does not work. `
Avoidance: Use the command "dd if=/dev/extape of=/tmp/MSC675 bs=32768" as
documented on the same page.
4631
Not Found
68
Miscellaneous - Shell Script - Data File
If the name of the .dat file happens to match the beginning of the directory
name, and that directory is included in the 1st argument (jid), line 184 of the
Convex script file will remove the file name portion from the directory path,
and thus the data file will not be found: For example if you have a data file
named "abc.dat" in directory /usr1/jones/abc_dir, then submitting a V675 job
as:
nast675 /usr1/jones/abc_dir/abc
will yield:
Data file /usr1/jones_dir/abc.dat not found.
Avoidance:
Change the the following (line 184) in the script:
(add a "\$" sign after the "name")
from
jid_dir=ècho ${jid} | sed "s;\/$name;;"`
to
jid_dir=ècho ${jid} | sed "s;\/$name\$;;"`
also change the name into nametmp
old line:
jid_dir=ècho ${jid} | se
4634
swers
69
Cyclic Symmetry - EIGRL, CYSUP - Wrong An
In cyclic symmetry analysis, the Lanczos method of eigenvalue extraction may

incorrectly apply "SUPORT" logic which is selected by the CYSUP Bulk Data
entry. In one problem, the CYSUP entry resulted in the first eigenvalue of the
second Harmonic (a flexible mode) being set to 0 incorrectly. The eigenvector
for this mode is correct.
Avoidance: Do not use the CYSUP entry with the Lanczos method of eigenvalue
extraction.
4637
70.7
, Wrong Answers
DMAP - VECPLOT - Incorrect Matrix Trailer
When the VECPLOT module is used to generate a matrix containing the geometry of
the model, the resulting matrix may have an incorrect trailer value for the
number of rows. If this is the case, subsequent modules that use the matrix may
fail or give incorrect results.
Avoidance: The following DMAP Alter demonstrates the use of the VECPLOT module
to generate a matrix called OUTGEOM with the model geometry and uses the MODTRL
module to correct the trailer.
VECPLOT ,,BGPDT,EQEXIN,CSTM,,/OUTGEOM/0/3 $
MODTRL OUTGEOM///LUSET $
4644
ng Output
68.2
Acoustic Analysis - PARAM,FLUIDMP - Missi
The panel participation factors output are missing when the modal participation
factors are requested for panels in acoustics, the request is for a selected
set of grids, and the model consists of only fluid elements. This error exists
in Version 67.5 and 68. Version 67 users should refer to Error 3672 before
proceeding.
Avoidance: To avoid this error in Version 67.5, apply the DMAP Alter listed
below.
COMPILE SEMFREQ SOUIN=MSCSOU NOREF
ALTER 125,125
EQUIVX OG/OA/NOA $
IF (NOA>-1) UPARTN USET,OG/OA,,,/'G'/'A'/'S'/1 $
ALTER 148
IF ( FLUIDMP<NFEIG ) THEN $
MATGEN ,/FTMP/6/NFEIG/0/FLUIDMP $
PARTN
UHFF,,FTMP/,UHFF1,,/1 $
EQUIVX UHFF1/UHFF/-1 $
PARTN
PHFA1,FTMP,/,,PHFA2,/1 $
ELSE $
EQUIVX PHFA1/PHFA2/-1 $
ENDIF $
ALTER 155,162
To a
4654
SORT1 Output
68
Documentation - PARAM,CURVPLOT - Missing
The documentation for PARAM,CURVPLOT does not indicate that it is a valid

parameter for Solutions 71, 72, 111, and 112. This parameter must be specified
to obtain SORT1 output in the aforementioned solution sequences. This
documentation error is corrected in the 2nd printing of the Version 68 Quick
Reference Guide.
4655
68
DMAP - COMPILE, XREF - Missing Output
The MSC/NASTRAN User's Manual for the COMPILE statement states that a
cross-reference is available for an NDDL COMPILE. The Version 67 documentation
should be amended as follows to indicate the specific circumstances when the
NDDL X-REF is available. This capability has been added to Version 68, please
see error 2869.
[Add to Remark 6.]
d. The cross-reference is produced only when the NDDL source is provided

directly in the input file. It is not produced when the source is obtained
from a SOUIN command. For example, the following two-run sequence produces a
cross-reference of NDDLOLD. Note that the cross
reference can be large. The cross-reference produced for the NDDL of the
Structured Solution Sequences is more than 1000 pages in length. The cross
reference for NDDLOLD p
4656
68
DMAP - RESTART, DELETE - Wrong Answers
The DELETE module is skipped in an automatic restart if the datablock(s) to

be deleted exist on the database. Note that MSC/NASTRAN's solution sequences
use the RESTART module to delete data blocks from the database on a restart
run. Thus, this error only affects user DMAPs.
Avoidance: Set system cell 109 to 1 before the DELETE and back to 0
immediately after the DELETE.
For example, to delete data blocks A and B:
PUTSYS(1,109) $
DELETE /A,B,,, $
PUTSYS(0,109) $
4663
swers
70.7
Old Design Sensitivity - DSCMR - Wrong An
For large problems (many elements) with many design variables, the DSCMR
sensitivity coefficient matrix may have zero values for design variables that
should have non zero values of sensitivity coefficients. This problem has
been addressed by the solution 200 material sensitivity project in Version
70.7.
Avoidance: If the user suspects that there are zero values in the sensitivity
coefficient matrix that should be non zero, then reduce the number of design
variables requested and compute a new DSCMR matrix.
4670
67.5
DMAP - DIAGONAL - Missing Documentation
There is no mention in the Version 67 "Nonupward Compatible Features" that the

DIAGONAL DMAP module changed and that these changes may result in a nonupward
compatibility for user DMAPs. Starting with Version 67, the OPT parameter was
changed from BCD to a CHARACTER input. Thus, the values must be enclosed in
quotes. If a value is not enclosed in quotes, MSC/NASTRAN interprets the input
as a variable and sets the variable to the default value of 'COLUMN'. Since
the "Nonupward Compatible Features" for Version 67 documentation will not be
re-issued, this error is considered addressed with this error report.
4677
ong Answers
68
Lagrange Multiplier - CVISCi, CDAMPi - Wr
The Lagrange Multiplier DMAP alter delivered in the file RFLAG.V675 in Version
67.5 results in wrong answers for modal frequency response analysis when the
models contains viscous dampers.
Avoidance: Change RFLAG.V675 as follows:
COMPILE GKAMJR $
$ . . . . skip down about 20 lines, replace following statement
$ IF (YES2SET=-1) THEN $ insert next statement in its place

IF (false) THEN $
Further client information indicates that this alter still does not work.
4684
Nonlinear Analysis - NLEMG - Load Increment is Skipped
In solution 106 if param,lgdisp is set to 1 and no nonlinear elements exist,

then after a stiffness update the load increment will skip to the next
increment.
Avoidance: Either add a nonlinear element or place yes in 9th field of the
NLPARM entry.
4687
g Answers
Grid Point Stress - GPSTR1, QUAD4, TRIA3, QUAD8, TRIA6 - Wron
If grid point stress output is requested and the edge point is attached to a
linear plate element (QUAD4 or TRIA3), the grid point stress calculation at
this edge point may be incorrect. The error only occurs when the other end of
the interior line segment connecting to the edge grid is attached to a higher
order shell element (QUAD8 or TRIA6). In this case, the stress contribution of
the interior grid point is not included in the grid point stress calculation at
the edge point.
Avoidance: If the edge grid point is connected to a QUAD4 element, then
requesting corner output resolves this problem. Unfortunately, corner output
is only available starting with Version 67.5. If the edge point is connected
to a TRIA3 element or Version 67.5 is not available, then there is no avoidance.
4692
67.52
- No Access Allowed
Installation - Incorrect File Permissions
The delivery tape for MSC/NASTRAN Version 67.5 for the CRAY Y-MP (UNICOS) was
incorrectly written. In particular, all file permissions for 'other' access
are blank, i.e., no access is allowed. The error is corrected for all new
installations by the tape labeled "V67.5 MSC/NASTRAN (r2)".
Avoidance: The error may be corrected by executing the following commands:
cd /msc
cd bin
find . -perm
find . -perm
find . -perm
find . -perm
# or the actual "repository" directory.

770
660
750
640
-exec
-exec
-exec
-exec
chmod
chmod
chmod
chmod
777
666
755
644
{}
{}
{}
{}
\;
\;
\;
\;
If the repository and installation directories are not the same, execute the
following additional commands:
cd /msc/nast675
# or the actual "installation" directory
find . -perm 770 -exec ch
4695
69
TRESS Discontinuity Output, SWM 6247
Grid Point Stress - ELSDCON - Missing GPS
When requesting grid point stress discontinuities, and more than one type of
element is in the surface or volume, the following message is received:
"SYSTEM WARNING MESSAGE 6247 (STD2HD/S), THERE IS AN INCONSISTENT POINTER TABLE

FOR SCR4 FILE...CHECK POINTER TABLE 5 FOR SCR4 FILE"
The run then terminates.
Avoidance: Only use one element type in a surface or volume.
4696
68
Aeroelastic Analysis - SPLINE - UFM 2262
If a SPLINE Bulk Data entry specifies BOX1 and BOX2 or ID1 and ID2 such that
there are no aerodynamic boxes splined, the code does not detect the user
error. The job will subsequently fail and issue the misleading messages "USER
FATAL MESSAGE 2262 (GIPTSD) SPLINE **** INCLUDES AERO BOX INCLUDED ON AN
EARLIER SPLINE".
Avoidance: Correct the offending SPLINE entry.
4700
ing Output
68
Elements - QUAD4(CORNER) - UWM 6418, Miss
If a Case Control data recovery request is made for QUAD4 corner and center
output within the same run, then the message "USER WARNING MESSAGE 6418" is
output to warn the user that only one output type is supported per run. The
hierarchy of the request that takes precedence is documented in the MSC/NASTRAN
Release Notes for Version 67.5. The user warning message contains null
characters which may cause some editors to fail and all subsequent output to be
missing.
Avoidance: Correct the Case Control output requests so that they all request
either corner or center output.
4701
4276, EC 3012
68
Frequency Response Analysis - FRRD1 - SFM
Under unusual circumstances a frequency response run (Solution 26) fails in

the FRRD1 module and the message "SYSTEM FATAL MESSAGE 4276 QOPEN ERROR CODE
3012" is issued. This error occurs when there are multiple calls to FRRD1
where the first call solves for a single subcase (load case) or a single
frequency and a subsequent call solves for multiple frequencies and multiple
subcases (load cases).
Avoidance: In Solution 26 the error may be avoided by reordering subcases.
The subcases that solve for multiple frequencies and multiple subcases (load
cases) must be placed first in the Case Control Section.
4703
ong Answers
Nonlinear Transient Analysis - TSTEPNL, TLOAD1 - UFM 4605, Wr
If the "AUTO" method is selected on the TSTEPNL entry for nonlinear transient
analysis and the excitation function on the TLOAD1 entry specifies an enforced
displacement, then the results are unpredictable. In some cases, the job may
fail with the following error message:
USER FATAL MESSAGE 4605. INPUT MATRIX PST IS INCOMPATIBLE WITH ITS ASSOCIATED
OUTPUT LIST (I.E., TOL,FOL,LAMA,CLAMA).
In other cases, the run may generate wrong answers. Furthermore, the results
may not be repeatable from run to run even on the same machine.
Avoidance: Use the "ADAPT" method, which is the default method.
4707
wers
67.5
Restarts - MATi, PCOMP, PELAS - Wrong Ans
If a change is made to the upstream superelement structural damping terms (GE

field on MATi, PCOMP and PELASi entries), then the structural damping matrix,
K4GG is not reassembled to include the upstream structural damping changes.
This results in wrong answers in dynamic response solution sequences.
Avoidance: Use Version 67.5 or higher for both the COLD start and RESTART. If
you must use Version 67 (or Version 67R2), then insert the following alter
which will force K4GG to be reassembled on restart.
COMPILE SEMRB SOUIN=MSCSOU NOLIST NOREF
ALTER 5
PUTSYS (1,109)
ALTER 10
PUTSYS (0,109)
ENDALTER
4712
68.1
Cyclic Symmetry - RESTART - Wrong Answers
Restarts to compute modes for additional harmonics does not work correctly. In
the RESTART, MSC/NASTRAN calculates the eigenvalues correctly but prints out
the eigenvectors for the harmonics from the initial run.
Avoidance: To obtain the eigenvectors for the additional harmonics, apply the
following alter:
COMPILE MODECYC SOUIN=MSCSOU LIST NOREF
ALTER 28
PUTSYS(1,109) $ ...FORCE EXECUTION
ALTER 30
PUTSYS(0,109) $ ...RESET
ENDALTER
COMPILE SEDISP SOUIN=MSCSOU LIST NOREF
ALTER 130
PUTSYS(1,109) $ ...FORCE EXECUTION
ENDALTER
4717
g Answers
68
Superelements - RESTART, SEEXCLUDE - Wron
The automatic restart logic in the SSS does not recognize the SEEX case control
command. If the only change to a model is to attempt to exclude a superelement
(or set of superelements) on a restart, then the program does not perform the
necessary operations and the answers from the original run are used.
Avoidance: Make a change to the superelement immediately downstream from the
superelements affected by the SEEX command. For example, add a disjoint GRID
point to the downstream superelement. The automatic restart logic then
reprocesses the downstream superelement and correctly processes the SEEX
command.
4718
nite CPU Loop
68
File Management Section - DBUNLOAD - Infi
Attempting to DBUNLOAD a data block in the neutral format that is not defined
in the NDDL may result in the program entering an infinite CPU loop.
Avoidance: Do not use the DBUNLOAD neutral option when outputting non-NDDL
data blocks.
4721
68
entified Keyword on IBM RS/6000
Miscellaneous - Shell Script Error - Unid
An error exists in the IBM RS/6000 operating system that causes the NASTRAN
shell script to incorrectly translate keywords resulting in an "unidentified
keyword" error message being output during submittal of the NASTRAN job. The
problem lies with the translate function. If a keyword is specified in
uppercase in the nast675rc file, then it will be transposed by one character.
The following example of the "tr" command illustrates the error:
echo "FrEd" | tr '[a-z]' '[A-Z]'
gRfD
Thus, the valid keyword SDIR is translated to "tejs" and an unidentified
keyword entry error results.
Avoidance: This error may be overcome by using the "tr -A" option.
4723
Documentation - OUTPUT2, RCOUT2 - Poor Message, SFM RC0005
The OUTPUT2 neutral option is driven by the NDDL description for the datablock
to be neutralized. An incorrect NDDL description results in the following FATAL
message during the RCOUT2 run.
0*** SYSTEM FATAL MESSAGE RC0005 (RCOUT2)
ILLEGAL KEY VALUE DETECTED
USER INFORMATION:
EXPECTED KEY VALUE: GREATER THAN OR EQUAL TO
DETECTED KEY VALUE:
-3
FATAL ERROR CODE - INVALKEY 0004
FATAL ERROR
Although the consequences of attempting to output a non-NDDL data block using

the neutral option is not documented, the MSC/NASTRAN Release Notes for Version
67.5 clearly documents that only NDDL data blocks may be output with the
neutral option.
Avoidance: The new documentation for OUTPUT2 in Appendix C of the MSC/NASTRAN
Release N
4727
68
Inefficient Decomposition
Optimization/Design Sensitivity - FRRD2 -
In frequency response, SOL 200, module FRRD2 may do unsymmetric decomposition

when symmetric decomposition should be used. Although answers are unaffected,
the processing is inefficient.`
4730
ng Labels
69
Nonlinear Analysis - PUNCH, SORT2 - Missi
In Solution 66 and 106 grid ids and element ids are missing from the punched
output file whenever SORT2 output is requested. The missing element ids and
grid ids may be obtained in Version 69 by specifying system(210)=1.

4731
Accounting
67.5
Miscellaneous - Shell Script - Incorrect
On earlier maintenance levels of AIX 3.2, the date(1) command changed its
default output format - the command no longer displayed the time zone. As a
result, the information written to the accounting file is missing the time
zone. This results in all items on the line after the time zone to be
misinterpreted. This is manifested in the accounting file by the last two
fields on each line doubling with each run until the dc(1) command blows up and
corrupts the accounting file.
This error is present at AIX 3.2.0, it may also be present at level 3.2.1. The
error is corrected at AIX 3.2.2 and above.
Avoidance: Upgrade to AIX 3.2.2 or beyond. The accounting file may be
corrected by deleting the lines which
do not match the fourteen field format described in the header of the file.
4733
Nonlinear Analysis - PSOLID,CORDM - Wrong Answers
In nonlinear geometric analysis, if the CORDM field on the PSOLID entry is set
to 0 (basic coordinate system), then the stresses for the corresponding solid
elements printed under the linear format will be incorrect since they are
transformed to the basic system using small angle theory. The stresses printed
under the nonlinear format are still correct since they are always printed in
the element coordinate system. Note that in Version 68 the default output
coordinate system for solid elements has been changed to the basic coordinate
system. In Version 68 SYSTEM(204) may be set to -1 to change the output back
to element coordinate system.
Avoidance: Use the default CORDM value on the PSOLID entry when performing
geometric nonlinear analysis. In this case, the stresses will be printed
4734
68
ss Output Not Sorted
Miscellaneous - STRSORT, PARAM,S1G - Stre
When PARAM,S1G,1 is specified, the stresses at the grid points are not sorted
as requested. The stresses are output in the order of the grid IDs.
4737
67.0.1
G, MDCASE - Missing Output
Optimization/Design Sensitivity - BUCKLIN
On the CRAY C-90 MSC/NASTRAN Version 67.7 system, no data recovery results will
be output for the buckling subcase of a design optimization/sensitivity
analysis. This error has been corrected for the residual structure in the
Version 67.7.0.1 system.
4740
), OS 5.0.1
67.5
Security - Authorization - SGI(Challenger
The usual "sysinfo -s " command as documented in Section 7.7 of the MSC/NASTRAN
Application Manual for SGI Computers does not return a correct machine ID under
Version 5.0.1 of the IRIX operating system.
Avoidance: Log on as superuser and enter the following commands:
systune -i
$ this takes you into the Kernel tuning tool
use_old_serialnum 1
exit
then use auto config and reboot.
After doing this, sysinfo -s will return the correct ten-digit serial number.
4741
68
Composites - PCOMP - Infinite CPU Loop
When modeling a sandwich or honeycomb structure with PCOMP and MAT1 entries,
setting the modulus of elasticity E to 0.0 for the core's material may result
in MSC/NASTRAN entering an infinite CPU loop on some computers. In MSC/NASTRAN
Version 68 USER FATAL MESSAGE 6662 is issued if the modulus of elasticity is
entered as zero.
Avoidance: Set E to a relatively small value or use a MAT2 entry with
relatively small Gij's to model the core.
4747
e Analysis
68
Documentation - DPHASE- Frequency Respons
Remark 5 on page 411 of the MSC/NASTRAN Quick Reference Manual and page 2.4-204
of the Version 67 MSC/NASTRAN User's Manual for the DPHASE Bulk Data entry
should be deleted. DPHASE entries can be applied to loads generated by the
LSEQ entry in frequency response analysis.
4748
GL
Miscellaneous - IFP - No Error Message
The character type and other input types of fixed field Bulk Data input are
designed not to allow embedded blanks and they must lie completely within the
designated field. If any embedded blanks occur within any input, a UFM 300
message is to be issued. However, if the embedded blank(s) are preceded by the
characters D, E, + or -, then MSC/NASTRAN does not detect the input error.
MSC/NASTRAN will combine the 2 fields into a single input data. Two examples
follow. The input error in the first example is correctly fielded by
MSC/NASTRAN by issuing USER FATAL MESSAGE 300. The input error in the second
example is not correctly fielded, and in this case a character string of "PID
9" is assigned to LABEL.
. 1 ..
DVAR
2 ..
3 ..
4 ..
4750
68
SFM 4276, EC 3001
5 ..
6 ..
7 ..
8 .
Optimization/Dynamic Sensitivity - LSEQ -
If multiple LSEQ entries are used in a dynamic sensitivity analysis, the job
fails and the following error message is output:
SYSTEM FATAL ERROR 4276.GREAD
ERROR CODE 3001
Avoidance: Reference all loads on a single LSEQ entry.

4752
ent Restart
GL
Nonlinear Analysis - MPC, MCE1 - Ineffici
If there are multiple subcases in a nonlinear statics restart run, and there
are MPCs in the model, the MCE1 module is reexecuted for each subcase. This is
true even if the MPCs are not modified from the coldstart run. If the MPC is
not changed on the restart run, the MCE1 module should only be reexecuted for
the first new subcase. This is because the transformation matrix between the m
and n sets is not saved in the cold start run. Subsequent subcases should not
reexecute the MCE1 module unless the MPC has been changed.
Avoidance: If the restart run has more than one new subcase and the MPC has
not changed from the coldstart run, then insert the following DMAP alters to
avoid this situation:
COMPILE NLSTATIC,SOUIN=MSCSOU,NOLIST,NOREF
ALTER 13 $
TYPE PARM,,I,N,FIRST=0 $
ALTER
4753
67
ble Wrong Answers
Old Design Sensitivity - BUFFSIZE - Possi
On the SUN and possibly other machines, if the old dynamic design sensitivity
capability is used and a non-default buffsize is specified, then the
sensitivity coefficients may be wrong. This problem has been observed on the
SUN computer for very large problems. The only obvious indication of an error
is that different sensitivity coefficients for the same design variables may be
obtained by using different sets on the SET2 entry.
Avoidance: Use the default BUFFSIZE.
4758
68
g Answers in the XDB
Nonlinear Analysis - DBC - SWM 6065, Wron
In a nonlinear analysis, if the model contains more than one element type
(e.g., QUAD4 and TRIA3) and "PARAM,POST,0" is used, then the results in the
graphical database (xdb) may be incorrect. This error has no effect on the
printed results in the F06 file. If this error occurs, then the following
messages appear in the F06 file. This error occurs in all Version 67.5
systems.
SYSTEM
DBCMSG
OUTPUT
SYSTEM
DBCMSG
OUTPUT
WARNING MESSAGE 6065 (DBC)

ERROR MESSAGE 23 FROM SUBROUTINE GRIDBK
LIST SYNCHRONIZATION PROBLEM FOR NLLF VALUE = xxx , POSITION = y
WARNING MESSAGE 6065 (DBC)
ERROR MESSAGE 23 FROM SUBROUTINE ELMBLK
LIST SYNCHRONIZATION PROBLEM FOR NLLF VALUE = xxx , POSITION = y
Avoidance: Request displacement output for at least one grid point for all sub
4760
SFM
67.7.0.1
Acoustic Analysis - ACMG - Wrong Answers,
Acoustic models that have structural interface points with an output coordinate
system defined other then the basic, fails with a floating point error in
module ACMG or produce incorrect answers. Note that this error is not
repeatable on any other machine. It is also not repeatable in V67R2 CRAY YMP.
Avoidance: Do not specify an output coordinate system.
4765
Poor Answers
68
Heat Transfer - RF61D01, PARAM,HEATSTAT -
There is an error in the stiffness matrix formulation for the QUAD4 element,
which only occurs after the approach is changed during the same execution. The
two possible approaches are heat transfer and structural analysis. Different
Gauss integration locations have been chosen for each approach. If the approach
is changed, and the executable is not reloaded, then wrong locations are used.
The effect is answers of less accuracy. In Version 64 and earlier releases of
MSC/NASTRAN, frequent link switches avoided this error. In Version 65 and
higher, this error only occurs in SOL 61 (with RF61D01), SOL 101 (with PARAM
HEATSTAT) and user DMAPs which change SYSTEM(56).
Avoidance: There is no user avoidance which allows QUAD4's to have both
approaches in one execution. If QUAD4's are needed,
4766
68
t Link Not Redefined
Documentation - Installation Script - Sof
If there is an existing 'nastran' or 'emas' command (soft link) in /usr/bin,

the ninstall and einstall scripts will not redefine the command. Thus, users
will execute the previous version of MSC/NASTRAN or MSC/EMAS instead of V67.5
or V2.5 This problem occurs on all 67.5, 2.5 UNIX platforms except SGI and
INTEL.
Avoidance: Manually redefine this soft link to point to {install
directory}/bin/nast675,emas25.
4768
68
issing Timing Constants
DMAP - ACQUIRE NDDL - Poor Performance, M
When a user creates a user DMAP, the original design intent was that the user
DMAP would automatically acquire the NDDL of the structured solution sequences
unless a user supplied NDDL was provided with the DMAP or an
ACQUIRE NDDL=NDDLOLD or an ACQUIRE NDDL=UserNDDL was used. In MSC/NASTRAN
Version 67.5 this automatic acquire of NDDL=NDDL was inadvertently removed.
This is an inconvenience to the user but more importantly the user who does not
think he or she needs any data base access and hence does not need any NDDL for
the user supplied DMAP will not acquire the appropriate timing constants that
reside on the delivery data base.
Avoidance: The user must explicitly specify an ACQUIRE NDDL entry.
4769
68
DMAP - MESSAGE Module - Trap encountered
On the IBM RS 6000, if the MESSAGE Module is used, the job may fail with the
following error messages in the log file.
Trap encountered, Traceback:
Offset 100043c8 in procedure
Offset
3cc in procedure xtrac2_
Offset
324 in procedure semtrn_
Offset
6c in procedure semint_
Offset
48 in procedure xsem01_
Offset
e4 in procedure mainal
Offset
0 in procedure start
Both the F06 and F04 files may be incomplete. This error is encountered if the
MESSAGE statement spans more than one line and the first value (Pi) on the
continuation line starts with a blank string '
'. An example of such a
situation is as follows:
MESSAGE // ' '/'User information message,'/
' '/' this is a test'/ $
Avoidance: Replac
4773
Answers
68
Nonlinear Analysis - RFORCE/LOAD - Wrong
In a nonlinear analysis, if the RFORCE is referenced by a LOAD or DLOAD entry,

and the scale factor on the is not equal to one, then the loads are be
generated incorrectly. This error leads to wrong answers.
Avoidance: Reference the loads directly on the RFORCE entry.
4774
UWM 8592
68
Documentation - PARAM,NMLOOP - SFM 3001,
In SOL 106, normal modes will be computed with the updated nonlinear stiffness
by using PARAM,NMLOOP. The description of NMLOOP on page 787 of the Quick
Reference Guide Version 67 and page 3.1-50 of the User's Manual
should read:
This option requires the presence of a METHOD
command in the Case Control Section within or above
SUBCASE 1 that references an EIGR or EIGRL entry in the
Bulk Data.
If the METHOD command is put in the Case Control after SUBCASE 2, the following
messages are issued: "SYSTEM WARNING MESSAGE 3001 - ATTEMPT TO OPEN DATA SET
105 IN SUBROUTINE REIG, WHICH WAS NOT DEFINED IN THE FIST."
and "USER WARNING MESSAGE 8592, (REIG). THE METHOD RECORD IN CASE CONTROL IS
MISSING OR INCORRECT. THIS WILL CAUSE THE FOLLOWING FATAL ERRORS. USER ACTION:
PUT
4775
66
VAX V65 and V65C
Miscellaneous - LORY Codes Inoperatble on
LORY security codes do not work for VAX V65 and V65C. If the need for a
LORY security code arises, please
make a request for V65Z on the VAX which has corrected this error.
4782
sults.
68
Documentation - RSPLINE - Inconsistent re
There are two undocumented rules for the RSPLINE element.

The order of the grids on the RSPLINE entry affects the constraint coefficient
(RMG) matrix in all solution sequences. The sequence of the grid
identification numbers should appear in the same order as the line that joins
the two mesh regions. If this order is not followed then the RSPLINE will have
folds in it that may yield some unexpected interpolation results.
The component R3, i.e., degree of freedom 6, of the independent grids on the
RSPLINE should not normally be constrained. This restriction is discussed in a
July 1982 Application Note entitled: "Interfacing Finite Element Models and
Constraint Elements".
4785
68
Documentation - TYPE - Unexpected Results
Although it is not documented, the 'TYPE' DMAP statement is positional. It

must occur before the first use of any datablocks listed on the TYPE statement.
If any referenced datablocks are defined as output before the TYPE statement,
they are replaced with what is on the database (usually nothing, since they
haven't been defined as database datablocks yet). This may result in unexpected
results.
4790
FM 5401
67.7.0.2
Eigenvalue Analysis - EIGRL - UIM 4158, S
If the V1 field on the EIGRL entry is left blank, the Lanczos eigenvalue
extraction method may fail to find all the desired eigenvalues in the range.
This error occurs when the decomposition of the dynamic matrix fails as the
result of ill-conditioning and the message "USER INFORMATION MESSAGE 4158,
MAXIMUM RATIO OF MATRIX TO FACTOR DIAGONAL = ** AT ROW NUMBER **" is issued.
The Lanczos method then tries to correct the ill-conditioning problem changing
the shift eigenvalue. Large negative shift values result and the job
subsequently fails and the message "SYSTEM FATAL MESSAGE 5401 (REIGL). LANCZOS
METHOD IS UNABLE TO FIND ALL EIGENVALUES IN RANGE" is output.
Avoidance: Specify V1 on the EIGRL entry as a small negative number.
4793
68
DMAP - COMPILE, RF3D66 - SFM 9876, OC4
When compiling DMAP alters in the USS in versions 66 thru 67.5, it is possible
to get an 0C4 error. The problem occurs in subroutine COLD.
Avoidance: The problem does not occur in the SSS. The following ZAP will
correct the error in the USS:
//ZAP
EXEC PGM=AMASZAP
//SYSPRINT DD SYSOUT=*
//SYSLIB
DD DISP=OLD,
DSN=...Library with MSC/NASTRAN MSP-EX modules...
//SYSIN
DD *
NAME NASTRAN COLD
VER
0E4C 5830,D118,8930,0002,58F0,D530,5823,F008
CHECKSUM A49F9273
VER
0E5C 58E0,D504,502E,A01C,580E,A010,5900,6028
CHECKSUM 83B55A1C
VER
0E6C 4770,DBFC,507E,A01C
CHECKSUM 8A8497EE
REP
04EC 58E0,D504,1827,580E,A010,5900,6028,4780
CHECKSUM A0D18242
REP
0E6C F008,0700,502E,A01C
CHECKSUM B5894036
IDRDATA COLD-0C
4795
69
Warning Message
Nonlinear Analysis - NLPARM, INTOUT - No
The only acceptable entries for the INT field on the NLPARM entry are YES, NO,
or ALL. If any other strings are entered in this field, then the program uses
the default of NO and no intermediate output is produced.
Avoidance: Enter one of the three valid entries.
4800
68
Documentation - Incorrect Command in Inst
all Manual., Application Manual 7.6-7.7
The command documented to retrieve the nastran or emas installation script
from a remote tape device is not valid on the HP. Specifically, the option "B"
is not a valid option and causes the tar command to fail.
Avoidance: Do not specify the "B" option. This allows the user to perform a
remote installation of the installation script; however, the script must be

modified to complete the installation with the following UNIX commands:
sed 's/rsh /remsh /;s/xvfB/xvf/' < ninstall >ninstall.hp
chmod a+x ninstall.hp
Then execute this new script, i.e. ./ninstall.hp.
The same commands are to be used for a remote MSC/EMAS V2.5 installation
substituting einstall for ninstall.
4816
und
68
Installation - - /usr/local/mscrc not fo
The user may encounter the message "/usr/local/mscrc not found" while
installing MSC/NASTRAN Version 67.5.
Avoidance: Create /usr/local directory.
4823
68
Matrix Methods - FBS - SFM 4276, EC 7777
Regular (non-sparse) FBS may fail if the following conditions are true:
1. Multiple passes are required.
2. Either the right-hand side matrix is an identity matrix or the right hand
side matrix is complex and the factor matrix is real.
Typically, the symptom of this error is a "SYSTEM FATAL MESSAGE 4276, EC 7777"
being issued from the FBS module. This error is most likely to occur when
executing frequency response with the mode acceleration method of data recovery
(PARAM,MODACC) since this analysis can produce a large complex matrix as input
to FBS for the right-hand side.
Avoidance: Use the sparse method or increase the memory size.
4824
68
- SWM 3002, Missing Output
Random Response Analysis - QUAD4(CORNER)
A random analysis request of QUAD4 corner stress output results in the message
"SYSTEM WARNING MESSAGE 3002, MODULE=RANDOM EOF ENCOUNTERED WHILE READING DATA
SET OES2 (FILE 107) IN SUBROUTINE RAND2" being output.
Avoidance: Other than requesting center stress output and performing the
random analysis on the center stresses, there is no avoidance.
4825
69
n 7.7 - HP 9000 Version 67.5 Only
Installation - Application Manual, Sectio
Section 7.7 of the MSC/NASTRAN Application Manual for HP 9000/700 computers

refers to /dev/update.src as the standard tape device name. The device name
currently used is /dev/rmt/0m.
4827
g Answers
69
Complex Eigenvalue Analysis - CEAD - Wron
The complex eigenvalue solution to a two dof problem with structural damping
(no viscous damping) will result in incorrect answers for all extraction
methods except INV. This problem is limited to two dof systems with no viscous
damping, one dof and three dof or greater problems produce correct answers.
Avoidance: Include a small viscous damper in the analysis set.

4829
68
, DESVAR - Wrong Answers
Optimization/Design Sensitivity - DVPREL2
If a design variable value defined on a DESVAR entry or a second level model

property defined on a DVPREL2 entry is less than 1.E-3 in magnitude, wrong
answers occur.
Avoidance: Rescale the model so that the second level model property is
greater than 1.E-3.
4830
68
Restarts - SYSTEM(148) - UFM 1215
Databases created with MSC/NASTRAN Version 67 are compatible with MSC/NASTRAN

Version 67.5 and the intent is that SYSTEM(148)=1 should not be required to
restart from a Version 67 database into Version 67.5. An error on the CRAY
Y-MP UNICOS Version 67.5 requires that this system cell be set to avoid the
message "USER FATAL MESSAGE 1215 (CKRVER) THE PRIMARY DATABASE IS INCOMPATIBLE
WITH THIS VERSION OF THE PROGRAM".
Avoidance: When restarting from a Version 67 database, specify NASTRAN
SYSTEM(148)=1 in the input file for the CRAY Y-MP UNICOS system.
4832
GL
Plotting - XYPLOT - Erratic Plot Output
When using XYPLOT, if the largest value to be plotted (YMAX) is approximately

(but not exactly) equal to the smallest value (YMIN), the plot may appear
erratic. This is due to the plotter scaling the range to fill the plot.
Avoidance: Set YMIN and YMAX with plotter commands a reasonable distance apart.
4834
68
Documentation - TABDMP1, SDAMP
In the User's Manual, equation 7 on page 1.6-4 indicates that the value of
"g(i) is obtained by interpolation of a table supplied by the user" on the
TABDMP1 entry. This statement is true but is incomplete for type "CRIT" and
"Q" damping. For these types of damping the value of g(i) is obtained by
interpolation from the TABDMP1 entry and the value is converted by the program
to type "G" damping. The MSC/NASTRAN Version 68 Dynamics User's Guide
discusses damping in depth. Thus, this error is considered corrected in
Version 68.
4843
69.1
607, Poor Message
Superelements - SEQSET - SEP2 Logic Error
In a superelement model, if the SEQSET dof's for one superelement are placed
interior to a superelement at
the same level in the tree (or in a different branch of the tree), a SEP2 LOGIC
ERROR 607 occurs.
Avoidance: Degrees of freedom used for the SEQSET of a superelement must belong
to a downstream superelement in the same branch.
4846
68
- Poor Message, SFM 4276, EC 1044
Optimization/Design Sensitivity - TRIAX6
TRIAX6 elements are not supported in shape sensitivity. If TRIAX6 elements are
present in a shape sensitivity analysis the message "SYSTEM FATAL MESSAGE 4276
QOPEN ERROR CODE 1044" is issued from the DOMCO2 module.

4851
68
Wrong Maximum BUFFSIZE
Documentation - Application Manual 7.6 -
The MSC/NASTRAN Application Manual, Version 67.5 for CONVEX computers

incorrectly documents the maximum allowable BUFFSIZE as 17921. The correct
maximum value is 65537.
4854
imitation
68
Documentation - DEQATN - Incorrect Size L
The number of allowable characters for the DEQATN entry was increased in
MSC/NASTRAN Version 67 and error number 3284 cited this enhancement. However,
the MSC/NASTRAN Version 67 User's Manual and Quick Reference Guide were not
updated to reflect the change. The current number of allowable characters is
approximately 5000. This is equivalent to approximately 65 card images. The
MSC/NASTRAN Version 68 Quick Reference Guide documents the latest limit which
is 12,500 characters.
4855
SFM 3007
68
Heat Transfer Analysis - SPARSE, SSGHT -
Although it is intended for the sparse solver (NASTRAN SPARSE=25) to work in

heat transfer analysis in MSC/NASTRAN Version 67.5, heat transfer data decks
executed with the sparse solver fail and issue the message "SYSTEM FATAL
MESSAGE 3007, ILLEGAL INPUT TO SUBROUTINE" in module SSGHT.
Avoidance: Do not use the sparse solver in heat transfer solutions (SOL 153).
4856
69
g - Incorrect Coordinate System
Documentation - Reference Manual, Plottin
Page 4.2-17 of the MSC/NASTRAN User's Manual incorrectly states that X,Y,Z
components of displacement are CONTOUR plotted in the global coordinate system.
The default for the displacement CONTOUR plots is the Basic coordinate system.
4860
69
Modifiable - SUN4, IBM RS/6O00 Only
Documentation - Application Manual, User
The instruction that states "copy the nastran shell script into a file umn675"
in Section 7.6.7.3 of the SUN4 and IBM RS/6000 MSC/NASTRAN Application Manuals
should read "copy the nastran shell script into a file nastumn675". The shell
script must begin with the letter "n" as this letter is used internally with
the shell script to distinguish between a NASTRAN and EMAS execution.
4862
70.5
Elements - CRAC2D, CRAC3D - Wrong Answers
The CRAC2D and CRAC3D elements are extremely sensitive to aspect ratio effects.
An aspect ratio of even two to one results in wrong answers.
Avoidance: When using the CRAC2D or CRAC3D element keep the aspect ratio at or
very near one to one.
4867
68
s - Missing Documentation
Documentation - Version 67.5 Release Note
At least one client's Version 67.5 delivery package contained two copies of the
MSC/NASTRAN Common Questions and Answers for Version 67.5" manual but did not
contain a copy of "MSC/NASTRAN Release Notes for Version 67.5". The release
notes are a critical document for understanding the enhancements for Version
67.5. If your delivery is missing this document, please contact your local
representative and request a copy be sent. The delivery letter in future
releases of MSC/NASTRAN will contain a contents list so that client's can
quickly ascertain if there are any missing materials.
4868
68
l Stresses sort problem
Elements - HEXA, PENTA, TETRA - Principa
The output for solid element principal stresses is not sorted well in all
cases. The element output principal stresses should be sorted with the
largest first (major), the smallest second (minor), and the middle last (second
major). However, if two of the principal stresses are the same value, the
first principal will be the unique one and the other two will be the ones that
are the same, regardless of the relative values of each. The .xdb file and the
OUTPUT2 file of the output table also contains this output order. Thus,
postprocessors, including MSC/XL, read the principals as they are written and
assume that they are in the major, minor, 2nd major order and the resulting
plots can be wrong.
4870
68.2
ng NDDL Descriptions
Miscellaneous - OUTPUT2 - UIM 1206, Missi
Some datablocks which are described in the NDDL for the Structured Solution
Sequences (SSS) are not described in the NDDL for the Unstructured Solution
Sequences (USS). If the neutral option on the OUTPUT2 statement is to be used
for these datablocks, the NDDL_NAME must be specified. Note that this is a
Version 67.5 plus capability. MSC/NASTRAN Version 68 includes the correct NDDL
description for the USS for all the data blocks noted below except ONRGY1.
List of known datablocks;
Datablock
OES1
OES2
OEF2
OPG2
OQG2
ONRGY1
OSTR2
NDDL_NAME
OES
OES
OEF
OPG
OQG
ONRGY
OES
4872
69
ng Answers for SPCFORCES
Nonlinear Transient Analysis - RBE2 - Wro
Nonlinear Transient Analysis that contain RBE2 elements with grounded

independent degrees of freedom produce wrong answers for the SPCFORCE output.
Avoidance: Remove the RBE2 element and constrain the dependent degree of
freedom directly.
4879
ong Answers
67.7.0.3
Frequency Response Analysis - FRRD1A - Wr
Frequency Response Analysis may produce wrong answers on all CRAY C90 and later
CRAY Y-MP systems that have split memory. This includes all Y-MP/8I, Y-MP/4E
and some Y-MP/2E systems. The error can occur in Version 67R2, 67.5 and Version
67.7 and has been caused by a bad coding practice and a change in the later
version of the CRAY FORTRAN compiler. The error is dependent on the manner in
which the frequency dependent load is defined and can only occur if the
following three conditions are met:
1. DLOAD entries are in the bulk data
2. Total number of (RLOAD1's, RLOAD2's, TLOAD1's, and TLOAD2's) > number of
DLOAD's + 5
3. Total number of (RLOAD1's, RLOAD2's, TLOAD1's, TLOAD2's and DLOADs) = An
odd number
Avoidance: Avoid one of the three conditions mentioned by adding dummy en
4880
68
COMP, DOTRD - Poor Answers
Parallel Matrix Methods - SYSTEM(107), PD
Parallel decomposition may produce poor answers on large problems on the IBM
MVS/XA Version 67.5.1 release of MSC/NASTRAN running in Vector mode.
Avoidance: Either do not run with vector, do not select parallel decomposition,
or apply the ZAP to correct the problem:
//ZAP EXEC PGM=AMASPZAP
//SYSLIB DD DISP=SHR,DSN=..nastran load library..
//SYSIN DD *
NAME NASTKVCT KERNVCT1
VER 09F6 1200,4780,F10A
REP 09F6 47F0,F10A,0700
/*
4881
68
, DESVAR - UFM 6421
Optimization/Design Sensitivity - DVPRELi
In MSC/NASTRAN Version 67.5 solution 200, if the initial property value as

specified from a DVPRELi entry is the same as PMIN on the DVPRELi entry, then
due to machine roundoff the job may fail and issue the message "USER FATAL
MESSAGE 6421 (DOM11A)" that indicates that the property value is less than PMIN
on the DVPRELi entry.
In an attempt to correct this error in Version 67.7.1, errors were introduced.
The first error occurs whenever a PMIN value is less than the designed property
value, but both values round to the same integer. This case should result in a
user fatal message but does not. The second error may result in an integer
overflow and the third error may cause the final design to violate the minimum
property constraint by as much as 1.0 unit. The significance of this e
4883
Differential Stiffness and Buckling - QUADR - Wrong Answers
The QUADR and TRIAR elements do not support differential stiffness as is

documented in the User's Manual. Therefore, they should not be used for
buckling analysis. User Warning Message 5481 will be issued when either one of
these elements is used in a buckling analysis. However, if the QUADR is used
in a buckling analysis, an incorrect rather than a null differential stiffness
will be generated and wrong answers occur.
Avoidance: Do not use QUADR or TRIAR for buckling analysis. Replace them with
the QUAD4 and TRIA3 elements
4884
68
Differential Stiffness and Buckling - No
output request - Wrong Answers

If no data recovery is requested in solution 105 in the static subcase, then
the eigenvalue calculation will be wrong.
Avoidance: Request data recovery in the static subcase. A request for
DISP(PLOT)=ALL avoids unwanted output in the F06 file and still avoids the
error.
4885
68
Cyclic Symmetry - RESTART, GRAV, RFORCE,
LOADCYH - Missing Loads, Wrong Answers
In solution 114, if a coldstart run defines GRAV and RFORCE loads in the bulk
data but the loads are not referenced, then the GRAV and RFORCE loads are
missing in a subsequent restart that references them.
Avoidance: Coldstart any cyclic symmetry run that references GRAV and RFORCE
loads, or add a dummy CMASSi to the restart deck to force the recalculation of
the mass matrix and the regeneration of the inertia loads.
4888
67.5.0.1
Chips - Bad Request Code
Miscellaneous - SGI Computers With R3000
MSC/NASTRAN Version 67.5 does not run on SGI computers with R3000 chips. A
message similar to the one below appears in the .log file:
Bad request code: /usr2/msc/nast675/nast675/NAST675
Where /usr2/msc/nast675/nast675/NAST675 is the MSC/NASTRAN executable on your
machine.
Avoidance:
The user must remake the NAST675 executable or request a re-release of
MSC/NASTRAN Version 67.5.0.1 on SGI Computers from their MSC sales office. The
following C program called "magic" is supplied and must be applied to the
MSC/NASTRAN executable.
If the user has a C compiler follow the procedure in
Note #417.
4893
tput
68
Cyclic Symmetry - PARAM,MPCF - Missing Ou
A request for forces of multi-point constraints (PARAM,MPCF,YES) in cyclic

symmetry (SOL 114) is ignored.
Avoidance: A DMAP avoidance for MSC/NASTRAN Version 67.5 is presented below:
ALTERS FOR MPC-FORCES, SOL114 (CYCLIC STATICS), VERSION 675
1. SUBDMAP SEDRCVR NEEDS TO TRANSFORM PGC BACK
2. SUBDMAP SEDRCVR NEEDS TO GET KGG (REASON FOR SUBDMAP CYCMPCF)
ALTER 15,19 $ REMOVE MPCF FOR STATICS, V675
IF
( NOMSET>-1 AND MPCF='YES' AND APP='CYC' AND
APP1='STATICS' ) CALL CYCMPCF UGVS/QGM1 $
COMPILE CYCMPCF NOLIST NOREF $
SUBDMAP CYCMPCF UG/QGM $
TYPE
DB KGG,PGC,BACK,USET $
MPYAD
MPYAD
UPARTN
RETURN
END $
PGC,BACK,/PGB $
KGG,UG,PGB/QG///-1 $
USET,QG/QGM,,,/'G'/'M'/'N'/1 $
$
4897
68
correct Slip Code
Nonlinear Slide Line Contact - BLSEG - In
The "RESULTS FOR SLIDE LINE ELEMENTS" may incorrectly indicate the "SLIP CODE"
as "OVERHANG" instead of "OPEN". This condition occurs when the contact
surfaces are relatively far apart. The correct slip code is output as the
surfaces become closer together. Note that the 2-D Surface Contact capability
is considered experimental in MSC/NASTRAN Version 67.5. The capability is not
documented in the Version 67.5 Release Notes and can only be accessed through
DMAP ALTER.
Avoidance: No avoidance is necessary as there is no adverse affect to the
converged solution.
4898
ct Eigenvector
68
Superelements - METHOD, RESTART - Incorre
If the only change in a superelement dynamic restart, is the METHOD selection

for the residual structure, the program will correctly calculate the new modes
for the residual structure, but if residual structure modes from a previous
runs exist on the restart database, they will be used to find the eigenvectors
of the upstream superelements. Therefore, it is possible to have incorrect
eigenvectors for the upstream superelements.
Avoidance: The avoidance is to make a dummy change to the residual structure,
for example, adding an additional GRID point.
4903
Wrong Answers
68.2
Nonlinear Analysis - BEAM, PARAM,LGDISP -
A geometric nonlinear analysis (SOL 64 or SOL 66, 99, 106 and 129 with
PARAM,LGDISP) that contains BEAM elements produces poor answers. The answers
are not independent of the local BEAM element coordinate system. The magnitude
of the error appears to be proportional to the displacement of the structure.
4907
ers
68
Superelements - RESTART, SPC - Wrong Answ
If the only change to a superelement restart run is the selected SPC set for
the residual structure, incorrect answers result. The correct results are
obtained for the residual structure, but the results are unchanged from the
previous run for the upstream superelements.
Avoidance: Add an SPC entry to the restart bulk data.
4914
GL
, DESVAR - Wrong Answers
Optimization/Design Sensitivity - RESTART
If an optimization analysis is restarted and the DESVAR entries from the cold
start are deleted and replaced, SOL 200 yields wrong answers. Section 7.11 of
the MSC/NASTRAN Design Sensitivity and Optmization guide documents this
limitation.
Avoidance: After the initial cold start is executed, merge the original data
deck with the new DESVAR entries from the .PCH file from the initial run and
execute the run as a cold start.
4915
Nonlinear Analysis - MATi - Missing Output
If a material id contains more than 8 characters, nonlinear stress output is

unavailable for any element referencing the material. Material ids containing
more than 8 characters are generated by the composite capability and whenever
they occur, the program assumes that the material is being used by a composite
element.
Avoidance: Use material ids with 8 or fewer characters
4917
70.5
4276, EC 7777, Numeric Trap
Material Nonlinear Analysis - MATS1 - SFM
If the TABLES1 referred to by a MATS1 for a PLASTIC material does not start at
the origin then a numeric trap may occur on IBM RS/6000 systems.
Avoidance: Specify the first x-y pair to be 0.0, 0.0
4918
ts
69
Documentation - DMIG - Inefficient Restar
Automatic restart for superelement analysis may be inefficient if DMIG entries

are added or changed. The current logic will process all superelements
completely if any DMIG entry is changed from the original run.
Avoidance: As long as the DMIG is selected in the CASE CONTROL (i.e., K2GG,
M2GG, B2GG), the following alter will remove this part of the logic, while
retaining the CASE CONTROL checking logic.
COMPILE IFPL, SOUIN=MSCSOU
ALTER 90,90 $ V675
This removes the restart checking for BNDFL, DMIAX, DMIG, ELIST, MFLUID,
RADLIST, and RADMTX bulk data changes.
4923
68
RA - Missing Routine GPSPTS
Grid Point Stress - GPSTRESS, CHEXA, CTET
A request for grid point stress data recovery for a VOLUME containing CHEXA
and/or CPENTA elements may fail on the HITACHI VOS3 and FUJITSU MSP/EX
MSC/NASTRAN Version 67 systems. The error message issued indicates "MISSING
ROUTINE ( GPSPTS ).
Avoidance: The error can be avoided by setting the CORDM field on the PSOLID
entry to 0 (note that the default for this field is -1).
4926
Miscellaneous - - "NaNQ" in the Output
John, I suspect that this is a limitiation of the OS.
--Mike 3/12/08
If a term in a matrix becomes too large for the computer to represent, the IEEE
standard replaces it with "NaNQ" on the output. Therefore, it is possible to
have "NaNQ" appear in the place of numbers in the output from MSC/NASTRAN. If
this occurs, it is an indication that the numbers involved are too large to be
accurately processed on the computer.

4930
Sequencer - PARAM,SUPER,2 - Infinite Loop
If PARAM,SUPER,2 is specified in the BULK DATA and there are no superelements

in the model, the sequencer may enter an infinite cpu loop.
Avoidance: Do not use PARAM,SUPER if there are no superelements in the model.
4935
umentation
69
Documentation - TABTST - Insufficient Doc
The documentation of the TABTST utility program in Section 7 of the MSC/NASTRAN

Version 68 Installation and Operation Instructions needs to be enlarged to
explain that this is only a sample program that illustrates how to read an
output2 file. The sample is for reading a stress datablock. This explanation
is contained in the tabtst.f source file. In order for the user to read
another datablock, tabtst.f may be used as a guide but the format of the
datablock that is to be read must be known. The NDDL (NASTRAN data definition
language) file or the Programmer's Manual to determine a specific datablock
definition.
4937
70.7
Acoustic Analysis - ACRSE - UFM 2071
The Users Manual improperly states that field 4 on the ACRSE entry is used to
specify a DPHASE entry. If this field is used to select a DPHASE entry "USER
FATAL MESSAGE 2071" is output stating that the load entry specifies an
undefined table. Field 5 on the ACSRCE is used to select a DPHASE id, not the
DELAY id as indicated in the MSC/NASTRAN Version 67 User's Manual. There is no
field that references a DELAY entry on the ACSRCE entry.
4938
69
- Poor Message, UWM 229 (PRERR2)
Optimization/Design Sensitivity - DEQATN
The message "USER WARNING MESSAGE 229 229 (PRERR2)" is output if a semicolon is
input at the end of the last equation on a DEQATN entry. The semicolon
separates equations on the DEQATN entry but should not be placed after the last
equation. Although this is a user input error a better message should be
issued to assist the user in locating the input error. Please see error 4525
for a more general description of deficiencies in processing the DEQATN entry.
4939
68
FIBER) - Misleading Answers
Optimization/Design Sensitivity - STRAIN(
A STRAIN(FIBER) case control request is not recognized in quantities related to

design optimization. That is, the design responses used in sensitivity and
optimization with the DRESP1 entry with RTYPE=STRAIN assume a STRAIN(STRCUR)
form.
Avoidance: There is no avoidance other than to explicitly provide strain
relations on the DEQATN entry.
4943
68
ing Documentation
Documentation - NLPARM, RESTART - Mislead
The documentation in the MSC/NASTRAN Version 67 User's Manual states that the
INTOUT field is used to specify intermediate output requests, (displacements,
forces, stress, etc.). There is no specific indication that it controls
restartability. Furthermore the Handbook for Nonlinear Analysis specifically
states "Further improvements were made in Version 67 so that the data blocks
for the last converged load step will be saved if the solution is terminated in
the middle of a subcase due to divergence or consumption of the specified CPU
time. Consequently, the solution can always be restarted." Contrary to these
descriptions the INTOUT field of the NLPARM entry must be set to yes to be able
to subsequently restart from the middle of a subcase.
4944
68
MIgration - DBLOAD, DBTRANU - UFM 6281
Migrating a Version 65C superelement database to Version 67.5 may result in the
following fatal message:
USER FATAL MESSAGE 6281 (SEP2D)
NO SUBCASES ARE SPECIFIED FOR THE RESIDUAL STRUCTURE.
IN A STATIC ANALYSIS, AT LEAST ONE SUBCASE MUST BE SPECIFIED FOR THE RESIDUAL
STRUCTURE.
This error occurs because the CASECC datablock is not stored on the database
in Version 65C and Version 67.5 requires the datablock.
Avoidance: The following alter circumvents the requirement for the CASECC
datablock in Version 67.5:
compile dbtranu souin=mscsou noref nolist
alter 73,73
SEP2CT SLIST,CASECC,,EMAP,/CASES,,/'reig'/V,N,SEID $
Note that this error has been marked as fixed in Version 68 since migration
from Version 65C is no longer supported.
4947
68
Documentation - DSCREEN - UFM 315
The MSC/NASTRAN User's Manual documentation states, " If TYPE = "LAMA", "EIGN",
"WEIGHT" or "VOLUME" then NSTR is not used.". However, if NSTR is input by a
user when TYPE is specified as one of the aforementioned responses, the message
"USER FATAL MESSAGE 315 (IFPDRV) FORMAT ERROR ON BULK DATA ENTRY DSCREEN" may
be issued.
4954
68
nfusing Message, UWM 4595
Grid Point Stress - SURFACE, VOLUME - Co
An MSC/NASTRAN superelement run in which the residual structure has no elements

issues the following at the beginning of data recovery for the residual
structure:
*** USER WARNING MESSAGE 4595. UNABLE TO OPEN INTERNAL DATA BLOCK (NONE) IN
GPSTR1 MODULE - PROCESS STOPPED.
if the following Case Control conditions exists:
1) SURFACEs and/or VOLUMEs are defined.
2) No ELSDCON, GPSDCON, GPSTRESS, or STRFIELD Case Control commands are
present.
Avoidance: Add a dummy element to the residual superelement or disregard the
message.
4968
68
EG - Wrong Answers
Nonlinear Slide Line Contact - BCONP, BLS
The DMAP alters delivered for the nonlinear slide line capability in
MSC/NASTRAN Version 67.7 produce wrong eigenvalues for nonlinear modes
(PARAM,NMLOOP). Note that the nonlinear slide line capability (a.k.a., 2D
Contact) is considered experimental in Version 67.5 and 67.7. The capability
is only available through DMAP alters.
4978
Elements - QUAD4 - UFM 4297
If a CQUAD4 element's dimensions are small, in the order of 1.E-5, the job may
fail and the message "USER FATAL MESSAGE 4297, ELEMENT HAS AN INTERIOR ANGLE
POSSIBLY GREATER THAN OR EQUAL 180 DEGREES" is issued.
Avoidance: There is no known avoidance other than to use different units.
4981
69
- Meaningless Answers
Optimization/Design Sensitivity - DRESPi
If an invalid item code is entered in the seventh field of the DRESP1 entry
meaningless results are produced for sensitivity and optimization.
Avoidance: Specify a valid plot code.
4986
68
Missing Description of Plastic Hinge
Documentation - Reference Manual, BEAM -
For nonlinear analysis, the BEAM element may be used for geometric
nonlinearities or for the modeling of a plastic hinge under elastic-perfectly
plastic conditions. The latter application by design intent is the only
material nonlinearity valid for the BEAM element. Any other type of material
nonlinearity, such as creep or a stress-strain curve, will yield inaccurate
answers. In the case of creep, due to the assumption that only 1/8 of the
length at the ends of each BEAM abides by the nonlinear material law, the BEAM
appears too stiff. In the case of a stress-strain curve, the beam acts as a
linear element.
This is addressed in the Version 68 Reference Manual.
Avoidance: ROD elements should be used to model axial material nonlinearities
4994
tput, UWM 9012
69
Documentation - PARAM,FIXEDB - Missing Ou
The current documentation for PARAM,FIXEDB states only that PARAM,FIXEDB,-1 is

to be specified in the residual subcase or the bulk data if the modes of the
residual structure are not desired. When printout or plots of component modes
are desired in SOL 63, PARAM,FIXEDB,-1 must be specified for both the desired
superelement(s) and the residual structure. If this is not done, the
superelement component fixed boundary modes will not be available and UWM 9012
will be printed.
Avoidance: Specify PARAM,FIXEDB,-1 for both the superelement(s) and the
residual structure. This can be accomplished by either by specifying the
parameter in the BULK DATA or by specifying the parameter in CASE CONTROL for
both the superelement(s) and the residual structure.
5003
69
Documentation - Superelements, STRESS(COR
NER) - Missing Output

The Release Notes for MSC/NASTRAN Version 67.5 state that the request for
CORNER output must occur in the first SUBCASE. This is correct for conventional
analysis. In superelement analysis this input yields standard center stress
output for the upstream superelement only. If the run is using superelements,
the request must be above the SUBCASE level or in the first residual structure
SUBCASE.
5011
- SFM 3060
68
Security - Incorrect Authorization Codes
There are bugs in the SUN4 version of the MSC/NASTRAN authorization code
generator that create bad authorization codes. It sometimes creates
authorization codes that will not allow MSC/NASTRAN to run, while other times
particular solution sequences will not work.
The following is a list of reported problems:
-For
-For
-For
-For
VAX/VMS, we cannot get a code (3 times)

HP9000, we cannot get it sometimes,not always.
SUN4, we cannot get it for Nonlinear option.
CONVEX, grid point limitation inadvertently set.
Avoidance:
When an incorrect authorization code is found by the client, send the necessary
information to LA and we will generate the code for you since the VAX
authorization code generator always gives a correct code.
5017
70.7.2
Cyclic Symmetry - SOL 115 - Missing Plots
In SOL 115 (CYCLIC Modes), if repeated roots exist for a harmonic, the batch
plotter will not create stress plots for the second occurence of the
eigenvalue.
5018
68
77, Segmentation Fault
Matrix Methods - SMPYAD - SFM 4276, EC 77
A multiplication of the type [A]T[B][A]+[C] results in an error in the SMPYAD

module if the precision of the output matrix is set different than the machine
precision. This error does not occur in any unaltered delivered solution
sequence.
Avoidance: Either do not set the precision of the output matrix or replace
SMPYAD with the equivalent calls to MPYAD.
5020
69
- Wrong Answers
A DEQATN of the form F(A,B) = F**2 + B**2 should fail to compile because the
right hand side of the equation refers to the function defined on the left hand
side, but it does not.
Avoidance: Do not define DEQATNs where the right hand side of the equation
refers to the function on the left hand side.
5021
4276, EC 7777
68
Acoustic Analysis - MODEPT, PACABS - SFM
If a PACABS entry references a non-existant table or the table contains

negative frequency values, then UFM 6167 should be issued and the run should
terminate in the MODEPT module. In some instances the UFM 6167 is missing, the
run fail in the MODEPT module but issues the message "SYSTEM FATAL MESSAGE 4276
ERROR CODE 7777" instead.
Avoidance: Correct the PACABS entry or supply the missing tables.
5024
2001
Composites - PCOMP - Extraneous Output
The header:
"F A I L U R E I N D I C E S F O R L A Y E R E D C O M P O S I T E E
L E M E N T S" is output to the f06 file even when no failure calculation is
requested (i.e., the FT field on the PCOMP entry is left blank).
5031
69
for SE SPC changes
Superelements - DBLOCATE - Wrong Answers
SYSTEM(143)=1 specifies that the bulk data is being obtained via the DBLOCATE
FMS statement. Although it is not documented, the design intent is to allow
load changes only when SYSTEM(143)=1 is specified. Any other changes such as
connectivity, grid location or constraints are reflected in the bulk data echo
but are not effective even when they apply to superelements that have yet to be
processed.
5034
69
Optimization/Design Sensitivity - DRESP1,
BEAM, BAR, BEND - Meaningless Answers
The BEAM, BAR, ROD and BEND elements set the margin of safety to an integer
value of 1 when the stress in the element is zero. Further, for the BAR, BEAM
and BEND elements which have separate tension and compression margins, if the
element is purely in tension, the compression safety is set to 1. The module
which calculates DRESP1 values does not know about this convention and
therefore uses the real number equivalent to 1 in its computation. On many
machines the real number equivalent to the integer 1 is a real number near
zero. Thus, if the analysis has been defined to achieve larger margins
meaningless answers may result. There is a similar problem in modal response
calculations when the DDRMM parameter is 0. In this case the margin of safety
cannot be calculated but the DRESP1 ev
5035
ins of Safety
Dynamic Analysis - DDRMM, CBEAM, CBAR, CBEND - Incorrect Marg
The margins of safety cannot be calculated correctly in a modal dynamic

response analysis when PARAM,DDRMM is 0. Depending on the element and Version
of MSC/NASTRAN the printed value of the margin of safety may be incorrect or
simply 0.0.
Avoidance: If the margin of safety output is desired for dynamic analysis the
user must select PARAM,DDRMM,-1.
5041
Message
68
Acoustic Analysis - ACMG - SFM 6211, Poor
The message "SYSTEM FATAL MESSAGE 6211 (ACMG), A NORMAL TABLE HAS BEEN
INCORRECTLY CREATED" is misleading. The message is the result of a problem in

the boundary area factor generation code in the ACMG module. The error is
believed to be caused by a problem with LOCATE. The message occurs when a
CHEXA fluid element in the ECT table can not be located.
Avoidance: The only avoidance is to specify the "IDENT" option on ACMODL
entry. Since the "IDENT" option requires a matching interface between the
structure and fluid in most cases the model must be remeshed.
5044
68
ement Force Label
Eigenvalue Analysis - SDR2 - Incorrect El
An incorrect eigenvalue label is output for element forces when the

generalized mass of an eigenvalue is zero.
5047
GL
Installation - IBM 386/486 IX - UFM 3060
When both the mouse and the authorization device (dongle) use the same port
(for example the com1 serial port) MSC/NASTRAN will not run and UFM 3060 is
received.
Avoidance: The only avoidance is to obtain another serial port and use one
for the mouse and one for the authorization device.
5050
Data
68.2
Postprocessing - PARAM,POST,-1 - Missing
When using SOL 105 with PARAM, POST, -1, the datablocks from the static
subcase, the differential stiffness results, are missing from the OUTPUT2 file.
Only the geometry and buckling modes are contained in the OUTPUT2 file.
Avoidance: To obtain the results from both subcases, insert the following
alters:
For Version 67.5:
SOL 105 $ V67.5, PATVER=3.0
COMPILE DMAP=SEBUCKL,SOUIN=MSCSOU,NOLIST,NOREF
ALTER 29 $ BEFORE SUPER3, STATICS
TYPE PARM,,I,Y,OTAPE2 $
OTAPE2=-1
ALTER 55 $ AFTER SUPER3, BUCKLING
TYPE PARM,,I,Y,OUNIT2 $
$ WRITE END-OF-DATA ON FORTRAN UNIT OUNIT2
OUNIT2=12
OUTPUT2 //-9/OUNIT2 $
COMPILE DMAP=SUPER3,SOUIN=MSCSOU,NOLIST,NOREF
ALTER 170 $ BEFORE OUT2GEOM
IF (APP1='BKL1
') OTAPE2=0
ALTER 181,181 $ REMOVE EOF ON OUTPUT2 FILE
ENDDALTER
SOL 105 $ V67
5056
70.7
Elements - QUAD4(CORNER) - Poor Answers
The STRESS(CORNER) request may produce a large variation in the answers for
QUAD4 corner stresses for elements with thickness variation or warp.
Avoidance : It is recommended that STRESS(BILIN) be used for problems with warp
or thickness variation. The default option for STRESS(CORNER) is changed in
Version 68.2 to BILIN to address this problem. See also error 6421.
5058
69
EIGL - UWM 8592, SWM 3001
Cyclic Symmetry - Normal Modes, READ or R
A cyclic symmetry modal analysis that fails to specify NOUTPUT (the segments
for which output is desired) or HOUTPUT will fail issue the following messages:
*** USER WARNING MESSAGE 8592, (REIG). THE METHOD RECORD IN CASE CONTROL IS
MISSING OR INCORRECT.
THIS WILL CAUSE THE FOLLOWING FATAL ERRORS.
USER ACTION: PUT A METHOD ENTRY IN CASE CONTROL WHICH POINTS TO AN EIGR,
EIGRL, OR EIGB RECORD IN BULK DATA.
0*** SYSTEM WARNING MESSAGE 3001 MODULE = READ
0ATTEMPT TO OPEN DATA SET 105 IN SUBROUTINE REIG , WHICH WAS NOT DEFINED IN
THE FIST
Avoidance: Specify NOUTPUT or HOUTPUT in the Case Control.
5062
69
(RDINIT) ILLEGAL KEYWORDS
File Management Section - INIT - UFM 426
The word "LOGICAL" or "SCR300" must not appear starting in column one (1) on
the INIT statement if there is more than one (1) member being defined, else
"USER FATAL MESSAGE 426 (RDINIT) THE FOLLOWING KEYWORDS ARE ILLEGAL FOR THE
INIT COMMAND" is output.
Avoidance: The following are examples of valid and invalid INIT entries:
$ -Invalid FMSINIT MASTER(S)
INIT SCRATCH,
LOGICAL=(SCR1,SCR2),
SCR300=(SCR3,SCR4)
INIT DBALL,
LOGICAL=(DB1,DB2)
ENDJOB
5063
67.5
5090
2004
ED3, TABLED4 - UFM 6167
$ -Valid FMSINIT MASTER(S)

INIT SCRATCH,
LOGICAL=(SCR1,SCR2),
SCR300=(SCR3,SCR4)
INIT DBALL,
LOGICAL=(DB1,DB2)
ENDJOB
$ -Valid FMSINIT MASTER(S)

INIT SCRATCH,
LOGICAL=(SCR1),
SCR300=(SCR2)
INIT DBALL,
LOGICAL=(DB1)
ENDJOB
DBLOCATE COPY Fails - SFM 1013

Documentation/QRG - PACABS, TABLED2, TABL
If the table that is used to define the resistance, reactance, or weighting

function is the type TABLED2,
TABLED3, or TABLED4, then the program issues "USER FATAL MESSAGE 6167 THE BULK
DATA TABLED1 ENTRIES, ID= N WERE NOT SUPPLIED"
Avoidance: The PACABS entry should reference TABLED1 entry instead.
- note this is a documentation error. Tables referenced by
TID1, TID2, TID3 can only be TABLED1- The TABLEDi i=2,3,4 imply a certian look
up strategy TABLED2 and TABLED3 by
shifting the curve and compressing the x-axes. TABLED4 is a polynomial
expansion. The PACABS entry does not use these tables for
look up. Rather it uses TABLED1 to perform a least square fit to determine a K
and M value which bests fits the curve.
5091
ce
68.2
Acoustic Analysis - ACMG - Poor Performan
Acoustic element problems with coupled fluid/structure boundaries and non"IDENT"ical meshes can lead to excessive cpu time.
Avoidance: Other than using identical meshes, there is no avoidance.
5101
68
r Method - UFM 4252
Superelements - SEMA, CSUPER, Multi-Maste
When using the multi-master method with image superelements on Version 67.7,
"USER FATAL MESSAGE 4252, DATA BLOCK NOT FOUND IN DATABASE" may be issued by
the SEMA module for the image superelement.
Avoidance: The problem is under investigation. The only avoidance is to use
the conventional (single-master) approach.
5102
wers
68
Aeroelastic Analysis - AEFACT - Wrong Ans
Changes in the AEFACT bulk data entry should, on restart, force the
recomputation of the aerodynamic
matrices. However, the required dependencies are absent in the NDDL with the
result that the aerodynamics
are not recalculated and the user's intent is not fulfilled.
Avoidance: Submit the job as a cold start.
5106
ers
68
Miscellaneous - BFORCEA.V675 - Wrong Answ
When using the bforcea.v675 alter in the sssalter directory, if different load
ids are specified for different superelements in the Case Control, incorrect
answers may result. This is due to the LOAD qualifier's value remaining at the
last value used, even though different values are necessary for each
superelement during data recovery. Standard data recovery is not affected by
this.
Avoidance: Modify the alter by replacing the line
MPYAD
KAA,ULS,PL/BFORCEL///-1 $ CALC BOUNDARY FORCES
with the following:

TYPE PARM,,I,N,SEID1 $
SEID1 = SEID $
DBVIEW MYPL=PL, (WHERE SEID=SEID1 AND WILDCARD = TRUE) $
$ CORRECT THE MPYAD TO HAVE MYPL, INSTEAD OF PL
MPYAD
KAA,ULS,MYPL/BFORCEL///-1 $ CALC BOUNDARY FORCES
5110
70.6
Nonlinear Superelement Analysis - PARAM,
BUCKLE,1 - Missing Output

Solution 106 with buckling (PARAM,BUCKLE,1) is not designed for upstream data
recovery. A request for upstream data recovery is ignored.
5124
68
Restarts - DBSTORE - DBSTORE Not Executed
The restart logic in the SSS will prevent the execution of the DBSTORE subdmap
during restart runs.
Avoidance: To force execution on restart set system cell 109 to 1 before the
call to DBSTORE. This action turns off restart checking.
That is:
putsys(1,109) $ turn restart checking off
CALL DBSTORE A,B,,,//QUAL1/QUAL2/DBSET/COND $
putsys(0,109) $ turn restart checking back on
This error is considered to be a documentation error and has been fixed in
Version 68 by adding an appropriate remark under the description of the DBSTORE
module in the DMAP Module Dictionary.
5137
68
nual - Incorrect Documentation
DBC/TRANS/ACCESS - ACCESS, Application Ma
All references to "MSC07" in Section 7.7.6 of the MSC/NASTRAN Version 67.5 IBM
MVS/XA Application Manual should be changed to "MSC06A". These changes must be
made to install the program.
5146
68
Restarts - SPCD - Wrong Answers
If all SPCD entries are entered on the initial run, and a different set is
selected on a restart run, the program will use the set called out in the
initial run, resulting in incorrect answers.
Avoidance: Add or change an SPCD entry on the restart run.
5160
68
Elements - CHEXA, CPENTA - UFM 4658
"USER FATAL MESSAGE 4658, DIFFICULT GEOMETRY PREVENTS FURTHER COMPUTATIONS FOR
ELEMENT WITH ID = ***" is presently encountered when solid elements have an
aspect ratio greater than 1000. This geometry check is changed in MSC/NASTRAN
Version 68 such that the fatal message is only encountered if elements have bad
aspect ratios in two directions. That is only elements that are long and thin
like a straw should encounter this fatal message.
5164
68
Restarts - PARAM,SERST,SEMI - ?
PARAM,SERST,SEMI may skip PHASE1 on a restart run, even though the SUPER
command requests processing for the superelement. The restart logic properly
deletes datablocks, however, the requested processing may not be performed.
Avoidance: The following DMAP alter forces execution of PHASE1
compile super1 souin=mscsou nolist noref
alter 35
putsys (1,109)
alter 36
putsys (0,109)
5178
70.6
6036, Wrong Answers
Nonlinear Buckling Analysis - SPCD - SFM
Nonlinear buckling in SOL 106 does not work if the loading includes enforced
displacements. If the load consists entirely of enforced displacements, the
following message will occur:
SYSTEM FATAL MESSAGE 6036 (XQAROS)
ATTEMPT TO DIVIDE BY REAL, SINGLE PRECISION ZERO
USER INFORMATION:
1. PROCESSING ASSIGNMENT STATEMENT: ALPHA
AT DMAP SEQUENCE NUMBER:
360
1. PROCESSING INSTRUCTION: /
00000005 00010005 00000002
If enforced displacements are combined with other load types, then the critical
load factor ALPHA will be computed incorrectly. This error can be avoided
using the following DMAP alter:
compile nlstatic
$ alter for sol 106 in V70.5 to correct an error in CSR 5178
$ nonlinear buckling analysis made possible
5209
68
Max Shear Stress is Always Output
Documentation - STRESS(VONMISES), PCOMP -
For composite shell elements, the default for the ply stress output is Max
Shear. In fact this calculation is hard-coded into MSC/NASTRAN, requesting von
Mises is ignored. The 2nd printing the Version 68 Quick Reference Guide has
been updated to correct this error.
Avoidance: This is a limitation of the code. The documentation for STRESS
command should be updated to reflect this limitation.
5212
Missing Output
70
Miscellaneous - STRESS(CORNER), SUBCOM -
The corner stress data recovery is not done in SUBCOM if the corner stress
output request does not exist in
the first SUBCASE. The following is an example which will produce missing
output:
SUBCASE 1
LOAD = 1
SPC = 1
SUBCASE 2
LOAD = 2
SPC = 1
SUBCOM 3
STRESS(CORNER) = ALL
SUBSEQ = 1.0,1.5
Avoidance: The following input avoids the error:
STRESS(CORNER) = ALL
SUBCASE 1
STRESS(CORNER) = NONE
LOAD = 1
SPC = 1
SUBCASE 2
LOAD = 2
SPC = 1
SUBCOM 3
SUBSEQ = 1.0,1.5
5227
69
ng Modal Participation Factors
The description of the FLUIDMP
Guide states that "If n=-1 for
factors will be output for all
no modal participation factors
Documentation - PARAM,PANELMP, -1 - Missi

and PANELMP parameters in the Quick Reference
any parameter, then (modal participation)
modes". In fact if PARAM,PANELMP is set to -1
are output.
Avoidance: Set PARAM,PANELMP to the number of modes that modal participation

factor output is desired.
5229
68
T,TRIA3, MAT5 - Wrong Answers
Heat Transfer Analysis - SOL 101, APP HEA
Heat transfer flux data recovery for TRIA3, TRIA6, and QUAD8 elements which
reference MAT5 (anisotropic) material properties is incorrect. When using MAT5
(anisotropic) materials, the user supplied matrix must be transformed to the
element system. The values needed for this transformation are not calculated.
Whatever values are currently stored in memory is used for the transformation
matrix, yielding unpredictable results. If only TRIA3 elements are used, and
the memory is initialized to zero (as it is on the VAX/VMS), the FLUX output
will be zero.
5232
Answer
68
Acoustic Analysis - RMS Velocity - Wrong
The (RMS of the velocity)=(RMS

Version 67 and 67.5 the (RMS of
fluid degrees of freedom. Thus,
output by MSC/NASTRAN is off by
5255
of the Acceleration/2*PI*f). In MSC/NASTRAN

the velocity)= (RMS of the Acceleration/f) for
the RMS velocity for fluid degrees of freedom
a factor of 2*PI.
Dynamic Response Analysis - Superelements - Missing Output
When performing frequency response using superelements, no output will be

available for any superelement which is not mentioned in a SUBCASE for dynamic
loading. This design extends to XYPLOT output. This is especially pronounced
when multiple residual solutions are requested using multiple subcases.
Avoidance: For each residual subcase, a corresponding subcase for each
superelement should exist in the input.
5267
69
, GDR - Missing Output
Documentation - Acoustic Analysis, DYNRED
If a modal approach is used for fluid-structure interaction, Generalized

Dynamic Reduction should not be used. If used, the generalized dynamic
reduction is performed on the combined matrices and the program will use those
matrices in the structural eigenvalue problem. This will provide both the
structural and fluid modes, but the program requires the fluid and structural
modes to be separate in order to calculate the coupling terms.
5277
68
g, DSAL - SFM 4276, EC 1409
Optimization/Design Sensitivity - Bucklin
If more than one buckling subcase exists in a SOL 200 run, the program will
terminate with SFM 4276, ec 1409 in DSAL. This limitation has been removed in
Version 69.
Avoidance: If buckling optimization is used, use only one buckling SUBCASE.
5282
Documentation
Documentation - Reference Manual, CRAC2D, CRAC3D - Incorrect
Table 1 in Section 5.1 of the Version 68 MSC/NASTRAN Reference Manual indicates

that temperature loads are not supported for the CRAC2D and CRAC3D elements.
In fact temperature loads are supported for these elements.
5292
68
Aeroelastic Analysis - CAERO3, CAERO4, CA
ERO5, ADG - Datablock 107 is Missing
In Version 67.7, the static aeroelastic capability includes a divergence
analysis that can
be based on an aerodynamic model using any of the available aero methods.
However, trim and
stability analysis does not allow Strip, Mach Box or Piston theories. If the
user attempts the latter,
a SYSTEM FATAL MESSAGE indicating missing datablock 107 is output by the ADG
module. Earlier Versions of MSC/NASTRAN provide an explicit message that the
user requested capability is not supported.
5294
nswers
Dynamic Response Analysis - Modal Transient Analysis - Poor A
If a modal transient analysis is performed with eigenvalues which vary by

several orders of magnitude (the problem which demonstrated this had
eigenvalues ranging from 10e1 to 10e10), then poor answers may result. The
degradation of the answers is a result of using the single-precision LAMA table
to generate the modal matrices which are used for the integration. The problem
is not as pronounced on long word (i.e. CRAY) computers.
Avoidance: In these cases, a direct transient solution using either
superelements, or GDR would be more accurate.
5300
69
Composites - PCOMP, MAT8, IFP - UFM 315.
If either Xt or Xc or Yt or Yc or S are specified on the MAT8 entry, then Xt

and Yt and S must also be specified even though the FT field on the PCOMP entry
is blank indicating that no failure calculation is to be performed. If some
but not all of the allowable mentioned are not specified, then the run fails
and the message " USER FATAL MESSAGE 315 (IFPDRV) FORMAT ERROR ON BULK DATA
ENTRY MAT8" is encountered.
Avoidance: Always enter at least XT, YT, and S allowable terms or none at all
of XT, XC, YT, YC, and S on the MAT8 entry.
5303
2001
to Multiply Incompatible Matrices
Superelements - MPYAD - UFM 5423, Attempt
When superelements are used in a static solution and there are more subcases
for a superelement than there are for the residual structure and the load
sequence number is not specified on the SUPER command in the superelement
subcases, the program will terminate with UFM 5423 ATTEMPT TO MULTIPLY
INCOMPATIBLE MATRICES in module SDR1.
Avoidance: Ensure that the number of subcases for a superelement does not
exceed the number of residual structure subcases or specify the load sequence
number on all SUPER commands.
5304
70.5
Case Control - SET - No Warning Message
The documentation states that a SET may be redefined in the case control. This
is true, however, the second definition is ignored and the first one is used.
No warning message is issued and this is inconsistent with the design of other
Case Control commands that are defined twice.
5325
7777
70.5
Transient Analysis - TRD1 - SFM 4276, EC
A floating point overflow can occur when the uncoupled integration algorithm is
used in module TRD1. It is believed that this occurs when unrealistic
parameters are chosen. The modal mass, damping and stiffness for the problem
that failed were Mi = 1. , Bi = 2.5+5 , and Ki = 6.9389-18 .
Avoidance:
the coupled
spring to a
proortional
The error can be avoided by setting PARAM NONCUP = 1 , which forces

integration algorithm. Another avoidance is to add a very small
DOF active in this mode so that its eigenvalue is larger. Ki is
to the eigenvalue.
5331
Material Nonlinear Analysis - TEMP(LOAD) - wrong answers
Using Solution 106 with HEXA, PENTA or TETRA elements having midside nodes and
temperature loads gets wrong answers because the material properties are not
updated properly. The error occurs because TEMP(LOAD) is used to determine the
temperature dependent material properties for module SSG1, which generates the
loads, but the temperature dependent material properties are ignored for module
SDR2, which provides data recovery.
Avoidance: There are two possible avoidances for V67
1. This avoidance uses the SOL 101 method in module SSG1 and requires that no
nonlinear elements except GAPS exist in the deck.
COMPILE NLSTATIC SOUIN=MSCSOU NOLIST NOREF
ALTER 177,177 $ REPLACE SSG1, VERSION 67
MESSAGE //'SUBDMAP NLSTATIC, MODULE SSG1, APPROACH=ALL ' $
SSG1
SLT,BGPDTS,CSTMS,SILS,EST
5335
68.2
Aeroelastic Analysis - FA1 - Wrong Output
Starting in Version 67.5 of MSC/NASTRAN the "less critical" real flutter roots
are printed for informational purposes. However, this printout is incorrect
when these roots are "almost" real roots.
Avoidance: Turn DIAG 39 on to request printout of all the roots in order to
get a complete picture from this printout.
5336
70
,Missing Output
Postprocessing - DBC - SWM 6065, UWM 3030
The DBC module in MSC/NASTRAN which creates the xdb file may issue the
following warning messages:
OUTPUT LIST SYNCHRONIZATION PROBLEM FOR aaaa
VALUE =
POSITION =
n
or:
xxxxx,

*** DBCMSG ERROR MESSAGE 23 FROM SUBROUTINE ELMBLK
OUTPUT LIST SYNCHRONIZATION PROBLEM FOR aaaa
VALUE =
POSITION =
n
xxxxx,
where: aaaa is the datablock that is having problems,

xxxxx is the problem value
n is the problem position.
These messages are indication that a mis-match of data is being passed to the
DBC module. All conditions that can trigger the error are not yet fully
understood but the error appears to be
5339
69
ponents of Scalar Elements
Documentation - Coordinate System for Com
The MSC/NASTRAN Quick Reference Guide description of scalar elements should be

clarified to state that the component number for all scalar element connection
entries (CELASi, CDAMPi, CMASSi) refer to the grid displacement coordinate
system, i.e., (CD) on the GRID entry.
5341
69
Plotting - XYPLOT, XYTRAN - UWM 979, Punc
h Output Constains Control Charachters
The XYTRAN module may encounter a traceback, output control charachters and/or
incorrectly issue USER WARNING MESSAGE 979 indicating that elements do not
exist.
5349
Miscellaneous - OUTPUT2 - Output Written to Log File
If a user-written DMAP alter uses OUTPUT2 without specifying the output unit,
then the default value of 0 is used for the output unit. On some systems, unit
0 is a valid unit and a file will be created. On other systems, it may not be a
valid unit and the results may be unpredictable. On the IBM RS/6000 and the
SGI, it will write the information to the log file.
5350
MSGMESH, MSGSTRSS, MSGVIEW - MSGMESH, IFP - UFM 2052
If free format is used in conjunction with MSG/MESH, and the individual field
exceeds 8 characters, then the extra characters may be treated as the next
field in MESH command which can lead to unexpected results. If this extra data
is invalid for MSG/MESH, then the job may fail UFM 2052 or other fatal messages
depending on the type of error.
SPC,101,60817,1,0.0066767
when used in conjunction with MESH will generate the following error message:
0*** USER FATAL MESSAGE 2052, UNDEFINED GRID POINT 7 IN SINGLE-POINT CONSTRAINT
SET 101
Avoidance: When using MESH and free format, keep within the 8 field format.
5353
70.5.1
Plotting - PLOT - SFM 4276 EC 3002, FREAD
If structure plots are requested for CTRIAX6 elements, then the job will fail
and the message "SYSTEM FATAL MESSAGE 4276 ERROR CODE 3002 FREAD ERROR" is
issued.
5369
69
EMP(LOAD) - SFM 6223
Grid Point Force - GPFDR, CGAP, CELAS2, T
If grid point force balance output (GPFORCE) is requested for CGAP and/or
CELAS2 elements, and there is thermal loads, then the job fails in the GPFDR
module and the following message is issued:
SYSTEM FATAL 6223 (GPFDR2), RECORD POINTED AT BY INDEX IN SCRATCH FILE IS
WRONG.
USER ACTION: CONTACT MSC CLIENT SUPPORT
Avoidance: Other than not requesting this output, there is no avoidance.
5373
2001
fails when writing OES1X in SOL 106
Postprocessing - OUTPUT2 - Neutral option
The OUTPUT2 neutral option fails when writing the OES1X datablock in SOL 106.
Avoidance: Use the binary option.
5390
Miscellaneous - OUTPUT2 - UWM 1223
On 386 and 486 ix machines, when the OUTPUT2 neutral format is used to write
out a matrix generated by the DIAGONAL module, the job may fail with the
message "USER WARNING MESSAGE 1223 - THE NRECL SPECIFIED ON THE OUTPUT2
STATEMENT IS GREATER THAN THE MAXIMUM VALUE ALLOWED FOR NEUTRAL FILES". This
error occurs only if the OPT=COLUMN option is used with the DIAGONAL module.
Avoidance: Use the DIAGONAL module to create an identity matrix and then
perform a term by term multiply with the ADD module to create a diagonal
matrix. An example follows:
diagonal mdd/identmod/'square'/0.0 $
add mdd,identmod/mdiag///1 $
output2 mdiag//0/11// $
Another alternative is to use the form=unformatted option.
Comment from JAS: This file runs properly on Windows, Linux and AIX when the
proper NDDL name ('MATRIX') is specified on the OUTPUT2 statement. If the NDDL
name is omitted, OUTPUT2 does not write the MDIAG data block to the neutral
.op2 file because it cannot find any associated NDDL description for a data
block with the name MDIAG. Because of these problems, I am marking the Quality
as "cancelled" and am reassigning it to bhe originator.
5393
69
- Wrong Answers
The EQID field on the DEQATN entry must be unique. However, no uniqueness test
is performed. Therefore, if the EQID is not unique, incorrect answers may
result or the run may issue a message stating that a "wrong number of
arguments" is provided on the DEQATN entry.
Avoidance: Do not give more than one EQID the same value.
5394
Optimization/Sensitivity - CORDiC,CORDiS - Inaccurate Results
When displacements are defined in a non-rectangular global coordinate system,

their sensitivity results are inaccurate. In turn, the associated stress
sensitivities are also affected.
Avoidance: Use a rectangular global coordinate system.
5400
swers
69
Composites - PCOMP, TEMP(INIT) - Wrong An
The TEMP(INIT) case control command supersedes the TREF field in the bulk data
section in the event that both values exist. However, for composite plate
elements that are referenced by a PCOMP entry, the TEMP(INIT) is ignored which
can lead to wrong answers.
Avoidance: If a PCOMP exists in the model, use the TREF field on the PCOMP
entry instead of the TEMP(INIT) case control command.
5401
68.1
of DATABLK CMLAMA is Incorrect
Miscellaneous - TABPRT - NDDL Description
The NDDL description of DATABLK CMLAMA is incorrect for both the unstructured
and structured solution sequences. Print labels will be wrong if the formatted
option (P3>0) is selected on the TABPRT module.
The formatted option of the OUTPUT2 module and migration is not affected by
this.
Avoidance: In the cnddls.dat file in the del directory replace the existing
DATABLK CMLAMA statement and all subsequent statements up to but not including
the next DATABLK statement with the following:
DATABLK CMLAMA TYPE=TABLE
SAMEAS,LAMA,EOF
5402
69
SFE 4276, EC 7777
PATH=MLAA1
LOCATION=DBUPX,
Heat Transfer - VIEW3D, PARAM,VIEW3D,1 -
On the HP 9000 Version 67 and later releases of MSC/NASTRAN, if the Gaussian

integration method (PARAM,VIEW3D,1) is used to compute the geometric view
factors, then the job may fail with the following message:
SFE 4276 - EC 7777 - RECEIVED SIGNAL 10 - ABORTING
Avoidance: Use one of the following avoidances to compute the geometric view
factors:
1. Add a dummy HBDY element.
2. Use the finite difference or contour integration method instead of the
Gaussian integration.
5409
69
Transient Response - OTIME - Wrong Labels
If the OTIME case control command is used on a model with superelements in SOL
109, the correct output values are calculated, but they are labeled with
incorrect time values for superelements outside the residual structure.
Although the output is given for the correct time steps as specified on the
OTIME command, the time labels appear in sequential order starting with the
initial time, as they would without the OTIME request.
Avoidance: Place all superelements in the residual structure or remove the
OTIME request.
5410
4276, EC7777
70
Nonlinear Analysis - MATS1, NLITER - SFM
On the VAX, if the elastic-perfectly plastic option is used for the work
hardening slope by letting H=0.0 (the default) on the MATS1 entry, then the job
may fail in the NLITER module and issue the message "SYSTEM FATAL MESSAGE 4276
- ERROR CODE 7777".
Avoidance: Specify a small number for the work hardening slope (e.g., 1.E-10).
5414
70.6
- Wrong Answers
Complex Eigenvalue Analysis - EIGC, CLAN
In some cases, erroneous right eigenvectors have been produced by the Lanczos
method of complex eigenvalue extraction. An unsymmetric mass matrix may be the
cause of the error. In one known case results were found to be incorrect on
the IBM RS/6000 system but correct on the DEC VAX/VMS release. Version 70.5 of
MSC/NASTRAN introduces Block Complex Lanczos eigenvalue extraction method which
will solve this problem. The new method is not yet the default and must be
selected by setting system(108)=4.
Avoidance: There is no avoidance. However, it is recommended that, if complex
eigenvectors are an
integral part of an analysis, the results be checked using the DMAP alter
contained in Section 7.5 of the MSC/NASTRAN User's Guide for Numerical Methods,
Version 67 edition.
5416
68.2
or Upstream Superelements
Superelements - SEDRCVR - Extra Output f
If a solution 106 analysis contains superelements, and output (e.g.,

displacement) is requested for the residual structure, then an error in the
DMAP results in the same type of output being printed for the upstream
superelements even though no output is requested for these superelements.
Avoidance: Insert the following DMAP avoidances:
$
$ for v67 and v67.5
$
compile sedrcvr souin=mscsou nolist noref $
alter 199,199 $
if (seid=0) then $
OFP
OUGV1,OPG1,OQG1,OEF1X,OSTR1//S,N,CARDNO $
endif $
$
$
for v68
$
compile sedrcvr souin=mscsou nolist noref $
alter 209,209 $
if (seid=0) then $
OFP
OUGV1,OPG1,OQG1,OEF1X,OSTR1,,
CSTMS,EPTS,GEOM1VU,ERROR1//
S,N,CARDNO//PVALID $
endif $
$
5418
table results
68.2
File Management Section - INIT - Unpredic
If more than one INIT statement is supplied per LOGICAL DBset, then
unpredictable results occur. For example:
INIT DBALL LOGICAL=(DB01(100),DB02(100),DB03(100),DB04(100))
INIT DBALL LOGICAL=(DB05(100),DB06(100))
creates DB05, DB06, DB03, and DB04 members of DBALL but DBO1 and DB02 are not
created. No warning or fatal messages is issued.
Avoidance: Specify only one INIT statement per LOGICAL DBset. A continuation of
the INIT statement may be specified by ending a line with a comma as follows:
INIT DBALL LOGICAL=(DB01(100),DB02(100),DB03(100),DB04(100) ,
DB05(100),DB06(100))
5422
68.2
Sensitivities, UFM 5165
Optimization/Sensitivity - DSCM2 - Wrong
MSC/NASTRAN Version 67.7 and 68 do not calculate sensitivities due to damping

effects for modal transient response. Therefore, either the sensitivity results
are not accurate or the message "USER FATAL MESSAGE 5165 (DSVG1D-1) UNDEFINED
INPUT FILE = 106, NAME = (NONE) , ERROR CODE = -6, MODULE DSVG1 IS
TERMINATED" is output.
Avoidance: Use the following DMAP avoidance for version 68 only.
compile pslgdv list noref souin=mscsou $
alter 199 $
IF ( DODFREQ>0 OR DOMFREQ>0 OR DOMTRAN>0 ) EMG,
EST,CSTMS,MPTS,DIT,,,,,,/
,,,,BELM,BDICT/0/0/S,N,NOBGG $
5423
68.2
DRESP2 - Extra Column in DSCM2 Matrix
If a DRESP2 entry does not reference a DRESP1 entry and if there are multiple
solution types (there are three: frequency response, modal transient, and
everything else), the DRESP2 entry is included in each solution type.
For this to be a problem, the DRESP2 entry must be invoked by a DESOBJ request.
The error is benign in that
the problem can only have one objective but it does manifest itself as a
duplicate column in the DSCM2 matrix.
5425
69
5225, UWM 3057, SFM 3002
Documentation - AUTOSPCR - UFM 6137, UFM
When performing nonlinear analysis, PARAM,AUTOSPC does not operate on the

residual structure, PARAM,AUTOSPCR is provided for that function. However,
PARAM,AUTOSPCR does not behave in the same way as AUTOSPC. It only operates on
the o-set. Therefore, in nonlinear analysis using AUTOSPCR, many degrees of
freedom may not be eliminated which would have been eliminated with AUTOSPC
(e.g. DOFs 456 for solid models). This could result in various fatal messages
such as "USER FATAL MESSAGE 6137 (DFMNRS/D) INPUT MATRIX IS RANK DEFICIENT,
RANK = 99 USER ACTION: CHECK MODEL","USER FATAL MESSAGE 5225. ATTEMPT TO
OPERATE ON THE SINGULAR MATRIX KLLRH IN SUBROUTINE DCMP.", "User Warning
Message 3057 Module=nliter,matrix CNVTST not positive definite","System Fatal
Message 3002 illegal input to subrouti
5428
2166
68.2
Acoustic Analysis - GIV, HOU, PARTN - UFM
If an acoustic analysis model contains massless degrees of freedom and any

transformation method of eigenvalue extraction is chosen (i.e., GIV, MGIV, HOU,
MHOU, AGIV, AHOU) on the EIGR entry, then the run fails in the PARTN module and
issues the message "USER FATAL MESSAGE 2166". This error exists in MSC/NASTRAN
Version 68.0.0 on the IBM RS/6000, SGI, HP 9000/700, SUN SUNOS and SUN SOLARIS
systems only. It has been corrected in MSC/NASTRAN Version 68 on all DEC,
CONVEX and CRAY systems.
Avoidance: A DMAP avoidance will be made available, however the simplest
avoidance is to choose the Lanczos method of eigenvalue extraction.
5429
70.5
Acoustic Analysis - VELOCITY - Meaningles
s Answers for Complex Acoustic Results
In acoustic analysis if the user requests VELOCITY=ALL in the Case Control,
then "COMPLEX ACOUSTIC RESULTS" are output for the fluid grid points only and
the standard complex velocity is output for the structure point. This is by
design intent. However, if the user requests VELOCITY=setid and the setid
contains structural and fluid points, then the program attempts to output
"COMPLEX ACOUSTIC RESULTS" for the structural points and meaningless data is
output.
Avoidance: The only avoidances are to request VELOCITY=ALL or define a set
comprised entirely of fluid points. Data recovery for structural point may
then be obtained in a subsequent restart.
5431
68.2
2011, Misleading Message
Heat Transfer - Superelements, IFP - UFM
Superelements are no longer allowed in heat transfer problems (SOl

74,89,153,159). However, if the user attempts to use superelements, a
misleading fatal message such as "USER FATAL MESSAGE 2011 NO PHBDY ENTRIES FOR
CHBDYP" is issued.
Avoidance: Use Solution 101 with app heat or remove the superelements.
DMAP avoidance
compile phase0, souin=mscsou, nolist, noref $
alter 32 $
type parm,nddl,logical,n, nlheat $
if ((nose > -1) and nlheat) then $
$
message //' ' $
message //'dmap fatal error: superelements are not allowed' $
message //'
message //' ' $
exit $
in nonlinear heat transfer analysis' $
$
endif $
5435
68.0.1
OST, DBC - Missing Output
Optimization/Design Sensitivity - PARAM,P
When PARAM,POST,0 is used in a SOL 200 design optimization analysis incomplete

data is output to the .XDB file. The results for first design cycle are missing
from the output. The result for only the last design cycle is output to the XDB
file. Also, the qualifier corresponding to the last design cycle (DSN=)
incorrectly identifies the data as the first design cycle. i.e. the DSN was set
to 1 instead of 5. This error effects MSC/NASTRAN Version 68 on the IBM RS6000,
SUN SUNOS, SUN SOLARIS, HP 9000/700 and SGI releases only. The error is
corrected in Version 68 on the CRAY and all DEC releases.
Avoidance: The following alter may be applied to avoid this error:
compile super3 souin=mscsou noref nolist
alter 88
type parm,,i,n,descycl1 $
descycl1=descycle $
5437
68.0.1
T, VIEW - Inefficient Restart
Nonlinear Heat Transfer - SOL 153, RESTAR
In a nonlinear heat transfer restart with SOL 153 that does not change view
factors; e.g., changes in boundary conditions, MSC/NASTRAN Version 68.0.0
unnecessarily recalculates the view factors . This error exists in MSC/NASTRAN
Version 68.0.0 on the IBM RS/6000, SGI, HP 9000/700, SUN SUNOS and SUN SOLARIS
systems only. It has been corrected in MSC/NASTRAN Version 68 on all DEC,
CONVEX and CRAY systems.
Avoidance: Insert the following alter in the restart run(s):
compile nlscsh souin=mscsou noref nolist
alter 226
putsys(0,109) $
alter 227
putsys(1,109) $
5442
68.2
LOAD - UFM 2166
Transient Heat Transfer - PARTN, OTIME, D
In MSC/NASTRAN Version 68, if the OTIME case control option is used to reduce
the output and the problem has constant boundary conditions, fixed with SPC
entries, but does not have a DLOAD, then the run fails and issues the following
message " USER FATAL MESSAGE 2166, MATRIX TO BE PARTITIONED IS OF SIZE *** ROWS
BY *** COLUMNS."
Avoidance: Define at least one time-varying load using DLOAD in conjuction with
TLOAD1 or TLOAD2 entries to fix the temperatures instead of the SPC entry.
DMAP avoidance:
compile sedisp, souin=mscsou, nolist, noref $
alter 194,195 $
MODACC CASEDR,OL1R,YS,,,/OL1DUM,YS1,,,/APP1 $
PARTN
YS1,COLP,/YQ ,,,/1 $
SDR1
USET,,UL1,,YS1,GOA,GM, , , ,/UG,, /
1/'STATICS'/-1 $
endalter $
5443
le
68.0.1
Documentation - NEWS - Incomplete NEWS Fi
The MSC/NASTRAN news file delivered with MSC/NASTRAN Version 68.0.0 on the HP,
RS6000, SunOS, Solaris, and SGI is incomplete. The correct news file is listed
below with "***" next to the lines omitted in the delivered news file:
Welcome to MSC/NASTRAN Version 68
MSC/NASTRAN Version 68 adds the following major new capabilities:
*
*
*
*
*
*
*
*
*
*
*
*
Completely rewritten documentation, including online delivery

Shape optimization
Dynamic and acoustic optimization
Superelement optimization
Aeroelastic optimization
P-version elements and adaptivity
3D slideline contact
Additional hyperelastic elements
Improved differential stiffness
Substantially enhanced heat transfer
Multiple boundary conditions in SOLs 101, 103, and 200
Perform
5444
ect Labeling
68.0.2
Eigenvalue Analysis - ESE, MODES - Incorr
Element Strain Energy output is incorrectly labeled when the MODES command is
used. If an ESE request is made for the first mode then all ESE output is
labeled as mode 1. If no ESE request is made for the first mode, then all
subsequent requests are labeled as mode 0. This error is a result of an
attempt to fix error 3560. The correction to 3560 has been removed in Version
68.0.2
5446
s
70.7
P-Elements - GPFORCE - Meaningless Answer
If a model is comprised entirely of P-elements, a request for GPFORCE is

ignored. If the model contains P and H elements an attempt is made to process
the GPFORCE request for the P-element internal grid points but the results are
incorrect.
Avoidance: Ignore GPFORCE output request for the P-element degrees of freedom.
By default the IDs of the internal points are greater than 101000000. The ID
of the first internal grid point may be adjusted by the user by setting
SYSTEM(178) or its alias SYSTEM GNSTART.
5447
tation
Documentation/Reference Manual - P-Elements - Missing Documen
There are several undocumented SYSTEM cells that relate to P-element and the
internal generation of IDs. These system cells, there defaults and their
aliases are documented below:

SYSTEM ALIAS
DEFAULT
DESCRIPTION
178
179
180
181
182
183
101000000
110000000
111001001
120000000
100001001
200000000
Adaptive Grid Start ID

Adaptive Grid Maximum ID
VU-Grid Start ID
VU-Grid Maximum ID
VU-Element Start ID
VU-Element Maximum ID
GNSTRT
GNMAX
VGSTRT
VGMAX
VESTRT
VEMAX
5448
beled Output
2005.0.2
Buckling Analysis - Superelements - Misla
Upstream eigenvector data recovery in buckling analysis incorrectly identifies

the output as the first subcase. The eigenvalue label is correct.
5454
Miscellaneous - SEMAP - Wrong Resource Estimates
In Version 67+ systems, the disk space estimate printed in the "Estimation Data
for Superelement x" generated by SEMAP is not accurate. In Version 68, for
large problems, the time estimates may also be quite meaningless since these
formulas are based on nonsparse methods and the default solver is the sparse
solver.
Avoidance: There is no complete avoidance. The time estimates from the
DECOMP, FBS and MPYAD modules can be used instead. The DECOMP estimate is
printed by default in the Execution Summary (f04 file). The MPYAD and FBS
estimates can be obtained in the f04 file by requesting DIAG 19 in the
executive control section.
5455
68
45, Incorrect Format
Postprocessing - OUTPUT4, ASSIGN - UWM 64
On the MSC/NASTRAN Version 67.5 SCO Unix system, if FORM=FORMATTED output is

requested with the OUTPUT4 ASSIGN statement, then the OUTPUT4 file generated
may not be in an 80 column format. This is most likely to occur if a
non-default number of significant digits is requested on the OUTPUT4 statement.
The message "USER WARNING MESSAGE 6445, INTPTYP, INPUTT4 FAILS WITH FORTRAN
IOSTAT=10006" may also appear in the OUTPUT4 file. The values generated in the
OUTPUT4 file are correct. Only the format is different.
Avoidance: Add RECL=80 to the ASSIGN statement.
5458
68.1
Database - DBCRT - SFM 446
If NASTRAN attempts to lock a database file that resides on a swap partition

(memory), MSC/NASTRAN Version 68 on the SUN 4 issues the message "SYSTEM FATAL
MESSAGE 446 (DBCRT) SFM 446 ERROR ATTEMPTING TO CREATE A FILE (LOGICAL= xxx )
FOR DBSET xxx WITH READ AND WRITE PRIVILEGES". The following message is also
written to the log file:
SYSTEM FATAL MESSAGE - bio_c.opnlck.fcntl
A BIO operations on a GINO file has failed.
File name: "filename"
File descriptor: n.
errno: 22 - Invalid argument
Result: -1
This error normally occurs when /tmp is defined as a swap partition and
SDIR=/tmp is set in an RC file.
Avoidance: There are two avoidances:

1) Direct the file to a non-swap partition.
2) Turn file-locking off by set
5462
68.0.2
Eigenvalue Analysis - ESE, DBC, PARAM,POS
T - Missing Output from XDB, SWM 6065
If a modes analysis contains subcases that are not numbered sequentially from
1, then element strain energy data is not output to the XDB. The warning
message "SYSTEM WARNING MESSAGE 6065 (DBC) DBCMSG ERROR MESSAGE 8 FROM
SUBROUTINE DBCESE INSUFFICIENT MEMORY TO PROCESS RELATIONAL REQUIREMENTS" is
issued in the output file. This error was introduced by the correction to
related errors 3560 and 3841.
Avoidance: Other than numbering the subcases in sequential order there is no
known avoidance.
5463
Answers
68.2
Superelements - RESTART, CSUPER - Wrong
In MSC/NASTRAN, if a CSUPER entry is added to a restart run to define an image

superelement, the system modes may not be recalculated which can lead to wrong
answers (related to error 3514). This error is most likely to occur if there
are no grid points added in the restart run.
Avoidance: Add a dummy grid point to the restart run. This grid point may be
constrained in all six degrees of freedom.
5465
or
68.2
Miscellaneous - TABTST - System Fatal Err
The example program TABTST, delivered as a utility program for MSC/NASTRAN

Verion 68 and MSC/EMAS Version 3, contains a statement that is out of order.
As a result of this error, the program loops until the buffers overflow and a
system error occurs.
Lines 216 and 317 of the TABTST source file read:
IF(IN .NE. 0) GO TO 70
IUAP=0
The order of these two lines should be reversed, i.e., the correct order is:
IUAP=0
IF(IN .NE. 0) GO TO 70
This source file is found in:
Unix:
<install-dir>/msc68/util/tabtst.f
VMS:
[.UTIL]TABTST.FOR
MVS:
UTILSOU(TABTST)
This error is present in all MSC/NASTRAN V68.0.X and MSC/EMAS Version 3.0.X
systems.
5467
5407
70.5
Buckling Analysis - EIGRL - UFM 5401, UFM
When using Lanczos for solution 105 with F1 and F2 blank on the EIGRL entry,
the following messages may be issued:
SYSTEM FATAL MESSAGE 5407.
INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES ACTUALLY
COMPUTED IN A (SUB-)INTERVAL
SYSTEM FATAL MESSAGE 5401 (REIGL). LANCZOS METHOD IS UNABLE TO FIND ALL
EIGENVALUES IN RANGE.
ACCEPTED EIGENVALUES AND ADDITIONAL ERROR MESSAGES MAY BE LISTED ABOVE.
USER ACTION: RERUN WITH ANOTHER METHOD OR ANOTHER SETTING ON EIGRL ENTRY.
Avoidance: Specify finite values for F1 and F2. Also, it is not recommended
to use system cell 146=1 to reduce scratch space without the use of finite
values for F1 and F2. Another avoidance is to set SHFSCL on the EIGRL entry
near the absolute value of the lowest execpted root.
Please se
5468
fails
68.0.2
Miscelleneous - util build - makefile.inc
The script file delivered with MSC/NASTRAN Version 68.0.0 for the util build
command is incorrect. The following messages are issued:
make ARCH=sunos EXE=../exe FFLAGS=-Bstatic build
make: Warning: Can't find `../makefile.inc': No such file or directory
make: Fatal error in reader: makefile, line 44: Read of include file
`../makefile.inc' failed
This error occurs for the following machines: Sun SunOS, Sun Solaris, IBM
RS/6000, HP, and SGI.
Avoidance: The corrected makefile follows:
#!/bin/sh
#
# This is a shar file that will replace the util shell script and makefile.
#
# Change directory to install-dir/msc68/util and run this script using
# sh, for example:
#
#
sh util.shar
#
echo "Creating util"
sed 's/^X//' << 'END_OF_util' > util
X#!/bin/sh
X#
util
X#
X#
5469
g answers
68
Complex Eigenvalue Analysis - EIGC - Wron
For the complex Lanczos method of eigenvalue extraction, an error exists that
results in incorrect left eigenvectors.

Avoidance: There is no avoidance. However, it is recommended that, if complex
eigenvectors are an integral part of an analysis, the results be checked using
the DMAP alter contained in Section 7.5 of the MSC/NASTRAN User's Guide for
Numerical Methods, Version 67 edition.
5471
ages
69
Miscellaneous - BUFFPOOL - Confusing Mess
The minimum BUFFPOOL value allowed is 15. If this minimum is violated, then in
addition to the appropriate USER FATAL MESSAGE 1287, the following misleading
fatal message appears:
*** USER FATAL MESSAGE 1286 (SEMINT)
THE VALUE SPECIFIED FOR NASTRAN SYSTEM CELL 119 IS 0
USER INFORMATION: THE VALUE MUST BE EQUAL TO -3 WHICH IS THE DEFAULT.
5475
68.0.0
AM), OUTPUT2 - UIM 1206
File Management Section - INIT MASTER(NOR
The message, "USER INFORMATION MESSAGE 1206 (OUTPN2) THE DATABLOCK OQG1
/OQG
IN AN OUTPUT2 REQUEST IS NOT DEFINED IN THE MSC/NASTRAN DATA DEFINITION
LANGUAGE (NDDL) THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT", is
improperly issued when writing to a formatted OUTPUT2 file if INIT
MASTER(NORAM) is used in the FMS section in an Unstructured Solution Sequence
run of MSC/NASTRAN Version 67.5.
Avoidance: Do one of the following.
1. Remove the INIT MASTER(NORAM) request from the FMS Section.
2. Use a Structured Solution Sequence (e.g., sol 101) instead.
5476
68.0.2
/4" Tape, error 0511-193
Installation - IBM RS/6000 - Unreadable 1
The IBM RS/6000 MSC/NASTRAN Version 68 1/4" tape may not be readable if the
block_size is changed. The following messages may be issued.
tar xf /dev/rmt0.1
the AIX 3.2.5 OS issues an error 0511-193
The 1/4" tapes must have a block_size=512, the Installation & Operation
Instructions page 4 indicate that the block size can be changed with 'chdev'
command. The tape drive block_size can be only changed with 'smit' command.
Avoidance: Use the 'smit' command.
5482
ve directory
68.0.2
Miscellaneous - Missing /msc68/util/archi
The MSC/NASTRAN Version 68.0.0 system delivered on the IBM RS/6000, SUN SUNOS,
SUN SOLARIS, SGI, and HP does not contain the following directory and its
contents:
install-dir/msc68/util/archive
This directory contains the source for utilities delivered in previous versions
of MSC/NASTRAN.
5483
69
Guide, Wrong Table for 20 Node HEXA
Documentation - CHBDYE - Quick Reference
Remark 7. under the documentation for the CHBDYE element on Page 367 of the
MSC/NASTRAN Version 68 Quick Reference Guide contains an incorrect table for
the 20 node HEXA element. The 20-noded HEXA should refer to the same table as
the 8-noded HEXA.
5485
69
Version 68 Only, Wrong Answers
Migration - QUAD4, TRIA3, PSHELL - Convex
Migration of a Version 67 or 67.5 database that contains any elements that

reference a PSHELL entry (i.e., QUAD4, QUADR, TRIA3, TRIAR, QUAD8, TRIA6) to
MSC/NASTRAN Version 68 on the Convex computer may result in incorrect answers
for plate stresses. The incorrect answers result from the fibre distance not
being migrated correctly. This error only affects the unstructured solution
sequences. This error may also affect a database that is transferred to
another machine.
Avoidance: This error is easily avoided by requesting SEMG=ALL in the Case
Control. It is recommended that the first restart of any unstructured solution
sequence database that contains PSHELL entries always request SEMG=ALL.
5486
nswers
68.2
Heat Transfer - CHBDYE, CTRIAX6 - Wrong A
If a CHBDYE specifies a CTRIAX6 element for radiation or convection along the

edge, wrong answers result because the area used for the CHBDYE option for the
CTRIAX6 is incorrect.
Avoidance: Use the CHBDYG,REV option to specify the edge of CTRIAX6 element
5489
69.1
- Wrong Answers Von Mises Strain
Miscellaneous - PARAM,CURV, PARAM,S1AM,1
The CURV module is used when stresses or strains are desired in the direction
of the projection of the x-axis of a coordinate system onto a plate. However,
the von Mises strain is incorrect if the CURV module is used with PARAM,S1AM,1.
The strains in the direction of the coordinate system projection are correct,
though.
In addition, the von Mises stress is also incorrect if the CURV module is used
with PARAM,S1M,1.
Avoidance: Don't use the CURV module for strain Von Mises output. The correct
value is obtained with normal strain output.
5490
Documentation - MPC, Nonlinear Analysis - Unexpected Answers
In nonlinear static analysis, the MPC has been implemented in SOL 66 and
later in SOL 106 to enforce the specified MPC condition within the Subcase.
In other words, the MPC constraints for each subcase are applied incrementally
to the pre-existing displacements from the prior subcase and they are not
enforced in the original configuration as SPCs.
If the displacements resulted certain values in the first Subcase,
the MPC in the second Subcase will start from the value in the first Subcase
and maintain the specified MPC condition within the specified Subcase.
This may not be consistent with the SPC specification or MPC specification
in linear solutions. However, the initial design in 1980 adopted this
convention and we have maintained upward compatibility since. I
5491
nite CPU Loop
68.0.2
Miscellaneous - SPOINT, EMA, PARTN - Infi
An error in EMA in MSC/NASTRAN Version 68 may result in models with SPOINTS

entering an infinite cpu loop in the PARTN module. This error only occurs when
the model is not resequenced, i.e., PARAM,NEWSEQ,-1 is specified. Please also
see related error 5640.
Avoidance: Resequence the model. This can be accomplished by not specifying
PARAM,NEWSEQ,-1 since method 3 is the default.
5494
69
Nonlinear Analysis - CGAP - UFM 2025
If the user defines the connecting grids in the gap element to be coincident
(closer than 1.0e-3 in V68) and a coordinate system is not specified in field 9
of the CGAP entry, then the run should fail with User Fatal Message 6459.
However, the Cray fails with the misleading message "USER FATAL MESSAGE 2025,
UNDEFINED COORDINATE SYSTEM -1".
Avoidance: Specify the coordinate system on the CGAP entry.
5495
68.0.1
, ERROR IN DMAP INSTRUCTION
Miscellaneous - RFALTER, COMPILE - UFM 22
Many of the RFAlters delivered with MSC/NASTRAN Version 68.0.0 on the IBM
RS/6000, SGI, HP 9000/700, SUN SUNOS and SUN SOLARIS systems are incorrect and
require minor modifications to COMPILE. The names of the RFAlters that are
incorrect are:
rf24d66.dat, rf26d66.dat, rf27d66.dat, rf3d66.dat, rf3d82.dat, rf47d66.dat,
rf48d66.dat, rf61d66.dat, rf66d66.dat, rf5d66.dat, rf29d83.dat, rf30d83.dat,
rf31d83.dat, rf48d83.dat, rf53d01.dat, rf61d01.dat, rf63d89.dat
Avoidance: The error in the first nine alters listed above can be corrected by
simply adding a comma at the end of the input block definition for the VECPLOT
DMAP call. For example:
Incorrect : VECPLOT UGV,BGPDT,EQEXIN,CSTM,CASECC,,/UGVB//0/1 $
Correct : VECPLOT UGV,BGPDT,EQEXIN,CSTM,CASECC,,,/UGVB//0/1 $
----------5497
68.2
Inertia Relief - SUPORT - Missing Output
In SOL 101 with a SUPORT entry (i.e., inertia relief), the forces of single
point constraint at the SUPORT entry are not output when the job is submitted
with a scratch database (i.e., SCR=YES on the nastran submit command). The
user should be aware that although the forces of single point constraint at the
SUPORT entry has been traditionally output, that there is no physical reaction
at the SUPORT point. The SUPORT entry signifies an inertia relief analysis
where the applied loads are balanced by the inertia of the structure.
Avoidance: The easiest avoidance is to submit the job with SCR=NO on the
nastran submit command.

5499
UFM 4551
68.2
Heat Transfer - CHBDYG, HEXA - UFM 6193,
If 20 node HEXA elements are used with 8 different ambient points specified,
then MSC/NASTRAN Version 68 fails with the message:
USER
INFORMATION MESSAGE 6193,
MAXIMUM NUMBER OF BISECTIONS OR MINIMUM LOAD STEP HAS BEEN REACHED.
USER
FATAL
MESSAGE 4551,
STOPPED PROBLEM DUE TO FAILED CONVERGENCE
Avoidance: It is very unusual that the user needs to specify all eight ambient
points for convection, traditionally only one ambient point is used for
convection. The user may avoid this error by:
1) Use 20 node HEXA and CHBDYG,AREA8 but on the CONV entry only asked for one
ambient point or 8 identical ambient pointS.
2) If more ambient points are needed, then the user can use a 20 node HEXA but
two CHBDYG,AREA6 need to be defined for the face convection. Please note t
5501
EC 7777
68.2
Heat Transfer - SOL 101, EMG - SFM 4276,
If a linear heat transfer analysis is attempted in SOL 101 on MSC/NASTRAN

Version 68 on the DEC ALPHA VMS or OSF/1 systems the run may fail in EMG and
the message "SYSTEM FATAL MESSAGE 4276, ERROR CODE 7777" is printed to the
output file.
Avoidance: Execute the job in SOL 153. This requires the addition of an
NLPARM Case Control and Bulk Data entry.
5503
68.2
g Answers, Missing Fatal Message
Single Point Constraints - SUPORT1 - Wron
If the SUPORT1 entry is incorrectly defined, i.e. it references a nonexistent

grid point, the entry is ignored and no messages are output. This can lead to
a singularity problem in a static analysis and no suport point being applied in
dynamic analysis. This error only occurs in MSC/NASTRAN Version 68 since this
entry is first introduced in Version 68.
Avoidance: Correct the offending SUPORT1 entry.
5505
68.2
ntinuous Parameters - UFM 4659
P Elements - Geometry Evaluator for Disco
For geometric curves and surfaces which do not have uniquely defined
parameters, elements which cross the discontinuous points may be mapped
incorrectly. For instance, an element edge which crosses from theta=350 to 10
on a circle may be mapped as a 340 degree arc rather than a 20 degree arc.
This can result in the error:
*** USER FATAL MESSAGE 4659 (EMGPSD)
DURING INTEGRATION FOR ELEMENT WITH ID
=
BAD GEOMETRY HAS BEEN DETECTED.
An avoidance is to define the curve or surface so that no discontinuous points
exist, which
may involve breaking up the existing entries. For instance, the above curve
could be defined
from -180 to +180 rather than 0 to 360.
5506
ion
68.2
Documentation - GMBC - Unclear Documentat
A GMBC entry with an LID=0, will not impose a nonzero enforced displacement.
The appropriate
degrees of freedom are constrained, but to zero instead of the displacement
value specified on the entry.
The program should be changed to enforce the displacement value.
The documentation states that for LID>0, both SPC and SPCD entries are
generated; for LID=0, only SPC entries are generated. This documentation is
meant to imply that displacements would be zero and that nonzero specifications
would be ignored. However, this is confusing since the SPC can also have
displacement values, leading the user to believe those values would be imposed.
This error has an additional related consequence. The displacement value for
the GMBC is being lost if
the GMBC is part of an SPCADD, even if
5511
ssing Output
68.2
Aeroelastic Analysis - PARAM,OPPHIPA - Mi
If there are extra points and the user requests normal modes output at the
aerodynamic grid points using PARAM OPPHIPA, the expected results do not appear
in the correct location. The eigenvector results are null for the aerodynamic
grid points.
Avoidance: A DMAP avoidance follows:
compile opph souin=mscsou nolist noref
alter 15,15
NOIS=NOMDS-NOUE $
MATGEN ,/PHPV/6/NOMDS/NOIS/NOUE $
5512
C 46
69.1
Miscellaneous - CORD2i, GP1 - SFM 4276, E
If a CORD2i entry references a coordinate system that does not exist, then the
job may fail with the following unclear message:
SYSTEM FATAL ERROR 4276.GCP
ERROR CODE
46
Avoidance: Other than locating and correcting the entry in error, there is no
avoidance.
5514
70
Rigid Elements - GPSP - Wrong Answers
When some DOFs of a grid point are attached to rigid elements it may defeat the
AUTOSPC function for the remaining DOFs. This was observed on a client problem
where two rotations at one grid point were connected to a rigid element, but
the third was not. It happens that this DOF has a very small stiffness due to
a pin flag on a beam element. The stiffness would be identically zero except
for roundoff effects. The evidence was that the eigenvector value for this
point was 8 orders of magnitude larger than any other eigenvector DOF.
Avoidance: A method to avoid this behavior, once observed, is stabilize this

point with a stiffness value or other type of constraint. In this instance,
when a ground spring of 1.E-10 was added to this DOF its eigenvector values
approached zero. Another
5515
68.0.2
Eigenvalue Analysis - EIGRL, REIGL, SYSTE
M(194), FASTIO - Incorrect Eigenvectors
The Lanczos method of eigenvalue extraction produces incorrect eigenvectors
when the NASTRAN keyword FASTIO (alternatively NASTRAN SYSTEM(194)=1) is set to
1. This error is corrected in Version 68.0.2 to be available on all platforms.
Avoidance: Do not select the FASTIO option.
5516
69
Infinite CPU Loop
DMAP - SOL 200, COMPILER, DESOPT, DPD1 -
An attempt to COMPILE the entire SOL 200 DMAP with the REF option specified in
MSC/NASTRAN Version 68.0.1 on CRAY computers may result in an infinite cpu
loop.
Avoidance: Either do not request the REF option or COMPILE individual subDMAPs
separately.
5527
70.5
UTPUT2 - Incorrect Description
Documentation - DMAP Module Dictionary, O
The OUTPUT2 records description for records 25 and 26 are incorrect in the
MSC/NASTRAN Version 67 User's Manual (Volume II Page 5.4-161). Records 25 and
26 are repeated for each column and their description needs to be the same as
records 20 and 21.
5529
tput
68.2
Postprocessing - PARAM,POST,-2 - Extra Ou
If PARAM,POST,-2 is used in Version 68 of MSC/NASTRAN, then stress and force

data is written to the OUTPUT2 file twice. The data is written to the OUTPUT2
file twice since both sets of data blocks OES1,OEF1 and OES1X, OEF1X are
output.
Avoidance: There are two avoidances.
1. Include PARAM,PATVER,2.0
in the bulk data deck.
2. Use the following alter.

COMPILE SEDRCVR SOUIN=MSCSOU NOREF NOLIST
ALTER 307,307
IF ( POST=-2 AND APP='NLST' AND SEID=0 ) THEN $
5530
4203
68.0.2
Limitation on Problem Size - SPOINT - SFM
A day one limit in MSC/NASTRAN limits the number of SPOINTs to 32,000.

5538
68.2
- Untrapped User Input Error
Optimization/Design Sensitivity - DESOBJ
The DESOBJ case control command specifies minimization or maximization of the
objective function. Section 7.3 of the Version 68 Design Sensitivity and

Optimization User Guide documents TPL test problem D200X5 and indicates
DESOBJ(MIN,MAX). The code should trap this input error but instead the first
string, in this case MIN. Thus, DESOBJ(MIN,MAX) minimizes the function, and
DESOBJ(MAX,MIN) maximizes the function. This error is fixed in MSC/NASTRAN
Version 68.2 by issuing "USER WARNING MESSAGE 639 (IFP1D) YOU MAY NOT SPECIFY
BOTH MAX AND MIN FOR OBJECTIVE THE DEFAULT VALUE OF MIN WILL BE USED".
5540
68 -
69
Documentation - Release Notes for Version
The Release Notes for Version 68 contain the following errors in Chapter 4
which describes the enhancements for Design Optimization.
1. In the middle of page 84 the following line is printed and should be removed
since it is not correct. The
sentence prior to this sentence describes the restrictions correctly.
" Superelements are not supported either in the primary model or in the
auxiliary boundry models."
2. The example problem specified on page 85, 86 and 87 is in the Version 67.7
format. The converted deck for Version 68 may be found in the directory
$MSC_BASE/msc68/nast68/misc/doc/desopt. The deck names are d200x3.dat
d200x3s.dat.
5541
ASE ID
68.0.2
Miscellaneous - ESE, PUNCH - Missing SUBC
Punched Element Strain Energy (ESE) is missing the value for the SUBCASE ID.
This error occurs on all Version 68.0.0 and 68.0.1 systems. This error
resulted from an attempt to correct error 3560. MSC/NASTRAN Version 68.0.2
removes the correction to error 3560 to correct this error. Please not that
this error is considered fixed in 68.0.2 and later systems even though the
subcase identifier is not always correct. The punched subcase identifier has
the same limitations as the f06 output. Please see errors 3560 and 3841.
Avoidance: Either request Version 68.0.2 or use Version 67.5.
5544
68.2
CFORCE - Excessive CPU time
Transient Response Analysis - SPCFORCE,MP
If SPCFORCEs or MPCFORCEs are requested in SOL 112 and PARAM,DDRMM is 0

(default), then their computation can take a substantial amount of CPU time
compared to Version 67.5. (Version 68 only).
Avoidance: Do not request MPCForce or SPCForce output or insert the following
DMAP alter:
compile cforce souin=mscsou noref nolist
alter 9,13
EQUIVX UhY/UY0/-1 $
alter 21,21
IF ( NOMXY>-1 ) MPYAD
MXY1,uy,/QMX1 $
IF ( NOMXY>-1 ) MPYAD
QMX1,ACCE,/QMX $
alter 23,23
MPYAD
BXY1,uy,/ QBX1 $
MPYAD
QBX1,VELO,/QBX $
alter 29,29
MPYAD
MPYAD
endalter
KXY1,
QKX1,
uy, / QKX1 $
disp, / QKX $
5545
69
t Written to OUTPUT2
Documentation - PARAM,POST,-2 - OGPFB1 No
The Grid Point Force datablock is not output to the OUTPUT2 file when
PARAM,POST,-2 is specified, even though the documentation claims otherwise.
Furthermore, attempting to force this output by including PARAM,OGPF,YES does
not work.
Avoidance: For Version 68 use the following DMAP avoidance,
COMPILE sedrcvr souin=mscsou nolist noref
alter 270,270
IF ( OGPF='YES' ) THEN $
ENDALTER
For version 67.5 include the following DMAP alter
COMPILE sedrcvr souin=mscsou nolist noref
alter 260,260
IF ( OGPF='YES' ) THEN $
ENDALTER
5549
68.2
,-2 - Wrong Datablock Output
Postprocessing - ESE, OUTPUT2, PARAM,POST
In solution 103, PARAM,POST,-2 OUTPUT2s the LAMA datablock as OLB. This

causes problems for the SDRC Dataloader program. The LAMA table is only needed
if element strain energy output is requested for SDRC/IDEAS. This error occurs
in Version 67.5 and 68.
Avoidance: The error may be avoided by using the following DMAP alters.
Version 67.5 DMAP avoidance:
compile sedrcvr souin=mscsou nolist noref
alter 271,271 $ v67.5
matmod olbm,,,,,/lama,/13 $
output2 lama,onrgy2//otape2/ounit2//omaxr $
------------------------------------------------------Version 68 DMAP avoidance:
COMPILE SEMODES SOUIN=MSCSOU, NOLIST, NOREF $
ALTER 115 $
CALL DBSTORE LAMA,,,,//0/0/'DBALL'/0 $
COMPILE SEDRCVR SOUIN=MSCSOU, NOLIST, NOREF $
ALTER 93,93 $
CALL SDRCFIX OUGV1/DUM/OTAPE2/O
5554
68.2
P-Elements - EMA, CORDi - Wrong Answers
If p-elements are mixed with h-elements and grid points that are attached to
the h-elements have an output coordinate system specified other than the basic
coordinate system, then the transformation to the global coordinate system is
not performed. This leads to an incorrect stiffness matrix and wrong answers.
Avoidance: If h-p elements the output coordinate system should be the basic
system throughout the model.
5555
Superelements - CORD1 - UFM 2004
CORD1-type coordinate systems cannot be used as either the location coordinate

system or the output coordinate system for grids in one superelement if the
grids used to define the CORD1 coordinate system belong to another
superelement. The job will end with one of the following USER FATAL MESSAGES:
2004, 2006, 2104. Similarly, CORD1-type coordinate systems should not be
referenced on SURFACE or VOLUME GPRSTRESS requests if superelements are
present. Otherwise, GPSTRESS results will be missing for superelements which do
not recognize the coordinate system and USER WARNING MESSAGE 4598 will be
issued.
Avoidance: Use CORD2 type description.

5556
2004
s Guide - Incomplete Data Listing
Documentation - Design Optimization User'
Listing 7-7 in the Design Optimization User's Guide for Version 68 is missing a
few lines of input data. This data is the Von Mises stress constraint data for
the analytic boundary shapes example in Section 7.6 of the guide.
Avoidance: Refer to the TPL deck D200AM3.dat for the correct listing. The
documentation will be updated in Version 69.
A new user's guide based on MSC.Nastran 2004 has been developed and is now
available electronically and will soon be in hardcover. EHJ 1/2004
5557
68.2
SOl 159 - UFM 5423
Nonlinear Transient Analysis - MCE2, MPC,
Solution 159, nonlinear transient heat transfer, with a stuctural problem that
contains an MPC fails with the following fatal message "USER FATAL MESSAGE
5423---ATTEMPT TO ADD INCOMPATIBLE MATRICES, (SADD5)". This message is output
from the MCE2 module in subdmap SEMR2. The same problem runs to completion in
SOL 129 with a correct solution.
Avoidance: Use solution 129 for the nonlinear structural problems.
5560
68.2
206 and Missing Output
Postprocessing - PARAM,POST,-1/-2 - UIM 1
When using param,post,-1 or -2, param,patver,2.0 and/or param,ougcord,basic,

and form = formatted on the ASSIGN OUTPUT2 statement the following message is
issued:
0*** USER INFORMATION MESSAGE 1206 (OUTPN2)
THE DATABLOCK ***/*** IN AN OUTPUT2 REQUEST IS NOT DEFINED IN THE
MSC/NASTRAN DATA DEFINITION LANGUAGE
(NDDL) THIS DATABLOCK WILL NOT BE
TRANSLATED TO NEUTRAL FORMAT
Avoidance: Insert the following DMAP Alter:
compile sedrcvr souin=mscsou,nolist,noref $

alter 74,74 $
output2 ougv1pat//otape2/ounit2//omaxr/'oug' $
alter 78,78 $
output2 bophig//otape2/ounit2//omaxr/'oug' $
alter 81,81 $
output2 bougv1//otape2/ounit2//omaxr/'oug' $
5563
68.0.2
Will Not Create New File.
Miscellaneous - ACCT=YES - Missing Data,
The MSC accounting function in the nast68 script, which is called out on the
submittal line with the command acct=yes, has several errors:
1) The username, product, and version are blank in the accounting file.
2) If the acct file does not exist, the script does not create a new
acct/mscYYMM.acct file.
Avoidance: To correct the second item comment out the following lines in the
nast68 script:
#
#
#
#
test -w "$MSC_ACCT" || {
echo "No permission to write accounting file $MSC_ACCT"
MSC_ACCT=""
}
or create a new accounting file every month. However, the best alternative is
to use the Nastran 68.0.2/Emas 3.0.2 script.
5565
68.2
ified as Scalar Matrices
Miscellaneous - OUTPUT2 - Tables Misident
Some tables may be misidentified as scalar matrices during OUTPUT2 neutral

processing. The error occurs when the datablock trailer meets all three of the
following conditions:
1. The trailer word 4 is greater than or equal to 13.
2. The trailer word 2 is greater than 0 OR trailer word 3 is greater than
0.
3. The trailer word 5 is between 1 and 4, inclusively.
5567
70
- SOL 101, AXMPR1- SFM 3001
Optimization/Design Sensitivity Analysis
If auxiliary models are defined in SOLs 101 through 159 then the run will fail
with SYSTEM FATAL MESSAGE 3001 being issued from the AXMPR1 module.
Avoidance: Remove all auxiliary models.
5568
68
- PARAM,PATVER
Documentation - V68 Quick Reference Guide
The MSC/NASTRAN Version 68 Quick Reference Guide documentation for

PARAM,PATVER,2.0 incorrectly indicates that the OES1X datablock is output.
This error is corrected in the 2nd printing of the Version 68 Quick Reference
Guide.
5569
68.1
Miscellaneous - MACOFP - Infinite Loop
If spill logic is necessary in the MACOFP module, then the module may go into
an infinite cpu loop. Note that the MACOFP module is only used in user DMAPs.
Avoidance: Because the VAX has a smaller default buffsize then other systems,
this error has only been observed on the VAX VMS system. The avoidance is to
increase buffsize. A value of 4 times the default is suggested.
5570
M 5037
Old Design Sensitivity - CBEND, DVSET - UFM 316, UFM 2040, SF
According to Remark 7 in the MSC/NASTRAN Quick Reference Guide for the DVSET
entry there is a way to perform design sensitivity analysis on the BEND element
using the original design sensitivity capability of SOl 53. However, if this
is attempted, the analysis fails with the following fatal messages:
1. "USER FATAL MESSAGE 316 (IFPDRV) ILLEGAL DATA ON BULK DATA CARD DVSET 111
SORTED CARD COUNT = 3"
2. "SYSTEM FATAL MESSAGE 5037 UNEXPECTED EOR READING DVSET CARDS OFF EDT-- DSTA
MODULE TERMINATED IN DSTA"
3. "USER FATAL MESSAGE 2040, SINGULAR MATRIX FOR ELEMENT 1"
Avoidance: Replace the BEND element with multiple BAR elements.
5571
10 - UFM 6390
68.2
P-Elements - GPOA, HEXA20, PENTA15, TETRA
If h-elements with midside nodes (HEXA20, PENTA15, TETRA10) occur in a model

with p-elements, the analysis
fatals and the message "USER FATAL MESSAGE 6390, (GPOA), ELEMENT ID = *** TYPE
HEXA20 OR PENTA15 AND/OR TETRA10 ARE NOT SUPPORTED IN P-ELEMENT ANALYSIS" is
output. The analysis should be allowed to proceed if the midside nodes do not
occur on the edge of a p-element. In addition, the error message reports the
Property ID instead of the Element ID.
Avoidance: Remove the midside nodes from the aforementioned h-elements.
5572
68.2
P-Elements - FEFACE, GMSURF - SFM 3007
When the SURFID field of the FEFACE entry is specified and there are no
corrosponding GMSURF entries, then the following poor message is issued,
"SYSTEM FATAL MESSAGE 3007 MODULE = GP0 ILLEGAL INPUT TO SUBROUTINE EVLCRD
FATAL ERROR".
Avoidance : Remove the SURFID fields on the FEFACE entries if the corrosponding
GMSURF entries do not
exist.
5573
t Restart
69
Nonlinear Analysis - RESTART - Inefficien
In nonlinear analysis restarts, some residual error may be inadvertently

carried over from the previous run. This may cause extra iterations to
convergence when compared to an equivalent run that executes the identical load
path in a single run.
Avoidance: Apply the following DMAP alter:

COMPILE NLSTATIC SOUIN=MSCSOU NOLIST NOREF
ALTER 307,307 $ V681T1
MPYAD KGG0,UGNH,PGNL/QQGNX $
UPARTN USETNL,QQGNX/,QQSVI,,/'G'/'F'/'S'/1 $ SET F-SET COMPONENTS
UMERGE1 USETNL,,QQSVI,,/QQGNI/'G'/'F'/'S'/1 $ TO ZERO MAY 23, 1995
5575
69
CHECKOUT - Incorrect Documentation
Documentation - PARAM, POST,-1,-2, PARAM,
In MSC/NASTRAN Version 68, geometry OUTPUT2 datablocks for PARAM,POST,-1 or

PARAM,POST,-2 are written to the unit specified by PARAM,OUNIT1 which defaults
FORTRAN unit 11 whenever PARAM,CHECKOUT,YES is used. This is contrary to Quick
Reference Guide documentation for PARAM,POST which states that the geometry
datablocks are
written to the unit specified by PARAM,OUNIT2 which defaults to FORTRAN unit 12.
5578
68.0.2
pression Program
Installation - Unable to Locate the Decom
The local tape option cannot be used to install MSC/NASTRAN V68 or MSC/EMAS V3
on a Cray system where the tape mount daemon, tpdaemon, is running. The tape
mount deamon runs on ALL Cray mainframe systems; it is an option on EL systems.
Instead, the tape is mounted using tpmnt and used by mscsetup as a local disk
archive file.
Avoidance: The commands to load MSC/NASTRAN V68 or MSC/EMAS V3 when tpdaemon is
running are:
# Mount the tape files. Note: <vsn> must be 1 to 6 characters.
$ rsv TAPE
$ tpmnt -l nl -v <vsn> -p /tmp/MSC68.1 -q 1 -b 10240 -g TAPE -r out
$ tpmnt -l nl -v <vsn> -p /tmp/MSC68.2 -q 2 -b 10240 -g TAPE -r out -w
# Extract mscsetup et al
$ tar xvf /tmp/MSC68.1
# Run mscsetp
$ sh mscsetup
.
.
.
3
<- Select a loca
5579
4562
68.2
Transient Nonlinear Analysis - TRLG - UFM
When performing a transient nonlinear analysis (Sol 129) with superelements,

the fatal message " USER FATAL MESSAGE 4562, TSTEP (TIME STEP) DATA IS MISSING"
is output when attempting data recovery on the first non-residual superelement.
This is a Version 68 only error.
Avoidance: Remove all requests for SPCFORCEs, MPCFORCEs, OLOADs
from the superelement subcases or insert the following DMAP avoidance.
COMPILE SEDISP SOUIN=MSCSOU NOREF NOLIST

ALTER 180
NONLNR0=NONLNR $ THATS A ZERO AT THE END OF NONLNR0
ALTER 218,218
IF ( SEID<>0 AND (NOQG>-1 OR NOQMG>-1) AND
NOT(APP='CEIGEN') AND NOT(NONLNR) ) THEN $
5583
68.0.2
Read/Write Access to Filname++
Miscellaneous - Install Script, NFS - No
The nastran script in 68.0.0 and 68.0.1 uses the plus sign, `+', as a delimiter
when processing the command line. Unfortunately, this character is typically
used by NFS on the Cray to generate temporary filenames. As a result,
filenames using the plus sign are mangled on the Cray. This error has been
corrected in Version 68.0.2 by using the ampersand, `&', as the delimiter.
5586
68.1
rong Answers for Resultants
Miscellaneous - VECPLOT, PARAM,GRDPNT - W
Setting PARAM,GRDPNT to other than 0 may result in wrong answers for the OLOAD
RESULTANT and SPCFORCE RESULTANT in MSC/NASTRAN Version 68. This error may also
cause VECPLOT option 4 to give incorrect
Rigid Body Vectors, which can cause "clean" models to fail rigid body motion
checks. Such checks are
performed, for example, in the model checkout alters (checka) in the SSSALTER
directory. This error
may also cause wrong answers in Inertia Relief (PARAM,INREL,-1 or INRLM,-1)
since the
vecplot module is utilized in inertia relief for computation of rigid body
motion vectors.
5590
68.2
P-Elements - EMA - Wrong Answers
If p-elements are mixed with scalar h-elements such as CELASi, then the scalar
elements are not assembled to the global matrix and wrong answers occur.
Avoidance: Use non scalar elements such as the CROD in place of scalar
elements.
5591
68.2.0
Answers, UWM 6498
P-Elements - GMLOAD, GMSURF, GMBC - Wrong
When doing p-element analysis with MSC/NASTRAN Version 68 on CRAY computers,

incorrect results occur for problems with loads defined with convective
coordinate systems. The incorrect results are preceded by the USER WARNING
MESSAGE 6498 which indicates that the equation evaluator is having difficulty
converging.
Avoidance: Don't define loads with convective coordinate systems.
5596
69
NG MESSAGE XXXX. (CURVIT-1)
Miscellaneous - PARAM,CURV,1 - USER WARNI
If PARAM,CURV,1 is specified to request element stress and/or strain output to

be computed in a material coordinate system or to interpolate the data to grid
points in a run with fewer than 3 elements that are not colinear, then the
following unnumbered message occurs:
USER WARNING MESSAGE XXXX. (CURVIT-1) LOCAL INTERPOLATION USING INDEPENDENT
VALUES WITHIN RANGE OF THE
0-TH SORTED ORDER GRID ID INVOLVED WITH RESPECT TO MATERIAL COORDINATE
SYSTEM ID =
1
CAN NOT BE COMPLETED. ILL-CONDITION MAY HAVE RESULTED FROM ALIGNMENT OF
INDEPENDENT VALUE COORDINATES.
OUTPUT FOR THE GRID ID IN QUESTION WILL NOT APPEAR.
Avoidance: Specify PARAM,OG,-1.
5597
Guide
69
Documentation - CHBDYE - Quick Reference
Remark 3 on page 366 of MSC/NASTRAN Version 68 Quick Reference Guide should be

removed because the front face of a surface element is not always associated
with the outward normal vector. The user should consult the table on Page 367
of the Guide to determine the normal orientation.
5598
68.2
ssing Displacements in OUTPUT2 file
DBC - PARAM,POST,-1 PARAM,PATVER,2.0 - Mi
In Buckling Analysis (SOL 105) when DISP=ALL is used along with PARAM,POST,-1
and PARAM,PATVER,2.0 the
OUTPUT2 file (fort.12) does not contain the
displacement information for the buckling modes.
Avoidance: The avoidance is to include the following alter,
SOL 105
COMPILE SEDRCVR SOUIN=MSCSOU
ALTER 208 $
OUTPUT2 OUGV1//OTAPE2/OUNIT2//OMAXR $
5599
68.2
- Wrong Answers
If a DVPREL1 bulk data entry has a COEFi value of 0.0 and there are also
DVPREL2 entries, wrong answers are produced for sensitivity results and
therefore for optimization. A similar error is produced if a DVPREL1 entry
references more than one design variable and there are DVPREL2 entries. This
is a Version 68 only.
Avoidance: An avoidance for the COEFi= 0.0 is to delete the 0.0 values or
replace them with very small values. There is no avoidance for the multiple
desgin variable reference.
5601
s
68.0.2
Miscellaneous - RFLAG.V68 - Fatal Message
In MSC/NASTRAN 68.0.0 there are two versions of the Lagrange Multiplier

Technique alters on the delivery tape. One is in the SSSALTER directory and an
old noncurrent copy is in the TPL.
Avoidance: Use the alter in the SSSALTER library.
5615
68.2
Eigenvalue Data
Postprocessing - OUTPUT2, .XDB - Missing
When p-elements are used in normal modes, and stress/strain output is

requested, the eigenvalue data is missing from the OES1 data block in the
OUTPUT2 and .XDB files. This means that post-processors do not have access to
the eigenvalues.
5616
GL
DMAP - DIAGONAL - UFM 5250
The DIAGONAL module issues the message "USER FATAL MESSAGE 5250, RAISING A
NEGATIVE NUMBER TO A NON-INTEGER EXPONENT IS NOT ALLOWED" incorrectly for
integer exponents when the matrix element is negative. The message should only
be issued for exponents which are not integers.
5620
6551 (INPTX2)
70
Miscellaneous - INPUTT2, PARAM,POST - SFM
"SYSTEM FATAL MESSAGE 6551(INPTX2) A READ ERROR WAS DETECTED ON UNIT XX DURING
BINARY INPUTT2 PROCESSING" may be encountered on MSC/NASTRAN Version 68.0.2 on
CONVEX computers when reading unformatted OUTPUT2 data.
Avoidance: OUTPUT2 and INPUTT2 the necessary data specifying "FORMATTED" on
the associated ASSIGN statement.
5621
Static Analysis - BEAM - Missing Force Output for BEAM
If a BEAM's forces are zero, the force results for end A of the BEAM may not be
output. This has only been observed on the CONVEX, however, there is the
potential for this error to occur on other machines.
5622
nate System
68
Documentation - PBEAM - Incorrect Coordi
Remark 10 under the documentation for the PBEAM entry is incorrect. The remark
indicates that the I1, I2 and I12 values are the Izz(elem), etc. The reference
to (elem) is not correct. The I1, I2 and I12 are determined with respect to
the neutral axis not the element (shear center) coordinate system. This
documentation error is addressed in the 2nd printing of the Version 68 Quick
Reference Guide.
5626
68.2
Nonlinear Analysis - SPARSE - UWM 4698
When running sparse decomposition in solution 106, the message:

USER WARNING MESSAGE 4698, STATISTICS FOR DECOMPOSITION OF MATRIX ***.
THE FOLLOWING DEGREES OF FREEDOM HAV FACTOR DIAGONAL RATIOS GREATER THAN ***
OR HAVE NEGATIVE TERMS ON THE FACTOR DIAGONAL"
does not list the grids/dofs corresponding to the negative diagonal terms.
It will however list the DOF's corresponding to factor diagonal ratios greater
than MAXRATIO.
Avoidance: Run the job with SPARSE=1 to identify the negative diagonal terms.
5627
68.1
Superelements - CORD1S, CORD2S - UFM 2104
If superelements are used in conjunction with spherical coordinate systems

(i.e. CORD1s or CORD2S) in MSC/NASTRAN Version 68, then the following fatal
message occurs, "USER FATAL MESSAGE 2104, UNDEFINED COORDINATE SYSTEM".
Avoidance: Remove the Superelements, use a non-spherical coordinate system or
use a prior version of MSC/NASTRAN.
5633
69
tion NAME.cfg Failed to Open
Online Documentation - Ghostview - Collec
MSC/NASTRAN Encyclopedia sometimes issues messages such as "... collection

NAME.cfg failed to open", if there are other unrelated .cfg files in the
filesystem.
Avoidance: These messages have no consequence to the operation of the
Encyclopedia and can be safely ignored.
5636
rong Answers
68.2
Cyclic Symmetry - PARAM, AUTOSPC, YES - W
If PARAM, AUTOSPC, YES is specified in cyclic symmetry analysis with dihedral

symmetry (STYPE="DIH" on the CYSYM Bulk Data entry), then grids and components
specified on the CYJOIN or CYAX Bulk Data entries may be constrained improperly
by the AUTOSPC operation. PARAM, AUTOSPC, YES is the default in SOLs 81, 82,
83, 88, 114, 115, and 118; and NO is the default in SOLs 47, 48, 77, and 78.
This is an error in Versions 67, 67.5, 67.7, 67R2 and 68 only.
Note that it is the design intent of the GPSP module to not constrain any
degrees of freedom on the CYJOIN entry. It is the responsibility of the user
to constrain any singular degrees of freedom on the CYJOIN entry. For example,
in a solids model it is the user's responsibility to constrain the rotational
degrees of freedom on the CYJOIN
5639
68.2
Moment Resultants
P-Elements - VECPLOT - Wrong Answers for
Whenever there is a CID for edges or faces of p-elements, the OLOAD and
SPCFORCE RESULTANTS for the moments are incorrect. See related error report
5586.
Avoidance: Other than not specifying a CID for edges and faces of the
p-elements, there is no avoidance.
5640
68.0.2
Sequencer - SEQP , SPOINT - Wrong Answers
In MSC/NASTRAN Version 68.0.0, when the stiffness matrix is dense, wrong

answers may result if there are scalar points (SPOINT) in the model. Wrong
answers can only occur if structural elements attach to the SPOINTs. Thus,
models that include SPOINTs only to be used as q-set degrees of freedom need
not be concerned. This error is related to error 5491.
Avoidance: Replace all SPOINTs with GRID points. (If the SPOINTs were used for
beam warping degrees of freedom, constrain D.O.F.s 23456.)
5642
70
er's Guide - Incorrect PBEAM entry
Documentation - Linear Static Analysis Us
The PBEAM entry shown in Listing 4-4 (page 87) of the MSC/NASTRAN Linear Static
Analysis User's Guide is incorrect for the example beam. Note that the
displacement output shown on page 88 will change with the modified PBEAM entry.
Avoidance: Replace the PBEAM entry shown in Listing 4-4 with the following
PBEAM entry.
PBEAM
11
-3.000
YES
-2.850
YES
-2.700
YES
21
.867
.100
.824
.200
.780
.300
12.000
-3.000
10.830
-2.850
9.720
-2.700
8.670
56.000 17.000
4.867 3.000
45.612 13.847
4.624 2.850
36.742 11.154
4.380 2.700
29.232 8.874
5644
69
ript Only Allows Default Iview File
4.867
4.624
4.380
3.930
3.000
3.201
2.850
2.579
2.700
.867
.824
.780
Online Documentation - Iview - mscdoc1 Sc
When using the MSC/NASTRAN Online Documentation, the SGI/IRIX systems attempts
to use the default Iview file even if there is an Iview file in the user's HOME
directory and even if the MSCDOC_IVIEWFILEDIR is explicitly specified.
Avoidance: Comment out lines 152-160 from the script $MSC_DOCBASE/bin/mscdoc1.
5646
68.1
s and nast68 script
Miscellaneous - FFIO has problems with nq
There are two problems that can prevent MSC/NASTRAN Version 68.0.2 running
under NQS from using EIEIO. The first error involves NQS generated filenames.
These filenames include a `.', e.g., `/tmp/nqs.++++107Yo'. When nastran
generates unique filenames, it adds `N$$.sec' where $$ is the pid and sec is
the seconds in the time, so the complete filename looks like
`/tmp/nqs.++++107Yo/N13634.17.SCRATCH'. Unfortunately, EIEIO fails to
recognize that a name of this pattern should be matched by the string '*.SCR*'.
The second problem occurs when the FF_IO_OPTS and FF_IO_DEFAULT are set in both
an RC file and as environmental variables, the RC file values override the
environmental variables. In Version 67.5, the environmental variable overrode
the RC file variables (this is the correct beh
5647
FM 6309
68.2
Nonlinear Slide Line Analysis - BCONP - U
The message "USER FATAL MESSAGE 6309, (BGLSCW ) GRID POINT ID = xxxx REFERRED
IN BOTH SLAVE AND MASTER REGIONS FOR BCONP ENTRY ID = yyyy USER ACTION : DO NOT
INCLUDE A GRID POINT IN SLAVE AND MASTER REGIONS.",
may incorrectly occur with slidelines when one of the following 2 conditions
are met:
1) Two or more master segments overlap (i.e., share one or more grids).
2) One master is connected to more than one slave segment on various BCONP
entries, and there are two or more slave segments that consist of a single
point (i.e. "a slave point" instead of a "slave segment").
Avoidance: The only known avoidance is to eliminate the occurrence of the

conditions above.
5650
s Requests
69
Plotting - XYPLOT - UWM 979, Missing Plot
In MSC/NASTRAN Version 68, if more than three XYPLOTs are requested for any
given frame, then the message, "USER WARNING MESSAGE 979, AN XY-OUTPUT REQUEST
FOR POINT OR ELEMENT ID * -****- CURVE IS BEING PASSED OVER. THE ID COULD NOT
BE FOUND IN DATA BLOCK ***", may be issued and some requested plots are
skipped.
Avoidance: When using XYPLOT do not request more than three plots per frame.
5654
Output
70.6
Nonlinear Buckling - Missing Eigenvector
There is no way to get the nonlinear buckling eigenvectors printed or sent to

an output2 file. In the buckling restart with PARAM,BUCKLE the request for
any output2 data via PARAM,POST is ignored.
Avoidance: Apply the following dmap alter:
compile nlstatic, nolist noref$
alter 530
equivx ophig/ougv1/always $
alter 543
output2 ougv1//0/ounit2//omaxr $
ofp ophig// $ Put $ in col 1 if don't want eigenvector to be printed
5656
68
t a Documented Option
Documentation - GRDSET - SEID Field is No
The GRDSET bulk data entry can be used to define the default values of the
CP,CD,PS and SEID fields for all GRID entries in the model. However, all
versions of the Quick Reference Guide and the User's Manual give no indication
that the GRDSET entry may be used for the SEID field. The 2nd printing of the
Version 68 Quick Reference Guide has been updated to reflect this capability.
5660
68.1
Case Control - GPFORCE - Missing output
When a GPFORCE = (Set ID) is used, then there may be missing GPFORCE output in
the .F06 and the punch file.
Avoidance: Specify GPFORCE=all. Best way to get around this error is to specify
dummy temperature load
as follows;
case control card,
temp(load) = setid
bulk data card,
tempd, setid, tref (see field 8th of mat1
card )
5663
ix
68.2
Elements - QUAD8, TRIA6 - Wrong Mass Matr
If midside nodes are used on QUAD8 or TRIA6 elements and a midside node is
specified after an omitted midside node, then the mass matrix for the element
is incorrect.
25%. However,
percent of the
the individual
The error for the individual element may be

in most models where midside nodes are only
total elements, for example in a transition
element should not significantly affect the
significant, up to
deleted in a few
region, the error in
results.
Avoidance: Do not specify a midside node after an omitted midside node.

5664
69
Restarts - PLOTEL - Inefficient Restarts
If a PLOTEL is the only modification in a restart, the solution will be

unnecessarily re-executed.
Avoidance: Other than not modifying the PLOTEL, there is no other avoidance.
5666
69
Miscellaneous - File Locking - Job Hangs
MSC/NASTRAN V68 and MSC/EMAS V3 may hang in link 1 if file locking is enabled
under SunOS 4.1.3_U1 (a.k.a. Solaris 1.1.1). It is not known if the problem is
present in both Version A and Version B or if it is restricted to only one of
these versions.
Avoidance: Disable file locking by setting the following system cell:
This system cell can be set in an RC file, the architecture RC file is
preferred. The name of the architecture RC file is
(<install-dir>/conf/sunos/nast68rc, <install-dir>/conf/sunos/emas3rc).
Alternatively, each affected user's home RC file may be set. The name of the
home RC file is ($HOME/.nast68rc, $HOME/.emas3rc). This may be preferred in a
file server environment where only a few of the SunOS systems using MSC/NASTRAN
V68 or MSC/
5667
68.2
cs, MODACC - SFM 3001
Optimization/Design Sensitivity - Acousti
If ANALYSIS=STATICS or SAERO is requested in SOL 200 along with an acoustic

analysis with ANALYSIS=MFREQ or MTRAN, then the run fails and the message
"SYSTEM FATAL MESSAGE 3001" is output in the MODACC module.
Avoidance: Insert the following DMAP alter:
COMPILE PHASE0 SOUIN=MSCSOU NOREF NOLIST
ALTER 374,374
IF ( FSCOUP AND NOT(DESOPT) AND
(STATICS OR CYCLIC OR NLHEAT OR AERO) ) THEN $
5668
68.2
- UFM 1126 on data block K4DD
Optimization/Design Sensitivity - UMERGE1
If structural damping is defined in SOL 200 then "USER FATAL MESSAGE 1126" may
be issued for data block K4DD in module UMERGE1 in subDMAP DPD1. UFM 1126 may
also be issued for data block GOD if an o-set exists and for data block GMD if
multipoint constraints (rigid elements or MPCs) are present.
Avoidance: Insert the following DMAP Alter.
COMPILE DPD1 SOUIN=MSCSOU NOREF NOLIST
ALTER 7
FILE K4DD=OVRWRT/GOD=OVRWRT/GMD=OVRWRT $
5672
ge
2004
Miscellaneous - UFM 307 - Bad Error Messa
If a 0 (zero) character or blank is placed in front of a bulk data entry, then

USER FATAL MESSAGE 307 is issued. However, the bulk data entry name listed in
the message is an unintelligible series of characters.
See also see 1-10515201.
5673
68.2
DMAP - REIGL - Bad Message
IF the third input datablock to REIGL is missing, an erroneous message is

issued. The message indicates that an output datablock with name of **** is
missing. This error only occurs in user DMAPs.
5674
rs
68.2
Optimization - PARAM,DSNOKD - Wrong Answe
The differential stiffness sensitivity calculation is performed under the

assumption that all the displacements are enforced (i.e,, the change in the
stiffness matrix due to the changes in the displacements are not computed). In
almost all cases, this is a very poor assumption. Buckling sensitivity for an
Euler column can be in error by a factor of 1000, and have the wrong sign.
Avoidance: It is recommended that PARAM,DSNOKD always be set to 0.0. This
neglects the differential stiffness sensitivity in the buckling sensitivity
calculation. For statically determinate structures, this is exact. For almost
all structures, this is not a bad approximation and is better than including
the incorrect calculation. The default for PARAM,DSNOKD has been changed to
0.0 in Version 68.2.
5678
68.2
DSAH - SFM 4276 EC 1409
Optimization/Design Sensitivity - OFREQ,
If an OFREQ request is present in the Case Control section and dynamic

sensitivity/optimization is being performed, then the run fails in the DSAH
module with the message "SYSTEM FATAL MESSAGE 4276 ERROR CODE 1409". (V68 only)
compile fea, souin=mscsou, nolist, noref $
alter 257 $
equivx fol1/fol/-1 $
alter 314 $
equivx fol1/fol/-1 $
endalter $
5682
68.2
set to late for CALL SETDROPT
Optimization/Design Sensitivity - DESMAX
5694
Composites - PCOMP - Missing Output
69
If data other than NO or YES is entered in the SOUT field of the PCOMP entry,
instead of fataling, the default of not writing results is used.
5696
ges
69
Superelements - Case Control - Poor Messa
If the Case Control references a nonexistant superelement, the program does not
issue a fatal message, but continues processing. It then becomes very
difficult to determine the cause of subsequent error messages indicating
missing datablocks.
Avoidance: Reference only existing superelements in the Case Control.
5699
68.2
P-Elements - EMG - UWM 6498
In some models, the elements are being mapped to the geometry incorrectly. The
warning message:
*** USER WARNING MESSAGE 6498 (EQUATION Evaluator, Get Surface Parameter)
GEOMETRY API MESSAGE FOLLOWS.
USER INFORMATION: Point not close enough.
Point: (-1.414214, 1.414213, 0.000000).
Projection Parameters: 1.000000, 0.786178.
Distance: 2.235370.
Surface: 3.
Point/Grid Id: 102.
followed by the error message:
1
DURING INTEGRATION FOR ELEMENT WITH ID
is output if the element mapping is bad enough.

Avoidance: The workaround is to split the curves or surfaces int
5700
P-Elements - ADAPT - Poor Answers
When the error is calculated for a p-element, the energy of each function at
the current p-level should be considered. However, only the last function for
each edge, face, and body is being considered. This is not a problem for edges
which only have one function for each p-level, but the other terms should be
considered for the faces and body. The result is that element errors may be
higher than reported leading to a premature convergence.
Avoidance: There is no workaround.
5703
69
Incorrect Installation Instructions
Documentation - User Modifiable NASTRAN -
The appendices of the Installation and Operation Instructions describe the

installation procedure for User Modifiable MSC/NASTRAN Version 68. The
following errors have been detected in this documentation:
SGI(IRIX)
: APPENDIX C
After all 5 steps are done final executable is named UMNASTRAN2 instead of
NAST68. Therfore
page C-6 section C.4 item 2 should read
nastran link16b exe=./UMNASTRAN2

IBM RS/6000 : APPENDIX C
Page C-5, section C.3, item 2 the compile command is incorrect. In item 2 the
following command should be
issued.
link.sh xmplbd.f
For section C.3, item 3 the commnad should read
nastran link16a exe=./UMNAST68
Page C-6, section C.3, item 4 the commnds should be
mv link16a.pch newdriver.f
5708
69.0.4
ess DOF - Wrong Answers
Complex Eigenvalue Analysis - EIGC, Massl
In a direct complex eigenvalue problem, if the model contains massless degrees

of freedom, then the answers may be wrong. A possible symptom of this problem
is the existence of spurious modes. Version 69.1 addresses this error by
issuing the following message:
SYSTEM WARNING MESSAGE 9093 (SOL10)
THE FOLLOWING DEGREES OF FREEDOM HAVE NO MASS.
USER INFORMATION: THIS CONDITION CAN PRODUCE EIGENVALUES AND EIGENVECTORS
WHICH MAY BE DIFFERENT
THAN THOSE CALCULATED IN A MODAL SOLUTION SEQUENCE; I.E., SOL 10.
USER ACTION: AT THE MASSLESS DEGREES OF FREEDOM
SPECIFY EITHER A SMALL
AMOUNT OF MASS ON CMASS ENTRIES
OR SPECIFY THE GRID AND COMPONENT ON OMIT_ ENTRIES.
Avoidance: Manually omit the massless degre
5709
69
and Optimization - Incorrect Query
Online Documentation - Design Sensitivity
Full Text Queries do not work in Chapter 7, "Example Problems," of the Design
Sensitivity and Optimization User's Guide. If a query is made on a string in
this document, the full text query tool may highlight spurious text.
Avoidance: If a user wants to search in this document, they need to go
directly to the document, then issue a Search -> Text command (i.e., a local
text search confined to this document only).
5720
68.1
ITER, TEMP(LOAD) - SFM 2085
Nonlinear Slide Line Analysis - BLSEG, NL
If slideline contact with temperature loads is attempted the message "SYSTEM

FATAL MESSAGE 2085, ELEMENT TYPE 116 NOT SUPPORTED FOR NONLINEAR ANALYSIS" is
encountered in the NLITER module.
5723
M 73
68.1
Miscelleneous - SSALTERS, checka.v68 - UF
If the checka.v68 dmap alter is used with Version 68.0.1 or newer versions of
MSC/NASTRAN, then your job may fail with the following fatal message:
USER FATAL MESSAGE 73: THE PARAMETER NAMED DESCYCL1 IS UNDEFINED.
The checka.v68 dmap alter is written for Version 68.0.0 and you will not
encounter this error if you are running Version 68.0.0. This error is due to
the change in the DMAP in Version 68.0.1 to correct error 5435.
Avoidance: Replace the following Call statement:
CALL SEDRCVR,
UG,QG,BGPDTS,EQEXINS,CSTMS,CASEDR,MPTS,DIT,
ETT,OL1S,PJ1,ESTN,XYCDBDR,GEOM2S,GEOM3X,POSTCDB,
ECTS,GPLS,EPTS,SILS,INDTA,KELM,KDICT,GPECT,VELEM,
FORCE,XYCDB,PCDBDR,USET,SLT,UH1,OL1,DLT,
FRL,SPSEL
5724
rong Answers
69
Documentation - PCOMP, TEMPP3, TEMPP1 - W
Models that specify nonzero ZO offsets on the PCOMP data entry in the presence
of thermal gradient loads (TEMPP1 or TEMPP3) produce incorrect results.
Avoidance: When using thermal gradient loads and PCOMP structure, specify any
nonzero ZOFF on the connection entry, (i.e., the CQUAD or CTRIA entry).
5727
Missing Output
68.2
Superelements - RANDOM, RANDPS, RANDTi -
If random analysis is performed (i.e., a RANDOM case control command references

RANDPS and RANDTi bulk data entries) in a model containing superelements, then
data recovery is not available for the upstream superelements. This is a
Version 68+ error.
COMPILE SEDRCVR SOUIN=MSCSOU NOLIST NOREF $
ALTER 194,194 $
dbview dynamic0=dynamics where (peid=0) $
DPD
DYNAMIC0,GPLS,SILS,USET,,/
XGPL,XSIL,XUSET,,,PSDL,,,,,XEQDYN/
-1/DUM2/0/0/S,N,NOPSDL/0/0/
0 / 1
DUM10 $
5728
68
Only, Data File Not Found
/123/
Miscellaneous - nastran script - SCO/UNIX
MSC/NASTRAN Version 67.5 under SCO/UNIX 3.2 may fail with a message indicating
the input data file is not found if the job is submitted with the .dat file
extension.
Avoidance : Submit the NASTRAN job without the .dat extension or modify the
script as follows:
At about line 190 of the nastran script:
was:
name=`basename ${jid} ${ext}`

#jid_dir=`dirname ${jid}`
nametmp=`basename ${jid}`
if [ "$nametmp" = "$jid" ] ; then
jid_dir="."
else
jid_dir=ècho ${jid} | sed "s;\/$name;;"`
fi
pid=${jid_dir}/${name}${ext}
jid=${jid_dir}/${name}
change to:
name=`basename ${jid} ${ext}`
jid_dir=`dirname ${jid}`
#nametmp=`basename ${jid}`
#if [ "$nametmp" = "$jid" ] ; then
# jid_dir="."
#else
# jid_dir=ècho ${jid} | sed "s;\/$name;;"`
#fi
pid=${jid_dir}/${name}${ext}
5733
rong Answers
2001
Composites - PSHELL, PCOMP - ZOFF Gives W
Composite ply stress and strain data recovery is incorrect in nonlinear

analysis solutions 66, 99, 106 and 129 when offsets are specified (i.e., ZOFFs
on the CQUAD or CTRIA entries).
Avoidance: No practical avoidance exists.
5736
68.1
) - SFM 6137, Rank Deficient
Matrix Methods - Sparse DECOMP, SYSTEM(69
When SYSTEM(69), a.k.a. the DECOMP system cell, is set to 16 to place a 1.0 in
the diagonal position for all null columns, sparse decomposition ignores this
setting if spill occurs. If null columns exist, this error leads to SYSTEM
FATAL MESSAGE 6137 indicating a RANK DEFICIENT matrix results. Note that
SYSTEM(69) is set to 16 within some solution sequences. The solution sequences
include cyclic symmetry.
Avoidance: Increase memory to avoid spill, select standard decompositions by
setting the SPARSE keyword to 1, or constrain the singular degrees of freedom.
5737
Loads - PLOAD4 - Creates Unnecessarily Large Tables
If a PLOAD4 entry has a large "THRU" range, a table is created in IFP

containing all numbers in the range. This can require excessive disk space for
user input files with large THRU ranges for which all of the elements in the
range do not exist.
Avoidance: Do not use large "THRU" ranges when most of the elements in the
range do not exist. It is better to either use individual entries, or a
combination of smaller THRU ranges.
5739
put
68.2
RFALTERS - RF31D81 - Missing GPSTRESS Out
The entry point for rfalter rf31d81 is incorrect as it appears on the delivery
tape, and therefore the GPSTRESS output is omited.

Avoidance: Replace the following line in the RFALTER:
alter 566 $
with
alter 572 $
5754
68.2
Insufficient Memory
Optimization/Design Sensitivity - DSAD -
The DSAD module assumes that there is sufficient memory available for 7 *
NCONSTR words of data where NCONSTR is the number of design constraints
specified on DCONSTR entries. A test of this requirement is not made until
after the data has been read in. If there is inadequate space, a machine
dependent error is issued.
Avoidance: Reduce the number of constraints or increase the available memory
using the MEM request on the job submittal.
5758
s
68.2
Cyclic Symmetry - MPCFORCE - Wrong Answer
The MPCFORCE output in cyclic symmetry analysis is not calculated correctly.

Avoidance: Insert the following DMAP alter avoidance:
COMPILE SEDISP, SOUIN=MSCSOU, NOLIST, NOREF $
$
$ CYCLIC SYMMETRY ALLOWS ONLY ONE BOUNDARY CONDITION.
$ DO NOT PARTITION ACCORDING TO NUMBER OF LOADS AS IN REGULAR
$ STATIC PROBLEM. IN CYCLIC, COLUMNS CORRESPOND TO SEGMENT OR
$ HARMONIC RESPONSES, AS REQESTED BY USER.
$
ALTER 133,133 $
PARTN
PB,,ROW/,PM,,/1 $
ALTER 134 $
IF ( APP <> 'CYC' ) THEN $
ALTER 137 $
ELSE $
EQUIVX UGI/UGJ/ALWAYS $
ENDIF $
ENDALTER $
5760
69
Elements - CTETRA - UFM 4659
If "USER FATAL MESSAGE 4659, DURING INTEGRATION FOR ELEMENT WITH ID = ***, BAD
GEOMETRY HAS BEEN DETECTED." is encountered the user has the option to continue
the run by setting SYSTEM(213)=1. This possible user action should be noted in
the text of the message.
5763
69
DMAP - APPEND - UFM 5007
The APPEND module will not append two matrices of different TYPE together. If
this is attempted, the module issues UFM 5007. Although this is clearly
documented, the fact that the MATGEN and MATMOD modules output inconsistent
matrix types may cause unsuspecting DMAPers to encounter this fatal message.
Avoidance: Check the matrix trailers to verify that matrices going into APPEND
are compatible.
5764
68.2
Optimization/Design Sensitivity - Multipl
e Boundary Conditions, GRAV - UFM 5423
If there are multiple boundary conditions and gravity and/or temperature loads
in SOL 200, the run fails
in the sensitivity analysis when it attempts to add the matrices EGM and EGKL.
The message, "USER FATAL MESSAGE 5423---ATTEMPT TO ADD INCOMPATIBLE MATRICES"
is output.
COMPILE PSLGDV SOUIN=MSCSOU NOREF NOLIST
ALTER 95,95
SSG1
SLT,BGPDTS,CSTMS,SILS,ESTDV2F,MPTX,ETTDV,EDT,,
CASESX,DIT,,,,/AG ,PTELMDS,/LUSETS/0/1/'all' $
ALTER 100,100
SSG1
slt,bgpdts,cstms,sils,ESTDV2B,MPTXB,ettdv,edt,,
casesx,dit,,,,/AGB ,PTELMDSB,/lusets/0/1/'all' $
5765
68
Missing RF47D87
Documentation - Quick Reference Guide -
Table 6. in the Case Control Command section of the MSC/NASTRAN Quick Reference
Guide indicates that STRAIN output for SOL 47 requires RF47D87. This RFAlter
has never existed.
Avoidance: Use SOL 114 to request STRAIN output in cyclic symmetry analysis.
5766
68
pported in Cyclic
Documentation - GPSDCON, ELSDCON - Not Su
The GPSDCON and ELSDCON documentation in the Version 68 Quick Reference Guide
states that these Case Control requests are valid in 114. However, when these
requests are specified in SOL 114, the following message is issued "SYSTEM
WARNING MESSAGE 6245 (STDCON), ANALYSIS TYPE =CYC IS NOT SUPPORTED IN ERROR
ANALYSIS. USER ACTION: USE STATIC ANALYSIS WITH STRESS REQUEST." This
documentation error has been corrected in the 2nd release of the Version 68
Quick Reference Guide.
5776
68.2
- Wrong Answers
DVPREL2 entries that result in initial property values that are negative
produce wrong answers in the optimizer. The problem can be observed by setting
the IPRINT parameter to at least four and observing the constraint values
inside the DOT optimizer.
Avoidance: The only known avoidance is to replace the DVPREL2 entry with a
DVPREL1 entry. This, of course, is only feasible when the relationship between
the property value and the design variables is linear.
5777
68.2
Optimization/Design Sensitivity - DOPR1,
DESVAR, DLINK - SFM 3007, Poor Message
When a DLINK entry references a non-existent DESVAR entry the following message
is issued.
SYSTEM FATAL MESSAGE 3007 MODULE = DOPR1
ILLEGAL INPUT TO SUBROUTINE DOPR1B
FATAL ERROR
Avoidance: Other than correcting the DLINK entry in error, there is no
avoidance.
5778
70
DMAP - MESSAGE - UNRECOVERABLE Error
If a MESSAGE DMAP statement contains two quote marks with no text between them
(''), then the job fails on a CRAY computer with a message in the .log file
stating:
UNRECOVERABLE error on system request
No such file or directory
Avoidance: Always have at least one character between the quotation marks
(even a blank character is acceptable).
5781
68.1
elist is supplied
script: - quelist - Script error if no qu
If the optional quelist is left off the "submit" line in the RC file as shown:
submit=qsub -nc -q %que% -x -i -l -eo -s /bin/sh %job%
then the job name to be executed in the que will have either an ampersand "&"
(Version 68.0.2 and later system) or a "+" (Version 68.0.0 or Version 68.0.1)
added to it. The improper jobname is echoed on the screen as follows:
%nast68 ck1
MSC/NASTRAN
MSC/NASTRAN
qsub -nc -q
que=large
(Sun SunOS 4.1.2) Thu Oct 20 14:11:10 CDT 1994
job ck1 submitted on queue large
largish -x -i -l -eo -s /bin/sh ./ck1.N13745.06+
This error only occurs when the quelist is left off the submit definition as
would be used when the same submit command is to apply to all que options.
Avoidance:
Change the following line in the nast68/emas3 script (about 2
5786
68.2
- Wrong Answers
Eigenvalue Analysis - EIGRL, SYSTEM(194)
The Lanczos eigenvalue extraction method may produce incorrect results when the
"High Performance Option" Number of frequency spectrum subsegments SYSTEM(197)
is set to greater or equal to 2.
Avoidance:
Do not use the "High Performance Option" SYSTEM(197).
5787
69
sis User' Guide - Incorrect Index
Documentation - MSC/NASTRAN Thermal Analy
The index of the MSC/NASTRAN Thermal Analysis User's Guide is misaligned. The
index of the Version 69 online documentation on the Thermal Analysis User's

Guide is correct.
5788
68.2
1 - Extra Output
Grid Point Force - GPFORCE, PARAM,NOGPF,-
PARAM,NOGPF,-1 does not suppress the GPFORCE output for statics and modes.
Avoidance : Either remove the GPFORCE request from the case control or apply
the following alter:
ALTER 268,268 $ v68 remove printing of gpforce
5789
68.2
Heat Transfer - CHBDYi, CONV - UFM 311
Multiple convection boundary conditions on a single CHBDYi surface are not

allowed in MSC/NASTRAN Version 68. If attempted the message:
USER FATAL
NON-UNIQUE
COUNT =
DMAP FATAL
MESSAGE 311 (IFPDRV)

FIELD 2 ON BULK DATA CARD CONV
60
SORTED CARD
14
MESSAGE 9002 (IFPL) ERROR ENCOUNTERED IN MODULE
IFP
.
SEE MESSAGES ABOVE IN THE BULK DATA ECHO.

Avoidance: Define multiple CHBDYi elements.
For example:
CHBDYE,60,1,6
CONV,60,35,1,,99
CONV,60,35,1,,99
is not allowed whereas
CHBDYE,60,1,6
CHBDYE,70,1,6
CONV,60,35,1,,99
CONV,70,35,1,,99
is allowed.
Avoidance: Define another CHBDY card and apply second set of convection
boundary condition on that card.
5797
al.
Documentation - Coupled Fluid Structure Interaction, Ref Manu
The equations describing the structural modal participation factors and the
load modal participation factors for a coupled fluid-structure interaction
problem listed on page 15.4.2-6 of the MSC/NASTRAN Reference Manual, V68 are in
error.
Z2=[-w^2 Mf + i w Bf + K ]^(-1) modal impedence
structure participation = -w^2 [PHIf] [Z2] [a]^T [XIs] where [a] is the modal
coupling matrix and [XIs] is diagonal

load participation = [PHIf][Z2]{Qf} where {Qf} is fluid modal load
panel participation = -w^2 [PHIf][Z2][PHIf]^T [Ab]^T [PHIs][XIs] where [XIs] is
diagonal
5798
68.2
for Panel Participation Factor
Acoustic Analysis - PANEL - Wrong Answers
If more than one PANEL is defined, panel modal participation results are wrong.
The results are the same for all the panels.
Avoidance:
Either run the analysis for one panel at a time or use the following Version 68
alter:
compile mpf souin=mscsou
alter 1
type db abeh $
5802
Material Nonlinear Analysis - TEMP(LOAD) - Superelements vs.
Non-Superelements
If superelements are used in a nonlinear run with temperature dependent
material properties, the superelement properties are calculated using the
TEMP(INIT), rather than the TEMP(LOAD). This is a limitation since
superelements are linear, their material properties are not changed during the
analysis. This can lead to different answers when comparing superelement models
to non-superelement models.
Avoidance: In order to use the TEMP(LOAD) for the material properties, use the
following DMAP alter in Version 68:
COMPILE SELG, SOUIN=MSCSOU, NOLIST, NOREF
ALTER 11,11
SSG1 SLT,BGPDTS,CSTMS,SILS,EST,MPTS,ETT,EDT,MJJ,CASESX,
DIT,,,,/PJX,PTELEM,/LUSETS/1//'NLST' $
5803
(bio_c.read)
69
Miscellaneous - GINO - SYSTEM FATAL ERROR
UNIX versions of MSC/NASTRAN Version 68 and MSC/EMAS Version 3 may report a

SYSTEM FATAL ERROR (bio_c.read) in the LOG file but will complete the job
normally.
Avoidance: No avoidance is necessary, the error message can be ignored.
5804
69
NSINIT ERROR 20, UFM 17
Miscellaneous - RC File - NASTRAN OLDQ4K,
"NSINIT ERROR 20 *** SYNTAX ERROR IN CONTROL FILE"or "UFM 17 UNIDENTIFIED

NASTRAN CARD KEYWORD" occurs if NASTRAN OLDQ4K is placed in a runtime
configuration file or the data deck. Refer to section 3.4 of the MSC/NASTRAN
Version 68 Installation and Operation Instructions for information on the
location and format of the runtime configuration files.
Avoidance: Two avoidances exist. Either OLDQ4K can not be the first system
cell on the NASTRAN command line or the equivalent system cell, SYSTEM(173),
must be used in place of the keyword.
5805
044, UIM 4550
Nonlinear Transient Analysis - NLTRD, RESTART - SFM 4276 EC 1
IF a model containing superelements is executed in solution 106, and then

restarted into solution 129 (using PARAM, SLOOPID), and the "METHOD" field on
the TSTEPNL entry is set to AUTO, then the job fails and the following fatal
message is issued:
SYSTEM FATAL MESSAGE 4276 ERROR CODE 1044 (BIOMSG: ERROR 1044 HAS OCCURRED IN
ROUTINE OPEN FILE INDEX (FILEX) = 0)
Immediately preceeding this fatal message, USER INFORMATION MESSAGE 4550, NEW
STIFFNESS MATRIX REQUIRED is issued. This error may happen even though the
nonlinear iteration module output indicates that all time-steps have been
successfully completed.
Avoidance: Use the default ADAPT method.
5807
70
DMAP - COMPILE - UFM 423
If a user attempts to compile a user dmap where the name of the dmap begins
with the letter "E", the job may fail with the message "USER FATAL MESSAGE 423
(ATTDBS) THE FOLLOWING PHYSICAL FILE DOES NOT EXIST
/msc/msc68/emas3/sunos/del/ESS.MASTERA".
Avoidance: Change the main dmap and SOL name so that it does not begin with
"E". This apparent error is the result of an MSC/NASTRAN feature that will run
MSC/EMAS if a deck with a 'SOL 300' or 'SOL E*' entry is submitted. If such a
SOL entry is found, the script attempts to attach the MSC/EMAS Solution
Sequences. This delivery database does not exist in a pure MSC/NASTRAN
installation.
5808
68.2
Differential Stiffness and Buckling - EIG
RL, EIGB - Wrong Answers or UFM 4683
If the a-set and g-set are the same (no SPCs, MPCs, or reduction) in any
superelement or the residual structure, then the differential stiffness matix
used in solution 105 (buckling) or the buckling option in solution 200 will not
be correct. The error may lead to wrong answers or "USER FATAL MESSAGE 4683,
DIFF. STIFFNESS MATRIX NEEDED FOR EIGENVALUE ANALYSIS".
DMAP avoidance:
COMPILE SEKDR, SOUIN=MSCSOU, NOLIST, NOREF $
ALTER 42, 42 $
EQUIVX KDGGX/KDAA/-1 $
5819
9058
69
Static Analysis - TEMP(LOAD), LSEQ - UFM
If the LOADSET, LSEQ combination and TEMP(LOAD) are specified in MSC/NASTRAN

Version 68, then "USER FATAL MESSAGE 9058" may be issued in SOL 101. This
error occurs when there are unreferenced LSEQ entries.
Avoidance: Remove the unreferenced LSEQ entries or insert the following alter:
compile sestatic souin=mscsou noref nolist

alter 59 $
PARAML CASEsx//'DTI'/nskip/7//S,N,TEMPLD $
5820
68.2
S=SAERO - Wrong Answers
Optimization/Design Sensitivity - ANALYSI
Applied loads, for example to simulate subcase dependent fuel loads, are
ignored and wrong answers are produced if a static aeroelastic design task is
submitted in solution 200.
Avoidance: Insert the following DMAP avoidance:
compile phase1dr souin=mscsou nolist noref
alter 81,81
alter 89
equivx casesx/casew/-1 $
5823
68.1
T1 entries - Wrong SPC forces
Inertia Relief - Multiple Subcases, SUPOR
If inertia relief is used in conjunction with multiple subcases each

referencing a different set of SUPORT DOFs, then the spcforces will be
incorrect. This is a Version 68 error since prior versions do not support
multiple inertia relief sets. This feature is activated with the use of the
SUPORT1 entries.
Avoidance: Insert the following DMAP alter avoidance.
compile sestatic souin=mscsou nolist noref
alter 100,100 $
CALL SUPER3 CASECC,
,UL, , , , , , , ,
CRX,
, ,,,,
PCDB,XYCDB,POSTCDB,FORCE,EMAP,MAPS,EQEXINS,
PVTS,CASES,SLT,ETT,GOAT,,LOO,CRJ,LAO,UOO,UOX,GPLS,USET,
SILS,PJ,EDT,YS,GM,PSS,KFS,KSS,QR,,,,,,
DYNAMICS,BGPDTS,CSTMS,MPTS,DIT,EST,GEOM2S,GEOM3S,ECTS,
EPTS,INDTA,KE
5829
t
69
Plotting - SEUPPLOT - Missing Plot Outpu
In SOL 103, if the SEUPPLOT command is used to generate assembly plots, plots
will be available for only the first half of the modes in the solution.
Avoidance: Apply the following DMAP avoidance in Version 68:
compile semodes, souin=mscsou, nolist, noref
alter 1
$ disable scratch LTU logic - otherwise the datablocks will
$ not be there when needed for plotting
putsys(0,192)
$
compile sedrcvr, souin=mscsou, list, noref
alter 1
type db,phidlg
$unused datablocks in SOL 103
$
alter 48 $ after sdr2
copy ug/ugcopy $
append ug,ugcopy/ugtwice $ get "double" set of solutions
$ SDR2 to get "double plot vectors"

message //'seid='/seid $
SDR2
CASEDR,CSTMS,MPTS,DIT,EQEXINS,,ETT,OL2,BGPDP,
PJ1,QG,UGtwice,EST ,XYCDBDR,OINT,PELSETS,VIEWTB/
,,OUGVxxx,,
5831
, SFM
68.2
DMAP - MATMOD, FBS, TRNSP - Wrong Answers
There is a special form of an identity matrix called a form 8. Conventional

identity matrices are form 6. This type of matrix can be generated with MATMOD
option 2, or may be generated internally in modules. The new sparse options
may have trouble with this form of matrix. Troubles observed to date include:
Wrong answers from FBS when more than one pass is required. The symptoms for
the FBS problem found to date include a solution which has about 50% more
non-zero terms than it should.
A SYSTEM FATAL MESSAGE in the TRNSP module.
Avoidance: The error in FBS may be avoided by switching back to the non sparse
methods by setting SYSTEM(126)=1. It is recommended this be done only locally
around the offending module with PUTSYS statements. The error in TRNSP may
only be avoi
5838
69
Loads - TEMP(LOAD) - UWM 4012, UFM 4017
When doing a static analysis with temperature loads in Version 68, it is

necessary to specify the temperature for all grid points in the model. If this
is not done, the following messages will be issued, "USER WARNING MESSAGE 4012,
THERE IS NO ELEMENT, GRID POINT, OR DEFAULT TEMPERATURE DATA FOR TEMPERATURE
SET 102, WITH RESPECT TO ELEMENT ID = 0","USER FATAL MESSAGE 4017. THERE IS NO
TEMPERATURE DATA FOR ELEMENT 15 IN SET 2". Unfortunately, the element ID and
set numbers are incorrect.
Avoidance: Always include a TEMPD bulk data entry in any static analysis with
temperature loads.
5839
68.2
Heat Transfer - heatconv, SPC - Cannot Co
nvert Large Field Format, Wrong Answers
The heatconv program does not correctly handle all large field SPC entries. In
particular, given the following large format SPC entry:
SPC*
1 2.00000000E+01
heatconv will incorrectly copy this to a small format entry as follows:

SPC
2.000000
Whenever the temperature fields, i.e., fields 5 & 8, exceed eight characters in
length, incorrect results will occur.
5841
2001.0.1
Composites - PCOMP, MAT2 - UFM 4291
Certain MAT2 entries that are referenced from a PCOMP are not checked for
correctness. In particular, if 13 and/or 23 terms are non-zero and the 33 term

is zero, the matrix is not positive definite. In this case MSC/NASTRAN will
create potentially incorrect PSHELL/MAT2 combinations from the PCOMP/MAT2
inputs.
Avoidance: Enter a positive definite MAT2 entry.
5843
M 4276
68.2
P-Elements - RFORCE - Wrong Answers or SF
Although it is not documented, RFORCEs are not implemented for p-elements. If

RFORCES are applied to p-elements either wrong answers or a SYSTEM FATAL
MESSAGE 4276 results.
Avoidance: Do not apply RFORCEs to p-elements.
5844
69
ssing Documentation
P-Elements - HEX20, PENTA15, TETRA10 - Mi
The CHEXA element with 20 grids, the CPENTA element with 15 grids, and the
CTETRA element with 10 grids may not be used as p-elements by referencing the
PVAL entry. If attempted, the following message is issued:
*** USER FATAL MESSAGE 6390, (GP0A),
ELEMENT ID =
1 TYPE HEXA20 OR PENTA15 AND/OR TETRA10 ARE NOT
SUPPORTED IN P-ELEMENT ANALYSIS.
USER ACTION: CHECK ELEMENT CONNECTION ENTRY OR SET ENTRY.
5848
68.2
- Poor Convergence
Optimization/Design Sensitivity - DSCREEN
The DSCREEN entry permits the user to override default screening parameters for
design optimization. This capability does not work for responses
TDISP,TVELO,TACCL,TSPC,TSTRE,TFORC,TRIM,STABDER and FLUTTER.
Avoidance: The only avoidance is to do a TABEDIT on the DSCREN datablock. The
following words correspond to the data locations for the responses
TDISP
TVELO
TACCL
TSPC
TSTRE
TFORC
TRIM
STABDER
FLUTTER
TRS
179
182
185
188
191
194
245
248
251
NSTR
180
183
186
189
192
195
246
249
252
A candidate DMAP for performing the TABEDIT is:

compile desopt souin=mscsou nolist noref
alter 41 $
call dbstore dti,dtindx,,,//1/
5849
swers
68.1
Matrix Methods - FBS - UWM 4398, Wrong An
MSC/NASTRAN Version 67.7 and 68 on the CRAY C90 computer may produce wrong
answers for models where FBS method 2 is selected. The error may be evidenced
by "USER WARNING MESSAGE 4398" which indicates "DEGREES OF FREEDOM DO NOT PASS
SYMMETRY CHECK". The error only occurs when there are strings in the factor
that are longer than 64 terms. Note that except in superelement models, that
FBS method 2 is rarely selected.
Avoidance: FBS Method 2 should be deselected by setting "FBSOPT=-1" in the
system RC file on Version 67.7 and 68 CRAY C90 computers.
5850
68.1
U Loop, Overflow Input Buffer
Miscellaneous - IFP, XRCARD - Infinite CP
Some invalid bulk data input may result in an infinite cpu loop in the routine
XRCARD. Although the exact type of input that results in this error is not
known, the specifics of the input line that resulted in this error is that the
line was over 80 characters, contained many leading blanks and included an
embedded negative, "-", sign. The infinite cpu loop has only been reproduced
on the CRAY computer but may occur on other systems.
Avoidance: There is no practical avoidance.
5852
2001
ODTRL - Bad Input Matrix
Documentation - DMAP Module Dictionary, M
If the MODTRL module is used to increase the number of columns in a matrix, the
resulting matrix is unusable in most modules, including matprn and ADD. The
cause of the error is that the matrix does
not have column headers for the added null columns.
Avoidance: The MATGEN and ADD module should be used to increase the number of
columns in a matrix. An example follows:
matgen ,/nullab/7/rn/cn $ null matrix with rn rows and cn cols. user must set
rn and cn above.
add nullab,oldmat/newmat $ trailer will match first input
equivx newmat/oldmat
$ oldmat is now 'bigger'
5858
68.2
E and MPCFORCE - Wrong Answers
Optimization/Design Sensitivity - SPCFORC
If scr=yes is used in SOL 200 with dynamic optimization or sensitivity, then

MPCFORCE and SPCFORCE output does not include mass and damping effects after
the first design cycle. (Version 68 only)
Avoidance: Specify scr=no. An extensive DMAP alter is also available if
scr=yes is desired.
5860
69
- Wrong Answers
Aeroelastic Analysis - GI, CAERO1, CAERO2
MSC/NASTRAN Version 68 on Sun computers may produce wrong answers for

aeroelastic flutter problems when aerodynamic bodies, i.e. CAERO1 or CAERO2
elements, are present.
5861
nt Results
69
Dynamics - PARAM,MODACC - Poor Displaceme
The mode acceleration method is intended to improve element stress data
recovery in dynamic solutions using modal formulations. However an error may

occur in the total displacements when free-body motions are present. This error
will NOT affect strains, stresses or constraint forces. The major problem is
that the angular displacements or pointing directions will be affected. The
problem occurs because the "improved" relative displacements are not orthogonal
to the free-body modes and create small additional displacements and rotations.
The error is proportional to the local frexibility of the SUPORT degrees of
freedom. This error is considered fixed in Version 69 by the addition of a new
mode acceleration option which is selected by setting PARAM,MODACC,1 instead of
PARAM,MODACC,0.
Th
5862
VT
Database - DBUNLOAD - UFM 3007, illegal input to subroutine P
If the dbunload is done on a long word machine such as Cray and dbload is
attemted on a short word machine, then UFM 3007, illegal input to subroutine
PVT may be issued. This error occurs only if the initial run which created the
databases had parameter specifications in the Case Control. This occurs since
the diliminator for the parameter in the Case Control is machine dependent.
1. Remove the parameter specifications from the initial run which creates the
databases.
or.
2. Use the following alter in the dbload run.
ACQUIRE NDDL
ASSIGN DBLOAD='neutrala.cray',FORM=FORMATTED
DBLOAD FORMAT=NEUTRAL
$
$ avoidance is to add the follo
5863
T EXIST (GP4)
68.2
P-Elements - GP4 - UFM 4276, CSTM DOES NO
If a model contains p-elements and there is insufficient memory in the GP4

module the message "USER FATAL MESSAGE 4276, CSTM DOES NOT EXIST (GP4) may be
output.
Avoidence: Request more memory and rerun the job.
5864
68.2
d Rigid Stability Derivatives
Aeroelastic Analysis - DIAG 50 - Unspline
For Version 68, static aeroelastic analyses (SOLs 144 and/or 200) produce
Unsplined Rigid Stability Derivatives. These data are presented only to
provide a check of the splining and are not used in the solution. For
antisymmetric models and models with no symmetry (SYMXZ = -1 or 0), the numbers
may be in error. For sideforces the error is likely to be simply one of sign.
For yawing and rolling moments, the error is less obvious.
5866
68.2
uation Entry with Multiple Cavities
Heat Transfer - RADMTX - Duplicate Contin
For the multiple cavity radiation view factor calculation, each cavity will
have a RADLST and RADMTX entry associated with it. The punch file which
contains the MSC/NASTRAN calculated RADMTX entries for each cavity contains
duplicate RADMTX continuation identifiers. Thus, subsequent restarts using the
punch file fail.
Avoidance: Since continuation identifiers are not necessary if the input is in
sequential order, blank out all the continuation identifiers in field 10 and
field 1 of the RADMTX entries.
5867
68.2
ar Matrix, Wrong Answers
Mulitpoint Constraints - SPLINE2 - Singul
The Quick Reference Guide indicates that the DTOR value input on the SPLINE2
entry must be greater than 0.0.
However, this requirement is never checked. If the user leaves DTOR field blank
the run could give wrong answers or fail due to a singular spline matrix.
Avoidance: Specify a value greater than 0.0 for DTOR.
5868
68.1
BUCKLING not in Approved List
Installation - Authorization - UFM 3060,
An authorization code for the workstation option is suppose to include

statics, normal modes and buckling. An error in the authorization code
generator resulted in workstation options not including buckling.
Avoidance: The error in the authorization code generator has been corrected.
Contact MSC for a new code.
5871
Restart
68.2
Restarts - RESTART PROJECT - Inefficient
In Version 68, the PROJECT keyword is ignored on the RESTART statement which
will result in an inefficient restart. For example,
1. The initial run creates project A:
PROJECT='A'
ASSIGN MASTER='A.MASTER', DELETE
2. The subsequent run restarts from project A into project B:
PROJ='B'
ASSIGN MASTER='A.MASTER'
RESTART PROJECT='A',KEEP
Avoidance: For SOLs 101 through 200 insert the following DMAP alter:
compile ifpl souin=mscsou noref nolist
alter 80,80
type parm,,i,,projid=1,versid=1 $
projid=1 $ set the projid to the integer equivalent of the project you are
restarting from.
versid=1 $ set the versid to the version you are restarting from $
dbdict datablk=geom1q $
alter 118,131
DBVIEW GEOM1R=GEOM1Q(WHERE version=versid and PROJECT=PROJID) $
DBVIEW
5876
69
File Management Section - EXPAND, RESTART
- SFM 4276 XIO, EXPAND, SCR300

An attempt to expand a database fails when restart is attempted in the same
run. A sample File Management Section demonstrating the error follows:
assign dbup1a='scr7a.dbup1a'
expand dbup1, logical=(dbup1a(100))
restart version=1 keep
The sample input leads to the following fatal message due to the scr300 file
being improperly defined:
"SYSTEM FATAL MESSAGE 1030 (XIO)
BLOCK NUMBER MISMATCH IN READ
SYSTEM FATAL ERROR 4276.XIO
ERROR CODE 4276"
Avoidance:
1) run an "expand" job only (i.e. expand and endjob)
2) run the restart job
5877
67.5.0.1
Miscellaneous - SCO/UNIX - UFM 3060
The SCO/UNIX Version 67.5 of MSC/NASTRAN may issue "USER FATAL MESSAGE 3060"
indicating authorization code violation during long running job with many
module changes (e.g. nonlinear).
Avoidance: There is no avoidance. This problem will be fixed on a rerelease
version (MSC/NASTRAN v67.5.0.1 for SCO/UNIX).
5880
68.2
P-Elements - TEMP - UFM 4017
All p-version models which contain thermal loads via TEMP entries and more than
one type of solid element (HEXA, PENTA, TETRA), fail with the following fatal
message, "USER FATAL MESSAGE 4017. THERE IS NO TEMPERATURE DATA FOR ELEMENT y
IN SET x".
Avoidance: If the thermal loading is a uniform temperature increase throughout
the entire structure, use a TEMPD Entry. Otherwise, the user must use an
equivalent TEMPF Entry. Also, it may be possible to use only one element type
in the model.
5881
ocumentation
69
Documentation - PARAM,BAILOUT - Missing D
MSC/NASTRAN Version 68 supports multiple boundary conditions in the structured

solution sequences. However, PARAM BAILOUT cannot be changed between subcases.
5889
68.2
- Wrong Answers
Optimization/Design Sensitivity - DRESP2
If a DRESP2 entry refers to two or more DRESP1 entries and there are DVPREL2
entries in the input file, then the sensitivities printed in the columns of the
DSCM2 matrix associated with the DRESP2 entry are in error.
Avoidance: There is no avoidance other than to recast the problem so that it
does not require the offending DRESP2,DRESP1,DVPREL2 combination.
5891
, UFM 4654
70.5.1
Elements - PENTA - Possible Wrong Answers
If a pyramid-shaped degenerate PENTA element is input to MSC/NASTRAN, USER

FATAL MESSAGE 4654 is issued warning of two corner points with the same
coordinates but the run will continue. Pyramid-shaped PENTA elements are not
supported and should not be used.
5893
69
DSEQ,6 - SFM 4276, EC 3002
Sequencer - SEQP, PARAM,NEWSEQ,6 PARAM,OL
It is possible that jobs that request param,newseq,6 prior to Version 69 or

param,oldseq,6 in Version 69 and after may encounter SYSTEM FATAL MESSAGE 4276,
ERROR CODE 3002 in the SEQP module.
By default sequencing in the SEQP module was turned off in Version 69 and
beyond. PARAM,NEWSEQ was changed to PARAM,OLDSEQ to force the user to go out
of his way to request sequencing. Thus, this error is considered corrected in
Version 69 by the fact that sequencing is no longer recommended.
5900
GL
PARM - DIM 9005, UFM 2044, SFM 3007
Material Nonlinear Analysis - RESTART, NL
If thermal loads are applied in a SOL 106 cold start, and, if in the restart,
PARAM,LOOPID is not the last loop id for the subcase prior to PARAM, SUBID then
the program will issue various misleading fatal messages. In one example the
message "USER FATAL MESSAGE 2044 UNDEFINED TEMPERATURE SET, SYSTEM FATAL
MESSAGE 3007 MODULE=NLCOMB ILLEGAL INPUT TO SUBROUTINE NLCPTM" was encountered.
Avoidance: Other than specifying the correct LOOPID, there is no avoidance.
5911
Wrong answers
68.2
Complex Eigenvalue Analysis - SPCForces -
In MSC/NASTRAN Version 68, the SPCForce results are incorrect in SOLs 107, 110,
and 145 only. The SPCForces do not include the effects of the imaginary part
of the eigenvalue which results in "undamped" SPCforces.
COMPILE CFORCE SOUIN=MSCSOU noLIST NOREF $
ALTER 47,47 $ replace DSAP
PARAML OL//'TRAILER'/1/S,N,NFREQS $ NUMBER OF Eigenvalues
TYPE PARM,,I,N,II=0,iip3,iip4 $ LOOP COUNTER
TYPE PARM,,CS,N,IOMEGAX,MOMEGX $
FILE qx1=APPEND $
DO WHILE (II<NFREQS) $
II = II + 1
iip3=6*(ii-1)+3 $ clama word 3
iip4=6*(ii-1)+4 $ clama word 4
PARAML OL//'DTI'/2/IIP3/S,N,omega $ real eigenvalue
PARAML OL//'DTI'/2/IIP4/S,N,omegai $ imag eigenvalue
IOMEGAX = CMPLX(omega,OMEGAi) $
MOMEGX = IOMEGAX**2 $
MATMOD KUx,,,,,/K
5914
68.2
Nonlinear Transient Analysis - PARAM,G,
PARAM,W3 - Incorrect Structural Damping
In MSC/NASTRAN Version 68, solution 129, the structural damping for linear
elements specified by parameters G and W3 is doubled. The structural damping

specified by GE and parameter W4 are correct. (V68 only)
compile nltran, souin=mscsou, nolist, noref $
alter 224, 224 $
ADD5
BDD0,KDDNL,K4DDNL,,/BRDD//GW3/RW4 $
endalter $
5915
Output
69
Case Control - GPSDCON, ELSDCON - Missing
Element and grid point stress discontinuity output (ELSDCON and GPSDCON Case
Control commands) cannot be requested for a single subcase or a set of
subcases. This output is only generated if the request is made for all
subcases in Case Control.
Avoidance: The user must place these commands above the subcase level or in
each subcase.
5918
69
Message, UFM 4215
Complex Eigenvalue Analysis - CEAD - Poor
When running a complex eigenvalue analysis, the message "USER FATAL ERROR
4215. COLUMN 1 OF DATA BLOCK SCRATCH IS NULL BUT ROW 1 IS NOT" may be issued.
However, this null column does not affect the solution.
5920
SFM 2090
68.2
Transient Heat Transfer - MATT4,TABLEM4 -
Contrary to the documentation , the temperature dependent specific heat, T(CP),

on the MATT4 entry, cannot be specified with the TABLEM4 entry (coefficient of
a power series). If this definition is attempted, the message "SYSTEM FATAL
MESSAGE 2090, TABLE DICTIONARY ENTRY 201 MISSING" is output.
Avoidance: Use the TABLEM1, TABLEM2 or TABLEM3 entry to specify temperature
dependent specific heat.
5922
69
12 DBSET DBALL IS FULL
Miscellaneous - ALPHA OSF/1 Only - UFM 10
On the ALPHA OSF/1 release of MSC/NASTRAN when the system runs out of allocated
disk space the job may hang. When the process is killed, the system sends the
message that the job is finished and the output files look as they should with
no indication of a problem. This error has also been observed in connection
with SFM 4393 followed by SFM 4276 Error Code 3002.
Avoidance: Other than killing the job, there is no avoidance.
5924
68.2
C - SFM 4276 EC 3021
Nonlinear Transient Heat Transfer - TEMPB
If a TEMPBC entry of TYPE="STAT" and TYPE="TRAN" is referenced in the same

nonlinear transient run, then the job fails and the message "SYSTEM FATAL ERROR
4276.WRITE ERROR CODE 3021", is issued.
Avoidance: Use SPC's to fix the constant temperature boundary condition. Use
TEMPBC TYPE="TRAN" to designate the time-varying boundary condition.

5927
68.2
37, INPUT MATRIX IS RANK DEFICIENT
Matrix Methods - MCE1, RBEi, MPC - UWM 61
Although it is not illegal to specify a DOF as independent on one rigid element

and dependent on another rigid element, if the definitions form a "closed loop"
such that DOF A is dependent on DOF B and DOF B is either directly or
indirectly dependent on DOF A, and sparse decomposition is selected the
message, "USER WARNING MESSAGE 6137, INPUT MATRIX IS RANK DEFICIENT" is output.
Avoidance: This error is corrected in Version 67 and later systems for standard
decomposition. Thus, if the user forces standard decomposition by setting the
SPARSE keyword to 1, then USER FATAL MESSAGE 6202 is produced which identifies
the rigid elements in error.
5930
UWM 2013
68.2
Transient Heat Transfer - MATT4, RADMT -
In a transient thermal analysis (SOL 159), if QVECT load is used in conjunction

with temperature dependent absorptivity. This input leads to the message "USER
WARNING MESSAGE 2013, NO STRUCTURAL ELEMENTS EXIST. FATAL ERROR" being issued.
The QVECT load is directional load such as solar load.
Avoidance: Defines a constant absorptivity value instead of temperature
dependent absorptivity value.
5931
DMAP - COMPILE - UFM 151 (LINKAR)
A DMAP compile error may be encountered when logical parameters are in a call
statement.
An avoidance is to replace the logical in the call statement with another
type, such as an integer or to delete the parameter from the subdmap call
altogether.
5933
s
GL
DMAP - DCMP, DECOMP - Wrong (Zero) Result
The DECOMP and DCMP modules have an optional set of parameters which should
give the scaled determinant (DET) and the scale factor (POWER) of the input
matrix. For the sparse methods, they are set to zero.
Avoidance: An avoidance is to select the nonsparse decomposition methods when a
determinant is needed. That is set system cell 126 to 1 (a.k.a. NASTRAN SPARSE
keyword) for symmetric matrices and system cell 209 equal to 0 (a.k.a. NASTRAN
USPARSE keyword) for unsymmetric matrices.
5934
68.1
Documentation - GMBC - UFM 315
The following message is issued when the LID field of the GMBC entry is 0 and
it contains a continuation entry, i.e., ENTITY = FEFACE and METHOD = LINEAR.
FORMAT ERROR ON BULK DATA ENTRY GMBC
SORTED CARD COUNT =
**
Remark 4 under the Version 68 Quick Reference Guide's description of the GMBC
entry should be updated to include this condition and it should be stated that
not only is the METHOD field not required but will result in a USER FATAL
MESSAGE if included.
This error is essentially the same as error 5506, it has been corrected in the
2nd printing of the Quick Reference Guide.
5935
69
Miscellaneous - ADD5 - SFM 4276, EC 70020
An error in the bufferpool logic may result in "SYSTEM FATAL ERROR 4276.BPREAD
ERROR CODE 70020" to be issued from the ADD5 module. This error is very much
problem and buffersize dependent.
Avoidance: Changing the buffersize may avoid the error but the sure avoidance
is to turn off bufferpooling prior to the ADD5 module by setting SYSTEM(119) as
follows:
ALTER xxx $ turn off buffpool just before ADD5
putsys (2,119)
ALTER yyy $ turn buffpool back on just after ADD5
putsys (3,119)
5941
69
- Missing Output
If the P1 parameter on the DOPTPRM bulk data entry is either set to the default
value of 0 or simply not specified and allowed to become the default value of
0, and the P2 field is specifed, then requested data on the P2 field is not
printed for the last design cycle.
Avoidance: Set parameter P1 to 1 to obtain the output for the last design
cycle or apply the following dmap alter:
$
$ This alter will print the design optimization output
$ for the last design cycle regardless of what the value
$ of the 'p1' parameter in the doptprm entry is set to.
$
ksh: cray.err: permission denied
$ **** THIS ALTER IS FOR VERSION 68.2 ONLY ****
$
compile desopt nolist noref souin=mscsou
alter 'CALL PREDOM'
$ dummy matgen calls to satisfy dmap complier
file cntabrgp=save,ovrwr
5946
68.2
- Uses Von Mises Only
Remark 1 for the DRESP1 entry indicates that, for stress/strain item codes that
have dual meanings, the selection is made based on the option specified in case
control. This pertains to Von Mises and Max Shear selection. Due to a
programming error, the remark is incorrect and Von Mises results will be
selected, regardless of the case control request, as it was in Version 67.
Avoidance: Users desiring to use Max Shear in a design task will have to
synthesize it from basic stress results.
5948
07
70.5
Documentation - QRG, USET, PARTN - SFM 30
If a USETi bulk data entry lists a standard MSC/NASTRAN set, such as S or M,

the program may fail in the PARTN module with the message "SYSTEM FATAL MESSAGE
3007, ILLEGAL INPUT TO SUBROUTINE".
Avoidance: This entry should only reference new sets defined on DEFUSET bulk
data entries.
5953
68.2
,DCONSTR - UFM 316
Optimization/Design Sensitivity - DCONADD
If the DCONADD entry references only a single DCONSTR entry on any continuation
entry, then the job fails and the following message is issued:
ILLEGAL DATA ON BULK DATA CARD DCONADD
COUNT =
yy
xx
SORTED CARD
An example of a DCONADD entry that causes this error is as follows:

DCONADD, 1, 10, 11, 12, 13, 14, 15, 16, +DCON1
+DCON1, 17, 18, 19, 20, 21, 22, 23, 24, +DCON2
+DCON2, 25
$
Note that the second continuation entry contains a single DCONSTR entry (25 in
this case).
Avoidance: Add a dummy DCONSTR to the DCONADD continuation entry. The limits
should be set to a large value to ensure that the constraint screening will
remove this constraint prior to performing optimization. A suggested lower
bound (LALLOW)
5956
68.2
Missing Datablocks
Old Design Sensitivity - PARAM,POST,-2 -
In MSC/NASTRAN Version 68, if sensitivity output (SENSITY command) is requested

using SOL 103 in conjunction with param,post,-2, not all datablocks are written
to the output2 file. Note this error applies only to the old design
sensitivity method. It does not apply to the new sensitivity calculation (SOL
200).
Avoidance: Insert the following DMAP alters.
compile super3 souin=mscsou nolist noref $
alter 90,90 $
gp1
GEOM1,GEOM2,,,/GPL,EQEXIN,GPDT,CSTM,BGPDT,SIL,/0/0/0 $
alter 208,208 $
alter 211,211 $
5960
69
SFM 5407, SFM 5401, SFM 4276
Buckling Analysis - EIGRL, SYSTEM(146) -
If SYSTEM(146) is set to save scratch space and reduce I/O in sparse

decomposition during a Lanczos eigenvalue buckling run, then the job fails.
Different fatal messages have been encountered including "SYSTEM FATAL MESSAGE
5407 INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES ACTUALLY
COMPUTED IN A (SUB-) INTERVAL", "SYSTEM FATAL MESSAGE 5401 (REIGL) LANCZOS

METHOD IS UNABLE TO FIND ALL THE EIGENVALUES IN RANGE" AND "SYSTEM FATAL
MESSAGE RECOVERY ERROR CODE 7777" in sparse decomposition.
Avoidance: Do not use SYSTEM(146) during a Lanczos buckling run.
5961
ers
68.2
Heat transfer - SET1, RADCAV - Wrong Answ
If the SET identification pairs for the calculation of global view factors
exceeds 10 pairs, then an erroneous result is output for the global view
factors. The documentation states that only 10 pairs can be shown for one run.
This limit is expanded to 30 in Version 68.2.
5962
70.5
- UFM 4276, EC 3007
Acoustic Analysis - REIGL, SUPORT, MERGE
SUPORT entries do not work in acoustic analysis. USER FATAL MESSAGE 4276,
ERROR CODE 3007 from subroutine merge called from the REIGL module is issued.
Other eigenvalue extraction methods result in other fatal messages.
Avoidance: Remove SUPORT entries.
5963
utput
69
Case Control - STRAIN(CORNER) - Missing O
If a STRAIN(CORNER) request is made without a STRESS(CORNER) request, only

centroidal strains are output.
Avoidance: Request STRESS(CORNER,PLOT) in the Case Control Section.
5977
69
Buckling Analysis - SPCD - Wrong Answers
If SPCD entries are used in SOL 105 and the SUBCASE used for the buckling
analysis does not contain a call for a LOAD set using the SPCDs, the SPCD
entries are ignored in the solution.
Avoidance: Either use different SPC sets for each SUBCASE, or include a LOAD
command in the buckling SUBCASE pointing to the SPCD set.
5981
Time, SFM 4276
Optimization/Design Sensitivity - DSAD, FRRD1 - Insufficient
If an optimization run encounters an "INSUFFICIENT TIME" type message during

the finite element part of the solution (the example encountered was
insufficient time to complete the frequency response solution, FRRD1) it is
possible the run will continue into the optimization process and fail in the
optimizer (the example fails in DSAD with SFM 4276, ERROR CODE 3001).
If an unexplained error occurs during optimization, check the output file for
other messages.
Avoidance: Specify sufficient time on the TIME statement in the executive
control section.
5982
69
FATAL ERROR, UIM 5458
Eigenvalue Analysis - AGIV, AHOU - SDCOMP
If an eigenvalue analysis specifies either the AGIV or the AHOU method, then
standard GIV and standard HOU are attempted first. If the mass matrix is
singular, an unnumbered fatal message "SDCOMP FATAL" is issued even though the
problem continues and the program switches to the modified Givens or
Householder method.
Avoidance: If the problem runs, ignore the FATAL message.
5983
69
, DOM10 - SFM 3001
An optimization run with P1=1 and P2=15 on the DOPTPRM entry fails and issues
"SYSTEM FATAL MESSAGE 3001" from the DOM10 module even though the run works
fine without these parameters. These are output control parameters and should
not effect the solution.
Avoidance: If P1 and P2 have been used on the DOPTPRM and the run fails, try
the run again without specifying P1 and P2.
5984
68.2
- Missing Output
Nonlinear Analysis - PARAM,NMLOOP , SE's
When using the nonlinear normal modes option in Sol 106, no modal analysis is
performed when there are superelements and PARAM,NMLOOP is specified in the
Case Control.
Avoidance: Place the PARAM,NMLOOP statement in the bulk data.
or
Use SUPER=ALL in the case control.
or
DMAP alter:
compile nlstatic souin=mscsou nolist noref $
alter 480 $
seid= 0 $
pvt pvts,cases/pvtxx/ $
endalter $
5987
taloader Abort
68.2
Postprocessing - PARAM,POST,-2 - IDEAS Da
In MSC/NASTRAN Version 68, the structured solution sequences with

PARAM.CHECKOUT,YES and PARAM,POST,-2 do not write an END-OF-DATA on the FORTRAN
file.
Avoidance:
COMPILE PHASE0 SOUIN=MSCSOU NOREF NOLIST
ALTER 527 $ Before CALL PRTSUM
OUTPUT2 //-9/OUNIT1//OMAXR $ write END-OF-DATA
CEND
5993
ies
69
Documentation - PBEAM - Continuation Entr
The documentation for the PBEAM entry in the MSC/NASTRAN Version 68 Quick
Reference Guide states that the fields "SO" and "X/XB" on the second
continuation entry are required. A footnote should be included (as was in the
Version 66 User's Manual) that states that these fields are only required when
the second continuation entry is desired to request intermediate stress output.
5995
Elements - QUAD4, TEMP(LOAD) - Wrong answers
Warped QUAD4 elements with thermal loads give wrong answers. This error is
similar to the thermal expansion error in elements with rigid offsets, there is
no expansion for the offset.
If offsets and orthotropic materials are present, the errors are magnified.
5998
2004
er's Guide - Wrong output
Documentation - Linear Static Analysis Us
Incorrect output result files are included in Figures 11-2 and 11-3 of the
MSC/NASTRAN Linear Static Analysis User's Guide. Due to a missing carriage
control character, a pload1 entry for element # 2 is missing for the
inertia2.dat file that is delivered with the delivery tape. Furthermore, due
to error 5522, PLOAD1 yields incorrect results for the BAR, BEAM, or BEND
elements when used in conjunction with inertia relief. Thus, this example
(using PLOAD1) should not be emulated until error 5522 is corrected.
Avoidance: Replace the PLOAD1 with equivalent grid point loads and regenerate
the output file.
6000
- Poor Answers
2001
Transient Analysis - RESTART, PARAM,NOAP
If TIC entries are used to set initial velocity values, the computed initial
velocity will be slightly different from the specified initial velocity. On a
case where v0 was set to 1.0, the output velocity was computed as 0.9969. This
model has a dt of 0.1
Avoidance:
An avoidance is to run the model once to determine the computed
initial velocity, and increase the input initial velocity enough so that the
computed intital velocity is the value desired on a second run.
6004
68.2
SSSALTER Library - ZFREQ - Wrong Answers
The ZFREQ alter delivered in the Version 68 SSSALTER library allows frequency
dependent springs and dampers to be defined. However, the nominal spring
stiffness is not updated in the data recovery phase. Thus, element force
output for these elements is incorrect. This is a known limitation of the
alter that should have been documented in the ZFREQ.RDM file. The information
contained in this error report is to be included in the Version 68.2 ZFREQ.RDM
file and the error is considered corrected.
Avoidance: An avoidance is to place a stiff spring in series with the mount,
the forces in the stiff spring represent the correct element force for the
mount spring. The error introduced by this technique is proportional to the
ratio of the stiff spring rate to the mount spring rate. For e
6007
69
TEL - K-set is not Output
Documentation - PARAM, USETPRT PARAM, USE
The MSC/NASTRAN Quick Reference Guide incorrectly states that the parameters
usetprt and usetsel can be used to print k-set degrees of freedom. That is,
the k-set decimal equivalent is listed as an option in table 1 of the usetprt

parameter description.
6010
68.2
EG - Wrong Answers
An overhang slave node is not considered as "overhang" if the overhang value is

less than 5% of the master segment length. For models with large master
segments, this may lead to wrong answers. Typical symptoms include the
printout of a wrong slip code (e.g., SLIDE instead of OVERHANG) and incorrect
surface coordinates.
Avoidance: Use smaller master segments when modeling overhang situations.
6011
70
ault, Signal Number 11 in Log File
Security - NAO - UFM 3060, Segmentation F
Large jobs that use Network Authorization (NAO) may fail in various moudules on
the DEC/ALPHA OSF with the message, "Receiving signal number 11: Segmentation
fault", in the MSC/NASTRAN log file. Similarly, if using node lock
authorization, and running a looping solution sequence like nonlinear and a
large problem, then User Fatal Message 1019 "Fortran Unit Open Error" pointing
to the authorization file may be issued. This message is followed by USER FATAL
MESSAGE 3060. The problem occurs because a socket (file) is left open each time
MSC/NASTRAN checks the authorization code and when the system reaches the open
sockets limit, the job fails as indicated above.
Avoidance: Edit the system configuration table (sysconfigtab) and increase the
value of the OPEN_MAX parameter. (This is a syste
6012
69
le Precision Accuracy
Dynamic Response Analysis - EPOINT - Sing
If there are EPOINT entries in the bulk data file, the eigenvalue matrix PHIA
is expanded to the d-set matrix PHIDH in the GKAM module. On short-word
machines PHIA is double precision. At present PHIDH is single precision. As
this matrix is used to reduce load matrices and expand modal solutions to
physical DOFs this may reduce the precision of the solution.
Avoidance: An avoidance is to discard the PHIDH matrix output by the GKAM
module and build an alternate matrix with DMAP. The equations defining how
PHIDH is formed from PHIA are given in the MSC/NASTRAN REFERENCE MANUAL.
6013
69
DMAP - DMIG - Wrong Answers
If a DMIG entry references a degree of freedom which does not exist, the
corresponding coefficients are assigned to another degree of freedom, without
any diagnostic messages.
In one example, an open set was used to define a series of scalar points. A
DMIG term referenced a point that was not defined on an SPOINT entry which
occurred between two points which were listed on SPOINT entries. The
coefficient was placed on the last DOF.
6015
68.2
- UFM 2268 (FA1)
Documentation - Aeroelastic Users' Guide
Example HA145I in the Version 68 Aeroelastic User's Guide contains an alter

that is in error. The alter inserts a MATPRN after line 50. It should be
after line 45. If submitted as documented, the run fails and issues the
message "USER FATAL MESSAGE 2268 (FA1) FMETHOD SET
0 NOT FOUND".
The data deck delivered in the tpl has been made current. The documentation
will be updated to reflect the latest version when it is updated.
6016
68.2
t Ratios at p=2 (UFM 9050)
P-Elements - HEXA, PENTA - Excessive Pivo
If a model consists of HEXAs or PENTAs at a p-level=2 or higher connected

end-to-end, the following message may occur:
DMAP FATAL MESSAGE 9050 (SEKRRS) - RUN TERMINATED DUE TO EXCESSIVE PIVOT
RATIOS
IN MATRIX KLL. USER PARAMETER BAILOUT MAY BE USED TO CONTINUE THE RUN.
This fatal message is caused by the reduced integration used at a p-level=2 and
higher. Reduced integration is the current default.
Avoidance: SYSTEM(212)=1 may be set to work around the problem.
6017
68.2
EG - Extraneous Output
The following parameters are printed in the "LINE CONTACT REGION" output when
using the slide line contact capability.
CONT BEHA
TYPE
FO
CO
These values should be ignored as they are not implemented in the program.
Avoidance: These values have no effect on the rest of the output and they can
be safely ignored.
6024
Wrong Answers
68.2
Optimization/Design Sensitivity - DLINK -
If the user inputs a nonzero value for C0 on the DLINK entry, it is incorrectly
processed by the optimization algorithm. Values used by the optimizer for the
dependent design variables will be incorrect. This will directly affect
constraint calculations from the upper and lower bounds input on the associated
DESVAR entry. These constraints may not be critical and and the optimization
results may be valid. The printed summary values for the dependent design
variables will be incorrect.
6030
68.2
E, PARTN, DSAP - UFM 2166, UFM 5901
Optimization/Design Sensitivity - MPCFORC
In Version 68, if MPC forces are requested in an optimization run under static
analysis, the program fails at line 121 of subDMAP SEDISP with UFM 2166 stating
that the number of columns in the partition vector is incorrect. Under
frequency response analysis, UFM 5901 will be issued from the DSAP module.
Avoidance: Either remove the MPCFORCE output request or apply the following
DMAP alter to avoid the error:
$for statics approach:
compile sedisp, souin=mscsou, nolist, noref
alter 109
noqmg=ltoi(delta) $
$ For Frequency approach:

alter 238
if (not delta ) then $
alter 239
endif $
6031
ot Found
68.2
Documentation - gentim2.dat - Data File N
The MSC/NASTRAN V68 Installation and Operation Instructions implies that the
gentim2.dat file used to update timing constants is in the same directory with
the SSS.MASTERA and USS.MASTERA (ie /msc68/nast68/aix/del) but it is not. The
file is located in the /msc68/nast68/del directory. The install guide should
be clarified to tell users where the data file is located.
6033
68.2
Answers for TETRA(10) Stresses
Elements - TETRA(10), TEMP(LOAD) - Wrong
If the temperature at the grid points of a TETRA(10) element vary (i.e. they
are not constant), then the stresses for the element are incorrect.
Avoidance: The error is proportional to the variance of temperature within the
element; however, refining the mesh so that the temperature within each element
is near a constant is not considered a practical avoidance. Stresses requested
at the gauss points are correct.
6036
68.2
P-Elements - Punch Output not Supported
When stresses and strains are output in the punch file, they are output in the
print file (F06) format, with titles and labels, rather than a format suitable
for the punch file.
6038
Encountered
69
Elements - CTRIA3, TA1 - No Message, Trap
If a CTRIA3 element references a nonexistent material coordinate system (field

7), the job should issue USER FATAL MESSAGE 2025 UNDEFINED COORDINATE SYSTEM.
The IBM RS/6000 versions of MSC/NASTRAN do not issue this message. The job
stops without a message being issued. The f04, Execution Summary, indicates
that the last module executed is either TA1 or PHASE1DR and the log file
contains a "Trap Encountered" message.
6042
GL
nswers for Stresses
Elements - PENTA(6), TEMP(LOAD) - Wrong A
If the temperature at the grid points of a PENTA(6) element vary (i.e. they are
not the same at all points), then the stress output is wrong. Both corner
point (default) and Gauss location (selected on PSOLID) options give wrong
answers. The stress error is proportional to the amount of temperature change
within the element.
Avoidance: This is a limitation of the element. The only avoidance is to
refine the mesh so that the variation of temperature within the element is
minimal.
6044
68.2
ct Sensitivities for Superelements
Optimization/Design Sensitivity - Incorre
Incorrect design sensitivities are computed for superelement models in which a

superelement has
design variables but no design responses. This error occurs only in statics.
Avoidance: The avoidance is to specify WEIGHT=ALL (for all superelements) as a
design response.
6046
68.2
ESPCH - Incorrect Action
Optimization/Design Sensitivity - PARAM,D
Setting PARAM,DESPCH to a negative value will not prevent DESVAR and GRID
Entries from being written to the PUNCH file.
Avoidance: The following DMAP alter may be used to avoid the problem:
compile exitopt nolist noref souin=mscsou
alter 24 $ just before executing module DOM11
type parm,,i,n,desitert
if (despch < 0) then
desitert = desiter
desiter = 0
endif
alter 25 $ right after execution of module DOM11
if (despch < 0) then
desiter = desitert
endif
$$$ end of alter
6047
rs
68.2
SSSALTER Library - RESFLEXR - Wrong Answe
The alter to add residual vectors into a dynamic solution delivered in the
sssalter directory with Version 68 does not handle SUPORT entries properly for
free-free structures. If a SUPORT entry is present, residual vectors are not
generated for the residual structure.
Avoidance: Call MSC for an updated version of the alter.
6050
ate systems
68.2
P-Elements - GMLOAD in convective coordin
If a GMLOAD is applied in a convective coordinate system defined on a GMCURV or

GMSURF where the CIDIN is other than basic coordinate system, then the
following message is output from SSG1:
USER FATAL MESSAGE 2025, UNDEFINED COORDINATE SYSTEM
FATAL ERROR
Avoidance: Possible avoidances include defining the GMCURV or GMSURF in the

basic coordinate system, and applying the load in a non-convective system, or
using PLOAD4.
6051
t Clear
69
Documentation - MAT1 - Programs Action no
Remark 3 under the documentation for the MAT1 entry in the Quick Reference
Guide states that the relationship between E, G and NU "must be satisfied". It
should be clarified that satisfying the relationship is merely a
recommendation, rather than a requirement. The values furnished are used as

indicated in Table 1. and if the relationship is not satisfied the program
proceeds but issues USER WARNING MESSAGE 2251A and 2251B. Furthermore, the
relationship indicates ">" when it should indicate "<".
6052
69
Acoustic Analysis - ACMG - Job Aborted, N
o Message, Receiving Signal Number 10
An acoustic job that specifies DIFF on the ACMODL entry aborted in the ACMG
module with no message issued in the f06 file. A message may appear in the log
file indicating the job has aborted but the message will be different depending
on the computer. One such message is "Receiving signal number 10: Bus error"
Avoidance: The cause of the error is under investigation. Selecting the IDENT
method on the ACMODL entry will probably allow the problem to execute to
complete but unless the fluid and structural mesh are compatible will not yield
the correct results.
6058
system
68.2
P-Elements - Convective output coordinate
If a convective coordinate system is specified for the output coordinate system

of a GMSURF, GMCURV, FEFACE, FEEDGE, or GRID, the following message is output
from GP1:
*** USER FATAL MESSAGE 2104, UNDEFINED COORDINATE SYSTEM
13

6059
Nonlinear Static Analysis - Restarts - Missing Displacements
In the nonlinear static solution sequences, displacement output is missing from

the restart run, when the following conditions are met:
1) A new subcase is added which requests intermediate output (INTOUT=YES on
NLPARM).
2) The restart run regresses to a subcase prior to the last executed subcase
(using PARAM,LOOPID and
PARAM,SUBID). In other words, if the cold
start finished with subcase 4, the new restart subcase 5 would
start with
the last LOOPID of subcase 3 or prior and a SUBID of 5 (effectively skipping
subcase 4).
When these conditions are met, the .F06 and the punch file contains ONLY the
first intermediate displacements for the new subcase, and no other displacement
output for that subcase. Other forms of output are unaffected.
Avoidance: Avoid one of
6065
70.7
correct Term Output for MAT2
Composites - PCOMP, MID4, TEMP(LOAD) - In
If unsymetric thermal properties and thermal loads are present on a composite

plate that is using the PSHELL/MAT2 instead of the PCOMP/MATi method of
composite property description, then the PSHELL's MID4 MAT2 must have a ID
greater than 400,000,000 and the thermal properties in that MAT2 must be
written in a special nonstandard format (see Remark 13 on the MAT2 description
of the MSC/NASTRAN Quick Reference Guide). This is because the MSC/NASTRAN
composite formulation is different than the noncomposite formulation for
unsymmetric thermal loading. The MID4 MAT2 ID is the flag that tells
MSC/NASTRAN whether the PSHELL/MAT2s are composite or not composite.
PSHELL/MAT2s that are internally generated from PCOMPs and which are written to
the .f06 file or to the .pch file have the correct m
6067
68.2
ted for Error Tables
P-Elements - Punch File Output not Suppor
When the error table is output in the punch file, it is output in the print
file (F06) format, with titles and labels, rather than a format suitable for
the punch file.
6068
68.2
P-Elements - GMBC - UIM 6353
If a zero displacement value is entered on the GMBC entry, the following

message is issued for each grid point associated with the GMEDGE or GMFACE
entry:
USER INFORMATION MESSAGE 6353 (EGENDD)
ENFORCED DISPLACEMENT VECTOR IS NULL FOR COMPONENT=** OF EDGE ID= *** ON GMBC
LOAD ID= 0 AND SPC ID= **
Avoidance: Although there is no way to avoid the information message from
being output, there is no other adverse affect on the run and the message may
be ignored.
6070
68.2
PA, HFREQ - UFM 5423
Aeroelastic Analysis - PARAM,LFREQ, OPPHI
A flutter or dynamic aeroelastic run that uses PARAM LFREQ or HFREQ to

eliminate modes and PARAM OPPHIPA to print the normal mode shapes including
aerodynamic grid points, fails with the message "USER FATAL MESSAGE 5423
ATTEMPT TO MERGE INCOMPATIBLE MATRICES".
Avoidance: There is no avoidance other than do not use PARAM LFREQ or HFREQ in
combination with OPPHIPA.
6072
69
- UFM 224 (PRERMM),
If the PI(1) function on the DEQATN entry is used with an integer, it results
in a mixed mode arithmetic operation error and the following message is issued
"USER FATAL MESSAGE 224 (PRERMM) MIXED MODE USAGE BY THE ARITHMETIC OPERATOR *
IS INVALID DURING DEQATN PROCESSING".
Avoidance: Use a real number instead of an integer. For example, PI(1.0) is
acceptable and produces the desired result. The user could also define pi on a
DTABLE entry as a constant and not rely on the DEQATN function.
6079
69
,0 (default) - Missing output
Dynamics - Data recovery with PARAM,DDRMM
By default (PARAM,DDRMM,0) in dynamic data recovery for modal frequency or

modal transient analysis (SOLs 11, 12, 111, 112, 146, and 200) any FORCE,
STRESS, SPCF (if PARAM,DYNSPCF,OLD is specified), or STRAIN request in a
subcase subsequent to the first subcase is not honored. For example, if the
subcase structure shown below is specified then the forces for element 20, 40
and 60 are not output.
set 1=100,200
set 2=20,40,60
subcase 10
FORCE = 1
Subcase 20
FORCE = 2
Avoidance: Including PARAM,DDRMM,-1 avoids the problem but this forces the
output to be in SORT1 format.
Another avoidance is to add a new subcase above the existing subcase structure
for the FORCE(PLOT)=ALL and STRESS(PLOT)=ALL as shown below. With this
avoidance the output is in SORT2 format.
set
6080
FM 5401
70.5
Eigenvalue Analysis - REIGL - SFM 5407, S
Large Lanczos buckling runs may fail in the REIGL module on the CRAY C-90
release of MSC/NASTRAN with the following messages:
COMPUTED IN AN (SUB-)INTERVAL
SYSTEM FATAL MESSAGE 5401 (REIGL).
USER
FATAL
MESSAGE 4405,
NO EIGENVECTORS COMPUTED FOR COMPONENT MODE SYNTHESIS OR SYSTEM SOLUTION.
Avoidance 1: An avoidance is to set SHFSCL on the EIGRL entry near the
absolute value of the lowest expected root.
Avoidance 2 (preferred over Avoidance 1): include sss alter br.v69 for Nastran
version 69.0.2 or br.v691 for Nastran version 69.1. Leave the SHFSCL entry on
the EIGRL card blank.
6087
68.2
Heat Transfer Analysis - heatconv, CHBDY
large field format - Wrong Conversion
The heat transfer converter program, heatconv, cannot process CHBDY large field
format with ambient points correctly. Specifically, the GA1, GA2, GA3, GA4
points on the CHBDY continuation entry are not copied to the new Version 68
bulk data CONV entry.
Avoidance: Use small field CHBDY format.
6093
68.2
, RBEi, RBAR - UFM 2101A, UFM 3001
Optimization/Design Sensitivity - BNDGRID
When a shape optimization job is run which uses BNDGRID entries to define shape
basis vectors, if the same
component of a grid referenced on a BNDGRID entry is also referenced by a rigid
element, then the message "USER FATAL MESSAGE 2101A" is correctly issued
stating that a grid component can not be defined in both S-set and M-set. This
is a user input error.
For versions prior to 68.2, if a shape optimization job uses Analytic Boundary
Shape and also includes MPC or rigid element entries in the primary model,
error message "USER FATAL MESSAGE 3001 MODULE = UPARTN THE INPUT DATA BLOCK
NAMED USET0 AT POSITION 1 DOES NOT EXIST." may be output.
Avoidance: Replace the offending RBE's with extremely stiff elements.
6095
2001
Material Nonlinear Analysis - CQUAD4, CTR
IA3, PSHELL, MID3 - No Warning Message
Material nonlinear analysis does not support the transverse shear stiffness in
a CQUAD4 or CTRIA3. This is documented in the MSC/NASTRAN nonlinear seminar
notes. However, if the MID3 references a MATS1 entry, no warning message is
issued stating that material nonlinearities are not supported for this
stiffness.
Avoidance: There is no avoidance other than realizing the fact that the
transverse shear stiffness remains linear for CQUAD4 and CTRIA3.
6100
rs
Aeroelastic Analysis - PK Flutter Analysis - Extra Eigenvecto
If a user requests flutter eigenvectors in a pk flutter analysis and there are

real roots, an eigenvector is printed for each real root. This is confusing to
our users since only half of the real roots are provided in the flutter
summary.
Avoidance: Ignore the first half of the flutter eigenvectors that have real
eigenvalues.
6101
.
Aeroelastic Analysis - ADR, AERO - Incorrect Frequency Labels
If the AEROF request is used in a flutter analysis, the frequency used to

annotate the forces is incorrect. The frequency is computed based on the
reduced frequency of the flutter analysis. In dimensionalizing this reduced
frequency, the velocity from the AERO bulk data entry (VELOCITY) is used rather
than the velocity from the flutter analysis (VFLUT).
Avoidance: The correct frequency can be computed based on:
f
correct
f
* (VFLUT / VELOCITY)
printed
6111
68.2
,OLD - Wrong Answers
Dynamic Response Analysis - PARAM,DYNSPCF
If PARAM,DYNSPCF,OLD is used in a modal solution and the matrix method of data

recovery is used (the default), incorrect SPC Force output occurs.
Avoidance: Either specify PARAM,DDRMM,-1 or include the following DMAP alter:
compile sedrcvr, souin=mscsou, nolist, noref
alter 163
TYPE PARM,,CHAR8,Y,DYNSPCF='NEW' $
if (dynspcf='old') then $
DDRMM
CASEDR,UH1,OL1,OUGV2,oqg2,OES2,OEF2,XYCDBDR/
OUGV2Y,oqg2y,OES2Y,OEF2Y, $
equivx oqg2y/oqg2/always $
else $
alter 164
endif $
6112
2001
eference Manual
Documentation - MATT8 - MSC/NASTRAN V68 R
The documentation in Chapter 5 of the Version 68 MSC/NASTRAN Reference Manual

referencing the MATT8 entry is incorrect. The MATT8 entry does not exist and
it is not possible to define temperature dependent orthotropic material
properties.
6116
68.2
P-Elements - RBE, MPC - UFM 5289
The external id field in the message "USER FATAL MESSAGE 5289, COMPONENT WITH
EXTERNAL ID = ***, DOF = **, APPEARS MORE THAN ONCE ON THE SAME MPC OR RIGID
ELEMENT" is limited to eight characters. Thus, if the message attempts to
identify an internally generated degree of freedom from a p-element "********"
are output.
6118
201
68.2
Heat transfer - CHBDYE, TA1 - SFM 4276 EC
The message "SYSTEM FATAL ERROR 4276.WRITE ERROR CODE 201" occurs when a CHBDYE
element references a non-existing conduction element ID.
Avoidance: Make sure all the CHBDYE have a corresponding conduction element ID
6123
68.2
, P2=8 - Missing Response Output
The design optimization print produced when P2 is set to 8 on the DOPTPRM Bulk
Data entry does not
include transient responses.
Avoidance: Insert the following DMAP alter in V68.2:
compile desopt noref nolist
alter 'dom10',''
dbview xxxx=oli where (solapp='mtran') $
DOM10,
DESTAB,XINIT,XO,CNTABRG, CVALRG, CVALO,
DVPTAB,PROPI,PROPO,R1TABRG,R1VALRG,R1VALO,
RSP2RG,R2VALRG,R2VALO,OPTPRMG,OBJTbg,DRSTBLg,
xxxx,fol1,frqrprg//
DESCYCLE/DESMAX/OBJIN/OBJOUT/ $
6126
69.1
Superelements - PLOADX1 - Wrong Answers
The PLOADX1 bulk data entry is not supported when using superelements. No load
is generated for a PLOADX1 entry that references elements that belong to an
upstream superelement,
Avoidance: Place any elements loaded by PLOADX1 entries in the residual

structure.
6127
69
U, MHOU - Wrong Answers
Eigenvalue Analysis - EIGR, GIV, MGIV, HO
If any transformation method (i.e. GIV, MGIV, HOU or MHOU) is used to extract
eigenvalues from a two degree of freedom problem the eigenvectors may be
reversed.
Avoidance: Select the lanczos method of eigenvalue extraction.
6129
69
ed Element Not Detected
Elements - CTETRA - Poor Answers, Distort
Severely distorted TETRA elements may not always be identified, this may lead
to poor answers.
Avoidance: Other than avoiding severely distorted elements, there is no
avoidance.
6138
68
OUTPUT2 - RCOUT2 - BUS ERROR (CORE DUMP)
In Version 67.5, if the RCOUT2 program is used to read a formatted output2 file
on the HP machine, the job may fail with following error messages:
BUS ERROR (CORE DUMP)
This error only occurs on the HP Version 67.5 system when reading an output2
that is written in a neutral format.
Avoidance: Use the Version 68 RCOUT2 program to read the Version 67.5 output2
file.
6142
68.2
P-Elements - EMG - UFM 4659
For some complicated geometric surfaces, such as a sphere which has

singularities at the poles, element edges which are mapped directly to the
surface may be distorted enough to cause the the fatal message:
USER FATAL MESSAGE 4659 (EMGPMD)
***
DURING INTEGRATION FOR ELEMENT WITH ID =
Avoidance: There is no current workaround.

6147
68.1
tric DECOMP (Non-sparse)
Matrix Methods - FBS-Method 2 and Unsymme
Errors have been found in the Vector Math Kernels for Hitachi VOS3. The errors
will only occur when sparse is deselected (i.e., when NASTRAN
SPARSE=1,USPARSE=0 is specified). There are two separate errors -- one in FBS
Method 2 and one in Unsymmetric Decomp. Both errors can be corrected using the
following ZAP:
//... JOB ...
//*
//* CORRECT ERRORS IN NON-SPARSE VECTOR KERNELS
//*
//ZAPKVCT EXEC PGM=AMASPZAP

//SYSLIB DD DISP=SHR,DSN=...NAST68.NASTRAN ..NASTRAN LIB..
//SYSIN
DD *
NAME NASTKVCT $PMDINF
VER 0000 C8C9,E3C1
REP 0018 0000,0002,0000,0016,0000,005F
NAME NASTKVCT VOS3VCT2
VER 20CA 47B0,F094
VER 2844 0840,4242,0842,4442
REP 20CA 47D0
REP 2844 0840,4442,0842,4642
NAME NASTKVCT VOS3VC1A
VER 3450
6148
68.2
9015 (FEA) USET TABLE NOT PRESENT
Optimization/Design Sensitivity - DMAP FM
Shape optimization jobs that contain an auxilary model to define the boundary
shapes but do not include a static subcase may fail with the message:
DMAP INFORMATION MESSAGE 9052 (FEA) - STATIC ANALYSIS COMPLETED. DESIGN
CYCLE NUMBER=
1
DMAP FATAL MESSAGE 9015 (FEA)
THE USET TABLE IS NOT PRESENT FOR:
ANALYSIS = FREQ
MPC
=
-1
SPC
=
-1
AUXMID =
1
compile sedisp souin=mscsou list noref
alter 206
diagon( 20 ) $
alter 207
diagoff( 20 ) $
endalter
compile descon souin=mscsou list noref
alter 108
diagon( 20 ) $
alter 109
diagoff( 20 ) $
endalter
compile d
6152
ng Answers
68.2
P-Elements - GMCORD, GMCURV, FEEDGE - Wro
When a GMCORD coordinate system is specified on a GMCURV, the 2 and

3-directions are incorrect. The 2-direction is opposite the normal to the
associated GMSURF, and the 3-direction is the cross product of the tangent to
the edge and the normal to the face. The 3-direction should be the normal, and
the 2-direction should be the cross product of the normal to the surface and
tangent to the curve.
6155
69
Miscellaneous - XCSA - Poor Performance
The documentation states that an alphabetic character must be used to start the
ID entry if one is used. If a non-alphabetic character is used, the program

will issue UFM 300. On some client machines, it appears that excessive time is
taken before this message is issued.
Avoidance: Do not start any words on the ID entry with a non-alphabetic
character.
6156
Check
68.2
Elements - CTRIAi - Poor Answers, No Skew
There is no skew check performed on triangular plate elements in MSC/NASTRAN.

Excessively skewed elements may result in poor answers.
Avoidance: Many pre-processors have skew checks for triangular plate elements.
A skew check is in MSC/NASTRAN Version 68.2. The test in Version 68.2 is
based upon the three vertex angles. A warning message is issued if any vertex
angle is less than "T3SKEW", where "T3SKEW" is a user controllable NASTRAN
keyword with a default value of ten degrees.
6157
Performance - DPD - Excessive Time in DPD Module
On large-size models, the main function of the DPD module is to generate the
usetd table from the uset table. It has been observed that the time to perform
this operation on large models can exceed the time to generate the uset table
and process all rigid elements in the GP4 module.
Avoidance: An avoidance on sol 103 models which do not have EPOINTs is to
write a DMAP to branch over the DPD module, and equiv uset to usetd, dynamics
to eed, and set noue to -1.
6159
umentation
69
Documentation - MPCFORCE - Misleading Doc
The MSC/NASTRAN Version 68 Quick Reference Guide description of the MPCFORCES

command, remark 1, states that the MPCFORCE requests are honored in the
Structured Solution Sequences only. This remark implies that MPCFORCE output is
available in all of the SSS. It is not available in the nonlinear solutions
SOLs 106, 129, 153, or 159. This fact is documented in Table 3 of the Case
Control section of the Quick Reference Guide.
6166
, UIM 4158
69.1
Eigenvalue Analysis - GIV - Wrong Answers
Using the GIVENS method to calculate modes of a structure which has a non
positive definite mass matrix, should result in the following error message:
"USER FATAL MESSAGE 4646---- THE MASS MATRIX IS NOT POSITIVE DEFINITE,USING THE
GIVENS METHOD. USE MGIV INSTEAD"
However, the run may proceed and incorrect answers may be produced. Since
MSC/NASTRAN automatically omits massless degrees of freedom, this error only
occurs with models involving nearly massless mechanism. The user is warned of
the poor answers by a very large value for the factor diagonal ratio in the
following message:
USER INFORMATION MESSAGE 4158 ---STATISTICS FOR CHOLESKY DECOMPOSITION OF DATA
BLOCK MXX FOLLOW
MAXIMUM RATION OF MATRIX DIAGONAL TO FACTOR DIAGONAL =
The user may also be warned of the poor r
6171
Plotting - CGAP - UWM 979
CGAP elements using multiple subcases are incorrectly plotted seperately by

subcase. The correct plotting procedure is, as for other elements, on plot
that contains all the subcases concatenated. This error is exacerbated because
the scaling is done on the first subcase which is then used for all the
subcases, even though the data from the following subcases was not used in the
scaling. This causes the data from the other subcases to be off the plot.
Another problem caused by the CGAP is that all the requested plotting is
attempted twice; once after the CGAP f06 printing and the other after the other
element f06 printing. In the first plot attempt, only data for the CGAP is
available, causing UWM 979 to be printed for the other element plot requests.
In the second plot attempt, onl
6181
- UFM 5423
68.2
Optimization/Design Sensitivity - VECPLOT
If acoustic analysis is requested in SOL 200 with ANALYSIS=MFREQ, DFREQ, or

MTRAN and also ANALYSIS=STATICS, then the run fails in the VECPLOT module
during static analysis data recovery.
compile sedrcvr,souin=mscsou,noref,nolist $
alter 28,28
IF ( NOT(PEXIST) AND NOT(NLHEAT) AND (NSILS*6)<>LUSETS ) THEN $
6184
70.5.2
ible Divergence
Nonlinear Static Analysis - NLPARM - Poss
If the stiffness update method, KMETHOD field, is specified incorrectly on the

NLPARM entry, a fatal message is not issued and the default AUTO method is
used. Note that the double quotes surrounding the legal choices in the
MSC/NASTRAN Version 68 Quick Reference Guide should not be included when
specifying the KMETHOD field. If the double quote is used, it will be
considered as part of the string specified.
Avoidance: Specify a correct method in the KMETHOD field.
6186
68.2
SFM 4276 GREAD EC
Optimization/Design Sensitivity - DSAH -
If a design optimization task contains multiple subcases that include design

constraints on dynamic responses (either frequency or transient) and there are
no active constraints for the first dynamic subcase, the above fatal error
occurs.
Avoidance: A possible avoidance is to force retention of a response using a
DSCREEN bulk data entry with a threshold set to a large negative number.
6192
Message
69.0.2
Eigenvalue Analysis - EIGRL, REIGL - Poor
If ND, the number of desired roots, is specified

greater than the total number of eigenvalues and
Summary "TERMINATION MESSAGE" may indicate "NOT
RANGE" even though all possible eigenvalues have
on the EIGRL entry to be

, the Eigenvalue Analysis
ALL EIGENVALUES FOUND IN
been found.
Avoidance: Either specify a frequency range or specify an appropriate value

for ND.
6196
68.2
SFM 3002 EOR RSP2RG
In a design optimization task, if the objective is a synthetic (DRESP2)

response and there are no constraints on synthetic responses, the above error
may occur.
Avoidance: An avoidance is to formulate and constrain a DRESP2 response. For
example the DRESP2 = 1.0 * DRESP1. In order to force retention of the
constraint, a DSCREEN entry with RTYPE = EQUA and TRS = -1000. should be used.
6201
68.2
T,-2 - Missing Output
Postprocessing - Heat Transfer, PARAM POS
In heat transfer analysis solutions 153 and 159, the temperature and flux
results are not properly written to the OUTPUT2 file under when using PARAM,
POST, -2.
compile sedrcvr souin=mscsou noref nolist
alter 66,66
alter 68,68
IF ( POST=-2 AND GETSYS(NH,56)<>0 ) THEN $
MATMOD ougv1,,,,,/tougv1,/13 $
alter 112,112
IF ( POST=-2 AND GETSYS(NH,56)<>0 ) THEN $
6221
or Messages
69
Miscellaneous - CORD2i, GP1 - Missing Err
On the DEC/OSF1 (and possibly other machines), when a large number (e.g.,
1.E+35) is used to define the vectors of a secondary coordinate system (e.g.,
CORD2S), the job may fail without issuing an error message in the F06 file. A
message such as "abnormal time termination" may be observed in the LOG file.
On other machines, SFM 2005, UFM 316, or SFE 4276 EC 7777 may be issued in the
F06 file.
Avoidance: Use smaller numbers to define the vectors.
6224
8
69
Transient Response - DMAP, TRD1 - SFM 300
The transient response solutions in MSC/NASTRAN do not support complex

arithmetic. If a complex matrix is introduced by DMAP, the program attempts to
process the problem, but may fail in the module TRD1 with a message similar to
the following: "INSUFFICIENT CORE FOR SPARSE FBS IN SPFBS USER ACTION: INCREASE
CORE BY xxx WORDS. *** SYSTEM FATAL MESSAGE 3008 MODULE = TRD1 INSUFFICIENT
MEMORY AVAILABLE FOR SUBROUTINE."
Avoidance: Do not use complex matrices in a transient solution.
6226
68.2
SFM 4276, Attempt to Read Past EOR
Optimization/Design Sensitivity - SDSC -
In a dynamic response sensitivity analysis, the above message can occur when
the are multiple superelements and one of the superelements has no active
responses.
Avoidance: A possible avoidance is to explicitly specify each superelement
subcase in the case control and not place a design condition for the
superelements that are known not to be active in the sensitivity analysis. A
less satisfactory fix is to delete the SDSC and DSTAP2 modules in the EXITOPT
subdmap. The sensitivity matrix would then be printed without the
IDENTIFICATION OF COLUMNS IN THE DESIGN SENSITIVITY MATRX table.
6228
69
- DSCM Matrix Row Deficient
Optimization/Design Sensitivity - DVPRELi
The number of rows in the DSCM matrix should be equal to the number
independent design variables plus the number of DVPREL2 entries. If
no DVPREL2 entries and the trailing independent design variables are
referenced by any DVPREL1 entries, the number of rows in DSCM matrix
deficient by the number of unreferenced trailing design variables.
of
there are
not
will be
Avoidance: An avoidance is to rearrange the ID's of independent design

variables so that the unreferenced ID's are not the highest numbers.
6229
68.2
Heat Transfer - CHBDY, Forced Convection
Heat Flow - Inconsistent Calculations
The forced convection heat flow is calculated by upwinding shape functions in
the solver and by the average fluid temperature in the data recovery. This
inconsistency results in an unbalanced energy between the forced convection
heat flow output and the mass flow convection (mdot*Cp*Delta T). This error
may lead to poor answers for the "FORCED-CONVECTION" and "HEAT FLOW INTO HBDY
ELEMENTS" results.
6233
ormance
69
Aerodynamic Flutter - SOL 145 - Poor Perf
The solution approach used in SOL 145 is different in Version 68 as compared to

Version 67.5. Invariant matrices are created in Version 68 for aerodynamic
optimization. These matrices are larger than the matrices used in the Version
67.5 approach. Therefore, the performance (e.g., in the FBS module) may be
slower in Version 68 as compared to Version 67.5. Due to these larger
matrices, the disk space requirement may also be larger.
6234
70
Size Increased to 32000 Characters
MSC/NASTRAN Version 70 has increased the allowable number of characters for the
DEQATN entry from 12,500 to 32,000.
6235
Loop
68.2
Static - PLOAD1, CBEAM, CBEND - Infinite
If a problem contains PLOAD1, CBEAM, and CBEND entries, then MSC/NASTRAN may
become trapped in an infinite loop. The error only occurs when no PLOADs are
applied to any CBEND elements.
Avoidance: Apply a zero dummy load on a CBEND element.
6240
68.2
UWM 4698, UWM 5221, UFM 5225
Static Analysis - QSETi, SSG3 - SFM 3007,
In static analysis, if QSETi entries are defined for SPOINTs and ASETi entries
are defined for physical degrees of freedom then the run will fail in SOL 61
and 101 with SFM 3007 in module SSG3 and subroutine SSG3A. In SOL 24, the run
will issue USER WARNING MESSAGEs 4698 and 5221 and then fail with USER FATAL
MESSAGE 5225.
Avoidance: Insert the following avoidance for SOL 101 or remove the QSETi
entries:
compile selrrs souin=mscsou noref nolist
alter 5,5
PARAML USET//'USET'//////'q'/S,N,NOqSET/
't'/S,N,NOtSET $
IF ( FIXEDB <> -2 ) THEN $ A-SET PARTITIONING ( Q + T )
EQUIVX
PA/PT/NOQSET $
IF ( NOQSET>=0 AND NOTSET>=0 ) UPARTN USET,PA/PT,,,/'A'/'T'/'Q'/1 $
ENDIF $
EQUIVX PT/PL/NORSET $
alter 8,8
UPARTN USET,PT/PL,PR,,/'T'/'L'/'R'
6241
Wrong Answers
69
Random Response Analysis - STRESS, BEAM -
If stresses are requested for BEAM elements in a random response analysis, and
the STRESS output is requested as real/imaginary values, then the PSD output
for the RMS stresses at point F of end A are incorrect.
Avoidance: Request the stresses in magnitude and phase by using the
STRESS(PHASE) Case Control command.
6242
69
Optimization/Design Sensitivity - DSAD Datablock Does not Exist, Poor Message
The message "INPUT DATA BLOCK NAMED OUGVS1 AT POSITION 12 DOES NOT EXIST. DSAD"
is produced when the user requests responses at a set of grid points that do
not exist. If some of the grid points exist and some of them don't, a more
meaningful message is produced. A similar nonexistent datablock error is
produced for other response types; e.g., the OES1 datablock is missing if none
of the requested elements exist.
Avoidance: Do not request responses for grids that do not exist.
6244
68.2
.5 - Extra Data Block LAMA
Post Processing - PARAM,POST,-1; PATVER,2
If PARAM,POST,-1 and PARAM,PATVER,2.5 are used in SOL 103, MSC/NASTRAN Version

68 incorrectly writes the LAMA (OLB) datablock to the output2 file for PATRAN.
PATNAS cannot recognize this datablock and issues an error message.
Avoidance: Use the following DMAP alter:
ALTER 92 $
IF (POST=-1 AND PATVER=2.5) THEN $
OUTPUT2 OUGV1//OTAPE2/OUNIT2//OMAXR $
ELSE
$
ENDIF
ALTER 93 $
$
6249
69
DMAP FATAL MESSAGE 9015
Miscellaneous - PARAM,NMLOOP - UWM 4500,
If "PARAM,NMLOOP" is included in the Bulk Data section for a Structured

Solution Sequence input file other than SOL 106 or 153, then the job may fail
with one or more of the following error messages:
USER WARNING MESSAGE 4500, STIFFNESS MATRIX PURGED. GRID POINT SINGULARITY NOT
TEST
DMAP FATAL MESSAGE 9015 (SEBUCKL) - THE USET TABLE IS NOT PRESENT
Note that this parameter is not used except in SOL 106 and 153.
Avoidance: Remove the offending parameter as this parameter is only used for
SOL 106 and 153.
6252
Available
69
Documentation - SPCFORCE - PLOT Option is
The SPCFORCE output request supports the plot option even though it is not
listed in the MSC/NASTRAN Quick Reference Guide.
6253
68.2
- Incorrect Eigenvectors
Complex Eigenvalue Analysis - CEAD, CLAN
The complex lanczos method of eigenvalue extraction may produce non-orthogonal

eivenvectors for models with multiple roots at the same eigenvalue. This error
is under investigation, currently it has been experienced on short-word
machines only. The CRAY produced correct results.
Avoidance: Use the Hessenberg method.
6257
69
Miscellaneous - File Not Found, UFM 423
Prior to Version 69, filenames were limited to 80 characters. Filenames that

were longer were trunctated by MSC/NASTRAN, this generally resulted in file not
found errors.
Version 69 increases the allowable filename length limit to 256 characters.
6258
2001
MATMOD Option 16
Documentation - DMAP Module Dictionary -
The first line of the example DMAP for MATMOD option 16 in the MSC/NASTRAN DMAP
Module Dictionary (page 196) is incorrect.
Avoidance: In the DMAP example, replace the following line
MATMOD EQEXIN/INTEXT/9/0/LUSET $
with
MATGEN EQEXIN/INTEXT/9/0/LUSET $
6260
Nonlinear Heat Transfer - NOLINi, ADAPT - Wrong Answers
The ADAPT strategy and the PW convergence criterion leads to an erroneous

solution if NOLIN cards are enforcing square wave type of power input loading
that is based on specified temperatures at certain grid locations of the model.
Particularly, the iteration strategy fails when the temperature of the curve is
nearly constant. This phenomenon occurs for the ablation problem for which
NOLIN entries are used to model the heat transfer through out the medium.
Avoidance: Set the ADJUST of the TSTEPNL entry to zero, so that the automatic
time step adjustment is disabled. Also set the convergence criterion to U, and
set the EPSU to 1.0-5 instead of the 1.0-3 default value. This avoidance
yields correct answers but the actual CPU time to reach convergence will be
much longer than using SOL 8
6261
300
70
Miscellaneous - ADAPT,OUTPUT,OUTRCV - UFM
If free field format is being used with the ADAPT, OUTPUT, or OUTRCV bulk data
entries, and the first comma does not occur in columns 1-8, the fatal message,
"USER FATAL MESSAGE 300, DATA ERROR IN FIELD UNDERLINED", occurs.
Avoidance: Eliminate spaces between the entry name and the first comma.
6264
Thermal Stress Analysis - TEMPBC - Wrong Answers
The TEMPBC bulk data entry is used to specify time-dependent temperatures

(TYPE=TRAN) at grid points for transient thermal analysis (SOL 159). Internally
in MSC/NASTRAN, this time dependent load is accomplished using SLOAD and the
CELAS2 bulk data entries. For thermal analysis, these generated CELAS2's
produce correct temperatures. However, if a TEMPBC entry with the TRAN option
is included in a thermal stress analysis (SOL 101, SOL 106), then the thermal
stress calculations are wrong because extra forces are introduced in the
problem.
Avoidance: Remove TEMPBC entries with TYPE=TRAN.
6267
68.2
Static Analysis - SUPORT - UFM 3055
In MSC/NASTRAN Version 68, if multiple SUPORT sets are used in SOL 101, it is
possible to get "USER FATAL MESSAGE 3055 ATTEMPT TO MULTIPLY INCOMPATIBLE
MATRICES". This error occurs when there are a different number of loading
conditions for the various SUPORT points.
Avoidance: If multiple SUPORT sets are used, insert the following DMAP alter
for SOL 101
compile sestatic, souin=mscsou, nolist, noref
alter 69
type parm,,i,n,storit=0 $
call dbstore crx,,,,//suport/0/'DBALL'/s,storit $
$
alter 14
type parm,,i,n,gotit=0
purgex /crx,,,, $
call dbfetch /crx,,,,/suport/0/0/0/s,gotit $
$
6269
68.2
es, DDAM Will not Compile
SSSALTERS - DDAMF.FOR - Missing Subroutin
The ddamf.for FORTRAN program delivered with the SSSALTER library for the ddam
related alters is missing two subroutines. This is a Version 67.5 plus error.
Avoidance: The updated ddamf.for will be delivered with Version 68.2. If you
need a copy of this updated program, you can contact your local technical
support representatives.
6270
70.5
5401, UFM 4405
Buckling Analysis - EIGRL - SFM 5299, SFM
In a buckling analysis, if the buckling load is reversible (e.g., a torsional

buckling load applied to a cylinder), then the job may fail with the following
error messages:
*** SYSTEM FATAL MESSAGE 5299.UNRECOVERABLE TERMINATION FROM LANCZOS ITERATION
*** SYSTEM FATAL MESSAGE 5401 (REIGL). LANCZOS METHOD IS UNABLE TO FIND ALL
*** USER
FATAL
MESSAGE 4405,
In this case, the Lanczos shift logic finds many negative legitimate roots. The
number of these negative roots will increase as the model size increases.
Avoidance 1: If you are interested in only a few modes, which is the case for
most buckling analysis, use the SINV method. If you wish to use the Lanczos met
6271
nswers
69
Aeroelastic Analysis - AESTATRS - Wrong A
In a static aeroelastic analysis, if two dynamic pressures differ by less than

5.0e-4, the analysis will be repeated with the results for the first dynamic
pressure duplicated rather than new results being generated for the second.
Avoidance: The following DMAP avoidance gives differing results whenever the
dynamic pressures differ by more than 5.0e-7:
compile aestatrs souin=mscsou nolist noref
alter 30,30
IQ=NINT(1000000.*Q) $
6272
69
No Check for Symmetry
Documentation - DMIG, M2GG, K2GG, B2GG -
User-provided matrices, such as M2GG, K2GG, and B2GG, are not checked by the
program for symmetry. If non-symmetric matrices are entered for any matrix
which should be symmetric, the program may fail in a later operation, or give
incorrect answers.
Avoidance: Use the symmetric option on the DMIG entry.
6274
68.2
r Multiple Large Cavities
Heat Transfer - RADSET - Wrong Answers fo
For multiple radiation enclosures, the contents of the radiation matrix for the
first cavity is overwritten if the element size of the second cavity is greater
than 200. This error also occurs for large sizes of
third, fourth and subsequent cavities.
Avoidance: Use a single cavity or keep the sizes of the second, third, and
subsequent cavities small.
6282
69
Buckling - Thermal Loads - Wrong Answers
If multiple buckling analyses are executed in a single solution 105 run, and
thermal loads are present, then wrong answers (eigenvalues, eigenvectors etc.)
are generated for the second and greater buckling subcases. The error occurs
because MSC/NASTRAN uses incorrect temperature information when generating the
differential stiffness matrix for the second and greater buckling subcases. The
solutions in the static subcases are correct.
Avoidance: Specify all loads in both the static and buckling subcases, and
include the following dmap alter:
compile sekdr souin=mscsou nolist noref $
alter 25, 25 $
if (seid = 0) then $
case cases,/case1/'tran'/colno $
else $
equivx cases/case1/-1 $
endif $
call setq case1//seid/peid/s,mtemp/s,k2gg/s,m2gg/
s,b2gg/s,mpc/s,spc
6285
Nonlinear Transient Analysis - MATi, TRD1 - SFM 4276 EC 105
In a nonlinear transient problem (SOL 129), the job fails in TRD1 and the
misleading message "SYSTEM FATAL ERROR 4276.PACK ERROR CODE 105" is output
whenever all the mass properties are omitted. Therefore, the message occurs
whenever the user forgets to specify the mass density on their MATi bulk data
entries and doesn't have any other concentrated masses (CONMi, CMASSi)
specified.
Avoidance: Specify the mass density on MATi bulk data entries or include a
concentrated mass.
6289
4276 EC 3002
69
Static Analysis - GPSDCON, ELSDCON - SFM
When attempting to calculate Grid Point Stress Dicontinuities (GPSDCON) or

Element Stress Dicontinuities (ELSDCON) on a model containing HEXA, PENTA and
TETRA solid elements it is possible to get the following fatal message "SYSTEM
FATAL ERROR 4276.FREAD ERROR CODE 3002" if the calculations are done over a
volume containing both types of elements.
Avoidance: Perform two runs and define the Volume set in the OUTPUT(POST)
section to be PENTA or HEXA only. Also, grouping the element types by element
id number allows the STDCON module to run.
6291
BCASE ID
69
Miscellaneous - SORT2, PUNCH - Missing SU
If punched output is requested in SORT2 format (e.g.,

STRESS(SORT2,PUNCH)=all), then the punch output does not contain the
appropriate subcase labels. This error is considered fixed in Version 69 since
the subcase id may be obtained by setting system(210)=1.
Avoidance: Either request SORT1 output or specify system(210)=1.

6292
69
de HEXA - Infinite CPU Loop
Nonlinear Transient Heat Transfer - 20 No
If a 20 node HEXA element is used in a transient thermal analysis (SOL 159),

the solution will not converge because the weighting of the capacitance matrix
is not correct. The job may go into an infinite CPU loop and will have to be
manually killed by the user.
Avoidance: Use 8 noded HEXA instead.
6294
Nonlinear Transient Analysis - TSTEPNL - SFM 4276 EC 1044
Solution 129 runs may fail with the message, "SYSTEM FATAL ERROR 4276.OPEN
ERROR CODE 1044" in the NLTRD2 module. The error is still under investigation
but the error only seems to appear when the NO field is not set to 1 or the
timestep field (NDT) is not 1.E**.
Avoidance: Specify the NO field to 1 or NDT to 1.E** (i.e., .001, .01, .1, 1.
...).
6296
69.0.2
DBCMSG ERROR 23 FROM GRIDBK/ELMBLK
Nonlinear Analysis - DBC, PARAM,POST,0 -
If in a Version 68.2 nonlinear transient analysis with PARAM,POST,0 the

following warning messages are encountered the graphic database, xdb, will be
corrupt.
OUTPUT LIST SYNCHRONIZATION PROBLEM FOR TOL
VALUE =
POSITION =
52
*** DBCMSG ERROR MESSAGE 23 FROM SUBROUTINE ELMBLK
OUTPUT LIST SYNCHRONIZATION PROBLEM FOR TOL
VALUE =
POSITION =
52
1.2879E+00,
1.2879E+00,
Avoidance: The following DMAP avoidance may avoid the error in Version 68.2.
The error has been corrected in Version 69.0.2; however most Unix workstations
were released as Version 69.0.0 and Version 69.0.2 must be
specially requested.
6307
3007
68.2
Heat transfer - SSG1, QVECT, RADBND - SFM
If the QVECT (direction heat flux) is used in conjunction with RADBND

(wave-length dependent radiation) for more than one element , then you SYSTEM
FATAL MESSAGE 3001 will be encountered in the SSG1 module. The exact message
is:
SYSTEM FATAL MESSAGE 3007 MODULE = SSG1
ILLEGAL INPUT TO SUBROUTINE HMAT
FATAL ERROR
Avoidance: Instead of using the QVECT entry to specify heat flux, use the QHBDY
entry to define the heat load.
6308
ccuracy
Grid Point Stress Discontinuities - GPSTRESS, GPSTR1 - Poor A
Even though the stress discontinuities are exactly zero in the normal-x,
normal-y and shear-xy directions the major and minor directions may indicate
small, non-zero stress discontinuities.
6310
68.2
nfinite CPU Loop, SWM ????, UWM 2354
Buckling - ESE, GPFDR - Missing Output, I
Element strain energy and grid point force does not work in Version 68, SOL 105
buckling runs. A request for ESE or GPFORCE may produce an infinite cpu loop
or SYSTEM FATAL MESSAGE 4276 with a traceback in the log file. The job may
eventually fail due to lack of disk space because the following warning message
is issued repeatedly:
USER WARNING MESSAGE 4506--- TOTAL STRAIN ENERGY IS ZERO. THE PERCENT OF TOTAL
STRAIN ENERGY IS ALSO SET TO ZERO.
USER INFORMATION MESSAGE 4507--- IN SUBCASE
****
THERE ARE *** QUAD4
ELEMENTS HAVING STRAIN ENERGY WHICH IS LESS THAN
.0010 PERCENT
OF THE TOTAL STRAIN ENERGY OF ALL ELEMENTS.
The following message is another symptom of this error.
SYSTEM WARNING MESSAGE ???? ***, GPFDR FINDS A SYMMETRY SEQUENCE LENGTH
WHILE ATTEMP
6312
68.2
19
Heat Transfer - CHBDYE - UWM 2154
A CHBDYE which is defined as side 4 of a PENTA element does not work. If

attempted the message "USER WARNING MESSAGE 2154, A ZERO AREA OR ILLEGAL
CONNECTION FOR CHBDYE ELEMENT NUMBER xxxxx" is generated.
Avoidance: If possible reorder the grids so the CHBDYE can be defined for a
side other than side 4.
6313
69
ansfer - SFM T10 (XMIT)
DBC/TRANS/ACCESS - CHBDYP, PHBDY, Heat Tr
TRANS will not work on heat transfer decks that contain CHBDYP elements with
PHBDY property cards. The following message is written out and no neutral
file is created:
*** SYSTEM FATAL MESSAGE T10 (XMIT)
A DATABLOCK WAS ENCOUNTERED THAT HAD MORE FIELDS THAN WERE DEFINED
IN THE DATA DEFINITION LANGUAGE.
DATABLOCK NAME =
PHBDY
DATABLOCK LENGTH =
7
DATA DEFINTION LENGTH =
4
Avoidance: The only avoidance is to run MSC/NASTRAN on the machine that you
intend to perform post processing on (or other compatible machine) so that
TRANS is not required. Note that machines that use the same UNIX IEEE
structure machines are compatible and TRANS is not required. The list of
compatible machines is documented in Chapter 6 of the Installatio
6316
70
OM - BIOMSG: ERROR 3001 IN FREAD
Frequency Response/Random Analysis - RAND
If the RANDPS entry references subcases that do not exist the following
uninformitive message is issued:
BIOMSG: ERROR 3001 HAS OCCURRED IN ROUTINE FREAD
Avoidance: Correct the RANDPS entry that is in error.
6317
- UFM 6293
68.2
"USER FATAL MESSAGE 6293 (DSAD16) GRID NO. *** REFERENCED ON A DRESP1 ENTRY
COULD NOT BE FOUND" may be issued in error in a frequency response optimization
or design sensitivity analysis if there are multiple frequencies and multiple
grid points appearing on DRESP1 entries, but not every response is designed for
every frequency.
Avoidance: The first check should be to make sure the message is in error. If
this appears to be the case, it is necessary to add a constraint for every
response at every frequency. Very generous limits could be set on these added
constraints so that they play no role in the design process.
6319
2001
DMAP - INPUTT2 - Poor Message
If a DMAP alter using INPUTT2 is used, and a parameter is used to specify the
INPUTT2, the parameter must be assigned a value before execution of the INPUTT2
module. If no value is assigned, the module will fail with a FORTRAN read
error. The message may be different for each computer type, and appears only in
the log file. The .f06 and .f04 files end abruptly and no error message is
printed.
Avoidance: Be sure the unit number is defined before INPUTT2 is used.
6322
ent restart
GL
Superelements - SEMA - SFM 4252, Ineffici
On a restart run, if the user changes PARAM,AUTOSPC for the residual structure,
then SYSTEM FATAL MESSAGE 4252 may be issued or all superelements will be
recomputed. This error was found on a sol 103 restart to sol 129. In a sol
129 run, the PARAM,AUTOSPC default is "NO" in the residual and it should not be
changed. Therefore, single point constraints for singularities that were
eliminated by PARAM,AUTOSPC,YES in the sol 103 run must be explicitly defined
in sol 129 for the residual.
Avoidances:
1) Specify PARAM, SPCGEN, 1 in the cold start run to punch SPC entries based on
the
the AUTOSPC operation. Include the puched SPC entries in the restart Bulk
Data section.
2) Use the following alter
compile ifpl souin=mscsou,nolist,noref
$alter 89,89
$ v67.5 removes autospc re
6326
68.2
UTOSPC; MERGE, PARTN - Various SFM
In SOL 200 with PARAM, AUTOSPC, YES, if the model is a fluid/structure model
then the run may fail with various matrix partition or merge errors indicating
incompatible matrices. The error occurs after the first design cycle if the
AUTOSPC operation produces a different set of constraints then in the previous
cycle. (Version 68 only)
compile dpd1 souin=mscsou noref nolist
alter 29
delete /vafs,,,, $
6328
69
Authorization - UFM 3060
If an MSC/NASTRAN Version 67.5 based authorization file is merged with a

Version 68 authorization file, it is possible that Version 67.5 runs will fail
with USER FATAL MESSAGE 3060 indicating that OPTION NOT IN APPROVED LIST even
though the file contains a valid Version 67.5 authorization code. This problem
only occurs when Version 68 authorization codes precede the Version 67.5
authorization code.
Avoidance: Version 68 authorization codes should be appended to the end of the
authorization file.
6329
Optimization/Design Sensitivity - PCOMP - Wrong Answers
If the ply orientation angle is selected as as a design quantity and the

initial ply orientation angle specified by the DESVAR/DVPREL1 combination is
0.0, incorrect sensitivities can result. The error occurs because the finite
difference perturbation used to produce the sensitivity is too small when the
initial ply angle is zero.
Avoidance: Provide an initial design with a non-zero ply orientation angle.
6332
68.2
M, SYSTEM(146) - SFM 5401, UFM 4405
Eigenvalue Analysis - EIGRL, REIGL, FBSME
If the NASTRAN keyword FBSMEM (a.k.a. SYSTEM(146)) is set to too large a value
such that there is insufficient memory to honor the request, then LANCZOS stops
in the REIGL module and issues the messages:
USER FATAL MESSAGE 4405
NO EIGENVECTORS COMPUTED FOR COMPONENT MODE SYNTHESIS OR SYSTEM SOLUTION
Avoidance: Large values of FBSMEM are not necessary in Lanczos eigenvalue
analysis. A value of 4 is the largest recommended value. Larger values are
only a significant benefit to frequency response and transient solution
sequences. Either inc
6338
ers
68.2
Heat Transfer - TRIAX6, QVOL - Wrong Answ
TRIAX6 elements with QVOL heat loading produce wrong answers on long word
machines such as CRAY Y-MP and CRAY C-90.
6339
68.2
- UFM 6545 (DOPR3)
Optimization/Design Sensitivity - DESGLB
The following fatal error message is issued for superelement optimization when
a global response is selected from case control using the DESGLB entry. This
error only occurs when a weight or volume response is selected in a non-statics
case.
USER FATAL MESSAGE 6545 (DOPR3)
A DESGLB =
10 COMMAND APPEARS AT THE SUBCASE LEVEL.
USER ACTION: EITHER REPLACE THE DESGLB COMMAND WITH A DESSUB COMMAND OR PLACE
THE DESGLB REQUEST ABOVE THE FIRST SUBCASE.
Avoidance: The only avoidance is to specify a dummy statics subcase and to
select the global (weight or volume) response with a DESSUB command from the
statics subcase.
6348
69
, PBEND - UFM 7052, Misleading Message
If an invalid property type is referenced on a DVPREL1 entry, the message "USER
FATAL MESSAGE 7052, DOMPTC. ILLEGAL PROPERTY ENTRY NAME *****" is printed. In
most cases this message would be caused by a typographical error on the DVPREL1
entry and would be easy to spot. However, the message is misleading for the
legal PBEND property entry. As is documented in remark 3 under the DVPREL1
entry, the PBEND entry is not supported on the DVPREL1 entry. The message
should read "USER FATAL MESSAGE 7052, DOMPTC. ILLEGAL PROPERTY NAME *****
REFERENCED ON DVPREL1 ENTRY". Note that UFM 7052 is not documented in the
Reference Manual and needs to be added.
6353
- UFM 5502
68.2
If a frequency sensitivity or optimization is performed at multiple frequencies

and there are multiple
element types and only a subset of the output frequencies are invoked on DRESP1
entries, then the following message is issued:
USER FATAL MESSAGE 5502 (DSAD17)
ELEM NO.
**** REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND.
USER ACTION : USE OF UNREFERENCED ELEMENTS IS NOT RECOMMENDED AND MAY
INDICATE A USER INPUT ERROR,
RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.
One message is output for each element in the model.
Avoidance: Only perform the analysis at frequencies for which design results
are required.
6355
NUMBER 11
2001
Miscellaneous - IFPL, MAT1, MAT8 - SIGNAL
If the same ID is used a MAT1 and MAT8 entry, the job should fail with the
following message:
USER FATAL MESSAGE 2017, MATERIAL PROPERTY IDENTIFICATION
DUPLICATED.
x WAS
On the Intel SCO/UNIX, the job terminates without any error message in the f06
file. A symptom of this error is the appearance of the following message in
the log file:
SIGNAL NUMBER 11
Avoidance: Use unique ID's for each MATi entry.
6360
Miscellaneous - NFS Mount - Job Hangs
Submitting a job from a machine that is nfs mounted may result in the job
hanging. The exact cause of this specific problem is under investigation but is
often the result of incompatibilities in the operating systems.
Avoidance: Prior to MSC/NASTRAN V69, set system cell SYSTEM(207)=1; after
that, set the keyword "sysfield=lock=no". This feature is designed to block
file locking for those situations where, despite the correct programming of the
file locking calls, the system hangs or aborts.
6361
68.2
ORD,BASIC - Missing output
Postprocessing - PARAM,POST,-1/PARAM,OUGC
If the neutral format option is requested when using "param,post,-1" and

"param,ougcord,basic", then the ougv1pat datablock will not be written to the
output2 file. This is due to the fact that the datablock ougv1pat is not
defined in the NDDL.
Avoidance: Add the following DMAP alter avoidance:
compile sedrcvr souin=mscsou nolist noref
alter 74,74 $
OUTPUT2 OUGV1PAT//OTAPE2/OUNIT2//OMAXR/'oug' $ V68
6364
68.2
Single and Multipoint Constraints - MPCFO
RCE - Wrong Answers for Superelements
In static analysis in the structured solutions the MPCFORCE output is wrong for
upstream superelements when rigid elements are on the boundary between the
residual and the superelement or completely interior to the superelement.
compile sedisp souin=mscsou noref nolist

alter 121,121 $ PARTN
PG,COL,ROW/,,,PMI/1 $
upartn uset,pg/pmx,,,/'G'/'M'/'S'/1 $
if ( seid=0 ) then $
PARTN
Pmx,COL,/,,,PMI/1 $
else $
equivx Pmx/pmi/-1 $
endif $
6365
Material Nonlinear Analysis - QUADX, TRIAX - Poor Answers
The radial degree of freedom should be constrained for all grid points on the
axis of symmetry for hyperelastic axisymmetric problems else poor answers may
result.
6366
2001
Elements - CROD - Wrong Answers
When a CROD or CONROD that has torsional properties only, nonzero axial
stresses are printed if the attached grids move.
Avoidance: Use a torsion only CBAR or ignore the nonzero stresses.
6367
68.2
ANALYSIS=DFREQ - SFE 4276, EC 3001
Optimization/Design Sensitivity - OFREQ,
If a OFREQ Case Control command is present in a direct frequency response

optimization/design sensitivity analysis the following message is issued:
ERROR CODE 3001 (DSAD)

$
compile fea souin=mscsou list noref
alter 297,298 $
CALL SUPER3,
CASECC,
,ULF,FOL1,PPFX,PSF1, , , ,DLT,
,
, ,,,,
PCDB,XYCDB,POSTCDB,,EMAP,MAPS,EQEXINS,PVTS,CASES,
SLT,ETT,GOAT,GOAQ,,,,UFOO,,GPLS,USET,SILS,
PJ,EDT,YS,GM,,KFS,KSS,QR,,,,MAR,MEA,
DYNAMICS,BGPDTS,CSTMS,MPTS,DIT,EST,GEOM2S,GEOM3S,ECTS,
EPTS,INDTA,,,GPECT,,,SILX,EQEXINX,
ECTX,BGPDTX,,GEOM4S,PG,,,,EPT,MPT,
GEOM1,GEOM2,GEOM3,GEOM4,,,,CASERS,,,,,,GPSNTS,PVT,,,,,,
KSF,KMG,MMG,MSF,BMG,BSF,K4M
6368
stems on Edges
p-Elements - FEEDGE - Undetermined Displacement Coordinate Sy
If two faces with different displacement coordinate systems intersect at an

edge that has no explicitly defined displacement coordinate system, then the
coordinate system used for the edge cannot be easily determined.
Avoidance: In this situation, specify the displacement coordinate system for
the edge explicitly.
6374
69
FORCE - SFM 6220
Grid Point Force - TEMP(LOAD), SUBCOM, GP
If a SUBCOM involves a temperature load, and gpforce is requested as an output,

then the job will fail with the following error messages:
SYSTEM FATAL MESSAGE 6220 (GPFDR2), ERROR SEARCHING INDEX IN SCRT9 FILE
Avoidance: Replace the SUBCOM with an appropriate SUBCASE.
6377
68.2
uperelements, SESET
Documentation - Quick Reference Guide - S
The Gi description for the SESET entry is incorrect. The GRID ID limit of less
than 1,000,000 is a pre Version 68 limit. The new limit is less than
100,000,000.
6378
2004.0.4
Element - GENEL - UFM 316
If the [S] matrix is left out (to be generated automatically by MSC/NASTRAN)

when using the GENEL element, then {ud} must contain six and only six degrees
of freedom. This fact is documented in the MSC/NASTRAN Quick Reference Guide
under the GENEL entry description. However, if less than six degrees of
freedom are defined when using the Z option, then the following unclear error
messages is issued:
ILLEGAL DATA ON BULK DATA CARD GENEL
COUNT =
y
SORTED CARD
On the other hand, if the K option is used, no error message is issued. The
job most likely fails downstream with other error messages.
Avoidance: If the [S] matrix is to be generated automatically by MSC/NASTRAN,
define six and only six degrees of freedom for the {ud} vector.
6380
Nonlinear Analysis - RESTART, LOOPID, SUBID - Missing Output
If PARAM,LOOPID and PARAM,SUBID are used to restart a nonlinear analysis and

SUBID references a SUBCASE that is not the next sequential subcase following
the subcase associated with LOOPID, then missing output occurs.
Avoidance: If the user wants to restart an analysis and continue at the
beginning of a new subcase, then the subcase(s) should be added sequentially
following the subcase associated with LOOPID.
6383
P-Elements - MODES - UFM 6500 (ADAPT)
The modes command does not appear to work with p-elements and yields an
incorrect fatal message. The following Case Control:
ADAPT
= 150
VUGRID(PLOT)=ALL
ADACT = ALL
$
METHOD=151
SPC=999
DISP=ALL
SUBCASE 1
MODES=1
SUBCASE 2
STRESS=ALL
resulted in the following fatal message:
USER FATAL MESSAGE 6500 (ADAPT)
MULTIPLE SUBCASES WITH DIFFERENT METHOD COMMANDS AND/OR SPC/MPC/SUPORT COMMANDS
HAVE BEEN SPECIFIED
WITH P-ELEMENTS IN NORMAL MODES ANALYSIS.
USER INFORMATION: ONLY ONE BOUNDARY CONDITION AND ONE METHOD COMMAND PER RUN IS
ALLOWED.
Note that the method command and constraint requests are above the subcase
level.
6386
69.0
UFM 2143
If the MPL listing for the module show that the parameters are of the BCD type,
then they must be of length 8 as shown by the following example.
type parm,,char8,n,major,setj,comp='comp' $
major='g' $
setj='a' $
vec uset/vgacomp1/major/setj/comp $
If other lengths are used, e.g., char4 instead of char8, then the job may fail
with the following error
message:
USER FATAL MESSAGE 2143, MODULE VEC UNABLE TO IDENTIFY SET OR
SUBSET DESCRIPTOR G A
This fact is not documented in the DMAP Module Dictionary.
Avoidance: Define the BCD parameter type as char8.
6387
68.2
- SFM 4276, EC 7777, Inefficient
Nonlinear Analysis - NLTRD2 PARAM,TSTATIC
An error in the bisection logic may cause nonlinear analysis to overshoot the
load factor and the subcase may be repeated. If this error is encountered in a
transient nonlinear analysis using PARAM,TSTATIC then (depending on machine)
the job may issue SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777 in the NLTRD2
module or may exit the NLTRD2 module without any message.
6388
p-Elements - GMSPC, GMBC, CORDiR, CORDiC - Wrong Answers
When constraints, either GMSPCs or GMBCs, are defined in a cylindrical or

spherical displacement coordinate system on an edge or face, the constraints
can only be approximately satisfied. It has been observed that in some cases
this leads to non-physical singularities.
Avoidance: If possible, the basic coordinate system should be used.
6391
69
r in Solution 129
DMAP - Matrix K4AA Has an Improper Traile
In a SOL 129 run, the K4AA matrix for the superelement is FORM=1 (square)
instead of FORM=6 (symmetric). This may cause DMAP fatal messages in user DMAPs
that expect the matrix to be symmetric. No adverse affect in the delivered
solution sequences is known.
Avoidance: In Version 68, the following alter changes the trailer to be FORM=6:
compile semrb, souin=mscsou, nolist, noref
alter 13
modtrl xaa////6 $
6396
69
g Documentation
Documentation - SPLINE1, SPLINE2 - Missin
The description of the SETG field of the SPLINE1 entry in the MSC/NASTRAN
Version 68 Quick Reference Guide refers to remark 4 which does not exist. Even
though the SETG field on the SPLINE2 entry serves the same function, the
description does not refer to any remark at all.
Avoidance: The remark's original intent was to inform the user that SETi
entries are bulk data entries and as such they are described in the same
section.
6397
68.2
M(205) - SFM 5407, 5401
Lagrange Multipliers - SYSTEM(198), SYSTE
In Version 68.1, if the Lagrange Multiplier Technique is used on the SGI, the
job may fail with the following (or possibly other) error messages:
COMPUTED IN AN (SUB-)INTERVAL
This error is most likely to occur when using one of the Lagrange Multiplier
alters from the sssalter library (e.g., lmt11.v68).
Avoidance: Set SYSTEM(198) and SYSTEM(205) to 1 at the top of the input file
with the following NASTRAN statements:
6402
69
Data Recovery - ESE - SFM 6212
If ESE=n references a SET n then the run fails with SFM 6212.
Avoidance: Use ESE=ALL.
6404
leted
2004
Restart - SCR=YES, DBVIEW - Datablocks De
If a restart run uses the DBVIEW statement in conjunction with SCR=YES, it is

possible that the DBVIEWed datablocks may be deleted from the database. This is
in spite of a RESTART, KEEP FMS statement.
Avoidance: On restart runs, do not use SCR=YES.
6405
) on RCOUT2
69
Postprocessing - RCOUT2 - SFM 1208 (LDSTR
Using RCOUT2 to convert a neutral binary output file that was ftp'd from an IBM
MVS/XA system results in SYSTEM FATAL MESSAGE 1208 (LDSTR). This error occurs
because a hex 71 is mistakenly written from MSC/NASTRAN, and it is not an
acceptable character in EBCDIC.
The error will be fixed in future versions. The client can fix MSC/NASTRAN at
their site using the following superzap:
NAME NASTRAN UNSTR
VER 031C BD71
REP 031C BD5F
IDRDATA FXUNSTR
6406
68.2
fferential Stiffness not Ignored
Nonlinear Analysis - PARAM,TESTNEG,2 - Di
In nonlinear static analysis PARAM,TESTNEG,2 option is suppose to allow the

user the option to ignore the affects of differential stiffness. This
parameter does not work.
Avoidance: A DMAP avoidance will be supplied shortly.
6413
rectly Set
68.2
Miscellaneous - script, SMEM - SMEM Incor
The runtime script incorrectly sets smem=100 as a default value.

Unfortunately, this overrides the system supplied default value. The script
should not enter a value for smem unless the user wants to change the default
value. The 68.0 and 68.1 scripts may be corrected as follows:
Change the line:
smem="100"
to:
smem=""
Change the line:
echo "SMEM=${smem}"
to:
test -n "$smem" && echo "SMEM=${smem}"
6416
68.2
5 Does Not Terminate Run
Static Analysis - SOL 101, SSG1 - UFM 202
For any structured solution sequence which computes static loads, if UFM 2025
(UNDEFINED COORDINATE SYSTEMS) is issued more than once by the SSG1 module then
the job will continue through DCMP and attempt a static solution instead of
terminating the run. This error is caused by load entries such as GRAV, FORCE,
MOMENT that reference a coordinate system that does not exist.
Avoidance: Insert following DMAP alter:
COMPILE SELG SOUIN=MSCSOU NOREF NOLIST
ALTER 12,12 $ v68
IF ( NOGO<0 ) THEN $
6419
68.2
N BIO Fatal Message
Miscellaneous - DBUNLOAD, SMEM=0 - FORTRA
If a DBUNLOAD is requested and a FORTRAN unit number is not explicitly

specified, then the default unit number is 51. This number causes a conflict
when SMEM=0 on systems with FORTRAN BIO. For Version 67 this error only occurs
on Hitachi OSF machines when ESS is used.
Avoidance: Specify a FORTRAN unit number on the DBUNLOAD entry that is less
than 50.
This was fixed in v68.2 for both Hitachi and NEC
6420
1039
Nonlinear Transient Analysis - SCR=YES, NLTRD - SFE 4276, EC
In a nonlinear transient analysis, if the AUTO method is selected and the job
is submitted with scr=yes, then the job may fail with the following error
message: (HP only)
0*** SYSTEM FATAL ERROR 4276.SKPFIL
ERROR CODE 1039

1. Submit the job with scr=no
or insert the following dmap alter avoidance
2. Compile nltran souin=mscsou nolist noref
alter 1 $
putsys(0,192) $
6421
efault
68.2
Elements - QUAD4, STRESS(CORNER) - Poor D
In MSC/NASTRAN Version 68 there are three different options (CUBIC, BILIN and
SGAGE) for the calculation of QUAD4 corner stresses. Any of these options may
be explicitly requested on the STRESS entry. The default option obtained by
simply selecting STRESS(CORNER) is the CUBIC option. It has been determined
that the BILIN option produces better results for a wider range of problem,
thus beginning with Version 68.2 the default option is changed to BILIN.
Avoidance: In versions prior to Version 68.2 the user should explicitly
specify STRESS(BILIN) to obtain the BILIN option.
6422
SFM 3001
69
If there are no retained type 1 responses, a request for design sensitivity

output (PARAM OPTEXIT = 4 or 7) produces the following fatal message:
SYSTEM FATAL
MESSAGE 3001 MODULE = DOM6
THE INPUT DATA BLOCK NAMED DSCMG
AT POSITION
6 DOES NOT EXIST.
Avoidance: Force the retention on at least one type one response. This can be
done by creating a dummy invariant response that is constrained at a level that
will require its retention but that will not affect the design task when
OPTEXIT=7.
6424
mentation
Nonlinear Analysis - CGAP - UFM 2025, Poor Error Message/Docu
If a gap element connects coincident grid it is a documented requirement that a

coordinate system must be specified else USER FATAL MESSAGE 2025 will be
issued. Although this is a user input error, the fatal message should be
improved to include more descriptive text such as:
"USER FATAL MESSAGE ----, COINCIDENT GRIDS WITH NO CID FOR THE GAP ELEMENT
----."
6426
105
69
DMAP - MATMOD - Poor Message, SFM 4276 EC
If the first datablock for the MATMOD module does not exist, then SYSTEM FATAL
ERROR 4276.PACK ERROR CODE 105 may result. This has not been observed in the
solutions provided with MSC/NASTRAN. It has only been observed when a user DMAP
is used.
Avoidance: Make sure that the first datablock exists.
6430
69
DOM11 - SFM 3002
Optimization/Design Sensitivity - CORDi,
"SYSTEM FATAL MESSAGE 3002 MODULE = DOM11" may occur in an optimization run
that has many coordinate systems.
Avoidance: The error may be avoided by providing a set of dummy GRID entries
in the deck. Let NGRID be the total number of GRID entries including dummy ones
and NCS be the total number of coordinate systems defined in the deck. Then,
NGRID should be determined as follows:
NGRID > NCS * 13 / 8
6431
S - UFM 1126
69
Optimization/Design Sensitivity - GPSTRES
In solution 200, if a GPSTRESS request is made in two subcases with different

analysis types, for example analysis=statics and analysis=modes, then the
following fatal message is encountered:
USER FATAL MESSAGE 1126 (GNFIST)
DMAP MODULE SUPER3 IS ATTEMPTING TO OUTPUT DATABLOCK
206 NAME = GPSF
, WHICH ALREADY EXISTS.
USER ACTION: DELETE THE DATABLOCK, OR USE FILE GPSF
=OVRWRT
Avoidance: Remove the GPSTRESS request from one of the subcases.
6433
- SFM XXXX
69
Grid Point Stress - PARAM CURV, PARAM,S1M
In a normal mode analysis (e.g., SOL 63, 103, etc.), if the stress output is
requested in a material coordinate system, then the following error messages
may be issued:
SYSTEM FATAL MESSAGE XXXX. SUBROUTINE CURV2
HAS RETURNED WITH ERROR CONDITION
-2
LOC CODE = 600 IN SUBROUTINE CURV2
FILE NUM = 301
In addition to printing the regular stress output, the run will print the
transformed stresses for the first mode only.
Avoidance: Add modes=x in the Case Control Section. The value "x" is an
integer greater than or equal
to the number of modes in the model.
6436
68.2
, APRCOD=2 or 3 - SFM 4276, EC 7777

"SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777" indicating a divide by zero is
possible in the DOM9 module when either the default approximation method, Mixed
Method, or type 3, Convex Linearization, is used. The approximation method is
set by specifying APRCOD on the DOPTPRM entry.
Avoidance: If this error is encountered set APRCOD equal to 1, Direct
Linearization. Note that Direct Linearization is recommended for shape
optimization problems.
6454
Dynamic Response Analysis - SDAMP, FRRD1 - UFM 2089
The SDAMP case control command selects modal damping and thus should be ignored
in direct dynamic solutions. When it is present in a direct solution, it
results in the following misleading diagnostic messages:
USER FATAL MESSAGE 2089 MODULE = FRRD1
TABLE
4 IS UNDEFINED.
USER FATAL MESSAGE 2089 MODULE = FRRD1
TABLE
5 IS UNDEFINED.
Avoidance: Remove the SDAMP case control command.
6457
69
APD, BUFFSIZE - SFM 4276
Optimization/Design Sensitivity - DSVG4,
When a nonstandard buffsize is used, it is possible that a run will fail and
issue a SYSTEM FATAL MESSAGE 4276. To date this error has only been experienced
on HP systems in the DSVG4 and APD modules. The DSVG4 module is no longer
executed in the Version 68.2 solution sequences.
Avoidance: To avoid the error in general specify a standard buffsize. To
avoid the error in the DSVG4 module apply the following DMAP avoidance:
compile respsen souin=mscsou nolist noref
alter 171,171
PARAML
PARAML
matgen
diagonal
mpyad
6458
UFM 5165
UGy//'TRAILER'/1/S,N,NCOL $ no. of cols reqd. in SPAW1

UGx//'TRAILER'/1/S,N,nrow $ no. of rows reqd. in SPAW1
,/spaw1/4/ncol/nrow/0/1/nrow/1/1/nrow $
spaw1/spawn/'whole'/0. $
ugx,spawn,ugy/ugsn $
69
Optimization/Design Sensitivity - DSVG1 -
The message: "USER FATAL MESSAGE 5165 (DSVG1D-1) UNDEFINED INPUT FILE = 108,
NAME = (NONE) , ERROR CODE = -2, MODULE DSVG1 IS TERMINATED" has been
encountered in a static - normal modes design optimization run with
PARAM,OPTEXIT,7. (Version 68 and 68.2 only)
compile desopt souin=mscsou noref nolist
alter 257,257 $ version 68
alter 269,269 $ version 68.2
delete /fol1,ppf1,,, $
alter 291,291 $ version 68
alter 305,305 $ version 68.2
delete /fol1,ppf1,,, $
6460
70.5
) DMAP MODULE PARAML
Superelements - PARAML - UFM 1127 (GNFIST
If the split database approach is used in the SSS in Version 68 or later

releases, if any upstream superelement databases are "OFFLINE" (not available),
it is possible that MSC/NASTRAN may fail in module PARAML with USER FATAL
MESSAGE 1127 stating that the USET is not present. This only occurs if the
program is allowed to attempt to process the superelements whose databases are
OFFLINE.
Avoidance: As long as there are no changes to the previously processed
superelements, the SEALL command may be used pointing to only the superelements
to be processed in the current run. If the previously processed superelements
are changed, their databases must be ONLINE in order for MSC/NASTRAN to include
the effects of the changes.
6461
nswers
69
Heat Transfer Analysis - CQUAD8 - Wrong A
The capacitance matrix for the higher order CQUAD8 element uses a lumped
capacitance matrix instead of a consistent capacitance formulation. Therefore,
the weighting on the QUAD8 capacitance is not correct.
Avoidance: Use the CQUAD4 element instead.
6463
NE CURV3
69
Data Recovery - CURV3 - SFM XXXX SUBROUTI
The following error message may occurs when PARAM,CURV,1 and PARAM,S1M,1 are
used.
SYSTEM FATAL MESSAGE XXXX. SUBROUTINE CURV3
HAS RETURNED WITH ERROR CONDITION
LOC CODE = 150 IN SUBROUTINE CURV3
FILE NUM = 302
-3
Although the fatal message is printed, the run continues and gives the correct
results.
The reason for this error is not known at this time.
Avoidance: Ignore the error message.
6464
issing Output
70
Miscellaneous - SPCF=set id, DISP=ALL = M
If a deck contains a request for DISP=ALL and a SPCFORCE output request that
refers to a set id, then the displacement output may also be restricted to the
set. This error does not occur all the time. The exact cause is under
investigation.
Avoidance: Request SPCFORCE=ALL instead of a set id.
6466
2001
Miscellaneous - UFM 316
"USER FATAL MESSAGE 316" which indicates a format error may be issued when the
large-field input format is used when the format of the entry appears correct.
The error message may be caused because the number of large-field entries is
odd. Section 3.7.1 of the Reference Manual states that the number of
large-field format entries must be even. The program should check and issue a
specific fatal message if this rule is violated, or better yet, accept an even
or odd number of entries.
Avoidance: Add a blank wide field continuation line if you have an odd number
of large-field lines.
6468
69
stic Message, UFM 5401
Eigenvalue Analysis - REIGL - Poor Diagno
If the user sets f2 on the eigrl entry less than the first frequency of the
component, the design intent
is that the run is to continue, and set neigv=-1. The dmap writer then can
decide to continue or write his own fatal error. Lanczos (a.k.a. the REIGL
module) does all this, but also puts out the following misleading message:
*** SYSTEM FATAL MESSAGE 5401 (REIGL). LANCZOS METHOD IS UNABLE TO FIND ALL
6469
69
TOSPC - UFM 6137, SFM 3007
Nonlinear Transient Analysis - NLTRD2, AU
When using component modes synthesis on superelements in a nonlinear transient

analysis with adaptive time stepping (METHOD=ADAPT on the TSTEPNL entry), you
must select the exact number of generalized coordinates to match the number of
modes; otherwise, your job may fail with one of the following error messages:
*** USER FATAL MESSAGE 6137 (DFMNRS/D)
INPUT MATRIX IS RANK DEFICIENT, RANK =
SDCOMP INFORMATION MESSAGE--COLUMN YYY OF DATA BLOCK SCRATCH IS NULL.

SYSTEM FATAL MESSAGE 3007
ILLEGAL INPUT TO SUBROUTINE NLTRD2
Avoidance:
1. Specify NASTRAN SYSTEM(69)=16.
2. First determine the number of modes in the range of interest for each
component by specifying a small
frequency range for SINV on the EIGR
entry. Then specify the number of
6476
to Max Shear
2001
Plotting - XYPLOT - Stress Plots Default
The MSC/NASTRAN Quick Reference Guide states that von Mises stresses are the
default, but if von Mises stresses (item code 9 for QUAD4) are requested
through a xyplot request, but there is no corresponding case control request,
then max. shear is calculated instead of von Mises. This happens because the
stress request in case control is defaulted to von Mises in IFP, but the
corresponding default is not set in SDR2 or DDRMM for implied stress recovery
using the xyplot section.
Avoidance: The user can request STRESS(PLOT)= n in the case control to force
von Mises.
6477
ements
69
p-Elements - Missing Mass Matrix for p-el
If the first p-element processed (sorted by element type, then ID) has zero
density, then the mass of all elements are ignored.
Avoidance: If a zero mass element is desired, then it must be given a higher
ID. Another alternative is to assign a tiny density, like 1.e-30.
6478
68.1
Error, Traceback
Executive - XCSA - Unrecoverable Library
If a CEND is missing in the input deck the CRAY Version 68.0 of MSC/NASTRAN
hangs in module XCSA with the following messages:
lib-1212 /msc/msc68/exe/unicos/analysis.Y-MP: UNRECOVERABLE library error
An internal WRITE tried to write beyond the end of an internal file.
apparent state: unit 6 named out//infinite_loop.f06
last format: (A4)
lately writing sequential formatted internal
SIGNAL - Signal SIGABRT(6) caught, job aborting.
See signal(2), CRI manual SR-2012 for further information.
TB001 - BEGINNING OF TRACEBACK
- $TRBK
WAS CALLED BY RECOVR AT 525143a (LINE NUMBER
33)
- RECOVR WAS CALLED BY sysrcv AT 525363a (LINE NUMBER
112)
- sysrcv WAS CALLED BY __handlr AT 1053431a
etc.
6481
p-Elements - EMGPMD - UFM 4659
P-element models with cylindrical or spherical coordinate systems generated

using the Aries evaluator may encounter the message "USER FATAL MESSAGE 4659
(EMGPMD) DURING INTEGRATION FOR ELEMENT WITH ID =". This error is
demonstrated by tpl deck pfms03.dat.
Avoidance: Other than removing cylindrical and spherical coordinate systems
which is probably not practical, there is no guaranteed avoidance. Changing
the meshing or geometry of the model slightly may avoid the error.
6482
- UFM 2104
69
p-Elements - ADAPT, DATAREC, OUTRCV, GP1
If the p-Element Case Control commands ADAPT, DATAREC, or OUTRCV reference

nonexistent bulk data entries, then the job may fail in the GP1 module with the
message "FATAL MESSAGE 2104, UNDEFINED COORDINATE SYSTEM"
Avoidance: Add the appropriate bulk data entries.
6483
M 6286
69
Postprocessing - OUTPUT2, OGS1, OGPS - UW
If a param,post,-1 is used in sol106 then following warning message is issued

while writing the
OGS1 datablock.
USER WARNING MESSAGE 6286 (ZREAD)

THE NDDL DESCRIPTION OF DATA BLOCK=OGS1
, RECORD=IDENT ,DOES NOT HAVE AN
EITHER/OR TO MATCH OPT= 10.
ITEMS ARE ASSUMED TO BE UNDEFINED.
USER INFORMATION: PROBABLE CAUSE IS WRONG NDDL DESCRIPTION CODED, OR ,
WRONG GENERIC DATABLOCK USED (E.G. OES INSTEAD OF OEF).
6484
21
70.5.1
SSSALTER - PARAM,DRMH,1 - SFM 4276, EC 30
Single precision machines, i.e., Cray, some SGI, and NEC, fail when trying to
run the files "CBAR1G.DAT" and "cbar9g.dat" in the sssalter directory. This
data deck requests data recovery using client developed modules, drmh1 and
drmh3, which have not been ported to single precision (long word) machines.
SUN systems may experience problems running the DRMH3 module only. The jobs
may end in the DRMH3 module with the message "time: command terminated
abnormally" issued to the log file.
Note that in versions past v68, the problem test decks have been renamed to
alter1g.dat, 2g, 3g, and 9g respectively.
6485
T FROM DUMMY
70
DMAP - TRNSP - Poor Message, CALLING PEXI
The following error message may be output from the TRNSP module when the DMAP
forces single precision to be used by setting system cell(55) in the DMAP
(i.e., PARAM //'SYSTEM'/S,N,IPREC/55/1 ):
CALLING PEXIT FROM DUMMY
Avoidance: A user should avoid forcing the precision. MSC recommends letting
the precision default to machine precision. The avoidance is to remove this
PARAM module from the dmap.
6487
69
ODES - SFM 4276 GETSTR E.C. 1409
Optimization/Design Sensitivity - DSAL, M
If the MODES case control command is used in SOL 200, module DSAL will issue
the message "SYSTEM FATAL MESSAGE 4276 ERROR CODE 1409".
Avoidance: Do not use the MODES command in SOL 200.
6488
69
utput, Fails to trap syntax error
Executive - COMPILER,LIST,REF - Missing O
When COMPILE,LIST is input instead of COMPILER,LIST, the job runs failing to

trap the syntax error and the listing is not produced.
6490
69
- Misleading Subcase Identifier
The subcase identifier for the design objective produced when the P2 DOPTPRM
parameter is set to 1 lists the first subcase when the objective function is
weight or volume.
Avoidance: Weight and volume responses are not a function of the subcase and
the misleading subcase identifier should be ignored. Version 69 corrects this
error by indicating a subcase id of zero.
6491
DMAP - COMPILE, DIAG 4,14, COMPILER - Extra Output
Starting in Version 68, if the COMPILE NDDL command is used to punch out the
NDDL and both the SOL and DIAG 4,14 (or COMPILER LIST,REF) statements are
specified in the Executive Control Section, then NDDL will be written to the
punch file twice.
1. Remove the SOL statement.
2. Remove either 4 or 14 from the DIAG (or REF or LIST from the COMPILER)
statement.
6492
69
171 (DSVG1D-7) Unexpected EOR
Design Sensitivity - DSVG1, MATi - UFM 5
The following message occurs when mass sensitivities are being calculated and
some of the materials associated with the designed elements have a density of
zero and others do not.
UFM 5171 (DSVG1D-7) Unexpected EOR in File 101.
SYSTEM FATAL
MESSAGE 3003 MODULE = DSVG1
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK MDICT (FILE
106) IN SUBROUTINE DSVG1D
Avoidance: Assign a small, non-zero density in place of the zero values.
6494
p
69
Eigenvalue Analysis - SDRX - Infinite Loo
In SOLs 39, 63, 103, and 200 with ANALYSIS=MODES, if PLOAD1 entries are present
and they are applied to CBAR or CBEAM elements then the run will go into an
infinite loop in the SDRX module. (Version 68.2 only)
Avoidance: Remove PLOAD1 Bulk Data entries or remove the STRESS and FORCE Case
Control command requests.
6504
2001
Rigid Elements - GP4, RBE3 - Poor Message
If the components specified on the "UM" set reference the same grid point as
the REFGRID, and the "UM" components is an incomplete subset of the REFC
components, then the job may fail with the following error message in versions
prior to Version 68.
0*** USER FATAL MESSAGE 2332, DEPENDENT MPC COMPONENT HAS BEEN SPECIFIED TWICE.
EXTERNAL ID = xx DOF = yy
In Version 68 and above, depending on the solution sequence, the job may
terminate with no messages in GP4 or it may fatal with the following unclear
error message:
FATAL ERROR
A sample of an RBE3 that can cause this error is as follows:
RBE3,
,33,
10,,
4.7,
12,
16,
17,
1234,
31
1.,
123,
11,
26,
,UM,
16,
14
Avoidance: Remove the offending "UM" gr

6508
69
S=BUCK - UFM 4683
Shape optimization with the analytic boundary shapes approach and buckling
analysis (ANALYSIS=BUCK) in solution 200 produces the following error message:
USER FATAL MESSAGE 4683, KDIF MATRIX NEEDED FOR EIGENVALUE ANALYSIS
Avoidance: The error is avoidable if the user generates basis vectors using
either the direct input of shapes method or the DVGRID (i.e., manual) approach.
Using geometric boundary shapes will also produce the same error.
6509
68.2.3
p-Elements - PLOAD4 - Wrong Answers
If a PLOAD4 is used to apply a pressure load to a p-element that has the

connectivity inverted, i.e. that the right hand rule applied to the numbering
of the first face produces a vector pointing out of the element, then the
pressure is applied in the wrong direction and wrong answers result.
6514
69
- Poor Performance
Optimization/Design Sensitivity - RESPSEN
The RESPSEN subDMAP uses the UG datablock rather than UG1. The result is that
much of the efficiency that can be gained from load case and/or frequency
deletion is lost. Further, there is no current requirement for static
spcforces in this subDMAP.
Avoidance: A new RESPSEN subDMAP is available on request.
6515
69
DLINK - UWM 7001 (DOPR1B)
Optimization/Design Sensitivity - DOPR1B,
The message "USER WARNING MESSAGE 7001 (DOPR1B) DLINK GIVES WRONG XINIT VALUE"
is produced in error whenever NMSG = INT (( ndv - 4 )/ 7 ) - ndvi +1 is a
positive number. For example, if there are 30 design variables, but only one
independent design variable, 3 incorrect messages are produced. The user input
value for the design variable value is incorrect. The value computed based on
the DLINK entry is correct. Thus, the error does not produce wrong answers.
Avoidance: No avoidance is necessary since the error does not produce wrong
answers but only an incorrect warning message.
6517
69
Bad CSTM Trailer
p-Elements - GMCORD, DBUNLOAD, OUTPUT2 -
Data decks that contain only convective coordinate systems (GMCORD) and no
CORDij type data entries have bad CSTM trailers. This does not cause a problem
on homogeneous platforms, however, difficulty may be encountered during the
neutral OUTPUT2 or DBUNLOAD operations.
Avoidance: Include a dummy CORDij entry in the data deck.
6521
Poor Message
2004.0.4
Nonlinear Analysis - TABLES1 - UFM 2076,
In nonlinear analysis, USER FATAL MESSAGE 2076 is issued if the MATS1 entry is
type PLASTIC and the slopes of the first two segments of the stress-strain
curve on the referenced TABLES1 entry are the same. The message:
USER FATAL MESSAGE 2076, ELEMENT 0 REFERENCES TABLES1 4 WHICH IS THE INCORRECT
FORM FOR NONLINEAR ELASTIC ANALYSIS
does not clearly indicate the problem and incorrectly references element 0.
6525
F Output
69
Nonlinear Analysis - CGAP - Incorrect SPC
When the GAP element has an offset moments may be created by the shear force
times the axial offset and the axial force times the lateral offset). These
moments are balanced by forces of single point constraint, however, the SPC
Force output is incorrect in both magnitude and sign.
Avoidance: Remove the offset.
6527
69
nual - PARAM,ACOUT,RMS
Documentation - Quick Ref. Guide, Ref. Ma
PARAM,ACOUT,RMS only applies to element output. The current documentation in

the MSC/NASTRAN Version 68 Quick Reference Guide erroneously implies that all
the pressure output will be RMS.
Avoidance: In the MSC/NASTRAN Quick Reference Guide, in the definition for
parameter ACOUT, the following:
ACOUT specifies the type of sound pressure level output to be
used with the DISPLACEMENT or PRESSURE Case Control command in
coupled fluid-structural analysis (see the MSC/NASTRAN Reference
Manual, Chapter 15). The default requests the peak pressure
level. ACOUT = RMS requests RMS pressure level and is only
available in Solution Sequences 108 and 111.
To obtain sound pressure level in units of dB and dBA, a peak
reference pressure must be specified with PARAM, PREFDB. The
6528
68.2
) - Wrong Answers, SFM 4276
Composites - SDR2, SDRCOMP, STRESS(CORNER
If a STRESS(CORNER) request is made for a deck with composite elements wrong

answers result. The run may also issue SYSTEM FATAL MESSAGE 4276 EC 7777 or
stop with a "Terminated Abnormally" message in the log file.
Avoidance: The only avoidance is to either not request STRESS(CORNER) at all,
execute STRESS(CORNER) for noncomposite elements in a cold start and then
recover the stresses in the layered composite elements in a restart run. In
Version 68.2 this error has been addressed by treating a STRESS(CORNER)=ALL
request as STRESS(CORNER) for noncomposite elements only and outputting center
stress for the composite elements.
6534
2072
69
Acoustic Analysis - RESTART, GEOM2 - SWM
The message "SYSTEM WARNING MESSAGE 2072, CARD TYPE

7408 NOT FOUND ON DATA
BLOCK" may be issued in an acoustic analysis restart. The warning message does
not affect the run and may be ignored.
Avoidance: No avoidance is necessary.
6535
Restart
69
Acoustic Analysis - RESTART - Inefficient
Changing the PANEL definition in the restart of an acoustic analysis causes the
modes to be unnecessarily re-calculated.
Avoidance: Apply the following DMAP alter to MSC/NASTRAN Version 68.1
COMPILE IFPL SOUIN=MSCSOU NOLIST NOREF
ALTER 146,146
6537
68.2.1
Dynamics - STRAIN - Missing output
STRAIN output is missing in SOLs 110, 111, 112, 145, 146, and 200, with
ANALYSIS=MFREQ, MTRAN, and FLUTTER if PARAM, DDRMM is 0, which is the default.
This error occurs in MSC/NASTRAN Version 68.2.0 only. This version of
MSC/NASTRAN is included with MSC/Aries 7.0.0 on the IBM/RS6000, HP 9000/700,
SUN SUNOS and SUN SOLARIS systems. Version 68.2.0 has not been delivered to
non MSC/Aries users. Version 68.2.1 corrects this error and is delivered to
non MSC/Aries clients. (Version 68.2. only)
Avoidance: Insert PARAM, DDRMM, -1 or the following DMAP alter:
compile sedrcvr noref nolist
alter 174
DDRMM
CASEDR,UH1,OL1,,,OSTR2,,XYCDBDR/,,OSTR2Y,,//3 $
6538
try
69
Documentation - Illegal data on EPOINT en
The MSC/NASTRAN Version 68 Quick Reference guide does not document a limit for
the ID of an EPOINT. The limit is 1000000.
6539
module
70
P-Elements - SDRP - SFM 4276 EC 7777 SDRP
The job will stop in the SDRP module and the message "SYSTEM FATAL ERROR
4276.RECOVR ERROR CODE 7777" will be output when multiple output requests
are used on the output bulk data entry. The error only occurs on the Convex
Version 68 systems. The error only occurs when the output requested is
changed between sets.(i.e. when output requested for set 3 is different than
output requested for set 2. For example:
OUTPUT
1
ELSET=3,DISP=PRINT,STRESS=NONE,STRAIN=NONE,ERROR=NONE,
PVAL=NONE,FIRST=NO,BY=0
ELSET=2,DISP=NONE,STRESS=PRINT,STRAIN=NONE,ERROR=NONE,
PVAL=NONE,FIRST=NO,BY=0
ELSET=999999,DISP=NONE,STRESS=NONE,STRAIN=NONE,ERROR=PRINT,
PVAL=PRINT,FIRST=YES,BY=1
6544
69
SCREEN - SFM 3001
Optimization/Design Sensitivity - SDSC, D
The message "SYSTEM FATAL MESSAGE 3001 MODULE = SDSC THE INPUT DATA BLOCK NAMED
DSCMCOL DOES NOT EXIST" is produced in a sensitivity analysis when there are no
active responses; i.e., all the responses have been screened out becuase they
do not exceed the threshold required for sensitivity computations.
Avoidance: Use the following DMAP avoidance (for V68.2.3):
compile exitopt list noref souin=mscsou
alter 'putsys'
dbstatus R1TABRG,RSP2RG//S,N,NORSP1/S,N,NORSP2 $
if (NORSP1>0 OR NORSP2>0) THEN $
alter 'optexit'(7)
endif $ NORSP1>0 OR NORSP2>0
6547
FM 4276 EC 211
70
Heat Transfer Analysis - CHBDYG, RMG2 - S
If a connection order error is made on the CHBDYG, AREA4 element, the message
SYSTEM FATAL ERROR 4276.BLDPK
ERROR CODE
211
may be output which does not give the user any clude to the input error.
Avoidance: There is no simple avoidance other than manually checking your
CHBDYG,AREA4 elements for the correct connectivity.
6551
rs
69.1
Elements - HEXA, TEMP(LOAD) - Wrong answe
The stress output for the HEXA element has an error. This error occurs only
for grid locations (not at the center location). The error occurs only when
the following conditions are all true:
1. An eight node HEXA element with bubble functions is used.
2. The temperatures are not the same at all grid points.
3. The stress output coordinate system axes do not align with the element
coordinate system axes.
Avoidance: The error may be averted by avoiding any one of the aforementioned
conditions.
6552
69
Heat Transfer Analysis - VIEW - Missing O
utput, UFM 6660, Not Upward Compatible
Using the old VIEW module produces a punch file in which the RADMiX ambient
element (CHBDYP,POINT) is missing. If the punch file is included in a
subsequent job, MSC/NASTRAN fails and the following message is issued:
USER FATAL MESSAGE 6660 (VIEW)
THE RADIATION MATRIX FOR RADIATION CAVITY ID=
11 DEFINED ON RADLST OR
RADMTX BULK DATA ENTRIES HAS WRONG FORMAT OR DATA. USER INFORMATION: THE
RADIATION MATRIX MUST BE SPECIFIED COMPLETELY.
Avoidance: Use the VIEW3D entry to avoid the problem.
6554
69
Heat Transfer Analysis - PARAM,NDAMP - Ph
ase Change Analysis, Poor Convergence
PARAM,NDAMP only allows a maximum value of .1. This is inadequate for the
highly nonlinear phase change problem. The value of .1 is equivalent to a beta
of .55 using the Crank-Nicholson method. The phase change problem requires a
beta value of 1.0. Convergence is extremely difficult for the phase change
problem with the current limitation on PARAM,NDAMP.
6558
nswers
69
Matrix Methods - SMPYAD, DBVIEW - Wrong A
If SMPYAD is asked to do a matrix product of the form A(transpose)*B*C, and

matrix C is a DBVIEW version of the datablock with the same name as matrix A,
then SMPYAD substitutes matrix A for matrix C and performs A(transpose)*B*A
instead, which will lead to wrong answers. For example:
type db phg,mgg
type parm,nddl,i,n,meth
meth=6
dbview phg2=phg(where meth=3)
$ Points to phg, but where method=3 not
6!
smpyad phg,mgg,phg2,,,/phimphi1/3////1 $ Does phg*mgg*phg, not
phg*mgg*phg2!!!!!!
Avoidance: The simplest avoidance is to set nastran system cell 129 to 1 prior
to the smpyad (e.g. insert PUTSYS(129,1) into the DMAP. The system cell may
be reset to zero immediately after the smpyad by inserting PUTSYS(129,0).
6570
RT - UFM 2166
69
Nonlinear Transient Heat Transfer - RESTA
The enforced temperature datablock, YSNL, is not stored in the database. This
causes restarts in solution 159 to fail with the message:
USER FATAL MESSAGE 2166, MATRIX TO BE PARTITIONED IS OF SIZE xx ROWS BY yy
COLUMNS.
ROW PARTITION SIZE IS xx COLUMN PARTITION SIZE IS zz (INCOMPATIBLE).
Avoidance: Insert the following alter in both the cold start and all
subsequent restarts:
compile nltcsh souin=mscsou noref nolist
alter 583 $ v68
$alter 585 $ v68.2
call dbfetch /ysnl,,,,/0/0/0/0/0 $
alter 618 $ v68
$alter 620 $ v68.2
call dbstore ysnl,,,,//0/0/'
'/0 $
6571
68.2
Miscellaneous - SSG1 - SFM 4276 EC 7777
In MSC/NASTRAN version 68.0 or 68.1 it is possible to get the message "SYSTEM

FATAL MESSAGE 4276 ERROR CODE 7777", in the module SSG1 because of an error in
SSG1 which causes overlapping memory regions. This error is therefore data
dependent and is most likely to occur on the Hewlett Packard 9000, SGI R8000 or
the DEC/Alpha OSF/1 systems. This error has been fixed in the V68.2 system.
Avoidance: It may be possible to avoid this error if the model were changed
slightly.
6572
p-Elements - GMCURVs with MSC/Aries Geometry Evaluator
For certain cases, when the end GRID or the secant point is mapped back to the
GMCURV, the MSC/Aries geometric evaluator (i.e., group MSCGRP2 on the GMCURV or
GMSURF entry) returns the following message:
SYSTEM FATAL MESSAGE 6498 (Aries B-spline Evaluator, Get Curve Parameter)
GEOMETRY API MESSAGE FOLLOWS.
USER INFORMATION: Numerical Error in Evaluator.
Curve: 150.
Point: ( 1.000000e+01 1.288252e+02 1.402565e+02).
Avoidance: The problem is under investigation and it is unclear specifically
when this error occurs or how to avoid the problem.
6573
69
- Obsolete, Superseded Documentation
Documentation - Reference Manual, PLOTPS
Section 13.4 of the MSC/NASTRAN Reference Manual is obsolete. It has been

superseded by the Utilities section of the Installation Guide for the each
computer type.
6574
nswers
69
Heat Transfer Analysis - CHBDYE - Wrong A
If a CHBDYE (Boundary element) is used where side 5 represents an edge of a

shell element such as a CQUAD4, CQUAD8, TRIA3, or TRIA6 element, the surface
area calculated will be incorrect and wrong answers are produced.
Avoidance: Use the CHBDYP,LINE option to represent the convection or radiation
off the edge of the shell element.
6575
Answers
2001
Nonlinear Analysis - QUAD4, ZOFF - Wrong
In Nonlinear Statics Analysis the output element forces from the QUAD4 elements
are incorrect when the uniform offset (ZOFF field in the CQUAD4 bulk data) is
non-zero. The force values are actually calculated in the non-offset element
coordinate system while the stresses are calculated correctly in the offset
reference system. All other solutions calculate both outputs in the reference
system.
Avoidance: Use the stress output and ignore the element force output.
6577
2001
GC - UFM 2075 and UFM 2079
Eigenvalue Analysis - DPD, EIGR, EIGB, EI
When the POINT method of normalizing eigenvectors is selected on EIGR, EIGB or

EIGC entries, and the specified grid/dof does not exist, the following
mis-leading error messages is issued:
1) If the grid does not exist:
SYSTEM OR USER DMAP FATAL MESSAGE 2075, IMPROPER VALUE xx FOR FIRST
PARAMETER IN DMAP INSTRUCTION SDR2

2) If the component is invalid (in the case of SPOINT for example):
USER FATAL MESSAGE 2079, GRID OR SCALAR POINT
COORDINATE REFERENCED ON A NOLINI
CARD.
0 HAS AN UNDEFINED
Note that these messages are issued even if the EIGR, EIGB or EIGC at fault is
not selected by a METHOD
entry in the Case Control section.
Avoidance: Remove or change the offending entry.
6578
swers
Heat Transfer - VIEW3D, CHBDYG,AREA8, CHBDYG,AREA6 - Wrong An
The boundary surface elements CHBDYG type AREA8 and AREA6 were implemented in
Version 68 to complement higher-order conduction elements such as the CQUAD8,
HEX20, and TRIA6. Using these surface elements in View factor calculations
results in an incorrect view factor if the surfaces are not in-plane or on a
curve surface. Therefore in order to model surfaces on curvilinear surfaces
such as cylinder it is best to use AREA4 and AREA3 elements.
Avoidance: Use CHBDYG,AREA4 instead of AREA8 to model curvilinear surface for
view factor calculation.
Similarly, use CHBDYG,AREA3 instead of AREA6 to model curvilinear surface for
view factor calculation.
6579
69
ALL - SFM 4276 EC 7777
Dynamic Response - SDR2, OFREQUENCY, SET=
In a frequency response run if the OFREQUENCY references a set where "all"

frequencies are specified, then the job may fail with the message "SYSTEM
FATAL ERROR 4276.RECOVR ERROR CODE 7777".
Avoidance: Remove the ofreq=xxx case control command.
6580
69
- SFM 4276 EC 7777
Nonlinear Transient Heat Transfer - VIEW
An integer overflow, SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777, has been
encountered on the VAX VMS system while calculating the matrix density of RECM
in the VIEW module.
Avoidance: The only way to avoid the error is to reduce total number of HBDYi
elements for each radiation cavity.
6582
69.1
Postprocessing - DBC - XDBs are Too Large
XDB files generated on a NEC SuperUX system are excessively large (by a factor
of 8). These files are still readable from RECEIVE, the corresponding NTRL
files are the correct size.
Avoidance: The corresponding NTRL files are the correct size, so storing the
XDB files in this form resolves the problem.
6590
Message
69
DMAP - ALTER, Missing Blank - No Warning
When the following DMAP statement:

alter 449,449 $
was mistyped as:
alter449,449 $
the alter was ignored and no warning message was issued.
6596
70
EL - Missing Documentation
Documentation - PARAM,USETPRT PARAM,USETS
In the Version 68 MSC/NASTRAN Quick Reference Guide, the documentation for

PARAM,USETPRT and USETSEL should include the following set names and their
decimal equivalents:
U1
U2
U3
U4
U5
U6
6598
Output
2147483648
1073741824
536870912
268435456
134217728
67108864
GL
Miscellaneous - PARAM - UFM 300, Improper
MSC/NASTRAN has a restriction on the magnitude of an integer parameter of nine

(9) digits. If an integer value with more than 9 digits is used for a
parameter value (e.g. PARAM*,USETSEL,2147483648) then the parameter does not
function properly. If the value of the parameter is hard coded directly in the
DMAP (e.g. TABPRT USET,EQEXIN//'USET'/0/2147483648) the message " USER FATAL
MESSAGE 300 FROM CRCARD ABOVE" is issued.
6599
MP - UFM 6137
69
Frequency Response Analysis - FRRD1, DECO
When singular matrices are encountered in a frequency response analysis,

MSC/NASTRAN Version 68 would fail in sparse decomposition with the message:
USER FATAL MESSAGE 6137 (DFMNRS/D)
INPUT MATRIX IS RANK DEFICIENT, RANK = 2
USER ACTION: CHECK MODEL
The most common cause of the singular systems is a free body excited at zero
frequency. Non-sparse decomposition, which was the default prior to Version
68, behaves differently. Non-Sparse decomposition would output messages that
warn the user that a small term was being added to the diagonal so that
decomposition could continue. An example of the messages are:
USER WARNING MESSAGE---ROW
3 OF LOW. TRI. FACTOR HAS DIAGONAL TERM = 0( OR
.LT. 0 IF CHOLESKY )
USER INFORMATION MESSAGE--- 1.0E-10 SUBSTITUTED FOR DIAG. TERM OF
6601
69
Buckling - TEMP(INIT) - Wrong Answers
In a linear buckling analysis, if TEMP(INIT) references a temperature that is

non-zero, then the eigenvalue calculation will be incorrect, which in turn will
lead to a wrong buckling load. The results of the static subcase are correct.
Avoidance: Use one of the following avoidances:
1. Set TEMP(INIT) to zero and adjust the applied temperature to yield the same
delta temperature
or
2. Set the initial temperature using the TREF field on the MATi entry instead
of using the TEMP(INIT) Case
Control Command.
6603
70
FM 4252, UIM 4570
DMAP - SELA, SEMA, SEDR, PLTVEC, SEP4 - S
Starting in Version 67.7, the superelement modules, SELA, SEMA, SEDR, PLTVEC,
and SEP4, only recognize a qualifier name of SEID for the qualifier which
defines the data block family in the DBVIEW WHERE clauses. For example, in
subDMAP SELA, if we modify the DBVIEW PAUP statement for a family of userdefined data blocks, MYDB, and modify the 2nd parameter in the SELA module,
DBVIEW PAUP = MYDB (WHERE MYQUAL=*) $
DBVIEW MAPUPL = MAPS (WHERE SEDWN=TEMP AND SEID=* AND PEID=*) $
SELA
PJC,SLIST,EMAP,EQEXINS,PAUP,MAPUPL,GDNTAB/
PG/
SEID/'MYQUAL'/0/S,N,NOPGS $
then the SELA module will not find any members in the family PAUP.
Avoidance: Modify the NDDL so that the PATH statement for the data block MYDB
contains SEID as a qualifier.
6610
69
Inconsistent Capacitance Matrix
Heat Transfer Analysis - ROD, BAR, BEAM -
The rod element was changed in Version 68 to have a consistent heat capacitance
matrix. However, all the other one dimensional heat conduction elements such as
the beam and bar elements have a lumped representation. This difference
between the one dimensional element formulations may result in slight
differences between a model comparing RODs to BARs and/or BEAMs. For a
typical transient thermal analysis comparing the result between ROD and BAR
elements, the difference in temperature output is generally less than 0.2%.
Avoidance: Use bar or beam element.
6613
69
Incorrect Loading, Wrong Answers
Heat Transfer Analysis - CHBDYE, SSG1 -
If a CHBDYE surface type element is used to model an edge with mid-side nodes
and a heat flux loading is applied to this edge, then the answers will be
incorrect. This error occurs because the SSG1 module does not know there is
loading on the midside nodes.
Avoidance: Do not reference elements with mid=side nodes on the CHBDYE entry.
For example, instead of using the higher-order CQUAD8 elements that have
mid-side nodes, use the lower order CQUAD4 elements.
6614
s
69
Acoustic Analysis - ACSRCE - Wrong Answer
The ACSRCE which defines the power versus frequency curve for an acoustic
source results in an incorrect acoustic fluid power input. The power is off by
a factor of i*omega, the radian frequency.
Avoidance: Use the RLOAD data entry instead with Qdot, (volume acceleration).
Qdot is calculated as the square-root of 8 times pi times the speed of sound in
the fluid times power divided by the density of the fluid:
Qdot = sqrt(8*pi*c*power/rho)
6618
300
69
Documentation - String-based alter - UFM
When using the string-based alter feature in Version 68.2, the dmap strings
should be enclosed by the ' single-quotation string on both ends (e.g.,
'string1'). In the Version 68.2 Release Notes, the dmap strings are shown to
be enclosed with the ` single-quotation string on the left end and the inverted
single-quotation string on the right end (e.g., `string1') throughout chapter
5. An example of this documentation error is shown on page 40 of the Release
Notes as
ALTER `CALL.*PHASE1B' $
The correct format for the above string-based alter is
ALTER 'CALL.*PHASE1B' $
Note that the V68.2 Release notes can not be corrected. Since this
documentation error does not exist anywhere else it is considered fixed in
Version 69.
6620
69
- Poor Message
Installation - No Authorization Code File
During the installation of MSC/NASTRAN V68.2 the user is asked to run a test
problem after installation. If the user requests to run a test problem and
there is no authorization code file, then the job aborts with:
'The test appears to have failed for an unknown reason.'
If a bad authorization code is installed, then the installation test problem
determines the correct error.
But if no authorization code has been installed, then the noted message is
issued.
Avoidance: Install a correct authorization code.
6631
M 5609
69.0.2
Optimization - Superelements, DRESP2 - UF
If an optimization model contains superelements, UFM 5609 may be incorrectly

issued if different response types are combined using a DRESP2. For example,
this error occurs if a superelement is defined in a frequency response
optimization model, and both FRDISP and FRFORC responses from DRESP1 entries
are combined on a DRESP2 entry.
Avoidance: If different response items need to be combined, use a

residual-structure only model or use external superelements.
6632
69
- Missing Documentation
Documentation - SYSTEM(198), SYSTEM(205)
Version 68.1 of MSC/NASTRAN introduced a very significant performance

improvement to sparse decomposition. This enhancement is called the high-rank
update. The capability is controlled by two system cells, SYSTEM(205) and
SYSTEM(198). The optimum value of these system cells is machine dependent. In
Version 68.1 the optimum value of these two system cells are set in the
delivered system rc file. In Version 68.2 the optimum values are set in the
code. In either version the values may be overwitten by the user but this is
generally not recommended.
SYSTEM(205) sets the value for the rank of update. The value used for any run
may be determined from user information message 4157 output in the f04
execution summary. SYSTEM(198) sets a lower bound on the number of rows to be
elimina
6643
69
PTEXIT, DSAL - SFM 4276, EC 3021
Optimization/Design Sensitivity - PARAM,O
The message "SYSTEM FATAL MESSAGE 4276, ERROR CODE 3021" occurs in the DSAL
module when a converged optimum solution is achieved in a modal frequency
response design task and OPTEXIT=7 is used to obtain sensitivities of the final
design.
Avoidance: Remove the OPTEXIT=7 request. A new run that uses the final design
and has OPTEXIT=4 will provide the desired information.
6656
69
- Segmentation Fault, Trap Encountered
A DEQATN bulk data entry may not end with a semicolon(;). If it does, the run
fails while processing the input in a machine-dependent manner. This error has
appeared as a segmentation fault on SGI machines and a "Trap Encountered" on
RS/6000 machines.
Avoidance: Do not use a semicolon as the last character on a DEQATN entry.
6668
68.2
DMAP - OUTPUT2 - FORTRAN I/O ERROR 910
On the HP, if a user dmap contains an output2 request and there is no

corresponding assign statement, then the job may terminate without any error
messages in the f06 file. The following error messages may appear in the log
file.
*** FORTRAN I/O ERROR 910: ACCESS PAST END OF RECORD ATTEMPTED
FILE: ftn11, UNIT: 11
Avoidance: Explicitly define the output2 file using the assign statement in the
FMS section.
6676
Plotting - SPCFORCE, MPCFORCE, XYPLOT - Missing Output
If XYPLOTs of SPCFORCEs or MPCFORCEs are requested, the items must be requested

in the case control before the OUTPUT(XYPLOT) section. For example, if SPCFORCE
plots are to be requested for points 1 and 5, the following output request (or
a similar one) would be required in the case control:
SET 99 = 1,5
SPCFORCE = 99
6678
Nonlinear Analysis - TEMP(LOAD) - Wrong Nonlinear Strains wit
h Temperature Loads
In nonlinear solution sequences, the output entitled "Nonlinear Stresses"
prints mechanical strains which do not include the thermal strains. The true
strains are the sum of the mechanical and thermal strains. The only exception
to this limitation are the hyperelastic elements which output the true strain.
6682
nd P5<0.0.
69
DMAP - MATMOD - MATMOD with option P1=2 a
Option P1=2 of the MATMOD module is intended to filter the matrix and set all
terms in the matrix with magnitude smaller than P5 to 0.0. However, if P5 is
set to a negative value, no filtering will take place.
Avoidance: Use a positive value for P5.
6701
nswers
69
Transient Heat Transfer - TETRA - Wrong A
The 10-noded tetra for the transient thermal analysis (SOL 159) will obtain
wrong answer.
Avoidance: Use lower order tetra elements.
6705
69
E - Missing Output, Wrong Answers
Optimization/Design Sensitivity - MPCFORC
Running SOL 200 with SCR=NO may result in wrong or missing MPCFORCE output.
ANALYSIS=STATICS results in missing MPCFORCE output for all but the first
cycle. Other approaches result in wrong but plausible answers for all but the
first design cycle.
Avoidance: Submit job with SCR=YES.
6718
Ignored
P-Elements - GRMAX, GNSTRT, GNMAX, VGSTRT - Keyword Settings
The NASTRAN keywords GRMAX, GNSTRT, GNMAX, VGSTRT,VGMAX,VESTRT,VEMAX, that

control p-element parameters may be ignored.
Avoidance: Use the actual system cells 175, 178, 179, 180, 181, 182, and 183.
6722
69
sing CHBDYE - Wrong Answers
Transient Heat Transfer - TRIA6 element u
The heat capacitance for the edge of the TRIA6 element is not correct. This
results in wrong answers whenever the CHBDYE (boundary element) is used with
SIDE other than side 1.
Avodiance: Use TRIA3 element with CHBDYE or CHBDYP,LINE for the edge convection.
6724
69
- UFM 149 and SFE 4276 in LINKAR
DMAP - Linking with SOL or LINK statement
If UFM 149 is issued then, in some cases, SFE 4276 will be issued and the run
does not terminate gracefully. The exact symptoms are under investigation. If
this occurs during the creation of a delivery data base, then the data base
will be corrupted.
Avoidance: Other than correcting the DMAP error indicated by UFM 149, there is
no avoidance.
6725
COMP - UFM
68.2
Matrix Methods - Sparse Decomposition, DE
A large model that has run successfully on other machines experiences negative
terms on the factor when decomposing KOO on the MSC/NASTRAN Version 68.1 on the
SGI R8000 computer.
Avoidance: If decomposition errors are encountered that do not appear to be due
to modeling problems, then it may be due to the High Rank Update feature
introduced in Version 68.1. Disable this feature by setting NASTRAN
SYSTEM(198)=1 SYSTEM(205)=1 or switch to Version 68.2 where the error has been
corrected.
6726
68.2
Miscellaneous - MPYAD - SFM 4276
Large client model failed in the MPYAD module on the SGI R8000 computer.
Avoidance: The problem was avoided by disabling the sparse option for MPYAD.
This was done by NASTRAN SPARSE=24, however, a significant penalty in CPU
resulted.
6727
69
Cyclic Symmetry - CYSUP - UFM 5423
In MSC/NASTRAN Version 68.2 it is possible to get the message "USER FATAL

MESSAGE 5423 --- ATTEMPT TO ADD INCOMPATIBLE MATRICES, (SADD5)" in a cyclic
symmetry (SOL 114) run using the CYSUP entry. Version 67.5 produces incorrect
answers under the same circumstances.
Avoidance: For V67.5
COMPILE STATCYC SOUIN=MSCSOU NOREF NOLIST
ALTER 8,8
NOA=LTOI(NOGSET=NOASET) $
CEND
Avoidance: For V68
compile statcyc noref nolist
alter 'noa=ltoi',''
noa=ltoi(nogset=noaset) $
6728
69
heat transfer - apply boundary condition
on both side on CHBDYE or CHBDYG aqa_02
heat transfer - apply boundary condition on both side on CHBDYE or CHBDYG SEE CSR 7462 for the fix that have corrected this error in version 69
Wrong summary for the H E A T
F L O W
I N T O
H B D Y
E L E M E N T S
The user has the option using same boundary element to specify front side and
the backside convection and radiation. The temperature vectors calculated from
using this option is correct. However, the summary table only show the energy
on the front side of the element
H E A T
F L O W
I N T O
H B D Y
E L E M E N T S
(CHBDY)
ELEMENT-ID
APPLIED-LOAD FREE-CONVECTION
FORCED-CONVECTION
RADIATION
TOTAL
13
4.000000E+00
0.000000E+00
0.000000E+00
4.0000
6731
ng Output
69
0.000000E+00
Cyclic Symmetry - SPCFORCE, CYSUP - Missi
The forces of single point constraints in the static cyclic symmetry solution
sequence SOL 81 do not include the reactions at the degrees of freedom
specified on the CYSUP Bulk Data entry.
Avoidance: Use SOL 114 or insert the following DMAP alter:
alter 818,818
6733
P-Elements - TEMP(LOAD), PVAL,ADAPT - Wrong Answers
If thermal loads are applied to p-elements and the PVAL entry (referenced by
the ADAPT entry) defines the polynomial order to be 1, then the solution may
converge to wrong results. Wrong results definitely occur for models with only
one element.
Avoidance: Set POLYi field on the PVAL entry to 3 or more.
6738
rmance
69
Superelement Analysis - SEMA - Poor Perfo
If the residual structure of a large superelement model contains a relatively

large percentage of the total grid points, then the total run time may be
significantly larger then the same model without superelements. For example, in
one client's superelement model with over 100,000 grid points in the residual
structure with 16 superelements (each with about 1500 grid points) the total
run time increased by a factor of 7. The increased time required was due to
the SEMA (superelement assembly) module. SEMA is intended to work on a
collector superelement (or residual structure) that is much smaller than the
total model size.
Avoidance: Try to keep the residual structure and collector superelement size
to less than 10 percent of the model. The smaller these components are, the
more efficien
6744
70.5
GMA - User Fatal Message 5423
Optimization/Design Sensitivity - MTRXIN,
The message "USER FATAL MESSAGE 5423" may occur in the MTRXIN module when an
attempt is made to read M2PP, B2PP and K2PP matrices a second time. This error
occurs in optimization analyses with K2PP, B2PP and TF inputs. This error was
fixed in Version 69.0.2 and 69.1 but occurred in Version 70. The error is
fixed in Version 70.5.
Avoidance:
Use the following DMAP to skip MTRXIN for subsequent times:

COMPILE GMA SOUIN=MSCSOU NOREF NOLIST $
ALTER 2 $
TYPE DB,ZUZR01,ZUZR02,ZUZR03 $
TYPE PARM,,I,N,NOM2PP,NOB2PP,NOK2PP $
ALTER 9,9 $
PARAML ZUZR02//'PRESENCE'////S,N,NOZUZ2 $
PARAML ZUZR03//'PRESENCE'////S,N,NOZUZ3 $
IF ( NOZUZ2<0 AND NOZUZ3<0 ) THEN $
MTRXIN CASES,MATPOOL,EQDYN,,TFPOOL/K2PP,M2PP,B2PP/LUSETD/
NOK2PP/NOM2PP/NOB2PP $
COPY
M2PP/ZUZR0
6745
69
P-Elements - GMBC, SPCADD - Wrong Answers
GMBC entries referenced by SPCADD bulk data entries are ignored.

Avoidance: Other than not using the SPCADD entry, there is no avoidance.
6753
GL
- Wrong Answers
Nonlinear Static - RESTART, PARAM, NMLOOP
If PARAM,NMLOOP is used to restart from SOL 106 (nonlinear statics) into a

linear solution, the data recovery output is performed using linear element
properties. Ths design causes displacements and element results to be
incorrect. However, the solution is performed using the nonlinear equilibrium
position (allowing EIGENVALUES to be correct). Only data recovery is in error,
hence displacements and element results are wrong. This design does not affect
a restart from a nonlinear run to a nonlinear run.
Avoidance: There is no reason to perform a RESTART from solution 106 to 101,
perform the desired data recovery in solution 106.
6755
69
ARAM,INREL - Wrong Answers
Documentation - Inertia Relief, SUPORT, P
In addition to a SUPORT entry, PARAM,INREL,-1 is required to perform inertia

relief in solution 101. This requirement is not documented under the
description of the SUPORT entry. It is documented under the SUPORT entry
description the SUPORT entry "does not perform the same function as a
constraint". In fact if PARAM,INREL,-1 is not included the SUPORT entry will
act like a constraint.
6759
r
69
SSSALTER Library - RFLAG,LMT - Fatal Erro
The SSSALTER Library files RFLAG and LMT will cause fatal errors when used with
SOLS 107, 108, and 109 if the stiffness matrix is singular.
There are two possible avoidances:
1. Modify the dmap alter with the following change:
Change the DMAP Alter from:
GETLLL=(STATICS OR NORSET>-1 OR NO3SET>-1 OR
(MODACC>=0 AND (SOLTYP='MODAL' OR APP='REIG'))) $
to:
GETLLL=(STATICS OR NORSET>-1 OR
(MODACC>=0 AND (SOLTYP='MODAL' OR APP='REIG'))) $
Removing the NO3SET. This matrix does not need to be decomposed for direct
analysis. The alter causes a branch over this unneeded operation.
2. Modify the model by adding enough SUPORT entries to stabilize KLL. These
SUPORTs will not modify the answers.
6761
69
ot Check if FEFACE Exists
P-Elements - GMLOAD - GMLOAD Entry Does N
The GMLOAD entry allows the following options in the entity field:
FEEDGE, GMCURVE, FEFACE, and GMSURF
If there are no FEFACE, GMCURV or FEFACE entries in the model, no error message
is issued, and the user is not given a clear idea of what is wrong.
6768
69
F24D40 - Curve Projection Limits
Documentation - Reference Manual, CURV, R
The description for the CURV module processing in the Reference Manual under
RF24D40 (page 15.8-19) Remark 4.a. states:
- If |n.i|>= 0.4 the projections of the y-axis on the surface of the element is
taken as the reference axis.
This statement should read:
- If |n.i| > 0.4 the projections of the y axis....
6772
69
L - Wrong Answers
P-Elements - TEMP(LOAD), CHEXA,PSOLID,PVA
A skewed p-hexa element with p=1 (on the PVAL entry) produces incorrect results
with thermal loading. If the p-hexa is not skewed or if p>1, the answers are
correct. Incorrect results may also occur if the p-element is next to an
h-element, since the p-element will be reduced to p=1 on that face to be
compatible with the h-element.
Avoidance: Turn off the bubble functions using the PSOLID entry (5th field) or
set p>1 on the PVAL entry.
6785
70.5
Buckling Analysis - EIGRL - SFM 5401
In a buckling analysis, if only the V1 and ND fields are specified on the EIGRL
entry, then the job may fail with the following error messages:
SYSTEM FATAL MESSAGE 5401, LANCZOS METHOD IS UNABLE TO FIND ALL EIGENVALUES IN
RANGE.
A symptom of this error is the continuing shifting of Lanczos when ND roots
have been found.
Avoidance 1: Specify the V2 field in addition to the V1 and ND fields.

Setting SHFSCL on the EIGRL entry near the absolute value of the lowest
expected root may also avoid the error and improve efficiency. Another
alternative is to use the SINV method if only a few roots are desired (which is
true for most buckling analysis).
Avoidance 2 (preferred over Avoidance 1): A new alter has been added to the
sssalter library that can be used with Version 69.0.2. (
6786
69
ETi - SFM 2198 and 2199
Optimization/Design Sensitivity - FBS, QS
If QSETi entries are specified in solution 200 for the purposes of dynamic
reduction and the a-set contains only the q-set degrees of freedom and there is
also a static subcase, then the run will fail with SYSTEM FATAL MESSAGE 2198
and 2199. (Version 68.2 only)
Avoidance: There are three possible avoidances:
1. Remove the q-set and the dynamic reduction requests and, if not already
done so, then replace with a
Lanczos eigenvalue analysis (see EIGRL
entry).
2. Specify ASETi entries for one or more physical degrees of freedom.
3. Insert the following DMAP alter:
compile fea noref nolist
alter 'FBS'(,-1),'FBS' $
DBSTATUS UL,USET,LLL//S,N,NOUL/S,N,NOUSET/S,N,NOLLL $
IF ( NOUL=-1 AND NOLLL>0 ) FBS
LLL,,PL/UL $
6788
2001
M 982, Missing Output
Transient Response Analysis - XYPLOT - UW
If an xyplot is requested for the velocity of a grid point which does not exist
and there is no VELO=
request in the CASE control for printed data, then no displacement, velocity,
or acceleration data will be printed or plotted and the following message will
be issued:
*** USER WARNING MESSAGE 982. FORMAT OF OUGV1
CODE = 165
INCOMPATIBLE WITH SDR3 DESIGN.
Avoidance: Review the output requests versus the grid and element ids in the
model, insuring that all requests reference proper ids. Another avoidance is
to add a VELO(PLOT)=ALL command to the case control. This command will produce
very large files on large size models, however.
6789
ect Damping
Nonlinear Transient Analysis - PARAM,LGDISP, PARAM,G - Incorr
There is a problem in the way element damping is implemented in nonlinear

transient analysis (SOL 99 and 129). The implementation can result in answers
with apparently very wrong damping when large displacement effects are
requested with PARAM LGDISP. These solution sequences create a "B" damping
matrix, from which damping forces are computed. This matrix is updated
whenever the stiffness is updated. The problem is that many structures have
stiffness ratios (and hence damping ratios) in perpendicular directions that
are orders of magnitude different. A tiny misalignment of the damping can be

intolerable.
Avoidance: There is no avoidance. See also related error 7199.
6790
69
07, UFM MATGEN-4, Poor Message
Nonlinear Statics - MATGEN, SCE1 - SFM 30
In nonlinear static analysis, SOLs 66 and 106, if the model has no l-set, a
poor message is issued.
In SOL 66, SFM 3007 is issued for module SCE1 at line 858 in Version 68. In
SOL 106, " USER FATAL MESSAGE MATGEN-4, ILLEGAL VALUE FOR PARAMETER 2 = -1" is
issued for module MATGEN at line 143 in Version 68.
Avoidance: Insert the following DMAP alter in SOL 106 to obtain the correct
message, UFM 4402.
compile nlstatic souin=mscsou noref nolist
$alter 117 $ V68
alter 119 $ V68.2
IF ( NOLSET=-1 ) CALL ERRPH2 //SUBDMAP/4402 $
6794
69
T,-1 - Missing Datablocks
Postprocessing - Heat Transfer, PARAM,POS
Executing solutions 153, heat transfer, or 159, nonlinear transient heat

transfer, with PARAM,POST,-1 does not produce the geometry data blocks GEOM1,
GEOM2 etc. in the OUTPUT2 file. This error only occurs in MSC/NASTRAN Version
68.2.
Avoidance: Apply the following alter:
compile super3 noref nolist
alter 217,217
alter 220,220
6795
69
Terminated Abnormally
Miscellaneous - SGI R8000 Only - Command
Jobs submitted with scr=yes on MSC/NASTRAN Version 68.2 on the SGI R8000
computer may in rare cases not write the "END OF JOB" to the f06 file but
instead issue a "Command Terminated Abnormally" message in the log file. In the
single case experienced the job otherwise completed processing and the error
was easily avoided by running with scr=no.
6797
70
s not support READONLY
DBC/TRANS/ACCESS - V6 & Later for IBM doe
Version 6 and later releases for MSC/ACCESS for IBM Mainframes running MVS/XA
does not allow for current access of XDB databases via the READONLY request.
As per the information from the NASTRAN Product Manager, there will be no more
versions of MSC/NASTRAN for the IBM MVS platforms so this error will not be
corrected.
This problem is considered fixed in Version 70 because there will be no more
IBM MVS/XA releases.
6799
69
t available in V68
Optimization/Design Sensitivity - DOM2 no
Prior to Version 68, design variable values could be passed into the DOM2
module and an EPT datablock based on the values and the property to design
variable relations would be produced. This capability was
removed from DOM2. The functionality has been re-instated in the DOM9 module
in Version 69.
6800
UFM 2071
2001
Transient Analysis - DPD - Poor Message,
In solution 109, if an initial condition, ic, is specified without the

presence of a DLOAD command in the case control, the following fatal message is
produced:
USER FATAL MESSAGE 2071 MODULE = DPD
DYNAMIC LOAD SET
1 REFERENCES UNDEFINED TABLE
This message occurred despite the fact that no DLOAD was selected, and the
TLOADi,1 entry in the bulk data was a TLOAD2, which can not reference a table.
Avoidance: Input a DLOAD command in the case control which references a TLOADi
entry which in turn
references a DAREA entry with a zero coefficient.
In general, all dynamic load input must be complete, even when it can not be
selected. For example, if there is incomplete frequency response load data in
a transient analysis input file, they will cause fatal errors
6801
70
SUPER3 - UFM 9058
In solution 200, if a DRESP1 entry is provided for an analysis type that is not
present in a case control ANALYSIS command (e.g. RTYPE = DISP, but there is no
STATICS of SAERO subcase) then "USER FATAL MESSAGE 9058 (SUPER3) THE SOLUTION
FOR THE RESIDUAL STRUCTURE DOES NOT EXIST" may occur.
Avoidance: Do not use unreferenced DRESP1 entries.
6802
o Message
69
Optimization/Sensitivity - DOM9 - Quits N
If an optimization problem has a near mechanism and param,bailout is set to

force it through static decomposition without a fatal message, then the job may
fail on DEC ALPHA systems in the DOM9 module with no message. Other machines
will produce meaningless answers.
6808
2001
nce Manual - Incorrect Equations
Documentation - CBEND, MSC/NASTRAN Refere
There are typographical errors in equation 7 of section 5.2.3 of the Reference

Manual. R-sub-R should be R-sub-B and in the integral for Z, "R" in the
expression R/R-sub-b should be "r".
Avoidance: The correct equations may be found in the old MSC/NASTRAN User's
Manual
6809
70
Miscellaneous - XSORT - UFM 1126 (GNFIST)
If the input data contains two "BEGIN BULK" entries, then the following
misleading message may be produced:

DMAP MODULE XSORT IS ATTEMPTING TO OUTPUT DATABLOCK 201 NAME = IBULK, WHICH
ALREADY EXISTS.
USER ACTION: DELETE THE DATABLOCK, OR USE FILE IBULK =OVRWRT
6810
69
- UFM 6545 (DOPR3)
The message "USER FATAL MESSAGE 6545 A DESGLB= XXX COMMAND APPEARS AT THE
SUBCASE LEVEL" is issued in error when the DESGLB command appears above the
subcase level and there is more than one "super" discipline in case control.
There are three super disciplines in MSC/NASTRAN design sensitivity and
optimization: Frequency (ANALYSIS=MFREQ or DFREQ), Transient (ANALYSIS=MTRAN)
and everything else (ANALYSIS=STATICS,MODES,BUCK,FLUTTER or SAERO).
Avoidance: Remove the DESGLB command and invoke the constraint with a DESSUB
command from the first subcase.
This will force the evaluation of the constraint at the subcase level even
though there are no subcase
associated responses involved in the constraint evaluation.
6812
02
69
Eigenvalue Analysis - READ, EIGR - UWM 54
In normal modes or buckling analyses which are defined by the EIGR Bulk Data
entry, if the reduced stiffness matrix is less than 0.0001% dense, and the
stiffness is not null, then UWM 5402 is issued and no eigenvalue analysis is
performed.
Avoidance: Use the EIGRL Bulk Data entry or insert the following DMAP alter:
compile moders souin=mscsou noref nolist
alter 100 $ Version 68 and 68.2
modtrl kxx///////1 $ set density to .0001
6813
de - UFM 5423
70.5
Restarts - SOL 144, TRIM, Aero User's Gui
The RESTART example ha144a_rst in Chapter 4 of the Aeroelastic Analysis User's

Guide deletes two of the three subcases from ha144a.dat, the cold start run.
This causes the RESTART job to fail when it tries to use the UOOX matrix from
the cold start with the new GOAT matrix.
Avoidance: Add a dummy FORCE Bulk Data entry to the Bulk Data section and it
need not be referenced by the LOAD command. In general lines should not be
deleted from the Case Control, subcases and output requests should be added.
6814
p-Elements - GMCURV, GMSURF - Poor Answers
When p-elements are connected to h-elements the polynomial order at the

interface should be p=1.
If GMCURV or GMSURF data is used along the interface surface the code ignores
the different connections and allows the polynomial order to grow. Severe
stress concentrations will be calculated at the connected points.
Avoidance: Since the interfaces must be straight there is no need for

geometry, remove the gmcurv or gmsurf from the interface.
6815
68.2
OST - Missing Results for PATRAN
If a SOL 200 analysis is run with PARAM,POST,-1, only the last design cycle
results are available for postprocessing in MSC/PATRAN using the output2 file,
and there is no any model information.
Avoidance: The error has been fixed in MSC/NASTRAN Version 68.2, the user
should switch to this version.
6821
69
ncountered, Traceback
Acoustic Analysis - ACMODL, ACMG - Trap E
In acoustic/fluid analysis, if DIFF is used on the ACMODL entry and some fluid
grids on the fluid/structure interface are not captured by the FSTOL tolarance,
then the job may fail without any message being written to the f06 file. The
log file may indicate a traceback as follows:
Trap encountered, Traceback:
Offset
Offset
Offset
Offset
17dc
1f0
140
0
in
in
in
in
procedure
procedure
procedure
procedure
acmg_
xsem05_
mainal
start
Avoidance: Set a value for FSTOL that captures all of the fluid grids at the
fluid/structure interface.
6823
IFP - SFM 3003
2001
Optimization/Design Sensitivity - PCOMP,
The auxiliary model technique of shape optimization (solution 200) does not
work when PCOMP entries are present. The following message is received:
SYSTEM FATAL
MESSAGE 3003 MODULE = IFP
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK IEPTX
202) IN SUBROUTINE IFP6
(FILE
Avoidance: The avoidance is to use one of the other three shape optimization
methods.
6826
69
M 6137, UFM 3005
Inertia Relief - PARAM,INREL/ SUPORT - UF
If the inertia relief feature is used in SOL 101, and the model does not
contain a mass matrix, then the job will fail with the following unclear
messages:
*** USER FATAL MESSAGE 6137 (UDSSDD)
*** USER FATAL
MESSAGE 3005 MODULE = SOLVE
In SOL 24, the job will terminate without any messages. A symptom of this
error is printing of the parameters after echo of the input file.
Avoidance: Include the appropriate mass required for inertia relief.

6829
69
ob Not Submitted
Miscellaneous - Network Job Submittal - J
If the current working directory is auto-mounted, and there is a delay in

starting execution of an MSC/NASTRAN or MSC/EMAS job (e.g., submitting job with
aft= or que=), then there is a chance that the job will not be submitted.
Depending on your network setup, you may receive the following message:
/tmp_mnt/net/<node>/<somedir> : not found
from the daemon.
This error is encountered when it attempts to change the working directory to
the current working directory as determined by the nast682 or emas32 script.
The error can occur on any system where the "pwd" command does not return the
canonical working directory. For example,
% cd /net/<node>/<somedir>
% pwd
/tmp_mnt/net/<node>/<somedir>
If sufficient time passes, the system will release the mount of
'/tmp_mnt/net/<no
6831
Message
69
Installation - Remote Installation - Poor
If the "Remote Installation" option of the script is chosen, AND the user's
shell on the remote system is csh AND the remote system is not properly
configured so that test(1) is in the PATH during an rsh command,
the installation will fail indicating the CD or media could not be found on the
remote system.
Avoidance: The installation cannot use the specified remote system until the
PATH is corrected. The script has been modified to explicitly test for this
user error so that a meaningful message is output.
6833
2001
Examples Result in UFM
The example in Section 2.1 of the DMAP Module Dictionary has several errors in
it. The following lines of the input file cause fatal errors if used as is:
QVOL 123
1.E+2 1
GRID 5
0
36O.O
MAT1 1
30.0E3
*MAT1
16.99235344
CORD2R, 3,
0, 0.,0.,
+CORD 1.
0.
1.
THRU
240.0
9
0.0
0
3456
1.
6.5-6 5.37+2 +MAT1
11.814744801
1.E04
0., 0., 0., 1., +CORD1
Avoidance: Change the above input to:

QVOL
GRID
123
5
1.E+2
0
360.0
1
240.0
THRU
0.0
9
0
3456
MAT1 1
30.0E3
1.
6.5-6 5.37+2
*MAT1 16.99235344
11.814744801
1.E04
CORD2R, 3,
0, 0.,0.,
0., 0., 0., 1., +CORD1
+CORD1 1.
0.
1.
6839
69
- Missing Documentation, Messages
+MAT1
Dynamic Analysis - FREQ, TSTEP, SDAMPING
By design intent, solutions 107 through 112 do not support changes of freq=,
tstep=, method=, cmethod=, sdamping commands in subcases. For example, if in
sol 111 there are two subcases, and each has a different freq= command, only
that in the first subcase will be honored. All similar commands in the second
and subsequent subcases will be ignored. The output for all subcases will be
for the frequency set selected in the first subcase. Note that solutions 108
and 111 do correctly support changes in the DLOAD command between subcases.
6849
rong Answers
69
Aeroelastic Response - PARAM,DDRMM,-1 - W
When a transient analysis is performed in SOL 146 with PARAM,DDRMM,-1 wrong

answers are produced.
Avoidance: Use PARAM,DDRMM,0 (i.e., the default), use SOL 76 or apply the
following DMAP avoidance for Version 68.2:
compile seaero nolist noref
alter 'call mfreqrs'
app1=app $
6850
69
PTEXIT,-4 - Output Overwritten
If "param,optexit,-4" is used in a design optimization run (SOL 200), then the

OUTPUT2 results for table DSCMCOL will be overwritten by the matrix DSCM2.
This error is due to assigning both the output2 and output4 files to the same
unit.
Avoidance: Insert the following dmap avoidance.
compile exitopt souin=mscsou nolist noref $
alter 20,21 $ v68.02
output4 dscm2,,,,//-1/12 $
output4 ,,,,,//-2/12 $
6853
70.5
OM - Infinite CPU Loop
If a zero hertz excitation frequency is specified in a run which has a

free-free model and is using modal frequency response to perform a random
analysis, the run may encounter an infinite loop. This problem appears to be
due to the zero frequency solution being a numeric infinity. If the same model
is used in a direct frequency response, the run will fail during the
decomposition due to the 0.0 hertz static solution being singular. In the
modal solution, a matrix decomposition is not performed (in the uncoupled
solution), therefore, a solution is obtained for the 0.0 hz excitation.
Avoidance: Do not request a 0.0 excitation frequency in a modal frequency
response analysis.
6854
SEQMR
Sequencer - PARAM,SUPER, SEQP - SFM 4276, EC 7777, Traceback
If a superelement model uses PARAM,SUPER,2 without PARAM,MPCX,sid (where sid is

the MPC set to be used), the run may fail with no messages in the sequencer.
Avoidance: Include PARAM,MPCX in the run if PARAM,SUPER,2 is used.
6855
69
SSSALTERS - SEP1, lmt11.v682 - SFM 6357
In version 68.2, if the lagrange multiplier solution dependent sssalters

lmt*.v682 are used, then the job may fail with the following error messages:
SYSTEM FATAL MESSAGE 6357 - NO GRID POINTS DEFINED FOR SEP1
Avoidance: Use the solution-independent lagrange multiplier sssalter
rflag.v682 instead of the lmt*.v682.
The rflag.v682 alter combines the function of all the lmt*.v682 alters.
6859
69
DMAP - MODTRL, PARTN - Infinte CPU Loop
If an element of a matrix is given an index for a row number larger than the
number of rows in the matrix, as defined by the matrix trailer, and partn
operates on this matrix, partn will go into an endless loop.
The MTRXIN and MODTRL modules, and perhaps inputt4, can generate such matrices
when used injudiciously.
Avoidance: One way to avoid this error is to first put the matrix through the
ADD module. The module will throw away all terms beyond the boundaries of the
matrix as defined by the matrix trailer.
6866
69
Miscellaneous - Cray J90, T90 - UFM 4311
If you are running MSC/NASTRAN V68.2 or MSC/EMAS 3.2 on a Cray T90 or J90 which
has more than 16 CPUs, then your job may fail with the following error
messages:
USER FATAL MESSAGE 4311 (XSEM)
TIME EXPIRED PRIOR TO LINK NS01, CALLING MODULE - 19 IFPL
Note that this error may occur even if you are not using more than one CPU as
long as the T90 or J90 has more than 16 CPUs. The error is due to one of the
timing kernels on the T90 and J90 returning an erroneous number.
Avoidance: A fix for this kernel error is available from Cray Research. Even
though this is not MSC's error, the error is marked as fixed in Version 69 to
remove it from the list.
6867
om .neu
69
Plotting - PLOTPS/NEUTRL - No .ps file fr
According to the documentation, the plotps utility should be able to generate a

postscript formatted plot from the MSC/NASTRAN plot file (.plt) or a neutral
(.neu) format plot file. (The neutral file format is necessary for transferring
data between different machine types). However, when the neutrl utility
translates a plot (.plt) file into a neutral (.neu) format, the plotps utility
cannot translate the neutral file and fails with the following message "USER
WARNING MESSAGE (PLTFIL) No frames found in file." The plotps utility works
fine for translating standard plot (.plt) files.

Correction:
The error exists in the neutrl utility, which is provided in source form. In
subroutine RDBIN, change line
240 from:
ibyte = 0
to
ibyte = 1
Note: A neutral (.neu) plot file i
6868
69
7777, Command Terminated Abnormally
Data Recovery - CBAR, SDR2 - SFM 4276, EC
Extremely small stresses for bar elements may lead to extremely large margin of
safety output. These large numbers may cause MSC/NASTRAN to abort in the SDR2
module. This error has been observed on the DEC ALPHA OSF/1 and the HP/9000
systems. The DEC OSF/1 issues a "command terminated abnormally" message in the
log file, while the HP/9000 issued a "SYSTEM FATAL MESSAGE 4276, ERROR CODE
7777" followed by a traceback in the log file. The traceback in the log file
indicates that the job was in the "numcvt" routine at the time of failure.
Avoidance: The error may be avoided by not setting PARAM,POST,0 for MSC/XL
data recovery. The error may also be avoided by removing the stress limits on
the MATi entries which results in the margins of safety being calculated.
6876
ssing
69
Matrix Methods - ADD5 - Inefficient Proce
NO EXTERNAL ERROR REPORT NECESSARY

If the scaling factor (for example, alpha) for any matrix in the ADD5 statement
is zero and there are additional matrices input to the module, the module will
scale each term of the associated matrix by 0.0 and add it to the additional
matrices.
Avoidance: No avoidance is necessary as this error is simply an efficiency
issue and wrong answers are not produced. DMAP may be used to check if any
scaling factors are 0.0 and the associated matrices may be excluded from the
addition.
6877
69
Mislabeled and/or Extraneous Output
Composites - Stress and Failure Indices -
In SOL 106, composite stress and failure index output is not labeled with the
load step as is found in other nonlinear output. Thus, PATRAN is not able to
distinguish composite output at different load steps.
In addition, in any solution that supports composite output, even if no failure
index output is requested, the header labels for failure index output are
always printed.
6879
70
ncorrect Output.
Acoustic Analysis - DISP, ACCE - Extra, I
If a fluid structure analysis is performed and accelerations are requested for

structural points and displacements are requested for the fluid points,
additional (incorrect) output will occur beyond the requested fluid point
output. Various machines may behave slightly differently. Some machines may
fail with the message "SYSTEM FATAL MESSAGE 4276, ERROR CODE 7777" indicating a
numeric overflow, other machines may output "NaNQ" or "**********" indicating a
numeric overflow.
Avoidance: Do not request structural accelerations in the same run requesting
fluid displacements. Perform a restart and keep the requests separate.
6880
69
DISP - SFM 4276, EC 7777
Differential Stiffness - QUAD4, PARAM,LG
Nonlinear analysis with QUAD4 elements and PARAM,LGDISP or buckling analysis

may fail in MSC/NASTRAN Version 68 on long word machines such as CRAY and NEC.
The run may issue SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777 indicating a
numeric overflow. Other messages may be written to the log file.
Avoidance: The error can be avoided by setting SYSTEM(170)=1 which select the
old quad4 differential stiffness formulation.
6881
roperties
70.5
Miscellaneous - TA1 - UFM 2010, Missing P
If a model has a large number of property entries and insufficient memory is

allocated, the program may issue USER FATAL MESSAGE 2010 stating that
properties which are in the input file do not exist. This occurs in DMAP module
TA1.
Avoidance: Increase the amount of memory for the run or increase the BUFFSIZE
on the NASTRAN statement.
6882
69
cient Disk Space, Excessive Output
Miscellaneous - SFM 4276, EC 923, Insuffi
NO EXTERNAL ERROR REPORT UNTIL I GET A DECK AND A BETTER DESCRIPTION AS TO WHEN
THIS HAPPENS.
If the files used by an MSC/NASTRAN run exceed the available space on a disk,
the program will provide SFM 4276 EC 923, indicating that system resources were
insufficient. However, the message is followed by a "core-dump" which will be
several thousand lines long. This additional output has no meaning to the user.
6883
Wrong Answers
69
Elements - HEXA(8), TEMP(LOAD), PSOLID -
If an eight node HEXA uses full 27 point integration (IN=3 on the PSOLID
entry), incorrect thermal loads are computed resulting in wrong answers.
Avoidance: The avoidance is to use the default integration method.
6887
Wrong Answers
69
Frequency Response Analysis - PARALLEL -
MSC/NASTRAN Version 68 may produce wrong answers for frequency response

analysis whenever PARALLEL=n is selected, where n is greater than 0.
Avoidance: The error only affects parallel sparse complex decomposition.
Parallel may be selected for other operations while being deselected for this
operation by:
instead of parallel=1, the workaround is parallel=262145

6888
69
rror in Scaling of Results
SSSALTER - mfreqa.v68 and mfreqa.v682 - E
In the sssalter mfreqea.v68 and mfreqea.v682 the scaled results of the modal
contributions are incorrectly scaled. Only as many modal contributions as there
are excitation frequencies are scaled and the others are not printed.
Resolution/Avoidance:
Change the following line :
mpyad onec,totalt,/scalit $
to be
mpyad oner,totalt,/scalit $
In the alter for V68.2, also change the following line:
mpyad kinetc,onec,/totalk/1 $
to be:
mpyad kinetc,oner,/totalk/1 $
6893
ge, Traceback
Complex Eigenvalues, Matrix Methods - CEAD, UDCOMP - No Messa
If sparse unsymmetric decomp spills the run may go into an infinite cpu loop or
fail with the following traceback being issued to the log file but no other
message:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0x00000010
0x00000010
0x00000164
0x000031dc
0x00000440
0x000000e8
0x00000120
0x00000e88
0x00000c24
0x0000006c
0x00000994
in
in
in
in
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
txuycd_
udspcd_
udsncd_
udsfa_
udcomp_
factru_
classd_
clasdd_
cead_
xsem11_
mainal
Avoidance: Increase memory to avoid spill. In Version 70.7 the pivot

threshold has been changed from 1.e-6 to 1.e-10 to make this error less likely.
Furt
6894
NT 3.1
70
Miscellaneous - No Output - Intel Windows
During testing of MSC/NASTRAN Version 68.2 some jobs produced no output on the
Windows NT 3.51 system. The error could not be debugged because when the
command prompt window was closed and re-opened the error could not be
reproduced. Thus, this report is being written to assist users who possibly
encounter the same problem.
6902
682
69
SSSALTER - Possible error using alter2g.v
If the DMAP alters for coupled analysis are used with the OUTPUT2 (MATPOOL)
option and a component has no damping matrix, the component matrices may not be
stored properly on the database.
Avoidance: In the alter, change NOM2GG to NOB2GG in the following DMAP
statement
mtrxin ,,baap,EQEXINS,SILS,/baaext,,/LUSETS/
S,N,NOM2GG///1 $
6903
g Answers
69
p-Elements - FEEDGE, GMLOAD, CORDi - Wron
If a GMLOAD is applied to an FEEDGE or GMCURV which have grids with

displacement coordinate systems other than the Basic coordinate system, the
loads are not properly applied.
Avoidance: Set the grids' displacement coordinate system to the Basic
coordinate system.
6904
69
- Wrong Answers
Nonlinear Analysis - MATS1, QUAD4, TRIA3
There are two errors in element force output for nonlinear QUAD4 and TRIA3
elements. The first error results in over-estimated force components. This
error exist in Version 68 systems only. This error occurs when geometric
nonlinear (LGDISP=1) is turned on and the element is in the nonlinear material
portion of the stress-strain curve (MATS1). Forces may be over-estimated by
more than 40%. The second error results in under-estimated force components,
on the order of 4%, when param,lgdisp is the default, -1. This day one error
is directly linked to the default value of param,nlayers,4.
Avoidance: There is no avoidance for the over-estimated element forces when
param,lgdisp is 1. The under-estimated element force error may be reduced to
.7% by setting param,nlayers to 12.
6910
70.5
l Unit Number for INPUTT4 -11
Documentation - OUTPUT4, INPUTT4 - Illega
If the sparse option is used to write a matrix using OUTPUT4 (IUNIT<0), then
the program will fail when reading the matrix using INPUTT4 if the sparse input
option is used (IUNIT<0).
Avoidance: Do not use the sparse option when reading or outputting a matrix
with inputt4 or output4. Use a positive value for IUNIT. .
6913
70.5.2
ata Recovery for External S.E.
Superelements - Can Not Perform Dynamic D
Data recovery is not supported for external superelements in dynamic solution

sequences.
Avoidance: There is no avoidance. Version 70.5.2 has been enhanced to provide

this support, please see PARAM,EXTDR.
6914
ot found
68.2.3
Installation - LANG - awk: UNIX command n
MSC/NASTRAN Version 68.2 may get the following message, "awk: UNIX command not
found", or some other UNIX level fatal message on SGI machines outside the US.
Non US language AIX machines are unable to understand the 'mem' command line
parameter. Other machines may exhibit different problems. The problems are
all caused by the fact that the LANG environmental variable is set to null in
the Version 68.2 NASTRAN script and not explicitly to 'C'.
Avoidance: All non US Language machines should change the MSC/NASTRAN script to
specify C explicitly:
# Set the "C" locale
LANG="C"; export LANG
This error is corrected in the Version 68.2.3 R2 CD.
6916
ase Output
69
Acoustic Analysis - HEXAPR - Incorrect Ph
The "COMPLEX ACCELERATION VELOCITY AND PRESSURE LEVEL" output is incorrect for
models that include damping. "REAL/IMAGINARY" output will always indicate a
zero value for the imaginary part of the acceleration and pressure output and
the real part of the velocity output. The nonzero part indicates the
magnitude. Likewise "MAGNITUDE/PHASE" output gives a correct magnitude but an
incorrect phase angle. An example of the incorrect output is shown below.
C O M P L E X A C C E L E R A T I O N S
E S S U R E L E V E L S
V E L O C I T I E S
A N D
P R
(REAL/IMAGINARY)
EL-TYPE
X-ACCELERATION Y-ACCELERATION Z-ACCELERATION
Y-VELOCITY
Z-VELOCITY PRES(DB)
HEXPR
-1.215000E-09
3.504862E+03
6921
69
timates, Poor Performance
X-VELOCITY
-1.262103E-09
Matrix Methods - MPYAD - Negative Time Es
It is possible to get a negative time estimate for MPYAD. This error may lead
to poor method selection and thus poor performance.
6928
69
- Wrong Answers
In Versions 68, weight and volume cannot both be selected as design responses
in the same solution 200
job. The problem will run to completion but one of these responses will have
zero value (i.e., it will be ignored in the design process). This leads to
incorrect answers.
The avoidance is to either:
1.) Use only weight or only volume in the design model
2.) Include the following DMAP alter (version 68, 68.2):

compile desinit souin=mscsou nolist noref
alter 66
wgtvol = 3 $
endalter
6932
2001
, ELTPRT - UFM 5165, SFM 3002
Optimization/Design Sensitivity - PACABS
If the B field of the PACABS (acoustic absorber element) data entry is

specified as a design variable in an optimization analysis, then the execution
will result in one of the following fatal messages:
USER FATAL MESSAGE 5165 (DSVG1D-1)
UNDEFINED INPUT FILE = 106, NAME = (NONE) ,
DSVG1 IS TERMINATED.
ERROR CODE = -6, MODULE
or
SYSTEM FATAL MESSAGE 3001 (DSVG1)
Avoidance: Use the following alter for 68.2.3:
compile pslgdv list noref souin=mscsou
alter 239, 239
IF ( DODFREQ>0 OR DOMFREQ>0 OR DOMTRAN>0 ) EMG,
EST,CSTMS,MPTS,DIT,,,,,,,GPSNTS,EQEXINS,SILS/
kelmx,kdictx,,,BELM,BDICT//0/s,n,nobgg $
In addition to the above error, optimization of the PACABS properties with the
objective to minimize weight fails at module ELTPRT in RESPSEN with the
following error message:
6933
Wrong Answers
69
Optimization/Design Sensitivity - PMIN -
If the user specifies a value of PMIN that is less than -0.99e35, the value
could potentially be incorrectly reset to 1.0e-20. This will happen for I12 on
a PBAR or PBEAM and for orientation on the PCOMP entry.
Avoidance: Specify PMIN values that are greater than -.99e35
6934
69
- Incorrect UFM 7618
When USER FATAL MESSAGE 7168 is encountered, the DVPREL2 ID referenced is in

error.
USER FATAL MESSAGE 7168 (DOPR1Z)
EQID XXX REFERENCED ON DVPREL2 YYY IS NOT PRESENT ON A DEQATN ENTRY.
Avoidance: A nonexistent EQID has been referenced on a DVPREL2 entry. The
burden is on the user to determine which DVPREL2 makes the incorrect reference.
6936
t Exist
69
Documentation - umsec6.doc - File Does No
The "readme" file in the nast68/doc directory states that the directory
contains the file UMSEC6.DOC which includes a list of MSC/NASTRAN diagnostic
messages. This file is no longer included with the delivery. The MSC/NASTRAN
online encyclopedia, delivered with all Version 68 systems, contains this

information (and much more) in an easily accessable format. Thus the online
encyclopedia is a far superior method for accessing information. The readme
file will be updated for Version 69.
6937
69
DMAP - COMPILE - UFM
Multiple COMPILE statements for the same subdmap may result in a user fatal
message. For example the following DMAPs should be equivalent but the first
may lead to a UFM:
COMPILE A
ALTER 1
COMPILE B
ALTER 2
COMPILE A
ALTER 3
COMPILE A
ALTER 1
ALTER 3
COMPILE B
ALTER 2
Avoidance: Combine the alter so that a single COMPILE statement may be used
for the subdmap. Re-arranging the COMPILE statements such that the COMPILE
statements for each subdmap follow each other directly should also avoid the
problem.
6939
69
US - SFM 4276 EC 7777
Nonlinear Analysis - PARAM,NMLOOP, DBSTAT
Nonlinear analysis jobs with PARAM,NMLOOP may fail on the DEC ALPHA OSF/1
Version of MSC/NASTRAN.
compile nlstatic noref nolist
$alter '/s,n,fact','' $ V68.2
alter 486,486
PARAML ESTNL//'DTI'/0/6/S,N,FACT $ LOAD FACTOR
6943
69
TEMP(INIT) - UIM 9052, SFM 3001
Optimization/Design Sensitivity - SHPCAS,
Using TEMPERATURE(INITIAL) in a solution 200 shape optimization run with an

auxiliary model results in the messages:
USER INFORMATION MESSAGE 9052 (FEA) - STATIC ANALYSIS COMPLETED. DESIGN
CYCLE NUMBER=
1
SYSTEM FATAL
MESSAGE 3001 MODULE = SHPCAS
THE INPUT DATA BLOCK NAMED YGBNDR AT POSITION
2 DOES NOT EXIST.
Avoidance:
Specify TREF on the MAT1 entry or apply the following DMAP alter:
compile bndshp nolist noref souin=mscsou

alter 'auxmid'(2)
dbview ugx=ug (where mtemp=*) $
alter 'partn','partn'
PARTN UGx,,AXMVEC/UGA,,,/1 $
alter 'equivx','equivx'
EQUIVX UGx/UGA/ALWAYS $
6947
69
Miscellaneous - INPUTT4 - SFM 4276 EC 777
7
When reading a double-precision datablock on an SGI R8000 computer using
INPUTT4, the run will fatal in the INPUTT4 module with the following message in
the .f06 file:
RECEIVED SIGNAL 0, ABORTING ...
BIOMSG: ERROR 7777 HAS OCCURRED IN ROUTINE RECOVR
FILE INDEX (FILEX) =
0
SYSTEM FATAL ERROR 4276.RECOVR
ERROR CODE 7777
Avoidance: An avoidance is to have the datablock output in the neutral format

(OUTPUT4 in the ASCII format) and edit the datablock header to change the data
type (the 4th word in record 1) from 2 (double precision) to 1 (single
precision).
6949
69
Description format is incomplete.
Documentation - RS/6000 IOI DBset ASSIGN
In Section 4.3 of the MSC/NASTRAN Installation And Operating Instructions, the

description of the DBset ASSIGN statement is incomplete. The reference to the
"action" options is not specified. Please see the MSC/NASTRAN Quick Reference
Guide for a complete description of the ASSIGN statement.
6951
Null Load
70.5
Nonlinear Analysis - P2G - Wrong Answers,
If P2G is used to import loads onto the residual structure (with or without
superelements) in SOL 106, their contribution to the overall loading is
ignored.
compile nlstatic
alter 'ssg1
'
MTRXIN CASESx2,MATPOOLS,EQEXINS,,/
P2J,,/LUSETS/S,N,NOP2J///2 $
ADD
Pgres,P2J/Pgres1/CP1/CP2 $
equivx pgres1/pgres/-1 $
endalter
or use a LOADSET callout above the SUBCASE level and a CLOAD within each
residual subcase to include the P2G contribution as shown:
LOADSET = 10
P2G = ExtLds
SUBCASE 1
LOAD = 20
CLOAD = 30
BEGIN BULK
LSEQ, 10,9999,20
CLOAD,30,1.,1.,9999
6952
P-Elements/Superelements - GP4 - UFM 2101, SFM 3062
The output coordinate specification is not allowed for the FEEDGE or FEFACE
entries when an FEEDGE or FEFACE is specified on the superelement boundry. Do
not use global coordinates on superelement boundries in p-element substructures

else the following fatal message will be encountered:
*** USER FATAL MESSAGE 2101 (GP4)
GRID POINT 101000048 COMPONENT 1 ILLEGALLY DEFINED IN SETS
UB
6953
69
- Poor Message, SFM 7127
UM
The following message is misleading in that it should be a USER FATAL MESSAGE

and it does not indicate that the error is on a DRESP1 entry.
SYSTEM FATAL MESSAGE 7127 (DOPR3B)
AN ELEMENT WHICH REFERENCES PTYPE 52 20 PID
ANALYSIS MODEL.
6957
69
34 IS NOT DEFINED IN THE
Documentation - NOLIN2
Remark 4 under the MSC/NASTRAN Version 68 Quick Reference Guide description of

the NOLIN2 entry should state "GK-CK" not "CK-CK".
6960
69
SDR2 - SFM 4276, EC 3001, SWM 2092
Optimization/Design Sensitivity - SUBSEQ,
If zero values are used for the SUBSEQ command for a SUBCCOM subcase in a
solution 200 analysis the following messages will be encountered from the SDR2
Module:
SYSTEM WARNING MESSAGE 2092 MODULE = SDR2
SDR2 FINDS A SYMMETRY SEQUENCE LENGTH = X
AND AN INSUFFICIENT NUMBER OF VECTORS AVAILABLE = Y WHILE ATTEMPTING TO COMPUTE
STRESSES AND FORCES.
ALL FURTHER STRESS AND FORCE COMPUTATION TERMINATED.
ERROR CODE
3001 PID=
Avoidance: The avoidance is to not use 0.0 coefficients in a SUBSEQ request

when performing design sensitivity and optimization.
6963
ed Answers
69
Documentation - SUBCOM, SUBSEQ - Unexpect
The documentation for the SUBSEQ command is misleading. Unless it is read

carefully, the user might expect the first number to apply to the first SUBCASE
and so on. Actually, the way it is applied is that the last number is applied
to the most recent SUBCASE, the next to last number is applied to the SUBCASE
preceding it, and so on. If scaling factors are not included for all preceding
SUBCASEs, unexpected results may result.
Avoidance: Include scaling factors for all preceding SUBCASEs.
6964
69
Utilities - Intel Windows/NT Only
If the utilities are executed on the Intel Windows/NT Version 68.2 release of
MSC/NASTRAN without any argument the command line input format is not output to
the console. This command line description is instead output the FOR000 file.
The command line description is also documented in section 6 of Installation
and Operation Instructions.

6965
69
Miscellaneous - Include File Not Found
MSC/NASTRAN on Windows NT can be run one of two ways. One is via command line
and second is by clicking on an icon. If nastran is run via the second method
and the input data deck contains an include file, the include file will not be
found.
Avoidance: 1. Run nastran using the command line.
2. Define the environmental variable in the MSCN4NT1.INI file
specifying the location of the
data deck. This also requires the same environmental symbol be
included while specifying the
include file. This method is described in the section 4.1 of the
Installation and Operation
instructions.
3. Add a complete path name to the include file.
6966
69
FLUX, SET - Wrong Answers
Nonlinear Transient Heat Transfer - HBDY,
If a set definition is used for a FLUX request, then wrong (zero) values in
the radiation column of the
heat flow into HBDY elements may be produced. This error causes all results in
the radiation column to be incorrect. This error does not affect the
temperature results.
Avoidance: A FLUX=all request avoids the problem.
6968
r Starts
69
Miscellaneous - Bad File Names - Run Neve
When using MSC/NASTRAN in either Windows95 or Windows/NT, the program will fail
if any embedded blanks exist in either the filenames or directory names used.
Avoidance: Do not include any embedded blanks in file or directory names.
6969
69
ll on Windows NT Version 4.0
Installation - MSC/NASTRAN Will Not Insta
For Windows NT Version 4.0, which is the Windows 95 interface on top of Windows
NT 3.5, the installation of MSC/NASTRAN will not work. There is a problem with
the installation software (Installshield).
Avoidance:
6971
Do not upgrade your operating system to 4.0.

69
On one client model, RFORCE entries generated null loading vectors in

MSC/NASTRAN Version 68.2. Correct answers were produced in MSC/NASTRAN Version
68.0 and V68.1. This error results in incorrect results.
Avoidance: We have been unable to duplicate this problem on any other input
files. For the client input deck, setting METHOD to 2 on the RFORCE entry
resulted in the correct loads being generated. Our recommendation is whenever
you have an RFORCE in your input file, include a SUBCASE which applies the
RFORCE only and verify the OLOAD resultant is correct for that SUBCASE. If the
OLOAD resultant for that SUBCASE is null set method to two on the RFORCE entry
and please send the deck to MSC.
6972
69
Installation - MSCID - UFM 3060
The MSC Authorization program (an icon) has, on some configurations (usually
laptops with docking stations), shown a "0" for "MSC id". This is not correct.
If you get a "0" while using the authorization program during installation or
running from the icon, do not use this number to get an authorization code from
MSC.
To get the proper ID, run a MSC/NASTRAN job and the 3060 error message in the
.f06 file will contain the correct ID. Use the ID in the .f06 file when calling
MSC for an authorization code.
6976
ssage
69
Acoustic Analysis - EMA, PSOLID - Poor Me
When executing a fluid/structure analysis, if the FCTN field is not set to

FLUID on the PSOLID data entry for a fluid element the execution will fail with
the message:
SYSTEM FATAL ERROR 4276.BLDPK
ERROR CODE
211
Avoidance: Other than correcting the model, there is no avoidance.

6980
69
swers for HBDY Output
Heat Transfer Analysis - QVECT - Wrong An
The QVECT load defines thermal flux from a distant source into a face of a
CHBDYi boundary element. If a coordinate system(CE) for the thermal vector flux
is rotated with respect to the basic coordinate system, the data recovery for
the APPLIED LOAD under the HEAT FLOW INTO HBDY ELEMENTS is not correct.
However, the actual temperature results are correct. The actual loading can be
seen using the OLOAD=all output. There is no error if the coordinate system is
merely translated, not rotated, with respect to the basic coordinate system.
Avoidance: Ignore the incorrect output.
6981
69
RT, PARAM,SLOOPID - Wrong Answers
Nonlinear Transient Heat Transfer - RESTA
If PARAM,SLOOPID is specified for a nonlinear transient heat transfer (SOL 159)

analysis restarting from a steady state thermal analysis (SOL 153), the initial
temperature from the SOL 153 run is zero.
Avoidance: Use the following DMAP ALTER.(V68.2 ALTER)
$ DMAP alter to repair SLOOPID restart from sol 153
$ MSC/NASTRAN V68.2
$
compile nltcsh,souin=mscsou,nolist,noref
$
$ bypass the restart deletion of estnl in case that a
$ TEMPBC entry is added to the bulk with the sol 159 input
$
alter 39 $
type db zuzr01 $
dbview xestnl = estnl (where nloop=sloopid) $
copy xestnl/zuzr01 $
alter 281,281 $
alter 300,300 $
copy zuzr01/estnl $
$
$ save the sol 153 temperatures to database
$
alter 310 $ V68.2
equivx ulx/ulnt/noeset $
cend
6982
2005.0.2
olution Does Not Converge
Heat Transfer Analysis - PARAM,LGDISP - S
PARAM,LGDISP is intended only for the nonlinear structural analysis. However,

if it is used in heat transfer analysis (SOL 153 or 159) the solution will not
converge.
Avoidance: Delete the PARAM,LGDISP from any heat transfer analysis.
6984
69
DMAP - MALTER - UFM 806
If the input file for a restart run contains a DMAP alter using MALTER commands
and has no "compile" commands, the run will fail with User Fatal Message 806
stating that the MALTER statements were not found in the source files.
Avoidance: This error may be avoided by either:
1) Inserting ACQUIRE NDDL in the FMS section of the restart deck.
or
2) Inserting a COMPILE command for a subdmap in the deck.
6986
Convex
69
Dynamics - DPD, SEQP - Poor Efficiency on
Models which have been resequenced cause the DPD module to run up to 5 times
slower than models which have not been resequenced on MSC/NASTRAN Version 68.2
on the Convex. This also affects reading large numbers of FORCE bulk data
entries.
Avoidance: The combination of the sparse solver and the seqp module is almost
always more than the sparse solver without resequencing. Thus, sequencing
should be simply turned off. Remove resequencing by:
1. Remove any PARAM, NEWSEQ entry and replace it with PARAM,NEWSEQ,-1.
2. Remove any SEQGP entries which may be in the bulk data file.
This avoidance will not help the reading of the FORCE bulk data entries.
6990
rs
69
Acoustic Analysis - PARAM,G - Wrong Answe
If the structural damping (either PARAM,G or "ge" damping on the MATi entry) is
the only change in a restart to a fluid-structure acoustic analysis, the change
is ignored and the answers are incorrect, i.e., they remain the same as before
the change.
Avoidance: Execute the analysis as a cold start.
6991
nswers
69
Heat Transfer - CHBDYG, CTRIAX6 - Wrong A
Currently there is a design limitation using CHBDYG,REV to represent the higher

order CTRIAX6 element because only two grid points are allowed on the REV
option. Therefore, the weighting on the mid-side node is misrepresented if the
two node REV option is used.
Avoidance: Use CHBDYE to represent the CTRIAX6 element with midside nodes.
Please note that without the midside node, the CHBDYG,REV can be used.
Please note that the REV option G1,G2,G3
Where G1 and G2 are the edge grids and the G3 is the midpoint grid
6992
69
Wrong Answers for LOAD VECTOR
Heat Transfer Analysis - OLOAD, CTRIAX6 -
Applying a heat flux to the edge of the midside node of a CTRIAX6 element
results in wrong answers for the LOAD VECTOR output at the midpoint. This
error is only in the data recovery. The temperature results are not affected.
Avoidance: Ignore the OLOAD output for the midside node of the CTRIAX6 element
6994
2001
Miscellaneous - ASET1 - UFM 2049
If an ASET1 entry references a non-existing grid as an end point for the "thru"
option, then the following fatal message is issued: "USER FATAL MESSAGE 2049,
UNDEFINED GRID POINT ** HAS A COORDINATE REFERENCED ON A ASET CARD." Besides
the fact that this message should not be encountered at all, this message is
poor for the following reasons:
(1) The missing grid point specified in the message will always be the first
grid point in the "thru" range, not the actual missing grid point.
(2) The word "coordinate" is incompatible with other documentation which uses
the word "component".
(3) It uses the obsolete word "CARD"
(4) It repeats the message twice.
(5) If the user explicitly specified the grids on the ASET1 entry rather than
using the "thru" option, they would have gotten User W
1/2/02 abb
6996
7
Optimization/Design Sensitivity - Q4TAPER - UWM 5491, UFM 429
If an auxiliary model is used to generate the shape basis vector for a shape
optimization analysis and in the subsequent dblocate optimization run an
element exceeds the maximum allowable taper value of .5 then EMG issues UWM
5491 that may identify elements with bad geometry that do not exist in the
model. The run may also issue USER FATAL MESSAGE 4297 indicating that an
element has an interior angle greater than 180 degrees. An example of the
warning message follows:
USER WARNING MESSAGE 5491 (EQD4D)
BAD GEOMETRY FOR QUAD4 ELEMENT ID = 2600 THE TAPER OF 0.582639 EXCEEDS THE
MAXIMUM VALUE OF 0.500000
USER ACTION: THE TOLERANCE MAY BE ADJUSTED WITH Q4TAPER KEYWORD ON THE NASTRAN
STATEMENT.
Avoidance: EMG is reporting the internal identification numbers for the
perturbed elemen
6997
70.5
nce Manual - Wrong answer
Acoustic Analysis - Superelements, Refere
The Version 68 MSC/NASTRAN Reference Manual Section 15.4.2 states that the
"grid points at the fluid-structure interface may be assigned to the residual
structure only". This statement is not restrictive enough. The MSC/NASTRAN
Common Questions and Answers Guide states the restriction correctly; "for
coupling to occur, all fluid elements that are in contact with the structural
elements must be in the residual structure, and all structural elements that
are in contact with the fluid elements must also belong to the residual
structure.
6998
swers
69
Heat Transfer Analysis - QBDY2 - Wrong An
QBDY2 (Boundary Heat Flux Loading) loading on CQUAD8, CTRIA6, CHEXA20,

CPENTA15, CTETRA10 elements results in incorrect data recovery for the element.
The temperature vectors are correct. The heat flow into the HBDY elements is
wrong.
Avoidance: Ignore the Heat Flow into HBDY element for the Applied Heat load.
All other output is unaffected by this error. If the user wants to see the
correct applied load under the Heat Flow into the HBDY element, they must use
the QBDY3 bulk data entry to apply the loading.
7001
70.5
Nonlinear Transient Heat Transfer - QRG,
PARAM,AUTOSPC - UFM, Failed to Converge
PARAM,AUTOSPC,YES will automatically constrain floating degrees of freedom.
The floating grid is used in heat transfer to model ambient temperature as a
function of time .Heat transfer analysis uses these floating grids to apply
temperature as a function of time through the TEMPBC,TRAN. Use of this
PARAM,AUTOSPC,YES in nonlinear heat transfer results in a run that fails to
converge. This limitation is documented in the Version 68 Release notes but
needs to be documented in the Quick Reference Guide.
7002
Sequencer - GP2 - UFM 2007
If an attempt is made to use the punched grid and element output of a p-element
run in the bulk data the following error will occur and the run will fail in
the SEQP module or GP2 modules:
*** USER FATAL MESSAGE 2007 MODULE = GP2
ELEMENT ******** REFERENCES UNDEFINED GRID POINT 111001009
USER FATAL MESSAGE 2007, ELEMENT******** REFERENCES UNDEFINED GRID
POINT********.
This message occurs since grid ids larger than 100000000 are not valid on the
grid card and the vu-grids have ids greater than 100000000. .
Avoidance: Following system cells should be set in a p-element run to generate
smaller vu-grid ids and vu-element ids.
System cell values are beginning and maximum for vu-grids and
vu-elements
nastran system(175)=9000,
$ GRMAX = 1
7006
69
ct RTYPE, Missing Documentation
Documentation - DRESP1, DVPREL2 - Incorre
The Version 68 MSC/NASTRAN Quick Reference Guide description of the DRESP1

entry indicates the RTYPE for SPCFORCE as FRSPC and TSPC, it should be FRSPCF
and TSPCF. Remark 3 under the description for the DVPREL1 entry for
PTYPE="PBEND" should also be included for the DVPREL2 entry.
7007
69
TRANSFER ERROR NO. -3
Installation - NASTRAN FOR WINDOWS - FILE
If long file names have been disabled by the following registry entry the
NASTRAN FOR WINDOWS VERSION 68.2 Installation will fail with the message "FILE
TRANSFER ERROR NO. -3".
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\Win31FileSystem
Avoidance: Reset the registry entry and restart your computer.
7010
2001
PLOT - UFM 5423
Axisymmetric Fluid Elements - CAXIF4, VEC
Models with CAXIF4 axisymmetric fluid elements fail in the VECPLOT module with
the message:
USER FATAL MESSAGE 5423 - ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES.
This error has been fixed for real formats but complex formats still cause a
fatal message. There is no plans to fix the complex formats since this
capability has been replaced by more modern methods.
Avoidance:
Apply the following alter:
compile selg nolist noref
alter 63,63
endalter
7011
69
DMAP - VECPLOT - Excessive CPU
The VECPLOT module can consume a significant amount of CPU when processing
RESULTANTS and MAXIMUMS. This information may be of no interest to the analyst
yet the only way to turn it off is thru DMAP. MSC/NASTRAN Version 69 has been
enhanced to give the analyst options to avoid these calculations.
PARAM,PRTMAXIM (default=no) and PARAM,PRTRESLT (default=yes) have been added to
control the calculation of MAXIMUMS and RESULTANTS respectively.
7012
70.5
Executive - DIAG 14,64 - UFM 69
The presence of both DIAG 14 and DIAG 64 in the same run will cause the
following message "USER FATAL MESSAGE 69, SUBDMAP STATEMENT PARAMETER APP NOT
DEFINED". This error is only known to occur in the structured solution
sequences (SOLs > 101)
Avoidance: Remove Diag 14 and/or Diag 64.
7013
Entries
Miscellaneous - COMIFP, PUNCH - Produces Incorrect Bulk Data
The comifp module has been modified for Version 69 to support the part
superelement concept. It can take ifp-like files from the sep2 module and
punch bulk data files which may then be used as part files. At present, the
RBE2 and RBE3 elements are punched incorrectly.
Avoidance: An avoidance is to separate the elements not properly processed by
hand.
7014
69
Heat Transfer Analysis - MAT4, CONVM, EMG
- FATAL ERROR, Bad Diagnostic Message
If the user fails to define a dynamic viscosity in field 7 of the MAT4 entry
for a forced convection analysis the job fails in the EMG module with no
indication of the cause of the error.
Avoidance: Make sure the dynamic viscosity is input on the MAT4 card if the
problem has CONVM bulk data entries.
7015
69
CLOAD - Wrong Answers
Material Nonlinear Analysis - TEMP(LOAD),
In Version 68.2 and SOL 106 only, thermal loads applied to upstream
superelements results in incorrect stresses and forces.
Avoidance: Use SOL 66 or apply the following alter to SOL 106:
compile super3 noref nolist
alter 'IF ( NOCASRS1>-1 AND SEID=0 )',''
IF ( (NOCASRS1>-1 AND SEID=0) or app='nlst' ) THEN $
7021
69
Wrong Ordering
Optimization/Design Sensitivity - DSCM2 -
In design sensitivity analysis, there is a table printed just prior to the

DSCM2 (design sensitivities matrix) which specifies the ordering of the columns
in the matrix. If some of the design responses specified on the DRESP1 entry
are the eigenvalues, then the table claims that the eigenvalue responses are in
ascending order by DRESP1 entry ID. However, the matrix is actually in
ascending order by mode number.
Avoidance: The only avoidance is to be aware that the output is in ascending
order by mode number.
7040
69
Documentation - DRESP1 - UFM 316
The documentation for the DRESP1 entry in the MSC/NASTRAN Version 68 Quick
Reference Guide states that the SPC force component is chosen with the
RTYPE=FRSPC or RTYPE=TSPC. However, if either of these RTYPEs are used, the
following fatal message is issued, "USER FATAL MESSAGE 316 (IFPDRV) ILLEGAL
DATA ON BULK DATA CARD DRESP1 331 SORTED CARD COUNT = ***". The documentation
should say the the SPC force component is chosen with RTYPE=FRSPCF or
RTYPE=TSPCF.
Avoidance: Use RTYPE=FRSPCF or RTYPE=TSPCF not FRSPC or TSPC when the SPC
force component is desired as a response type.
7041
ce
69
Nonlinear Analysis - EMG - Poor Performan
NO EXTERNAL ERROR REPORT

When there are no linear elements in a model, the EMG module is unnecessarily
executed.
This appears to be a minor performance improvement, I see no need to publish to
clients.
7044
69.1
T, DLOAD - Wrong Answers
Nonlinear Transient Heat Transfer - QVEC
Scaling by other than 1. of a vector flux QVECT load by a DLOAD bulk data entry
produces wrong results in the "APPLIED-LOAD" column of the "Heat Flow into HBDY
Elements" table. The actual load vector generated is correct and therefore the
temperatures are correct.
Avoidance: Use only scale factors 1 on the DLOAD entry.
7045
69
Case Control - SUBCASE - Poor Message
The message " *** USER FATAL MESSAGE 609 (IFP1D) SUBCASE DELIMITER CARDS MUST
HAVE A UNIQUE IDENTIFYING INTEGER " which does not accurately describe the
input error is issued for the following situation:
1. When the subcase id exceeds 9999999.
2. In solution 200 when the subcase id of the preceding subcase is higher than
the id of subsequent subcase.
7047
69
the Flutter Summary
Aeroelastic Analysis - Unwanted Output in
In the pk flutter solution, all combinations of velocity, Mach number and

density are used. In certain situations (e.g., if analyses are only required
at 50 velocity-density combinations) it would be preferable to only do ordered
combinations.
Avoidance: The current avoidance is to put each required combination in its
own subcase. For the
example given above, this would require 50 subcases, but it would reduce the
number of flutter
analyses from 2500 to 50.
7048
Keyword
69
Submittal Script - node - Error With node
When the "node" keyword is used along with the "user" keyword ( i.e. nastran
..... node=pelee user=ssp) then
job will not get submitted to remote node and the following message will be
displayed on the console:
nast68: (W) node=pelee specified, setting app=yes bat=no scr=yes
nast68: (E) node=pelee: no execute permission on remote node.
Avoidance: The following line in the nastran shell script should be changed.
The shell script is
$MSC_INSTALLDIR/bin/nastran.
rx="$remcmd $tuser $node"
should be changed to
rx="$remcmd $node $tuser"
7050
69
Labeled as SPCF in .pch file
Multipoint Constraint - MPCFORCE Output -
MPCFORCE output when printed to a punch file, is mis-labeled as SPCF. The data
is correct however. Confusion may arise when both SPCFORCE and MPCFORCE are
printed to the punch file. The user must use care to read the correct results.
The error is considered fixed in Version 69; however, setting of SYSTEM(210)=1
is required.
Avoidance: Print and punch the data so that the output can be compared and
correlated.
7053
ding
69
Documentation - DVPREL1 - UFM 2042 Mislea
The DVPREL1 entry is used to define a relationship between an analysis model

property and a design variable. However, not all analysis model properties are
valid choices. For example it is not valid to link the MID field on a property
entry (which is an integer) to a design variable (which is always real). If
this is done the MATi entry in the analysis model is overwritten with a
nonexistent MATi and then the following misleading message is issued, "USER
FATAL MESSAGE 2042, MISSING MATERIAL TABLE******** FOR ELEMENT xx". Invalid
choices for the analysis property chosen on the DVPREL1 should be screened out
prior to the start of optimization.
Avoidance: Choose only valid analysis properties on the DVPREL1.
7055
69
ELL, PCOMP - Missing Documentation
Documentation - Composites, Buckling, PSH
The following remark should be added to the PSHELL bulk data entry description
in the MSC/NASTRAN Quick Reference Guide:
The use of MID4 will cause incorrect results in buckling analysis and
differential stiffness.
The following remark should be added to the PCOMP bulk data entry documentation
in the MSC/NASTRAN Quick Reference Guide:
An unsymmetric layup or the use of ZO to create an unsymmetric layup will cause
incorrect results in buckling analysis and differential stiffness.
7059
2001
op, Device Full
Miscellaneous - DMIG - Psuedo Infinite Lo
If characters are input in the NCOL field of a DMIG header entry and the matrix
is rectangular (IFO=9), then the MTRXIN module may be caught in a pseudo
infinite loop which may be finally stopped by a "device full" message. The
MTRXIN module interprets the characters in NCOL as an integer and this is

normally a huge number. The IFP module should stop the execution with "User
Fatal Message 327" in case that the input for NCOL is not an integer.
7065
Poor Answers
69
P-Elements - Wrong Adaptivity Analysis -
If a data deck contains different TYPEs of P-elements (e.g. a HEXA and a

PENTA), the adaptivity error analysis likely to be in-accurate leading to poor
answers.
7073
69
ot Read TEMP Vector
Heat Transfer - PARAM,POST,-2 - SDRC Cann
SDRC is not able to read the temperature vector in the output2 file produced
with PARAM,POST,-2.
Avoidance: Use EQUIVX instead.
7076
Timing Estimate - DECOMP - UIM 4157
The CPU time estimates issued in USER INFORMATION MESSAGE 4157 for sparse
decomposition can be overstated by a factor of 7 to 15 times on some machines.
This is due to the fact that the timing estimates do not take into account the
high rank performance update enhancement which was introduced beginning in
Version 68.1. By overstating the CPU time estimates the job may fail with a
message that it does not have enough time to complete Decomposition.
Avoidance: Include an extra large value for time on the TIME executive control
entry or remove the TIME entry.
7085
M - UFM 4342
70.5.2
Cyclic Symmetric - Dihedral, LOADCYH, DSY
A cyclic symmetry analysis using dihedral symmetry and centrifugal loads may
issue the following message:
USER FATAL MESSAGE 4342,
THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALYSIS
HARMONICS OR SEGMENTS OR SYMMETRY TYPE.
LOADCYH
20
0CSTAR
2000004
The message occurs when a SS (Symmetric=Symmetric) boundary condition is
specified on the DSYM case control command and the LOADCYH bulk data requests
an 'RLOAD' for the HTYPE field. In this condition the code generates too many
load vectors.
Avoidance: One avoidance is to change the HTYPE field to 'C' on the LOADCYH
bulk data entry. A better avoidance is to eliminate the DSYM request in the
case control.
7088
70
4 and ZOFF may be combined
Documentation - PSHELL, MID4, ZOFFS - MID
Remark 6 under the description of the PSHELL entry in the Version 68 Quick
Reference Guide states that "Only one of the options MID4 or ZOFFS may be
used". This is a guideline to prevent users from offsetting the element twice.
Depending on the intent of the user these affects may be combined and correct
answers achieved.
7093
s
70.5
Complex Eigenvalues - CLAN - Wrong Answer
For one model, the complex lanczos eigenvalue method in solution 107 produced
erroneous eigenvalues on the CRAY computer. The same model produced consistent
real eigenvalues across all machines so there does not appear to be anything
wrong with the model. MSC/NASTRAN Version 70.5 introduces the new Block
Complex Lanczos method. This method correctly solves this problem on CRAY and
all other machines. This method must be selected in Version 70.5 by setting
system(108)=4 on the NASTRAN entry or rc file.
Avoidance: Until the error is better understood, use SOL 110, modal complex
eigenvalues, with the Hessenberg Method.
7100
69
Static Analysis - SPC - UFM 5423
A DMAP error exists in multiple boundary condition with non-zero SPC in SOL
101. The error is triggered
when the same boundary conditions are not grouped together, i.e., the same SPC
is selected again following
a SUBCASE with a different SPC. The error is detected by the SSG2 module with
a UFM 5423 "attempt to multiply incompatible matrices." This error is related
to error 5977 which is detected when SPCD is used instead of non-zero SPC.
Avoidance:
1. Shuffle the Subcases so that the same boundary conditions are grouped
together (to appear consecutive Subcases).
2. Use SOL 106 with unsorted SUBCASE set-up and run it as a linear problem
without any nonlinearity.
7108
cient Time
69
Acoustic Analysis - SDR1, MPYAD - Insuffi
Acoustic Analysis in MSC/NASTRAN does not support the matrix method of data
recovery. Thus, the data recovery performed by the modal displacement method
for small sets of data is very inefficient. This deficiency is complicated by
poor timing estimates in MPYAD. MPYAD, which is called by SDR1 during the data
recovery, may yield a time estimate that overflows the machine. Version 69
will support data recovery in the DDRMM module, i.e., the matrix method.
Avoidance: There is no simple avoidance. Perform modal reduction on the fluid
and limit the number of frequencies in the analysis. The following alter can
be applied to recover pressure only by the matrix method.
compile semfreq souin=mscsou noref nolist
alter 74
lamx
,,lamas/mlamas/-1 $
lamx
,,lamaf/mlamaf/-1 $
ma
7109
70.5
DMAP - MATMOD OPTION 17 - Wrong Answers
MATMOD option 17 generates a g-size partitioning vector from a user-defined set

of grid and/or scalar points. If the 3rd parameter (SETFLG) is set to 1, it is
supposed to look for the PARTN case control command and put a value of 1.0 in
the vector for grid points listed in the set defined by the PARTN case control
command. If there is no PARTN case control command, it is supposed to use the
sets defined by the 2nd parameter (UBIT). However, the above operation
returned a vector with all values set to 1.0 instead. Depending on subsequent
operations, this can either lead to fatal errors or wrong answers.
Avoidance: Include the appropriate PARTN case control command.
7110
69
SSSALTERS - evds.v682 - Fails to Converge
When using the eigenvector sensitivity dmap alter (evds.v682) delivered with
the sssalter library in Version 68.2, and the model does not contain any
elements which references a mass property entry, then the job may fail to
converge.
Avoidance: Replace the following dmap statement in evds.v682 subdmap fox:
TYPE
PARM,,I,N,NULLDM $
with
TYPE
PARM,,I,N,NULLDM,NZWD $
7118
69
ed Limits, User Modifiable NASTRAN
Documentation - ADUMi, PDUMi - Undocument
The number of additional fields "NP" on the PDUMi entry is limited to 24 words.
This limit is not documented in the description of th NP field of the ADUMi
bulk data entry description.
7127
69
NORM - UFM 2025 in module TA1
Optimization/Design Sensitivity - PARAM,S
If in SOL 200, parameter SNORM is greater than or equal to 0.0 and if a

coordinate system is specified in the MCID field of the connectivity entry in
the run then the following fatal message will be issued.
*** USER FATAL MESSAGE 2025 MODULE = TA1
UNDEFINED COORDINATE SYSTEM
3
This error might also occur in SOL 101 and 103 if p-element adaptive analysis
is performed.
Avoidance: Two avoidances exists:
1. Remove the SNORM parameter.
2. Add the following alter.
compile update souin=mscsou nolist noref
alter 51,51 $
TA1
,,ECT,EPTX,BGPDTSCR,SIL,,CSTMSCR,/
ESTJNK,,,GPECT0,/
LUSETS/-1/S,N,NOSIMP/1/S,N,NOGENL/0 $
7136
69
Restarts - MAT2, IFPL, RESTART - DEC Alph
a Only Aborts on Restart

There is an error in the nddl for the MCSID field of the MAT2 entry. The nddl
types the field as real when it should be an integer. If this field is changed
in a RESTART the execution will fail. The message
"time: command terminated abnormally" is issued in the log file.
Avoidance: The run should be executed as a cold start.
7137
Extra Output
69
Postprocessing - PARAM,POST,-2, SOL 112 -
In SOL 112 with PARAM, POST, -2, the geometry tables are written twice to the
OUTPUT2 file. However, this does not seem to negatively affect the IDEAS
translator.
7138
70
ers - Incorrect Problem Descriptions
Documentation - Common Questions and Answ
The problem description on page 103 of the Common Questions and Answers ,2nd
Edition, does not match figure 40 on the same page. The acceleration should be
negative, as is reflected in fig. 40 and the 3 in field 5 of the RLOAD2 entry
should be moved to field 6.
The title for figure 39 on page 101 of the Common Questions and Answers book
refers to point loads when in fact the example discusses pressure loads
(PLOAD4s).
7139
69
or Access Violation
Executive System - COMPILE - Segmentation
An attempt to compile the NDDL and more than 75 subDMAPs in a single run causes
a segmentation or access violation. The limit in Version 69 has been expanded
to allow for at least 100 subdmaps.
Avoidance: Split the job into two runs.
7141
70.7.2
M 4551 (NL2CON)
Nonlinear Transient Analysis - CBEAM - UF
It has been found that in rare cases when then the orientation vector for a
beam element is exactly normal to the axis of the beam, the Cray may exhibit a
round-off error that leads to convergence difficulties and ultimately USER
FATAL MESSAGE 4551, STOPPED PROBLEM DUE TO FIVE CONSECUTIVE DIVERGING TIME
STEPS.
7142
SFM 4276
69
Optimization/Design Sensitivity - DOPR3 -
If the user provides constraints for multiple DRESP1 entries in a single

flutter subcase, then SYSTEM FATAL MESSAGE 4276 GREAD
ERROR CODE
3001
will occur in the DOPR3 module.
Avoidance: If it is not possible to define all the flutter responses on a
single DRESP1 entry, multiple
flutter subcases are required, each with a single referenced DRESP1 entry.
7144
Nonlinear Transient Analysis - OTIME - Missing Output
In nonlinear transient analysis (SOLs 129 and 159), the solution vectors
(SDISP, SVELO, and SACCEL) should
be output for each subcase independently. However, SDISP, SVEL, or SACCEL does
not appear in the output unless the request is specified above the subcase.
Avoidance: Specify the output request for SDISP, SVELO, or SACCEL above the
subcase level.
7147
69
Utilities - OPTCONV - Fails On Windows NT
If the OPTCONV program delivered with the Windows NT version of NASTRAN is used
to convert an old optimization deck to the current format, the following
message is obtained in a pop-up window: "The instruction at 004147cc referenced
memory at 0d4212b9 The memory could not be written Click on OK to terminate the
application". Therefore, it is not possible to convert any old optimization
decks on Windows NT.
Avoidance: Convert the decks by hand or have them converted on a different
machine variation.
7156
Output
69
P-Elements - PARAM,USETPRT,0 - Incorrect
PARAM,USETPRT,0 produces incorrect output for P-Elements.

Avoidance:
Use PARAM,USETPRT,1 instead.
7163
69
AUTOSPCR - UWM 5225, Wrong Answers
Nonlinear Static Analysis - ASETi, OMITi,
In nonlinear static analysis, any nonlinear degree of freedom in the o-set (via
ASETi or OMITi entries)
may result in a singularity in the o-set linear stiffness matrix (UWM 5225).
Also, if PARAM,AUTOSPCR is used, all the nonlinear degrees of freedom will be
constrained and the resulting solution will be incorrect.
Avoidance: Include all the active nonlinear degrees of freedom in the A-set.
7167
193, UFM 4551
69
Nonlinear Heat Transfer - UIM 6194, UIM 6
Nonlinear Heat Transfer jobs with more than one subcase may fail to converge
and issue UIM 6194, UIM 6193 and USER FATAL MESSAGE 4551. This error was
experienced in a job where the second subcase was the same as the first. The
job should have converged immediately in the second subcase since there was no
change.
USER
STOPPED ITERATIONS DUE TO REACHING MAXIMUM ITERATION LIMIT WITHOUT CONVERGENCE
***
USER
MAXIMUM NUMBER OF BISECTIONS OR MINIMUM LOAD STEP HAS BEEN REACHED.
USER
FATAL
MESSAGE 4551,
STOPPED PROBLEM DUE TO FAILED CONVERGENCE
7170
t node option
69
Heat Transfer - CHBDYP, LINE with midpoin
Currently there is a design limitation using CHBDYP,LINE to represent thhigher

order CQUAD8 or CTRIA6 for the edges with midpoint option. Therefore, the
weighting on the mid-side node is misrepresented if the two node LINE option is
used.
Avoidance: Use CHBDYE to represent the CQUAD8 or CTRIA3 element with
midsidenodes. Please note that without the midside node, the CHBDYP,LINE can be
used.
7171
2001
Field description
Documentation - Reference Manual - Large
There is an error in the Reference Manual documentation for the description of

the Small/Large/Free field format of the bulk data entries as follows:
pp 3.7.1-2 Bottom of the page, Large Field example. The first field of the
parent card should be TYPE* not TYPE. The continuation of the parent card
should be QED123 not QED124.
pp 3.7.1-3 Top of the page, Large field with large field continuation example.
This is shown as all small fields. There should only be 4 (double wide)
fields between the first and last fields.
7173
69
P-elements - CHEXA - UFM 9050
CHEX p-Elements can have singularities in the stiffness for the default
integration options. This error only occurs in a model with a single layer of
elements. In particular the default reduced integration order with
rectangular elements with p values of [2,2,3] in the three directions may be
singular. This error may lead to the following fatal message:
USER FATAL MESSAGE 9050 (SEKRRS) - RUN TERMINATED DUE TO EXCESSIVE PIVOT
RATIOS
IN MATRIX KLL. USER PARAMETER BAILOUT MAY BE USED TO CONTINUE THE RUN.
Avoidance: Specify a different p value.
7175
e Dictionary
70.5
Documentation - CALL DBFETCH - DMAP Modul
The description of the DBFETCH command in the DMAP Module Dictionary should
enhanced to state "if you are using DBFETCH in a Sol 100 (USER DMAP) to get
data blocks from a previous run, include a RESTART FMS statement to specify the
version number on which the data blocks were written".
7176
g Answers
69
Direct Frequency Response - CHACAB - Wron
The damping terms for the acoustic absorber element, CHACAB, are "lost" in
solution 108 resulting in null damping from this element.
Avoidance: Place equivalent CDAMP or CVISC elements across the structural
boundary points.
7179
69
Documentation - QRG - Inconsistent E,G, N
U with MAT1
Table 1 under the MAT1 description in the Version 68
Reference Guide indicates that "E" and "NU" are used
for "Membrane and Bending" of the CQUADi, CTRIAi and
should be clarified to state "should be clarified to
Inplane Shear".
7182
69
2 - Missing Output
MSC/NASTRAN Quick
to define the properties
CCONEAX elements. This
"Membrane, Bending and
Post Processing - SOL 103 and 105, OUTPUT
When multiple subcases are used in SOL 103 or 105 and PARAM,POST,-1/-2 is
chosen, the output2 file is written over with each subcase and only the last
subcase remains in the output2 file for post processing.
Avoidance: Request different output2 units in each subcase using param,ounit2
or the following DMAP alters may be used for some post processors (PATRAN3 v5)
For SOL 103:
$
ALTER 'IF ( POST=-1 AND OUNITX\<\>OUN','IF ( ( ((DROPT=0 OR DROPT=4)'
PARAML CASECC//'DTI'/1/1//S,N,SUBC1 $
PARAML CASEDR//'DTI'/1/1//S,N,SUBCNO $
IF ( POST=-1 AND SUBCNO=SUBC1 AND OUNITX<>OUNIT2 AND NOT(PEXIST) AND
NOT((APP='NLST' OR APP='TRANRESP') AND PATVER>=3.) AND
(((DROPT=0 OR DROPT=4) AND APP1<>'BKL1') OR APP='BKL0')
) OTAPE2=-1 $
7184
69
VER,3 - Incorrect Deformed Shape
Postprocessing - PARAM,OUGCORD,BASIC, PAT
PATRAN 3 will display an incorrect deformed shape when PARAM OUGCORD is set to
BASIC and the gridpoint output coordinate systems (field 7, CD) is anything
other than the basic (coordinate system ID 0). SubDMAP SEDRCVR transforms the
displacement vector into the basic coordinate system based on the value of the
parameter OUGCORD and PATVER. In Version 67.5 the DMAP IF test includes the
value of the parameter PATVER which prevents transformation if PATVER=3.0
(default for PATVER is 3.0).
66
67
ELSE IF ( NOT(PATVER>=3.) AND OUGCORD='BASIC' ) THEN $

VECPLOT UGVS,BGPDP,EQEXINS,CSTMS,CASEDR,/UGVSB//0/1 $
The reason for preventing this transformation is that PATRAN 3 understands the
CD field for the GRID entry. In Version 68 the DMAP test for PATVER is not
present:
70
7185
66
Response Spectra - SDR2 - Wrong Answers
The response spectra summation process for the NRL and SRSS methods handle
the CBAR and CBEAM elements
differently. Both the NRL and SRSS methods involve taking the square root of
the sum of the squares of the value
of interest, in this case stress. For the BEAM element the summation is made
for the combined bending and axial
stress, while for the BAR element the bending and axial stress is summed
independently to coincide with the BAR's

output which prints the axial stress separately. This leads to incorrect
results for the output of the maximum and
minimum stress.
Avoidance: The CBEAM element should be used for Response Spectra Analysis
whenever stress results are
desired.
7186
t Found
70.6
Documentation - INCLUDE - Include File No
The Installation and Operations manual Section 4.5 states that the default
directory for an include file is the input file's directory. The default
directory is actually the current directory.
Avoidance: Place the file to be included in the current directory or specify
the complete path name of the file to be included.
7191
69
Optimization/Design Sensitivity - TEMP(LO
AD), TEMP(MATERIAL), SHPCAS - SFM 3001
When a TEMP(LOAD) and/or TEMP(MATERIAL) entry is used in the primary Subcase
Control section of a shape optimization job using the analytic shape boundary
shape approach in MSC/NASTRAN Version 68.2, the job will fail in module SHPCAS
with the message "SYSTEM FATAL MESSAGE 3001".
Avoidance: Apply the following DMAP alter.
compile bndshp nolist noref souin=mscsou
alter 'auxmid'(2)
dbview ugx=ug (where mtemp=*) $
alter 'partn','partn'
PARTN UGx,,AXMVEC/UGA,,,/1 $
alter 'equivx','equivx'
EQUIVX UGx/UGA/ALWAYS $
7193
2004
- UFM 313 or Wrong Answers
Miscellaneous - Wrong continuation format
If column 1 of the continuation entry is blank, then the continuation entry is

interpreted as a continuation of the last sorted bulk data entry. The error is
likely to result in USER FATAL MESSAGE 313 ILLEGAL NUMBER OF WORDS ON
CONTINUATION" or in rare cases possibly even wrong answers. An example
follows:
.
Begin Bulk
.
.
tic,100,101,1,0.,0.
$
grid,1000,,0.,2.5,2.5
$
grid,101,,0.,0.,0.
grid,102,,10.,0.,0.
$
2
3
cbar
1
1
+000015
+000015
4
101
5
102
6
1000
0.25
0.
0.
0.25
0.
0.
10
$
.
.
enddata
will be interpreted as
BEGIN BULK
.
.
CBAR
1
.
GRID
101
102
1000
+000015
7196
, SFM 3003
2001
Miscellaneous - GP2, GENEL - Poor Message
When at least one entire line is missing from a GENEL element, GP2 issues the
message:
SFM 3003 ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK
GEOM2S (FILE 101) IN SUBROUTINE GP2.
Avoidance: Correct any offending GENEL elements. At a minimum the Reference
Manual documentation should cite incorrect GENEL input as a possible cause of
the error message.
7197
Documentation - Security - NAO - NAO Not Working, UIM
The following message may be issued if network problems are encounterd during
an MSC/NASTRAN run using the Network Authorization option. These messages are
not, but need to be, documented in the Installation and Usage Guide for the MSC
Network Authorization option.
USER INFORMATION MESSAGE: MSC Network Authorization Option
Reconnection completed.
Feature NASTGPLM10000000 reconnected after 1 of 5 attempts at 30 second
interval
Avoidance: This error occurred due to network problems at a client site. NAO
worked correctly once the network problems were corrected.
7199
Nonlinear Transient Analysis - PARAM,LGDISP - Poor Answers
In MSC/NASTRAN Version 68 nonlinear transient analysis, solutions 99 and 129,

were improved to correct error 2665 which stated that in nonlinear transient
analysis the damping matrix is not updated. The damping forces for the large
displacement solution now use the current "updated" damping matrix, which may
have been calculated at an unconverged solution. This approach was intended
to provide better directionality to the damping forces when they rotate.
However, every time the damping matrix is updated for convergence, a change
will occur in the force balance which will cause an erroneous step in the
converged accelerations.
7201
70
lculated in Single Precision
Element - CELASi - Forces/Stresses are Ca
Scalar spring and damper element's (ELASi and DAMPi, 1=1,2..4) stress and force
outputs are calculated with only single-precision arithmetic. If a scalar
element connects two points with small differences in displacements, relative
to the total displacements, some numerical roundoff will occur. Since the
stiffness and damping matrices are calculated in double precision the overall
results will not be affected.
The problem also does not occur on large-word, 64-bit computers such as CRAY
and NEC.
Avoidance: More precise results for the ELASi elements may be obtained from the
GPFORCE output request.
7202
ut
69
Case Control - MPCFORCE=NONE - Extra Outp
The mpcf=none command does not turn off mpcforce output in a subcase when it
has been requested above the subcase level.
Avoidance: Define set 1 = [x], where x is a nonexistent grid or scalar point
and use mpcf=1 instead.
7206
69
Y - Wrong Answers
Heat Transfer Analysis - CHBDYE,TUBE PHBD
The convection area used by the CHBDYE for the structure TUBE element is
incorrect whenever D2 is left blank. In Version 69 the code is changed so that
if D2 is left blank then D2 is set to D1.
Avoidance: Use CHBDYP,TUBE option to represent the tube convection area or
explicitly set D2.
7207
69
Restart - SPCFORCE - Missing Output
SPC force output request is ignored during automatic restarts in dynamic

structured solution sequences. See related Error 3119 which was fixed for SOL
101 only.
Avoidance: Include the entry PARAM, SERST, SEDR in the bulk data section of
the restart deck.
7210
R70
Security - NAO, NAOOPT - Job Hangs
If the NAOOPT=INFO,MSG2 keyword is used with MSC/NAO Version 2 on the DEC ALPHA
OSF/1 release of MSC/NASTRAN, the job will hang.
Avoidance: Remove the NAOOPT keyword from the nast682rc file or do not use it
on the command line.
7213
DMAP - FBS, SYSTEM(72)=1 - Wrong Answers
Left handed fbs solves the equation of the form:

t
t
[X] [L][U]=[B]
In addition left handed fbs has an option of solving
T
[X] L U = [B]
This option is only documented in the MSC/NASTRAN Numerical Methods Guide and
is selected by setting SYSTEM(72)=1. This option produces wrong answres when B

is rectangular. The left hand fbs method is not used in the delivered solution
sequences for non symmetric matrices. Thus, only user DMAPs may encounter this
error.
Avoidance: Use right hand fbs.
7215
45
Cyclic Symmetry - SECSET1, VAXW, GIV, MGIV - UWM 3034, UFM 46
Massless degrees of freedom that are placed in the c-set are not properly
removed before entering the READ Module in Cyclic Symmetry component mode
synthesis. Attempts to remove these degrees of freedom by explicitly
constraining them will also be ignored. This may lead to "USER WARNING MESSAGE
3034, ORTHOGONALITY TEST FAILED" followed by a fatal message, "USER FATAL
MESSAGE 4645---- THE SHIFTED STIFFNESS MATRIX IS NOT POSITIVE DEFINITE IN
MGIVENS METHOD" or "USER FATAL MESSAGE 4646---- THE MASS MATRIX IS NOT POSITIVE
DEFINITE, USING THE GIVENS METHOD. USE MGIV INSTEAD".
Avoidance: Do not put the degrees of freedom in the c-set, specify Lanczos
instead of a transformation method or add a small amount of mass to the
massless degrees of freedom.
7219
69
Miscellaneous - IFP - Infinite CPU Loop
The following continuation entries while legal when using the NASTRAN MESH
option result in an infinite cpu loop in IFP when the NASTRAN MESH command is
removed.
SPC1
=
DESVAR
=2
10
*1
20
*1
10
*-1
ABC
=
11
*1
1.
*1.
Avoidance: Add the NASTRAN MESH command or correct the continuation entries in
error.
7220
put
69
Postprocessing - PARAM,POST - Missing Out
If the ASSIGN statement is not used or if the complete path is not specified on
the ASSIGN statement for an OUTPUT2 file on the Windows NT Version of
MSC/NASTRAN, the file is not written to the jid directory but is instead
written to the "bin" directory.
Avoidance: Specify a complete path on the ASSIGN statement.
7231
69
Incomplete Sorted Output
Optimization/Design Sensitivity - XSORT -
The XSORT Module may encounter errors for large input files, when it is
executed more than once during a run. The messages encountered are various, but
the sorted file will be incomplete in every case. The error occurs only on
large files, and only on the second and subsequent bulk data files. The errors
occur when the bulk data to be sorted does not fit into memory. In Version 68
this error occurs only in design optimization analysis.
Avoidance: Increase the memory request so that the file will fit into memory,
or reduce the size of the file.
7232
77
69
Miscellaneous - IFP, RBEi- UFM 4276 EC 77
When the RBE3 bulk data entries contains illegal data in the REFC field, USER
FATAL MESSAGE 316 should be issued to identify the offending entry. USER FATAL
MESSAGE 4276 ERROR CODE 7777 is issued instead, which does not identify the
illegal data.
Avoidance: Other than locating the input in error and correcting it, there is
no avoidance.
7233
69
Matrix Methods - FBS, MPYAD - UFM 4547
FBS may set the density of GOAT incorrectly for some large models. The density
should be between 0 and 10000 (i.e., 100%). However, it sometimes overflows
this field and is printed in the f04 as *******. In this case the run will
fail in the MPYAD module with the message "USER FATAL MESSAGE 4547"
Avoidance: Use the following alter to re-set the trailer to a value of 80% (or
any value they desire).
compile sekr, souin=mscsou, nolist, noref
alter 106 $ the line which creates GOAT in his run
modtrl goat///////8000 $
7234
69
nexpected Answers
Loads - PLOAD1 - Missing Documentation, U
If on the TYPE field of the PLOAD1 entry, the element coordinate system
direction (e.g. TYPE=FYE) option is selected, then the projection (i.e.
SCALE=FRPR or LEPR) option is ignored and the result is the same as the
SCALE=FR (or LE) option.
7237
70.5
UTPUT2, INPUTT2 - SFE 4276 EC 1401
Documentation - DMAP Module Dictionary, O
MSC/NASTRAN Version 68 may not be able to handle an OUTPUT2 file of a matrix

generated from an external client written computer program that follows MSC's
documentation description of proper OUTPUT2 format. It is not the INPUTT2 step
that is crashing, it is any subsequent operation on the datablock, such as
TABPT, OUTPUT4, ADD, MATPRN or the like.
Avoidance: Use V67.5 to convert the OUTPUT2 file to an OUTPUT4, and then read
in the OUTPUT4 file into V68.
7238
SDRPOP)
69
p-Elements - DATAREC, OUTPUT - UWM 6514 (
When there are any OUTPUT bulk data entries, but no DATAREC case control
keywords, the following
warning is produced:
*** USER WARNING MESSAGE 6514 (SDRPOP)
THE DATAREC=
0 CASE CONTROL COMMAND REFERENCES UNDEFINED OUTPUT BULK
DATA ENTRY.
USER INFORMATION: THE DATAREC COMMAND WILL BE IGNORED.

USER INFORMATION: THERE WILL BE NO ERROR-ESTIMATE OUTPUT FOR THE
ADAPTIVITY ANALYSIS.
Avoidance: To avoid the warnings, the OUTPUT entries should be removed.
7242
p-Elements - GMCORD - Inefficient Processing
If a GMCORD coordinate system is used for the material, load, or displacement

coordinate system, execution may be inefficient since the coordinate system is
processed independently for each integration point.
Avoidance: Other than not using GMCORDs there is no avoidance.
7243
le Dictionary
70.5
Documentation - TABPT, BGPDTS - DMAP Modu
According to the DMAP module dictionary "TABPT may occasionally misidentify

real numbers or character values on the IBM/MVS-like computers". This problem
is not limited to the IBM/MVS-like computers.
Avoidance: Use TABPRT instead of TABPT.
7244
69
S=FLUTTER, DMIG - Wrong Answers
For flutter design sensitivity and optimization, the sensitivity results will
be in error if there
are multiple subcases and a second or subsequent subcase includes a different
M2PP, K2PP or B2PP request in the case control. The sensitivity analysis is
based on the generalized matrices from the first subcase and
will therefore be incorrect for the subsequent subcases.
7253
utput
69
Nonlinear Analysis - MPCFORCE - Missing O
MPCforces are not output in nonlinear analysis, solution 106.

Avoidance: Insert the following DMAP alter in Version 68.2:
compile nlstatic
alter 'ADD
DELCVECT,CVECT0'(,-1)
add5 qqgni,qgni,,,/qmgni//-1. $
call dbstore qmgni,,,,//nloop/0/'
'/0 $
alter 'DBVIEW CVECTH'
call dbfetch /qmgni,,,,/solcuri/0/0/0/0 $
call dbstore qmgni,,,,//solcur/0/'
'/0 $
alter 'APPEND QGNI,/QGNR'
$
file qmgni=ovrwrt $
$
call dbfetch /qmgni,,,,/nloop/0/0/0/0 $
file qmgnr=append $
APPEND QmGNI,/QmGNR/2 $ APPEND MPC FORCE VECTORS
alter 'EQUIVX QGNR/QGN'
call dbstore qmgnr,,,,//0/0/'
'/0 $
compile super3
alter 'ADD
PG,PJ/DPJ'
call dbfetch /qmgnr,,,,/0/0/0/0/0 $

equivx qmgnr/qmg/-1 $
COMPILE SEDISP
ALTER 'MPYAD
PSS,CRX'(2)
MPYAD PG,CRX,/PGX $
$
7260
69.1
, CHBDY - Incorrect Load Output
Nonlinear Transient Heat Transfer - DELAY
If the DELAY bulk data entry is used to define an offset in time for the
applied load. The actual heat load is applied correctly, and the resultant
temperature value is correct. However in the data recovery for the heat flux of
the HBDY element the load is applied incorrectly.
Avoidance: Ignore the applied load output for the HBDY elements.
7266
69
DMAP - MALTER - Extra output
The MALTER statement produces a listing of the altered subDMAP. This printout
cannot be suppressed even
if COMPILER NOLIST is specified. However, COMPILER REF and COMPILER DECK
produce the correct results.
7270
Answers
69
Acoustic Analysis - PARAM,WTMASS - Wrong
PARAM,WTMASS is applied to both the fluid and the structure, even though the
mass of the fluid is in different units.
Avoidance:
a. use mass density for density values and ensure that all mass input
values are in mass units.
b. or insert the following DMAP alter in V68.2:
compile semg noref nolist
alter 'MJJX,/-1/WTMASS','' $
type parm,,cs,n,cwtmass,mwtmass $
IF (NOMGG>=0) then $
dbstatus VGFS//S,N,NOVGFS $
IF ( NOVGFS>0 and wtmass<>1.0 ) THEN $
EMA
GPECT,MDICT,MELM,BGPDTS,SILS,CSTMS,MDICTP,MELMP/
MJJX1,/-1 $ MASS
matgen ,/ig/6/lusets/0/lusets $ gx1 matrix
cwtmass=cmplx(wtmass) $
add
ig,vgfs/wtmass/cwtmass//3 $
matmod wtmass,,,,,/wtmassg,/28 $ gxg
mpyad
mjjx1,wtmassg,/mjjx $
ELSE $
EMA
7276
Composites - PARAM,NOCOMP - Inconsistent Stresses
Homogeneous stresses, output when using 0 or -1 for PARAM,NOCOMPS, for

PCOMP-based elements are calculated inconsistently between linear and
non-linear solutions. Since homogeneous stresses are based upon smeared

laminate properties, both calculations yield only approximate the lamina
stresses (see also current error list number 1818) but both solutions should
use the same method. The two methods currently being used are:
For linear analysis:
S(z) = G1 * E - z * G2 * C
(1)
while for nonlinear analysis:

S(z) = G1 * ( E - z * C )
(2)
where:
C = curvature (chi)
E = reference plane strain (epsilon)
G = modulus matrix
S = stress
z = distance from reference plane
7284
Not Checked
69
Miscellaneous - DIAG - DIAGs Out of Range
I don't think this needs to be an external error report.

Please read text below for error.
7288
ong Answers
69
Nonlinear Buckling - MPC, RBE*, RBAR - Wr
If MPC's or rigid elements are used in a nonlinear buckling analysis, then

there is an error in the nonlinear buckling load factor (alpha computed by DMAP
in SOL 66 or 106). This error causes the critical buckling factor (UIM 9040)
to be estimated incorrectly. The remainder of the solution (eigenvalues and
displacements) is OK.
Avoidance: Use the following DMAP alter:
compile nlstatic noref nolist $
alter 'MPYAD DULV,DPL0,/NUM3/1','' $
mpyad dugni,dpgni,/num3/1 $
7289
69
TEMP(LOAD), SSG1 - UFM 3032
Optimization/Design Sensitivity - CELASi,
USER FATAL MESSAGE 3032 may occur in optimization solution sequence when
temperature loads are selected.
The error will occur when the following three conditions are true:
1) A structural model contains scalar elements such as CELAS1.
2) The grid points connected to these scalar elements are subjected to a
temperature load.
3) Only these scalar elements are designed and no other structural elements are
designed.
Note that scalar elements do not support temperature loading.
Avoidance:
1) Make a dummy design variable and related it to a non scalar structural
element in
the model. Then impose the same lower and upper limits on the dummy design
variables.
2) Replace the scalar elements with non scalar elements, i.e., use CROD instead
of CELAS1.
7290
Nonlinear Analysis - QUAD4, TRIA3 - Update Documentation
The existing documentation , such as MSC/NASTRAN V68 Reference Manual, Section

15.3.9 Small Strain Elements,
needs to be updated to indicate that the QUAD4 and the TRIA3 act differently
than the other "small strain" elements in that they satisfy equilibrium in the
deformed configuration.
This difference can have an increase in accuracy of internal loads in nonlinear
analysis if elements strains are significant.
7291
Performance,
69
Eigenvalue Analysis - REIGL, EIGRL - Poor
The REIGL module, when solving for normal modes of a vibration problem, under
certain rare circumstances will perform many negative shifts and ultimately
fail to find the modes requested by the user. Although one negative shift
often proves useful in picking up rigid body modes, additional negative shifts
are unnecessary and wasteful of computer resources.
One way to duplicate the problem is to specify on the EIGRL card, F1=blank,
F2=very large, ND=blank. If the F2 value is several orders of magnitude
greater than the largest eigenvalue in the model, the shift logic will usually
fail with the multiple negative shifts.
7294
2001
Miscellaneous - SUPORT1 - UFM 316
If a value of 0 (zero) is entered for the component number on a SUPORT1 entry

USER FATAL MESSAGE 316 will result.

ILLEGAL DATA ON BULK DATA CARD SUPORT1 ***
Avoidance: If you are referencing SPOINTs on the SUPORT1 entry, then use 1
(one) or blank.
7295
70.5
Documentation - SYSTEM(196), SCRSAVE - No
Documentation on Lanczos System Cell
There is no documentation in the Quick Reference Guide on the use of
SYSTEM(196) (a.k.a. SCRSAVE). This system cell control reuse of scratch files
when segment logic is invoked. System(196) is useful only when multiple
frequency segments are requested on a Lanczos run. (Multiple frequency
segments can be requested via the NUMS field in the EIGRL entry and by
system(197).) Each frequency segment requires a minimum of three scratch
files. When multiple frequency segments are used on a single processor
computer then each frequency segment is solved serially. In this case, it
makes sense to let segment #2 use the scratch files which were used by segment
#1 since work for segment #1 has been completed (otherwise it wouldn't be
working on #2). Similarly, when work for segment #2 is finish
7298
70.7
Hyperelastic Elements - QUAD4, MATHP, PLP
LANE - UFM 4297

Small hyperelastic QUAD4 elements may incorrectly fail with the message:
USER FATAL MESSAGE 4297 (EQDGED)
QUAD ELEMENT WITH ID =
XX
HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL TO 180 DEGREES.
event though the geometry is actually good. The error is caused by a bad test
on elements with lengths less than 1.0E-3.
Avoidance: The only avoidance is to use different units to make the distances
larger.
7300
Nonlinear Analysis - CGAP - Poor Results
If the adaptive GAP element indicates an update of an element stiffness AFTER

the program has converged on a solution, the program FAILS to re-iterate upon
that newly updated stiffness matrix hence the results are based upon the GAP
stiffness prior to the update.
This error has been encountered when the adaptive GAP gets the following
message:
*** NEW STIFFNESS MATRIX IS REQUIRED BY GAP FOR PENALTY VALUE ADJUSTMENT
***
PENALTY VALUES ARE ADJUSTED BY YYY FOR ELID = xx
AFTER the program has converged on the solution.
Avoidance: Increase the number of increments, NINC on the nlparm entry, or
adjust the value of the stiffness on the offending PGAP or both.
7305
70
Documentation - OTIME - Extra Output, OTI
ME Not Effective in Nonlinear Transient
The OTIME case control command is used to limit output in transient analysis.
This command is not effective for nonlinear transient stress output.
7306
nd Answers
70
Online Documentation - Common Questions a
The line "NASTRAN SCRATCH(MEM=n)" on page 267 of MSC/NASTRAN Common Questions

and Answers (Second Edition) in the MSC/NASTRAN Encyclopedia, page 144 in the
printed text, should be: "INIT SCRATCH(MEM=n)"
7307
T FOUND
2001
Dynamic Analysis - UWM 4684 LOADSET ID NO
In a dynamic response analysis, when the bulk data contains LOAD entries that
are not referenced by the CASE control and if STRESS output is requested, then
the following warning message is issued.
USER WARNING MESSAGE NUMBER 4684 LOADSET ID NOT FOUND FOR SUBCASE
Avoidance: Remove the non referenced LOAD entries from the bulk data.
7312
69
GEOM1 - SFM 3001
Optimization/Design Sensitivity - DOM11,
When only scalar points (no GRID entries) are defined in an optimization model
and the SEQP module is not executed to resequence the model, then there is no
GEOM1 generated. The run subsequently fails in the DOM11 module when it tries
to make a copy of GEOM1 with the message "SYSTEM FATAL MESSAGE 3001 MODULE =
DOM11 GEOM1 AT POSITION 12 DOES NOT EXIST".
Avoidance : Include a dummy GRID entry.
7314
69
Performance - VECPLOT - Poor Performance
On problems with more than 65,000 dofs, the vecplot module is inefficient, and
may cost as much as the
rest of the calculations. It is used in several places, primarily as a means
of providing checks such as
applied load resultants.
Avoidance: If you observe that the amount of time being spent in this module
is excessive you may insert an alter to delete this module call. The alter for
all Version 68.2 structured solutions is:
compile selg nolist noref $
alter 63,63 $
7320
FM 3007
69
Heat Transfer Analysis - CHBDYE, VIEW - S
The message "SYSTEM FATAL MESSAGE 3007 MODULE=VIEW, ILLEGAL INPUT TO SUBROUTINE
VNASIN" will occur if using the backside on the CHBDYP LINE element, for
example:
CHBDYP 101
+
11
1111
LINE
0
111
-1.0
2
1.0
3
0.0
Avodiance: Specifying the VIEWID on the frontside resolves this problem.

7326
umentation
70
Documentation - FORCE(PLOT) - Missing Doc
The MSC/NASTRAN Quick Reference Guide does not document the FORCE command
(PLOT) option. This option may be used if element force calculations are
desired for post-processing without printing them.
7331
Writing EPT
Postprocessing - PBCOMP - Formatted OUTPUT2 on DEC Alpha dies
If an EPT table containing entries for more than two PBCOMPs is written to a
formatted OUTPUT2 file on a DEC Alpha system, then the job will terminate with
either no message or a "time: command terminated abnormally" message in the
.log file.
Avoidance include: 1)
2)
3)
OUTPUT2 statement.
4)
Using PARAM, OGEOM, NO.

Writing to a formatted OUTPUT2 file.
Altering the OUT2GEOM subdmap and removing EPT from the
7333
69
TETRA, PSDF - UFM 3052
Running on a different platform

Frequency Response and Random Analysis -
Random response analysis that requests PSDF xyplots of TETRA stress results may
result in the following fatal message:

USER WARNING MESSAGE 3052, A RANDOM REQUEST FOR CURVE TYPE - STRE -, POINT 1
COMPONENT - 12 -, SPECIFIES TOO LARGE A COMPONENT ID. THE LAST COMPONENT
WILL BE USED.
The XYPLOT summary will then indicate that the correct plot is used, but wrong
results will be presented on the XYPLOT summary. In fact, if 6 plots are
selected, with items codes 6,7,8,9,10 and 11, the summary will say they all
have the same RMS value, even though they are asking for normalx, normaly,
normalz, tauxy, tauxz, and tauyz, which cannot be the same. Running a similar
problem with a HEXA instead of TETRAs, produces good results.
7335
Wrong Answers
69
Optimization/Design Sensitivity - PBEAM -
Errors occur in design optimization of beam elements if the following two

conditions are met:
1.) The beam section is constant (e.g., end b data is not supplied on the
PBEAM entry)
and
2.) End B data is referenced on a DVPREL1 entry.
By not supplying end B data, the code is mislead to believe the section is
constant, even if this is in conflict with information supplied in the design
model.
Avoidance: Supply end B data in the case of a tapered beam, and all necessary
intermediate stations in
the case of a variable beam section.
7338
69
SSSALTER - resflexa.v682
An error in the resflexa.v682 alter in sssalter directory may result in

loadings applied to the residual structure not being included in the residual
vector calculation.
Avoidance: Add the following line after the line containing 'type db,pss $'
TYPE DB,PL
7339
44
Nonlinear Transient Analysis - NLTRD2, ADAPT - SFM 4276 EC 10
Nonlinear transient analysis fails in the module NLTRD2 with the message
"SYSTEM FATAL ERROR 4276.OPEN
ERROR CODE 1044". This error happens when
the adapt method is used if
1. There are no nonlinear elements in the model.
2. Stress output is requested.
3. The NO field of the TSTEPNL entry is greater than 2.
Avoidance: Use the default (1) for NO field of the TSTEPNL entry.
7340
2004
DMAP - LTU - SFM 3001
User DMAP runs submitted with scr=yes may fail with SYSTEM FATAL MESSAGE 3001.
This error may result if the LTU logic deletes a datablock even though it is
still needed.
Avoidance: Run the job using SCR=NO or create a copy of the datablock and use
the copy in the DMAP alter.
7342
70
- Wrong Answers
Optimization/Design Sensitivity - STATSUB
Wrong buckling sensitivities may occur when the following conditions are true:
1. DSNOKD is nonzero,
2. The Subcase Control command STATSUB does not refer to the first subcase and
3. The referred subcase does not have retained responses of its own.
Avoidance: Define an artificial response with very large upper and lower
limits and force retention of the response in the referred subcase using
DRESP1, DCONSTR and DSCREEN entries.
7356
2001
P-Elements - DATAREC - UFM 6352
If a model contains output requests for p-elements (i.e., a DATAREC and OUTPUT
entry), but no p-elements are defined in the model, UFM 6352 may occur.
Avoidance: Either create a p-element in the model or remove the p-element
output requests.
7358
CRAY C90 Only
69.1
Installation - User Modifiable NASTRAN -
The CD for User Modifiable MSC/NASTRAN Version 68.2 contains errors in the
unicos and unicosc90 directories.
1) The unicos*/undynamic* files are misnamed. They are renamed as
follows:
mv
mv
mv
mv
unicos/undynamic_7X.o unicos/undynamic_70.o
unicos/undynamic_8X.o unicos/undynamic_80.o
unicosc90/undynamic_7X.o unicosc90/undynamic_70.o
unicosc90/undynamic_8X.o unicosc90/undynamic_80.o
2) The unicosc90/umnld script is incorrect. All references to

"unicos" must be changed to "unicosc90".
7365
ulation
Heat Transfer Analysis - VIEW3D, CHBDYE - No VIEW Factor Calc
The CHBDYE element references the conduction element for the geometry. If the
user attempts to calculate the view factor exchange between two plates by using
a line element such as a bar or rod and the CHBDYE element which references the
rod element for the surface information, then no view factor calculation will
be performed on the CHBDYE line element. .
Avoidance: Use the CHBDYP,LINE to model the surfaces instead of the CHBDYE
element.
7367
70
Documentation - Design Sensitivity/Optimi
zation, RBEi, MPC's, DVGRID - UFM 6499

It is a limitation of MSC/NASTRAN, that the sensitivities are incorrect for
shape optimization runs which have DVGRID entries which reference grid points
on MPC or RBEi entries. Often, the sensitivities are 0.0 and therefore the
following message is produced "ONE OR MORE VIOLATED CONSTRAINTS HAS A ZERO
GRADIENT **** NO PROGRESS IS POSSIBLE. OPTIMIZATION TERMINATED *** USER FATAL
MESSAGE 6499 (DOM9) THE DOT OPTIMIZATION ALGORITHM HAS ENCOUNTERED AN ERROR
THAT MAKES FURTHER PROGRESS IMPOSSIBLE. SEE MESSAGES ABOVE". This limitation
should be documented under the DVGRID entry.
Avoidance: It may be possible to replace the RBEi or MPC relation with an
element which has an extremely large stiffness.
7376
2004
p-Elements - CORD3G - SFM 6333 (EQNINI)
When a convective coordinate system (cord3g) is specified as a stress output

coordinate system in OUTRCV, sdr2 crashes with
BIOMSG: ERROR
211 HAS OCCURRED IN ROUTINE BLPK68 .
Avoidance: Other than not referencing a cord3g entry, there is no avoidance.
7380
69
URV,1 - User Output Coord. Systems
Documentation - QUAD4, PARAM,S1M, PARAM,C
QUAD4 corner stresses do not support output in a user defined coordinate system
using PARAM,CURV,1 and PARAM,S1M,1 and a MCSID coordinate system on a MAT1 or
MAT2 entry. The MAT1 and MAT2 Quick Reference guide documentation needs to be
updated as follows:
The MAT1 remark 7 needs to changed to:
7. MCSID must be nonzero if PARAM,CURV is specified to calculate stresses or
strains at grid points on plate and shell elements only. This feature does not
support QUAD4 corner stresses.
The MAT2 remark 6 needs to changed to:
6. MCSID must be nonzero if PARAM,CURV is specified to calculate stresses or
strains at grid points. This feature does not support QUAD4 corner stresses.
7391
69
6, Infinite Loop
Heat Transfer Analysis - RADCAV - SFM 427
In SOL 153, if global view factors are specified (i.e. the continuation entry
on the RADCAV is used), then the run may go into an infinite loop or issue
SYSTEM FATAL MESSAGE 4276 for some set definitions.
Avoidance: Do not use global view factors or redefine which elements are
contained in sets selected by the RADCAV entry.
7397
69
Documentation - QRG, APP COUPLED - Incorr
ect Reference to Thermal User's Guide
The MSC/NASTRAN Version 68 Quick reference guide makes the following
refererence under the description of the APP Executive Control Command:
APP COUPLED Indicates that a coupled analysis combining heat transfer and
structural analysis
in SOL 153. See the MSC/NASTRAN Thermal Analysis Users Guide.

In fact there is no description of the coupled thermal analysis in the Version
68 Thermal Analysis User's Guide.
7403
70.7
rner Stress Request
Optimization - PCOMP - UFM in SDRCOMP, Co
The presence of composites in SOL 200 when corner stresses are requested will
cause the following unnumbered fatal message in the SDRCOMP module:
USER FATAL MESSAGE. INCONSISTENT DATA DETECTED IN THE OES1A LAMINATE STRAIN AND
OEF1A ELEMENT FORCE DATABLOCKS
In V70.5 and later, an error message similar to the following may be output
instead from the SDRCOMP module:
*** SYSTEM FATAL ERROR 4276.GREAD
ERROR CODE
3001 PID=
Avoidance: Remvoe the CORNER, BILIN, SGAGE or CUBIC option from your STRESS or
FORCE output requests. However if noncomposite load responses are not used, the
following DMAP alters will allow noncomposite corner stress responses and
composite center stress and failure index responses to be used. But it will
cause non-composite force responses to fail.
7404
69
Memory, Excessive Runtime
p-elements - GP4 - SFM 3008, Insufficient
When converting a large h-element model directly to a p-element model, the run
may fail in GP4 with the following error messages:
SYSTEM FATAL
MESSAGE 3008 MODULE = GP4
0INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE CSTRAN
0FATAL ERROR
The runtime in GP4 will also be excessive. This error is most likely to occur
when there are many grid points which reference non-basic output coordinate
systems.
Avoidance: Other than increasing the memory on the mem keyword, there is no
other known avoidances. The amount of memory required for a large problem can
be substantial in this case.
7409
69
76. FREAD EC 3002
Heat Transfer Analysis - SOL 101 - SFM 42
Solution 101 heat transfer (app heat) superelement runs will fail in solution
101 with the following message:
SYSTEM FATAL ERROR 4276.FREAD
ERROR CODE 3002
Avoidance: Other than no running superelements there is no avoidance.

7410
rs
69
If the following EIGRL format
Eigenvalue Analysis - EIGRL - Wrong Answe
EIGRL,SID,V1,,ND
is used, and the first flexible mode is substantially higher than the rigid
body modes, then modes below V1 may also be included in the eigenvalue table
printout.
Avoidance: Either increase V1 or include a shift scale that is close to the
estimated first desired mode.
7414
Optimization/Design Sensitivity - Poorly Labeled Output
It is difficult to relate the output in solution 200 (DISPLACEMENT, STRESSES,

SENSITIVITY, ETC ) to the design cycle. The output headers do not include the
design cycle number for which the output is printed.
Avoidance: Look for the "USER INFORMATION MESSAGE 9051" , which contains the
design cycle information preceding the output.
7425
DMAP - CALL - Incorrect PARAM Value Passed Back
If a parameter is passed into a subDMAP on the CALL statement, it is possible

that the program may pass a value of 0.0 back to the calling subDMAP for that
parameter. This has only been observed if the following conditions are met:
1) The parameter appears on the CALL statement without the 'S' feature
2) The parameter is defined as being able to be changed in the bulk data or
case control ( 'Y' option on
the TYPE statement in the called subDMAP')
3) The same name is used for the parameter in the calling and called subDMAPs
4) The value of the parameter is changed in the called subDMAP
Avoidance: Change the name of the parameter in the called subDMAP or use the
'N' option on the TYPE statement in the called subDMAP.
7428
70
RDSi - Wrong Answers
Documentation/Elements - CGAP, CORDCi, CO
If a cylindrical (CORD1C/CORD2C) or spherical (CORD1S/CORD2S) coordinate system

is specified for a gap element (CID field of CGAP entry), and one of the
connected GRIDS is defined at the center of that coordinate system, wrong
answers result. Wrong answers result, even if the GRID at the center of the
coordinate system is defined in a cartesian system.
Avoidance: Displace the GRID at the center by as little as 1.E-40 in the
direction of the desired gap axis, or define the v vector and leave the CID
field blank.
7452
69
ssing Datablock CHISTM from xdb
Postprocessing - Optimization, TRANS - Mi
MSC/NASTRAN Version 68.2 on CRAY computers fails to write the CHISTM datablock
to the .xdb file. An incorrect xdb will show the following when the resulting
xdb file is written to neutral format with the TRANS utility:
.
.
DATA BLOCK
CHIST
CQD4
PROJECT
1
1
SE ID
0
0
PATH
1
1
SUBCASE
0
0
SET ID APPROACH
0
0
0
0
CQD4
CQD4
CTAB
CTAB2
DCYCT
1
1
1
1
1
7454
69
MP(LOAD) - SFM 4276, EC 7777
0
0
0
0
0
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
Nonlinear Analysis - PLSOLID, PLPLANE, TE
Hyperelastic elements with temperature loads do not work on MSC/NASTRAN Version

68 Alpha OSF/1 system. All
jobs with temperature loads and hyperelastic elements will fail with the
message "SYSTEM FATAL MESSAGE 4276, ERROR CODE 7777" in the NLITER Module.
Avoidance:
Other than running on another machine there is no avoidance.
7460
69
SUBCOM - SFM 3007
The message, "SYSTEM FATAL MESSAGE 3007 MODULE = DSAL" is produced if:
(1)there are active DRESP1 responses associated with composites
(CSTRESS,CSTRAIN,CFAILURE), (2) SUBCOM's are used and (3) One or more of the
subcases used in the SUBCOM has no active responses.
Avoidance: An avoidance is to add responses in the subcases referenced on the
subcom and force their
retention using DSCREEN.
7462
wers
69
Heat Transfer - CHBDYG, RADBC - Wrong Ans
If a negative EID is specified on the RADBC entry to indicate that the

boundary condition is to be applied to the back face of the element, then the
load applied is incorrect and wrong answers result.
Avoidance: Define another CHBDYG or CHBDYE on the backside and use it to apply
the load.
7463
70.5
ient Processing
Stress Discontinuities - STDCON - Ineffic
The STDCON module can be very inefficient. For some problems, enhancements in
Version 70.5 have improved the performance of this module by several orders of
magnitude.
7464
69
POI) Preliminary edge table
P-Elements - CQUAD8, CTRIA6 - SFM 6398 (G
If there are h-element CQUAD8s and/or CTRIA6s next to p-elements, and there are
midsides on the common edges, the following message may result:
SYSTEM FATAL MESSAGE 6398, (GP0I),
PRELIMINARY EDGE TABLE CREATED IN GP0B IS INVALID.
USER ACTION:
CONTACT CLIENT SUPPORT AT MSC.
The error message should be more specific. The error is considered corrected
in Version 69 by issuing the following message:
USER FATAL MESSAGE 6544, (GP0I),

THE EDGE WITH GRIDS ID = **,
** ON P-ELEMENT ID = ** IS SHARED BY
AN H-ELEMENT WITH MID SIDE GRID.
7469
2001.0.1
M 4276 EC 3001, Poor Message
Frequency Response Analysis - Random - SF
In a random analysis, the J and K fields (fields 3 and 4) on the RANDPS entry
should reference the subcase identification number, as documented in the Quick
Reference Guide. However, if the J and K fields reference the subcase sequence
number instead, the job will fail with the following unclear messages.
0
ERROR CODE
, FILE INDEX (FILEX) =
3001 PID=
Avoidance: Modify the J and K fields on the RANDPS entry to reference the
appropriate subcase identification numbers.
7470
69
S4 - Wrong Answers
Geometric Nonlinear Analysis - ELAS3, ELA
CELAS3 and CELAS4 elements produce wrong answers in SOL 64.

Avoidance: Use CELAS1 or CELAS2 elements.
7476
in EMG
69
Heat Transfer - EMG, FTUBE, MATT4 - Quits
If the data on the TABLEM1 referenced by a MATT4 entry is poorly defined such
that the extrapolated viscosity versus temperature results in a negative
viscosity (which is physically impossible) then the run fails without message
in the EMG module.
Avoidance: Make sure that the viscosity versus temperature curve always
remains in the (+,+) quadrant.
7480
DMAP - Delivery Database Build - SFE 4276 in XCSA
When building a delivery database in more than one run, if any subDMAP fails
compilation in the first run, which also compiles the NDDL, then a subsequent
run may fail with BIOMSG error 3001 in GREAD and SYSTEM FATAL MESSAGE 4276 in
XCSA.
Avoidance: If this message is encountered, the delivery database is corrupted
and must be rebuilt. To avoid corrupting the database again, do not compile
any subDMAPs in the first run.
7481
NKER
DMAP - Delivery Database Build - Poor Message, SFE 4276 in LI
When building a delivery database in more than one run, if a subDMAP which is
called by a main subDMAP fails during compilation in one run and then a link of
the main subDMAP is attempted in the next run, then the run will fail with
BIOMSG error 3001 in GREAD and SYSTEM FATAL MESSAGE 4276 in LINKER. The run
should have failed with USER FATAL MESSAGE 443 or 444.
Avoidance: Recompile the offending subDMAP and relink the main subDMAPs which
call the offending subDMAP.
7495
sive CPU
69
P-elements - VIEWP, TETRA, FEEDGE - Exces
For large models of TETRA p-elements with curved edges (i.e. FEEDGE bulk data
entries), the VIEWP module takes excessive CPU time. The time spent in the
VIEWP for TETRA p-elements with curved edges is approximately ten times a model
that does not have curved edges. The overall run time may be increased
approximately 30 percent.
7498
69
2079, SWM 2072
Transient Heat Transfer - DPD - UFM 2066,
If the grid points are given TEMP for the initial conditions without the use of
a TEMPD bulk data entry, then you the following error message is encountered:
USER FATAL MESSAGE 2079, GRID OR SCALAR POINT ******** HAS AN UNDEFINED
COORDINATE REFERENCED ON A NOLINI
CARD.
USER FATAL MESSAGE 2066, UNDEFINED GRID POINT
0 ON DAREA-, RLOAD- OR
TLOAD- CARD.
SYSTEM WARNING MESSAGE 2072, CARD TYPE
7107 NOT FOUND ON DATA BLOCK.
Avoidance: Add a TEMPD bulk data entry.
7511
g Answers
69
Eigenvalue Analysis - REIGL, EIGRL - Wron
In rare cases Lanczos may produce wrong answers and no warning message is
issued. MSC/NASTRAN Version 69 corrects this situation by issuing appropriate
messages.
Avoidance: Prior to Version 69, it is the user's responsibility to verify that
the actual eigenvalues found agree with all sturm checks. If the results do
not agree then they can not be correct. The eigrl entry should be modified by
increasing maxset to 15 from the default of seven and the job should be re-run.
Changing the frequency range of interest such that f1 is blank, not 0.0, often
corrects the problem.
7513
70.5
RESP2, PARAM,OPTEXIT - SFM 3001
Optimization/Design Sensitivity - DOM6, D
When only DRESP2 responses are defined in an optimization job, the requested
OPTEXIT=4 or -4 results in two different errors:
1. In Version 68.x, SYSTEM FATAL MESSAGE 3001 occurs in DOM6.
2. In Versions 69 and 70, the DSCM2 matrix is not generated in an f06 file.
Avoidance:
There is no avoidance for v68.x. A dmap avoidance is available for v69 and
v70:
compile exitopt
alter 'if ( ((','if ( (('
if ( ((dsprint or dsunform or dsexport) and mdtrkflg=0) and
(NORSP2>0 or nodscmg>0) ) THEN $
endalter
7515
69.0.4
OADSET/LSEQ - Wrong Answers
Direct Transient Analysis - CBAR,PLOAD1,L
In a direct transient dynamic analysis, if a CBAR element is loaded by a PLOAD1

entry through the LOADSET/LSEQ combination, then the output titled "force
distribution in bar elements" will be wrong.
1. Replace the CBAR element with a CBEAM element.
2. Replace the PLOAD1/LOADSET/LSEQ combination with equivalent point loads
using the DLOAD/TLOADi/DAREA
combination.
7518
70.5
GCORD,BASIC - Missing Output
Post-processing - PARAM,POST,-5, PARAM,OU
If PARAM,POST,-5 is specified with PARAM,OUGCORD,BASIC then PARAM,POST,-5 is

effectively ignored and the expected output will be missing.
compile sedrcvr
alter 'ELSE IF ( NOT(post',''
ELSE IF ( post>-3 and PATVER<3. and OUGCORDX='BASIC' ) THEN $
7539
UFM 2166
69
Optimization/Design Sensitivity - PARTN -
If a statics and a modes subcase are attempted in the same geometric shape
optimization run, then the following fatal message is issued, "USER FATAL
MESSAGE 2166, MATRIX TO BE PARTITIONED IS OF SIZE 22806 ROWS BY 7 COLUMNS. ROW
PARTITION SIZE IS 22806 COLUMN PARTITION SIZE IS 5 (INCOMPATIBLE)."
Avoidance: Include the following DMAP avoidance:
compile bndshp nolist noref
alter 'shpcas'
type parm,,i,n,nt $
MDCASE
CASEXXu/
CASESTAT,,,,,,,,,,,,,/
S,N,STATCC $
tabpt casestat/ $
paraml casestat//'trailer'/1/s,n,nstat $
paraml ygbndr//'trailer'/1/s,n,nyg $
nt=nstat+nyg $
delete /cvec,,,, $
matgen ,/cvec/6/nt/nstat/nyg $
7542
69
DOM9 - Unexpected EOF in DOM9
If a data deck has multiple weight or multiple volume responses that are
referenced by the objective or are
constrained, unexpected results occur and the answers are wrong. System Fatal
Messages such as "Unexpected end of file in DOM9" may also occur.
Avoidance: Remove the multiple DRESP entries.

7546
- SFM 7127
69
In an optimization run, if a series of DRESP1 entries makes alternating

references between different types (such as PSHELL and ELEM) in the PTYPE
field, then the message "SYSTEM FATAL MESSAGE 7127 (DOPR3B) AN ELEMENT WHICH
REFERENCES PTYPE **** ** PID *** IS NOT DEFINED IN THE ANALYSIS MODEL" is
issued.
Avoidance: Put all DRESP1's that reference a particular type in consecutive
order, where the order is given by the DRESP1 ID.
7547
Documentation - Slip Ratio - Reference Manual
Documentation that defines the meaning of "Slip Ratio" for gap and slideline
elements does not exist. The following paragraph should be added to the
Section 15.3.12 of the Reference Manual.
The slip ratio is defined as the (shear force)/(coefficient of friction *
normal force). Thus, a ratio of 0.0 indicates no shear (or no contact), a slip
ratio of 1.0 indicates slipping, and a value in between 0.0 and 1.0 is a
normalized value which indicates how close to impending slipping the shear
force is."
7550
69
ODEPT - Parameter not set Correctly
Optimization/Design Sensitivity - PARAM,M
The MODEPT parameter in SOL 200 is intended to indicate whether the design
model EPT (element property table) differs from the analysis model. There are
a number of implementations errors associated with this parameter:
The DOPR1 module has an error which results in the MODEPT parameter being set
to true only when the FINAL
designed property differs from the analysis value.
The DESOPT driver does not correctly pick up the MODEPT value set in subDMAP
PREDOM because of an error
in the call to PREDOM.
The design intent should be that the EPTN datablock is only equivalenced to EPT
when MODEPT is true. Currently it is always equivalenced with the results that
the finite element analyses on the
database gets destroyed on a restart when they should not.
7552
69
the icons on Beta NT systems
Installation - MSC/NASTRAN will not make
For Windows NT Version 4.0, which is the Windows 95 interface on top of Windows
NT, the installation of MSC/NASTRAN will not create the icons or group for the
Beta versions of this Operating System.
Avoidance: Do not upgrade your operating system to 4.0 until the non Beta
software is available. Or manually create the group (MSC) and create the icons
in the group.
7553
3002
70
Restarts - - PBCOMP - SWM 2072 CARD TYPE
If a model contains a pbcomp entry, and a restart is performed going from SOL
103 to SOl 111 on a DEC
AlPHA OSF machine, then the job may terminate with the following messages in
the f06 file.
SWM 2072 - CARD type 3002
On some DEC ALPHA machines, no messages may appear in the f06 file. In all
cases, the following messages appear in the log file:
1. Perform the analysis in one pass using solution 111 without using solution
103 for restart.
2. Replace the PBCOMP with an equivalent PBEAM entry.
3. Replace the PBCOMP record in the NDDL with the following:
RECORD=PBCOMP(5403,55,349),
PID,I, MID,I, A,RS, I1,RS, I2,RS, I12,RS, J,RS, NSM,RS, K1,RS,
K2,RS, M1,RS, M2,RS, N1,RS, N2,
7555
68.2.9
Floating Operation
Miscellaneous - PUNCH - SFM 4276, Invalid
A request for PUNCH output may result in the following traceback on Fujitsu
computers running MSC/NASTRAN Version 68.2:
jwe0292i-e Invalid floating operation exception was detected.
execution mode = advanced
error occurs at ofppun_ line 156 loc 00857c10 offset 00001800
ofppun_
at loc 00856410 called from loc 0083be68 in ofp_
1340
ofp_
at loc 008366f0 called from loc 00006eb8 in xsem14_
124
xsem14_
at loc 00006850 called from loc 00000928 in MAIN__
108
MAIN__
at loc 00000500 called from o.s.
taken to (standard) corrective action, execution continuing.
line
line
line
Avoidance: The error can be avoided by setting system(210)=1. It is

recommended that this system cell be set in the system rc file of all F
7556
70
onse of Rigid Body Modes
Documentation - Frequency Response - Resp
When an excitation is made at zero frequency for a model with rigid body modes,
the contribution from the rigid body modes (which is theoretically infinite) is
discarded. Only the finite modal displacements from modal DOFs with non-zero
natural frequencies are retained. An xy plot of element stresses from zero to
small excitation frequencies will be continuous. An xy plot of displacements
will grow rapidly as zero excitation frequency is approached, then drop to
values of the same magnitude as response at frequencies away from natural
frequencies. The solution at zero frequency is analogous to an inertia relief
solution, while the other solutions are made in an inertial basis. The
following remark should be added under the FREQi entries:
Remark 4. In modal analysis, solutions fo

7557
efault
70
Documentation - PBCOMP, I12 - Incorrect D
The default value for the I12 field of the PBCOMP entry is 0.0 and not
I1*I2-(I12)**2 as described in the MSC/NASTRAN Quick Reference Guide. The
correct description for I12 is as follows:
I12
Area product of inertia. See Remark 6. (Real, default=0.0, but
I1*I2-I12**2 > 0.0).
7561
70
Documentation - BUFFPOOL - UFM 1286
Remark 2d in the section "How Can I Reduce the Size of the SCRATCH DBset?" of
the Common Questions and Answers Guide, Second Edition, should be changed from
d. Increase the available memory to the functional modules by setting the
"smem" and BUFFPOOL parameters
to zero......
to
d. Increase the available memory to the functional modules by setting the
"smem" parameter to zero......
Starting in Version 68, the default solver is the sparse solver. BUFFPOOL
cannot be turned off with the
sparse solver.
7564
69
OM, K2PP - SFM 4276 FREAD
When K2PP matrices or FREQ looping are present in random analysis, the RANDOM
module fails.
The problem has been identified as the wrong case control data block being
passed to the RANDOM module. The RANDOM module should get CASEXX instead of
CASECC. The following is a DMAP avoidance.
compile sol30 or SOL26
alter 'random',''
RANDOM XYCDB,DIT,PSDL,OUGV2,OPG2,OQG2,OES2,OEF2,CASExx/PSDF,AUTO/
S,N,NORAND $
7583
essages
68.2.8
Miscellaneous - INPUTT4 - Various Fatal M
MSC/NASTRAN may not be able to read INPUTT4 files on certain machines. Known
problem machines are Fujitu and DEC ALPHA. The Fujitsu systems gave the
following traceback in the INPUTT4 module:
error occurs
pack_
359
inptt4_
125
xsem02_
at pack_
line 113 loc 00e577b0 offset 00000360
at loc 00e57450 called from loc 00712bb0 in inptt4_
line
at loc 00711580 called from loc 000024c0 in xsem02_
line
at loc 00001e60 called from loc 00000868 in MAIN__
line 84
MAIN__
at loc 00000500 called from o.s.
error summary (fortran77 ex system)
While the DEC ALPHA OSF system completed but issued the following messages:
Unaligned access pid=15155 <analysis> va=14011d924 pc=1201febe0 ra=1201feb4c
type=ldt
Unaligned access pid=15155 <ana
7591
LL
70
Databases - MATREDU - Wasted Space in DBA
The module MATREDU is using the DBALL as its scratch space instead of SCR300 or
the regular SCRATCH space.
7599
69
ed in Case Control
Documentation - PARAM,TSTATIC - Can Be Us
The MSC/NASTRAN Version 68 Quick Reference Guide states that param,tstatic can
only be used in the Bulk Data section. It can be used in the Bulk Data and
Case Control.
7600
70.5
- Missing Roots
A complex lanczos eigenvalue analysis of a model with zero damping will likely
not find all the roots that are found by a real lanczos eigenvalue analysis
with the same shifts. Likewise in models with damping, complex lanczos is
likely to have missing roots.
Avoidance: The only avoidance is to add additional shift points. In Version
69.1 the epsilon has been adjusted so that correct behavior should be achieved
for real world models. Thus, a Version 69.1 run is likely to find more roots
then the same run in 69.0.
7615
70.5
DMAP - ALTER - UFM 3063
If a DMAP contains a long alter followed by short alters followed by a long

alter the following message may be encountered:
SYSTEM FATAL
MESSAGE 3063 MODULE = PREFACE
MEMORY ALLOCATION FAILURE IN SUBROUTINE XALTER ERROR CODE: -1
MEMORY CORRUPTION FOUND. PREVIOUSLY ALLOCATED MEMORY AREAS HAVE BEEN
INCORRECTLY MODIFIED.
USER ACTION: CONTACT MSC CLIENT SUPPORT.
Avoidance: There are two avoidances. The user can either re-arrange the
alters so that the long and short alters are placed together or split alters
that are more than 112 lines into smaller segments.
7616
69
essage, Wrong Answers
Aeroelastic Analysis - APD, PFAERO - No M
Specifying a theta-1 array and no theta-2 array for an aerodynamic interference

body may yield results that do not include all the interference body effects.
For example, if a PAERO2 specifies that an interference body has 3 elements, of
which elements 1 and 2 specify a theta-1 array, and element 3 does not, the
program will run and yield wrong results.

Avoidance: The wrong results can be avoid by properly specifying all
interference elements with a theta array.
7617
s
Loads - PLOAD2, PLOAD4 - SFM 2105, SFM 4577, Missing Element
If PLOAD2 or PLOAD4 entries specify a range of element ids with the "thru"
option and an element does not exist for each id in the range, the job will
fail with SYSTEM FATAL MESSAGE 2105 and SYSTEM FATAL MESSAGE 4577. This
limitation is not clearly documented and limits the usefulness of the thru
option and should be corrected.
7619
Documentation - Nonlinear Analysis Data Recovery Restarts
The current documentation does not make it clear how one should prepare input
files to perform data recovery restarts with a
nonlinear analysis. If the user expects to obtain any data recovery from
solution 106, 129, 153 or 129, the input file should be prepared to perform
the complete solution and not rely on the database to contain the necessary
datablocks. For example, flux output must be explicitly requested in the cold
start if one wants to obtain it on the restart. The user may specify
flux(plot) if he chooses not to see the printed output in the cold start.
7627
69
ormance, SFM 4276
Heat Transfer Analysis - VIEW - Poor Perf
Heat Transfer analysis that involves third body shadowing calculations for a
large number of surface element in the VIEW module may experience poor
performance or fail with the message SYSTEM FATAL MESSAGE 4276.
Avoidance: There is no guaranteed avoidance; however, if parallel processing
is being selected, deselecting parallel may avoid the problem. Furthermore,
even though the error is possible on all machine types a specific problem may
run on one machine but not another. Thus, running on another machine may avoid
the problem.
7632
FM 4287
70.7
Design Sensitivity - SENSITY, SOL 103 - U
Material sensitivity analysis in SOL 103 fails on Cray computers with the
following message, "USER FATAL MESSAGE 4287 , ILLEGAL THICKNESS FOR PLATE
ELEMENT ID = xxx".
Avoidance: Use SOL 200.
7633
69
re Convergence for Optimization
Optimization/Design Sensitivity - Prematu
As explained in Section 3.4 of the MSC/NASTRAN User's Guide for Design

Sensitivity and Optimization, a design task is considered converged if the
objective is not changing and the design is feasible. This has been found to
be sometimes unconservative in the case where the previous design was
unfeasible. That is, if the design changes from being infeasible to feasible
without a weight change, it may be that further iterations will produce a
further improvement in the objective.
Avoidance: If the next to last design was infeasible, as indicated by its
maximum constraint value being

greater that GMAX, it is worthwhile to start a new design task starting from
the final design of the
run using the DESVAR values from the punch file.
7637
ut
69
Case Control - ECHO=NOSORT - Missing Outp
If ECHO=nosort is used in the case control section, bulk data echo is not
printed to the output.
Avoidance: use ECHO=unsort.
7644
TRAN - UFM 315
GL
Transient Heat Transfer - CELAS2, TEMPBC,
In transient thermal analysis, if the user has CELAS2 entries in the input test
deck and there is also TEMPBC,TRAN bulk data entries, then the following fatal
message will be encountered:
0*** USER FATAL MESSAGE 315 (IFPDRV)
FORMAT ERROR ON BULK DATA ENTRY TEMPBC
CARD COUNT =
761
102
SORTED
This error occurs because the TEMPB,TRAN bulk data entry internally produce
CELAS2 entries for the large conductance method. These entries then conflict
with explicitly defined CELAS2 entries.
Avoidance: Instead of CELAS2 bulk data entry uses CELAS1,and PELAS to define
the thermal conductance value.
7655
70.6
OOP - Missing Eigenvectors
Nonlinear Eigenvalue Analysis - PARAM,NML
If a nonlinear normal modes analysis (param,nmloop) is requested in a SOL 106

run, and there are more than one subcase and the displacement output is not
requested for all the subcases, then the nth eigenvector will be missing for
the nth subcase that does not have a displacement output request. In the
following example, eigenvectors 1,3,4,5,6,7,8,9, and 10 will be printed.
Eigenvector number 2 will be missing.
sol 106
.
subcase 1
load 1
nlparm = 10
disp = all
subcase 20
load = 2
nlparm = 20
subcase 35
load = 3
nlparm = 30
disp = all
Begin bulk
.
param,nmloop,20
eigrl,10,,,10
.
Avoidance: Request displacement output for all subcases.
7659
69.1
DMAP - COMPILER - Various Failures
If an "ELSE" statement appears in a DMAP without a matching set of IF and ENDIF

statements, various random failures may occur. In one instance, a "FILPOS"
error exit was taken upon entering the subdmap where the error was made. In
another instance, a USER FATAL MESSAGE was issued indicating that there was "NO
MASS MATRIX AVAILABLE FOR EIGENVALUE ANALYSIS"."
Avoidance: There is no avoidance only the recommendation that the statements
inside if-endif clauses be indented to insure that all else statements are
bracketed by if-endif statements. DIAG 44 is also useful for pinpointing the
location of the error when this type of error is suspected.
7660
P-Elements/Superelements - GP4 - UFM 2101A
The following error message will be issued if a grid point appearing on a

p-element edge is constrained and
not in an upstream superelement.
*** USER FATAL MESSAGE 2101A MODULE = GP4
GRID POINT xxxx COMPONENT y ILLEGALLY DEFINED IN SETS
UM
UB
For superelements, there is a general restriction in p-elements for boundary

degrees of freedom ( exterior degrees of freedom in superelements). That is
there is an internal MPC created for SPCs on edges and faces (GMSPC, GMBC).
Consequently, the constrained degrees of freedom are subject to the rules for
MPCs. The dependent degrees of freedom (m-set) have to be in the upstream
superelement, they can not be exterior.
7668
ault
70
Documentation - PCOMP, TREF - Missing Def
The PCOMP bulk data entry description in the MSC/NASTRAN Quick Reference Guide
does not give the default for TREF field. The default is "0.0".
In addition, remark 3 would be clearer if instead of:
3. TREF given on the PCOMP entry will be used for all plies of the element; it
will override values supplied on material entries for individual plies. If the
PCOMP references temperature dependent material properties, then TREF given on
the PCOMP will be used as the temperature to determine material properties.
TEMPERATURE Case Control commands are ignored for deriving the equivalent
PSHELL and MATi entries used to describe the composite element.
it said the following:
3. The TREF specified on the material entries referenced by plies are not
used. Instead TREF on the PCOMP entry
7678
69
RANK DEFICIENT
Matrix Methods - Sparse DECOMP - UFM 6137
Sparse decomposition in Version 69 has been changed to all rank deficient,

singular matrices, to go through. The action taken is now the same as the old
active column decomposition, i.e., it puts a very small term on the diagonal
and proceeds with the solution. The user is then warned about the degrees of
freedom causing the high maxratio.
7680
69.1
- RSSCON - Wrong Answers
Rigid Elements and Multipoint Constraints
The RSSCON element produces wrong answers if the shell grid is not on the
straight edge connecting the two solid grids. This is evident because the
element in this condition will not pass a rigid body check.
The magnitude of the error is related to the magnitude of the offset. In
Version 69 an offset up to 5% of the height of the solid is allowed. The mpc
relations generated by the element are adjusted as if the grid point was moved
onto the straight line but the actual geometry is not adjusted.
Avoidance: Other than manually moving the grid points so that they line along
the straight line there is no avoidance.
In V69.1, the shell grid point is moved on to the straight edge connecting the
two solid grids if the shell grid lies close to the edge within a tolerance.
The tol
7682
69.0.2
Incorrect GRID IDs
Elements - RSSCON - UWM 6695, References
If a shell grid point lies outside the straight line between the two connecting
solid grid points when using the RSSCON element, then the following warning
messages will be issued.
*** USER WARNING MESSAGE 6695 (CONSSD )
RSSCON NUMBER aaa WILL MPC ONLY GRID bbb OF QUAD ELEMENT ccc TO HEXA
ELEMENT ddd
IT WILL NOT MPC GRID ddd; THE CORNER SHELL GRIDS MUST LIE ON OPPOSITE
EDGES OF A FACE
OF THE SOLID ELEMENT.
This is the proper message to issue; however, the error message may reference
an incorrect offending shell grid point "bbb".
Avoidance: Modify the shell grid point to lie on a straight line between the
two connecting solid grid points.
7685
ce Degradation
Performance - MPYAD, FBS - Increasing Memory Causes Performan
Increasing memory for a particular run may cause poor performance in sparse FBS
and sparse MPYAD. This problem is usually caused by poor method selection and
is considered a limitation.
Avoidance: Other than requesting less memory or forcing more efficient methods
(please see the MSC.Nastran Numerical Methods Guide) no avoidance exists.
7689
ages
69.0.2
Optimization - PBARL - Various Fatal Mess
The new capability in MSC/NASTRAN Version 69 which allows users to define their
own beam cross sections has two undocumented limitations. There is a limit of
250 user defined beam cross section types, and there is a limit of 7
dimensions, including the Non-Structural Mass (NSM) on user defined sections.
If either of these limits are exceeded various error types may be generated.
In optimization, the fatal message may be issued from the module DOPR1H, or it
may be issued from the API with the phrase buffer overflow.
Avoidance: Do not exceed the limits. The limits have been raised to 2000 beam
cross section types and unlimited dimensions on a beam section for the next
release.
7690
70.5
MATMOD Option 5
Example 3 of the MATMOD option 5 documentation is incorrect. This example shows

how to transform KGG from a global to a basic coordinate system. Following the
documentation results in the wrong matrix. In the SMPYAD shown, the last and
not the first TRANSG matrix should be transposed. However, SMPYAD will not let
you transpose the last matrix of a triple multiply, so you must transpose
TRANSG before SMPYAD. The incorrect and corrected documentation follow:
Incorrect:
matmod cstm,sil,bgpdt,,,/transg,/5//-1 $
smpyad transg,kgg,transgt,,,/kggbasic/3////1 $
Correct:
matmod cstm,sil,bgpdt,,,/transg,/5//-1 $
trnsp transg/transgt $
smpyad transg,kgg,transgt,,,/kggbasic/3//// $ No transpose flags set
7692
*)
70
Superelements - MATGPR - Overflow (*****
When using the enhanced superelement features (parts), the boundary points of
the upstream superelements may be sent downstream. Internally, these boundary
points are assigned very large ID numbers, numbers that are much larger than
the user can specify on the grid entries. These large numbers do not fit in
the format for the MATGPR module. If MATGPR is used with the enhanced
superelement, the IDs for these grids will be printed
as (*******). The matrix values are, however, correct.
Avoidance: Use MATPRN instead of MATGPR and use PARAM,USETPRT and the boundary
sequence table to identical the external degree of freedom.
7697
ATMOD-4
70
Heat Transfer - SPC - Poor message, UFM M
Currently the transient heat transfer analysis capability does not support
multiple SPC conditions. An analysis can only have one SPC condition apply
through all subcases. If multiple boundary conditions are attempted the message
"USER FATAL MESSAGE MATMOD-4" will be issued.
Avoidance: Multiple boundary conditions must be executed in separate runs.
7699
80
69.0.2
P-Elements - GP0, GMLOAD, FEFACE - UFM 63
If the GMLOAD entry references an FEFACE entry that is undefined the following
fatal message is correctly issued but the FEFACE ID is not properly identified.
USER FATAL MESSAGE 6380, (GP0F),

THE FEFACE ID =
0 REFERENCED BY GMLOAD
IS UNDEFINED.
Avoidance: There is no avoidance to make the code identify the incorrect

entries. The user must find and correct the input error.
7705
es
70
Documentation - EIGRL - Performance/Crash
The MSC/NASTRAN Version 69 Quick Reference Guide description of the EIGRL entry
documents a new parallel Lanczos capability. This new capability was not
documented in the Version 69 Release Guide because it did not meet MSC's strict
standards for quality. The capability and documentation has several errors:
1. The Quick Reference Guide fails to mention that the new capability is only
available on the CRAY and SGI
systems.
2. The following FATAL messages have occurred while using this capability:
*** SYSTEM FATAL ERROR 4276.SFUPFI
*** USER FATAL MESSAGE 815 (RDINIT)
(Note that bad answers have never been encountered as a result of this
capability.)
3. The purpose of this capability was to reduce the elapsed time. It has been
found that parallel lanczos
7706
69.1
SSSALTER - evds200a.v69 - UFM 149
If the evds200a.v69 sssalter is used, the job will fail with the following
messages:
*** USER FATAL MESSAGE
149 (LINKAR )
CALL STATEMENT IFPS IN SUBDMAP IFPL HAS AN ARGUMENT LIST OF DIFFERENT
LENGTH THAN THE CALLED SUBDMAP
*** SYSTEM INFORMATION MESSAGE 480 (SEMINT)
JOB TERMINATED DUE TO ABOVE ERRORS IN THE DMAP/NDDL LINKAGE EDITOR
(LINKER)
Avoidance: Replace the following statements:
type parm,,logical,n,noedom2,ambs9,nogoifp9,ngoxsrt9
type parm,,char8,n,dball9
$
call IFPS ,,bulk2/BULK9,
$
GEOM1Q,EPT,MPT,EDT,DIT,DYNAMIC,GEOM2,GEOM3,GEOM4,
GEOM1Q9,,MPT9,EDT9,DIT9,DYNAMIC9,GEOM29,GEOM39,GEOM49,
$
MATPOOL,AXIC,DEFUSET,DMI,DMINDX,DTI,DTINDX,PVTX,
7707
CFORCE Output
69.1
Nonlinear Analysis - CBUSH - Incorrect SP
Nonlinear static analysis does not include the effect of the CBUSH element
forces in the forces of single point constraint output.

7711
70
Time Command Terminated Abnormally
Frequency Response - SEUPPLOT - SFM 4276,
IF an SEUPPLOT request is made in solution 108, the job may fail with the
message time command terminated abnormally or, SYSTEM FATAL MESSAGE 4276.
Avoidance: Use SEPLOT instead of SEUPPLOT.
7713
69
s With No Message
P-elements - FEFACE, CIDBC, MODGM4 - Stop
In MSC/NASTRAN Version 68.2 on the DEC/ALPHA, if a secondary coordinate system

is referenced on a FEFACE (CIDBC field), then the job may terminate in the
MODGM4 module without any error messages. Another symptom of this error is the
generation of a core file in the submittal directory.
Avoidance: If feasible, do not reference a secondary coordinate system on the
CIDBC field.
7715
MA)
69.0.2
P-Elements - GMINTC, GMBNDC - SFM 6425 (E
On machines that enforce boundary alignment such as the HP 9000 the following
fatal message may be issued when the GMINTC entry is used:
*** SYSTEM FATAL MESSAGE 6425 (EMA).
THE KDICTP TABLE AND KDICTP TRAILER ARE INCONSISTENT.
This error does not occur on the IBM/RS6000 or the CRAY machines.
7716
Output
69.0.2
Miscellaneous - SYSTEM(210)=1 - Excessive
SYSTEM(210) can be used to correct punch errors on many systems; however when
SYSTEM(210)=1 is used on the Sun/Solaris machines, excessive output is
generated causing the .f06 and/or .pch file to be very large.
Avoidance: There are no known problems that require Sun/Solaris systems to set
system(210)=1. Thus, on this system do not specify SYSTEM(210)=1.
7717
69.1
lements, GP2 - SFM 3001
Database - Neutral File Transfer with p-e
The following message is issued when an attemt is made to load the neutral
database (created by dbunload) via sol DBTRANS. This error occurs only if the
database datablocks are related to p-element analysis.
SYSTEM FATAL
THE INPUT DATA BLOCK NAMED EQEXINS AT POSITION
2 DOES NOT EXIST.
Avoidance: There is a rather complex avoidance which requires an NDDL

recompilation; however, it is not deemed practical.
7718
69.1
Virtual Mass - MPRES - Wrong Answers, SFM
4276 EC 7777
If MPRES output is requested and PARAM,DDRMM,-1 is not specified wrong answers
or a SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777 may appear.
Avoidance: In Version 68 simply specify PARAM,DDRMM,-1. For Version 69 the
following alter from the sssalter library will improve efficiency and correct
the error.
$ FILE VMEA.V69
$ LAST REVISED 17 DEC 96 M. A. GOCKEL
$ VIRTUAL MASS EFFICIENCY IMPROVEMENTS, FOR SOLS 103,111,112.
$ FOR NAST69 DATED 10/18/96, WITH DEL. DB TIME STAMP OF 961018160119
ECHOOFF $
COMPILE SEMRM nolist NOREF $
ALTER 'CALL MGEN1','' $
$ MODERNIZE NAMES
EQUIVX MCHI/CEE/ALWAYS $
EQUIVX MCHI2/BEC/ALWAYS $
EQUIVX MLAM/MEE/ALWAYS $
EQUIVX MLAM2/MEC/ALWAYS $
EQUIVX GEG/GGE/ALWAYS $
CALL DBSTORE CEE,MEE,BEC,MEC,MAR//SEID/0/'
'/0 $ FO
7719
70.7
, TEMP - Wrong Answers
Material Nonlinear Analysis - HEXA, PENTA
In non-linear analysis the HEXA and PENTA elements will give incorrect results
if the element references a MATS1 or MATT1 or both and has a non-constant
temperature distribution. The displacements are correct. The center stresses
are correct. The Gauss/Grid Point Stresses have an incremental error which is
proportional to the temperature gradient.
7720
n
Documentation - MSC/NASTRAN Reference Manual - Wrong Dimensio
The dimensioning of the channel-section as shown on page 5.2.1-8 of the Version

68 MSC/NASTRAN Reference Manual is incorrect. The b value should only extend
to the median line of the web instead of all the way to the outside edge of the
web.
7728
Restart
69.1
Database - DBUNLOAD, DBLOAD - Inefficient
When a neutral database created by DBUNLOAD is migrated to CRAY and is dbloaded

for the purpose of a subsequent restart, the restart job goes through
unnecessary steps and recalulates the stiffness matrix.
7734
69.0.2
mulation for Beam Library I-beam.
Elements - BEAM, PBAR1 - Incorrect K2 For
The PBAR1 and PBEAM1 area shear factor term, K2, for the I-beam cross section
is incorrectly calculated. It is formulated to be the area of flanges divided
by the total area, when it should be 5/6 of this amount.
Avoidance: The error can be avoided by specifying the correct properties on a
PBAR or PBEAM entry or the user could add their own section. The error has
been corrected in MSC/NASTRAN Version 69.0.2. If you have already been
delivered 69.0.0 or 69.0.1, then 69.0.2 must be explicitly requested.

7735
69.0.2
ith TYPE REV - Wrong Answers
Heat Transfer - QVECT, CHBDYE or CHBDYG w
When QVECT loads are applied to CHBDYE or CHBDYG elements with surface type REV
and midside nodes, the orientation vectors are not calculated. This error
results in zero directional heat loads for this type of
element.
Avoidance: There is no avoidance. The error has been corrected in Version
69.0.2. Version 69.0.2 will not be automatically delivered to clients who have
received 69.0.0 or 69.0.1, it must be requested.
7737
69.0.2
SFE 4276 EC 3001
In certain cases solution 200 jobs that contain DRESP2 entries may fail in the
DOM9 module with the following error:
*** SYSTEM FATAL ERROR 4276.GREAD
ERROR CODE
3001 PID=
Avoidance: There is no simple avoidance. The error is corrected in

MSC/NASTRAN Version 69.0.2. Version 69.0.2 will not be automatically delivered
to clients who have already received Version 69.0.0 or 69.0.1. The client
should request this corrected version.
7738
70
Documentation - PBARL - Wrong Information
Figure 1 under the PBARL description on page 793 and PBEAML on page 810 of the
MSC/NASTRAN Version 69 Quick Reference Guide indicates TYPE=BOX where it
should be BAR and vice versa.
7740
G 3002
69.1
Superelements - SEP1X, RBAR, RBE2 - BIOMS
Superelements with RBAR and RBE2 elements may cause an error in the sep1x
module which results in the message "BIOMSG 3002" being output.
Avoidance: Replace the RBAR and RBE2 elements with other types of rigid
elements.
7742
Superelements - MIRROR, REPEAT - Possible Wrong Answers
When using the enhanced superelement features, if the mirror or repeat option
is used to generate a copy of a primary superelement, and any of the GEOM4-type
data (e.g., MPC, RBEi, SPCi, ASETi, OMITi, BSETi, CSETi, etc.) for the mirrored
or repeated superelement is modified as compared to the primary superelement,
then the answers may be wrong.
Avoidance: If any of the GEOM4-type data for the mirrored or repeated
superelement must be different than the primary superelement, create a new
primary superelement instead of using the secondary superelement.
7743
Work.
GL
Submittal - notify=yes May Not Appear to
If a user has set the message state to off, e.g., with the 'mesg n' command,
the notification message cannot be sent. This is most noticable when a job is
run in the background, as the notification message is the only positive

indication the job has completed. The user may receive no indication at all,
or may receive the cryptic message "permission denied" when the notification is
actually attempted.
Avoidance: The user must enable messages for the notification message to be
received under batch=yes.
7748
70
Miscellaneous - Authorization - UFM 3060
If the memory specified on the 'mem' parameter is too high, then MSC/NASTRAN
may abort with a UFM 3060. The MSCID printed will be 0:
0*** USER FATAL MESSAGE 3060, SUBROUTINE MODEL
- OPTION NAST NOT IN APPROVED
LIST.
SYSTEM DATE (MM/DD/YY): 11/11/96
SYSTEM MSCID:
0 (DECIMAL) 00000000 (HEXADECIMAL) SYSTEM MODEL
NUMBER:
-1 , SYSTEM OS CODE:
1
Avoidance: Reduce the memory request.
7757
tation Error
69.1
Documentation - 'symbol' Keyword Documen
The documentation for the symbol keyword in Section 4.1.2 and in Appendix B.1
of the MSC/NASTRAN Version 69 Configuration and Operations Guide (UNIX) is
incorrect. The correct syntax for the keyword is:
symbol=<symbolic_name>=<string>
where <symbolic_name> is the name of the symbol to be defined and <string> is
the value of the symbol.
The specific example in 4.1.2 should read:
SYMBOL=DATADIR=/dbs/data
The specific example in Appendix B.1 should read:
SYMBOL=DBSDIR=/dbs
7773
69.0.2
when submitted through at(1).
Miscellaneous - Job hangs on HP-UX 10.20
On HP-UX 10.20, an MSC/NASTRAN V69 job may hang if the job was run using the
at(1) facility. There are two ways to run a job using at(1), the most obvious
is to use the after keyword. Another is to create a queue command such as
submit=at -q %queue% -m -f %job% %after%
Once the job is submitted, it will hang in the limits special function with the
following error message
displayed on your window or sent in an email:
sh[29]: ulimit: The specified value exceeds the user's allowable limit.
Avoidance: This problem is corrected by inserting the line
unset MSC_ARGV
just before the line

%0% limits
in the file
<install_dir>/bin/nast69.lcl
7775
ambled
69.0.2
Plotting - PlotPS - Contour lines are scr
Contour plots are incorrect on the Solaris Version 69 system. These plots have
the contour lines going to the origin instead of to each contour point. The
effect is a set of vectors going from the origin to the contour points.
Avoidance: Use a post-processor such as MSC/PATRAN to view stress contours.
The error has been fixed in Version 69.0.2 and Version 69.1.
7776
Superelements - BSET - UFE 4156, Poor Message
When using the enhanced superelement capabilities introduced in Version 69,

only the boundary points can be assigned to the BSET degree of freedoms, and
this is the design intent. However, if any interior point on a part
(superelement) is assigned to the BSET, then the job will fail with the
following unclear error messages.
0*** USER FATAL ERROR 4156--- DIMENSIONS OR TYPE OF DATA BLOCK KLAAV ,
SUPERELEMENT
y
TRAILER=(
xx
xx
x
x xxx) ARE INCONSISTENT WITH SUPERELEMENT MAP.
Avoidance: If an interior degree of freedom on a part is desired to be placed

in the BSET, then assign that grid point to the ASET. Note that when using
parts (superelements), if a degree of freedom at a grid point is assigned to
the ASET, then all six deg
7780
B - UFM 453
70.7
Executive System - ACQUIRE, DBLOAD, ENDJO
If you specify the ACQUIRE NDDL, DBLOAD, and ENDJOB statements and the "del="
keyword on the submittal command then UFM 453 is issued.
Avoidance: Do not use the "del=" keyword. Add ASSIGN statements for MASTERA,
MSCOBJ, and MSCSOU.
7789
70
Superelements - PARAM,METHCMRS - UFM 3032
If superelements are present and PARAM,METHCMRS is specified for the residual

structure, then UFM 3032 will be issued stating that the program is unable to
find the selected set (EIGRL entry).
Avoidance:
Verify that the referenced EIGRL entry exists in the input file. If it does,
then include the following DMAP alter in the input file:
$
$ for V69
$
compile ifpl
alter 'call ifps'

TYPE PARM,,I,N,DOIT=0 $
CALL DBSTORE DYNAMIC,,,,//0/0/'MASTER'/S,DOIT $
$
compile semr3
alter 'REIGL.*CMKXX,CMMXX','REIGL.*CMKXX,CMMXX'
TYPE PARM,,I,N,OK $
CALL DBFETCH /DYNAMIC,,,,/0/0/0/0/S,OK $
REIGL
CMKXX,CMMXX,DYNAMIC,CASES,,,,USET,EQEXINS,SILS,VYXW/
CMLAMA,CMPHIXZ,CMMI,EIGVMATS,/
'MODE'/S,N,NOZSET////METHRS////////CMSET $
$
$ DMAP to fix error 7789 - V70.5
7791
IZ
70.5
Databases - DBLOAD, GP1 - SFM 307 in IFPS
If a neutral database is DBLOAD'ed and GP1 is executed without first running

IFP, then the job will fail in GP1 with:
0*** SYSTEM FATAL MESSAGE 307 (IFPSIZ)
THE NAME OF BULK DATA ENTRY CORD1C IS INVALID.
PROGRAMMER ACTION:IF THE ABOVE NAME IS A VALID BULK ENTRY,
THEN CHECK THE HASHING FUNCTION TABLE(S),
AND MAKE SURE THERE ARE NO "LOST" ITEMS.
0*** SYSTEM FATAL MESSAGE 3007 MODULE = GP1
0ILLEGAL INPUT TO SUBROUTINE IFPSIZ
0FATAL ERROR
Avoidance: Always run DBTRANS when DBLOADing a database.
7792
2007.0.0
FSI=3 - UWM 4260
Documentation - Reference Manual, PBEND,
The documentation in Volume 3 of the MSC/NASTRAN Reference Manual for USER

WARNING MESSAGE 4260, BENDING CHARACTERISTIC PARAMETER EXCEEDS RANGE OF
APPLICABILITY FOR ELEMENT ** indicates an acceptable range of .5 to 1.0. In
fact the acceptable range is .05 to 1.0.
7796
Missing Plots
GL
Superelements - PLOTS - Missing Features,
The "LABEL GSPC" and "LABEL EPID" are not supported with the new superelement
features in Version 69.
7798
ed by Default
Documentation - Parallel Processing EMA, SYSTEM(107) - Disabl
On most of the systems supporting parallel operation with MSC/NASTRAN, the

Parallel EMA function shows little or no performance gain over the non-parallel
EMA. Because of this, by default, Parallel EMA will be disabled on all
platforms for MSC/NASTRAN Version 69.
If a you wish to enable PEMA, you may do so by setting the MSC_PEMA environment
variable to a value of YES (the test for "YES" is case-insensitive). In this
mode, the standard SYSTEM(107) enable/disable tests for PEMA are active.
7799
69
Performance - Infinite Cpu Loop of Cray -
Missing Insufficient Space Message

On the Cray, if there is insufficient disk space in the directory that you
submit your job, then the job may be trapped in an infinite loop when
attempting to report the error message and shut down. Messages similar to what
is shown below, including "not enough space" or "no space left on device",
should appear in your log file. In version 69, the job will terminate with
similar messages as shown below, except the "not enough space" or "no space
left on device" message may or may not appear.
Process Id = <pid>
Attempting to bypass eie layer : Not enough space for cache pages
apparent state: unit 6 named <path>.f06
last format: (13X
,I8,
1H-,
8X,
10A
08 )
lately writing sequential formatted external
S
7808
69.1
ESPCH - Missing Output
If PARAM,DESPCH is set to a value greater than one, then there should be DESVAR
and GRID output in the punch file for every design cycle. However, in Version
69 the GRIDS are not punched.
compile desopt
alter 'dom12,',''
DOM12,
XINIT,XO,CVALO,PROPI,PROPO,OPTPRMG,HIS,DESTAB,
geom1,coordo,edom,mtrak/
HISADD,NEWPRM,,NEWDES/
DESCYCLE/OBJIN/OBJOUT/S,N,CNVFLG/1/OPTEXIT//
MDTRKFLG/DESPCH/MODETRAK/eignfreq $
Grid output for the last design cycle can be obtained by setting PARAM,DESPCH,0.
7814
P-Elements - GMBCs - Wrong Answers
When boundary conditions in shell p-elements are specified on an edge using a

global coordinate system, the answers become wrong for p=9 and the program
crashes for p=10. The answers are correct up to the order of p=8.
7818
o Message
Optimization/Design Sensitivity - TRD2, NOLINi - Quits With N
If a modal transient analysis is performed in Sol 200 (ANALYSIS=MTRAN) and the

job contains NOLINi entries, the job may abort in module TRD2 with no message
except a machine dependent message in the log file.
Avoidance: NOLINi entries are not supported in solution 200. The modal
transient analysis may be run in solution 112.
7829
M 1127
70.7
Restart - DBLOCATE read-only restart - UF
If the LOGICAL keyword is specified on the RESTART statement and the

corresponding database on the ASSIGN statement specifies a path for the MASTER
DBset which is different from the path in which the job is run then the DBALL
and any other associated DBsets will not be auto-assigned. For example, if an
input file is located at /home/zzz/test.dat, and the desired databases are
/tmp/fender.MASTER and /tmp/fender.DBALL, and test.dat contains:
ASSIGN abc='/tmp/fender.MASTER'
RESTART LOGICAL=abc
then only the MASTER DBset is attached and all other DBsets will have the
status of "OFFLINE" echoed in the
.f04 file. Also, UFM 1127 will probably be issued.
Avoidance: Move the DBsets to the same path that the job is run in or specify
ASSIGN statements for all
DBsets.
7832
Elements - PBAR - Missing Torsional Mass Moment
The BAR element in MSC/NASTRAN does not include a term for the torsional mass
moment of inertia in its formulation (even in the coupled mass matrix). This is
documented in the Basic Dynamics User's Guide, but not in the Quick Reference
Guide.
Avoidance: If torsional mass moments of inertia are needed, use BEAM elements
or provide the values using CONM elements.
7839
69.1
, Segmentation Fault
P-Elements - DBUNLOAD - SFM 4276, EC 7777
A DBUNLOAD of a database with p-elements may produce SYSTEM FATAL MESSAGE 4276
or a segmentation fault followed by a traceback.
7841
ory
69.0.2
DMAP - REIGL - UFM 6413, Insufficient Mem
The REIGL module was enhanced in Version 69 to allow a dmap writer to call it
without the input of a dynamics or casecc input data blocks. The data they
contain is input on some new parameters added to the end of the REIGL call. If
REIGL is run by itself, it quits with an "insufficient memory" error:
USER FATAL MESSAGE 6413 (DFMSA)
INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION.
USER ACTION : INCREASE MEMORY BY AN ESTIMATED 9401 WORDS.
Avoidance: An avoidance is to run reigl without case control inputs after a
call with the case control input. The first call will initalize a variable
properly for the second call. The first call could contain
a small set of matrices from matgen, for instance.
7844
69.0.2
entation Fault, Access Violation
Acoustic Analysis - ACMG - SFM 4276, Segm
Acoustic jobs may fail unexpectedly in ACMG. The error was discovered by
looking at the code, to our knowledge the error has never been encountered.
Avoidance: There is no avoidance. The error has been corrected in MSC/NASTRAN
Version 69.0.2. This release is not being shipped to clients who have already
received Version 69.0.0, it must be specifically requested.
7851
70
Buckling Analysis - SUPORTi - SFM 3011
When a SUPORT entry is present in sol 105 the following error message appears:
*** SYSTEM FATAL
MESSAGE 3011 MODULE = RBMG4
ATTEMPT TO WRITE A TRAILER ON FILE 201WHEN IT HAS BEEN PURGED
Avoidance: Replace the SUPORT entry with a selected SPCi entry. In Version 70
the suport entry is treated as an SPC which is consistent with solution 101
when param,inrel is not selected. This error occurs in sol 103 also.
7852
wers
70
Inertia Relief - DMIG, UACCEL - Wrong Ans
When using inertia relief without using the rigid body acceleration
(DMIG,UACCEL), and any one of the following entries
BNDFL, DMIAX, ELIST, MFLUID, RADCAV, RADSET, RADLIST, RADMTX, DMIG
is present in the input file, then a conventional static analysis is performed
instead of inertia relief. A symptom of this error is the printout of the URA
intermediate matrix will be missing. A review of the spcforce output will also
reflect that a conventional static analysis is performed instead of inertia
relief.
Avoidances: There are two possible avoidances.
1. Remove or comment out the above offending entries since they are not used
in a static analysis anyway.
or
2. Add the following dmap avoidances:
compile statrs $
alter 'paraml.*matpool' $
7854
DMAP - TYPE - Possible Wrong Values for Parameters
If a parameter is defined in the NDDL, and a DMAP "TYPE" statement declares it

as changeable in CASE CONTROL or BULK DATA ("Y") but not as an "NDDL"
parameter, then the program will incorrectly use the NDDL default
value and TYPE for the parameter. If the parameter is listed as a qualifier
(QUAL) in the NDDL, the default
value works correctly in the DMAP. For example, the following subDMAP in SOL
100
SUBDMAP TEST input/output
type parm,,i,y,maxit=10 $ parameter is in the NDDL, NDDL default = 4
type parm,,i,n,modacc=10 $parameter is in the NDDL, but "N" is used on the TYPE
type parm,,i,n,maxratio=1 $ parameter is in the NDDL as RS, but "N" is used on
the TYPE
type parm,,i,y,mesh=1 $ different type than NDDL
type parm,,i,y,seid=345 $ test a qualifier
$
RETURN
END
will resul
7855
69.1
Buckling - TAFF, PARAM,FOLLOWK - Tracebac
k
If a PARAM,FOLLOWK,YES is requested to include follower force affects to the
differential stiffness and loads that do not exist are referenced the job will
stop in the TAFF module and the following traceback will be issued in the log
file.
Traceback:
Offset
Offset
Offset
Offset
Offset
0x000000ac
0x000000e8
0x00000684
0x000002d0
0x00000950
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
tafest_
tafldt_
taff_
xsem10_
mainal
Avoidance: Remove the reference to the loads that do not exist.

7856
69.1
ESTIMATE Utility - Missing GRID Entry
The ESTIMATE utility may flag GRIDs as missing when in fact the GRID entries
are present. The error occurs when a line that exceeds 80 characters precedes
an otherwise valid line. Under certain circumstances, the valid line may be
skipped.
Avoidance: As a work around, delete all trailing blanks from the data file,
expand all tabs to spaces, and
truncate any lines exceeding 80 characters.
7857
69.0.4
Superelements - SELA - SFM 4276, EC 1200
Superelement jobs may fail in module SELA with the message SYSTEM FATAL MESSAGE
4276 ERROR CODE 1200. Encountering the error is dependent upon the size of the
load vector and the amount of memory requested.
Avoidance: Increase memory and re-run the job.
7860
68.2.8
SFM 4276, EC 7777
Optimization/Design Sensitivity - FRRD2 -
Solution 200 with analysis=dfreq may fail in the FRRD2 module with the message:
ERROR CODE 7777
The log file may contain a traceback from subroutine frrd2.

Avoidance: The error has been corrected in Version 69. It has also been
corrected in Version 68.2.8, a re-release for Fujitsu systems.
The following
DMAP avoidance may also be applied that replaces FRRD2 with FRRD1:
compile fea list noref $
$ 285 FRRD2 CKDD,CBDD,CMDD,,PDF,FOL1/DETA/0.0/0.0/0.0 $
$ FRRD1
CASES,DIT,CKDD,CBDD,CMDD,K4DD,PDF,FRL,FOL/
$ UDVF/SOLTYP/0 $ RF8 - FRRD /UDVF
alter 'FRRD2
CKDD','' $
frrd1 casers,dit,ckdd,cbdd,cmdd,,pdf,frl,fol1/deta/'direct'/0 $
7871
g Output
70
Heat Transfer Analysis - GPFORCE - Missin
GPFORCE output is missing for steady state heat transfer analysis, SOL 153, in
Version 69.0.
Avoidance: Place the following alter in Version 69.0.
compile sedrcvr list$
alter 299,299 $ V69.0.2
IF ( GPFDR ) THEN $ GRID POINT FORCE
7874
h File
2001
Miscellaneous - Extra plot request - Punc
If an output request has two plot requests, e.g.,

disp(plot,plot) = all
then in addition to the plot file, a punch file containing the referenced
quantities will
also be generated.
Avoidance: Remove the extra plot request.
7875
01
69
P-Elements - GP1, GMCORD, GMLOAD - SFM 30
If a GMLOAD references a GMCORD in Version 68.2, then the job will fail with
the following error messages.
*** SYSTEM FATAL
THE INPUT DATA BLOCK IN POSITION
5 DOES NOT EXIST.
Avoidance: Use a CORDij instead of GMCORD when using GMLOAD.
7878
Optimization/Design Sensitivity - TEMP - Wrong Answers
An optimization job may yield wrong sensitivity results when temperature loads
are applied but certain designed elements (either DVGRIDs or DVPRELi) are not
temperature loaded.
Avoidance: A possible avoidance is to add a small temperature load on unheated
elements in Version 68.2.
7881
69.1
- Missing tables in .xdb file
Postprocessing - PARAM,POST,0 in SOL 200
Design sensitivity coefficient tables ( R1SEN and R2SEN datablocks) are missing
from the XDB.
Avoidance:
1. Copy the nddl.dat file from the MSC/NASTRAN DEL directory.
2. Replace the DATABLK r1MAPR and R2MAPR statements with the following.
DATABLK R1mapR TYPE=TABLE
EOF
DATABLK R2mapR TYPE=TABLE
EOF
PATH=geomi,
LOCATION=DSOr,
PATH=geomi,
LOCATION=DSOr,
3. Insert the following in your executive control section above all compile
statements:
compile nddl noref nolist
incl nddl.dat
7892
69.1
r Gives Wrong Answers
Matrix Methods - SOLVIT - Iterative Solve
If the solvit module is given a diagonal matrix it returns a null output

matrix.
Avoidance: Add at least one small off-diagonal term.
7893
69.1
the SEPLOT Command
Plotting - SEPLOT - UFM, Problems Parsing
When plotting superelements, the SEPLOT module may have problems parsing when
the command extends multiple lines. This may lead to a USER FATAL MESSAGE
pointing at the SEPLOT command.
Avoidance: If possible put the plot command all on one line. If not possible,
rearranging the command may help.
7903
70.5
K - Misleading Documentation
Documentation - QRG, SYSTEM(148), DBVERCH
The MSC/NASTRAN Quick Reference Guide documentation for SYSTEM(148), a.k.a.

DBVERCHK, states that this system cell permits restart from a pre-Version 69
database into Version 69. This system cell simply bypasses the check in
MSC/NASTRAN that ensures the Version of the database is the same as the Version
being executed and to that extent it is applicable to all Versions of
MSC/NASTRAN. The system cell does nothing to make the databases compatible.
Avoidance: In general databases are not compatible between Version 68, 69 or
70. The only way to restart is to perform a DBUNLOAD and a DBLOAD:
Step 1: Unload database in V68
assi dbunload='______.u68'
dbunload
endjob
Step 2: Load V68 database into V69
assi dbload='______.u68'
dbload
$
sol dbtrans
18854
fety
Postprocessing - PARAM,POST,-1 CBAR - Incorrect Margins of Sa
PATRAN P3 will display margin of safety results for bar elements even though no
allowables were specified in the analysis.
Avoidance: Either specify allowables or ignore the results.
25363
69.1
utput Printed to the Screen
Miscellaneous - NOTIFY=YES - Extraneous O
Extraneous output will be written on Cray (and others?) when submitting a job.
The text "is y" or "is n" may appear on the screen just after the system ID
line is written as shown below:
mwali[136]: nast69t2 d10101d bat=n app=y scr=y
MSC/NASTRAN V69.0t2 (CRAY UNICOS 8.0.4.2) Tue Dec 17 09:12:20 1996
is y
MSC/NASTRAN beginning job d10101d.
This is the output from the mesg(1) command. This output should have been
captured by the nastran driver, and will result in the nastran driver not being
able to warn to user if they set notify=yes and their current message state is
"n".
25365
fault
70
Statics - DCMP, SGI R4400 - Segmentation
In Version 69, when running a large problem on the SGI R4400, if there is
insufficient memory allocated for SPARSE DECOMP, then the job may fail with no
error messages in the f06 file. A symptom of this error is the printout of the
following unclear message in the log file.
Receiving signal number 11: Segmentation fault.
Note that in Version 69 sparse decomp is designed with an enhanced spill logic
so that it should be able to execute in significantly less memory.
Avoidance: Increase the memory substantially to avoid spill.
25375
69.0.2
- SFM 4276, EC 7777
DMAP - Complex Double Precision Functions
Double precision complex functions in DMAP cause the following error on the HP
9000/800 Version 69.0.0 release of MSC/NASTRAN.
ERROR CODE
7777 PID=
Avoidance: Set nastran system(100)=255 or request Version 69.0.2 where this

error has been corrected.
25377
2004
Documentation - MATMOD option 25
matmod option 25 dmap dictionary article incomplete

This option is designed
matrices (form 1). For
output. This condition
set to -1 for symmetric
25378
ams
69.1
to produce two output vectors for only unsymmetric

symmetric matrices (form 6) only the O1 vector is
can be detected by the sym output parameter, which is
matrices, and 0 for unsymmetric matrices.
ACCESS - Cannot Build ACCESS Sample Progr
Any attempt to build the ACCESS sample programs will fail with the error
message:
make: Cannot find a rule to create target sol301.o from dependencies.

This error can be corrected by taking the revised makefile from Scopus tan
2523, or editing the
file <install_dir>/msc69/access/makefile:
Change the line:
build: nastran emas ddl
to
build: nastran ddl
Remove the trailing backslash in SECOND line of the following two:
install: $(EXE)/demo1 $(EXE)/demo2 $(EXE)/smplr
dlprt $(EXE)/ddlqry
$(EXE)/d
And delete the immediately following line:

$(EXE)/sol301 $(EXE)/sol302
25379
70
AL TERMS ENCOUNTERED
Matrix Methods - DECOMP - UWM ZERO DIAGON
In MSC/NASTRAN Version 69, if the decomp module runs out of memory and the
DECOMP parameter is set to 4 or 32, incorrect warning messages may be issued
that indicate "ZERO DIAGONAL TERMS ENCOUNTERED". The message that should be
output is:
USER FATAL (or WARNING) MESSAGE 6413 (DFMSA)
INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION.
USER ACTION : INCREASE MEMORY BY AN ESTIMATED XXXXX WORDS.
Avoidance: Increase the memory and re-run.
25422
69.1
UFM 4551, Failed Convergence
Static Nonlinear Analysis - PARAM,KDIAG -
In nonlinear analysis (SOL 106), if the model has zero stiffness in the
undeformed configuration, then the solution may fail to converge or it may
converge to a wrong answer. This error first appears in Version 69, and is
associated with an error in the "KDIAG" processing.
Avoidance: Put PARAM,KDIAG,-1.-30 in the input file to avoid the error or
apply the following alter:
in NLSTATIC replace statement
ADD5
KAAL,KLLTX,KLLRH,,/KAALX///-1. $
with the statement
ADD5
KAAL0,KLLTX,KLLRH,,/KAALX///-1. $
25423
entified
69.1
Installation - SGI IP19 is Incorrectly Id
The Silicon Graphics IP19 system is an R44 system, but is able to run IRIX64.
SGI had categorically claimed that IRIX64 would *only* be found on R8/R10
systems. As a result of the presence of IRIX64, M/N V69 will attempt to run
the incompatible R8/R10 executable.
An IP19 system can only run the "irix" executable.

The work-around for V69.0.2 is to:
1) Modify the shell script "<install_dir/bin/msc69" and change the case label
"IRIX" to "IRIX*".
Note, this will leave the succeeding "IRIX64" case active, but ineffective.
2) Modify the file "<install_dir>/bin/nast69.ini" to include the line:
s.arch=irix
This error should not occur in V69.0.0 or V69.0.1. If it does, the solution is
identical.
25425
69.0.4
brary Optimization is Inefficient
Optimization/Design Sensitivity - Beam Li
Beam Library optimization is inefficient. For a model with 1000 designed

properties, a speedup of a factor of 70 has been demonstrated. The poorly
performing modules are DOM6 and DOM9. MSC/NASTRAN Version 69.1 corrects this
inefficiency.
25439
69.1
brary - Incorrect Sensitivities
Optimization/Design Sensitivity - Beam Li
If the design optimization feature of the beam library is utilized with

multiple designed stress recovery points, the sensitivities may be in error.
The error is most likely to show up when the stress recovery coordinate (e.g.,
C1 or C2) is not a function of all the designed dimensions. This error can
occur for both the MSC provided sections and for user provided sections.
25451
ound
69
Submittal - Windows NT - Input File Not F
Version 68 of MSC/NASTRAN on Windows NT must have .dat extensions specified for

input files. This error has been fixed in Version 69.
25456
69.1
- Zero Gradients
It is possible to generate the message "Zero Gradients of Violated Constraints"

in error if both the lower and upper bounds of a constraint are active for the
DOT optimization algorithm and if the underlying response was generated using a
DRESP2 entry. This condition will produce a fatal message and the job will
terminate. In other cases where both constraints are active, the optimizer may
become confused, but it will not terminate.
Avoidance: Be careful when specifying tight limits on a DRESP2 entry and be
aware that this may lead to difficulty. The error has only been diagnosed when
using the SQP algorithm (METHOD=3 on the DOPTPRM entry).
25470
69.1
NREL - Poor Performance
Optimization/Design Sensitivity - PARAM,I
Calculation of design sensitivities for static subcases with inertia relief can
be CPU intensive.
Avoidance: A DMAP avoidance is available.
25472
69.1
s fatal messages or wrong answers
Inertia Relief - SOL 200, INREL - Variou
If the value of PARAM,INREL is specified differently in one or more subcases,

then various fatal messages
will be issued or wrong answers may result.
Avoidance: Do not specify PARAM,INREL in the Case Control. Always specify in
the Bulk Data.
25501
70
Superelements - SEPLOT - Missing Plots
If there are no SEMOVES, REPEAT, or MIRROR superelements in the deck and if

there is a CSTM in a substructure there is a possible memory error causing the
substructure not to get plotted or if plotted not in its correct orientation.
Avoidance: If the user is missing plot output of a substructure or suspects
that it is in the wrong location put in a dummy semove substructure and the
problem should go away.
25531
May Fail
70
Submittal - Remote Execution via 'node='
The ability to run an MSC/NASTRAN job on a remote system using the 'node'
command line keyword will fail in Version 69.0 if the command is not named
'nastran' on the remote system. The nastran command is supposed to use the
actual command name used to run the job on the local system when running the
job on the remote system. The V69.0.X release will only use the generic
'nastran' command name on the remote system.
Avoidance: To correct this problem, the generic nastran name must be available
on the remote system.
25532
69
BLED1 - Possible Wrong Answers
Miscellaneous - Large field format for TA
The correct specification of a long-field format entry requires a blank entry

to be included for blank fields. For example, fields 4 thru 9 of the TABLED1
entry are not used, thus the correct specification of a long-field formatted
TABLED1 entry requires the second entry to be blank. In Version 68, if this
rule is not followed for the TABLED1 and x-y pair data is specified on the
second entry the data is ignored. The program performs a linear interpolation
from the data on subsequent entries for the ignored region and this is not
likely to be the intent of the user. Version 69 corrects this error by issuing
"USER FATAL MESSAGE 315 (IFPDRV)".
Avoidance: An example of an incorrect entry and the correct specification
follows:
TABLED1*1
25545
4276, EC 7777
69.1
Eigenvalue Analysis - REIGL, EIGRL - SFM
In rare circumstances, Lanczos eigenvalue analysis may fail in the REIGL module
and the message "SYSTEM FATAL MESSAGE 4276, ERROR CODE 7777" will be issued.
Avoidance: The error is more likely when a large buffsize is set. The error
may be easily avoided by either increasing or decreasing the buffsize.
25555
lters
69.1
Miscellaneous - SSSALTER - Old Released A
The SSSLATER library released for V69.0.2 is not the current library intended
for release.
Avoidance: Contact your MSC representative for the correct versions of the
alters.
25595
69.1
ses a Memory Fault
Submittal - Command Line Option "cpu" Cau
For Alpha/Unix Version 69.0.2 the use of the command line option cpu causes a
memory fault.
Avoidance: Set ppcdelta to .1 in the system rc file.
25673
70
Modal Transient Analysis - TRD1 failure w
ith SYSTEM(146)=2 and unsym. DMIG input
If in a modal transient analysis uses Lanczos with SYSTEM(146)=2 and an
un-symmetric direct matrix input with B2PP is activated, then the TRD1 module
fails on an SGI R4400 machine with the log-file message:
Receiving signal number 10: Bus Error
Avoidance: Do not set SYSTEM(146)=2.
25675
70
ll T3SKEW - Missing Documentation
Documentation - CTRIA3, NASTRAN system ce
The MSC/NASTRAN Version 68.2 Release Notes document the

which allows the user to control the the minimum vertex
elements at which USER WARNING MESSAGE 5491 is issued.
should have been but was not transferred to the Version
Guide.
25681
rs
70
T3SKEW system cell

angle for TRIA3
The documentation
69 Quick Reference
Documentation - SETREE - Unexpected answe
If SETREE entries are used to define a multi-level processing tree, then

according to Remark 6 under the Quick Reference Guide description of the SETREE
entry superelements that are not specified on the SETREE entry will not be
included in the analysis. However, if the non-listed superelements are
attached to grid points which belong to the residual structure, they will be
placed in the tree immediately above the residual structure and included in the
analysis.
25688
69.1
Modal Analysis
SSSALTER - rflagb.v69 - Wrong Answers for
The rflagb.v69 alter gives correct answers for motion at the enforced motion
DOFs, but wrong answers for all other DOFs. The cause of the error is in the
assembly of the modal matrices. This error applies to the alter dated November
96. The version delivered with Version 69.1 dated 10 Jan 97 has this error
corrected.
Avoidance: If you do not have access to Version 69.1, you may request a copy
of the updated alter through client support.
25691
777
69.1
Nonlinear Analysis - OFP - SFM 4276, EC 7
A nonlinear analysis that requests stresses for plane strain elements in

MSC/NASTRAN Version 68 may fail in the OFP module with the message SYSTEM FATAL
MESSAGE 4276 ERROR CODE 7777 on CONVEX computers.
25700
69.1
Restart - Mini-database Restarts with Sup
erelements - Missing Output, UWM 4410
If superelements are present in a mini-database restart using a dynamic
solution sequence such as SOL 103, 107--112, 129, 145, and 146, or dynamic
analysis in 200, then data recovery output for the residual structure will be
missing and UWM 4410 will be issued.
compile phase0
alter 'IF ( (DYRD',''
IF ( (DYRD<>0 OR (SEID<>0 AND METH<>0)) AND
(NOT(STATICS) OR AERO) and not(saverstl) ) THEN $
25713
ers
69.0.2
Rigid Body Elements - RSSCON - Wrong Answ
In Version 69.1, the shell-solid connector RSSCON does not allow the connection
of midside noded elements with non midside noded elements when the ELEM option
is used. For example, a CQUAD8 shell element can not be connected to a CHEXA
with 8 nodes. A fatal message is issued.
In Version 69, non matching elements were connected with the ELEM option.
Spurious zero energy modes appeared
as a result of the incomplete connection. In Version 69.0.2 the fatal message:
USER FATAL MESSAGE 6689 (GP4RS2)
BULK DATA RSSCON
201 ELEMENT
1 CONNECTED TO ELEMENT
5 IS AN
INCOMPLETE ATTACHMENT.
ONLY A SUBSET OF THE SHELL GRID AND EDGE DEGREES OF FREEDOM ARE CONSTRAINED
is issued, wrong answers are avoided and thus the error is considered
corrected.
Avoidance: If non matchi
25715
70
ints - RSSCON - UFM 6692 (SECNSD)
Rigid Body Element and Multipoint Constra
If more than one shell element is connected to the same solid element with the
RSSCON element using the ELEM option, conflicts in the multi-point constraints
may occur. A message of the form:
USER FATAL MESSAGE 6692 (SECNSD )
RSSCON NUMBER
*** CANNOT CONNECT AN EDGE OF TRIA ELEMENT
ELEMENT **
TO TETRA
will be output for those shell grids which can not be connected. The Version
70 Quick Reference Guide documents this limitation closing this report.
Avoidance: In general, it is NOT recommended to connect more than one shell
element to the same solid element.
25724
70
Documentation - CELAS1, CELAS2 - UFM 316
The MSC/NASTRAN Version 69 Quick Reference Guide description of the CELAS1 and
CELAS2 indicates that multiple degrees of freedom may be attached on a single
entry. This is not the case and if attempted will result in the message:
*** USER FATAL MESSAGE 316 (IFPDRV)
ILLEGAL DATA ON BULK DATA ENTRY CELASi
25730
70
***
SORTED ENTRY COUNT = *
Postprocessing - DBC - Excessive CPU Time
DBC can take an inordinate amount of time to write to the .xdb file in some
sort1 jobs. For instance, a 130000 dof dynamics job that is writing 100 modes
spent 50 minutes cpu time to calculate the modes, but 16 hours writing to the
.xdb file.
Avoidance:
Use the following alter which forces sort2 only for writing to xdb.
compile sedrcvr souin=mscsou list, noref
$ force sort2 output in a sol 103, normals modes run
alter 329,329 $
SDR3
OUGV1,OPG1,OQG1,OEF1X,OES1X,OSTR1/
OUGV2,OPG2,OQG2,OEF2,OES2,OSTR2 $ SORT2 OUTPUT
DBC OPG2,OUGV2,OEF2,OES2,OQG2,GPLS,EGPSTR,EGPSF,GPDCT,ELDCT,
ONRGY1,OGPFB1,ERROR1,,,,,,,//
'OPG'/'OUG'/'OEF'/'OES'/'OQG'/'GPL'/'GPS'/'SVF'/
25746
Matrix Methods - MPYAD - Segmentation Violation
A client deck fails with a segmentation violation while performing a sparse

MPYAD in the SDR1 module.
Avoidance: The cause of this is under investigation, but the following alter
avoided the problem by deselecting sparse MPYAD before the module where the
error occurred.
alter 217
type parm,,i,n,sys126=0 $
sys126 = getsys(sys126,126) $
putsys(24,126) $
alter 218
putsys(sys126,126) $ put original value back
25747
70.5
ning Message 3 from Subroutine CHEXA
Documentation - PARAM,POST,0 - DBCMSG War
The DBC module which creates the graphics database may issue unclear messages
such as those that follow.
CHEX
ELEMENT
19 HAS BEEN UPDATED.
This message is simply an indication that an xdb existed prior to the run and
the element cited has been updated or changed.
25773
Rigid Elements - RSSCON - UFM 6689
RSSCON elements do not correctly connect warped solid elements to shell

elements. In the case of a CHEXA with midside nodes out of alignment with the
corner grids by more than TOLRSC*(element edge length), the shell attachment to
the midside nodes results in the following improperly issued FATAL message:
USER FATAL MESSAGE 6689 (CONSSD)
RSSCON NUMBER
200 CANNOT CONNECT HEXA ELEMENT
3
USER ACTION: CHECK GEOMETRY
1 TO QUAD ELEMENT
Avoidance: Other than modifying the geometry to eliminate the warped elements
there is no avoidance.
25814
T.
70.5
DMAP - AUTOSPC Incorrectly Constrains USE
If a user places a degree of freedom into the user sets (U1-U6), and the degree
of freedom is singular, then when GPSP moves it to the s-set it also removes it
from the user sets. The user sets are mainly used by DMAP writers
Avoidance: Use the USET table produced by the GP4 module rather than the
updated version produced by the GPSP module.
25817
70
, 1 and 3 Do Not Work.
Postprocessing - Stress sort PARAM SRTOPT
Module STRSORT which is activated by PARAM,SRTOPT does not work as documented

for values 1 and 3. The module does not sort in ascending order.
25819
- UFM 4252
69.1
Superelements - Mini-Database (scr=mini)
The mini-database option only supports data recovery restarts, i.e., the
coldstart run must be executed for all superelements plus the residual
structure; i.e., SEALL=ALL, before the data base is useful. In other words,
superelements cannot be generated in separate runs with SEALL=n referring to
one or more superelements under the mini-database option. If this is attempted
then UFM 4252 will be issued in module SEMA.
Avoidance: None.
25821
70
C/NASTRAN Encyclopedia
Online Documentation - Installation of MS
When performing a custom install of the MSC/NASTRAN Version 69 Encyclopedia for

WorldView 2.2 Architectures, the following choices for systems are presented
which contain duplicate menu choice labels for HP and SGI systems:
---------------------------------------------------------------MSC Installation and Setup - Interleaf WorldView V2.2 Architectures
Sel
1.
2.
3.
4.
5.
Architecture
Mode Mbyte
Digital Alpha UNIX . . . . . . . . . . . . . . . . . . . . . No
9
Hewlett Packard 9000
No
9
Hewlett Packard 9000 . . . . . . . . . . . . . . . . . . . . No
9
IBM RISC System/6000
No
8
Silicon Graphics . . . . . . . . . . . . . . . . . .
25824
70
SSSALTER - sm03a.v69 - SIM 6470
If the lanczos module is given a mass matrix which contains terms further from
the diagonal than occur for the stiffness matrix, various errors may occur.
One symptom is a fatal message mentioning "spurious modes". Another is a
message of the form
*** SYSTEM INFORMATION MESSAGE 6470 (SSMR0D)
MORE EFFICIENT PROCESSING IN LANCZOS EIGENSOLUTION MAY BE POSSIBLE BY
INCREASING THE BUFFER SIZE OR
THE VALUE OF SYSTEM CELL 199 SUCH THAT THE PRODUCT OF THESE TWO VALUES
IS AT LEAST 2266 WORDS.
This above message is actually a symptom of a fatal error which will occur
later, of the form
0*** SYSTEM FATAL
MESSAGE 3001 MODULE = LANCZOS
THE EXECUTIVE FILE
0 DOES NOT EXIST.
This problem most commonly occurs with component mode synthesis, a capability
supported
25836
70
nstallation Problems
Documentation - V69 Online Encyclopedia I
The V69 MSC/NASTRAN ENCYCLOPEDIA (MNE) Installation does not work if the user
chooses to keep both collections on the CD-ROM. This is the minimum
installation option.
Avoidance: If you want to install only the WorldView browser and access both
V69 and V68.2 documentation collections from the CD-ROM (minimum installation),
you must do the following before you start the installation.
1. Decide on the <install_dir> directory in which to install the MNE.
2. Before installation, create the directory <install_dir>/mne69
After installation, edit the <install-dir>/iview22/Iview file and change the
line
Iview*welcomeDoc:<install-dir>/mne69/v69docs/69doc/start69.pl
to
Iview*welcomeDoc:<install-dir>/mne69/v69docs-cd/69doc/start69.pl
Also, on some IBM RS6000 systems, when iview
25845
6578
70
Eigenvalue Analysis - EIGRL, REIGL - UFM
A new feature in V69 allows the use of parameters on the REIGL DMAP statement
to be used to control Lanczos eigenvalue solutions. An error exists that if
this approach is used, then the a value must be provided for parameter 9 (NDES)
or the module will fail with UFM 6578 indicating that the value for parameter 9
is out of bounds.
Avoidance: If parameters on REIGL are used to control Lanczos, always include
a value for parameter 9 (NDES).
25846
70
6578 parameter 9 out of bounds
Eigenvalue Analysis - EIGRL, REIGL - SFM
In MSC/NASTRAN Version 69, it is possible to provide the control parameters for

the eigenvalue solution on the REIGL statement. If this is done and no value is
provided for ND (number of roots desired, the run will fail with SFM 6578
stating that parameter 9 is out of bounds on the REIGL module.
Avoidance: Provide a large integer in the field for ND on the REIGL module
statement.
25851
70
ANALYSIS=AERO - UFM 1126
Optimization/Design Sensitivity - SCR=NO,
If aeroelastic optimization is attempted using scr=no, errors in the NDDL

dependencies cause the run to
fail on the second design cycle with the message:
DMAP MODULE AMP
202 NAME = QKH
USER ACTION: DELETE THE DATABLOCK, OR USE FILE QKH
=OVRWRT
If a flutter analysis is included, the QKH datablock causes the initial error.
If this datablock problem is corrected and/or there is a static aeroelastic
subcase, the failure is in the DBSTATUS module when it is checking for the
presence of the AUG datablock.
Avoidance: Make the following NDDL changes:
depen qkh
/qhh $
DEPEN AUG /IFPA(VP),lsall $
25852
70
S=FLUTTER, DSAD14 - SFM 3007
If flutter optimization is used in conjunction with the PKNL flutter method,

SYSTEM FATAL MESSAGE 3007 is issued which is of limited usefulness to clients.
Avoidance: The PKNL method is not currently supported in SOL 200. Use the PK
method.
25861
044
70
Superelements - SCR=MINI - SFM 4276, EC 1
In version 69 a new "minimum database" capability has been introduced for

MSC/NASTRAN. This capability is implemented by specifying "SCR=mini" on the
submittal statement. If this feature is used with the split database capability
of superelements, the following error may occur:
BIOMSG: ERROR 1044 HAS OCCURRED IN ROUTINE OPEN
0
Avoidance: If this occurs, either use SCR=NO or SCR=YES on the submittal line.
25865
70
Superelements - BUSH - Wrong Answers
If the BUSH element is used in a model with superelements, the

frequency-dependent capability will not work.
Avoidance: Either include the following DMAP alter in the input file:
compile phase1a
alter 'TA1.*,,ECTS,EPTS,BGPDTS'(,-1)
if(seid=0)then $
type db,ept $
dbview epttemp=ept (where wildcard=true) $
TA1
,,ECTS,EPTTEMP,BGPDTS,SILS,ETT,CSTMS,DIT,ECTAS,EHT/
EST,,GEI,GPECT,,VGFD,DITID/
LUSETS/-1/S,N,NOSIMP/1/S,N,NOGENL/0///S,N,FREQDEPS $
else $
alter 'TA1.*,,ECTS,EPTS,BGPDTS'
endif $
or:
place all superelements in partitioned bulk data sections and place the
residual structure in the main bulk data. The frequency dependent capability
will work if the main bulk data does not have any superelement-related entries.
25866
70
SFM 4276 EC 7777 Sig 8
The overflow message, "SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777" has been
observed on the CRAY in the DOM6 module and has been identified as being caused
by a combination of requesting prints of sensitivity data (OPTEXIT = 4 or 7 the
DSAPRT case control command) when both DLINK and DVPREL2 entries are present.
Avoidance: The only avoidance is to eliminate one of the three contributing
factors. The Beam Library enhancement in Version 69 alleviates the need for
DVPREL2 entries and may be a desirable avoidance in many cases.
25873
70
ry for External Superelements
Superelements - SCR=MINI - No Data Recove
In MSC/NASTRAN Version 69 a minimum database capability was introduced. If

external superelements are used and SCR=MINI is used for the residual
structure, then data recovery is not possible for the upstream external
superelements.
Avoidance: Add the following line to the FMS of the external superelement data
recovery run:
dblocate param=(saverstl), where (peid=0), logical = rsdb
(where RSDB is the logical name used for the database with the residual
structure solution)
25884
70
Possible Wrong Answers
Superelements - SESEB - Missing UFM 6794,
Version 69 on CRAY computers may not correctly detect duplicate boundary points
and thus may fail to issue:
USER FATAL MESSAGE 6794 (SEPSEB)

DUPLICATE BOUNDARY POINTS DETECTED CONNECTING TO SUPERELEMENT ** AT GRID **
FROM DOWNSTREAM **.
The failure to issue this message may result in an upstream superelement being
connected to an unintended degree of freedom resulting in wrong answers.
Avoidance: When using the automatic superelement connection logic, be careful
in maintaining unique grid locations for boundary points.
25888
, UIM 4158
69.1
Eigenvalue Analysis - GIV - Wrong Answers
Using the GIVENS method to calculate modes of a structure which has a non
positive definite mass matrix, should result in the following error message:
"USER FATAL MESSAGE 4646---- THE MASS MATRIX IS NOT POSITIVE DEFINITE,USING THE
GIVENS METHOD. USE MGIV INSTEAD"
However, the run may proceed and incorrect answers may be produced. Since
MSC/NASTRAN automatically omits massless degrees of freedom, this error only
occurs with models involving nearly massless mechanism. The user is warned of
the poor answers by a very large value for the factor diagonal ratio in the
following message:
USER INFORMATION MESSAGE 4158 ---STATISTICS FOR CHOLESKY DECOMPOSITION OF DATA
BLOCK MXX FOLLOW
MAXIMUM RATION OF MATRIX DIAGONAL TO FACTOR DIAGONAL =
The user may also be warned of the poor r
25891
70.5
Rigid Elements - RBE3 - Poor Answers
If an RBE3 element is input with insufficient independent degrees of freedom to

define all 6 possible rigid body modes of the element, a set of constraint
equations may be produced that do not reflect the weighting factors input by
the user, and can also cause internal constraints associated with stiffness and
mass terms associated with degrees of freedom attached to the RBE3 element.
This error was observed on a model which has an RBE3 element of the form
$
refc
wti ci
RBE3, [eid], , [refgrid],123456, 1.0, 123, gida, gidb
As the two attached grid points have only translations coupled, (123 input for
ci), the element is not capable of reacting the component of moment applied at
refgrid that is parallel to a line drawn between gida and gidb. The element was
25893
70
a Recovery in SOL 103 - UFM 1126
Superelements - External Superelement Dat
In external superelement data recovery restart runs in which there are multiple
normal modes solutions, the run may fail with UFM 1126 on data block PHA.
Avoidance: Insert the following alter:
compile extdrin
alter 1
file ul=ovrwrt/ol=ovrwrt $
25909
70
RESTARTS - PBCOMP - ERROR 7777 HAS OCCURR
ED IN ROUTINE tbk,FILE INDEX (FILEX)=0

Restarts of decks with PBCOMP entries may fail the message:
ERROR 7777 HAS OCCURRED IN ROUTINE tbk,FILE INDEX (FILEX)=0
Avoidance: The simplest avoidance is to execute the analysis as a cold start.
25916
rid Point
2001
p-Elements - CBEAM - UFM 6367 Undefined G
A client p-element model using the adaptive beam failed with the following
message;
USER FATAL MESSAGE 6367, (POLYD), GRID OR POINT ID =******** FOR ELEMENT ID =
*** IS UNDEFINED
even though the grid points were correctly defined for all elements in the
model.
Avoidance: The cause of this error is still under investigation; however,
modifying the sixth field of the PVAL entry from explicitly specifying "0" to
blank as follows caused the job to run successfully.
PVAL
SET
SET
to
PVAL
25939
70
SFM 4276 EC 3002
Optimization/Design Sensitivity - OFREQ -
If an OFREQ entry is specified in the case control of a solution 200, modal

frequency response analysis the following error message is issued:
ERROR CODE
3002 PID=
Avoidance: Remove the OFREQ entry from the case control. A DMAP avoidance is
under investigation.
25948
70
Undefined Coordinate System
Miscellaneous - CORD1i - UFM 2006 (GP1C),
In MSC/NASTRAN Version 69, If two coordinate systems are defined on a CORD1i

entry, then the second coordinate system definition will be ignored. This
error will likely lead to the message:
USER FATAL MESSAGE 2006 (GP1C)
GRID POINT *** REFERENCES UNDEFINED COORDINATE SYSTEM ***
Avoidance: Other than editing the input bulk data to place the CORD1i
definitions on separate entries, there is no avoidance.
25950
70.5
MHOU, HOU - Wrong Answers
Eigenvalue Analysis - SUPORT, MGIV, GIV,
For a two degrees freedom system, if one of the tridiagonalization eigenvalue

methods (e.g., MGIVENS) is used and the model contains a SUPORT entry, then the
answers will be wrong. A symptom of this error is the existence of an extra

rigid body mode and zero generalized mass for the flexible body mode.
Avoidance: There are three possible avoidances.
1. Use the Lanczos eigenvalue solver.
2. Add an extra degree of freedom.
3. Remove the SUPORT entry if feasible.
25970
70
HT - Wrong Answers
Frequency Response Analysis - CBUSH, PBUS
If the KN field is used on the PBUSHT entry in a frequency response solution,

incorrect answers will result.
Avoidance: If BUSH elements are used in a frequency response solution, do not
use the KN entries.
26022
67.5
R 933, Unclear Message
DMAP - INPUTT2/OUTPUT2 - FORTRAN I/O ERRO
When using INPUTT2 and ALL of the following conditions are met:
1) Multiple rewind/reads off same INPUTT2 file (as would happen in a looping
situation)
2) Using a neutral (formatted) INPUTT2 file
3) An EOF marker (OUTPUT2, ,,,,//-9/iunit $) was NOT used when writing out the
output2 file
then the job will terminate in the f06 file without any messages. The log file
file may contain any
one of the following messages:
1)FORTRAN I/O ERROR 933 - Job aborts reading INPUTT2
2)1525-001 The READ statement on the file xxxxx cannot be completed because the
end of the file was reached.
The program will stop.
Avoidance: Add an EOF marker by adding an output2 statement similar to the
statement shown below:
output2,
26060
-UX - UFM 3060
70
,,,,//-9/junit $
Submittal - Memory Allocation Error on HP
MSC/NASTRAN V69.X on HP-UX systems may be unable to acquire necessary shared

memory or queue resources due to lack of available resources. These errors
will be manifested as the inability to allocate memory or UFM 3060 errors
citing NUSR.
The problem is that MSC/NASTRAN's shared memory and queues may not get properly
cleaned up if MSC/NASTRAN does not exit normally, e.g., is terminated via kill
-9. As a result, system resource remain committed to
jobs that have terminated, and are unavailable later on when needed for another
job.
Rebooting the system will clear up these resource, but we don't recommend this
as the fix as it's more than a little disruptive. The following changes to the
local template will give MSC/NASTRAN an additional opportunity to clean up

after itself.
MSC/
26069
g
70
Restarts - RANDOM - Inefficient Processin
In MSC/NASTRAN Version 69, if a random analysis is executed as a restart to a

frequency response analysis the FRRD1 module will be unnecessarily re-executed.
compile sedfreq
alter 'if ( not noph2'(2),''
if ( false ) then $
26076
70
ata Recovery Restarts may Fail
Superelements - DBLOCATE - Multi-Master D
If the database for a superelement has changed from the original run, then a
multi-master data recovery restart may fail in DBLOCATE.
26078
70
Traceback in CURV1
Static Analysis - PARAM,CURV1, PARAM,OG -
If PARAM,CURV,1 is specified to request that the CTRIA3 and CQUAD4 element

stress and strain output be computed in the material coordinate system and
PARAM,OG,-1 is specified to avoid calculation of the stresses at the grid
points, the run will fail in the CURV module with the following traceback
printed in the log file or other machine dependent symptoms such as excessive
times or stopping without any messages.
Traceback:
Offset
Offset
Offset
Offset
0x00000a78
0x000000d4
0x000000e4
0x0000097c
in
in
in
in
procedure
procedure
procedure
procedure
curv1_
curv_
xsem14_
mainal
Avoidance:
The CURV module grid output in the user defined coordinate system is obtained
by using PARAM,S1G,1 for stresses and PARAM,S1AG,1 for strains. This grid
output can either be turned off
26111
70.5
- UFM 6656 (MODTRK) PHGREF Not Found
Optimization/Design Sensitivity - MODTRK
If mode tracking is attempted with multiple boundary conditions and if two or

more DRESP1 entries identify the same mode, mode tracking will fail and the
message following message will appear.
USER FATAL MESSAGE 6656 (MODTRK) PHGREF CANNOT BE FOUND
Avoidance: Do not list the same mode number on multiple DRESP1 entries. If
the same mode number is
being tracked in multiple boundary conditions, a single DRESP1 entry can be
invoked by separate DCONSTR entries for each of the boundary conditions.

26127
70
r, Segmentation Violation
Miscellaneous - EMG - SIGNAL 10: Bus Erro
MSC/NASTRAN Version 69 stops in EMG with no messages in the F06 file when
materials with duplicate IDs exist. The log file indicates either:
SIGNAL 10: Bus Error
or:
SIGSEGV - Segmentation violation.
In Version 68.2, USER FATAL MESSAGE 2017 MATERIAL PROPERTY IDENTIFICATION xxx
WAS DUPLICATED
was correctly issued.
26128
70
, DECOMP - Unexpected Fatal Message
Differential Stiffness - STATSUB, BAILOUT
PARAM,BAILOUT has the incorrect default in solutions 103, 105 and 107 when the
STATSUB command is specified; i.e., differential stiffness is requested. This
may cause jobs to stop and issue fatal messages in DECOMP. Also,
PARAM,BAILOUT,-1 is ignored in SOLs 103, 105, and 107 when the STATSUB command
is specified.
compile statics2
alter 'call phase1c'(,-1)
bailout=-1 $
endalter
26132
2004
SAERO - UFM 4574
Optimization/Design Sensitivity - STATIC,
Analysis types STATIC and SAERO, do not work together in solution 200. If they
are attempted in the same run the following message is issued, "USER FATAL
MESSAGE 4574, DATA RECOVERY STARTED BUT NO DISPLACEMENT VECTORS AVAILABLE"
26173
2001
ng Documentation
Documentation - GPFORCE(PLOT)=ALL - Missi
Although it is not documented in the QRG, the plot option is supported for the
GPFORCE entry.
26180
70
P-Elements - TEMPF, ADAPT - Traceback
TETRA and PENTA p-elements with TEMPF thermal loading fail in the ADAPT module
with the following traceback.
Traceback:
Trap encountered:
SIGTRAP - Trace trap
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0x00000414
0x00000b80
0x00000900
0x00000c70
0x0000134c
0x000003ac
0x0000094c
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
gxstrn_
adpegd_
adpeld_
adp_
adapt_
xsem14_
mainal
--- End of call chain --Avoidance: Use another method to define the thermal loads.
26187
2001
AKEOLD - Missing Documentation
Documentation - DMAP Module Dictionary, M
In the Release Notes for Version 69 it states that the MAKEOLD module may be
needed to convert datablocks to the old format. This module is not documented
anywhere and there is no list of the datablocks it works on.
Avoidance: A brief description follows:
Description: Used to convert datablock GEOM1, GPDT, BGPDT, CSTM, AXIC and EST
to old format for OUTPUT2 module.
Format:
MAKEOLD
IDB1,IDB2,IDB3,IDB4,IDB5/ODB1,ODB2,ODB3,ODB4,ODB5/P1/P2/P3/P4/P5/P6/P7/P8/P9/P10
$
IDBi = Input Data Block, targeted datablocks are GEOM1, GPDT, BGPDT, CSTM, AXIC
and EST.
ODBi = Output Data Block.
P1:P5 Character input, default is blank. Then generic name of the
corresponding input data block; e.g. P3 corresponds to IDB3, etc.
P6:P10 Character input, default is blank. The generic n
26190
Warning Message
Heat Transfer Analysis - RADBC, RADM - Wrong Answers, Missing
If the user intends to use RADBC, radiation to space, the absorptivity value
on the RADM bulk data entry must be specified. Otherwise, the ambient space
temperature is ignored and unexpected answers will result.
Avoidance: Make sure that when you have RADBC in the problem, you specify the
absorptivity value.
26204
70
ning Message, NaN in Output
Heat Transfer Analysis - CTRIAX6 - No War
No warning message is issued if convection or radiation is specified on the

axis of rotation for the axisymmetric CTRIAX6 element. This is an impossible
physical boundary condition that may lead to "NaN" being output for the "HEAT
FLOW INTO HBDY ELEMENTS".
Avoidance: The user should check whether he is applying this ill-posed boundary
condition.
26221
70
MSC/ACCESS - DBCTA1 Datablock Description
The MSC/ACCESS sample programs need to be updated to the same version of

MSC/NASTRAN that they are delivered with, including having the most recent
versions of MSC/NASTRAN source in them and updating the program so they work.
They currently contain v67.5 element definitions and, thus, cannot be used as a
guide to MSC/ACCESS users on how to access information on modern elements.
Avoidance: Send the latest version of the MSC/NASTRAN source file "dbctbd.f"
to the client, and have the client update the "sampler.f" sample program as
practice and then update their own program in a similar way.
26230
70.5
DR, TEMP(LOAD) - Wrong Answers
Buckling and Differential Stiffness - GPF
Grid point force data recovery for static analysis in SOL 105 is incorrect when
thermal loads are applied.
In version 69, the error exists also in SOLs 103 and 107. In version 70, the
error exists also in SOLs 103 and
107 through 112.
Avoidance: A DMAP avoidance is given below for Versions 68.2, 69, and 70.
compile phase1a
alter 'call selg'
equivx ptelem/ptel/-1 $
call dbstore ptel,,,,//seid/0/'
'/0 $
compile sedrcvr
alter 'GPFDR
CASEDR',''
call dbfetch /ptel,,,,/seid/0/0/0/0 $
GPFDR
CASEDR,UG,KELMx,KDICTx,ECTS,EQEXINS,GPECT,PG1,QG,
BGPDTS,SILS,CSTMS,VELEM,PTEL/
ONRGY1,OGPFB1/APP2/TINY//CYCFLG $
26231
)
70
Documentation - RESTART - UFM 146 (LINKTP
Version 69.1 cannot RESTART from a Version 69.0 database. If attempted the the
message:
USER FATAL MESSAGE
146 (LINKTP )
A 'TYPE' STATEMENT DEFINES A DATABLOCK PVTBC
DEFINED IN THE 'NDDL'
IN SUBDMAP SEMFREQ WHICH IS NOT
will be encountered.
Avoidance: It is possible to perform a DBLOCATE restart.
26244
70.7
OST - Optimized Soluton not on OP2 File
Solution 200 has been enhanced in MSC/NASTRAN Verison 70.7 to output the
optimized solution to the op2 file. Prior to this enhancement it was required
to update the bulk data file with the punch file solution results and rerun a
static solution to obtain an updated op2 file.
26250
ented
70.5
Documentation - DBDELETE Module Not Docum
The new DMAP module DBDELETE in Version 69 is not documented.

This module is useful for those writing looping dmaps. It was introduced late
in Version 69 development, and is not in current documentation.
Examples of its use may be seen in the fea subdmap.
Format:
DBDELETE [DATABLK=(datablk-list)] WHERE (where_expr)
The where_expr rules are similar to those for the dbdict module. A
wildcard option is available.
Example:
DBDELETE KJJ WHERE (WILDCARD)
Function: All copies of KJJ will be erased from the database,
regardless of the values of their qualifiers.
26267
UFM 2166
70
Heat Transfer Analysis - RESTART, TEMP -
If enforced temperatures are applied in a transient heat transfer analysis cold

start, then a subsequent restart may fail with the message:
USER FATAL MESSAGE 2166, MATRIX TO BE PARTITIONED IS OF SIZE
** ROWS BY
*** COLUMNS.
ROW PARTITION SIZE IS
** COLUMN PARTITION SIZE IS
*** (INCOMPATIBLE).
Avoidance: Insert the following alter into the Executive Control section:
compile nltran
alter 'copy
ysnt/ysnr',''
endalter
26274
70
rmediate CBAR Results
Documentation - CBARAO - Plotting of Inte
In order to get a CBAR element with a plot code of 100 which provides for data
recovery at intermediate locations on the bar, a PLOAD1 must be specified for
the element in question. Remark 1 under the Quick Reference Guide description
on the CBARAO incorrectly indicates that this a requirement for the SCALE=LE
option only.
26278
70
EW - Wrong Answers
Heat Transfer Analysis - CHBDYG,AREA8, VI
Radiation heat transfer using the backside of the CHBDYG,AREA8 or CHBDYG,AREA6

for view factor calculation yields incorrect results.
Avoidance : Always use the front side for the CHBDYG,AREA8 and AREA6 elements
for view factor calculations.
The normal directions can be reversed on the CHBDYG,AREA8 by changing the grid
connectivities.
26283
70
Incorrect Punched Output
Documentation - Transient Heat Transfer -
The PARAM,CURVPLOT,1 is used to force SORT1 output for transient thermal

analysis in MSC/NASTRAN Version 68. However, the DMAP has been changed in
Version 69 so that PARAM,CURVPLOT,1 can no longer force SORT1 output in
transient thermal analysis. To request SORT1 output in Version 69 specify
THERMAL(SORT1) or FLUX(SORT1) and remove the OUTPUT(XYPLOT) section from the
case control section.
Avoidance: If you remove the OUTPUT(XYPLOT) section, then version 69 can output
the SORT1 in transient thermal analysis
26285
Job Hangs
70
Matrix Methods - Parallel Decomposition -
Eigenvalue analysis using the Housholder method may hang on the VAX/VMS Version
69 system if parallel decomposition is selected.
No sparse parallel decomp has been blocked on all systems in Version 70.
Avoidance: Do not select parallel processing.
26294
70.7
for unformatted file
Utilities - tabtst.f - illegal structure
In the MSC/NASTRAN Version 68.2 Installation and Operating Instructions Guide

for Windows NT for INTEL, Chapter 2 How to install MSC/NASTRAN, Section 2.1,
Installing MSC/NASTRAN, section 2.1.1, Before You Begin, it says:
"If you are going to build the Utility Programs using the supplied source, you
must also have a suitable compiler. The supplied source has been compiled and
tested using:
WATCOM FORTRAN 77/32, Version 9.5c
WATCOM C/C++ 9.5c
.
.
Note: Later versions of the WATCOM compilers should work but have not been
tested. The supplied source should work with other compilers available for
Windows NT but has not been tested."
This should be changed to indicate that if the customer's program reads binary
files, it probably won't work due to binary file format difference
26298
70
L - Incorrect von Mises Stresses
Response Spectra - DDRMM, PARAM,OPTION,NR
In a response spectrum analysis, if the NRL summing option is used, then the
Von Mises stresses are calculated differently than what is described in the
NAVSEA 0908-LP-000-3010 specification. In the NAVSEA spec, the von Mises
stresses are calculated for each mode based on the sigma-x, sigma-y, and tau-xy
for that mode. The von Mises stress for each element is then summed using the
NRL criteria based on the von Mises stresses for the modes. In MSC/NASTRAN, the
component stress (e.g., sigma-x) for each element is calculated using the NRL
criteria based on the component stresses for the modes. The von Mises stress
for the element is then calculated using the component stresses.
26304
wers
70
Aeroelastic Analysis - ZONA51 - Wrong Ans
The supersonic aerodynamics code (ZONA51) used in the AERO II option in

MSC/NASTRAN has been observed to produce incorrect results when the z distance
between boxes on interfering non-coplanar surfaces is less than half the width
of a spanwise strip of boxes in the aerodynamic mesh.
Avoidance: A possible avoidance is to decrease the width of the maximum strip.
An alternative avoidance is to artificially modify the geometry of the
aerodynamic model by either making the interfering surfaces coplanar or by
increasing the z separation of the two surfaces. Another option is to make the
surfaces non-interfering by putting them in interference groups (IGID on the
CAERO1 entry).
26315
70
- SFM 4276, EC 7777
Optimization/Design Sensitivity - CORD2i
A shape optimization job may produce a numerical overflow (division by zero in

tranms/d) or produce the wrong updated mesh when it uses a chain of CORD2i
entries. The error may occur when the following conditions are true:
1) At least two CORD2i entries define a parent and child coordinate systems
where the child system is a non-basic coordinate system and,
2) The non-basic child system has a different type of coordinate system from
its parent.
For example, the following two entries will trigger the error:
CORD2R 1
CORD2S 2
2
1
...
...
where the first entry is the parent and the second entry is the child. Note
that the second condition above is met because the parent is of type
rectangular while the child is spherical.
Avoidance: Use the
26329
70.5
REFC - Wrong Answers
Optimization/Design Sensitivity - AEROS,
Solution 200 supports the ability to simultaneously analyze and design

responses associated with static
aeroelasticity and flutter. If the user inputs a reference chord on the AEROS
entry that differs from
the reference chord input on the AERO entry (both fields are designated REFC),
an incorrect flutter analyses
will be performed with unpredictable results. That is, the run may terminate
with an unrelated error message or it may run to completion, with wrong
answers.
Avoidance: Make sure that the two REFC values are the same.
26331
70
mentation Violation, Traceback
Nonlinear Analysis - RFORCE, NLCOMB - Seg
Nonlinear Analysis that combines RFORCEs with other loads will fail with the
following traceback in the NLCOMB module:
Traceback:
Offset
Offset
Offset
Offset
Offset
0x0000099c
0x00000210
0x00000234
0x0000017c
0x0000098c
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
nlcslb_
nlcslt_
nlcomb_
xsem15_
mainal

26340
Output
70
Heat Transfer - RADBC, SPCFORCE - Missing
SPCFORCE output is missing in heat transfer. In solution 159, any SPCFORCE

output associated with an element with nonlinear capability is overwritten by
noise at all points. In both solutions 153 and 159 the RADBC
element gives no heat to ambient points.
26342
4
70
Miscellaneous - CORDi - SFM 2005, UFM 675
In Version 69.0, if there are multiple nested coordinate systems (e.g., CORD a
references CORD b and CORD b references CORD c, etc.), then the job may fail
with the following error messages on some machines. This error has so far been
observed on the SUN and HP machines when the nested coordinate system is
cylindrical and the z-axis lines up with one of the axes of the basic
coordinate system.
*** SYSTEM FATAL MESSAGE 2005 (GP1C)
INCONSISTENT COORDINATE SYSTEM DEFINITIONS DETECTED IN SUPERELEMENT
x
*** USER FATAL MESSAGE 6754 (GP1C)
NO GRID POINTS DEFINED FOR CORD1I ENTRIES IN SUPERELEMENT
Avoidance: Changing the location of the z-axis slightly in the nested

cylindrical coordinate system may avoid the problem.
26349
70
Optimization/Design Sensitivity - DVGRID
When a shape optimization job has DVGRID entries that refer to non-existing
grids, Version 69 produces the following message:
0*** SYSTEM FATAL
MESSAGE 3062 MODULE = DOPR2
FAILURE OCCURRED IN UTILITY MAPXTI CALLED IN SUBROUTINE DSAJ1
REQUESTED EXTERNAL ID(S) NOT FOUND.
Version 68 produced the following message:

0*** USER FATAL MESSAGE 5492 (DSAJ1
AN UNDEFINED GRID ID =
9999 HAS BEEN REFERENCED BY A DVGRID BULK DATA
CARD WITH A DVID =
1
USER ACTION: CHECK THE DVGRID AND GRID BULK DATA CARDS
Avoidance: Correct the offending DVGRID entry.
26351
70
UWM 7001 (DOPR1B), Wrong Answers
If the DLINK ID and the DDVID across multiple DLINK bulk data entries are not
in the same ascending order, then the message
USER WARNING MESSAGE 7001 (DOPR1B)
may be issued in error and the subsequent results will be incorrect.
Avoidance: Make sure the lowest DLINK ID corresponds to the lowest DDVID and
that subsequent ID, DDVID
pairs are in monotonically ascending order.
26352
70
Superelements - UFM 7139
If an optimization run with ANALYSIS=SAERO or ANALYSIS=FLUTTER has

superelements, then one of the following fatal messages are issued:
"USER FATAL MESSAGE 7139 (DOPR3C) ON DRESP2 entry ID = xxxx, RESP1 ID = yyyy
DOES NOT REFERENCE AN EXISTING DRESP1 ENTRY."
"SYSTEM FATAL MESSAGE 3007 MODULE = SEDR ILLEGAL INPUT TO SUBROUTINE SEDR"
"SYSTEM FATAL ERROR 4276.GETSTR ERROR CODE
3021 PID= 0"
Avoidance: The run must be made without superelements.
26354
ion is ignored
70
Superelements - CSUPEXT, SEELT - THRU Opt
The CSUPEXT entry with the "THRU" option does not function correctly. Only the
first grid point is made exterior to the superelement and all other points are
ignored. The SEELT and the RELEASE entries also have problems processing the
"THRU" range. It has been experienced that the last element of the range may
be dropped. The "THRU" problem may apply to other entries also.
Avoidance: Do not rely on the "THRU" range for the CSUPEXT, RELEASE or SEELT
entries. Explicitly specify the list of grid points or element ids for these
entries.
26356
70
Utilities - BUILDSSS -
The buildsss.sh file in the <ins-dir>/msc691/util uses 'which', which is not

part of the standard UNICOS bsh environment.
This may result in the following error:
buildsss.sh[122]: test: argument expected
Avoidance:
Comment out the lines:
test -x
test -x
echo
exit
}
26376
$progexe || progexe=`which $PROG 2>/dev/null`

$progexe || {
"$tool: prog=$PROG: executable not found."
1
70
Optimization/Design Sensitivity - PARAM,C
DIF,YES - UFM 1126 (GNFIST)

If the central difference method is selected in a solution 200 run by setting
PARAM,CDIF,YES with Transient response the following error message will be
issued.
0*** USER
DMAP
EGKGB ,
USER

MODULE DSVG1
201 NAME =
WHICH ALREADY EXISTS.
ACTION: DELETE THE DATABLOCK, OR USE FILE EGKGB =OVRWRT

compile pslgdv
alter 'egkgb'(,-1)
delete /egkgb,egmgb,egbgb,, $
delete /egkgc,egmgc,egbgc,, $
26377
70
S=FLUTTER - Wrong Answers
If a design sensitivity run is made in SOL 200 that includes multiple flutter
subcases that use the same FMETHOD case control entry to invoke the same
FLUTTER bulk data entry, results will be repeated from the first subcase rather
than extracted from each subcase in turn.
Avoidance: Specify unique FMETHOD entries in each ANALYSIS=FLUTTER subcase in
SOL 200.
26404
70
Virtual Mass - MFLUID - UFM 4258
In Version 69, when you select PLANE1 symmetry on an MFLUID bulk data entry,
MSC/NASTRAN incorrectly checks for PLANE2 symmetry instead. This may
incorrectly cause the following fatal message to be output if your model
violates the PLANE2 symmetry:
USER FATAL MESSAGE 4258. ELEMENT xxxx WHICH IS ON FLUID STRUCTURE BOUNDARY,
CROSSES A PLANE OF SYMMETRY
Avoidance: Put a coordinate system on the MFLUID bulk data entry such that
PLANE2 symmetry is not violated (even though it doesn't matter for the
problem). Note that PLANE1 symmetry is not checked.
26410
70
Unexpected Zero Gradients, UFM 6499
The optimization algorithm will stop if a violated constraint is found to have

a zero gradient. It has been
found that these zero gradients can be produced in error whenever the amount of
space required to hold the active solution vectors (that is those that are
associated with active constraints) exceeds the amount available in the run.
For example, 100 double precision solution vectors, each having 250,000
degrees of freedom, would require 50 megabytes of memory to hold all this
information in core. If less than this is available, all the sensitivity
results will be in error and many will have zero gradients.
Avoidance: Estimate the amount of memory required and request this amount when
running the job, or reduce the amount required by reducing the number of
solution vectors
26424
69.1.1
PD - Wrong Answers
Elements - PSOLID, MAT9, CORD*, TEMP, TEM
If thermal loads are applied to a structure and all of the following conditions
exist in the model:
1. A PSOLID property entry that references a MAT9 material property
2. The CORDM field on the PSOLID entry references a non-basic coordinate
system
then the answers will be incorrect. This error occurs on virtually all Version
69.0 and Version 69.1; however, the error has been corrected in Version 69
system that were built and released after April 1997. The corrected Version
69.0 systems are the DEC VAX and DEC Alpha/NT Version 69.0.4 systems and the
HP Exemplar SPP S CLASS (PA2) and NEC SX-4 Version 69.1 systems. This error
applies to all CHEXA, CPENTA, and CTETRA elements.
Avoidance: Transform the Gij matrix on the MAT9 entry into the basic
coordinate system and refer
26425
69.1
AD) - Wrong Answers
Optimization/Design Sensitivity - TEMP(LO
In MSC/NASTRAN Version 69, when an optimization job has TEMP load entries and
different types of elements in the model are subjected to the thermal loads,
wrong sensitivities may result.
26427
70
S4 - Wrong Answers
Geometric Nonlinear Analysis - ELAS3, ELA
CELAS3 and CELAS4 elements may cause geometric nonlinear analysis, sol 4 in
Version 69, sol 64 in Version 68, to stop in the GNFM module on DEC Alpha
systems.
Avoidance: Use CELAS1 or CELAS2 elements.
26429
70
PTEXIT - Incorrect Termination Message
When param,optexit,4 is specified for an optimization job, the the correct job
termination message is:
RUN TERMINATED DUE TO PARAMETER OPTEXIT =
4.
However, when DESMAX on the DOPTPRM entry is set to 1 in the same deck, the
following job termination message will be produced:
RUN TERMINATED DUE TO MAXIMUM NUMBER OF DESIGN CYCLES =
1.
Avoidance: Remove DESMAX = 1 from the DOPTPRM entry, or simply ignore the
message.
26436
t Formats
Superelements - PARAM,USETPRT PARAM,OPGEOM - Overflow of Prin
PARAM,USETPRT and PARAM,OPGEOM request a print of the user set table for the
g-set and the full set. When SENQSET entries are present in the main bulk data
deck, or when CAEROi entries exist, leading to k-set variable, the degrees of
freedom automatically generated have large ids which may overflow the print
formats or these parameters.
An avoidance is to use param, usetprt, 1 instead of ,0.
26438
70
evel 6.2, R4400, R4000, R5000
Installation - Version 69.1 SGI IRIX 64 l
MSC/NASTRAN V69.1 installation will fail on SGI R4XX and R5000 machines running
the IRIX64 operating system. A clue to this problem will show up when the
mscsetup installation script incorrectly identifies the machine as type
R8000/R10000. A "uname -a" command will also echo IRIX64.
Avoidance:
Prior to installation set the environment variable MSC_ARCH to irix. In c-shell
for example:
setenv MSC_ARCH irix
After this, the mscsetup script should correctly indicate the machine type as
R4XX/R5000 and the installation should complete normally.
26440
utput
70
Parallel Processing - OLOAD - Erroneous O
If parallel processing is selected on SGI 4D computers, then erroneous output

that contains "nan" may appear.
Avoidance: Turn off parallel processing by removing the "parallel=x" from the
nastran statement.
26448
Superelements - LOADSET, LSEQ - UFM 4390, Poor Design
When the LOADSET command is used in partitioned bulk data superelements, all
superelements for which the LOADSET applies must have LSEQ entries. If not, UFM
4390 will result.
Avoidance: Either have LSEQ entries for all partitioned superelements using
the LOADSET command or use the LOADSET command only in SUBCASEs applying to the
superelements which have LSEQ entries.
26450
70
s - Bad Message, SWM 3001
Plotting - OUTPUT(PLOT) with superelement
If there are superelements present along with an OUTPUT(PLOT) section but there
is no SEPLOT or SEUPPLOT
command in the OUTPUT(PLOT) section then SWM 3001 will be issued.
Avoidance: Specify an SEUPPLOT or SEPLOT command.
26455
MNE
Online Documentation - IVIEW - Can Not Print from Version 69
Printing using the print command defaults will not work in the Version 69
MSC/NASTRAN online encycopedia for the UNIX BSD4.2 operating system.
The UNIX System V default command
messages:
lp -s ... gives the following error
Avoidance:
edit as root the file <NASTRAN-install-dir>/iview22/Iview as follows:
! example of printer definition for UNIX BSD4.2 default:
Iview*printerConfig:
grz13p2 PS-doublesided, LaserWriter+, lpr -P%s %s;
no-default, LaserWriter+;
26464
e (DIN A4)
Online Documentation - IVIEW - Printing to European Paper Siz
Printing pages from the NASTRAN V69 Encyclopedia to DIN A4 paper (european
paper size) there is no reduced scaling. This means the contents of the page is
cut on the upper and right border.
This error exists since the first release of the on-line documentation.
Avoidance:
Due to the non-function of the <NASTRAN-install-dir>/iview22/Iview entry
Iview*europeanPaper: True
use the following
Workaround to print NASTRAN V69 Encyclopedia pages to european paper size:
-------------------------------------------------------------------------$ su
$ cd /msc/iview22/ps
$ cp -p psprolog.600 psprolog.600.org
Edit the standard postscript prolog file:
$ vi psprolog.600
Edit original line 49:
% modified by A. Hopf MSC/Germany 20-Mar-1997 --------------------------26475
70
n first subcomplex
The MSC/NASTRAN
CONVEX Exemplar
this keyword is
An error in the
usually this is
Submittal - MSC/NASTRAN Always Executes o
submittal command provides the 'subcomplex' keyword for HP

system to select a specific subcomplex to run the job on. If
not set, the job is supposed to run on the current subcomplex.
driver always forces the job to run on the *first* subcomplex,
'System'.
There are three choices:

1) Accept this restriction.
2) Force the submittal command to always choose the current subcomplex by make
the following changes to the local template file(s):
a) MSC/NASTRAN V69.0.X: In <ins-dir>/bin/nast69.lcl:
i) remove the line:

%s.arch=sppux:%
echo "Subcomplex:
%subcomplex%"
ii) Remove the two words "-sc %subcomplex%" from the line
%s.arch=sppux:% $tcmd /bin/m
26500
GL
E - SFM 1033 (XIO)
Optimization/Design Sensitivity - DBLOCAT
When using DBLOCATE to continue any analysis into a subsequent optimization

analysis, the following error occurs:
0*** SYSTEM FATAL MESSAGE 1033 (XIO)
FILE
0 NOT FOUND IN FIST
0********* DUMP OF XIO PARAMETERS
0XIO NAME =
0
ATTEMPTED OPERATION = OPEN (UPDATE)
FILEXX =
0
.
.
.
0*** SYSTEM FATAL ERROR 4276.XIO
ERROR CODE
4276 PID= 0
0*** USER INFORMATION MESSAGE: TO OBTAIN A NASTRAN DUMP, RESUBMIT JOB WITH DIAG
44 INSERTED IN THE EXECUTIVE CONTROL SECTION.
This is caused because the DBLOCATEd file is read only, but optimization
analysis requires the desiter qualifier to be set on the datablocks
Avoidance: Change the DBLOCATE statements to include "convert (desiter=n)"
where n is the design iteration number. Include a separate DBLOCATE stateme
26508
70
WM 6137, UIM 4258, UIM 4698
Miscellaneous - PARAM,BAILOUT Ignored - U
It has been observed in a model which has obvious singularities that Version 69
may continue with the solution after flagging these singularities using UWM
6137 (rank deficient matrix) and UIM 4258 and 4698 indicating that MAXRATIO has
been exceeded. This is in spite of explicitly setting PARAM,BAILOUT,1.
Avoidance: There is no known avoidance for this error. Search the output file
for message 6137. If it occurs look for UIM 4258 and 4698. The most obvious
evidence is large displacements (possibly as large as 1.E=12) with low stresses.
26527
70
xpected Results when Velocity = 0.0
PK-Method Flutter Solution - FLFACT - Une
If a PK flutter analysis is attempted at zero velocity, unpredictable results

can occur, ranging from
bad answers to floating point divide checks. This error has been corrected in
Version 70 by issuing a user fatal message whenever a zero velocity is
specified on a FLFACT entry.
Avoidance: do not specify velocities of 0.0 of the flfact bulk data entry.
Very low velocities should be
avoided in general, since they may cause the aerodynamics to be extrapolated to
reduced frequencies
above those regarded as acceptable for the aerodynamic theory.
26530
70
- Wrong Answers
Multipoint Constraints - MPC, RBEi, MCE1
Models that contain MPC equations or RBEs may produce wrong answers in Version
69. The symptoms which can cause this error
usually occur when the dependent points for the equations are widely spread
over the columns of the matrix, resulting in a need to pivot when solving the
equations. In this condition the pivoting may discard terms, leading to a
plausible but incorrect solution.
Avoidance: Models with rigid elements should be run through the checka alter
delivered in the sssalter library. SYSTEM(247) may be set to 1 to avoid this
error.
26547
70
t Identify Grid Point
Rigid Elements - RSSCON - UFM 6694 Doesn'
In Version 69.1 the following fatal messages about RSSCON are properly issued,
but instead of printing the grid ID which is causing the error, the printout is
*** . The grid IDs are properly printed in Version 69.0.2.
*** USER FATAL MESSAGE 6694 (GP4RS4)
RSSCON CAUSES CONFLICTING ROTATIONAL CONSTRAINTS AT SHELL GRID POINT ***
26557
70
mented Differences
Nonlinear Analysis - PARAM,KDIAG - Undocu
In MSC/NASTRAN Version 68 and prior releases, in non-linear statics if the

nonlinear stiffness matrix contained nulls on the diagonal then if kdiag<0 (the
default) the program would automatically add a 1.0 to the 0. diagonal term(s).
If kdiag>0 the program would always add a user specified value to the all
diagonal terms.
If kdiag=0, nothing was done.
In Version 69 a change was made: First the addition of a term to the diagonal
of the stiffness matrix was based on the total stiffness
Knl+Kslide-line+Kdiff-stiff and second terms were added to the right hand side.
If KDIAG<0 these additional terms will automatically be discarded (though in
Version 69 there was a variable error-see alter below to fix)
If kdiag>0, then these terms need to be turned off after the first subcase s
26560
70
Rigid Elements - RBE3 - Wrong Answers
In MSC/NASTRAN Version 69, if the 'UM' option is used on the RBE3 entry and the
GMi terms are not in ascending order then wrong answers result.
Avoidance: Specify the GMi terms in ascending order. This error may be avoided
by setting system(247)=1. Please also see error number 26530.
26571
70
DMAP - TYPE, RD - BIOMSG: ERROR 7777
If a double precision parameter is specified as follows:

type parm,,rd,,(dumvar=0.0)
then either incorrect values or garbage (e.g., #.#####-315) will be assigned to
this variable on the Digital ALPHA OSF/1 and INTEL NT Versions of MSC/NASTRAN.
Depending on the subsequent operations, a core dump similar to the following

messages may be produced.
BIOMSG: ERROR 7777 HAS OCCURRED IN ROUTINE tbk, FILE INDEX (FILEX) =
0
STATUS =
********* NASTRAN FILE TABLE *********

Avoidance: Modify the type statement as follows:
type parm,,rd,,(dumvar=0.d0)
26574
70
- Possible Wrong Answers
External Superelement - CSUPER, DBLOCATE
When using the external superelement feature in Version 69 with the DBLOCATE
method, if data recovery for a superelement is requested in a separate run from
the residual structure run (as shown in the superelement seminar notes), then
the answers may be incorrect. Note that this error report does not apply to
the enhanced superelement features introduced in Version 69, as external
superelement using the enhanced superelement technology is not supported in
Version 69.
Avoidance:
Change the following:
dblocate db=eqexins, where (peid=0), logical = rsdb

to:
dblocate db=bgpdts, where (peid=0), logical = rsdb
26575
est, UFM 1019
70
Miscellaneous - RCFILE - Enhancement Requ
Blank characters are significant in the symbol definitions in an RC file or on

the command line.
For example, in the following line:
SYMBOL = MTF
= /u/jfc/csr
The symbol name will be taken as

"MTF
"
and the value as

" /u/jfc/csr"
Write the symbol definition as
symbol=mtf=/u/jfc/csr
26586
70
- Missing View Factor Output
Heat Transfer Analysis - VIEW, CHBDYG,REV
Although the MSC/NASTRAN Quick Reference Guide description of the CHBDYG

element states that View factor calculations are not supported with the REV
option, Version 68 and prior releases supported the calculations when no third
body shadowing existed. In Version 69, even for this limited case, View factor
output for the CHBDYG element using the REV option is missing.
26609
Output
70
Post-processing - PARAM,POST,-2 - Missing
PARAM,POST,-2 does not properly output the geometry data blocks if

superelements exist.
compile phase0
alter 'POST=-2 OR ',''
if ( false ) then $
compile super3
alter 'RSPECTRX='
CALL OUT2GEOM CSTM,GPL,GPDT,EPT,MPT,GEOM2,GEOM3,GEOM4,
GEOM1,DIT,DYNAMICS,EQEXIN,BGPDT,CASECC//
OUNIT2/0 $
26620
70
d 112 - Inefficient Load Calculation
Transient Response Analysis - SOLs 109 an
In SOLs 109 and 112, transient response loads are computed inefficiently and,
depending on the number of time steps, may require significant CPU.
Avoidance: Insert the following DMAP alter in SOL 109 or 112:
compile sedtran
alter 'trlg ','trd1 '(,-1)
copy usetd/usett $
paraml usett//'trailer'/4/s,n,usetr $
PARAML USETT//'USET'//////'m'/S,N,NomSET/
's'/S,N,NosSET/
'o'/S,N,NooSET $
if ( nomset>-1 ) usetr=usetr-1 $ turn off m-set bit
i
26624
70.7
Wrong for Fluid Problems
DMAP - VECPLOT, option 1 - Output Matrix
In a fluid problem (CD=-1 on GRID entry), if option 1 is used in module

VECPLOT, then the output matrix is bad. A symptom of this error is indicated
by a different matrix trailer size in the f04 file as compared to the matrix
size printed in the f06 file. Sometimes "BIOMSG: ERROR 211 HAS OCCURRED IN
ROUTINE BLDPK" fatal message occurs. This output matrix is not used in any
standard SOL sequence, so only user-written DMAP may encounter this error.
26633
2001
04, Wrong Answers
DMAP - BNDSPC, APPEND - BIOMSG: ERROR 14
The BNDSPC module is a new module introduced for partitioned bulk data
superelements in Version 69. Its function is to take spcs and spcds on
upstream superelement boundary points and transfer them to the downstream
superelement with the same boundary point. While this module has passed many
tests, different bad behaviors have been detected on some input files,
including:
[The s-set variables appear out of sequence when printed by use of param,
usetprt, 0. If the input datablocks (YSB and YSD) to the BNDSPC module are
null, then corrupted output datablocks may be generated which may lead to
failure in a subsequent module with the following messages: this may be wrong.
delete this sentence from error report]
BIOMSG: ERROR 1404 HAS OCCURRED IN ROUTINE GETSTR ,
This error has
26634
GL
issing Plot Output
Postprocessing - PARAM,POST, ANALYSIS - M
Optimization jobs which have multiple analysis types and requests to the
MSC/NASTRAN plotter can cause problems with the OUTPUT2 file for MSC/PATRAN.
The OUTPUT2 file may be missing data and contain extra data.
Avoidance: Do not combine NASPLOT requests with PARAM,POST,-1 in solution 200.
26677
70
M 2051A, UFM 2052, SFM 3001
Single Point Constraints - SPC, SPCD - UW
If enforced displacements are specified on the SPC or SPCD entries on grid

points that are not in the structure, then the following messages:
*** USER WARNING MESSAGE 2051A (GP4)
UNDEFINED GRID POINT
x IN SPC SET
ALSO IGNORED)
y IGNORED. (ANY OTHERS

x IN SINGLE-POINT CONSTRAINT SET
are issued. These messages are the correct messages and the job should have
terminated in GP4. MSC/NASTRAN is designed to continue when spcs are specified
on non-existent grid points, but not on spcd values. However, the job will
continue without producing a uset table. The next module that needs the uset
table will then fatal with the following error message:
*** SYSTEM FATAL
26728
692
MESSAGE
70
Rigid Elements - RSSCON - UFM 4296, UFM 6
The shell-solid connector RSSCON fails for certain irregular geometries when
the ELEM option is used.
In the example, the following fatal messages are issued
*** USER FATAL MESSAGE 4296. (SECNSD) ILLEGAL GEOMETRY FOR QUAD4 ELEMENT
WITH ID =
129131
*** USER FATAL MESSAGE 6692 (SECSR )
RSSCON NUMBER 129780 CANNOT CONNECT AN EDGE OF SHELL ELEMENT
TO SOLID ELEMENT 129079
129131
The failure occurs when the shell element shares an edge with the solid element
and the shell plane is tilted
to the solid face.
Avoidance: Use the GRID option to make the connection.
26735
70
OL MEMSAVE IS UNDEFINED
Eigenvalue Analysis - EIGRL - UFM 17 SYMB
If the System Cell MEMSAVE=1 is specified instead of SYSTEM(229)=1, the run

results in a UFM 17.
26739
70
)=1 - Misleading Documentation
Documentation - EIGRL, NASTRAN SYSTEM(229
The documentation for SYSTEM(229), a.k.a. MEMSAVE, indicates that setting this
system cell to 1 reduces scratch space usage in Lanczos by 67%. This is the
maximum possible savings. Jobs that execute three shifts or less will
experience no savings.
26747
70
2, Wrong Answers
Superelements - MATREDU - SFM 4276 EC 301
In superelement analysis, if rigid elements or mpcs exist for a superelement

but no spcs exist, and damping elements exist that do not intersect the m-set
DOFs the damping effects are discarded. This may lead to SYSTEM FATAL MESSAGE
4276, ERROR CODE 3012 or wrong answers
1. Add a token grid point to the superelement. Autospc will cause the dummy
grid point to generate spcs.
or
compile semrb
alter 'matredu',''
paraml uset//'uset'//////'f'/s,n,nofset/
'a'/s,n,noaset/
'm'/s,n,nomset/
'o'/s,n,nooset/
's'/s,n,nosset $
matgen ,/iff/1/nofset $
equivx iff/rfa/nooset $
if ( nooset>-1
26752
70
; SDAMP - Inefficient Processing
Frequency Response - SOLs 11, 111 and 200
For modal frequency response (SOLs 11,111, and 200), if only modal damping
(SDAMP) exists in the model, then the uncoupled solution algorithm should be
used. However in Version 69.1, the coupled solution algorithm will be used
even though only modal damping exists in the model.
Avoidance: Insert the following dmap alter for SOLs 111 and 200:
$
compile freqrs souin=mscsou list
$$$$
alter ' frrd1 ','' $
FRRD1
CASES,DIT,CKDDF,CBDDF,CMDD,K4DDF,PDFI,FRLI,FOLI,
EDT,SILD,USETD,/
UDFI,FOLI1/SOLTYP/-1/////S,N,FIRSTBD0/FRRDSET $
$$$$
alter ' frrd1 '(2),''
FRRD1
CASES,DIT,CKDD,CBDD,CMDD,K4DD,PDFx,FRL,FOL,
edt,sild,usetd,/
UDF,fol1/
SOLTYP/-1/////s,n,firstbad/frrdset $
$
For SOL 11 (or 30) insert the following al

26762
70
U - Missing Eigenvector, UIM 5218
Eigenvalue Analysis - MGIV, GIV, HOU, MHO
On long word machines like CRAY, if the following user information message is
encountered in an eigenvalue analysis using a transformation method such as
Givens or Househoulder, then some of the eigenvectors requested may not be
output.
USER INFORMATION MESSAGE 5218
EIGENVALUE APPROACHING INFINITY AT ** MODE. EIGENVECTORS WILL NOT BE COMPUTED
BEYOND THIS POINT.
The error only occurs when ND on the EIGR entry is less than the number of
eigenvalues calculated. In this case there will be one missing eigenvector for
each mode that UIM 5218 is output for.
Avoidance: Increase ND by the number of missing eigenvectors.
26772
GL
C,TRAN - Wrong Answers
Nonlinear Transient Heat Transfer - TEMPB
If there are unreferenced type TRAN, TEMPBC entries in the test deck, then
different answers occur. This is a design limitation. TEMPBC entries
internally generate CELAS2 elements and DAREA input. The CELAS2 elements are
generated whether the TEMPBC is referenced or not and this may cause unexpected
results.
Avoidance: Remove any unreferenced type TRAN, TEMPC entries.
26775
70
Superelements - DEFORM - Wrong Answers
If DEFORM bulk data entries are included in a part superelement file (that is,
after a BDGIN SUPER= entry) they will be ignored.
Avoidance: Place DEFORM entries in the main bulk data deck.
26778
Wrong Answers
70
Nonlinear Transient Heat Transfer - EMG -
When multiple subcases are specified in a nonlinear heat transfer analysis in

MSC/NASTRAN Version 69, module EMG does not generate the nonlinear heat
transfer capacitance matrix BGGNL at the first iteration. This leads to wrong
answers.
Avoidance: Do not specify subcases.

26818
70
S=SAERO, UMERGE1 - SFM 3001
The design intent in solution 200 is that all static aeroelasticity subcases
should have the same boundary condition but that other analysis types can have
different boundary conditions specified. The sensitivity analysis for static
aeroelasticity may produce a fatal error in UMERGE1 of the form below if
different boundary conditions are applied to static aeroelastic subcases:
SYSTEM FATAL
MESSAGE 3001 MODULE = UMERGE1
THE INPUT DATA BLOCK NAMED USET
AT POSITION
1 DOES NOT EXIST.
USER INFORMATION: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING:
Avoidance: This following is a dmap avoidance for the problem:
compile pslgdv
alter 'desaerdr'(1,-1)
CALL SETQ CASES//SEID/PEID/S,MTEMP/S,K2GG/S,M2GG/S,B2GG/S,MPC/
S,SPC/S,LOAD/S,DEFORM/S,TEMPLD
26825
Nonlinear Slide-Line Analysis - BLSEG, BCONP - Wrong Answers
The statement below is in error. Replace unsymmetric with symmteric and

vice-versa. Unsymmetric is the default and use the deafult option.
Rakesh Allahabadi
Wrong answers may occur for nonlinear slide-line analysis when the unsymmetric
search option, PTYPE=2 on the BCONP bulk data entry is selected.
Avoidance: Use the symmetric option which is the default.
26842
es Ignored
70.5
Superelements - ASETi, BSETi, CSETi Entri
When part superelements are present, aseti entries in the main bulk data
section are ignored. That is all free degrees of freedom are placed in the
a-set, and none in the omitted set. In a non-superelement model all free
degrees of freedom not placed on aseti entries are moved to the omitted set.
Avoidance: An avoidance is to use BSETi entries in place of ASETi entries
26844
Aeroelastic Analysis - SPLINEi, OMITi, ASETi - Wrong Answers
In SOL 144 and for ANALYSIS=SAERO in solution 200, wrong answers will result if
the user splines the aerodynamics to omitted degrees of freedom.
Avoidance: Do not spline to omitted structural degrees of freedom
26846
ith batch=yes
70
Submittal - XNASTRAN - Job will not run w
If a job is submitted using the XNASTRAN GUI with "batch=yes" and the "after"
keyword blank, the job will not execute.
Avoidance: Set the "after" keyword to a non-blank value. Setting "after=now"
will cause the job to run as soon as it's submitted. See the at(1) man page
for additional information and acceptable keyword values.

26855
70
ts Written to OUTPUT2 File
Postprocessing - PARAM,POST - Wrong Resul
If PARAM,POST,-1 or -2 is specified in a modal response run (e.g. SOL 111 or

112), and XYPLOTS are requested, or SORT2 output is requested, then the
displacements written to the OUTPUT2 file are the modal eigenvectors instead of
the frequency or transient response solutions.
Avoidances: Two avoidances follow, however, the first avoidance is inefficient
and the second avoidance is recommended.
1) Insert PARAM,DDRMM,-1
or
2) Insert the following DMAP alter (V69.x)
compile sedrcvr
alter 'if ( app1=\'mmreig\' and not(sort2) )',''
if ( app1='mmreig' ) then $
alter ' sdr3 ',''
SDR3
qUGV1,OPG1,qQG1,qEF1,qES1,qSTR1/
OUGV2,OPG2,OQG2,OEF2,OES2,OSTR2 $ SORT2 OUTPUT
26866
70
Miscellaneous - CURV - SFM 6806
In MSC/NASTRAN Version 69, if the CURV module is used with elements other than
QUAD4s or TRIA3s the run may abort with the following message:
*** SYSTEM FATAL MESSAGE 6806 (CURV)
RETURNED ERROR CONDITION
-3, LOC CODE =
FILE NUM = 104
(NOTE ADDITIONAL MESSAGES.)
645, IN SUBROUTINE CURV1,
No CURV module output will occur. The non-CURV module output will be available
in the f06 file and is unaffected.
26867
70
- SELA, INREL - UIM 4570, UFM 4575
If inertia relief is requested in solution 200 with superelements then the run
may fail with UIM 4570 and UFM 4575.
compile pslgdv
alter 'null egx'
type parm,,i,n,nopgs $
NOPGS=NDVAR*6 $
matgen ,/egpg6/7/lusets/nopgs $
26869
70.0.1
DMAP - OUTPUT4, Sparse - Quits No Message
If an OUTPUT4 request is made for a sparse, formatted matrix, then the job
quits in the OUTPUT4 module with no message, no "END OF JOB" and the OUTPUT4
file is empty.
Avoidance: Do not request sparse output.

26879
70
EIGRL - Poor performance
Eigenvalue Analysis - SOL 3, 10, 11, 12,
A lanczos eigenvalue analysis, EIGRL entry, may require more memory in

solutions 3, 10, 11, and 12 than in Version 68.2 or the corresponding
structured solution sequence.
malter 'cmset=\'v\''
cmset='a' $
26899
Composites - Buckling, PCOMP - Spurious Modes
Spurious modes may be observed in linear buckling (Sol 105) of composite

shells that have extremely soft transverse shear material properties. The
error is under investigation but it is possible that the spurious modes are be
due to a limitation in Mindlin shell theory.
26953
70.5
in sample problem input deck
Documentation - V69 Release Notes - Error
The input deck for the V69 Release Notes sample problem "blexam.dat" contains
an error on the continuation card for PBARL 1 (should be "A" instead of "B").
This error is in the file itself as well as the book (pp. 55-57). If run as
is, the input gives a fatal error. The corrected test deck has been put on the
Version 70.5 delivery in the archive directory, the documentation can not be
updated.
27029
70.5
Loads - DEFORM, GRAV - Wrong Answers
If DEFORM entries are combined with GRAV entries with the same SID, wrong OLOAD
resultants and wrong answers result. It is documented that DEFORM entries
require unique SID; however, the following fatal messages should be issued not
wrong answers:
USER FATAL MESSAGE 628 (IFP1D)
THERMAL, DEFORMATION, AND EXTERNAL LOADS CANNOT HAVE THE SAME SET
IDENTIFICATION NUMBER.
or:
USER FATAL MESSAGE 2134 MODULE = GP3
LOAD SET
1 DEFINED FOR BOTH GRAVITY AND NON-GRAVITY LOADS.
27036
70
Loads - PLOAD1, FRPR - Erroneous Output
When applying a PLOAD1 with a SCALE of FRPR, and the load direction is parallel
(or near parallel) to the beam element, then a zero load will be generated in
versions prior to Version 69. In Version 69, an undefined load is generated
which leads to output that contains the following character "NANQ".
Avoidance: Since the load is parallel to the axis, use the SCALE of FR instead.
27048
2001
RESP1 - SFM 4276, Trap Encountered
Optimization/Design Sensitivity - FREQ, D
If a FREQ response type is used on the DRESP1 entry and the associated
eigenvalue is negative, the code
attempts to compute the frequency by taking the square root of the negative
eigenvalue, subsequently a trap occurs in subroutine dsad11 and the job
terminates without a meaningful explanation.
Avoidance: A negative eigenvalues typically occurs with unsupported rigid body
modes. It is probably not the
intent of the user to place design conditions on these roots. Therefore,
review the design intent and force the eigenvalue analysis to only find
non-negative eigenvalues.
27055
)
70
Static Analysis - SNORM - UFM 316 (IFPDRV
Even though GRID ids may be up to one hundred million, the GRID ids referenced
on a SNORM bulk data entry must be less than one million. If larger GRID ids
are referenced the message:
ILLEGAL DATA ON BULK DATA ENTRY SNORM
will be issued.
Avoidance: Other than renumbering the model so that the grid id's are less
than one million, there is no avoidance.
27065
DMAP - Inconsistent lusets - Possible Infinite Loop
When using dmap, the lusets parameter of the TA1 module must be set consistent
with the values in the SIL table. If these values are not set consistently,
the results are unpredictable. In one instance, when lusets was set to 1
rather than the value of 150 set in the SIL data block, the TA1 module produces
a corrupted gpect data block. When this data block is subsequently input to
the EMA module, the job is trapped into an infinite loop and terminates only
after it runs into a resource limit (e.g., insufficient disk space).
Avoidance: Set the luset value equal to the second word in the trailer of sil
LUSET is used as a module parameter in not a few modules.
It also appears in a few data blocks. It cannot be arbitrarily set
a number, instead, it is determined by the model, otherwise,
error will occur!
In the system development, you can use a data block which includes the LUSET to
avoid use LUSET as a module parameter.
This is a good idea, but need not mandatory to do so.
Charles
27139
70
DMAP - DBDICT - Missing Output
The datablk(local) option of the dbdict DMAP command which should list the
non-nddl datablocks contained in a subdmap does not work.
Avoidance: DBDIR ////64 $ can be used to provide the same information.
27147
- SFM 2085
70
Nonlinear Analysis - CBUSH, PARAM,LGDISP
Nonlinear jobs with PARAM,LGDISP,1 and CBUSH elements may fail with the
message:
SYSTEM FATAL MESSAGE 2085 MODULE = NLITER
ELEMENT TYPE
102 NOT SUPPORTED FOR NONLINEAR ANALYSIS.
SYSTEM FATAL MESSAGE 3007 MODULE = NLITER
ILLEGAL INPUT TO SUBROUTINE NLEMG
Avoidance: Other than not selecting PARAM,LGDISP there is no avoidance.
27247
utput
70.5
Static Analysis - SOL 1, LSEQ - Missing O
Solution 1 accepts the LOADSET case control command and the LSEQ entries it
references. It calculates loads and solutions
for all of the load conditions listed on LSEQ entries, but outputs loads only
for the first loading condition.
Avoidance: Use subcases with LOAD commands instead.
27255
DMAP - TABPT, CASECC - SFM or Nan in Output
When a user dmap uses the TABPT module to print the CASECC datablock, a system
fatal message may occur on certain platforms if a parameter is specified in the
case control. Other platforms may not give a system fatal message, but
instead print "nan" or "Nan" in the output.
Avoidance: Put the parameter in the bulk data if possible.
The problem is due to a non-printable (at least in some platforms)
simbol used as a end -of-entry mark. To avoid this, tabprt should
be used instead of tabpt.
Charles
27257
299 (PARCPU)
70.7
Parallel Processing - SYSTEM(107) - SWM 6
In NASTRAN Version 69 through Version 70 on HP computers with pa2.0 chips and

on all NASTRAN versions on SUN Solaris Version 7, the following message in the
execution summary will indicate that no parallel processing is occurring, when
in fact it is:
*** SYSTEM WARNING MESSAGE 6299 (PARCPU)
NO PARALLEL PROCESS CREATED
Avoidance:
Ignore the message.
27286
2001
H) - Mislabeled Punch File
Transient Response Analysis - STRAIN(PUNC
When strain output is requested for transient analysis, the punch file labels
it "POINT ID" instead of "ELEMENT ID". The element ID numbers and the "ELEMENT
TYPE" labels are correct.
27291
70
Eigenvalue Analysis - REIGL - Incorrect H
iwater Memory Output, Poor Performance
The REIGL module does not keep track of the maximum amount of memory it uses so
the HIWATER value reported in the .f04 file may be underestimated for
eigenvalue jobs that go through REIGL. An eigenvalue run using mem=X, where X
is the HIWATER value from a previous run of the same deck, may run slower, use
a smaller MAXSET (Lanczos block vector size), require many more solves, or may
not have sufficient memory to complete.
27368
Executive - ASSIGN - Cryptic Message, SFM 1019
If a file exists and the keyword NEW is indicated on an ASSIGN statement SYSTEM
FATAL MESSAGE 1019 will be printed. Included in this message is text returned
by the operating system. It should be noted that under some operating systems
this text does not always clearly indicate the nature of the file open problem
and may include the somewhat cryptic message "Not a typewriter (errno=25)".
27503
70
Superelements - Split Database - UFM 1127
When using a split database with superelement in Version 69, if the upstream
database for a superelement is offline during a residual structure run, then
the job will fail with the following error messages:
DMAP MODULE XPURGE IS ATTEMPTING TO ACCESS DATA BLOCK 201 NAME = BTOPO WHICH
IS ON AN UNAVAILABLE DBSET
Avoidances: 1. Leave the upstream database online.
2. Modify the NDDL. Replace "PATH NLOOP ..." with:
" PATH NLOOP
PEID,APRCH,HIGHQUAL,NLOOP $"
27515
SSSALTERS - rflagb.v69 - Restarts
Restarts using the rflagb.v69 alter in the sssalter directory have not been
tested. While some restarts may work correctly, this can not be determined for
any particular run without testing, and perhaps modification of the alter.
Restarts are not supported for production work, and should be regarded as an
experimental technique when using the
alter.
Avoidance: Do not use the alter for restarts on production runs.
27516
70
SSSALTER - effmassa.v69 - UFM 2025
The effmassa.v69 dmap alter included in the sssalter directory for V69 may fail
with the message:
USER FATAL MESSAGE 2025, UNDEFINED COORDINATE SYSTEM
Avoidance: The cause of this is under investigation. If you encounter this
error, contact MSC client support for an updated version of the alter.
27524
2001
Superelements - DMIG - UFM 327
If a DMIG matrix is input after two or more BEGIN SUPER or BEGIN AUXMODEL bulk
file delimiters, and the DMIG matrix in each partitioned file has the same
name, an error message of the form
*** USER FATAL MESSAGE 327, BAD DATA OR FORMAT OR NON-UNIQUE NAME. DMIG AXGGT
SORTED CARD COUNT =
1
is produced.
Avoidance: An avoidance is to place a second dmig matrix in each file, with a
different name. Only a header entry is needed. The code keeps only one name
from the dmig entries in the bulk data deck stored between repeated calls to
ifp.
27533
70
n SGI R4400 Computers -Very Serious
Matrix Methods - SPARSE - Wrong Answers o
In Version 69 on SGI R4400 computers, if the memory specified with the default
memory or a mem= on the command line causes the MEMORY AVAILABLE to be between
the MINIMUM MEMORY REQUIREMENT and the SPARSE DECOMP SUGGESTED MEMEORY as
listed in USER INFORMATION MESSAGE 4157 of the f04 file, bad results may be
calculated. One symptom of the bad results is a very large epsilon in the f06
file. Larger problems are more likely to be affected by this. Sometimes under
these conditions the problem will terminate with a Segmentation fault.
Avoidance: Specify more memory or set SYSTEM(205)=1 and SYSTEM(198)=1. The
latter avoidance can cause up to a 30% increase in decomposition times. MSC
RECOMMENDS adding the two system cell settings to
install_dir/conf/irix/nast69rc for V69 and install_dir/co
27561
70
Wrong Answers in XDB
The nonlinear stress values for
in the .XDB graphical database.
the stress for the y direction.
strains for the center point).
NPENR.
Post Processing - CHEXA, CPENTA, CTETRA the center point of any solid element are wrong
The stress in the x direction is swapped with
All other data is correct (including nonlinear
The data blocks affected are NHEXR, NTETR, and

27572
69.1
UFM (decode_keyword)
Documentation - Logical Symbol, RC file -
In Version 69, you can define a logical symbol in the RC file. However, if the
logical symbol is defined in the rc file as shown on page 43 of the MSC/NASTRAN
Configuration and Operations Guide, then the job will fail with the following
error messages:
*** USER FATAL MESSAGE (decode_keyword)
SYMBOL XXX=yyy
Set by ./.nast691rc[1].
This keyword is not recognized.
Avoidance: Replace the following statement
SYMBOL DATADIR=/dbs/data
with
SYMBOL=DATADIR=/dbs/data
27580
70.0.1
PLOT - SEUPPLOT - Incorrect Plots
If a superelement run is sent to the plotter and the residual contains no plot
information, the resulting plots may be bad for SEUPPLOT 0.
Avoidance: Include at least one grid/scalar which has a finite displacement.
27597
70.5
slabeled Datablocks
Postprocessing - PARAM,POST,-1 or -2 - Mi
Solutions 1-16 are new in Version 69. If PARAM,POST,-1 or -2 is used in these

solution sequences, the output datablocks are mis-labeled. For example, GEOM1
will be mis-labeled as IGEOM1 on the output file and I-DEAS or MSC/PATRAN will
not interpret the data properly.
Avoidance: Other than using solution 101 thru 200 there is no avoidance.
27598
70.5
P COUPLED - UFM 9086
Heat Transfer Analysis - Restarts with AP
A restart into a structural analysis with APP COUPLED from a previous heat
transfer run fails with the message:
USER FATAL MESSAGE 9086 (GETLOOP)
THE DATA BASE IS INSUFFICIENT FOR PARAM,LOOPID RESTARTS. CHECK FOR BULK DATA
CHANGES RELATED TO
GEOMETRY, CONNECTIVITY, AND PROPERTIES, WHICH CAUSE THE RECALCULATION OF
NONLINEAR DATA.
Avoidance:
Insert the following DMAP alter:
compile super1
alter 'PARAML CASECC',''
type parm,nddl,i,y,subid $
PVT
PVT,CASECC/PVTX $
PARAML CASECC//'DTI'/SUBID/251////S,N,PATH $
compile getloop
alter 1
type parm,nddl,char8,n,aprch $
if ( GETSYS(1,21)=5 and APRCH='
' ) APRCH='HEAT
27611
70
CD, BC - Wrong Answers
' $
Optimization/Design Sensitivity - SPC, SP
In Design Optimization (Sol 200) with multiple boundary conditions, an enforced

displacement of 0.0 is not preserved after the initial design cycle when one
subcase puts a non-zero enforced displacement (using SPC or SPCD) on the same
degree of freedom that a different subcase puts an enforced displacement of
0.0. When these conditions apply, the initial design cycle will be correct,
but the subsequent design cycles will put the nonzero enforced displacements on
all subcases.
Avoidance: Use the following DMAP avoidance:
compile update nolist, noref $
alter 129 $ V69.0
$alter 132 $ V69.1
paraml ysb//'null'////s,n,nullysb $
if (nullysb < 0) then $
matgen ,/yg1/7/lusets/1 $
else $
alter 130 $ V69.0
$alter 133 $ V69.1
endif $
27617
oop
70
SSSALTERS - alter9ga.v69 - Infinite cpu L
If alter9ga.v69 is used in a frequency response solution, an infinite cpu loop

will result. This problem did not occur in previous versions of the alter.
Avoidance: Call MSC and request an updated version of the alter.

27623
70
Superelements - SELA - Wrong Answers
If there are more than 5 superelements at a single level, then the static load
matrices in the downstream superelement will be wrong.
Avoidance: Increase BUFFPOOL on the NASTRAN statement or insert the following
DMAP alter:
compile fea noref nolist
alter 'return'(,-1)
dbdelete datablk=(zuzr11) where(zname='pav' and zuzr1=*) $
$
compile sela1 souin=mscsou noref nolist
ALTER 'TEMP=SEID','END $ SELA1'(1,-2) $ V68.2.3 and up
call dbfetch /pav,,,,/s,seid/0/0/0/0 $
add5
pav,pjc,,,/pg $
$
compile phase0 noref nolist
$
$ The alter and GP1 call are for V68.2.3 and up
$
ALTER 'IF ( IMAGE OR EXTER ) THEN'(1,+1) $ V68.2.3 and up
GP1
GEOM1I,GEOM2Scr,,GDNTAB,MEDGE/
xGPLS,xeQEXIN,xGPDT,xCSTM,xBGPDT,xSIL,xVGFS/
S,N,xLUSET/0/NOGPDT $
call dbstore xeq
27629
70.5
Buckling - EIGB,SINV - UWM 6278
A buckling analysis in Version 69.1 that specifies the SINV method will issue
the warning message:
*** USER WARNING MESSAGE 6278 (MTMD23)
THE BULK DATA ENTRY SELECTED BY THE CASE CONTROL COMMAND METHOD
FOUND
= xx WAS NOT
If there is no fatal message printed in the f06 file, this warning message can
be safely ignored.
1. Ignore the extraneous warning message.
2. Use Lanczos method.
27647
70
tor Information not Written to XDB
Post Processing - CBEAM - Orientation Vec
When the GRID option is used to define the orientation of the CBEAM element,
the orientation information is not written to the XDB file.
Avoidance: Other than using the vector option, there is no avoidance.
27659
70
TSUB - Wrong Answers
Optimization/Design Sensitivity - BC, STA
Eigenvalue sensitivity analyses (normal modes and buckling) require the

associated eigenvectors. In Version 69, the
appropriate set of normal modes eigenvectors is selected based on the BC case
control command. For buckling, the
STATSUB command is used. If BC or STATSUB does not result in a unique
eigenvector set, wrong answers can result.
Avoidance: Use BC and STATSUB requests in a way that ensures uniqueness.
27674
69
PTION NUSR NOT IN APPROVED LIST
Security - UFM 3060, SUBROUTINE MODEL - O
The message "USER FATAL MESSAGE 3060, SUBROUTINE MODEL, OPTION NUSR NOT IN
APPROVED LIST" will appear when running on Windows NT systems that allow
multiple users to run concurrently, e.g., Windows NT 4.0 with "remote shell"
support. The problem has been fixed in MSC/NASTRAN V69.0.4 on the updated
Windows NT CD released with the Digital Alpha NT system.
27677
ed Features
70
Documentation - SEMPLN,NORMAL - Unsupport
When defining the mirror plane for a partitioned, image superelement, only the
MTYPE=PLANE option on the SEMPLN entry is supported. The Version 69.1 Release
Guide incorrectly states that the MTYPE=NORMAL option is also supported.
Avoidance: Use the MTYPE=PLANE option on the SEMPLN entry.
27685
mation in XDB
70
Post Processing - CTRIAX6 - Missing Infor
The "negative" key is not written to the STX6R Object to distinguish between
Von Mises and Octahedral Shear stress results for the CTRIAX6 element.
27704
2001
Nonlinear Transient Heat Transfer - CP is
Temperature Dependant - Wrong Answers
If CP, specific heat is a function of termperature, in a nonlinear heat
transfer transient analysis then wrong answers will be produced.
Avoidance: There is no avoidance
27717
70.5
Wrong Margins of Safety in XDB
Postprocessing - BAR, BEAM, ROD, CONROD -
The Bar, Beam, Rod and Conrod elements all get wrong answers for the margins of
safety in the .XDB file.
27722
M 5199
70
Documentation - QRG, PARAM,PRETEQXIN - UF
The MSC/NASTRAN Version 69 Quick Reference Guide incorrectly documents

PARAM,PRETEQXIN, the parameter should be PARAM,PRTEQXIN. If PRETEQXIN is
specified USER FATAL MESSAGE 5199 may result.
27734
ads
70
Documentation - QRG - ESE With Thermal Lo
Prior to Version 70 element strain energy output was incorrect in the presence
of thermal loads. This limitation was documented in the Quick Reference Guide
under Remark 4 of the ESE Case Control Command. This limitation has been
removed in Version 70 but the Version 70 QRG had already been sent to press, so
Remark 4 was not removed.
27739
4276
Nonlinear
with USER
dependent
corrected
70
Nonlinear Heat Transfer - SDR3, XDB - UFM
Heat Transfer jobs that request an XDB (i.e. param,post,0) may fail
FATAL MESSAGE 4276 on HP 9000/700 systems. The error appears to be
on problem size, machine and operating system. The error has been
in Version 70.
Avoidance: Other than running on a different system there is no avoidance.

27747
70.5.1
FM 3007, Wrong Answers
Heat Transfer Analysis - CHBDYi, SSG1 - S
If the model has nonunique element IDs among with heterogeneous type of
CHBDYP,CHBDYG, or CHBDYE , MSC/NASTRAN does not know which CHBDYx element ID
should be used in the convection or radiation. This confusion in the code may
lead to wrong answers or SYSTEM FATAL MESSAGE 3007 in the SSG1 module. The
fix to the code allows the program to flag the non-unique CHBDYP and CHBDYG in
the GP2 module.
Avoidance: Change the Element IDs of CHBDYP and CHBDYG so that the IDs are
unique.
Duplicate CHBDYi element ids may result in the message:
27755
Eigenvalue Analysis - EIGRL, REIGL - SFM 5299
Small models with many repeated modes may require smaller values for MAXSET
else the following message may be encountered:
*** SYSTEM FATAL MESSAGE 5299.UNRECOVERABLE TERMINATION FROM LANCZOS ITERATION
INTERNAL ERROR CODE = -3
USER ERROR RETURN = -33
Avoidance: Reduce the value of MAXSET on the EIGRL entry.
27757
70
WM 4398, BIOMSG ERROR 1305
P-Elements - FEFACE,SURFID, EMA, GPSP - U
If p-elements have FEFACE records that use SURFID to specify the geometry of
the edges of the face, bad answers or one of
the following messages may result.
Module EMA may give the message:
BIOMSG: ERROR 1305 HAS OCCURRED IN ROUTINE ENDPUT,
FILE INDEX (FILEX) =
0
Module GPSP may give the message:
USER WARNING MESSAGE 4398 (GPSP)
GRID POINT nnnnnnnnn FOR TRANSLATION DEGREES OF FREEDOM DOES NOT
PASS SYMMETRY CHECK. NO SINGULARITY TESTS MADE ON THESE TERMS.

Avoidance: This error occurs when several elements are connected to the edge
with conflicting geometry. The only known avoidance is to identify the edges
which are failing, and use consistent geometry for the FEFACEs which are
associated with the edge.
27761
uffix
70
Submittal - Can't Modify the Input File S
In Version 69, there is no simple method to specify a user or site-dependent

default input file suffix for the nastran command.
The V70 nastran command allows the keyword 'j.dat' in the '.ini' file to define
the default input file suffix. For example, 'j.dat=.bdf' sets the default
suffix to '.bdf'.
Avoidance: There is no simple avoidance. The nastran script could be
modified by the user to add a suffix whenever one is not provided. Since the
order of input to the nastran command does not matter, the script would have to
search for the input with no equal sign and then append the desired suffix to
that input.
27762
2001
P-Elements - EMG - SFM 3008
A p-element run may terminate with a fatal message if a shell p-element and a
solid p-element share a face and the p-order of the edges of the face is higher
than 2. There is no avoidance to this errror. The following fatal message is
issued
0*** SYSTEM FATAL
MESSAGE 3008 MODULE = EMG
0INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE PSHELD
0FATAL ERROR
27774
70
Documentation - EXTRN - Incorrect Format
The format for the EXTRN entry as shown in the Version 69.1 Release Guide is
incorrect. The correct format is as follows:
EXTRN
GID1
GID5
C1
C5
GID2
-etc-
C2
GID3
C3
GID4
C4
Avoidance: Correct the entry as shown above.

27775
70
Documentation - SEBULK - Incorrect TYPE
When defining the superelement boundary search options for the external
superelement using the partitioned bulk data method, the TYPE field on the
SEBULK entry should be specified as EXTERNAL. The V69.1 Release Guide
incorrectly states that the TYPE field is either EXTRNLG or EXTRNLA. The
documentation will be corrected in the Version 70 Quick Reference Guide.
Avoidance: Use TYPE is equal to EXTERNAL.
27789
Wrong answers
69.0.4
Matrix Methods - PARALLEL, SYSTEM(107) -
If parallel processing is selected by setting SYSTEM(107) or the PARALLEL

keyword on MSC/NASTRAN Version 69.0.2 for Windows NT wrong answers may result.
Avoidance: Other than not selecting parallel there is no avoidance. A new

version of MSC/NASTRAN Version 69 (V69.0.4) is in the process of being released
and the problem will be corrected in this version. Also, the new executable
(analysis.exe) is available on the MSC FTP site, in file mscnv69.exe in the
/pub/outgoing directory. This is a self-extracting ZIP file that contains a
single file, analysis.exe. To update an installation, copy this mscnv69.exe
file to the install_dir\msc69\i386 directory and run it by entering "mscnv69".
Reply "y" to the request to overwrite the existing executable (or rename the
existing executable be
27804
2001
ated in .ini File - UFM 3060
If during an
authorization
default, the
authorization
27811
rmation
Installation - Authorization File not Upd
installation of MSC.Nastran on an NT system an existing

file is selected and that file's name is different from the
.ini file will not be updated with the location of the
file. This will lead to USER FATAL MESSAGE 3060.
70.5
Documentation - PBARL, QRG - Missing Info
In the MSC/NASTRAN Quick Reference Guide it states that elements which use the
PBARL entry to define their properties have the origin of the element
coordinate system at the shear center of the cross-section. The manual does not
state that the PBARL does not account for offsets between the neutral axis and
shear center. Therefore, the CHAN, CHAN1, and CHAN2 cross-sections may produce
incorrect results.
Avoidance: If a cross-section does not have coincident shear center and
neutral axis, use a PBEAML.
27819
2001
e Strain - Wrong Answers
Miscellaneous - GPSTRESS, Von Mises, Plan
In a plane strain analysis, the von Mises stress output using the grid point
stress option is incorrect. The component
stresses using the grid point stress option are, however, correct.
Avoidance: If feasible, use the von Mises stress output from the element
stress output.
27820
Nonlinear Analysis - PELAST - Possible Wrong Answers
When the nonlinear property PELAST is used for the scalar spring, CELAS1 or
CELAS3, the linear stiffness, Ki, must be greater than zero. If Ki is non-zero
the actual value is replaced by the PELAST function. However, if 0.0 is
entered then the value of 0.0 is used.
27821
70.5
ch standard MSC/NASTRAN RC files
ESTIMATE - Estimate Utility does not sear
The ESTIMATE utility does not examine the standard nast*rc files to determine
default settings for any of its keywords.
Avoidance: In order to set default values, you must set them in the
$MSC_BASE/$MSC_VERSD/$MSC_ARCH/estimate.ini, $HOME/.estimaterc, or the
./.estimaterc files.
ESTIMATE V70.5 will use the nastran command to search the standard MSC/NASTRAN
RC files. In order to do this properly, (i) the nastran command executable
must present in the same directory containing the ESTIMATE executable, and (ii)
ESTIMATE must be passed the same values for <version> and <rcf> (if any) that
will be passed to the nastran command. Items set in the ESTIMATE RC files and
on the ESTIMATE command line will override the MSC/NASTRAN RC files.
27822
- UFM 316
70.5
Optimization/Design Sensitivity - MODTRAK
The Quick Reference Guide appears to allow the user to leave the HIGHRNG field
blank with the algorithm defaulting to
the highest extracted mode. However, if the user has set LOWRNG and leaves
HIGHRNG blank, the following fatal message is issued:
ILLEGAL DATA ON BULK DATA ENTRY MODTRAK
Avoidance: Either remove the LOWRNG value or specify the HIGHRNG value.
27824
70
SIGNAL 10 ABORTING
Miscellaneous - SDR3 - SFE 4276 EC 7777,
On the HP that uses the PA2.0 processor, if the SDR3 module is being exercised
(whether it is through user-dmap or executed automatically by the SOL sequence,
e.g., SOL 111), the job may fail with the following error messages:
***** RECEIVED SIGNAL 10, ABORTING ...
BIOMSG: ERROR 7777 HAS OCCURRED IN ROUTINE RECOVR , FILE INDEX (FILEX) =
0
0*** SYSTEM FATAL ERROR 4276.RECOVR ERROR CODE
7777 PID= 0
The module SDR3 is used to convert sort1 output to sort2 output.
Avoidance: If feasible, use sort1 output instead of sort2 output to avoid
execution of the SDR3 module.
27826
70
acking and Acoustics - UFM 6677
Optimization/Design Sensitivity - Mode Tr
If fluid elements are present in SOL 200 and mode tracking is requested the run
may fail with:
USER FATAL MESSAGE 6677 (DOM12E)
RUN TERMINATED DUE TO MODE TRACKING FAILURE. SEE USER FATAL MESSAGE 6677
(MTFTRD) PRINTED ABOVE FOR INFORMATION.
COMPILE FEA
ALTER 'MODTRK','MODTRK'
MODTRK CASEM,EDOM,LAMAS,MGG,MAA,PHG,PHSA,
PHGREF0,PHAREF0/
MTRAK,NEWLAMA,NEWPHG,NEWPHA,PHGREF,PHAREF/
DESCYCLE/S,N,NOTRACK $
27828
70
Heat Transfer Analysis - RADMT - UFM 4658
Large models with RADMT bulk data entries may fail in NLITER with the message:
USER FATAL MESSAGE 4658 . DIFFICULT GEOMETRY PREVENTS FURTHER COMPUTATIONS

FOR ELEMENT WITH ID = ***
Avoidance: The only avoidance is to increase memory.
27833
NASTRAN
2005
Documentation - Getting Started with MSC/
The "Getting Started with MSC/NASTRAN User's Guide" states that "In any
coordinate system, all angular input is in degrees, but output ... is in
radians". This statement needs clarification. The "input" refers only to
geometric locations. If an angular enforced displacement is specified the
input is in radians.
27867
70
INPUT TO SUBROUTINE MPGTKG
Superelements - SEMA - SFM 3007, ILLEGAL
Superelement jobs with SETs with large thru ranges may encounter the following
fatal message:
SYSTEM FATAL MESSAGE 3007 MODULE = SEMA
0ILLEGAL INPUT TO SUBROUTINE MPGTKG
0FATAL ERROR
27872
Ignored
70
Dynamics - PARAM,APHAi - Raleigh Damping
Raleigh damping is ignored when using param,alpha1 (proportional to mass) and

alpha2 (proportional to stiffness).
Avoidance: Add the following dmap avoidance.
compile gma $
alter 'call.*xadd5.*mhh.*khh.*bhh','' $
add5 mhh,khh,bhh,,/bhhx/alpha1/alpha2/cu $
alter 'call.*xadd5.*mdd.*kdd.*bdd','' $
add5 mdd,kdd,bdd,,/bddx/alpha1/alpha2/cu $
27879
70
ents - Missing Data from XDB
Post Processing - Optimization, Superelem
In solution 200 with superelements, requested data may be missing from the XDB
for any design cycle after the initial analysis.
compile update
alter 'do while'(,-1)
descycle=descycle-1 $
alter 'descycle=descycle-1',''
27880
70
T,0 - SWM 6065, 6066
Superelements - Postprocessing, PARAM,POS
Superelement jobs that set PARAM,POST,0 to produce an .XDB file may encounter
the following messages when the new partitioned bulk data superelements are
used:
SYSTEM WARNING MESSAGE 6065 (DBC)
*** DBCMSG ERROR MESSAGE 11 FROM SUBROUTINE DBCEQG
PREMATURE EOR FOR MSC/NASTRAN LOGICAL FILE GEOM1S
DBSET
0.
FOR SEID
0,
*** SYSTEM WARNING MESSAGE 6066 (DBC)

*** DBCMSG ERROR MESSAGE 34 FROM SUBROUTINE DBC
THE DBC MODULE HAS BEEN TERMINATED BECAUSE OF THE ABOVE FATAL DBC ERROR.
USER INFORMATION: SUBSEQUENT DBC CALLS WILL NOT BE EXECUTED, AND THE
DATABASE CONVERSION IS INCOMPLETE.
27881
70
Miscellaneous - IFPDRV - UFM 316
Large input files (<1 million entries) can cause overflow in the sorted entry
count of an error message. For instance:
ILLEGAL DATA ON BULK DATA ENTRY MPC 1 SORTED ENTRY COUNT = ******
^^^ USER FATAL MESSAGE 9002 (IFPS)
^^^ ERROR(S) ENCOUNTERED IN THE
MAIN BULK DATA SECTION
^^^ SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE
IFP,
27917
P1X - SFM 3001
70.5
Superelements - External Superelement, SE
In Version 69.1, when using the parameter EXTOUT=dmigop2 option for external
superelements, and more than one external superelement is brought in, then the
job will fail with the following error messages:
*** SYSTEM FATAL MESSAGE 3001 (SEP1X )
THE EXECUTIVE FILE
0 DOES NOT EXIST.
PROGRAMMER INFORMATION: SUBROUTINE SEPMAB
0FATAL ERROR
Avoidance: If more than one external superelement is to be brought in, use the
dmigpch option.
Or insert the following DMAP avoidance:
compile phase0
alter 'dbview geom1f','dbview
dbview geom1f=geom1qs where (
dbview geom2f=geom2s where (
dbview geom4f=geom4qs where (
dbview sgpdtf=sgpdts where (
27918
geom1f'(,3)
peid<>0 ) $
peid<>0 ) $
peid<>0 ) $
peid<>0 ) $
70
Miscellaneous - DEQATN - SFM 6048
A DEQATN entry is validated for syntax by evaluating the equation with all
variable set to zero. If this evaluation results in an invalid operation,
like the square root of a negative number, then the following message may be
unnecessarily issued:
SYSTEM FATAL MESSAGE 6048 (XQFNC7)
Avoidance: The error should be able to be avoided by adding appropriate
absolute value operators to the equation.
27927
escription
70
Documentation - QRG, PARAM,ACOUT - Poor D
The description of the ACOUT parameter in the Version 69 Quick Reference Guide
states;
To obtain sound pressure level in units of dB and dBA given by the FORCE,
DISPLACEMENT, and PRESSURE commands, a peak reference pressure must
be specified with PARAM, PREFDB.
The sentence should read:
To obtain sound pressure level in units of dB and dBA given by the FORCE
command, a peak reference pressure must be specified with PARAM, PREFDB.
27930
Acoustic Analysis - Modelling Error - SFM 6169, Poor Message
When a plate is immersed in a fluid, then the structural grid points will be
attached to up to eight fluid HEXA elements (more if PENTAs and/or TETRAs are
use) and two fluid/structure interfaces, one for each side of the plate
structure. The fluid grids on each side of the plate are on different
interfaces and thus must have unique coincident grids. Thus, at a point in
space there should be two fluid grids and one structural grid.
If only one fluid grid is erroneously used, that is, the fluid elements on both
sides of the interface use the same grid, then the following error will occur:
*** USER FATAL MESSAGE 6169, FOUND TWO OR MORE STRUCTURAL GRID POINTS WITH
IDENTICAL COORDINATES
WHICH LIE ON THE FLUID/STRUCTURE BOUNDARY.
USER ACTION: CHECK GRIDS AND/OR SET1 CARDS WHI
27936
70
issing FMS statements
Documentation - External Superelement - M
Item 1 of Step 3 of the data recovery procedure as described on page 8 of the

MSC/NASTRAN Version 69.1 Release Guide is incomplete.
Avoidance: Add the following FMS statements.
Assign sexx='step1.MASTER'
Restart logical=sexx
where step1.MASTER is the database from the first step.
27937
Ignored.
70
Miscellaneous - NASTRAN - NASTRAN Command
The NASTRAN command must be the first entry in an input file, disregarding
comment lines. If the NASTRAN command is mixed in with FMS commands such as
ASSIGN statements, the command may be ignored.
27938
UFM
70
Cyclic Symmetry - EMG - UFM 2016, Various
APP HEAT will be ignored in cyclic symmetry jobs. The job may fail in various
ways, one likely way is:
USER FATAL MESSAGE 2016 MODULE = EMG

NO MATERIAL PROPERTIES EXIST.
FATAL ERROR
Avoidance: Apply the following dmap avoidance.
COMPILE SUPER1 NOLIST NOREF
ALTER 'IF (GETSYS(1,56)=1)'(,-1) $
PUTSYS(1,56) $ HEAT TRANSFER
27944
70
Rigid Elements - RSSCON - UFM 6692
In nonlinear statics (Sol 106), the following user fatal messages are issued
when a bulk data entry RSSCON with option
"ELEM" is in the residual structure.
*** USER FATAL MESSAGE 6692 (GP4RS1)
BULK DATA ENTRY RSSCON CAN NOT FIND ELEMENT IDS, USER ACTION: CHECK
SUPERELEMENT STRUCTURE.
*** SYSTEM FATAL MESSAGE 3001 (GP4 )
11 DOES NOT EXIST.
Avoidance: Use the following DMAP alter which provides the element connection
GEOM2S to
the GP4 module.
compile nlstatic souin=mscsou, nolist, noref
alter 'GP4
CASESX2,GEOM4S','GP4
CASESX2,GEOM4S' $
GP4
CASESX2,GEOM4S,EQEXINS,SILS,GPDTS,BGPDTH,CSTMS,,,,GEOM2S,/
RGNL,YS1H,USET1,/
LUSETS/S,N,MPCF1/S,N,MPCF2/S,N,NOSSETX/
27964
Old Design Sensitivity - DSVG1, PARAM,EIGD - SFM 4276 EC 1409
IN ROUTINE GETSTR
When param,eigd,yes is used in solution 103 to calculate the eigenvector
derivatives, SYSTEM FATAL MESSAGE 4276 ERROR CODE 1409 is issued from module
DSVG1 in subdmap DSAMODES.
Avoidance: Use the alter evds103a.v691 provided in the SSSALTER library.
27968
Submittal - PSL: NUSR: unable to initialize (0 expired keys)
The following error is issued in

NUSR queues in the system. (i.e.
job gets killed some of the NUSR
following message will be issued
the log file when an abnormality occurs in the

if a nastran
queues will not be removed from the system and
when a subsequent job is started.
PSL: NUSR: unable to initialize (0 expired keys).

Avoidance: Flush the queues by rebooting the machine.
or,
Remove nastran related queues by the command
ipcrm -q PROCESSID of the queue.
27996
70
62, Subroutine CNSTRC
Superelements - Plotting, PLTSET - SFM 30
Use of a plot set defining a list of elements and grids to be used by the
structure plotter cause a SFM 3062 whenever the exclude option is used.
For example:
SET 1001 =110106 THRU 110452 110553 220101 THRU 220120 120274 THRU,
120292 120134 THRU 120178 230274 THRU 230286 220208 220218,
.
.
5033 5080 241 5034 5078 240 209 218 520 545 208 219,
exclude grid points 1 thru 999999
results in the SFM 3062 from the PLTSET module.
Avoidance: Commenting out the exclude set from the set definition allows the
run to proceed but the plots are not consistent with the request of the set.
That is, more information is plotted than requested.
28008
ack
2001
DMAP - MATMOD Option 2 - SFM 4276, Traceb
This option of matmod filters small numbers from the input matrix. When given
a complex matrix, a floating point overflow occurs at 1.E19 on rs/6000
computers, and other relatively small numbers on other computer types. Since
the range of this computer type is greater than 1.E30, this is not a reasonable
limitation.
The diagnostics from such a crash are machine dependent. On the rs/6000, the
following appears in the .log file:
Traceback:
Offset 0x00000028 in
Offset 0x0000042c in
Offset 0x000028e4 in
FP overflow
procedure pack_
procedure mtmd02_
procedure matmod_
Avoidance: Use the NORM module to first find the largest number in the matrix,
scale it with the inverse of this number before using matmod(2), then re-scale
the results. The NORM m
28009
76, EC 7777
70
Miscellaneous - TABLED1, TABLEM1 - SFM 42
Extrapolation of data from either TABLED1 or TABLEM1 entries beyond the end
points of the table may result in numerical overlfow. Version 70 has been
enhanced to trap machine overflow due to extrapolation and will issue USER
FATAL MESSAGE 6917 to address this error.
Avoidance: Add additional data points at each end of the curve to make the
curve flat so that extrapolation to any x value can not be unbounded.
28011
70.5
ot Codes - Missing Definitions
Documentation - CHEXA, CPENTA, CTETRA, Pl
The stress item codes 8, 16 and 22 in the Quick Reference Guide are incorrectly
labeled for the CHEXA (page A-7), CPENTA (page A-9 and A-10), and CTETRA (page
A-17). Modern textbooks arrange the principal stresses in this order:

First Principal> Second Principal> Third Principal. MSC/NASTRAN arranges the
principals as: First Principal> Third Principal> Second Principal. MSC/NASTRAN
arranges the principals this way because the principal stresses are the roots
of a cubic polynomial and the this is the order that the method that extracts
the roots puts out. The stress item codes 8, 16, and 22 for the solid elements
should have the labels changed to the following,
8 - First principal
16 - Third principal
22 - Second principal
A note should also be added to the element description
28027
g Answers
70
Elements - TETRA, TEMP(LOAD), MAT9 - Wron
In MSC/NASTRAN Version 69 on the IBM RS6000 power2 computer, the 10 noded TETRA
element in conjunction with MAT9 and thermal loads produces wrong answers
whenever there is also HEXA elements in the model.
Avoidance: The non-power2 executable can be selected with the exe submittal
line command but this executable will run significantly slower.
28047
rong Answers
70.5
Material Nonlinear Analysis - TABLES1 - W
If stress-strain data is entered on the TABLES1 entry in descending order wrong

answers may results.
Avoidance: Enter data in ascending order.
28052
70
109 - Wrong answers
Dynamics - OFREQ and OTIME, SOLs 108 and
The OFREQ and OTIME case control commands will produce wrong answers in SOLs
108 and 109 in MSC/NASTRAN Version 69.1.
Avoidance: Insert following DMAP alter to avoid this error:
compile disprs
alter 'upf1'
equivx upf1/upf/-1 $
28063
formance
70.5
Acoustic Analysis - SDR2,OUG1F - Poor Per
Acoustic analysis jobs that request data recovery sets with the thru option may
experience very poor performance in the SDR2 module.
28070
70
Left on Remote Node
Postprocessing - PARAM,POST,0 - XDB File
When using the <node> keyword, the XDB file is left on the remote node. This
file should have been deleted after it was copied from the remote node to the
local node.
Avoidance: Add the following line:
%trans=[ya]:%
%s.rsh% %node% -l %username% /bin/rm -f %r.out%.xdb
just before the following line in the <install-dir>/bin/nast*.rmt file:

%trans=[ya]:%}
28073
70
CTRIA3, SNORM - SFM 3062
Optimization/Design Sensitivity - QUAD4,
In Version 69.1 of MSC/NASTRAN, optimization and design sensitivity runs with

shell normals may fail with SYSTEM FATAL MESSAGE 3062.
28087
70
Parameter Not Passed to Utility
Miscellaneous - ESTIMATE - SMEM and BPOOL
If the ESTIMATE utility is being used by the nastran command to estimate the
memory requirements of a job, the nastran command fails to pass in either
"smemory" or "bpool". If set to non-default values, they could have a
significant impact on ESTIMATE's accuracy.
Avoidance: Either use the default "smemory" and "bpool", or set the values in
the following files:
UNIX: $HOME/.estimaterc or <jid-dir>/.estimaterc
NT: %HOME%\estimate.ini or <jid-dir>\estimate.ini
VMS: SYS$LOGIN:estimate.ini or <jid-dir>:estimate.ini
28088
70
S Defined in RC File Not Used
Miscellaneous - ESTIMATE, SYMBOL - SYMBOL
The nastran command will not use SYMBOLs defined in the RC files on the command
line.
For example, if the following line exists in one of the system RC files or the
$HOME RC file,
symbol=MYDIR=/my/main/project
The following will fail
msc69 nastran MYDIR:myjob ...
Avoidance: Set the SYMBOL values that will be used in the command line as
environmental variables, e.g.,
export MYDIR=/my/big/project
MYDIR=/my/big/project; export MYDIR
setenv MYDIR /my/big/project
# Korn shell
# Bourne shell
# C-shell
and use the environment variable on the command line.

msc69 nastran $MYDIR/myjob ...
28102
70
Submittal - System RC Files on Remote Nod
e Cannot Contain 'nastran' Statements
The system RC files on a remote system cannot contain a 'nastran' statement.
For example
$ msc691 nastran myjob node=remotenode ...

The system RC files on remotenode cannot contain a 'nastran' statement.
Note: This restriction *only* occurs if the "node" keyword is used.
Avoidance: Remove the 'nastran' keyword and set system cells by number. For
example, change
nastran system(196)=1, massbuf=10
to
system(196)=1
system(199)=10
28104
ision Machines
DMAP - TABPT of CSTM and BGPDT - Wrong Answers on Double Prec
If the TABPT module is used to print the CSTM or BGPDT tables on double
precision, short-word machines, then incorrect data for the tables is printed.
Avoidance: Use TABPRT (Formatted print of selected table data blocks) to print
the CSTM and BGPDT table.
TABPRT
TABPRT
TABPRT
TABPRT
$TABPT
CSTM/////1$
CSTM//'CSTM'$
BGPDT/////1$
BGPDT//'BGPDT'$
CSTM,EQEXIN,BGPDT/ $
28123
3) CD for HP
70
Installation - Invalid Media for V69.1 (R
The MSC/NASTRAN V69.1 (r3) CD has an error when attempting to install on an HP

system with a local CD. The installation script, mscsetup, will incorrectly
report the following error:
MSC Installation and Setup - Invalid Media
The specified CD pathname
/CDROM
does not contain any of the installation filesets.
Please ensure that the pathname is correct, and the correct installation
media is mounted.
Press ENTER or RETURN to continue...
1) Copy the installation script to a local directory
cp /CDROM/MSCSETUP.\;1 mscsetup
Change line 3475 from
iv_file="$iv_dev/${iv_file};1"
to
iv_file="${iv_file};1"
Install the CD using the modified scr
28124
o Convergence
70
Nonlinear Analysis - PELAST - UFM 4551, N
Nonlinear analysis with CELAS elements that reference PELAST may encounter
difficult converging. The problem is caused by an error in the element's
coordinate transformation.
Avoidance: Replace the nonlinear spring by a ROD element with nonlinear elastic
material.
28128
70.5
t Description in QRG
Documentation - CMASS1, CMASS2 - Incorrec
The description of the CMASSi bulk data entries in the Version 69 and 70 Quick
Reference Guide indicates that multiple degrees of freedom, "up to six unique
integers", may be specified for the component degree of freedom. This is
incorrect, only a single degree of freedom may be specified.
28158
70
MSC_BASE is not Properly Defined.
Submittal - Remote Execution will fail if
The remote execution capability of the nastran command will fail if the
MSC_BASE on the remote machine is not properly defined. The command will fail
even if the nastran command on the remote machine was able to determine the
proper MSC_BASE value.
Avoidance: Make sure the MSC_BASE value is properly defined in the
<install_dir>/bin/nast70 script.
28169
70
ay Cause Wrong Answers
Miscellaneous - Cray T90 Hardware Error M
Cray Research has reported a T90 hardware error that has the potential to
return random results for certain vector operations. The specific MSC/NASTRAN
routines that may be affected by this error have been identified.
It is very important to note that:
1) In our testing, and in specific testing of MSC/NASTRAN by Cray Research, the
effects of this error have NOT been seen.
2) This error is ONLY present on T90 systems.
3) No client has ever reported a problem related to this error.
The specific MSC/NASTRAN executables that are affected by this error are:
MSC/NASTRAN Version
--------------------V68.0
Executables
--------------------------------------unicos/analysis.C90
V68.1
unicos/analysi
28184
t Description
70.5
Documentation - PARAM,COUPMASS - Incorrec
The definition of PARAM,COUPMASS in the Version 69 and 70 MSC/NASTRAN Quick

Reference Guide is incorrect. It says:
COUPMASS
Default=-1
COUPMASS>=0 requests the generation of coupled rather than
lumped mass matrices for elements with coupled mass capability, ...
It should say:
COUPMASS
Default=-1
COUPMASS>0 requests the generation of coupled rather than
lumped mass matrices for elements with coupled mass capability, ...
Note that the action of the code has never changed. To obtain coupled mass a
setting of 1 or greater has always been required.
28186
70.5
t to non-local filesystem.
Submittal - Job will fail if <sdir> is se
Jobs on an SGI R8K, R10K system will fail if the <sdirectory> keyword or TMPDIR
environment variable is set to a non-local, i.e., NFS-mounted, filesystem.
1) Do not set <sdirectory> or $TMPDIR to an NFS-mounted filesystem.
2) In <install-dir>/bin/nast*.lcl, change the line
"TMPDIR=%sdir%; export TMPDIR"
to
"TMPDIR=%TMPDIR%; export TMPDIR"
28194
70
P - Missing Output
Documentation - QRG, CQUADR, CTRIAR, PCOM
The Quick Reference Guide indicates that a PCOMP entry may be referenced by the
CQUADR and CTRIAR element. It should be noted that composites are not
supported for these elements and it is not possible to obtain lamina stresses
and strains.
28199
s
External Superelement - SEBULK, EXTRN - Possible Wrong Answer
When using the enhanced external superelement capability in Version 69.1, if

more than one external superelement is dblocated in a single assembly run using
the matrixdb option, then the answers may be wrong. Also see error 27917.
Avoidance: Attach one external superelement at a time in the assembly run.
Attach additional external superelements by making successive restarts--one
additional restart for each additional external superelement.
28205
69
X dbiolib.a for Catia
Post Processing - Special Version of HP-U
Catia Versions 4.1.6 and 4.1.7 require a shared dbiolib.a to link with
MSC/NASTRAN Version 68.0 and Version 68.1 on HP 9000 systems. The standard
dbiolib.a delivered with V68.0/V68.1 was not built this way (all subsequent
releases were). This standard library is available from the anonymous ftp site
under the URL
ftp://ftp.macsch.com/pub/msc-products/NASTRAN/V68/v68-hp9000-dbiolib.a+z
This file is NOT required for MSC/NASTRAN V69 and later versions.
28210
70.5
ommands No Longer Exist
Documentation - RFALTER and RFINCLUDE - C
Starting with Version 69, the RFALTER executive control statement and the
RFINCLUDE FMS statement no longer work. This is due to the removal of RFALTERs
from the program. The Quick Reference Guide incorrectly still lists these as
valid commands.
Avoidance: Use the INCLUDE command.
28218
70
ND SCR=NO - UFM 9050
External Superelement - SOL 101, NO SPC A
If the reduced external se is unconstrained and scr=no is used, then the job
will fail with UFM 9050 (run failed due to
excessive pivot ratio). The subsequent residual restart run will fail with the
following messages:
SYSTEM FATAL MESSAGE 6551 (INPTX2)
AN END-OF-FILE WAS DETECTED ON UNIT
30 DURING BINARY INPUTT2 PROCESSING
1. A KEY VALUE WAS BEING READ
2. THE LAST KEY VALUE READ:
0
FATAL ERROR.
0
NO. FORTRAN RECORDS READ =
0
NO. FORTRAN WORDS READ =
0
0FATAL ERROR
28219
70.5
Documentation - QUADR, PCOMP - UWM 4385
The Quick Reference Guide indicates that the QUADR element may reference a
PSHELL or PCOMP property entry. Although referencing a PCOMP entry may not
cause a fatal error, technically the QUADR element does not support composites
and referencing a PCOMP will lead to the following message:
USER WARNING MESSAGE 4385, STRESS PROCESSING FOR NON-COMP ELEMENTS IN SUBCASE
XX
NOT COMPLETE BECAUSE OF INSUFFICIENT DATA IN DATA BLOCK OES1A
28226
GL
Elements - QUAD4 - Incorrect Corner Stres
ses and Forces with Variable Thickness
The corner stresses and forces are incorrect for the QUAD4 element if variable
thickness is specified.
Avoidance: Do not request corner stresses, request stresses at the centroid
(the default).
28227
70.0.1
Optimization/Design Sensitivity - DSAE -
UFM 3003, Wrong Answers

Beginning in Version 69 a shape optimization deck with superelements whose
grids are designed may either fail with the message "USER FATAL MESSAGE 3003
MODULE = DSAE, READ PAST DATABLOCK TABEVS" or result in wrong answers.
Avoidance: Either do no use superelements or use Version 68.
28234
70.5
lements - Inefficient CPU
Acoustic Analysis - SOL 111 with CAABSF e
Use of frequency dependent material property elements such as the CAABSF

element may make frequency response analyses take an order of magnitude more
cpu time.
Avoidance: Insert the following DMAP alter, in Version 69 or V69.1 solutions
108 or 111, to improve performance.
compile sedfreq
alter 'call freqrs'(,-1)
call dbstore vgfs,,,,//0/0/'
'/0 $
compile semfreq
alter 'call freqrs'(,-1)
call dbstore vgfs,,,,//0/0/'
'/0 $
compile freqrs
alter 'do while'(,-1)
call dbfetch /vgfs,,,,/0/0/0/0/0 $
trnsp
vgfs/vgfst $
matmod vgfst,,,,,/vgsf,/12//1 $
alter 'ckddf1',''
call fd3mpy kggf1,vphfs,vgsf,vgfs,rgdfd/ckddf1 $
alter 'cbddf1',''
call fd3mpy bggf,vphfs,vgsf,vgfs,rgdfd/cbddf1 $
alter 'k4ddf',''
call fd3mpy k4ggf,vphfs,vgsf,vgfs,rgdfd/k4ddf $
compile fd3mpy
s
28275
70
Documentation - Superelements - UFM 6794
The example jet101a.dat in the MSC/NASTRAN Version 69 Release Notes section

describing superelement enhancements contains an error that will lead to:
UFM 6794 (SEPSEB)
The error is caused by duplicate boundary points connecting to superelement 4
at grid 26.
The input requires the following changes to work:
$GRID,4001,,-1.975,-3.4125,0.
$GRID,4002,,-1.925,-3.9875,0.
GRID,4003,,-1.925,-3.9875,1.
$SELOC,5,1,3,6,4001,4002,4003
SELOC,5,1,3,6,4101,4102,4003
28281
70.5
,PRTMAXIM - Missing Output
Documentation - QRG, PARAM,PRTRESLT PARAM
The MSC/NASTRAN Quick Reference Guide indicates that PARAM,PRTRESLT and
PARAM,PRTMAXIM are supported for solution 106. They are not supported and
their specification will yield no output. These parameters on supported in
solution 106 starting in Version 70.5.
28304
Documentation/Online Encyclopedia - Missing Footnotes
The element summary table (Table 1. Element Summary - Small Strain Elements) in
the Encyclopedia Reference Manual chapter 5.1 pg 158-164 is missing important
footnotes. The symbols appear in the table but the corresponding footnotes are
missing. The critical footnote that is missing is that that midside nodes are
not allowed for elements in geometric nonlinear analysis.
Avoidance: See the printed version of the Reference manual for the proper
footnotes.
28338
UFM 2042
70.5
Optimization/Design Sensitivity - CBUSH -
When a design optimization analysis has a DRESP1 entry with RTYPE=WEIGHT and
CBUSH elements, it may result in the following error message:
*** USER FATAL MESSAGE 2042 MODULE = WEIGHT
MISSING MATERIAL TABLE ******** FOR ELEMENT
xxx.
Avoidance: Specify VOLUME instead of WEIGHT as the RTYPE.

28348
70.5
POST - Missing Output
Postprocessing/Buckling Analysis - PARAM,
In buckling analysis, solution 5, the static results are not written to the xdb
file. The buckling results
are written properly.
Avoidance: Insert the follwing DMAP alter:
compile sol5
alter 'EQUIVX CASECC\/CASEXX',''
if ( post=0 ) soltype='statics' $
CASE
CASECC,/CASEXx/'TRAN'/1 $
alter 'DBC OSTR1'
soltype='bkl0' $
28373
ng FLEXlm
70.5
Installation - mscsetup hangs when starti
As documented in the INSTALL.html and INSTALL.txt files, and in the mscsetup

output, installing FLEXlm requires root privileges. Specifically, root is
required to modify the /etc/inittab file.
If non-root attempts to install FLEXlm AND modify /etc/inittab AND start lmgrd
before the next system boot, mscsetup may appear to hang after it writes the
following message to the screen:
Starting /etc/inittab command now...
The system is actually waiting for the password of the account that owns the
lmgrd process.
Avoidances: There are two avoidances-
1) Install FLEXlm as root.

2) Enter the password for the user that owns the lmgrd process if mscsetup
appears to hang as described above.
28383
70.5
n HP-UX Doesn't Support Large Files
Limitation on Problem Size - Version 70 o
MSC/NASTRAN V70 on HP-UX does not support large files. Both the PA-RISC 1.1
and PA-RISC 2.0 executables should have supported large files, i.e., files
larger that 2GB. This support is missing.
Avoidance:
Use FMS commands to partition the database into multiple files, each of which
is smaller than 2GB.
28395
FM 3002
69
Nonlinear Normal Modes - PARAM,NMLOOP - S
When performing a nonlinear normal modes analysis (param,nmloop,x), if the load

increment is anything other than one, then
the job will fail on the NT system in Version 68.2.5 with the following error
messages:
*** SYSTEM FATAL
MESSAGE 3002 MODULE = CASE
EOF ENCOUNTERED WHILE READING DATA BLOCK CASEI (FILE 201) IN SUBROUTINE CASE
FATAL ERROR
Avoidance: If the number of load increments is more than one, break the
subcase into multiple subcases--one load increment for each subcase.
28421
70.0.1
, CORD1C, CORD2C - Wrong Answers
Nonlinear Analysis - CBUSH, COR1S, CORD2S
If the CBUSH entry references a non-cartesian coordinate system, wrong answers

result.
Avoidance: Use a cartesian system.
28483
70.5
P-Elements - GMSURF, GMCURV - UFM 4659
If an element edge being mapped to a GMSURF or GMCURV has tangents which are
anti-parallel at the endpoints, the mapping is incorrect, possibly causing the
following fatal message in EMG.
DURING INTEGRATION FOR ELEMENT WITH ID =
An example of an element that will cause this error is an element edge spanning
a semicircle.
Avoidance: Move one of the endpoints or split the element into multiple
elements, such that the tangents are not anti-parallel.
28508
ERG)
70
SSSALTERs - alter1ga.v691 - UFM 5423 (DUM
Use of alter1ga.v691 from the sssalter library may result in USER FATAL MESSAGE
5423 point to the trailers for matrices GOAQ and AIDENT matrices.
Avoidance: If this error occurs, call your local MSC office for an updated
version of the alter. If you wish to make the correction yourself, change the
line:
UMERGE USET,QIDENT,/AIDENT/'A'/'Q'/'T' $
to:
umerge1 uset,qident,,,/aident/'A'/'Q'/'T' $
28509
27, EC 7777
70
Parallel Processing - SYSTEM(107) - SFM 4
It has been reported on a Cray Version 69 system that when more than one
processors is requested, then the job may fail with the following error
messages:
0*** SYSTEM FATAL ERROR 4276.RECOVR
ERROR CODE
7777 PID=
Avoidance: We have been unable to duplicate this error at MSC. To avoid the
error simply do not select parallel processing.
28525
70
tall, V70 No such file
Documentation - V70 COG: HP Remote CD Ins
The "MSC/NASTRAN V70 Configuration and Operations Guide UNIX Edition", Section
2.2.2, for remote CD installation of V70 on HP systems specifies
file_set = "/CDROM/MSCSETUP.TAR;1"
It should specify
file_set = "'/CDROM/MSCSETUP.TAR;1'"
28533
Acoustic Analysis - VELO(PHASE) - Wrong Answers
If the user requests VELO(PHASE) output and the resultant velocity is near
zero, then NASTRAN will not convert the result to the phase format and will
print the real/imaginary result in an F rather than an E format. An example of
the case control request and the incorrect output is:
VELO(PHASE,SORT2) = 100
X-VELOCITY
0.0
-0.0159
Avoidance: Correct E format results may be obtained by selecting
VELO(REAL,SORT2), the phase option is not applicable.
X-VELOCITY
0.0
1.591795E-02
28554
Matrix Methods - Iterative Solver, ITER - SFM 6723
The iterative solver may issue the message "SYSTEM FATAL MESSAGE 6723" NON
POSITIVE DIAGONAL ELEMENT IN SCALAR ROW INCREASE IPART VALUE ON BULK DATA
CARD".
Avoidance: IPAD may be increased by 1, the current value is given in SYSTEM
INFORMATION MESSAGE 4157 in the f04. However, SFM 6723 is often an indication
of an ill-conditioned model. Thus, the model should be reviewed by plotting
and/or by using the checka alter in the sssalter library.
28557
1305, EC 32
70.0.1
Frequency Response - MPYAD - SFM 4276, EC
In Version 70, if a large number of frequencies is requested in a frequency

response run, then the job may fail with one of
the following error messages:
BIOMSG: ERROR 1305 HAS OCCURRED IN ROUTINE ENDPUT , FILE INDEX (FILEX) =
0
STATUS =
0
0*** SYSTEM FATAL ERROR 4276.ENDPUT ERROR CODE
1305 PID= 0
BIOMSG: ERROR
32 HAS OCCURRED IN ROUTINE GETSTR , FILE INDEX (FILEX) =
0
0*** SYSTEM FATAL ERROR 4276.GETSTR ERROR CODE
32 PID= 0
Avoidance: Reduce the number of frequencies. In modal frequency response, the
new freq3, freq4 and freq5 entries may be used to guarantee that a solution is
requested at each of the modes without specify a large number of frequencies.
28558
70.5
uccessfully map soname 'c_code.so'
Installation - rld: Fatal Error: cannot s
The "Minimum" installation of MSC/NASTRAN Version 70 on the SGI R8000/R10000

will fail to load a file required by the MSC/NASTRAN solver executable, as a
result, MSC/NASTRAN will fail with the following error message:
$ msc70 nastran myjob
MSC/NASTRAN V70.0 (Silicon Graphics IRIX64 6.1) Tue Jul 29 08:52:34 1997
MSC/NASTRAN beginning job myjob
21692:/scratch1/dnl/msc/msc70/irix64/analysis: rld: Fatal Error: cannot
successfully map soname 'c_code.so' under any of the filenames
/scratch1/dnl/msc/msc70/irix64/c_code.so:/usr/lib64/c_code.so:/lib64/c_code.so:/
usr/lib/64bit/c_code.so:/lib/64bit/c_code.so:
$
This file is loaded with the "standard", "full", and "custom" installations.
Avoidances: There are two avoidances:
1) Use the "standard" or "full" installation.
2) If a mini
28565
70.0.1
- FLFACT - UFM 7087
Design Optimization/Aeroelastic Analysis
The message "USER FATAL MESSAGE 7087" is issued when a velocity requested in a
flutter design task does not correspond to one used in the analysis. This
could be a user input error, but it has been found that it can also be
encountered when the user uses the thru option on the flfact entry. An
equality check is being used to make the comparison and the numerical values
that appear to be the same can differ slightly when they are generated from the
thru data.
Avoidance: Do not use the thru option on the flfact entry to specify analysis
and/or design flutter velocities in design optimization (SOL 200).
28566
70.0.1
DSDJ2S - SFM 3007
Optimization/Design Sensitivity - DSDJ2D,
The message "SYSTEM FATAL MESSAGE 3007" can appear when performing adjoint
sensitivity analysis if the adjoint solution vector is null. The adjoint
solution vector will only be null if the resultant sensitivity is null. Thus,
the message indicates a poorly posed design task in that a critical response is
unaffected by the design variables. An example is asking that an acceleration
response be greater than zero at zero hertz. Since this response can only be
zero, the error is triggered.
Avoidance: Remove the responses that trigger the message since they cannot
affect the design.
28573
t - SFM 3007
70.7
Normal Modes - REIGL module with auto-omi
When computing normal modes using Lanczos in the REIGL module, if the number of
generalized coordinates assigned is larger than the actual number of component
modes available or auto-omit is performed, then the job will fail with the
following messages:
*** SYSTEM FATAL MESSAGE 3007 (REIGL )
ILLEGAL INPUT TO SUBROUTINE MERGE
Avoidance: Remove the extra generalized coordinates or insert the following
DMAP alter avoidance:
compile moders
alter 'EQUIVX MKAA\/KXX\/NOARED'(,-1)
noared=-1 $
28581
70.5
ses on SGI R8K, R10K Systems
Security - FLEXlm - Unable to serve licen
If the FLEXlm license server is installed on an SGI R8K, R10K system and
mscsetup installs the license file, the DAEMON line will incorrectly reference
the irix64 architecture (which isn't used on FLEXlm). As a result, the license
server will not function.
Avoidances: Either of the following two avoidances can be used:
1) Modify the <install_dir>/flexlm/licenses/license.dat file and change the
"irix64"
reference on the "DAEMON" line to "irix"
2) Create a link in the <install-dir>/flexlm directory from irix64 to irix with
the command
ln -s irix irix64
28582
69
ist Upon Return from SUPER3
DMAP - SUPER3 - OPG1, OQG1, etc do not Ex
In SOL 101, the tables containing containing the results in "OFP" format are
not returned from subDMAP SUPER3. This means if a client DMAP alter tries to
use these tables (OPG1, OQG1, etc) in SESTATIC, they will not exist.
There is no effect on the solution or output.
Avoidance:
Insert the following DMAP alter in runs using DMAP in SOL 101:
COMPILE SEDRCVR, SOUIN=MSCSOU, NOLIST, NOREF
ALTER 2,2
28604
2gB on HP
70.5
Miscellaneous - PUNCH files Cannot Exceed
Punch files can not exceed the 2 giga-byte limit on HP and possibly other
machines. The 2 giga-byte limit still applies to all FORTRAN I/O files.
Avoidance: The only avoidance is to break-up the output requests so that the
punch files remain under the 2 giga-byte limit.
28605
Matrix Method - HP-Examplar PA-RISC 1.1 - SFE 4276, SFM 1013
If a large job is run on a HP-Exemplar PA-RISC 1.1 system in Version 70, then
the job may fail in DCMP with one of the following error messages:
*** SYSTEM FATAL MESSAGE 1013 (GBKMGR)
CANNOT FIND CORRECT CLUSTER POINTER RECORD
BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGR , FILE INDEX (FILEX) =
0
*** SYSTEM FATAL ERROR 4276.GBKMGR
ERROR CODE
4276 PID=

=
BIOMSG: ERROR 7777 HAS OCCURRED IN ROUTINE RECOVR , FILE INDEX (FILEX)
0
STATUS =
0
Avoidance: Use the iterative solver instead of the sparse solver. The
iterative solver can be activated by adding
the following nastran statement to the top of the input file.
nastran iter=yes
28615
70
Error in Transformation Matrix
SSSALTER - alter1ga.v691 - Wrong Answers,
An error in the transformation matrix used in alter1ga.v691 may result in wrong

answers for displacements during data recovery or in applied loads.
Avoidance: Modify the following line in the alter:
UMERGE USET,GOAQ,/GOGT/'G'/'O'/'A' $
to:
UMERGE USET,GOAT,/GOGT/'G'/'O'/'A' $
or request an updated copy of the alter from MSC.
28650
Answers
70.7
Aeroelastic Analysis - USPARSE=0 - Wrong
If unsymmetric sparse is turned off using NASTRAN system cell 209 (USPARSE=0)
and a complex left-handed fbs is required,
wrong answers are produced and there is no warning message. This error affects
all SOL 145 and 146 runs that use
doublet lattice aerodynamics. Also any solution 200 run that uses doublet
lattice aero in a flutter analysis.
Avoidance: Do not select USPARSE=0.
28655
70.5
W Poor Performance
Nonlinear Slide-Line Analysis - BGP - MN4
The performance suffers on the NT running slide-line contact problem using SOL
106 as memory is increased.
Avoidance: Limiting the memory to 4 million words will improve performance.
28662
70.5
ND1, IFP - UFM 315
Frequency Response/Random Analysis - TABR
If the TABRND1 entry uses the log-log option with very small data the following
fatal message may result:
FORMAT ERROR ON BULK DATA ENTRY TABRND1
Avoidance: This message has been encountered for data on the order of e-12.
The only avoidance is to either use the linear option or to use different units
to scale the data up.
28669
sing Output
2001
Eigenvalue Analysis - PLOAD1, FORCE - Mis
If element force output is requested in SOL 103 and one or more PLOAD1 entries
exist in the bulk data, there will be no element force output provided.
Avoidance: Remove the PLOAD1 entries from the input.
28673
70.6
76, EC 1401 Using GIVENS
Eigenvalue Analysis - READ, EIGR - SFM 42
If GIVENS or MODIFIED GIVENS method is used for an eigenvalue solution and

spill is required, it is possible that the run may terminate with:
SYSTEM FATAL ERROR 4276.GETS68
ERROR CODE
1401
Avoidance: Either provide additional memory so that spill is not required or

use the Lanczos method.
28675
EFORM
70.5
Documentation - Plotting, QRG - MAXIMUM D
The documentation for the MAXIMUM DEFORM plot entry is deficient. Remark 2 is
not true, and should be replaced with the remark below. Remarks 3, and 4
should be added:
2. If you wish the FIND command to utilize the d value, a MAXIMUM DEFORMATION
command should precede the FIND command.
3. If you wish the plot deformation scaling to be different then the FIND
scaling a different MAXIMUM DEFORMATION command can appear first before the
PLOT command.
4. For nonlinear plotting MAXIMUM DEFORMATION d and the MAXIMUM DEFORMATION
field on the PLOT command should have the same value.
28679
70.5
Dynamic Analysis - Multiple FREQ, TSTEP,
DLOAD Subcases - Inefficient Processing
In SOLs 111 and 112, if multiple FREQ or TSTEP and/or DLOAD subcases are
specified and default data recovery (PARAM, DDRMM, 0) is performed then SDR1
and SDR2 are re-executed every subcase even though their outputs do not change.
Avoidance: If no superelements are present, then use SOLs 11 or 12.
28680
70.5
MPYAD - SFM 3007, UFM 5423
Acoustic Analysis - PARAM,RESVEC, MERGE,
When a fluid/structure model with rigid body modes (requiring a SUPORT card) is
run with PARAM,RESVEC,YES the following FATAL errors are issued:
0FATAL ERROR
or
*** USER FATAL MESSAGE 5423---ATTEMPT TO MULTIPLY OR ADD INCOMPATIBLE
MATRICES, (SMPYAD)
Avoidance: Apply the following DMAP avoidance:
compile modefsrs
alter 'call resvec'(,-1)
call dbstore vafs,,,,//0/0/'
'/0 $
compile resvec
alter 'px1',''
call dbfetch /vafs,,,,/0/0/0/0/0 $
partn
pab,,vafs/px1,,,/1 $
alter 'px3,,,'(,-2)
merge
pxf,,,,,vafs/pxfs/1 $
equivx pxfs/pxf/-1 $
alter 'phux1'(3,-1)
partn
ux2,,vafs/ux2s,,,/1 $
equivx ux2s/ux2/-1 $
endalter
28684
70.5
in SOLs 11 - Missing output
Dynamic Analysis - STRAIN and SPCF output
In SOLs 11 with default dynamic data recovery (PARAM, DDRMM,0) and multiple
FREQ subcases,
element strain and SPCforce (if PARAM,DYNSPCF=NEW) output will be missing in
the 2nd and subsequent subcases.
compile sol11
alter 1
file mus=append/kus=append/bus=append/istr1=append $
file mum=append/kum=append/bum=append/istr2=append $
28685
70.5
bcases - SFM 3002
In SOLs 108,
subcases, if
the run will
module. For
Superelements - CASE, Multiple Dynamic Su
109, 111 and 112 with multiple FREQ and TSTEP (or DLOAD)
a superelement has fewer subcases than the residual structure then
fail with the message SYSTEM FATAL MESSAGE 3002 in the CASE
example,
disp=all
subcase 10
super=10
subcase 100
freq=1
subcase 200
freq=2
Avoidance: Specify SUPER=ALL or the same number of subcases for the
superelements and the residual structure or insert the
following DMAP alter:
compile super3
alter 'casedrm',''
paraml casedr//'trailer'/1/s,n,norec $
if ( dloop>norec ) then $
CASE
CASEDR,/CASEDRM/'tran'/norec $
else $
CASE
CASEDR,/CASEDRM/APP/DLOOP $
endif $
28686
70.5
Acoustic Analysis - Modal Participation
Factors - Missing Output, Wrong Answers
In solution 111, modal frequency response, modal particicipation factor output
is wrong or missing when PARAM,ACSYM,YES, which is the default.
Avoidance: Insert PARAM,ACSYM,NO or the following DMAP alter:
compile mpf
alter ',ah,'
type parm,,char8,y,acsym='yes' $
if ( acsym='yes' ) then
delete /ah,,,, $
PARTN
bHH,VPHFS,/,mAH,, $
add5
mah,,,,/ah/-1. $
endif $
alter 'z2x'
if ( acsym='yes' ) then $
add5
z2x,,,,/z2xx/-1. $
equivx
endif $
z2xx/z2x/-1 $
28687
70.5
L, EIGR, SUPORT - SFM 3007, UFM 4405
Eigenvalue Analysis - ASETi, SPOINT, EIGR
In an eigenvalue solution, if null dofs (e.g., SPOINTS) are placed in the aset,
and a SUPORT entry exists, then depending on the eigenvalue solver requested,
the job will fail with one of the following error messages:
FATAL ERROR
or
USER
FATAL
MESSAGE 4405,0
Avoidance:
1. Do not place the unreferenced SPOINTs in the ASET.
2. Remove the SUPORT entries if feasible. This avoidance only works for the
Lanczos method.
28688
6, EC 7777
70.5
Acoustic Analysis - EMG, CAABSF - SFM 427
When a solution at zero frequency is requested and frequency dependent acoustic

absorber elements, CAABSF, are specified, then EMG fails with a divide by zero.
At zero frequency, the frequency dependent acoustic absorber element should
put out zero impedance.
Avoidance: Do not request a solution at zero frequency.
28697
SFM 3007
2001.0.1
Acoustic Analysis - ACSRC, FORCE, DPD6 -
If an ACSRCE Bulk Data entry has the same DAREA ID (field 3) for loads applied
to structural grid points and the loading applies to more than one degree of
freedom at a given structural grid point then the run will fail in the DPD
module with SFM 3007. The run should fail with UFM 6825 (see CSR 4618).
Avoidance: See CSR 4618.
28710
rong Answers
70.5
Heat Transfer - MAT4, CONVM - UFM 6715, W
If UFM 6715 shown below is issued in SOL 153 (or 106) then the run will not
terminate but will continue and produce wrong answers.
*** USER FATAL MESSAGE 6715 (ECNVMD)
THERE IS NO DYNAMIC VISCOSITY SPECIFIED ON THE MAT4 ENTRY FOR CONVM
ELEMENT
11.
USER INFORMATION: FORCED CONVECTION ELEMENTS REQUIRE SPECIFICATION OF
DYNAMIC VISCOSITY
ON A MAT4 ENTRY IF ON THE PCONVM ENTRY THE REYNOLDS
NUMBER CONVECTION EXPONENT
IS GREATER THAN THE PRANDTL NUMBER CONVECTION EXPONENT.

compile nlstatic
alter 'call super1'
putsys(0,82) $
28712
70.5
ufficient Disk Space
Eigenvalue Analysis - REIGL, DECOMP - Ins
MSC/NASTRAN Version 70 introduces a new re-ordering method in sparse

decomposition for CRAY and SGI computers. While this method has been found to
have performance advantages in nearly all cases, there may be cases where the
improved performance is at the expense of requiring more memory. If the memory
is not available, which is more likely the case on very large jobs, additional
spill may be required and the job may fail due to insufficient space.
Avoidance: In the single problem case encountered to date the problem was
resolved by increasing NQS memory. An error was found in the error handling
when NQS memory was insufficient. Although we don't think it should be
necessary for the user to ever have to deselect the new ordering method,
SYSTEM(206) controls the re-ordering method a
28713
70
Security - NT Only - UFM 3060
A problem with MSC/NASTRAN Version 69 NT system causes authorization codes that

would normally produce expiration warning messages to issue USER FATAL MESSAGE
3060.
Authorization expiration warning messages should be produced under the
circumstances listed below. The only avoidance is to request a new auth code
for a longer duration.
1. If the duration of an auth code is four months or longer, an expiration
warning message is displayed when the code is within 3 months of expiring.
2. If the duration of an auth code is three months, an expiration warning
message is displayed when the code is within 2 months of expiring.
3. If the duration of an auth code is two months, an expiration warning
message is displayed when the code is within 1 month of expiring.
If t
28716
70.5
uids with Enforced Motion
SSSALTERS - rflagb - Wrong Answers for Fl
Wrong answers have been observed when the rflagb.v70 alter is used on
fluid-structure problems, and enforced pressures are input via the Lagrange
Multiplier Technique. The problem has been observed only on short word
machines, and does not occur on long word computers such as Cray. The alter
package has been modified to test for wrong answers, and to switch to the
avoidance procedure automatically when wrong answers are found. An
investigation is underway to determine if this type of wrong answer could be
achieved in any other manner, in particular when no dmap alters are present.
The only cases found to date were for the circumstances given above.
Avoidance: An avoidance is to cause the unsymmetric matrix solver to run

instead of the symmetric solver. There is some economic penal
28730
70.5
ble Longer Runtime
Miscellaneous - GPFORCE, BUFFSIZE - Possi
A significant efficiency improvement has been added to the GPFDR module in

Version 70 which can cause GPFORCE output to run much faster than previous
versions. This improvement is most significant for large models with multiple
subcases and open sets (using the thru option). A 20 to 1 cpu improvement has
been observed on a client model. However, for smaller models, the GPFDR time
may take longer than the previous versions, especially when using a large
buffsize is specified.
Avoidance: Use a smaller buffsize and the run time should then be comparable
to previous versions. As the model gets larger, the runtime will become faster
as compared to previous versions.
28757
70.5
L, K2PP, M2PP, B2PP - Wrong answers
Frequency Response - SOLs 108 and 111, TP
If the Case Control commands TF, K2PP, M2PP, or B2PP, change between subcases
in SOLs 108 and 111, then the frequency response solution is repeated but the
answers will not be correct.
28762
70.0.5
ible Wrong Answers
Buckling - CBAR, MATi, ALPHA, TREF - Poss
In a buckling analysis, if the thermal coefficient of expansion on the MAT1

entry is non-zero, and no thermal loads are applied, then the differential
stiffness for the BAR element will be incorrect.
Avoidance: If there are no thermal loads then remove the thermal coefficient
of expansion since this quantity is not needed for a mechanical load.
28765
Documentation - Aeroelastic User's Guide
Equation 8-43 in Section 8.10 of the Aeroelastic User's Guide indicates that
the Imaginary part of Q31 is used to calculate the yawing moment coefficient
due to sideslip rate. This is a typographical error. It should be using the
Real part of Q31. See the Version 65 Aeroelastic Handbook equation 18 on page
6.2-190.
28778
70.7
SSSALTERs - rflagba - Segmentation Fault
A frequency response run on an SGI R8000 using the sssalter rflagba.v691 may
fail in FRRD1 with "signal 11 : segmentation fault" in the log file.
Avoidance: The problem is under investigation at this time. Try to use the
large mass approach in place of the alter.
28782
70
User Modifiable NASTRAN - XGPIDG - SFM 52
When adding new user modules to the MSC/N user modifiable in version 69.1, the
job may fail with the following error messages:
** SYSTEM FATAL MESSAGE
52 (XGPIDG )
NAMED COMMON /XLINK/ IS TOO SMALL

This error is most likely to occur when adding more than one new module.
Avoidance: Contact your local support for the corrected source to semdbdf.f.
28798
2001
Nonlinear Analysis - SPCD - Wrong Answers
Applying an enforced displacement with SPC or SPCD while using the CONV field
set to UPW causes wrong answers.
28813
UFM 6011
DMAP - PARAM - CHAR8 Variables on PARAM Entries Must Be BCD,
The Quick Reference Guide states that character parameters are allowed as
inputs on the PARAM entry. However, the
full range of character values are not allowed. The Old Exec construct of
"BCD" parameters is enforced by the preface. This construct states that only
alphanmumeric values are used, that is, the first character must be a letter of
the alphabet. An input of param, char, -1, where char is typed as a char8
variable in dmap, results in the fatal diagnostic:
USER FATAL MESSAGE 6011 (IPVDFT)
THE MAIN SUBDMAP VPS TYPE OF PARAMETER CHAR DIFFERS FROM THE TYPE DETERMINED
FROM PARAM CARD DEFINITION.
USER INFORMATION: VPS TYPE IS CHARACTER. PARAM TYPE IS INTEGER.
28817
70.5
Default Value for BAILOUT in QRG
Documentation - PARAM,BAILOUT - Incorrect
The V70 Quick Reference Guide states the default for BAILOUT is -1. In Version
70 of MSC/NASTRAN, the default is 0.
28829
2001
), Poor Message
Superelements - SEP2D, SUPER - UFM (SEP2D
When the SUPER=i,j feature is used to input different load ids in subcases for
different superelements, messages of the form

*** USER FATAL ERROR ---- (SEP2D)
CASE CONTROL RECORDS FOR SUPERELEMENT
2 CONTAIN A MIXTURE OF ZERO
AND NON-ZERO LOAD SEQUENCE NUMBERS.
may occur. The error message does not cause the program to exit, however. In
all cases studied to date it continues to completion, and produces correct
answers.
Avoidance: The error message may be ignored. Using a fully expanded case
control instead of using SUPER=ALL above the subcase level and SUPER=i,j within
the subcase will also avoid the problem.
28840
k, UFM 476
File Management Section - ASSIGN - DELETE Option does not wor
If an ASSIGN statement is used to define the database and the ASSIGN statement
specifies the DELETE option, a pre-existing database may not be deleted and the
run may fail with the message:
USER FATAL MESSAGE 476 (GPFILX)
THE LOGICAL NAME DBALL_1 ASSIGNED TO A PHYSICAL FILE NAME OF THE PRIMARY
DATA BASE, DOES NOT EXIST.
USER INFORMATION: PHYSICAL FILE NAME =
Avoidance: Delete unwanted databases before executing the run
THis quality is a dupplication of 31608.
28846
70.5
Complex FBS with 2 by 2 Pivots
Matrix Methods - FBS - Wrong Answers for
FBS of complex symmetric, non-positive semi-definite matrices may produce wrong

answers. Standard structural elements do not produce non-positive
semi-definite matrices so this error is unlikely to occur in most runs but it
is possible in poorly conditioned models and users dmaps that solve Ax=b, where
A is complex symmetric and not positive semi-definite. The error has been
observed on runs using the rflagb.v70 alter, which uses Lagrange Multiplier
Method techniques which cause indefinite systems of equations.
Avoidance: Use the unsymmetric solution method. In the current version of the
rflagb.v70 alter, the model is run first with the symmetric solver, usually the
least expensive option. A check of the solution is made immediately after the
frrd1 module, and if the accuracy is po
28848
70.5
6143, Segmentation Fault
Inertia Relief - PARAM,INREL, MERGE - UFM
On Digital UNIX Version 69.1 only, if inertia relief is requested in some

subcases, but not all, then the run will fail with a "segmentation fault" in
the MATGEN module. On all other machines in Version 69.1 and 70, if inertia
relief is requested in some subcases, but not all, in the presence of enforced
displacements then the run may fail with UFM 6143 in the MERGE module.
compile selr
alter 'IF ( INREL0',''
IF ( INREL=-1 and not(delta) ) THEN $
28853
70.5
es could be decompressed
Installation - mscsetup - Not all the fil
On Version 70 HP systems, mscsetup may incorrectly report the total or

available disk space on a file system during the query or installation phases.
If the error occurs during the installation phase, the installation may
terminate with the following error message:
Not all the files could be decompressed.
<req> MB free space are required.
<avail_insdir> MB were available in the installation directory <insdir>.
<avail_tmpdir> MB were available in the work directory <tmpdir>.
Please make more space available and
redo this installation using the command
./mscsetup -t <work_directory> <insdir>/mscsetup.pbk
where <work_directory>
is an alternate directory with at least <req> MB free
space that can be used for scrat
28857
GL
aster - SFM 4276 EC 3001
Optimization/Design Sensitivity - Multi M
The multi-master technique, allows the user to develop a design task in pieces.
That is, an automotive design task might have a chassis in one model, the body
in another and doors and windows in other models. As part of the adjoint
sensitivity development, an efficiency was introduced, which skips the
generation of pseudo-loads if there are no active responses for a particular
subcase. Unfortunately, this breaks the random order capability of the
multi-master technique which would allow the user to have pseudo-load
information available on a standby basis in case a later job submittal requires
it. If a later run needs the pseudo-load information from a previous run,
which did not calculate it, then the message "SYSTEM FATAL ERROR 4276.GREAD
ERROR CODE 3001 PID= 0" is issued.
Avoidanc
28891
Incorrect
70.5
Documentation - MATHP - Equations in QRG
Remark 1 under the Version 70 Quick Reference Guide description of the MATHP
entry shows the equation 2D1=K2D1=K, it should read 2D1=K.
28892
Wrong Answers
70.5
Optimization/Design Sensitivity - AERO -
If, in design optimization, a static aeroelastic subcase is present and their

are no static aeroelastic specific responses (TRIM or STABDER on a DRESP1), the
mass effects in the sensitivity analysis are ignored and wrong answers can
result.
Avoidance: Include a token static aeroelastic response. It could be
constrained with very generous limits so that it
is never needed for the design task, but at the same time the DSCREEN
parameters should be set to force retention of the
unimportant constraint.
28893
70.5
sing Documentation
Documentation - MODTRL - Various UFM, Mis
In Version 70, the capability to modify the type and/or precision of a matrix
with the MODTRL module was removed. DMAPs that use MODTRL in this way will
fail with a message of the form:
USER FATAL MESSAGE
(MODTRL)
AN ATTEMPT TO MODIFY MATRIX 101 TYPE OF TERMS HAS BEEN MADE.
USER INFORMATION: USE MATMOD OPTION 34 TO CREATE TWO OUTPUT REAL MATRICES
FROM A COMPLEX INPUT MATRIX.
USE ADD OR ADD5 TO CREATE A COMPLEX OUTPUT MATRIX FROM
ONE OR TWO REAL INPUT MATRICES.
Unfortunately there is no documentation in the Version 70 Release Guide and the
diagnostic messages from the MODTRL module
above may be misleading.
Avoidance:
1. In order to change the precision of a matrix, use ADD5. If the new
precision does not match the mach
28894
70.5
ARAM,RESVEC) - Wrong Answers
Eigenvalue Analysis - Residual Vectors (P
If there is a c-set and/or r-set and component modes are augmented with
residual vectors (PARAM,RESVEC,YES or PARAM,INRLM,-1) then the answers will be
wrong.
compile semr3
alter 'call resvec',''
call resvec pg,uset,gm,kfs,ys,bgpdts,scstm,cstms,medge,mff,
cmpho0,loo,koo,cmlama0,moo,got,koo,cmphrc/
cmpho,cmlama/
nozset/norc/seid/'o
' $
compile resvec
alter 'if ( nobset',''
if ( nobset>-1 ) upartn uset,got/,,gorc,/'t'/'b'/'c'/2 $
28917
70.5
Nonlinear Analysis - MATHP - Poor Answers
Using MATHP with Isotropic Materials
Hyperelastic elements have been designed to allow incompressible solutions.
The elements yield poor results when used with isotropic material properties.
1. In the Version 70 QRG entry for MATHP, Remark 1. Wrong: "2D1 = K2D1 = K"
Correct: "2*D1 = K"
2. The "MEAN PRESSURE" is wrong for the hyperelastic element.
28919
PCKI EC 62
70
Matrix Methods - DCMP, Spill- SFM 4276.SF
The message, "SYSTEM FATAL ERROR 4276.SFPCKI ERROR CODE 62 PID= 0", is supposed
to be issued when the matrix to be decomposed exceeds the maximum allowable
size. However, prior to MSC/NASTRAN Version 70, it may be issued erroneously,
when the DCMP module starts to spill. This is because the spill logic may
overwrite the variable that contains the matrix size.
Avoidance: If possible, increase memory to avoid spill. Otherwise, change the
available memory, so the spill logic will work differently, and perhaps not
overwrite the variable with a number larger than allowed.
28936
swers
70.5
Elements - CQUAD4, OLDQ4K - Unexpected An
The NASTRAN system cell OLDQ4K is ignored in Version 69.1 and 70 systems.
Avoidance: The avoidance is to set SYSTEM(173)=1.
28939
ULE = SDRCOMP
70.5
Composites - PCOMP, PSHELL - SFM 3002 MOD
If a model requests STRESS output for some plate elements referencing PCOMPs
and other plate elements referencing an equivalent PSHELL/MAT2 combination
generated in a prior MSC/NASTRAN run, then no composite ply stress output or
homogeneous stress output occurs and the following error message is issued:
0*** SYSTEM WARNING MESSAGE 3002 MODULE = SDRCOMP
0EOF ENCOUNTERED WHILE READING DATA BLOCK EPTS
(FILE 103) IN SUBROUTINE
SDRCMA
Avoidance: MID1s, MID2s, MID3s, MID4s that are created on the equivalent
PSHELL/MAT2s are equal to 100000000 plus the PCOMP PID. This is a flag to
NASTRAN that they are from PCOMPs. If the MIDis in the punched output are
change to smaller numbers, then composite ply stresses for the PCOMP elements
and homogeneous stresses for the PSHELL element
28959
70.5
Superelements - EXTRN - UFM 6894
The Quick Reference Guide documentation for the EXTRN bulk data entry states
that a thru option is available for listing connected points. When this option
is used for scalar points the following fatal error messages are output:
FOR EXTERNAL SUPERELEMENT ID=
ILLEGAL COMPONENT DESIGNATED ON THE
EXTRN BULK DATA ENTRY.
3, SCALAR POINT ID=
712 HAS AN
Avoidance: Remove the thru range and list each point explicitly.
28965
- Wrong Answers
Nonlinear Analysis/Hyperelastic Elements - Lumped Mass, MATHP
The 20-noded hyperelastic hexa element produces wrong answers when used with
lumped mass. The mean pressure output is wrong for all hyperelastic elements.
Avoidance: Use consistent mass, ignore the mean pressure output.
28972
70.5
LFACT, DSAD - SFM 3007
Optimization/Design Sensitivity - AERO, F
If the velocity specification for a flutter design response is a positive

number on the associated FLFACT entry while the
FLFACT velocity specification for the analysis is negative (to indicate that
eigenvectors are required at that velocity), the above fatal message will
occur.
Avoidance: The simple avoidance is to not specify negative velocities on either
the analysis or the design FLFACT entries.
A slightly more complex avoidance is to not design at velocities at which
flutter eigenvectors are desired.
28987
70.5
Submittal - V68.X and earlier used nice(1
) with bat=yes, V69 and later doesn't.
The nastran command, introduced with Version 69, removed the nice(1) command
from the "batch=yes" submittal. This can be returned by setting the "-bg"
queue command to "nice %job%" in any RC file. For example, the line
submit=-bg=nice %job%
can be placed in any RC file.
29002
70.5
Frequency Response, Flutter, Complex Eige
n - DLOAD, CMETH - UWM 6498, Signal 11
In Version 70, if the DLOAD Case Control command references a non-existing

DLOAD or RLOADi entry, or a CMETHOD Case COntrol command references a
non-existing EIGC entry, othen depending on the machine, the job may fail with
one of the following unclear messages:
*** USER WARNING MESSAGE 6498 (MsgGetStr)
Message number is not found
Check call to MSGPOP from FRLG with the message number 3031
Severity is USER WARNING
Parameter 1 is
2
Parameter 2 is DLT
Parameter 3 is FRRD
USER ACTION: Please contact MSC Client support
Signal 11 (in the log file)
Avoidance: Correct the offending DLOAD/RLOADi entries or CMETHOD/EIGC entries.
29005
ite Ignored
70.5
Miscellaneous - nastxxrc, symbol - Overwr
Once a symbol is defined in an rc file, it cannot be overwritten by a later RC

file that you would expect to take precedence. This error prevents a site from
providing a default value in a system RC file and the user from overriding that
value in their local RC file. Similarly, a user cannot provide a default in
the HOME RC file and then override it in the local RC file.
1. Use a different symbol
or
2. Override the RC file value with an environment variable as follows
(assuming the symbol name is MYDIR):
export MYDIR=/my/big/project
MYDIR=/my/big/project; export MYDIR
setenv MYDIR /my/big/project
29011
70.5
S=MODES - Missing Output
# Korn shell
# Bourne shell
# C-shell
A solution 200 shape optimization analysis that contains multiple subcases and
ANALYSIS=MODES will not output the eigenvectors for the final design cycle.
compile presens
alter 'deseig=false',''
29013
70.5
Optimization Input
Documentation - DRESP2 - Questions about
Remark 2 under the DRESP2 entry should be changed to read:

DRESP1 entries can not span analysis types or superelements.
29016
70.5
Documentation - QRG, EXTRN - Blank Field
Feature not Documented.

The EXTRN bulk data entry, first documented in the Version 70 Quick Reference
Guide, allows pairs of blank fields. The pair is read as if it weren't there.
This makes it easier to repair or modify EXTRN entries.
For example, suppose that an EXTRN entry were of the form:
$EXTRN GID
$
GID
EXTRN, 12
CID
GID
CID
(ETC)
123456 14
CID
GID
CID
123456 22
123456 24
and the model is changed so that GID 13 should be

the sequence of points on the list is of critical
to move the input entry for every point after GID
requirements. This change can be accomplished as
$EXTRN GID
CID
GID
29043
70
ay cause Auth Code Error, UFM 3060
CID
GID
CID
123456, $ etc.
added to this list. Since

importance, it is necessary
13 to meet the sequencing
shown:
GID
Installation - Folded license.dat Files m
Various mail tools may fold text that exceeds a pre-determined line length.
Generally, the tool will break the line between words, i.e., at whitespace. In
normal text this is, at worst, annoying. In a license.dat file, this can
result in the failure of lmgrd.
Avoidance: Use the mscsetup script in TAN #2778 to install a license.dat file.
If the file has already been installed, but has been folded, copy the file to
another location and reinstall it using the revised mscsetup.
29044
2001
Initial Stiffnes on PELAS
Documentation - PELAS, PELAST - Requires
When a CELAS1 element is used with a PELAST property entry to represent a

nonlinear spring in nonlinear analysis, an initial, non-zero stiffness must be
specified on the PELAS entry. Other capabilities in MSC/NASTRAN require the
flexibility to allow the stiffness field on the PELAS entry to be blank so the
code will not be changed to trap this condition. A remark will be added to the
PELAST documentation stating the requirement.
29047
70.5
SWM 6911 (QCBFIN)
Optimization/Design Sensitivity - AERO -
The warning message:

*** SYSTEM WARNING MESSAGE 6911 (QCBFIN) MORE THAN ONE KHH
appears when a solution 200 run is restarted from a solution 145 run. The
message is, most likely, benign, but does have the potential for producing
wrong answers.
compile respsen
alter 'khhx','qhhx'
type parm,,i,n,ncycl
dbview khhx=khh
dbview mhhx=mhh
dbview bhhx=bhh
$
where (wildcard and desiter=ncycl) $
dbview qhhx=qhhl
alter 'dscmg'(2)
ncycl = desiter $
29050
70
SSSALTERs - resflexa, RESTART - SFM 3003
It is possible that the resflexa.vxxx alter will not automatically remove

static vectors which are a linear combination of the elastic modes. If this
error occurs, the program may encounter SYSTEM FATAL MESSAGE 3003, indicating
an attempt to read past the end of a record.
Avoidance: The alter has been updated to correct the error. Either request an
updated version of the alter or include the following in the alter:
mpyad phiajc,pfac,/stamod/0 $
<== existing line
add stamod,uarsflx/resvec//-1. $ <== existing line
$ filter null columns if they exist - Sept, 1997
matmod resvec,,,,,/nullcol,/12/s,n,nonull/1 $
if(nonull>0)then $
message //'at least one residual vector can be represented' $
message //'by the elastic modes. the following matrix has 1.0' $
me
29052
70.5
envalues, Wrong Answers, UFM 9050
P-Elements - ADAPT, PSHELL - Negative Eig
In eigenvalue analysis, negative eigenvalues may occur in shell p-elements if

bubble functions are present and the distribution of p-values is non uniform.
In static analysis wrong answers or USER FATAL MESSAGE 9050 may occurBubble
functions may be present whenever the p-level is less than 3.
Avoidance: To avoid this error, bubble functions must be turned off by setting
system cell 225 to 1.
29053
n SGI
70.5
Rigid Elements - RSSCON - Wrong Answers o
The RSSCON (rigid shell to solid connector element) has been found to produce
wrong answers for one problem on SGI computers.
Avoidance: The problem is not yet fully understood. In the case where the
answers were wrong the oload and spc resultants did not agree. Thus, the user
is advised to closely check these results. If they do not agree, then if
possible run the job on another computer or use another method such as rbe2s to
connect the shell elements to the solids.
29064
70.5
es for Prestressed Eigenvectors
Nonlinear - Modes, Preload - Wrong Stress
If a Sol 106 run calculates a preloaded condition and then solves for the
modes, the stress output for the modal portion of the analysis will be wrong
whenever the stiffness matrix has been updated because the stresses are
calculated using the initial geometry. The nonlinear stresses are still
correct.
Avoidance: A DMAP avoidance for Version 70 is:
$
$
s29064.v70
11-13-97
$
$ ALTER FOR SOL 106 (VER 70) FOR NMLOOP DATA RECOVERY
$
AVOIDS LARGE SOURIOUS STRESSES (CSR 29064)
ECHOOFF
COMPILE NLSTATIC $
ALTER 'APPEND *UGNI' $
IF
( NLOOP = NMLOOP ) CALL DBSTORE UGNI,,,,//0/0/'
$
COMPILE SEDRCVR $
ALTER 'OPG1,OQG1,OUGV1','' $
TYPE
PARM,
,I,Y,NMLOOP=0 $
TYPE
PARM,NDDL,I,Y,LGDISP $
IF ( APP1 = 'REIG' AND NMLOOP > 0 AND LGDISP > 0 ) THEN $
29068
70
Insufficient Memory in FRRD2
'/0 $
Matrix Methods - UDSFA, FRRD2 - UFM 6136,
It has been observed that for some frequency response problems that an
incorrect estimate is made for the amount of core required for the incore
decomposition. This error results in the message:
*** USER FATAL MESSAGE 6136 (UDSFA) insufficient memory in FRRD2
regardless of how much memory the job is given.
Avoidance: The avoidance is to set system(166)=1 so that if this error is
encountered the job will revert to standard decomp and avoid this error.
29082
70.5
ng mscsetup to Crash
Installation - mscsetup - noclobber Causi
If the noclobber flag is set, mscsetup will fail when it starts.

Avoidance:
Insert the line
set +C
as the first executable line of mscsetup and rerun.
29087
70.5
recision in Dynamic Aeroelasticity
Aeroelastic Analysis - MKAERO - Lack of p
The aerodynamic matrices required in SOL 146 are interpolated from aerodynamics
calculated at reduced frequencies input on the MKAEROi bulk data entries. The
calculations are performed in single precision and it has been observed that
this can produce bad answers when a poor choice of MKAERO data is entered. The
problem has not shown up on long word machines.
Avoidance: Restrict the number of k's input on the MKAERO to no more than
eight. Avoid k's that are close to one
another (certainly no closer than 0.005). Check answers on a long word machine
if possible.
29096
70.5
Include Inertial Forces
Superelements - MPCFORCE - Answers do not
If MPCFORCEs are requested for MPCs or R-type elements (RBAR, RBE2, etc) in a
transient response or frequency response solution, the resulting output will

not include the inertial forces due to attached masses.
Avoidance: Insert the following alter into the input file:
compile cforce, souin=mscsou, list, noref
alter 'IF ( APP=',''
IF ( APP='reig' or seid>0)then $
$
29105
70.5
Optimization/Design Sensitivity - AERO Wrong Answers for rtype=trim or stabder
If a static aeroelastic subcase retains a STABDER or TRIM response types, but
no element or grid type responses, the required sensitivity analyses will not
be performed and wrong answers will be produced for the sensitivities.
Avoidance: Include element and/or grid response in the subcase and force its
retention through appropriate DSCREEN values.
29126
still running
Installation - Uninstall Problems on Windows NT, MSCEXE file
If MSC/NASTRAN or MSC/PATRAN on Windows NT are unistalled and the system may

not reboot and may issue the message "MSCEXE file still running".
Avoidance: When performing an uninstall of MSC/NASTRAN or MSC/PATRAN, the user
must kill the FLEXlm service daemon. This may be done through the following
steps; type ctrl+alt+del, select task manager; find the mscexe process, and
then kill it. The system may then be rebooted.
29139
cumentation
70.5
Documentation - QRG, CONVM - Incorrect Do
The description of the CONVM bulk data entry in Quick Reference Guide
incorrectly states that the EID may be that of a CHBDYE or CHBDYP element.
This entry may only reference the CHBDYP entry and only when the FTUBE option
is specified.
29140
70.5
Optimization/Design Sensitivity - SIGSEGV
Segmentation Violation - Problem Size
The message "SIGSEGV - Segmentation violation" can appear in the log file of
short word machines for large optimization design tasks. The cause is an
integer overflow calculation. A general limit on problem size is that the
2*ndv + ncon SQRT< 2**31-1 = 46,341 (where ndv is the number of design
variables and ncon is the number of constraints,
including property limits but not side constraints.
Avoidance: Reduce the problem size to fit within the above limit or run on a
long word machine where the comparable limit is 3 billion and therefore not
meaningful.
29144
70.5
COMP, CTRIA3 - UFM 5626 (DSAD13)
Optimization/Design Sensitivity - DSAD, P
The above message can occur in error when a DRESP1 entry asks for a CFAILURE
response and the deck contains only CTRIA3's or CQUAD8's and no CQUAD4's.
Avoidance: Add a dummy, disjoint QUAD4 that references the same PCOMP entry
and constrain its response.
29150
70.5
), EIGRL - UFM 4418
Cyclic Symmetry, Buckling - SOL 16 (or 77
If a buckling analysis is performed using a cyclic symmetry solution sequence

(SOL 16), and the Lanczos eigenvalue solver is requested, then the job will
fail with the following error messages:
0*** USER
0
FATAL
MESSAGE 4418,
NO EIGENVALUE EXTRACTION DATA IS AVAILABLE.

compile sol16
alter 'matmod',''
MATMOD CASEds,DYNAMICS,,,,/,/23/S,N,NP/S,N,LANCZOS $
endalter
29165
rs
70.5.1
P-Elements - Shell Elements - Wrong Answe
The bending energy is calculated incorrectly for the error estimator for
p-shell elements. Thus, p-shell element models subjected to bending may
produce poor or wrong answers.
Avoidance: There is no avoidance using p-elements.
29178
70.5
ored, Reduction Not Performed
Superelements - ASETi - ASETi Entries Ign
The aseti entries are ignored if they are placed in the main bulk data section
using the enhanced superelement capabilities (begin super=seid).
1. Perform a component mode reduction instead of a Guyan reduction on the
residual structure.
or
2. Place only aset grids in the residual structure and put the rest of the
grid points in a separate superelement.
29199
4276, EC 7777
70.5
Cyclic Symmetry - LOADCYT, CYCLIC1 - SFE
Cyclic symmetry problems on the Cray T90/IEEE Version 70 release of MSC/NASTRAN

that contain LOADCYT entries may fail with the following traceback in the
CYCLIC1 Module.
Beginning of Traceback:
Called from line 42 (address 15262370c) in routine 'TRBK'.
Called from line 39 (address 202316c) in routine 'RECOVR'.
Called from line 112 (address 1101772a) in routine 'sysrcv'.
Called from address 14765131c in routine '__handlr'.
Called from address 1717073a in routine 'CY1CYT'.
Called from line 119 (address 1714533c) in routine 'CY1CYD'.
Called
Called
Called
Called
29200
from
from
from
from
line
line
line
line
36 (address 1711300c) in routine 'CY1CCL'.

267 (address 1747550d) in routine 'CYCL1'.
116 (address 10753001b) in routine 'XSEM12'.
342 (address 2117a) in routine
Superelements - PARAM,POST,-1 (-2) - Erroneous Output
In a superelement analysis, if param,post,-1 or param,post,-2 is used, and is

placed inside a subcase, then some of the output for
the output2 file will be sent to the log file. A symptom of this error is the
erroneous output printed in the log file similar to the following:
Process Id = 20562
X 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ$/+-()'=.*"#%&,;:<>?@![]^_\
61^GGPL F^4^66^810/81BK33333^71^60^3^61^GGPL
F^72^60^3^81BK^813.813*813"813#813
020080

1. Place the param,post,-1 or param,post,-2 in the bulk data section or above
the first subcase.
or
2. Add the following dmap alter and place "param,ounit1,12" inside the same
subcase as "param,post,-x".
compile out2geom $
alter 'type.*parm.*ounit1','' $
type parm
29202
70.5
- Wrong Answers for Multiple B.C.s
Optimization/Design Sensitivity - ADJOINT
The release guide for V70 states that the adjoint sensitivity method is not
available when there are multiple static boundary conditions. In fact, the
adjoint method may still be selected by the code but will yield wrong answers.
Avoidance: The following alter avoids the problem:
compile descon
alter 'IF ( DOSTATX'(,-1)
mbcflg=false $
alter 'bcdr '(,-1)
mbcflg=true $
29203
70.5
, FBS - SFM 2198
Optimization/Design Sensitivity - SUPORT1
The message "SYSTEM FATAL MESSAGE 2198, INPUT DATA BLOCK 101 HAS BEEN PURGED"
may be produced when a design sensitivity task contains static and normal modes
subcases and the normal modes subcase contains a SUPORT1 entry that the static
subcase does not.
Avoidance: Use the following DMAP alter
compile desopt
alter 'fbs '(,-1)
CALL SETQ CASESx//
SEID/PEID/S,MTEMP/S,K2GG/S,M2GG/S,B2GG/S,MPC/
S,SPC/S,LOAD/S,DEFORM/S,TEMPLD/S,P2G/S,DYRD/S,METH/
S,MFLUID $
PARAML CASESx//'DTI'/1/255//S,N,SUPORT $
29210
70.5
NDDL Description for AERO Datablock
Aeroelastic Analysis - AEROS - Incorrect
The first record of the AERO datablock was changed for Version 70, but the NDDL
description was not updated. Three additional words were added to the datablock
to support running static aero and flutter in the same run while using
different reference chord lengths. The words are the reference chord length
from the third field of the AEROS entry, plus the aerodynamic and reference
coordinate system ID's from field 7 and 8.
Avoidance: The correct NDDL description for Version 70 is:
Desc={Aerodynamic Matrix Generation Data }
Desc={Contains information for control of }
Desc={aerodynamic matrix generation and flutter
Desc={analysis }
Desc={ }
RECORD=HEADER,
NAME(2),CHAR4,{Data block name
}
EOR,
RECORD,
ND,I,{Y sym flag SYMXZ
$
$
$
$
29213
n QRG
70.5
Documentation - STRAIN - Clarify Remark i
Remark 1 of the Quick Reference Guide description of the STRAIN case control
command claims that 'Strains for nonlinear elements are requested by the STRESS
command and appear in the nonlinear stress output'. This remark should state
that 'Nonlinear strains for nonlinear elements are requested by the STRESS
command and appear in the nonlinear stress output'.
29310
70.5
DVPREL2 - UFM 316
The message "USER FATAL MESSAGE 316 ILLEGAL DATA ON BULK DATA ENTRY DVPREL2"
will be produced in error if the input deck contains DRESP2 entries and the
highest numbered DRESP2 entry references DVPREL1 data.
Avoidance: Remove the DVPREL1 references from the highest numbered DRESP2
entry. In almost all cases, this is a simple replacement to a DESVAR reference.
29311
Iterative Solver - SITDR2, SOLVIT, ITER - UFM 6724 (SB1RM)
The iterative solver may fail with the message:

USER INFORMATION MESSAGE 6447 (SITDR2)
ITERATIVE SOLVER DIAGNOSTIC OUTPUT
EPS : 1.00000E-06
BICWELL PRECONDITIONING
USER FATAL MESSAGE 6724 (SB1RM)
TOO MANY RESTARTS.
USER ACTION: INCREASE IPAD VALUE ON BULK DATA CARD ITER.
0FATAL ERROR
Avoidance: This message may be caused by a negative term on the factor
diagonal.. A potential cause for getting a negative diag. term is that the
matrix is ill-conditioned. The error may be avoided by increasing the IPAD
parameter on the ITER entry. Another possibility is- to use BICILL instead of
BICWELL.
29315
70.5
Missing Documentation & Examples
Accounting - MSCACT, acct, acid, acdata -
To add accounting of the account ID (acid) and site-dependent account data

(acdata) to the acct and MSCACT utilities, the following steps are required:
1) Modify the nastXX.lcl, where XX is "69", "691", "70", to pass the acid and
acdata values to acct. For example, in the nast70.lcl file, change
%acct=y:%
%a.archdir%/acct $acctf $startdate %user% %out%
MSC/%appl% %version%
to
%acct=y:%
%a.archdir%/acct $acctf $startdate %user% %out%
MSC/%appl% %version% "%acid%" "%acdata%"
This change adds the two values, in quotes, to the acct command line.
2) Compile the modified mscact.c source as described in the COG, chapter 6.
# cd <ins-dir>/msc70/util
# msc70 util mscact
This modified program adds "summary=acid" and "summary="acdata".
3) I
29316
70.5
referenced on a DRESP2 - SIGTRAP FP
The message SIGTRAP TRACE TRAP FP OVERFLOW may appear in the log file when a
DVPREL1 entry is referenced by a DRESP2 entry and sensitivity results are
requested.
Avoidance: Replace the DVPREL1 reference with a reference to the associated
DESVAR's or remove the request for sensitivity output.
29324
70
signal number 10 : Bus error
SSSALTERs - rflagba.v691, TRD1 -Receiving
When running a large problem in Version 69.1 on the SGI, if insufficient memory
is available, then the job may fail in the TRD1 module with no error messages
in the f06 file. A symptom of this error is the presence of the following
error message in the log file:
Receiving signal number 10 : Bus error
This error has been observed in a large transient dynamic run when using the
rflagba.v691 sssalter.
Avoidance: Increase the memory.
29329
2004
Virtual Mass - MPRES - Missing Element La
bles from Output, Missing Output

Element labels for complex "PRESSURES FOR ELEMENTS ON FLUID STRUCTURE BOUNDARY"
may be missing if SORT2 output is requested.
Avoidance: Request SORT1 output.
29338
ssing Output
Postprocessing/Nonlinear Analysis - PCOMP, PARAM,POST,-2 - Mi
In solution 106 with lgdisp,1 and composite elements, ply stresses are printed
in the f06 file but not in the param,post,-2 output2 file. Also homogeneous
stresses are put in the output2 file although they are not requested.
Avoidance: Use the following alters:
V68:
$
$ the following alter is used to work-around a problem when
$ using PCOMP in SOL106 with INTOUT=YES on NLPARM (V68.2.3)
$ originally the NLSTATIC DMAP writes OESCP multiple times
$ with PARAM,POST,-1 which causes problems for PATRAN...
$ the fix is to APPEND OESCP within the loop and write it
$ afterwards.
$ modified 10-9 to add I-DEAS output (POST=-2)
$
$ output2 blocks: OESCP laminar stresses
$
OESTRCP laminar strains
$
COMPILE NLSTATIC SOUIN=MSCSOU NOLIST NOREF $ v68.2
$
AL
29339
Elements - Fluid Points, CELASi, CDAMPi, CMASSi - UFM 2012
If a scalar element is attatched to a fluid point, the following error message

may occur:
** USER FATAL MESSAGE 2012 (GP1GSM)
IDENTIFICATION
1 SAME BETWEEN GRID, SCALAR OR POINT IN
SUPERELEMENT
-1
Avoidance: Use DMIG entries for these coefficients or attach the scalar
elements to the 1 dof instead of the 0 dof of the fluid point.
29340
swers
70.5
Heat Transfer Analysis - MATT4 - Wrong An
Transient Heat transfer - CBAR element - Version 69 and version 70 only

If MATT4 references TABLEM1 or TABLEM2 entries that define constant values,
then wrong answers result.
Avoidance: Do not use the MATT4 if the material properties are constant. Use
the MAT4 to specify these properties.
Or if you are using the CBAR element,changed to crod element
29341
70.5
76 FILPS2 EC 1044
Static Analysis - GPFORCE, GPFDR - SFE 42
If grid point force output is requested for only some of the subcases, and the
set does not contain all the grid points, then the job may fail with one of the
following error messages below. Similarly in superelements, if there is a
gpforce request above the subcase level that references a set and the set does
not contain a grid point in each of the superelements then the job will fail.
SYSTEM FATAL ERROR 4276.FILPS2
ERROR CODE
1044 PID=
0 GPFDR
*** USER WARNING MESSAGE 2354 (GPFDR)

MODULE IS UNABLE TO CONTINUE AND HAS BEEN TERMINATED DUE TO ERROR MESSAGE
PRINTED ABOVE OR BELOW THIS MESSAGE.
THIS ERROR OCCURRED IN CODE WHERE THE VARIABLE -NERROR- WAS SET =
43
*** SYSTEM WARNING MESSAGE 3002 (GPFDR )
EOF ENCOUNTERED WHILE READING DATA BLOCK SCRATCH (FI
29342
GL
T - CMR DOF AUTOSPC'd in SE0
Superelements - External SE with CMR, CSE
If a component mode DOF from an external SE is not being attached into the
residual structure as anticipated it is an indication that the mode is either a
linear combination of the static transformation vectors or the first mode
calculated. MSC/NASTRAN will eliminate this mode via the autospc and INREL DMAP
mechanism by design. Two avoidances exist.
1) remove the cset entries from the external SE run.
or
2) ask for more modes to be calculated and add a second spoint putting it into
the qset.
29344
70.5
al Orientation, Wrong Answers
Elements - CTRIAR, MCID - Error in Materi
Specifying a MCID (integer, material coordinate system) in field 7 of the

CTRIAR entry does not work. The resulting THETA (real, orientation angle)
will be a large number ( 512.*(MCID+1) ), yielding incorrect stiffness for
anisotropic materials. It may also lead to wrong element mass matrix.
Avoidance: Do not use an integer in field seven of the CTRIAR entry, use the
CTRIA3 element instead. DIAG 38 may be used to print the material angles.
29348
70.5
,FLUIDMP - Missing Output
Acoustic Analysis - PARAM,STRUCTMP, PARAM
Requests for structural modal participations and fluid modal participation

factors do not work.
Avoidances: Structural modal participations can be obtained for Version 69 and
later systems with the following dmap alter:
compile mpf
alter ',ah,'
type parm,,char8,y,acsym='yes' $
if ( acsym='yes' ) then
delete /ah,,,, $
PARTN
bHH,VPHFS,/,mAH,, $
add5
mah,,,,/ah/-1. $
endif $
alter 'z2x'
if ( acsym='yes' ) then $
add5
z2x,,,,/z2xx/-1. $
equivx
z2xx/z2x/-1 $
endif $
and fluid modal participation factors can be obtained with the following alter:
alter 'ENDIF \$ FLUIDMP\<NOFHSET'(,-1)
else $
equivx PHDFH1/PHDFH2/-1 $
29356
70.5
mem - SFM 3007
Optimization/Design Sensitivity - DESVAR,
If an optimization job does not have enough memory allocated to it, it may fail
with the message " *** SYSTEM FATAL MESSAGE 3007 (DOM9 ) ILLEGAL INPUT TO
SUBROUTINE DOM9P4".
Avoidance: Allocate more memory (using mem keyword on NASTRAN command line).
If more memory is not available, and the model contains only DVPREL1 entries
with one associated DESVAR, then you can reduce the memory requirement by
setting DELP > DELX on the DOPTPRM entry.
29367
70.7
FM 4551, UFM 5423, Missing Output
Nonlinear Transient Analysis - SADD5 - U
When a nonlinear transient model has difficulty converging, NASTRAN issues some
variation of the message "USER FATAL MESSAGE 4551". The job stops at that
point and results which have been obtained up to that point are printed out.
However, if the variation "USER FATAL MESSAGE 4551, STOPPED PROBLEM DUE TO TWO
DIVERGENCES IN THE SAME TIME STEP." is issued, then no results are printed, and
it is followed by the fatal message:
0*** USER FATAL MESSAGE 5423---ATTEMPT TO ADD INCOMPATIBLE MATRICES, (SADD5)
COLS ROWS FORM TYPE
NZWD DENS
2
TRAILER FOR PST1
IS
27
22
TRAILER FOR IFS
IS
28
22
875
19 9740
Avoidance: Correct t
29398
Force Output
70.7
Nonlinear Analysis - CGAP - Incorrect SPC
When the CGAP element orientation is defined by the orientation vector in

fields 6 through 8, the moment due to frictional shear force is not calculated
correctly. The resulting moment ignores the length of the element and is
incorrectly calculated as the (shear force)/2. As a consequence, the moment
component in SPC forces is incorrect.
Avoidance: Use CID on CGAP to define the orientation of the Gap element.
29411
70.5
S=BUCK - Missing Eigenvalue Table
If buckling analysis is used in an optimization run, then only the initial

eigenvalue table will be printed.
Avoidance: Insert the following dmap alter:
compile moders $
alter 1 $
type parm,,logical,n,eigprt $
alter 'if.*nasout.*ofp.*lama'(,-1) $
eigprt=nasout $
nasout=true
alter 'if.*nasout.*ofp.*lama' $
nasout = eigprt $
endalter $
$
29412
70.01
r on Windows NT
Security - FLEXlM - Missing License Serve
The initial delivery of the MSC/NASTRAN Version 70 CD-ROM does not contain the
FLEXlm network licensing servers for Windows NT.
If you want to use your Intel Windows NT system as the license server and do
not already have this software, then you can get the network software from MSC
by calling our toll-free Order Processing hotline at: 1-800-400-4672. A
revised Version 70 CD is available, the Version 70.5 CD will also have the
Intel Windows NT license server.
For Digital Alpha Windows NT systems, we do not have the network license server
available.
We will update the Version 70 Windows NT CD-ROM to contain both licensing
servers in the near future.
29421
s
Miscellaneous - after keyword - Maximum File Size 2 Giga Byte
On an SGI IRIX 6.4, use of the NASTRAN keyword "after" will lower the maximum
filesize from unlimited to 2Gb. This is error is caused by a bug in the SGI
operating system.
Avoidance: There is no avoidance except not to use the "after" keyword.
29425
70.5
4276, EC 7777, Trap Encountered
Elements - CTRIA6, CQUAD8, ELFORCE - SFM
If element force data recovery is requested for the CTRIA6 elements, then the
job may fail on the IBM RS6000, HP, and possibly other machines. Depending on
the machine, the job may fail with the following error message in the f06 file,
0
STATUS =
0
or with the following error messages in the log file without any messages in
the f06 file.
Trap encountered:
SIGTRAP - Trace trap FP overflow
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
0x00000024
0x00005044
0x0000075c
0x00000c54
0x00000260
0x00000194
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
proc
gmmatd_
str61d_
s2bbrd_
sdr2b_
sdr2_
29442
70.5
Process GPFORCE Results
Post Processing - GPFORCE - Can Not Post
An error in the access key for grid point force results in the xdb prevents
these results from being post processed in transient and modes runs.
MSC/PATRAN Version 7.5 supports post processing of these results but
MSC/NASTRAN Version 70.5 will be required to produce the corrected xdb.
29478
69.1
- UFM 6794 (SEPSEB)
Documentation - Release Notes/jet101.dat
The file jet101.dat on the V69 delivery CD, in the msc69/nast/misc/doc/relnotes

directory, contains an error which will result in the following message:
DUPLICATE BOUNDARY POINTS DETECTED CONNECTING TO SUPERELEMENT
26 FROM DOWNSTREAM
0.
LIST FOLLOWS:
4101
4001
4 AT GRID
This error is caused by grid points 4001 and 4002 which are not needed.
Avoidance: Remove the definition for grid 4001 and 4002. The correct file is
on the delivery CD for Version 69.1.
29480
2001
, TABLED1 - BIOMSG ERROR 1044
Nonlinear Transient Analysis - PBUSHT, KN
Nonlinear transient analysis with CBUSH elements that refer to a PBUSHTentry

that defines stress dependent properties may fail in the NLTRD2 module with
SYSTEM FATAL MESSAGE 4276 BIOMSG ERROR 1044.
29489
70.5
- Poor Answers
P-elements - GMSURF with zero derivatives
If a GMSURF has a point with zero derivatives, such as the center of a cylinder
or sphere, linear element edges with grids at the singularity may have skewed
parameterizations. This may result in poor answers.
Avoidance: An avoidance is to specify an FEEDGE for any such element edge. No
GMCURV or POINTs need to be specified for a linear edge.
29508
on Fault
Nonlinear Transient Heat Transfer - THERMAL, DBX - Segmentati
If a nonlinear transient heat transfer analysis, sol 159, specifies multiple

THERMAL case control requests the job may fail with the following message in
the log file.
Process Id = 4393
Receiving signal number 11: Segmentation fault
Job aborting...
dbx: Not found
Unable to call dbx for trace: Error 0
Avoidance: The data deck that encountered this error was attempting to request
printed output for a specific set and punched output for all. The correct way
to make this request is to use the OTIME entry to limit the printed request.
29526
316 (IFPDRV)
70.5
Random Response Analysis - TABRND1 - UFM
The SKIP feature on the TABRND1 entry does not work when LOG-LOG option is
used.
The following messages are issued.
ILLEGAL DATA ON BULK DATA ENTRY TABRND1
ENTRY COUNT =
**
*****
SORTED
Avoidance: Do not use the SKIP feature when LOG-LOG is used.

29531
70.5
SIGSEG, Segmentation violation
Superelements - SEBULK, SECONCT, SEP1X -
When using the enhanced superelement capabilities (begin super=x), only one
grid point may occupy the same location for a particular superelement at a
particular boundary location. This is a documented limitation. Logically a
user may believe that one way to get around this limitation is to use the
SECONCT command; however, the use of the command for this purpose will cause
the job to terminate with no message in the f06 file and the traceback shown
below in the log file. The proper way to get around this limitation is to use
the SEEXCLD command.
Trap encountered:
SIGSEGV - Segmentation violation
Traceback:
Offset
Offset
Offset
Offset
29532
3062
0x00000a90
0x000003f8
0x00000180
0x00000754
in
in
in
in
70.5
procedure
procedure
procedure
procedure
sepmc1_
sepman_
sepsrh_
sep
Superelements - SEEXCLD, SEMA - SFM 4192,
If the enhanced superelement capabilities (begin super=x) are used, and there
is more than one boundary point that occupies the same location, the SEEXCLD
can be used to exclude the extra boundary points. However, if the model also
contains the old superelement type (seset), then the job may fail with the
following misleading error messages:
0*** SYSTEM FATAL message 4192 (sema)
GRID POINT
10 IN SUPERELEMENT
0 IS NOT DEFINED IN BGPDT FOR
DOWNSTREAM SUPERELEMENT
0*** SYSTEM FATAL
MESSAGE 3062 MODULE = SEMA
FAILURE OCCURRED IN UTILITY MAPBTI CALLED IN SUBROUTINE SEMA
.
0FATAL ERROR
Avoidance: Reordering the grid sequencing for the superelements may avoid this
error. Reorder the grids such that the lowest s
29547
70.5
Aeroelastic Analysis - MKAERO - UFM 1126
The message:
*** USER FATAL MESSAGE 1126 (GNFIST)
DMAP MODULE ADD
201 NAME =
AJJ0
USER ACTION: DELETE THE DATABLOCK, OR USE FILE AJJ0
=OVRWRT
is produce when the input deck has m,k (Mach number and reduced frequency)
pairs that are identical.
Avoidance: Remove duplicate mk pairs.
29548
swers
70
SSSALTER - seaspa.v70 - Possible Wrong An
An error in the seaspa.v70 alter (wrong value of app to some apd calls) results
in un-needed data being checked improperly. It is unlikely that the error in
the alter will cause errors in answers; however, the alter has been fixed to
remove this error and it also gives better diagnostics if the auxmodel input
file is given a wrong value. The revised alter may be down loaded from the web
and has a revised date of Oct 23, 1997. The appropriate sample input files have
also been updated and posted on the web at http://www.macsch.com.
29577
70.5.2
Interior Angle of Element is Small
P-Elements - Singularity in Stresses When
P-Elements may encounter a data recovery error when the interior angle of the
element is small.
Avoidance: Other than modifying the mesh, there is no avoidance. In Version
71 an new system cell 269 is introduced to allow the user to specify a
threshold ratio for the Jacobian determinant at a VU-grid with respect to it
p-element center. If the ratio is smaller than the threshold specified, then
the Jacobian determinant at the VU-grid is replaced with its element-center
value when computing the stress and strain.
29580
70
es not include HP Exemplar
Documentation - V69/70 COG - Sec 4.8.3 do
In the COG, Section 4.8.3 describes a method to flush the F04 and F06 files to
disk during a long running job. The method is stated to work on Convex, Cray,
and SGI systems. The method also works on HP Exemplar systems. The
documentation should also explicitly state that after the buffers are flushed
the job is terminated.
Edition 2 of the Version 70 Configuration and Operations Guide has been
clarified.
29581
(SLCDRV)
70.5
DMAP - MATMOD OPTION 13, COPY - SFM 1269
Copying the lower triangular factor from DECOMP or DCMP module may lead to the
fatal message:
*** SYSTEM FATAL MESSAGE 1269 (SLCDRV)
THE ASSOCIATED FILE FNUMERIC OF DATABLOCK
101 IS ALREADY OPEN.

0FATAL ERROR
Avoidance: The error occurs only in Version 70, Version 70.5 corrects the
error and prior versions also work.
29613
70.5
nded Minimum p-order.
Documentation/P-Elements - PVAL - Recomme
In general, an analysis started at P=1 will not produce the same results as
starting at other p-levels. Although it is not suggested in the PVAL
documentation where the p-order is set by either default or recommendation, a
minimum starting p-level of 3 is recommended for accuracy and efficiency.
29615
Example in QRG
70.5
Documentation - DMIG, UACCEL - Incorrect
The format and example for the UACCEL entry in the Quick Reference Guide
implies that enforced accelerations are input as one column. The correct input
format is one column for each enforced acceleration case. A better example
with more typical values follows:
$
dmig,
dmig,
dmig,
dmig,
2
uaccel,
uaccel,
uaccel,
uaccel,
3
0,
2,
3,
4,
4
9,
,
,
,
5
1,
,
,
,
6
,
2,
2,
2,
7
,
3,
4,
6,
8
,
386.4
3.0
1.0
9
4
Remark 2 implies that the SUPER case control command must be present. This is
not true. A better remark would be:
"2. The load sequence number interpretation depends on the value of NCOL field
on dmig, uaccel, 0 entry. The recommended method is to set it equal to the
number of loading conditions, 4 in this example. The load sequence number L is
then the sequence numbe
29619
70.5
for K1, K2, Cw, J
Elements - PBARL, PBEAML - Wrong Answers
The BEAM library capability in MSC/NASTRAN Version 70 calculates the K1, K2

(the shear stiffness factor and CW (the warping coefficient) for the the BOX
section incorrectly.
Avoidance: Calculate the correct cross sectional properties and enter use the
pbar and pbeam entries or create a beam server library with the correct cross
sectional properties.
29622
07
70.5
Cyclic Symmetry - SOL 15, EIGRL - SFM 30
If the EIGRL Bulk Data entry is selected and the CYSUP entry is also specified
in SOL 15 then the run may fail with SFM 3007 in REIGL.
Avoidance: Run SOL 115, use EIGR entry or insert the following DMAP alter:
compile sol15
alter 'reigl
',''
REIGL
Kxx,Mxx,DYNAMICS,CASEcc,,MR,DMx,vxcompr,,,vaxw/
LAMA,phixc,MI,EIGVMAT,OUTVEC/READAPP/S,N,NEIGV/RECNO/
///////////nreigl $
29625
70.5
mentation Violation
Nonlinear Analysis - PARAM,POST - DBC Seg
Nonlinear jobs that fail due to insufficient time or failure to converge that
have param,post,0 may continue and issue a traceback from the DBC module:
Traceback:
Offset
Offset
Offset
Offset
Offset
0x000006c4
0x00000db8
0x00001180
0x000002d4
0x00000984
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
dbcaol_
convrt_
dbc_
xsem14_
mainal
--- End of call chain ---
29639
70.5
ng DMAP Non-upward Compatibilities
Documentation - V70 Release Notes - Missi
The MSC/NASTRAN Version 70 Release Guide did not contain the description of the
DMAP module non-upward compatibilities. Below is the information that should
have been included. The information is also soon to be included on the MSC
external web site. The location will be included in this report when it
becomes available.
This section summarizes DMAP module changes from Version 69 and 69.1 to Version
70. This information is intended to help you convert your Version 69 and 69.1
DMAP alters or sequences to run in Version 70.
A structured solution sequence excerpt shows how the module is
actually invoked in the structured solution sequences and the additions or
deletions are shown in lowercase in the Version 69 or 70 excerpt, respectively.
Th
29643
ntation
70.5
Documentation - COMPILER - Missing Docume
The design intent of the COMPILER LIST statement is to list all subDMAPS called
by a solution sequence. If you wish to list only specific subdmaps you must
input a specific COMPILE LIST statement for each subdmap listing desired.
Remark 4 should be clarified to discuss this design intent.
29645
Wrong Answers
70.5
Static Analysis - GPFORCE, SUBCOM, SET -
If GPFORCE force is requested for a set of grid points and SUBCOM is used, then
the the gpforce output from the SUBCOM subcase will be incorrect.
1. Request GPFORCE=all
or
2. Use SUBCASE instead of SUBCOM
29646
70.5
tial Stiffness - STATSUB - UFM 1126
Optimization/Design Sensitivity, Differen
When performing a buckling analysis in Optimization (SOL 200) with no mass on

any unconstrained degree of freedom in the model and with scr=yes on the
nastran command line, then the message "USER FATAL MESSAGE 1126 (GNFIST) DMAP
MODULE UPARTN IS ATTEMPTING TO OUTPUT DATABLOCK 202 NAME = KSF, WHICH ALREADY
EXISTS. USER ACTION: DELETE THE DATABLOCK, OR USE FILE KSF=OVRWRT", may be
issued.
The error may also occur in SOLs 103 and 107 through 112 if differential
stiffness is requested with the STATSUB command.
Avoidance: There are three avoidances:
1. Insert a dummy mass element on any unconstrained degree of freedom.
2. Insert the following DMAP avoidance in V70.
compile sekr nolist, noref $
$
alter 10 $
$
$ check for KFF
$ if KFF exists, then so does KFS, KSF, KSS
29648
C 7777
70.5
Eigenvalue Analysis - EIGRL - SFM 4276, E
MSC/NASTRAN Version 70 on Dec Alpha OSF may fail in the EIGRL module with the
message SYSTEM FATAL MESSAGE 4276, ERROR CODE 7777. The following traceback
will be issued in the log file:
handler(0x11fffdff8,0x11fffdf98,0x8,0x0,0x11fffdff8) L. 28
<<?? pc=0x12180e0b4>>(0x0,0x0,0x0,0x8,0xc00000007) L. 28
dot3rd_(0x140602658,0x1208397bc,0x1409cbddc,0x12164ccc8,0x1409eb378)
lncrdd_(0x1404c1678,0x165000b38,0x1404c1678,0x1409eb378,0x165001708)
lncr3d_(0x165001c30,0x1407ac4f0,0x165001c50,0x165001c70,0x165000b38)
lncr2d_(0x1650023c8,0x165002550,0x1650026d8,0x1650008f8,0x140645210)
lncr1d_(0x165002550,0x165001cc8,0x1650026d8,0x165000250,0x1650002f8)
lncs1d_(0x1405d2348,0x14064522c,0x140645230,0x140645228,0x1406450c8)
L.
L.
L.
L.
L.
L.
93
266
357
429
457
893
Avoidance: In the si
29655
Answers
70.6
SSSALTERs - propa.v70, propf.for - Wrong
The sssalter propa.v70 and accompanying fortran program propf.for enables the
flutter analysis of propellers. Two errors have been discovered in this
package. The first is that the propeller blade aspect ratio is based on the
propeller diameter when it should be based on the radius. The second is that
the example case based on NASA TN 1807, uses a reference semichord that is
twice that specified in the NASA TN. The updated input file (prop1.dat) and
the input for the pre-processor (prop_data.dat) has been added (8/15/2007).
This will be delivered with the next version of MSC Nastran.
Avoidance: Either input the aspect ratio into the preprocessing routine
directly or modify the supplied FORTRAN code to use radius in the aspect ratio
calculation. For the test case, divide the input chord lengths by two.
29663
3007
70.5
Elements - CRAC3D, TEMP(LOAD), GP3D - SFM
If TEMP is applied to a CRAC3D element that has 32 grids or more the run will
fail with the message:
*** SYSTEM FATAL MESSAGE 3007 (GP3 )
ILLEGAL INPUT TO SUBROUTINE GP3D
Avoidance: If possible use TEMPD to apply the temperature load.
29672
2004
PCOMP, STRAIN - Missing Output
The case control command STRAIN=n is supposed to write ply strains to the .f06
file. This command only works if stress is also requested. Thus, there is no
way to get ply strains only.
Avoidance: To get only strain output, specify the STRESS=m command where SET m
specifies an undefined element or use FORCE=m
Cancelling this one since Xref'd CR 33749 is being worked on
29691
70.5
S=FLUTTER, K2GG, M2GG B2GG - SFM 6296
If flutter optimization is attempted with CASE CONTROL commands K2GG, M2GG or
B2GG then the run will fail and the message SYSTEM FATAL MESSAGE 6296 Unable to
locate a member of datablock QHHL" will be issued.
Avoidance: Don't use the K2GG, M2GG or B2GG commands in an ANALYSIS=FLUTTER
subcase in SOL 200. A complex workaround involving TABEDIT's is available if
this avoidance is unacceptable.
29699
70.5
2 - Misplaced Output
Postprocessing - PARAM,OUNIT1 PARAM,OUNIT
The parameters ounit1 and ounit2 are ignored in Version 70 when used with
param,post,-2.
Avoidance: If the ounit1 and ounit2 are needed, the following DMAP alter may
used:
$
$ for v70.0
$
compile super3 nolist, noref $
alter 335,335 $
type parm,nddl,i,y, ounit1 $
type parm,,i,n, ounit1x $
message //' ounit2 before out2geom call= '/ounit2 $
IF ( POST<0 ) THEN $
IF ( OUNIT1>0 ) THEN $
OUNIT1X=OUNIT1 $
ELSE $
OUNIT1X=OUNIT2 $
ENDIF $
ENDIF $
IF ( ( ((DROPT=0 OR DROPT=4) AND APP1<>'BKL1')
OR APP='BKL0') AND
(OGEOM='YES' OR OGEOM=' ') AND
(POST=-2 OR POST=-4) ) CALL OUT2GEOM,
CSTM,GPL,GPDT,EPT,MPT,GEOM2,GEOM3,GEOM4,
GEOM1,DIT,DYNAMICS,EQEXIN,BG
29704
70.5
essive Run Time
Performance - MPYAD - Large MPYAD has Exc
It has been observed on a very large test problem (1.5M DOF) that the matrix
operation PhiT*M required more than 1000 passes, where M is symmetric and
nearly diagonal, and Phi has the same number of rows of M and 70 columns. This
type of operation is unlikely to occur in a standard solution, but may occur in
a user-dmap. This operation is, for example, used in the checka.v70 sssalter.
The MPYAD method selected was method 1T, which unpacks the (mostly null) rows
of M in memory. This is on a model for which eigenvectors had already been
computed, and the time spent up to the start of the mpyad was less than the
estimate for the multi-pass solution.
Avoidance: Instead of solving for x=PhiT*M in one step, break the operation
into two steps as follows:
xt = M*Phi
x = trns
29705
70.5
- Missing OUTPUT2 Data
Postprocessing - PARAM,POST,-2, SCR=MINI
When an input file is submitted with the scr=mini option and param post,-2 is
used, no op2 output will be generated.
Avoidance: Do not use the scr=mini option. If the scr=mini option and
param,post,-2 are needed, then the following dmap alter may be used.
ALTER 335,335
IF ( (OGEOM='YES' OR OGEOM=' ') AND
(POST=-2 OR POST=-4) ) CALL OUT2GEOM,
CSTM,GPL,GPDT,EPT,MPT,GEOM2,GEOM3,GEOM4,
GEOM1,DIT,DYNAMICS,EQEXIN,BGPDT,CASECC//
OUNIT2/S,NP $
29710
70.7
Unrequested punch file
Miscellaneous - PBARL,PBEAML, ECHO=NONE -
If both the beam library and echo=none are used in the same run, then a punch
file containing the equivalent beam properties will be created.
Avoidance: If this additional punch file is not desired, then remove the
echo=none case control command.
29723
70.7
,FOLLOWK - SFM 3002 (TAFF)
Buckling & Differential Stiffness - PARAM
When performing buckling analysis or stress stiffened analysis (STATSUB) with

follower force effects (PARAM, FOLLOWK, YES), and a LOAD bulk data entry
references more than one PLOAD4 entry, then the following fatal message will
occur:
*** SYSTEM FATAL MESSAGE 3002 (TAFF )
EOF ENCOUNTERED WHILE READING DATA BLOCK (NONE) (FILE
SUBROUTINE TAFMEG
0) IN
Avoidance:
1) Set PARAM, FOLLOWK, NO -- thus follower force effects will be ignored.
2) Do not reference more than one PLOAD4 card on the LOAD bulk data entry.
29724
ujitsu systems
70.5
Miscellaneous - Incorrect OS Version on F
The Operating System version reported by the nastran command and in the
MSC/NASTRAN F06 title block is incorrect. The correct version is obtained with
the 'uname -v' command.
The result "1" indicates "V10L10"; "2" indicates
"V10L20"; and "3" is expected to indicate "V20L10".
The correct version may be specified with the "s.osv" keyword in any RC file,
for example
s.osv=V10L10
29736
70.5
S=MFREQ - SFM 4276 EC 3001 module DSAD
If FREQ3, FREQ4 or FREQ5 Bulk Data entries are specified in SOL 200 run with
ANALYSIS=MFREQ and a METHOD entry, the following message is erroneously
received:
USER WARNING MESSAGE 6645 (FRSRTD)
FREQ3,FREQ4, AND FREQ5 ENTRIES ARE PRESENT IN A DIRECT FREQUENCY RESPONSE
ANALYSIS.
and the following message is issued in the DSAD module:
BIOMSG: ERROR 3001 HAS OCCURRED IN ROUTINE GREAD
0
STATUS =
0
0*** SYSTEM FATAL ERROR 4276.GREAD
3001 PID=
ERROR CODE

compile presens
alter 'dopr3 '
type parm,nddl,logi,n,zuzrl1 $
if ( not zuzrl1 ) then $

delete /CONTAB,R1TAB,RESP12,RSP1CT, $
delete /frqrsp,CASEDS,ointds,pelsetds, $
endif $ no
29759
70.5
H=SINV - Inefficient Processing
Eigenvalue Analysis - EIGR entry with MET
Auto-omit processing is done unnecessarily with METHOD=SINV on the EIGR entry.

Auto-omit requires a decomposition to condense out the massless dofs which
produces a denser stiffness matrix.
compile moders
alter 'noared'(2)
noared=-1 $
29772
70.5
Documentation - QRG, DRESP1 - Wrong units
The units for eigenvalues is incorrect as described in remark 18 of the Quick

Reference Guide's description of the DRESP1 entry. The correct units are
(radian/time)**2 instead of (radian/time).
29778
70.5
Plotting - PLTSET - Poor Performance
The PLTSET module for Version 70 has a severe performance degradation as

compared to Version 68.1. For one probelm, the two PLTSET calls in Version
68.1 used less than 11 CPU seconds while Vhile 70 consumes 470 CPU seconds.
This problem has been corrected in Version 70.5
29779
P-Elements - h-p Interface, FEEDGE - Incorrect Results
When a model consists of both h- and p-elements, the edges of the p-elements
which are on the h-p boundary will not remain at p-level 1 if these edges are
defined with curved geometry. These edges will adapt to higher p-level, giving
incorrect results.
Avoidance: Do not define curved FEEDGE geometry on the h-p element boundary.
29780
70.5
P-Elements - Singular Stiffnes Matrix
Singular stiffness matrices or negative eigenvalues may occur in QUAD

p-elements for lower p-values when the p-distribution is nonuniform. This is
due to an error in bubble functions which are used for edges with p=1 and p=2.
The error is fixed in V70.5
Avoidance: Turn bubble functions off with system cell 225, specify NASTRAN
SYSTEM(225)=1 in the input file.
29781
70.5
LINKER - Trap Encountered
Optimization/Design Sensitivity - PBARL,
In an optimization run, if the PID (field 4) on the DVPREL1 entry references a

PBARL entry, and the FID (field 5) references an invalid field on the PBARL
entry, then the job will terminate in the f06 file without any messages. In
this case, the job terminates after generating the equivalent PBAR entries.
This error will result in the following error messages in the log file.
Trap encountered:

Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
0x000006f8
0x000005dc
0x0000028c
0x000010c0
0x00000284
0x00000934
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
domcb_
domc_
dopr1f_
dopr1_
xsem03_
mainal
Avoidance: Reference a valid PBARL FID.

29788
SG: ERROR 211
70.5
DMAP - MATMOD(12) - Illegal Trailer, BIOM
MATMOD(12) may output matrices with an incorrect trailer of the form of 7, when
it should be a form of 2. Some modules may accept this vector, while others
may crash in unpredictable manners. The ADD module, for example, exits with
the message below:
BIOMSG: ERROR 211 HAS OCCURRED IN ROUTINE BLDPK, FILE INDEX (FILEX) = 0
Avoidance: Use the MODTRL module to change the form to 2.
29797
2004
NALYSIS=FLUTTER - SFM 3007
Optimization/Design Sensitivity - DSAD, A
Flutter optimization cannot be performed with superelements unless the design

model is in the residual. If attempted the run will fail and issue the
following messages:
^^^ FLUTTER ANALYSIS COMPLETED. DESIGN CYCLE NUMBER=
*** SYSTEM FATAL MESSAGE 3007 (DSAD )
ILLEGAL INPUT TO SUBROUTINE DSAD14
0FATAL ERROR
29798
70.5
FRSPCF, TSPCF, DSADJ - UFM 5423, 3007
If the DRESP1 entries requests spc forces (FRSPCF or TSPCF) in a frequency
response or transient response optimization task and all the constraints are
inactive then an incompatible matrix multiply may result leading to the
following message:
*** SYSTEM FATAL MESSAGE 3007 (DSADJ )
ILLEGAL INPUT TO SUBROUTINE DSDJ2D
0FATAL ERROR
or
*** USER FATAL MESSAGE 5423---ATTEMPT TO ADD INCOMPATIBLE MATRICES, (SADD5)
Avoidance: Use the DSCREEN entry to force a constraint in each subcase to be
active.
29800
70.5
FLUID - SFM 3001 in MGEN
Virtual Mass - SOLs 3 and 7 through 12, M
In SOLs 3 and 7 through 12, if there is an ELIST1 entry and no free surface nor
plane of antisymmetry then
SFM 3001 is issued from the MGEN module.
Avoidance: Use SOLs 103 and 107 through 112.
29802
Equation
70.5
Documentation - QRG, SPLINE3 - Incorrect
The equation written in Remark 2 for the SPLINE3 Bulk Data Entry is incorrect.
The sign on the right-hand side of the equation should have a minus sign.
That is the processing of the SPLINE3 entry is similar to the MPC entry and the
equation should be written as:
u + sum(A * u ) = 0
d
i i
29817
70.0.5
pendent Materials May Fail, SFM 3007
Materials - MATT1, MATT2 - Temperature De
In Version 70, material table lookups can fail if there are points outside the
range of the supplied tables. This is true
for both linear and nonlinear solution sequences. Symptoms of this error are
the following messages:
*** USER WARNING MESSAGE 4698. STATISTICS FOR DECOMPOSITION OF MATRIX KLLRH
.
THE FOLLOWING DEGREES OF FREEDOM HAVE FACTOR DIAGONAL RATIOS GREATER THAN
1.00000E+07 OR HAVE NEGATIVE TERMS ON THE FACTOR DIAGONAL.
*** USER WARNING MESSAGE 3057 (NLITER)
MATRIX IS NOT POSITIVE DEFINITE.
*** SYSTEM FATAL MESSAGE 3007 (NLITER)
ILLEGAL INPUT TO SUBROUTINE NLINIT
Avoidance: Define the temperature dependent material tables over a wider range.
29825
70.5
UFM 316, Partitioned Superelements
Superelements - BEGIN BULK SUPER, GENEL -
If GENEL elements are used in a partitioned superelement run, then "USER FATAL
MESSAGE 316 (IFPDRV) ILLEGAL DATA ON BULK DATA ENTRY GENEL xxx SORTED ENTRY
COUNT = yyy" will be incorrectly issued if any GENEL ids in the second and
subsequent bulk data sections are greater than or equal to any GENEL ids in a
previous bulk data section.
Avoidance:
1) Do not use duplicate GENEL ids, and
2) Number your GENELs and order the bulk data sections such that the GENEL ids
of the second and subsequent bulk data sections are less than those of the
preceding bulk data sections.
29829
70.5
g may be Inefficient
Static Analysis - STRSORT - Stress Sortin
In very large models, if stress sorting is requested, then the time spent in
the stress sorting module STRSORT may dominate the total runtime. This is most
apparent in less efficient I/O machines.
29837
70.5
7, 108, 109, scr=no - UFM 9058
Differential Stiffness - STATSUB, SOLs 10
If scr=no and the Case Control command STATSUB are specified in SOLs 107, 108,
or 109 to select the static subcase for differential stiffness, then the run
will fail with the message:
USER FATAL MESSAGE 9058 (STATICS2) THE SOLUTION FOR THE RESIDUAL
STRUCTURE AND THE CURRENT SUBCASE DOES NOT EXIST.
Avoidance: Submit the job with scr=yes or insert the following DMAP alter:
compile phase1dr
alter 'not(statics) or kdiff',''
IF ( true ) then $
29851
Decompressed.
70.5
Installation - Not all the files could be
If the "GZIP" environment variable is set, mscsetup may fail with the error
message
Not all the files could be decompressed.
<req> MB free space are required.
<free> MB were available in the installation directory /some/dir/
<free> MB were available in the work directory /some/otherdir/
Please make more space available and redo this installation using the co
mmand
/some/dir/mscsetup.pbk -t <work_directory>
where <work_directory> is an alternate directory with at least <req> MB
free
space that can be used for scratch purposes during the installation proc
ess.
Prior to this error message, you may also see lines like:
7 22:18
36976
120864 69.4% ./msc70/irix64/demo1 11 Jul
7.gz: No such file or directory
22:18.gz: No such file or directory
29852
FDR)
70.0.5
Grid Point Force - GPFORCE - UWM 2354 (GP
Large TETRA models, about 35000 grids, with a GPFORCE request may fail with the
message:
. *** USER WARNING MESSAGE 2354 (GPFDR)
37
*** SYSTEM WARNING MESSAGE 3003 (GPFDR )
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK SCRATCH
(FILE 302) IN SUBROUTINE GPFDFB
0FATAL ERROR
Avoidance: Increase memory.
29859
70.7
raceback in hess1, UWM 6137
Complex Eigenvalue - CEAD, EIGC, HESS - T
Complex eigenvalue analysis that selects the Hessenberg method may issue a
traceback in the hess1 routine with no other message whenever the mass matrix
is singular. Other runs may issue a warning message that the input matrix is
rank deficient or may explicitly state that the mass matrix is singular and
proceed and give unreliable answers. Examples of the traceback and warning
message are given below:
Offset
Offset
Offset
Offset
Offset
0x00000030
0x00000ec4
0x00000c60
0x0000006c
0x00000994
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
pack_
hess1_
cead_
xsem11_
mainal
*** USER WARNING MESSAGE 6137 (DFMN)

INPUT MATRIX IS RANK DEFICIENT, RANK = 159
*** USER INFORMATION MESSAGE 4158 (DFMSA)
----STATIST
29890
70.5
Frequency Response - DLOAD, RLOADi, NEC -
On the NEC, if the DLOAD entry references more than 12 RLOADi entries in a
frequency response analysis, only the last 12 RLOADi entries will be included
in the applied load. The other loads are ignored.
Avoidance: If more than 12 combined loadings are required, use a single RLOADi
entry which in turn references multiple DAREA entries with the same ID.
29898
70.5
i - UIM (RESVEC) No Static Shapes
Modal Augmentation - PARAM,RESVEC, SUPORT
When a structure is free-free and a SUPORTi entry exists, there will be no

static shapes to augment the mode shapes when there are no constraints in the
model (i.e., no s-set, m-set or o-set). This condition leads to the following
message:
^^^ USER INFORMATION MESSAGE ( RESVEC )
^^^ NO STATIC SHAPES WERE FOUND TO AUGMENT MODE SHAPES
Avoidance: Add a disjoint grid point, with no elements attached to it.
Autospc will cause an s-set to exist.
29901
70.5
Superelements - CBEND - UFM 2016
If a superelement contains a CBEND element that uses a MAT1 that is not

referenced by any elements type, the MAT may not get copied internally into the
bulk data associated with the superelement. This will results in:
UFM 2016 MODULE = EMG
NO MATERIAL PROPERTIES EXIST

Avoidance: Make sure that each MAT1 that is used by a CBEND elements is also
used by an element type other than the CBEND. This may require a dummy element
such as CBAR be included in the appropriate superelements. This dummy element
does not need to be part of the structure and may be fully constrained.
29909
2001
32, Missing Output
Frequency Response - FREQ - SFE 4276, EC
In a frequency response analysis, if too many continuation entries are used for
a FREQ entry, then the job will either fail with the following error messages:
SYSTEM FATAL ERROR 4276.GETSTR
ERROR CODE
32 PID=
or the output will not be generated for all the frequencies.

Avoidance: Use a combination of the FREQ3, FREQ4, and FREQ5 in a modal
frequency response analysis.
29919
iption
70.5
Documentation - SEEXCLD - Incorrect descr
The description for field 3 (SEIDB) of the SEEXCLD entry should be changed from
SEIDB Superelement identification. (Integer > 0 or Character = "ALL")
to
SEIDB Superelement identification. (Integer >= 0 or Character = "ALL")
29922
Rigid Elements - RSSCON, SECNSD - UFM 6692
When a highly skewed plate element is attached to a solid element with an

RSSCON entry, the run may fail with the message:
*** USER FATAL MESSAGE 6692 (SECNSD )
RSSCON NUMBER *** CANNOT CONNECT AN EDGE OF QUAD ELEMENT *** TO HEXA
ELEMENT ***
Avoidance: The only avoidance is to reduce the skewness of the plate element
or to use the GRID option on the RSSCON entry.
29932
n SGI IRIX 6.4
69
Installation - MSC/NASTRAN will not run o
MSC/NASTRAN V68.2.3 (r2) for the SGI R8K may not run on IRIX 6.4 or later
systems. The failure will occur at program start, before any processing has
begun, with the following message:
MSC/NASTRAN started Mon Nov 17 08:45:14 PST 1997
Process Id = 27828
idalloc: address of dynamic common is too low
current brk value:
0x12700000 ( 309329920)
current address of XNSTRN: 0x121f0000 ( 304021504)
***memory allocation failed, program stop***
real
user
0m0.04s
0m0.02s
sys
0m0.02s
MSC/NASTRAN finished Mon Nov 17 08:45:14 PST 1997
The specific reason is that the amount of code and data put into the user's
address space by the runtime libraries and OS has become too large and
interferes with MSC/NASTRAN
29944
70.5
Static Aeroelastic Analysis - QSETi, SEQS
ETi - UWM 5229, SFMs 2198, 2199, 3007
If QSETi entries are present in SOL 144, Static Aeroelastic Analysis, the run
will fail in subDMAP AESTATRS. The message issued from subDMAP AESTATRS
varies. If the a-set contains only q-set dofs, the following messages are
issued:
*** USER WARNING MESSAGE 5229 (DDCOMP)
INPUT FILE TO MODULE DECOMP PURGED. MODULE RETURNS WITH PURGED OUTPUT.
*** SYSTEM FATAL MESSAGE 2198 MODULE = FBS
INPUT DATA BLOCK
101 HAS BEEN PURGED.
*** SYSTEM FATAL MESSAGE 2199 MODULE = FBS
SUMMARY, ONE OR MORE OF THE ABOVE FATAL ERRORS WAS ENCOUNTERED IN
SUBROUTINE DFBS
.
If the a-set contains q-set and t-set dofs the the following message are
issued:
*** SYSTEM FATAL MESSAGE 3007 (UMERGE)
QSETi and SEQSETi entries
29965
70.5
C, SWM 6065 (DBC)
The DBC module always has had a
available for any process list,
modes, etc. The enforcement of
until V70. This limit may lead
DBC - SWM 6065 - Undocumented Limit in DB

limit of 9999 allowable output positions
ie time, frequency,
this limitation has not always been consistent
to the message:
^^^ SYSTEM WARNING MESSAGE 6065 (DBC)

^^^ DBCMSG ERROR MESSAGE 43 FROM SUBROUTINE DBCAOL
OUTPUT LIST SUPPLIED EXCEEDS INTERNAL LIMIT, SUPPLIED
LIMIT 10000.
20013 INTERNAL
Version 70.5 uses a new dynamic access key technique which effectively
increases the limit for many problems. MSC/XL and other programs may no be
compatible with this new technique. SYSTEM(274)=1 (a.k.a. DBFACT=1) is
provided to access the old technique. This system cell may be set in the
system or user rc file as well as the individual test deck.
29976
Online Documentation - MNE - Irregular Fonts
The MSC Nastran Encyclopedia is no longer active. Cancelling CR.

Don
--------------------------------------------------------------------------------------------------------The characters on the menus of the MSC/NASTRAN Online Encyclopedia (MNE) appear
as irregular fonts when displayed on a Digital UNIX V4.X.

Avoidance: Change the Iview*fontList resource value from -*-bold-r-*-*-14-* to
-*-bold-r-*-*-12-*
29998
76 EC -31
70.5.2
Matrix Methods - MPYAD METHOD 4T - UFM 42
Certain problems cause MPYAD METHOD 4T to be selected when other methods would
solve the problem much more efficiently. The problem will take longer to run
than it should and may run out of disk space. The symptom of the bad method
selection is that MPYAD METHOD 4 T is selected with a large number of passes.
This can be seen in the f04 file, for instance, as follows:
20:36:57
END
20:36:58
BEGN
267:07 53987.9
626.3# 6843.0
267:08 53998.1
0.5
81.7, I/O=
40.0, TOTAL=
20:36:58 267:08 53998.1
20:36:58 267:08 53998.9
121.8
0.0
0.8
188.9#
FDRMGEN
0.0
FREQRS
6843.1
MPYAD
15 MPYAD
METHOD 4 T , NBR PASSES=****, EST. CPU=
30005
, SFM 3007
70.5
6843.1
6843.2
0.0
MPYAD BGN P=2930
External Superelement - ASETi, SE - SEP1X
In an external superelement generation run, if the DMIGPCH option is used with

the ASETi entries, and the external superelement contains upstream
superelements, then the punch file will not contain the physical boundary
matrices. The job may also fail with SFM 3007.
Avoidance:
1. Use BSETi instead of ASETi entries to represent the boundary points.

2. Use the DMIGDB, DMIGOP2, or MATRIXDB option instead of the DMIGPCH option.
30007
nt Answers
Documentation/Nonlinear Analysis - Multiple Subcases, Differe
A transient nonlinear analysis may yield slightly different results when the
problem is defined with multiple subcases rather than a single subcase. The
difference occurs because loads are averaged over three timesteps. The loads
at the end of a subcase and the beginning of the subsequent subcase may then be
slightly different.
30009
, or CODE 6
70.5
Installation - SIGNAL 11 (SIGSEGV) CODE 5
The submittal script on MSC/NASTRAN Version 70 on Convex computers has an error

which may cause jobs that request more than 10 million words of memory to fail
with the message:
***** RECEIVED SIGNAL 11 - Segmentation fault (SIGSEGV);
CODE 5 - Invalid page table reference (SEG_INVPTP_TRAP)
JOB ABORTING...
Avoidance: Modify the nast70.lcl file in the msc70/bin directory as follows:
%MSC_ARCH=convex:%
$tcmd %a.solver% $asgf %mem%
rather than
%MSC_ARCH=convex:%
30010
- SFM 3001
$tcmd %a.solver% %a.rel=68:% $asgf %mem%
2005
Superelements - BEGIN BULK SUPER, RESTART
A restart of a superelement problem will result in the fatal message shown

below, if the cold start contains superelements defined in the main bulk data
section as well as other superelements defined in the partitioned bulk data
sections.
*** SYSTEM FATAL MESSAGE 3001 (SEP1X )
THE EXECUTIVE FILE
0 DOES NOT EXIST.
PROGRAMMER INFORMATION: SUBROUTINE SEPMAB
Avoidance: Define all superelements in either the main bulk data section or the
partitioned bulk data section, but not both.
30011
70.5
OFREQ - SFM 4276.GREAD EC 3001
Optimization/Design Sensitivity - MFREQ,
If a multidisciplanary optimization run uses MFREQ as one of the disciplines,

contains an OFREQ Case Control requests and has a value of P2>=8 on the DOPTPRM
entry to indicate that the responses are to be printed, then the job will fail
with the following fatal message in the DOM10 Module:
SYSTEM FATAL ERROR 4276.GREAD ERROR CODE 3001 PID= 0
USER INFORMATION MESSAGE: TO OBTAIN A NASTRAN DUMP, RESUBMIT JOB WITH DIAG 44
INSERTED IN THE EXECUTIVE CONTROL SECTION.
Avoidance: Remove the OFREQ request or lower the value of P2 on the DOPTPRM
entry.
30015
70.5
TRIAX6 elements.
ESTIMATE - Incorrect estimates of DOF on
The ESTIMATE utility may incorrectly count the degrees of freedom associated
with CTRIAX6 elements. If the singular degrees of freedom are explicitly
constrained, either on spc entries, grid entries or grdset entries, then the
ESTIMATE will assume that a constraint in the 2 degree of freedom is removing
one of physical degrees of freedom. This is not correct as a CTRIAX element is
define in the x-z plane not the x-y plane. As a result, ESTIMATE will
undercount the DOF by one per CTRIAX6 element.
Avoidance: Do not explicitly constrain the singular degrees of freedom, let
autospc perform this function.
30020
wers
70.7
Matrix Methods - MPYAD 2 or 3 - Wrong Ans
When very low memory is requested such that MPYAD method 2 or 3 are selected,
and multiple passes are required, then the job will produce wrong answers.
Insufficient memory causes the sparse method to be deselected and MPYAD METHODs
2 and 3 to spill in multiple passes. This information is contained in the f04
file with DIAG 19.
Avoidance: Deselect method 2 and 3 by adding the following system cell to the
top of the input file or system rc file:
nastran system(66)=60
This may cause some jobs that require methods 2 or 3 to fail with the message:
*** SYSTEM FATAL MESSAGE 3001 (*** )
THE SCRATCH FILE
399 DOES NOT EXIST.
PROGRAMMER INFORMATION: SUBROUTINE GOPEN
0FATAL ERROR
The most likely jobs to encounter this message are optimization jobs in DOPR1.
If
30023
P Systems
70.5.1
Miscellaneous - Ishell does not work on H
The ISHELL module will not work on the HP Version 70 system because the
allocated size of the stack and child thread was too small for HP machine. The
original cause of this error was fixed in Version 70.5.0 but another error
effectively renders the error not fixed on HP-UX 10.2 systems. The error has
been fixed in Version 70.5.1.
30027
70.5
Optimization/Design Sensitivity - SPCD, s
cr=no, auxiliary models - Wrong Answers
In a shape optimization run with SPCD loads on auxiliary models and scr=no the
answers are wrong after the first cycle.
Avoidance: Use scr=yes or insert the following DMAP avoidance:
compile update
alter 'delete
\/yg1,'
DBVIEW ygp=yg
(WHERE DESITER=DESP) $
RESTART YGp,YG,//TRUE $ DETECT ENFORCED DISP CHANGES
endalter
30030
ency
70.5
Aeroelastic Analysis - SSG2 - Poor Effici
The ssg2 module reduces the spline matrix gtkg to several other components.
The r-set component is not used anywhere, and this operation takes a
considerable amount of cpu time.
Avoidance: An alter which eliminates this computation is to remove this
component from the dmap call:
COMPILE AESTAT NOLIST NOREF $ V70
ALTER 'SSG2','' $ REMOVE GTKR FOR EFFICIENCY. NOT USED DOWNSTREAM.
$SSG2
USET,GM,,,GOA,DM,GTKG/GTKR,GTKO,GTKS,GTKA,GTKL $
SSG2
USET,GM,,,GOA,DM,GTKG/,GTKO,GTKS,GTKA,GTKL
30037
70.5
TFL - UFM 3055
Optimization/Design Sensitivity - DESOPT,
If the TFL command is specified and ANALYSIS=MFREQ or DFREQ in a SOL 200 run
that performs adjoint sensitivity then the run will fail with UFM 3055 at
statement 404 in subDMAP DESOPT.
compile desopt
alter 'PARAML CASERS'
PARAML CASERS//'DTI'/1/ 15// S,N,TFL $
30041
70
authorize.dat or license.dat Files
Installation/Security - No read access to
If the user running mscsetup has their umask set to a value that disables group
or other access, e.g., 026 or 027, mscsetup may create files that are not
readable by the user community. The specific files of concern are:
<install-dir>/flexlm/licenses/license.dat and/or
<install-dir>/conf/authorize.dat.
Note, having a restrictive umask value is a necessary, but not sufficient,
condition for the error to occur. This error has been corrected on the
MSC/NASTRAN V70 (r4) CD.
Avoidance: Either of the following actions below will avoid the error.
1) Set the umask to 022 before running mscsetup.
or
2) Change the permissions of the affected files after installation, e.g.,
chmod a+r <install-dir>/flexlm/licenses/license.dat
chmod a+r <install-dir>/conf/authorize.da
30045
70.5
USH - Wrong SPCFORCE Output
Frequency Response Analysis - CDAMP1, CB
If frequency dependent damping and no stiffness is specified on a CBUSH-element

then the SPC forces will be wrong.
compile freqrs
alter 'equivx bggf\/xggf',''
ADD
bggf,/xGGf/iomega $
endalter
30054
70.7
L - UFM 9058 (SUPER3)
Eigenvalue Analysis - STATSUB, PARAM,INRE
If a PARAM,INREL,-1 is erroneously placed in a SOL 103 run along with a STATSUB

command for differential stiffness, then the following error message will be
received:
^^^ USER FATAL MESSAGE 9058 (SUPER3) - THE SOLUTION FOR THE RESIDUAL
STRUCTURE DOES NOT EXIST.
This error needs to be trapped in order help the user correct the problem.
Avoidance:
Remove the PARAM,INREL,-1 since it is only valid for inertial relief in SOL 101.
30058
70.5.2
Documentation - Incorrect Specification o
f FLEXlm License Servers on Windows NT
The MSC/NASTRAN Version 70.5 NT "Configuration and Operations Guide" indicates
the format for a list of alternate FLEXlm licensing files or license server
nodes is specified as
value:value:...
The correct format for NT machines is
value;value;...
Note, ANY list of values, such as a PATH, or the FLEXlm license spec, use
semicolons on Windows NT.
30064
ages
Matrix Methods - UDECOMP - Various User and System Fatal Mess
As problem sizes get larger the unsymmetric solver becomes less robust and the
program may fail after significant time is spent in the module.
Avoidance: The use of the unsymmetric solver can be avoided for some
solutions by:
SOL 108, fluid structure analysis. The default method now selects the
symmetric solver, where possible. Do not use PARAM, ACYM, NO, because it
forces use of the unsymmetric solver. The default value for this parameter
since Version 69 provides the correct action.
SOL 144. Several methods are introduced in Version 70.5 which avoid use of the
unsymmetric solver, which is still the default method. The recommended method
is requested by use of PARAM, AESMETH, AUTO. This selects an iterative
solution.
30073
C 1039
70.6
Nonlinear Analysis - APPEND - SFM 4276, E
In a nonlinear run, it is possible that the run may terminate in APPEND with
SFM 4276, EC 1039.
Avoidance: Set SYSTEM(158)=1000 and SYSTEM(159)=500
30083
70.5
Transient Response Analysis - TLOAD, TRL
,- time: command terminated abnormally
If a transient response analysis has a DLOAD that references a nonexistent
TLOAD id, the job aborts without any messages except:
*** TERMINATING
/pw/devl/svr4/structures/t477/nastran/msc70/solaris/analysis.ult
ra
*** Received signal 11 (SIGSEGV)
in the log file.
Avoidance: Remove the reference to the nonexistent TLOAD id.
30101
70.5
- UFM 3007 (UMERGE)
Superelements - Component Mode Synthesis
If an insufficient number of q-set degrees of freedom are allocated through the

SEQSETi entry to hold all of the internally generated residual flexibility
vectors, the run will fail in the UMERGE module with the message "USER FATAL
MESSAGE 3007" indicating illegal input to a subroutine.
Avoidance: Supply a larger number of SEQSETi degrees of freedom.
30104
ault Value
70.5
Documentation, QRG - TIME - Incorrect Def
The default value for the executive control section entry "TIME" changed in
V69. The value is now 1.892160e9 (seconds), not 60 minutes as documented.
Avoidance: Specify a user defined value for TIME.
30109
70.5
DMAP - NORM - SFM 4276 EC 7777
The norm module sets an output parameter to the size of the maximum magnitude
number in a matrix. On short word machines these numbers can be as large as
1.E60+. The number is stored in an output parameter of single precision whose
maximum size is 1.E30+. Therefore, matrices which are legal for other modules
cause overflow in norm.
Avoidance: Short of not generating matrices with large numbers in them, there
is no avoidance.
30124
70.0.3
me: command terminated abnormally
Miscellaneous - GPWG, PARAM,GRDPNT,0 - ti
Jobs with PARAM,GRDPNT on SUN SOLARIS Version 70.0.0 systems may fail in the
GPWG Module with the message:
*** TERMINATING /local/msc/msc70/solaris/analysis
*** Received signal 11 SIGSEGV
time: command terminated abnormally.
Avoidance: Remove the PARAM,GRDPNT from the data deck. The error could not be
repeated on Version 70.0.3 or 70.5.
30136
issing:"
70.5
Installation - "The following items are m
If a user or site has replaced the standard tar(1) command with another
"equivalent" utility, e.g., pax(1), mscsetup may fail with the following error:
The following items are missing:
msc70/access
where msc70/access is any file to be loaded from the CD-ROM.
Avoidance: Make sure the tar command invokes the standard tar(1) executable.
30147
2008.0.0 (MD R3)
ve Load Factors
Nonlinear Analysis - NLPCI, CRIS - Negati
If the Crisfield arc length method (TYPE=CRIS) is used in a post buckling

analysis, then the job may not converge. A symptom of this problem is the
printing of large negative load factors as shown below.
SUBID
SUBID
SUBID
2
2
2
LOOPID
LOOPID
LOOPID
29
30
31
LOAD STEP -6.389

LOAD STEP -7.891
LOAD STEP -10.059
LOAD FACTOR-7.38852477
LOAD FACTOR-8.89144518
LOAD FACTOR***********
Avoidance: Use the RIKS method or SOL 400.

30200
70.5.2
rectly Worded Fatal Message
Rigid Elements - RSSCON - UFM 6694, Incor
When two solid elements are connected to one shell element using the ELEM
option on the RSSCON entry, the following error message
is issued:
USER FATAL MESSAGE 6694 (GP4RS4)
SHELL GRID POINT xxx IS CONNECTED TO MORE THAN TWO SHELL ELEMENTS BY RSSCON
BULK DATA ENTRIES.
THIS IS NOT ALLOWED IF THE SOLID ELEMENT FACES CONNECTED ARE TRIANGLES.
Although the user made an illegal connection, the error message is incorrectly
worded. The problem is not that the shell is connected to a shell but that it
is connected to two solids.
The RSSCON entry can not connect more than one
solid element to one shell element when the ELEM option is used. If the shell
to solid connection spans across more than one solid element, the GRID option
must be used.
30201
70.7
Loads - FORCE - Unexpected Answers
A negative sign in the CID field of the FORCE entry may not be trapped and the
analysis may continue as if the field was left blank indicating the loads are
to be applied in the basic coordinate system.
Avoidance: Other than checking the oload output and entering proper data in
the field, there is no avoidance.
30204
Sensitivities/Optimization - MSGMESH - MSGMESH FE 9104
Running an input file with an auxiliary model generated with MSGMESH fails with
the fatal error:
1 CGEN
QUAD4 2001
2000
1
INPUT **
*** MSGMESH FATAL ERROR 9104 *** N1=1
ERROR **
2001
N2=5
N3=0
2054
N4=0
for any MSGMESH input entries.

Avoidance: Do not use MSGMESH entries in the auxiliary subcase.
30205
70.5
ith MAX Normalization
Dynamics - PARAM,RESVEC - Wrong Answers w
The Modal Augmentation (Residual Vector) Method introduced in Version 70 gives

wrong answers if the modes are normalized to MAX.
Avoidance: Use MASS normalization of modes.
30212
3007 (UMERGE)
70.5
Superelements - SUPORTi, CSETi, GDR - SFM
When performing component mode synthesis using generalized dynamic reduction

(GDR) and CSETi and SUPORTi entries are present the run may fail in the GDR
module with the following message:
^^^ USER INFORMATION MESSAGE ( RESVEC )
^^^ NO STATIC SHAPES WERE FOUND TO AUGMENT MODE SHAPES
*** SYSTEM FATAL MESSAGE 3007 (UMERGE)
0FATAL ERROR
Avoidance: Apply the following DMAP alter to avoid the error:
compile semr3
alter 'call resvec',''
call resvec pg,uset,gm,kfs,ys,bgpdts,scstm,cstms,medge,mff,
cmpho0,loo,koo,cmlama0,moo,got,koo,cmphrc/
cmpho,cmlama/
nozset/norc/seid/'o
' $
alter 'equivx cmpho0',''
CALL SEGOA uset,GOT,/GOAt/NOOSET/NOQSET/NOTSET $
EQUIVX CMPHO0/PHIVZ/NORC $
IF ( NORC>
30229
70.5
uring V70 installation
Installation - SGI R10000 misidentified d
On multi-processor SGI system running IRIX 6.2 or later, mscsetup may report a
syntax error such as the following:
./mscsetup[24]: 10000^J10000^J10000^J10000^J10000^J10000^J10000^J10000:
syntax
error
Avoidance:
Set the MSC_ARCH environment variable to "irix64" for any R8 or R10 processor
running IRIX64, or "irix" for any other combination of processor and OS. Note,
specifically "O2" systems use the "irix" architecture.
For example, on an Origin2000 system, set
export MSC_ARCH=irix64
setenv MSC_ARCH irix64
30235
M 3055 (MPYAD)
70.5
# Korn shell
$ C-Shell
Superelements - SUPORT1, PARAM,SESEF - UF
The use of SUPORT1 entries with PARAM,SESEF,>=0 and superelements will result
in *** USER FATAL MESSAGE 3055 (MPYAD ) AN ATTEMPT TO MULTIPLY OR MULTIPLY AND
ADD NON-CONFORMABLE MATRICES TOGETHER WAS MADE IN MODULE MPYAD.
Avoidance:
$V70
compile postreig nolist noref
alter 4 $
type parm,nddl,i,n,suport $
alter 25 $ after call setq
paraml casedr//'dti'/1/255//s,n,suport $
ENDALTER
30250
70.5.2
- SFM 3002 (DSADJ )
Optimization/Design Sensitivity - REPCASE
The message:
SYSTEM FATAL MESSAGE 3002 (DSADJ)
may occur when the adjoint method is invoked and there are REPCASE case control
commands.
Avoidance: The best avoidance is to remove the REPCASE commands. A more
complex and less robust avoidance is to force the direct sensitivity method.
This latter technique entails forcing the retention of an element response.
30251
70.5
R - SFM 4276, EC 7777
Grid Point Force - GPFORCE, SUBCOM - GPFD
If a run contains SUBCOMs and a GPFORCE request, the run will fail on Digital
Alpha UNIX systems in the GPFDR module with the following message and
traceback:
SYSTEM FATAL ERROR 4276.tbk ERROR CODE
7777 PID= 0
USER INFORMATION MESSAGE: TO OBTAIN A NASTRAN DUMP, RESUBMIT JOB WITH DIAG 44
INSERTED IN THE EXECUTIVE CONTROL SECTION.
Process Id = 9467
handler(0x11ffff138,0x0,0x120974d00,0x150fb59a4,0x1405fd6c0) L. 24
<<?? pc=0x12105c844>>(0x120974d00,0x150fb59a4,0x1405fd6c0,0x8,0xc00000007) L.
24
gpfdr_(0x1409ac7b0,0x11ffff494,0x14057e9b0,0x14057e9b4,0x1409ac7b4) L. 1057
xsem13_(0x12005727c,0x11ffff915,0x11ffff710,0x0,0x1) L. 94
mainal_(0x11ffff710,0x0,0x1,0x0,0x3ffc0082620) L. 349
<<?? pc=0x12005727c>>(0x140a40188,0x0,0x100000000,0x100000001,0x100000000) L.
349
<<?? pc=0x12
30252
70.5
uation Entries in Punch File
Heat Transfer - RADMTX - Duplicate Contin
If a heat transfer analysis contains multiple cavities and each cavity exceeds
100,000 elements the duplicate continuation entries for RADMTX may be output
to the punch file.
This problem only occurs when each cavity exceeds 100,000 elements.
If each cavity has more than 100,000 elements,then you will get the duplicate
continuation entries on the RADMTX bulk data entry. This error will lead to:
*** USER FATAL MESSAGE 4392. CONTINUATION CARD ERRORS. EXPLANATIONS FOLLOW LIST
OF CARDS IN ERROR
when the punch file is used.
Avoidance: Manually edit the punch file. The continuation fields may be left
blank as long they are in order.
30254
70.5
Complex Eigenvalue Analysis - CEAD - SFM
4276, EC 7777
If a complex eigenvalue analysis is missing a cmethod entry in the Case Control
the job may end with a traceback in the CEAD module.
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0x00000020
0x00004110
0x00000134
0x00000240
0x0000019c
0x00004048
0x000002c0
0x000010d8
0x00000094
0x000009b4
in
in
in
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
raise
bioxxx_routine
bioxxx_
nsexit_
pexit_
gperr_
mesage_
cead_
xsem11_
mainal
--- End of call chain --Avoidance: Add a cmethod entry in the Case Control.
30259
or Answers
70.5
Heat Transfer - TETRA, PENTA, CHBDYG - Po
The ten noded TETRA element and the 15 noded PENTA element produce poor answers
when the convection coefficient is large relative to the thermal conductivity
of the material. For example , when h*delta(x)/k is larger than 10, where h is
the convection coefficient, delta(x) is the element length and, the k is the
thermal conductivity of the material poor answers result.
Avoidance: Use other element types such as the 4 noded TETRA which uses
CHBDYG,AREA3 for convection.
30273
age
2001.0.1
DMAP - CALL statement - UFM 72, Poor mess
If a value or variable is not specified for all parameters on a CALL

statement then UFM 72 is issued with
misleading information becaue the parameter named in the message is not the
cause of the error.
The error is caused by the unspecified parameter following the named parameter.
For example,
83
CALL FRRD2X KDDZ,BDDZ,MDDZ,,PDFZ,FOL,CASES,

EDT,SILD,USETD,/
UDVF1,FOLI1/ENFORCE///////FRRDSET//FIRSTBD0 $
0*** USER FATAL MESSAGE 72 (XGPIDG )

PARAMETER SYNTAX ERROR IN ABOVE STATEMENT. PARAMETER IS ENFORCE --ERROR CODE =
2
Avoidance: Remove the unspecified parameters or specify dummy va
30293
2001
- Undocumented Limit
The intrinsic functions MIN and MAX for the DEQATN entry have an open ended
list of arguments. There is an undocumented limitation that the number of

arguments for these functions has to be less than 100.
This problem is
considered fixed in Version 2001 by raising the limit to 1000.
Avoidance: If it is desired to take the max (or min) of more than 100
arguments, several intermediate functions can be defined that find the max of a
number of arguments less than 100 and then the max of the intermediate
functions will result in the overall maximum.
30299
70.5
uperelements - SFM 3002
Optimization/Design Sensitivity - BCDR, S
If all the design variables and responses are specified in upstream

superelements then the following messages may be issued in subDMAP PSLGDV and
module BCDR:
*** SYSTEM FATAL MESSAGE 3002 (BCDR )
EOF ENCOUNTERED WHILE READING DATA BLOCK (NONE) (FILE 101) IN
SUBROUTINE BCDR.
1. Specify at least one design variable or response in the residual
structure.
compile desopt
alter 'call descon'
seid=0 $
peid=0 $
equivx cases/casdsn/-1 $
endalter
30322
swers
70.0.5
Heat Transfer Analysis - TETRA - Wrong An
In MSC/NASTRAN Version 70, a temperature look-up for a temperature dependent

material property for the TETRA element only occurs at temperature=0.0. This
causes wrong answers.
Avoidance: Use other element types such as HEXA or PENTA elements when there
are temperature dependent material properties in the problem.
30325
DMAP - Reserved Names
If a parameter or datablock on a type statement uses a name that has "cond" as

a prefix, for example, condnosq, then the results using these parameters or
datablocks in subsequent operations are unpredictable. For example, in the
following dmap operation,
type parm,,rs,n,condnosq $
condnosq = 1.0 $
message //condnosq $
does not produce a value of 1.0 for the condnosq parameter. The reason is that
"cond" is a dmap exec statement for branching operations.
Avoidance: Do not define a datablock, parameter, or label using "cond" as a
prefix for the name.
30336
Poor Message
DMAP - Building a New Solution Sequence - UIM 1179 (RESDBS),
An attempt to LINK a "called SUBDMAP" (one with input and output arguments on
the SUBDMAP line) will result in the following error message, which does not
explain the problem:
*** USER INFORMATION MESSAGE 1179 (RESDBS)
A DB-DIRECTORY IMPROPERLY CLOSED IN THE PREVIOUS RUN IS BEING RESTORED BY
THIS RUN.
MAIN: "Access violation" (C0000005) exception encountered.
MAIN: For reference, A(MAINAL) = 408540, A(/SYSTEM/) = 14ef640
MAIN: Exception occurred at address 89050D.
MAIN: Program attempted to access data at location 19970738.
MAIN: Context Flags 0001001F
Avoidance: Do not LINK a "called SUBDMAP" only MAIN SUBDMAPs with no arguments
in the SUBDMAP line are to be linked.
30367
Stresses
70.5
Dynamic Analysis - TEMP(LOAD) - Incorrect
It is an undocumented limitation that thermal loads cause incorrect stresses in

dynamic analysis. This limitation will be documented under TEMP(LOAD) case
control entry in the Version 70.5 Quick Reference Guide.
30414
70.7
Miscellaneous - SET - SFM 3008
Long SET case control entries may cause NASTRAN fail with the message SYSTEM
FATAL MESSAGE 3008. The following SET entry resulted in this fatal:
SET 1 = 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21
Avoidance: The above SET entry may be broken up as follows:
SET 1 = 1,2,3,4,5,6,7,8,9,
10,11,12,13,14,15,16,17,18,19,
20,21
30419
70.5
e Field Format Continuation Entries
Documentation - QRG - Description of Larg
In the discussion in the QRG on the "Format of Bulk Data Entries" there is no
mention made of how to continue a large field format Bulk Data Entry. There is
an example of a large field format entry, which shows the correct use of the
"*" in column 1 that marks field 1B as a continuation mnemonic of the parent
entry begun in field 1A. However, in the "Continuations" discussion, there is
no mention made of how to continue with child entries that are also of the
large field format. These types of continuations require an "*" in column 1 of
field 1B along with the continuation mnemonic of the first half of the entry.
Additionally, it is stated that continuation fields can be auto-generated (the
recommended practice) within MSC/NASTRAN, provided that those continuations
immediately follow
30420
or Message
70.5
Nonlinear - EIGB - SFM 6707, SFM 3007, Po
In a nonlinear buckling analysis, if the method on the EIGB entry is SINV or

INV and no eigenvalues are found in the range, then the following misleading
messages will be printed in the .F06:
*** SYSTEM WARNING MESSAGE 3030 (OFP) THE OFP MODULE CANNOT PRINT THE DATABLOCK
LAMA USER ACTION: USE THE MATPRN OR TABPT MODULE. PROGRAMMER INFORMATION: OFP
LOC CODE =
40 FILE = 102
*** SYSTEM FATAL MESSAGE 6707 (PARAML) THE PARAML MODULE WITH P1=DTI DETECTS A
STRING RECORD. *** SYSTEM FATAL MESSAGE 3007 (PARAML) ILLEGAL INPUT TO
SUBROUTINE PARAML
or
0*** SYSTEM FATAL
MESSAGE 4540,
INPUT ESTNL DATA BLOCK IS NOT NONLINEAR FORMAT.
Avoidance: Choose a more appropriate range on the EIGB ent
30425
PPUN
Miscellaneous - (PUNCH) - Segmentation Fault in OFP Source OF
Large punch jobs on the HP and SUN may fail with the following message:
Segmentation fault in OFP source OFPPUN
SIGSEGV in ofppun.f
and in the log file:
11:21:41 Beginning Analysis
Process Id = 23091
Process 23091 received signal 8
Process traceback ...
( 0) 0x0009700c sysrcv + 0x320 [/apps/msc70/msc70/hpux/analysis.pa2_0]
( 1) 0x00f83310 _sigreturn [/apps/msc70/msc70/hpux/analysis.pa2_0]
( 2) 0x00f48644 __convert_and_assign_data + 0x1464
[/apps/msc70/msc70/hpux/analysis.pa2_0]
( 3) 0x00f4a368 __cnv_fc + 0xb0 [/apps/msc70/msc70/hpux/analysis.pa2_0]
( 4) 0x00f335bc __a_c_t + 0xed4 [/apps/msc70/msc70/hpux/analysis.pa2_0]
( 5) 0x00f33ecc __a_c_t + 0x17e4 [/apps/msc70/msc70/hpux/analysis.pa2_0]
( 6) 0x00f342d8 __io_tn1 + 0x118 [/apps/msc70/ms
30453
r, UFM 802
2001
Documentation - ALTER - String Based Alte
If a string-based DMAP alter uses the ! in the expression (find occurrence at

the beginning of a line), it is possible that MSC/NASTRAN will fail with USER
FATAL MESSAGE 802 stating that no match was found, even if there should be a
match.
Avoidance: If you encounter UFM 802, check to see that the desired line is not
preceded by a comment in the DMAP. The search logic using the "!" assumes the
line begins on the preceding comment. In order to avoid this, remove the ! from
the text string (be careful to verify that the DMAP alter is inserted at the
correct location, as this will then search for any occurrence of the text on a
line, rather than only searching for lines which begin with the text). If
necessary a more unique search string will have to be selected.
30459
Results
70.5
Estimate - Leading 0's in Integers - Poor
If an integer has leading 0's (e.g., 05 instead of 5) on a NASTRAN bulk data

entry, MSC/ESTIMATE may not interpret the data correctly.
Avoidance: Remove any leading 0's from the bulk data of a file to be processed
by ESTIMATE.
30462
70.5
Estimate - Excessive Errors - Run Aborted
If 'memory=estimate' or 'buffsize=estimate' is specified on the nastran command

line or in an RC file, messages generated by the ESTIMATE utility may overflow
a buffer within the nastran command. When this overflow occurs, the following
message will appear:
*** SYSTEM WARNING MESSAGE (nastran.estimate_job_requirements)
a.estimate=<install-dir>/msc705/<arch>/estimate
(program default)
ESTIMATE executable filename. This keyword may only be specified on the
command line or in the command initialization file (see <0.ini>).
It appears that ESTIMATE has failed. Ensure that the program is properly
installed. Assuming default value for buffsize.
Avoidance:
Either of the following avoidances will work:
1. Fix the errors in the input file and rerun wi
30468
70.5
Miscellaneous - VECPLOT - SFM 3062
If a very large memory is requested in a run, then the job may fail in vecplot
with the following error messages:
0*** SYSTEM FATAL
MESSAGE 3062 MODULE = VECPLOT
FAILURE OCCURRED IN UTILITY GETGPT CALLED IN SUBROUTINE VECPL1 .
PREXYZ FLAG ARGUMENT WAS SET WITH AN INCORRECT VALUE TO GET THE REQUESTED
DATA RETRIEVAL.
In this case, a memory of 400mw was requested.
Avoidance: Reduce the amount of memory request.
30496
tal Messages
2001.0.3
Restarts - Delete Entry - Various User Fa
When a restart delete entry, using the small field format, is incorrectly
shifted a column to the left, the beginning and end values are misread without
a fatal message.
For instance the following delete bulk data entry:
/
65266
65267
is read as:
/
5266
5267
Avoidance: Use free field, comma separated input for this entry.
30507
SFM 3062
70.5
Optimization/Design Sensitivity - SDR2 -
A shape optimization task may fail with a system fail message,

0*** SYSTEM FATAL
MESSAGE 3062 MODULE = SDR2
FAILURE OCCURRED IN UTILITY MAPXTI CALLED IN SUBROUTINE SHLNRM .
The failure may occur when the following conditions are met:
1. A shape optimization job;
2. Shell normal is invoked;
3. The identification id for grid points is larger than the total number of
grids in the model. Say the model has 10 grids but the ten grids are identified
by 100001 to 100010.
The possible avodance:
1. Always start grid ids from 1;
2. Set SNORM=0.0.
Notice that if shell normal can not be ignored, the avoidance # 1 should be
used.
30515
70.5
Restarts - EPOINT - Inefficient Restart
If a restart is made from a solution 103 normal models run and epoints are
added, the modes will be recalculated even though they are unaffected by the
epoints.
Avoidance: Use the following alter, it removes the check on DYNAMIC(s) and the
restart skips the READ or REIGL module.
THIS AVOIDANCE PRODUCES INCORRECT RESULTS!
compile ifpl
alter 158,158
compile phase0
alter 590,590
endalter
30522
70.5
SFM 5628 (DSAD12)
Optimization/Design Sensitivity - PCOMP -
In design optimization, if there are composite responses (DRESP1 = CSTRESS,

CSTRAIN or CFAILURE) and force responses (DRESP1=FORCE), a USER FATAL MESSAGE
5628 as shown below will be encountered unless the highest element ID has a
composite response.
0*** USER FATAL MESSAGE 5628 (DSAD12)
DRESP1 ID =
5363003 IS FOR RTYPE =
FORCE AND ELEMENT ID =
5682.
THE RESPONSE COULD NOT BE FOUND, EITHER BECAUSE THE ELEMENT DOES NOT EXIST
OR
BECAUSE THE RESPONSE TYPE IS NOT AVAILABLE FOR THE ASSOCIATED ELEMENT
TYPE.
0*** USER FATAL MESSAGE 5628 (DSAD12)
DRESP1 ID =
5363004 IS FOR RTYPE =
FORCE AND ELEMENT ID =
5682.
THE RESPONSE COULD NOT BE FOUND, EITHER BECAUSE THE ELEMENT DOES NOT EXIST
OR
BECAUSE THE RESPONSE TYPE IS NOT AVAILABLE FOR T

30542
sing Output
70.5
Response Spectra Analysis - SUBCASE - Mis
When using Response Spectrum ananlysis in SOL 103, if you have multiple
SUBCASEs (solutions) and there are diffenrent output requests in various
SUBCASEs, only the requests which match the first SUBCASE will be honored.
compile postreig
alter 'sdr2 ',''
SDR2
CASEDR,CSTMS,MPTS,DIT,EQEXINS,,,,BGPDTS,OLB,PHQG,
PHIGH,EST,XYCDBDR,,,,GPSNTS,,,/
,IQG1,IPHIG1,IES1,IEF1,/
'mmREIG' $
endalter
30550
rect Default
70.5
Documentation - QRG, INIT,SCRATCH - Incor
The default value for the SCRATCH dbset is stated as 175,000 gino blocks in the
Quick Reference Guide. The correct default value
is 250,000 gino blocks.
30560
70.5
4410, Missing output
Restarts - scr=mini, SUPORT command - UWM
If SCR=MINI is specified on the command line and the SUPORT command is

specified in the Case Control, then subsequent data recovery restarts will
terminate with UWM 4410 and no data recovery output.
compile sestatic
alter 'call setq'
PARAML CASES//'DTI'/1/255//S,N,SUPORT $
endalter
30563
ong answers
70
Transient Analysis - OTIME, op2, f06 - wr
In Version 69.1, the OTIME command is ignored for element-type output (e.g.,
forces, stresses). Furthermore, the time labels are in the correct sequencial
order, but the label values are incorrect. The OTIME command functions
properly for grid-type output (e.g., disp, velo, acc). This problem has been
corrected in Version 70.
Avoidance: Either remove the OTIME command or upgrade to Version 70.
30575
GL
n the Number of Design Variables
Optimization/Design Sensitivity - Limit o
There is a limit imposed by the optimization algorithm used for design

optimization that the number of design variables (NDV).
squared must be less than the number of machine precision words available. For
example, if a job is run with 40 million single precision words, the number of
design variables must be less than the sqrt(40,000,000/2) = 4472 on a short
word machine and 6324 on a long word machine.
30578
2008.0.0 (MD R3)
1, LOAD - Wrong Answers
Nonlinear Analysis - PARAM,LGDISP, PLOADX
If PLOADX1 (pressure loads for axisymmetric elements) is referenced by a bulk

data LOAD record, follower forces (in nonlinear solution sequences) do not
work. Pressure loads are computed based upon the initial geometry.
Avoidance: An avoidance is to write PLOADX1 records for every load magnitude
needed, and not use the LOAD records to combine loads.
30585
70.5
Licenses for MSC/NASTRAN
Installation/Security - Unable to Obtain
There is an error in the FLEXlm libraries provided by Globertrotter that result

in the libraries ALWAYS examining the LM_LICENSE_FILE environment variable even
though a valid license file or server has been explicitly named in the
"authorize" keyword. As a result of this, the following limitation is set:
If the LM_LICENSE_FILE environment variable is set, it shall point to a
valid license file.
This error is most easily seen by setting the "authinfo" value to 9 and
examining the LOG file output. If a license file not named by the "authorize"
keyword is present, it was obtained from the LM_LICENSE_FILE environment
variable.
Avoidance: Delete the LM_LICENSE_FILE environment variable if it does not
point to a valid FLEXlm license file.
30590
70.5
, Restarts - SFM 4540
Nonlinear Static Analysis - Superelements
When downstream superelements are processed in a SOL 106 coldstart by using

SEALL=n, where n is the superelement number, NASTRAN incorrectly issues the
SYSTEM FATAL
MESSAGE 4540,
INPUT ESTNL DATA BLOCK IS NOT NONLINEAR FORMAT.
Avoidance: If you are using partitioned superelements and you are going to
restart to process the residual, ignore the fatal message and restart anyway.
The fatal message is benign and restarts are possible.
30617
70.5
n(corner) - Incorrect default
Documentation - QRG, Force(corner), strai
The Quick Reference Guide incorrectly lists cubic as being the same as the
corner output for the force and strain output. The correct default corner
option for the force and strain corner output is BILIN, similar to the stress
output.
30631
rted
Documentation - Reference Manual, GPSTRESS - Strain Not Suppo
In the second paragraph of Section 10.1 of the MSC/NASTRAN Reference Manual it

states "The calculation of strains may be sustituted for stresses using the
STRAIN command in place of the STRESS command in the Case Control Section"
inside the same paragraph that describes the GPSTRESS features. This may lead
users to incorrectly conclude that grid point strain can be obtained by
substituting the STRESS Case Control Command with the STRAIN command. Grid
point strain output is not supported.
30638
70.5
- Wrong Answers
Grid Point Force Balance - GPFORCE, PLOAD
Grid point force balance output of element force contributions are not correct
when pressure loads are applied. For example, PLOAD1 on BAR, BEAM and BEND
elements will produce different element forces with the ELFORCE data recovery
than from that printed in the grid point force balance output. The same is
true of the plate elements under pressure loads.
Avoidance: There is no avoidance, this is currently a limitation of the GPFDR
module. The GPFDR module has as input the discrete load vector to perform the
data recovery operations. The discrete load vector does not contain any of the
distributed load effects and will calculate element force contributions based
on the discrete loads not the distributed loads. The limitation has not been
removed but is now documented under the G
30639
70.5
BEAM - Wrong Answers
Optimization/Design Sensitivity - PLOAD1/
A design optimization job may report incorrect element response value

(Stress/Strain/Force) for CBAR, CBEAM and CBEND elements subjected to pressure
loads because SOL200 does not account for distributed forces of the PLOAD1
entry while recovering those element response quantities.
30645
70.5
datablocks on type Statements
DMAP - User Supplied subdmaps may Discard
If a user subdmap is of the form:

subdmap mine in1/out1
type db sils
mod1 sils/out1 etc.
etc.
. . .
return
end $
and sils is a datablock in the nddl, which means it is stored in the database,
then assuming qualifiers are set correctly, module mod1 will find sils and
use it appropriately. However, at the end of the execution of the subdmap the
LTU logic will automatically delete the datablock. This will not be discovered
until the datablock is needed by a downstream subdmap, when it will no longer
be in the database. Consequences include wrong answers or mysterious fatal
error crashes such as "SILS NOT AVAILABLE" for modules that allow purged
inputs. These errors occur even though SILS was in the database in prior
subdmaps.
Avoidance: Do not write the type stateme
30703
GL
Number of Grids
Postprocessing - XDB Limitation - Maximum
There is a limit on the number of GRID points which can be processed by the DBC
module for the ".xdb" file. The

most significant factors is the
solution sequences the limit is
exist in the model, some of the
the ".xdb" file.
limit is dependent on many factors, one of the

solution sequence. For dynamic and nonlinear
214748 GRID points. If more GRIDs than this
desired data may not be processed and placed in
Although there is still a limit on the total amount of data DBC can process,
Version 70.5 contains changes that take into account the actual number of
timestep or load steps actually solved. Thus, the program can more accurately
predict the amount of data that it must process. The maximum number of grids
is now determined dynamically and this change effectively greatly increases
At 2005R2 this limitation is removed with DBCFACT=2.
30704
57
70.5
Nonlinear Heat Transfer - CHBDYG - UFM 21
The backside on an ambient plate element cannot be used for thermal radiation.
If attempted the follow message results:
USER FATAL MESSAGE 2157, MATERIAL ID = 0 FOR ELEMENT ID =
DOES NOT APPEAR ON ANY RADM RADIATION MATERIAL DATA CARD
FATAL ERROR
Avoidance: Add a front face RADM entry.
30712
70.5
NREL, ADD - UFM 5423
The USER FATAL MESSAGE below may occur when performing an inertial relief
sensitivity analysis with multiple subcases and one or more subcases does not
have any retained responses. The message is:
0*** USER FATAL MESSAGE 5423---ATTEMPT TO ADD INCOMPATIBLE MATRICES, (SADD5)
COLS ROWS FORM TYPE NZWD DENS
TRAILER FOR PL
IS
6
57
2
2
50 3596
TRAILER FOR PLR6Y
IS
12
57
2
2
64 5614
TRAILER FOR PLIPA
IS
12
57
2
2
34 2281
FATAL ERROR
compile desopt
alter 'call descon'
solapp='stnmbk' $
call dbstore caseds,casdsn,,,//0/0/'
'/0 $
compile inersen
alter 'plbase','qrbase'
call dbfetch /caseds,casdsn,,,/0/0/0/0/0 $
type parm,,i,n,ic
30721
70.5
- Eigenvectors in Wrong Order
Mode tracking in design optimization seeks to place modes back into their
original order if any mode switching has occurred as a result of changes made
to the design. The eigenvalue summary, however, will not be correctly
correlated with the eigenvector output if modes have switched, and the
parameter, NASPRT is set to a positive integer to request data recovery for the
intermediate design cycles. The values are correct but the order does not
agree with the eigenvalue summary table.
Avoidance: The following is a DMAP alter for Version 70 that correctly
reorders the eigenvector summary output as a result of mode tracking. This
alter has been built into Version 70.5 of MSC/NASTRAN along with some
additional module MODTRK enhancements.
$
$ v70 avoidance for csr 30721:
$
comp
30738
2001
, - SFM 3001, Possible wrong answers
Frequency Response - QUAD4, sort2, corner
In a frequency response analysis, if SORT2 output is requested, then the

following error message may be issued in data recovery after printing the
element force output.
*** SYSTEM FATAL MESSAGE 3001 (DPD )
THE OUTPUT DATA BLOCK IN POSITION
11 DOES NOT EXIST.
Furthermore, on the SGI (and possibly other machines), a sort2, corner output
request for quad4 elements may produce incorrect results that are evident by
the printing of very large element forces (e.g. E+20) or "Inf".
Avoidance: Use a sort1 output request with frequency response. If corner
output is not being requested, and if random response is not being performed,
then the following alter may avoid the problem in Version 70.
compile sedrcvr souin=mscsou nolist noref $ V70
alter 'dpd'(1,-2),'dpd'(1,7) $ De
30740
70.5
2 - UFM 3005, Subroutine AMPC
Aeroelastic Analysis - AMP, CAERO1, CAERO
The message:
USER FATAL MESSAGE 3005 (AMP )
ATTEMPT TO OPERATE ON THE SINGULAR MATRIX SCRATCH IN SUBROUTINE AMPC
FATAL ERROR
will occur in the AMP module if multiple group ids are used in defining the
aerodynamic model and the model contains both lifting surface entries (CAERO1)
and body entries (CAER02).
Avoidance: Place all the aerodynamic panels and bodies in the same
interference group.
30766
70.5
MNE - Missing Collection on V70 MNE
If you choose an installation option that does not install the PRIMARY (V70)
documentation set onto the hard disk, you must do the following after executing
the installation script:
1. Change the current directory to <install_dir>/mne70, where <install_dir> is
the directory in which you installed the MNE:
cd
2.
rm
3.
ln
<install_dir>/mne70
Remove the existing erroneous symbolic link to v70qrg:
v70qrg
Add the correct link for v70qrg:
-s /<CDROM>/doc/mne70/v70qrg
where <CDROM> is the CD-ROM mount point.
30775
s
70.5
Loads - PLOADi - Incorrect Follower Force
There is an error in the follower force stiffness matrix (see PARAM FOLLOWK)
due to PLOAD, PLOAD2 or PLOAD4, if the global displacement system is not in the
basic coordinate system. This error occurs if the first grid point listed on
the PLOADi has a non-basic coordinate system reference in field seven of the
corresponding GRID entry.
30776
or Buckling
GL
Element Strain Energy - ESE - Incorrect f
The element strain energy output for modes found in SOL 103 using STATSUB is
incorrect. It includes only the linear portion
of the ESE; the differential stiffness contribution is ignored.
Avoidance: The following alter will calculate the strain energy contribution
of the differential stiffness in addition to the linear portion:
$ the following dmap is for V70 SOL 103 with STATSUB
$ after the solution completes, there are 2 ESE outputs
$ 1st: unstiffened ESE due to KELM
$ 2nd: stiffened ESE due to KDELM
$ combine these to get the total modal ESE
$ this has not been tested with superelements.
COMPILE SEKDR,NOLIST,NOREF
ALTER 'EMG.*KDELM'
$
CALL DBSTORE KDELM,KDDICT,,,//-99/SEID/'DBALL'/0 $
COMPILE SEDRCVR,NOLIST,NOREF
ALTER 'OFP.*ONRGY1
30782
Superelements/Buckling - Wrong Answers.
Superelements give wrong answers for buckling.

Avoidance: Do not use superelements.
30797
70.5
Utilities - ESTIMATE - Poor Diagnostics
The ESTIMATE program is currently limited to estimating resources for models

composed of GRID and connectivity entries. If no GRIDS are present, ESTIMATE
will return a USER FATAL MESSAGE or may indicate NaNQ for memory or disk
estimates. If no recognized connectivity bulk data entries are present,
ESTIMATE will return DOF=-2**(32-1).
Avoidance: Do not use the ESTIMATE program for models as described above. Do
not use either the "memory=estimate" or "buffsize=estimate" keywords on a
nastran command for models as described above.
30805
Nonlinear Analysis - Multiple Subcases - Error in Bisection l
ogic, Infinite LoopSFE 3002 (TOLAPP)
In a nonlinear analysis, in some instances, the load factor tolerences may be

in error. When this occurs the value of the load factor exceeds 1.0 and the
solution may enter an infinite loop or produce some other error later on.
The problem is identified when one of the load factors > 1.0
Avoidance: On the NLPARM entry increase the ninc field by 1 and restart into
the offending subcase. This will change the tolerance
30810
2001
Infinite CPU Loop
Optimization/Design Sensitivity - SEP1A -
When the analytic boundary shape option is used for a shape optimization task
and a local coordinate system is defined for the auxiliary boundary model, the
job may fall in an infinite loop in the SEP1A module.
Avoidance: Do not define local coordinate systems in the auxiliary boundary
model.
30852
, UIM 1206
GL
Postprocessing - PARAM,POST,-4 - UIM 1207
If PARAM,POST,-4 is used and FORMATTED output is requested in the OUTPUT2 file,

error messages 1207 and 1206 will occur indicating that several datablocks have
not been written to the file. An example of these message are:
USER INFORMATION MESSAGE 1207 (OUTPN2)
THE DATABLOCK KDICT /KDICT
DEFINED AS NDDL TYPE KDIC IS NOT SUPPORTED
BY NEUTRAL FILE TRANSLATION.
THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT
0*** USER INFORMATION MESSAGE 1206 (OUTPN2)
THE DATABLOCK OPHIG /OPHIG
IN AN OUTPUT2 REQUEST IS NOT DEFINED IN
THE MSC/NASTRAN DATA DEFINITION LANGUAGE (ND
This is due to the fact that these datablocks are not described in the NDDL.
Avoidance: Use binary OUTPUT2 if PARAM,POST is set to -4.
30903
Constraint
GL
Superelements - PARAM,AUTOSPC - Incorrect
If two or more superelements which have no internal constraints applied, meet

at a single GRID point, and no elements which are not in those superelements
connect to that GRID point, AUTOSPC may incorrectly constrain that point. The
reason for this is that the reduced stiffness matrix at a single point for a
determinate structure with no constraints is a null matrix. This limitation is
unlikely to affect real world models since it is unlikely that the boundary
between superelements will be comprised of a single point.
Avoidance:
1. Put the DOFs you want as dynamic analysis variables on spcoff bulk data
entries.
2. Put in small springs to ground, large enough to turn off autospc but not
large enough to change dynamic analysis results. This is the most practical
method for supere
30947
ror 7777
70.5
Static Analysis - MATTi - SDR2, biomsg er
For a large job on the hp (hpux), if temperature-dependent material property

exists in the model, then the job may fail in SDR2 with following error
messages:
0
Avoidance: Remove the MATTi entry and define the desired properties at the
appropriate temperature on the MATi entries since for a linear analysis, the
temperature-dependent lookup is only performed once in the beginning of the
run.
30959
U0 is Negative
Nonlinear Analysis - CGAP, PGAP - Possible Wrong Answers when
Use of a gap element (tmax>=0.) with a negative value of U0 when GA and GB are
NOT coincident may lead to wrong answers. Consider two grids on the x-axis
with GA to the left of GB and the CID field blank and U0 specified to a
negative value. Then the gap will always try to push GA to the left and GB to
the right regardless of whether GA comes first or GB comes first in field 4 on
the CGAP entry. Thus, a press fit with the inner radius of the outer disk at GA
and the outer radius of the inner disk at GB would always pull in the wrong
direction when UO is negative.
Avoidance: To make the gap sensitive to the order of GA and GB with U0
negative, the CID entry of field 9 must be specified.
30969
70.7
M 4276, EC 3061, SWM 3002
GPFORCE - SET, GPFORCE - Poor Message, SF
If a GPFORCE request is made for a SET that only contains grid points attached
to rigid elements then the deck will fail in the GPFDR module. The exact
message encountered may vary. The following messages have been encountered:
SYSTEM FATAL MESSAGE 4276, ERROR CODE 3061
or
33
*** SYSTEM WARNING MESSAGE 3002 (GPFDR)
EOF ENCOUNTERED WHILE READING DATA BLOCK SCRATCH (FILE 303) IN
SUBROUTINE GPFDFA
Avoidance: GPFDR does not support rigid elements, request MPCFORCE output
instead.
30976
70.5.1
Online Documentation - Installation
The UNIX installation aborts if you choose an installation option that installs
the V69.X documentation set on the hard disk. The old V69 documentation is
duplicated on this CD only for those customers still running MSC/NASTRAN V69 or
V69.2. If you use MSC/NASTRAN V70, we recommend not installing V69.X
documentation onto your hard disk, since all the documents applicable to V70
are already contained in the Standard installation. If you occasionally need to
refer to V69 documentation, it is best to access it directly from the CD.
If you frequently need V69-specific documentation and you prefer to access it

from the hard disk instead of the CD, please follow the Installation
Instructions on the pink sheet included with the delivery package.
30981
70.5
Online Encyclopedia is Incorrect
Online Encyclopedia - INSTALL.txt on V70
The INSTALL.txt file on the MSC/NASTRAN Version 70 Encyclopedia (MNE) is

incorrect. It is the file for MSC/NASTRAN Version 70 not the MNE.
Avoidance: Either view the INSTALL.htm file using a web browser or request a
printed copy of the file from MSC.
30987
GL
Eigenvalue Analysis - EIGRL, GMINTC, GMIN
TS - Possible Missing Roots, SFM 5407
The Lanczos method of eigenvalue extraction does not work well when interface
elements (GMINTC or GMINTS) are present, roots may be missing in the range.
This may lead to the message:
SYSTEM FATAL MESSAGE 5407 (LNCS1D)
COMPUTED IN A (PARTIAL) INTERVAL
Avoidance: If interface elements are present, the SINV method is recommended.
30995
70.5
SYM,YES - Wrong Answers
Acoustic Analysis - GE on MAT10, PARAM,AC
If GE is specified on the MAT10 entry and PARAM,ACSYM is YES (default) then the
answers will be wrong.
compile gma
alter 'if ( app=\'tranresp\''(2),''
alter 'if ( app=\'tranresp\''(3,-1)
if ( app='tranresp' or soltyp='direct' or modacc>=0 ) then $
alter 'k4hh',''
if ( nok4dd>0 ) then $
if ( acsyml ) then $
add5
ifdd,,,,/mifdd/-1. $
MERGE
isdd,,,mifdd,VAFSE,/idd $
mpyad
k4dd,idd,/k4ddx $
SMPYAD PHDH,K4DDx,PHDH,,,/K4HH/3////1 $
else $
SMPYAD PHDH,K4DD,PHDH,,,/K4HH/3////1 $
endif $
endif $ nok4dd>0
endalter
31000
tors Ignored
GL
Eigenvalue Analysis - READ - Initial Vec
The READ module has provisions for initial vectors as input for the Lanczos
method. These vectors are ignored in the READ module.
Avoidance: Use the REIGL module.
31003
70.5
DMAP - MATMOD Option 12 - Wrong Answers
The form of the column vector output in MATMOD option 12 is 7 (labeled "ROW
VECTOR") and should be 2 (labeled "ROW RECTANG.").
Avoidance: Run MODTRL on the output; for example,
MATMOD I1,I2,I3,,,/O1,O2/12 $
MODTRL O2// / /2 $
31027
70.5
PRTPG, SSG1 - SFM 3003
Miscellaneous - PARAM,CHECKOUT and PARAM,
If PARAM,CHECKOUT,YES and PARAM,PRTPG,YES are specified, and thermal loads are

also applied, then SYSTEM FATAL MESSAGE 3003 will terminate the run in the SSG1
module in the PHASE0 subDMAP.
compile phase0
alter 'ssg1 ',''
SSG1
SLT,BGPDTS,CSTMS,SILS,EST,MPTS,ETT,EDT,MJJX,CASESX,
DIT,,DEQATN,DEQIND,GPSnts,cstm0,scstm/
PJX,PTELEM,NEWSLT/
LUSETS/1//'ALL '/ALTSHAPE/TABS/seid $
endalter
31037
70.5
Superelements - SEMA, SEBNDRY, SECONCT, S
EEXCLD - UFM 4192, UFM 7341, UFM 6787
Two errors relating to checking the input on the SEBNDRY, SECONCT and SEEXCLD
entries have been discovered.
1. The SEIDA field is not verified to be restricted to partitioned
superelements. The failure to check this may cause UFM 4192 to occur in SEMA.
This message may be followed by a SFM 3062 concerning the MAPBTI utility. The
true message is UFM 7341.
2. Conflicts in grid usage between the SECONCT and SEEXCLD is not properly
verified and should have result in UFM 6787.
Avoidance: Follow the rules for the entries delineated in the Quick Reference
Guide.
31051
70.5.2
tation Violation
P-elements - GMSURF, GMCURV, GP0 - Segmen
If you use an EQUATION or Aries BSP for geometry evaluation, in other words, if
"MSCGRP1", or "MSCABS" is specified for the 'group name' field on the GMCURV or
GMSURF entries the job may fail with the following traceback in GP0:
Trap encountered:
Traceback:
Offset 0x000003d4 in procedure get_edge_info
Offset 0x000000e8 in procedure abspnt
Offset 0x000000a8 in procedure ngpont_
Offset
Offset
Offset
Offset
Offset
Offset
0x00000b80
0x00000680
0x000017c8
0x00000cf8
0x000004b0
0x000009a8
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
gp0dx_
gp0dc_
gp0da_
gp0_
xsem02_
mainal
--- End of call chain --Avoidance: There is no avoidance.

31054
2001
SELABLE, SELOC, SENQSET - UWM 9013
Documentation - SEBULK, SECONCT, SEEXCLD,
In the interest of upward compatibility, several of the bulk data entries

implemented in Version 69 will only work if PART superelements (BEGIN SUPER)
exist. These entries are: SEBULK, SECONCT, SEEXCLD, SELABEL, SELOC, SEMPLN,
SENQSET, SETREE.
Avoidance: Do not use these entries unless you have defined PART superelements.
31067
10
70.5.1
Miscellaneous - SFM 4276 EC 7777, signal
It is possible, but not probable, that a file run on the HP9000 using the
analysis.pa2_0 executable may fail with SFM 4276, EC 777, signal 10. This is
due to a kernel error on the PA2 machines.
Avoidance: There are several possible avoidances:
1) run using a different BUFFSIZE or memory
2) try using a different SMEM
3) run using the older 'analysis' executable (this will avoid the error, but is
slower)
4) change bpool
31069
2042
Optimization/Design Sensitivity - DVPREL1, DVPREL2, EMG - UFM
In an optimization analysis, if a negative FID is specified on a DVPREL1/2

entry when PTYPE is not PBEAM, the job may result in the following error
message:
USER FATAL MESSAGE 2042 (EMG )
MISSING MATERIAL TABLE ******** FOR ELEMENT
IIIIIIII
Avoidance: Always use a positive FID on a DVPREL1/2 entry when PTYPE is not
PBEAM.
31070
70.5
Nonlinear Analysis - File indexing error
A file indexing error may cause a nonlinear analysis to fail in the NLTRD2
module.
Avoidance: Increase the bufferpool or smem.
31071
70.5
DMAP - PARAML DTI option - Wrong Answers
If the PARAML module DTI option is used to extract a character string then the
variable contains both the value from the selected word in the record and also
the value in the next word; e.g.,
PARAML TABLE//'DTI'/1/45////S,N,STRING $
the variable STRING will contain the character value from the 45th and 46th
word.
Avoidance: Add the following statement after the PARAML module:
STRING=SUBSTRIN(1,4,STRING) $
31073
70.6
DMAP - MATMOD OPTION(17) - UFM 6968
MATMOD OPTION(17) is designed to read the PARTN case control entry. When PARTN
is present, it sets p4 to 0, properly. When it is not present it sets p4 to
-1, also properly, but also outputs
*** USER FATAL MESSAGE 6968 (MTMD17)
NO GRID OR SCALAR POINTS IN SELECTED SET. PARTITIONING VECTOR N ULL.
However, execution continues.
Avoidance: Ignore the message, or test for the presence of a PARTN command,
and branch over the module if none is present. SSSALTER evds103.f705
demonstrates this avoidance.
31076
70.5
(15) - Failed Convergence
Nonlinear Transient Heat Transfer - PENTA
If there are temperature dependent material properties in the model and you are
running a transient thermal analysis using the PENTA(15) element the run will
fail to converge.
Avoidance: Use lower order PENTA elements.
31083
70.7.2
Superelement - SET, THRU - Extra Output
In a superelement analysis, if output is requested with a SET command using

multiple "thru" ranges, then extra output that is not specified in the range
may appear in the output in addition to the requested output. An example of
the offending SET command is as follows:
SET 100 = 1 THRU 10, 80 THRU 90
DISP = 100
The displacements for grid points that are outside of the range may appear in
addition to output for the above grid points. The answers are, however,
correct.
Avoidance: If the extra output is not desired, then specify the SET explicitly
without using the THRU range. The above
example can be modified as shown below:
SET 100 = 1,2,3,4,5,6,7,8,9,10,
80,81,82,83,84,85,86,87,88,89,90
disp = 100
31096
70.5
P-Elements - GP4 - BIOMSG: ERROR 1044 OCC
URRED IN ROUTINE FILPS2

A P-element analysis with coordinate systems may fail in the module GP4 with
the message:
BIOMSG: ERROR 1044 HAS OCCURRED IN ROUTINE FILPS2 , FILE INDEX (FILEX) = 0
STATUS = 0
Avoidance: Increase the memory request.
31101
P-Elements - PLOT, SDR2 - SFE 4276 EC 211
The nastran plotter does not support the plotting of p-element results. If the
nastran plotter is requested with p-elements, then the job will fail with the
following unclear messages.
BIOMSG: ERROR
0
STATUS =
211 HAS OCCURRED IN ROUTINE BLPK68 , FILE INDEX (FILEX) =

0
0*** SYSTEM FATAL ERROR 4276.BLPK68 ERROR CODE

211 PID= 0
0*** USER INFORMATION MESSAGE: TO OBTAIN A NASTRAN DUMP, RESUBMIT JOB WITH DIAG
44 INSERTED IN THE EXECUTIVE CONTROL SECTION.
Avoidance: If plotting of p-element results is desired, use MSC/PATRAN.
31104
7
70.5
It has been observed on a very large problem, if the matrices are very dense,
then the job may fail in MPYAD. On some machines, the following message may
appear at the bottom of the f06 file.
0
STATUS =
0
On other machines, there is no messages in the f06 file, but the following
messages may appear in the log file:
Trap encountered:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
0x00000024
0x000007bc
0x00000708
0x000004f8
0x0000029c
0x000008f4
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
gino_
mpytim_
mpyad_
dmpyad_
xsem07_
mainal
This is due to an o
31105
70.5
oundary Lead to UFM 6794
Superelements - Duplicate Point ID's on B
When a model with list superelements has part superelements added to it,
duplicate grid points at the boundary of the list superelements are not
allowed, although they were allowed prior to Version 69. This condition leads
to following error message:
DUPLICATE BOUNDARY POINTS DETECTED IN UPSTREAM SUPERELEMENT xxx WHILE SEARCHING
0 AT GRID
yy.
LIST FOLLOWS:
Avoidance: Remove the part superelements, or move one of the offending grid
points.
31114
LL
70.5
Database - DBUNLOAD - Signal 11 Writing L
If the NEUTRAL option is used in DBUNLOAD, the run will fail. The f06 will
likely contain no message, the log file will contain a message of the form:
0
STATUS =
0
Avoidance: Use the BINARY DBUNLOAD.
31118
70.0.5
GPFORCE - GPFDR, TEMP(LOAD) - SFM 6218
If a model has thermal loadings and GPFORCE is requested, the run may terminate
with SFM 6218 in the GPFDR module.
Avoidance: Remove the request for GPFORCE or the thermal loads. Defining SETs
(which omit the GRID points connected to the element mentioned in the message)
for GPFORCE may avoid the problem.
31139
70.5
age and Wrong Answers.
DMAP - SAMEAS Keyword in NDDL - Poor Mess
If SAMEAS,recnam is specified in the NDDL and RECORD=recnam is specified below

SAMEAS,recnam then the following
message is issued but the run is not terminated.
*** SAMEAS CTETRA
NOT FOUND
RECORD=recnam must appear above SAMEAS,recnam.

31141
nswers
Eigenvalue Analysis - EIGRL, very large v2 - Possible Wrong A
If the specified V2 value on the eigrl entry is substantially larger than the
last mode found and the absolute value of V2 is large (e.g., 99999.), then the
eigenvectors may be incorrect. This can lead to incorrect responses in a
subsequent modal response analysis. This error is most likely to occur if
there are massless degrees of freedom and/or large mass in the model and the
above conditions exist. If the model is stable, a possible symptom of this
error is large rotational displacements in the eigenvectors. This error does
not occur with the new Lanczos method which is the default method in Version
70.5.
1. In v70.5, use the new Lanczos (the default method).
2. Based on the last eigenvalue calculated and the sturm sequence
31145
70.5
c Analysis for Base Excitation
Nonlinear Analysis - Restarts into Dynami
A method to perform automatic restarts from static nonlinear analysis (SOL 106)
to linear dynamic analysis (SOLs 103-112) has been avaialble for several
versions. The resart runs have limitations on the type of data that can be
changed. A Technical Application Note (TAN) describing this capability can be
obtained from your MSC Technical Represenative.
31150
70.7
PTEXIT - Incorrect Termination Message
When optexit is set to -4 (output design sensitivity information into an
external file) for a design optimization input file, the task terminates with
an incorrect message:
IIIII.
The correct message should be RUN TERMINATED DUE TO PARAMETER OPTEXIT =

-4.
31154
t Detected
70.5
Superelements - Duplicate Element ID's no
It is a rule of superelement usage that element ids must be unique across all
element types, including structural, rigid, and plot elements. When part and
grid list superelements are in one model, duplicated element ids in the list
superelements are not detected. The results are difficult to predict. Some
models have computed correct results, but it is possible that others would
either give wrong answers or take confusing fatal exits.
Avoidance: An avoidance is to perform a data check run where all of the part
superelements are removed. This will result in a different path through the
code which will identify all illegal duplicate element ids.
31155
UFM 6174
Buckling, Nonlinear Analysis - CBEAM, CQUAD4, ZOFF, OFFSET -
Offsets should not be used for the beam and plate elements in a buckling or
nonlinear analysis. This is a documented limitation. However, the action
taken for the beam and plate element with offsets is inconsistent. In the case
of a beam element, the job terminates with UFM 6174; however, in the case of
the plate element, the job continues without any messages.
31189
4276, EC 7777
70.5.2
Nonlinear Analysis - NLITER, CREEP - SFM
Nonlinear analysis with creep and temperature loads may fail in the NLITER
module with the message:
0*** SYSTEM FATAL ERROR 4276.tbk ERROR CODE
7777 PID=
The traceback will indicate the routine nmcrd. Other machines may produce
NaN's in the output.
Avoidance: The only avoidance is to use Version 70.5.2 where the error has
been fixed.
31209
401
GL
Eigenvalue Analysis - READ, REIGL - SFM 5
If f1 is set on an eigrl entry to avoid computing rigid body modes, and f1 is

much closer to the origin than the first flexible mode's frequency, than SYSTEM
FATAL MESSAGE 5401 may be encountered.
Avoidance: An avoidance is to first run with f1 blank. It should be possible
to compute the flexible modes, as well as the rigid body modyes. On a second
run, set f1 10% below the first flexible mode.
31218
rces of SPC
70.5
GPFORCE - SUBCOM, TEMP(LOAD) - Missing Fo
GPFORCE output for SUBCOMs with thermal loads will be missing the contribution
of the Forces of Single Point Constraint. Standard SUBCASE processing will be
correct.
31225
70.5
4382, Wrong Answers
Elements - PBAR/PBARL, PBEAM/PBEAML - UFM
A job that includes PBARs and PBARLs with the same PID will issue USER FATAL
MESSAGE 4382 and then continue to run. The same behavior is seen with
PBEAM/PBEAML.
*** USER FATAL MESSAGE 4382 (IFP9 )
PBARL AND PBAR IDENTIFICATION
31232
xxx WAS DUPLICATED
Transient Analysis - LOADSET - UWM 4582
If a static pre-load is used in a modal solution, then LOADSET entry may not be
used to define the dynamic loading. This combination will lead to either UWM
4582 show below (if the number of LSEQ entries is not equal to the number of
static subcases) or wrong answers (if the number of LSEQ entries is equal to
the number of static subcases).
USER WARNING
STATIC LOADS
USER WARNING
STATIC LOADS
MESSAGE 4582---,
MATRIX COLUMN
MESSAGE 4582---,
MATRIX COLUMN
LSEQ CARD SID=

2 ( NCOLS=
1
LSEQ CARD SID=
3 ( NCOLS=
1
100 REFERS TO A NON-EXISTENT

)
100 REFERS TO A NON-EXISTENT
)
Avoidance: Do not use the LOADSET command when using static pre-loads.
31237
Online Encyclopedia - Installation
If MSC/NASTRAN Online Encyclopedia (MNE) is installed on a directory path name

that is too long or contains a name with embedded space characters (e.g.
"Program Files"), the documentation browser will not execute properly.
Avoidance: Use the suggested default directory <Disk>:\msc
31249
70.5
Heat Transfer Analysis - SFM 3002 (TAHT)
If a control node is used in a very large heat transfer analysis model, then
the following fatal message may be encountered:

*** SYSTEM FATAL MESSAGE 3002 (TAHT )
EOF ENCOUNTERED WHILE READING DATA BLOCK NEWSLT
SUBROUTINE TAHA
(FILE 101) IN
Avoidance: Run the job with more memory.

31256
70.5
UBCOM - SWM 2092, ERROR 3021
Optimization/Design Sensitivity - SDR2, S
If a design optimization design task contains subcoms and one or more of the
subcom related subcases has no retained responses,
the following fatal message may occur:
SYSTEM WARNING MESSAGE 2092 MODULE = SDR2
SDR2 FINDS A SYMMETRY SEQUENCE LENGTH = xx
AND AN INSUFFICIENT NUMBER OF VECTORS AVAILABLE = yy WHILE ATTEMPTING TO
COMPUTE STRESSES AND FORCES.
ALL FURTHER STRESS AND FORCE COMPUTATION TERMINATED.
BIOMSG: ERROR 3021 HAS OCCURRED IN ROUTINE GREAD , FILE INDEX (FILEX) =
0
STATUS =
0
In a related error, if a subcom contains subseq coefficients that are 0.0 and
the subcase associated with this zero coefficient has no retained responses,
the above fatal message may occur.
Avoidance: Either remove the subcase that has no retained responses or fo
31262
2001
ents are Always Set to Zero.
Documentation - PBEAML - Warping Coeffici
The documentation for the PBEAML does not state that the equivalent PBEAM
created will not contain warping coefficients.
Avoidance: Provide the terms using a PBEAM entry.
31263
70.5
Documentation - QRG - PARAM,ACSYM
The description for the parameter "acsym" in the Quick Reference Guide states
that the parameter only works for coupled fluid-structure analysis in direct
frequency response. This parameter also works for coupled fluid-structure
analysis in modal frequency response.
31266
70.5
Documentation - QRG, DRESP1
The Quick Reference Guide states that the PKNL method can be used in the
evaluation of a DRESP1 with RTYPE=FLUTTER if the
word `PKNL' is placed in the ATTB field of the DRESP1 entry. This is an error,
it should be placed in the PTYPE field of
the DRESP1 entry.
Avoidance: Move PKNL from the ATTB to the PTYPE field.
31271
2001
- Unexpected Answers
Documentation - DECOMP, PARAM,AUTOSPC,NO
If the automatic grid point singularity check is turned off (param,autospc,no),

and there are singularities in the model, then the run may continue and produce
large deflections. The next release of the Quick Reference Guide will warn the
user that if param,autspc,no is set, then the user should take extra caution
analyzing the results in the GRID POINT SINGULARITY TABLE, EPSILON output as
well as all warning messages.
31278
M 4188
70.5
Superelements - DBLOCATE, SERST,SEMI - UF
A superelement job that contains PARAM,SERST,SEMI and attempts to add the bulk
data for a new superelement fails with the message:
USER FATAL MESSAGE 4188 QUAD4 ** REFERENCES UNDEFINED GRID POINT **.
COMPILE IFPS1 nolist noref
alter 60 $
putsys(1,109)
endalter
31304
Answers
Transient Analysis - PARAM,ADSTAT,YES with TEMP(LOAD) - Wrong
In a transient analysis, if "param,adstat,yes" is used to include a preload

effect in the transient analysis data recovery, and the preload is due to
thermal loads, then the transient results will be incorrect.
Avoidance: Use solution 129.
31308
2001
i - Missing Punch Output
Element Strain Energy - ESE(PUNCH), CELAS
In MSC/NASTRAN Version 70, if ESE(PUNCH) is requested and there are CELAS1

elements in the model, then there will be no output in the punch file.
Avoidance: Insert NASTRAN SYSTEM(210)=1 at the top of the MSC/NASTRAN input
file.
31312
Wrong Answers
70.5
Aeroelastic Analysis - CAERO2 - Possible
If the aerodynamic coordinate system is not aligned with the basic coordinate
system, the geometry of CAERO2 slender bodies IN THE BASIC COORDINATE SYSTEM
(BGPA or BGPDT where MODLTYPE=aerostruc) may be incorrect. These data are used
in Spline calculations, so that, if the geometry is affected in such a way as
to shift the location of the body relative to the spline computational
coordinate system, erroneous results may be obtained. The geometry in the
aerodynamic coordinate system is not affected, so the "rigid aerodynamic" data
are not affected--only the spline matrix MAY BE affected.
It has been observed, however, that certain erroneous transformations in
combination with TYPEs of CAERO2 bodies (Z, Y or ZY) can yield identical
answers even if the transformation error has moved the bo
31318
EC 7777
70.5
Composite Analysis - SEDRCVR - SFM 4276,
Large composite models that request large amounts of data recovery may fail on
CRAY systems with SYSTEM FATAL MESSAGE 4276, ERROR CODE 7777 in the SEDRCVR
module.
31322
70.5
- SWM 3001 in SEP1X, Wrong answers
Heat Transfer - RSSCON and PARAM,HEATSTAT
If PARAM,HEATSTAT,YES is specified in SOL 101, then SWM 3001 will be issued by

the SEP1X module. Theis warnings
may safely be ignored unless there are RSSCON elements present, in which case,
wrong answers may result.
compile sestatic
alter 'hsflag\=false'
peid=-1 $
seid=-1 $
endalter
31323
Miscellaneous - SFM 3063, Memory Allocation Error
If a run is submitted using the MEM= option and the memory allocated is above
or near the limit of what is available, it is possible that the run may fail
with SFM 3063 indicating that there is no more dynamic memory available.
Avoidance: Always leave at lease 8mW of memory available for the system when
using the MEM keyword. For example, if you are using a queue which has a 128mW
limit, use a MEM value of 120mW or less.
31327
2001
EXTDR, EXTDROUT, EXTOUT and EXTUNIT
Documentation - CSUPER - Should Reference
The Version 70.5 Quick Reference Guide documentation for the CSUPER entry
should be modified to reference parameters EXTDR, EXTDROUT, EXTOUT and EXTUNIT
in section 6 of the QRG.
31334
2001
REL2 - QRG Not Updated for V70.5
Documentation/Optimization - DVPREL1, DVP
Version 70.5 has simplified the interface for the design of constant section
beams. The revised user interface requires changes
in the Quick Reference Guide's description of the DVPREL1 and DVPREL2 entries.
These changes were not completed in time before the Version 70.5 QRG was sent
to press.
Avoidance: The revised descriptions can be found in Appendix B of the Version
70.5 Release Notes.
31351
70.5
- SFM 4276.GETSTR ERROR CODE 31
Optimization/Design Sensitivity - SUBCOM
The message:
SYSTEM FATAL MESSAGE 4276, GETSTR ERROR CODE 31
may occur if the user employs SUBCOMs and the adjoint sensitivity method is
selected.
Avoidance: Since the adjoint method is not selected when there are p-elements,
an easy avoidance is to tell the module that determines whether the adjoint
method can be selected that there are p-elements in the model. This is done
with the following dmap alter:

compile descon $
alter 'dsad'(1,-1) $
type parm,,logical,n, hold $
hold=pexist $
pexist=true $
alter 'dsad' $
pexist=hold $
31364
Wrong Answers
70.5
Aeroelastic Analysis - AEROS, ZY Bodies -
IF there are zy bodies in the model and the aerodynamic coordinate system is
rotated about the x-axis relative to the aerodynamic reference system, wrong
answers can occur in the stability derivative prints, and hence, the trim
solution.
Avoidance: If ZY bodies are included in the analysis, make sure the aerodynamic
coordinate system and the reference coordinate systems appearing on the AEROS
entry are not rotated relative to each other.
31374
70.5
Elements - PBEAM, IFP - SFM 469
If a PBEAM entry contains an integer in a real field, then the job may fail in
IFP without a meaningful message.
Avoidance: The error was only experienced on CRAY systems. If you have access
to another system then run the job on that system to identify the invalid
entries and correct them.
31381
Miscellaneous - INPUTT2 - UFM 1019, SFM 6551
If the .dat file that is used to read the INPUTT2 file has the same prefix as
the referenced INPUTT2 file--for example, test.dat is the .dat file and
test.op2 is the referenced INPUTT2 file--then depending on the value of
STATUS=x, the job may fail with one of the following error messages:
ASSIGN INPUTT2='test.op2',UNIT=12
USER FATAL MESSAGE 1019 (OPNPFL)
FORTRAN UNIT OPEN ERROR
IOSTAT =
6, No such file or directory(errno=2)
LOGICAL = INPUTT2 FILE = test.op2
0
FATAL ERROR
0
NO. FORTRAN RECORDS READ
This error is caused because of the versioning code (old=yes, old=no) in the
nastran command processor. Without
possibly extensive logic changes, there is no workaround other than making the
inputt2 file name something other than
<jodname>.op2. For example, if the name is created as "<jid>.inp2" the job
will run properly. The status has been changed
from "ERROR" to "LIMITATION".

31392
70.5
Incompatible Matrix Multiply
SSSALTERS - GPFORCE, trncompa - SFM 5423,
If GPFORCE output is requested when using the trncompa alter, then the job may
*** SYSTEM FATAL MESSAGE 5423 (DMPYAD)
ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES
COLS ROWS FORM
TYPE NZWD DENS
2
12
18 7792
TRAILER FOR QG2
IS
101
21
739
TRAILER FOR UHDISP
IS
102
21
11
TRAILER FOR (NONE) IS
77
0
TRANSPOSE FLAG IS 0
0FATAL ERROR
1. Add "param,ddrmm,-1" to the input file
or
2. Replace the following dmap statement
mpya
31399
2001
SEL - Incorrect Decimal Equivalent
Documentation - PARAM,USETPRT, PARAM,USET
the Version 70 and 70.5 Quick Reference guide parameter section indicates that
the decimal equivalent of set U6 (to be specified on PARAM,USETSEL for
PARAM,USETPRT) is 76108864, it should be 67108864.
31422
T - UWM 979
2001
Documentation/QRG - XYPLOT, PARAM,CURVPLO
If XYPLOT commands are specified for plotting in transient or frequency

response analysis with grid points on the abscissa, as defined under
PARAM,CURVPLOT, then USER WARNING MESSAGE 979 is issued and no plots are
output. PARAM,CURVPLOT is applicable only in static and normal modes
analysis; i.e., SOLs 1, 3, 5, 14, 15, 16, 101, 103, 105, 106, 114, 115, 144,
and 200 even though Table 1 of Section 6 in the Quick Reference Guide indicates
that it is applicable in all the structured solution sequences. Table 2 is
documented correctly for CURVPLOT. Section 13.3.6 of the Reference Manual is
also documented incorrectly with regards to solution sequence applicability.
31423
03
Interface Elements - GMBNDC - GMCURV Option Results in UFM 64
The GMCURV option on the GMBNDC entry may incorrectly result in the following
fatal message:
*** USER FATAL MESSAGE 6403 (CIFCRV)
THE GMBNDC ID =
2 REFERENCED BY GMINTC
CONTINUOUS AT GRID ID=
1.
ID =
5001 IS NOT
Avoidance: The exact cause of the problem is not yet known. The FEEDGE and
GRID options may be used instead.
31427
70.5
5) exception encountered
Miscellaneous - Access violation (C000000
When there is an illegal bulk data entry "0" as shown below, then the job may
fail in various ways. NT systems have failed with the message "Access
violation (C0000005) exception encountered"
0
4602
4603
4606
4607
4604
4605
Avoidance: Correct the offending bulk data entries.

31430
2001
GPWG - QRG Unclear
Documentation/Elements - CMASS1, CMASS2,
The CMASSi elements have provisions for defining a pair of DOFs, although they
are often used for point masses. To input a point mass, define only a single
DOF. When two DOFs are used a coupled mass matrix is produced. If not input
correctly it may cause internal constraints. No checks are made for internal
constraints in such elements. The following remarks should be added to the
CMASS1 and CMASS2 Quick Reference Guide Descriptions:
7. Scalar elements input coupled mass matrices when the second pair of fields
is entered. When uncoupled point masses are desired input only the first pair
of fields. When a coupled mass matrix is requested the submatrix added has M
on the diagonal, and -M on the off-diagonal. The element is not checked for
internal constraints, which is the user's
31436
ocumentation
2001
Documentation - PBARL, PBEAML - Missing D
There are undocumented limits in the use of the beam library.
For the PBEAML:
The beam can have no more than 14 dimensions per station.

The total number of dimensions at all stations must be less than 200.
The transfer of data with the beam server is limited to 4000 words.
None of these limits are exceeded with the MSC beam library, but a user defined
beam library could. The data transfer limit would most likely be exceeded when
the number of dimensions for a PBARL exceeds 235 (4000 / 17 properties per
bar).
There is a further limit that the NSM values input on the PBARL and PBEAML must
be >= 0. No other property types have this limit.
31447
70.5
Aeroelastic Analysis - EPOINT, SOL 145, M
ultiple Eigenvalue Subcases - UFM 1126
In aeroelastic flutter analysis (SOL 145 only) UFM 1126 as shown below is
issued when there are multiple normal mode boundary conditions and the model
contains epoints.
UMERGE1 IS ATTEMPTING TO OUTPUT DATABLOCK NAME = GMD which already exists

compile sefluttr
alter 1
file gmd=save,ovrwrt/god=save,ovrwrt/k4dd=save,ovrwrt $
endalter
31452
P-Elements - GMINTC and GMINTS - Non-Zero Rigid Body Stresses
Models that connect curved surfaces with the GMINTC and GMINTS interface
elements may experience non-zero stresses due to rigid body motion. These
non-zero stresses are caused by the differences in cubic geometry on the
dissimilar mesh.
Straight interfaces have no such problem, since the geometry is identical.
Avoidance: The tolerance TOL on the PINTC and PINTS property entries will
generate a warning message for differing geometry, and may be set lower to be
more conservative.
31461
Documentation
2001
Documentation - PARAM,NQSET - Missing QRG
For part superelements, generalized coordinates can be defined automatically by

senqset entries, as documented in the qrg, or by the param, nqset entry. The
param method was introduced in Version 69 but has yet to be documented. The
documentation follows:
NQSET
Default=0
If NQSET>0, and the PARAM entry is in case control, all part superelements that
do not contain qset entries, or are not referenced by senqset entries in the
main bulk data deck, have NQSET generalized coordinates assigned to them.
These qset variables are functionally equivalent to those generated by senqset
entries.
31463
70.5
ATICS - UFM 9058
Optimization/Design Sensitivity - ANAL=ST
In solution 200 with ANALYSIS=STATICS, if the static loads are null then UFM
9058 will be issued during the sensitivity analysis:
THE SOLUTION FOR THE RESIDUAL STRUCTURE DOES NOT EXIST
compile pslgdv
alter 'call sela1'(,-1)
dbstatus egxp//s,n,noegxp $
if ( noegxp<=0 ) matgen ,/egxp/7/lusets/nopgs $
endalter
31465
- Record 16
2005.5
Documentation - DMAP Prog. Guide, OUTPUT2
The DMAP Programmer's Guide incorrectly states that for matrices Record 16
(OP2NEW=0) is not equal to zero. Record 16 is always zero for both matrices and
tables. The same error exists for OP2NEW=1 in Record 20.
31469
GL
Superelements - SECONCT - UFM 4156
If PART superelements are used in a model and manual connections are specified
through the SECONCT entry and there are coincident exterior points in the
PARTs, the run will fail when attempting to connect the reduced matrices with
UFM 4156 indicating an incorrect matrix trailer as shown below:
USER FATAL ERROR 4156--- DIMENSIONS OR TYPE OF DATA BLOCK XAAV
,
SUPERELEMENT
xx
TRAILER=( 1278 1278
6
2
58
52) ARE INCONSISTENT WITH
SUPERELEMENT MAP.
FATAL ERROR
Avoidance: Coincident points are not supported when connecting PART
superelements. It is possible that the error could be avoided by only
connecting one of the points to the other PARTs in the model and using an RBAR
or CBUSH to connect the coincident points in the PART. If the automatic
connection logi
31472
2001
P-Elements - PBEAM - UFM 3005 (SNGERR)
BEAM p-elements fail in an adaptive loop if J(A)>0 is not specified on the

PBEAM entry. The following fatal message is issued.
*** USER FATAL MESSAGE 3005 (SNGERR)
ATTEMPT TO OPERATE ON THE SINGULAR MATRIX D IN SUBROUTINE ADPF1D
0FATAL ERROR
Avoidance: Specify J(A)>0 in the 8th field of the PBEAM entry.
31473
2001
not Applicable
Documentation - CVISC - Stress Plot Codes
The Appendix A in the Quick Reference Guide documents stress plot codes for the
CVISC element. The CVISC element only supports force output.
31475
70.6
- Multi-Level Superelments - UFM 9058
"USER FATAL MESSAGE 9058" may appear in a superelement sensitivity analysis if
the model contains multilevel superelements and an upstream superelement
contains a design model but more than one of its downstream superelements does
not.
Avoidance: Place dummy design information in downstream superelements.
31479
70.5
6497 on SGI and SUN Machines
P-Elements - TETRA, GMLOAD, GMCORD - UFM
TETRA p-elements with GMLOAD and GMCORD may lead to the following fatal
message:
*** USER FATAL MESSAGE 6497 (TRNJFD)
THE POINT AT: X= 0.346875D+03 Y= 0.500000D+03 Z=-0.203698D+03, IN THE
BASIC COORDINATE SYSTEM
COULD NOT BE LOCATED ON FEFACE ID=
1.
*** USER FATAL MESSAGE 2025 MODULE = SSG1
UNDEFINED COORDINATE SYSTEM
1
0FATAL ERROR
Avoidance: Either:
- mesh with HEXA elements.
- use a system other than GMCORD with GMLOAD
- use PLOAD4 instead of GMLOAD
31488
r SUBTITLE
70.5
ESTIMATE - May Ignore Entry After TITLE o
Under certain circumstances, ESTIMATE will ignore the entry following a TITLE,
SUBTITLE, or LABEL entry. This may cause ESTIMATE to ignore a METHOD, MPC,
SPC, STRAIN, or STRESS CC entry if it immediately follows a TITLE, SUBTITLE, or
LABEL that contains a comma "," character.
Avoidance: One of the following avoidances may be used:
1) Enter a comment following the TITLE, SUBTITLE, or LABEL.
or
2) Specify the missing METHOD, MPC, or SPC entry on the command line.
31498
2001.0.9
357, plus others
Restart - DBALL offline - UFM 1127, SFM 6
If scr=no is specified in a cold start, but the data base path and name is
not assigned by the dbs keyword or the ASSIGN statement, then a restart run in
a different directory with only an ASSIGN statement for the MASTER dbset, and
not DBALL, will fail with UFM 1127. This problem does not occur if the dbs
keyword specifies the location of the database on the command line. Some of
the possible error messages are shown below:
DMAP MODULE PLTSET IS ATTEMPTING TO ACCESS DATA BLOCK
GEOM2
WHICH IS ON AN UNAVAILABLE DBSET
*** SYSTEM WARNING MESSAGE 3001 (SEP1X )
THE INPUT DATA BLOCK NAMED GEOM1QS AT POSITION
103 NAME =
2 DOES NOT EXIST.
*** SYSTEM FATAL MESSAGE 6357 (SEP1A)

NO GRID POINTS FOU
31537
rrect Default
2001
Documentation - QRG, PARAM,AUTOSPC - Inco
Starting with Version 69, the QRG states that the default for PARAM,AUTOSPC is
NO in SOL's 1 thru 12, when in fact it is YES for all of these solutions except
SOL 4.
31540
in XDB
69.1
Postprocessing - Incorrect Approach Code
Solution 1 in Version 69 will incorrectly set the approach code to 4 in the xdb
file. The correct value is 1.
Avoidance: Either insert the following DMAP alter or use solution 101:
compile sol1
alter 'dbc '(2),''
DBC CASECC,,,,,,,,,,,,,,,,,,,//
'CASECC'////////////////////
-1/DBCPATH/S,N,CP/soltype//V,Y,GEOMU/V,Y,LOADU/V,Y,POSTU/
V,Y,DBCDIAG/V,Y,DBCCONV/V,Y,DBCOVWRT $
endalter
31568
70.7
Restarts - DBLOC - UFM 723 (LCDEFW)
The WHERE clause on the DBLOC command does not work consistantly with the
VERSION and PROJECT qualifaiers with the DBDICT entry.
The following
statement:
DBLOC DATABLK=(QKKS) WHERE (VERSION=* AND PROJECT=*) LOGICAL=QTODB5
caused the diagnostic message:
0*** USER FATAL MESSAGE 723 (LCDEFW)
PROJECT ID EXPRESSION HAS AN UNBALANCED NUMBER OF SINGLE QUOTES
Other variations of the WHERE clause with these qualifiers may cause data to
not be found.
31578
nite Loop
Nonlinear Analysis - Load Factor Greater than 1.0 causes Infi
In a nonlinear analysis, on some instances, the load factor tolerances may be

in error. When this occurs the value of the load factor exceeds 1.0 and the
solution may enter an infinite loop or produce some other fatal message later
on.
The problem is identified when one of the load factors > 1.0
Avoidance: On the NLPARM entry increase the NINC field by 1 and restart into
the offending subcase. This will change the tolerance calculation.
31582
2001
Miscellaneous - PARAM,DESPCH1 - Punch out
put with small field format not allwed
Bulk Data paramter DESPCH1 can be used to request the format type for the
punched output. A negative DESPCH1 requests the small field format while the
positive DESPCH1 requests the large field format. However, when an optimization
deck specifies the negative DESPCH1 and also specifies the second parameter
DESPCH>0, the small field format is ignored.
Avoidance: Apply the dmap alter below:
compile nddl=nddl
include 'nddl.dat' $ where the nddl.dat is the modified nddl list
that includes the following two lines:
param,despch =0, type=I, PATH=GEOM,LOCATION=master
param,despch1 =6, type=I, PATH=GEOM,LOCATION=master
compile desopt
alter 'despch'
type parm,,i,y,despch1
compi
31583
305
Acoustic Analysis - METHOD(STRUCTURE), SDFREQ - UFM 4276 EC 1
In modal frequency response analysis, solution 111, with fluids, if the

METHOD(STRUCTURE)=n case control command is missing, the following error will
occur:
USER INFORMATION MESSAGE 5222 (SQFREQ)

COUPLED SOLUTION ALGORITHM USED.
BIOMSG: ERROR 1305 HAS OCCURRED IN ROUTINE ENDPUT , FILE INDEX (FILEX) =
0
STATUS =
0
INDEX
2
3
4
6
7
8
LOGNAME
OBJSCR
DBA
MAST
SCRA
SCRU
MASTER
31590
ar restart run
STREAM_ID
00000002
00000003
00000004
00000006
00000007
00000008
NAME
/work/30314_42.OBJSCR
/work/fnd1.dba
/work/fnd2.mast
/home/no4/emc/emc3fnd/fnd5.scra
/tmp/fnd6.scru
Nonlinear Analysis - Missing Intermediate output on a nonline
If additional subcases are added in a restart of a solution 106 nonlinear job

then there may be missing intermediate output.
Avoidance: The problems is under investigation. Other than performing the job
as a cold start there is no avoidance.
31591
70.5.2
OMU,0 - NASTRAN Stops in DBC Module
Postprocessing - DBC, PARAM,POST PARAM,GE
If PARAM,GEOMU,0 is used to suppress the writing of geometry into XDB (i.e.

PARAM,0) is in the deck, then the job will stop without message in the DBC
module. The log file may contain a message of the form:
1525-001 The READ statement on the file ./s31591.xdb cannot be completed
because the end of the file was reached. The program will stop.
31608
ed
File Management Section - ASSIGN, DELETE - DBALL is not Delet
The fms statement ASSIGN includes the DELETE qualifier, which specifies that an
existing data base at the start of a run should be deleted, and replaced with a
new version. If this qualifier is applied against a MASTER database, it
properly deletes the MASTER database. However, MASTERs point to one or more
data base members, such as DBALL. The index for these databases are stored on
MASTER, so they are useless after MASTER is deleted and they too should be
deleted but are not.
Aoidance: using assign with delete option applying to all dbsets of the
database.
31622
70.5.1
egmentation Error
Heat Transfer Analysis - CHBDYE, TA1A - S
Heat Transfer models with CHBDYE elements may fail with a segmentation error.
31636
2004
- UFM 6293 incorrectly issued
Optimization/Design Sensitivity - DESSUB
If an attempt to place limits on a global response (such as weight) is applied

using a DESSUB command, the program will incorrectly issue UFM 6293.
Avoidance: Global responses (such as WEIGHT) may only be constrained using the
DESGLB command. They may not be constrained by the DESSUB command.
31655
70.5.2
SFM 4276, EC 3002, EC 1409, EC 31
The message:
SYSTEM FATAL MESSAGE 4276, ERROR CODE 1409
can occur in the DOM6 or DOM9 module if there are DRESP2 responses and two or
more of the DRESP1 id's invoked by a single DRESP2 are duplicates.
Avoidance: Remove the duplicate DRESP1 id's from the DRESP2 entry. It is most
likely not the user intent to have duplicated the id's, but it will be
permitted once this error is corrected.
31662
p
70.7
Miscellaneous - DBVIEW - Infinite CPU Loo
If the view name and the datablock name are identical on the DBVIEW statement,
and the datablock is local scratch, then an
infinite CPU loop will occur in GNPREP when the view name is used as input to a
module. The following input deck demonstrates the
problem:
sol AERBG
diag 8,24$
compile AERBG
$
SUBDMAP AERBG
dbview uset = uset ( where peid=1)
tabprt uset
END $
$
CEND
BEGIN BULK
ENDDATA
31664
70.7
4, No Fatal Message
Rigid Elements - RBE3, GP4 - EXIT from GP
The um fields of the RBE3 element contain grid point and component data. A
GID-component pair may appear only once in the um fields. When a pair appears
more than once, the gp4 modlule takes an exit without producing any
diagnostics.
The most likely clue that this has happened is to inspect the .f04 file. If
the last several modules to run are gp4, append, bcdr,prstum, and exit, a bad
rbe3 may be the cause.
Avoidance: An avoidance is to check the um fields of all rbe3 entries.
31665
P-Elements - MATGPR - GRIDN Labels Incorrect
When using the MATGPR module to print a matrix for p-elements, the components
of the higher-order degrees of freedom represented by the GRIDNs are incorrect.
They are labeled T1,T2,T3,R1,R2,R3 followed by garbage, since the number of

components may be much higher than 6. They should simply be labeled with
integers.
31668
Wrong Answers
70.5.1
The Version 70.5 Release Notes state that it is now possible to design
properties for the constant cross section PBEAM by
referencing the END A fields only on the PBEAM bulk data entry. (Previously,
one had to reference the EPT and explicitly
design END A and END B). The implementation of this new capability was
incomplete in that it does not change the DVPREL2 invoked designed properties
at END B. As a consequence, sensitivities of END B responses are most likely
incorrect. If an optimization
task in undertaken with END B responses, the redesigned structure will provide
incorrect analysis results at END B and lead to invalid designs.
Avoidance: Either do not use the new feature or do not ask for data recovery at
END B in the design task.
31671
2001
ssing, Excessive Output
Documentation - MODES - Inefficient Proce
The MODES case control command may be used in all solution sequences as a
subcase replicator. The most common and obvious use is in eigenvalue solutions
and is demonstrated under the Quick Reference Guide's description of this
entry. This command may be of no use in other solution sequences such as
transient response and may cause the data recovery processing to be repeated
and printed multiple times.
31674
2001
Documentation - PARAM, CB1, CB2, CK1, CK2
, CK3, CP1, CP2, CM1, CM2 - UFM 6011
Parameters CB1, CB2, CK1, CK2, CK3, CP1, CP2, CM1, and CM2 are incorrectly
indicated to be real parameters with a default of 1.0 when
they are complex parameters with a default of (1.0,0.).
Avoidance: If you use these parameters, define both the real and imaginary
terms.
31686
- UFM 316
70.7
Elements - CQUAD4, CQUAD8, CTRIA3, CTRIA6
The MCID field on the CQUAD4, CQUAD8, CTRIA3 and CTRIA6 entries cannot be
greater than 999999 or else UFM 316 will be generated. However, on the PSOLID
and CGAP, coordinate system IDs > 999999 are accepted.
31689
2004
Nonlinear Static Analysis - PGAP - Unnec
essary Restriction for Non-Adaptive Gap
The adaptive gap element requires that MU2 <= MU1; however, this restriction is
unnecessarily imposed on the non-adaptive gap element.
Avoidance:
vector.
31694
swers
This limitation can be avoided by proper choice of the orientation
70.7
Dynamics - SOLs 103-112, PARAM - Wrong An
In SOLs 103, 105, and 107 through 112, if the Case Control section contains
multiple dynamic subcases or a static subcase for differential stiffness, then
PARAM commands specified in the dynamic subcase(s) are ignored.
Avoidance: Specify PARAMs in the Bulk Data section or insert the following
DMAP alter:
compile sekdr
alter 'pvt ',''
pvt
pvts,casebuck/pvtxxx $
endalter
31703
6944
70.5.1
Aeroelastic Analysis - AELIST, ADG - UFM
If an AELIST set is referenced by more than one AESURF entry, then the job will
USER FATAL MESSAGE 6944 (ADG)
AELIST ENTRY ID = xxx THAT IS REFERENCED ON AESURF ENTRY ID =yyy DOES NOT
EXIST.
The id's specified in the message are also scrambled in that aesurf id's are
given in the aelist position and vice versa.
Avoidance: Create another AELIST entry with a unique ID but with the same set
of aero boxes.
31717
70.7
DMAP - SOLVE - Inefficient Processing
The internal resequencing option for decomposition in the SOLVE module is not
performed. This may lead to inefficient processing.
Avoidance: Use the DCMP and FBS modules.
31721
t Problems
70.5.1
Miscellaneous - Missing Release Guide Tes
The MSC/NASTRAN Version 70.5 Release Guide as well as the README file in the
Version 70.5 relnotes directory refer to the problems ar29be01.dat,
ar29src1.dat, tpsnp.dat, and tpsp.dat. These problems are missing on the UNIX
R0 cd.
Avoidance: The input decks are listed below separated by $fname.
$ ar29be01.dat
$
$*********************************************
$ Test of nonlinear shock absorber
$ under large deformation
$********************************************
TIME 1000
SOL 129
$********************************************
CEND
$
TITLE = Shock absorber and spring loaded with sine pulse
LABEL = CBUSH1D with SHOCKA option and SPRING option
ECHO = SORT
SET 1= 1,2
DISP(SORT2,PLOT) = 1
SET 2 = 1, 100
STRESS(SORT2,PLOT) = 2
OLOAD(SORT2,PLOT) = 1
$
SPC = 1
$
31724
Wrong Answers
2004
Optimization/Design Sensitivity - OFREQ -
If sensitivity is requested in a frequency response analysis and there is an

OFREQ request to limit output, the sensitivity results will be in error.
Avoidance: Remove the OFREQ request from case control. In Version 2003 this
error is considered fixed by simply ignoring the OFREQ Case Control command in
Solution 200 during DSA phase of the job.
31738
70.7
- Possible Infinite Loop
In optimization analysis, if none of the connectivity cards reference existing

property entries and a dresp1 selects an existing property card for an element
response, it is possible to enter into an infinite loop in subroutine DOMLOC of
module DOPR3.
Avoidance: Correct the missing property entries or the incorrect connectivity
references.
31751
s
2001
Nonlinear Analysis - CBUSH - Wrong Answer
This error points out two problems:

1. A code problem where the CBUSH has a secant logic for load deflection which
can not properly track the curve.
2. A user problem with use of the field 9 CID. The CID sets the element axes in
cement. The element then becomes sensitive to the order of the grids when
computing an internal force. The relation is Ke * (Ub - Ua) If Ua > Ub a
compressive force will result. This is unlike the G0 option which flips the
element axies if the grids are interchanged.
31757
70.5.1
Transient Analysis - TRLG - UFM 2025
The following fatal message may be incorrectly encountered in the TRLG module:
*** USER FATAL MESSAGE 2025 (TRLG)
UNDEFINED COORDINATE SYSTEM ID = 1065353216
0FATAL ERROR
Avoidance: The error exists in Version 69.1, 70. and 70.5. The best avoidance
is to request MSC/NASTRAN Version 70.5.1. The correction of this error has
been integrated in to Version 70.0.5 for NASTRAN for Windows. The fixed version
remains at 70.5.1 since this error was never an issue for the prior release of
NASTRAN for Windows which was based on Version 68.2.
31759
2001
Documentation - RELEASE - UFM 6755
The documentation for the RELEASE entry does not state that it is not supported
if the model has PART superelements. If a model containing PART superelements

contains a RELEASE entry, the program will issue UFM 6755 and terminate the run.
31763
70.5.1
340 (LNNHERR), LNNDRVD
Eigenvalue Analysis - EIGRL, READ - SFM 7
In the rare case that Lanczos shifts directly on a mode, the new lanczos shift
logic in MSC/NASTRAN Version 70.5 may encounter an error which may cause the
job to fail with messages similar to those below instead of performing a new
shift.
*** USER WARNING MESSAGE 4698 (DCMPD)
STATISTICS FOR DECOMPOSITION OF MATRIX (NONE) .
*** SYSTEM FATAL MESSAGE 7340 (LNNHERR)
process error reported by subroutine LNNP2CD
see LNNP2CD abstract (ier = -729)
warning reported by subroutine LNNDRVD
see LNNDRVD abstract (ier = 729)
Avoidance: The simplest, most guaranteed avoidan
31769
70.5
Missing from Index
Online Encyclopedia - RANDPS - RANDPS is
The RANDPS index is missing from the Table of Content section of the online
documentation. The actual RANDPS entry is in the online CD.
Avoidance: Click on the RANDT1 button and scroll one page up to find the RANDPS
entry.
31775
70.5.1
BLE library error
Utilities - PLOTPS - Fail with UNRECOVERA
On all Cray platforms, PLOTPS will fail with the following error message
lib-1171 plotps: UNRECOVERABLE library error
An output list item is incompatible with its data edit-descriptor.
Encountered during a sequential formatted WRITE to an internal file (character
variable)
Error initiated at line 647 in routine '_wrfmt'.
Abort
Beginning of Traceback:
Interrupt at address 74547a in routine '_lwp_killm'.
Called from line 16 (address 75571a) in routine 'raise'.
Called from line 92 (address 15347c) in routine 'abort'.
Called from line 59 (address 352112a) in routine '_ferr'.
Called from line 647 (address 424651c) in routine '_wrfmt'.
Called from line 232 (address 343053c) in routine '_xfer_iolist'.
Called from line 396 (address 423231c) in routine '_FWF'.
31778
ees of Freedom
Nonlinear Analysis - DECOMP - UWM 4698 Does not Identify Degr
When running sparse decomposition in solution 106, the message:
USER WARNING MESSAGE 4698, STATISTICS FOR DECOMPOSITION OF MATRIX ***.

THE FOLLOWING DEGREES OF FREEDOM HAVE FACTOR DIAGONAL RATIOS GREATER THAN ***
OR HAVE NEGATIVE TERMS ON THE FACTOR DIAGONAL"
does not list the grids/dofs corresponding to the negative diagonal terms.
Avoidance: Run the job with SPARSE=1 to identify the negative diagonal terms.
31784
70.5.2
ing CBUSH STRESS/FORCE Output
Nonlinear Analysis - CBUSH, PBUSHT - Miss
In a SOL 106 run, if a CBUSH element is present using the nonlinear

force-deflection feature (KN on the PBUSHT entry) and there is no other
nonlinear material present, then the STRESS/FORCE output for the CBUSH element
may be missing. This has been observed on some, but not all problems.
Avoidance: Add param,lgdisp,1 to the input file. A safer avoidance would be to
define a dummy rod or quad4 element with
an associated MATS1 entry
31787
Wrong Answers
70.5.1
Heat transfer Analysis - CHBDYG, CHBDYP -
If the user has nonunique CHBDYP element

element ID, the NASTRAN program does not
used in the convection calculation. The
non-unique CHBDYP and CHBDYG id's in the
ID that are the same as a CHBDYG

know which CHBDYx element ID should be
fix will allow the program to flag the
gp2 module.
Avoidance: Change the conflicting CHBDYP and CHBDYG element id's so that they
are unique.
31796
s
70.5.1
P-Elements - ADAPT, EPSTOL - Wrong Answer
When a shell or beam p-element is omitted from the error analysis because of
the EPSTOL parameter on the ADAPT bulk data entry, all subsequent shell and
beam p-elements will also be omitted.
Avoidance: An avoidance is to set the EPSTOL parameter to zero on the ADAPT
entry so that no elements are omitted.
31801
70.5.1
P-Elements - ADAPT, EPSTOL - Poor Answers
If a shell or beam p-element has a low stress at one grid, the element may be
omitted from the error analysis because of the EPSTOL parameter on the ADAPT
bulk data entry. The element should not be omitted unless all grids have a low
stress.
Avoidance: An avoidance is to set the EPSTOL parameter to zero on the ADAPT
entry so that no elements are omitted.
31804
70.5.2
Thermal Loads - PSHELL - Wrong Stresses
If the T1 and T2 fields are specified on the TEMPP1 entry and the MID1 field on
the PSHELL record is left blank, then the calculated element stress will be
wrong.
Avoidance: Specify the MID1 field on the PSHELL entry.
31814
70.5.1
age 1 - Memory Allocation Error
Matrix Methods - MPYAD Method 1 NT/T Stor
Runs on aix platforms with large multiply-adds, in

1 is selected, may unexpectedly run out of virtual
error depends on such variables as the size of the
system paging space available on the machine. When
terminates with the following error message:
which Method 1 NT/T Storage

memory. Encountering the
problem and the amount of
the error occurs, the run
SYSTEM ERROR MESSAGE (gotsig33):

SYSTEM RAN OUT OF PAGING SPACE.
Avoidance: Note that when this error is encountered, increasing the memory
allocation with the NASTRAN mem parameter will not generally avoid the problem.
The avoidance is to increase the system paging space.
31817
ocessing
70.5.2
Dynamics - PARAM,VMOPT,1 - Inefficient Pr
If PARAM,VMOPT,1 is specified then the MGEN module is executed twice. Also, if

component modes are not requested then the fluid mass should not be computed at
the g-set level; in other words, PARAM,VMOPT,1 should be ignored.
compile semrm
alter 'mgen '(,-1)
if ( vmopt=0 or not((DYNRED=-1 or METHOD=-1) and noqset>-1) ) then $
alter 'vmopt'(2),''
alter 'call mgen1'(,1)
endif $ NOMGEN>-1
alter 'PURGEX \/mvaa',''
dbstatus mej//s,n,nomej $
if ( nomej>0 ) then $
alter 'mpyad meo'(,-1)
CALL SEGOA uset,GOT,GOQ/GOA/NOOSET/NOQSET/NOTSET $
alter 'mpyad meo'(,1)
else $
purgex /mea,,,,/-1 $
endif $ nomej>0
alter 'ENDIF \$ NOMGEN',''
compile semg
alter 'vmopt'(2),''
type db uset0 $
PARAML CASES//'DTI'/-1/150//S,N,DYNR
31832
t
2004
Miscellaneous - PARAM,USETPRT - Wrong Sor
If there is a user defined degree of freedom set (USET, USET1), and row sorting
is selected (PARAM,USETPRT,0 or 10), then the uset print tables will not be
sorted in ascending order, but will be in a random order.
Avoidance: Select 'Column'(val=1 or 11) or 'Row and Column'(val=2 or 12) sort
on the PARAM,USETPRT entry.
31842
70.7
Miscellaneous - INCLUDE, SOL - UFM 443
If the SOL executive statement points to a user-written dmap, and the dmap is
inserted in front of the SOL statement using the include command, then the job
may fail with the following messages on some machine.

*** USER FATAL MESSAGE 443 (DBALOC)
THE SUBDMAP MAIN
REFERENCED BY THE SOL, LINK OR COMPILE STATEMENT WAS NOT
FOUND ON THE MSCOBJ DBSET.
Avoidance: Either move the SOL statement before the include command or insert
the dmap into the actual file instead of using the include command.
31844
70.7
ER - Slow Convergence
Aeroelastic Anaslysis - AEKX, AESMETH=IT
When using AESMETH=ITER or AESMETH=AUTO in SOL 144 and the displacement and
force splines are not the transpose of one another (e.g., if the USAGE field is
not BOTH on all SPLINEi entries), the iterative aeroelastic solution may
converge slowly or even fail to converge. This is caused by an error in the
AEKX subdmap in which it was mistakenly assumed that the splines were
transposes of one another (as they had been required to be prior to Version
70.5). If the force and displacement splines are transposes of one another,
this problem does not occur.
Avoidance: An avoidance is to use identical FORCE and DISP splines (which was
a requirement prior to Version 70.5). Another avoidance is to apply the
following alter to Version 70.5:
compile aekx list noref $
$ fix errors due to mqg' an
31849
70.5.1
pplication Error
Submittal - nastran.ini on Windows NT - A
If the last line of the nastran.ini file (found in the $MSC_BASE\msc705\<arch>\

directory) is not terminated, then the NASTRAN command will fail with the
following message generated by Windows:
An application error has occured and an application error log is being
generated
nastran.exe
Exception: access violation (0xc0000005), Address: 0x0041c608
This error is easily created with Notepad.
Note that the ini file is now only used to set a very small number of keywords,
e.g., msc_base, and version. In most other cases the rcf files are now used.
If other keywords are set in the nastran.ini file they are ignored.
Avoidance: Put an end-of-line at the end of the last line in the nastran.ini
file.
31855
2004
bly Large Damping
Documentation - CGAP, PARAM,G - Unreasona
With penalty CGAP (default), W3 damping can become excessive because of large
CGAP penalty stiffness. This is a limitation that should be documented under
the CGAP entry.
Avoidance: When gap elements are used in nonlinear transient analysis,
param,g damping should be avoided. Damping should be specified on the MATi
entries and PARAM,W4 set.
31884
70.7
ARAM, DSNOKD - UFM 5423
Optimization/Design Sensitivity - ADD5, P
The message "USER FATAL MESSAGE 5423" indicating an incompatible matrix

multiple is output from the ADD5 module in SOL 200 when PARAM DSNOKD is
non-zero and there are multiple subcases that have active buckling design
constraints.
Avoidance: Set DSNOKD to 0.0 or restrict the buckling design task to a single
subcase.
31885
70.7
Rigid Elements - RBE3 - UWM 7343
Diagnostic USER WARNING MESSAGE 7343 for the RBE3 element appears, properly,
when an RBE3 element has inadequate connectivity and is approaching
singularity. It may also appear for a stable element when there is a large
distance between the grid points to which it attaches. This is because the
test used to measure singularity is not independent of the units of measure of
the model. A test model of an rbe3 connecting 4 grid points in a square
pattern to a point at their center does not cause the message when the points
are 100 units apart, but does cause the message when they are 10,000 units
apart on certain computer types.
Avoidance: The criterion used to print this message is that the computational
zero ("error value") associated with its use is greater than 1.E-10. This
conserva
31890
70.5.2
illegal RBE3 found per run
Rigid Elemets - RBE3 - UFM 2038, Only one
All bad rigid elements should be found and identified in a single execution.
However, the RBE3 is an exception. It causes the program to stop after the
first bad element is found.
This is a particular problem with Version 70.5 because improved logic for
detecting singular RBE3 elements was introduced in this version, and the
program may fail RBE3 elements that earlier versions passed.
Avoidance: The error has been corrected in Version 70.5.2. Another avoidance
is to run the model in Version 70 with param, checkout yes present. This makes
tests on the model including equibrium tests on the rigid element constraint
matrix. Elements which will pass tests in Version 70 but fail with
singularity messages in Version 70.5 are likely to show poor equilibrium
properties in the para
31891
2001
r Midside Nodes
Documentation - GPSTRESS - No Printout fo
MSC/NASTRAN does not printout GPSTRESS for midside nodes. This limitation is
documented in the Application Manual but since that manual is no longer current
a remark should be added to the Quick Reference Guide.
31898
70.5
Frequency Response - FREQ - UWM 6498
In a frequency response analysis run (SOL 108 and 111), if the FREQ Case
Control command does not exist, then the job will terminate with the following
unclear error messages on some machines.
Check call to MSGPOP from FRLG with the message number 3031
Parameter 1 is
0
Parameter 2 is FRL
Parameter 3 is FRRD
0FATAL ERROR
On other machines, the job may terminate with a signal 11 error in the log
file.
Avoidance: Add the appropriate FREQ case control command.
31906
70.5.2
Nonlinear Analysis - DBC - UFM 4551
If a nonlinear analysis fails to converge and PARAM,POST,0 is set, the job will
issue fatal messages indicating that the analysis has not converged but then
will continue and will fail in the DBC module with a machine dependent message.
An example of the messages are:
*** USER
*** STOPPED ITERATIONS DUE TO REACHING MAXIMUM ITERATION LIMIT WITHOUT
CONVERGENCE ***
*** USER
*** MAXIMUM NUMBER OF BISECTIONS OR MINIMUM LOAD STEP HAS BEEN REACHED.
*** USER
FATAL
MESSAGE 4551,
*** STOPPED PROBLEM DUE TO FAILED CONVERGENCE
^^^ USER INFORMATION MESSAGE 9005 (NLSTATIC)
^^^ THE SOLUTION FOR THE LAST CONVERGED LOOPID=
85 IS SAVED FOR RESTART
BIOMSG:
31919
70.7
Installation - Sun/Solaris - fatal : libs
unmath.so.1: can't open file errno = 2
For Sun SuperSPARC V70.5 and v70.6 and Sun UltraSPARC V70.0.3 Clients only, If
you do not have a Fortran compiler on your system, you may
receive the following error message in the LOG file when you attempt to run
MSC/NASTRAN:
ld.so.1: <install-dir>/msc705/solaris/analysis:
fatal : libsunmath.so.1: can't open file errno = 2
This error occurs when the system cannot find the "libsunmath" dynamic library.
This error is corrected on the MSC/NASTRAN V70.5.1 (r2) CD-ROM.
You can also obtain the missing libraries from your MSC representative or
directly from MSC's Web site at the URL:
ftp://ftp.macsch.com/pub/msc-products/NASTRAN/V70.5/solaris/libsunmath.so.1
Once you have obtained the file, please copy it to the solaris architecture
directory, i.e.,
31931
70.6
Acoustics - ACMODL, CTETRA, CTRIA3, GP5 -
SFM 6169
Some models with TRIA3 structural elements and TETRA fluid elements at the
fluid/structure interface using IDENT method on the ACMODL bulk data entry fail
in the GP5 module with a message similar to:
*** USER FATAL MESSAGE 6169, FOUND TWO OR MORE STRUCTURAL GRID POINTS WITH
IDENTICAL COORDINATES
WHICH LIE ON THE FLUID/STRUCTURE BOUNDARY.
USER ACTION: CHECK GRIDS AND/OR SET1 CARDS WHICH
BELONG
TO PANEL OR ACMODL CARDS.
GRID ID =
12
GRID ID = 101979
^^^ USER WARNING MESSAGE 9031 (ERRPH1) NOGO ENCOUNTERED IN SUBDMAP
SEMG
This message is in error since one of the referenced structural grids is really
a fluid grid. Abitrary changes to the model can make it run or not run.
Avoidance:
Use the DIFF method on the ACMODL
31933
2001
AP Module Dictionary
Documentation/DMAP - MATGEN Option 5 - DM
The documentation for MATGEN option 5 states that the parameter p5 may be used
to select pseudo-random or non-repeating random numbers, but the equation used
is incorrect. It states that if P5<0, a matrix of random numbers that do not
repeat from call to call is produced. By implication, values outside this
range produce pseudo random numbers. The usual definition of this term is that
while the numbers produced should have reasonable distributions for a set of
random numbers, the matrix produced on each call should be the same, both on
one run, and on different runs.
The correct formula is "if p5 is less than or equal to 0" the non-repeating
("seeded") type of random numbers are used. Note that this changes the action
for the default value of p5, which is zero.
31934
the CD Field
2001
Documentation - RFORCE - Clarification of
The content description of the CID and R1, R2, R3 fields for the RFORCE entry
currently states CID must be a Caresian system. It should state that if a
non-rectangular system is specified, RFORCE will use the CID as if it were a
rectangular system and unexpected answers may result.
The desrcription of
CID, R1, R2, R3 should read as follows and remark 14 should be added.
CID
vector.
Coordinate system used to define the components of the rotation

(integer >= 0, Default = 0)
R1, R2, R3
Rectangular components of the rotation vector R. The vector wil
l
pass through G,
please see remark 14. (R1**2 + R2**2 + R3**2 > 0.0)
Remark 14.
If CID is not a rectangular coordinate system, RFORCE will
treat it as if it were a rectangular system

when d
31958
2007.0.0
75 and SFM 4276
Memory Management - REIGL, GPFDR - SFM 42
On a large model, it has been observed that the job may fail in REIGL or GPFDR
with the following unclear messages:
*** SYSTEM FATAL MESSAGE 4275. DURING A
READ OPERATION, UNIT = 26, DATA
BLOCK=NUMERIC
, A BLOCK NUMBER CHECK CONDITION OCCURRED. ( IONAST
CODE= 304)
0*IONAST* err 304 pid,name,b+1,z4(b+1),nxtblk,pbknbr=
0 118 62402415
0
3377
5912
BIOMSG: ERROR 304 HAS OCCURRED IN ROUTINE IONAST , FILE INDEX (FILEX) =
0
STATUS =
0
The exact cause of this error is currently unknown. MSC has been unable to
obtain the input file that shows this error due to the confidentiality of the
input file.
Avoidance: Increasing memory cured this particular problem.
31966
70.7
2, MATHP - UWM 6286 in ZREAD
Nonlinear Analysis - CBUSH, CELAS1, CELAS
If nonlinear stress output is requested for CBUSH, CELAS1, and CELAS3 elements
which reference PBUSHT and PELAST in nonlinear
analysis then UWM 6286 will be issued. This also occurs for hyperelastic
element grid point output.
Avoidance: Insert and/or replace the following changes into nddl.dat under
DATABLK OES:
OR,40,{ Bush1d }
EITHER,BACK(FCODE)=0,{ Real
}
FE,RS,{Element Force}
UE,RS,{Axial Displacement}
VE,RS,{Axial Velocity* }
S,RS,{Axial Stress*}
E,RS,{Axial Strain*}
EP,RS,{Plastic Strain*}
FAIL,I,{Failed Element Flag}
OR,1,{ Real / Imaginary
}
FER,RS,{Element Force}
UER,RS,{Axial Displacement}
SR,RS,{Axial Stress*}
ER,RS,{Axial Strain*}
31970
erelement
Superelements - CSUPEXT Ignored if no Elements Exist in a Sup
If there are no elements inside a superelement, but there are interior points,
and CSUPEXT entries are used to define the exterior points, the CSUPEXT entries
will be ignored.
Avoidance: Add PLOTEL elements between interior and exterior points.
31980
70.5.1
Nonlinear Analysis - NLCOMB - Traceback
If a problem has BEAM, BAR, or BEND elements and thermal loads in a nonlinear
solution sequence (106 and 129), the job may fail in module NLCOMB. This error
first occurred in Version 70.5. This has been observed only on the Cray, but
might occur on other systems. On the CRAY the following traceback was
encountered:
Beginning of
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
31982
Traceback:
line 42 (address 15517150b) in routine 'TRBK'.
line 39 (address 132053d) in routine 'RECOVR'.
line 112 (address 140623d) in routine 'sysrcv'.
address 15237006a in routine '__handlr'.
address 5616165c in routine 'NLCWRK'.
line 126 (address 5607145c) in routine 'NLCOMB'.
line 90 (address 10632226d) in routine 'XSEM15'.
line 363 (addr
70.6
SSSALTERs - checka.v70 - UFM 13
In the checka.v70 and checka.v705 alters, there are two lines which exceed 80
columns. If these alters are pasted into the data file, the line will wrap in
many editors, and cause the following fatal message:
0*** USER FATAL MESSAGE 13 (XGPIDG )
ERROR IN DMAP INSTRUCTION Q-SET
INSTRUCTION NO. 50
DMAP INSTRUCTION NOT IN MODULE LIBRARY.
Avoidance: Shorten the comments following the DMAP instructions "type
db,aagds,ptga $", and "upartn uset0,aagds/ptga,,,/'G'/'A'/'S'/1 $". Another
option is to avoid pasting the file in, but instead use the include statement.
31986
70.5.2
Superelements - DBDN DBset Too Large
The DBDN DBset is larger in V70 and V70.5 than in earlier versions of
MSC/NASTRAN. The increased size is due to several data blocks which are
generated during dynamic reduction being incorrectly stored on DBDN. The only
effect of this error is an increase in the DBDN Dbset disk usage.
compile semr3
alter 'call cmpmode'
type parm,nddl,char8,n,dbupx,dbdnr1 $
type parm,,char8,n,dbtmp $
dbtmp=dbdnr1 $
dbdnr1=dbupx $
alter 'call sesum'
dbdnr1=dbtmp $
compile sekr
alter 1
dbtmp=dbdnr1 $
dbdnr1=dbupx $
alter 'end \$'(,-2)
dbdnr1=dbtmp $
compile semrm
alter 'mvaa'(2,-1)
dbtmp=dbdnr1 $
dbdnr1=dbupx
31990
2001
Documentation - PBUSH1D
The MSC/NASTRAN Quick Reference Guide for Version 70.5 incorrectly states that
SHOCKA, CVT, IDTS, IDETS, IDETSD, TYPE, IDT, IDTTU, IDTDV are required on the
PBUSH1D entry. These fields may be required based on values in other fields
and options selected, but are not mandatory.
32011
2001
Direction Not Described
Documentation - PBUSH - Element Property
The documentation for PBUSH does not say which coordinate system the
"directions 1 through 6" refer to. These directions refer to the element
coordinate system.
32014
70.5.2
Answers, Traceback
Transient Analysis - NLRGAP, TRD1 - Poor
Input files using the NLRGAP in SOL 109 may fail with a floating point
exception on NT platforms or may issue a traceback in the TRD1 module, routine
tabld on SGI R8000/R10000 systems. The error is caused by the table look up
for the coefficient of friction for the NLRGAP. All 32 bit, short-word,
machines will return an incorrect value for the coefficient of friction;
however, this is not likely to have a significant effect on the results of most
problems.
Avoidance: Run the problem in solution 129. A different error with similar
symptoms may also be encountered in the same area of the code, please see error
number 32685.
32015
2001
es Not Work in Solution 112.
Documentation - Release Guide - NLRGAP Do
The MSC/NASTRAN Release Guide for Version 70.5 incorrectly states that the
NLRGAP element works in SOL 112. The NLRGAP does not work in this solution, but
it does work in SOL 9.
32016
2001
, Wrong Answers
GAP Constraints - PARAM,CDITER - UWM 9096
If the iterative solution for GAP constraints in SOL 101 does not converge, a
warning message is issued (9096), indicating that the solution has not
converged; however, the results for displacements, etc. are still output.
^^^ USER WARNING MESSAGE 9096 (CSTRDISP)
^^^ CONSTRAINED DISPLACEMENT ITERATIONS FAILED, ITERATION LIMIT LOAD CASE =
1
Avoidance: If warning message 9096 is issued, do not use the results.
Increasing the value of CDITER may help the problem to converge.
32022
oblem
70.5.1
Miscellaneous - NLRGAP - Incorrect TPL Pr
The tpl test deck nlrgap.dat referred is not the problem described in the
Version 70.5 Release Guide. The tpl deck nlrgap.dat has been replaced with
the correct input deck on the Version 70.5.1 r2 cd. A listing of the correct
input follows:
$ shaft1x.dat
$ radial gap, .002 clearance, contact stiffness = 1.e6 constant
$ example: rotating load on cantilevared shaft
$ 40" shaft, circular x-section, 2" diameter shaft
$ 10" diameter rotor
$ 15 hz. imbalance
sol 129
time 80
cend
title= 15 hz. rotating imbalance, radial gap
set 1 = 9,10
set 2 = 1,8
set 3 = 1001,1002
$sdisp=3 $ epoint displacements (relative displacements)
disp(plot) = 1$ NLRGAP grid displacements
force(plot) = 2
nlload=1 $ NLRGAP load output
nonlinear = 200 $ NLRGAP set ID
tfl=900 $ transfer function ID fo
32047
70.7
nswers with Material Damping
Optimization/Design Sensitivity - Wrong A
Material damping defined on a material bulk data entry is ignored in an adjoint

sensitivity analysis.
Avoidance; If damping is a constant across all materials, param,g may be used.
Otherwise the adjoint method needs to be avoided by forcing the direct
sensitivity method using the following alter:
COMPILE DESCON
alter 'dsad'(,-1) $
type parm, ,logi,n,hold $
hold = pexist $
pexist = true $
alter 'dsad'
pexist = hold $
32070
70.5.2
2 - Wrong answers
Differential Stiffness - SOLs 103, 107-11
If QSETi, SEQSETi, or SENQSET entries are used to compute component modes in

SOLs 103 and 107-112 and differential stiffness is requested with the STATSUB
Case Control command, then the differential stiffness will not include the
effects of the q-set degrees-of-freedom.
Avoidance: Insert the following DMAP alter which is valid for Version 70.5
only:
compile sekdr
$ this alter is for Version 70.5 only
alter 'call segoa',''
type db goq $
CALL SEGOA USET,GOT,goq/GOAT/NOOSET/NOQSET/NOTSET $
endalter
32073
70.5.2
swers or Fatal Messages
Superelements - Partitioned SE - Wrong An
If scalar points are defined in a partitioned superelement and the scalar

points are also defined as exterior to the superelement (e.g.; QSETi) then the
run may produce wrong answers and/or issue a fatal message. This error can
also occur using the SENQSET entries.
compile phase0
alter ',SILS,VGFS'
delete /vgfs $
alter ',SILS,VGFS'(2)
delete /vgfs $
endalter
32074
70.5.2
ls in SOLs 110-112 - UWM 9098
Performing data recovery using external
with SEBULK type external superelements
9098 indicating that the data necessary
available. The run will then fail in an
Superelements - Data Recovery for Externa

superelements in SOLs 110, 111, and 112
will result in user warning message
to perform data recovery is not
unexpected manner.
Avoidance : Include the following DMAP alter in the run which performs the
residual structure solution
compile super3
alter 'call extdrout'(4),''
if ( extdrout<>'
' ) then $
if ( app1='mmreig' ) then $
call extdrout uls,ol1m,eqexins,maps/
dum/app1/'
'/true $
call extdrout uh2,ol1r,eqexins,maps/
dum/app/soltyp/true $
else $
call extdrout uls,ol1m,eqexins,maps/
dum/app1/soltyp/true $
endif $
32080
4276, EC 1605
70.7
Complex Eigenvalue Analysis - CEAD - SFM
On the SGI, complex Lanczos eigenvalue analysis may produce the unexpected
system fatal message 4276 error code 1605. This appears to be caused by
insufficient memory for the CEAD module.
Avoidance: In most if not all cases experienced to date, increasing the memory
has allowed the runs to run successfully.
32087
rs
70.7
Frequency Response - TLOADi - Wrong answe
TLOADi entries are ignored in direct frequency response (SOLs 8, 11, and 108).
Avoidance: Insert the following DMAP alter in SOL 108:
compile sedfreq
alter 'CASE
CASErs'
type parm,,logi,n,fourier $
paraml dynamics//'bulk'//////'tload1'/s,n,tload1/
'tload2'/s,n,tload2 $
PARAML CASEF//'DTI'/-1/38//S,N,TSTEP $
fourier=(tstep=-1 and (tload1=-1 or tload2=-1)) $
alter 'call freqrs',''
CALL freqrs CASEF ,USETD ,DLT
,FRL
,trl
rpd
,DIT
,EST
,cstms ,mpts
bgpdts ,gpsnts ,GPECT ,SILS
,edts
ckdd
,cmdd
,cbdd
,k4dd
,
,
,
,sild
,ditid
vafs
,rgdfd ,rsgg
,rmgg
,ppf
32091
70.7
N, PARAM,POST,0 - Missing XDB Output
,
,
,
,
,
,
Nonlinear Analysis - PCOMP, STRESS, STRAI
If PARAM,LGDISP,>0 and PARAM,POST,0 is specified in SOL 106, then laminar

stress and strain output is missing from the .xdb file.
compile nlstatic
alter 'oescp,oestrcp'
file oescpr=append/oestrcpr=append $
append oescp,/oescpr/2 $
append oestrcp,/oestrcpr/2 $
alter 'OUTPUT2 oesnlxr'
IF ( POST=0 ) then $
DBC
OEScpr,,,,,,,,,,,,,,,,,,,//
'OESC'/'CASECC'/'OL'//////////////////
-1/DBCPATH/S,N,CP/app//GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT $
DBC
OEStrcpr,,,,,,,,,,,,,,,,,,,//
'OESC'/'CASECC'/'OL'//////////////////
-1/DBCPATH/S,N,CP/app//GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT $
endif $ post=0
endalter
32093
IFPDRV)
70.5.1
Aeroelastic Analysis - CSSCHD - UFM 311 (
If a subcase invokes multiple CSSCHD bulk data entries, the user fatal message
shown below incorrectly states that the CSSCHD ID's must be unique.
NON-UNIQUE FIELD 2 ON BULK DATA ENTRY CSSCHD
ENTRY COUNT =
153
10
SORTED
Avoidance: There is no avoidance other than to limit the scheduled control

surface functionality to a single control surface for each subcase.
32094
70.7.2
ar Trim Analyis - BIOMSG: ERROR 100
Optimization/Design Sensitivity - Nonline
Version 70.5 added a basic capability to perform nonlinear static aeroelastic

trim analysis. This capability is not available in SOL 200 for sensitivity
analysis and its use results in a nondescriptive fatal message such as
BIOMSG: ERROR
100 HAS OCCURRED IN ROUTINE PACK
Avoidance: Either linearize the static aeroelastic trim analysis or do not

attempt to perform this type of sensitivity analysis. Version 70.7.2 has been
corrected to provide a meaningful message.
32098
2001
- typographical error
Documentation, QRG - PSHELL, remark # 14
There is a typographic error for Remark 14 of the PSHELL entry in the Version
70 and 70.5 Quick Reference Guide. The term (Ts)10**8(Ts) should simply be
10**8 instead.
32099
2004
Geometry Written to OUTPUT2 File
Postprocessing - PARAM,POST,-2 - Multiple
If multiple boundary conditions are specified in a normal modes analysis and

param,post,-2 is set, the geometry data blocks are written to the output2 file
in each subcase rather than just once. This unnecessarily increases the size
of the output2 file.
Avoidance: Specify PARAM,OGEOM,NO in all but the last subcase or insert the
compile super3
alter 'call out2geom'(,-1)
type parm,nddl,i,n,ncase $
if ( ncase<=1 ) then $
alter 'call out2geom'
endif $
endalter
32101
70.7
SOL 101 - UWM 979
Plotting - XYPLOT of Grid Point Stress in
If an XYPLOT of grid point stress (param,curvplot,1) in solution 101 will lead

to the following message:
*** USER WARNING MESSAGE 979 (XYTRAN)
AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID xxx
-STRE- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA BLOCK
COMPILE SEDRCVR
$ALTER 'SORT2\=','' $ for V70
ALTER 'SORT2\='(2),'' $ for V70.5
SORT2=NOT(ANDL(NOSORT2,NOSTR2) OR CURVPLOT>-1) $
ENDALTER
32112
tput
70.7.2
Miscellaneous - MSCACT Missing Summary Ou
The MSCACT utility delivered with MSC/NASTRAN Version 70.5 on the UNIX and
Windows NT systems has an error that disables the "standard" output summary.
If one of the alternate summaries is selected via the "summary" keyword, the
correct detail lines will be generated, but the total line will be missing.
This error can be corrected by changing the following lines in the
<install-dir>/msc705/util/mscact.c source file and rebuilding the MSCACT
utility as described in Section 6 of the "Configuration and Operations Guide"

for you operating system.
NOTE: This error does not affect the accounting logger functions.
The changes are:
Change line 1339 from
if( total == -1 && !strcmp( p, TOTAL_LABEL ) )
to
if( total == EOL && !strcmp( p, TOTAL_LABEL ) )
32113
2001
Miscellaneous - DMIG, DMI - Poor Messages
The messages encountered when there is an error on a DMIG or DMI entry do not
point to the location of the error. This can make it almost impossible to
locate the error in a large matrix input.
32116
70.5.1
y ISHELL Not Found
Miscellaneous - ISHELL - Program Called b
If the program called by the ISHELL module has a name with fewer than 8
characters without including the extension, the module will not search properly
for the extension. For example, the file named "EFM.EXE" will be found if the
name "EFM.EXE" is entered, but will not be found if the name "EFM" is entered.
Avoidance: Use 8 characters in the filename if you do not include the
extension.
A related error that may occur on Windows NT if a 16-bit executable is to be
run. If ISHELL processing fails with an "UNABLE TO CREATE A NEW PROCESS"
error, specifying the standard NT command processor as the processor to be used
may solve the problem. That is, setting the MSC_ISHELLEXT environment variable
to exe#cmd, either in the System/Environment Control Panel tab or by a command
line set opti
32125
I
70.5.1
Submittal - DBINIT - Long filenames on SG
If a very long filename is used, either via the job datafile pathname, the dbs
or out keywords, or an ASSIGN statement, the job may fail without any messages
in the F06, F04, or LOG files. A clue to this error may be the termination of
the job in the DBINIT module (as indicated in the F04 file) or incomplete
reports for the "SUMMARY OF FILE ASSIGNMENTS" or "SUMMARY OF PHYSICAL FILE
INFORMATION" or "SUMMARY OF PHYSICAL FILE I/O ACTIVITY" tables.
Avoidance: Reduce the lengths of the longer pathname components. A pathname
component is either a directory name (i.e., the text between slashes) or the
actual filename part.
32127
rong Answers
70.5.1
Aeroelastic Analysis - AELINK, CSSCHD - W
If AELINK and CSSCHD entries appear is the same subcase in a static aeroelastic
analysis, wrong answers are produced.
32134
70.5.1
Installation - SGI IRIX64 Only
When trying to run Version 70.5 on SGI IRIX 64 systems the following error
message may appear in the command window:
3708:/msc/msc705/irix64/analysis: rld: fatal error: cannot successfuly map
soname 'libcomplib.sgimath.so' under any of the filenames < then a list of
library files follows >.
Avoidance: If the client does not have a complete set of sgi math libraries
they will need to get a /usr/lib64/mips4/libcomplib.sgimath.so from MSC. This
can be found at the following locations:
On the web at:
ftp.macsch.com/pub/msc-products/NASTRAN/V70.5/irix64
filename: libcomplib.sgimath.so
or the following computer file on MSC's net:
/net/oberon/oberon/disk1/msc705/unix/msc705/irix64/libcomplib.sgimath.so
32135
70.6
ing Left Hand Vectors
Complex Eigenvalue Analysis - CEAD - Miss
The new CEAD module option for the CLAN method in Version 70.5 will produce
both left and right hand eigenvectors. However, if there are less than three
DOFs in the problem only the right hand vectors are output.
Avoidance: An avoidance is to add a third DOF, uncoupled, if necessary.
32136
ct Equation
2001
Documentation/QRG - PARAM,CURVE - Incorre
The documentation for PARAM,CURV in the Quick Reference Guide indicates that
if:
| n dot lm | >= .4, then the projection of the y-axis on the surface of the
element is taken as the reference axis.
The left hand side of the inequality should be squared.
( n dot lm)**2 >= .4.
32143
P-Elements - TETRA - Incorrect Mass Matrix
The mass for TETRA p-elements at p-level 1 is incorrectly calculated.

Avoidance: Run the analysis at a p-level of 2 or higher when using TETRA
p-elements are present.
32145
al 10
70.5.2
Transient Analysis - TRD1 - Received Sign
Transient analysis may fail in the TRD1 module with no message. The log file
may contain a machine dependent message of the form:
*** Received signal 10 (SIGBUS)
Avoidance: The error is machine dependent and is caused by a boundary

alignment problem. The error will only occur on HP, SUN and SGI systems
(Digital will print warning messages but will complete successfully). The
error should be avoided by increasing memory by exactly 2 words on HP and SUN
system and by 6 words on SGI systems.
32157
ocument
Online Documentation - Installation - Not a Valid WorldView D
The MSC/NASTRAN Online Encyclopedia issues a "Not a valid WorldView document:"

error message when any hotlink button on a book selected from the main books
menu is picked. Iview configuration file entries for fulltextPath and
welcomeDoc are valid and the documents could be selected manually from the
Open/File menu picks.
Resolution/Avoidance:
This problem could occur on any system where:
1) the mne collections are moved from one location to another
2) the mne installation directory is nfs mounted or linked to a differently
named location
As part of the installation process, several *.cfg files are created on the fly
and locations are hardcoded with pathname of the installation directory. If
the mne collection directory is changed, it is not sufficient to upd
32168
70.5.2
Matrix Methods - DCMP - SFM 4276 EC 7777
It is possible that a job that should fail in DCMP with a max ratio error,
identifying the problem degrees of freedom, instead fails with a traceback in
sparse decomposition. The following is an example of the traceback from an
hpux system.
Process traceback
0) 0x0009700c
1) 0x00f83310
2) 0x005efba0
3) 0x0022b7b4
4) 0x004c355c
5) 0x00220eb8
6) 0x000c0fe8
(
(
(
(
(
(
(
32171
t
...
sysrcv + 0x320 [/cae_k_apps/msc/msc70/hpux/analysis.pa2_0]
_sigreturn [/cae_k_apps/msc/msc70/hpux/analysis.pa2_0]
dfmsj_ + 0x130 [/cae_k_apps/msc/msc70/hpux/analysis.pa2_0]
dfmsa_ + 0x2b20 [/cae_k_apps/msc/msc70/hpux/analysis.pa2_0]
sdcomp_ + 0xb8 [/cae_k_apps/msc/msc70/hpux/analysis.pa2_0]
dcmpa_ + 0x2b8 [/cae_k_apps/msc/msc70/hpux/analysis.pa2_0]
dcmp_ + 0x130 [/cae_k_apps/msc/msc
70.7
Composites - PARAM,POST,0 - Missing outpu
Laminar stress and strain output is not written to the xdb file in SOL 103 and
105.
compile sedrcvr
alter 'DBC
OSTR1'
endIF $ SORT2
alter 'endIF $ SORT2'(3),''
endalter
32174
70.5.1
Installation - xnastran not delivered
The XNASTRAN utility is missing from the Version 70.5 (R1) CD. The executable
file, <install-dir>/msc705/<arch>/Xnastran, can be copied from any earlier
version.
32176
n
2001
Documentation - EIGR - Point Normalizatio
In modal analysis (sol 103), when POINT normalization is selected on the EIGR
bulk data entry, and the defined component is zero, NASTRAN does not revert to
MAX as specified in the Quick Reference guide for the EIGR bulk data entry:
NORM
Method for normalizing eigenvectors. (Character: "MASS," "MAX," or
"POINT"; Default+"MASS")
.
.
POINT Normalize to a positive or negative unit value of the component
defined
in fields 3 and 4
(defaults to "MAX" if defined component is zero).
Documentation of NORM POINT should read:
.
.
POINT Normalize to a positive or negative unit value of the component
defined
in fields 3 and 4
(defaults to "MASS" if defined component is zero).
32177
2001
Default values
Documentation - QRG, INIT FMS - Incorrect
Under the description of the INIT command in the Quick Reference Guide, the
default values for DBALL and SCR300 are stated incorrectly as 25000 and 175000
blocks. The correct default value is 250000 blocks for each of the DBSETs.
32193
70.6
ST, NLITER - SFM 2085
Nonlinear Analysis - CELAS1, CELAS3, PELA
If the CELAS1 or CELAS3 element references the PELAST entry in a nonlinear

analysis where the TKNID field is used to define the nonlinear force vs.
displacement relationship, the job will fail with the following message:
ELEMENT TYPE
11 NOT SUPPORTED FOR NONLINEAR ANALYSIS.
ILLEGAL INPUT TO SUBROUTINE NLEMG
Avoidance: Use the CBUSH entry and define the nonlinear force vs. displacement
relationship through the KN field on the PBUSHT entry.
32218
2001
DVGRID - SFM 3007
Optimization/Design Sensitivity - CBUSH,
In shape optimization, if the CBUSH element is present, (even when not

referenced by a DVGRID), the job fails with the following fatal message,
"element type 102 is not supported *** SYSTEM FATAL MESSAGE 3007 (DOPR6)
ILLEGAL INPUT TO SUBROUTINE Dopr6a".
Avoidance: Don't use the CBUSH element in a shape optimization run.
32220
2001.0.1
Transient Analysis - TSTEP - UFM 4562
In a modal transient analysis, the following error messages may be erroneously

issued after the completion of the job.
0*** USER
FATAL
MESSAGE 4562,
TSTEP (TIME STEP) DATA IS MISSING
Avoidance: This message can be safely ignored if all the requested output is
obtained.
32225
ssing Option
2001
Documentation - QRG, System Cell 206 - Mi
Option 9 of system cell 206 which selects the better of METIS and MMD, is not
documented in the Version 70.5 Quick Reference Guide.
32259
70.7
for Unrestrained Hinge Moment Coeff.
Aeroelastic Analysis - Incorrect Answers
Two errors have been detected that relate to the printing of unrestrained hinge
moment coefficients in SOL 144 (static aeroelasticity):
1. The unrestrained hinge moment coefficient values printed for the "INTERCEPT"
coefficients are in error if they are nonzero.
2. If there are multiple subcases with the same Mach and q (dynamic pressure)
conditions, the unrestrained hinge moment coefficient values printed for the
second and subsequent subcases are in error. The coefficients for the first
subcase are deemed correct with the exception of the INTERCEPT value mentioned
previously.
Avoidance: Make the following DMAP change:
compile aestatrs list
alter 'totu','kbrzx'
dbstatus ipzf//s,n,noipz $
if ( noipz=-1 ) matgen ,/ipzf/7/norset/1 $
add ipzf,/mipzf/-1.0
append mipzf,k
32264
69
Parallel Processing - EMA - Wrong Answers
Due to an error in parallel EMA, any system running parallel EMA (even if they
are only using one processor), could get wrong answers.
Avoidance: Use the serial version.
32282
70.7.2
th the Wrong File Names
Utilities - XNASTRAN - xmonast Started wi
The XNASTRAN utility does not properly handle an alternate input data file
type, e.g., "example.bdf", when directly starting XMONAST to monitor a job. It
will attempt to directly start XMONAST on the files "example.bdf.f04",
"example.bdf.f06", and "example.bdf.log". Instead, it should be setting the
nastran command's "xmon" keyword and relying upon the nastran command to
correctly monitor the job.
Avoidance: Set "xmon=yes" in an RC file or as an "advanced argument" and do not
use XNASTRAN's ability to start XMONAST.
32286
70.6
- SFM 6710 (TAFF)
Superelement - STATSUB, multiple subcases
When more than one static subcase exists in the bulk data for forming the
differential stiffness matrix for a normal modes analysis (STATSUB), and the
model contains superelements, then the job will fail with the following unclear
messages:
*** USER INFORMATION MESSAGE 7325 (SEP2DR)
PROCESSING OF SUPERELEMENT
10 IS NOW INITIATED.
^^^ USER INFORMATION MESSAGE 9049 (SEKDR)
^^^ SUPERELEMENT DIFFERENTIAL STIFFNESS GENERATION, ASSEMBLY, AND REDUCTION.
*** SYSTEM FATAL MESSAGE 6710 (TAFF)
THE THIRD INPUT PARAMETER TO MODULE TAFF REFERENCES AN UNDEFINED LOAD SET
ID.
0FATAL ERROR
This job will fail even if there is only one static subcase callout, but there
are multiple loadings in the bulk data section that are not used.
Avoidance: There are two possible
32294
ory on CRAY
70.5
Miscellaneous - ISHELL - Insufficient Mem
Use of the ISHELL utility on a CRAY computer may cause the job to fail due to
insufficient memory.
Avoidance: Specify twice the memory that the job would normally take.
32296
2005.1
ements - UFM 5423 (MPYAD)
Differential Stiffness - STATSUB, Superel
In SOL 105, or if differential stiffness is requested (STATSUB Command) in

SOLs 103 and 107 through 112, when superelements are present and no SUPER
command, or SUPER=ALL, is specified, then static loads will be generated for
the second or dynamic subcase and the job will fail with the following error
messages.
*** USER FATAL MESSAGE 5423 (MPYAD)
COLS ROWS FORM
TYPE NZWD DENS
2
60 4333
8 3333
40 2000
32303
tput
TRAILER FOR GOAT
IS
106
12
50
TRAILER FOR UAS
IS
103
12
TRAILER FOR UOOX
IS
104
50
Nonlinear Transient Heat Transfer - SUBCASE, SET - Missing Ou
In nonlinear transient heat transfer (SOL 159), if different subcases request

different outputs, only the request for the first subcase will be honored and
no output will be obtained for subsequent subcases. In the following example
thermal results for grid 1 and 2 will be output for subcase 1 but no thermal
output will be obtained for subcase 2.
SUBCASE 1
TSTEPNL = 100
DLOAD = 200
SET 1 = 1,2
THERMAL =1
SUBCASE 2
TSTEPNL = 100
DLOAD = 200
THERMAL = ALL
Avoidance: The only avoidance is to request the same output for all subcases
above the first subcase. In the above example, request THERMAL=ALL above the
first subcase.
32320
Answers
70.7
Inertia Relief - PARAM,ALTRED,YES - Wrong
If PARAM,INREL,-1 and PARAM,ALTRED,YES are specified then wrong answers are

produced.
compile phase0
alter 'LFIXEDB OR INREL\=-1',''
IF ( LFIXEDB ) ALTRED='NO' $
alter 'SEID\=0 and (LFIXEDB',''
IF ( SEID=0 and (LFIXEDB or cditer>0)
) INREL0=false $
compile sedisp
alter 'MPYAD
LAO,UA,UOX','IF ( FIXEDB\>-1 ) CALL SEGOA,'
if ( inrel0 ) then $
IF ( SEID=0 ) THEN $
IF ( inrel=-1 ) then $
MPYAD
UOx,CRX,/UOXx $
else $
equivx uox/uoxx/-1 $
endif $
else $
MPYAD
UOx,CRj0,/UOXx $
endif $
else $
equivx uox/uoxx/-1 $
endif $
MPYAD
LAO,UA,UOXx/UOY/1 $
32321
70.7
CFORCE - Missing output
Static Analysis - PARAM,ALTRED,YES and MP
MPCForce output is not computed if PARAM,ALTRED,YES is specified.

compile sedisp
alter 'sdr1'(3,1)
ENDIF $ ALTRED
alter 'ENDIF \$ ALTRED',''
endalter
32361
o Not Work
Online Documentation, MNE - Links in DMAP Module Dictionary D
In the Version 70 MSC/NASTRAN Online Encyclopedia, the chapter contents links

in the first page of each chapter of the DMAP Module Dictionary do not work.
Avoidance: Use the main TOC in the quick access bar located at the top of every
page.
32362
2001
, GMBNDS - DMAP Fatal Message 9050
Documentation, Interface Elements - GMBDC
The Quick Reference Guide bulk data definitions for the GMBNDC and GMBNDS
entries needs the following remark added:
The interface elements may generate high or negative matrix/factor diagonal
ratios. If there are no other modelling errors, these messages may be ignored
and PARAM,BAILOUT,-1 may be used to continue the run.
32364
70.5.2
Answers, SWM 1204
Postprocessing - TABPRT, OUTPUT2 - Wrong
Incorrect data may be output by a TABPRT and/or an OUTPUT2 request using the
neutral option. Many occurences of SYSTEM WARNING MESSAGE 1204 may be an
indication of a problem.
Avoidance: For the OUTPUT2 neutral option, increase mem such that the value
is at least
f2 x size of largest record + 2 x nasbuff + compiled length of the NDDL of that
datablock
For TABPRT NDDL-output, increase mem such that the value is at least
4 x size of largest record + 1 x nasbuff + compiled length of the NDDL of
that datablock
32365
2001
free-free Dynamic Reduction
Documentation/QRG - SESUP - Problems with
Models with free-free component modal superelement reduction give poor answers
(or may fail).
This limitation should be documented under the SESUP entry by
adding the following remark:
5. SESUP bulk data records are not allowed for Part (partitioned bulk data)
Superelements. Use the SUPORT bulk data records to
identify component
rigid body modes.
32375
ut Mis-Labeled
70.5.2
P-Elements - Transverse Shear Strain Outp
The p-shell element's two transverse shear strain outputs for the default
curvature option are switched. Otherwise the values are correct.
32376
2001
ng P-Shell Output
Documentation/P-Elements - OUTRCV - Missi
When the PROJ=F option is used on the OUTRCV bulk data entry for p-shell
elements, no output is produced in the .f06 file. The option should be used if
a postprocessor requires results in terms of 3D vectors or tensors, for
example, stress tensors with 6 stress components. The option does not produce
output in the print file *.f06.
32388
R ERROR CODE 31
Nonlinear Transient Analysis - TSTEPNL, ADD5 - UFM 4276 GETST
If a nonlinear transient analysis has trouble converging and output is not

requested for every timestep, the job mail fail with one of the following type
messages in ADD5.
0*** SYSTEM FATAL ERROR 4276.NXTCOL
0*** SYSTEM FATAL ERROR 4276.GETSTR
ERROR CODE
ERROR CODE
-31 PID=
31 PID=
0
0
-> CELAS2
-> CBUSH1D
Avoidance: Request output for every timestep.

32390
SFM 3001
70.7
Cyclic Symmetry - READ, REIGL - UIM 6137,
The READ module may issue the message: UIM 6137 INPUT MATRIX
HAS xx SINGULARITIES, followed by *** SYSTEM FATAL MESSAGE
is due to null columns in the matrices. For cyclic symmetry
remove unused degrees of freedom if they are for grid points
records.
TO DECOMPOSITION
3001 (READ). This
AUTOSPC does not
listed on CYJOIN
Avoidance: For solid element models, add a bulk data record GRDSET,,,,,,456 to
remove unused rotation degrees of freedom. Setting NASTRAN SYSTEM(273)=1 (Use
earlier version Lanczos method) has been shown to work as well in NAST705. The
following ALTER may be applied to version 70.5:
COMPILE MODERS
ALTER 'MATMOD *CASES'
SETVAL //S,N,METHTYP/0 $
MESSAGE //'DO A-SET REDUCTION FOR MASSLESS DEGREES OF FREEDOM'
32394
3008 (UTMCOR)
70.5.1
Complex Eigenvalue Analysis - EIGC - SFM
The new block complex lanczos method in Version 70.5 (selected by setting
system(108)=4) does not accurately predict the memory requirement. For large
problems this may lead to the following fatal message:
*** SYSTEM FATAL MESSAGE 3008 (UTMCOR)
MODULE = CEAD
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE CLDRV
USER ACTION: INCREASE OPEN CORE BY AT LEAST 1130847 WORDS
PROGRAMMER INFORMATION: LOCATION KEY = TSLSPILL
Avoidance: The fatal message may not be able to be avoided by increasing
memory. The analysis may have to be performed with another method.
32395
7340 (LNNHERR)
70.5.2
Eigenvalue Analsysis - EIGRL, READ - SFM
The new lanczos in MSC/NASTRAN Version 70.5 may fail with some variation of the
following message:
process error reported by subroutine LNNDRVS
see LNNDRVS abstract (ier =
-1)
The message that should have been output is:

FACTORIZATION ERROR DURING FINITE INTERVAL ANALYSIS AT FLEFT. FLEFT =
-3.9478D-05
*** SYSTEM FATAL MESSAGE 5299 (LNCS1D)
FACTORIZATION ERROR AT A BOUNDARY SHIFT.
POTENTIAL FIXES:
IF LOWER BOUND IS ZERO USE A SMALL NEGATIVE VALUE.
IF LOWER BOUND IS A SMALL NEGATIVE VALUE DECREASE IT.
ELIMINATE MASSLESS MECHANISMS THE MODEL MAY CONTAIN.
Avoidance: Follow the direction of SFM 5299 above.
32411
AL - UFM 1245
70.7
Aeroelastic Analysis - APD, RESTART LOGIC
If a read-only restart (RESTART LOGICAL FMS statement) is performed in SOLs

144, 145, or 146, then the run will fail in the APD module with the following
message:
0*** USER FATAL MESSAGE 1245, (BIO)
AN ALLOCATION ERROR HAS OCCURRED FOR A DATABASE FILE, FILX =
WRITE ATTEMPTED ON FILX WHICH WAS OPENED FOR READONLY.
10.
Avoidance: Use RESTART with the COPY option.

32426
70.7
s May Lead to Traceback
P-Elements - GP0 - Distorted Element Edge
If a p-element edge is too distorted, the program may fail with the traceback
that follows in GP0 instead of exiting with a meaningful message.
SIGTRAP - Trace trap FP division by zero
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
0x00001380
0x00000c54
0x00001710
0x00000cd4
0x000004b0
0x000009dc
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
evlpnd_
gp0dc_
gp0da_
gp0_
xsem02_
mainal
--- End of call chain --Avoidance: Other than correcting the distorted geometry, there is no
avoidance.
32438
70.5.2
ted on HP-UX 11
Submittal - Wrong executable may be selec
Apparently HP will make both 32- and 64-bit versions of HP-UX 11.0 available.
As a result of this, if the client is running the 32-bit version of HP-UX 11.0
on a PA-RISC 2.0 system, the nastran command will incorrectly choose the
V-class executable.
This error can only occur with MSC/NASTRAN V70 and MSC/NASTRAN V70.5 (r1).
The bit size of the OS is determined with the following command:

$ getconf KERNEL_BITS
The command will print 64 on a 64-bit kernel, e.g., on a V-Class system; and 32
on a 32-bit kernel.
Avoidance: Set the following keyword in the either system (e.g.,
<install-dir>/conf/nast705rc) or node (e.g.,
<install-dir>/conf/net/<node>/nast705rc) RC files.
On a PA-RISC 1.1 system:
proc=
On a PA-RISC 2.0 system:
proc=pa2_0
The processor type can be det
32457
70.5.2
Answers, Inefficient Processing
P-Elements - Beam Error Estimator - Poor
The error estimators for the beam p-element are incorrect by a factor based on
the length of the beam. This error may lead to over adapting or under
adapting. That is the error may lead to poor answers or it may lead to an
unnecessarily high p-level.
32458
ry
70.6
ESTIMATE - P-Elements - Insufficient Memo
MSC Estimate underestimates memory for input files with P-elements. This
limitation will be removed with version 71 for P-element runs without interface
elements (GMINTC/GMINTS). The limitation still exists for runs with interface
elements.
Avoidance: Do not use estimate to determine memory and disk requirements of
runs with p-elements prior to Version 71, and do not use estimate to determine
memory and disk requirements of any run with interface elements.
32467
70.5.5
Parallel Processing - Incorrect CPU Times
When parallel processing is selected, the f04 per processor cpu times may show
negative cpu times on Version 70.5 NT systems. This problem has been corrected
in the Version 70.5.5 release.
32476
data correctly
Utilities - RCOUT2, BGPDT - rcout2 utility does not transfer
The rcout2 utility will not transfer the BGPDT correctly on short-word UNIX
systems.
32477
rmance
70.6
Estimate - SPC/SESET THRU 9999999 - perfo
If an input file has an SPC entry specifying 1 THRU 9999999, then estimate will
take a lot of CPU time. This performance error will be removed in version 71.
Avoidance:
Specify the last grid id instead of 9999999.
32482
.
2001
DMAP - DRMS1 - SFE 4276 EC 1305 in ENDPUT
The DRMS1 module may fail with SFE 4276 EC 1305 in ENDPUT.
Avoidance: Reduce the number of subcases (or modes) in the input data blocks to
the DRMS1 module.
32489
Aeroelastic Analysis - AEROF - Incorrect Aerodynamic Box ID's
In SOL 146 for Harmonic Gust (Frequency Response), the AEROF=<setid|ALL> option
is supported. However, if the ALL option is used in Version 70.5, the f06
output listing incorrectly lists the Aerodynamic Box ID's as 0 (zero) for all
boxes. Whereas, if a specific SET is used, the correct results are obtained.
The complex forces printed in both cases, are correct.
32490
70.7
Poor Message, UFM 3007
Inertia Relief - UPARTN, PARAM,INREL,-1 -
If PARAM,INREL,-1 is specified without any SUPORTi entries then the run will
fail in the UPARTN module with the message:
*** SYSTEM FATAL MESSAGE 3007 (UPARTN)
ILLEGAL INPUT TO SUBROUTINE PARTN
Avoidance: Remove PARAM,INREL,-1 or specify SUPORTi entries.
32495
70.6
OST,0 - Missing .xdb Output
Nonlinear Statics - PARAM,NMLOOP,-1 and P
If PARAM,NMLOOP,-1 and PARAM,POST,0 are specified along with multiple subcases

in SOL 106, then only the eigensolution results for the last subcase are
written to the .xdb file.
compile nlstatic
alter 'call super3'(2),''
CALL SUPER3 CASECC ,casei
,
,
,PCDB
EMAP
,MAPS
SLT
,ETT
,
USET
,SILS
,PHA
,olb
,
,XYCDB
,EQEXINS
,GOT
,
,OLB
,
,
,POSTCDB
,PVTS
,GOQ
,
,
,
,
,FORCE
,CASES
,
,GPLS
,
,
,
,
,
,
,
32496
Documentation - PSDF, ATOC, RALL - Random Requests not yet Su
pported in PATRAN
The documentation for the new random analysis data recovery request options
PSDF, ATOC and RALL for DISP, VELO, ACC, FORCE, and STRESS documented in the
Version 70.5 Quick Reference Guide is misleading. These options are not yet
supported in PATRAN and thus are of no use and should not be selected.
Presently if they are selected, the random output is written to output2 file
and no random output is written to the f06 file. Currently, nothing is written
to the xdb graphics data base as might be implied by the Quick Reference Guide
remarks. Furthermore, if PARAM,POST,-1, is set, and the OUTPUT2 file is

FORMATTED and the new format of the output requests for RANDOM results is used,
such as
DISP (PSDF) = all
then the run will issue UWM 1206 indicating that the datablocks created by the
RANDOM module are not written to the OUTPUT2 file.
Avoidance: Currently the avoidance is simply do not use these output requests
since they are not supported in PATRAN.
32502
oor Message
Optimization/Design Sensitivity - Superelements - UFM 9068, P
If superelements are used in design optimization and a DRESP2 entry references

DRESP1 entries which select responses in different superelements, the run may
fail with UFM 9068 incorrectly stating that there are no DRESP1 or DRESP2
entries for the DESOBJ selected. The program should issue a message indicating
that the DRESP1 entries incorrectly spans superelements.
Avoidance: Remark 2 in the Quick Reference Guide description of the DRESP2
entry states that DRESP1 entries referenced on a DRESP2 may not span
superelements. However, the error message issued is misleading. Simply place
all of the referenced items into a single superelement.
32504
Restarts - TEMPD - Inefficient Processing
If a bulk data entry used to define a temperature loadings (TEMP,TEMPD,etc) is

changed on a restart, the restart logic will delete the stiffness matrix and
create a new one. This results in inefficient restarts.
Avoidance:
Either:
1) Place all TEMPi entries in the initial input file, or

2) Insert the following DMAP in the restart run;
$ DMAP alter to remove checking for changed in temperature
$ BE CAREFUL WHEN USING THIS, AS IT REMOVES SOME OF THE RESTART LOGIC
compile ifpl
alter 'restart.*geom3,geom3r',''
compile phase0
alter 'restart.*geom3s,geom3sr',''
32514
2001
Documentation - LOADSET - Only One LOADSE
T Command is Allowed per Superelement
The Quick Reference Guide description of the LOADSET command does not
explicitly state that only one LOADSET command may be used for each
superelement (or, in the case of no superelements, only one per run). This
command should occur in the first SUBCASE for each superelement (or above the
SUBCASEs). Any LOADSET commands in subsequent SUBCASEs will be ignored.
32522
70.5.2
- Wrong Answers
External Superelements - CSUPER, SPOINTS
If an external superelement is brought in using the CSUPER entry and SPOINTs

are used for some of the attached dof, it is possible that the matrices will be
attached incorrectly. In the problem demonstrating this, if all GRID points
were listed before the SPOINTs on the CSUPER, the matrices were attached
correctly. If the SPOINTs were listed, then the GRID points, then the matrices
were incorrectly attached. (NOTE - the matrices are attached in the order
listed on the CSUPER and care must be exercised to verify that the correct
order is listed - do not simply change the order on the CSUPER to correct this
problem)
Avoidance: If possible, use only GRID points on the CSUPER, or be careful to
create the matrices for the external superelement in such a way that the terms
for the GRID point
32526
70.5.2
2 or Wrong Results
On the SUN computer, if a MYPAD operation uses the DOT3RD kernel, then the
answers may be incorrect or the job may terminate with one of the following
error messages:
BIOMSG: ERROR 3012 HAS OCCURRED IN ROUTINE QOPEN

Avoidance: We have been unable to describe in modeling terms when the
erroneous method is chosen. To date the error has only been observed in two
similar models using superelements while calculating the system modes at the
residual. To prevent the incorrect method from ever being selected it is
recommended to add the following system cell to the top of the input file or to
the system rc file for all runs on V
32550
2009.0.0 (MD R4)
utput, SFM 3002, UWM 5244
Static Analysis - SDR2, GPFDR - Missing O
If a model contains many subcases with mulitple boundary conditions and the
boundary conditions are not "grouped" then UWM 5244 in GPFDR or SFM 3002 in
SDR2 may result. If the warning message is encountered wrong answers or
missing output may result.
USER WARNING MESSAGE 5244 (GPFRBI)
HAS IGNORED DATA FROM THE PG MATRIX
DUE TO INCOMPATIBILITY WITH THE UGV MATRIX
OR
*** SYSTEM FATAL MESSAGE 3002 (SDR2)
EOF ENCOUNTERED WHILE READING DATA BLOCK UG2
SUBROUTINE SDR2
(FILE 112) IN
Avoidance: Group all subcases with the same boundary condition together or
insert the following DMAP alter:
compile phase1dr
alter 'S,N,load'(2)
PARAML CASEq//'DTI'/nskip/1//S,N,subid $
load=100000+subid $
compile sestatic
alter 'PARAML CASESX'(2)
PARAML CASEsx//'DTI'/nskip/1//S,N,subid $
load=100000+subid $
compile sedisp
alter 'PARAML USET'(,-1)
PARAML CASEw//'DTI'/nskip/1//S,N,subid $
load=100000+subid $
endalter
32551
2001
IFP - SFM 4276, Error Code 7777
If integer values are used for XINIT, XLB, or XUP on DESVAR entries,
MSC/NASTRAN may fail in the IFP module with either SIGNAL 8, error 7777, or SFE
4276, EC 7777.
Avoidance: Correct the format on the DESVAR entries.
32557
70.7
ements - UFM 4562 in TRLG
Differential Stiffness - STATSUB, Superel
When performing transient analysis (SOL 109) with superelements and

differential stiffness, with STATSUB, then UFM 4562 may
be issued.
compile super3
alter 'equivx CASERS'
else if ( nocasrs1>-1 ) then $
equivx CASERS1/CASE0/-1 $ for non-SOL 200 with dynamic looping
endalter
32561
70.5.2
Frequency Response/Random Response - RAND
PS - Time Command Terminated Abnormally
An underflow error may occur on some machines when the random module squares
stress values that are numeric zeroes. If this error is encountered the job
will stop in the RANDOM module, the f06 file will not contain a message, and
the log file may contain and overflow/underflow message. The DEC ALPHA OSF/1
system issued the message:
Time command terminated abnormally.
Avoidance: Do not request random xy output for very small output quantities.
If the quantity is near 1.e-19, when it is squared for random, it can cause an
underflow to occur. Most machines will catch this and output a zero in the
results. The ALpha stops with no meaningful messages
32572
70.6
in SDR1 or UFM 7324, missing output
Superelements - SUBCASE,SUPER - UFM 5423
If there exists more subcases for a superelement than the residual structure,
then the run may fail with UFM 5423. If the load sequence number is specified
on the SUPER commands for the superelement subcases, then UFM 7324 is issued.
However, the run continues and output is missing for the extra superelement
subcases.
Avoidance: Remove the extra superelement subcases or add residual structure
subcases.
32608
70.6
Inertia relief - DMIG, UACCEL - UFM 6143
If less than 6 degree of freedom are specified on a single grid point on the
DMIG,UACCEL entry, then the job will fail with the following messages:
*** USER FATAL MESSAGE 6143, (MERGE1)

INPUT MATRICES AND VECTORS ARE INCOMPATIBLE
$
$ for v70, v70.5
$
compile statrs
alter 'UPARTN USET,UACCEL',''
IF ( NOUACCEL>=0 ) UPARTN USET,UACCEL/URAx,,,/'G'/'R'/'S'/1 $
alter 'dbstatus',''
dbstatus urax//s,n,noura $
alter 'solve '
endif $
alter 'endif \$ nullqrr',''
endalter
32609
cumentation
2001
Documentation - PARAM,UNSYMF - Missing Do
Complex eigenvalue analysis may be performed in nonlinear static analysis, SOL

106, with PARAM,UNSYMF,YES. This feature is documented in the Version 70.5
Release Guide but the PARAM,UNSYMF is not documented in the Version 70.5 Quick
Reference Guide. The parameter should be documented and referred to from the
cmethod case control command in the QRG.
32611
70.5.2
P-Elements - Beam Error Estimator
If there are beam p-elements in a model with no strain, such as rigid body
modes in modal analysis, the error estimator may crash. The EPSTOL parameter
does not work with beam p-elements so it will not help avoid this error.
Avoidance: Exclude beam p-elements from the error estimate in such models, or
turn off the error estimator.
32612
P-Elements - BEAMP - Wrong Answers at P=2
A BEAMP p-element has bad residual bending flexibility when p=2. The error is
more apparent when small values for the modulus "E" are used.
Avoidance: Set NASTRAN SYSTEM(226)=1, to turn off the residual bending
flexibility.
32615
Submittal - A "$" Sign in Command Line Argument Causes Argume
nt to be Truncated
If a command line argument contains a dollar sign ('$'), the command line
argument is truncated at the dollar sign. This probably should only occur for
NASTRAN cards encountered in RC file processing.
Avoidance: There is no avoidance for Windows NT. The error can be avoided on
UNIX by quoting the argument and escaping the dollar sign, however, a dollar
sign is a very unusual UNIX filename character.
32626
atio
Matrix Methods - DECOMP - UFM 9050 (SEKRRS) Excessive Pivot R
If negative terms occur on the factor diagonal matrix during matrix

decomposition using the SPARSE (default) solver, UFM 9050 will correctly be
printed, but the dof containing negative factors on the factor diagonal matrix
will not be identified. Terms which have factor diagonal ratios greater than
the value of PARAM,MAXRATIO will be properly identified.
Avoidance: If the problem is run using NASTRAN SPARSE=1, the degrees of
freedom with negative terms in the factor diagonal matrix will be properly
identified in the listing.
32633
70.6
s not work Properly.
ACCESS - smplr - Program to Read .xdb Doe
A dynamic factor was added for the access key in MSC/NASTRAN Version 70.5.
Thus, the program smplr.f delivered with MSC/NASTRAN Version 70.5 does not work
properly.
Avoidance: An illustration of the protocode required is:
Call READR (file,ia,0,iret)
<- when output object is open
attempt to locate entry with key=0
if ( iret.eq.0 ) then
factor = ia(2)
<- obtain dynamic factor for
access key
else
if ( approach=statics ) then
<- conventions before V70.5
more or less
factor = 1
else
factor = 10000
endif
key = intid*factor + offset
<- intid from EQEXING/E and
offset from TOL,FOL, etc.
32639
answers
70.6
Complex Eigenvalues - EIGC, HESS - wrong
The HESS method may produce one pair of roots that are wrong for diagonal input
matrices. The symptoms indicate that the shift may not be removed from the
last pair calculated. The solchk alter in the sssalter libray may be used when
it is suspected that roots may be wrong. It computes a normalized residual for
each eigenvector. Similar code is built into the complex eigensolver for
systems after v70.5. It has been confirmed that a new HESS method implemented
there has solved the two problems discovered to date that have wrong answers.
Avoidance: An avoidance is to use the CLAN method instead. In Version 70.6
and beyond this error occurs only when the old HESS method is selected by
system cell 108. An avoidance is to remove the system cell request from the
NASTRAN card. The n
32642
70.7
ting Point Exception
Complex Eigenvalue Analysis - CEAD - Floa
An error in the spill logic on "small endian" computers which include Digital
and Windows NT systems may cause a floating point exception to occur in the
complex eigenvalue solver.
The message obtained is machine dependent, one
example is:
"The FPU has been reset after floating point exception"

Avoidance: Increase the available amount of memory until spill is not
necessary. Memory on Intel NT systems can be increased above 25 mw only in
Version 70.5.
32647
70.6
P-Elements - EMA - Wrong Answers
A wrong stiffness matrix may occur if both h- and p-elements occur in the same
model, the h-element grid points use a non-basic coordinate system for
displacements, and multiple passes are required for matrix assembly. Since
some columns are output using the Basic coordinate system rather than the local
system, the matrix will be unsymmetric. The wrong answers should be evident by
high epsilon values and the spcforce resultants will not balance the applied
loads.
Avoidance: Either increase memory to avoid multiple passes or avoid the use of
displacement coordinate systems.
32660
bnormally
70.5.2
Installation - time: command terminated a
MSC/NASTRAN will fail to run if the hard limit for the system's data segment
size, see the "data(kbytes)" line of the "ulimit -H -a" command, has been set
to any value other than "unlimited".
Avoidance: Reset the hard limit to unlimited. This can only be done by root,
it will require the user to exit the affected shell.
32664
316
70.6
Random Analysis - RANDPS - UFM 5418, UFM
The RANDPS bulk data entry has an error that limits the number of RANDPS
entries that are processed. This error occurs only for the special case of
uncoupled PSDF (see remark 8 in the QRG). The error may results in various
fatal messages. Those experienced include USER FATAL MESSAGE 5418 and USER
FATAL MESSAGE 316. The text of these messages indicate that there are illegal
RANDPS entries and NO GRID POINTS IN THE MODEL. It is speculated that there is
a transition area somewhere between 100 and 320 bulk data entries where
different types of bulk data entries may be discarded, leading to many
different error messages.
This error does not apply to other types of random analysis input, where the
number of RANDPS entries that are allowed depends only on memory requirements.
Avoidance
32670
ncy Modes
70.7
P-Elements - QUADP - Spurious Zero Freque
The QUADP element may have spurious modes (more zero frequency modes than
expected) for certain values of p along the edges.
Avoidance: An avoidance is to set SYSTEM(225)=1, which turns off the bubble
functions.
32677
oes Not Exist
2001
Documentation - PARAM,EIGD - PARAM,EIDG D
In the Version 69, 70, and 70.5 Quick Reference guides the parameter
description for EIGD says:
"PARAM,EIDG,YES requests ..." But, it should say:
"PARAM,EIGD,YES requests ..." (note EIDG vs EIGD)
32685
70.5.2
- TRD1, Signal 10, Bus error
Transient dynamics - NLRGAP with SOL 109
When using the NLRGAP element in SOL 109, the job may terminate with no error
messages in the TRD1 module on some machines. Depending on the machine, the
log file may contain messages similar to the following:
Receiving signal number 10: Bus error
The FPU has been reset after floating point exception.
Avoidance: Look at the "TOTAL MSC/NASTRAN MEMORY LIMIT" in the Execution
Summary (f04 file) and increase the memory by exactly 2 words on SUN systems
and 6 words on SGI systems by specifying mem= on the nastran submittal command.
See also error 32014 before proceeding.
32705
Grids
2001
Documentation - RSPLINE - Maximum of 100
The RSPLINE has an undocumented limit of 100 grid points.

added to the next release of the Quick Reference Guide.
32707
AD)
70.5.2
A remark will be
Acoustic Analysis - CTETRA - UFM 4683 (RE
Acoustic Analysis with the 10 noded CTETRA element fails with the message:
*** USER FATAL MESSAGE 4683 (READ)
MASS
MATRIX NEEDED FOR EIGENVALUE ANALYSIS
Avoidance: Other than using the 4 noded TETRA element there is no avoidance.
32717
Bus error
Complex Eigenvalue Analysis - CEAD, EIGC - signal number 10:
If the INV complex eigenvalue method is used in version 70+ and the model
contains transfer function callout (tfl) and p-elements, then the job may fail
with one of the following error messages:
Trap encountered:
Access violation
Avoidance: Use the complex lanczos method instead of the inverse method.
32725
2004
PARAM,FIXEDB - Missing Output
Postprocessing/Component Mode Synthesis -
If PARAM,POST is set to 0 to generate an MSC/XL database and PARAM,FIXEDB,-1 is

used, the ".xdb" file will not contain the component modal results.
Avoidance: There is no avoidance. Version 2003 adds a new SOL 9 to address

this problem.
32728
70.5.2
iven is SOL 114
Cyclic Symmetry - Incorrect UWM 6231 is g
An erroneous message of the following form may appear in SOL 114:

*** USER WARNING MESSAGE 6231 (CY1CCT)
BOUNDARY CONDITIONS IN SUBCASEKKLL
ARE DIFFERENT THAN THOSE IN THE
FIRST SUBCASE.
SUBCASE
1 SPC= .001 AND MPC=
SUBCASE .001 SPC=
AND MPC= .001
USER INFORMATION: ONLY ONE BOUNDARY CONDITION IS PERMITTED FOR ALL
SUBCASES IN CYCLIC SYMMETRY ANALYSIS.
THEREFORE, THE CONDITIONS IN THE FIRST SUBCASE WILL BE
USED FOR ALL SUBCASES.
Avoidance: Ignore the message.
32731
g Answers
70.5
SSSALTERs - sebloada.v705 - Possible Wron
Due to an error in the sssalter sebloada.v705, output from the alter in

transient solutions may not be printed correctly. Rather than printing a time
history of OLOAD (boundary force), it may print only a few points with an
incorrect time step.
Avoidance: Change the alter:
change the line:
EQUIVX OL1/OUTPLIST/ALWAYS $ OUTPUT LIST
to:
EQUIVX OL1r/OUTPLIST/ALWAYS $ OUTPUT LIST
32733
External Superelements - PARAM,EXTOUT, EXTSEOUT - Ignores dif
ferential stiffness
When creating an external superelement using PARAM,EXTOUT or the EXTSEOUT case
control command, the first residual structure SUBCASE is used. This means
that it is not possible to include a static preload. See also QD 1-19045121.
Avoidance: Apply the following DMAP alter when creating the reduced
superelement:
Note: the component modes computed by the following alter do not include the
preload.
$ dmap from CR 32733; updated to V2005, llp
$ note: will not create .asm files
$ .pch file is deficient: it only contains KAAX/MAAX
$ should use with DMIGPCH only
compile phase1dr
alter 'EXTOUT0=.*EXTSEOUT' $
EXTOUT0=FALSE $ set to false to avoid processing w/o KDIFF
$
compile semodes, list
$
$ insert external superelement creation after differential stiffness is added
$
alter 'xadd5.*kaa,kdaa'
type db,gpak,gdak
CALL EXTOUT mKAA,MAA,BAA,K4AA,PA,GPAK,GDAK,
EQEXINS,USET,BGPDTS,CASES,GOT,GOQ,GM,MSF,
BSF,KSF,K4SF,CMLAMA,ECTS,SILS,UOO,CSTMS,
MPTS,DIT,ETT,EST,IBULK,VGFS,AAA/
DUM/LUSETS $
CALL PRTSUM /RSTJUNK $
EXIT $
32748
70.5.2
Documentation - Network Mounted Database
Files Affect Elapsed Time Performance
Database files that are remotely mounted will affect elapsed time performance
of MSC/NASTRAN jobs. There is no explicit documentation or user warning to
this fact.
Depending on the I/O characteristics of the job, the relative performance of
the processor, and the relative performance of the network, the penalty can be
extreme. One user saw a 24:1 ratio of elapsed time to CPU time with NFS files
and 2:1 with local files. Higher ratios would not be surprising.
32751
70.5.2
MATT4 - SFM 4276, EC 7777
Nonlinear Transient Heat Transfer - EMG,
Nonlinear transient heat transfer analysis that involves a phase change in

MSC/NASTRAN Version 70.5 may fail in the EMG module with the following
traceback:
Trap encountered:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0x00001250
0x0000059c
0x0000aeb4
0x0000054c
0x00000b68
0x000004a0
0x000000fc
0x00000948
in
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
tab_
hmat1_
ehexd_
emgbrd_
emgpro_
emg_
xsem09_
mainal
--- End of call chain --Avoidance: User avoidance is to add an additional point at the end of the
TABLEMi table.
32760
mate.generate_)
Utilities - estimate program, replication entries - UFM (esti
If the input file uses the nastran replicator to generate continuation entries,
the ESTIMATE program may fail with the following error messages:
*** USER FATAL MESSAGE (estimate.generate_bulk_entry)
In file "run1.dat", at line 26:
*1,
*2, *2
Field 10 is blank.
Avoidance: Echo the input file into a sorted nastran punch file and run the
ESTIMATE program on the new file.
32773
70.5.2
- UFM 6695 (SEGRDD)
Rigid Elements - RSSCON with ELEM option
When using the ELEM option of the RSSCON entry, the following error may result
when the shell element has a significant acute angle causing attachment to the
wrong edges of the solid:
*** USER FATAL MESSAGE 6695 (SEGRDD)
RSSCON
12 CANNOT CONNECT SHELL GRID POINT
CHECK THE GEOMETRY
*** USER FATAL MESSAGE 6695 (SEGRDD)
RSSCON
13 CANNOT CONNECT SHELL GRID POINT
CHECK THE GEOMETRY
32783
orrect Default
70.7
44 : USER ACTION,
43 : USER ACTION,
Installation/Security - flexlm, rcf - Inc
On NT systems using flexlm, the authorization code specified on the System

environment variable MSC_LICENSE_FILE (under settings/control
panel/system/environment) overwrites the rcf file but not the command line. If
you want the RC file to override MSC_LICENSE_FILE, you must lock the keyword in
the RC file. For example,
auth=what_ever_the_filename_is
lock=auth
Any attempt to set a new auth value will be silently ignored. Unfortunately,
an error in prior versions of the nastran command allowed the environment to
override a locked keyword. This error has been corrected for v70.7.
Avoidance: Either specify the authorization file on the command line or remove
the MSC_LICENSE_FILE variable from the system environment.
32784
Value
2001
Documentation - EIGC - Incorrect OMEGAAJ
Under the Quick Reference Guide description of the EIGC entry, field 3, the
OMEGAAJ-field, of the first continuation entry should be +5.6 instead of -5.6
32793
70.7
entation Violation in TRLG
Transient Analysis - LOADSET, LSEQ - Segm
In SOL 129, various computer types may fail with a segmentation fault of a
"signal" error if LOADSET-LSEQ is used to define the dynamic loadings and the
static load ids on the LSEQ entries are identical to the associated DAREA ids.
Avoidance: Always use unique ids for the static loadings and DAREA ids
32828
Parts superelements - SECONCT - Wrong Answers
External superelements at present require the presence of a seconct entry in

the main bulk data deck, and an extrn entry in the part superelement. If the
number of DOFs listed on the seconct entry is less than the number on the extrn
entry, then what is called the g-set option is being used. There is an error
in the map matrix which resequences the boundary point, leading to incorrect
assembly of the external superelement in the assembly run.
The error does not exist when the a-set option is used. For this option the
number of DOFs listed on the seconct entry is exactly equal to the number on
the extern entry.
Avoidance: If it is required to release some of the boundary dofs this can be
done by coupling them to an extra grid point in the downstream superelement,
then connecting
32829
uild
70.5.2
Beam Library - Missing bmsrv.o file for b
The main program object file for the Beam Server is missing from the
MSC/NASTRAN V70.5 CD's. This file is only needed by clients building a beam
server. If a build is attempted messages similar to the following will be
encountered:
f77 -o beamserv /big_fish/msc/msc705/hpux/bmsrv.o bsmsg.o bsbrc.o
bsbrg.o bsbri.o bsbrp.o bsbrt.o bscon.o bsgrq.o mevbr.o msbri.o msbrg.o
msbrc.o brtup.o brtui.o brtug.o brtuc.o /big_fish/msc/msc705/hpux/libbmsrv.a
-Wl,-a,archive +O3 +U77 +Oparallel_env +Onolimit +DS770 -v -lM
f77: Cannot read file /big_fish/msc/msc705/hpux/bmsrv.o
f77: Errors detected, no link
*** Error exit code 1
Stop.
Avoidance: The files will soon be available from the following URL:
ftp://ftp.macsch.com/pub/msc-products/NASTRAN/V70.5/
Select the appropriate
32837
70.5.2
mand will Fail.
Submittal - Remote Execution Via node Com
Remote execution of a nastran job using the "node" keyword will fail. A
typical error message that will appear on the terminal or window is:
ksh: 128: not found.
Avoidance: Edit <install_dir>/bin/nast705.rmt and change all four (4)
occurrences of the text "0.name" to "rcmd".
32846
External Superelements - SECONCT - Wrong answers
The g-set option allows connecting less DOFs to the downstream superelement
than exist in the boundary matrices. If the number of DOFs listed on the
SECONCT entry is less than the number on the EXTRN entry, then what is called
the g-set option is being used. The method, used to discard unwanted DOFs, is
to discard their rows and columns from the boundary matrices, which is
analogous to spcing them. This will make internal constraints in the model,
that is, spcs whose affects are visible implicitly in missing rigid body modes,
load and element force unbalance at some of the grid points, etc. but the
internal spc forces do not appear in spcforce output. Also be aware of error
32828.
Avoidance: An avoidance is to use the a-set option only. See the discussion
in error 32828 on how to
32852
Security - FLEXlm - Can't locate Multi-processors
Status: Fixed during NA_SMP upgrade of N2004.

When using FLEXlm, if the number of processors specified by the PROC entry in
the license file is less than the total number of processors on a machine,
MSC/NASTRAN will use only one processor even if more are requested.
Avoidance: Obtain a license file that allows the maximum available (or
unlimited) number of processors.
32854
2001
Documentation/Superelements - SETREE, SEL
ABEL - Entry Ignored, Incorrect SE Tree
The SETREE entry will only work if PART (BEGIN SUPER) superelements exist in
the model. If there are no PARTs in the model, the SETREE entries will be
ignored. A remark should be added to the SETREE and SELABEL entries stating
this limitation.
Avoidance: Either:
1) Change BEGIN BULK to BEGIN SUPER to force new superelement logic
or:
2) use DTI, SETREE
32858
2001
E2, GI - Poor Message
Documentation/Aeroelastic Analyis - SPLIN
If an aeroelasticity run, contains a SPLINE2 element that incorrectly

references only one grid point, the GI module issues a FATAL ERROR message with
no explanation of the cause of the error.
Avoidance: Increase the number of grids to the required two or more.
32860
70.6
Differential Stiffness - LOADSET, superel
ements, STATSUB - Wrong answers or UFM
If the LOADSET command is used in SOLs 107 through 112 with superelements and
differential stiffness (STATSUB Case Control command) then wrong answers may
occur. For example, if LOADSET is specified above the subcase, the static
loads in the static subcase are wiped out. If the LOADSET command is specified
in the dynamic subcase following the static subcase, the dynamic load
via LSEQ disappears.
Avoidance: Specify two LSEQ Bulk Data entries with the same SID and two
different DAREA IDs; one for the static preload and one for the dynamically
applied static load. The LSEQ with the smaller DAREA ID must correspond to the
static preload. The LSEQ with the larger DAREA ID must correspond to the
dynamically applied static load. Also, insert the following DMAP alter
avoidance:
c
32861
ery
70.5
Utilities - DBC.XDB missing from NT deliv
The DBC.XDB schema database was not included with the NT Version 70.5 delivery.
This will cause the ddlqry and ddlprt utilities to fail or not have access to
the Version 70.5 description information.
32864
AD - SFM 3001
70.5.2
Superelements - EXTRN, PARAM,EXTOUT, SMPY
If external superelement matrices are used in SOL 101 or 103, then the run may
fail with SFM 3001 in SMPYAD.
compile extin
alter 'smpyad xmap,x_k','mpyad
xmap,x_p'
type parm,,char8,n,name $
trnsp
xmap/xmapt $
smpyad xmap,x_k ,xmapt,,,/kxx/3////////6 $
call fname /mxx,ZUZR11/S,NAME
if ( name<>'
' ) smpyad xmap,x_m ,xmap,,,/mxx/3////1////6 $
call fname /bxx,ZUZR11/S,NAME
if ( name<>'
' ) smpyad xmap,x_b ,xmap,,,/bxx/3////1////6 $
call fname /k4xx,ZUZR11/S,NAME
if ( name<>'
' ) smpyad xmap,x_k4,xmap,,,/k4xx/3////1////6 $
mpyad
xmap,x_p,/px $
32870
70.5.2
X6 with MATT4 - UFM 4551
Nonlinear Transient Heat Transfer - CTRIA
Nonlinear transient heat transfer models that use the 6 noded CTRIAX6
axi-xymmetric element will not converge and will fail with the message:
*** USER FATAL MESSAGE 4551 (NL2CON)
Avoidance: Use the 3 noded axisymmetric element instead.
32873
70.5.2
TRIAP elements
P-Elements/Plotting - Wrong VUGRID ID for
The VUGRID id for TRIAP elements may be output as zero. This will cause
missing points in deformation plots.
32884
70.7
with MATT4 - Wrong Answers
Nonlinear Transient Heat Transfer - CBEND
The CBEND element produces wrong answers in nonlinear transient heat transfer
analysis.
Avoidance: Use the CBEAM element.
32890
70.6
mbered Fatal Message
Aeroelastic Analysis - GI, SPLINE2 - Unnu
Spline checking improvements made in V70.5 can result in erroneous and

unlabeled "FATAL ERRORs" out of the GI module. These errors occur if a SPLINE2
is attached to a single grid point (a situation that can produce a singular
spline matrix). Due to the code error, ANY SPLINE2 with a single structural
grid point will generate the singularity fatal, whereas those attached to a
single grid point for both translation and rotations will produce the correct
results. Unfortunately, a secondary error causes the message to be lost; hence,
the unlabeled FATAL.
Avoidance: In the case of a single grid point accounting for both translation
and rotations, in order to avoid the erroneous fatal message, RBAR another GRID
to it. The other GRID has no use in the analysis, but just allows the model to
a
32899
70.6
AUTOSPC,NO - SFM 3001, SFM 3002
Eigenvalue Analysis - EIGRL, READ, PARAM,
A model which contains degrees of freedom with no mass or stiffness may cause
the Lanczos eigensolver to fail with one of the messages below. The most
likely cause for this is submitting a model with PARAM,AUTOSPC,NO. This error
is also likely in cyclic problems with solid elements and points on the axis of
symmetry since these points are unaffected by PARAM,AUTOSPC,YES and are
singular in the rotational degrees of freedom.
*** SYSTEM FATAL MESSAGE 3001 (READ)
13 DOES NOT EXIST.
1. THE DATA BLOCK IS UNSPECIFIED ON THE DMAP MODULE.
2. THE DATA BLOCK IS SPECIFIED ON THE DMAP MODULE AND ON THE SUBDMAP
STATEMENT
BUT NOT ON THE CORRESPONDING
32901
70.5.2
, TABK - Possible Wrong Answers
Nonlinear Transient - NLRGAP, AUTO, TSTEP
When using the NLRGAP element, if the gap stiffness varies as a function of
time, and either the AUTO or TSTEP method is selected on the TSTEPNL entry,
then the answers may be incorrect.
Avoidance: Use the default ADAPT method.
32906
- Poor Message
Aeroelastic Analysis - SPLINEi Referencing Non-existent GRID
If an aeroelastic model is created in which a SPLINEi entry references

non-existent aerodynamic grid points (boxes), a misleading error message is
issued in which the missing box id's are correctly listed, but the the message
associates them to a SET1 or SPLINE3 entry that is, itself, nonexistent.
Furthermore, the SET1/SPLINE3 association is only applicable to missing
structural grids and, in this case, it is the aerodynamic grids that are
missing. These data are on the SPLINEi entry and not on the SETi entry.
32909
wers
Nonlinear Transient Heat Transfer - PARAM,AUTOSPC - Wrong Ans
The default for PARAM,AUTOSPC is NO for the nonlinear solution sequences, this
includes solution 159 for nonlinear transient heat transfer. This is because
AUTOSPC only acts on the linear portion of the kgg matrix and thus if it was
YES it could lead to wrong answers. To prevent possible wrong answers, Version
70.5 ignores a YES setting for AUTOSPC. The correct action would be for
AUTOSPC to act on the sum of the kggl and the kggnl matrices. The correction
of this error will be to take this action.
Avoidance: Do not use the PARAM,AUTOSPC,YES in transient heat transfer
analysis. Identify any isolated/disjoint grids and constrain them.
32917
2001
Superelements/Plotting - SET, INCLUDE - A
ll Elements Plotted instead of Subset

When using superelements, any plot request which references a set definition
using the INCLUDE option to select elements will plot the entire superelement.
Avoidance: Use the EXCEPT feature. Example:
SET 1 = ALL EXCEPT QUAD4
32929
UFM 2105
$ will plot all elements except QUAD4s.
2001
Documentation - P-Elements, PLOAD2, GP3 -
The MSC/NASTRAN Quick Reference Guide does not state that the PLOAD2 may not be
applied to p-elements. If a PLOAD2 references a p-element the message:
PLOAD2 CARD FROM LOAD SET xxx REFERENCES MISSING OR NON-2-D ELEMENT OR
HYPERELASTIC PLANE ELEMENT
yyy
will be encountered.
receive UFM 2105 stating that the loading references a missing or non 2-d
element or hyperelastic element.
Avoidance:
Use a PLOAD4 to load p-shells.
32931
Wrong Answers
Restarts - MATi, RESTART - Restarts Ignore Material Damping,
If a restart is performed from solution 106 (nonlinear static analysis) to

solution 108 the GE field of the MAT1 entry is ignored.
Avoidance: Specify PARAM,G damping instead.
32937
8, UFM 4574
70.6
Optimization/Design Sensitivity - UWM 905
If the direct sensitivity method is used in one iteration and then the adjoint
method is selected by the program in a subsequent iteration, then the run will
fail with the following messages:
^^^ USER WARNING MESSAGE 9058 (FEA)
^^^ THE
PSEUDO SOLUTION AND THE PSEUDO LOADS FOR THE RESIDUAL
STRUCTURE
AND THE CURRENT SUBCASE ARE ZERO.
*** USER
FATAL
MESSAGE 4574,
DATA RECOVERY STARTED BUT NO DISPLACEMENT VECTORS AVAILABLE
compile pslgdv
alter 'isolapp\=1'
psload=false $
endalter
32938
70.5.2
P-Elements - TEMP, TEMPF - Wrong Answers
If a model with p-elements has both TEMPF and TEMP entries, a solid element
without a TEMPF entry will be assigned the default temperature, rather than
using the nodal TEMP temperatures.
Avoidance: A workaround is to use all TEMPF or all TEMP entries to assign
temperatures.
32944
ocumentation
2001
Documentation - PARAM,FLUIDSE - Missing D
The parameter fluidse is only documented in the Version 70.5 Release Guide, it
is not documented in the Version 70.5 Quick Reference.
Prior to Version 70.5 the fluid-structure analysis capability required that all
fluid elements and all points (structure and fluid) at the fluid-structure
interface be in the residual structure. With this parameter the structure
points may now be assigned to upstream superelements.
32945
Miscellaneous - BEGIN BULK - Wrong answers
The BEGIN BULK command may contain the words SUPER=seid or AUXMODEL=auxmid. If
any other word is input, then the BEGIN BULK command is not recognized as a
delimiter and no related fatal or warning message is issued.
32951
Mid-Side Nodes
Nonlinear Analysis - CGAP - Poor Answers when GAPs used with
GAP elements do not work well with elements with midside grid points.
Irregular stresses will be produced in elements near the GAPs. This problem is
severe when quadrilateral faces are involved (HEXA-20) and moderate when
triangular faces are used (TETRA-10).
Avoidance: Use elements without midside nodes.
32960
e
70.5.2
Restarts - GP2 and MCE2 - Poor Performanc
In the static solution sequences; e.g., SOLs 101, 114, 106, MCE2 may be
reexecuted unecessarily during a restart. In SOLs 101-200, GP2 is reexecuted
unecessarily.
Avoidance: Insert the following alter in all runs including the restart:

compile sekmr
alter 'ENDIF \$ SEMR'(,-1)
else if ( statics ) then $
purgex /goq/-1 $
compile phase0
alter 'gp2 ',''
GP2
GEOM2,EQEXIN,EPT,geom2a,epta/ECT,ecta/S,N,ACOUSTIx $
alter 'fscoup\=',''
FSCOUP=(ASCOUP='YES' AND ACOUSTIx=2) $
endalter
32961
4276 EC 1044
70.6
Aeroelastic Analysis - AMP, RESTART - SFM
A restart into SOL 146 from SOL 103 may fail with SYSTEM FATAL MESSAGE 4276,
ERROR CODE 1044 in the AMP module.

Avoidance: If this error occurs, it is because the spline matrices are not
being generated on the restart, insert the following DMAP alter.
compile phase1a
alter 'aspline'(,-1)
delete /gpjk,gdjk,,, $
32972
eter Ignored
70.5.2
P-Elements - PARAM,PEDGEP, FEEDGE - Param
If PARAM,PEDGEP,1 is specified in the bulk data file, the POINTs on the FEEDGEs
are not re-parameterized. This parameter only applies to cubic edges; for
quadratic edges, the parameter is ignored.
Avoidance: There is no avoidance; however, it is unlikely that this
inconsistency would negatively affect answers.
32973
ts
SSSALTERS - alter2ga, alter2ha - Potential Inefficient Restar
In some instances, a restart from a run using alter2ga.vxx or alter2ha.vxx may

try to "re-process" the superelement brought in using the alter. The cause of
this is under investigation.
Avoidance: Insert the following DMAP into the run which is failing (not the
run with alter2ga or alter2ha). BEWARE - this DMAP will cause the program to
ignore any changes made in the model during a run which uses it.
compile chkgoaq
alter 3,3 $
$
compile phase0
$ alter 581,585 $ V70
alter 694,697 $ V70.5
32979
2001
issing Remark from PAERO2 Entry
Documentation - Static Aeroelasticity - M
The following remark needs to be added to the Quick Reference Guide for the
PAERO2 bulk data entry as follows:
Remark:
8. For half models, the theta arrays LTH1 and LTH2 should encompass a full 360
degree range.
32981
70.5.2
If NSM (non-structural mass) is

result. The NSM is interpreted
unit area. This leads to wrong
eigenvalues and static response
P-Elements - PSHELL, NSM - Wrong Answers

used on shell p-elements wrong answers may
as mass per unit volume instead of mass per
answers in the Grid Point Weight Generator,
due to gravity loads.
Avoidance: The only avoidance is to adjust NSM to take into account the
thickness of the element.
32983
70.7
Superelements - SEBULK - SFM, EC 1044 IN
FILPS2
When a sebulk entry references a seid that is not on a begin super entry, the
following system error occurs:
BIOMSG: ERROR 1044 HAS OCCURRED IN ROUTINE FILPS2
A log file message also appears, with a machine-dependent message.
32987
6985
70.5.2
Nonlinear Analysis - CBUSH1D, SDR2 - SFM
The BUSH1D element when used in Nonlinear Statics (106) will abort in the SDR2
module when STRESS data recovery is requested.
The fatal message is shown
below.
*** SYSTEM FATAL MESSAGE 6985 (SDR2RD)
PREVIOUS ELEMENT-ID =
101
DID NOT REQUEST CORRECT NUMBER OF PHASE-1 OUTPUT WORDS.
0FATAL ERROR
Avoidance: An avoidance is to request the BUSH1D data recovery with the
NLSTRESS Case Control Command and to EXCEPT the range or BUSH1D elements from
the STRESS Case Control Selection.
32991
70.0.5
RFORCE - SFM 3002, TAFF
Nonlinear Analysis - PARAM,FOLLOWK, GRAV,
SOL 106 Follower forces. EOF ENCOUNTERED WHILE READING DATA BLOCK (NONE)
(FILE
0) IN SUBROUTINE TAFMEG
In nonlinear analysis, solution 106, when follower forces are used and there
are GRAV and/or RFORCE inertial loads, the job may fail in the TAFF module with
the message:
EOF ENCOUNTERED WHILE READING DATA BLOCK (NONE) (FILE 0) IN SUBROUTINE TAFMEG.
Avoidance: A DMAP avoidance is under investigation. Currently there is no
practical avoidance other than inserting PARAM,FOLLOWK,NO or removing the
inertial loads. Although this error exists in Version 70.5.0 (it was fixed in
70.5.2) the error correction was taken to Version 70.0.5 for NASTRAN for
Windows. Therefore, the fixed version has been changed to 70.0.5 under the
assumption that all 70.5 cl
33006
70.5.2
Frequency Response Analysis - MPYAD, SOLs
108, 111, 146, 200 - Poor Performance
The MPYAD module in subDMAP FREQRS for frequency response analysis that is used
to compute the PDF matrix does not take advantage of the tendency of the
dynamic load matrix to be very sparse and this leads to poor performance.
compile freqrs
alter 'mpyad '(,-1)
trnsp ppf/ppft $
matmod ppft/vppf/12/s,n,nullppf/1 $
if ( nullppf>-1 ) then $
partn
ppf,,vppf/ppf1,,,/1 $
partn
rpx,,vppf/rpx1,,,/1 $
mpyad
rpx1,ppf1,/pdf/1 $
else $
alter 'mpyad '
endif $
endalter
33012
SFM 6804
2001
Superelements - SPCs on Boundary Grids -
If a boundary (exterior) point for a PART (BEGIN SUPER = i) superelement is

constrained, then the fatal message below will be issued if different
displacement coordinate systems are used for the coincident GRID points.
SYSTEM FATAL MESSAGE 6804 (BNDSP3)
THE DISPLACEMENT COORDINATE SYSTEM (CD FIELD ON GRID ENTRY) SPECIFIED FOR
BOUNDARY GRID ID 4 B
IN SUPERELEMENT 1 IS NOT CONGRUENT WITH DISPLACEMENT COORDINATE SYSTEMS IN
OTHER CONNECTING SUPERELEMENTS.
Avoidance: Either apply the constraints in the downstream superelement (the
one which has the coincident point as an interior point) or use the same
displacement coordinate system on all of the points which are coincident.
33016
2001
Documentation/QRG - SEEXCLD
The Quick Reference Guide description for the SEEXCLD entry states that
SEIDA(field 2) must be larger than zero. A value of 0 (zero) is also allowed.
Also, the thru range is indicated as 61<62 it should be GIDA1<GIDA2
33023
Superelements - SEPLOT - No Contour Plot Output
Currently, the SEPLOT module does not support contour plots of superelements.
33026
70.7
PARTN) from CALCV
Nonlinear Buckling Analysis - UFM 3007 (U
A nonlinear buckling analysis will fail in the NLSTATIC module with the
message:
ILLEGAL INPUT TO SUBROUTINE CALCV
if the run contains superelements and there are no spc or mpc sets in the
residual structure.
Avoidance: Apply the following dmap avoidance:
compile nlstatic
alter 'upartn.*dugni.*dulv'(2),'upartn.*dpgni.*dpl0'
paraml usetnl//'uset'//////'G'/s,n,Gsize/'L'/s,n,Lsize $
message //'debug: from UsetNL, G-size is '/Gsize
message //'debug: from UsetNL, L-size is '/Lsize
if(Gsize = Lsize) then
message //' fyi: copying dugni --> dulv, dpgni --> dpl0'
equivx dugni/dulv/-1 $
else
message //' fyi: doing normal upartn on DUGNI and DPGNI'
UPARTN
endif
endalter
USETNL,DUGNI/DULV,,,/'G'/'L'/'M'/1 $
33027
- Incorrect ID
2001
On CRAY systems DEQATN id's may be printed incorrectly in error message output.
33045
2004
ETi - Wrong Answers at Omitted DOF
Nonlinear Analysis - CGAP, TEMP(LOAD), AS
Nonlinear analysis in Version 70 and 70.5 systems with multiple subcases,

thermal loads, asets and gaps will give erroneous results at omitted degrees of
freedom in the first printed load increment in the second subcase. If
intermediate load increment results are not requested, the errors will occur in
the final subcase.
Avoidances:
1)Use the following alter:
===========================================
COMPILE NLSTATIC $
ALTER
'SOLPRE=SOLCUR-1', 'SOLPRE=SOLCUR-1' $
ENDALTER $
===========================================
2) Set INTOUT=YES in the NLPARM bulk data card,
3) use a version prior to 70.
4) Do not use SOL 106 with O-set in the resudual, in V2001.
33075
70.7
Superelements - SECONCT - Wrong Answers
If coincident grid points exist in a superelement and a SECONCT entry is used

to connect one of them to a grid point in another superelement, it is possible
that the SECONCT entry will not work properly and incorrect answers will
result. If no SECONCT is used, then the program will correctly issue UFM 6794
Avoidance: Review the "BOUNDARY SEQUENCE ASSIGNMENT TABLE" for grids that are
attached to multiple downstream GRIDS instead of the usual one to one
correspondence. Do not create coincident grid points in a superelement where
BEGIN SUPER is used.
33076
gnal 10
70.5.2
Buckling - EIGRL, READ - UFM 4276 7777 si
It is possible that the new Lanczos eigensolver may terminate with a

machine-dependent error (signal 10 on an HP) followed by
BIOMSG: ERROR 7777 HAS OCCURRED IN ROUTINE RECOVR in the READ module.
Avoidance: For the model that demonstrated this error, adding V1 and V2 on the
EIGRL entry in addition to the ND specification allowed the problem to be
solved. Setting SYSTEM(273)=1 to select the old Lanczos method will allow the
problem to be completed.
33078
rap
70.7
DMAP - CALL DBSTORE - Fails with Signal T
If CALL DBSTORE and DIAG 47 are used then the run will fail with a hard crash
in the PARAML module.
Avoidance: Remove DIAG 47 or insert the following DMAP alter:
compile dbstor
alter 't6',''
type parm,,i,n,t6 $
endalter
33080
70.7
IOMSG: ERROR 1044
Nonlinear Transient Analysis - NLTRD2 - B
If a nonlinear transient analysis has only stiffness, but no mass or damping

the job may fail with the message
0
STATUS =
0
in NLTRD2.
Avoidance: Add appropriate damping and mass to the model.
33101
6498
2001
Nonlinear Transient Analysis - TRLG - UWM
Module TRLG issues the following message if a nonlinear transient analysis has
a DLOAD command which refers to non-existant TLOADi entries:
Check call to MSGPOP from TRLG with the message number 3031
Parameter 1 is
111
Parameter 2 is DLT
Parameter 3 is TRLG
Avoidance: Remove references to non-existant loadings on the DLOAD entry.
33108
2001
Documentation/Buckling - EIGRL - UFM 4405
The Lanczos buckling shift logic in MSC/NASTRAN Version 70.5 was enahanced.
The enhanced code allowed many outstanding difficult problems to be solved
without resorting to adjustments of the EIGRL entry. However, a very unusual
case has been found that gives the Lanczos new shift logic trouble, wheras the
old Lanczos shift logic solved the problem. The problem case occurs when there
are on the order of thousands of eigenvalues below 1. and there are on the
order of thousands of eigenvalues in the frequency range of interest. The old
Lanczos shift logic would shift near V1 first, thus if ND was specified and
there were ND roots near V1, the old shift logic would solve the problem. The
new shift logic has a tendency to shift near 1. first or V2 if V2 is less than
1. The new logic solve
33113
70.6
OMSG: ERROR 3021 from FILPS2
Documentation/Superelements - CSUPER - BI
Although the documentation does not specifically state so, a superelement which
is a copy (mirror or otherwise) of another superelement may not be copied or
mirrored. Version 70.6 addresses this error by issuing a more meaningful fatal
message.
Avoidance: If additional copies are required, make more copies of the original
superelement.
33118
ng
70.5.2
Installation - IRIX 6.5; libblas.so missi
MSC/NASTRAN Version 70.5 does not run on IRIX 6.5 with a standard operating
system configuration. Error messages such as those shown below will be
encountered:
MSC/NASTRAN V70.5 (Silicon Graphics IRIX64 6.5) Fri Aug 21 20:11:26 1998
MSC/NASTRAN beginning job test. PID: 4669.
jever 5% 4735:/msc/msc705/irix64/analysis: rld: Fatal Error: Cannot
Successfully Map soname 'libblas.so' under any of the filenames
/msc/msc705/irix64/libblas.so:/usr/lib64/libblas.so:/usr/lib64/internal/libblas.
so:/lib64/libblas.so:/opt/lib64/libblas.so:/msc/msc705/irix64/libblas.so.1:/usr/
lib64/libblas.so.1:/usr/lib64/internal/libblas.so.1:/lib64/libblas.so.1:/opt/lib
64/libblas.so.1:
Avoidance: If the client does not have a complete set of sgi math libraries
they will need to get a /usr/lib64/mips4/libco
33119
wers
70.6
Elements - TRIAX6, TEMP(LOAD) - Wrong Ans
The TRIAX6 element gives incorrect stresses if THETA (see CTRIAX6 entry) is
nonzero, and there is thermal expansion. The deflections are not affected.
The THETA field is most likely used for MAT3 orthotropic materials.
Avoidance: The only known avoidance when there is thermal expansion, is to
input the material properties in the r-z system, so THETA is zero.
33121
70.5.2
ystem, Wrong Answers
P-Elements - BEAMP - Element Coordinate S
If the curvature of a beam p-element exceeds 90 degrees, the element coordinate

system may reverse itself. For a beam with a symmetric cross section, this
will probably only affect the data recovery points.
Avoidance: Use beam p-elements that have a curvature of less than 90 degrees.
33131
Iterative Solver - P-Elements, Solvit - UFM 4157
The iterative solver may fail without issuing a meaningful message if the
model contains adaptive p-elements. USER FATAL MESSAGE 4157 may be issued
indicating insufficient memory; however, the message may not indicate the
amount of memory required or it may indicate an incorrect amount.
Avoidance: The failure may be the result of insufficient memory. Thus,
increasing memory may solve the problem. If increasing memory does not solve
the problem, then do not use the iterative solver.
33171
Elements - CBUSH1D, SHOCKA - No Warning Message
By design intent NASTRAN allows the unmodified CBUSH1D element to be used in a
linear static analysis where the linear initial stiffness is used. However,
the SHOCK option has no stiffness and NASTRAN does not issue a warning message.
33181
NEC V70.5.1
70.5.2
Performance - SDR2 - Poor Performance on
The SDR2 module in V70.5.1 on the NEC system may be up to 60% slower than in
V70.0.
Avoidance: The problem has been fixed in Version 70.5.2.
33186
Nonlinear Analysis - RESTARTS - SFM 4252
Nonlinear analysis restarts may fail with the message:

^^^ PHASE 1 - SUPERELEMENT GENERATION, ASSEMBLY AND REDUCTION.
*** SYSTEM FATAL MESSAGE 4252 (SEMA)
MATRIX XAAV
FOR UPSTREAM SUPERELEMENT
10 DOES NOT EXIST.
USER INFORMATION: THE CURRENT SUPERELEMENT REQUIRES ALL OF IT'S UPSTREAM
SUPERELEMENT MATRICES
FOR ASSEMBLY INTO THE CURRENT SUPERELEMENT. THE
PROBABLE CAUSES ARE:
1. THE UPSTREAM SUPERELEMENT'S DBSET OR DATABASE IS
NOT ATTACHED.
2. THE UPSTREAM SUPERELEMENT DID NOT COMPLETE
REDUCTION IN A PREVIOUS RUN.
Avoidance: This problem is still under investigation but is believed to occur
when temperature loads are applied in the cold start with TEMP(INIT) but are
removed in the RESTART.
33192
2001
upports ANALYSIS=BUCKLING
Documentation - STATSUB in SOL 200 only s
Remark 1 of the MSC/NASTRAN Version 70.5 Quick Reference Guide's description of

the STATSUB command indicates that STATSUB is supported in SOLs 103, 105, 107
through 112 and 200. However, the support in solution 200 is limited to
ANALYSIS=BUCKLING.
33202
2001
ues. - GKAM - Wrong Answers
Modal Response Analysis, Complex Eigenval
It has been found that a very low memory request may result in poor complex
eigenvalues being produced when using the modal method or poor answers in a
modal response. In the case that demonstrated the problem the memory was set
to one million words, well below the default of four million words. The one
million word value was barely above the minimum needed for subroutine xspace.
This error is not expected to occur if more than 1mw of open core memory is
available to nastran, which is the case if the default memory and buffsize are
used. The error appears to have occurred in the GKAM module which assembles
the modal matrices.
Avoidance: Make sure that sufficient open core memory is available.
33233
ong Answers
70.6
Inertia Relief - SUPORT, PARAM,INREL - Wr
If an inertia relief analysis in solution 101 or 200 specifies less than six
suport degrees of freedom in Version 70.5 of MSC/NASTRAN, then wrong answers
may result.
Avoidance: Apply the following dmap alter or use solution 1.

COMPILE STATRS
ALTER 'upartn ','fbs '
UPARTN USET,DRG/D6T,,,/'G'/'T'/'S'/2 $
TRNSP
D6T/DT6 $
MPYAD
DT6,DT6,/D6T2/1 $
MODTRL D6T2////6 $
DECOMP D6T2/LD6T2,,////////1.+8/16 $
MATGEN ,/IRR/1/NORSET $
UMERGE USET,DM,IRR/DML/'T'/'L'/'R' $
MPYAD
DT6,DML,/DT6TDML/1 $
FBS
LD6T2,,DT6T/CRYY $
compile inersen
alter 'upartn ','fbs '
UPARTN USET,DRG/D6T,,,/'G'/'T'/'S'/2 $
TRNSP
D6T/DT6 $
MPYAD
DT6,DT6,/D6T2/1 $
MODTRL D6T2////6 $
DECOMP D6T2/LD6T2,,////////1.+8/16 $
MATGEN ,/IRR/1/NORSET $
UMER
33239
esults
70.5.2
Nonlinear - GPSTRESS, QUAD4 - Incorrect r
In a nonlinear analysis with PARAM,LGDISP,1, the grid point stress (GPSTRESS)

output for grids attached to CQUAD4 elements with a STRESS(CORNER) request will
be incorrect. Values of 1.0E+30 are printed for all components.
Avoidance: Do not request STRESS(CORNER) and GPSTRESS in the same run.
33242
70.6
UFM 5423 in AMP module
Aeroelastic Analysis - SOL 145 restart -
Restarts into SOL 145 or 146 may fail with UFM 5423 in the AMP module.
compile phase1dr
alter 'call phase1a'(,-1)
delete /gpjk,gdjk,gdak,gpak, $
delete /gpgk,gdgk,,, $
compile pfaero
alter 'DELETE \/D1JK,D2JK',''
DELETE /D1JK,D2JK,wskjf,, $
endalter
33272
70.6
inite Mass Matrix, Wrong Answers
Eigenvalue Analysis - READ, REIGL - Indef
If the mass matrix is indefinite, then the roots coming out of Lanczos may not
be correct. A symptom of this error is the issuance of the following error
messages:
COMPUTED IN A (PARTIAL) INTERVAL
FOUND xxx MODES BETWEEN aaaa HZ AND bbbb HZ BUT THERE SHOULD BE ONLY yyy
MODES.
Note that in almost all cases, an indefinite mass matrix is caused by modeling
errors. Starting in Version 70.6, the job will terminate with the fatal
message below if an indefinite mass matrix is encountered.
USER FATAL MESSAGE 4646 (REIG)
THE MASS MATRIX INPUT TO THE REAL EIGENSOLVER IS INDEFINITE.
USER ACTION: REMOVE THE NEGATIVE MASS TERMS.
If GDR is being used (DYNRED) it is possible that poor numerics (very s
33274
70.6
Superelements - SFM 5423
Coupled Fluid/Structural Analysis - Fluid
If PARAM,FLUIDSE,>0 and any structural grid points or SPOINTs are assigned

interior or exterior to the fluid superelement then SFM 5423 may be issued.
Avoidance: Ensure that no structural points appear in the interior and
exterior point list for the fluid superelement. This can be verified in the
printout of the superelement map. This includes generalized coordinates used
for component mode synthesis on the fluid superelement. The seqset1 should be
input on fluid points (grid, CD=-1) rather than scalar points.
33285
Plotting - Aeroelastic Elements - Missing Plot Output
Beginning in Version 70.5 the NASTRAN plotter no longer supports aeroelastic

elements.
Avoidance: The only avoidance is to use Version 70 or PATRAN Version 8.1 which
is due out by the end of this year.
33299
70.7
P-Elements - QUAD4 - Poor Answers for p=1
The QUAD4 p-element may be too stiff when p=1 on some edges. This is most
noticible for coarse meshes. An avoidance is to specify p >= 2.
33307
5267
70.6
Aeroelastic Analysis - AELINK, TRIM - UFM
The above message was produced by a client whose length units was millimeters
and mass units were kilograms. The trim matrix became singular in this case,
apparently because of the dynamic range within the equations to be solved.
*** USER FATAL MESSAGE 5267 (ASGLD)
ZXX MATRIX IS SINGULAR. TRIM AND AELINK ENTRIES SPECIFY AN INADEQUATE
CONSTRAINT SET.
Avoidance: In this case, the problem was avoided by scaling the ZZX and PZ
matrices going into the trim module by 1.0e-4. This avoidance is likely to be
problem dependent, so other factors may be required in other cases. The alter
to perfrom the scaling is:
compile aestatrs
alter 'asg'(,-1)
add zzx,/zzxs/1.0e-4 $
add pz,/pzs/1.0e-4
delete /zzx,pz,,,/ $
equivx zzxs/zzx/always $
equivx pzs/pz/always $
A more general
33308
Sequencing - SEQP - Memory Allocation Error
Very large problems that use the metis method of sequencing (system(206)=8)
may fail with a memory allocation error as follows:
*** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)
MALLOC FAILED INSIDE METIS. DECREASING THE MEMORY GIVEN TO THE JOB WILL
INCREASE THE MEMORY AVAILABLE FOR MALLOC.
DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD
Dynamic memory starts at address 000000008BE56940
*** Opencore memory reduced to
49791588 ***
Metis Error: ***Memory allocation failed for CreateCoarserGraph: gdata.
Requested size: 21237992 bytes
Avoidance: There is no guaranteed avoidance. Decrease the memory or use
another sequencing method. Requesting system(206)=72 requests the metis method
with a different pre-phase t
33309
2001
MIGPCH - UFM 327
External Superelements - PARAM, EXTOUT, D
When using the external superelement capabilities with the

"param,extout,dmigpch" option in a SOL 103 run, the header entry for the load
PAX will also be written out, even though it is not used. This will cause the
issue of the following error messages in a subsequent attachment run.
*** USER FATAL MESSAGE 327 (IFS2P)
BAD DATA OR FORMAT OR NON-UNIQUE NAME. DMIG PAX
COUNT =
161
IFP,
SORTED CARD
Avoidance: Remove the offending PAX header. This entry is not used in a SOL
103 run.
33334
2001
Documentation - DEQATN - Increased Limit
The number of allowable non-blank characters for the DEQATN entry was increased
from 12,500 to 32,000 in Version 70; however, the Quick Reference was not
updated to reflect this.
33367
- UFM 316
70.6
Optimization/Design Sensitivity - DESVAR
The message:
ILLEGAL DATA ON BULK DATA ENTRY DESVAR xx SORTED ENTRY COUNT = yy
was produced when a DESVAR punched at the end of an optimization task had an
XINIT that was very slightly less than the XLB value. When a new run is
attempted, an equality test is used to see if the input satisfies XINIT .ge.
XLB and the entry is rejected even though it had been produced in a previous
run.
Avoidance: Manually reset any punched DESVAR values to satisfy the relations
XLB .LE. XINIT .LE. XUB
33401
2008.0.0 (MD R3)
UFM 9015, Poor Message
Case Control - SEALL, SEMG, SEKR, etc. -
If the SEALL, SEMG, SEKR, SELG, SELR, or SEMR command is specified in a subcase
which is not the first subcase then the operation requested by that command is
not performed and various messages or wrong answers may result. For example,
with SEALL or SEMG then UFM 9015 will be issued.
USER FATAL MESSAGE 9015 (SEMODES)
THE USET TABLE IS NOT PRESENT.
Avoidance: Specify SEALL, SEMG, SEKR, SELG, SELR, or SEMR above all SUBCASE
commands.
33424
70.6
- UFM, Incompatible Matrix Multiply
Aeroelastic Analysis - SPLINEi, AESTATRS
An incompatible matrix multiply can occur in calculating the intercept hinge

moment coefficients if the aerodynamic forces are splined only to dependent
degrees of freedom (e.g., to m-set and r-set points).
Avoidance: A DMAP workaround is to include the following alter:
compile aestatrs $
alter 'add *uintl','add *intl' $
type parm,,i,n,nointl $
dbstatus uintl//s,n,nointl $
if ( nointl < 1 ) then $
PARAML ALX//'TRAILER'/2/S,N,NOLSET $
MATGEN ,/MUNTL/7/NOLSET/1 $
MATGEN ,/MINTL/7/NOLSET/1 $
else $
ADD
UINTL,/MUNTL/-1.0 $
ADD
INTL,/MINTL/-1.0 $
endif $
endalter $
33427
70.6
PYAD - SFM 5423
Aeroelastic Analysis - AELINK, RESTART, M
An error in the dependencies results in restarts into solution 144 where only
the AELINK entries have been changed failing with SYSTEM FATAL MESSAGE 5423
indicating an attempt to multiply incompatible matrices:
SYSTEM FATAL MESSAGE 5423 (DMPYAD)
TRAILER FOR WSKJ
IS 101
40
80
2
2
4 250
TRAILER FOR FFAJI
IS 102
7
40
2
2
80 10000
TRAILER FOR FFINT
IS 103
2
80
2
2
0
0
Avoidance: Do not attempt restarts when only changing AELINK bulk data
entries. A simultaneous change in the aerodynamic model geometry will enable
the restart, but this would also entail recalulation of the aerodynamics. Alter
33454
2001
Complex Lanczos is not the Default
Documentation - EIGC, SYSTEM(108) - Block
The more modern and reliable Hessenberg which supports spill was made the
default in Version 69 by switching the meaning of system(108)=0 and 1.
However, the documentation was never updated to reflect this change.
Furthermore, because of poor performance for some problems the new Block
Complex Lanczos was not made the default in Version 70.5. Although this
decision is reflected in the release notes the decision was made too late to be
reflected in the Quick Reference Guide's description of system(108) under the
NASTRAN command and EIGC entry.
33476
70.6
Miscellaneous - Elapsed Time Incorrect
The elapsed time will be incorrect if more that 24 hours are spent in any one
module.
33480
70.6
POST - Missing output
Postprocessing - SOL 1 through 16, PARAM,
No results will be written to the .op2 or .xdb file if PARAM,POST is specified

in SOLs 1 through 16 where SORT2 is the default output format or in all SOLs if
SORT2 is explicitly requested.
Avoidance: Insert the following DMAP alter in any SOL 1 through 16:
compile sol__ $ insert SOL number for __
alter 'IF (POST=0) THEN'(,-1)
LABEL
LNOSORT1 $
alter 'LABEL
LNOSORT1',''
endalter
33481
d
70.6
Estimate - SPC - Undefined GRID reference
When an SPC references an SPOINT, the estimate utility may indicate that a
undefined GRID has been referenced.
33491
- UFM 7115
70.6.1
Optimization/Design Sensitivity - CAABSF
The acoustic absorber element (PAABSF) is not supported in optimization and

design sensitivity (SOL 200). If a PAABSF entry is included in the bulk data,
even if it is not one of the design variables, the following message is issued,
" *** USER FATAL MESSAGE 7115 (DOM2B) PTYPE 1502 15 IS NOT SUPPORTED".
Avoidance: Do not include PAABSF entries in an optimization run.
33495
in xdb
Postprocessing/Random Analysis - PARAM,POST,0 - Missing Data
The results from a response spectrum spectrum analysis are not written into the
".xdb" file when PARAM,POST is set to 0.
Avoidance: Set PARAM,POST,-1 and they are written into the OUTPUT2 file.
Fix being imported via 38537.
33499
Elements - PSOLID - Spurious Modes
Spurious hourglass modes have been observed when solid elements refer to an
anisotropic smeared material property that has a modest shear modulus, but
almost zero extensional modulus.
Avoidance: Put ISOP=1 on the PSOLID record for these elements.
33500
rference Groups
Static Aeroelastic Analysis - Wrong Answers for Multiple Inte
If multiple interference groups are used with bodies in any interference groups
except the last one and control surfaces exist, the DJX matrix generated by ADG
(adgdjx routine) is corrupted.
Avoidance: Specify a single interference group.
33517
Installation - Missing FLEXlm Installation Documentation
The Version 70.5 Configuration and Operation Guide for NT does not discuss the
installation of the FLEXlm license manager. This software is provided on the
Version 70.5 NT CD but must be installed separately. Please see the
"install.htm" on the NT-CD itself for installation instructions.
33527
5
70.6
Iterative Solver - ITER, JACOBI - SWM 671
An error in the iterative solver for real-unsymmetric problems using the

default Jacobi preconditions may lead to poor convergence and the message
below:
*** SYSTEM WARNING MESSAGE 6715 (SUCGRD)
THERE IS A ZERO DIAGONAL TERM IN COLUMN 1 OF DATA BLOCK CEE WHICH WILL BE
REPLACED BY 1.0
IN THE PRECONDITIONER.
USER ACTION: IT MAY BE BETTER TO USE CHOLESKY PRECONDITIONING (PRECOND=C ON
ITER BULK DATA ENTRY) OR
THE DIRECT SOLVER (ITER=NO ON NASTRAN STATEMENT) FOR THIS
PROBLEM.
Avoidance: The error is caused because instead of using the diagonal terms of
the stiffness matrix as the Jacobi preconditioner (as intended) the iterative
solver is running with an identity matrix as the preconditioner which is the
same as running with no preconditioner at all. Use
33529
70.6
DBC - CTRIAR, PARAM,POST - UFM 6498
If a run with a ctriar element is execute back to back and the xdb file is not
removed, the job will fail with the following message unclear message:
*** USER FATAL MESSAGE 6498 (MsgGetStr)
Check call to MSGPOP from with the message number 0.0
Severity is INVALID ERROR TYPE (0)
Parameter 1 is
3
Parameter 2 is CTRIAR
Parameter 3 is CTRR
Parameter 4 is
0
*** USER FATAL MESSAGE 6498 (MsgGetStr)

Avoidance: Delete the xdb and re-submit the job.
33533
2005
Superelements - Component Modes, SECSET -
If free-free component modes are used (e.g., secset), then the eigenvectors may
be incorrect. A symptom of this error is indicated by the discrepancies
between the eigenvalues printed in the eigenvalue table versus the eigenvalues
printed at the top of the eigenvector output.
Avoidance: Do not use free-free components, use the default fixed-fixed
component modes. See related error 32365.
33543
70.6
Estimate - Recommends Setting SPARSE=1
The estimate program may incorrectly recommend turning sparse decomposition off
(i.e. setting SPARSE=1) for tet models. Sparse decomposition is virtually
always better than standard decomposition for decomposing stiffness matrices
for real world models. Sparse should never be turned off.
33559
2001
XS is not an Equivalent Stress
Documentation - PSHELL, STRESS(MAXS) - MA
A remark should be added to the Quick Reference guide description of the STRESS
case control command that MAXS for shell elements is not to be confused with an
equivalent stress as is the case for von Mises stress or the octahedral stress.
33566
2001
UFM 327 (IFS2P)
Static Analysis - PARAM,EXTOUT,DMIGPCH -
If param,extout,dmigpch is used in but there are no loads (for example in an

eigenvalue analysis) a header record for the "PAX" load matrix is printed to
the punch file. When this punch file is included in the bulk data of a
subsequent run, the job will fail with the following message:
BAD DATA OR FORMAT OR NON-UNIQUE NAME. DMIG PAX
COUNT =
52
IFP,
Avoidance:
SORTED CARD
Edit the punch file and delete the DMIG entry for PAX.
33568
70.6
ARAM,NOCOMP, PCOMP - SFM 3007
Optimization/Design Sensitivity - DSAD, P
When param,nocomps,0 is used in an optimization run with composite stress or

strain responses the following message will occur and homogeneous responses are
also requested, the following SFM is produced:
*** SYSTEM FATAL MESSAGE 3007 (DSAD )
Avoidance: Use param,nocomps,1 which is the default.
33572
70.6
upersedes RC file "auth" keyword
Installation - MSC_LICENSE_FILE env var s
The precedence of the "authorize" keyword hierarchy in the "MSC/NASTRAN

Configuration and Operations Guide", Section 3.2, is incorrect. The actual
hierarchy is:
1)
2)
3)
4)
5)
"authorize" keyword on command line.

MSC_LICENSE_FILE environment variable.
"authorize" keyword in an RC or RCF file.
<install-dir>/flexlm/licenses/license.dat
<install-dir>/conf/authorize.dat
<install-dir>/conf/authoriz.dat
6) LM_LICENSE_FILE environment variable.
# Windows NT
Note, the first three items are consistent with all other nastran command
keywords.
33573
70.6
- Mislabeled Output
The P2 parameter on the DOPTPRM entry is used to control the output of design
optimization results. The output that is produced for composite responses is
scrambled in that CFAILURE output appears as CSTRESS, the CSTRESS appears as
CSTRAIN and the CSTRAIN appears as CFAILURE.
Avoidance: The numerical values are correct. It is only the labeling that is
in error.
33588
70.6
STRESS, CSTRAIN, CFAILURE - SFM 3007
Optimization/Design Sensitivity - DSAD, C
The message:
*** SYSTEM FATAL MESSAGE 3007 (DSAD) ILLEGAL INPUT TO SUBROUTINE DSAD13
can be produced if there is a combination of CSTRESS, CSTRAIN, and CFAILURE
response types on DRESP1 entries and they invoke different sets of elements.
Avoidance: Either only use one composite response type or apply the multiple
response types to exactly the same set of elements.
33600
Wrong Answers
70.6
Aeroelastic Analysis - RESTART, MKAERO -
If a restart is selected with additional MKAERO data, only the new MKAERO pairs
will be used in the Flutter or Dynamic Aeroelastic analysis and the original
data will be ignored.
Avoidance: For SOL 145, apply the following dmap alter in the restart run:
compile flutter
alter 'cntr'(2,-1)
endif $
alter 'endif'(2),'endif'(2)
For SOL 146, the appropriate alter is:
compile seaero
alter 'cntr'(2,-1)
endif $
alter 'endif'(7),'endif'(7)
33606
70.7
al Input to Subroutine CALCV
SSSALTERs - checka.v705 - SFM 3007, Illeg
If the sssalter checka.v705 is used on a deck that has no spcs or rigid

elements then the message:
SYSTEM FATAL MESSAGE 3007, ILLEGAL INPUT TO SUBROUTINE CALCV
may be encountered.
Avoidance: Put in a dummy grid point and constraint.
33626
70.6
M,POST,0 - SWM 6066 (DBC)
Postprocessing - Nonlinear Analysis, PARA
In nonlinear analysis with superelements, MSC/NASTRAN Version 70 and 70.5 may

fail with messages similar to those below when it attempts to write results to
the XDB file.
*** DBCMSG ERROR MESSAGE 44 FROM SUBROUTINE DBCAOL
OUTPUT LIST DOES NOT MATCH EXISTING IN THE DATABASE, MERGE/RESTART
OPERATION IMPOSSIBLE.
MSC/XL
DATA BASE CONVERSION FINISHED
THE DBC MODULE HAS BEEN TERMINATED BECAUSE OF THE ABOVE FATAL DBC ERROR.
USER INFORMATION: SUBSEQUENT DBC CALLS WILL NOT BE EXECUTED, AND THE
DATABASE CONVERSION IS INCOMPLETE.
*** DBCMSG ERROR MESSAGE 14 FROM SUBROUTINE DBCROL
UNABLE TO OPEN INPUT RELATION NLLF
RETURN
33628
2004
Superelements - CSUPEXT - UWM 4155
If an image superelement has SPOINTs for component mode synthesis the the
following warning message may be incorrectly encountered:
USER WARNING MESSAGE 4155---GRID POINTS FOR SECONDARY SUPERELEMENT 82 ARE
COLINEAR. CONFORMITY CHECKS NOT MADE.
33629
2001
CTRIA3 - SFM 6352
Documentation/P-Elements - CBEAM, CQUAD4,
If beam and plate p-elements are used in random analyses, the following
uninformative message is printed in the .f06 file:
*** SYSTEM FATAL MESSAGE 6352 (SDRP36)
LOGIC ERROR: KERROR=
7.
PROGRAMMER INFORMATION: SUBCASE ID =
101 IN RECORD NUMBER
OUGV1
DATA BLOCK DOES NOT MATCH
THE SUBCASE ID =
102 IN RECORD NUMBER
2 OF CASEDR DATA BLOCK.
0FATAL ERROR
Avoidance: There is no avoidance, p-elements are not supported in random
analysis.
29 OF
33644
70.7
es with DLOAD - Wrong Answers
Transient Heat Transfer - Multiple subcas
Different DLOADs may not be applied in different subcases of a transient heat

transfer analysis. If attempted the load applied in the first subcase will be
lost in the second subcase.
Avoidance: Loads should be combined in a single DLOAD. If multiple subcases
are necessary to reference different tstepnl entries, than the DLOAD case
control request should be put above the subcase level.
33647
Follower Force - FORCE1 - Wrong Answers, Poor Convergence
In all linear solutions, the follower stiffness is erroneous when FORCE1

loads are applied. The convergence will be degraded in solution 106.
Avoidance: Use PARAM, FOLLOWK, NO to turn off the follower stiffness or apply
the loads using another type of force entry.
33725
sage
2007.0.0
Matrix Methods - MPYAD - System Fatal Mes
If insufficient scratch space is available for a large mpyad, the job may crash
and a meaningful message may not be output.
Avoidance: Increase the amount of scratch space available ot the job.
33726
70.7
stic Analysis, FLUTTER - SFM 7088
Optimization/Design Sensitivity - Aeroela
The message:
*** SYSTEM FATAL MESSAGE 7088 (DOPR3I)
MODE NO. xx ASSOCIATED WITH FLUTTER DRESP1 ID = yy EXCEEDS 0, THE NUMBER
OF MODES
AVAILABLE FROM THE ANALYSIS.
may be produced in error when NVALUE is not explicitly specified on the FLUTTER
entry. Since there is a default value for NVALUE, the input may be valid. The
message is also incorrect in that it is
(a) listed as a system fatal message when it should have been a user fatal
message and
(b) the run does not stop despite the supposedly fatal message.
Avoidance: If the default value has been used for NVALUE, the message can be
ignored.
33749
2005.5
STRAIN case control
Composites - No ply failure indices with
When STRAIN ply results are requested, failure indices are not calculated.
Avoidance:
Supply a STRESS=n also, where n is the set of elements that will have failure
indices calculated, but you get the extra ply stress results in addition to the
ply strain results..
See related CR 1-18756447 which is being fixed right now.
33753
2001
n QRG results in UFM 6721
Documentation/QRG - Replication example i
The replication example in the Version 70.5 Quick Reference Guide on page 427
results in USER FATAL MESSAGE 6721. The example:
GRID, 101, 17, 1.0, 10.5,,17,3456
=(4),*(1),=,*(0.2),==$
Should be changed to:
GRID, 101, 17, 1.0, 10.5,,17,3456
=,*(1),=,*(0.2),==$
=3
33770
Message
70.7
Documentation - Submittal - submit - Poor
A Bourne shell cannot be used to process the job file in a user's submit
command. If a Bourne shell is used, the following error may occur:
-sh: MSC_ASG=/Stemp/TT7293_19.asg: is not an identifier
The error message:
MSC_ASG=/Stemp/TT7293_19.asg: is not an identifier
was written by the Bourne shell, /bin/sh, and was complaining about an export
command.
Avoidance: Do not specify a Bourne shell. Section 3.11 of the "Configuration
and Operations Guide" does specifically state that a Korn shell must be used.
However, the example should be changed from "-s /bin/sh" to "-s /bin/ksh".
Note, the use of "/bin/sh" is correct on a POSIX-compliant system, but could be
misleading to an inexperienced user.
33775
Optimization/Design Sensitivity - MODES - Missing Output
When an optimization job with ANALYSIS=MODES uses more than one MODES
statements in Subcase Control section, the results are printed in *.f06 file
only for the first subcase.
Avoidance: Do not use the MODES command.
33776
Output
70.6
Aeroelastic Analysis - AEROF - Null AEROF
The AEROF output from solution 146 is all zeroes in Version 70.5. For
frequency response analysis, the AEROF case control command should produce
force and moment data for the the aerodynamic boxes of the DLM.
Avoidance: A workaround is to supply a Case Control SET having the desired ids
and referencing that SET in the output request: AEROF=<setid>
33779
70.6
DM - Wrong Answers
Grid point stress - PSOLID, GPSTRESS, COR
When higher order solid elements are used in Grid Point Stress Volumes, and
their PSOLID references a material coordinate system, the local grid point
stress will be incorrect. The invariants, such as Pressure or Von Mises are
correct.
Avoidance: Use the default basic coordinate system.
33797
2001
on Clarification
Aeroelastic Analysis - GUST - Documentati
The Version 64 Programmer's Manual indicates that the X0 field of the GUST bulk
data entry will change the phase relationship (it can be viewed as a time
delay) whenever a harmonic gust is used in SOL 146. Also the streamwise
location of aerodynamic elements introduces a phase change (a delay) in the
aerodynamic forces caused by a harmonic gust. The statement on page 606
paragraph 2 is not completely accurate. The X0 and the aerodynamic element
center streamwise location are terms in the equation that calculates the real
and imaginary parts downwash for each aerodynamic element. The phase relation
represents a time delay for an excitation at X0 to arrive at an aerodynamic box
streamwise position.
33809
70.6
Incorrect Unrestrained Hinge Moments
Aeroelastic Analysis - SPLINEi, SUPORT -
The unrestrained hinge moments are in error in static aeroelastic analysis if

the aerodynamic and structural model coupling splines the displacements from
the suport points to the aerodynamic mesh. This error is caused by omitting the
suport point displacements from the computation of the aerodynamic mesh
displacements for aeroelastic feedback.
Avoidance: A DMAP avoidance is:
compile aestatrs list noref
alter 'mpyad *gdkl.*ukpi',''
UMERGE USET,ULPI,URPI/UAPI/'A'/'L'/'R' $
mpyad gdka,uapi,/ukpi $ capture the r-set motion, too
33818
70.7
Segmentation Fault
Buckling Analysis - large problem - READ,
On a very large buckling problem, 2.6 million degrees of freedom in this case,
depending on the machine, the job may fail with one of the following error
messages either in the log or f06 files. The error is caused by trying to
solve THE BUCKLING SHIFT SCALE CALCULATION FBS OF a very large problem in core
instead of out of core.
Trap encountered:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0x0000007c
0x00000488
0x00000b50
0x00000040
0x000003f8
0x0000041c
0x00000598
0x0000039c
0x000010c4
0x000
in
in
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
dbsmr1_
gbkmgr_
ionast_
girdbk_
sfupfc_
ssmf1d_
ssm5d_
bucksd_
lnnrigl_
33841
70.6
using Drucker-Prager Yield Criterion
Nonlinear Analysis - Inaccurate Stresses
The Mohr-Coulomb and Drucker-Prager yield criteria (selected on the MATS1

entry) entry create an inaccurate solution. The error is the result of an
incorrect correction factor to the yield stress, which accounts for effects of
the internal friction angle. Incorrect factors underestimate the yield
stresses, resulting in premature yielding in tension.
Avoidance: There is no avoidance, but the error is negligible if the strain is
very small.
33860
70.6
in the f04 Output
Miscellaneous - Execution Summary - "nan"
If MSC/NASTRAN is run on a computer which has more than 68 CPUs. Then the F04
file may have "nan" in the output.
15:44:41
0:00
0.0
0.0 nan
nan
SEMTRN
BGN
Avoidance: There is no avoidance but the "nan" ouput may be safely ignored.
33861
70.7
VGRID - abnormally terminated
Optimization/Design Sensitivity - DSAJ, D
Shape optimization jobs may fail in the DSAJ module on machines that enforce
boundary alignment. This includes SUN, HP and Digital Alpha. The log file
will contain a message of the form;
*** TERMINATING /software/msc/nastran705/msc705/solaris/analysis.ultra
*** Received signal 10 (SIGBUS)
and then a machine dependent traceback:
from SUN:
t@1 (l@1) signal BUS (invalid address alignment) in unpack_ at 0x8fcc58
unpack_+0x1d8: std
%f2, [%o1]
(dbx) where
=>[1] unpack_(0x275, 0x1, 0x1dbb92c, 0x1a494e0, 0x1a49430, 0x0), at 0x8fcc58
[2] dsaj4_(0x18a88d4, 0x244598, 0x18a8680, 0x18a86d8, 0x1f6d010, 0x18a8638),
at 0x244810
[3] dsaj_(0x18a8680, 0x18a8690, 0x1358, 0x18a8574, 0x0, 0x18a8578), at
0x243510
[4] xsem02_(0x123, 0x18852b0, 0x1
33863
70.7
Poor Performance
Buckling Analysis - PARAM,FOLLOWK, TAFF -
If follower force stiffness is turned on (which is the default) in a buckling

analysis, and there are many load entries, then the calculation of the follower
force stiffness will be extremely slow.
Avoidance: If the effect of the follower force stiffness is not important, add
the following parameter to the bulk data section:
PARAM,FOLLOWK,TAFF
33874
2001
Documentation - EIGRL, SYSTEM(146) - Inco
rrect Description
The descriptions for system cell 146 in the Quick Reference Guide under the
EIGRL entry and the NASTRAN statements are incorrect. The system cell values
are no longer a percentage increase of the memory reserved for the sparse
method, rather, it is calculated as (3 * x * buffsize), where x is the value
specified for system cell 146.
33896
Dynamic Analysis - TEMP, Thermal loads - UFM 4017
If multiple LSEQ entries exists in a model and the LSEQs reference different
TIDs, then the job will fail with the following unclear messages:
*** USER FATAL MESSAGE 4017 (GETEMP)
THERE IS NO TEMPERATURE DATA FOR ELEMENT x IN SET yyy
0FATAL ERROR
Avoidance: Reference the same TID on all the LSEQ entries.
33911
70.6
ry Restart for Modal Solutions
Restarts - GKAM - Inefficient Data Recove
In a data recovery restart run in SOLs 110, 111, 112, 145, and 146, the GKAM
module is unnecessarily reexecuted.
Avoidance: Insert the following DMAP alter in the restart run:
compile semfreq
alter 'call gma',''
CALL GMA CASERS ,MATPOOLs,EQDYN
,
,MAA
USETD ,KAA
,BAA
LAMAs ,DIT
,VAFS
AGG
,kddd
/
,
,CMDD
MHH
,BHH
,KHH
K2MG
,M2MG
,B2MG
B2SF
/
LUSETD /SOLTYP /APP
FALSE /FMODE /FALSE
33913
2001
- Missing Output
,TFPOOL
,GOD
,K4DD
,PHFA
,
,GMD
,PHsA
,lamaf
,
,
,
,
,CK2DD
,PHDH
,K2SF
,CB2DD
,VPHFS
,M2SF
,
,
,
/NOUE
/FALSE
/NOA
/FS
/
/
Documentation - PARAM,CHECKOUT, PARAM,GPL
The parameter GPL described under PARAM,CHECKOUT in the Quick Reference Guide
should be PARAM,PRTGPL.
33936
70.5
utput from a Trim Analysis.
Aeroelastic Analysis - Mislabeled Force O
If there are multiple interference groups (IGID on the CAEROx entry) and the
element ID's are not in ascending order with respect to the IGID's, the trim
force output can have incorrectly labeled element id's since it uses
monotonically ascending values starting from the lowest element ID.
Avoidance: Remove the multiple IGID's or make sure that element id's ascend in
order with the IGID's.
33938
2001
RESTARTS - Inefficient Restart between bi
nary compatible machines.

If a database is created on one machine and read into NASTRAN on a different
binary compatible machine, the RESTART logic may detect that there are minute
differences in the model and everything may be re-calculated.
Avoidance:
compile phase0
alter 'RMGR,RMG,/','RMGR,RMG,/'
The above alter should be used only if your are certain there are no changes to
the model.
or superelement manual restart logic could be used. See SERST parameter.
33942
id Body Modes
Documentation/Differential Stiffness - EIGR, EIGRL - Poor Rig
If the pressurized modes of a free-free structure are desired, the rigid body
modes may not be very clean and may only be separated from the flexible modes
by 3 orders of magnitude. Negative values may also be observed. This
condition may occur in any model with follower stiffness or rigid elements.
Avoidance: No avoidance is necessary. Even though eigenvalue analysis without
follower forces typically produces 6 orders of magnitude separation between the
flexible and rigid body modes the answers should be acceptable.
33943
Miscellaneous - PARAM - No Warning Message
If a PARAM is entered in the input data but is not used (for example when the
param does not exist), no warning message is issued. Depending on the intent of
the user this may lead wrong answers.
33952
70.7
Does not work in SOL 107
Component Mode Synthesis - PARAM,METHCMRS
If residual structure cms is requested and METHCMRS is used to select the

eigenvalue solution method in SOL 107, the program will perform a static
reduction and will ignore the request for cms. Table 1 in section 6 of the
Quick Reference Guide incorrectly indicates that this parameter is supported in
solution 107.
Avoidance: Use the METHOD command in the CASE CONTROL to request cms for the
residual structure.
33953
nswers
2001.0.9
Component Mode Synthesis - QSET - Wrong A
If residual structure cms is used, unused Q-set dof are not automatically
removed by AUTOSPC. This may result in unexpected or incorrect answers.
Avoidance: Either specify the correct number of Q-set dof (this may be
difficult, as it requires prior knowledge), or use PARAM,SMALLQ,0., which will
remove unused Q-set dof from the solution.
33954
cumentation
2001
Documentation - PARAM,SMALLQ - Missing Do
PARAM,SMALLQ is not documented in the Quick Reference Guide. The purpose of
this parameter is to remove unused Q-set degrees of freedom from the solution
set. If you are performing residual structure qms, then it is recommended to
set PARAM,SMALLQ,0. in order to remove the unused Q-set dof.
33955
Stresses
Elements - BEAM, BAR, TEMP(INIT), TEMP(LOAD) - Incorrect Beam
In Version 70.5 if TEMP(INIT) references TEMPRB or TEMPP1, then TEMP(LOAD)

must reference TEMPRB and TEMPP1 for the same elements, conversely if
TEMP(LOAD) references TEMPRB or TEMPP1, then TEMP(INIT) must reference TEMPRB
or TEMPP1 for the same elements, else wrong answers will results.
33957
- Poor Results
2004
Documentation/Composites - CQUAD8, PCOMP
The bulk data description of the CQUAD8 in the Quick Reference Guide needs to
be changed as follows:
- Remove Figure 1 and change the title of Figure 2 to Figure 1,
- The description of the MCID field needs to be changed as follows:
"MCID
...................MCID coordinate system (defined by the
CORDij entry or zero for the basic coordinate system) onto
the surface of the element (see Remark 3). MCID is
ignored ........."
- Change Remark 3 as follows:
"3.
........the line of constant xi."
- Add the following paragraph to Remark 3:
"The definition of the material coordinate system by
projection is used to calculate an angle THETA.
Please note that since xi changes direction throughout
the element based on element shape, the material
coordinate system varies similarly. Because of this an orthotropic or
anisotropic material will cause the CQUAD8's stiffness to be biased by both
it's shape and grid ordering. Use the QUAD4 element if a constant material
coordinate system direction is desired."
33960
er Technique
Documentation/Aeroelastic UG - SOL 110 with Lagrange Multipli
Mike suggested to keep in the enhancement status for the later relase.- Raj
Section 8.11 in the Aeroelastic User's Guide demonstrates the use of the
Lagrange Multiplier Technique with TPL problem ha110a.dat. Currently, solution
110 problems can not be solved reliably with the LMT approach and this example
should be removed.
33973
70.6
The form of the column vector outputs in MATMOD option 25 is 7 (labeled "ROW
VECTOR") and should be 2 (labeled "ROW RECTANG.").

Avoidance: Run MODTRL on the output; for example,
MATMOD I1,I2,I3,,,/O1,O2/25 $
MODTRL O1// / /2 $
MODTRL O2// / /2 $
33994
70.6
DVBSHAP - UFM 1126
Optimization/Design Sensitivity - scr=no,
In Version 70.5, if shape optimization is attempted with the command line

option 'scr=no', then the following fatal message occurs:
*** USER
DMAP
CASESTAT,
USER

MODULE MDCASE IS ATTEMPTING TO OUTPUT DATABLOCK
201 NAME =
ACTION: DELETE THE DATABLOCK, OR USE FILE CASESTAT=OVRWRT

compile desopt
alter 1
file casestat=ovrwrt $
endalter
33997
2001
Elements - Large Field PSOLID Entry - Str
ess Results at GAUSS Points, not GRID
A missing PSOLID large field format continuation line will incorrectly cause
stresses to be returned at the GAUSS points instead of the GRID. This will
change the output values to those calculated at the GAUSS points instead of the
GRID points. This could cause optimistic results to be inadvertently used for
design.
Avoidances:
1) Include the blank continuation line, (you may want to consider specifying
the defaults so someone doesn't delete the blank line thinking it is a useless
line),
2) Use sma
34005
70.6
stic Analysis - Wrong Answers
The Version 70.5 release of MSC/NASTRAN enabled the ability to simultaneously

perform static and static aeroelastic analysis and design. It has been found
that, if the static aero and static subcases both have load requests, the load
calculation can become confused and incorrect or no loads can be applied in the
static aeroelastic subcases.
Avoidance: The only known avoidance is to not use LOAD requests in static aero
subcases in situations where there are also static subcases.
34015
70.7
Rigid Elements - RSPLINE - UFM 4204
The word "WARNING" in "USER WARNING MESSAGE 4204" which warns the user that
there are RSPLINE elements with no dependent degrees of freedom was
inadvertently changed to "FATAL" in Version 70.5. The run continues and the
results are unaffected.
34028
70.5
M 4276, EC 7777
Elements - CBAR, EMG, PARAM,COUPMASS - SF
If coupled mass is used with CBAR elements with pinflags, the run may fail with
the following traceback in the EMG module:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0x00000010
0x00000130
0x000003ac
0x00000a08
0x000003c8
0x00000108
0x0000097c
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
zerod_
ebarkd_
emgbrd_
emgpro_
emg_
xsem09_
mainal
--- End of call chain --Avoidance: Do not use coupled mass.
34038
2001
DSAJ - SFM 4276, EC 31
When a solution 200 run has both shape and sizing variables and the shape
variables have smaller ids than those for the sizing variables, the job may
fail in the DSAJ module with "SYSTEM FATAL MESSAGE 4276, ERROR CODE 31".
Avoidance: Renumber the DESVAR ids so that the shape DESVAR have larger ids
than the sizing variables.
34042
70.6
issing xdb Output
Postprocessing - GPSTRESS, PARAM,POST - M
If your run contains multiple subcases in nonlinear static analysis and you
have requested strfield, output will only be obtained for the first subcase and
subsequent subcase output will be missing.
Avoidance: There is no avoidance other than performing RESTARTs for each
subcase.
34043
2001
upport of SOL 153 not Documented
Documentation - ITER - Iterative Solver S
The Quick Reference Guide description of the ITER bulk data entry fails to list
solution 153 as a supported solution sequence.
34060
70.6
If superelements are present and PARAM,METHCMRS is specified for the residual

structure, then UFM 3032 will be issued stating that the program is unable to
find the selected set (EIGRL entry).
compile cmpmode
alter 'methc\=',''
if ( seid=0 and methcmrs>0 ) methc=methcmrs $

alter 'read ',''
read
cmkxx,cmmxx,,,dynamics,uset,cases,vyxw,sils,uset,,,eqexins/
cmlama,cmphixz,cmmi,cmoeigs,eigvmats,/
'mode'/s,n,nozset//methf/cmset/methc $
endalter
34084
70.7
SFM 4276 EC 1044 QOPEN
Aeroelastic Analysis - AMP, SPC, METHOD -
SYSTEM FATAL MESSAGE 4276. QOPEN ERROR CODE 1044 is issued in SOL 145 if BOTH
the METHOD and SPC change (or are not included) for each subcase.
Avoidance: Include the same METHOD and SPC callouts in all residual subcases
or place them above the subcase level.
Also include the following DMAP alter:
compile sefluttr
alter 'modefsrs',''
$ change cases to casem
call MODEFSRS MR,USET,DM,CASEm,DYNAMICS,MAA,KAA,GPLS,SILS,EED,
EQEXINS,,pg,gm,got,kfs,ys,lll,kll/
,,,,PHA,LAMA,PHA0,LAMA0/
app/NORSET/NOASET/false/
0/NOASET/METH/0/true/NOQSET/nsub/0 $
alter 'call setq',''
CALL SETQ CASE1//
S,SPC/S,LOAD/S,DEFORM/S,TEMPLD/S,P2G/S,
34089
70.7
nfinite CPU Loop
Composites - RESTART, PCOMP, DBLOCATE - I
If PCOMPs are changed in a RESTART and there is more than one PCOMP entry in
the model, then the run may enter an infinite cpu loop in the DBLOCATE module.
Avoidance:
You can avoid the error with the following DMAP alter.
malter 'ept,eptr','ept,eptr'
restart ept,,/list/ $
malter 'epts,eptsr','epts,eptsr'
restart epts,,/hists/ $
This alter will redo the entire analysis. Only use this alter if there is a
difference in the number of plies between the restart pcomp card and
the new pcomp card.
34114
70.6
PTEXIT,3 - Missing Output
PARAM OPTEXIT 3 is used to exit SOL 200 after evaluating the constraints.
However, the results of this evaluation are not printed, making this option of
marginal utility. These prints could be of particular benefit if the user has
synthesized a response that is not currently available with standard output
requests. The user could see the values of the response, but avoid costly
sensitivity/optimization calculations.
Avoidance: The following dmap alter provides the P2 output (see the DOPTPRM
bulk data entry) when PARAM OPTEXIT= 3
compile desopt $
alter 'optexit=3'(,-1) $
if ( descycle=1
) DOM10
DESTAB,XINIT,,CNTABRG, CVALRG, ,
DVPTAB,PROPI,,R1TABRG,R1VALRG,,
RSP2RG,R2VALRG,,OPTPRMG,OBJTbg,DRSTBLg,
34139
g UWM 3204
2001
Dynamic Analysis - LSEQ, STATSUB - Missin
If a dynamic response analysis specifies a static subcase but then in the

dynamic subcase the dynamic loads are incorrectly applied such that the LID
field of the LSEQ entry references non-existant static load entries, no warning
message will be issued and unexpected answers will result. The following user
warning message should be issued:
*** USER WARNING MESSAGE 3204 (SSG1)
UNABLE TO FIND SELECTED SET ( yy) IN TABLE (SLT ) IN SUBROUTINE (SSG1).
Avoidance: Other that ensuring that the static load entries exist, there is no
avoidance.
34151
2001
st some, 2206 of 2209 eliminated
Miscellaneous - Unknown Error Message, Lo
When the new reordering methods are used, it is possible that the message "Lost
some, 2206 of 2209 eliminated" (the numbers may not be the same) may be written
to the f04 and the job will stop. This appears to happen when the EXTREME
reordering is used and insufficient memory is available. This has only been
observed in two client runs.
Avoidance: If the message above is encountered, disable the EXTREME method by
setting SYSTEM(206) to 1, 8, or 9
34153
70.7
UFM 6482, Response Types Mislabeled
If a composite type response (CSTRESS,CSTRAIN, or CFAILURE) is invoked in a

subcase that does not support this type of response (e.g, ANALYSIS=MODES). The
designated response type is scrambled; CFAILURE becomes CSTRESS, CSTRAIN
becomes CFAILURE, and CFAILURE becomes CSTRAIN. Further, RTYPE CFAILURE is
misspelled CFAIURE in USER FATAL MESSAGE 6482.
Avoidance: The FATAL message is legitimate, but one needs to infer the correct
response type.
34200
70.6
Geometric Nonlinear Analysis - CHEXA, CQU
AD4, CTRIA3, TEMP(LOAD) - Wrong Answers
In sol 4, ssg1 puts out an incorrect load vector for CHEXA, CQUAD4 and CTRIA3
elements when thermal loads are present along with a global output system.
Avoidance: Use solution 106 or 64.
34208
FM 3001
70.7
Optimization/Design Sensitivity - TA1 - S
When a design variable overrides an analysis property in a p-element sizing
optimization job, it results in the following error message:

SYSTEM FATAL MESSAGE 3001 (TA1)
THE INPUT DATA BLOCK NAMED EHT
AT POSITION
10 DOES NOT EXIST.
Avoidance: Ensure that property values for both the analysis and design model
are identical or apply the following dmap alter.
compile desopt
alter 'luset= '
DBVIEW eht0=eht (WHERE DESITER=0) $
EQUIVX eht0/eht/always $
DBVIEW ehta0=ehta (WHERE DESITER=0) $
EQUIVX ehta0/ehta/always $
DBVIEW gdntab0=gdntab (WHERE DESITER=0) $
EQUIVX gdntab0/gdntab/always $
DBVIEW medge0=medge (WHERE DESITER=0) $
EQUIVX medge0/medge/always $
DBVIEW mfac
34211
N - UFM 6962
70.6
Shape Optimization - DBLOC, DVSHAP, MATGE
When performing shape optimization using an external database for basis

vectors, if the dblocated basis vectors (UGD) do not have same GSET size as the
analysis model, then the following fatal message will occur:
USER FATAL MESSAGE 6962 (MATGEN)
ILLEGAL VALUE FOR PARAMETER 3 = ****
Avoidance: Use an external model displacement vector (UGD) compatible with the
current analysis model GSET size.
34236
70.5
Installation/Authorization - FlexLM Faili
ng on NEC SX4 with SIGALARM error -5038
There is a problem on the NEC SX4 machine using the FlexLM network licensing
manager that may cause large jobs to fail with the message: SIGALARM - Alarm
call 5038 error.
Avoidance: There is no avoidance, use a node lock authcode instead.
34238
C 7777
70.7
Elements - PBEAM, PBAR, IFP - SFM 4276, E
HP systems may have fail with a traceback in IFP when it attempts to read bulk
data inputs that contain PBAR and/or PBEAM input with very large property
values.
34239
ation
2001
Documentation - TLOADi - Missing Document
A remark under the description of the TLOADi entries in the Quick Reference
Guide indicates that if time dependent loads are applied in a frequency
response solution, that a Fourier transform is performed to transform the loads
to the frequency domain and that the results are converted and reported in the
time domain. This remark should refer the user to the Section 5.4 in the
Advanced Dynamics User's Guide to obtain more information on the process.
34254
70.7
rmance, Poor Convergence
Iterative Solver - ITER, BIC - Poor Perfo
If an initial guess is given to the iterative solver with BIC preconditioning

(default) in MSC/NASTRAN V70.5 it will be ignored.
avoidance: To be able to use an initial guess with the Version 70.5 set
PRECOND=BICWELL or PRECOND=BICILL on the ITER Bulk Data entry and set
SYSTEM(241)=2000 on the NASTRAN entry.
34259
101
2001.0.1
Acoustic Analysis - Superelements - UFM 9
When a fluid only model with a fluid superelement is run in solution 103, the
job may fail with the following messages:
^^^ BULK DATA AND CASE CONTROL PARTITIONING,
RESTART CHECKING, AND
UNDEFORMED PLOTTING IS
^^^ INITIATED FOR SUPERELEMENT
0
^^^ USER FATAL MESSAGE 9101 (PHASE0)
^^^ FLUID ELEMENTS ARE DETECTED IN THIS SUPERELEMENT.
^^^ USER ACTION: ENSURE THAT ALL FLUID ELEMENTS
ARE ASSIGNED TO
SUPERELEMENT
yy
Avoidances:
1) Do not use a superelements for this analysis, it is not needed. This may
require stripping the superelement designation from all of the fluid grids if
the model comes from a fluid/structure analysis.
2) Add a dummy structural element similar to the following:
grid, 10000 $ token grid point in se 0
celas2,
34264
nks
70.6
Estimate - File Names may not Contain Bla
Blanks in pathnames are not handled properly when "memory=estimate" is

specified. Only the part of the directory name after the blank is shown and
estimate issues the message "This file does not exist." The job continues, but
the default memory or buffsize is used.
Avoidance: Specify a pathname that does not include blanks.
34265
2001
OA - Undocumented Parameter
Documentation/Superelements - PARAM,MINIG
In MSC/NASTRAN Version 70, an undocumented parameter (MINIGOA) was added to

allow reduction in the amount of disk space used when using superelements. When
this parameter is used, the transformation matrix (GOA) will contain terms only
for the degrees of freedom defined in the U5 (USET, USET1, SEUSET, SEUSET1)
set. As the GOA matrix is often one of the largest matrices stored in the
database, this can allow for a significant reduction in the amount of disk
space used. The limitation of using this approach is that data recovery will be
available only for these degrees of freedom and the elements connected to them.
34266
2001
ocumented in the QRG
Documentation - EIGRL - SYSTEM(273) Not D
In Version 70.5, setting SYSTEM cell 273 to 1 allows the selection of the old
(pre-v70.5) Lanczos eigensolver. This is mentioned in the Version 70.5 Release
Guide, but is not documented in the QRG.
34270
P-Elements - Wrong Answers for p-BEAM Element at p=1
BEAM p-elements with p-order of 1 are stiffer in bending than BEAM h-elements
due to incorrect residual bending flexibility in BEAM p-elements.
Avoidance: The avoidance is to start at a p-order of 3.
34271
70.6
Results in OES1 Table
Optimization/P-Elements - P-BEAM - Wrong
Wrong ENDB max and min stresses are written to the OES1 table for the p-Beam
element types by Module SDRP. However, the OFP printout of the ENDB max and min
stresses is correct since the OES1 table values are not read but computed by
the OFP module. This error will affect design optimization results and
postprocessors which report these values.
34287
70.6
y Derivative Sensitivities
Aeroelastic Analysis - Incorrect Stabilit
The UXU and UXR matrices produced by DSARLP may be in error. Consequently,
this can produce wrong answers for the sensitivities of stability derivatives
and will produce unpredictable downstream errors.
Avoidance: There is no known avoidance. This capability should be used with
caution. Zero or unreasonable stability derivative sensitivities may be an
indication that this error has been encountered.
34290
2001
ty is not Allowed, UFM 316
Documentation/QRG - TABLES1 - Discontinui
The Quick Reference Guide description for the TABLES! entry should explicity
state that discontinuities are not allowed and will lead to a fatal message.
34321
Installation - FLEXlm on NT needs lmutil.exe program
The client installation of FLEXlm on NT needs to also install the lmutil.exe

program (and the lmgr325c.dll file) so the user can check the availability and
usage of Nastran licenses. The current installation does not allow this.
Under the current installation procedure the user would have to get these files
from the FLEXlm license server computer. This should be automatically done
with the installation.
Avoidance: The flexlm directory in the standard installation should have
lmutil.exe. Also, the msc705\i386 directory contains lmgr325c.dll. The
installer may have to copy the .dll from the i386 directory to the flexlm
directory for lmutil to be able to find it.
34325
70.7
may give bad answers
P-Elements - GMLOADs on FEEDGEs with p=1
GMLOADs on FEEDGEs with p=1 will give incorrect loads if another edge with p>1
was processed.

34362
70.7
h PROJ=F Option
P-Elements - Incorrect p-shell Output wit
If the PROJ=F option is chosen on the OUTRCV entry for p-shells, the moments
may be incorrect. In addition, if a coordinate system is specified with the
CID=n option, the transformation may be incorrect.
Note that the PROJ=F option does not output any data into the f06 file, but it
does affect the output in the OP2 and XDB files. The option was created
primarily for use by MSC/ARIES.
34393
70.7
work for NASTRAN Version 70.5
Utilities - xdb, DBC - msc2ptc Failed to
The msc2ptc utility does not run due to a problem with the nast705 script and
missing m2p.dsc file. An attempt to convert the xdb file fn.xdb results in the
message:
fn: executable for fn not found or not executable.
Verify that the fn executable has been installed.
The full pathname of the bracket executable is:
/nastran705/msc705/solaris/fn
Avoidance: The updated files are posted at
http://www.macsch.com/support/support.html
34415
70.6
Superelements - EPOINT - Wrong Answers
In part superelements with extra points, the sequence of grid points provided
in the usetd table, produced from the uset table by adding extra point data,
may differ. This will cause plausible but wrong answers. In one example
discovered in testing the load vectors were in a different sequence than the
corresponding terms in the stiffness matrix.
Avoidance: An avoidance which prevents the error is
SEQGP entry for a residual structure grid point. It
that will cause no extra resequencing of the model.
bulk data file includes grid point 47, the following
SEQGP, 47,
to put in at least one

can be input in a manner
For example, if the main
SEQGP entry will suffice:
47.1
This avoidance may be used with any model, of any size, with negligible effect
on cost. The presence of an SE
34424
2001
to List All Keys
File Management Section - DBDICT May Fail
NDDL datablocks are uniquely defined by their qualifier values. In addition to

the NDDL datablock name, a path, or list of applicable qualifiers, is thus used
to "point" to a particular datablock. The DBDICT FMS statement (which can also
be called in DMAP) can be used to list qualifier values for datablocks stored
on the database, and does so by printing out "keys," or unique lists of
qualifiers and their values. A code error may prevent some of the keys from
being printed out.
Avoidance: If this problem is encountered, the DBDIR FMS statment (also

callable in DMAP) can be used to obtain a complete qualifier listing.
34429
04.
70.6
Miscellaneous - Overflow "*****" in the f
If a job requires more than 999999.9 CPU seconds, then the F04 will print
********. If a job requires more than 999999.9G of I/O then ******** will be
printed.
34459
70.7
n in Punch File
Heat Transfer - Missing RADLST Informatio
If large CHBDYG id's exist, then the punch file which contains the RADLST
entries will be incomplete and contain a line such as:
RADLST
12
1****************
Avoidance: 1) Do not use element ID greater than 10000001

2) Use restart for the subsequent run rather than including the
RADLST punch file because all the radiation matrix
information is in the NASTRAN database.
34462
70.6
too stiff when modeling thin plate
P-Elements - HEXA - Poor Answers, Element
The HEXA element with p=1 on most edges is too stiff. This was discovered when
analyzing the thin flat plate test problem of the MacNeal Harder test set. For
most problems the effect is small, but for the thin flat plate model the effect
is dramatic.
Avoidance: Use a higher p-order.
34467
70.7
g Answers for Transformed Stresses
P-Elements - CHEXA, CPENTA, CTETRA - Wron
If stresses and strains are being transformed using the CID= keyword in the
OUTRCV bulk data entry, then wrong answers may result.
Avoidance: The only avoidance is to request the stresses in the basic
(default) coordinate system.
34474
70.6
by the nastran Command
Security - FLEXlm License may be Refused
The nastran command will refuse to accept an otherwise valid FLEXlm license
spec for redundant servers written as:
port@host1,port@host2,port@host3
Avoidances:
1) Do not use redundant servers. They are high maintenence with little gain.
Multiple servers, specified via "port@host1:port@host:..." on UNIX and
"port@host1;port@host;..." are more powerful and less work.
2) Only specify one of the hosts. Each of the hosts in the quorum knows about
the other two, so the comma specification is redundant. You could even specify
all three hosts as if they weren't redundant, using the ":" or ";" separators
as appropriate.
34480
70.6
Missing Eigenvalues
Eigenvalue Analysis - PARAM,RESVEC,YES -
By simply specifying PARAM,RESVEC,YES, incorporated residual flexibility in the

solution sequences making the the resflex sssalter unnecessary. There is an
error in the capability which may cause missing modes. The error in the
results is obvious because there will be fewer rather than more eigenvalues
when you compare the eigenvalues "BEFORE AUGMENTATION OF THE RESIDUAL VECTORS"
to those "AFTER AUGMENTATION OF THE RESIDUAL VECTORS".
Avoidance : Insert the following DMAP alter:
compile resvec
alter 'if ( noxset'(3),''
if ( noxset>-1 or append ) then $
endalter
34482
70.6
ot Function on RESTART
DMAP - Database, DBSTORE - DBSTORE Does n
The automatic restart logic does not schedule modules to run on restart that
have no output data blocks. The dbstore subdmap, and the dbstor subdmap which
it calls, have this attribute.
Avoidance: Use putsys(1,109) before the call statement, or use an alter in the
v70.5 sssalter library that includes dummy output data blocks for both modules.
34491
xtend file
70.7
Delivery Database - eie layer unable to e
On Cray systems, if a user has the Delivery Data Base (SSS*) files on a device
that does not have a sector size that is a multiple of 4096 words, and if the
user specifies ff_io_defaults=eie.sds.diag, then the following message is
printed:
eie layer unable to extend file
"/apps/mscnast/v7052/msc705/unicosts/SSS.MASTERA" to a multiple of 65536 bytes
/apps/mscnast/v7052/msc705/unicosts/SSS.MASTERA : open failed : errno =5048 :
Unknown error
ffopen(/apps/mscnast/v7052/msc705/unicosts/SSS.MASTERA) using alternate layers
system
opening layer system
/apps/mscnast/v7052/msc705/unicosts/SSS.MASTERA : using layers : syscall
The job will then continue to run if the the BUFFSIZE is 4097. However, if
BUFFSIZE is set to a different value, then the following error is printed:
34517
70.7
P-Elements - STRAIN, SHELLS & SOLIDS -- I
ncorrect Principal and von mises strain
If a problem has either shell or solid p-elements, then the principal, von
Mises, and mean pressure strains may be incorrect.
34520
rong Answers
70.7
Acoustic Analysis - METHOD(STRUCTURE) - W
In fluid/structure analysis, in modal frequency response (SOL 111), if the

fluid modes are calculated using the modal method, i.e. the case control
command METHOD(FLUID)=n, but no METHOD(STRUCTURE) is specified, incorrect
results occur.
Avoidances:
1.
2.
3.
4.
Use
use
put
use
SOL 108, or,

both a METHOD(FLUID) and a METHOD(STRUCTURE), or,
the fluid in a superelement and process it separately, or
the following alter for Version 70.5:
compile gma
alter 295
partn k1dd,vafse,/k1shh,,, $
partn kddd,vafse,/kdhh,,, $
igh=ig $
call xadd5 k1shh,kdhh,,,/gk1shh/igh/cu/cz/cz/cz $
endalter $
34523
- SFM 4276
2001
Optimization runs with large DEQATN entries that are near or exceed the limit
of 32000 non-blank charachters may fail on Cray computers with the following
message:
lib-1190 /u/app/nastran/msc/msc705/unicosc90/NAST705: UNRECOVERABLE library
error
A numeric input field contains an invalid character.
Encountered during a sequential formatted READ from an internal file (character
variable)
Error initiated at line 656 in routine '_rdfmt'.
See signal(2), CRI manual SR-2012 for further information.
Beginning of
Called from
Called from
Called from
Called from
34535
2020, UFM 5503
Traceback:
line 42 (address 15624627c) in routine 'TRBK'.
line 39 (address 132322c) in routine 'RECOVR'.
line 112 (address 15073635b) in routine 'sysrcv'.
Optimization/Design Sensitivity - PCOMP, MAT8, SDRCOMP - UWM
In solution 200, if ply failure indice responses are requested for a composite
element whose PCOMP entry references a material entry that does not define the
composite failure allowables for one or more of the plies, then the following
fatal and/or warning messages are issued and the failure index responses are
not used for that element in the optimization analysis.
** USER FATAL MESSAGE 5503 (DSAD13)
ELEM NO.
42649 PLY NO.
1 REFERENCED ON A DRESP1 ENTRY COULD NOT
BE FOUND.
*** USER WARNING MESSAGE 2020 (SDRCOMP)
ONE OR MORE OF THE ALLOWABLE STRESS CONSTANTS WERE INCORRECT FOR ELEMENT
1 PLY
4
ELEM NO.
1 PLY NO.
1 REFERENCED ON A DRESP1 ENTRY COULD NOT
BE FOUND.
USER ACTION: CHECK THE ELEMENT IDS REQUESTED ON THE DRESP1
34548
6719 (MRGIDX)
70.6
Acoustic Analysis - EPOINT, CAABSF - SFM
In frequency response, if EPOINTs exist in a fluid-only analysis with CAABSF

elements with no SPCs, the following fatal message will be encountered:
*** SYSTEM FATAL MESSAGE 6719 (MRGIDX)
MATRICES HAVE DIFFERING NUMBERS OF ROWS:
[A] =
48 x
48
[B] =
44 x
48
[D] =
48 x
48
0FATAL ERROR
44
[C] =
48 x
Avoidance: Insert the following DMAP alter or add a dummy grid point and
constrain all of its degrees-of-freedom.
compile fdrmgen
alter 'if ( noa',''
type parm,,i,n,noue $
if ( noa=-1 and noue=-1 ) then $
compile freqrs
alter 'if ( noa'(3),''
IF ( noa>-1 or noue>-1 ) then $
endalter
34552
th no message
70.6
Acoustics - EPOINTs, GMA, GKAM - Fails wi
If EPOINTs are used in a fluid-only model in solution 111, the run will fail
without message after the eigenvalue extraction and before the frequency
response output.
Avoidance: Use the following alter:
compile gma
alter 'gkam'
if ( fonly and noue>-1 ) then $
matgen ,/iee/1/noue $
paraml phfa//'trai'/1/s,n,nohset $
paraml phfa//'trai'/2/s,n,noaset $
type parm,,i,n,nhe,nae $
nhe=nohset+noue $
nae=noaset+noue $
matgen ,/vhe/6/nhe/nohset/noue $
matgen ,/vae/6/nae/noaset/noue $
merge phfa,,,iee,vhe,vae/phdfh/1 $
merge MFHH,,,,vhe,/mfhh1 $
equivx MFHH1/mfhh/-1 $
merge K1FHH,,,,vhe,/k1fhh1 $
equivx K1FHH1/k1fhh/-1 $
endif $ fonly and noue>-1
34558
70.7
at View Points
P-Elements - BEAM, OUTRCV - Wrong Answers
The results output at view points for beam p-elements is wrong if a curved
coordinate system is specified as the output coordinate system on the OUTRCV
entry.
34581
R THAN "VFZTOL"
Heat transfer - VIEW3D - FATAL, DIMENSION LENGTH x IS SMALLE
It is possible running a view factor calculation using the VIEW3D module (this
is the default view factor method selected by PATRAN) to encounter the message:
*** FATAL *** DIMENSIONAL LENGTH: 1.732432600E-11 IS SMALLER THAN "VFZTOL":
1.000000013E-10
REASSIGN "PARAM,VFZTOL,X.XE-XX" TO BE SMALLER THAN THE
DIMENSIONAL LENGTH.
Avoidance: Comment out the VIEW3D input so that the older view factor module is
used. In the test problem that encountered the poor message, the old view
factor module issued the messages below which identified the problem:
*** USER FATAL MESSAGE 4528 (VNASIN)
ERROR IN CHBDY CARD xx AN AREA4 ELEMENT MUST BE A QUADRILATERAL
CONTAINING NO ANGLE GREATER THAN OR EQUAL
TO 180 DEGREES. THE GRID POINTS MUST BE SPECIFIED SEQUENTIALLY AR
34585
2001
Database - SFM 1041 (GALLEX)
A limit in the database directory size may cause large jobs to fail with the
message SYSTEM FATAL MESSAGE 1041 (GALLEX).
Avoidance: This limitation can be overcome by increasing the buffsize and/or
setting system(158)=1000 and system(159)=500 to allow for a larger expansion of
the database.
34590
GL
- SFE 4276, FREAD EC 3002
Eigenvalue analysis - EIGB, SINV, CYCLIC4
In SOL 16, cyclic buckling, if the SINV method is used, and no eigenvalues are
found for the current harmonic, then the run fails with the following message
in CYCLIC4.
*** SYSTEM FATAL ERROR 4276.FREAD
ERROR CODE
3002 PID=
Avoidance: Use the Lanczos method.

34591
70.6
- SFM 3001 and UFM 1126
Cyclic Buckling - SOLs 116 and 16, CYSUP
The use of CYSUP in SOL 116 causes SFM 3001 in UPARTN. In SOL 16, if
eigenvalues are requested at more than one harmonic, then UFM 1126 in CYCLIC3
is issued.
Avoidance: Insert the DMAP alter:
compile sol16
alter 1
file pvec=save,ovrwrt $
COMPILE MODECYC $
ALTER 'CALL *MODERS'(,-1) $
DELETE /MR1,,,, $
REACT = -1 $
endalter
34592
2004.0.7
OINT - Missing Random Output
Aeroelastic Analysis/Random Analysis - EP
Random analysis with an aeroelastic model fails to yield the acceleration

random output if any random output requests for EPOINT dofs are made.
Avoidance: Make two separate runs, with the epoint data recovery being
requested in a separate runs. The runs will be more efficient if restart is
used.
34602
70.7
S(CORNER) - Wrong Answers
Frequency Response - STRESS(BILIN), STRES
Complex corner stress output for QUAD and TRIA elements is incorrect in
MSC/NASTRAN Version 70.5.2. The value for the real part of the stress at the
grid point will be overwritten with the imaginary value. The results at the
center of the element are not affected.
Avoidance: Other than not requesting the corner stress option, there is no
avoidance.
34604
f Resources
70.6
P-elements - Estimate - Over-prediction o
MSC/ESTIMATE may predict significantly more resources than required for

P-elements. This over-prediction is partially a result of the uncertainty of
the P value.
Avoidance: Do not use MSC/ESTIMATE for P elements.
34613
Aborts
70.6
Cyclic Symmetry - LOADCYN - UFM 4342, Job
If a cyclic symmetry job encounters the fatal message:

USER FATAL MESSAGE 4342 (CY1BLD)
ANALYSIS HARMONICS OR SEGMENT OR SYMMETRY TYPE.
then the job will not produce an "END OF JOB" and will issue the traceback
below:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0xffffffff
0x0000014c
0x00001094
0x00000884
0x0000063c
0x000008c8
0x00000114
0x000009a0
in
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
WriteUnit
_xlfWriteFmt
cy1bld_
cy1ccl_
cycl1_
xsem12_
mainal
--- End of call chain --Avoidance: Although the job should not issue a traceback, the fatal message
output is correct and the user should cor
34652
2001
1 and 2 Produce the Same Loads
Documentation - RFORCE, CTRIAX6 - METHOD
Remark 9 in the MSC/NASTRAN V70.5 Quick Reference Guides for the RFORCE bulk
data entry states:
9. METHOD=2 should be used for the CTRIAX6. METHOD=1 produces null loads.
This is incorrect. Method 1 produces the same loads as method 2.
34665
70.6
- Under-predicts Memory
Estimate - Nonlinear, HEXA, PENTA, TETRA
In a NonLinear analysis (SOL 66, 99, 106, 129, 153,159) the ESTIMATE utility
erroneously assumes the rotational degrees of freedom are fixed for grids
attached only to 3-dimensional elements. The result is that the memory and
disk requirements may be under-predicted.
34666
70.7
Optimization/Design Sensitivity or Super
element- GENEL - Possible Wrong Answers
If the number of GENEL's is an odd number greater than 1, the stiffness terms
produced by the GENEL's will be in error on the second and subsequent design
cycles in SOL 200. Similarly, in other solution sequences, having GENELs in
more than one superelement, or in a superelement and residual structure can
result in some of the GENELS not generating their respective stiffness matrices
which will lead to wrong answers.
Avoidance: Insert the following dmap alter.
compile semg1 $
alter 1 $
type parm,,i,n,nsize $
alter 'sma3.*nogenl','' $
if ( nokggx<0 ) then
paraml kjjz//'trailer'/2/s,n,nsize $
else $
paraml kjjx//'trailer'/2/s,n,nsize $
endif $
matgen ,/knull/7/nsize/nsize $
sma3 gei,knull/kjjy/lusets/nogenl/-1 $
$
34671
70.7
Beam Library - PBARL, PBEAML - Incorrect
Sensitivity for Custom Cross Sections
If custom beam cross section are added to the beam library and they are applied
in the model without providing analytical sensitivities of the beam properties
with respect to the beam dimensions, the sensitivities calculated using finite
difference techniques will be too large in magnitude by 50%.
Avoidance: There is no easy avoidance except to manually scale the gradients.
The sensitivities are of the correct sign and are therefore of some value when
optimizing the cross section.
34699
Heat Transer Analysis - Coupled Convection - SFM 6934
The fatal message below will be encountered if a connection grid is also

specified as an ambient point.
*** SYSTEM FATAL MESSAGE 6934 (EMGPOM)
FOR ELEMENT ID =
100020 AND FILE TYPE =
1
EMGPRO DETERMINES A DIFFERENT COUNT OF ACTIVE CONNECTION SILS THAN DOES
CALLER OF EMGPOM
EMGPRO COUNT =
5 CALLING ROUTINE COUNT =
6
Avoidance: If the PATRAN interface is being used, make sure there are no
overlapping points between application region one and application region two
while applying coupled convection LBCs
Developer's comments:
This is a limitation, because each CONV entry is treated as an element and
duplicated points are not allowed in a single nastran element.
34706
70.6
Restarts - RSSCON - UFM 9086
Running a nonlinear analysis restart with RSSCON entries results in USER FATAL
MESSAGE 9086. In other solution sequences the restart may be inefficient. The
restart fails because of a logic error in subdmap PHASE0.
Avoidance:
compile phase0
alter 'if ( noxsort )',''
equivx geom1/ngeom1/-1 $
endalter
34714
70.6
ements - UFM 7052, Wrong Answers
Optimization/Design Sensitivity - Superel
RTYPE=FREQ was introduced in Version 70 as a "friendly" alternative to

RTYPE=EIGN. When RTYPE=FREQ is used with superelements,
it can produce an incorrect user fatal message:
*** USER FATAL MESSAGE 7052 (DOMPTC)
ILLEGAL PROPERTY NAME
This error was observed when there was no DESOBJ request. When a DESOBJ
request was included, the job ran, but the sensitivity results were incorrect.
Avoidance: Use RTYPE=EIGN and not RTYPE=FREQ when there are superelements.
34740
70.7
Postprocessing - Corrupted XDB
Access Objects with internal keys exceeding 214747 in solution sequences other
than linear statics will corrupt the object maps in the xdb. The internal key
id is a 1 to n list of any particular type of output such as grids, bar
elements, quad elements etc. In the Version 70.5 system, logic has been added
to prevent integer overflow before the access key formation. A FATAL error
indicating that translation has stopped is generated if an overflow condition
is encountered.
Avoidance: Each superelement restarts the 1 to n list for each type of output,
thus splitting the model into superelements is one avoidance.
34756
2001
Documentation/Aeroelastic User's Guide Inconsistent Description of REFC Field
The Aeroelastic User's Guide should be consistent in referring to the REFC
field on the AERO and AEROS entries as being the reference chord. The
following places in the Guide incorrectly refer to REFC as the semichord:
Section 8.2, page 350, should refer to chord rather than semichord.
Section 8.13 (example HA145KR ) incorrectly inputs the reference semichord on
the AERO bulk data entry. The REFC should be 40.0 and the same answers could
be produced if the reduced frequency values were doubled.
Section 9.1, page 578 should refer to chord rather than semichord.
34766
70.7
correct Mass Calculation
Beam Library - PBARL, NSM, TYPE=HEXA = In
For the beam library, PBAR section properties are computed based on the user's
PBARL input. Due to a code error, this computation is incorrect for the NSM
(non-structural mass) property calculation for section TYPE=HEXA. Therefore,
if the mass properties of the BAR are used in the analysis, the answers will be
incorrect.
Avoidance: The PBEAML/PBEAM computation is correct for TYPE=HEXA, so PBEAML's
could be used in place of PBARL's for this section type if the bar is not being
designed. The error is benign in a static analysis without inertial relief or
gravity loads.
34767
70.6
Freedom Identifiers
SSSALTERS - checka - Incorrect Degree of
The output for the checka alter was modified for V69.1. Due to an error in the
alter, the degree of freedom identifiers for the matrices REACCOLN and
REACCOLA will be incorrect.
Avoidance: Change the following line in the alter:
MATGPR GPLS,USETB,SILS,REACcoln//'H'/'G'//printol $
to:
MATGPR GPLS,USETB,SILS,REACcoln//'H'/'N'//printol $
and change the following line:
MATGPR GPLS,USETB,SILS,REACcola//'H'/'G'//printol $
to:
MATGPR GPLS,USETB,SILS,REACcola//'H'/'A'//printol $
34774
70.7
Fluid Elements - GRIDB - UFM 315
In Version 69 and later MSC/NASTRAN releases, when fields 3, 4, and 6 of the

GRIDB entry are used the job will fatal with the following error messages:
FORMAT ERROR ON BULK DATA ENTRY GRIDB
Although the fields are not used, Remark 6 of the Quick Reference Guide's
description of the GRIDB entry clearly states:
"Fields 3, 4, and 6 are ignored, which facilitates the conversion of GRID

entries to GRIDB entries. Note that the fields are the same except for fields
1 and 9 when a cylindrical coordinate system is used."
Thus, allowing information in these fields is an important design feature.
When blanks are used on fields 3, 4, and 6 of the GRIDB in an attempt to
circumvent the above error, if structure with GRIDs i
34781
70.7
, SFM 7340 (LNNHERR)
Eigenvalue Analysis - READ - Poor Message
If a Lanczos eigenvalue analysis requests more modes than exist, it is possible

that the job will fail with the message:
This error has been observed only on small problem where some dofs did not
have independent mass terms.
Avoidance: An avoidance is to set f2 to limit the search region within
plausible limits. For small models where all the eigenvalues are desired a
Givens method may also be selected.
34783
Case Control - MPCFORCE - Incorrect Subcase Labels
If mpcforce output is requested in a multiple subcase run, and not all subcases
have an mpc callout, then the subcase labels for the mpcforce output will be
incorrect. The results, however, are correct. The labels will be in ascending
order of the subcase ids. Using the following case control setup,
Avoidance: Ignore the subcase labels, the results are correct. Else place the
subcases with MPC requests first.
verified fixed in V2001
34784
2001
ect Default Value
Documentation - SYSTEM(198), QRG - Incorr
The MSC/NASTRAN Quick Reference Guide states that the default for SYSTEM(198)
(a.k.a MINFRONT) is 8. The default is actually machine dependent is documented
in the Configuration and Operations Guide.
34795
2044
Nonlinear Static Analysis - PARAM,BUCKLE, Thermal Loads - UFM
In a PARAM,BUCKLE,1 restart with thermal loads, if the PARAM,LOOPID specifies a

loop ID which occurred in a subcase earlier than the previous subcase in the
cold start run, then the restart run will fail with UFM 2044 in the NLCOMB
module.
Avoidance: In the restart run remove all subcases after the subcase in which
PARAM,LOOPID occurred. For example, if the cold start contained 4 subcases and
PARAM,LOOPID value occurred in the 2nd subcase, then remove the third and
fourth subcases in the restart run.
34824
te Output
Nonlinear Analysis - CQUAD4,CTRIA3 TABLEM1 - Wrong Intermedia
All output for the QUAD4 and TRIA3 elements at intermediate steps (NLPARM
INTOUT > 1) is wrong when there exists a temperature dependent material
property.
Avoidance: Other than ignoring the intermediate output there is no avoidance.
34833
70.5
ng or Wrong Corner Force
Frequency Response - Corner Force - Missi
If corner force output ( stress(corner...)=x ) is requested in a frequency

response analysis, the corner force for the QUAD4 will either be missing or
incorrect. This error has been corrected for Version 70.5.
Avoidance: Use the center stress.
34834
g Answers
70.5
Eigenvalue Analysis - PARAM,RESVEC - Wron
If a C-set is defined for a superelement, the component modes are passed thru a
filtering process to remove any which might be a linear combination of the
static transformation. In V70, if residual vectors are not requested, the
component modes will not be passed thru the filter. This may lead to either
rank-deficient matrices or wrong answers. If the filtering is not performed,
the reduced stiffness matrix will incorrectly contain the original eigenvalues
on the diagonal and there will be no off-diagonal terms (as there should be if
the filtering is not performed).
Avoidance: If residual vectors are requested with at lease one loading or
U6-set dof defined, then the filtering will be performed. Otherwise, use
Version 70.5 or later version.
34850
er than f06
Postprocessing - DBC, PARAM,POST - OPNPFL Message to log Rath
DBC OPNPFL messages may be written to the log file rather than the f06.
34874
70.7
elements - Poor Answers
Eigenvalue Analysis - PARAM,RESVEC, Super
If residual vectors are requested in dynamic analysis (PARAM,RESVEC,YES) and

none are appended, the original modes will be lost without warning. The user
should also see related error 34480.
Avoidance: Either do not include residual vectors, make sure that residual
vectors are calculated, or include the following DMAP alter:
compile resvec
alter 'WERE AVAILABLE AFTER FILTERING'
equivx phx/aphx/-1 $
equivx lama/alama/-1 $
endalter
34902
70.7
CVISC, CDAMP - UFM 1126
Optimization/Design Sensitivity - CBUSH,
Optimization (SOL 200) produces User Fatal Messages 1126 when damping element
properties ( CDAMP, CVISC, CBUSH) are active design variables and superelements
are used in the model.
Avoidance: Apply the following DMAP alters:
compile desopt
alter 'type DB'
type db belmdsf, bdictdsf, belmdsb, bdictdsb $
alter 'dopr5'
type db zuzr01
equivx tabdeq/zuzr01/always $
compile fea list
alter 'type parm'
type db zuzr01
alter 'dspt1'(2),'dspt1'(2)
PARAML zuzr01//'TRAILER'/1/S,N,NDVAR $ no. of des. var.
alter 'dspt1'(3),'dspt1'(3)
PARAML zuzr01//'TRAILER'/1/S,N,NDVAR $ no. of des. var.
matprn zuzr01 // $
alter 'trd2'(2),'trd2'(2)
TRD2
CASERS,TRL,NLFT,DIT,KHH,BHH,MHH,PHT,zuzr01,,,/
UHTDS,,TOLSCR/
SOLTYP/NOUE/NONCUP/0 $
COMPILE PSLGDV
alter 'emg,'(3),'
34925
2001
Documentation - QRG - DISPLACEMENT
Remark 2b for the DISPLACEMENT Case Control Command should be modified

from
SORT2 is the default in transient response analysis (structural and heat
transfer). SORT2 is not available for real eigenvalue (including buckling)
complex eigenvalue, or flutter analysis. If SORT1 is selected for one or more
of the commands ACCE, DISP, ENTH, FORC, HDOT, MPCF, OLOA, SPCF, STRA, STRE, and
VELO than the remaining commands will also be output in SORT1 format.
to
transfer). SORT1 is the default in frequency response analysis. SORT2 is not
available for real eigenvalue (including buckling), complex eigenvalue, or
flutter analysis. If SORT1 is selected in a transient solution for one or more
of the c
34926
or 110
2001
Superelements - SEALL - SEP2DR, Logic err
If the SEALL command refers to an undefined superelement, directly or via the

SET command, then the run terminates with "SEP2DR LOGIC ERROR
110".
Avoidance: Correct the undefined superelement references.
34940
2005
SFM 4276, Traceback
Nonlinear Heat Transfer - RADBC, NLITER -
In the radiation dominate problem, the stiffness term is approximately equal to

4*T**3. Therefore, if the guess at the initial temperature value is too low for
the problem, the temperature may rapidly exceed an infinite value and the
traceback that follows will occur:
Trap encountered:
SIGTRAP - Trace trap FP overflow
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
0x00000014
0x00000564
0x00001124
0x00000780
0x00000088
0x00000990
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
zerod_
nrdbcd_
nlemg_
nliter_
xsem15_
mainal
--- End of call chain --Avoidance: Make a better estimate of the initial temperature on the TEMPD bulk
data entry. In general it is safer to have a very high initial temperature
than too low
The deck with default temperature=0.0 ran to the end without errors on v2005t1
of AIX and LINUX platforms.
34949
Plotting - XYPLOT - Bad Scaling of XYPLOT data
The XYPLOT capability fails to scale the xy-plots properly when small values of
displacement exist in the entire frequency range of interest.
Resolution/Avoidance: Use Microsoft Excel to plot the data or scale the model
so the response values are not so small.
34956
Matrix
Aeroelastic Analysis - Panels in XY Plane Produce a Singular
The Quick Reference Guide AERO and AEROS descriptions caution against placing a
lifting surface in the plane of symmetry. The problems associated with this
modelling practice in the XZ plane of symmetry have been removed in Version
70.6. However,
the XY symmetry was not addressed so that vehicles flying in ground effect
(SYMXY=-1) with any panel or body
in the XY plane still produce a singular matrix. The user is also cautioned
not to attempt to perform a SYMXZ=1 (symmetric) analysis with ALL panels and
bodies on the XZ plane.
34967
70.7
M,RESVINER Ignored
If PARAM,RESVINER,YES
inertial loads due to
LOADSET-LSEQ loadings
be ignored. This may
Eigenvalue Analysis - PARAM,RESVEC - PARA

is specified to calculate residual vectors for the
the unit acceleration of mass and there are no
or U6 set degree of freedom, then PARAM,RESVINER,YES will
lead to poor answers.
Avoidance: Include the following DMAP alter for V70.5

compile semodes
alter 'call modef',''
CALL MODEFSRS MR,USET,DM,CASEM,DYNAMICS,MAA,MKAA,GPLS,SILS,EED,
EQEXINS,,PG,GM,GOT,KFS,YS,LLL,KLL,
bgpdts,scstm,cstms,medge/
,,,,PHA,LAMA,PHA0,LAMA0/
APP/NORSET/NOASET/FALSE/0/NOASET/METH/METHF/TRUE/
NOQSET/NSUB/0 $
compile modefsrs
alter 'subdmap',''
SUBDMAP MODEFSRS MR,USET,DM,CASES,DYNAMICS,MAA,KAA,GPLS,SILS,EED,
EQEXINS,VAFS,PG,GM
34969
70.5
FM 4659, UIM 4656 from EHEXD
Optimization/Design Sensitivity - EMG - U
When superelements are used in a shape optimization task with solids elements,
the job may fail in EMG during the sensitivity analysis phase with the user
fatal messages: UFM 4659 and UIM 4656 from routine EHEXD. Other similar error
message may also be issued depending on the type of elements being used in the
model.
35007
70.6
DRMM,0 - UFM 5629, UFM 9058
If PARAM,DDRMM,0 is specified in SOL 200 with ANALYSIS=MFREQ or MTRAN, then the

run will fail with UFM 5269 or UFM 9058, respectively.
compile fea
alter 'delete \/msf1,bsf1,ksf1,,'(,-1)
if ( drmm ) drmm=false $
alter 'IF ( DROPT\=2'(2)
delete /msf1,bsf1,ksf1,, $
IF ( DOSPCF
) call CFORCE1 MSF,M2SF,BSF,B2SF,KSF,K4SF,K2SF,,/
msf1,bsf1,ksf1/
APP/APP/false $
delete /MMG1,BMG1,KMG1,, $
IF ( DOMPCF
) CALL CFORCE1 MMG,M2MG,BMG,B2MG,KMG,K4MG,K2MG,,/
MMG1,BMG1,KMG1/
APP/APP/true $
alter 'destrn\=true'(,-1),'destrn\=true'(,2)
alter 'ELSE if ( drmm )'
destrn=true $
drmm=false $
endalter
35029
70.7
Incorrect Attributes in the XDB
Postprocessing - DBC - LAMA Objects have
When subcases in optimization refer to eigenvalue or buckling analysis, the

LAMA objects in the XDB will have incorrect attributes and this may effect the
ability of other products such as MSC/InCheck to process the results. In
addition, if a frequency range is specified rather than an explicit number of

modes, NASTRAN DBC translation may be incorrectly terminated.
35040
2007.0.0 (MD R2)
tput has Zero Results
Static Analysis - SORT2, PUNCH - Punch Ou
If SORT2 is requested for static analysis results, zero results are written to
the PUNCH file.
Avoidance: The following DMAP alter uses OFP to write the data in f06 format
to an alternate fortran unit thus avoiding the punch unit.
$
$ Output of QUAD4 Element Stress data
$ for post-processing of printed stress in
$ a fortran unit separate from the usual
$ f06 file.
$
COMPILE SEDRCVR,SOUIN=MSCSOU,NOLIST,NOREF
ALTER 'OFP.*OES2S,OSTR2,,,,,','' $
type parm,,i,n,linespp $
linespp=getsys(linespp,9) $
paraml kelm//'trailer'/1/s,n,noelem $ No. of nl elem. in model
noelem=20*noelem $ calc. lines per page to 20 x no. of elem.
putsys(noelem,9) $ set lines per page
putsys(13,2) $ write printed output to unit 13
ofp oes2s,ostr2 // s,n,cardno $
putsys(linespp,9) $ reset lines
35050
dow and UNIX
70.6
Miscellaneous - Data Transfer between Win
When an input file for MSC/NASTRAN is generated in a Microsoft Windows

environment and is moved to a window on a unix computer with the drag and drop
feature, it causes input errors. Each line of input has a "|" symbol at its
end, symbolizing an illegal, unprintable character (carriage return) in the
input, leading to many illegal input messages.
Avoidance: An avoidance is to use a file transfer utility such as ftp instead.
It may require some experimentation to find out if the ftp utility you use
avoids inserting these illegal characters. They are carriage return symbols.
MSC has had success using the ftp option in the EXCEED product.
MSC/NASTRAN itself will delete these spurious carriage returns from its input
files, starting with Version 70.6. If other files are transferred
35054
UFM 6143
70.6
Optimization/Design Sensitivity - INREL -
If inertia relief (PARAM,INREL,-1) is requested in SOL 200 and there are more
than 12 static load cases then the run will fail with UFM 6143 in the MERGE
module in subDMAP INERSEN.
Avoidance: Insert the following DMAP alter in V70 or V70.5:
compile inersen
alter 'nld6\=' $
type parm,,i,n,nz $
nz=nld6-5 $
alter 'vn6r'(2),''
matgen ,/vn6r/4/1/nld6r//6/nz/i661/0/1 $
alter 'vn6r'(4),''
matgen ,/vn6r/4/1/nld6r//6/nz/i661/0/1 $
endalter
35066
- UFM 315
2001
When a DRESP2 bulk data entry is missing a continuation line an error message
is issued but the message indicates that a subsequent DRESP2 is in error. The
message is similar to the following:
FORMAT ERROR ON BULK DATA ENTRY DRESP2
1001
SORTED
ENTRY COUNT =
584
USER INFORMATION : THE FORMAT OF DRESP2 ENTRY HAS BEEN MODIFIED IN
MSC/NASTRAN VERSION 68. PLEASE REFER TO THE QUICK
REFERENCE GUIDE FOR MORE INFORMATION.
USER INFORMATION : PLEASE NOTE THAT THE FORMATS OF THE FOLLOWING DESIGN
OPTIMIZATION ENTRIES HAVE BEEN MODIFIED IN
MSC/NASTRAN VERSION 68 :
DCONSTR DOPTPRM DRESP1
DRESP2
DSCREEN DTABLE
DVPREL1
DVPREL2
*** USER FAT
35067
5423, 6719
70.7
Frequency Response - PBUSH, PELAST - UFM
In SOL 111, if there are frequency dependent elements, and if the a-set equals
the g-set, the modal reduction of the frequency dependent matrices is not
performed. In a structural analysis, this results in UFM 5423, and in an
acoustic (uncoupled) analysis, the result is SFM 6719.
Avoidance: Add a dummy SPC.
35096
0 (SB85RD)
70.7
Iterative Solver - ITER, DEFORM - SFM 698
A job that uses the iterative solver and specifies DEFORM type loads failed
with the message:
*** SYSTEM FATAL MESSAGE 6980 (SB85RD)
LARGEST BLOCK ROW OF THE INITIAL MATRIX ( 85606 WORDS) EXCEEDS THE
SPECIFIED MAXIMUM RECORD LENGTH ( 65536 WORDS).
USER ACTION: PLEASE CONTACT MSC CLIENT SUPPORT.
MODULE = SOLVIT
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE
USER ACTION: INCREASE OPEN CORE BY AT LEAST
20070 WORDS
PROGRAMMER INFORMATION: LOCATION KEY = M
FATAL ERROR
Avoidance: Increasing memory may solve the problem but it is likely that the
sparse solver will need to be selected.
35117
Answers
70.7
Acoustic Analysis - FORCE(PHASE) - Wrong
When magnitude/phase force output is requested for fluid elements,

real/imaginary outputs are printed in the magnitude/phase format instead.

35121
70.7
DRESP2 - UFM 7139 (DOPR3C)
When an unreferenced DRESP1 entry of RTYPE=FREQ appears in a superelement

optimization job the fatal message below may occur:
*** USER FATAL MESSAGE 7139 (DOPR3C)
ON DRESP2 entry ID =
10, RESP1 ID =
EXISTING DRESP1 ENTRY.
1001 DOES NOT REFERENCE AN
Avoidances:
1) Remove the unreferenced DRESP1 entry using RTYPE=FREQ or
2) Use RTYPE=EIGN instead of RTYPE=FREQ
35138
70.7
no longer needed
Documentation/SSSALTER - prldbckla.v706 -
Buckling with preload has been included in the standard 105 solution sequence
in v70.6. Therefore, the prldbcka alter is no longer needed.
Avoidance: The new capability is invoked through the STATSUB Case Control
command. The documentation for STATSUB in Version 70.6 follows:
Format:
STATSUB[(BUCKLING)]=n
(PRELOAD)
Examples:
STATSUB=23
STAT=4
STATSUB(PRELOAD)=7
Describer
Meaning
BUCKLING
Subcase id number corresponding to static subcase of buckling or
varying load (default in buckling analysis)

PRELOAD
Subcase id number corresponding to static subcase of preload or
constant load (default in dynamic analysis)
n
Subcase identification number of a prior SUBCASE specified for s
tatic
analysis (Integer>0)
Remarks:
1. Unchanged
2. Unchanged
3. R
35139
5
70.7
Inertia Relief - param,inrel,-1 - UFM 910
If param,inrel,-1 is included in the input file for a solution sequence that

does not use inertia relief (e.g., sol 103), then the job will terminate with
the following error messages:

^^^ A SUPORTI BULK DATA ENTRY IS NOT PRESENT
(PARAM,INREL,-1).
FOR INERTIA RELIEF ANALYSIS
Avoidance: Remove param,inrel,-1 from the input file since it is not used in a
non inertia relief run.
35141
70.7
PARAM,MODACC, CVISCi - Wrong Answers
Frequency Response/Complex Eigenvalues -
If PARAM,MODACC,>-1 is specified in SOLs 110, 111, 146, or 200 with ANAL=MFREQ

and the model contains viscous damping then wrong answers will result.
compile gma
alter 'call xADD5 K2XDD'
equivx b2ydd/b2dd/-1 $
endalter
35143
70.6
SFM 1015 (GBKMGR)
Optimization/Design Sensitivity - DSADJ -
The fatal message:

SYSTEM FATAL MESSAGE 1015 (GBKMGR)
may occur in the DSADJ module and has been attributed to an incorrect
assessment of the amount of open core available.
Avoidance: The message has only occurred when running with a small memory
request. A possible avoidance is to increase the memory request.
35154
70.7
Superelements - BEGIN SUPER - SFM 3007
In a superelement analysis using PARTS, if more than 12 points occupy the SAME
location at the boundary in the same superelement, then the job will fail with
*** SYSTEM FATAL MESSAGE 3007 (SEP1X)
ILLEGAL INPUT TO SUBROUTINE SEPBSD
0FATAL ERROR
Avoidance: Do not define more than 12 points occupying the same location at
the boundary for a single part superelement.
35158
70.7
DMAP - LCGEN - SFM 3007, Poor Message
If the first input, usually CASES, to LCGEN is purged then SFM 3007 is issued.
SFM 3001 should be issued instead.
35187
2001
Miscellaneous - UFM 6440 (MODGM2)
If double-field entries are used to enter property ID's longer than 8 digits,
then it is possible to obtain USER FATAL MESSAGE 6440 indicating that a
property id is not found even though it exists in the input file. The cause of
this error is the sorting routine which uses only the first 8 digits of the id.
The problem will only occur if property ID's which are both 8-digit and longer
than 8-digits exist in the input.
Avoidance: Either keep the property ids less than 9 digits, or use all
property ids greater than 8 digits in length.
35188
70.7
Restarts - SFM 471
The database of large restart runs may be corrupted when data spills from one
file to another. In the restart run the error may lead to the message:
** ERROR ** UNABLE TO VALIDATE DATABASE FILE FORMAT. DATABASE MAY NOT HAVE
BEEN BUILT ON A COMPATIBLE PLATFORM.
BIOPNR ERROR ** TIMESTAMP/RECL VALIDATION FAILED. FILX = 30, LOGNAME =
DBALL5 , NSBUF3 =
4096
FILE = /disk/tmp/test.dball
TIMESTAMP OFFSET INVALID.
*** SYSTEM FATAL MESSAGE 471 (DGETTS)
ERROR ATTEMPTING TO OPEN THE FOLLOWING PHYSICAL FILE NAME (PFILEX= 30) :
/disk/tmp/test.dball
USER ACTION: 1) CHECK THE READ/WRITE PRIVILEGES GRANTED THIS FILE.
2) CHECK MAXIMUM NUMBER OF FILES THAT MAY BE OPENED
SIMULTANEOUSLY.
3) CHECK THAT THIS DATABASE FILE IS COMPATIBL
35197
2001
DVPRELi - Unexpected Results
Documentation/Optimization - QRG, PBUSH,
The Quick Reference Guide fails to document that when a property on a PBUSH
entry is designed a negative FID number must be specified on the DVPREL1 and
DVPREL2 entries. If a positive FID number is specified on a DVPREL1/2 entry,
unexpected results may occur.
Avoidance: Use a negative word position number from the element property table
for the FID field on the DVPREL1/2 entry. The following table provides the word
positions for the PBUSH entry in the element property table.
EPT Section for PTYPE = "PBUSH"
Word
1
2 through 7
8 through 13
14
35200
QRG
Type
I
R
R
R
2001
Item
Property ID
K1 through K6
B1 through B6
Documentation - QRG - FSLIST Missing from
Version 69 and later Quick Reference Guides do not have a description for the
FSLIST bulk data entry.
Avoidance: See the V68 Quick Reference Guide or the Fluid-Structure Seminar
Notes for the description. An abbreviated description follows:
FSLIST
Defines the fluid points (RINGFL entry) that lie on a free surface boundary.
Format:
FSLIST, RHO, IDF1,IDF2,IDF3........

Field
Contents
RHO
Mass density at the surface. Real>0.0; the default is taken from
DRHO on
the AXIF entry).
IDFi
Identification number of RINGFL entry. (Integer>0 or Character="
AXIS" in
first and/or last field only)
Remarks:
1. This entry is allowed only if an AXIF entry is also present.
2. The order of the points must be sequential with the fluid on the right with
respect to the directi
35206
70.7
rong Answers, UFM 5423
External Superelements - PARAM,EXTOUT - W
If external superelements are used and restarts are performed, the restart
logic will insist on re-processing the external superelements and any
downstream superelements whether or not any changes are made to the model. If
the superelements are created using PARAM,EXTOUT,DMIGDB, this may result in
incorrect answers or UFM 5423 indicating an incompatible matrix multiply.
Avoidance: When restarting from a run which read in external superelements
which were created using PARAM,EXTOUT,DMIGDB insert the following DMAP alter:
compile extin
alter 'IF.*NOKAA.*0.*THEN',''
IF ( NOKAA>0 and nomatk<0) THEN $
35217
70.7
GDB - Inefficient Restarts
External Superelements - PARAM,EXTOUT,DMI
If external superelements are used and restarts are performed, the restart
logic will insist on re-processing the external superelements and any
downstream superelements whether or not any changes are made to the model.
Avoidance: The following alter will disable the deletions for external
superelements. If any changes are made to the external superelements, this
alter should not be used.
compile phase0
alter 'INVOKE ALL RESTART DELETIONS HERE',''
if(setype<>'EXTRNA')RESTART ,,,HISTS/TLIST/TRUE $
35234
age
70.7
Miscellaneous - DPD - UFM 2079, Poor Mess
The text of UFM 2079 is incorrect. The text reads:

*** USER FATAL MESSAGE 2079 (DPD) GRID OR SCALAR POINT <nn> HAS AN UNDEFINED
COORDINATE REFERENCED ON A <xxxx> ENTRY.

Both of the the values "nn" and "xxxx" may be wrong and words "UNDEFINED
COORDINATE" should be "ILLEGAL COMPONENT".
35246
70.7
or 32 on Large Matrices
Matrix Methods - MPYAD - SFM 4276 EC 3002
It is possible that MPYAD may fail with SFM 4276 EC 3002 or 32 when very large,
dense matrices are being multiplied. The client model that encountered this
error had a very long duration transient analysis (more than 100000 time
steps). This model failed during mode-acceleration data recovery in module DDR2
(using MPYAD).
Avoidance: It is possible that providing more memory may allow the run to
finish. For the problem mentioned above, using residual vectors
(PARAM,RESVEC,YES) instead of mode-acceleration allows the run to complete. If
you are encountering this problem in a run using mode-acceleration, try using
residual vectors instead of mode-acceleration.
35259
ng answers
70.7
Nonlinear Transient Response - LSEQ - Wro
If LSEQ entries are used in SOL 129 and the DAREA and LID fields have the same
ID, then the dynamic loads which are based on the LSEQ entries will be doubled
and wrong answers will result.
compile nltran
alter 'trlg ',''
TRLG
CASESX2H,USETD,DLT,,BGPDTS,SILS,CSTMS,TRL,DIT,
GMD,GOD,,EST,MPTS,/,,,PDT,,TELH,DLT1/
/S,N,DCOL/IMETHOD/RSTIME/BETA/S,N,FAC1/S,N,FAC2/
S,N,FAC3//TABS $
endalter
35261
70.7
Heat Transfer - CHBDYG, NLCOMB - UFM 4017
If the area of a CHBDY element is less than 1.E-10, than the job may fail with
the message:
0*** USER
FATAL
MESSAGE 4017, ESTNL AND FILE (103) ARE NOT PROPERLY
ALIGNED
*** SYSTEM FATAL MESSAGE 3007 (NLCOMB)
ILLEGAL INPUT TO SUBROUTINE NLCKDT
0FATAL ERROR
Avoidance: This error may be caused by a poor selection of units. Change the
units to increase the size of the element.
35277
g Answers
70.7
Static Analysis - LOAD, TEMP, GRAV - Wron
If a LOAD bulk data entry references a TEMP bulk data entry which has already
been referenced by a previous subcase (TEMP(LOAD)), then the temperature loads
are ignored and wrong answers are produced for all subcases which contain GRAV
or TEMP loads. In addition, then the warning message below, will not be
issued:
USER WARNING MESSAGE 3204 (SSG1)

UNABLE TO FIND SELECTED SET (
2) IN TABLE (SLT ) IN SUBROUTINE (SSG1)
Avoidance: Do not reference TEMP bulk data entries from the LOAD bulk data
entry. In order to combine temperature and mechanical loads, use a LOAD case
control entry to specify the static loads, in combination with the TEMP(LOAD)
case control entry to specify the TEMP loads.
35280
70.7
PANELMP - Wrong answers
Coupled Fluid/Structure Analysis - PARAM,
In a coupled modal frequency response analysis (SOL 111), if there is no ASETi

or OMITi entries, rigid elements, multipoint constraints nor single point
constraints, all panel participation factors are zero.
Avoidance: Add 1 dummy grid with all degrees of freedom constrained.
35289
70.7
Miscellaneous - DBLOCATE - UFM 453
DBLOCATE fails if the MASTER dbset is assigned twice under different logical
names and the first assignment is not used on a DBLOCATE statement. The
following is an example of the input and fatal message:
ACQUIRE NDDL
ASSIGN ADB_1='test.MASTER.2'
DBLOCATE LOGICAL=ADB_2 WHERE(DBSET='ADB' OR DBSET='AEDB') $
ASSIGN ADB_2='test.MASTER.2'
DBDICT
ENDJOB
35295
2004
- Inertia Relief
Documentation/Linear Static User's Guide
In SOL 101, inertia relief is calculated differently than in SOL 1. The

description of inertia relief in the Linear Statics User's Guide describes the
method used in SOL 1 to calculate the accelerations. In SOL 101, the approach
is different. In SOL 101, 6 additional loads are created. These loads are
created by applying unit accelerations in each of the 6 dof about PARAM,GRDPNT.
The matrix URA is the accelerations required on these 6 new loads to provide
static equilibrium when combined with the original loadings. In SOL 1, the
accelerations about the SUPORT dof are calculated.
35298
ge
70.7.2
DMAP - SDR1, UMERGE1, UMERGE - Poor messa
When two matrices are being merged row-wise in modules SDR1, UMERGE1, SSG4,
DDR2, and READ and the number of columns in each matrix do not match, then the
following message is issued. This error also occurs in UMERGE and UMERGE1 if
the the number of zeros and non-zeros in the partitioning vector do not match
the corresponding number of rows and columns in the sub-matrices.
ERROR CODE
31 PID=
along with the following traceback

Traceback:
Offset 0x00000020
Offset 0x00000020
Offset 0x00000184
Offset 0x0000016c
Offset 0x00004000
Offset 0x00000480
Offset 0x000001ac
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
raise
tracbak_
nsexit_
pexit_
gperr_
getstr_
m
35314
2004.5
Buckling Analysis - Insufficient memory SFM 3001,1015, Out of range, Error 924
In a buckling analysis and possibly other eigenvalue solutions, if insufficient
memory is allocated, then depending on the machine and number of cpus
requested, the job may fail with any one of the following unclear messages:
1. *** SYSTEM FATAL MESSAGE 3001 ()
xx DOES NOT EXIST
2. *** SYSTEM FATAL MESSAGE 1015 (GBKMGR)

PHYSICAL FILE NOT FOUND IN FILE ASSIGNMENT TABLE
BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGR , FILE INDEX (FILEX) =
0
STATUS =
0
3. BIORD ERROR - FILX =
0(00000000 HEX) OUT OF RANGE
BIOMSG: ERROR 924 HAS OCCURRED IN ROUTINE IONAST , FILE INDEX (FILEX) =
0
BIOWRT ERROR - FILX =
0(00000000 HEX) OUT OF RANGE
0*** SYSTEM FATAL M
35315
2001
ive after job is killed
Parallel Processing - Process remains act
If a model using parallel on HPUX 10.20 is 'killed' by the system (for example,
due to a full disk or exceeding file size limits), it is possible that a
process may still remain active, possibly with a high CPU usage.
Avoidance:
If this occurs, use 'kill -9 pid' (where pid is the process id obtained using
ps -ef) to 'kill' the remaining process.
35324
Submittal - No Output
If an MSC/NASTRAN output file is opened by some other program, that other

program may prevent MSC/NASTRAN from using the file. If it does, an error
message such as the following may be displayed:
*** SYSTEM FATAL MESSAGE (pgm: nastran, fn: run_job)
Unable to rename:
./d10101d.out
to
./d10101d.out.1
Avoidance: Close any MSC/NASTRAN output files in use by other programs.
35333
Nonlinear Analysis - CBUSH, PBUSHT - Nonlinear Affects Ignore
d
If a nonlinear model contains a CBUSH element, no nonlinear materials, and
PARAM,LGDISP is not set, NASTRAN will solve the problem as a linear analysis.
Avoidance: Add PARAM,LGDISP to the deck.
35370
70.7.2
ibuted Memory Parallel Hangs
Eigenvalue Analysis - READ, EIGRL - Distr
MSC/NASTRAN Version 70.5.4 for IBM/SP computers introduces Distributed Memory

Parallel Lanczos as a beta capability. There are known problems with the
capability that may cause the system to hang. The problems include
1. If the master node does not find any roots the job will fail, and if bat=no
is set the job will hang. This problem may be avoided by selecting a different
number of processors. This problem may be also be caused by error 2 below.
2. If dmp=n is specified on the submittal line but nastran numseg=x is not
specified in the data deck or rc file, numseg will automatically be set to n.
This action changes the shift logic which often causes the master node to find
any roots. Error number 1 above is then encountered. An avoidance is to
explicitly specify numseg.
35410
Nonlinear Transient Response - SPC, LSEQ - SFM 6920 in MATMOD
In SOL 129, if the number of unique, with respect to DAREA ID, LSEQ Bulk Data
entries is less than the number of subcases and static enforced displacements
are specified, then SFM 6920 will be issued from the MATMOD module.
compile nltran
alter 'MATMOD YST',''
paraml yst//'trai'/1/s,n,yscol $
if ( yscol>1 ) then $
MATMOD YST,,,,,/YS,/1/1 $
else $
equivx yst/ys/-1 $
endif $ yscol>1
alter 'MATMOD YST'(2),''
paraml yst//'trai'/1/s,n,yscol $
if ( yscol>1 ) then $
MATMOD YST,,,,,/YSt1,/1/1 $
else $
equivx yst/yst1/-1 $
endif $ yscol>1
35411
70.6
Submittal - news=yes - UFM 756 (XCSA)
If an include statement is the first line of an input deck or follows

immediately after a NASTRAN statement and news=yes is requested, then the job
may fail with the message:
USER FATAL MESSAGE 756 (XCSA)
THE BEGIN
CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION.
USER INFORMATION: THE BEGIN STATEMENT IN THE EXECUTIVE CONTROL SECTION HAS
BEEN REPLACED BY THE SUBDMAP DMAP
STATEMENT. SEE USER MANUAL SECTION 5.
ENDDATA
*** USER FATAL MESSAGE 765 (XREAD)

END-OF-FILE ENCOUNTERED ON UNIT
1. THE INPUT FILE IS INCOMPLETE.
USER INFORMATION: THE FOLLOWING GUIDE LINES SHOULD BE FOLLOWED FOR
PREPARATION OF AN INPUT DECK.
FILE MANAGEMENT SECTION (FMS) CAN BE ENDED BY EITHER AN "ENDJOB" OR A
NON-FMS CARD.
35415
70.7
, SET - SFM 3003 (DOPR3)
Optimization/Design Sensitivity - REPCASE
The fatal message shown below may be issued in an optimization job if there are
REPCASE subcases but no SETt case control commands (all the data recovery
requests = ALL)
*** SYSTEM FATAL MESSAGE 3003 (DOPR3) ATTEMPT TO READ PAST RECORD IN DATA
BLOCK
Avoidance: Place a set command in the case control.
35460
2001
AM,SNORM - SFM 4276
Nonlinear Transient Analysis - NLTRD, PAR
A nonlinear transient run may give a traceback similar to the following when
param,snorm is used.
+80
+81
+82
+83
+84
+85
+86
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Avoidance:
0x000001c4
0x0000003c
0x00001688
0x00000258
0x00001124
0x000004c0
0x000001a4
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
getnml_
gshnod_
nqd4d_
nembrd_
nlemg_
nltrd_
xsem15_
Do not specify param,snorm.
35483
70.7
ng Message with ff_io=no
Performance - SGI Only, Implausible Warni
MSC/NASTRAN V70.5(r4) mistakenly omitted support for EAG FFIO in the template
file. On some jobs this may lead to a slight degradation in I/O performance
and hence longer run times.
Avoidance: This can be corrected by updating:
<install-dir>/bin/nast705.lcl
After line 143, which currently reads:
%MSC_ARCH=irix64:%%threads:%
print "MP_SUGNUMTHD_VERBOSE: %thread_ver
bose%"
the following lines can be added:
%MSC_ARCH=irix64:%%ff_io=^[ya]:%%ff_io_opts:%
export
FF_IO_OPTS='%ff_io_opts%'
%MSC_ARCH=irix64:%%ff_io=^[ya]:%%ff_io_defaults:%
export
FF_IO_DEFAULTS='%ff_io_defaults%'
%MSC_ARCH=irix64:%%ff_io=^[ya]:%
print "EAG FFIO enabled."
print "FF_IO_OPTS:
$FF_IO_OPTS"
print "FF_I
35508
2008.0.0 (MD R3)
sless Mechanisms
Eigevalue Analysis - READ - UIM 4158, Mas
Eigenvalue analysis of models with massless mechanisms may fail in the READ
module with the following messages:
*** USER INFORMATION MESSAGE 4158 (DFMSA)
---- STATISTICS FOR SPARSE DECOMPOSITION OF DATA BLOCK KFF
FOLLOW
NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL =
5
MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL = 1.0E+15 AT ROW
NUMBER
4*** SYSTEM FATAL MESSAGE 7340 (LNNHERR)
process error reported by subroutine LNNP1ED
see LNNP1ED abstract (ier = -729)
process error reported by subroutine LNNDRVD
see LNNDRVD abstract (ier = -729)
Avoidance: Add a small amount of mass to the mechanism or remove the mechanism.
35547
70.5.5
ank space in path
ESTIMATE - Will not work if there is a bl
If a directory in the path to the file contains a blank space (for example
('Program Files'), MSC/ESTIMATE will not be able to find the input file and
will fail.
Avoidance: Do not include blank spaces in directory names.
35549
2005.1
l input to subroutine SEPEXT
Superelements - SFM 3007 (SEP1X), Illega
If an EXTRN entry is not used when trying to use the new (V69+) external
superelements, the run will fail and issue SYSTEM FATAL MESSAGE 3007 indicating
illegal input to subroutine SEPEXT. The run will then terminate.
Avoidance: Be sure to use an EXTRN entry when using the external superelements.
35551
6739 (SEP2MP)
70.7
Superelements - THRU, SPOINT, EXTRN - UFM
If the THRU range is used on the EXTRN entry for a set of SPOINTs, the program
will incorrectly issue UFM 6739 stating that the SPOINTs are specified with a
nonzero degree of freedom
Avoidance: Do not use the THRU option on the EXTRN for SPOINTs.
35562
rs
70.7
Aeroelastic Analysis - TRIM - Wrong Answe
Version 70.5 introduced the capability in SOL 144 to trim an aircraft that had
more free variables than there are free degrees of freedom. The results from
this Generic Control System capability will be in error unless the aerodynamic
extra points (AESTAT and AESURF) specified on the TRIM bulk data entry are in
ascending ID order.
Avoidance: When there are redundant control surfaces, list the known trim
variables on the TRIM entry in ascending ID order. The ID's are those entered
on the AESTAT and AESURF bulk data entries.
35603
70.7
Parallel - Confusing Messages
Parallel Processing - Distributed Memory
At submittal, confusing error messages may be issued to the terminal when

running MSC/NASTRAN V70.5.3 or V70.5.4 on AIX in distributed mode. The various
messages may lead you to believe the job has failed even though it hasn't. The
error messages will be displayed if the IBM Parallel Environment for AIX V2.4
or later is installed.
Avoidance: The messages may be ignored or they may be avoided by changing the
following line in the <install-dir>/bin/nast705.dmp file from:
%MSC_ARCH=aix:%
print -u3 $host %cpu_use% %adapter_use%
%MSC_ARCH=aix:%
print -u3 $host
to
35615
Missing output
Aeroelastic Analysis - scr=mini, multiple subcases, SOL 145 -
If multiple flutter subcases are specified in a SOL 145 job and the job is run
with scr=mini, then the job will only process the first subcase and ignore
subsequent subcases.
compile super3
alter 'saverstl\=',''
compile sefluttr
alter 'call super3'(,1)
if ( saverst='sedr' ) saverstl=true $
compile sedisp
alter 1
file ol1s=ovrwrt $
endalter
35619
70.7
esired Roots not Found
Complex Eigenvalue Analysis - Number of D
Prior to MSC/NASTRAN 70.7 the Complex Lanczos eigenvalue method would require
the user to specify many shifts to find many modes in a lightly damped system.
Beginning in Version 70.7, an the system will automatically choose new shifts
until the desired number of modes is found.
35622
70.5.2
ing the Called Program
DMAP - ISHELL may have Difficulties Locat
In versions prior to V70.5.2, the ISHELL module may have difficulty locating
the called program file. This may result in the fatal message:
^^^ PRECLOSING FORTIO UNIT
25
^^^ ISHELL PROCESS RETURN CODE:
^^^ ISHELL FAILED WITH RETURN CODE
1
1
Starting with V70.5.2, the search logic has been improved to search for
different file extensions and thru the path correctly.
Avoidance: If you are using ISHELL in a version prior to V70.5.2, use a program
name containing the exact name specified in the ISHELL statement (upper-case
only, maximum of 8 characters including the extension) and make sure that the
program is in the current directory.
35630
Postprocessing/Eigenvalue Analysis - PARAM,POST- Wrong Eigenv
ector Labels in XDB
If multiple eigensolutions are requested in SOL 103 with PARAM,POST,0, then the
eigenvectors will be labeled incorrectly in the xdb file.
Avoidance: Use PARAM,POST,-1 or insert the following DMAP alter:
compile super3
alter 'EQUIVX CASECC',''
EQUIVX CASErs/CASESEP4/-1 $
endalter
35633
Acoustic Analysis - Missing Output
In solution 108, if displacements are requested for fluid grids, and

accelerations are requested for structural grids, then no fluid grid pressures
will be output..
Avoidance: Solution l111 works correctly.
35646
- UFM 9101
70.7
Acoustic Analysis/Superelements - CAABSF
If a fluid superelement is used, and frequency dependent acoustic absorbers

(CAABSF) are correctly put in the residual with their fluid grids (in order to
keep them frequency dependent), then an error message similar to the following
is erroneously invoked causing the run to fail prematurely:
^^^ BULK DATA AND CASE CONTROL PARTITIONING,
RESTART CHECKING, AND
UNDEFORMED PLOTTING IS
^^^ INITIATED FOR SUPERELEMENT
0
^^^ FLUID ELEMENTS ARE DETECTED IN THIS SUPERELEMENT.
^^^ USER ACTION: ENSURE THAT ALL FLUID ELEMENTS
ARE ASSIGNED TO
SUPERELEMENT
2000
compile phase0
alter '9101'(,-1),''
paraml ects//'trailer'/5/s,n,trwd5 $ bits 161-176 and 65-80
type parm,,logi,n
35647
ed Grid Point
70.7
Elements - CBEAM, GP2 - UFM 2007, Undefin
If a model contains both CBAR and CBEAM elements and the value of BIT is set to
0.0 on a CBEAM entry and p-elements are not being used, the run will fail with
UFM 2007 stating that the BEAM element references an undefined GRID point.
ELEMENT xx REFERENCES UNDEFINED GRID POINT yyy
Avoidance: Do not place a value in the BIT field of the BEAM element unless
you are using p-elements.
35657
on of Remark 1
2001
Documentation/QRG - THERMAL - Clarificati
The following remark should be added to THERMAL case control command

description in the Quick Reference Guide.
3. In a transient heat transfer analysis the SID on the punched TEMP bulk data
entries equal the time step number.
35695
copied.
Restarts - Nastran fails to trap invalid dbset that have been
Nastran fails to trap invalid copies of DBSETs used in RESTART (or reuse) runs.
The following sequence demonstrates the problem:
> nastran s31498a.dat
# cold start run creates s31498a.MASTER
and s31498a.DBALL
> cp s31498a.MASTER s31498b.MASTER
# copy s*a.MASTER to s*b.MASTER; DBALL is
not copied
> nastran s31498b.dat
# run using s*b.MASTER; nastran finds
s*a.DBALL using autoassign
> nastran s31498a.dat
# run using s*a.MASTER; nastran fails to
recognize s*a.DBALL was modified above and is no
# longer in synch with
s*a.MASTER
35726
2001
ID COULD NOT BE FOUND
Elements - CBUSH - UWM 979 (XYTRAN), THE
Trying to use XYPLOT for CBUSH postprocessing results in the following error
message:
AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID
n
-FORC- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA
BLOCK
106
35743
70.7
tries with no Fxed Parameters
Aeroelastic Analysis - IFP - UFM, TRIM En
If you define a TRIM subcase in MSC/NASTRAN in which all trim parameters

(aerodynamic extra points) are FREE, the resultant MSC/NASTRAN execution will
fail due to an illegal TRIM Bulk Data Entry.MSC/NASTRAN considers it to be
illegal to have a TRIM entry with zero PARAM/VALUE pairs. That TRIM entry would
imply that all parameters were FREE, something that is not necessarily illegal,
even for regular TRIM.
Avoidance: Specify at least one parameter that is fixed at some value.
35745
2001
1126 (GNFIST) or 2011 (TA1)
Elements - PBARL/PBEAML, SOLs 1-16 - UFM
PBARL and/or PBEAML entries do not work in SOL 1. They cause the following
error message:
in V69.0 - V70.0;
DMAP MODULE MODEPT IS ATTEMPTING TO OUTPUT DATABLOCK
201 NAME =
IEPT
USER ACTION: DELETE THE DATABLOCK, OR USE FILE IEPT
=OVRWRT
FATAL ERROR
or UFM 2011 (TA1) in V70.5;

*** USER FATAL MESSAGE 2011 (TA1)
NO PROPERTY ENTRY FOR ELEMENT TYPE BAR
NO PROPERTY ENTRY FOR ELEMENT TYPE BEAM
0FATAL ERROR
Avoidance: Insert the following DMAP alter in SOLs 1-16:
MALTER 'IFP9
EPT',''
IFP9
EPT.7/IEPTX/S,N,NOGOIFP9 $
endalter
35754
70.7
entation in NT C.O.G.
Documentation - Missing Beam Server Docum
The documentation for the beam server is missing from the "Configuration and
Operations Guide, Windows NT Edition".
Avoidance: The UNIX documentation can be used in its place.
35760
tent Answers
GL
Transient Analysis - MPCFORCES - Inconsis
In a transient analysis, the MPCFORCES may appear incorrect because they may
vary when the independent and dependent degrees of freedom are reversed.
This is due to the inconsistency between the way the "equilibrium" is
calculated using the modified Newmark integration scheme (which is evaluated at
3 time steps-- Un+1, Un, and Un-1) and the MPCFORCE data recovery (which is
evaluated at Un).
Avoidance: Use a smaller time step if mpcforces are desired. The error is
negligible if (delta t)**2 * acc << disp
35762
ers
2001
DMAP - MATMOD, P1=4 - Possible Wrong Answ
Matmod option 4 (p1=4) does not produce the correct output matrix when using
form 2 (LUSETS).
Avoidance: Use form 1 (SILS) instead of form 2
35765
Nonlinear Analysis - ITER - UFM 3032 (NLITER), Poor Message
If the ITER entry uses the free field keyword approach but it is entered
incorrectly a misleading fatal message may result. For example the entry
"ITER,100,IPAD=3" lead to the following fatal message:
*** USER FATAL MESSAGE 3032 (NLITER)
100) IN TABLE (
0FATAL ERROR
This entry should have been:
ITER,100
,IPAD=3
35778
Superelements - SELOC, SEP1X - Poor Message
If the GRID points or POINTs listed on a SELOC entry in the PBi fields do not
have the same relative geometry as the GRID points listed in the PAi fields,
then the following misleading error message may occur:
*** USER FATAL MESSAGE 6790 (SEPO21)
THE FOLLOWING SUPERELEMENTS ARE DETACHED:
Avoidance: Be sure that the relative geometry is correct.
I believe that the intent of the quality is related to the content of the
message 6790 which was broken when MSGPOP was introduced. It was changed
during the 2004 release under 1-4266901 and is more distinct. I do not believe
it is related to the SELOC since all integrety tests were passed and a correct
SCSTM matrix was produced. Since unattached parts can exist outside the domain
of REPEAT usage, I believe the current messages are sufficient.
35781
70.7
nlinear Stresses, SWM 6065 (DBC)
Nonlinear Analysis - PSHELL, MID2=-1 - No
If plane stress elements are mixed with plane strain elements (i.e., PSHELL
with MID2=-1) then garbage may appear in the nonlinear stress output and if
PARAM,POST,0 is selected then the DBC module will issue the following warning
message:
SYSTEM WARNING MESSAGE 6065 (DBC)
DBCMSG ERROR MESSAGE 22 FROM SUBROUTINE ELMBLK
35790
RFORCE - SOL 103, Followk - Wrong Answers
RFORCE follower force effects (param,followk) were included in Version 70.6.

However, it was not documented that only RFORCE method 2 is supported. If
method 1 is chosen follower force effects are ignored.
Avoidance: Use method 2 for the RFORCE.
35819
RP)
70.7
Superelement - RROD, RBAR- UFM 6591 (SEP2
If RROD or RBAR elements are used to connect interior and exterior degrees of
freedom on a PART superelement, the run may incorrectly fail with the
message:
*** USER FATAL MESSAGE 6591 (SEP2RP)
RIGID ELEMENT DEFINES DEPENDENT EXTERIOR POINTS
Avoidance: An avoidance which sometimes works is to interchange the ga and gb
points, and their related data. This behavior has not been found using other
rigid elements, such as the RBE2.
35821
2001
equired for Ply Stresses
Documentation/QRG - PCOMP - ELFORCE Not R
In the MSC/NASTRAN Quick Reference Guide, Remark 7 under the PCOMP entry which
states that an ELFORCE and ELSTRESS request is necessary for composite ply
stresses is no longer true. Only a STRESS request is required.
35845
Iterative Solver - PARAM CDITER, NASTRAN ITER=YES
The iterative solver produces incorrect results for the SPCFORCE RESULTANT when
the linear gap (PARAM,CDITER) is used.
Avoidance: Use the direct solver or ignore the spcforce resultant output.
35851
70.6
DMAP - ISHELL - Access Violation on NT
A call to the ISHELL module in Version 70.5 on Windows NT may fail with an
Access Violation.
Avoidance: Two possible avoidance exist. If the problem occurs, use Version
70.6 or higher. Else, use character parameters whose length is 8 characters
with no blank spaces. The workaround for Version 70.5 may not always work.
Whether or not the access violation occurs depends on the contents of the
various data fields and is unpredictable.
35857
Message
Nonlinear Transient Analysis - PCOMP, STRESS - SFM 1013, Poor
Composite materials run in sol 129 that request stress output may fail with the
message:
*** SYSTEM FATAL MESSAGE 1013 (GBKMGR)
BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGR , FILE INDEX (FILEX) = 0
Avoidance: Do not use the STRESS= case control command since nonlinear
transient analysis does not support composite data recovery. Else substitute
equivalent PSHELL/MAT2 entries for the PCOMP entries.
35876
70.7
rices Incorrect
SSSALTERs - checka - Effective Weight Mat
Output for the checka.vxx alter has the row and column output for the modal
effective mass and FRACTOT output incorrectly labeled. It should state that
each column represents a mode and each row represents an associated degree of
freedom.
Avoidance: Edit the alter to correct the printout form or request an updated
copy from MSC.
35877
70.7
rrect DOF Identified
Rigid Elements - RSPLINE - UFM 5289, Inco
If an RSPLINE specifies dependent degrees of freedom that have already been

specified as dependent by another RSPLINE entry, then USER FATAL MESSAGE 5289
is correctly issued. However, the UFM incorrectly calls out the independent
degrees of freedom on the entry as dependent and lists the independent degrees
of freedom twice. The dependent degrees in error are also listed but they may
be obscured by the incorrect data.
Avoidance: Inspect the RSPLINE and other MPC entries to determine which are in
error.
35882
70.7
SSSALTERs - modevala.vxx - Matrix STRAIN
ED is off by a Factor of 2
If PARAM,EVAL,-1 is used in the modevala.vxx alter, the matrix for the modal
strain energy (STRAINED) is off by a factor of 2. If the recommended value of
PARAM,EVAL,-2, is used this problem does not occur.
Avoidance: Modify the alter to divide the MATRIX by 2 as follows:
Replace:
DIAGONAL STRAINE/STRAINED/ $
with
DIAGONAL STRAINE/STRAIND2/ $
add straind2,/strained/(.5,0.) $
35886
cted Answers
70.7
Loads - LOAD(TEMP), LOAD - No UFM, Unexpe
As documented in the Quick Reference Guide, the TEMPERATURE load ID should be

unique with respect to all other loads in the model. However, this rule is not
enforced, and misleading results can occur under the following situation.
1) The TEMPERATURE load has same set ID as a mechanical (e.g. FORCE, PLOADi)
or body (e.g. GRAV) load.
2) The mechanical or body load is scaled by a non-unity value on a LOAD bulk
data entry.
Although the Quick Reference Guide LOAD card documentation implies that the
TEMPERATURE loads are ignored by the LOAD card, the temperature load delta-T
will be scaled by the load factor on the LOAD card if there is a
mechanical/body load with the same set ID as the TEMPERATURE set.
Avoidance: Ensure that the TEMPERATURE set is unique with respect to all other
l
35892
70.7
ACCESS - Sample Program Build Errors
The MSC/ACCESS sample programs are built with the command

msc705 access build
Failing to use the msc705 (msc706, msc71, et al) and access scripts will result
in the makefile failing. Alternatively, you could set MSC_BASE and MSC_ARCH to
the correct values and directly invoke
access build
However, under no circumstances can you use
make
or
make build
35893
G ERROR 3012
70.7
Plotting - OUTPUT(POST) - SFM 4276. BIOMS
If OUTPUT(POST) and SETS DEFINITION are incorrectly both included in the case
control the following error message is output:
19
OUTPUT(POST)
20
SETS DEFINITIONS
0
The message should say the same thing as Remark 1 of the SETS DEFINITION
description of the MSC/NASTRAN Quick Reference Guide:
"Either SETS DEFINITION or OUTPUT(POST) may be specified but not both."
35895
ETT
70.7
Buckling - EMG, TEMP(LOAD) - SFM 3003 EMG
If a buckling job, SOL 105, contains multiple static/buckling subcase pairs,

and if a temperature set (e.g. TEMP(LOAD)) is called out in the second or later
static subcase that does not exist, then the following error occurs:
SYSTEM FATAL MESSAGE 3003 (EMG) ATTEMPT TO READ PAST THE END OF A LOGICAL
RECORD IN DATA BLOCK ETT
(FILE 107) IN SUBROUTINE EMGTAB
Avoidance: Add the referenced temperature set entries to the bulk data file.
35896
2004
Z0 - Unexpected Answers
When optimizing ply thicknesses in Sol 200, the user must

recalculate Z0 if the midplane is to remain at the nodes.
users to leave field 3 of the PCOMP entry (Z0) blank, and
calculate Z0 as -t/2. But in optimization, this field is
automatically, which can lead to unexpected results.
remember to
It is common for
let MSC/NASTRAN
not updated
Avoidance: Either:Create another design variable for Z0 (field 3 of PCOMP) and

use DLINK to calculate updated Z0 or use an additional DVPREL1 to calculate z0
= 1/2 ( c0 + x1 + x2 + x3 + ... xn) where co is the thickness of invariant
plies and the xi's are designed ply thicknesses)
35901
70.7
Optimization/Design Sensitivity - Rigid E
lement Sensitivity - UFM 1126 in UMERGE
When a shape optimization job includes grid points which are associated with
rigid elements and are designed (referenced by DVGRID/DVSHAP/DVBSHAP) and the
job is run with the option of SCR=no, it may fail in subdmap respsen with the
following error message:
DMAP MODULE UMERGE IS ATTEMPTING TO OUTPUT DATABLOCK
USER ACTION: DELETE THE DATABLOCK, OR USE FILE DUG=OVRWRT
Avoidance:
1) Use SCR=YES
2) Use the following dmap alter if SCR=NO,
compile respsen
alter '\/ dug ','\/ dug '(,1)
umerge uset, uny, dum / dugz / 'G'/ 'N'/ 'M' $
equivx dugz / ugy / always $
201 NAME = DUG
alter '\/ dug '(2),'\/ dug '(2,1)

umerge uset, upnds1, dum / dugz / 'G'/ 'N'/
35914
Answers
70.7
Static Analysis - MPCForce output - Wrong
In linear static analysis (SOLs 101 and 200), if there exist MPC entries, but
no rigid element entries, and some subcases, but not all select those MPCs,
then MPCFORCE output may be labeled with the incorrect SUBCASE ID listed in the
upper right hand corner of the printed output and the forces will be wrong.
Avoidance: Add a rigid element or insert the following alter:
compile sedisp
alter 'IF ( NOQMG',''
IF ( NOQMG>-1 and not(delta) ) THEN $
if ( nomset<0 ) then $
PARAML USET//'USET'//////'g'/S,N,NOgSET $
matgen ,/qmx/7/nogset/nloads $
else $
alter 'call cforce'
endif $
endalter
35918
70.7
cient Processing
Acoustic Analysis - PARAM,WTMASS - Ineffi
When param, wtmass is used in conjunction with fluid elements it causes the
mass matrix to be of form 1 (unsymmetric). This causes an unsymmetric
solution, which requires more memory and cpu time than a symmetric solution.
Avoidance: The following alter avoids this problem:
compile semg list noref
alter 'MPYAD.*MJJX1','' $ add sym flag
matprn wtmassg// $
MPYAD
MJJX1,WTMASSG,/MJJX/////6 $ force symmetry
35921
(MKSPL)
70.7
Aeroelastic Analysis - SPLINE3 - UFM 2331
Aeroelastic Analysis with SPLINE3 entries may fail with the following message
in Version 70.5:
*** USER FATAL MESSAGE 2331 (MKSPL)
BOXES PICKED ON SPLINE3 ENTRY ID =
ENTRY ID =
yyy
USER INFORMATION: CAERO ENTRY ID =
zzz.
xxx HAVE NOT BEEN GENERATED BY CAERO

yyy GENERATES BOXES
yyy to
Avoidance: Use SPLINE2 entries if possible. If that is not possible, order

GRID components by internal order which can be determined by using
PARAM,USETPRT,1 .
35931
ong Answers
70.7
Restarts/P-Elements - PARAM,PVALINIT - Wr
If a restart is performed from a p-version run and PARAM,PVALINIT is not

specified, then the restart will default the starting p-value to the first
p-value rather than the last p-value computed in the cold start.
Avoidance:
Specify PARAM,PVALINIT or insert the following DMAP alter:
compile ifps1
alter 'type ',''
type parm,,i,n,seid,gnmax,pvalid,pvaltmp,np,adptindx,pval0,
oldseq1 $
type parm,nddl,i,n,pvallast $
endalter
35932
2004
without Friction, UFM 316 (IFPDRV)
Nonlinear Analysis - NLRGAP - Radial Gap
Using the NLRGAP does not allow input of the nonlinear forces without reference
to a TABLED1 which specifies O.O for friction. Leaving the field 8 blank
yields the following message:
ILLEGAL DATA ON BULK DATA ENTRY NLRGAP
ENTRY COUNT =
36
20
SORTED
for the input item:

NLRGAP 20
SID
90
GA
101
GB
XY
plane
21
tabk tabg tabu radius

22
0.0
Avoidance: The avoidance is to specify a table for the TABU field with values
of 0.0 for friction.
35935
Nonlinear Analysis - NLRGAP - UFM 2093 (DPD4)
An NLRGAP element that identifies a non-existent grid id produces a fatal

message that incorrectly identifies the grid. The following fatal message was
produced by an NLRGAP element that referenced a nonexistent GRID id of 90:
*** USER FATAL MESSAGE 2093
NOLIN OR NLRGAP SET
61 WHICH IS NOT IN UD SET.
NOLIN OR NLRGAP SET
62 WHICH IS NOT IN UD SET.
(DPD4)
20 REFERENCES GRID
100 COMPONENT
1 SIL
(DPD4)
20 REFERENCES GRID
100 COMPONENT
2 SIL
(DPD)
90 ON NOLIN- ENTRY.
Avoidance: Correct the NLRGAP entry.

35937
Performance - CPU Time not reported consistently
The CPU time reported in the f04 file is not consistently reported across all
platforms. Thus, comparisons of CPU time between machines that are reported
differently are meaningless. The method of reporting for most systems is
shown below:
Compaq:
Cray:
HP:
IBM:
NEC:
SGI:
user + system
user
user
user + system
user
user
Sun:
user
Windows: user + system

Avoidance: To compare CPU times across different platforms, use the time
summary at the end of the LOG file.
35939
70.7
ected Answers or Messages
Miscellaneous - INCLUDE - UFM 398, Unexp
In Version 70.6, if a referenced include file does not exist, the job will
issue the following fatal message
*** USER FATAL MESSAGE 398 (GETLIN)
A REQUESTED INCLUDE FILE WAS NOT FOUND
.
.
THE INCLUDE REQUEST IS SKIPPED
but the job will continue. This may lead to unexpected results as the
information in the INCLUDE file will not be included.
Avoidance: Make sure that the referenced INCLUDE file exists.
35993
70.7
- UFM 6482 (DOPR3R)
If the DESOBJ references a DRESP1 that refers to a dynamic response (e.g.,

FRDISP or TACCL) and there are constraints on nondynamic responses (e.g.,
WEIGHT or DISP) then the message:
USER FATAL MESSAGE 6482 (DOPR3R)
FOR SUBCASE
0, THE ANALYSIS TYPE IS GLOBAL
COMMAND REFERENCES AN INCOMPATIBLE
DRESP1 ENTRY WITH RID =
n AND RTYPE = FRACCL.
0FATAL ERROR
BUT THE DESOBJ
is produced in error and it incorrectly states that the response type is

incompatible with the analysis type.
Avoidance: Modify the input to have the DESOBJ refer to a DRESP2 and then
create a DRESP2 as shown in the example
Example,
CASE control has:
DESOBJ=40001
Bulk data has
DRESP1, 40000, ZIEL1, FRACCL ,
dresp2 40001 kludge 40
, ,
35996
SSSALTERs - trncomp1 - SFM 3002 (SDR2)
2001
2,
140.,
6294
If the sssalter trncomp1 is used with PARAM,DDRMM,-1 or in SOL 112 T then the
message:
SYSTEM FATAL ERROR 3002 (SDR2 )
EOF ENCOUNTERED WHILE READING DATA BLOCK SILS
(FILE 106) IN SUBROUTINE SDR2.
is issued whenever a STRAIN case control request occurs.

Avoidance: To avoid the error the follwing sdr2 dmap statements must be
changed.
SDR2
SDR2
CASEDR,CSTMS,MPTS,DIT,EQEXINS,SILS,ETT,OL2,bgpdts,
,,UG,EST,,,,,GPSNTS,,,/,,,,OEF1AX,/
APP1/S,N,NOS/FRCNCMP $
CASEDR,CSTMS,MPTS,DIT,EQEXINS,SILS,ETT,OL2,bgpdts,
,,UG,EST,,,,,GPSNTS,,,/,,,OES1AX,,/
APP1/S,N,NOS/STRNCMP $
to:
SDR
36000
on
Nonlinear Transient Analysis - NLTRD2 - Performance Degradati
In many problems nltrd2 runs slower in Version 70.5 than in previous versions.
The investigation continues; however, it has been found that increasing smem
from the default of 100 to 1000 significantly improved the performance of
nltrd2 to where it exceeded prior versions performance.
Avoidance for V69: Nastran command should include keyword "sysfield=mapio=no"
in all v69 runs to improve the performance.
36014
70.7
strained Unit Solution not available
Aeroelastic Postprocessing - FLD&S - Unre
The static aeroelastic solution sequence (SOL 144) will store the "unit
solutions" (displacements and aeroelastically corrected forces associated with
the unit perturbation of the aerodynamic extra point) on the XDB if PARAM,
POST,0 is specified in the Bulk Data. Due to a typographical error, the
variant of the unit solution forces associated with the unrestrained
formulation are not correctly passed to the DBC module for storage.
Consequently they are not available to be visualized in MSC/PATRAN V8.1+ (which
has been enhanced to recognize these data as part of MSC/FLD V1.0).
No other results are affected since the data are computed. They are simply not
stored for subsequent post processing.
Avoidance: The following DMAP alter against V70.6 will correct the problem
compile aeopu
36042
70.7
brary, DVPREL1 - Wrong Answers
Optimization/Design Sensitivity - BEAM Li
The design of the PBARL creates internal constraints on the bar dimensions to
insure, for example, that the inner radius of a tube does not exceed the outer
radius. The calculation of these constraints will be in error if the DVPREL1
that designs a beam dimension that is included in the constraint has a non-zero
value for C0.
Avoidance: There is no avoidance other than to recast the design task in a way
that eliminates the need for a C0 term.
36066
70.7
P-Elements - Incorrect Answers for p>=10
P-Elements with p>=10 may yield incorrect applied loads, boundary conditions,
and displacement coordinate systems.
36073
2001
mputed for METHOD(FLUID)
Acoustic Analysis - No Component Modes Co
If an uncoupled acoustic analysis is performed and some of the fluid grids

are placed into the a-set because frequency dependent elements are attached to
them, then in SOL 108 no component modes are computed when the eigenvalue
extraction method is selected using the METHOD(FLUID) Case Control command.
Instead the METHOD Case Control command has to be used. This is due to a logic
error in SEMRM which does not look for METHOD(FLUID).
Avoidance: A workaround is to use METHOD or to use the following DMAP-alter
(tested with V70.6):
compile semrm
alter 'PARAML CASES'
if(method=0) PARAML CASES//'DTI'/1/226//S,N,METHOD $
endalter
36075
2198 in FBS
2001
Eigenvalue Analysis - PARAM,RESVEC - SFM
If residual vectors are requested for an unconstrained superelement which

has no physical exterior points (no T-set), the run will fail with SFM 2198 in
FBS which means that the LOO matrix is missing.
Avoidance: Either have at least one exterior point for the superelement, or
insert the following alter:
compile sekr
alter 'IF ( NLKOT>-1 )','IF ( NLKOT>-1 )'
IF ( NLKOT>-1 OR RESVEC='YES') THEN $
endalter
36076
EAD ONLY file
2004
Miscellaneous - INPUTT2 - SFM 6551 with R
On NT computers, if the permission of a file used for INPUTT2 is "read-only",

the program may fail with SYSTEM FATAL MESSAGE 6551 indicating that the
end-of-file was detected incorrectly.
Avoidance: Change the file permission to be full access.
36078
70.7
M 9050 (SEKRRS)
Complex Eigenvalue Analysis - SCR=NO - UF
If while running a Complex Eigenvalue Analysis in MSC/NASTRAN Version 70.6 the

run encounters
^^^ USER FATAL MESSAGE 9050 (SEKRRS)
^^^ RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX KLL.
and SCR = NO, set SCR = YES this may correct the problem.
36096
2001
U - UWM 4648,3034
Eigenvalue Analysis - GIV, MGIV, HOU, MHO
When the tridiagonal eigensolution methods GIV, MGIV, HOU, or MHOU are
selected, and the roots are closely spaced, the messages below may result:
0***USER WARNING MESSAGE 4648---- THE MODAL MASS MATRIX IS NOT POSITIVE
DEFINITE.
0*** USER WARNING MESSAGE 3034, ORTHOGONALITY TEST FAILED. LARGEST TERM =
1.00E+00 ,NUMBER FAILED =
36
Avoidances:
An avoidance is to select the Lanczos method instead. It tests for
orthogonality as a requirement for stopping the solution process.
Another avoidance when using the tridiagonal methods is to stlightly perturb
the system so that the repeated roots are separated. It was found by
experiment with a 10 by 10 problem with 9 repeated roots in one cluster that
only the first four modes had good orthogonality. If 10 stiffness terms
36104
2001
- Infinite cpu Loop, read error
If a large DEQATN entry is used, then depending on the machine, the job may
terminate without any messages in the f06 or f04 files or the run may appear to
be caught in an infinite loop. Depending on the machine, any of the following
messages may appear in the log file. This situation can occur even if the
number of non-zero characters are below the 32,000 limits.
1.
fmt: read unexpected character

apparent state: unit -1 named
last format: (I2,4X,I4)
Unit -1 is a (null) formatted internal file
*** Execution Terminated (115) ***
2. 1525-097 A READ statement using decimal base input found the invalid digit
'' in the input file. The program will
recover by assuming a
zero in its place.
Avoidance: Reducing the size the DEQATN entry.
36112
Output
Transient Response Analsyis - DRMS1 DMRH1 - UWM 5186, Missing
DMAP modules DRMS1 and DRMH1 will issue the message:

*** USER WARNING MESSAGE 5186. (DRMH1C)
A CHANGE IN WORD 2 OF THE OFP-ID RECORDS OF DATA BLOCK 101 HAS BEEN
DETECTED.
PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED.
and no output will be produced when the input OUGV1 matrix contains more than 1
type of grid output request (e.g. displacements AND velocities).
Avoidance: The easiest avoidance is to only include one type of output request
in the case control (e.g. DISP or VELO or ACCE). A possible DMAP avoidance
would involve breaking the UG matrix into 3 separate matrices (disp, vel, acc)
before running through SDR2 to make 3 separate OUGV1s.
36133
70.7
Optimization/Design Sensitivity - Rigid E
lement Sensitivity - UFM 1126 in DSVGP5
If rigid element sensitivity is requested in SOL 200 for static and frequency
response analysis, then UFM 1126 is issued from module DSVGP5 in subDMAP
PSLGDV for data block ENX3.
compile pslgdv
alter 1
file enx3=ovrwrt/kmmb=ovrwrt/kmntb=ovrwrt/kmnb=ovrwrt/knnb=ovrwrt/
gtkmn=ovrwrt/ym=ovrwrt/egxx=ovrwrt/egx3=ovrwrt/mmmb=ovrwrt/
mmntb=ovrwrt/mmnb=ovrwrt/mnnb=ovrwrt/gtmmn=ovrwrt/gtmmny=ovrwrt/
gtmyg=ovrwrt/gtkmny=ovrwrt/gtbmny=ovrwrt/gtbyg=ovrwrt/gtkyg=ovrwrt/
gtkyg1=ovrwrt/gtk4yg=ovrwrt/gtk4mny=ovrwrt/egx4=ovrwrt $
endalter
36136
70.7
PBARL - Incorrect Sensitivities
Optimization/Design Sensitivity - PBEAML,
The sensitivities of the stress recovery locations with respect to the section
dimensions are in error for the CHAN and Z section types. This error will
result in incorrect stress response sensitivities.
Avoidance: There is no avoidance. The magnitude of the error has been under
10% in the examples that have been seen. Thus, the designs produced using the
incorrect sensitivities should be adequate.
36155
70.7
Poor Performance
Design Sensitivity - DSAMODES, SENSITY -
The eigenvector sensitivity capability of the dsamodes module requires the

identification of the row of the eigenvector which contains the largest value.
Currently this is done by a do loop in the subdamp which checks the magnitude
of each term in the vector in turn. This can be very time consuming if the
size of the eigenvector is large.
compile dsamodes
alter 'do while ( mode'(,-1)
PARAML USET//'USET'//////'f'/S,N,NOfSET $
matgen ,/row1/4/nofset/1 $ row matrix of 1 2 3 4 ....
trnsp
row1/rowt $ column matrix of 1 2 3 4 ....
alter 'ir\=0','ir\=0'(,5)
matmod phj,,,,,/phjn/2////1. $ filter out values less than one
add
phjn,rowt/phjx///1 $ element-by-element multiply
norm
phjx/junk///s,n,irr $ find row number
36160
rs
User's Modifiable - blank common block - Possible Wrong Answe
The blank common block name for the User's Modifiable has been changed for
Version 70.5. If the old name common /
/ is used, the results may be
unpredictable.
Avoidance: Replace the following common block
common /
/
with
common /BLNKCM/
36215
Output
2001
Documentation/QRG - PCOMP - Failure Index
In the MSC/NASTRAN V70.5 QUICK REFERENCE GUIDE, Remark 7 under the PCOMP bulk
data description needs to be changed:
from:
7. ELFORCE and ELSTRESS requests must be present for all elements for which ply
stress or failure index output is desired.
to:
7. In order to get failure index output the following must be present:
a) ELSTRESS or ELSTRAIN case control commands,
b) Sb, FT, and SOUTi on the PCOMP bulk data entry,
c) Xt, Xc, Yt, Yc, and S on all referenced MAT8 bulk data entries if str
ess
allowables are used,
or Xt, Xc, Yt, Yc, S, and STRN=1.0 if strain allowables are used.
36230
2001.0.1
2 - Unexpected Answers
Aeroelastic Analysis - SPLINEi, SET1, SET
If an input file contains both a SET1 and a SET2 Bulk Data entry with the same
identification number, one or the other willl randomly be used in the spline(s)
that reference that SETi identification number. There is no way to control
which entry will be used and no error message is issued that indicates that one
of the two inputs is being ignored.
Avoidance: There is no real avoidance. You must ensure that your SET1 and SET2
entries do not have common identification numbers.
36245
2001
FUSET References PA or PS Sets
Documentation - DEFUSET - UFM 316 When DE
If a DEFUSET entry references the PA or PS sets the following fatal message

will be encounterd:
ILLEGAL DATA ON BULK DATA ENTRY DEFUSET ********
ENTRY COUNT = xx
36247
2001
SORTED
Documentation - LOADSET - Wrong Answers
Multiple loadset entries may not be specified in a dynamics run. If there are
loadsets in each subcase the results for the subsequent subcases use the
initial loadset and are usually zero. However if the user defines the same
assumed DAREA id on each of his LSEQ entries wrong results will occur for the
subsequent subcase. The load is calculated from
using the initial loadset. A warning or fatal message should be issued if the
loadset is ignored. This problem has been fixed in the code in V2001.
36250
Static Analysis - SUBCOM, SUBSEQ, SDR2 - SFM 3002
If a static analysis has SUBCOMs and SUBSEQ, the job may issue SYSTEM FATAL
MESSAGE 3002 from the SDR2 module if the referenced subcases have different spc
sets.
36251
70.7
Properties for "T1" Section
Beam Library - PBEAML, PBARL - Incorrect
PBEAML and PBARL produce incorrect I2 and J properteis for the "T1" type
section.
Avoidance: If possible use the "T" type section.
36257
70.7
Nonlinear Analysis - UWM 4698 (DCMPD)
Nonlinear analysis may identify degrees of freedom large factor diagonal ratios
at every iteration with the UWM 4698 shown below. This may result in a large
amount of output. Version 70.7 has been enhanced so that this output may be
controlled by setting SYSTEM(60)=-999.
USER WARNING MESSAGE 4698 (DCMPD)
STATISTICS FOR DECOMPOSITION OF MATRIX KLLRH .
36286
70.7
In Version 69 and later systems, RFORCE will produce incorrect moment loads.
Moments are produced when CONM2 entries have an offset specified. Moments are
also produced for the mass associated with a PBEAM entry when an offset is
specified and for the PBEAM entry when a channel cross section is specified. .
Avoidance: The only avoidance is to specify an additional GRID at the offset
location and use a rigid element to attach it to the main GRID.
36287
70.7
, scr=no - SFM 3001 in DOM12
When running SOL 200 with mode tracking (MODTRAK) and scr=no, the job may
terminate with the following diagnostic message in the f06 file:
*** SYSTEM FATAL MESSAGE 3001 (DOM12)
THE EXECUTIVE FILE -112 DOES NOT EXIST.
PROGRAMMER INFORMATION: SUBROUTINE DOM11C
Avoidance: Run with scr=yes or insert the following DMAP alter:
compile fea
alter 'if ( modetrak'(2)
IF ( MODETRAK>0 ) THEN $
delete /mtrak,,,, $
modtrl mtraki//nomod/nomtk $
copy
mtraki/mtrak $
endIF $ MODETRAK>0
alter 'delete /mtrak'(,-1),'delete
endalter
36299
ing
70.7
/mtrak'(,3)
Miscellaneous - OFP - Inefficient Process
Efficiency has been improved in the OFP module for MSC/NASTRAN Version 70.7 for
jobs that request only plot output.
36350
70.7
FMS - INIT MASTER(NORAM) - SFM 1026
In Version 70.6, if the fms statement INIT MASTER(NORAM) is used on UNIX

machines, then the job may terminate
*** SYSTEM FATAL MESSAGE 1026 (XIO)
ATTEMPT TO ACCESS A FILE WHICH IS NOT OPENED
0********* DUMP OF XIO PARAMETERS
0XIO NAME = 423
ATTEMPTED OPERATION = FILPSX
FILEXX = 23
Avoidance: Remove INIT MASTER(NORAM).
36366
SSSALTERs - mtacca.vxxx - Wrong Answers
SSSALTER mtacca.vxxx assumes that the modes are mass-normalized. If your modes
are not mass-normalized, wrong answers will result.
Avoidance: Use the default (MASS) eigenvector normalization.
36389
r Performance
70.7
Miscellaneous - Case Control, MODES - Poo
If a very large value of x is requested with the modes=x case control command,
then the performance will be very inefficient. An example of this situation is
illutrated below:
Subcase 1
modes = 20
disp = all
Subcase 21
modes = 9000
disp = none
Avoidance: Request a reasonable modes value.
36391
5423
2001
Documentation - Superelements/CLOAD - UFM
In the MSC/NASTRAN V70.5 Quick Reference Guide, remark 1 of the CLOAD case
control command should read:
"1. This command may only appear in the residual structure subcases (see SUPER
command) and it must be specified in all of them."
36410
cases
Static Analysis - TEMP(INIT) - Wrong Answers for Multiple Sub
In Sol 101, if TEMP(INIT) is not defined above the subcase level, it is ignored
and incorrect results occur. Contrary to the Quick Reference Guide
documentation TEMP(INIT) is the recommended way for specifying the datum
(reference) temperature for static analysis with temperature loads. However,
TEMP(INIT) must be made above the subcase level.
36428
UWM 7602
70.7
Optimization/Design Sensitivity - DOPR1 -
The following message is correctly issued but is confusing because it states

the analyis value which in this case is not greater than the maximum value
allowed. The message should state the design value.
*** USER WARNING MESSAGE 7602 (DOPR1I)
ON PROPERTY ENTRY PBEAM
WITH PID=
7610 AND FID=
-9, THE
PROPERTY VALUE 9.93100E+06 IS
GREATER THAN THE MAXIMUM PMAX VALUE 1.00000E+07 SPECIFIED ON THE DVPREL2
761001 ENTRY.
36450
70.7
Conditions - SFM 6363
P-Elements - GMBC, Multiple Edge Boundary
If there are multiple edge GMBC's for different coordinate directions using
different methodon a p-element, the following error results:
*** SYSTEM FATAL MESSAGE 6363 (EVLEDG)
THE ENFORCED DISPLACEMENT VECTOR COLUMN DOES NOT EXIST
FOR EDGE ID =
-21 FOR COMPONENT =
3
PROGRAMMER ACTION: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE (IERROR=2).
Avoidance: A workaround is to use the same method for the multiple boundary
conditions.
36451
Answers
2005
Superelements - MATMOD option 16 - Wrong
When using a determinate interface with an external superelement, using MATMOD

option 16 may lose rigid-body modes due to numeric roundoff.
Avoidance: When creating external superelements, do not use a determinate
interface for the component models.
36463
70.7
, PBUSH, PSHELL - UFM 7190
When an optimization task includes DVPRELi entries refrencing PBUSH as well as

other property entries, it fails in module DOPR1 with the following error
message:
*** USER FATAL MESSAGE 7190 (DOPR1I)
PTYPE PBUSH
DEFINED ON A DVPREL1
2 ENTRY CAN NOT BE FOUND ON A
PROPERTY ENTRY.
USER ACTION: DELETE THE DVPREL1 ENTRY OR INCLUDE AN ADDITIONAL PROPERTY
ENTRY.
Avoidance: Remove DVPRELi entries which do not reference PBUSH entries.
36465
70.7
QHHL in tpl ha145i
Aeroelastic Analysis - Wrong Answers for
The tpl deck ha145i fails in Version 70.6 due to an interaction between the
incomplete Case Control used in this test case and the changes made to NASTRAN
to support multiple aerodynamic symmetries.
Under those changes, the AERO/AEROS symmetries (which are single valued for a
run) are "replaced" by symmetry in Case Control. However, for upward
compatibility, the AERO/AEROS symmetries are used in the absence of any Case
Control. A subtle requirement of this upward compatiblity logic is that the

Cases must be "aerodynamic" cases for the procedure to function. Unfortunately,
HA145I doesn't have a complete Case Control, so the fact that the run is
aeroelastic cannot be determined from Case. Consequently, the defaulting rules
(whereby the AERO/AEROS would have provided the symmetry) were no
36528
70.7
- Infinite CPU Loop
If a DEQATN contains a double precision constant (e.g. 10.0D0) in a design

optimization task, an infinite loop will be encountered and the job will enter
the PREDOM subdmap and never complete. Version 70.7 outputs USER FATAL MESSAGE
224 to correct this problem.
Avoidance: Remove the double precision constant from the DEQATN.
36530
70.7
(65): floating invlaid
TRANS - MAT5, MAT9, MAT10 - forrtl: error
The trans program may fail to convert a binary XDB file to a neutral file when
MAT5, MAT9, or MAT10 entries are present in the MSC/NASTRAN input file. This
error has only been duplicated on DEC ALPHAs running UNIX thus far. The error
message from trans is: forrtl: error (65): floating invlaid.
Avoidance: Set PARAM,GEOMU,0 which eliminates all of the undeformed geometry
or edit the PHASE0 subdmap DBC statement to eliminate the writing of the MPT
table.
36546
Nonlinear Buckling Analysis - QUAD4 - Spurious Modes
For a rare case of boundary conditions, spurious modes in nonlinear buckling

(Sol 106) may occur for coarse meshes of CQUAD4 elements. The rare case of
boundary conditions is described as follows. All rotational degrees of freedom
in a CQUAD4 are constrained. The transverse displacements are not constrained
or only partially constrained.
Avoidance: Refine the mesh.
36547
70.7
perelements - SFM 4276, EC 1044
Superelements - Limit of the number of su
Models that contain more than 100 superelements may fail with SYSTEM FATAL
MESSAGE 4276, ERROR CODE 1044 caused by an integer overflow in routine GETOFF.
36563
70.7
ving signal number 10: Bus error
Miscellaneous - SGI, OS level 6.5 - Recei
On the SGI when running OS level 6.5, if the scratch disk is full, then the job
may fail with the following unclear messages in the log file:
Job aborting..
Avoidance: Allocate more space with the scratch disk..
36569
70.7
rror Messages, Unexpected Answers
Miscellaneous - SUBCOM,SUBSEQ - Missing E
The number of coefficients for SUBSEQ are limited to 200, which is documented
in the QRG. However, if more than 200 coefficients are used--in the case of
combining more than 200 subcases--only the first 200 coefficients are used
without any warning or fatal messages.
Avoidance: If more than 200 coefficients are needed, create a separate subcase
36589
rmance
70.7
Performance - MCE1, MPC, RBE - Poor Perfo
When there are a large number of m-set dofs, the mce1 module may exhibit poor
performance. In cases seen to date, the decomp portion of mce1 finishes in a
reasonable time, but the next portion, which happens to be an fbs with many
right-hand sides, ran for hours without completion.
This condition can be detected by looking at the run time for the decomp
operation. If the fbs takes more than 10 times this value, the avoidance below
may be worth considering.
Use the mce1.v706 subdmap from MSC's web site for sssalters. It has been
verified that it works correctly for Version 70.5 as well. On the model in
question, it reduced mce1 times from over 15 hours to minutes.
36611
2001
, DVGRID, MODTRK - UFM 1126 in GP4
If mode tracking is requested with BNDGRID and DVGRID entries present, then the
run will fail with the message:
*** USER
DMAP
USET0 ,
USER

MODULE GP4
203 NAME =
ACTION: DELETE THE DATABLOCK, OR USE FILE USET0=OVRWRT

compile desopt
alter 'lcgen '(,-3),''
if ( ambs or gmbs ) then $
endalter
36617
ith Low Memory
70.7.2
Matrix - SOLVE - Possible Wrong Answers w
If insufficient memory is available for the SOLVE module with SPARSE, then the
results may be incorrect.
36628
70.7
sary Calculation of View Factors
Heat Transfer Analysis - RADSET - Unneces
According to the MSC/NASTRAN Quick Reference Guide, the RADSET entry "Specifies
which radiation cavities are to be included for radiation enclosure analysis."
However, in a multiple radiation enclosure model, if an enclosure is NOT
referenced on the RADSET entry, the view factors are still calculated.
36630
70.7
ases causes failure in dbc
DBC - Changing tstep or freq between subc
If tstep or freq is changed between subcases and param,post,0 is specified to

create a dbc database, then dbc will not complete and the following messages
will be issued to the f06 file:
*** DBCMSG ERROR MESSAGE 44 FROM SUBROUTINE DBCAOL
OUTPUT LIST DOES NOT MATCH EXISTING IN THE DATABASE, MERGE/RESTART
OPERATION IMPOSSIBLE.
THE DBC MODULE HAS BEEN TERMINATED BECAUSE OF THE ABOVE FATAL DBC
ERROR.
USER INFORMATION: SUBSEQUENT DBC CALLS WILL NOT BE EXECUTED, AND
THE DATABASE CONVERSION IS INCOMPLETE.
Avoidance: The only avoidance is to execute the subcases in different runs.
36632
70.7
point overflow
Grid Point Stress - PARAM,CURV - Floating
If PARAM,CURV,1 is specified then the run may fail in the CURV module with the
following traceback:
Trap encountered:
Traceback:
Offset 0x00001bd4 in
Offset 0x000000e4 in
FP overflow
procedure
procedure
procedure
procedure
procedure
pstr2s_
curv3_
curv_
xsem14_
mainal
Avoidance: The input that demonstrated the error contained a STRESS=set id.
The error was avoided when this request was changed to STRESS=ALL.
36636
70.7
UIM 4534, UWM 6137 (UDSNRD)
Heat Transfer - VIEW, RADSET - UWM 6427,
If an initial run is used to generate a radiation matrix punch file and a

subsequent run inputs the punch file and defines a RADSET entry that attempts
re-calculate the view factor for some but not all of the cavities, then the job
will fail with the following messages:
*** USER WARNING MESSAGE 6427 (VIEWD)
VIEW FACTORS WILL NOT BE COMPUTED FOR RADIATION CAVITY ID=
85 BECAUSE
A RADIATION MATRIX IS ALREADY DEFINED.
USER INFORMATION: THE RADIATION MATRIX IS DEFINED ON RADLST OR RADMTX
BULK DATA ENTRIES.
*** USER INFORMATION MESSAGE 4534 (RMG2)
2 ELEMENTS HAVE A TOTAL VIEW FACTOR (FA/A) LESS THAN 0.99, ENERGY MAY
BE LOST TO SPACE.
*** USER WARNING MESSAGE 6137 (UDSNRD)
10 IERROR
USER ACTION: CHECK
36645
70.7
Rigid Elements - RBE3, GP4 - UFM 6490
When an extremely large number of RBE3 elements is used, the job may fail
indicating an RBE3 input error:
*** USER FATAL MESSAGE 6490 (WRGMTD)
FATAL ERRORS HAVE OCCURRED WHILE PROCESSING MPC AND RIGID ELEMENT ENTRIES.
PROGRAMMER INFORMATION: SIL NUMBER ******** DOES NOT EXIST IN THE
DEPENDENT SIL TABLE.
Other symptoms are that run times may increase greatly if the number of RBE3
elements increases. This effect begins to be noticeable at about 10,000 RBE3
elements, and becomes the dominant source of cost in runs where there are
hundreds of thousands of RBE3 elements.
The RBE3 code was revised in V70.7 to provide increased efficiency. The
original code was made with the assumption that no model would have over 100
RBE3 elements. More modern general software tools for
36646
79
2004
Random Analysis - CBUSH - SWM 3002, UWM 9
PSDF force plots fail for BUSH elements, but RESPONSE plots work. That is:
XYPLOT ELFORCE RESPONSE.... (works)
XYPLOT ELFORCE PSDF...(fails with the message below)
*** SYSTEM WARNING MESSAGE 3002 (RANDOM)
EOF ENCOUNTERED WHILE READING DATA BLOCK OES2
SUBROUTINE RAND2
(FILE 107) IN

36665
Loop PFAERO
70.7
Aeroelastic Analysis - PFAERO - Infinite
If the user attempts to run an aeroelastic solution sequence (SOL 144, 145 or
146 or SOL 200 with aeroelastic analyses) without any aerodynamic data, an
infinite loop will occur in the PFAERO subdmap. This is caused by a failure to
trap the absence of the requisite aerodynamic data. Subsequently, the PFAERO
subdmap (responding to data reuse logic) will endlessly attempt to create the
aerodynamic model.
Avoidance: You must have at least one aeroelasticity-related bulk data entry to
avoid the infinite loop and trigger the "missing data" error traps.
36678
340
2004
Eigenvalue Analysis - EIGR, EIGRL - SFM 7
The Lanczos method of eigenvalue extraction may give nonstandard error

messages. For example a run may terminate with the following messages.
Avoidance: The LNNDRVD or LNNDRVS messages meanings are given below:
ier error condition.
-723
-724
-725
-726
-727
insufficient workspace revealed during lanczos iteration

failure of tridiagonal ql iteration to converge
number of eigenvalues computed exceeds internal storage limitations
i/o error with lanczos vector file
failure of bidiagonal ql iteration to con
36682
70.7
ield Wrong Answers
Miscellaneous - Requesting Huge mem may y
Reguesting more than 1200mb of memory on an RS6000 system may result in wrong
answers or a fatal message.
36685
7 in UPARTN
70.7
Inertia Relief - INREL, SUPORT1 - SFM 300
If there are multiple subcases with SUPORT1 command in some, but not all,
subcases and PARAM,INREL,-1 is specified in the Bulk Data then the run will
terminate with:
compile statrs
alter 'if ( norset',''
if ( norset<6 and norset>0 ) then $
endalter
36701
wers
2001
Dynamic Analysis - DAREA - Unexpected Ans
If on the DAREA entry the coordinate system is specified as "0" for a grid
point it will be interpreted as "1". For example:
$
DAREA
pi
410
ci
1
is interpeted by the program as

DAREA
410
This may cause unexpected answers.

Avoidance: Specify the desired degree of freedom.
36706
Old Design Senitivity - CBEAM - Possible Wrong Answers
If BEAM elements are used in a modal analysis with the old design sensitivity
analysis, then the design sensitivity coefficients may be incorrect.
Avoidance: 1. Replace the beam elements with bar elements.
2. Use SOL 200 (v707.7) to perform the same task if the user
insists using beam elements.
36709
2005.1
Optimization/Design Sensitivity - DSVG1D
- UFM 5172 When Material has no Density
If a designed property (DESVAR/DVPREL1) references a material with zero
density, then the job will fail with the following messages:
*** USER FATAL MESSAGE 5172 (DSVG1D)
THE VARIATIONAL ELEMENT ID IN MDICTDSF INCONSISTENT WITH THE VARIATIONAL
ELEMENT ID IN DSPT1, MODULE DSVG1 IS TERMINATED.
*** SYSTEM FATAL MESSAGE 3001 (DSVG1)
THE INPUT DATA BLOCK NAMED MDICTDSF AT POSITION
1 DOES NOT EXIST.
Avoidance: Specify a non-zero density on the material entry.
36727
70.7
Dynamic Analysis w/Differential Stiffness
- SUPORTi, STATSUB, scr=yes - UFM 4407
If differential stiffness is requested in dynamic analyis, supported
degrees-of-freedom are specified (see the SUPORT or SUPORT1 entries), and the
job is run with scr=yes, then the mass matrix will not be reduced to the
supported degrees-of-freedom and UFM 4407 will be issued.
Avoidance: Run with scr=no or insert the following DMAP alter:
compile phase1dr
alter 'or kdiff',''
if ( true ) then $
endalter
36730
4
70.7
Superelements - SEBULK, SECONCT - UFM 679
When using part superelement, only a single boundary point is allowed at a

particular boundary location (within a specified tolerance), this is design
intent. However, it has been observed in a model that the job terminates with
*** USER FATAL MESSAGE 6794 (SEPSEB)
DUPLICATE BOUNDARY POINTS DETECTED IN UPSTREAM SUPERELEMENT
SEARCHING
0 AT GRID
7001.
LIST FOLLOWS:
13403
49682
1 WHILE
even though the points identified do not appear to be at the same location
within the tolerance. The exact cause of this error is not known at this
point.
Avoidance: Use the SEEXCLD command to remove all but a single boundary point
at each PART.
36737
70.7
OFTEXIT YES, SDR1 - UFM 4574
Optimization/Design Sensitivity - PARAM S
If PARAM,SOFTEXIT,YES is specified with static or frequency response analysis

in SOL 200, then the run will fail with UFM 4574 and SFM 3001 in module SDR1
and subDMAP SEDISP on the final data recovery.
compile desopt
alter 'dbdelete',''
endalter
36741
4276 EC 777
70.7
Response Spectrum Analysis - RSPEC - SFE
If a response spectrum analysis is performed in Version 70.5 on HP computers,

then the job may fail with the following message and traceback in the RSPEC
module:
Process traceback
0) 0x00093e90
1) 0x01126d78
2) 0x004935e8
3) 0x00199024
4) 0x00098d44
5) 0x0008fbc8
(
(
(
(
(
(
real
...
sysrcv + 0x2a0 [/nast2/msc705t2/hpux/analysis]
_sigreturn [/nast2/msc705t2/hpux/analysis]
rspcod_ + 0x740 [/nast2/msc705t2/hpux/analysis]
rspec_ + 0xbc [/nast2/msc705t2/hpux/analysis]
xsem14_ + 0x2fc [/nast2/msc705t2/hpux/analysis]
mainal_ + 0x9b0 [/nast2/msc705t2/hpux/analysis]
19.5
Avoidance: The only avoidances are to run Version 70 or generate the curves on
another computer.
36752
nown keyword
70.7
Miscellaneous - MSCACT - UFM (mscact) Unk
The MSCACT utility incorrectly flags the keyword assignment "summary=jid" as an

error and outputs the message shown below. However, "summary=job" is accepted
and generates the requested functionality.
USER FATAL MESSAGE (mscact)
unknown keyword "summary=jid".
Avoidance:
1) Use "summary=job" instead of "summary=jid".
2) Alternatively, the error can be corrected by changing line 1180 of
<ins-dir>/msc705/util/mscact.c from
else if( !strncmp( "job", q, lq ) )
to
else if( !strncmp( "jid", q, lq ) )
Once the change is made, rebuild MSCACT as described in the "Configuration and
Operations Guide".
36764
70.7
Acoustic Analysis - FORCE(PHASE), Velocit
ies and Pressure levels - Wrong Answers
The acoustic output titled "COMPLEX ACCELERATIONS VELOCITIES AND PRESSURE
LEVELS" prints an incorrect format for the element ID when the MAGNITUDE/PHASE
option is requested. The incorrect format is that the "PRESSURE(DB)" column
is truncated and the phase values are misaligned. Here is an example of the
incorrect MAGNITUDE/PHASE output:
( P E A K )
C O M P L E X A C C E L E R A T I O N S V E L O C I T I E S
A N D P R E S S U R E L E V E L S
(MAGNITUDE/PHASE)
ELE-ID EL-TYPE
X-ACCELERATION Y-ACCELERATION Z-ACCELERATION
X-VELOCITY
Y-VELOCITY
Z-VELOCITY PRESSURE (DB)
1.4994E-43
HEXPR
1.364242E-11 -2.376055E-10
36776
70.7
LINK, DOM9 - UFM 6499 (DOM9D)
Optimization/Design Sensitivity - PBAL, D
An optimization job which designs PBARL dimensions with DLINK entries fails in
DOM9 with the following message:
THE GRADIENT OF CONSTRAINT NUMBER
NNNNN IS ZERO
CONSTRAINT IS REMOVED FROM THE ACTIVE SET
** THIS IS A VIOLATED CONSTRAINT
** A FATAL ERROR WILL BE GENERATED
**** ONE OR MORE VIOLATED CONSTRAINTS HAS A ZERO GRADIENT ****
NO PROGRESS IS POSSIBLE
OPTIMIZATION TERMINATED
*** USER FATAL MESSAGE 6499 (DOM9D)
THE DOT OPTIMIZATION ALGORITHM HAS ENCOUNTERED AN ERROR THAT MAKES FURTHER
PROGRESS IMPOSSIBLE.
SEE MESSAGES ABOVE.
36777
70.7.2
Optimization/Design Sensitivity - ANALYIS
IS=MODES and MFREQ - SFM 3001 in DSAH
If a model has fluid-structure interaction in SOL 200 and both ANALYSIS=MODES
and ANALYSIS=MFREQ are requested, the run may fail with SFM 3001, stating that
data block PHG does not exist.
Avoidance: The following alter will avoid the FATAL error, but has not been
confirmed to give correct answers.
compile fea
alter 'IF.*DOSUPER3 AND NOT.*FSCOUP',''
IF ( DOSUPER3 ) THEN $
36780
rsion
70.7
Submittal - vers= - Does not get right ve
If a different version than the latest installed (or latest known by the
invoked nastran command if under the form nastxxx where
xxx is a version number) is requested, the rc files of the requested version
are picked up, but not the executable and SSS.
36790
Radiation Heat Tranfer Analysis - VIEW, UDSFA - UFM 6136, est
imate=mem, unsymmetric decomp
MEM=estimate did not yield the correct estimate for a large heat trasnfer
radiation problem. The job subsequenty Failed with the message:
*** USER FATAL MESSAGE 6136 (UDSFA)
INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION.
USER ACTION: INCREASE CORE BY
5217107 WORDS
0FATAL ERROR
Avoidance: Use the following dmap alter to run the symmetric decomp instead of
the unsymmetric decomp
sol 153
diag 8
compile nlstatic list noref
alter 'IF ( DCMPKLLT ) DCMP' (1,-1)$

modtrl kllrh////6/$
cend
Heat transfer problem is all symmetirc problem and thus using symmetric decomp
is a lot faster.The only exception is when there is fluid elements in the
problem such as CONVM or when when the user imported the radiationmatrix from
other software that has input an unsymmetric radiation exchange matrix (RADLST
and RADMTX with MTXTYP =3
These are the unsymmetric physics applications anyway.
As for the N4W avoidance:(there is no dmap available)
Therefore the user can use:
NASTRAN system(209)=0 in the executive section to force the unsymmetric solver
to run UDCOMP which will require less memory or
Increase mem=20MW in the NASTRAN submittal command
36792
issing output
70.7
Aerodynamic Analysis - PARAM,OPGTKG,1 - M
PARAM,OPGTKG,1 requests a printout of the aerodynamic splining matrices. The

capability was inadvertently deleted from Version 70.6.
compile phase1a
alter 'np\=seid',''
equivx uset0/aeusets/-1 $
equivx bgpdts/aebgpdts/-1 $
dbdict datablk=(aebgpdts,aeusets) select=(name,size,
modltype,aeconfig,symxy,symxz) qualcurr $
dbview bgpdtf=aebgpdts where (modltype='aerostrc' or
modltype='structur' ) $
dbview usetff=aeusets where (modltype='aerostrc' or
modltype='structur' ) $
IF ( OPGTKG>=0 ) then $
MATGPR bgpdtf,usetff,,GPJK//'K'/'G' $
MATGPR bgpdtf,usetff,,GDJK//'K'/'G' $
endIF $ OPGTKG>=0
endalter
36815
2001
Composites - TEMPP3 - Wrong Answers
The TEMPP3 thermal loading bulk data entry is obsolete and is no longer
supported. The TEMPP3 entry may give wrong answers for composites with inplane
or normal thermal gradients.
Avoidance: Use the TEMPP1 bulk data entry instead which works correctly in all
cases and includes the same features as the TEMPP3.
36821
nsitivities
Optimization/Design Sensitivity - RHO - Incorrect Material Se
The design sensitivities with respect to the material densities of transient

response analysis that has a steady state response may be incorrect.
Avoidance: Do not specify the material density as a response for a steady
state analysis since the response is not affected by the density.
36823
2001
Nonlinear Transient Analysis - OTIME, SDR
1 - BIOMSG: ERROR
211 in BLDPK
In nonlinear transient analyis, if the value of an output time on an OTIME=

request exceeds the time value of the final time step, the job will fail in
the SDR1 module with the message:
BIOMSG: ERROR
0
STATUS =
211 HAS OCCURRED IN ROUTINE BLDPK
the same job runs with fewer time step intervals for output (NO) on the TSTEPNL
card or with fewer OTIME requests in the case control.
Avoidance: Do not use the OTIME entry in nonlinear transient analysis. The
Quick Reference Guide does not indicate that OTIME is supported for nonlinear
transient solutions.
36836
FMS - INIT - UFM 1257
If a large value is assigned to a DBSET member, e.g.,

init scratch logical(scratch(50gb))
then the job may fail with the following unclear messages:
*** USER FATAL MESSAGE 1257 (DBMAP)
THE MAX-SIZE SPECIFIED ON THE INIT FMS STATEMENT OR SMEM VALUE IN THE RC
FILE OR SMEM
KEYWORD IN THE COMMAND PROCEDURE FOR THE MEMFILE OF DBSET SCRATCH IS
100 BLOCKS
AND IS LESS THAN THE RECOMMENDED MINIMUM OF
110 BLOCKS.
USER ACTION: SPECIFY A MAX-SIZE OR SMEM VALUE AT OR ABOVE THE RECOMMENDED
VALUE.
Avoidance: Either increase the buffsize or decrease the dbset value
36842
2004
Superelements - PARAM,SESEF - UFM 5423
If the fraction of total strain energy (PARAM,SESEF) is requested and external

superelements exist, the job will fails with USER FATAL MESSAGE 5423
Avoidance: Include the following alter:
compile postreig, list
alter 'MPYAD.*KAA,PHILS',''
type parm,,i,n,temp
dbview kaanew=kaa, where(seid=temp and wildcard)
temp=seid $
paraml kaanew//'trailer'/1/s,n,noaset $
MPYAD
KAAnew,PHILS,/FA $
36870
2001
INTOUT - SFM 5423 (DMPYAD)
Nonlinear Static Analyis - MPCFORCE, SE,
If mpcforce output is requested in a nonlinear analysis, and the model

contains superelements and intermediate output is requested, then the job will
fail with the following messages:
*** USER INFORMATION MESSAGE 7321 (SEDRDR)
DATA RECOVERY FOR SUPERELEMENT

COLS ROWS FORM
TYPE NZWD DENS
TRAILER FOR KMG
IS 101108522 1310
2
2
12
3
TRAILER FOR UGJ
IS 102
1108522
2
2179608 8275
TRAILER FOR PM
IS 103
5 1310
2
2
0
0
TRANSPO
36930
2001
Always Work Correctly
Miscellaneous - ECHOON, ECHOOFF - Doesn't
ECHOON and ECHOOFF entries may be used in the Executive, Case Control, or Bulk
Data but there are limitations. ECHOOFF must not be the first entry in the
Executive Control section else it will be ignored. ECHOOFF does not handle
continuation entries (for example SET commands) in the Case Control correctly.
If after and ECHOOF command has been placed in the Bulk Data, PARAM entries
are the only entries that follow the ECHOON command, they will not printed in
the unsorted output.
36943
70.7
tput for Gust Analysis
Aeroelastic Analyisis - GUST - Missing Ou
In SOL 146, the gust loads are computed inside the GUST module and then
transformed to generalized coordinates. Only the generalized loads are output.
This makes it impossible for clients to manipulate these loads in any
meaningful way.
36949
70.7
DMAP - GPFDR - Extra Output
The GPFDR module with the third parameter xflag=1 (the cross strain energy
output) gives extra output for the first subcase. There should be no results
output for the first subcase.
36978
70.6
Downwash Matrices not Kept
Optimization/Aeroelasticity - DMI, W2GJ -
In SOL 200 with static aeroelasticity, user input downwash matrices (W2GJ) are
not kept after the first cycle.
Avoidance: Apply the following dmap alter in V70 and V70.5:
COMPILE PFAERO
ALTER 'dmiin'
CALL DBSTORE W2GJ,,,,//0/1/'DBALL'/0 $
$
COMPILE FEA
ALTER 'fea' $
TYPE PARM,,I,Y,IFOUND $
ALTER 'pfaero'
IF ( DESCYCLE >1 ) CALL DBFETCH /W2GJ,,,,/0/1/0/0/S,IFOUND $
$
36997
70.7
re Termination - UIM 6464
Optimization/Design Sensitivity - Prematu
An optimization job starting from a feasible region may terminate for a hard
convergence after the first design cycle without showing any improvement in
either objective or constraint and showing any changes in the design variables.
Here is the termination message:
*** USER INFORMATION MESSAGE 6464 (DOM12E)
RUN TERMINATED DUE TO HARD CONVERGENCE TO AN OPTIMUM AT CYCLE NUMBER =
1.
Avoidance: None.
36998
cts Ignored
70.7
SSSALTER - nlgyroa.v706 - Gyroscopic Effe
The version 70.6 nlgyroa.v706 sssalter does not include the gyroscopic effect.
Avoidance: Replace nlgyroa.v706 with the following alter. A copy of the
revised alter is also available on the MSC web site.
$
$
$
$
$
$
$
THIS ALTER IS CONFIDENTIAL AND A TRADE SECRET OF THE

MACNEAL-SCHWENDLER CORP. THE RECEIPT OR POSSESSION OF
THIS ALTER DOES NOT CONVEY ANY RIGHTS TO REPRODUCE OR
DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL
ANYTHING HEREIN, IN WHOLE OR IN PART, WITHOUT THE
SPECIFIC WRITTEN CONSENT OF THE MACNEAL-SCHWENDLER CORPORATION.
$
echooff $
$
$
nlgyroa.v706 - updated 8-13-99
$
$ updated July 7, 1998 - tlr
$
$ added PARAM,RFORCE,i - set i to the RFORCE to be used by this alter
$
37010
2004
- SFM 4276, EC 31
When an optimization deck includes a DRESP2 entry which references the same
DRESP1 ID more than once, the following system fatal message is issued from
module DOM9:
BIOMSG: ERROR
0
STATUS =
31 HAS OCCURRED IN ROUTINE GETSTR , FILE INDEX (FILEX) =

0
followed by:
ERROR CODE
31 PID=
Avoidance: Do not duplicate the same DRESP1 ID on a DRESP2 entry.

37027
2001
Aeroelastic Analysis - RESTART - SFM 3001
for QHHA or Inefficient Restart

A read-only restart in aeroelastic solution 145 will unnecessarily
recompute and decompose the AJJT for a list of existing Mach numbers and
reduced frequency even though the list is a subset of the original list.
Another symptom is SFM 3001 for QHHA.
Avoidance: If the original MKAERO1 entry is re-entered as it was input on
the initial run, then the AMG and DECOMP modules in the PFAERO subDMAP will not
be re-run.
37031
70.7
AECONFIG, IFP - UFM 603
Aeroelastic Analysis - AESYMXZ, AESYMXY,
Case control commands are free field input and should allow users to add
comments at the end of the lines so long as a dollar sign precedes the comment.
The new Version 70.6 aeroelastic analysis case control commands do not allow
comments to be specified on the same line as the command. The simple input file
below fails in IFP due to the comments onthe AE* case control commands.
sol 144
cend
aesymxz=symmetric $ this is a comment on the aesymxy line
aesymxy=asymmetric $ this is a comment on the aesymxy line
aeconfig=csr $ this is a comment on the aeconfig line
spc = 1 $ this is a comment on the SPC line
begin bulk
param,checkout,yes
enddata
37032
2001
ible Wrong Answers
Eigenvalue Analysis - PARAM,RESVEC - Poss
When residual vector is requested, it has been observed on some models that
the additional augmented eigenvalue is lower than the highest calculated mode.
This has been observed on a very small problem and also on problems using
virtual mass.
compile resvec
alter 'matmod oxf',''
type parm,,rs,y,resvoxf=.001 $
matmod oxf,,,,,/ox5,/2////resvoxf $ filter again
alter 'append=',''
append=(noox5<0 or ox5r<10000) $ set flag for below
endalter
or inspect the augmented eigenvalue table, if the additional mode is lower than
the highest calculated frequency, use o
37038
2004.0.5
mance in Unsymmetric Decomp
Nonlinear Analysis - NLTRD2 - Poor Perfor
The nltrd2 module may exhibit poor performance while performing an unsymmetric
decomposition.
Avoidance: The following dmap alter will allow a factor of four performance
improvement.
compile nltran
alter ' kjjnl, '
trnsp kjjnl/kjjnlt $
add5
kjjnl,kjjnlt,,,/xxx//-1. $
norm
xxx/////1/s,n,xnorm $
if ( xnorm<=1.d-6 ) modtrl kjjnl////6 $
endalter
37042
70.7
Matrix Methods - MPYAD - SFM 4276 (GINO)
If working memory is small relative to problem size, data is stored past the
end of working memory, destroying executive tables. The result will ultimately
be a confusing error message, such as:
*** SYSTEM FATAL MESSAGE 4276 (GINO)
ERROR CODE
100 PID= 0
*** USER INFORMATION MESSAGE 4276 (GINO)
TO OBTAIN A NASTRAN DUMP RESUBMIT JOB WITH DIAG 44 INSERTED IN THE
EXECUTIVE CONTROL SECTION.
1
* * * END OF JOB * * *
*** SYSTEM FATAL MESSAGE 1123 (GDBSNO)

DATABASE NUMBER: -10855138 IS OUT OF RANGE. DBSPTR = -1085513983
USER ACTION : MAKE SURE ALL ATTACHED DATABASE(S), INCLUDING THE DELIVERY
DATABASE, ARE VERSION (e.g. 69) COMPATIBLE.
0FATAL ERROR
37043
ncy
70.7
Rigid Elements - RBE3, GP4 - Poor Efficie
When there are more than 50,000 rbe3 elements run times in the GP4 module,
where they are processed, may be very long.
Avoidance: Avoidances are to reduce the number of rbe3 elements, or put them
in several superelements. Each superelement will call GP4 for only the
elements within it.
37051
76, EC 100
70.7
Aeroelastic Analysis - TRIM, ASG - SFM 42
The message "SYSTEM FATAL ERROR 4276 ERROR CODE 100" is issued from the ASG
module in an aeroelastic trim analysis when there are no SUPORTed degrees of
freedom but there are aerodynamic extra points (AESTAT and/or AESURF entries)
that are not constrained on the TRIM entry.
Avoidance: Constrain or remove the aerodynamic extra points or add to the
SUPORT degrees of freedom.
37055
70.7
xcessive resource usage
Eigenvalue Analysis - Component Modes - E
If component modes are requested and the number of q-set points is not exactly
equal to the number of component modes then the reduced stiffness and mass
matrices and the resulting residual structure matrices will contain many small
off-diagonal terms which should be exactly zero. This condition contributes to
inefficiencies in subsequent matrix operations.

compile semr3
alter 'dotrip\=',''
alter 'dotrip\='(2),''
alter 'nullkqq'
nullkqq=0 $
alter 'cmmat'
if ( noqset1>noqset ) then $
partn
cmmat,,vq1qx/xxx,,,/1 $
equivx xxx/cmmat/-1 $
else if ( noqset1<noqset ) then $
merge
cmmat,,,,,vq1qx/xxx/1 $
equivx xxx/cmmat/-1 $
endif $
endalter
37059
s
70.7
Miscellaneous - NEC SX-5, HPIO - Job Hang
It has been reported that when HPIO is turned on the NEC SX-5 and the disk
space is full, then nastran will not terminate properly and the job will hang.
Avoidance: Kill the job manually.
37078
2001
, SFM 4276, missing PSD output
If PSD
random
random
one of
Random Response - CBAR, PLOAD1 - SWM 3002
element force or stress output for a BAR element is requested in a

analysis, and the loading involves PLOAD1 entries, then the requested
output will be missing. Depending on the machine, the job will issue
SWM 3002 "EOF ENCOUNTERED WHILE READING DATA BLOCK OES2 (FILE 107) IN
SUBROUTINE RAND2"
SFM 4276 in the SDRX module.
!. Replace the BAR elements with BEAM elements.
2. If the BAR element must be used, replace PLOAD1 with equivalent point loads.
37080
Wrong Answers
2001
Optimization/Desgin Sensitivity - PBAR -
When an optimization job includes CBAR elements which are loaded by PLOAD1
entries, the end-B maximum stress, end-B minimum stress and end-B Safety margin
in compression for the static case are incorrectly selected from the stress
data file.
Avoidance: Use item code + 1 for selecting end-B maximum stress and end-B
minimum stress. However, there is no avoidance for getting the correct end-B
safety margin.
37088
70.7.2
migop2 - Wrong answers
External Superelements - param,extdrout,d
When using the enhanced external superelement capability, if the boundary

points have a different order in the assembly model than in the component
model, then the boundary solution written out for PARAM,EXTDROUT,DMIGOP2 will
be in the incorrect order, resulting in incorrect results for data recovery on
the component.
compile super3
alter 'call.*extdrout','call.*extdrout'(3,)
CALL EXTDROUT ULS,OL1M,EQEXINS,MAPS,uset/
DUM/APP1/'
'/TRUE $
CALL EXTDROUT UH2,OL1R,EQEXINS,MAPS,uset/
DUM/APP/SOLTYP/TRUE $
ELSE $
37089
GL
Aeroelastic Analysis/Superelements - SPLI
NEi - AECOMP Datablock Does not Exist
If external superelements are used in an aeroelastic solution and all splines
are contained within the external superelements, the run will fail claiming
that datablock AECOMP does not exist.
37102
swers
2001
Superelements - Buckling, SPCD - Wrong An
If buckling (SOL 105) is run with superelements and there are enforced
displacement on the upstream superelements, then the static answers will be
incorrect and hence the eigenvalues will be wrong.
compile phase0
alter 'ISOLAPP\=NSOLAPP',''
noop() $
alter 'ISOLAPP\=ISOLAPP'(,-1)
IF ( SEID>0 ) ISOLAPP=NSOLAPP $
endalter
or place all enforced displacements on the boundary into the residual
superelement.
37106
70.7
nswers for TEMPP1 Loads
P-Elements - TEMPP1 - QUADp Gives Wrong A
The QUAD p-element gives wrong results if it is loaded with temperature

gradients (TEMPP1 entry).
37126
ault
2001
Documentation - XYPLOT - LONG Command Def
The MSC/NASTRAN V70.5 Quick Reference Guide case control description in the
XYPLOT section for the LONG command says that the default is YES. This is not
correct. The default is NO.
37128
70.7.2
MIGOP2 - SFM 3007 (UPARTN)
External Superelements - PARAM,EXTDROUT,D
If the original component model for an external superelement has one or more
superelements defined, and the residual structure is equal in size to the ASET
chosen for the reduced matrices, then the data recovery run on the component
will fail with the following messages if the PARAM,EXTDROUT,DMIGOP2 option is
used.
ILLEGAL INPUT TO SUBROUTINE CALCV
Avoidance: Insert the following alters.
compile extdrin
alter 'upartn.*uset.*ul',''
paraml uset//'uset'//////'g'/s,n,lgset/'a'/s,n,noaset $
if(lgset<>noaset)then $
UPARTN USET,EXTDB/UL,,,/'G'/'A'/'O'/1 $
else $
equivx extdb/ul/-1 $
endif $
37130
2001
S=FLUTTER, SE - SFM 3001
In SOL 200, if ANALYSIS=FLUTTER and superelements exist, the analysis results

will be wrong if the aerodynamic model is splined to an upstream superelement.
Further,the job may fail with SFM 3001 in DVSG1 indicating that datablock DUG
does not exist. See also CSR 38501
Avoidance: Run the model without using superelements, or use this alter for
V70.7.
compile respsen
alter 'dsflte','dsflte'
DSFLTE KHHx,BHHx,MHHx,QHHL,FLUTAB,r1tabr,casem/
CPHFL,CPHFR,VTQU $
alter 'dug0','vtqu0'(2)
IF ( NODUD>0 ) CALL xSEDRDR,
DUD,EMAP,CASEXX,SLT,ETT,MAPS,bgpdts,USET,
GOAT,GOAQ,GM,CASEs,casem/
DUG/
RSONLY/'DYNAMICS'/false $
IF ( NODVD>0 ) CALL xSEDRDR,
DVD,EMAP,CASEXX,SLT,ETT,MAPS,bgpdts,U
37132
t and c-set
70.7
SSSALTERs - sedampa doesn't supposrt r-se
If R- or C-set dof exist in a superelement and the sssalter sedampa is used,

the associated superelement will not have modal damping applied. The alter is
intended to terminate the run with a message stating that C- and R-set dof are
not supported by the alter.
Avoidance: Do not use R- or C-set dof with the alter. The alter has been
replaced by a standard feature, which does allow R- or C-set dof to exist in
Version 70.7.
To correct the alter, replace
paraml uset//'uset'////s,n,nousetxx//'R'/s,n,norset/
'C'/s,n,nocset $
with
paraml uset0//'uset'////s,n,nousetxx//'R'/s,n,norset/
'C'/s,n,nocset $
37146
70.7
M 5423, Incompatible Matrices
Aeroelastic Analysis - RESTART, GUST - SF
If an aerelastic gust analysis attempts to change the number of retained modes

in a restart, then "SYSTEM FATAL MESSAGE 5423" is issued indicating an "ATTEMPT
TO ADD INCOMPATIBLE MATRICES (SADD5)"
Avoidance: Perform a cold start.
37151
2001
miss typed as AXIS
Documentation/QRG - Plot Command AXES is
In case control section of Quick Reference Guide the Plot command AXES page
header and format spell it as AXIS which is incorrect.
37152
- SFM 3001
70.7
"SYSTEM FATAL MESSAGE 3001" occurs in the MODTRK module when all three of the
following are present:
1. shape design variables,
2. at least one subcase with mode tracking
3. and at least one subcase with ANALYSIS=STATICS
Avoidance: Place the MODTRAK request above the subcase level
37169
Error
2001
Documentation/QRG - ADAPT - Typographical
The Quick Reference Guide description of the ADAPT entry contains the
typographical error:
TY=PEUNIP, SIGT=OL22
it should be
TYPE=UNIP, SIGTOL=22
37173
2001
OFTEXIT - Incomplete Design History
Optimization/Design Sensitivity - PARAM,S
In SOL 200, if PARAM SOFTEXIT YES is used and soft convergence is achieved, the
DESIGN CYCLE HISTORY does not include the results
from the final exact analysis.
Avoidance: The information that should be in the DESIGN CYCLE HISTORY can be
obtained using the P1 and P2 parameters on the
DOPTPRM entry.
37178
ted Answers
70.7
Miscellaneous - Missing UFM 315 - Unexpec
If a negative sign is the only character in a field of a bulk data entry it may
be ignored. This may lead to unexpected answers. For example if the negative
sign was intended for the value in the following field as in the following
entry:
CBAR
70101
++000363
++000363
+000364
51001
464
1322
0.
.238
0.
1.0
-
.238
Avoidance: Specify "ECHO=PUNCH" in the Case Control and perform a search

(grep) on negative signs followed by blanks ("- ").
37190
Wrong Answers
70.7
Optimization/Design Sensitivity - PBARL -
Use of PBARL with "T" section in an optimization task may cause an infeasible
result with Version 70.5 or earlier release of MSC.Nastran.
Avoidance:
1. Use equivalent PBAR with DVPREL2 equations defining the PBAR properties.
2. Use a new version such as v70.7.
37195
70.7
Elements - Incorrect Sensitivities
Optimization/Design Sensitivities - Rigid
When a shape optimization job has locations of rigid elements being designed it
may result in incorrect sensitivities or may have difficulty converging. This
may lead to excessive time in the DSVGP5 module.
Avoidance: There is no avoidance. Version 70.7 corrects this error and shows a
dramatic improvement in performance of the DSVGP5 module for some problems.
37222
ssing
Optimization/Design Sensitivity - RESTART - Inefficient Proce
Restarts into SOL 200 will not be efficient if the design model is not
included in the cold start run.
Avoidance: 1. Include the design model in the cold start run
or
2. Insert the following alter in the cold start run:
compile prtsum
alter 1
DBEQUIV WHERE (DESITER=0 and WILDCARD) ,
CONVERT (DESITER=1), OVRWRT $
endalter
37224
2001
DSAD - SFM 4276, Poor Message
In solution 200, when using the cfailure criteria force item code 7
(interlaminar stress), NASTRAN will either fail in the DSAD module with system
fatal 4276 or give
wrong answers if the code is specified for the last lamina (ply). This fatal
occurs because there are no interlaminar stresses for the last lamina since
interlaminar stresses are between laminae. Also, using the cfailure criteria
as force item code 8 (max of FP and FB) will fail unless the lamina (ply)
number specified on the DRESP1 is the final one.
37227
70.7.2
Overflow - SFM 4276 in nmcrd
Nonlinear Analysis - Creep Law May Cause
Some forms of creep law may cause an overflow condition in nonlinear creep
analysis. The error causes an overflow in the nmcrd subroutine which will be
identified in the log file.
Avoidance: A different creep law may avoid the error.
37247
Transient Analysis - TEMP(LOAD) - Wrong Answer
In transient analysis, thermal strains are not subtracted from the total
strains before computing the state of stress. This leads to wrong answers.
Avoidance: This is a limitation, there is no avoidance.
37253
Wrong Answers
2001
Cyclic Symmetry - Virtual Mass, MFLUID -
Virtual mass will cause wrong results when used with cyclic symmetry if a
fluid segment is modeled. This path should be blocked with a fatal error.
Fully enclosed fluids in each segment will give correct answers.
Avoidance: Use acoustic fluid elements instead.
37263
2004
s Not Function Properly
Virtual Mass - MFLUID - PARAM,VMOPT,1 Doe
When param, vmopt, 1 is present, the virtual mass should be added to the
structural mass at the g-set, that is, before any constraints are applied. In
Version 70.6 and 70.7 and V2001, setting this parameter has no effect and the
solution method adds virtual mass after all constraints are applied. This may
or may not affect the results
Avoidance: The alter below will make vmopt, 1 take effect.
compile semg list noref $
Alter 'if ( vmopt=1 and','' $ always do what user requests
IF ( VMOPT=1 ) THEN $
Compile semrm list noref $
Alter 'if ( vmopt=0 or','' $
IF ( VMOPT=0 ) THEN $
Note that the original dmap would over-rule the user's request if it did not
seem to "make sense". The alter always honors the vmopt request. Note that if
vmopt=1 is used on medium- and large-size mode
37264
70.7.2
rage 2 not selected
Performance - MPYAD - MPYAD Method 1, Sto
Under certain condition, the MPYAD Method 1, Storage 2 method, which is

optimized for dense matrices, will not be correctly selected. This happens when
all of the B and D matrices just fit into working memory.
Avoidance: The work around is to either increase or decrease memory.
37272
k with IN=2
Elements - CHEXA - Stress Output at Gauss Points does not wor
Element Stresses at the Gauss integration points cannot be produced for the
8-point CHEXA element when the integration option, IN=2 is used. Instead, the
stresses at the corner points are generated. The description in the QRG for the
PSOLID bulk data entry states that if the stress flag is "1" or "GAUSS" the
integration points will be the location of the stress output, this is
incorrect.
Avoidance: There is no avoidance for this integration option.
37276
nverge
Nonlinear Transient Heat Transfer - TEMPC, TRAN - Fails to Co
This problem has been resolve in NASTRAN 2004 withintroduction of NASTRAN

system cell TBCMAG---close by dan chu
If an nonlinear transient heat transfer analysis has enforced temperature
boundary conditions, that is temperature boundary condition that are a function
of time, MSC/NASTRAN uses the large conductance approach to enforce the
temperature boundary condition. This is achieved by using a CELAS2 entry with
stiffness equal to 1.0E10, and an SLOAD entry on the node with a temperature of
1.0E10. Thus, the temperature is equal to u = F/K or SLOAD divide by the K
value. In some case this hard coded value for the spring stiffness may be to
large and it may adversely affect convergence.
Avoidance:
1. Replace the TEMPBC,TRAN with SLOAD and a CELAS2 entry, and set the
stiffness smaller.
2. Use convergence on P only on the iterations where convergence difficulties
are encountered.
A system cell TBCMAG has been implemented to allow users to adjust the
magnitude of CELAS2. See quality 1-12227004.
37284
ing Utility
70.7
Utilities - MSGCMP.EXE, Windows NT - Miss
The msgcmp.exe executable is missing from the Version 70.5 NT release of

MSC/Nastran.
Avoidance: Download msgcmp.exe from the MSC ftp site or contact your local
support person. The file is located in the /pub/outing directory. Since this
is an executable, use the BIN option for downloading.
37290
ay use the xdb
2001
Documentation/QRG - PARAM,POST - Patran m
The Quick Reference Guide documentation of parameter POST,0 does not mention
the possibility to use the xdb database with MSC.Patran. This should be added
and it should be clarified that the parameters MODEL and SOLID are not
supported by MSC.Patran.
37291
70.7
ong Sensitivities
Optimization/Design Sensitivity - GE - Wr
In a dynamic optimization job, if the design variables include damping

coefficients and the adjoint method path is invoked, then the dynamic response
sensitivity coefficients with respect to all design variables will be
incorrect. This error has been corrected in Version 70.7.
Avoidance: Turn off the adjoint method using the following dmap alter
compile descon
alter 'dsad'(1,-1)
pexist = true
alter 'dsad'
pexist = false
37295
nce
2001
Documentation/QRG - MATHP - Poor Converge
The following sentence need to be added to the Quick Reference Guide

description of the TAB1 parameter of the MATHP entry:
Stresses are negative for compression and positive for tension.
If this convention is not followed the job may fail to converge or issue a
traceback.
37307
2001.0.1
ong Equivalent Stress
Nonlinear Analysis - TEMP(MAT), HEXA - Wr
The "EQUIVALENT STRESS" for the nonlinear HEXA element is wrong if there are
temperature dependent material properties.
Avoidance: There is not avoidance.
37309
70.7
DMAP - APPEND - UFM 4276 EC 1039
The APPEND module may fail and issue the message "USER FATAL MESSAGE
4276.OPENDV EC=1039"
Avoidance: There is no avoidance. The error is fixed in Version 70.7.
37319
70.7.2
- Unexpected Answers
DESGLB is intended for the selection of design constraints at the global level
(e.g., weight, volume). If DESGLB is used above the subcase level with the
intent to apply the constraints to all the subcases, the constraints will be
ignored for the second and subsequent subcases.
Avoidance: Use of the DESSUB above the first subcase applies it to all
subsequent subcases until a new DESSUB request is entered. DESGLB is reserved
for subcase independent response only.
37335
70.7.2
start, Modes Recalculated
Restart - NMLOOP, LOOPID - Inefficient Re
In a restart from SOL 106 to SOL 111, the stiffened modes are being
recalculated unnecessarily.
Avoidance: Insert the following dmap avoidance.
compile semfreq $
alter 'call modefsrs'(,-1) $
equivx lama/lamas/-1 $
equivx pha/phsa/-1 $
if ( false ) then $
alter 'call modefsrs' $
endif $
endalter
37336
ter DEPEND=-1
SSSALTERs - SEGYRO, CYGYR0 Alters - Wrong Results with Parame
The SEGYRO alter puts the gyroscopic terms in the damping matrix and not in the
mass matrix for param, depend,-1 and this leads to wrong answers. The
assumption eigenvalue lambda = i*Omega is not valid in a rotating reference
frame.
The Corillis forces are equal to the mass times the cross product of the
rotation vector times the velocity vector in the ROTATING SYSTEM. ie. f=m(omega
X V ). The assumption that lambda is proportional to i*omega is only good
for a limited set of response cases where the applied load has the same
frequency as the rotations. An example would be an unbalanced turbine. The
problem would diverge at the critical rotational frequency.
37341
2001
- Wrong Answers
Static Analysis - PARAM,CDITER and INREL
If PARAM,INREL,-1 is specified along with PARAM,CDITER,n then no message is

issued stating that PARAM,INREL will be ignored The Version 70.5 Release Guide
and QRG indicate that PARAM,CDITER and INREL are mutually exclusive. A fatal
message will be issued in Version 2001.
37344
Answers
2004
Acoustic Analysis - ACSRCE, DAREA - Wrong
When using an ACSRCE power input during an acoustic frequency response

analysis, if the scale factor on the DAREA is increased, then QDOT is
erroneously factored instead of power.
Avoidance: Scale the values on the TABLEDi instead.
37356
70.7.2
D - SFM3002 (TAH1)
Nonlinear Transient Heat Transfer - DLOA
If transient thermal analysis loads (QVOL, QHBDY) are combined with

temperature dependent material properties (MATT4), then the analysis will fail
with SYSTEM FATAL MESSAGE 3002 in the TAHT module.
37382
Nonlinear Analyis - CBUSH1D, PARAM,LGDISP - Wrong Answers
Small initial values of stiffness for the CBUSH1D element, i.e. K=1, may lead
to wrong results when PARAM, LGDISP,1 is specified. The problem occurs because
the compression displacement is not limited to the length of the element.
Avoidance: Specify a larger value for the stiffness.
37392
5423
70.7.2
Acoustic Analysis - CELAS1, CAABSF - UFM
If frequency dependent elements are present in both the fluid (CAABSF) and the
structure (CELAS1) then the run will fail with UFM 5423.

compile freqrs
alter 'if ( fs )'(2),''
if ( false ) then $
alter 'if ( fs )'(3),''
if ( false ) then $
alter 'if ( fs )'(4),''
if ( false ) then $
alter 'if ( fs )'(5),''
if ( false ) then $
endalter
37394
hod
Eigenvalue Analysis - EIGRL, EIGR - Incorrect Termination Met
The Lanczos method for Real Eigenvalue analysis may not find all desired roots
when ND is specified on the EIGRL bulk data entry. Lanczos may report the
reason for termination as "REQUIRED NUMBER OF EIGENVALUES FOUND IN RANGE" even
though the number of desired eigenvalues is not output.
Avoidance: Specify a frequency range on the eigrl entry.
37399
AIN Requests
70.7.2
DMAP - OUTPTR Module does not Process STR
The OUTPRT module introduced in Version 70.7 does not process STRAIN requests.
As a results the partitioning vector that is generated will not include these
points unless they are requested with other output requests.
Avoidance: An avoidance is to also request STRESS for the same output set.
At present, this module is used only in sssalter spdra.v707.
37400
70.7.2
P-Elements - RFORCE - Wrong Answers
Wrong answers may be obtained when RFORCE is applied to p-elements where p>2.
Avoidance: The only avoidance is to use the origin of the basic coordinate
system to locate the rotation vector.
37402
70.7.2
- UFM 6499(DOM9), UFM 9050(SEKRRS)
When the C field on a BNDGRID entry in a shape optimization task is left blank
or takes the value of zero, this input error is not detected. Therefore, the
job may fail in one of the following ways:
1. UFM 6499 (DOM9) due to a zero gradient of a violated constraint
2. UFM 9050 (SEKRRS) due to excessive pivot rations in Matrix KLL.
3. Wrong Answers
Avoidance: Specify a non-zero component on the C field.
37403
2001.0.1
DMAP - MATMOD - Wrong Answers
If the first input, I1, to the MATMOD module, under option 12, is purged then
the module will incorrectly report that NONULL=0 and the O1 output is purged
without warning or fatal even if the second and third inputs (I2 and I3) are
not purged and contain null columns. The documentation for MATMOD option 12
contained in the DMAP Module and Data Blocks Guide states that only I2 and I3
may be purged, which implies that a fatal message should be issued if I1 is
purged.
Avoidance: Rearrange the inputs so that the first input is not purged.
37407
4276 EC 3001
2005.1
Superelements - SEP1X, DTI, SETREE - SFM
If external superelements are used in a multi-level model containing PART

superelements (BEGIN SUPER), and the multi-level tree is defined using a
DTI,SETREE entry, the run may fail in the SEP1X module with SYSTEM FATAL
MESSAGE 4276. The fatal message will indicate that "ERROR 3001 HAS OCCURRED IN
GREAD".
Avoidance: Replace the DTI,SETREE entry with an SETREE entries.
Actual error in DTI,SETREE where the user entry was DTI,SETREE,0 when the QRG
stipulates DTI,SETREE,1 as the required starting format. Using the latter the
job executes properly as a multi-level tree. Code corrected to use default of
single level as a processing attempt, and for this job is also successful.
37411
te CPU Loop
70.7.2
Parallel Processing - DMP - FATAL, Infini
If MSC.Nastran is run with DMP=n (n > 1) on an NEC system, and there is a FATAL
message, then the processors which do not get the FATAL hang. They accumulate
CPU time, but never finish.
Avoidances: Avoidances are given below; however, this and several other
problems related to DMP have been corrected in Version 70.7.2. DMP users
should install this later version.
1. Modify the $MSC_BASE/bin/nast707.lcl file:
insert after line 294:
%MSC_ARCH=superux:%
errorcode=$?
insert at the end of the file:
%MSC_ARCH=superux:%
exit $errorcode
2. Or run without DMP being specified.
37437
70.7.2
REQ subcases - Infinite loop
Frequency Response - dmp>1 and multiple F
A job with multiple frequency subcases submitted with Distributed Memory

Parallel, dmp>1, in solution 111 will hang.
compile freqrs
alter 'ckdd,cbdd'(,-1) $
putsys(1,287) $
alter 'ckddf,cbddf'(,-1) $
putsys(1,287) $
compile semfreq
alter 'fs and'(,2),''
jump endloop $
alter 'if ( loopflag'(,-2)
label endloop $
endalter
37454
- SFM
70.7.2
Parallel Processing - DMP, ITER=YES, SPCF
If distributed memory parallel processing is specified with the iterative

solver and spcforces are requested, the the job will fail.
Avoidance: Either do not request spcforces, distributed processing, or the
iterative solver.
37457
70.7
Smax, Smin - Possible Wrong Answers
In an optimization run, if PBARL is used and only Smax or Smin is specified

instead of the four stress data recovery points, then wrong answers may occur.
1. Specify all four stress data recovery points instead of using Smax or
Smin.
or
2. Use PBAR instead of PBARL.
37458
g BLKWRT
2001.0.1
DBC - DBC, PARAM,POST - Job Crashes durin
A job with thousands of subcases may fail in DBC during a BLKWRT. The
following message was encountered:
MSC.XL
DATA BASE CONVERSION STARTED

PROJECT
0
0
PATHQUAL
0
0
PATHLINK
0
0
0
PATHINT
0
0
POST-PROCESSING DATA RECOVERY INITIATED

SUBCASES
1
0
0
0
0
0
ILLEGAL DATA BASE NUMBER PASSED TO BLKW
37462
70.7.2
SEQP - SFM 4276
Parallel Processing - DMP>1, CBAR, CBEAM,
If a statics job is submitted with Distributed Parallel Processing, dmp>1, and

the job contains BAR or BEAM elements that specify disjoint GRID points for the
orientation vector then the job may fail in the SEQP module or hang.
Avoidance: There are several avoidances:
1. Do not use distributed parallel processing.

2. Modify the CBAR, CBEAM entries to explicityly define a coordinate
direction.
3. Modify the CBAR, CBEAM entry to reference an attached GRID point.
4. User Version 70.7.2 where this error has been corrected.
37483
70.7
LEGAL INPUT TO SUBROUTINE NLCXGR
Nonlinear Analysis - SFM 3007 (NLCOMB)/IL
MSC.Nastran may fail with SYSTEM FATAL MESSAGE 3007 (NLCOMB), ILLEGAL INPUT TO
SUBROUTINE NLCXGR on Sun/Solaris systems when run with MEM => 2Gb.
Avoidance: Either:
1. Reduce memory below 2Gb
2. Run with version 70.7 or higher.
37485
70.7.2
ct Sensitivities for Static Aero
Incorrect sensitivities and subsequent poor optimization performance occurs on

long word machines, such as the CRAY, for static aeroelastic sensitivity
analysis when there are more design variables than there are AESTAT and AESURF
entries.
Avoidance: Run the job on a short word machine, reduce the number of design
variables, or increase the number of AESTAT/AESURF entries to satisfy the
above inequality.
37486
70.7.2
dofs may be autospcd
SSSALTERs - GPSP, PARAM,AUTOSPC - be-set
The be-set is a new set introduced in Version 70.7. It is not used in any
solution sequences at present. Its only use is in the rflaga.v707 alter
package.
The be-set should not be autospcd, even when singular. This is analogous to
the suport entry. It sometimes is autospcd, although the circumstances when
this happens are not well understood yet.
Avoidance: An avoidance is to always used an spcoff entry for every be-set
point. It may not be necessary, but it should not cause problems either.
Example
uset, be, 17, 3
spcoff, 17 3
37487
or Message
70.7.2
Miscellaneous - USET - UFM 2104 (GP4), Po
The be-set is new in Version 70.7. When a degree-of-freedom is placed in a

mutually exclusive set, such as the s-set, and the be-set, the following
truncated message appears:
SCALAR POINT
1 ILLEGALLY DEFINED IN SETS
US
The phrase "UBE" should also appear.

If you see a message of this type look for be-set entries on the same dof .
These dofs are entered on USET, BE-type inputs.

37495
70,7
Documentation - Hoffman's Theory incorrec
t in Composites Seminar Notes (NAS113)
The Equation for Hoffman's Failure Theory in Chapter 5 of the NAS113 (Analysis
of Composites Materials) semninar notes is incorrect. There is a sign error for
one term. The term:
(SIG1*SIG2) / (Xt*Xc)
should be preceded by a negative sign in the equation.
37496
ong Answers
2001
Frequency Response - CELAS2 , STRESS - Wr
In a direct frequency response analysis, the stress output for the CELAS2
element is incorrect.
Avoidance: Use the CBUSH element instead,
37503
IFS5P)
2001.0.1
Acoustic Analysis - Misleading UWM 5462 (
The presence of acoustic elements always leads to the following misleading

warning message:
*** USER WARNING MESSAGE 5462 (IFS5P)
OPTIONS IN PSOLID ID = 800000 FOR FLUID ELEMENT ARE NOT ALLOWED.
DEFAULT VALUES WILL BE TAKEN.
Avoidance: Ignore the warning message.
37508
GPFORCE - PARAM,NOELOF - Incorrect Format on PUNCH Output
If PARAM,NOELOF,1 is specified the punch output format for GPFORCE is

incorrect.
Avoidance: There is no avoidance for this option. The f06 output is correct.
37585
707
Case Control - SET - Duplicate Output
If a SET command is used to request grid point output, and the set contains a
thru range referencing non-existing grid points, then duplicate output will be
printed for the last existing grid point. For the following example, no grid
point exists between the range of 10001 and 10010, the displacement for grid
point 12 is printed twice.
SET 1 = 11,12 , 10001 THRU 10010 $
DISP(PHASE,SORT2) = 1
Avoidance: Remove the reference to the non-existing grid points in the set.
37590
70.7.2
MPC forces in SOL 144
GPFORCE - GPFDR - Output does not include
When Grid Point Forces (GPFORCE) are requested in SOL 144 (Static Aero), the
forces of multipoint constraint (MPCFORCE) should be included in the output,
but are not.
Avoidance: Add the MPCFORCE=ALL or MPCFORCE(PLOT)=ALL output request to Case

Control to cause the MPC forces to be computed. Once computed, they will be
included in the GPFORCE output.
37593
70.7.2
M 1126 (GNFIST)
Superelements - CSUPER, STATSUB, SPC - UF
In a normal modes analysis with image superelements (CSUPER), if the structure

is preloaded (STATSUB) and spcs are applied to the interior of the primary
superelement, then the job will fail with the following unclear error messages:
DMAP MODULE MATREDU IS ATTEMPTING TO OUTPUT DATABLOCK
202 NAME =
KDSF
USER ACTION: DELETE THE DATABLOCK, OR USE FILE KDSF=OVRWRT
Avoidance: Replace the following nddl statement
PATH KDSF
PEID,MPC,SPC,MTEMP,NLOOP,DESITER,PVALID,
APRCH,HIGHQUAL,K2GG,M2GG,AUXMID,STATSUB,P2G $
with
PATH KDSF
seid,PEID,MPC,SPC,MTEMP,NLOOP,DESITER,PVALID,
APRCH,HIGHQUAL,K2GG,M2GG,AUX
37597
70.7.2
ts - Modes Not Deleted
SSSALTER - delmodea.vxx, Part Superelemen
When using the delmodea.vxx alter with PART superelements, and the DMI,SKPMODE
entry is placed in the main bulk data section, then selected modes will not be
deleted. The following warning messages will be issued:
^^^ USER WARNING MESSAGE: MODE PARTITIONING MATRIX NOT FOUND IN BULK DATA
^^^
PLEASE CHECK INPUT DECK FOR DMI, SKPMODE ENTRIES
^^^
^^^ THE MODE DELETION ROUTINE CANNOT CONTINUE - NORMAL PROBLEM SOLUTION
CONTINUING WITH ALL MODES...
Avoidance: Either request a copy of the updated alter from your local support
engineer or put the DMI, SKPMODE in the last partitioned bulk data section.
37598
70.7.2
s - Infinite loop
Parallel Processing - DMP, Component Mode
If distributed parallel processing is selected by setting dmp>1 on a component

modes analysis the job may hang.
compile cmpmode
alter 'xofp'
if ( getsys(np,265)>1 ) then $
delete /cmlama,cmphixz,cmmi,cmoeigs,eigvmats $
disutil ,,,,/cmlama///3 $
disutil ,,,,/cmphixz///3 $
disutil ,,,,/cmmi///3 $
disutil ,,,,/cmoeigs///3 $
disutil ,,,,/eigvmats///3 $
paraml
cmphixz//'trai
37600
LSTRESS Format
70.7.2
Nonlinear Analysis - PSHELL - Incorrect N
The NLSTRESS format is wrong if both plane-strain and plane-stress shell

elements exist in the same input file. That is if multiple PSHELL records
exist, some with MID2>-1 and some with MID2=-1.
Avoidance: This output can be turned off by requesting NLSTRESS=NONE.
Another avoidance is not to put both types of shell elements into a single
nonlinear run. The other results (including the stresses using the linear
format) are not affected.
37602
70.7.2
e solver - SFM 4276 (UNPACK)
Static Analysis - DMP, dmp>1 and iterativ
If a SOL 101 run is made with Distributed Memory Parallel and the iterative
solver is selected, then the job may crash with the following message:
*** SYSTEM FATAL MESSAGE 4276 (UNPACK)
ERROR CODE
20 PID= 0
Avoidance: Do not use DMP. The error is corrected in Version 70.7.2
37606
70.7.2
lts=yes, OLOAD - Wrong Answers
Parallel Processing - DMP>1 and mergeresu
In static analysis with domain decomposition (a.ka., Distributed Memory

Parallel, dmp>1) and mergeresults=yes on the nastran submittal line, the OLOAD
output and OLOAD maximums will be wrong for the boundary points if
distributed loads like PLOAD and GRAV are applied.
compile sedisp
alter 'pj0s','pj0s'(,1)
upartn usetx,pj/pax,pga,,/'g'/'a'//1 $
merge
,,pax,,,,spcpart/pag0/1 $ Loads at boundary due to local
$ distributed loads
DISUTIL pag0,,,/pg0///8 $ sum of all boundary dist. loads
disutil pg0,,,/pg00///3 $ broadcast to slaves
if ( getsys(np,265)>1 ) equivx pg00/pg0/-1 $
37615
2001.0.1
CMPD), SFM 7340
Eigenvalue Analysis - EIGRL - UWM 4698 (D
When Lanczos encounters a massless mechanism it will first provide the

following message:
GRID POINT ID
MATRIX DIAGONAL
37633
DEGREE OF FREEDOM
MATRIX/FACTOR DIAGONAL RATIO
Restart - EIGRL, EIGR - Inefficient Restart
In a restart run, if an unreferenced EIGRL (or EIGR) is added to the restart

run input, then the modes will be recalculated even though the entry is not
referenced.
Avoidance: Remove the unreferenced EIGRL/EIGR entry.
37635
t Answers
Nonlinear Transient Analysis - RESTART, PARAM,G, GE -Differen
In a nonlinear transient restart analysis, if large displacement is turned on

(param,lgdisp,1), and param W3 damping exists in the model (with PARAM,G ),
the results may be different than the one in the coldstart run. The difference
is due to the possible non-syncronization of the stiffness update between the
coldstart and restart runs.
Avoidance: Recommended damping in nonlinear transient (SOL 129) is param, W4
damping with GE value in MAT1.
If stiffness update syncronization is desired with param W3 damping, set
KSTEP=1 to force the stiffness update.
Care must be exercise when there is adaptive gap element since the penal
ty
stiffness can be fictituously
high inducing an unrealistic high damping force.
37642
- SWM 2072
2004.5
Restarts - CBUSH, CAABSF, GMINTS, GMINTC
If a model contains CBUSH elements, then upon RESTART SYSTEM WARNING MESSAGE
2072 will be issued by the RESTART module when it compares the GEOM2 data
block. A similar error can occur if the model contains CBEND, CAABSF, GMINTS,
or GMINTC entires.
Avoidance: No avoidance is necessary, ignore the message.
37646
2001
rk 3 of CSUPER Entry
Documentation/QRG - CSUPER - Improve Rema
Remark 3 of the description of the CSUPER bulk data entry in the QRG should be
improved to read:
3. For identical or mirror image superelements, the grid point IDs, GPi, may
appear in any order. However, if they are not in the same order as the external
GRIDs of the primary superelement, then the SEQSEP entry is also required. In
case of external superelements, the GRID IDs must be in the order that the
terms in the associated matrices occur in.
37653
n
2001
Documentation - CREEP - Thermal Correctio
The Quick Reference documentation for the CREEP entry should be changed to
further explain what turns on the thermal correction for the creep strain rate.
If the T0=0.0 or blank, then the thermal correction is not utilized. However
if PARA,TABS is used, TABS is added to T0 and then the thermal correction is
utilized even if T0 is blank or 0.0. If thermal correction is utilized then,
EXP must be meaningful and have the consistent units.
37661
70.7.2
UFM 7323, Possible Wrong Answers
Superelement - Repeated SUPER Command -
If the SUPER case control command is repeated incorrectly as shown below

.
subcase 100
super = 0,1
.
subcase 200
super = 0,2
.
subcase 300
super = 0,1
.
then following unclear fatal message is issued
*** USER FATAL MESSAGE 7323 (SEDRA)
SUBCASES FOR SUPERELEMENT
0 HAS A LOAD SEQUENCE NUMBER =
IS OUT OF ORDER.
1 WHICH
The job will continue to execute and the results are unpredictable.
Avoidance: Correct the offending SUPER case control command.
37700
70.7.2
Memory Processing - SFM 7492
Parallel Processing/Statics - Distributed
If DMP is specified on the command line for a SOL 101 run, the following error
message may appear:
*** SYSTEM FATAL
INCONSISTENT
ACCORDING TO
ACCORDING TO
USER ACTION:
MESSAGE 7492 (PRESOL)

VALUE FOR NUMBER OF LOCAL GRIDPOINTS ON PROCESSOR
1:
SIL TABLE, THE NUMBER OF LOCAL GRIDPOINTS IS
100763
GEQMAP, THE NUMBER OF LOCAL GRIDPOINTS IS
101073
PLEASE CONTACT MSC.SOFTWARE CLIENT SUPPORT.
Avoidance: Do not use DMP. This error is corrected in Version 70.7.2.

37719
PSEQ
2001
Documentation - V70.7 Release Guide - DCM
Section 2.7 of the Version 70.7 Release Guide documents a new keyword
"DCMPSEQ". This section of the guide does not give examples and it contains a
typo. The Guide states that this keyword is the same as SYSTBM(206), this is a
typo, it should be SYSTEM(206). It states that the new option is invoked by
adding 64 to the value of the keyword; however the default of SYSTEM(206) is
not documented. The default value of SYSTEM(206) is 4 for all systems except
NEC, the default for NEC is 0. This keyword must be set on the NASTRAN command
line in the input deck.
For all systems except NEC the input to activate this option is:
NASTRAN DCMPSEQ=68
or
37748
2001
ages - Wrong DOF Output
Miscellaneous - V70.7, New Log File Mess
The following new messages are sent to the log file in Version 70.7:
10:32:43 Finite element model generation started.
10:32:43 Finite element model generated
1 degrees of freedom.
10:32:43 Finite element model generation successfully completed.
The second message above always reports 1 DOF which is in almost all cases
wrong.
37764
70.7.2
DMP, PARAM,RESVEC - UFM
Parallel Processing/Frequency Response -
Distributed Memory Parallel frequency response analysis will fail when

PARAM,RESVEC,YES is used to specify residual flexibility.
Avoidance:
Either:
1) Run using a newer version (V70.7.2 or newer)
2) Do not use residual vectors with dmp
3) Insert the following DMAP alter:
compile resvec
alter 'read '(,-1)
$ For dmp>1, deactivate parallel
np=getsys(np,197) $ capture NUMSEG
if( np>1 ) putsys(0,197) $ set NUMSEG=0
alter 'read '
if( np>1 ) putsys(np,197) $ restore NUMSEG
compile cmpmode
alter 'read '
if ( getsys(np,197)>1 and getsys(np,265)>1 ) then $
$ Since the master node has all modes, then
$ then we will generate a dummy mode on the
$ slaves to avoid hang-ups.
delete /cmlama,cmphixz,cmmi,cmoeigs,eigvmats $
37773
rmance
70.7.2
Matrix Methods - PARTN/MERGE - Poor Perfo
The PARTN and MERGE modules perform poorly when the partitioning vectors are
purged.
Avoidance: There is no avoidance but this has been corrected in Version 70.7.2.
37775
70.7.2
Miscellaneous - Q4SKEW,Q4TAPER, TETRAAR,
and T3SKEW do not work in Unix rcfile
On unix workstations, if you attempt to set SYSTEM cells 189, 190, 191, or 218
in the "rcfile" using the cell name (Q4TAPER, Q4SKEW, TETRAAR, T3SKEW), the
default values will be used for these cells with no warning messages issued,
Avoidance: Use the SYSTEM cell number in the "rcfile" for these cells. For
example:
nastran
nastran
nastran
nastran
37793
system(189)=1.
system(190)=1.
system(191)=100.
system(218)=1.
2001
Nonlinear Normal Modes - RESTART, PARAM,F
OLLOWK - Wrong Answers

Nonlinear normal mode analysis by a restart in SOL 103 from SOL 106 database
gives erroneous solution in presence of follower forces in Version 70.7. The
follower
stiffness is not included in this restart runs. This error may be avoided if
the normal mode analysis is performed in SOL 106 during the coldstart run, or
SOL 103 is used with a statsub option for the preload. However, a restart
procedure is required if free-free modes are subject to
a nonlinear deformation under the preload.
Avoidance: For free-free modes, insert the following DMAP alter into the SOL
103 restart
compile semg
alter 'call semg1'
type parm,,char8,y,followk='yes' $
TYPE PARM,,RS,N,stol=0. $
type db slt $
dbstatus slt//s,n,noslt $
PARAML CASES//'DTI'/COLNO/4//S,N,LOADID $
if ( followk='yes' and noslt>0 and loadid>0 and
seid=0 ) then $
TAFF
SLT,BGPDTS/ESTF,GPECTF/
LUSETS/LOADID/0/1. $
EMG
ESTF,CSTMS,MPTS,DIT,,UGni,ETT,EDT,
DEQATN,DEQIND,BGPDTS,GPSNTS,,,,/
KFELM,KFDICT,,,,/
1/0/0//1/////////-1/1. $
EMA
GPECTF,KFDICT,KFELM,BGPDTS,SILS,CSTMS,,/
KFGG0,/-1 $
dbview cstm0=cstms where (peid=0) $
emakfr bgpdts,cstms,slt,mjj,cstm0,scstm/
kfrfgg/loadid $ rforce stiffness
ADD5
KFGG0,kfrfgg,,,/Kfgg $
PARAML KFGG//'TRAILER'/3/S,N,UNSYM//S,N,NOKFGG $
IF ( UNSYM<>6 AND NOKFGG>-1 ) THEN $
$ Symmetrize stiffness matrix if unsymmetric
TRNSP
KFGG/KFGGT $
ADD5
KFGG,KFGGT,,,/KF/1./-1. $
norm
kfgg/dummy///s,n,xnorm/1 $
stol = xnorm*1.e-11 $ tolerance recommended
matmod kf,,,,,/kfa,/2////stol $
paraml kfa//'null'////s,n,notnull $
if ( notnull=-1 ) modtrl kfgg////6 $ symmetric
ENDIF $ UNSYM<>6 AND NOKFGG>-1
add
kfgg,kjj/kfjj $
equivx kfjj/kjj/-1 $
ENDIF $ FOLLOWK='YES '
endalter
37797
70.7.2
rk for all diags
Documentation - diag= keyword does not wo
The "diag" command line keyword does not work for all possible diag flags. In
particular, diag flags 5 and 6 cannot be set from the command line or an RC
file.
Avoidance: Set these diags in the bulk data file using the standard DIAG
statement, DIAG 5,6
37799
(DOPR3)
2001
Optimization - DRESP2, DRESP1 - SFM 3007
In an optimization run, if a DRESP2 references both DRESP2 and DRESP1, and the
DRESP1 references a property PTYPE (e.g., PBAR) which points to more than one
element, then the job will fail with the following error messages:
*** SYSTEM FATAL MESSAGE 3007 (DOPR3)
ILLEGAL INPUT TO SUBROUTINE DOPR3J
0FATAL ERROR
*** SYSTEM INFORMATION MESSAGE 1156 (XCLNUP)
GINO FILE 110 WAS LEFT OPEN AT PROGRAM TERMINATION.
1. Avoid referencing a DRESP2 with a DRESP2, reference a series of DRESP1
instead.
2. Reference ELEM instead of property on the PTYPE field on the DRESP1 entry.
37805
70.7.2
S=MFREQ - UFM 9068
The message "USER FATAL MESSAGE 9068 NO DRESP1 OR DRESP2 ENTRIES EXIST FOR
DESOBJ=n" may be issued in error for a solution 200 analysis that contains only
frequency or transient analysis subcases and the objective is a WEIGHT or
VOLUME response. The fatal will only occur if the DRESP1 ID that is just below
the ID called out by the DESOBJ request has a blank ATT1 field on the DRESP1
bulk data entry; i.e., the response is RTYPE = EIGN, FREQ or LAMA.
Avoidance: Provide an ID on the DRESP1 entry for the WEIGHT or VOLUME objective
that is lower than any other DRESP1 ID or ensure that
the ID that is just below the objective ID has a non-blank ATT1 value.
37806
2001.0.1
Documentation - V70.7 Release Guide
Release Notes, p50, "File Size Reduction for Modal Frequency Response"
The efficiencies described in this section require the use of sssalter
spdra.v707, available on the msc internal web site. Contact your local MSC
Technical Representative to get a copy of this dmap alter.
37812
ct EPSILONs
70.7.2
P-elements - InterFace Elements - Incorre
The EPSILON table produced when interface elements are used is incorrect in the
NEC Version 70.7.0 release of MSC.Nastran The EXTERNAL WORK is correct
however.
Avoidance: There is on known avoidance. The error has been corrected in
Version 70.7.2.
37832
001(TA1)
70.7.2
Heat Transfer - TSTRU, TEMP(INIT) - SFM 3
If TEMP(INIT) is set to the same ID as TSTRU then the job will fail with the
message:
*** SYSTEM FATAL MESSAGE 3003 (TA1)

ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK ETT
(FILE 106) IN SUBROUTINE TA1ETD
Avoidance: Specify a different set ID for TEMP(INIT).
37833
70.7.2
m on CD state incorrect MPT version
Installation - INSTALL.txt and INSTALL.ht
The files INSTALL.txt and INSTALL.htm on the V70.7 CD state that for running
distributed parallel MSC.Nastran on SGI R8K/ R10K/R12K, MPT 1.5 is required.
This is a typo, MPT 1.3 is required.
37834
en in V70.7
70.7.2
Estimate - buffsize=estimate keyword brok
In Version 70.7, if the keyword buffsize=estimate is used, then the job will
fail with the following error messages in the f06 file.
NASTRAN BUFFSIZE=ESTIMATE $(/USERS/SWAN/.NAST707RC[26])
*** USER FATAL MESSAGE 17 (LOOKUP)
SYMBOL "ESTIMATE" IS UNDEFINED
followed later by:
*** USER WARNING MESSAGE 782 (SYSCHK)
THE NASTRAN BUFFSIZE PARAMETER CANNOT BE SMALLER THAN MACHINE DEFAULT =
2049
USER INFORMATION: NASTRAN BUFFSIZE PARAMETER IGNORED.
USER ACTION: USE THE INIT FMS STATEMENT TO SET THE DESIRED BUFFSIZE FOR
EACH INDIVIDUAL DBSET.
*** USER INFORMATION MESSAGE 480 (SYSCHK)
JOB TERMINATED DUE TO ABOVE ERROR(S) IN THE NASTRAN STATEMENT PROCESSOR.
FATAL ERROR
Avoidance: Specify a specific buffsize.
37835
70.7
rts No Disk Space Available
Installation - HP-UX, Install Script Repo
Under some circumstances on HP-UX systems, mscsetup may report "0 MB" disk
space available on NFS or automounted filesystems. The full circumstances are
not yet known.
Note: The error is a direct result of incorrect information being returned from
the df(1) command on HP-UX 10.20 and 11.00. The specific command used by
mscsetup is "df -k", and sample output showing the error is:
$ df -k /net/trinity/scratch
/tmp_mnt/net/trinity/scratch (trinity:/scratch
allocated Kb
) :
0 total
0 free allocated Kb
0 used allocated Kb
45 % allocation used
Another invocation of df, that does not return sufficient i

37837
70.7.2
Documentation/Estimate - Minimum Values
The ESTIMATE utility will apply a minimum value to estimates for the following:
Parameter
--------memory
disk
sdball
scratch
scr300
Keyword
Default Value (MB)
---------- -----------------memmin
16
dskmin
1
dballmin
1
scratchmin
1
scr300min
1
The minimum value is applied after the conservative value (i.e., "memco",
"dskco", "dballco", "scratchco", and "scr300co" respectively). Thus, setting
"memco=0.5" to reduce all memory estimates by 50% will have *no* effect if the
estimate falls below the minimum value.
37843
4577 (GP3C)
70.7.2
Loads - PLOAD4, Large Field Format - UFM
If a PLOAD4 references an element with large field format, the job may fail
with the message:
USER FATAL MESSAGE 4577 (GP3C)
PLOAD4 LOAD SET= 1 REFERENCES ELEMENT ID =*******************
WHICH WAS NOT FOUND AMONG TRIA3, TRIA6, QUAD4, QUAD8, HEXA, OR PENTA ELEMENTS
Avoidance: There is no avoidance other than renumbering the elements.
37844
2001
olution Sequence
Accounting - XSEMDR - Can not Determine S
In releases prior to Version 70.7 the f04 Execution Summary ended with the
last module specific to the solution. Beginning in Version 70.7 the f04
Execution Summary ends with the last line XSEMDR END. For example:
13:19:02
0:13
EXIT
BEGN
13:19:02
0:13
212.0
212.0
0.0
0.0
12.8
12.8
0.0
0.0
NLTRAN 527
XSEMDR END
This prevents the accounting program provided my MSC which reads the last line
from determining the solution sequence.
37859
at in V70.7
70.7.2
Miscellaneous - Missing TPL file mcso42.d
The file mcs042.dat was missing from the Version 70.7 tpl. It has been added
to the Version 70.7.2 tpl.
37862
GL
th system checkpoint capabilities
Miscellaneous - FLEXlm can not be used wi
MSC.Nastran jobs (as well as any other program) that use FLEXlm licensing or
any other socket-based communications cannot be checkpointed by system-level
checkpoint/restart capabilities, such as SGI's cpr utility. If attempted
messages similar to the following will be issued in the log file:
Checkpointing id 259527 (type PID) to directory /tmp/test.cpr
CPR Error: Uncheckpointable fd, pid 259527 fd 10 type socket
Checkpoint failed. Restarted all processes back to their running states
CPR Error: ckpt_create child failed: errno 47 (Checkpoint/Restart error)

Failed to checkpoint process 259527
--------------------------------Avoidance: Use a node-lock authorization code for licensing and avoid the use
of any socket connections by MSC.Nastran.
37872
07
2001
SSSALTERs - checka, PARAM,LANSUP - SFM 30
If PARAM,LANSUP,1 is used in the checka sssalter in version 70.5, 70.6, or

70.7, the run will fail with SYSTEM FATAL MESSAGE 3007 indicating an illegal
operation while merging matrices.
Avoidance: Replace:
UMERGE USET,DMI,Dar/DM1/'A'/'R'/'L' $ DN changed to DAR
with:
equivx dar/dm1/-1 $
37873
oes Not Exist
70.7
Old Design Sensitivity - SFM 3001, MPTS D
If the old sensitivity (SOL 103) is used and no material entries are present,
the run will fail with SFM 3001 indicating that data block MPTS does not exist.
Avoidance: 1) use SOL 200 to perform similar task or
2) or add a dummy material to the input file if the old dsa is used.
37880
70.7.2
ut with Multiple Subcases - UFM 5423
Parallel Processing - DMP - SPCForce Outp
Distributed Memory Parallel jobs, dmp>1, with multiple subcases will fail with
the following message if spcforce output is requested.
*** USER FATAL MESSAGE 5423 (SADD5)
ATTEMPT TO ADD INCOMPATIBLE MATRICES, (SADD5)
IS
1 450
2
2
0
0
IS
2 450
2
2
24 267
TRAILER FOR QG0S

TRAILER FOR QGI
0FATAL ERROR
Avoidance: Either do not select dmp or do not select spcforces.

37886
2001
K - Poor Performance EMAKFR
Nonlinear Analysis - RFORCE, PARAM,FOLLOW
Nonlinear analysis of large problems with RFORCE as a follower force may

exhibit poor performance in EMAKFR.
37892
e fails
70.7.2
Documentation/COG - V70.7 smaster=estimat
The "MSC.Nastran V70.7 Configuration and Operations Guide" incorrectly states

that "smaster=estimate" is valid, it is not.
Avoidance: Set an actual size if the MASTER DBSet default size needs to be
increased.
37898
2001
Superelements - SDAMPING; PARAM,SESDAMP,Y
ES - NORM=MAX or POINT, Wrong Answers
Superelement modal damping (PARAM,SESDAMP,YES) produces incorrect answers
when
MAX or POINT normalization is selected on the EIGR or EIGRL entries.
Avoidance: Use MASS normalization which is the default.
Verified in R.32. -TIN37907
70.7.2
PCOMP - UFM 5503
The message:
UFM 5503 ELEM NO. n PLY NO.y REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND
may be issued in error for composite responses (DRESP1 RTYPE=CSTRESS,CSTRAIN
or CFAILURE) if the SOUTi requests on the underlying PCOMP entries have
different values for the different layers (i.e., some are YES and some are NO
or blank).
Avoidance: Make all the SOUTi requests on a given PCOMP entry the same if
design responses are to be imposed on elements associated with the PCOMP.
37913
70.7.2
gnize LSF Submittal
Submittal - nastran Command does not reco
The nastran command does not automatically recognize a submittal via LSF. For
NQS, the nastran command will recognize it is running in a batch job and set
the defaults batch=no and notify=no. In addition, if submitted as a DMP job by
LSF, the nastran will not recognize the list of selected hosts.
Avoidance: The problem may be avoided by:
1. set
running
2. Set
command
37918
ed
notify=no and batch=no in an RC file or on the command line when

under LSF.
hosts=$(print $LSB_HOSTS | sed 's/^ *//;s/ *$//;s/ */:/g') on the
line when running a DMP job under LSF
2001
Documentation/DMAP - DISUTIL not document
The MSC.Nastran DMAP Modules and Datablocks CD for Version 70.7 mentions, but
does not document the module DISUTIL The following is the documentation for
this module:
Broadcast data blocks between slave and master processors for parallel
processing.
Additional processing may occur on the master processor.
Format:
Format for DISMETH=1 or 2:
DISUTIL B,X,R,EQMAP/
EPSSE/
NSKIP/S,N,EPSI/1 or 2 $
Format for DISMETH=3 on master processor:
DISUTIL DB,,,////3 $
Format for DISMETH=3 on slave processor:
DISUTIL ,,,,/DB///3 $
Format for DISMETH=4 or 5:
DISUTIL RESMAX,RESMAX0,CASECC,HEADCNTL////4 or 5 $
Format for DISMETH=6:
DISUTIL UG,SPCPART,GEQMAP,/UGG///6 $
Format for DISMETH=7:
DISUTIL PG,SPCPART,GEQMAP,/PGG///7 $
Format for DISMETH=8 or 9 on master processor:
DISUTIL MATS,,,
37925
2001
UFM 5629 (DSAD1C)
If RTYPE=STRESS or STRAIN in a composite optimiztion deck with NOCOMPS=1, the

following fatal message is issued.
*** USER FATAL MESSAGE 5629 (DSAD1C)
THERE ARE DRESP1 ENTRIES FOR RESPONSE TYPE =
CORRESPONDING OUTPUT RESPONSES.
Users need set nocomps=0 or -1.
37932
2001
, DVCRELi, scr=no - Wrong Answers
STRESS BUT THERE ARE NO
Optimization/Design Sensitivity - DVMRELi
In an optimization run, if the design variables involve

(DVMRELi) or connectivity (DVCRELi) only, and scr=no is
converge prematurely. A symptom of this problem is the
termination after the first design cycle with no change
function.
material properties
used, then the run will
unexplainable job
in the objective
Avoidance: Run the job with scr=yes or insert the following alter:
compile update
alter 'RESTART EPTS,EPTSP'
DBVIEW mPTSP=mPTS
WHERE (DESITER=DESP) $
RESTART mPTS,mPTSP,/UHIST $
DBVIEW geom2SP=geom2S
WHERE (DESITER=DESP) $
RESTART geom2S,geom2SP,/UHIST $
endalter
37944
2001
Datablock Dictionary
Documentation - VECPLOT - DMAP Module and
The Version 70.7 DMAP Module and Data Blocks Dictionary has incorrectly
indicates that the VECPLOT module has only one output datablock. Starting in
Version 70.7 the VECPLOT module has two output datablocks. This is correctly
documented in the V70.7 Release Notes.
37952
70.7.2
cedence of Keywords
Documentation/COG - Estimate Program, Pre
The precedence of ESTIMATE processed keywords in the MSC V70.7 Configuration

and Operations Guide listed in Section 6.2 should be as follows:
1) ESTIMATE keywords, which are also NASTRAN keywords that are recognized
in the bulk data file (Example: NASTRAN BUFFSIZE=4097)
2) ESTIMATE keywords on the command line, Example: msc707 estimate myjob.dat
memco=2.5
Note: NASTRAN only keywords will cause an error (example: auth=1700@server)
3) ESTIMATE keywords, which are also NASTRAN keywords, contained in the nastran
INI and/or RC files
(example: buffsize)
4) ESTIMATE keywords contained in data-file-directory/.estimaterc on UNIX, or
data-file-directory\estimate.rcf on NT, where
data-file-directory is the directory containing the input data file
5) ESTIMATE keywo
37969
EPO21)
2005
Superelements - Poor Message, UFM 6790 (S
UFM 6790 shown below is output when a list superelement has no points that can
be identified as boundary points. The fatal message is followed by table print
which may be ignored.
*** USER FATAL MESSAGE 6790 (SEPO21)
THE FOLLOWING SUPERELEMENTS ARE DETACHED:
1
3
62000000007
52000000008
212000000002
222000000003
232000000004
242000000005
252000000006
61101529088
71102053376
81102577664
91103101952
101103626240
11
22000000001
42000000007
52000000008
212000000002
22
2000000003
232000000004
242000000005
252000000006
-1
0
0
0
0
0
37978
2001
nce for Small Loads
Nonlinear Analysis - HEXA - Poor Converge
Geometric nonlinear analysis (SOL 106 with PARAM LGDISP > 0) with solid
elements and extremely small loads may fail to converge.
37981
2001
Entry Should be a FATAL
Nonlinear Analysis - UWM 5426 for DEFORM
Using a DEFORM entry in the case control for SOL 106 (nonlinear statics) will
produce:
*** USER WARNING MESSAGE 5426, DEFORM BULK DATA CARDS REFERENCED BY DEFORM CASE
CONTROL COMMAND ARE NOT DEFINED.
THE REQUEST FOR STRESSES AND/OR FORCES IS IGNORED.
This will cause data recovery for stresses and/or forces to be ignored. It
will also lead to misleading results, because the DEFORM entry is not
applicable to Sol 106.
Recommendations:
1) change Warning 5426 to Fatal for sol 106

2) Add the following remark to Deform Bulk data section:
4. The deform entry, when called by the deform case control command, is
applicable to linear static, inertia relief, differential stiffness, and
buckling (Solutions 101,105,114, and 200) and will produce fatal messages in
other solution
37990
FM 4549
Nonlinear Analysis - Beam with Warping Failed to Converge - S
A nonlinear analysis of a BEAM with the warping degree of freedom specified may
results in failed convergence or SFM 4549 followed by a traceback:
SYSTEM FATAL
MESSAGE 4549,
SINGULAR (C+KBRR) MATRIX ENCOUNTERED FOR BEAM ELEMENT
1001
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
Offset
38012
0x00003e28
0x000009d0
0x000022dc
0x0000017c
0x00001124
0x00000790
0x00000088
0x00000990
in
in
in
in
in
in
in
in
2001
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
nmepd_
nmatd_
nbem2d_
nembrd_
nlemg_
nliter_
xsem15_
mainal
Documentation/QRG - PARAM,FOLLOWK
The Quick Reference Guide incorrectly states that PARAM,FOLLOWK is available

only in solutions 103, 105, and 107. It is also available in solutions 108,
109, 111, and 112.
38013
DMAP - PARTN - TYPE is Ignored
Specification of TYPE is ignored in the PARTN module. This may cause a problem
in user dmaps. The avoidance is dependent on the intent of the DMAP.
38016
2004
sing THRU range entry
Superelements - SESET failures in SEP1X u
It has been observed that the SESET entry may cause failures when a THRU range
is specified where the low GRID ID is less than the starting GRID ID of the
model.
Avoidance: An avoidance is to make the starting grid equal to the low the low
grid identification.
38021
70.7.2
Documentation/COG - Fujitsu, XDB, TRANS
The V70.7 Configuration and Operations Guide states that the Fujitsu VPP,Vx
UXP/V systems require that the XDB file be translated. This information is
incorrect. The correct line would be similar to that of HP HP-UX right
underneath the Fujitsu line.
38023
2001
ncluded on PBEAML entry
Documentation/QRG - PBEAML - NSM(B) not i
The Quick Reference Guide incorrectly omits the field for the NSM
(non-structural mass) on end B of the PBEAML entry. The last field on this
entry is the NSM for end B.
38031
DB
Nonlinear Transient Thermal Analysis - Missing Results from X
A multiple subcase transient thermal analysis will be missing temperature

results in the OP2 and/or XDB files for the 2nd and subsequent subcases.
Avoidance: A DMAP avoidance is under investigation.
38041
70.7.2
GRAV, Multiple Subcases - UFM 5423
Optimization/Design Sensitivity - DESGLB,
In an optimization run, if the DESGLB global constraint is used, and there are
two or more static subcases with gravity loads, then the job may fail with the
following error messages:
COLS ROWS FORM TYPE
NZWD DENS
1830
TRAILER FOR EGM
IS
2 80532
TRAILER FOR EGKL
IS
1 80532
114
10976 681
0FATAL ERROR
Avoidance: Use the DESSUB constraint callout instead.
38046
2001
ct Format Field
Miscellaneous - OUTPUT2, TABPRT - Incorre
Output datablocks (OFP tables) contain information in the header record which
describes the information contained in the datablock. Word 9 is used to
indicate if the information is (1) REAL, (2) REAL/IMAGINARY, or (3)
MAGNITUDE/PHASE. If the data is REAL/IMAGINARY, this flag is incorrectly set to
1.
38055
70.7.2
Parallel Processing - DMP - Incorrect SPC
forces for constrained & loaded points
In a distributed memory parallel execution, dmp>1, SPCforces are incorrect for
constrained and loaded interior DOFs.
compile disph1b
alter 'pss'
call dbstore pss,,,,//0/0/'
'/0 $
compile sedisp
alter 'kfs,uox,pss'(,-1)
call dbfetch /pss,,,,/0/0/0/0/0 $
endalter
38056
2001
Beam Library - PBARL -
ILLEGAL INPUT
TO SUBROUTINE DOMPFTN
When the generalized PBARL is designed using the beam library server, the job
fails in DOPR1 with the following message:
"ILLEGAL INPUT TO SUBROUTINE DOMPFTN".
This message is caused by designing the sixth property (FE) in the EPT table
which is currently not used.
Avoidance: In the bsbrid subroutine, change the
Do 110 i = 1,nprop
do 100 j = 1,ndim
sentyp(i,j)=3
100 continue
110 continue
to
Do 110 i = 1,nprop
if ( iprop .eq. 6 ) go to 110
do 100 j = 1,ndim
sentyp(i,j)=3
100 continue
110 continue
38061
M 3003 (EMG)
2001
SSSALTERS - cygyroa.vxx, TEMP(LOAD) - SF
The following message will occur in with the SSSALTER CYGYROA if thermal loads
are used.
SYSTEM FATAL MESSAGE 3003 (EMG)
(FILE 107) IN SUBROUTINE EMGTAB
The error occurs when the differential stiffness matrix is being generated, and
hence the actual output (e.g. displacements, stresses) is correct. However,
since differential stiffness is not generated, restarts off this database will
not include the desired gyroscopic effects. The error occurs because of the
unique way thermal loads are called out in Cyclic solution sequences. The
TEMP(LOAD) case control command points to a bulk data LOADCYN entry which
inturn points to a temperature set. The EMG module issues the fatal error
because it is searching for
38062
2001
modes, tempi - UFM 4342, SFM 3001
Cyclic Symmetry - differential stiffness,
In a cyclic symmetry run that uses the differential stiffness (e.g., buckling
and normal modes with preload), the applied loads must be uniform. To enforce
this requirement, the loads must be applied to segment one only. If loads are
applied to segments other than one, then the job will fail with following error
messages:
*** USER FATAL MESSAGE 4342 (CY1BLD)
ANALYSIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE.
LOADCYN
xxxx
yyy
zzz
To avoid this message, remove loads from segments greater than one.
Furthermore, if the preload consists of thermal loads, then the job will fail
*** SYSTEM FATAL MESSAGE 3001 (CYCLIC4)
THE INPUT
38070
70.7.2
message at completion of job
Parallel Processing - DMP - System error
DMP jobs may report the following error text at job completion:
ERROR 0031-636 User requested child or EOF termination of pm_command
This message does not affect the MSC.Nastran job.
Avoidance: Delete the following line from <install-dir>/bin/nast707.dmp:
%MSC_ARCH=aix:%export MP_NEWJOB=yes
38073
2005.0.2
ficient Restart
Cyclic Symmetry - RESTART, STATSUB - Inef
If a restart from SOL 114 (Cyclic static) into SOL 115 (Cyclic modes) is
performed to calculate pre-stressed modes of the model, the static solution
will be re-calculated in SOL 115.
38096
2008.0.0 (MD R3)
type and CPU time are not written
Miscellaneous - Accounting file, Solution
The Version 70.7 accounting program does not properly identify the solution
name, CPU, or elapsed times in the account files.
Avoidance: Use the following procedure to modify and install a new accounting
logging program.
1) Change the current working directory to <install-dir>/msc707/util
2) Change lines 1440 through 1443 in mscact.c from
if( (f04 = fopen( f04f, "r" )) == NULL ) {
(void) strcat( f04f, ".f04" );
f04 = fopen( f04f, "r" );
}
to
(void) strcat( f04f, ".f04" );
f04 = fopen( f04f, "r" );
That is, delete the "if" statement and its matching closing brace.
3) Build a new version of mscact with the command
msc707 util mscact
4) Install the new account logger program with the command
cp -p mscact ../<
38097
is wrong.
70.7
Installation - FLEXlm - /etc/inittab file
mscsetup for MSC.Nastran Version 70.7 does not set the /etc/inittab line with
the full path of the flexlm utility. If the system is subsequently rebooted
FLEXlm will not run automatically.
Avoidance: If FLEXlm is already installed, and you want the new version of
FLEXlm, install it but do not have mscsetup set the /etc/inittab file; if
FLEXlm is being installed for the first time, modify the /etc/inittab file
after the installation is complete and add the full path for the
<install-dir>/bin/flexlm utility.
38100
70.7
Installation - No Output
When installing MSC.Nastran on Intel computers, the last step in the

installation asks if you would like to enter the authorization code. If you
choose not to enter the code, the program does not create the authorize.dat
file, but the nastxxx.rcf file will incorrectly point to the non-existant file.
If you submit a Nastran job, no output files will be created.
Avoidance:
Either:
1) enter the authorization code when installing.
2) edit the nastxxx.rcf file to remove the "AUTH=" line
3) when you try to run MSC.Nastran, enter the following on either the command
line or in the "optional keywords" box
pause=yes
If you do this, the command window trying to run the program will stay open and
you will obtain the error message indicating that the authorize.dat file does
not
38115
a[smprt.o]
70.7
Installation - Missing library libxlsmp.
IBM AIX clients that don't have the Fortran compiler installed will be unable
to run MSC.Nastran V70.7.0 and V70.7.2 until the libxlsmp.a library is
installed on their system or in the <install-dir>/msc707/aix directory. The
following message is issued in the log file:
MSC/NASTRAN started Mon Jan 03 09:46:03 EST 2000
Could not load program /tmp/vxlq/n707/msc707/aix/analysis
Could not load library libxlsmp.a[smprt.o]
Error was: No such file or directory
Avoidance: Install the missing library.
38116
Superelements - CSUPER, PARAM,INREL - SFM 5423 (DMPYAD)
If SOL 101 with inertia relief is used with external superelements, the
external superelement data recovery run will fail with:
indicating that UOO and CRX are not correct. This is due to an error which
results in CRX not being written to the EXTDRUNT.

Avoidance: Include the following DMAP alter in the residual structure run:
compile super3
alter 339
dbview crx0=crx (where seid=0 and wildcard) $
equivx crx0/ol1m/-1 $
38119
Missing Output
2001
Postprocessing - SOL 105, PARAM,POST,0 -
Under PARAM,POST,0 in SOL 105, the buckling eigenvalues and eigenvectors will
not be available in MSC.Patran.
Avoidance: Use PARAM,POST,-1 or insert the following DMAP alter:
compile super3
alter 'CASEdr,ol2s'(,-1)
app=app1 $
alter 'CASEdr,ol2s'
app='reig'
endalter
Verified , see attachs for files. Chanhed 'reported by to ABBEY as LIBBY no
longer with MSC
38123
2001
DRESP2 - Wrong Answers
Optimization/Design Sensitivity - DEQATN,
If multiple DRESP2's refer to the same DEQATN, only the first (lowest numbered
DRESP2 is checked to see if the number of DRESP2 arguments agrees with the
number DEQATN arguments. If a subsequent DRESP2 has a mismatch with the number
of arguments, the error goes undetected and unpredictable answers are produced.
Avoidance: There is no avoidance other than not sharing a DEQATN id on multiple
DRESP2's. If this is too tedious, the user must be vigilant in checking that
the number of arguments on the DRESP2 agree with the number of arguments on the
left hand side of the DEQATN in every DRESP2 except the lowest numbered one.
38127
2001
DSAPRT - Incorrect Sensitivity Data
When the formatted prints of sensitivity data (case control command DSAPRT) for
DRESP2 responses list a frequency value of the response, the value has been
incorrectly scaled upward by a factor of ten. A similar error exists for time
values. Also, values that are greater than 100. appear as *******.
Avoidance: Frequency/time values for DRESP1 responses are printed correctly.
The user must be aware that printed DRESP2 frequency/time values are 10 times
greater than they should be. It should also be noted that when a DRESP2
response spans several frequency, only the lowest frequency is printed.
38137
ter9ga.vxx
R2001
SSSALTERs - errors in alter1ga.vxx and al
SSSALTERs alter1ga.vxx an dalter9ga.vxx have errors in them when using OTM

(Output Transformation Matrices) with OUTPUT2 or in frequency response.
alter1ga.vxx does not correctly write the tables identifying the terms in the
OTM if OUTPUT2 is used. alter9ga.vxx does not correctly use the OTM if it is
used in frequency response.
Avoidance: Contact MSC and request an updated version of the alters or get
them from the MSC web page at:
http://www.mechsolutions.com/support/prod_support/nastran/sssalters/index.html
38141
70.7
rrect Year Printout
Miscellaneous - OUTPUT2, Year 2000 - Inco
When running nastran jobs in year 2000+, on some unix machines, the output2
trailer information will print out the date incorrectly. For example, when
using param,post,,-1, the trailer information for OEF1 coming out right after
UIM 4114 with a job ran on January 6, 2000 will appear as follows:
1001
63
6 100
instead of the correct value

1001
63
In this case field 5 is the year. This problem is fixed in Version 70.7
Avoidance: There is no avoidance. Note that the results are not affected by
the date printout.
38143
ormulation
2001
Documentation - SYSTEM(173) - Old QUAD4 F
SYSTEM(173) allows the selection of either the pre-V68 QUAD4 formulation or the
V68-V70.5 formulation. This system cell is incorrectly documented in the
Version 70.7 Release Guide. The documentation should state:
1: Requests pre V68 QUAD4 Formulation
2: Requests V68-V70.5 QUAD4 Formulation
Likewise the Version 70.7 Release Guide documentation for the keyword OLDQ4K
incorrectly states that this keyword is equivalent to setting SYSTEM(173)=2,
the keyword is equivalent to setting SYSTEM(173)=1.
38167
rsions
Installation - nastran command: fails with multiple 70.7.X ve
If V70.7.2 of MSC.Nastran is installed in the same directory as V70.7.0, then

both cannot run. The intent was to allow users to use "nast7070" for V70.7.0
and "nast707" or "nast7072" for V70.7.2. This feature was broken in the
V70.7.x releases.
Avoidances:
1. Install V70.7.2 in a directory with a different MSC_BASE than V70.7.0
2. Use V70.7.2 and not V70.7.0
Details:
Nastran can not have seperate versions installed in directories like:
/msc/md200700/linux
/msc/md200701/linux
/msc/md200702/linux
Rather, the whole tree needs to be under the version. Ie:
/msc/md200700/msc2007/linux
The /msc/bin/nast* files will need to have links made to
/msc/VERSION/msc2007/bin/nast2007
38168
2004
or different SEs w/ PARAM OUNIT2
Superelements - Incorrect OUTPUT2 units f
If PART superelments are used, and different values are provided for
PARAM,OUNIT2 in different PARTs, the program will use these values incorrectly.
1) Setting distinct PARAM, OUNIT2 values in each of the Partitioned Bulk Data
Sections is ignored - only the setting for the residual structure is used and
the OUNIT2 values set under the BEGIN SUPER=xxx are ignored.
2) Setting distinct PARAM, OUNIT2 values PER SUBCASE using expanded Case
Control causes:
A)
B)
C)
D)
All geometry for all SE to be written to the 1st OUNIT2 specified

End of Data record on that 1st OUNIT2
Results for the residual are then written to that 1st OUNIT2 file
The 1st OUNIT2 file is rewound and re-labeled (wiping out the geometry
and SE0 results) and the correct SE results are written.
E) L
38180
2001
id-structure decks - Wrong answers
Frequency Response - DMP>1, SOL 108, flu
If distributed memory parallel, dmp>1, is used with a fluid-structure in SOL

108, then wrong answers result.
compile freqrs
alter '197',''
if ( acsyml and adjflg<2 and
not(GETSYS(np,265)>1 and GETSYS(np,197)>0 and
soltyp='modal') ) then $
endalter
38195
ring
2001
Plotting - .plt File Contains Bad Date St
The plot file will contain an invalid date string on any file generated after
Dec 31, 1999. The error is present in all versions of MSC.Nastran, up to and
including V70.7.2. On Version 70.7 the year 2000 was written simple as "0",
for example 1-10-0; however other strings are possible.
This error does not cause any other problems with the plot data.
38207
2001
Design Sensitivity/Optimization - Static
Aero, METHOD - UFM 1126 for M1RR

If the Case Control for a multi-subcase static aeroelastic solution in SOL
200 contains a METHOD command that varies from subcase to subcase, a FATAL
error can occur in which the M1RR matrix is recomputed. Since the M1RR matrix
is not declared OVRWRT, this causes UFM 1126 shown below. The error occurs when
the METHOD command is the ONLY boundary difference between the two sets of
subcases.
DMAP MODULE MPYAD
201 NAME =
M1RR
USER ACTION: DELETE THE DATABLOCK, OR USE FILE M1RR=OVRWRT
0FATAL ERROR
Avoidance: Since static aero analysis in SOL 200 is not affected by METHOD
selection, remove the extraneous METHOD selection(s) from the Case Control or
insert the follo
38221
2001
ress Output for Plate Elements
Documentation - PSHELL, MAT2 - Missing St
When a plate element references a MAT2 entry with an MID larger than 99999999,
it is assumed that this MAT2 entry has automatically been created from a PCOMP
entry (see QRG, MAT2 entry, Remark 13). Thus, stress output will be missing
unless PARAM, NOCOMPS, -1 is specified.
Avoidance: Do not use MIDs of MAT2 entries larger than 99999999, or use PARAM,
NOCOMPS, -1.
38237
2001
s=no - Clarify Documentation for DMP
Documentation - slaveout=yes, mergeresult
Distributed Memory Parallel executions may specify the keywords slaveout and
mergeresults on the submittal line. These keywords are documented in the V70.7
Release Guide. The Release Guide should have clarified and emphasized that the
non-default values of these keywords, slaveout=yes and mergeresults=no are
typically only used for debug purposes. The following should also be noted:
1. If mergeresults=no is specified in a static run the results of the
individual domains will not be sent back to the master and the system solution
will not be obtained.
2. The keyword mergeresults has no affect on a solution 103 or 111 run.
3. In solution 108, if mergeresults=no is specified and slaveout=yes is not
specified, then the results of the slave processors will be lost.
4. In solution
38238
essage
2001
Cyclic Symmetry - SFM 3001 (READ), Poor M
In SOL 115, if the stiffness and mass matrix have common null-columns the
following message will be issued:
13 DOES NOT EXIST.
Avoidance: Make sure degrees of freedom with no stiffness and no mass are
constrained. In Version 70.7 parameter AUTOSPC will do this, but in Version
70.5 AUTOSPC would not correctly constrain grids on CYJOIN entries. A better
error message is implemented in Version 2001..
38254
2001
UFM 5626 (DSAD17)
Optimization/Design Sensitivity - PBAR -
Optimization analysis does not support item codes 18 and 19 for PBAR for
complex stress. If specified the following fatal message is issued:
*** USER FATAL MESSAGE 5626 (DSAD17)
ITEM CODE 18 REFERENCED ON DRESP1 ENTRY
16 WITH RTYPE = FRSTRE
IS INVALID FOR ELEMENT TYPE BAR
34.
USER ACTION: CHECK THE SPECIFIED ITEM CODE WITH THOSE LISTED IN
APPENDIX A OF THE MSC/NASTRAN QUICK REFERENCE GUIDE.
38257
31
2001
DMAP - FBS - Wrong Answers, BIOMSG: ERROR
The FBS module may return poor fatal diagnostics (BIOMSG: ERROR 31) or wrong
answers when a left hand fbs is requested incorrectly. An example of a left
hand fbs follows.
The conventional (right hand) equation solved by the FBS module is:
Given the square matrix A, and a collection of vectors X, find B, where
A*X< = B $ FBS module
A is first decomposed into its factors L and U. $ DECOMP OR DCMP modules.
Typically, X and B have many fewer columns than A.
There are applications where X has many more rows than A. That type of problem
is most naturally posed as
X*A<= B
The unknown vectors X have been moved to the left hand side, hence the name LH
FBS. One method to solve this problem is to transpose it. Assume, for the
sake of simplification, that A is symmetric
38263
2001.0.1
ry - Missing Output
Superelements - Multi-Master, Data Recove
In a dynamic response analysis using the mulit-master technique, no output

will be generated for the superelements. This error only occurs in Version
70.5, 70.6, and 70.7.
compile super3
alter 'equivx cases \/casedr1',''
equivx casedr/casedr1/-1 $
endalter
38268
acy
70.7.3
Transient Response - TRLG - Loss of Accur
Transient loads are computed in single precision in module TRLG. One effect
that has been observed is the accumulated time after many delta-T steps is in
error due to numeric underflow. This round-off error typically only occurs if
the duration, T is greater than 100000 times delta-T. Loads such as COS(W*T)
may appear to have a slight frequency shift.
This problem is more likely to occur on 32-bit computers than on 64-bit
computers.
38276
ctly Described
2001
Documentation/QRG - XYPLOT - XMIN Incorre
In the Quick Reference Guide, remark 2 on the XMIN (XYPLOT) command incorrectly
states that if XMIN is not specified, it is set to the lowest value of "Y".
This should state that it is set to the lowest value of "X".
38282
Elements - TETRA, SYSTEM(213), DISTORT - UFM 4659, 5271
Using NASTRAN system 213=1 to override the element distortion fatal message,
USER FATAL MESSAGE 4659, for TETRA elements does not work.
Avoidance: Set a high value for the maximum acceptable aspect ratio on
system(191).
38283
2001
rayservices not available
Parallel Processing - DMP - SGI Only, ar
When running distributed parallel (DMP) on the SGI, the job may fail with the
following error messages in the log file:
'MPI: asgetnetinfo_array('(null)') failed : array services not available
S L A V E 1
Avoidance: Change the authentication method in the /usr/lib/array/arrayd.auth
from
AUTHENTICATION NOREMOTE
to
AUTHENTICATION NONE
and make sure you start the array services with '/usr/etc/arrayd start' as
root. Furthermore, make sure that the user account can do a 'rsh shu01irx
date' on the shu01irx machine without running into a 'permission denied'
problem.
38293
2001
INE, AMP- SFM 4276 EC 1044 QOPEN
Aeroelastic Analysis - Superelements, SPL
In Version 70.7, a flutter analysis (SOL 145) with superelements may fail with
SFM 4276, EC 1044 (QOPEN) in the AMP module if the superelement reduction is
applied using separate subcases AND the separate subcases do not include the
FMETHOD bulk data entry .The problem occurs because the splining to upstream
superelements, combined with work in Version 70.6 to support multiple
aerodynamic symmetries has coupled the spline matrix data to both the
aerodynamic configuration (AECONFIG) and to the superelement/boundary condition
qualifier paths. To ensure that the correct linkage among configurations and
boundary conditions is performed, the Case Control is examined for aerodynamic
cases to determine the AECONFIG name of each subcase. In the case of
superelement reduction subcases, these fict
38295
2001
Wrong answers or fatal
Superelements - RESTART, SEBULK, CSUPER -
If external superelements are used in a solution, then a change is made to the

external superelement (new matrices generated) for use in a RESTART run, the
updated matrices will not be used.
Avoidance: If you are using external superelements created using
PARAM,EXTOUT,DMIGOP2, the following alter (for V70.5) will provide support for
restart changes to the matrices:
compile extin, list
alter 'FORTIO.*EXISTS.*EXTUNIT.*IOSTAT '
if(iostat=0)then $
dbdelete datablk=(extdb), where(xname=*) $
endif $
38304
ing Output
70.7
Frequency Response - STRAIN(SORT2) - Miss
If STRAIN(SORT2) output is requested in a frequency response run and there are

no other output requests, there will be no strain output produced.
Avoidance: Add any other (SORT2) output request - for example
DISP(SORT2,PLOT)=ALL - to the case control.
38306
able Answers
2001
Dynamic Analyis - DAREA, LSEQ - Unpredict
Non-unique Set-ID/DAREA-ID pairs in LSEQ data lead to unpredictable results.

This is because the user cannot be sure as to which of the static loads
specified as part of the non-unique data are actually applied and which ones
are ignored. Accordingly, this scenario must be regarded as a fatal error.
The user can avoid this situation by using and referencing the combination LOAD
bulk data instead of non-unique Set-ID/DAREA-ID pairs.
38308
UFM 6285
2005
Heat Transfer Analysis - CHBDYE, QUAD4 -
If a heat transfer analysis attempts to calculate view factor from the edge of
plate elements using CHBDYE with sides from 2 to 5, then you will get UFM 6285
Avoidance: Define the line segment with CHBDYP, LINE boundary elements.
38317
2001
record number outside range
ACCESS - Utilites error forttl:severe(25)
After a successful build, the following error may occur during execution of
any of the sample ACCESS utilities.. The error may occur for both v70.5 and
v70.7.
"forttl:severe (25) record number outside range, unit 40, file
c:\filename.xdb"
Avoidance: Download new dbio object libraries, libdbio_vc.lib and
libdbio_irc.lib, from MSC's ftp site.
38323
2001
Utilities - BUILDSSS - UFM 701 PRCMPL
In Version 70.7, when using the buildsss utility to create a new delivery
database with more than one added user dmap, the following error occurs:
*** USER FATAL MESSAGE 701 (PRCMPL)

THE NUMBER OF SUBDMAPS BEING COMPILED EXCEEDS THE MAXIMUM ALLOWED NUMBER
OF 200 FOR THIS VERSION
Avoidance: Compile the additional dmaps in a separate run and add them to the
delivery. Contact MSC Support for details on how to perform this.
38337
2001
may cause failure of nastran command
Submittal - Large physical memory (>8GB)
Machines with physical memory in excess of 8GB may cause the nastran command to
fail with a message similar to:
MSC/NASTRAN V70.7 (SUN SPARC SunOS 5.7) Wed Jan 26 14:23:19 2000
*** SYSTEM INFORMATION MESSAGE (pgm: nast707, fn: validate_buffsize_memory)
Assuming "memory=-2147483648" as specified by
"memorymaximum=0.8*physical".
In some instances, an error will not occur, instead the nastran command may
generate an incorrect memory request.
Avoidance: Set the maximum memory size in a system RC file to the value listed
in the "MSC.Nastran V70.7 Configuration and Operations Guide", Table 4-2, pg
90. For example, on Solaris:
memorymaximum=4GB
38349
2001
3001 VECRMA (70.7)
P-Elements - UFM 9050 DCMP (70.5) or UFM
It is possible that in a model containing both p- and h-elements that the run
may fail with either UFM 9050 or UFM 3001.
Avoidance: This problem is under investigation. The model demonstrating this
problem executed successfully when more memory was allocated or the BUFFSIZE
was increased.
38365
2001
Elements - PARAM,SNORM - Wrong Answers
The maximum allowed value of the SNORM parameter is 45 degrees. Higer values
are automatically set lower. For shells meeting at a large angle, such as a
right angle, with a
different number of elements on each side, the calculated normal may be greater
than 45 degrees from one side. This is legitimate, but will fail the error
check.
38373
2001
- RBEi, MPC - UFM 5289
Rigid Elements and Multipoint Constraint
If a dof is listed as depednt more than once on an MPC or RBEi entry, Nastran
will issue UFM 5289, indicating an error. Unfortunately, the message may point
to the wrong dof and may not point to the entry which has the error.
Avoidance: There is no avoidance other than inspecting the MPC and rigid
element entries.
38376
2001
AM,POST,0 - Missing output in xdb
Static Analysis - DMP>1, GPSTRESS and PAR
If grid point stresses are requested with dmp>1 and param,post,0 then the xdb
file will be missing the grid point stresses for the slave domains.
compile sedrcvr
alter 'GPLS,EGPSTR'(2),''
DBC
OPG1,OUGV1,OEF1X,OES1X,OQG1,GPL,EGPSTR,EGPSF,GPDCT,
ELDCT,error1,,,,,,,,,//
'OPG'/'OUG'/'OEF'/'OES'/'OQG'/'GPL'/'GPS'/'SVF'/
'GPDCT'/'ELDCT'/'perror'//////////
-1/DBCPATH/S,N,CP/APP1/ICYCLIC/GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT/DESCYCLE/////adptindx/lusets $
endalter
38378
2001
Missing Fatal Message
DMAP - MATMOD option 12 - Wrong answers,
If the first input, I1, to the MATMOD module, under option 12, is purged then
the module will incorrectly report that NONULL=0 and the O1 output is purged
without warning or fatal even if the second and third inputs (I2 and I3) are
not purged and contain null columns. The documentation for MATMOD option 12
contained in the "DMAP Module and Data Blocks" guide states that only I2 and
I3 may be purged, which implies that a fatal message should be issued if I1 is
purged.
Avoidance: Rearrange the inputs so that the first input is not purged.
38381
2001
- UFM 6482 from DOPR3R
USER FATAL MESSAGE 6482 indicates that an invoked DRESP1 entry in a SOL 200
subcase is not compatible with the ANALYSIS type for that subcase. Although
the message points to a real user input error, it is possible that the
identified DRESP1 type is not the type that caused the error.
Avoidance: The UFM has the correct RID for the DRESP1. Use the RID and not the
response type to identify the incorrect input.
38396
2005.0.2
192, SFM 3062 in SEMA
Superelements - NASTRAN LOCBULK=2 - SFM 4
If the multi-master method is used on a Cray and LOCBULK is set to 2 and there
are GRID id's greater than 1000000 (one million) then the run may fail with SFM
4192, indicating undefined grid points.
GRID POINT
.... IN SUPERELEMENT
and
0*** SYSTEM FATAL
MESSAGE 3062 MODULE = SEMA
FAILURE OCCURRED IN UTILITY MAPBTI CALLED IN SUBROUTINE SEMA
Avioidance: There are several avoidances:
1. Insert the following DMAP alter in the residual structure run:
compile phase0
alter ',np,'
paraml bgpdt//'trai'/6/s,n,maxgid//s,n,nobgpdt $
if ( nobgpdt>-1 ) putsys(maxgid,186) $
endalter
2. Reduce all GRID id's to less than one million.
3.
Run using a different computer type, or run using LOCBULK=1
38398
2001
DRESP1 - SFM 4276
Optimization/Design Sensitivity - DSAPRT,
If the fomatted sensitivity option is used and there are no retained responses
associated with DRESP1 entries, but there are retained DRESP2 responses, SYSTEM
FATAL MESSAGE 4276 and a traceback in dsaprt is produced.
Avoidance: Use the unformatted sensitivity option or force the retention of a
DRESP1 response.
38401
2001
s may yield Wrong answers
Restarts - Superelements - Changes in SPC
If in a superelement restart run, changes are made to the constraints (spcs) of

only one superelment, then wrong answers may result.
compile phase0
alter 'IF ( LRESTART )'(2)'
IF (KCHNG) CALL CHNGFLG //KCHNG/SEDWN/SEID/PEID $
IF (MCHNG) CALL CHNGFLG //MCHNG/SEDWN/SEID/PEID $
IF (BCHNG) CALL CHNGFLG //BCHNG/SEDWN/SEID/PEID $
IF (PCHNG) CALL CHNGFLG //PCHNG/SEDWN/SEID/PEID $
IF (K4CHNG) CALL CHNGFLG //K4CHNG/SEDWN/SEID/PEID $
endalter
38403
work with Aero
Postprocessing/Aeroelastic Analysis - TRANS utility does not
The trans utility prorgram delivered with Version 70.6 and 70.7 will not
convert a solution 145 xdb file to a ndb file. If executed the utility yields
a message similar to the following:
TRANS - V70.7 (23-NOV-1998)
XDB FILE:
mlgo_flutter2_test.xdb
NEUTRAL FILE: mlgo_flutter2_test.ndb
MSC DATA BASE TRANSMIT PROGRAM - VERSION 70.7COMPILE DATE: 30-AUG-1999
due: [22] Invalid argument
logical unit 42, named 'fort.42'
lately: reading direct unformatted external IO
Abort (core dumped)
Avoidance: The only avoidance is to execute the run on an ieee compatible
system where the post-processing will be performed so that trans is not
necessary.
38411
2001
, APRCOD, DOM9 - SFM 4276, EC1404
If an input file for optimization has DVPREL2 entries and APRCOD is set to 3 on
the DOPTPRM entry, the run may fail and issue SYSTEM FATAL MESSAGE 4276 ERROR
CODE 1404 in the DOM9 module. .
Avoidance: 1) If the file contains DVPREL2 entries, do not set APRCOD to 3 or
2) If the deck contains DVPREL1 entries, force them to be retained
using a DSCREEN entry.
38412
GL
irectories" error
Submittal - "pwd: cannot access parent d
Under not-fully-understood circumstances a small subset of C shell users may

encounter the following error message:
$ /nast/deliv/msc707/unix/bin/msc707
/nast/deliv/msc707/unix/bin/msc707[42]: pwd: cannot access parent directories
/nast/deliv/msc707/unix/bin/msc707[97]: cd: bad argument count
when submitting a nastran job.
Avoidance: One avoidance is to use the Korn shell (ksh) as the login shell.
38428
Aeroelastic Analysis - PAERO4, AEFACT - UFM 6171 (APD4)
If a PAERO4 entry has fewer strips that requested, the program will issue USER
FATAL MESSAGE 6171 (APD4) and terminate. Unfortunately, the fatal message will
incorrectly state that the error is on an AEFACT entry with the same id as the
PAERO4.
Avoidance:
38443
ts
Provide the correct number of strips on the PAERO4 entry.

2001
Documentation - DEQATN - Unexpected Resul
The documentation for the DEQATN entry does not mention that the arithmetic is
carried out using the type of the input data. For example, if a term is raised
to a fractional power:
X=A**(1/2)
since both values in the exponent are integers, the value returned for the
exponent is calculated using integer arithmetic or 1/2=0.
Avoidance: Excersize caution when writing equations. If possible, avoid
integer terms.
38449
2001
APP-LOAD Output
GPFORCE - MPCFORCE, TEMP(LOAD) - Missing
If there are thermal loads and mpcforces, GPFORCE output may be missing the
applied load (APP-LOAD) output.
38455
2001
s Guide - Maximum Memory on HP-UX
Documentation - Configuration & Operation
Tables 4-2 and C-7 of the "Configuration and Operations Guide" incorrectly
state the maximum memory size on HP-UX systems is 2 GB. The maximum memory size
on HP-UX systems is:
1 GB (256 MW) on HP-UX 10.20
2 GB (512 MW) on HP-UX 11.00, PA-RISC 2.0
The actual value usable by the "memory" keyword is reduced from this by
approximately 35 MB.
38458
Answers
Nonlinear Analysis - QUAD4 - Plastic In-Plane Bending, Wrong
If a nonlinear analysis is performed with QUAD4 elements with elastic,

perfectly plastic material and the elements are loaded in pure shear and twise
(no bending, no axial load), then the results may incorrectly indicate that the
model can sustain increasing loads even after the elements in the critical load
path have reached the inplane shear plastic limit. This problem only occurs
for coarse meshes subjected to pure shear loads. It is not likely to affect
real world models.
38468
70.7.3
es - Infinite Runtime
Miscellaneous - GP4, Possibly Other Modul
Sort routines in nastran have an upper limit that may be exceeded if models
have many of one type of element. The deck that encountered this error had
several hundred thousand rigid elements.
Avoidance: There is no avoidance. The limit has been removed in MSC.Nastran
V2001.
38478
2001
L - Non-Existant Developer's Guide
Documentation/QRG - CONNECT, PBARL, PBEAM
The MSC/NASTRAN Quick Reference Guide documentation for the FMS CONNECT
statement, remarks :
5. Custom beam cross-section evaluator libraries developed by users shou
ld
comply with the MSC/NASTRAN Beam Cross-section Evaluator Developer's Gui
de.
There is no such document.
Avoidance: The remark should instead, refer to:
MSC/NASTRAN V69 Release Guide,
Section 3.1 Beam Cross-Section Library
Appendix C: Adding Your Own Beam Cross Section Library
38501
2001
, Superelements - UFM 1126 for FPHP
Optimization/Design Sensitivity - Flutter
USER FATAL MESSAGE 1126 occurs if a flutter analysis is attempted with

superelements in SOL 200 and complex eigenvector output is requested. See also
CSR 37130.
Avoidance: Remove the eigenvector request or make the following dmap changes:
compile fea
alter 1
type db fphp
endalter
38502
Optimiztion/Design Sensitivity - DEQATN - SFM 233 (PRSPOP)
In SOL 200, if the DEQATN bulk data entry uses certain keywords such as "OR" as
variable names in the equation argument list, an error message similar to the
following will occur:
*** SYSTEM FATAL MESSAGE 233 (PRSPOP)
UNDERFLOW OCCURRED DURING PROCESSING OF OPERAND STACK
DURING DEQATN EQUATION PROCESSING.
PROGRAMMER INFORMATION: STACK POINTER = 0 WITH MINIMUM = 1
*** COMPILATION DIAGNOSTIC INFORMATION ***
1. STATEMENT TYPE: DEQATN EQUATION
2. EQUATION ID NUMBER:
14
3. EQUATION:
TWALL(OR,IR)=OR-IR
*** SYSTEM FATAL MESSAGE 233 (PRSPOP)
The error message needs to be improved to add the following:
Possible cause: variable name is a keyword such as "OR".
Avoidance: Change the variable name
38519
2001
Documentation/QRG - PACABS - Units
The Quick Reference Guide description for the PACABS entry should state that
the units of the B, K, and M fields are per unit area.
38539
2001
P - Infinite CPU Loop
Distributed Memory Parallel - DMP, DISDCM
MSC.Nastran may get caught in an infinite cpu loop when distributed memory
parallel is used with inertia relief.
Avoidance: Do not use ineria relief with distributed memory parallel in V70.7.
38542
ficient Memory
2001
Miscellaneous - VECPLOT - SWM 3062, Insuf
Module VECPLOT does not check for insufficient memory. This may lead to the
following unclear message:
0*** SYSTEM WARNING MESSAGE 3062 MODULE = VECPLOT
FAILURE OCCURRED IN UTILITY GTXYZD CALLED IN SUBROUTINE DMTRXD .
DATA RETRIEVAL.
*** USER WARNING MESSAGE 3199 (VECPLOT)
NON-FATAL MESSAGES MAY HAVE BEEN LOST BY ATTEMPTING TO QUEUE MORE THAN
100 MESSAGES.
38547
2001
tice Groups yield Wrong Answers
Aeroelastic Anaysis - Multiple Double Lat
If a doublet lattice model (CAERO1 and/or CAERO2) is created in SOL 144 for use
in static aeroelasticity, and the model has more than one interference group,
the downwashes representing unit perturbations of the control devices (the DJX
matrix) are incorrect under most circumstances. The problem is caused due to
the erroneous introduction in Version 70.5 of an assumption that the coordinate
system ID and the CAEROi ID are in the same order. This is true for a single
interference group, but not for multiple groups. As a result, the wrong
coordinate system may be used in the computation of the downwash.
Avoidance: There is no avoidance other than to convert the model to have a
single interference group. Note, also, that unsteady aerodynamics (SOL 145 and
SOL 146) are NOT affected.
38555
nd 11.0
70.7.2
Installation - NFS Mounted - HP-UX 10.2 a
The original MSC.Nastran V70.7 (r1) CD may fail to install correctly on some
HP-UX 10.20 and 11.00 systems if the installation base directory is NFS mounted
from another system. The problem is due to incorrect information being
returned from the df(1) utility, this should be visible from the output of the
command
df -k <install-dir>
Avoidance: Choose one of the following avoidances:
1) Use the MSC.Nastran V70.7.2 (r2) release, that works around the HP-UX
utility error.
2) Install on the computer exporting the filesystem. If this is not an HP-UX
system, you can use the "Custom" installation to deselect the local computer's
binaries and select the HP-UX binaries.
38559
2001
RESP2 - SFM 3007
Optimization/Design Sensitivity - DSAD, D
An optimization job may fail in module DSAD with SFM 3007 when the following
conditions are met:
1. The DRESP2 entry only references the DNODE term,
2. The job has more than one subcases,
3. The DESGLB entry references the DRESP2 entry with DNODE terms.
The avoidance is to replace DESGLB with the DESSUB entry and place it in the
last subcase.
38564
70.7.2
e files (> 2 GB)
Documentation - Linux: how to enable larg
The "Configuration and Operations Guide" incorrectly states that large files
are available on Linux. They were not in the version of either the Linux
kernel (2.0.36) or libc (2.0) that MSC.Nastran was built with.
Note: The support required for this was not built into MSC.Nastran, so using a
system with support for large files will not help.
Large file support will be available in a new release of MSC.Nastran Version

70.7.2 on Linux that is to have a build date and release date of June 2000.
Avoidance: Use INIT and ASSIGN statements to specify multiple physical files
for any DBSet that exceeds 2GB.
38574
2001
- Poor Performance
Optimization/Design Sensitivity - DISPRS
It is possible, when performing modal frequency analysis in SOL 200, to recover

results to the g-set in the DISPRS subDMAP twice with each call performing
identical operations. For large problems, this can entail significant CPU
resources with no benefit.
Avoidance: The following dmap alter removes the redundant call:
compile fea
alter 'if ( psldf'(2)
if (delta) then $
alter 'if (psldf'(2,4)
endif $
endalter
38595
2001
- Wrong Answers in xdb
Composites - PCOMP, PARAM,S1 PARAM,POST,0
If stresses are to be sorted (PARAM,S1) and composite stresses are requested,

then the xdb file will contain incorrect composite stresses.
compile sedrcvr
alter 'DBC
OES1C',''
DBC
ES1C,,,,,,,,,,,,,,,,,,,//
'OESC'////////////////////
-1/DBCPATH/S,N,CP/APP1/ICYCLIC/GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT/DESCYCLE/////adptindx $
endalter
38608
2001
tains incorrect equation
Documentation/QRG - FLFACT - Remark 4 con
The formula of Remark 4 on the FLFACT bulk data entry of the Quick Reference
Guide V70.5 has two omissions and a typographical error.
It should read as follows:
F1 (FNF-FMID) (NF-i) + FNF (FNF-F1) (i-1)
Fi =
----------------------------------------------------------------------(FNF-FMD) (NF-i) + (FMID-F1) (i-1)
The above formual was taken from the Aeroelastic Supplement and was compared to
output generated by Version 70.5.
38610
2001
29 Documentation Incorrect
Documentation/QRG - EIGRL - System Cell 2
The documentation for SYSTEM cell 229 incorrectly indicates that if it is

given a value of 1, then the scratch database usage for Lanczos will be
decreased. This system cell applied only to the old Lanczos solver and will not
have an impact on the current Lanczos solver in MSC.Nastran Version 70.7 (The
old Lanczos solver is available by setting SYSTEM(273)=1).
38614
e poor answers
2001
Nonlinear Analysis - PARAM NMLOOP may giv
Nonlinear SOL 106 with PARAM NMLOOP may give poor answers. The eigenvalues,
displacements, and stresses for modes including prestresses and nonlinear
geometry may be based upon matrices that do not reflect a converged solution.
This error started in version 70.7 when a different version of the history file
was used to construct the required matrices. The use of NLPARM method ITER-1
gives fairly good results.
Avoidance: An avoidance ALTER is available from MSC to improve results. When
using HEXA elements in nonlinear, include NASTRAN SYSTEM(309)=1 , see CSR 38899.
38620
2001
Superelements - DMIG - UFM 327
DMIG matrices in part superelements result in the following fatal message

BAD DATA OR FORMAT OR NON-UNIQUE NAME. DMIG
also for DMI
The message above occurs when two part superelements adjacent in the processing
order have dmigs or dmis with the same name.
Avoidance: Add a second dmig or dmi matrix. It does not need to be used
anywhere, it is only necessary to have more than one dmig or dmi name.
38627
2004
Subcases - SPC, DEFORM - UFM 9058
In static analysis, if DEFORM and SPC entries are changed between subcases the
job will fail with the message:
USER FATAL MESSAGE 9058 (SUPER3) - THE SOLUTION FOR THE RESIDUAL STRUCTURE DOES
NOT EXIST
Avoidance: Execute the subcases as two separate runs.
38629
AD Output
Nonlinear Analysis - TEMP(LOAD), PARAM,LGDISP - Incorrect OLO
MSC.Nastran considers the fictitious forces for thermal expansion to be loads.

These are output by a case control command OLOAD. The output is for the
initial geometry, even when geometric nonlinear effects are requested. Since
only the OLOAD output is wrong, other items like displacements, element forces
and SPCFORCEs are not affected. Other load types (like PLOAD and FORCE1) are
correctly updated to the new geometry.
38632
2001
ng for prestressed structure
Acoustics Analysis - KJJZ of fluid is wro
An acoustic analysis of a prestressed structure yields an incorrect fluid part

of KJJZ. The values are off by a factor of 2.
Avoidance: Apply the following dmap alter to Version 70.5 or 70.7:
compile semg
alter 'add5','add5'
add5 kjjl,kjjnl,kdjjnl,,/kjjz $
endalter
38634
g Output
2001
SSSALTERs - trncompa.v707, SORT1 - Missin
If sort1 output is requested while using the trncompa sssalter, no ply output
will be obtained.
Avoidance: Only request sort2 output.
38645
70.7
Plotting - XYPLOT - Missing Data Points
An XYPLOT of grid points versus temperature results in a heat transfer analysis

results in missing data points.
38653
7(LOOKUP)
2001
Mass Matrix - SYSTEM(303), CUTOFF - UFM 1
The MSC.Nastran Version 70.7 Release Guide states that the name for SYSTEM(303)
is CUTOFF. If SYSTEM CUTOFF=1 is specified, the program will issue:
USER FATAL MESSAGE 17 (LOOKUP)
SYMBOL "CUTOFF" IS UNDEFINED
Avoidance: Use the system cell number rather than the name.
38654
2001
POST,0 - SWM 6065 (DBC)
Superelements/Nonlinear Analysis - PARAM,
If superelements are used in SOL 106 and PARAM,POST,0 is used, it is possible

that SWM 6065 may be issued, followed by SWM 6066, indicating that the DBC
module has been terminated. If this occurs, no additional information will be
written to the .xdb file for post-processing.
Avoidance: Insert the following DMAP alter into the file:
compile super3
$ remove ol2s from DBC list
alter 'dbc.*casedr.*ol2s.*casecc.*oltype',''
DBC
CASEDR,,,,,,,,,,,,,,,,,,,//
'CASECC'////////////////////
-1/DBCPATH/S,N,CP/APP/ICYCLIC/GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT/DESCYCLE/////ADPTINDX $
38676
70.7.2
pation Factor Output
Acoustic Analysis - Missing Panel Partici
Prior to Version 70.7.2 fluid/structure problems that have no s-set (no

constraints) will not allow panel participation factors to be printed with
PARAM,FLUIDMP or STRUCTMP.
Avoidance: Use AUTOSPC and an unattached GRID to force a degree of freedom in
the s-set.
38682
ong Answers
2001
Nonlinear Analysis - NMLOOP - Possible Wr
The use of NMLOOP yields incorrect prestressed modes in Version 70.7 if the
user does not enforce a stiffness update. The prestressed modes are correct
in Version 70.5 because the stiffness is updated automatically at the end of
the subcase.
Avoidance: There are three possible avoidances in V70.7, we recommend the first
option.
1.
Insert the following dmap alter:
ECHOOFF $ SWITCH ESTNL, REPLACE MODULE EMAKFR WITH SUBDMAP CENTRIP

COMPILE NLSTATIC $
VER 70.7 BY R.L.H. MARCH 29, 2000
ALTER 'NMLOOP.*CNMLOOP=2','' $
IF ( NEWP>-1 AND NMLOOP<>0 ) THEN
CNMLOOP=2 $
MESSAGE //' DELETE/COPY ESTNL $ CSR 38614'
DELETE /MESTNL,,,, $
COPY
ESTNLH/MESTNL $
ENDIF
COMPILE NLKR $
ALTER 'EMAKFR','' $
TYPE
DB,EQEXINS $
CAL
38684
2001
0e8(ts) incorrect.
Documentation - PSHELL - Remark 14, (ts)1
Remark 14 under the PSHELL description in the MSC/NASTRAN Verson 70 and 70.5
Quick Reference Guide description is incorrect.
It says:
14.
If MIDi is greater than or equal to (Ts)10^8(Ts), then parameter NOCOMPS

is set to +1 indicating that composite stress data recovery is desired.
(MIDi greater than (Ts)10^8(Ts) are generated by PCOMP entries.)
It should say:
14.
If MIDi is greater than or equal to 10^8, then parameter NOCOMPS

is set to +1 indicating that composite stress data recovery is desired.
(MIDi greater than 10^8 are generated by PCOMP entries.)
The v70.5 online encyclopedia has the correct remark as does pre v70.0 Quick
Reference Guides.
38722
2001
UFM 315, UFM 316
In Version 70.7 it is possible to output updated propertied in an optimization

run. If a model contains PCOMP entries and one or more of the PCOMP entries
has an odd number of layers, then any subsequent run using the updated PCOMP
entries generated from the previous puch file will fail with the following
error messages:
FORMAT ERROR ON BULK DATA ENTRY PCOMP

ILLEGAL DATA ON BULK DATA ENTRY PCOMP
Avoidance: Punch out the PCOMP entries using the small field format (e.g.,
param,despch1,x) where x can be -1, -2, -3, -5 -,6, or -7. The default
is param,despch1,6.
38740
2001
DMAP - DRHM3 corrupts OSE1 table
It has been observed that on Version 70.5 SGI systems that the OES1 table
produced bythe DRHM3 module is corrupted and can not be printed.
38743
2001
E, DSCREEN - UFM 315
Optimization/Design Sensitivity - SPCFORC
Specifying the response type (RTYPE) of SPCFORCE on the DSCREEN entry in SOL
200 will result in UFM 315 ILLEGAL DATA ON BULK DATA ENTRY DSCREEN. Note that
the SPCFORCE response type was first added in V70.7.
Avoidance: Create an equivalent DRESP2 for each DRESP1 of type SPCFORCE that
will be constrained. Then specify the response type (RTYPE) of EQUA on the
DSCREEN entry.
Verified in R. 32. -TIN38750
2001
Inefficient Processing
Aeroelastic Analysis - RESTARTS, MKAERO -
The dynamic aeroelastic restarts are dependent on the sorted order of the
MKAEROi (i=1 or 2) bulk data entries whenever multiple entries are present.
This creates the situation of regenerating the aerodynamic matrices when the
/,1,99999 method of deleting and reinputting the bulk data is used. The
MKAEROi entries on the restart MUST be in the same order as the coldstart run
otherwise SOL 145 or 146 will rerun AMG/DECOMP even though the MKAEROi entries
are identical to the coldstart but in a different sorted order.
Aviodance: To avoid this problem the restart should only delete the specific
bulkdata entries required NOT the entire bulkdata input.
38769
2001.0.3
Materials - CQUAD4, MAT8, G12 - UFM 4297
In Version 70.7, if the G12 field on the MAT8 entry is blank, then the job will
fail with the following misleading error messages:
*** USER FATAL MESSAGE 4297 (EQD4D)
QUAD4 ELEMENT WITH ID =
1
HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180 DEGREES.
1. Add the G12 field to the MAT8 entry if appropriate.
or
2. Set SYSTEM(173)=2
38780
2001
SSSALTERs - mmecha.v707 - possible errors
It has been observed that the mmecha alter may fail due to a singularity
problem. This problem is due to an incorrect maxratio test in the presence of

2x2 pivots. This type of pivot can be caused by the Lagrange Multiplier
Method.
Avoidance: The revised alter for Version 70.7 is available on the MSC.Software
website. If you have trouble getting the updated alter, contact your local
support representative.
38788
70.5
Missing Grid ID
Static Analysis - STRESS, CORNER, PUNCH -
When requesting punch output for element forces or stress at the corners ,
the punch file does not print the grid ID. It does not know wich fields are
integer and which fields are floating point
38815
s Error on SGI
2005
Distributed Memory Parallel - DMP - Sigbu
SGI distributed memory parallel jobs that request 8 or more processors may fail
with a "SIGBUS: Bus error" as follows:
Core from signal SIGBUS: Bus error
(dbx) where
> 0 _realloc(0x100193e8, 0x190, 0x19450152, 0x0, 0x110, 0x9436c5a, 0x94369bd,
0x94369d2)
["/xlv43/6.5.7m/work/irix/lib/libc/libc_n32_M4/gen/malloc.c":367,0xfb2a1fc]
1 parse_file(0x111, 0x1, 0x19450152, 0xfb51ef8, 0x110, 0x9436c5a,
0x45,0x94369d2)
["/home/poppy08/kak1/mpt/1.3/mpi/lib/libxmpi/libxmpi_n32_M3/all/all_parse.c":264
,0x9406214]
2 parse_global_opts(0x9425388, 0x1, 0x19450152, 0xfb51ef8, 0x110, 0x9436c5a,
Avoidance: The following changes need to be made to the nast707.dmp file:
From:
%MSC_ARCH=irix64:%
print -nu3 -- "${hosts[$i]} -np 1 ${rcmds[$i]} -c$i
-d%r.debug% jid=$jid $args"
To:
%M
38839
3001 (READ)
2001
Superelements - SEBULK, Collectors - SWM
If component modes are requested on a collector superelement then the run will
fail with SWM 3001 in READ.
compile phase0
alter 'call ifps1'
if ( setype='colltr' ) equivx
endalter
38841
70.7
dynamic/dynamics/-1 $
Installation - Poor Error Message
If MSC.Nastran is NOT installed on a remote node properly, then the following

error may occur:
*** USER WARNING MESSAGE (pgm: nastran, fn: validate_dmp_hosts)
beowulf21(LAM n1): No response from MSC.Nastran remote query:

/scratch/msc/bin/nast707 -d0 -rN70.7 frs=/scratch/DMP/dmp_108.dat
drwx=/tmp fw=/scratch/DMP/dmp_108.T6084_15 drwx=/scratch/DMP
drwx=dmp_108 drwx=.
Segmentation fault (core dumped)
Avoidance: Install MSC.Nastran correctly on the remote node. If there is not
an authorization file, then the following error may occur:
*** USER FATAL MESSAGE (pgm: nastran, fn: validate_authorize)
authorize="???????"
(LM_LICENSE_FILE)
This file does not exist.
Avoidance: Install the an authorizatoin file.
38869
2004
APPEND 1st param cannot be 0
Documentation -- DMAP Module Dictionary -
Both the Version 68 DMAP Module Dictionary and the current Version 70.7 online
pdf documentation indicate that the 1st parameter for the APPEND module may be
either a "0" or a "1" in order to create an output datablock [IN1:IN2].
However, if "0" is used then "UFM 5005 INVALID VALUE OF OPTION PARAMETER
DETECTED 0" is issued, followed by "SFM 3007 MODULE = APPEND ILLEGAL INPUT TO
SUBROUTINE APPEND".
Avoidance: Set the 1st parameter to "1" instead of "0".
38889
2001
GPFORCE - TEMP(LOAD) - Wrong Answers
The applied load contribution of the GPFORCE output is incorrect in TEMP(LOAD)

is applied to only a portion of the model.
Avoidance: The only avoidance is to put a small thermal load on ever element.
.
38892
2001
2), DOPTPRM - Undocumented Feature
Optimization/Design Sensitivity - SYSTEM(
If the IPRINT parameter on the DOPTPRM entry is used to obtain intermediate

prints from the DOT optimizer, the output is always written to unit 6
regardless of which unit other "f06" output is directed to by NASTRAN
SYSTEM(2).
Avoidance: Undocumented paramter IWRITE can be used on the DOPTPRM entry to
direct the intermediate prints to the unit of the users choice. That is
IWRITE=4 places this output in the .f04 file.
38895
70.7.2
DMAP - PARAML - U1 Set not Recognized
Degree of freedom Set U1 is not recognized by DMAP modules dealing with degree
of freedom sets, e.g. PARAML, VEC, etc.
Avoidance: The only avoidance is not to use the U1 set.
38898
nce
70.7.3
Performance - SYSTEM(107) - Poor Performa
If Parallel processing is selected with SYSTEM(107) (a.k.a. keyword PARALLEL)

on MSC.Nastran Version 70.7 on the Cray J-90 executable cache memory will be
disabled and poor performance results.
Avoidance: Other than not selecting parallel there is no avoidance.
38899
Nonlinear Analysis - HEXA - Poor Convergence
Poor convergence may be experienced for Nonlinear jobs with HEXA elements in
MSC.Nastran Version 70.7. The problem occurs because the new HEXA formulation
introduced for linear analysis in Version 70.7 is used on the first iteration
and it shouldn't be.
Avoidance: Set SYSTEM(309)=1 to revert to the pre-Version 70.7 formulation for
all iterations.
38907
5411 (REIGL8)
2008.0.0 (MD R3)
Complex Eigenvalue Analysis - CEAD - UWM
The message below may appear many times when using the complex eigensolver
module CEAD.
*** USER WARNING MESSAGE 5411 (REIGL8)
NEGATIVE TERM ON DIAGONAL OF MASS(VIBRATION) OR STIFFNESS(BUCKLING)
MATRIX DETECTED.
ROW NUMBER =
80 VALUE = -1.20000D+02
Avoidance: This message may be safely ignored when encountered in the CEAD
module.
38925
2001
tact, PELAST - SFM 3001 in EMG
Nonlinear Static Analysis - slideline con
Job will fail in SOL 106 when line contact problem includes nonlinear springs
in the model. For example, any SLIDE-LINE model with PELAST and/or PBUSHT,
which refer to TABLEDi bulk data cards, will be terminated during contact
nonlinear stiffness generation in SOL 106.
Avoidance: Please insert the following DMAP alter into SOL 106 decks to avoid
this difficulty
COMPILE NLSTATIC $
ALTER 'CALL NLKR'(3),'' $
CALL NLKR MESTNL ,CSTMS
BGPECT ,BGPDTH
,
DEQATN ,DEQIND
/
BKELM ,BKDICT
,
S,NO
,
,USETNL
,USET1
,
,
,GMNL
,
,
,
,
,
,
,BKGG
,
,BKFS
,BKMG
,BKAA
/
38927
2001
UWM 4683 (READ) MASS MATRIX
,BTOPSTF
,SILS
,GPSNTS
,ETT
Elements - CTETRA, PSOLID - Poor Answers,
The mass matrices for mid-side-noded CTETRAs are not calculated correctly if
the defaults values for IN and ISOP fields on the PSOLID are not used. This
may lead to UWM 4683 from the READ module and poor answers.
Avoidance: Leave the IN and ISOP fields blank on the fluid PSOLIDs in order to
use the defaults.
38939
2001.0.1
on Windows 2000
Licensing - FlexLm - Problem with FlexLm
In some instances, the authorization process on NT and Windows 2000 may take
almost a minute to return with the authorization. If this is happening, add the
following line to your .rcf file
SYMBOL=LM_NO_SNMP=1
38949
and is ignored
2001
Submittal - hosts keyword on nast707 comm
If the hosts keyword is defined in any of the RC files, then you will be unable
to override it's value on the command line.
Avoidance: A work around is to put the keyword in a local RC file in the
directory where the input file resides. This value will override any values set
in the other RC files.
38951
2001
Submittal - Execution on remote node may
cause input and output to be deleted.
If a Nastran analysis is run on a remote system using the the node keyword, and
the output file directory is visable to the remote node, then all the output
files and the input files will be deleted after the job has run.
Avoidance: There are two avodiances.
1) Run the job in a directory that is not visable to the remote node
2) Make the following change near the end of the install_dir/bin/nast707.rmt
file.
127,128c127
< %s.rsh% %node% -l %username% /bin/rm -f "%r.out%*"
< %r.outvis=y:%/bin/rm -f "%r.out%*"
--> %r.outvis=n:%%s.rsh% %node% -l %username% /bin/rm -f "%r.out%*"
38955
oint Exception
2001
DMAP - PARAML - Overflow Exit, Floating P
When the PARAML module is used to extract an element from a matrix with the DMI
option, and the element is larger than the range allowed by single precision
parameters, a machine-dependent overflow error exit occurs. On NT MSC/NASTRAN,
the output from the f06 file is:
0THE NUMBER OF NON-ZERO TERMS IN THE DENSEST COLUMN =
1
0THE DENSITY OF THIS MATRIX IS 100.00 PERCENT.
MAIN: The FPU has been reset after floating point exception.
MAIN: For reference, A(MAINAL) = 405290, A(/SYSTEM/) = 1777f60
[similar data is presented in the .log file]
There is no mention in any of the diagnostic output that the PARAML module was
being executed when the overflow occurs. One diagnostic method is to
temporarily put a message statement in front of every suspected module ca
38960
pected Answers
2005.5
Documentation/QRG - PELAST, PBUSHT - Unex
If the initial slope of the nonlinear force-displacement relationship defined

on a PELAST or PBUSHT entry in a nonlinear solution does not match the
corresponding Ki value on the PELAS or PBUSH entry, then the results may be
unpredictable.
Avoidance: Make sure that the initial slope as defined on the TABLEDi entry
matches the corresponding Ki value on the PELAS or PBUSH entry.
39031
2004
MATMOD Option 5, Form 3
Example 3 under the DMAP Module Dictionary's description of MATMOD option 5

should be modified from
Transform KGGBASIC coordinate system 10.
MATMOD
TRNSP
SMPYAD
CSTM,SIL,,,,/TRANS10,/5//10 $
TRANS10/TRANST10T $
TRANS10,KGGBASIC,TRANS10T,,,/KGG10/3 $
to
Transform KGGBASIC to coordinate system 10.

MATMOD
TRNSP
SMPYAD
CSTM,SIL,,,,/TRANS10,/5//10 $
TRANS10/TRANST10T $
TRANST10T,KGGBASIC,TRANS10,,,/KGG10/3 $
39041
2001
OCOMPS -1 not supported on DRESP1
Optimization/Design Sensitivity - PARAM,N
PARAM NOCOMPS -1 is used to recover shell element stresses for an equivalent

homogeneous element. The use of this capability has been blocked in SOL 200 so
that if the user invokes the equivalent PSHELL on the DRESP1 entry to obtain
stress/strain responses of the element, the corresponding PSHELL will not be
found.
Avoidance:
39046
There is no avoidance. Version 2001 will remove this restriction.

File Management Section - DBDICT - Missing Dictionary
If the DBDICT FMS command is used in a run as follows, the dictionary will be
blank.
assign master='oldrun.MASTER'
DBDICT
endjob
Avoidance: Use a read-only restart similar to the following to list the
database dictionary.
assign run1='oldrun.MASTER'
restart, logical=run1
dbdict
sol 101
cend
begin bulk
enddata
39056
D)
2001.0.1
Grid Point Stress - GPSTRESS- 4276 (FREA
If GPSTRESS output is requested, then following error may occur.

SYSTEM FATAL MESSAGE 4276 (FREAD).
Avoidance: Ensure that case control requests for stress and force specify the
same type of output. If center and grid point output is specified for one, it
should also be specified for the other.
39067
2001
Poor Performance
Distributed Memory Parallel - DMP, READ -
Distributed Memory Parallel eigenvalue jobs may experience poor performance in

READ on Compaq Alpha clusters.
I can't find the data deck. But this csr has the same issue to vvpr 120092
which Joe Griffin had verified the performance of this job. So I consider it's
verified. -TIN39088
2005.1
Cyclic Modes - SFM 3001 (DCMP)
The following message may occur in a cyclic symmetry modal run (SOL 115) when
requesting a tridiagonal solution method such as AHOU or AGIV. The message is
output from the DCMP module if the USET and SIL tables are mismatched with the
input matrices.
*** SYSTEM FATAL MESSAGE 3001 (DCMP)
3 DOES NOT EXIST.
Avoidance: An avoidance is to use the Lanczos method which does not perform
this operation. Another avoidance is to use the DECOMP module instead:
Compile moders list noref $
Alter 'dcmp.*kww1'(,-1) $
If (cyclic) then $
Decomp kww1/lww1,, $
Else $
Alter 'dcmp.*kww1' $
Endif $
39098
AM,SETSTR1
2001
Documentation/QRG - PARAM,USETPRT and PAR
In Version 70.7 param,usetsel has been changed such that values greater than 0.
are not acceptable. If USETSEL is set greater than 0 the following message
occurs:
^^^ USER WARNING MESSAGE 9109 (SEKR0)
^^^ USETSEL IS GREATER THAN ZERO WHICH IS OBSOLETE. USETSEL WILL BE
TO -1 TO PRINT ALL SETS.
RESET
^^^ USER ACTION: SPECIFY PARAM,USETSEL,0 AND

THRU USETSTR4.
SET NAMES ON PARAM,USETSTR1
Avoidance: The syntax for the r USETSTRi paramerter is: PARAM,USETSTR1,M:R for
more info see the description under TABPRT in the Release Guide for Version
70.7.
39109
2004
U - Poor Answers
Eigenvalue Analysis - GIV, MGIV, HOU, MHO
When using methods GIV, HOU, or their variants, if there are repeated roots
their eigenvectors may not be orthogonal. A small test problem with 9 repeated
roots produced only three orthognal vectors.
Avoidance: An avoidance is to use the LAN method.
39125
2001
Elements - CRAC3D, MAT9 - UFM 3005
If a model has CRAC3D elements that reference MAT9 entries, then the job may
**** USER FATAL MESSAGE 3005 (SNGERR)
Attemp to operate on singular matrix AI in subroutine SD92ND.
39129
70.7
e non-integer exponent
DMAP - DIAGONAL - UFM 5250 DIAGNL Negativ
If the diagonal terms of a matrix are raised to a negative power using the
DIAGONAL command with the 'SQUARE' option, if there are negative off-diagonal
terms, the program will fail with:
UFM 5250 DIAGNL Negative non-integer exponent
Avoidance:
First extract the diagonal terms using a POWER of 1.0, then raise the resulting
matrix to the desired negative power.
39150
not Supported
2001
DSAPRT, TRIM, STABDER, - Formatted Output
The formatted sensitivity prints produced using the DSAPRT case control command
are not supported for aeroelastic responses (DRESP1 RTYPE = TRIM, STABDER or
FLUTTER
Avoidance: Use the unformatted sensitivity prints.
39168
DMAP - Access Violation Error
A dmap had a purged input data block of the form call xyz a,,c . . . It in
turn called another dmap, with the format call wyz b// $, where b is the purged
input. If an attempt was made to test for the presence of b with paraml or to
print it with matprn, an access violation occurs. If all inputs to a subdmap
are purged, an executive system error occurs.
Avoidance: An avoidance is to add another non-purged datablock to the calling
argument. This purged argument does not need to be used in the subdmap. Its
presence avoids the error that results when all inputs to the subdmap are
purged

39172
is discarded
2001
DMAP - paraml /dbname/'name' - Datablock
If the paraml option 'name' is used on a data block in the calling argument of
a subdmap, and the datablock used as input to paraml is an NDDL-scratch data
block that has previously been equivalenced, the data block is discarded at the
end of the subdmap.
39191
2001
WM 3001 UXAX Does not exist
Aeroelastic Analysis - SDR1 - UFM 4574, S
Aeroelastic analyses that result in no a-set elastic deformations for unit

perturbations of the controllers will result in the following error message:
*** USER FATAL MESSAGE 4574 (SDR1)
DATA RECOVERY STARTED BUT NO DISPLACEMENT VECTORS AVAILABLE
*** SYSTEM WARNING MESSAGE 3001 (SDR1)
THE INPUT DATA BLOCK NAMED UXAX
AT POSITION
3 DOES NOT EXIST.
The problem is that UXAX is purged because there are no elastic deformations.
This is a somewhat rare event, that can happen if you attempt to model a
"rigid" airplane. There are a number of ways in which a rigid airplane can be
better modelled. In particular, in the TRIM specification, you can set the AEQR
field to 0.0. That will result in a flexible vehicle with no elastic feedback
to modify the aero loads. This is t
39198
2001
DMAP - MATGPR - UWM 3059
If the 2nd parameter is unspecified on the MATGPR DMAP module, then UWM 3059
is issued. This warning can be safely ignored.
Avoidance: Specify the 2nd parameter.
39203
2001
Postprocessing Output
Nonlinear Analysis - PARAM,POST - Missing
PARAM,POST does not work correctly in the Case Control of a Version 70.7
Nonlinear run.
Avoidance: Insert the following DMAP alter;
COMPILE NLSTATIC
alter 'PVT
PVT,CASESX2',''
dbstatus casesx2//s,n,nocase2 $
if ( nocase2>0 ) PVT
PVT,CASESX2/ $
endalter
39208
Output
2004
Plotting - XYPLOT, XYTRAN - Missing Plot
If a non-existant grid point is requested by the XYPLOT command, the XYTRAN

module makes a premature exit. i.e. when a displacement plot command cannot
find the grid point, all of the acceleration and element stress/force plots
could be skipped.
39213
2001
Dynamic Anaysis - FRLG - Wrong Answers.
In MSC.Nastran it has been found that FRLG can produce incorrect loads when
insufficient memory is given.
Avoidance: If the answers are suspect, run the analysis at only the suspected
problem frequencies and see if the answers change. If the answers change
increase memory and rerun the job.
39215
2001
nts not Identified
Mass Matrix - UFM 4646, Grids and Compone
The indefinite mass matrix check may not correctly identify the grid point
and degree of freedom.
AN INDEFINITE MASS MATRIX DOF DETECTED AT GRID:
0 COMPONENT:
Avoidance: The run may be allowed to continue by setting system(303). MSC's

elastic elements do not produce an indefinite mass matrix. Massless mechanisms
may cause this error, dmig input, or improperly coded rigid elements.
39219
Complex Eigenvalue Analysis - EIGC - Missing Eigenvalues
In MSC.Nastran Version 70.7 the new Block Complex Lanczos Eigenvalue analysis
method automatically reverts to real operations when no damping matrix exists.
This may cause roots to be missed in acoustic/fluid problems.
Avoidance: Two possible avoidances are:
1. Introduce a false damping matrix by applying the following alter:
compile gma
alter 'acsyml\=',''
acsyml=(acsym='yes' and fs) $
endalter
2. Force the method to always use complex arithmetic by setting
system(108)=16384.
39224
UFM 7055
2001
Optimiztion/Design Sensitivity - PBEAM -
When an optimization task tries to design K1, K2 and other quantities specified
on the last two continuations of a PBEAM entry, then USER FATAL MESSAGE 7055
(DOPR1C/DOPR1Z) will be printed.
Avoidance: Do not design K1, K2 and others on the last two continuations of the
PBEAM entry.
39235
2001
Optimization/Design Sensitivity - UFM 300
1 (DSAL)
In a SOL 200 senstivity analysis with multiple frequency subcases, an error can
result if an initial subcase has no responses that require a direct (as opposed
to adjoint) sensitivity analysis and a subsequent subcase does.
Avoidance: A possible avoidance is to arrange the subcases so that any that the
initial subcase requires a direct analysis. Another avoidance is to force the
use of the direct senstivity calculation for all subcsases with PARAM AUTOADJ
NO.
39248
2001
, PBEAML, PBARL - UFM 7193
USER FATAL MESSAGE 7193 may be issued in error when there are both PBARL and
PBEAML entries being designed. The error does not occur when a single PBARL is
designed.
Avoidance: The only avoidance is to replace either the designed PBARL's or the
PBEAML's with PBAR's of PBEAM's and use the original dvprel1/dvprel2 techniques
to design these properties.
39269
2001
- SFM 4027 (WRITE), EC 3021
An optimization task may fail with the SYSTEM FATAL MESSAGE 4027 when the
following two conditions are met:
1) a DRESP1 response is referenced in the first subcase and
2) a DRESP2 response is retained in the second subcase where the DRESP2
response references to another DRESP2 entry.
Avoidance: Do not use a DRESP2 referencing a DRESP2.
39272
2001
- Wrong Answers
An optimization task may generate incorrect type 2 response values when the
nested referenced DRESP2 entries are used in multiple subcases.
39273
2001.0.1
Elements - HEXA, Corner Stresses, SDR2 -
In Version 70.7, if the HEXA element is highly distorted, then the corner
stresses may be incorrect. The element center stresses are correct.
1. Use the version 70.5 HEXA formulation by adding
to the top of the input file
2. Do not use the corner stress values.
39275
2001
FREQ3, 4, 5- SFM4276 (GREAD)
Optimization/Design Sensitivity - MODTRK,
In SOL 200, SYSTEM FATAL MESSAGE 4276 may be issued if mode tracking is
requested and there is a modal frequency subcase that uses the FREQ3, FREQ4,
or FREQ5 entries. in the specification of the excitation frequencies.
Avoidance: The use of FREQ3, 4 or 5 is not recommended with sensitivity and
optimization analysis since the excitation frequencies are not updated when the
structural model is changed. Further, the sensitivity calculations ignore the
effect of the change on the excitation frequency on the design response and are
therefore inaccurate, at best, and may cause the design to go in the wrong
direction.
39280
2001
er OUTPUT(POST) Missing Keywords
Documentation - QRG - SET description und
The SET description on page 244 of the V70.5 QRG for OUTPUT(POST) is the
missing keywords [ELEMENTS, GRID POINTS].
39285
IUNIT
Optimization/Design Sensitivity - PARAM EIGD, DSAPRT(EXPORT),
SUBDMAP EIGVECDS does not contain the parameter iunit. Thus, when the
DSAPRT(EXPORT) Case Control command is used, OUTPUT4 fails because IUNIT is
undefined.
INIT MASTER(S)
assign output4='a200.op4' unit=21 formatted delete
$
ID MSC, SWRO
TIME 100
DIAG 5,6,8,56
SOL 200
$need to rewind iunit before anything else
malter 'file.*append'
output4 //-1/iunit $
$ need to modify output2 from rewind to do nothing
malter 'output2.*dscmcol','output2.*dscmcol'
OUTPUT2 DSCMCOL,,,,//0/IUNIT/'DSCMCOL'/OMAXR $
compile eigvecds,nolist
alter 'nddl'
TYPE PARM,NDDL,I,Y,iunit
$need iunit id subdmap eigvecds
alter 'output4'
message // 'iunit='/iunit $
alter 'output4'(2,0),'output4'(2,0) $ remove rewind of iunit
$exit
39288
RRS)
2001
Elements - CTETRA, PSOLID - UFM 9050 (SEK
If a CTETRA with midside nodes references a PSOLID that has the IN field equal
to "TWO", the following error message occurs:
^^^ USER FATAL MESSAGE 9050 (SEKRRS)
^^^ RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX KLL.
^^^ USER ACTION: CONSTRAIN MECHANISMS WITH SPCI OR SUPORTI ENTRIES OR SPECIFY
PARAM,BAILOUT,-1 TO
CONTINUE THE RUN WITH MECHANISMS.

NASTRAN should give a warning message saying that IN = "TWO" is not allowed and
that the suggested IN = "THREE" is used instead, and the run should continue.
Avoidance: Use IN equal to "THREE".
39294
2001
DNODE - Incorrect Sensitivities
When an optimzation task includes a DRESP2 entry which also references a DNODE
and another DRESP2 entry, incorrect sensitivity coeffcients for the DRESP2
entry may be produced.
Avoidance: Do not reference both DNODE and DRESP2 on a DRESP2 entry.
39304
Postprocessing/Cyclic Symmetry Normal Modes - DBC, PARAM,POST
,0 - Incorrect Results in XDB
Cyclic Symmetry Modal Analysis produces incorrect XDB outputs. The results for
modes may be truncated.
39309
RV for CBEAMs
2001
P-elements - GP0 - GMLOAD applied to GMCU
For p-elements, if a GMLOAD is applied to a GMCURV in order to load CBEAMs, a

fatal error with no additional information occurs in GP0.
Avoidance: The avoidance is to apply the GMLOAD to the individual FEEDGEs for
the CBEAMs.
39314
Nonlinear Analysis - UIM 9005, Saved LOOPID is not correct
Even when an increment in nonlinear statics (SOL 106) cannot converge, it

still prints the following message, where "n" is the loopid of the unconverged
increment:
^^^ THE SOLUTION FOR LOOPID=
n IS SAVED FOR RESTART
This message is not true since increment "n" has not been saved for restart.
Avoidance: Ignore the message since only increments up to n-1 have been saved.
39326
Database - SFM 1041 (GALLEX)
A limit in the database directory size may cause large jobs to fail with the
message SYSTEM FATAL MESSAGE 1041 (GALLEX).
Avoidance: This limitation can be overcome by increasing the buffsize and/or
setting system(158)=1000 and system(159)=500 to allow for a larger expansion of
the database.
39342
rning
2001
DMAP - DEFUSET - Entry Ignored without Wa
The DEFUSET function was removed in Version 70.7. Any such bulk data entries
are now ignored, without warning.
39375
ted
2004
FMS - ASSIGN, scr=yes - Database Not Dele
:q
vi rIn Version 70.7, if an ASSIGN statement is specified for the database, the
database will not be deleted at the end of the job even if scr=yes is specified
on the command line.
1. Add the following FMS statement to the input file
init master(s)
2. Add a ",temp" to the end of the assign statement.
39378
am Servers
Beam Library - CONNECT - Incorrect Properties for Multiple Be
When more than one beam server is used, it may produce incorrect the
properties. This error occurs whe the Group names or evaluator class names
show certain pattern in which the first portion of the n-th group name is
identical to the name of the (n-1)-th group where n is => 2. In addition the
CONNECT entry including (n-1)-th group must precede the CONNECT entry
containing n-th group name. For example, the CONNECT entries given here will
produce the incorrect properties for the beamsrv1 group: CONNECT BEAMEVAL
beamsrv locbml and CONNECT BEAMEVAL beamsrv1 locbmls.
Avoidance: Do not use the problematic pattern as the group name for multiple
beam servers.
39386
2001
Documentation for SOL 109 and 112
Documentation/QRG - PARAM,S1 - Incorrect
Stress sorting was implemented in SOL's 109 and 112 in Version 69. The QRG
incorrectly shows that the associated parameters are not supported for these
solutions. .
39387
2001
- SFM 3007 DOM9
An optimization task may fail with the 'SFM 3007 DOM9, SUBROUTINE DOM91'
message when the DRESP2 response references another DRESP2 entry.
Avoidance: 1) Convert the offending DRESP2 entries into a single DRESP2 entry
or
2) Use the following dmap alter:
For v70.7
COMPILE DESCON
alter ' DSAD '
DBSTATUS RR2IDR//S,N,NORR2ID $
IF ( NORR2ID>0 ) THEN
PARAML RR2IDR//'TRAILER'/1/S,N,NRR2 $
TYPE PARM,,I,N,NRR2I
NRR2I = NRR2
PARAML RR2IDR//'DTI'/1/ S,N,NRR2I//S,N,R2ID $
IF (R2ID = 0) THEN
MODTRL RR2IDR //0 $
ENDIF
ENDIF
39391
2001
REQ, FLUTTER - Wrong Sensitivities
Optimization/Design Sensitivity - EIGN, F
Incorrect sensitivities can be produced in SOL 200 when all of the following
pertain:
a. There are superelements
b. A global response is selected as the objective
c. The response is not WEIGHT or VOLUME.
An example of responses are EIGN, LAMA, FREQ and FLUTTER.
Correct answers are provided when the response is constrained. It is only when
it is invoked by the DESOBJ case control command that incomplete sensitivity
information is provided.
39422
2001
ails with large value of "dmp"
Distributed Memory Parallel - Execution f
Nastran runs with large values of the "dmp" parameter will fail in the setup
of the run. The exact value that is allowed is a function of various factors
like the size of the current path name.
39426
2001.0.1
e Eigenvalue Subcases - Missing Output
If two eigenvalue subcases with different boundary conditions are run in SOL
200, the second subcases eigenvalues are printed twice but the first is not
printed. The eigenvector results are printed correctly and the optimzation is
performed correctly.
Avoidance: Setting NASPRT=1 will produce correct eigenvalue results at each
design iteration, including the last. Version 70.5 can also be used to get the
correct prints.
39433
8
2001
Inertia Relief - PARAM,INREL,-2 - UWM 469
When a matrix to be decomposed requires 2 by 2 pivots, its rows may be

identified as having negative factor terms by maxratio and USER WARNING MESSAGE
4698 may be issued. 2 by 2 pivots most commonly occur when using Lagrange
Multiplier techniques (LMT). The max ratio test is not valid for this
circumstance, so this warning message may be ignored. LMT methods are used in
sol 101 for param, inrel, -2.
39436
2001
plex Eigenvectors Missing from xdb
Aeroelastic Analysis - PARAM,POST,0 - Com
If complex eigenvalues/vectors are extracted using the pk method, they cannot

be written to the xdb file (PARAM POST 0) due to an error in the datablock
labelling
Avoidance: The op2 file (PARAM POST -1) can be used to display complex
eigenvectors in MSC.Patran
39439
2001
Inertia Relief - PARAM,INREL,-2 - Poor Pe
rformance
When the automated suport capability for inertia relief is selected (param,
inrel, -2) the problem may run many times slower than when other methods of
inertia relief are used.
Avoidance:
ir2a.v707.
A dmap avoidance is given in the sssalter library with the name
39440
Wrong Answers
2001
If any thickness of the various plies on a PCOMP entry is defined as a design

variable, Z0 is blank, and a DVPREL1 or DVPREL2 has not been used to define
ZO, then wrong answers may occur. This error occurs because the the initial
Z0 is used for the entire design optimization task even though Z0 changes as
the ply thicknesses change.. Thus, sensitivities and optimization results are
wrong.
Avoidance: A DVPREL1 or DVPREL2 entry must be used to define Z0 ( Z0 =-0.5
times the element thickness). Otherwise, the initial Z0 will be used for the
entire design optimization task even though Z0 changes as the ply thicknesses
change.. Thus, sensitivities and optimization results are wrong for Z0=blank
without DVPREL1 or DVPREL2 definition.
39449
2001
for nonlinear are wrong
Documentation/Plotting - CTETRA iem codes
The Stress-Strain Item Codes, in Appendix A, of nonlinear HEXA, PENTA and TETRA
are wrong in the current Quick Reference Guide, The errors and corrections are
listed as follows:
1) The last row of Nonlinear CHEXA (Code=93), "19-146 Items 3 through 17
Repeated for 8 corners", should be changed to
"19-146 Items 3 through 18 Repeated for 8 corners ".
2) The last row of Nonlinear CPENTA(Code=91), "19-146 Items 3 through 17
Repeated for 8 corners", should be changed to
"19-114 Items 3 through 18 Repeated for6 corners".
3) The last row of Nonlinear CTETRA(Code=85), "19-146 Items 3 through 1
39452
2001
External Superelements - ASET, USET, Resi
dual Vectors - Possible Wrong Answers
If an explicit ASET and a user USET (i.e. U1, U2, U3, U4, U5, or U6) are
specified, then the USET table is corrupted. The ASET will be reduced by the
dof which are common with the user set (u1-u6). and wrong answers may occur.
39473
2001
- PLSOLID, MATHP, PCOMP - SFM 3003
Nonlinear Analysis/Hyperelastic Elements
When hyperelastic material properties (PLSOLID and MATHP) are used together
with composites (PCOMP) or the alternate form of beam property (PBCOMP) in a
nonlinear analysis, Nastran fails in IFP6 if MATHP refers to any TABLES1
entry.
Avoidances:
This error can be avoided if user specifies the material
constants instead of using tables.

39482
Distributed Memory Parallel - DMP - Misleading f04 mesages
When running jobs using DMP (distributed memory parallel) with more than 2
cpus, the f04 file may only show the execution time of 2 cpus. The log file
does have the correct information. The results are correct.
Avoidance: The F04 and F06 output from Slave processes may be retained by
specifying "slaveout=yes" on the command line. Otherwise the Slave output is
discarded. The stderr/stdout output is retained in the log file regardless of
the slaveout setting.
39488
ce
Performance - DECOMP - Solver sequencer causes poor performan
The automatic sequencing options in the DCMP and READ solver modules go from a
grid point based sequencing to a DOF sequencing under some circumstances.
Avoidance: TAN 4593 describes the reasons for this transition, and methods to
avoid the transition. It has been observed that DOF sequencing can be more
than 10 times slower than grid point sequencing.
39490
FM 4276 UNPACK
2004
Nonlinear Transient Analysis - NLTRD2 - S
It is possible that a nonlinear transient analysis may fail with BIOMSG 33,
followed by SYTEM FATAL MESSAGE 4276, indicating an UNPACK error.
Avoidance: The exact cause of this problem is under investigation. One
potential cause is epoints. Replacing epoints with spoints may solve the
problem.
39502
Nonlinear Heat Transfer - RADBC - UFM 4551 (NCONVG)
This problem can be solved using coupled convection approach that is available
in PATRAN.
If a nonlinear heat transfer analysis models radiation across a gap using the
RADBC entry the job is likely to have trouble converging and will issue the
message:
*** USER FATAL MESSAGE 4551 (NCONVG)
Avoidance: Use a CONV entry to model the radiation across the gap.
Avoidance: Model radiation across gap using convection with exponent equal to
4.0
Or run the model in transient analysis until it reached steadty state solution
39508
2001
- PLSOLID, MATHP
Nonlinear Analysis/Hyperelastic Elements
Nastran job may fail in nonlinear analysis when the specified number(s) of NA
(order of polynomial function of the distortional strain energy) and/or ND
(order of polynomial function of thethe volumetic strain energy) in MATHP card
are higher than the real rank(s). The real ranks are computered from user
specified material constants (Aij and Di) or tables (TABLES1) in MATHP bulk
data card by NASTRAN automatically.

Avoidances: This error can be avoided if user controls the number of order of
NA and ND - don't make them higher than the possible ranks based on the user's
input of Material constants (Aij) or Tables (TABLES1) in the MATHP bulk data
card.
39509
Transient Analysis - PARAM,ADSTAT, LFREQ, STATSUB - UFM 6143
If a modal transient analysis is run using PARAMs ADSTAT and LFREQ and the
case control command STATSUB, then the run will fail with UFM 6143 indicating
incorrect input to the MERGE module.
Avoidance: Insert the following DMAP your file:
compile super3
alter 'matmod.*lm1.*mass'
type parm,,rs,y,lfreq
if(lfreq>0.)then $
$
$ correct error if ADSTAT, LFREQ, STATSUB are all used
$ this is a simple correction and will not work for the general case
$
paraml freq//'trailer'/2/s,n,nmodes $
type parm,,i,n,rmmodes
rmmodes=nmodes-NRUH1 $ number of modes removed by LFREQ - NOTE this alter does
$
not check for HFREQ or NMODES

matgen ,/lfmodes/6/nmodes/rmmodes/NRUH1 $ partitioning vector based on removed
modes
partn freq,,lfmodes/,nfreq,,/1 $
partn mass,
39510
Nonlinear Analysis - Incorrect Loadstep ID after UIM 6189
If a Nonlinear analysis issues the message:

*** USER INFORMATION MESSAGE 6189 (NCONVG)
*** BEST ATTAINABLE SOLUTION HAS BEEN FOUND ***
Then for the next load increment the 3 permitted bisections are going to take
place without convergence. The displacement output for the "BEST ATTAINABLE
SOLUTION" will then be labeled with a load factor that includes the increment
from the final step with 3 bisections.
Avoidance: Set the intermediate output (INTOUT) field 9 on the NLPARM entry to
YES.
39556
401
2001
Eigenvalue Analysis - EIGRL, READ - UFM 5
USER FATAL MESSAGE 5401 is issued when a Lanczos job does not find any roots.
Possible causes are given. One cause that is not given in the message is a
large maximum ratio indicating a modeling error.
39560
2001
S=FLUTTER SFM 4276 (tbk) at DSAPRT,DSAD
A design optimization analysis may fail in the DSAD or DSAPRT modules if
ANALYSIS=FLUTTER
*** SYSTEM FATAL MESSAGE 4276 (tbk)

ERROR CODE
7777 PID= 0
*** USER INFORMATION MESSAGE 4276 (tbk)
39572
2001
Normal Modes - SOL 103 - Bad Eigenvalues
Bad eigenvalues may occur on the Version 70.7.2 NEC system with a build date
of December 15, 1999. This error has been corrected in Version 70.7.2 on the
R3 CD. The error was fixed without changing the Version. The build date of
the corrected executable is June 28, 2000.
39609
Miscellaneous - SGI ffio may result in a traceback
The FFIO feature may cause problems on some SGI operating systems. The jobs
may stop with a traceback in ffopen.
Receiving signal number 5: Trace/BPT trap
Avoidance; Setting ff_io_opts = 'casecon.DB* casecon.db* casecon*SCR*
casecon*scr* may solve the problem. Else turn off FFIO.
39612
2004
a Matrix to a Null Matrix
DMAP - ORTHOG Module Incorrectly Declares
The ORTHOG module may incorrectly declare a matrix with small terms to be null
and the following message is then issued.
*** SYSTEM WARNING MESSAGE 6467 (ORTHRD)
A NULL COLUMN WAS ENCOUNTERED AT COLUMN NUMBER =
ORTHOGONALIZATION
39624
2001
1 DURING
P-Elements - MATTi - Wrong Answers
If temperature-dependent material properties are being used with p-element

shells,and the temperature field is not constant, the answers may be incorrect.
39629
Documentation/SOL 146 - DAREA, TABRNDG - Unexpected Answers
If the component number from the DAREA entry is not included on an SPC, then
its value is superimposed with the TABRNDG entry. For
gust analyses, this will duplicate the gust loading in Sol 146.
This is
discussed in section 9.3 of the Aero User's Guide but should also be discussed
in the QRG.
39630
- Missing Output
Modal Frequency Response - multiple subcases, element output
If multiple subcases exist in a modal frequency response analysis, and

element-type output is requested (e.g., force) in the second or subsequent
subcases without requesting it in the first subcase, then the element output
will be missing.
Avoidance: There are two possible avoidances. The first one is recommended.
1. Add the same request in the first subcase. If the printed output is not
desired, use the (plot) option.

2. Use param,ddrmm,-1. This method is not recommended as it may cause
substantial additional runtime.
39633
2001
E,2 - UWM 8592 (REIG)
Nonlinear Buckling Analysis - PARAM,BUCKL
Nonlinear buckling analysis in a cold start run was made possible in Version
70.7 by specifying param, buckle, 2. A buckling analysis should be able to be
selectively perfromed for each subcase that has a method = n specified.
However, if a method request is not made in each subcase the job will fail
with the following message:
*** USER WARNING MESSAGE 8592 (REIG)
THE METHOD RECORD IN CASE CONTROL IS MISSING OR INCORRECT.
0) IN TABLE (EED ) IN SUBROUTINE
(REIG).
0FATAL ERROR
Avoidance: Insert the following DMAP alter or make the
39636
2001
Aeroelastic Analysis - SPLINE - UFM 7358
In an aeroelastic analysis, USER FATAL MESSAGE 7358 may be issued in error.

This has been observed to occur when the the structural grid points used by the
spline are separated by a length that is much less than one.
Avoidance: Recasting the dimensions of the problem so that the distances are
greater than one should provide a workaround. Another alternative is to
select additional gridpoints that are outboard or inboard of the selection.
This error does not occur in Version 70.5 so this version could be used as an
avoidance.
.
39643
2001
DSAD13 - Read Past End of Record
In a Nastran optimization job (sol 200) the message

ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD (DSAD13)
is produced with composite responses (DRESP1 RTYPE = CSTRESS,CSTRAIN or
CFAILURE) if the lamina number requested in the ATTA field is greater than the
number of lamina on the associated pcomp entry.
Avoidance: Correct the incorrect lamina number request
39663
2001
Beam Library - DOM9 - Segmentation Error
A large optimization job that utilized the external beam library capability
gave a segmentation error in the DOM9 module. This problem was traced to a
time-out problem.
Avoidance: Use Node Locked instead of Flexm
39682
Answers
70.7
Aeroelastic Analysis - GUST, RMS - Wrong
In a symmetric aeroelastic analysis, if an aerodynamic panel lies on the plane

of symmetry wrong GUST RMS values or a rank deficient matrix result.
Avoidable: For symmetric analysis do not define panels that lie on the plane
of symmetry. Version 70.7 allows aerodynamic panels to lie on the plane of
symmetry by implementation of the AESYMXZ and AESYMXY commands.
39695
GL
Traceback in READ
Eigenvalue Analysis - PARAM,RESVEC,YES -
PARAM,RESVEC,YES may cause a floating point error in READ. This occurs when
the number of modes plus residual vectors exceeds the rank of the mass matrix.
This problem typically only occurs in very small test models where all modes
may be unexpectedely calculated.
Avoidance: Modify the EIGR(L) record so not all modes are computed. If there
are disjoint submodels, do not get all of the modes for any submodel for which
there will be residual vectors.
39697
2001
g eigenvalue table - SFM 3001
SSSALTER library - pstmac2a.v707, missin
When using the pstmac2a.v707 alter, if an eigenvalue table is not provided,

then the job will fail with SFM 3001
1. Provide an eigenvalue table
or
2. Modify the following statement from
lamx
,,lamdum1/lamat $
to
lamx lamdum1,/lamat/nummodes $
39705
2001
Virtual Mass - MFLUIED, ZFS - UWM 5411
When using virtual mass, if any grid point of an element listed on an ELIST
record lies very near the free surface, a nonpositive definite mass matrix may
occur. This may result in the following message:
*** USER WARNING MESSAGE 5411 (REIGL8)
NEGATIVE TERM ON DIAGONAL OF MASS(VIBRATION) OR STIFFNESS(BUCKLING)
MATRIX DETECTED.
ROW NUMBER =
56 VALUE = -3.60212D+01
The number of modes calculated may not match the Sturm sequence output.
Avoidance: Change the free surface level slightly so that no grid point lies
near the free surface. Near means a distance less than one percent of the
square root of the area.
39713
2001
Miscellaneous - DMIG - UFM 2070 (MTRXIN)
DMIG matrices may be selected by the (K2gg, M2gg, and B2gg) commands, and the
(K2pp, M2pp, and B2pp) commands. If the same matrix is requested twice, for
example
K2gg = AA $
M2gg = AA $
or
K2pp = AAX $
B2pp = AAX $
Then the following misleading fatal message is output:
*** USER FATAL MESSAGE 2070 (MTRXIN)
REQUESTED DMIG MATRIX AA IS UNDEFINED.
Avoidance:
Duplicate the DMIG matrix and rename.
39714
2001
, ERROR 3001 MTRXIN
Case Control - TFL - Poor Message, BIOMSG
If the Case Control contains the command TFL = [sid] but there is no TFL entry
in bulk data, a non-standard exit is taken. For Version 70.7 on the NT, the
following exit was taken in the MTRXIN module:
BIOMSG: ERROR
0.
STATUS =
3001 HAS OCCURRED IN ROUTINE FREAD
, FILE INDEX =
Avoidance: Correct the input data.

39718
els
2001
Case Control - MPRES - Missing Output Lab
If SORT2 format output is requested with the MPRESS Case Control command, the
associated "PRESSURES FOR ELEMENTS ON FLUID STRUCTURE BOUNDARY" output will
have no element labeling on it.
Avoidance: Request SORT1 output
39724
2001
r Normalization causes Wrong Ans.
SSSALTERs - modevala.v707 -MAX Eigenvecto
SSSALTER modevala.vxx assumes that the eigenvectors are normalized to unit

generalized mass. If they are not, incorrect results will occur.
Avoidance: Always normalize your eigenvectors to MASS (the default).
39742
tput
2001
Frequency Response - STATSUB - Missing Ou
If there is a static subcase in SOL 111 to apply a prestress followed by a

dynamic subcase, and if output requests are only in the dynamic subcase no
output is obtained.
Avoidance: Put the output request above all subcases or insert the following
DMAP alter:
compile super3
alter 'if ( desopt ) then',''

if ( true ) then $
endalter $
39751
LOADSET
2001
Loads - UFM 2008 (GP3) UNDEFINED GRID IN
If you have a large number of loads the analysis may fail with the message:
USER FATAL MESSAGE 2008 (GP3)
UNDEFINED GRID **** IN LOADSET ****
Avoidance: Increase BUFFSIZE
39771
2001
requires SOUT=YES
Optimization/Design Sensitivity - PBEAML
If a tapered PBEAML is being designed and the user has a value of NO for one of
the SO stress requests, incorrect sensitivity values will be created. The
optimizer will then be unable to make progress. A fatal message may be issued
or the job may indicate a hard convergence at design cycle 1.
Avoidance: Do not use SO(j) or SO(B) = NO.
39772
2001
Z0 term is Incorrect in Punch File
Optimization/Design Sensitivity - PCOMP
If a PCOMP with blank Z0 specified is designed in a Design Optimization (SOL

200) run, the punch file incorrectly changes Z0 to -1.
Avoidance: The only avoidance is to edit the punch file.
39773
2001
PBEAML - UFM 7052, 7197
Optimization/Design Sensitivity - PBEAM,
Solution 200 jobs may fail with USER FATAL MESSAGE 7052 or USER FATAL MESSAGE
7197 when the field name of an intermediate section of a PBEAML is referenced
on a DVPREL1 entry.
Avoidance: Split a PBEAM with multiple intermediate sections into multiple
CBEAM/PBEAML. For the new PBEAMLs, provide properties for end A and B only.
39786
2001
plication produces UFM 6721
Documentation/QRG - Continuation Entry Re
The "=(C)," immediate continuation format for card replication as defined on

page 428 of the v70.5 Quick Reference Guide no longer works.
Avoidance:
Use "," instead. For instance, instead of:
=(C), , *7, *7, *7, *7, *7, *7, *7
use:
, , *7, *7, *7, *7, *7, *7, *7
39791
2001
DMAP - SDR2 - SFM 3001, Wrong Datablock P
osition Number
The DMAP message:
10 DOES NOT EXIST.
may incorrectly identify the missing data block position.

Avoidance: Use DBSTATUS before the offending line to verify the status of the
input datablocks.
39806
2001
es part of input to be ignored
Miscellaneous - Missing "BEGIN BULK" caus
Starting with Version 70.7, if an input deck contains a "BEGINBULK" entry (no
space between "BEGIN" and "BULK") and the bulk data section contains INCLUDE
statements, then bulk data cards that appear BEFORE the "INCLUDE" statement
will be ignored.
39808
SSSALTERs - alter1ga - QGDYN is Output Twice
If MPCFORCE output is requested in a run using the alter1ga.v707 alter the run
will fail with a message warning that datablock QGDYN is being output twice.
Avoidance: Either remove the MPCFORCE request or request an updated version of
the alter from MSC.
39847
2001
Documentation/QRG - DCONADD and DCONSTR
When the same DCID specified by a DESSUB command is referenced by DCONADD and
DCONSTR entries, the constraints defined with the DCONSTR entry are ignored.
Avoidance: Two avoidances exist:
1. Do not reference the same DCID with the DCONADD and DCONSTR entries.
2. If one insists on referencing the same DCID with both entries, include that
DCID in the DCONADD entry as the DCONSTR identification number.
39871
_abort mpi bug
Distributed Memory Parallel - DMP, MPCs - signal caught, mpi
When using Distributed Memory Parallel (DMP) and there are many MPCs, then a
large amount of memory is needed. If insufficient memory is allocated, then
the job will fail with the following messages in the log file
---------SIGNAL CAUGHT:
Signal number
= 15
Signal code
= -1
Signal pid
= 3426
Signal uid
= 9450
Signal tid
= 1
Fault addr
= 00000d62
FP inexact
= 0x0
FP divide0
= 0x40000000
FP underflow
= 0x0
FP overflow
= 0x20000000
FP invalid
= 0x0
---------TRACEBACK:
Avoidance: If there are large number of MPCs, use a single processor instead
of DMP.
39885
2001
Materials - MAT2 - UFM 2042 (EMG)
Starting with Version 70.5, if a bulk data file includes PSHELL/MAT2s with
9-digit MIDs where any of the MIDs are greater than 400,000,000 then the deck
fails with the message:
USER FATAL MESSAGE 2042 (EMG) MISSING MATERIAL TABLE ****** FOR ELEMENT
Such PSHELLs/MAT2s are routinly constructed from the PUNCHed echo of a PCOMP
entry but they must not be mixed with other PCOMP entries. The message has
been improved in Version 2001.
39889
Job Hangs
2004
Distributed Memory Parallel - DMP, EMG -
A distributed memory parallel Statics, SOL 101, job will hang if one of the
tasks gets a fatal error in EMG.
Avoidance: Other than correcting the input there is no avoidance.
39892
nd
2001
DMP - Missing Library - libmpi.so not fou
The distributed version of MSC.Nastran Version 70.7 on linux requires a file

libmpi.so.1. This file was not placed on the CDROM.
1. The file may be created by using the lam-6.3.1.tar.gz file which is in
$MSC_BASE/msc707/linux with the following commands:
configure --with-fflags=-fno-second-underscore --with-shared
make install
These commands create /usr/local/lam-6.3.1/lib/libmpi.so.1. Please copy
this file into $MSC_BASE/msc707/linux.
2. The file may be downloaded from the MSC ftp site from:
ftp://ftp.macsch.com/pub/msc-products/NASTRAN/V70.7/linux/
or:
ftp.mscsoftware.com/pub/msc-products/NASTRAN/70.7/linux/
39896
2001
SFM 7340 (LNNHERR)
Eigenvalue Analysis - READ, EIGRL, RBE3 -
Lanczos eigenvalue problems that ran in Version 70.5 may fail in 70.7 with the
message:
Avoidance: This error may be related to the re-formulated RBE3 elements,
Setting rotational dof set as independent, appears to be the cause of the
problem.
If this is the case, either setting:

or removing all rotational dof from the independent set may fix the problem.
39901
TRANS/RECEIVE - Missing libF77.so.4
It is possible that the fortran libraries cannot be found for the NASTRAN
utilities 'trans' and 'receive'. This is evidenced by an error message like:
ld.so.1: receive: fatal: libF77.so.4: open failed no such file or directory
Avoidance: A possible solution is as follows (example for SUN SOLARIS):
Ensure the following three libraries( libF77.so.4; libM77.so.2;
libsunmath.so.1) exist in directory <installation-dir>/msc/msc707/solaris.
Then set the environmental variable LD_LIBRARY_PATH to that directory.
39904
2001
Superelement - heat transfer - UFM 6599
Superelement heat transfer works in SOL 101 by specifying APP HEAT. However,
it only works when there is no convection in the problem. NASTRAN heat transfer
applies convection by first defining a boundary element (CHBDYG or CHBDYE) and
then applying CONV with the same element ID on that boundary element. For
example:
chbdyg,101,,area4
,5,6,17,16
conv,101,1,,,99
However, there is a limitation in superelements that all element IDs must be
unique else the following fatal message is encountered:
*** USER FATAL MESSAGE 6599 (SEPUEC)
DUPLICATE ELEMENT IDS CONV
SUPERELEMENT
0
0FATAL ERROR
101 AND CHBDYG
101 IN

39931
2001
Database Missing on NT
DMAP - FIles Required to Create Delivery
If you are using Windows NT, the files necessary to create a delivery database
are not in the "del" directory.
Avoidance: Contact MSC and request a copy of the necessary files
Installed 2001 onto my w2k machine holywell, looks like files are
inD:\msc\msc2001\nast\del dir. Ken Winkler
39942
Nonlinear Normal Modes - PARAM,FOLLOWK - Wrong Answers
Using SOL 106 to perform a nonlinear static analysis of a rotating beam with
followk effects leads to wrong results when the modes are calculated by
restarting with SOL 103 using the NMLOOP parameter. Restarting SOL 106 from a
converged solution with just the NMLOOP parameter and a METHOD case control
request yields onty the results of the nonlinear static analysis, no normal
modes are computed.
Avoidance: To get the modes from a restart with SOL 106, add a static subcase
with the appropriate values of SUBID and LOOPID set with the NMLOOP parameter
and METHOD case control command, then the nonlinear normal modes could be
obtained.
39962
ers
2001
Superelements - PARAM,RESVEC - Wrong Answ
When using superelements or residual vectors, there is a hard-coded limit of

999 eigenvectors in the program for any single component. If a component has
more than 999 modes calculated, the program will incorrectly truncate it to 999
modes with no warning.
Avoidance: Insert the following DMAP alter to remove the limit:
compile resvec nolist noref
alter 'read.*kzz,mzz',''
paraml kzz//'trailer'/1/s,n,zzsize $
READ
KZZ,MZZ,,,,,,,,,,,/
ALAMA1,APHX1,MX,OX,EX,/
'MODES'/S,N,NV////-1/'LAN'////zzsize/0////PRTSUM $
39963
ign
2001
Nonlinear Analysis - CELAS1 - Incorrect S
The element force output for CELAS1 in nonlinear solutions has an incorrect
sign in MSC.Nastran Version 70.7.
39994
2004
Documentation/QRG - YTAXIS - UFM 676
If the XYPLOT command YTAXIS is used, the program will incorrectly issue UFM
676 indicating that it is not recognized.
*** USER FATAL MESSAGE 676 (IFP1XY)
YTAXIS IS NOT RECOGNIZED ON ABOVE CARD.
Avoidance: Remove the command
39995
2001
) with Concatenated DLINKs
Documentation - DLINK - UFM 7011 (DOPR1B
The following remark show be added to the DLINK bulk data description in the
QRG. i
Remark 6.
If a design variable is specified as dependent on a DLINK entry, then it
cannot be specified as independent on another DLINK entry.
39997
in MRGCOL
Static Analysis - PARAM,INREL, REPCASE - UFM 6143 or SFE 4276
If conventional static solutions are mixed with inertia relief in the same run
and REPCASEs are used, the run may fail with UFM 6143 indicating incompatible
matrices. This error can also occur in SOLs 105, 200, and all dynamic SOLs
with preload capability.
compile sestatic
alter 'NSKIP1=NSKIP-1',''
nskip1=nskipl-1 $
alter 'NSKIP1=NSKIP-1'(2),''
nskip1=nskipl-1 $
endalter
40001
Optimization/Design Sensitivity - SDAMPING - Wrong Answers
The BHH value for modal damping is computed as Bi = 2 * Mi * (omega) * (zeta)

. Mi and omega can vary with the design variable and therefore affect the
modal damping sensitivity. However, these perturbations are ignored in the
current sensivity analysis with ANALYSIS = MFREQ. The discrepancy associated
with neglecting this term is most pronounced at resonant peaks.
Avoidance: Alternative forms of damping, such as PARAM G, cvisc and cdamp
elements and material damping are supported and could be substituted for the
modal damping input.
40007
ls in DISFBS
2001
Distributed Memory Parallel - SUPER - Fai
A distributed memory parallel job with SUPER Case Control commands

DISFBS. Version 2001 traps this invalid input earlier in SEQP and
following fatal message
*** USER FATAL MESSAGE 7567 (SEQP)
THE SUPER CASE CONTROL COMMAND HAS BEEN SPECIFIED.
USER INFORMATION: THE SUPER COMMAND IS NOT PERMITTED WITH THE
MODEL PARTITIONER.
USER ACTION: CONSOLIDATE AND REWRITE THE SUBCASES WITHOUT THE
COMMAND.
40008
2001
G - Unexpected Answers
will fail in
issues the
AUTOMATIC
SUPER
Case Control - K2GG, K2PP, M2GG, M2PP, P2
DMIG entries are selected by the K2GG, M2GG, P2G, and K2PP, M2PP case control
commands. If a case control command selects a bulk data DMIG entry, and there
are no DMIG or TF entries in the bulk data file, the module that reads this
matrix returns without any error messages, and the run may go to completion
although it is missing the selected DMIG information.
Avoidance: An avoidance is to put in at least one legal DMIG matrix. The
program will provide good diagnostics and a fatal error exit if any selected
matrices are missing from bulk data.
40037
Heat Transfer Analysis - VIEW3D - Wrong Answers
The View factor calculation may have trouble detecting elements when the
elements are very close. This may lead to wrong answers.
Avoidance: Decrease the ETOL error estimate from default 0.1 to a small
number such as 0.0001 on the VIEW3D bulk data entry , so that the VIEW3D
program will go and calculate the view factor using the contour integration
method
40040
2001
P-Elements - TEMP(LOAD), ADAPT - SFM 3003
When the ADAPT module is retrieving the thermal loads to calculate the error
estimators, the following fatal error may occur:
*** SYSTEM FATAL MESSAGE 3003 (ADAPT)

(FILE 109) IN SUBROUTINE GETEMP
Avoidance: The error appears to occur with multiple element types. Currently
the only workaround is to specify temperatures using TEMPD.
40077
D
Documentation - DMAP Programmer's Guide - SUBDMAP NOT EXECUTE
If a SUBDMAP is called with no output datablocks or parameters, then it may not

execute. Symptoms will be missing output and a statement in the .f04 file
"SUBNAME NOT EXECUTED." where SUBNAME is the name of the subdmap.
Avoidance: Add an output block to the calling sequence, or add a parameter.
40088
SSSALTERs - mtacca - Wrong Answres
SSSALTER mtacca.vxxx correctly calculates the rigid-body acceleration terms

based on the initial conditions, however it does not include the effect of the
initial rigid-body acceleration on the rigid-body velocity and displacement
terms.
Avoidance: The flexible results are correct. If the relative solution is
obtained (positive value of PARAM,RBMODES), the answers are correct..
40094
3007 (TRD1)
2001
Transient Response Analysis - K2PP - SFM
If a complex matrix is input using the K2PP command, a transient response run
*** SYSTEM FATAL MESSAGE 3007 (TRD1)
ILLEGAL INPUT TO SUBROUTINE TRD1H
Avoidance: Use only real matrices in transient analysis.
40127
2001
Heat Transfer - RADBND - Wrong Answers
In a steady state heat transfer analysis if RADBND is used to model the

radiation across a gap then wrong answers may result.
Avoidance: Use RADBC to model radiation across gap instead of view factor.
40133
ng Answers
2001.0.1
Frequency Response - TLOAD1, TLOAD2 - Wro
TLOAD1 and TLOAD2 entries define a time dependent load. In frequency response
a Fourier analysis is used to transform the time-dependent load to the
frequency domain. The TYPE field on the TLOAD1 and TLOAD2 entry which
specifies whether the dynamic excitation is and enforced displacement,
velocity, or acceleration, is ignored in frequency response.
40134
2001
OJ statement is present
Miscellaneous - ESTIMATE crashes when PR
The estimate program fails when a PROJ file management statement is present.
Avoidance: Remove the PROJ statement.

40139
2001.0.1
DMAP - MATGPR, USET - Bad DOF Labels
When USET entries are present in the bulk data section that place degrees of
freedom in user defined displacement sets, Form 1 (MATGPR GPL,USET,SIL, ...)
usage of the MATGPR module may cause the degree of freedom output identifier
code to change from the expected T1/T2/T3/R1/R2/R3 to simply the component
direction number (1 thru 6). This will occur when the degree of freedom
internal number associated with the grid/components defined on the USET entry
is less than the number of grid points in the bulk data. External grid
identification numbers and printed matrix values are correct. Only the
component code identifiers may be displayed differently. The identifier
(whichever one is displayed) is correct.
Avoidance:
A possible avoidance is to use the second form of the MATGPR module
40141
2001.0.1
er has difficulty making progress
Optimization/Design Sensitivity - Optimiz
It has been observed that the Method of Modified Feasible Directions (Method=1
on the DOPTPRM entry) can sometimes fail to provide a better design even though
it seems that it should. This occurs in situations when there are many more
active constraints than there are design variables
Avoidance: The SQP algorithm (Method=3 on the DOPTPRM entry) may make progress
in these situations.
40156
2001
issing Acoustic Pressure Output
Acoustic Analysis - fluid-only models - M
If a model contains only fluid elements then the "COMPLEX ACOUSTIC RESULTS"
output will not be printed.
Avoidance: Insert a dummy structural element or the following DMAP alter:
compile sedrcvr
alter 'fscoup'
fscoup=true $
endalter
40157
ART - SFM 6036
2001
Nonlinear Analysis - PARAM,BUCKLE,1, REST
Nonlinear buckling analysis by a restart in SOL 106 with param, buckle, 1 will
encounter SFM 6036 (divide by zero) if the number of increments for the restart
subcase is different from 2 or the bisection is triggered.
Avoidance: Specify INTOUT=YES on the NLPARM Bulk Data entry in the last
subcase or insert the following DMAP alter:
compile nlstatic
alter 'IF ( BUCKLE=2 ) POUTF=1',''
if ( buckle>0 ) poutf=1
endalter
40158
ferent Answers
2001
Documentation/Rigid Elements - RBE3 - Dif
The reformulated RBE3 element in V70.7 can result in large differences in

answers between V70.5 and V70.7. This has only been observed on models where
rotations have been selected on the connected grid points. The changes are
most noticeable when the distances between connected grid points are much
greater than 1.0. The changes in answer between versions do not occur when
only translations are used for the independent dof.
Avoidance: To obtain same answers as in Versions prior to 70.7 set:
to use the old RBE3 formulation or do not use rotations on the "connected" grid
points on RBE3 elements. The answers will then be identical between v70.5 and
later versions.
40165
2001.0.3
Nonlinear Transient Analysis - NLRGAP, PA
RAM,TSTATIC, NLTRD2, UWM 5258, SWM 3002
An NLRGAP entry exists in a nonlinear transient analysis with param,tstatic,1
then the job will fail in the nltrd2 module with UWM 5258 and SWM 3002.
Avoidance: Other than removing the NLRGAP entry there is no avoidance.
40167
2001
Wrong Answers on NEC
Optimizaton/Design Sensitivity - CBUSH -
In MSC.Nastran Version 70.7 the NEC system has special code to enhance the
performance of design sensitivity tasks that utilize the adjoint method. This
code yields wrong answers when there are no coordinate systems in the bulk data
file and a CBUSH element is being designed.
Avoidance: Add a dummy coordinate system. For small problems where performance
is not a large concern, setting PARAM AUTOADJ NO will avoid the problem by
avoiding the adjoint method.
40171
2001.0.1
READ module is Indirect.
Eigenvalue Analysis - Maxratio Control in
Parameter MAXRATIO is used by the DCMP module in statics analysis to control

the degree of near-singularity that is allowed when computing solutions. It is
input to the DCMP module with a user parameter. This parameter is not an input
to the eigensolver, the READ module, although READ makes tests based on its
value. If the DCMP module has not run first the value READ uses is set to
1.E7. If DCMP has run prior to READ the value input by the user for DCMP is
also used for READ.
Avoidance: DCMP is called in modal analysis when SUPORTs exist, when
superelement reduction is used, when residual vectors are computed, and for
several other reasons. However, it is not always called before the READ
module, that behavior is problem dependent. Look in the .f04 file for the word
DCMP before R
40184
2001
- PLOADi, CBAR - Incorrect Sensitivitie
In solution 200, sensitivities are incorrect if a distributed load is applied
on CBAR and/or CBEAM elements and there are more than one design variable.
40228
2001
xception in SEP1X
Superelements - CSUPER - Floating Point E
A model bringing in an external superelement may fail with a floating point

exception in module SEP1X if the GRID points defined on the EXTRN entry do not
exist.
Avoidance: Always make sure that the GRID points on the EXTRN entry exist in
the model.
40257
2001
B - UWM 4568 (INTERR)
Dynamic Analysis - PARAM,RSPECTRA, STATSU
Response spectra analysis does not work with prestressing (STATSUB Case Control
command). If attempted the following message is issued:
.*** USER WARNING MESSAGE 4568 (INTERR)
THE NUMBER OF SPECTRUMS SELECTED ON THE, DLOAD CARD DOES NOT MATCH THE
NUMBER OF SUPPORT POINTS.,
CALCULATIONS FOR THIS SUBCASE TERMINATED.
compile semodes
alter 'call postreig'(,-1)
call dbstore casem,,,,//0/0/'
'/0 $
compile postreig list
alter 'equivx '
call dbfetch /casem,,,,/0/0/0/0/0 $
PA
40261
2004
PARAM,OUNIT2 is ignored
Documentation/QRG - Part Superelements -
The Nastran Quick Reference Guide indicates that PARAM,OUNIT2 may be specified
in either the Case Control or the Bulk Data. If it is specified in the Bulk
Data after a BEGIN SUPER entry it will be ignored.
Avoidance: Specify the parameter in the case control..
40263
2004
RAM,ADSTAT - UFM 6143
Transient Response Analysis - EPOINTS, PA
If a model has EPOINTs and PARAM,ADSTAT is specified on a pre-stressed

structure in a modal transient response analysis, the run will fail with UFM
6143 indicating that incompatible matrices were attempted to be merged.
compile super3
alter 'append.*freq0,mass'
if(n1<>nruh1)then $
type parm,,i,n,ted1 $
ted1 = n1 + 1 $
matgen ,/vone2/6/ted1/1/n1 $
merge ,,f0m,,,,vone2/f0m1/1 $
$
else $ n1=nruh1
$
alter 'merge.*f0m,,,,vone'
endif $
40275
2001
If the first input to MATMOD Option 20 is purged, then wrong answers result.
Avoidance: Rearrange the inputs so that the first input is never purged.
40276
2001
Restarts - SCR=MINI - UFM 2071 in DPD
In any dynamic solution with static loads used to define dynamic loads, if the
initial run is made using SCR=MINI, the restart run may fail with the following
message:
*** USER FATAL MESSAGE 2071 (DPD2) will be issued indicating that the DAREA set
is not defined.
Avoidance: Insert a dummy DAREA or the following DMAP alter in the restart
run only:
compile (insert main subdmap name; e.g., sedtran for SOL 109, sedfreq for SOL
108, semfreq for SOL 111, semtran for SOL 112)
alter 'dpd ',''
DPD
DYNAMICS,GPLS,SILS,USET,,/GPLD,SILD,USETD,
TFPOOL,,PSDL,,NLFT,TRL,EED,EQDYN/
-1/S,N,LUSETD/0/0/0//0/0/1/123/S,N,NOUE $
endalter
40280
03
Nonlinear Analysis - CBUSH, PBUSHT ,CBUSH1D, PBUSH1D - SFM 30
In SOL 106, the use of CBUSH or CBUSH1D elements with a nonlinear

force-deflection with a lot of zero slope around the origin may lead to the
following unclear fatal message
SYSTEM FATAL MESSAGE 3003 (NLITER)
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK MESTNL (FILE
208) IN SUBROUTINE NLINIT
This is due to the fact that all the nonlinear stiffness is zero for this
iteration. This should rarely occur-usually with single element decks. If it
does add a dummy nonlinear element that will never have a zero slope as for
example:
$ put in a mnl
$
2
CBUSH 6666
PBUSH 333333
PBUSHT 333333
TABLED1 1212
-2.3
40284
le
dummy element
3
4
5
6
333333 777777 888888
K
.1
KN
1212
-9.-9
0.
Postprocessing - Shock Response results not written to XDB Fi
Running shock response analysis using Sol 103 with PARAM,POST,0 will generate
an XDB file which contains only the model but no results.

Avoidance: Set PARAM,POST,-1 and the results will be written to the .op2
file.
Fix being imported under 38537
40296
2001
- Incorrect Punch File
Optimization/Design Sensitivity - DESPCH
When parameter DESPCH is set to a non-zero value in an optimization task, the

updated property entries written in the punch file do not correspond to the
current design cycle. In fact, the updated property entries for the previous
design cycle will be written.
Avoidance: use the following dmap alter where the original inputs of ept, geom2
and mpt are replaced by eptn, geom2n and mptn.
compile desopt
alter 'dom12 '(2),'dom12 '(2)
DOM12
XINIT,XO,CVALO,PROPIF,PROPOF,OPTPRMG,HIS,DESTAB,
geom1n,coordo,,,eptn,geom2n,mptn,epttabf,dvptabf,,,,,,,/
HISADD,NEWPRM,,NEWDES/
DESCYCLE/OBJIN/OBJOUT/S,N,CNVFLG/cvtyp/OPTEXIT//
MDTRKFLG/DESPCH/DESPCH1/MODETRAK/eignfreq//
PROTYP///fsdcyc $
40307
aster+slave(s)
2001
DMP - UFM 4276 EC 923, Infinite loop on m
In a DMP (distributed memory parallel) analysis if a slave runs out of disk

space then the job may hang and become caught in an infinite cpu loop.
40310
2001
Optimization/Design Sensitivity - DSAPRT
If a design variable has more than 6 digits in its id, the formatted
sensitivity output will replace the design variable id with ******.
Avoidance: Do not use design variables with more than 6 digits in the id.
40315
DIAGONAL
2004
The DMAP Module Dictionary description of the DIAGONAL Module's WHOLE option is
incorrect for complex matrices.
In case of a complex matrix, the option WHOLE gives the following result:
POWER = 1.: Magnitude of the complex matrix elements
POWER != 1.: The real part of the complex matrix element is raised to the power
40358
2001
xpected Results
Acoustic Analysis - PACABS - Possible Une
SYNTH=-YES requests the calculation of B, K, and M from the specified tables.

However if a value is given for B, K, or M on the PACABS entry, then any table
input is ignored and the data in the B, K, and M fields is used. If SYNTH is
specified as NO and no data is specified for B, K, or M then TIDi is used.
40369
002
Aeroelastic Analysis - HESS, KE-Flutter - SFM, BIOMSG ERROR 3
The Hessenberg eigenvalue extraction method used in the ke flutter analysis may
fail to converge. When this happens, a misleading message such as
BIOMSG: ERROR
, FILE INDEX = 0
is produced.
Avoidance: This problem has only been observed on decks where the flutter input
data is questionable. If this message is encountered it is suggested that the
k-method of flutter analysis be chosen combined with the complex lanczos
method.
40394
Wrong Answers
2001
GPFORCE - GPFDR, DEFORM, REPCASE, TEMP -
Grid Point Force gives incorrect answers when thermal (TEMP) loads are
combined with DEFORM loads in the same subcase.
40395
GPFORCE - GPFDR, CQUAD8 - Wrong Answers
The applied load may be incorrect for Grid Point Force output when thermal
loads are applied to CQUAD8 elements.
Avoidance: There is currently no avoidance.
40399
2001
RTYPE=ESE - UFM 1126 (GNFIST)
If RTYPE=ESE is specified on the DRESP1 entry then the job may fail with USER
FATAL MESSAGE 1126.
Avoidance:
compile respsen
alter 'IF ( DOWTVOLD\<=0 ) ELTPRT', ''
40408
Damping - GE, MAT8 - Possible Wrong Answer
The value specified for the GE, material damping, field on the MAT8 entry is
being ignored if it is referenced by a PCOMP entry.
Avoidance: If the GE field is important, replace the PCOMP/MAT8 with
equivalent PSHELL/MAT2/MAT1 entries.
40423
on
2004
nastran script - s.pmem - Memory Allocati
If s.pmem is set in the nast*.ini file, then it will be ignored.

Avoidance:
Set s.pmem in the nastran command script:
nast* )
exec $cmdtool "$@" s.pmem=1024mb
40438
User Modifiable Nastran - Not Enough Space
The executable built by User Modifiable Nastran can not use memory larger than
115mb else the following error may be encountered:
Error (errno=12) in opencore memory allocation of xxxx words
MSC.NASTRAN (ocalloc.c): Not enough space
This error may be caused by:
Insufficient swap space.
The maximum possible size was exceeded.
Avoidance: This problem is caused by a typo in the link script (umnld). In
this file, there is an enviroment variable MAXDATA. For non-dmp it should be
set as MAXDATA=0x80000000 and for dmp should be set as MAXDATA=0x70000000 (it
should have 7 zeros).
40444
2001
BAR - Wrong Answers
Optimization/Design Sensitivity - RBEi, R
When an optimization job includes both sizing variables, and shape variables
that affects the grid locations associated with the r-type elements, the
response sensitivities with resepcet to a sizing variable may be null.
Avoidance: use the following dmap alter:
compile desopt
alter 'rgsens='
rgsens = false
alter 'dopr5 '
rgsens = false
compile respsen
alter 'rgsens=('
rgsens = false
compile pslgdv
alter 'dsvgp4'
rgsens = false
40465
Complex Eigenvalue - EIGC, Massless DOF - SFM 3002
In MSC.Nastran Version 70.7, if the model contains massless degrees of freedom

and the old lanczos single vector method (system(108)=2) is used, then the job
may fail with the following error messages:
*** SYSTEM FATAL MESSAGE 3002 (CEAD)
SUBROUTINE CLASP
0FATAL ERROR
Avoidance: Use the new default block lanczos method.
40475
M 6985
2001
Nonlinear Elements - CBUSH1D, SDR2RD - SF
A FORCE=ALL Case Control request will cause an analysis with CBUSH1D elements
to fail with the message:
*** SYSTEM FATAL MESSAGE 6985 (SDR2RD)
PREVIOUS ELEMENT-ID =
9010
DID NOT REQUEST CORRECT NUMBER OF PHASE-1 OUTPUT WORDS.
Avoidance: Request STRESS=ALL instead or both FORCE and STRESS
40479
2001
DMAP - CEND, ENDALTER - UFM 601 (IFP1D)
The automatic generation of a CEND entry introduced in MSC.Nastran V70.7

causes jobs with user DMAP that does not end with an ENDALTER to fail with the
following message:
*** USER FATAL MESSAGE 601 (IFP1D)
THE KEYWORD ON THE ABOVE CARD TYPE IS ILLEGAL OR MISSPELLED.
Avoidance: Input an ENDALTER statement
40497
2005.5.2
ceback in lnnrigl, bucksd
Nonlinear Buckling Analysis - EIGRL - Tra
Tom, This is old error see Louis' comment in the attachement. - Raj
In a nonlinear buckling analysis, if the differential stiffnes matrix is null
then a traceback may occur in the READ module.
Traceback:
Offset 0x000003c0 in procedure
Offset 0x000005fc in procedure
Offset 0x0000149c in procedure
Offset 0x000028b8 in procedure
Offset 0x000000f4 in procedure
Offset 0x00000134 in procedure
--- End of call chain --40503
nce
2001
chkjacd_
bucksd_
lnnrigl_
reig_
xsem06_
xsemdr_
nastmon_
mainal
Transient Response - TRLG - Poor Performa
MPYAD picks inefficient methods. It tends to pick method 1 nt, when that is
almost always the slowest method, usually requiring multiple passes when there
are many time steps.
An alter that avoids this error is:
Compile semtran list
Alter 'trlg.*ppt'(,-1) $ before
type parm,,I,n,oldsys66 $
oldsys66=getsys(oldsys66,66) $
message //'oldsys66'/oldsys66 $
putsys (1,66) $ deselect 1 nt
Alter 'trlg.*ppt' $ after
putsys (oldsys66,66) $ restore original value
40514
2001
scr=yes - Wrong Answers
Nonlinear Analysis - PARAM,BUCKLE,2 and
Nonlinear buckling analysis in SOL 106 with PARAM,BUCKLE,2 may give poor
answers if a scratch data base is used (scr=yes) and there are linear elements
in the model.
COMPILE NLSTATIC
ALTER 1
FILE
KDJJ=SAVE,OVRWRT/KDGG=SAVE,OVRWRT/KDSF=SAVE,OVRWRT/
KDSS=SAVE,OVRWRT/KDAA=SAVE,OVRWRT/KDMG=SAVE,OVRWRT/
KDLL=SAVE,OVRWRT $
alter 'call sekdr '(,-1)
dbdelete datablk=(kdaa,kdmg,kdsf,kdjj,kdgg,kdss,kdelm,kddict) ,
where(wildcard) $
endalter
40545
2001
- Traceback in IFS6P
It has been observed on Cray computers that DEQATN input that exceeds 10000
characters can cause NASTRAN to fail during the processing of the input bulk
data deck. This is well below the 32000 character limit that is documented.
Symptons are erroneous echos of the deqatn input and a traceback in the log
file which includes subroutines PRERR2 and IFS6P.
Avoidance: Run on a computer other than the CRAY. Reduce the number of
characters in a DEQATN to less than 10000. In Version 70.7 a DRESP2 can
reference a DRESP2 so that a single DEQATN could be broken up into a string of
DEQATN's.
40547
2001
P-Elements - Missing Output
If there are both h- and p-elements in the model, and the output requests
differ, for example stress=print for h-elements and stress=print,plot for
p-elements, the p-element output may be missing.
40563
2004
on Units of ROLL, PITCH and YAW
Documentation/QRG - AESTAT - Add Remark
Table 1 of the description of the AESTAT bulk data entry in the Quick Reference
Guide states that ROLL, PITCH and YAW are urdot(R1), urdot(R2) and urdot(R3).
It might be incorrectly concluded that the units are rad/s. Actually, the
examples given in the Aeroelastic User's Guide as well as the more detailed
description in the seminar notes show that normalized roll, pitch and yaw rates
have to be input, i.e. ROLL = pb/2V, PITCH = qc/2V and YAW = rb/2V. A remark
should be added which explicitly states this.
40564
Description
2004
Documentation/QRG - AUNITS - Incomplete
The Quick Reference Guide description of parameter AUNITS should be replaced by

the clearer description from the seminar notes:
"Accelerations are divided by this parameter. To convert accelerations input in
g's into physical, consistent units, set AUNITS to 1/g."
40565
2001.0.1
- Wrong Sensitivity Coefficients
Optimization/Sensitivity - PARAM,EIGD,YES
If eigenvector sensitivity is requested (param,eigd,yes) and there is no

constraint in the model (e.g., spc, rbe, etc.), then the eigenvector
sensitivitiy coefficients may be incorrect.
Avoidance: Add a dummy grid point and constrain the dummy grid point or apply
the following dmap alter:
compile eigvecds
alter 'ssg2'(,-1)
if (omit = -1 and nomset = -1 and single = -1 ) then
equivx fg/ff/always $
else $
alter 'ssg2'(,6)
endif $ no spc, mpc or omit
40579
2004
erty Name for 12I/T**3
Documentation/QRG - DVPREL1 - PSHELL Prop
The DVPREL1 entry has the ability to reference property field id names;
however, the PSHELL id field 12I/T**3 and other fields that begin with integers
can not be referenced in this manner.
Avoidance: Refer to the field by the field position.
40582
2001
OFTEXIT,YES - UFM 2109 in DPD
Design Sensitivity/Optimization - PARAM,S
The message:
will be issued from the DPD module with an accompanying "NO GRID, SCALAR, OR
EXTRA POINTS DEFINED." when PARAM SOFTEXIT set to yes.
Avoidance: Do not specify PARAM SOFTEXIT YES
40620
2001
PARAM,SOFTEXIT - UFM 4276 EC 3001
Optimization/Design Sensitivity - DSAPRT,
When an optimization task includes the DSAPRT formatted request and

PARAM,SOFTEXIT,YES it may fail in subroutine dr2dx with the message
SYSTEM FATAL MESSAGE 4276 ERROR CODE 3001.
Avodiance:
1) Use either dsaprt(unformatted,...) option or use optexit=4.
2) Use the following dmap alter (for Version 70.7)
compile desopt
alter 'l exitopt'(8),'l exitopt'(8)
CALL EXITOPT XINIT,DESTAB,HIS,,,R1TABRG,RSP2RG,DRSTBLG,
FOL1,TOL2,FRQRPRG,DPLDXI,CONSBL,R1VALRG,R2VALRG,
DSCMG,DEQATN,PLIST2,DEQIND,DXDXIT,DCLDXT,DVPTAB,TABDEQ,
R1MAPR,R2MAPR,DPLDXT,EPTTAB,DBMLIB,,,PROPI,PROPO,,,,,
CASEXX,EDOM,MTRAK,HISADD,WMIDG,dnodel,rr2idrg,EPT,MPT,GEOM2/
DOM11SCR/
CNVFLG/
40628
Nonlinear Analysis - CROD, TEMP(LOAD) - Wrong Stress Results
for Linear Elements
If a thermal load is applied in one subcase in a nonlinear analysis and then is
removed in a subsequent subcase, the total thermal load is removed in one step
from linear elements. This may lead to incorrect stresses for intermediate
output. The output at the end of each subcase is correct.
Avoidance: Insert MATT1 for the linear element using a constant property, then
the stress will be correct for the linear elements at the immediate output.
40644
rrect Results
2001
SSSALTERs - alter1ha and alter2ha - Inco
It is possible that the results (printed output) from alter2ha may be

incorrect. This results from the internal sort of the exterior (connecting) dof
being different between the alter1ha run and the alter2ha run.
Avoidance: Verify that the exterior dof are in the same order between the runs
or request an ujpdated version of the alters for V70.7 (also available on the
MSC web page).
40647
SDR1
2001
Loads - DMIG UACCEL, SPCFORCE - UWM 3059
In Version 70.7, when using DMIG UACCEL to apply inertia loads in SOL 101 and
SPCFORCE = ALL is specified, the following error may occur:
*** USER WARNING MESSAGE 3059 (SDR1)
SET IDENTIFIER DOES NOT EXIST. ERROR DETECTED IN SUBROUTINE GETBOL
0FATAL ERROR
Avoidance: Either use GRAV/RFORCE to apply the loads, or remove the
SPCFORCE=ALL case control.
40667
2001.0.1
OM) Insufficient Memory for RAND5A
Random Analysis - SFM 3008/SWM 3002 (RAND
If SORT2 output is requested, and PSDF, ATOC, or RALL output are requested, and
the SET being used has a THRU range, the RANDOM module will fail with SFM 3002,
indicating insufficient memory.
Avoidance: This only occurs if all 3 of the above are done simultaneously.
Removing the SORT2 request or using a SET which does not contain a THRU will
allow the problem to run.
40670
2001
P-elements - Missing Output
If the p-element output requests are varied by subcase, for example stress only
for the first subcase and stress and displacement for the second, the output
for the earlier subcases may be missing and/or mislabeled.
Avoidance: An avoidance is to request the same output for all subcases.
40685
Systems
2001
Plotting - IFP1 - Access Violation on NT
When requesting XYPLOT output, several commands require that an equal (=) sign
be used. On NT systems, if any of these commands (XTGRID for example) do not
have the equal sign, the program will fail with an access violation in IFP1.
On other systems, it will terminate with "USER FATAL MESSAGE (IFP1X) 676 IS
NOT RECOGNIZED ON ABOVE CARD"
Avoidance: Be sure to include the equal sign on the appropriate commands.
40686
g Answers
2001
Acoustic Analysis - RLOADi, ACSRCE - Wron
If solution 111 is run with multiple subcases loading the fluid structure, all
loading on the fluid structure is lost after the first subcase.

$ begin lost loads fix
compile freqrs,list $
alter 'MATMOD FOL' $
if (ncol > nfreq) then $
$
$
ensure that omega contains nfreq for all subcases
$
file omegax=append $
type parm,,i,n,nsols $
nsols = ncol/nfreq $
trnsp omega/omegat $
do while (nsols > 0) $
append omegat,/omegax/2 $
nsols = nsols - 1 $
enddo $ (nsols > 0)
delete /omega,,,, $
trnsp omegax/omega $
endif $ (ncol > nfreq)
$ end lo
40700
Superelements - SWM 6065 (DBC), UWM 4698 (DCMPD)
When using PART superelements (BEGIN SUPER), error messages 6065 and 4698 may
use internal numbers, rather than the original ids, to identify GRID points.
*** DBCMSG ERROR MESSAGE 19 FROM SUBROUTINE DBCEQG
EXTERNAL GRID ID 2000000334 DOES NOT MEET UPDATE ASSUMPTIONS, CHECK
MODEL BEFORE PROCEEDING.
Avoidance: To guarnatee a specific order boundary grids are biased with the
value of system cell 223. The default value for this system cell is
2,000,000,000. Subtracting this value from the value identified in the message
will obtain the external grid id.
40725
2001
Strains overwrite Stress in XDB
P-elements/Postprocessing - PARAM,POST -
When stress and strain output is selected in an analysis with P-Elements, the
P-Element strains will over-write the P-Element stresses on the xdb file.
Avoidance: When saving P-element stresses on the xdb, make stress requests
only. Strain can be saved when no stresses are requested but will be
identified incorrectly on the xdb.
40732
2001.0.1
ing Fatal Message, Wrong Answers
Acoustic Analysis - CHACAB, CHACBR - Miss
The CHACAB and CHACBR elements are structural elements and all faces must
connect to structural points. The face on the fluid side should connect to
structural grids that have all degrees of freedom constrained (spc'd) except
the dof that is normal to the fluid. These grids should coincide with the
fluid grids but be separate from them. If the fluid side of the element
attaches directly to fluid points a bad solution will result with no warning.
This can happen when both the CHACAB or CHACBR element and the fluid points are
in the residual.
40733
2005.5
Missing ESE Results
Postprocessing/Buckling - PARAM,POST,0 -
In a solution 105 buckling analysis the Element Strain Energy results are
written to the xdb file for the static subcase but not the buckling subcase.
From the attachments and data base content I believe this problem no longer (
and possibly never ) existed from a XDB perspective. kkk
40734
2004
Superelements - SEBNDRY and SECONCT with
THRU - UFM 315, Wrong answers, UFM 6782
The THRU format on the SEBNDRY and SECONCT Bulk Data entries causes various
failures or wrong answers:
1. THRU ranges on SEBNDRY continuation entries cause UFM 315.
2. The second THRU range on the SEBNDRY parent entry is ignored
with no warning or fatal message issued and produces wrong answers.
3.
Multiple SEBNDRY entries causes UFM 311.
4. THRU ranges with gaps in numbering on the SECONCT entry causes UFM 6782.
Avoidance: For SEBNDRY use only one THRU range. For SECONCT, specify separate
THRU ranges without any gaps.
40773
2001.0.1
- SIGNAL 11 ERROR, access violation
Miscellaneous - ASSIGN, OUTPUT2, OUTPUT4
If there are many output2/output4 assign statements, then depending on the

machine, the job may fail with any one of the following messages:
SIGNAL 11 ERROR
MAIN: For reference, A(MAINAL) = 428ce0, A(/SYSTEM/) = 1781f80
MAIN: Exception occurred at address 005A04DD.
MAIN: Program attempted to store data at location CB31AF28.
Avoidance: Removing one or two of output2/4 statements avoided the error in
this case.
40805
2001
ct Eigenvectors for Component Modes
Superelements - PARAM,FIXEDB,-1 - Incorre
If output is requested for component modes using PARAM,FIXEDB,-1 and C- or

R-set degrees of freedom exist, the output eigenvectors and eigenvalues printed
will be incorrect. Note that all other output will be correct.
Avoidance:
Insert the following alter into SOL 103 to correct the problem.
compile semodes
alter 1
putsys(0,192)
$
compile super3
alter 'call.*sedisp.*cmpho',''
type db,cmpho0,cmlama0
CALL SEDISP,
GOT
,GOQ
,LOO
UOX
,USET
,PJ
CASESX ,CASEDR ,ULS
GM
,PSS
,KFS
CMPHO0 ,OL1M
40821
ong answers
,LAO
,UL
,EDTS
,KSS
2001
,UOO
,CRJ
,YS
,QR
,
,
,
,
Superelements - BEGIN SUPER, RESTART - Wr
When using part (BEGIN SUPER) superelements with any type of RESTART then the
data recovery may be incorrect.
Avoidance: Insert a dummy (unreferenced) FORCE Bulk Data entry in the main
Bulk Data section of the restart run.
40826
DMAP -- OUTPUT2 with MATRIX neutral format - Wrong answers
On short-word computers (all except Cray and Nec), if OUTPUT2 is used to

output a single precision matrix in neutral format then the INPUTT2 of the
neutrally formatted matrix will produce wrong answers.
Avoidance: Use the ADD or ADD5 module to convert the matrix to double
precision before passing it to OUTPUT2.
40831
7 (NLTRD2)
Nonlinear Transient Heat Transfer - UWM 6137(UDSNRD), UFM 300
If a nonlinear transient heat transfer analysis, solution 159, model has extra
grid points that are not attached to any elements and are not constrained, then
the job may fail with the message:
*** USER WARNING MESSAGE 6137 (UDSNRD),
0*** UNSUCCESSFUL MATRIX DECOMPOSITION.
7816 IERROR
*** SYSTEM FATAL MESSAGE 3007 (NLTRD2)

Avoidance:
Use the following alter:
compile nltran
alter ' kjjnl, '
trnsp kjjnl/kjjnlt $
add5
kjjnl,kjjnlt,,,/xxx//-1. $
norm
xxx/////1/s,n,xnorm $
if ( xnorm<=1.d-6 ) modtrl kjjnl////6 $
endalter
1) Rerun the model using SOL 101 with APP HEAT and insert PARAM,SPCGEN,1 in
the bulk data section. The PARAM,SPCGEN,1 entry will cause constraint entries
for the unattached extra grid points to be written to the punch file and these
constraint entries can be subsequently used in solution 159.
2) Rerun the tran
40839
2004
ficient Restart or SFM 4252
Documentation/QRG - RESTART, DMIG - Inef
Restarts with DMIG entries may unneccessarily re-process the entire model even
though no changes to the input have occurred. The way to verify that this is
happening is to run with DIAG 56 and to look in the .f04 file for "changed" and
"DMIG" on the same line. If these words occur on a line output by the RESTART
module, the program will re-run the entire model.
Avoidance: This is currently a limitation of the sort routines used in
Nastran. Other potentially problem entries include BNDFL, DMIAX, ELIST, DMIAX,
ELIST, MFLUID, RADLIST, and RADMTX. If there are no changes to any BNDFL,
DMIAX, DMIG, ELIST, MFLUID, RADLIST, and RADMTX entries, then insert the
following alter to disable the checking for changes in these entries.
compile ifpl
alter 'restart.*matpool',''
message //'re
40843
Beam Library - PBARL, PBEAML - SFM 6498 on Large Models
A very large model with PBARL or PBEAML entries may fail with the following
error messages:
*** SYSTEM FATAL MESSAGE 6498 (Beam Lib, allocate_Master_Buffer)
API MESSAGE FOLLOWS.
USER INFORMATION: Memory Limit exceeded.
Could not allocate Memory for the Main Buffer Pool!
MSC.Software has not been able to duplicate this error and the model that
causes this error is confidential. The client model contains over 1.3 million
entries, but only a few PBARLl entries.
Avoidance: There are three possible avoidances.
1. Replace the pbarl/pbeaml entries with equivalent pbar and pbeam entries.
2. Allocate more memory.
3. Run the job on a non-Cray computer since Cray computers require more
memory.
40874
2005.5
ssage, UFM 4016 (GETEMP)
Heat Transfer Analysis - NLCOMB - Poor Me
In Version 70.7 Heat Transfer analysis the following message indicating that
there is missing TEMP entry data will be output for any point with an SPC
constraint that does not have a corresponding TEMP entry.
USER FATAL MESSAGE 4016 (GETEMP)
THERE IS NO TEMPERATURE DATA FOR ELEMENT
FATAL ERROR
8127187 IN SET
Avoidance: Check all the grids with SPC constraints and ensure that there is a
corresponding TEMP entry.
Developer's comments:
The code has been fixed in v2005t1 to avoid the fatal messages. (7/7/05)
40892
2004
Documentation/QRG - PBEAM
The following remark should be added to the Quick Reference Guide description
of the PBEAM entry:
Remark 13:
In nonlinear analysis the location of the 8 plastic rods is the same on the
PBEAM as on the PBCOMP SYMOPT=0.
40909
2001
T - Missing Plot Output
Documentation/QRG - SEUPPLOT, SEPLOT, PLO
Starting with Parts superelements in Version 69 each PLOT command requires an

SEUPPLOT or a SEPLOT command. This requirement and an example should be noted
under the Nastran Quick Reference Guide PLOT command description.
An example follows:
some general plot commands such as VIEW etc.
SEPLOT 10
FIND SCALE ORIGIN 1 SET 1
PLOT SET 1 ORIGIN 1 $ SYMBOL 1 LABEL GRID
SEUPPLOT 0
FIND SCALE ORIGIN 1 SET 1
PLOT SET 1 ORIGIN 1 $ SYMBOL 1 LABEL ELEMENT
40910
tput
Nonlinear Transient Analysis - RESTART/CGAP - Missing CGAP Ou
If a nonlinear transient analysis restart run adds a request for CGAP element
force/stress output the output may be missing.
Avoidances: Request the output in a cold start run.
40934
2001
PBEAML - Illegal input to DPNCH6
When both PBARL and PBEAML entries are included in an optimization task, the
job may fail in routine dpnch6 with a SYSTEM FATAL MESSAGE indicating illegal
input to subroutine dpnch6.
Avoidance: Set PARAM,DESPCH,-1
40936
2001.0.1
Documentation - Missing Output, UFM 316
The Nastran Quick Reference Guide does not specify a limit for element
identification numbers. With the large field format 16 digits may be specified
but id's greater than 8 digits may result in missing output or USER FATAL
MESSAGE 316. In Version 2001 a limit of 8 digits will be enforced.
Avoidance: Do not specify element ids that are greater than 8 digits.
40937
UWM 4203
2001
Miscellaneous - SPOINTs, SEP1 - SWM 4203,
If a model has superelements and contains more than 32,000 SPOINTs the run may
fail after issuing SYSTEM WARNING MESSAGE 4203 and USER WARNING MESSAGE 4203,
indicating that the SEMAP datablock has been marked as non-executable in SEP1.
Avoidance: If possible use GRID points in place of SPOINTs.
40953
2001
- No Message, Traceback in dopr3m
Optimization/Design Sensitivtiy - DRESPi
If a DRESP2 entry references a DESVAR, DRESP1, DNODE, or DVPRELx with ID =

11000. The job will fail in the DOPR3 module. The traceback from the log
file follows:
Signal received: SIGSEGV - Segmentation violation
Traceback:
Offset 0x000002e4 in procedure
Offset 0x000009ac in procedure
dopr3m_
dopr3_
xsem03_
xsemdr_
nastmon_
mainal
Avoidance: Specify another DRESP id.

40974
2001.0.1
- Wrong answers
Superelements - part superelements, SNORM
If PARAM,SNORM or the SNORM Bulk Data entry is specified with part

superelements or BEGIN SUPER and main Bulk Data superelements, then wrong
Avoidance: Insert PARAM,SNORMPRT,2 or 3.
40990
Damping
2001.0.1
Superelements - PARAM,SESDAMP - Incorrect
If param,sesdamp,yes is used, then superelement component modes will have modal

damping applied based on the SDAMP command in each superelement's SUBCASE. The
residual structure will use the SDAMP command in the first residual structure
SUBCASE, unless there is none, in which case it will use the last SDAMP called
in a superelement subcase, which may result in unexpected damping in the
solution..
Avoidance: To be safe, if using PARAM,SESDAMP,YES, always explicitly specify
SDAMP in the residual subcase. If zero damping for the residual is desired,
SDAMP should refer to a TABDMP1 with 0.0 damping.
41009
is ignored
2001.0.1
P-Elements - PBEAM - Non-structural mass
For beam p-elements, the non-structural mass (NSM) on the PBEAM bulk data entry
is ignored.
Avoidance: An avoidance is to adjust the density to account for the
non-structural mass.
41020
2004
Optimization/Design Sensitivity - CSUPER
- SFM 3007 (MTRXIN)

If external superelements are used in optimization, and DESMAX has a value
greater than the number of cycles required to converge, and the run is not
saving the database (i.e. scr=yes), the run may fail with the following
message:.
SYSTEM FATAL MESSAGE 3007 (MTRXIN)
ILLEGAL INPUT TO SUBROUTINE MTRXIN
FATAL ERROR
Avoidance: Either set DESMAX to the number of cycles required to converge or
run with SCR=NO on the submittal.
41021
2001.0.1
Aeroelastic Analysis - APD - SFM 4276
If an AEFACT entry has a duplicate station defined, then the APD module fails
with a floating point exception.
Avoidance: The avoidance is to remove or correct the duplicate station
specification.
41034
2001.0.1
P-Elements - OUTPUT - Wrong Answers
If the output requests specified by the DISPLACEMENT, VELOCITY, and

ACCELERATION case control commands are different from the corresponding output
requests on the OUTPUT bulk data entry, then the output may be incorrect.
Avoidance: The only avoidance is to make sure the output requests are
consistent.
41036
2001.0.1
Miscellaneous - CORDi - UFM 6915 (GP1C)
When defining a coordinate system in MSC.Nastran, three non-colinear points are

required. If the dimensions of the three points are such that there are more
than 15 orders of magnitude difference between them, the program may
incorrectly issue the message:
indicating that the points are colinear.
Avoidance: Use 3 points which have locations within 10 orders of magnitude of
each other when defining coordinate systems.
41039
PHA
2001.0.1
DMAP - DRMH1 - SFM 4276 EC 7777 on DEC AL
Use of the DRMH1module to generate transfer matrices for certain element types
may cause an underflow to occur. Subsequent use of the matrices will generate
the following error on Alpha machines:
*** SYSTEM FATAL MESSAGE 4276 (tbk)
ERROR CODE
7777 PID= 0
Avoidance: This error appears to occur only on Compaq Alpha Unix systems. If
possible, try running on a different type of computer.
41050
2001
Distributed Memory Parallel - RBEi, DMP,
SEQP - Traceback in SEQP

If a Distributed Memory Parallel, DMP, run contains rigid elements or mpc
equations with many dependent degrees of freedom, then the job may fail in the
SEQP module with the following traceback:
Traceback:
Offset 0x000006d4 in procedure
Offset 0x00000f0c in procedure
seqcon_
seqmpc_
seqp_
xsem02_
xsemdr_
nastmon_
mainal
Avoidance: Increasing memory may allow the job to execute but there may still
be a performance penalty that makes Distributed Memory Parallel undesirable for
models with a large number of depen
41057
Nonlinear Analysis - PCOMP, TEMP(LOAD) - Wrong Answers
A nonlinear analysis with temperature loading applied to composite elements

where the PCOMP specifies an unsymmetric thermal coefficient expansion in the
1 and 2 direction results in wrong answers.
41059
nt Exceptions
2001.0.1
Aeroelastic Analysis - AMG - Floating Poi
The above error can result when using Strip Theory aerodynamics with a
Prandtl-Glauert correction to the lift curve slope (CLA < 0) and a supersonic
Mach number is chosen on a MKAEROi entry. This is because the correction
involves computing a term of the form sqrt(1.0 - M**2); i.e., taking the square
root of a negative number
Avoidance: If strip theory is to be used with lift curve slope corrections, use
CLA > 0
41061
WK - UFM
2004
Nonlinear Analysis - PLOADX1, PARAM,FOLLO
The follower stiffness for PLOADX1 is incorrect. This could cause some
nonlinear static problems in SOL 106 to diverge.
Avoidance: Turn off the follower stiffness by specifying param, followk, no.
41065
answers
Heat Transfer Analysis - VIEW Factor using CQUAD8 yields poor
The calculation of the VIEW factors for CQUAD8 elements for curve surfaces such
as cylinder and sphere in heat transfer analysis yields poor results when
compared to the CQUAD4 element.
Avoidance: Use the CQUAD4 element.
This quality is cancelled because the answere of CQUAD8 elements are close to
those of CQUAD4 elements
in v2005. The view factor calculations of mid-side nodes have been improved in
v2004. (8/18/04)
41066
2001
olution Sequences
Documentation - PARAM FOLLOWK - Missing S
The Version 70.5 Quick Reference Guide description of PARAM,FOLLOWK does not
include all applicable solution sequences. The description should read:
In Sols 103, 105, 106, 107, 108, 109, 110, 111, 112, 115, 116,
FOLLOWK=YES(default) requests......
and on the fourth line:
For FOLLOWK=YES in Sols 103, 105, 107, 108, 109, 110, 111, 112, 115, and 116 a
separate static subcase is required .......
41069
2001
RESVINER - SFM 5423 (DMPYAD)
Distributed Memory Parallel - DMP, PARAM,
MSC.Nastran Version 70.7 with DMP with PARAM,RESVINER,YES fails in SOL 111
with:
compile resvec
alter '\/paa',''
dbstatus vafs//s,n,novafs $
if ( novafs>0 ) then $
merge
mxx,,,,vafs,/mxx1 $
else $
equivx mxx/mxx1/-1 $
endif $
mpyad
mxx1,dga,/paa $
endalter
41071
EL,-2
2001.0.1
Inertia Relief - Enhancement to PARAM,INR
An inertia relief option based on measuring deflections from a body-based

coordinate system was introduced in Version 70.5. It is requested with param,
inrel, -2. This method uses constraint equations that cause deflections to be
measured from a coordinate system tied to the model's center of gravity. In
Version 70.7 the rigid body modes used to generate the constraint equations are
based on shapes made by moving a point at the basic origin through 6 unit
motions. Revision 1 of the ir2a.v707 sssalter package for improved efficiency
(dated 2 Jan 2001) now has the modes calculated around the grid point specified
on the param, grdpnt entry. The default action of this parameter is to use
the basic origin, as before. This change is in the revised sssalter package on
the MSC web site, an
41109
2001.0.1
Eigenvalue Analysis - EIGRL - Extra Roots
Some small eigensolutions compute extra roots by repeating one of the roots and
its eigenvector. This tends to cause fatal exits in the dynamics solvers such
as frrd1 and trd1.
Avoidance: Use the AHOU method. In MSC.Nastran 2001 Lanczos automatically
switches to a QLHOU method for problems with less than 20 degrees of freedom.
Thus, this and other difficulties that Lanczos has with small problems are
considered fixed.
41133
Strain Output
Nonlinear Analysis - PCOMP, PARAM.LGDISP - Missing Composite
Homogenous composite strain output will be missing in nonlinear analysis when

param,lgdisp,1 is specified.
Avoidance: Request STRAIN output in case control. Also request STRESS for at
least one element and apply the following alter:
compile nlstatic
alter 'sdr2.*oesxc'
SDR2
CASESX2,CSTMS,MPTS,DIT,EQEXINS,,
ETT,EDTS,BGPDTH,,,UGNI,EST,,,,,GPSNTS,
DEQATN,DEQIND,/
,,,OESXd,,/'GNST'//3 $
ofp oesxd/ $
41137
input matrices.
Eigenvalue Analysis - EIGRL - Lanczos unreliable for diagonal
The Lanczos method gets eigenvectors with poor orthogonality when there are
repeated roots, and both the mass and stiffness matrix are diagonal. On some
occasions these matrices can also cause overflow exits. Diagonal matrices
occur most commonly on research efforts when using dmap.
Avoidance: Use the AHOU method instead.
41142
2005.5
INTs - UFM 4156 (SEMA)
Parts Superelements - SELOC, Exterior SPO
If SELOC is used to locate a parts superelement that has exterior degrees of

freedom that include generalized coordinates that are defined by spoints and
qset1 entries, then the run may fail in the SEMA1 module with the following
message when the superelement is attempted to be attached to the residual:
*** USER FATAL MESSAGE 4156 (SEMA)
DIMENSIONS OR TYPE OF DATA BLOCK SCRATCH , SUPERELEMENT
10
TRAILER=(
72
INCONSISTENT WITH SUPERELEMENT MAP.
FATAL ERROR
72
18
662) ARE
Avoidance: The error occurs because the program assumes every scalar point has
six degrees of freedom. The error may be avoided by using the internally
generated q-set DOFs with the SENQSET entry. Remov
Note still errors at 70.7.2, however works from 2001.0.1 forward.
41146
2001
=2 on eigrl causes fatal exits
Eigenvalue Analysis - EIGRL - maxset=1 or
The number of vectors in a block for the LAN method is controlled by the maxset
input (field 7) on the eigrl entry. When set to any explicit value, several
classes of small problems have been observed to fail, with diagnostics
including floating point overflow, lnherr subroutine errors., and other obscure
diagnostics. Examples include those with Lagrange Multiplier variables and
those with diagonal input matrices.
Avoidance: Use the default value for maxset (leave it blank), or use the AHOU
method.
41152
Nonlinear Analysis - PARAM,SNORM - Slow Convergence
Dave, Sounds like a limitation that we should document. --Mike

When net rotations of shells become large in Sol 106 or Sol 129, some examples
have shown that convergence is slower in Version 2001 than in 70.7. This is
caused by shell normals which are turned on by default in 2001. Convergence can
improve by turning shell normals off (PARAM, SNORM, 0.).
Test files reside in /home/shl/vvpr/v25587/nlctire*. This information is
available in scopus, but not in Siebel.
41164
SFM 1012
2001.0.1
File Management Section - EXPAND, INIT -
Allocating too much space to scratch files may lead to poor messages such as;
"SPECIFIED RECORD IS BEYOND MAXIMUM FOR THIS FILE SYSTEM" or
"DBSET SCRATCH IS FULL AND NEEDS TO BE EXPANDED.
USER ACTION: USE FILE MANAGEMENT STATEMENT "EXPAND" FOR THIS DBSET."
Avoidance: The diagnostic stating to use EXPAND FMS statement is applicable
only to restarts. The user is referred to the Version 2001 Installation and
Operations Guide or tan 4893 on the msc web site for methods to make larger
databases.
41165
Eigenvalue Analysis - EIGRL - Possible Wrong Answers
If f1 is specified as 0.0 on the EIGRL entry and the model contains a "large
mass" for enforced motion the run may produce poor answers.
Avoidance:
41178
Leave f1 blank.
Parts Superelements - SEP1X - WM 6795, SFM 6790
If a PART superelement does not have any attachment points between it and the
rest of the model, the program will correctly issue SWM 6795, but may
incorrectly issue SYSTEM FATAL MESSAGE 6790 (SEP021) followed by an incorrect
list of superelements.
Avoidance: Be sure that PART superelements have points which connect to the
rest of the model.
Related to 35778, Corrected message content at 2004 under 1-4266901. kkk
41192
2001.0.1
i - Poor Efficiency
Nonlinear Analysis - PARAM,FOLLOWK, PLOAD
In most cases the formulation used for follower

unsymmetrical matrix. Since the default value
SOL106 most problems with pressure loads will
stiffness unless param,followk,no is specified.
inefficient solution.
stiffness results in an
for parameter FOLLOWK is yes in
have an unsymmetrical
This may lead to an
Avoidance: If the follower force effects are not great, a more efficient
solution may be achieved by setting PARAM,FOLLOWK,NO.
41198
2001
,RESVEC - SFM 6424 (DFNSB)
Modal Transient Response - SUPORT1, PARAM
If a modal transient response analysis has a static preload, a SUPORT1 entry,

and PARAM,RESVEC,YES is specified, the run may fail with :
SYSTEM FATAL MESSAGE 6424 (DFNSB)
THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE
INCOMPATIBLE
followed by:
*** USER FATAL MESSAGE 5423 (SMPYAD)
ATTEMPT TO MULTIPLY OR ADD INCOMPATIBLE MATRICES
Avoidance: Insert the following alter into your file:
compile resvec, list
alter 'SSG3.*LXX,,KXX,PX3,,,,,/UX1'(,1) $ 144
PARAML USET//'USET'//////'r'/S,N,NOxSET $
41215
tion in TRNSP
2001.0.1
DMAP - TRNSP, APPEND - Segmentation Viola
The APPEND module will append incompatible matrices and this may cause problems
in subsequent modules including a segmentation violation in TRNSP module.
Two steps have been taken to address this problem in MSC.Nastran 2001. First,
the following warning message is issued:
*** USER WARNING MESSAGE 5423 (APPEND)
ATTEMPT TO APPEND INCOMPATIBLE MATRICES
ID
COLS ROWS FORM TYPE
NZWD DENS
TRAILER FOR X
IS
101
20
30
TRAILER FOR Y
IS
102
40
10
60 10000
20 10000
Second, the program will select the greater number of rows for the output
matrix. For example if APPEND is requested to append a 10X40 matrix with a
30X20 matrix ins
41221
fficient Space
Distributed Memory Parallel - DOMAIN, dmp - Job Hangs if Insu
Distributed Memory Parallel jobs, dmp=n, executed on Sun systems may hang if
insufficient space exists. Currently, this is a limitation of the Sun MPI
implementation but this problem may also exist on other machines.
Avoidance: The only avoidance is to provide more space.
41237
2001.0.1
1 - Floating Point Exception
Aeroelastic Analysis - GI, SPLINE1, CAERO
If a SPLINE1 with the FPS option is used to connect a CAERO1 that only has one
spanwise box, then a floating point exception may occur in the GI module. This
error will also occurs if the spline connects to a chordwise strip of elements
on a CAERO1 that is 1 spanwise box wide.

Avoidance: Split the CAERO1 entry so that it has two span wise boxes, or use
the IPS option on the SPLINE1.
41241
2001.0.1
lt, Signal 11, Alpha Only
Miscellaneous - SMPYAD - Segmentation Fau
On Alpha platforms, large runs may fail during a SMPYAD operation with a
message in the log file:
Job aborting..
Avoidance: There are 2 possible avoidances either replace the SMPYAD in the
dmap with 2 equivalent MPYAD's, or set NASTRAN SYSTEM(129)=1. This error has
been corrected in the dot3rd kernel in Version 70.7.4 and 2001. Version 70.7.4
was not made available until after 2001 was released. It is available on
special request only.
41243
nput, SFM 6830
2007.0.1
DMAP - SOLVE does not exit when illegal i
The solve module requires a square input matrix when used for the matrix
inverse function. If it is given a rectangular matrix it issues a system fatal
message, but continues with no output and this may lead to SYSTEM FATAL MESSAGE
6830.
An avoidance is to test for the presence of output:
solve s,,,,/sinv/3 $
paraml sinv//'presence'////s,n,nooutp $ error avoidance
if (nooutp=-1) then $
message //'user fatal message. Solve failed due to illegal input' $
matprn s// $
exit $
endif $
41257
ra Output
2001.0.1
Complex Eigenvalue Analysis - OFREQ - Ext
OFREQ feature does not work for solution output requests in complex eigenvalue
analysis
41260
2001.0.1
Frequency Response - FRRD1 - SFM 3001
If the model in frequency response does not have any stiffness, the program
will fail in FRRD1 with SFM 3001 indicating that executive file 0 does not
exist.
41269
2001.0.1
Arithmetic Trap in gmtstd
Elements - SYSTEM(218) - SFM 4276 (tbk) ,
Setting SYSTEM(218) to a real number may cause an arithmetic trap in routine

gmtstd on some machines.
Avoidance: Use the keyword "T3SKEW" instead.
verif 1/2/02 abb.
41276
Lagrange Multiplier Technique - Wrong Answers
When using enforced velocity in transient analysis with the Lagrange

Multiplier approch, the LMT variables may show an instability. This appears as
a high frequency signal at the forcing variable only. If this is encountered,
contact MSC, and ask for details on residual mass. Mention this Client Service
Request Number (41276).
41280
er
DMAP - DIAGONAL - Module DIAGONAL may give a bad matrix trail
If a rectangular matrix (form=2) is processed by the DIAGONAL module using the

'SQUARE' option, the output matrix will have an incorrect trailer (form=6)
indicating that it is symmetric, when it should be rectangular(form=2).
Avoidance: If the input matrix to DIAGONAL is rectangular and the 'SQUARE'
option is specified, use MODTRL to update the trailer.
41301
tput
2001.0.1
Transient Analysis - GPSTRESS- Missing Ou
If GPSTRESS output is requested in SOL 112 in Version 70.7, there will be no

corresponding output created.
compile sedrcvr
alter 'call gpstress'(2),''
call gpstress postcdb,BGPDTN,ECTS,est,CSTMS,estnl,casedr,
eqexins,oes1x,oesnlx,ostr1/
egpsf,ogs1,egpstr,oeds1,ogds1,eldct,gpdct,
ogstr1,egpstra/
app/otape2/statics/app $
endalter
41302
ers
2001.0.3
Aeroelastic Analysis - CAERO - Wrong Answ
An error exists in the recovery of nodal aero mesh data (like OPPHIPA in Sol
145) if the CAERO ID's do not allow enough spacing for unique mesh point node
id's (element IDS must be unique, but node ids are allowed to be non-unique for
backward compatibility). In the case of non-unique nodes, the aero mesh data
should NOT be recovered. Instead, it is recovered but the results are
nonsensical. DBC may give warnings or fatal messages.
41308
Strains
2001.0.1
P-Elements - DDRMM - Incorrect Principal
For solid p-element dynamics in SOL 112 (modal transient), the principal
strains calculated with DDRMM are incorrect.
Avoidance: A workaround is to turn DDRMM off by setting param,ddrmm,-1.
41319
Nonlinear Analysis - BUSH1D - Wrong Answers for a Stepped For
ce-Deflection Curve
If a BUSH1D element references a TABLED1 that defines the force-deflection
curve in descending order, wrong answers will occur in nonlinear analysis.
Avoidance: Do not define the tabled1 for the bush1d in the descending order
If a TABLED1 is refered by a CBUSH1D element in nonlinear analysis, two

restrictions apply.
1. If TABLED1 values are defined in descending order, the results of the
CBUSH1D element are wrong. The x values of the x,y pairs must be in ascending
order. If the pairs are defined in descending order, the table values are
ignored.
2. If jumps are defined in the TABLED1 entry, the results of the CBUSH1D
element are wrong or the solution does not converge. It is recommended to
define a steep slope instead of a jump.
The slope shou
41335
2001.0.1
Material Damping Ignored
Nonlinear Analysis - Complex Eigenvalue -
The calculation of complex eigenvalues in SOL 106 does not include the effect
of structural damping defined by Ge on the material entries.
Avoidance: Insert the alter:
compile nlstatic
alter 'call semr2'
equivx kllrh/kaa/-1 $
type parm,,i,n,nobggnl=-1,nok4ggnl=-1 $
EMG
MESTNL,CSTMS,MPTS,DIT,,MUGNI,ett,,DEQATN,DEQIND,BGPDTS,
GPSNTS,,,,ditid/
x1,x2,,,belmnl,bdictnl/
-1/0/s,n,nobggnl/s,n,nok4ggnl/NSKIP/
/////////tabs/sigma/K6ROT/LANGLES/NOC//////unsym
41344
Acoustic Analysis - No Fluid to Structure Coupling in Comple
x Eigenvalue Analysis
The fluid/structure interface matrix (A matrix) is not used in a fluid
stiffened structure complex eigenvalue analysis. This results in no
interaction between the structure and the fluid. Thus, wrong answers
41348
Acoustic Analsysis - FORCE, DISP - Missing Pressure Output
When fluid elements are present in SOL 111 and the FORCE= case control is used,
the PRESSURE column in the element ACCEL, VELO, PRESS output has a N/A
incorrectly printed.
In SOL 108 or SOL 111, the COMPLEX ACOUSTIC results are always magnitude/phase
regardless of whether the REAL or PHASE options are used on the PRESSURE= or
DISPLACEMENT= case control commands.
41359
2001
NEi - Unexepected Answers
Documentation/Aeroelastic Analysis - SPLI
The USAGE field of the SPLINEi entries is not clearly documented that the
"BOTH" option is the ONLY one in which a single SPLINEi entry will transform
both loads and displacements (wherein the virtual work transpose of forces to
get displacements is used). Since the set of structural degrees of freedom
appropriate for load application may not be the same set that is appropriate to
represent the important deflections for the aeroelastic correction, the FORCE
and the DISP options allow the the splines to be defined separately. However,
FORCE or BOTH spline must be defined for each aerodynamic box to yield a
"complete" mapping of forces.
It is unusual (but not unheard of) to have aerodynamics for which forces are
not desired (e.g., to impose 2D-like boundary conditions or "infinite
41365
GL
C, RESVINER, INRLM - UFM 9050
Acoustic Analysis - STATSUB, PARAM, RESVE
If the STATSUB Case Control or PARAMs, RESVEC, RESVINER, or INRLM is requested

in a fluid-structure model then the job may fail with UFM 9050.
Avoidance: Specify a SUPORT entry for any grid point in the fluid model.
41379
2004
Poor Message, SFM 4276, EC 7777
Nonlinear Transient Analysis - TSTEPNL -
If NDT on the TSTEPNL entry is incorrectly set to a value less than 3, the
program will fail with a Floating Point Exception.
Avoidance: Specify a value greater than 3 for NDT.
41387
2008.0.0 (MD R3)
nswers for GPWG
Parallel Processing - DMP, GPWG - Wrong A
The GRID POINT WEIGHT GENERATOR output is incorrect in (DMP) Distributed Memory
Parallel solutions.
Avoidance: The only avoidance is to execute a checkout run without dmp.
41389
2001.0.1
- Incorrect DRESP2 Response Output
The print of the DRESP2 response values that are controlled by the P2 parameter
on the DOPTPRM entry may be in error. The error occurs when there are more
DRESP2 values than
the length of the maximum record in the RESP12 datablock (this value is the
second word of the trailer of the RESP12 datablock). The incorrect value that
is printed is not used for subsequent
calculations with the exception that it may get used in calculating the
sensitivities of DRESP2's that reference other DRESP2's. Optimization is not
affected.
41397
2004
DMIG - PUNCH File - UFM 316 (IFPDRV)
If MSC.Nastran is requested to generate DMIG entries, and those entries are

read back into MSC.Nastran on a restart job, then the following error may
occur:
ILLEGAL DATA ON BULK DATA ENTRY DMIG
DMIG *KAAX
7
1
+000001
*+000001
7
1 1.833933289E+01
+000002
The error is a result from the g77 (ecgs) compiler on linux writing double
precision variables with an "E" instead of with a "D"
Avoidance: Edit the DMIG file and change all the E formats to D. This can be
done with "g/E-/s//D-/" and "g/E+/s//D+/" from within "vi"

41408
2001.0.1
DMAP - MATGPR - Illegal Input to MATGPR
The MATGPR module fails with "Illegal input" error messages when attempting to
print matrices that contain the k or ks sets in aeroelastic analysis.
Avoidance:
For matrices that are of size (aero) x (unknown), or (unknown) x (aero),
MATGPR may be made to work by specifying DBVIEWs for the USET and BGPDT similar
to the following:
DBVIEW BGPDTF=AEBGPDTS WHERE (
(MODLTYPE='AEROSTRC') OR
(MODLTYPE='STRUCTUR' AND AECONFIG=AECONFIG
AND SYMXY=SYMXY AND SYMXZ=SYMXZ) ) $
DBVIEW USETFF=AEUSETS WHERE (
(MODLTYPE='AEROSTRC') OR
(MODLTYPE='STRUCTUR' AND AECONFIG=AECONFIG
AND SYMXY=SYMXY AND SYMXZ=SYMXZ) ) $
MATGPR BGPDTF,USETFF,,AEDBQKV//'H'/'K' $
41415
2007.0.0
tiffness Matrix Leads to SFM 4276
Nonlinear Buckling - EIGRL - Indefinite S
In some cases nonlinear buckling analysis may produce an indefinite stiffness

matrix. If this matrix is used in a nonlinear buckling analysis then the job
may fail in the READ module with SYSTEM FATAL MESSAGE 4276 indicating an
overflow.
41417
2001
Beam Library - Endless Error Message
When the server routine for either external beam library or external response
fails due to an unexpected error, the following error message may appear in the
f06 file. However, the SFM 6498 message will be repeated untill the disk space
is filled.
API MESSAGE FOLLOWS.
USER INFORMATION: Server has Crashed.
IpcRead: Read an End-Of-File from the Server
IpcRead: The server has probably Crashed.
*** SYSTEM FATAL MESSAGE 6498(code=32) Invalid Error Code
0FATAL ERROR
Avoidance: Kill the processes for both client and server.
41424
- SFM 5423
2001.0.1
Distributed Memory Parallel - MPCF, SPCF
If MPCForces or SPCforces are requested in a dmp run in SOL 111 then the job
will fail with SFM 5423.
compile semfreq
alter 'if ( not(acms'(2),''
if ( not(acms) and procid>1 and fdmodes ) jump endloop $
endalter
41437
g Frequencies
2004
Frequency Response - PARAM,DFREQ - Missin
Parameter DFREQ is used to determine how the program will filter the loading
frequencies to remove apparent duplications. This parameter is ignored in SOL
108, which may result in unintentional removal of desired loading frequencies.
Avoidance: Insert the following alter in your file:
compile sedfreq
alter 'frlgen ',''
type parm,nddl,rs,y,dfreq $
frlgen dynamics,,/frl0,frli///dfreq $
endalter
41458
2004
next: bad fileposition
Utilities - RCOUT2 - INTERNAL ERROR: buf_
RCOUT on the NT will not work with files larger than 2gb.
This limitation has been removed in Version 2003.
41487
d to Converge
Nonlinear Transient Analysis - Adaptive Time Stepping - Faile
This error no longer exists - dcc

If the thermal conductivity varies as a function of temperature in a nonlinear
transient thermal analysis, the criteria for choosing the adaptive time step
may fail and the job will end without any messages.
Avoidance: Turn off the adaptivity by setting the ADJUST field on the TSTEPNL
card to 0
41490
2001.0.1
message, SFM 3001 or UFM 1126
Aerodynamic Analysis - No Splines - Poor
If an aero model has no splines to the structure then:

1. In V70.7, SFM 3001 will be issued for data block KRZX.
2. In V70.5, SFM 1126 will be issued for data block WGJ.
110595
2004.0.3
Superelements - SELOC, POINT - UFM
POINT entires can not be used to locate a superelement (on the SELOC entry).
If attempted the run will fail.
Avoidance: User GRID entries instead of POINT entries.
110850
bels
69
P-Elements - Missing Output, Incorrect La
The triangular shellp elements produce incorrect point ids in the displacement
output.
Also, stress and displacement output is missing for certain elements in the
patran op2 file.
1-11YIK
2001.0.3
PBEAML, DVPREL2 - Wrong Answers
An optimzation task may produce wrong design sensitivity coefficients when it

meets the following conditions:
1) pbarl or pbeam properties are designed;
2) a DVxREL2 entry is presented.
Avoidance: use PBAR/PEAM to replace PBARL/PBEAML.
116498
5
SOLVIT - BICILL and System Cell(241)=2000 - Traceback in SBUT
The tpl deck it101err when modified to request SYSTEM CELL(241)=2000 and
PRECOND=BICILL on the ITER bulk data entry, crasehd with the following
traceback:
Trap encountered:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
0x0000002c
0x0000100c
0x00000c50
0x00000628
0x000005a0
0x00000964
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
sbut5_
sbvrd_
sitdr3_
solvit_
xsem07_
mainal
--- End of call chain --116508

2007.0.0 (MD R2)
yes in a protected directory
Submittal - ESTIMATE - fails with NASTRC=
If estimate is run in a protected directory and NASTRC is either not specified

or specified to yes, then the
following error occurs:
mayotte <201> msc705t2 estimate smaop
ESTIMATE - (Version 70.5 Mar 16 1998 07:19:15)
*** USER FATAL MESSAGE (nastran.validate_common_keywords)
out=./smaop
(program default)
Alternate output file prefix. If the prefix is a directory,
"/<jid-basename>" is appended. The default is "out=./<jid-basename>".
This directory exists, but is not writable.
*** SYSTEM FATAL MESSAGE (estimate.get_nastran_values)
No usable data was returned by the nastran command:
/msc/msc705t2/solaris/nastran -o smaop
whence=bpool,buffsize,memory,real,realdelta,smemory,version
*** Mar 19 1998 7:47AM *** Joe Griffin ***

1-1R8S9
2001.0.3
FM 1126 in CYCLIC3
Cyclic Symmetric Buckling - STATSUB - U
When running pre-stiffened modes in cyclic symmetry SOL 115 or buckling with
SOL 116, using STATSUB, if scr=no is used, UFM 1126 in CYCLIC3 is issued.
Avoidance: Either run with scr=yes or use the following alter for both SOL 115
and SOL 116.
COMPILE CYCBUCKL
ALTER 'CYCLIC3'(,-1)
DELETE /KKK,,,, $
COMPILE CYCMODE
ALTER 'CYCLIC3'(,-1)
DELETE /KKK,,,, $
ENDALTER
121710
2007.0.1
ect Results for frequency of 0.0.
Direct Frequency Response - ITER - Incorr
Iterative solver produces incorrect results for zero frequency.

124542
Distributed Memory Parallel - Poor Message, SFM 7402 (DFMFRD)
When using DMP, if each processor does not have at least one internal and one
external dof, then the job will stop with the following messages:
DFMSA: ICOMP= 1
*** SYSTEM FATAL MESSAGE 7402 (DFMFRD)
ERROR DURING NUMERIC ASSEMBLY OF MATRIX ROWS.
USER ACTION: PLEASE CONTACT MSC.SOFTWARE CLIENT SUPPORT.
0FATAL ERROR
Avoidance: Do no use dmp on small models.
125213
work with dmp.
Distributed Memory Parallel - MSC.Monitor (xmon=yes) does not
MSC.Monitor (xmon=yes) does not work with distributed memory parallel jobs.
125393
Poor Answers
2004
Optimization/Design Sensitivity - EIGC -
Any method other than complex Lanczos will not produce left-hand eigenvectors
of sufficient accuracy to yield reasonable complex eigenvalue sensitivities.
If another method is requested the job should issue a USER FATAL MESSAGE
recommend.
UFM 7629 (DOPR3) issued if method on EIGC is not CLAN or HESS. 3/28/02 gdc
125588
Superelements - multi-MASTER restart - UFM 3046 (TRD1)
A multi-MASTER residual structure run may fail and issue USER FATAL MESSAGE
3046.
Avoidance: If this fatal message is encountered add the following commands
into the Case Control:
SET 99=0
SELR=99
SELG=99
Else, insert NASTRAN OLDDAREA=0 above the FMS and Executive section
125797
Optimization/Design Sensitivity - Complex Eigenvalue Sensitiv
ity - SFM 3001 (DSFLTF)
If the only designed property is pushed to 0., the optimization job may fail
with the message:
*** SYSTEM FATAL MESSAGE 3001 (DSFLTF)
5 DOES NOT EXIST.
This message was encountered on a simple 2-dof model that was only designing
the damping. The damping value was correctly pushed to zero by the optimizer.
126109
ng Output
2001.0.9
Frequency Response Analysis - ESE - Missi
If element strain energy output is requested in frequency response analysis in

MSC.Nastran V2001 the output for the last frequency may be missing.
Avoidance:
To get the ESE for all the frequencies a subcase for each
frequency must be created and one extra dummy subcase must be added. An
example follows:
DISP(PLOT,PUNCH)=ALL
SUBCASE1
FREQ = 40
ESE(PLOT,PUNCH)=ALL
SUBCASE 2
FREQ = 41
ESE(PLOT,PUNCH)=ALL
SUBCASE 3
FREQ = 42
ESE(PLOT,PUNCH)=ALL
SUBCASE 4
126231
lation in sepltp
Distributed Memory Parallel - OUTPUT(PLOT) - Segmentation Vio
Distributed Memory Parallel jobs with OUTPUT(PLOT) may fail in sepltp with a
traceback.
Segmentation violation "Offset 0x00000334 in procedure sepltp_"
1-296X7
2004
Performance/Nonlinear Analysis - Poor pe
rformance in SOL 106 with superelements
If superelements are present, then SOL 106 executes subdmap XSEDRDR which may
take an excessively long CPU time to complete.
Module xsedrdr is no longer executed in v2004
1-2M26V
2004
4276 EC 3102 QOPEN
Nonlinear Analysis - GPFORCE, NLPCI - UFM
In Version 2001 a request for GPFORCE output in a nonlinear run that uses
arc-length methods specified on the NLPCI entry may result in USER FATAL
MESSAGE 4276 EC 3102.
Avoidance: Other than removing the GPFORCE request or NLPCI, there is no known
avoidance.
1-2WTGH
2001.0.4
AIN(FIBER,BILIN) option
Elements - CQUAD4 - Wrong Answers for STR
New QUAD4 element formulation (V70.7+) gives wrong answers for

strain(fiber,bilin) at corner GRIDS. V70.5 and earlier gives correct answers.
Avoidance: Set NASTRAN SYSTEM(173)=2 to get the pre-V70.7 formulation.
1-2706201
2001.0.3
Optimization/Design Sensitivity - DMIG Adjoint Method Produces Wrong Answers
If any of the mass damping or stiffness matrices are not symmetric, results
obtained using the adjoint sensitivity analysis will be in error. Asymmetry is
typically introduced via user input matrices that are not asymmetric. Acoustic
matrices generated in MSC.Nastran are handled correctly and do not have this
error.
Avoidance: Setting PARAM AUTOADJ NO forces the direct senisitivity analysis and
avoids the error. A dmap alter in the attachment corrects the error while
using the
adjoint method.
Fix taken in r30
1-2754601
2001.0.3
dynamic Force Output is Incorrect
Aeroelastic Analysis - Mach label in Aero
The AEROF request in SOL 146 produces a table which always indicates
MACH=0.00000, regardless of the Mach number used in the analysis. If there is
a single Mach number input with the MKAEROi entries, then only the label is
wrong. With multiple Mach numbers, the print will be based on the lowest Mach
number and the data will be in error if the analysis has been performed at
other than the lowest Mach number.
Avoidance: The following dmap alter produces the correct Mach number print:
compile seaero
alt
1-2771301
2004
uses excessive SWM 1204 (UNRTN)
Postprocessing - Formatted OUPUT2 File ca
When Nastran is writing a formated op2 file for certain large models, it
creates thousands of warning message:
*** SYSTEM WARNING MESSAGE 1204 (UNRTN)
ABSOLUTE VALUE OF SINGLE PRECISION VALUE IS LESS THAN THE MINIMUM FILTER
OF 1.0E-37,
AND WILL BE RESET TO THE CORRECTLY SIGNED FILTER VALUE
1-2791701
Large Model - DCMP - Excessive Disk Space
It has been observed on a large job (over 1.2million degrees of freedom) that
an excessive amount of disk space is required in DCMP. An indication of this
problem is the large disk space usage relative to the estimate for "the number
of NZ terms in the factor."

Avoidance: There are several possible avoidances:
1. Use the MMD reordering method by setting
2. Use the iterative solver by setting the
3. Use the new distributed parallel method
1-2804804
ers
2001.0.3
system cell 206 to 1

nastran statement iter to yes.
(DMP).
Elements - QUAD4, TEMP(LOAD) - Wrong Answ
The new skewed QUAD4 element formulation introduced in Version 70.7 may yield
incorrect answers for static analyses with thermal loads.
Avoidance: The version 70.5 formulation may be requested by setting
SYSTEM(173)=2.
1-2856201
Distributed Memory Parallel - DMP, GDMODES - Job Hangs
Models with indeffinite mass matrices may hang when using distributed memory
parallel gdmodes.
Avoidance: Correct the indefinite mass matrix.
1-2859001
2007.0.0
DMAP - Poor Message, UFM 404
The DMAP compiler gives a bad message, when a "/" delimiter is used instead of
a ",". The message is UFM 404 (CTYPE) "A NON-RIGHT PARENTHESIS DELIMITER WAS
DETECTED WHERE A RIGHT PARENTHESIS DELIMITER IS REQUIRED".
1-2883605
wers
Acoustic Analysis - ACSRCE, RLOAD1, DPHASE, DELAY - Wrong Ans
DPHASE and DELAY functions on fluid loads with ACSRCE and RLOAD1 entries give
incorrect delays in Version 2001 leading to wrong answers.
Avoidance: Use RLOAD1 with TD and TC combinations for phasing.
1-2971701
o errors
Cyclic Symmetry - CYSUP with differential stiffness - maxrati
The CYSUP entry is ignored in the static analysis part of SOLs 115 and 116.
This may lead to maxratio errors.
Avoidance: There is no Avoidance.
1-2994320
Dynamics - LOADSET/LSEQ - Poor Message, UFM 4603
If there is a LOADSET request in the Case Control and no LSEQ entries in the
Bulk Data but other static load entries with the same id , the program
terminates the job with a very confusing USER FATAL MESSAGE 4603.
The
program should terminate the job with the more appropriate UFM 4390.
1-2994324
2004
DMAP - ORTHOG Module - Incorrect Matrix T
railers may lead to various fatal messages
If the ORTHOG module is used to generate the Q and R output matrices for a
rectangular matrix A using parameter values of IOPT=1 and ICON=0, the R output
matrix, which is an upper traingular matrix, is generated with wrong trailer

values. This causes a fatal error if this matrix is subsequently used in a
module like MPYAD.
1-2999801
2001.0.3
Commands Cause Failure
Parallel Methods - DOMAINSOLVER ACMS - SE
In ACMS case control superelement commands such as SEALL=set will cause ACMS to
fail.
Avoidance: Comment out all superelement case control commands in runs using
DOMAINSOLVER ACMS.
Note that SEQP removes SUPER records from case control.
Fatal messages takes the form:
MATRIX XAAV FOR UPSTREAM SUPERELEMENT XX DOES NOT EXIST.
where XX is some upstream SE number.
1-3011601
Wrong Answers
2001.0.3
Nonlinear Transient Analysis - LOADSET -
When a static load set is specified in SOL 129 in version 2001, incorrect
result may be produced if:
(1) The LOADSET case control command and LSEQ bulk data entries are omitted
(an enhancement supported by v2001); and
(2) At least one of the following static loads is referenced by the field of
DAREA in TLOADi (i=1,2) bulk data card. They are FORCE1, FORCE2, MOMENT1,
MOMENT2, PLOAD, PLOAD4 and PLOADX1.
Avoidance: Always use the LOADSET case control command and the LSEQ bulk data
entries to specify static loads in nonlinear transient analysis (SOL 129) if
the type of static loads is a follower force.
1-3012601
Nonlinear Transient Analysis - OLOAD - OLOAD output may not i
nclude follower force effect.
In Version 2001, the OLOAD output does not include the follower force effect in
SOL 129 when static loads are selected but the case control command LOADSET and
bulk data entry LSEQ are omitted. This is a cosmetic problem that will not
affect the other results.
1-3036805
2004
Heat Transfer in P-Elements
Documentation - Missing Documentation for
P-Elements were extended to support heat transfer analysis in MSC.Nastran

Version 70.7. The Quick Reference Guide was not issued for 70.7 and the
updates have not been added to the 2001 QRG.
Avoidance: If you are interested in this capability contact support and the
documentation will be provided.
1-3063705
o Message
Distributed Memory Parallel - DOMAINSOLVER, GDMODES, SEQP - N
If a user attempts to submit a model with superelements in SOL 103 with

geometric domain Lanczos the job will fail in the SEQP module and will not
issue a meaningful message.
Avoidance: This is a limitation. References to superelements must be removed
from the model.
1-3068607
2004
Optimization/Design Sensitivity - Senstiv
ities of PBEAMLs that include warping may be incorrec
Sensitivities of warping coefficients are ignored in the design of PBEAML
section types. The effect of this is that warping coefficients are unchanged
from their initial value thereby creating wrong answers when these effects are
significant.
Avoidance: An awkward avoidance is to design equivalent PBEAM properties using
DVPREL1 and DVPREL2 entries. The SA and SB points on the CBEAM entry must be
grid points for warping sensitivities to be calculated correctly even when the
PBEAM entry is used. Otherwise, it is suggested that if the PBEAML is used,
the final PBEAML design be submitted in a new run to see if the neglected
warping effects are significant.
1-3068612
Aeroelastic Analysis - AMP - SFM LAJJT Matrix Not Available
If multiple aero methods such as strip theory and the doublet lattice method
are used in the same run, the AMP module will produce a message that the LAJJT
matrix is not available.
Avoidance: Do not run multiple aero methods in the same run or run in a
Version 70 or earlier system.
1-3103909
- SFM 3003
2001.0.3
The above fatal message can occur when spc forces or element strain energy
responses are used in conjunction with grid responses. The problem is caused
because the code incorrectly thinks that adjoint sensitivity method is
appropriate and subsequent calculations produce incompatible datablocks.
Avoidance: Set PARAM AUTOADJ NO to preclude the selection of adjoint senstivity
analysis.
1-3151101
2001.0.3
Optimization/Design Sensitivity - Adjoint
Method with Inertia Relief yields Wrong Answers
Sensitivity analysis results are in error for a statics analysis with inertia
relief when the program selects the adjoint method for the sensitivity
analysis.
Avoidance: Set PARAM,AUTOADJ,NO to force the direct sensitivity method.
1-3151106
2001.0.3
Optimization/Design Sensitivity - Gravity
effects ignored in adjoint method if PARAM,CDIF,YES
The adjoint senstivity calculation ignores the sensitivity of any gravity loads
when the PARAM,CDIF.YES is used to specify central difference based element
perturbations.
Avoidance: Set PARAM,CDIF,NO (the default for property optimization) or obtain
a DMAP alter from client support.

1-3159901
001 (DISUTIL)
2004
Distributed Memory Parallel - DMP - SFM 3
Small models, demonstration problem v10101.dat with dmp=2 is an example, that

are submitted with dmp may fail with SFM 3001 (DISUTIL) THE INPUT DATA BLOCK
NAMED QGHD DOES NOT EXIST.
The problem is that the partitioner is not able to partition the model into as
many domains as desired. Usually this does not cause a problem and the job
continues serially.
Other jobs that enter the following line in subdmap
sedrcvr will have the problem:
"if ( prtreslt='yes' and noqg>-1) then .. )
Avoidance; Don't run dmp on small jobs.
1-3162504
2001.0.3
3 - Inaccurate Gradients
Optimization/Design Sensitivity - APRCOD=
APRCOD=3 in design optimization approximates the constraint values using the

the most conservative prediction on the change in the constraint due to a
change in a design variable. The constraints calculated in this fashion are
computed correctly, but the gradient of these constraints can be computed
incorrectly.
Avoidance: Use another APRCOD value (1 or 2). Internal testing has not
revealed a case where the incorrect computation has produced a difference in
the final design.
1-3209214
2001.0.6
Dynamics - MEFFMASS - Missing Output
It has been observed on some problems that the output for the TOTAL EFFECTIVE
MASS FRACTION SUMMARY is missing in some of the directions.
Avoidance: Divide the appropriate diagonal term of the EFFECTIVE MASS MATRIX by
the corresponding RIGID BODY MASS diagonal term.
1-3209224
Optimization - PARAM,EIGD,YES - SFM 6920
If eigenvector sensitivity is requested (PARAM,EIGD,YES) and there is design

variable linking (DLINK), then the job may fail with messages similar to the
followin:
*** SYSTEM FATAL MESSAGE 6920 (MATMOD)
FOR MATMOD OPTION 1, THE COLUMN NUMBER
GREATER THAN ZERO AND LESS THAN
3.
3 IS INVALID. IT MUST BE

compile eigvecds list
alter 'L XINIT',''
PARAML DESTAB//'TRAILER'/2/S,N,NDB $
1-3297102
Complex Lanczos - EIGC - UFM 6138
In a complex eigenvalue problem using complex lanczos, if insufficient memory

is available for sparse fbs, then the following messages will be issued:
*** USER FATAL MESSAGE 6138 (UDSFBI)

INSUFFICIENT CORE FOR SPARSE FBS
1002 WORDS
However, increasing the MEM keyword may not increase the allocated memory.
Avoidance: Use one of the following avoidances.
1. Add nastran system(108)=512 to use the QZ HESS method.
2. Add nastran system(108)=2 to use the old complex Lanczos
3. Add nastran system(108)=131072 to the input file
1-3354804
2001.0.4
r on NT is missing .dll file
Installation - NT Only - New FlexLM serve
The new FlexLM license server (V7.0) delivered with Nastran V2001 on Windows NT
is missing a .dll file that allows the FlexLM GUI (from the Control Panel icon)
to check the license server status. Picking on the "Status" button on the NT
FlexLM GUI results in a message that it is "unable to obtain status due to
missing lmgr326a.dll The same message appears when you choose the HostID
button to find out the current FlexLM HostID.
1-3379905
ients
Optimization - PARAM,EIGD,YES - Incorrect Sensitivity Coeffic
If a model contains a PBEAML or PBARL entry, and eigenvector sensitivity is

requested, then the eigenvector sensitivity coefficients are all listed as
zeros.
Avoidance: Use the equivalent PBEAM or PBAR entry.
1-3379914
2004
ensitivity Coefficients
Optimization - PBEAML/PBARL - Incorrect S
In an optimization/sensitivity analysis, if the model contains PBEAML or PBARL

entries, then the eigenvector sensitivity coefficients will be incorrect.
V2004 supports 6 new response types in sol 200 for eigenvector sensitivity.
The responses must be specified on the DRESP1 entry, specifying param,eigd,yes
will not activate this capability. This addresses this error in v2004.
Avoidance: Replace the PBEAML or PBARL entry with the equivalent PBEAM or PBAR
entry.
1-3414201
)
2004
Documentation/QRG - TEMP(INIT), TEMP(LOAD
Table 4-3 in Section 4A of the Quick Reference Guide indicates that TEMP(INIT)
is not supported in SOL's 101, 103, and 105, 107, 108, 109, 110, 111, and 112.
TEMP(INIT) may be used in SOLs 103, 107, 108, 109, 110, 111, and 112 if
STATSUB is used to define the initial temperature. Likewise TEMP(LOAD) may be
used in SOLs 103, 107 and 110 if STATSUB is used.
1-3422001
2004
ing Documentation
Documentation/QRG - PARAM,INREL,-2 - Miss
The documentation for PARAM,INREL,-2 is missing from the QRG.
The value of param, inrel, -2 provides an inertia relief analysis in SOL 101
without the need for a SUPORTi entry. Remove all such entries. The model must
have mass defined. Request TAN 4854 from your client support user
documentation and example problems.
1-3437715
NRGY
2004
DMAP - TABPRT - NaN in TABPRT output of O
When the ONRGY datablock is printed using TABPRT using the NDDL descriptions,
the final -1 is not recognized and is printed as NaN.
compile sedrcvr
alter 208
tabprt onrgy1//'onrgy'///1 $
endalter
1-3439701
2004
DESSUB - Wrong Answers for Superelement Optimization
When a superelement optimization job includes a DESGLB (or DESSUB) command that
references a constraint defined by either a volume response or weight response
with ATT1=ALL, the contraint values for each SE, along with the one for the
whole model are presented to the optimizer which may lead the optimizer to
reach a wrong conclusion.
1-3451401
tput
2001.0.3
Nonlinear Analysis - GPFORCE - Missing Ou
In a SOL 106 run, if grid point force is requested, and the model contains more
than one linear element type and thermal loadings are applied, then the
following fatal message will be issued.
*** SYSTEM FATAL MESSAGE 3007 (GPFDR)
ILLEGAL INPUT TO SUBROUTINE GPFTDL
Avoidance: Other than having only one linear element type, there is no known
avoidance.
1-3458801
TSTEP
Nonlinear Transient Analysis - Wrong answers NO>1 w/ AUTO or
Wrong answers are produced if METHOD=AUTO or TSTEP are specified on the

TSTEPNL entry and the NO field (nskip) is > 1.
This error will not be fixed. The functionality of METHOD=AUTO or TSTEP is
fully replaced by METHOD= ADAPT. The AUTO and TSTEP methods have been
de-documented but are not blocked.
1-3477406
007 (MERGE)
2008.0.0 (MD R3)
Eigenvalue Analsyis - PARAM,SNORM - SFM 3
A model containing 59 massless mechanisms failed with SFM 3007 indicating

illegal input to MERGE during the eigenvalue solution.
Avoidance: For this model, changing the value of PARAM.SNORM to 0.0 allowed it
to run.
1-3496527
2001.0.3
Modal Frequency Response - ESE - Incorrec
t Output
In a modal frequency response analysis, if element strain energy is requested
and a set ID of 2 is used, then erroneous complex acoustic results may be
printed, even though there is no acoustic elements in the model.
Avoidance: Use a set ID other than 2.
1-3507901
2004
ting Point Overflow in frrd1
Eigenvalue Analysis - PARAM,RESVEC - Floa
Modal frequency response jobs may fail in the frrd1 module with a traceback
when param,resvec,yes is specified.
Traceback:
bldpk_
frrd1f_
sqfreq_
freq_
xsem10_
xsemdr_
nastmon_
mainal
Avoidance: Do no specify param,resvec or request fewer eigenvalues.

1-3524604
2004
modal transient
SSSALTER - gpftrna alter does not work in
SSSALTER gpftrna.v707 works only in direct transient, not in modal transient.

Avoidance: Change COMPILE SEDTRAN to COMPILE SEMTRAN in the alter or get an
updated version from the MSC web page
1-3525701
Wrong Answers
2001.0.3
In design sensitivity (DSVG1), if there is not enough space to hold the

solutions in core, the program will hold as many solutions as possible to
perform matrix multiplication, then, repeat for the rest of solutions causing
wrong results.
Avoidance: Increase memory using the following formula:
Minimum memory space to hold all solutions in core =
(NSOL * GSIZE * NWORD * NCMP * 4)
nsol - number of non-null solution vectors in UG
gsize - number of rows in the UG vector
NWORD - 2 for short word machine and 1 for long word machine
NCMP - 2 for complex number and 1 for real number in UG
1-3539967
2001
NALYSIS=SAERO - SFM 1013
Optimization/Aeroelasticity - BC, TEMP, A
Multiple boundary conditions with static aeroelastic optimization and

temperature loading results in SYSTEM FATAL MESSAGE 1013.
1-3543501
2004
e Superelement, Incorrect Complex Eigenvalue Sensitivities
In multiple superelements, the complex eigenvalue sensitivity coefficients are
incorrect for the residual superelement (SEID=0). This problem also exists in
flutter sensitivity when more than one superelement is in the model. This
problem can be avoided with following DMAP alter:
compile ceigsens,list $
alter 'EQUIVX CDELK1/CDELK/DMRESD',''(,10) $
IF ( DMRESD<0 ) THEN $
EQUIVX CDELK1/CDELK/DMRESD $
EQUIVX CDELM1/CDELM/DMRESD $
EQUIVX CDELB1/CDELB/DMRESD $
ELSE $
ADD5
CDELK1,CDELK,,,/CDELK2 $
ADD5
CDELM1,CDELM,,,/CDELM2 $
ADD5
CDELB1,CDELB,,,/CDELB2 $
EQUIVX CDELK2/CDELK/-1 $
EQUIVX CDELM2/CDELM/-1 $
EQUIVX CDELB2/CDELB/-1 $
ENDIF $ DMRESD<0
$
In addition, flutter job may fail if upstream SEs have their own subcase.
1-3556907
2004
, - SWM 2072, Missing Output
FLuid/Structure Analysis - FLSPOUT, PANEL
If the FLSPOUT Case Control command selects PANELMP and GRIDMP=ALL and one or
more of the PANEL Bulk Data entries lists more than one panel then SWM 2072 may
be issued and acoustic output will be missing for some panels.
1-3612601
2001.0.3
DMAP - ADD5 - SFM 6924 Wrong Answers for
Double to Single Precision Conversion
The procedure outlined in SFM 6924 and the DMAP Module dictionary to convert a
double-precision matrix to single-precision will produce wrong answers in
Version 2001.
Avoidance: Change the following in the outlined procedure:
PUTSYS(1,55)
ADD5 DOUBLE,,,,/SINGLE $
PUTSYS(2,55)
to
putsys(1,55)
add5 doubl,,,,/a52
putsys(2,55)
1-3654801
IFS10P
$
$
$
2001.0.3
Nonlinear Analysis - SFM 4276, EC 7777 in
Solution 106, nonlinear analysis, jobs may fail on Compaq Alpha systems in
routine IFS10P with the message:
BIOMSG: ERROR 7777 HAS OCCURRED IN ROUTINE tbk
1-3677801
2001.0.3
Elements - CWELD - Wrong Answers
The calculation algorthm for spot weld elements (CWELD) sometimes returns a
projection point outside of the triangular shell. The program should return an
error and abort the execution. This leads to wrong answers.
1-3677804
2001.0.3
Elements - CWELD - Performance
MSC.Nastran CWELD elements perform unnecessary operations that waste cpu

resources. The program shouldn't generate shell normals for the point-to-point
or point-to-patch connection of spot welds with the BEAR option. Furthermore,
the program shouldn't check if the projection points are shell grids.
1-3683607
2001.0.3
Loads - Extended output force resultants,
Wrong Answers with Output COORDi Systems
Moment summations for forces could be in error if output coordinate systems are
used at grid points. The error affects only the moment summations due to
forces in the extended (7-line output) summation option. The TOTALS line is
always correct.
Avoidance: Ignore the moment summation portion of the force output.
1-3694001
Database - DBLOAD - UFM 2025 (SSG1)
A neutral database load, DBLOAD, on little endian machines may lead to UFM 2025
(SSG1).
Avoidance: This error is believed to be related to p-elements and is not
likely to occur.
1-3694031
, Poor Message
2004
Acoustic Elements - NOGO Flag Encountered
If HEXA, PENTA, or TETRA acoustic elements fail the geometry check the job will
stop after EMG and the only message output will be "NOGO FLAG ENCOUNTERED".
Avoidance: Specifying
GEOMCHECK STD_MSG
in the Executive Section will cause the correct fatal message and the problem
elements will be identified.
1-3699001
nite loop
2001.0.3
Acoustic Analysis - XYTRAN gets into infi
Large acoustic analysis sol 111 jobs may get into an infinite loop in the
XYTRAN module. This behavior has been seen on both NEC SX-5 and AIX systems.
1-3724703
UFM 5608
2001.0.3
Optimization/Design Sensitivity - SDSAC -
When a superelement optimization task includes a DRESP2/3 entry that

references a DRESP1 entry and also references a design entry following DRESP1
(e.g., DViRELj, DRESP2, USRDATA), it will fail with the following error
message:
USER FATAL MESSAGE 5608 ()
DRESP2 ENTRY ID=
100 REFERENCES AN UNDEFINED DRESP1 ENTRY ID=
Avoidance: No practical avoidance exist. Do not include the offending entries

or do not use superelements.
1-3743525
2004
sticity with Temperature Loads
An aeroelastic optimization task with multiple subcases and with one or more
subcases having a temperature load will fail in the sensitivity phase. The
type of failure is dependent on the specific design task, but there will be an
indication of missing data.
Avoidance: The following DMAP avoidance is available for the V70.7 and 2001
Release:
compile saersens
alter 'dksalx'(,-1)
if ( stflg>0) then $
alter 'lauldx'(2)
endif $ stflg>0
alter 'lauldx'(3)
if ( ncol > 0 ) then $
alter 'lauldx'(5,2)
endif $ ncol>0
compile gendv2p
alter 'bcdr'
PARAML CASE0//'DTI'/s,n,nskip/7//S,N,TEMPLD $
PARAML CASE0//'DTI'/s,n,nskip/6//S,N,DEFORM $
compile xsedrdr
alter 'bcdr'
(complete alter does not fit in allowed space. See the attachment)
1-3745506
Nonlinear Analysis - Superelements - Missing or Extra Output
In nonlinear analysis (SOL 106), if superelements are used, they will use the
output requests from the residual structure subcases. Any output requests in
the superelement subcases will be ignored.
Avoidance: Insert the following alter into your input file:
compile super3
alter 'alter 'IF ( (NOCASRS1>-1',''
IF ( NOCASRS1>-1 AND SEID=0 ) THEN $
1-3749805
2004
T), Excessve Memory
Elements - ELSUM, PCOMP - SFM 3008 (ELTPR
If ELSUM output is requested and the model has composite elements, the run may
fail with in ELTPRT or ELTPT4 with a message of the form:
*** SYSTEM FATAL MESSAGE 3008 (ELTPRT)
INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE PREMAT
Avoidance: There is no avoidance other than providing a large amount of
memory or not requesting ELSUM output.
1-3751401
2004.0.5
Post Processing - param,post,0 - Patran c
an not view postprocess results in the xdb
If a linear heat transfer analysis is followed by a stress analysis in SOL

101, then Patran can only view the temperature output and can not view the
displacement output from the xdb.
1-3754501
2004
ficulty Converging, Follower Forces
Nonlinear Analysis - param,fksymfac - Dif
SOL 106 may diverge with symmetrized follower stiffness as the rotations
becomes large. If the effect of asymmetry of the follower stiffness dominates
the stiffness, but the default option for param,fksymfac symmetrizes it, then
the problem may have convergence difficulty.
Avoidance: Set param,fksymfac,0.0.
1-3770604
wers
2001.0.3
Frequency Response - MEFFMASS - Wrong Ans
If modal effective mass output (MEFFMASS) is requested in a frequency response

analysis that requests more that 50 modes, than the formatting of the "MODAL
EFFECTIVE MASS FRACTION" table will deteriorate and put each additional mode on
a new page. Also models with many roots (more than 100) may result in
meaningless results being printed to this table. This error has been fixed in
Nastran 2001.0.3 except on Cray platforms.
1-3771601
age
2004
Miscellaneous - NOLIN, NLRGAP - Poor Mess
MSC.Nastran issues an incorrect fatal error message when the NOLIN-type Bulk
Data entry (including NLRGAP) references an undefined grid point ID.
1-3787901
2001.0.3
Acoustic Analysis - Fluid/Structure Analy
sis with multiple PANEL bulk data entries - UFM 653
Fluid/Structure analysis using multiple PANEL bulk data entries may fail with a
GINO read error. The GP5 module counts EDT PANEL entries incorrectly when
there are 3 or more individual PANEL bulk data entries.
Avoidance: Use a single PANEL entry to list panel data.
1-3788001
2001.0.3
P-elements - CORDi - UFM 2025 (VECPLOT)
Large p-element models with output displacement coordinate systems may fail in
VECPLOT with the following message:
error in VECPLOT:
*** USER FATAL MESSAGE 2025 (VECPLOT)
UNDEFINED COORDINATE SYSTEM ID =
10
Avoidance: A workaround is to increase BUFFSIZE.

1-3816002
2004
or Invalid Requests
Case Control - No Warning Message Issue f
If a case control output request includes unsupported options, there is no

warning issued and the request is simply ignored. For example if DISP(POLAR)
is specified instead of DISP(PHASE) to get output as magnitude/phase, the

output will be real/imaginary and no warning message will be issued.
1-3827201
2001.0.6
DBC - SWM 6065, DBCMSG Error Message 14
In v70.7, if the geometry datablocks, load datablocks, and the output

datablocks are requested on the same DBC call, the job may fail with the
following error messages:
Avoidance: A DMAP avoidance is available that beaks the DBC into two separate
calls, one for the geometry and loads, and one for the output datablocks.
1-3860101
2004
ES - SFM 6143 (UPARTN)
Complex Eigenvalue Analysis - OFREQ, OMOD
Using the OFREQ or OMODES feature in modal complex eigenvalue analysis results
in SYSTEM FATAL MESSAGE 6143 in the UPARTN module.
1-3889242
a Output
2001.0.3
Case Control - WEIGHTCHECK. CGI=NO - Extr
If on the WEIGHTCHECK case control command set is not equal to g, then the CG
location, I(S), I(Q), and Q matrices are not printed unless the CGI keyword is
set to YES. This is the design intent. The default for CGI is NO. However,
if CGI is explicitly set to NO for set not equal to G, then the CG location,
I(S), I(Q), and Q will also be printed. For example:
weightcheck(set=(n),cgi=no )=yes
Avoidance: If this additional information is not desired, leave the CGI
keyword out.
1-3889601
2004
Documentation/QRG - GPFORCE - Slideline F
orces ignored in the GPFORCE Calculation
Remark 5 of the GPFORCE case Control description in the V2001 QRG needs to be
modified to state that Slideline force contributions are ignored in the GPFORCE
calculation.
1-3948211
Documentation
2004
Documentation/QRG - PARAM,OMID - Missing
The documentation for parameter OMID is missing from the 2001 Quick Reference
Guide. The parameter is documented in the 2001 Release Guide. The
documentation should read:
OMID
Default=NO
To print or punch the results in the material coordinate system,

set the parameter OMID to yes. Applicable to forces, strains, and stresses for
CTRIA3, CQUAD4, CTRIA6, and CQUAD8. Other elements and outputs are not
supported. This capability is not supported by pre-processors (xdb and op2
output are not changed) and grid point stress output that assumes output is in
element coordinate systems.
1-3961304
Generated
2004
Dynamics - PARAM,RESVEC,YES, SOL 103 -Not
In a SOL 103 run, if the direct load method is used (TLOADi pointing directly
to a spatial load, e.g, FORCE entry) instead of the LOADSET/LSEQ combination,
then the residual vectors are not generated.
Avoidance: If the residual vectors are desired in a SOL 103 run, then use the
LOADSET/LSEQ combination
1-3961311
2001.0.3
IDUAL VECTOR, USET,U6 - UFM 2049
Automatic Component Mode Synthesis - RES
If a job employs ACMS, and USET,U6 is used to request a residual vector, then
the job will fail with the following error messages:
xx HAS A COORDINATE REFERENCED ON A USET
CARD.
Avoidance: Use the inertial load method or the applied load method
(LOADSET/LSEQ combination)
1-3971529
2004
Issued for Missing MATi
Elements - CQUAD4 - UFM 4297 Incorrectly
If the PSHELL for a valid-geometry QUAD4 references a non-existent MATi entry,

then UFM 4297 (EQD4D) is issued indicating the element has an interior angle
greater than 180 degrees. This message is incorrect.
The UFM 4297 is followed by an appropriate UFM 2042 (EMG) that does indicate
that the MATi entry is missing. This sequence of messages occurs in both
Version 70.7.2 and 2001. In earlier releases (v70 and 70.5), only the
appropriate 2042 message is issued.
The UFM 4297 message is incorrect/misleading which will increase model debug
time for the user and increase support time/cost for MSC.
A small test deck demonstrating the problem is attached.
1-3975803
wers
2004
P-Elements - CBEAM, TEMP(MAT) - Wrong Ans
For the beam p-elements, the temperatures used for the

temperature-dependent material properties are incorrect.
1-3982601
Optimization/Design Sensitivity - Ordering of Costraint Value
s Differs for IPRINT=3 vs P2=4
Constraint values reported in SOL 200 with the P2=4 set on the DOPTPRM entry
may produce results in a different order than those produce with IPRINT=3
during the optimizaton. The discrepancy occurs when a mixture of designed
property types (property, material and connectivity) exist.
Avoidance: The different orders are confusing, but do not produce wrong
answers. The initial constraint prints with IPRINT=3 can be compared with the
P2=4 printout to map the different orders.
1-4015495
Heat Transfer Analysis - VIEW3D, CHBDYP - Wrong Answers
Bob Harder is looking into it. - Raj

The VIEW3D module gives bad results for the chbdyp,line option for rod
structures that span 360 degrees.
When there is potential shading where the ERROR=YES, for example 1-18 sees the
error,then it will recompute the view factor using contour integration.
The error of NASTRAN is that It Does not using the contour integration
method,and the view factor 1-18(on the second times) is 0.554.
The theory for 1 to 18 using Hottel's String method is 0.02851
*** VIEW FACTOR MODULE *** OUTPUT DATA *** CAVITY ID =
10
***
ELEMENT TO ELEMENT VIEW FACTORS
PARTIAL
SURF-I
SURF-J
SHADING ERROR SCALE
AREA-I
AI*FIJ
FIJ
C*
ERROR
1 -
18
6.5403E+00 6.82983E+00 1.04427E+00 6.8657E+01
NO
52
6.5403E+00 1.06617E+01 1.63015E+00 2.4993E+02
NO
1
1
18
52
6.5403E+00 3.62416E+00 5.54126E-01

6.5403E+00 1.32828E-01 2.03091E-02
YES
YES
240/256
Avoidance: Use the older view module.

The older view factor can be selected by commented out the VIEW3D bulk data
entry.
See attachment :2d_chbdyp_view_dcc_old.dat
1-4022230
M 4297.
2004
Elements - CQUAD4, CTRIA3 - Misleading UF
A missing material entry may cause UFM 4297 (EQD4D) to be incorrectly issued:
QUAD4 ELEMENT WITH ID =
140507
before issuing a correct message UFM 2042 (EMG)
MISSING MATERIAL TABLE 111551 FOR ELEMENT 140507
This is misleading when a large number of UFM 4297 are issued before the
correct UFM 2042.
1-4037006
Miscellaneous - MPC, blank coefficients - UFM 316
Miscellaneous - MPC, blank coeffiecients - UFM 316

The default for the coefficients of the independent degrees of freedom for an
MPC is 0.0. However, if they are left blank, then the job may fail with the
following messages:
ILLEGAL DATA ON BULK DATA ENTRY MPC
Avoidance: Remove the degrees of freedom that have zero coefficients.
1-4051301
2001.0.3
Elements - CWELD - Incorrect sign of mome
nts in plane 2.
The moments in plane 2 (m_y) of CWELD elements are
output with the opposite sign.
1-4056201
2001.0.3
Elements - CWELD, PWELD - UFM 2042 (EMG)
If the CWELD element is used in superelement analysis the job may fail with the
message:
*** USER FATAL MESSAGE 2042 (EMG)
MISSING MATERIAL TABLE xxx FOR ELEMENT yyy
1-4056908
2004
multiple BC's - SFM 6143 in DUMERG
Distributed Memory Parallel - GDMODES, w/
A sol 103 run w/ multiple subcases having different SPC sets runs in Version
70.7.2 DMP but not Version 2001. More precisely, multiple boundary condition
subcases with different s-set size do not run under Geometric Domain Parallel
(GDMODES).
The following error results:
*** SYSTEM FATAL MESSAGE 6143 (DUMERG)
THE SIZES OF THE INPUT MATRICES AND THE DOF SETS ARE INCOMPATIBLE.
SPECIFICALLY:
The number of rows in PHA1 is not equal to the size of the COMP-set
Essentially, when the F-set changes between subcases, an incompatible matrix
multiplication with PHA1 is attempted.
Multiple BC case works when Domainsolver FDMODES is used.
1-4063523
2005.0.2
(GKAM), Wrong Answers
Superelements - PARAM,SESDAMP - SFM 3001
If modal damping is requested for PART superelements using PARAM,SESDAMP,YES

the run may fail with SYSTEM FATAL MESSAGE 3001 (GKAM) or get incorrect
damping. This is due to the program trying to get the TABDMP1 data from the
main bulk data.
Avoidance: Copy the TABDMP1 entries into the main bulk data section.
1-4067301
2001.0.3
terminates Nastran
Miscellaneous - ISHELL module prematurely
The ISHELL module terminates the Nastran execution if any forked process takes
more than about 5 minutes to complete.
1-4070108
2001.0.3
Optimization - PBARLs, PBEAMLs - UFM 6499
In an optimization run, if both PBARL and PBEAML exist in the model, then the
job may fail with the following error messages:
THE GRADIENT OF CONSTRAINT NUMBER
x IS ZERO
CONSTRAINT IS REMOVED FROM THE ACTIVE SET
** THIS IS A VIOLATED CONSTRAINT

** A FATAL ERROR WILL BE GENERATED
**** ONE OR MORE VIOLATED CONSTRAINTS HAS A ZERO GRADIENT ****
NO PROGRESS IS POSSIBLE
OPTIMIZATION TERMINATED
Avoidance: Use either all PBARL or all PBEAML or convert them to equivalent
PBAR and PBEAM
1-4082701
Y1BLD)
2004
Documentation/QRG - LOADCYN - UFM 4342 (C
A remark needs to be added to the Quick Reference Guide LOADCYN entry that
indicates that in cyclic buckling anaysis loads may only be applied to the
first segment and only harmonic zero loads may be applied.
1-4082801
2004
Elements - CWELD - Incorrect sign on mome
nt force output.ccordinate system is not published
The sign of the m_y element moments of the CWELD is wrong, it must be opposite
to be the same as for the CBAR.
In adition, the CWELD element force item codes are not published in the Quick
Reference Guide and the rules for the element coordinate system have not been
published.
A word document is attached to this quality that contains all the necessary
information for post processing the CWELD.
1-4100101
49 from QRG
2004
Documentation/QRG - DIAG 49 - Remove DIAG
DIAG 49 should be removed for the Quick Reference Guide, see error 33293. The
utility f04rprt should be used to summarize the f04 Execution Summary.
1-4117910
2004
g Documentation
Documentation/QRG - PARAM,XYUNIT - Missin
The documentation for parameter XYUNIT is missing from the 2001 Quick Reference
Guide. The documentation should read:
XYUNIT
XYUNIT is used in conjunction with an FMS ASSIGN statement to specify the

unit number for the storage of design sensitivity data in comma separated value
format for use in a spreadsheet.
1-4126201
Element - CWELD, CQUADR, ALIGN - UFM 7546
If a CQUADR is connected to a weld element, then depending on the connecting

option, the job will fail with one of the following error messages:
*** USER FATAL MESSAGE 7546 (MDG2SW)
ON CWELD ENTRY ID=
xx, WITH FORM=ALIGN, THE GA (OR GB) GRID ID=
yy IS NOT A VERTEX GRID OF A SHELL ELEMENT.
ON CWELD ENTRY ID=
xx, WITH FORM=ELEMID, THE SHID1 (OR SHID2)=
yy IS
NOT A SHELL ELEMENT.

Avoidance: Replace the CQUADR with the CQUAD4 element.
1-4126807
2001.0.3
Part Superelements - BEGIN SUPER, CORD -
For a PART superelement, if the boundary point of a superelement uses a

secondary displacement coordinate system, then the results may be incorrect.
Avoidance: Use the assembly basic coordinate system at the boundary.
1-4150825
mula
2004
Documentation/QRG - FREQ1 - Incorrect For
The formula in Remark 3 of the FREQ1 bulk data entry description should say:
(NDF+1)
not
(NDF=1)
1-4168512
Random - multiple subcases,freq - SWM 3002
In a random analysis, if there are multiple subcases, and each subcase has a
different frequency callout, then the following unclear messages will be issued
without performing a random analysis:
EOF ENCOUNTERED WHILE READING DATA BLOCK OUGV2
SUBROUTINE RAND2
(FILE 104) IN
Avoidance: Use the same frequency callout for all the subcases
1-4168528
2004
r Dynamic Response
Documentation/QRG - GPKE Not Available fo
GPKE output is only supported for normal modes analysis. Contrary to what is
indicated in Table 4-5 of the QRG, the GPKE output is not supported in SOL 108.
GPKE output can be obtained for the normal modes part of the other modal
dynamic solutions.
1-4195201
2004
Buckling - CWELD - Possible Wrong Answers
The CWELD element does not support nonlinear analysis nor does it create a
differential stiffness matrix. However, if the CWELD element is used in a SOL
105 buckling analysis, depending on the problem and machine that you are
running on, the job may terminate without any message, yield incorrect results,
or terminate with the following messages:
MAIN: For reference, A(MAINAL) = 401380, A(/SYSTEM/) = 1915050
MAIN:
A(/XNSTRN/) = 3320020
MAIN: "Floating point zero divide" (C000008E) exception encountered.
MAIN: Exception occurred at address 010654CD.
MAIN: EAX 00000006 EBX 03
1-4214309
2004
Dynamic Analysis - Enforced Motion with S
tatic Preload - Wrong Answers

If enforced motion is used in a modal solution (SOL 111 or 112) with a static
preload, the run will either fail indicating that no loading is defined or will
run with incorrect results (if another loading is applied in addition to the
enforced motion).
compile SEMTRAN $ SOL 112 or SEMFREQ for SOL 111
alter 'umerge.*ys.*yg'(,-1)
lcgen casers,slt,ett,dynamic,geom4s/cases2t/s,n,dummt/'tranresp' $
paraml cases2t//'dti'/1/4//s,n,load $
1-4239801
2004
does not Include Thermal Strain
P-Elements - STRAIN, TEMP - Strain Output
The strain output for solid p-elements is the mechanical

strain, which is the difference of the total and thermal
strains. For a solid model undergoing free thermal
expansion, the strain output would be zero, rather than
the non-zero mechanical strain that is customary.
The stress output is calculated from the mechanical
strain and is correct.
1-4266901
2004.0.4
Distributed Memory Parallel - SPCD, DAREA
- Wrong Answers for Frequency Response
Sol 111 DMP returns incorrect responses for the responses for all slave
processes when both SPCD and DAREA/LOAD type subcases are mixed within same run.
1-4273414
2008.0.0 (MD R3)
- SFM 4276 EC 3001 from DSAB0
Optimization/Design Sensitivity - DVMRELi
This problem has been fixed under Quality # 36709 for 20055 (2005R3) and
2007R1 release.
In an optimization job, when an existing MATi entry is being designed by a
DVMREL1/2 but has not been referenced by any property entry, then the job will
fail in DSABO with SFM 4276, EC 3001.
Avoidance: Make sure the problematic MATi entry is referenced by a property
entry.
1-4299402
2005.5
iption Incorrect
Documentation/QRG - NLRGAP Contents Descr
The MSC.Nastran Quick Reference Guide incorrectly describes the TABK field of
the NLRGAP entry when it is set to less than zero. When TABK<0 the
description under the Contents heading on the NLRGAP entry should be "force vs
penetration" NOT "stiffness vs pentration".
1-4304427
2004
hanged on a PELASi entry
Restarts - Inefficient restart if Ge is c
When the Ge field of a PELAS entry is changed between a SOL 103 cold start and
a SOL 111 restart, the eigenvalues are recomputed. This is inefficient as the
change to damping does not affect the eigenvalue computation.
Resolution: Insert the following DMAP in your file (be careful, as it disables
the restart checking for element property changes)
compile ifpl
alter 'RESTART EPT,EPTR, /LIST','' $
message //'WARNING - element property
' has been disabled' $
endalter
compile phase0, list
alter 'RESTART EPTS,EPTSR','' $ line
message //'WARNING - element property
' has been disabled' $
endalter
1-4306901
2001.0.3
), ILLEGAL INPUT TO SUBROUTINE SDRX3
194
change restart checkingl/
841
change restart checkingl/
Elements - CBEND, PLOAD1 - SFM 3007 (SDRX
MSC.Nastran 2001 may issue SYSTEM FATAL MESSAGE 3007(SDRX) - ILLEGAL INPUT TO
SUBROUTINE SDRX3 for a model with CBEND elements requesting STRESS=ALL.
Avoidance: If this error occurs, use a SET which does not include the BEND
elements.
1-4332806
2004
Documentation/QRG - LOADCYH,DAREA
The following sentence in Remark 5 of the QRG description of the LOADCYH entry
..FORCE2,MOMENT2,PLOAD,...
should be replaced by
..FORCE2,MOMENT2,DAREA(if these entries have been converted),PLOAD,...
1-4342210
2004
Documentation/QRG - system cell 319
In the Release Guide, Section 9.8 says set system cell(119)=1 for extended
error messages. This should be system cell(319)=1 instead.
Release Guides are not re-issued. This error will be marked fixed when the
system cell is added to the 2003 QRG.
1-4344301
2004
.f and tabtst.f are reversed
Documentation/IOG - Description of mattst
The descriptions of mattst.f and tabtst.f in Section 6.15 of the MSC.Nastran

2001 Installations/Operation Guide are reversed. The sample source program
mattst.f reads binary output4 and not output2 and tabtst.f reads output2 and
not output4.
1-4365301
2004
Frequency Response - OFREQ, SPCF, MPCF, C
BUSH, frequency-dependent elements - SFM 5423
If OFREQ and MPCF (or SPCF) are requested in a run with frequency dependent
elements then the run may fail with SFM 5423 in MPYAD.
compile disprs
alter ' modacc ',''

MODACC CASEf,fOL,Uhf,PPf,qmgf,qsgf/
fOL0,Uhf1,PPf0,qmgf0,qsgf0/APP $
alter 'call cforce2'(1),''
call CFORCE2 USET,rgs,Uff,MSF1,BSF1,KSF1,Pgf1,fOL1,
qsgf0,
qdg,vspcg,/
Qpf/
APP/APP1/'spcforce'/true $
call CFORCE2 USET,rgs,Unt,MSn,bSn,KSn,Pgf1,fOL1,qsgf0,
qdg,vspcg,/
Qpf/
APP/APP1/'spcforce'/true $
call cforce2 USET,rgm,Uhf1,MMG1,BMG1,KMG1,Pgf1,
fOL1,qmgf0,,vmpcg,/
Qmpf/
APP/APP1/'mpcforce'/true $
call cforce2 USET,rgm,Upf1,MMG1,BMG1,KMG1,Pgf1,
fOL1,qmgf0,,vmpcg,/
Qmpf/
APP/APP1/'mpcforce'/true $
endalter
1-4371801
001 (DSAP)
2004
External Superelements - EXTSEOUT - SFM 3
A SOL 103 external superelement creation run using the EXTSEOUT Case Control
command fails with SFM 3001 in the DSAP module if the superelement is reduced
via static condensation (no QSET data provided) rather than via component mode
reduction.
1-4383701
2004
Aeroelastic Analysis - CBUSH - UFM 2170
In SOL 146, if a frequency-dependent element, such as a CBUSH element, is used

then the job will fail with the following error messages:
*** USER FATAL MESSAGE 2170 (PARTN2)
BOTH THE ROW AND COLUMN PARTITIONING VECTORS ARE PURGED AND ONLY ONE MAY BE.
FATAL ERROR
Avoidance: Apply the folloiwng dmap avoidance.
compile seaero $ v705
alter 'call.*freqrs','' $
CALL FREQRS CASES ,USETD ,DLT ,FRL ,TRL ,
RPH ,DIT ,EST ,CSTMS ,MPTS ,
BGPDTS ,GPSNTS ,GPECT ,SILS ,EDTS ,
KHH ,MHH ,BHH , ,QHJL ,
ACPT ,CSTMA ,QHHL , ,DITID ,
,RGHFD ,RSGG ,RMGG ,PPF ,
FOL , ,vgfd , /
AUHF ,QMGF ,QSGF ,PHF /
SOLTYP /FREQDEP /NOA /FOURIER /FALSE /
1 /TRUE /BOV /DOMPCFFD/DOSPCFFD/
FALSE /NOUE /0 $
1-4387523
Dynamics - SDAMPING, TRD1 - Wrong Answers or Fatal Message
If modal damping (SDAMP) is requested in modal transient analysis and some of

the natural frequencies result in negative modal damping, then either wrong
answers are produced or a fatal error is encountered in TRD1. (Test problem
no. d11257.dat exhibits this behavior if PARAM,RESVEC,YES and
PARAM,RESVINER,YES are BOTH specified. See discussion in the Attachment
dealing with various e-mails.)
Avoidance: Modify the TABDMP1 entries so that the interpolation over all
frequencies leads to positive modal damping values or use the MODESELECT
command or PARAM,HFREQ. LMODES, and/or LFREQ to specify only those modes with
positive modal damping.
1-4405020
M 3001 (FBS)
2004
ACMS - fluid/structure, DOMAINSOLVER - SF
When using ACMS for a fluid/structure model, the job may fail with the
following fatal messages:
*** SYSTEM FATAL MESSAGE 3001 (FBS)
THE INPUT DATA BLOCK NAMED LLL
AT POSITION
1 DOES NOT EXIST.
Avoidance: Setting NUMDOM to a different value on the DOMAINSOLVER entry

1-4405034
Output
2008.0.0 (MD R3)
ACMS - fluid/structure - Extra Erroneous
In an ACMS run with fluid/structure, the f06 and punch file may contain extra
erroneous output. An indication of this is the output results for non-existing
elements or grids. This error is considered fixed with the introduction of
auto-Qset.
Avoidance: Other than ignoring the extra output there is no known avoidance.
1-4405054
sages
2004
Buckling Analysis - CTRIAX6 - Unclear mes
The CTRIAX6 element should not be used in a buckling analysis since it does not
generate a differential stiffness matrix. This is documented in the Reference
Manual. If the CTRIAX6 element is used in a buckling analysis, then the job
will fail with the following unclear messages:
MAIN: For reference, A(MAINAL) = 401380, A(/SYSTEM/) = 1915050
MAIN:
A(/XNSTRN/) = 2e40020
MAIN: "Floating point zero divide" (C000008E) exception encountered.
MAIN: Exception occurred at address 010654CD.
MAIN: EAX 00000006 EBX 02F2C790 ECX 00000008 EDX 02F2CA58 ESI 02EDD4D8
EDI 02E8EA80
MAIN: EBP 02F2CAB0 ESP 0012F210 EIP 010654D3 EFLAGS 0001029
The traceback has been corrected. Models but differential stiffiness is not
supported and buckling analysis is likely to fail with a message that there are
no roots in the range.
1-4415801
2004
d FDMODES - SFM 3008
Distributed Memory Parallel - MEFFMASS an
If MEFFMASS is requested in a FDMODES DMP run in both Sol 103 (with

DOMAINSOLVER) and Sol 111 (default DMP) the following error message is
encountered:
SYSTEM FATAL MESSAGE 3008 (EFFMAS)
INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE EFFMA4
compile modefsrs
alter ' effmas '(,-1)
if ( procid<=1 ) then $
alter ' effmas '
endif $ procid=1
alter ' effmas '(2,-1)
alter ' effmas '(2)
endif $ procid=1
endalter
It tested successfully using MEFFMASS & DMP in Sol's 103 & 111. It was further
tested with: 1) multiple BC in Sol 103, and 2) Resvec's in Sol 111, and worked
well.
It is recommended this fix is coded into next v2001 release.
-- JoeM
1-4428001
- UFM 6499
2001.0.4
Design of more than approximately 20 PBEAML properties can result in wrong

answers or USER FATAL MESSAGE 6499.
Avoidance: Avoid the design of large numbers of PBEAML's or use Nastran
2001.0.4 or higher.
1-4467601
2004
Large Problem - EMG - SFM 4275
A very large problem fails in EMG with the following error message:
0*** SYSTEM FATAL MESSAGE 4275. DURING A
READ OPERATION, UNIT = 1, DATA
BLOCK=EST
, A BLOCK NUMBER CHECK CONDITION OCCURRED. (
IONAST CODE= 304) 0*IONAST* err 304 pid,name,b+1,z4(b+1),nxtblk,pbknbr=
0
101 366837611
0
466
6683
BIOMSG: ERROR
304 HAS
OCCURRED IN ROUTINE IONAST , FILE INDEX =
0.
STATUS =
0
The model that failed is a fluid structure interaction problem with
approximately 800,000 grids. It has been verified that the model ran past emg
in version 2004.
1-4470101
in output
2001.0.3
Miscellaneous - OUTPUTT4 - UWM 6445, NanQ
OUTPUT4 ASCII format closes off a matrix with an extra column. An arbitrary
number is placed in this column, which is later thrown away. On NT and Compaq
DEC Alpha systems this number may be an illegal number which prints as NaNQ
when viewed with an editor. This may also cause the INPUTT4 module to crash
with *** USER WARNING MESSAGE 6445 (INPTT4)
A FORTRAN FORMATTED READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = 12

USER INFORMATION: THE FILE WAS SPECIFIED IN AN ASSIGN FILE MANAGEMENT
STATEMENT
1-4470501
eds Updating
2004
Documentation/QRG - DTABLE Description ne
The description of the DTABLE entry in the Quick Reference Guide needs to be
updated to indicate that it may be referenced by a DVMREL2 entry.
1-4483401
2001.0.3
as Wrong Frequencies
Effective Mass Table - Frequency Column h
When effective mass is calculated for more than 100 modes, the effective mass
listing gives wrong frequencies in the table.
1-4507201
Hang
2004
Distributed Memory Parallel - DMP - Jobs
DMP jobs that encounter DMAP fatal errors in subDMAP PHASE0 may hang. DMAP
level fatal errors which are handled via NOGO/EXIT in subdmap PHASE0 are not
handled correctly.
compile phase0
alter 'if ( stop0'(,4)
if ( nproc>1 ) then $
param //'stsr'/1/-3 $
putsys(0,307) $
endif $ nproc>1
endalter
1-4534835
ACMS - MPCs, PLOTELs - SFM 6802, SEARCH KEY
When using PACMS in a model that has many MPCs (mpc, rbei, etc.) and/or
PLOTELs, the job may fail with the following unclear messages:
*** SYSTEM FATAL MESSAGE 6802 (SEPSUP)
SUPERELEMENT
xx HAS FAILED TO AUTOMATICALLY DERIVE A SEARCH KEY.
USER ACTION: REVIEW MODEL FOR REASONABLE GEOMETRY AND SELECT SEARCH KEY
VIA OVER-RIDE PARAMETER AND/OR REVIEW
GRID POINT LOCATIONS FOR REASONABLE GEOMETRY
Avoidance: The exact cause of this problem is not yet known. Other than using
a serial run, there is no known avoidance. Adjust system cell 360 (from 10 to
2000)
1-4534854
Superelements - EXTRN and PARAM, EXTOUT, DMIGOP2 - SFM 4252
In Version 2001, if an external superelement was created

PARAM,EXTOUT,DMIGOP2, and in the assembly run, PARAM,EXTUNIT is specified in
the Case Control then the run might terminate with SYSTEM FATAL MESSAGE 4252,
indicating that matrix XAAV does not exist for that superelement.
PARAM,EXTUNIT must be specified in the Bulk Data section of the external part
superelement.
1-4557005
Transient Analysis - Enforced Motion - UFM 3046
If modal transient analysis is performed with enforced motion, and there is no

coupling between the calculated modes and the enforced motion dof, the run will
fail with UFM 3046 indicating that no loading has been defined.
Avoidance: The enforced dof must be connected to the model and the attached
dof must have mass and stiffness.
1-4570801
2004
Documentation/QRG - PARM,OPPHIPA
The QRG documentation of the PARAM OPPHIPA should indicate that the resulting
normal modes are output in the global coordinates and refer to OPPHIB for the
option to have basic output.
1-4586601
Complex Eigenvalues - system(108)=4 - Incorrect Eigenvectors
There can be a difference in behavior for small problems for

the following reason:
The Lanczos method is designed and intended to be used to extract
a small number (no more than 10% of the total) eigenvalues from "large"
matrices
(say, more than 500 dof). For small matrices ( under 100dof), the QZ
Hessenberg
method should be more efficient, robust and accurate. So, when CLAN is
specified on the EIGC entry and the problem has 100 dof or less, QZ HESS is
used
to perform the analysis. This is similar to what happens in READ: when LAN is
specified
and the problem is small, AHOU is used.
However, sys108=4 forces Complex Lanczos, no matter what the problem size.
There could be a small model where Lanczos cannot find all of the required
modes, but QZ HESS can. No such model is provided in this CR, but if such
a model were created, then specifying sys108=4 would fail, while using CLAN
on the EIGC entry would succeed due to the automatic switch to QZ HESS.
If such a model is created, please attach it to the CR and open it again.
SYSTEM(108)=4 forces the new block complex Lanczos method. However in some
cases SYSTEM(108)=4 may not behave the same as specifying CLAN and may produce
incorrect complex eigenvectors.
Avoidance: Don't use system(108), specify CLAN on the EIGC entry.
1-4590301
2004
Axisymmetric Fluid Elements - PRESPT, RIN
GFL, CFLUIDi - Wrong Answers on Cray
Reran the following tests in v2005t1 on nihau and updated
archives(v2004,v2005): csr7377.f05 d07d2.f05 d10702.f05
e2280.f05 hydr26.f05 hydr27.f05 p3b1.f05 p3b2.f05
parcmp.f05 s32585a.f05 s32585b.f05 s34774c.f05
s34774c1.f05 s34774d.f05 s34774d1.f05 abb 1/12/04
Fluid pressure output at PRESPT points for axisymmetric fluid elements is
incorrect on all short word machines. Only the Cray gives correct answers.
1-4590602
2001.0.3
Optimization - Incorrect PCOMP Punch outp
ut when SOUTI = BLANK or "NO" on PCOMP entry
Solution 200 will generate incorrect punched PCOMP entries when the SOUTI field
is blank or "NO". On the punched entries the SOUTi field is populated with
"STRN" instead of "YES" or "NO". Reading this entry into Nastran will yield a
fatal message.
Also SOL200 generates designed PBEAM for both END A and B data for a constant
section beam. For constant section beams only END A data for PBEAM and PBEAML
should be output.
Avoidance: The only avoidance is to edit the punch file.
1-4598306
Dynamics - PBUSHD, TABLED1 - SFM 3001
For some problems, if a pbusht references a non-existing tabled1, then the job
may fail with the following unclear messages:
BIOMSG: ERROR 3001 HAS OCCURRED IN ROUTINE SYSTEM , FILE INDEX =
0.
STATUS =
0
INDEX LOGNAME
STREAM_ID
NAME
Avoidance: Provide the missing tables.

This is a user error because no TABLED1 entries exist. The program exits
normally after issuing SFM 3001
from EMG to indicate that the input data block DITID does not exist. The BIOMSG
ERROR messages are printed out because DIAG 44 is turned on.
1-4635614
ut datablocks
2004
Documentation - Vecplot - # of input/outp
In section 10.3 of the MSC.Nastran 2001 Release Guide, "Summary of DMAP Module
changes from V70.7 to MSC.Nastran V2001", the VECPLOT module description for
v2001 should be changed from
VECPLOT XG,BGPDT,SCSTM,CSTM,CASECC,{LAMA or USET}, MEDGE,x66p,vgq,rbf/
XOUT,RESMAX,HEADCNTL,x66/
S,N,GRDPNT/COORID/IOPT/TITLE1/TITLE2/TITLE3/
ALTSHAPE/WTMASS/SEID/setnam/rbfail $
to
VECPLOT XG,BGPDT,SCSTM,CSTM,CASECC,{LAMA or USET}, MEDGE,x66p,vgq/
XOUT,RESMAX,HEADCNTL,x66,gcfxx/
S,N,GRDPNT/COORID/IOPT/TITLE1/TITLE2/TITLE3/
ALTSHAPE/WTMASS/SEID/setnam/rbfail $
wher GCFxx is the ground check force.
1-4638015
2001.0.3
Property for Shear Center Location
Beam Library - CHAN, CHAN1, CHAN2 - Wrong
The beam library (PBEAML) calculates an incorrect shear center for the CHAN,
CHAN1, and CHAN2 cross sections. Patran uses the Nastran routines and also
calculates an incorrect shear center.
1-4659227
Plotting - XYPLOTs on HP Machines
Plotps on HP machines may fail to generate a readable postscript file due to

underflow processing. A xyplot with computed zeros for response quantities may
cause the plotps program on HP to place ****** in a postscript instruction.
Avoidance: Don't try to plot results that are computed zeros. Use the xyprint
feature of the program to identify potential problems and avoid requesting
these plots.
********************************************************************************
********************************************************************************
******************************
NJ Teng: As of 03/14/2008
Need to find an HP machine to reproduce the problem.
********************************************************************************
********************************************************************************
******************************
1-4668001
ames
2004
Documentation/QRG - INCLUDE - Long File N
MSC.Nastran 70.7 & 2001 INCLUDE statement can be longer than 72 characters,
even though the QRG indicates there is a 72 character limit (Remark 2 in the
INCLUDE keyword documentation)
Avoidance: The MSC.Nastran Configuration and Operations Guide, Section 4.9
indicates how to use long filenames.
1-4669601
Documentation/DMAP - ADD5 - CD Parameter
When the add5 module has a purged CS parameter for a data block, and an
explicit CD parameter set equal to zero, the module uses the default for the CS
parameter, which is 1.0. Complex Double paremeters used as inputs to the add5
module should not be set to zero values.
This is a limitation that should be
documented.
Avoidance: If a variable parameter is used to set the value of the DP input
parameters, and its value can be the DP equivalent of zero, the default value
of the corresponding SP parameter will be used instead. That happens to be
unity, unless changed with an explicit value. When using DP paramters set by
variable parameters, it is therefore a good practice to use calls of the form
ADD5 A,B,C,D,E/X/0./0./0./0./0./ALPHAD/BETAD . . etc.
1-4672328
Answers
2004
Enforced Motion - SDAMP, TABDMP1 - Wrong
If a high modal damping level is used with the new enforced motion capability
in MSC.Nastran 2001, then the answers may be incorrect. The effect on results
is not significant unless the modal damping value is high.
1. Approximate the modal damping with structural damping. See quality
1-5399310
2. Put the entire structure in a superelement and apply the modal damping to
the superelement.
1-4674201
2004
Documentation/QRG - PARTN Case Control Co
mmand Disabled
In coupled fluid structural analysis the PARTN Case Control command has been
disabled for Version 2001 but the Remark 2 under the QRG description of this
command was not removed.
This capability is being replaced by the FSLPOUT
command.
1-4678201
Acoustic Analysis - LFREQ PARAM is ignored in Fluid Participa
tion Factor Calculation
JoeM, The attached file contains an include for a file that is not in the list
of attachments. Please attach the missing file or attach another example that
demonstrates the problem. I am re-setting the status to open until I hear back
from you. It might even be that our latest efforts resolving related
difficulties may have solved this one too, but I will look into it if you
provide a deck. Thanks. Joe Cole 3/19/2008
The LFREQ param is ignored when calculating the fluid participation factors in
Version 2001, sol 111, using FLUIDMP & STRUCTMP params.
1-4698707
e
Restart - nonlinear, param,post,0 - Missing Output in xdb fil
In a nonlinear static restart run, the xdb does not contain all the output for
all the requested load steps.
Avoidance: Use op2 by selecting param,post,-2 or -1, instead of param,post,0.
1-4702701
2001.0.3
k in Unsymmetric Decomp
Parallel Methods - SYSTEM(107) - Tracebac
Shared memory parallel executions (system(107)=n) will give a traceback on Cray

SV1 2001.0.1 systems in unsymmetric decomp if the high rank system cell 221 is
set to other than 1.
Avoidance: High ranks is not supported for parallel on this platform. The
default for system(221) has been set back to 1 in 2001.0.3 to correct this
error.
1-4717576
sage
2004
Elements - GEOMCHECK - UWM 9031, Poor Mes
If a model contains elements which cause unusable matrices, the default value
of INFORM on the GEOMCHECK statement will not print a FATAL message. Therefore,
the run might fail later in the process with a message which does not indicate
the elements which caused the problem. In one example, a user encountered the
following message with multiple elements which gave bad jacobians:
^^^ USER WARNING MESSAGE 9031 (ERRPH1)
^^^ NOGO ENCOUNTERED IN SUBDMAP
SEMG
Avoidance: Use the FATAL option on GEOMCHECK rather than try to run a model
with bad elements.
1-4721414
Nonlinear Analysis/Loads - RFORCE - UWM 6584
USER WARNING MESSAGE 6584 might be incorrectly issued in SOL 106 if an RFORCE
load is used.
Avoidance: If p-elements or coupled mass are not being used, this message
can be ignored.
1-4724901
2004
ng reference to TEMPBC
Documentation/QRG - TLOAD1/TLOAD2 - Missi
Remark 4 under the description of the TLOAD1 and TLOAD2 entry in the
MSC.Nastran 2001 Quick Reference Guide should include the TEMPBC entry:
4. EXCITEDID may reference sets containing QHBDY, QBDYi, QVECT, QVOL and
TEMPBC entries when using the heat transfer option.
1-4733501
2004
DRMM,-1 - SFM 5423 (DMPYAD)
Frequency Response - SPCD, OFREQ, PARAM,D
When OFREQ is used with PARAM,DDRMM,-1 to output ESE (or EKE/EDE) in an SPCD
Sol 111 run, get the FATAL error:
compile disprs
alter 15,15 $ V2001
if( otf>0 and noypo>0 ) modacc casef,fol,ypo,,,/
fol00,ypo1,,,/app $
alter 30,30 $ V2001
if ( otf=0 and noypo>0 ) equivx ypo/ypo1/-1 $
alter 89,89 $ V2001
CALL SPMPYAD RPH1,UHF1,YPO1,V01DR/UPX/0/1 $
1-4734006
MTRXIN
2004
Superelements - CSUPER, EXTRN - UFM 2065
If DMIGDB is used when creating external superelements and they are brought
into the analysis using the CSUPER entry, the program will issue the message:
USER FATAL MESSAGE 2065 (MTRXIN)
if SPOINTs are referenced.
compile phase0
alter 'GP1
GEOM1I','GP1
GEOM1I'
GP1
GEOM1I,geom2scr,,,,,/
XGPLS,XEQEXINS,XGPDTS,XCSTMS,XBGPDTS,
XSILS,XVGFS,,/
S,N,XLUSETS/0/NOGPDT/////SEID $
endalter
1-4734222
2004
- SIM 6491, Wrong Answers
A complex eigenvalue analysis that produced reasonable answers in Version 70.5

is producing wrong answers in Version 2001 using complex Lanczos after issuing
the message:
*** SYSTEM INFORMATION MESSAGE 6941 (CLSCLD)
INVARIANT SUBSPACE DETECTED IN BLOCK LANCZOS.
Avoidance: The problem is still under investigation - using SOL 110 with HESS
produced the same results as the Lanczos method in Version 70.5. Setting
SYSTEM(108)=2 to force the old method or setting SYSTEM(108)=64 to force full
orthoganalization also avoided the problem.
1-4747001
ng Answers
2004
Eigenvalue Analysis - PARAM,MECHFIX - Wro
If PARAM,MECHFIX,YES is set or if MSC.Nastran encounters difficulties in the

eigenvalue analysis and it automatically enters the massless mechanism control
but no massless mechanisms are found, then rigid body modes may be incorrectly
constrained.
Avoidance: See SSSALTER mmfindfix.v2001 on the SSSALTER web page for an
avoidance. Another avoidance is to use param, mechfix, no, and fix any
mechanism errors that appear manually.
1-4748406
2001.0.3
Grid Point Force - GPFORCE, TEMP(LOAD), D
EFORM - Possible Wrong Answers or Overflow
Grid point force balance (case control GPFOR request) may fail or give wrong
answers if there are thermal or deform loads (case control TEMP or DEFORM
requests). The failure has been observed as either bad answers or an abort due
to overflow. The bad answers can be recognized if the grid
point TOTALS are not computed zeros. Only GPFDR results are affected, all
other output (such as displacements, spcforces, stresses, etc.) is not
affected. This error only occurs on version 2001.0.1 and is unlikely
for small models.
1-4748439
2004
Miscellaneous - OUTPUT2 - Missing Modes
If a user program is designed to read the element strain energy output from an
OUTPUT2 (op2) file created by Version 2001, it is possible that the program
might only find the first mode.
Avoidance: This problem is actually due to an error fix in 2001. In the table
description in the NDDL, it indicates that word 5 in the IDENT record of the
element strain energy is the mode number. In Version 2001, this is correct. In
previous versions, the mode number was incorrectly written in word 4. Many
programs which read OUTPUT2 files are looking for the mode id in word 4 and
will not find it in a v2001 OUTPUT2 file. The reading program needs to be
updated.
1-4807909
2004
nswers for Rotational Inertia Terms
Modal Effective Mass - MEFFMASS - Wrong A
The output for Modal effective mass (MEFFMASS) may have wrong values for the
rotational inertia terms.
Avoidance: Use the alter effmassa.v707 from the V70.7 sssalter directory.
1-4807929
Output
2008.0.0 (MD R3)
Miscellaneous - PARAM, AENLTOL - Missing
If the bulk data section contains a parameter called AENLTOL with a real value,
the run will terminate before printing the sorted bulk data (in module XSORT)
with no messages
Avoidance: Do not use this parameter name
Comment from JAS: This error was introduced when code was added to XSORSO to
handle PARAM,NLTOL,<integer value>. Since t his change was added by Ed
Dickerso, I am assigning this issue to him.
1-4819505
2001.0.7
- Missing Data in the USRDATA field on a DRESP3 entry
When the USRDATA field is present on a DRESP3 entry, the first part of the
string input data may be lost. The following remedies may be used to avoid the
data loss:
1) If the DRESP3 entry does not include any DNODE item, start the string input
from the fifth letter in the USRDATA field;
2) If the DRESP3 entry includes one pair of DNODE items, no action is needed;
3) If the DRESP3 entry includes more than one pair of DNODE items, the forward
offset in the server routine, r3svald/s is required to obtain the original
string input. The actual offset value may be obtained experimentlly.
1-4830716
2004
ectors not Calculated
Superelements - PARAM,RESVEC - Residual V
If a model has superelements and PARAM,RESVEC,YES is specified in the main bulk

data section, it is possible that the program will not calculate residual
vectors.
Avoidance: Either move PARAM,RESVEC,YES into the case control above all
subcases or include the following DMAP alter in your file:
compile phase1dr
alter 'sep2dr.*slist.*emap' $ line 80
pvt pvts,//s,n,dummy21 $
1-4833901
2004
EQ - SFM 3001 (MODACC)
Distributed Memory Parallel - OMODES, OFR
The presence of an OMODES or OFREQ case control request will result in a SYSTEM
FATAL MESSAGE 3001 from the MODACC module, if DOMAINSOLVER GDMODES is used.
This is a DMP method for SOL 103.
Avoidance:
Workaround is to apply the following alter:
compile super3 $
alter 'EQUIVX CASEcc\/CASEDR' $
EQUIVX UL/ULS/-1 $
compile sedisp $
alter 'equivx ul\/un'(2),''(2,1) $
equivx ul1/un/nosset $
if ( nosset>-1 ) umerge uset,ys,ul1/un/'N'/'S' $
endalter
1-4835004
2001.0.3
SDF, ATOC, or RALL
Random Analysis - No results when using P
If random output is requested using the PSDF, RTOC, or RALL options in case
control, no output will be produced unless there is a SORT2 output request or

an XYPLOT request for random output.
Avoidance: Although there is no printed output from these options, the output
datablocks can be created by adding a single XYPLOT command which requests
random output or requesting SORT2 output.
1-4837703
mentation
2004
Documentation/QRG - DRESP3 - Missing Docu
The DRESP3 (External Response) capability was developed as a funded project

that was intentionally not documented in the 2001 Release Guide but can now be
discussed.
The design optimization capability (SOL 200) in MSC.Nastran has a powerful
DRESP2 feature allowing the user to create a synthetic response. However, the
types of variables that a synthetic response can use are limited to the data
from MSC.Nastran. The external response feature extends the synthetic response
by allowing the user to define a custom response using either in-house programs
or any application programs written in Fortran, C or other languages. This
enables the use of proprietary responses as the objective or a constraint in a
design. The documentation for this feature is available in Solution 1-3772901
1-4854701
6984
2004
Frequency Response - CRAC2D, CRAC3D - SFM
The CRAC2D(ADUM8) and the CRAC3D(ADUM9) elements are not supposed to have any
frequency (SDR2) data recovery and should simply return when running frequency
response such as SOL 108. Instead they crash with SYSTEM FATAL MESSAGE 6984
(SDR2RD)
INCORRECT NUMBER OF WORDS BEING REQUESTED FOR TRANSMISSION TO AND BY PHASE-2
ROUTINE.
1-4855904
2004
ue for SYSTEM(166)
Documentation/QRG - Incorrect default val
The Quick Reference Guide incorrectly states that the default value for SYSTEM
cell 166 is 1. The actual default is 0.
The following alter will allow you to view the default value:
compile seaero
alter 1
type parm,,i,n,sys166 $
sys166 =getsys(sys166,166) $
message //' the value of system cell 166 is '/sys166 $
exit $ OPTIONAL
endalter $
$
1-4866203
not EKE.
2004
Documentation/QRG - PARAM,OUMU is for ESE
The Quick Reference Guide incorrectly states that parameter OUMU is for element
kinetic energy. It is for element strain energy.
1-4866209
ra Output
2004
Eigenvalue Analysis - PARAM,POST,-1 - Ext
If you specify PARAM,POST,-1 and PARAM,POSTEXT,NO in SOL 103, the program

will still unnecessarily calculate and write ONRGY2 to the OUTPUT2 file if you
have requested ESE output.

Avoidance: Set PARAM,OUMU,NO and the datablock will not be calculated or
written.
1-4880311
9
2004
SSSALTER - trncompa.v2001 fails in SOL 10
SSSALTER trncompa.v2001 will fail in SOl 109.

Avoidance: Request an updated alter from MSC or get a copy from the MSC web
site at:
http://www.mscsoftware.com/support/prod_support/nastran/sssalters/v2001/toc.cfm
1-4885505
007 (VECPLOT)
2001.0.3
Miscellaneous - WEIGHTCHECK, QSET - SFM 3
If WEIGHTCHECK or GROUNDCHECK is requested for a model with superelements and

the Q-set is defined using GRID points, the program will issue
*** SYSTEM FATAL MESSAGE 3007 (VECPLOT)
Avoidance: Either remove the WEIGHTCHECK request or don't use GRID points for
the Q-set degrees of freedom.
1-4891701
2004
may lead to overflow.
Materials - MAT1 - Large Property Values
Large magnitudes for the values of the material properties on the MAT1 bulk
data entry can cause floating point overflows in the material property lookup
routines.
Avoidance: Be sure that the magnitudes of the properties are less than the SQRT
of the largest magnitude number representable on the machine.
1-4902401
PYAD)
2001.0.7
Case Control - OFREQ, SPCD - SFM 5423 (DM
If the OFREQ Case Control command specifies different sets in different

subcases that reference SPCD type loads, then an incompatible matrix multiple
may result.
TRAILER FOR RPH
TRAILER FOR PPF
TRAILER FOR PYHF
IS
IS
IS
101
102
103
COLS ROWS FORM

23 504
868 504
651
23
Avoidance: Follow the recommendation desribed in Remark 7 under the OFREQ Case
Control Command desription in the Quick Reference Guide.
1-4915301
6137
Non Linear Buckling - PARAM,BUCKLE,2, NLPARM with AUTO - UIM
Non Linear Buckling with PARAM,BUCKLE,2 does not work with the AUTO KMETHOD
option on the NLPARAM entry. If an analyis contains these entries
iInformation message 6137 and user warning message 4698 listing almost all DOF
with MAXRATIO may be encountered.
Avoidance: User the ITER KMETHOD option.

1-4922804
2001.0.3
SDRX - UFM 2025
Optimization/Design Sensitivity - PLOAD1,
In solution 200, multiple PLOAD1 sets may result in USER FATAL MESSAGE 2025 in
the SDRX module.
1-4936611
igin Only
SSSALTER - checka - Modal Effective Weight is given around Or
When modal effective weight is calculated in checka, it will be calculated

about the origin no matter what value you give for GRDPNT.
Avoidance: Insert the following line after COMPILE KEEFW
TYPE PARM,,I,Y,GRDPNT=0
1-4938101
2001.0.3
PEAML - SFM 3007 (DOPR1)
SYSTEM FATAL MESSAGE 3007 (DOPR1) ILLEGAL INPUT TO DOP1E may be issued if
DVPREL1 entries point to designed PBARL's or PBEAML's while other DVPREL1
entries point to PBEAM's or PBEAML's.
Avoidance: The only sure avoidance is to not design PBARL's or PBEAML's with
PBEAM's or PBEAML's
1-4948003
2001.0.3
- ILLEGAL INPUT TO SUBROUTINE DSAD12
Optimization/Design Sensitivity - SUBCOM
The fatal message below may occur when SUBCOM's are used in SOL 200 with a
SUBSEQ request that references a single subcase.
USER FATAL MESSAGE
Avoidance: Either eliminate the SUBCOM request or reference more than one
subcase with the SUBSEQ. The Ri coefficients on the SUBSEQ can be 0.0
1-4966701
2004
rmalization - Possible Wrong Answers
Eigenvalue Analysis - MEFFMASS and MAX no
If the max option is used in the eigenvalue calculation, then the modal
effective mass output will be off by the generalized mass term. The modal
effective mass fraction, however, is correct.
Avoidance: Use the default mass option or insert the DMAP alter found in the
attachments.
1-4966763
Error
2005
Complex Eigenvalue - SGI - Signal 10: Bus
John, I think most of the old bus errors have been fixed in
v2004 or v2005, if it's ok please close this error.
On the SGI, it has been reported that on a large modal complex eigenvalue
problem, the job terminates without any messages in the f06 file. The log
file, however, contains the following messages:

Job aborting...
Unable to call dbx for trace: Resource temporarily unavailable
Error unable to remove temp file: /tmp/tt1376064
This type of error is generally due to a misalignment problem and can only
occur with the exact combination of memory usage, buffsize, other jobs running
the background, and what the operating system is doing. It may occur on the
SGI, SUN, and HP. MSC.Software has not duplicated this error on this
particular model.
Avoidance: Rerunning the job as it. Otherwise, changing the buffsize or memory
may also work.
1-5001808
2004
ting Point Exception
Miscellaneous - READ, PARAM,RESVEC - Floa
If all modes of a model are calculated and residual vectors are requested, the
run will fail in the second eigenvalue solution with a floating point
exception.
Avoidance: This error only occurs when the static solution cannot be
represented by a combination of all modes of the model. Then the residual
vector contains only dof which have no mass associated with them (and
therefore, an infinite eigenvalue). The avoidance is to not request residual
vectors when all modes of the model are found.
1-5009015
2001.0.3
Heat Transfer - VIEW - Large models may p
unch impropely formatted RADLST entries
Improperly formatted RADLST entries may be output from the VIEW module in heat
transfer analysis of large models.
1-5014405
2004
Cyclic Buckling - SOL 116 - Wrong Answers
In SOL 116 (buckling with cyclic symmetry), boundary conditions may not be
changed between the static preload and the buckling eigenanalysis subcases
leading to wrong answers.
COMPILE CYCBUCKL
ALTER 'ISOLAPP=2' $
CALL SETQ CASERS//
S,SPC/S,LOAD/S,DEFORM/S,TEMPLD/S,P2G/S,DYRD/
S,METH/S,MFLUID $
DELETE /CYCD,,,, $
CYCLIC2 GEOM4S,EQEXINS,USET/CYCD/NSEG/CTYPE $
endalter
1-5023407
Answers
2004
SSSALTERS - rigyroa alter sync=no - Wrong
Complex eigenvalues using the ridgyroa alter with sync=no and Lanczos causes
incorrect mode shapes in v70.7 and v2001.
Avoidance: Use system(108)=2 or the Hessenberg method.
1-5023428
2004
Elements - CBUSH - Unexpected Answers
If the user defines a cbush entry with the same grid id for end A and end B,
the cbush will be grounded. This input should result in a fatal error.
1-5023444
or PCOMP
2004
Miscellaneous - Incorrect ELSUM results f
In V2001, using the ELSUM Case Control command with a plate element that
references a PCOMP entry using the BEND option on the LAM field causes wrong
large numbers in the Structural Mass field of the ELSUM printout.
1-5052701
Eigenvalue Analysis - EIGRL - SFM 7340 lnnp2cd -729
The error message:

Lanczos *** SYSTEM FATAL MESSAGE 7340 (LNNHERR). . LNNP2CD. .(IER = -729)
may occur when the number of eigenvectors requested (ND) is greater than the
number in the structure. Evidence of this occuring is that the size of the
shifts increases at many steps, as listed in UIM 5010, but the number of
eigenvalues below the shift does not increase.
Avoidance: Decrease ND to the number found, or use FMAX instead.
1-5065701
2001.0.3
ut scrambled in incorrect order
Automatic Component Mode Synthesis - Outp
Running ACMS in SOL 111 with multi-grid, multi-frequency, multi-subcase, and

multi-output requests produces correct results but in the wrong order. That
is, the data from one subcase is not contiguous in the OFP data blocks.
1-5067801
.
2001.0.9
MEFFMASS - EFFMAS - SFM 4276, EC 7777 tbk
When requesting MEFFMASS in V2001 on an Alpha machine: BIOMSG: ERROR

HAS OCCURRED IN ROUTINE tbk.
Occurs while executing DMAP statement EFFMAS BEGN
7777
Avoidance: Other than running on a different platform, there is no known

avoidance.
Fixed in 2001r4.
Verified test problem runs nast2002t2 May29 build.
1-5079301
2001.0.3
rect senstivities with the PBEAML
Optimization/Design Sensitivities - Incor
The sensitivity of the N1(b) and N2(a) properties with respect to the PBEAML
dimensions are reversed. This can result in errors in the element response
sensitivities. To date, this error has only appeared to be significant with
the HAT1 section type.
Avoidance: If neutral axis locations are important, the only complete avoidance
is to replace the PBEAML with a PBEAM and use DVPREL2 relations to specify the
beam dimension/property relationships.
1-5081408
2005
SFM 3007 (DSFLTF)
Optimization/Design Sensitivity - CEIG -
In an optimization run, if the number of complex eigenvectors calculated are

less than the number of complex eigenvalues referenced on the DRESP1 entries,
then the job will fail with the following unclear error messages:
ILLEGAL INPUT TO SUBROUTINE DSFLTF
0FATAL ERROR
Avoidance: Make sure that the number of the complex eigenvectors requested is
equal to or greater than the number of complex eigenvalues referenced on the
DRESP1 entries.
This problem has been fixed in v2001 awhile back. Possibly before v2001 was
released. ---GDC
1-5088301
(BNDRYINFO)
2001.0.3
Superelements - QSET, EXTSEOUT - SFM 3200
A SOL 103 external superelement creation run using the EXTSEOUT Case Control
command with BULK=PUNCH option fails with SFM 3200 in the BDRYINFO module
(caused by logic error 11 in subroutine BDYINP) if the number of Q-set SPOINTs
specified is odd.
Avoidance: Use an even number of Q-set points.
1-5089207
2004
of OEE datablock.
Documentation/DMAP - Error in Description
In the NDDL description of datablock OEE in the DMAP Module Dictionary, there
is an error in the comment notes describing the approach codes.
The values for approach codes 1 thru 5 are correct, but
Approach code =6 should be Transient (not Buckling part 1)
the values after this should be increased by 1.
IE.
Approach Code Solution Type
1
Statics
2
Reigen
3
DS0
4
DS1
5
FREQ
6
TRANS
7
BKL0
8
BKL1
9
Complex Eigen
10
NonLinear Statics
etc
1-5093401
2004
Optimization/Design Sensitivity - Poor Me
ssage when DRESP2 incorrectly refers to DESVAR labels
Optimization run fail with no meaningful message when DRESP2 entries
incorrectly refer to DESVAR labels rather than ids.
The following is an example of the error message in log files:
for SUNS
iio: [-1] end of file

lately: writing sequential formatted internal IO
part of last string: |
for HP
*** FORTRAN I/O ERROR 958: FORMAT DESCRIPTOR INCOMPATIBLE WITH CHARACTER ITEM
IN I/O LIST
INTERNAL FILE.
LAST FORMAT: (I8,"|
There are no messages in the f04 file and f06 file.
The job fails with the correct error message on NT and in version 70.7 on unix.
1-5104006
2001.0.3
PBEAML - Divide by Zero
For closed hat sections, the input constraints are checked, but the less
stringent of 'GT' is utilized. This may cause a divide by zero in the RJ
computation.
Avoidance: To avoid the floating point divide by zero, observe the following
constraints on DIMx for HAT1 sections (closed hat)
1. DIM1>DIM3
2. DIM1>2*DIM4
3. DIM2>2*DIM4+DIM5
1-5104009
2001.0.4
- Incorrect Sensitivities
For tapered PBEAML, cw(b), na1(b) and/or na2(b) are perturbed when end a DIMx
are designed. Although this is not correct, the impact on sensitivity is not
expected to be significant.
1-5109902
2001.0.3
- Poor Accuracy
Automatic Component Mode Synthesis - ACMS
The accuracy of the dynamic response output (SOL 111 and 112) may be reduced
due the the retention of an inadequate number of Q-set points in the residual
structure.
If the number of O-set modes, plus the number of associated residual vectors,
is greater than [ngrids/(numdom*4)], the accuracy may suffer.
Avoidance: Include the following bulk data entry:
senqset,0,N
where N is greater or equal to the required number of Qset points.
1-5126706
3
2001.0.3
Dynamic Analysis - SPCD, BNDSPC - UFM 608
If the new Version 2001 dynamic enforced motion is used with multiple input
locations, it is possible that the run might fail incorrectly with UFM 6083 in
BNDSPC, indicating a long list of points which do not exist.
Avoidance:
This problem has only been seen on Windows/NT systems. If this problem is
encountered it may be avoided by defining an ASET.
1-5129501
5 (PREFACE)
2001.0.3
Superelements - EXTSEOUT, CORD2x - UFM 31
An external superelement creation run with a boundary grid point referencing a

CORD2x displacement coordinate system and using the EXTSEOUT Case Control
command with BULK=PUNCH option fails with UFM 315 in the Preface in a
subsequent assembly run due to a missing asterisk (*) in the CORD2x name field.
1-5129505
M 5290 (GPSP)
2001.0.3
Superelements - EXTSEOUT, BULK=PUNCH - UF
A SOL 103 superelement assembly run employing an external superelement created

in an earlier run by using the EXTSEOUT Case Control command and BULK=PUNCH
fails with UFM 5290 in the GPSP module if one or more A-set points of the
external superelement are not on the boundary.
See also related Quality 1-4371807; the difference between these qualities is
that this quality employs the BULK=PUNCH option.
1-5131904
2001.0.3
s not support DRESP1=CSTRAIN
Optimization/Design Sensitivity - FSD doe
Fully stressed design optimization runs do not fully support DRESP1=CSTRAIN.

1-5155018
ue
2004
Elements - PBEAML, HAT1 - Incorrect J Val
The QRG description of the HAT1 section of the PBEAML and PBARL incorrectly
describes dimensions as "Di" instead of "DIMi" and is missing the length of the
horizontal leg.
In addition, for both the HAT and the HAT1 sections, the torsional moment of
inertia incorrectly uses the open section equations instead of closed section
equations. This is incorrect for the HAT1 because it is shown as closed and
for the HAT because hats are by definition always attached to skins. A remark
needs to be added to this effect. In the unlikely event that a hat is used as
open (for instance, upside down), an option needs to be added to select an open
section calculation.
1-5162113
2004
GPFDR if ESE not in all REPCASEs
Element Strain Energy - SFM 4276 EC 31 in
If a file contains REPCASEs and ESE output is requested in some, but not all,
REPCASEs and SUBCASEs, the run may fail with SFM 4276 EC 31.
Avoidance: Place an ESE request in all SUBCASEs and REPCASEs.
1-5169004
2001.0.3
SFM 3200 (BDRINFO)
Superelements - EXTSEOUT, CORD2R, QSET -
A SOL 103 external superelement creation run with 9 boundary grid points, 120
Q-set SPOINTs and 15 CORD2R Bulk Data entries and using the EXTSEOUT Case
Control command terminates with SFM 3200 in the BDRYINFO module with Logic
Error 11 in subroutine BDYINF.
This problem is caused by a serious error associated with memory management in
the BDRYINFO module. There is no easy avoidance for this. The user may be
able to avoid it
if he reduces the number of grid points, Q-set SPOINTs or CORD2x entries (if
any) or a combination thereof in his input data.
1-5174501
2004
yields incorrect J value.
Elements - PBARL and PBEAML HAT1 Sections
The J calculated by MSC.Nastran for the PBARL and PBEAML HAT1 section is wrong.
1-5204241
2004.0.5
symmetric decomp
Heat Transfer - VIEW - Poor Efficiency-un
In nonlinear heat transfer solution with view factor calculations, unsymmetric

decomp is unnecessarily used. Since all the matrices are symmetric, sparse
symmetric decompositon should be used by default. Unsymmetric decomp requires
twices the memory to run and frequently will encounter UFM 6136, insufficient
core for numeric phase of sparse decomposition.
Avoidance: Set NASTRAN SYSTEM(209)=0 This forces the unsymmetric decomposition
with active columns which requires less memory to run as compared to the newer
sparse unsymmetric decomp.
dmap avoidance: using symmetric solver
SOL 153
compile nlstatic list noref
alter 'IF ( DCMPKLLT ) DCMP' (1,-1)$
modtrl kllrh////6/$
CEND
1-5233709
2004
Dynamics - MEFFMASS - SFM 3007 (EFFMAS)
If effective mass is requested and there is no s-set in the model, the job will
*** SYSTEM FATAL MESSAGE 3007 (EFFMAS)
Avoidance: Add and constrain a dummy grid point in the model.
1-5233716
2001.0.9
Dynamics - MEFFMASS - UFM 2025 (EFFMAS)
In a large model that has many coordinate systems and requesting effective mass
output (MEFFMASS), the job may fail with the following error messages
*** USER FATAL MESSAGE 2025 (EFFMAS)
UNDEFINED COORDINATE SYSTEM ID = xxxx
This error occurs even though the coordinate system referenced in the message
exists.
Avoidance: The effmass.v707 alter from the v70.7 sssalter library provides
similar output and this alter will run in v2001 also. Removing unused CORD2R
entries may also allow the job to run successfully.
1-5235204
eback in READ
2004
Eigenvalue Analysis - PARAM,RESVEC - Trac
Eigenvalue jobs with residual vectors (param,resvec) may fail ungracefully on

small models. In one example the job issued a traceback in the READ module.
Avoidance: Do no specify residual vectors for small models.
1-5241491
)
2004
Elements - MAT2, PSHELL - UFM 4297 (EQD4D
If a MAT2 entry has no elastic properties and is referenced by a PSHELL entry,

then a misleading message similar to the following may occur:
QUAD4 ELEMENT WITH ID = 16772653
Avoidance: Specify realistic material properties. The message should be
changed to read:
QUAD4 ELEMENT WITH ID = 16772653
CAUSES ARE:
1) THIS ELEMENT HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180
DEGREES.
2) NO ELASTIC PROPERTIES ARE ENTERED
3) G12 IS BLANK ON THE MAT8 ENTRY
4) G33 IS BLANK ON THE MAT2 ENTRY
5) MAT2 IN NOT POSITIVE DEFINITE
1-5271102
Results
2004
ACMS - PARAM,POST - Can not Post Process
In ACMS for certain post-processing programs, the data block names don't match
the names expected by the post-processor. This prevents these data blocks from
being imported into the post-processing program.
Note that Patran can read these names without any problems.
Avoidance: Please contact MSC Support for A DMAP alter avoidance.
1-5284409
2001.0.5
Optimization - DSAD, DRESP2 - Signal 11
If a DRESP2 references another DRESP2, and the referenced DRESP2 is actually an

implied DRESP2 (e.g., DRESP1 using the RSS option), then depending on the
machine, the job may fail with the following message in the f06 file
MAIN: For reference, A(MAINAL) = 401380, A(/SYSTEM/) = 193e800
MAIN:
A(/XNSTRN/) = 3370020
or it may fail without any message in the f06. The following message may
appear in the log file in this case.
Avoidance: There are 2 possible avoidances:
1. Add a dummy DRESP1 to the calling DRESP2

or
2. Define the referenced DRESP2 explicitly.
1-5284424
2004
ESPCH1,-4 - Missing DRESP1 entries in punch output
The punch file does not contain the DRESP1 entries when using param,despch1,-4
Avoidance: This is a documentation error. The design intent is that only mode
tracking related (RTYPE=FREQ and/or EIGN) are to be printed when despch1 = + or
-4
1-5301301
RESTARTS - METHOD - Eigenvalues not recalculated
SOL 103 restarts where the method command is changed in the Case Control will
not modes.
Avoidance: Use param,serst, manual and seall=0 commands.
1-5328702
2004
rrect with non-structural mass
Miscellaneous - CQUAD4, MAT1 - ELSUM Inco
When a MAT1 entry specifies nonstructural mass on a CQUAD4 element, ELSUM

incorrectly calculates the element and total mass.
1-5328715
2004
Acoustic Analysis - UWM 9031
Nastran Version 70.7.2 gives a clear message (UFM 4659) that a fluid element is
badly shaped, Nastran 2001 fails with
SEMG
without any indication of the problem.
1-5330601
ta
70.7
Miscellaneous - OUTPUT2, DTI - Missing Da
If the formatted option is used for OUTPUT2 of the DTI datablock, then some
information may be missing.
Avoidance: Other than using the binary format, there is no known avoidance.
1-5334628
2004
TSTRU - SFM 3003 (GP3)
Heat Transfer Analysis/Static Analysis -
A static analysis with temperature loads defined by a heat transfer analysis

with the TSTRU case control command with multiple subcases will fail with the
following message in the GP3 module:
*** SYSTEM FATAL MESSAGE 3003 (GP3)
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK GEOM3Y
(FILE 101) IN SUBROUTINE GP3B
0FATAL ERROR
1-5343701
2004
S=MTRANS - Enforced Motion results in SFM 5423

If SOL 200 is requesting modal transient analysis and enforced motion and the
skip factor on the TSTEP entry is not unity then the run terminates with SFM
5423 in the MPYAD module.
compile fea
alter 'trlg'(2),''
TRLG
CASErs,USETD,dlt,,BGPDTS,SILS,CSTMS,TRL,dit,
,,,,,,/
xppt,,,,,TOL,,yptt,ypot/////////1 $
alter 'call disprs casers,tol1,uhtds,',''
call disprs casers,tol1,uhtds,,ppt1,usetd,rph,rpd,
phdh,k2dd,b2dd,mdd,lll,dar,
uset,rgm,mmg1,bmg1,kmg1,,
rgs,msf1,bsf1,ksf1,,kss1,mss1,bss1,ypot,mechg,,,,/
tol2,uht1,pgt1,upt,qpt,qmpt,ypo1/
app/app1/soltyp/drmm/noa/noue/dospcf/dompcf/noph2/
true/0/false $
endalter
1-5361602
2004
et NASTRAN system(210)=1
Heat transfer - SOL 101 - SFM 3007(OFP),s
The following error message may be encountered in heat transfer analyis or in

static analysis with APP HEAT:
*** SYSTEM WARNING MESSAGE 6433 (ZREAD)
THE DECODED C-ITEM "TCODE" OF DATA BLOCK=OEF1X , RECORD=IDENT. EXCEEDS NORMAL
LIMITS "J"=**** "I"= 496.
PROGRAMMER INFORMATION: PROBABLE CAUSE IS WRONG POSITION OF TABLE CODE, OR
EARLIER RESET OF (C) ITEMS.
*** SYSTEM WARNING MESSAGE 3030 (OFP)
THE OFP MODULE CANNOT PRINT THE DATABLOCK OEF1X
USER ACTION: USE THE MATPRN OR TABPT MODULE.
PROGRAMMER INFORMATION: OFP LOC CODE = 510 FILE = 104
*** SYSTEM FATAL MESSAGE 3007 (OFP)
ILLEGAL INPUT TO SUBROUTINE ZREAD
Avoidance: This error only occurs when SYSTEM(201)=1, that is when the NEWPUNCH
option is selected. This option is the default in 2001, so SYSTEM(210) must be
set explicitly to 0 in 2001 to avoid the error.
1-5369401
Sequencing - SEQP Large jobs may fail with Metis reordering
On the NEC, the default sparse matrix reordering method is Metis. The Metis
package has some uncontrolled memory allocation instances (mallocs) that may
cause very large jobs, or jobs featuring dense matrices, to fail via operating
system fault. Beginning in Version MD R3 (2008.0.0) metis may be selected
automatically on an platform. If a job fails in without message, it is
possible that metis is the cause and extreme reordering should be attempted.
Avoidance: If jobs fail in the SEQP module, select Extreme reordering with
sys206=4.
1-5372208
2004
nite Root Aborts UWM 6137
Complex Eigenvalue Analysis - EIGC - Infi
Degrees of freedom with no stiffness may cause complex Lanczos to fail with the
following message:
*** USER FATAL MESSAGE 6138 (UDSFBI)
INSUFFICIENT CORE FOR SPARSE FBS
1002 WORDS

compile ceigrs list $
alter 'cead.*cphdx'(,-1) $
putsys(0,209) $ use active column solver
1-5377220
- UFM 6656
2004
When running optimization with discrete design variables and mode tracking is
used, the following error is obtained:
*** USER FATAL MESSAGE 6656 (MODTRK)
THE TRACKED SUBSET PHGREF OF MODES FROM A PREVIOUS DESIGN CYCLE CAN NOT BE
FOUND.
Avoidance: A dmap alter is available on request.
1-5378704
2004
Documentation/QRG - Elem ID - UFM 316
The explicit grid id and element id must be a positive integer greater than 0
and less than 100,000,000. This is documented for the grid id in the Quick
Reference Guide. However, for element id, the QRG only specfies the lower
bound, but does not the upper bound of 100,000,000. If an element ID of
100,000,000 or greater is used, then the following error messages will be
issued and the results are unpredictable.
Note that internally, nastran can generate larger values (e.g., p-elements).
Avoidance: Define the element id as (0< Integer < 100,000,000)
1-5386201
2004
Transient Heat Transfer - Models with sma
ll relative stiffness fail to converge.
In the transient thermal analysis, varying temperature boundary conditions
require that a value of 1.0e10 be used for the stiffness in conjuction with
SLOAD entry in order to apply time-varying temperature BC. If the model has
very small stiffness, then the transient solution will not converge.
The 1.0e10 is defined in the code and can not be changed by the user.
Avoidance: Change all the TEMPBC,TRAN into SLOAD and CELAS2 combinations.
Else, see the newly implemented NASTRAN TBCMAG=1.0e3 in Nastran Version 2004
1-5386817
2004
Stress Sorting/Filering - PARAM,NUMOUT2,0
causes strange characters in the f06 output
PARAM,NUMOUT2=0, used for filtering stress output according to PARAM,BIGER, may

result in strange characters in the f06 file.
Avoidance: Use PARAM,NUMOUT2=-1.
1-5396501
2001.0.5
- UFM 7137 (DOPR3C)
When an optimization task defines a DRESP2 entry that references an undefined

DESVAR entry, the job fails without a clear message being issued.
Avoidance: Reference only defined DESVAR entries.
1-5399310
rs
2004
Enforced Motion - SPCFORCEs - Wrong Answe
Wrong SPCForces at the enforced motion dofs will result in SOLs 111, 112, and
200 if any of PARAMs G, W3, or W4 are specified.
compile disprs
alter 'call CFORCE ',''
call CFORCE2 USET,rgs,yso,MSs1,BSs1,
KSs1,,fOL1,,,,/
Qpy/
APP/APP /'spcforce'/true $
endalter
If the DMAP option is not available then
add param,ddrmm,-1 to the input file.
1-5409701
2008.0.0 (MD R3)
Rigid Elements - RBE3 - Wrong Answers
If only one grid point is in the connected DOFs, the answers produced by the
RBE3 may be wrong.
Avoidance: Either replace the rbe3 with an rbar element, which will give
equivalent action, or use the "UM" feature. The error will not occur when this
feature is present.
1-5447411
2005.5
pe 38(gap) missing
Documentation/QRG - TAble A2 - Element ty
Element type (38) cgap is missing from Table A2 in the MSC.Nastran Quick
Reference Guide.
1-5450201
SSSALTER - vma.v2001 withdrawn - Wrong Answers.
SSSALTER vma.v2001 is being withdrawn because it may produce wrong answers, it

is too costly to update and correct, and the means to get most of its
capability without alters is included in Version 2001.
1-5461501
2004
ing read does not have a label.
DMAP - INPUTT2 - SFM 2190 if the file be
If you attempt to read data from a file without a label using a value of -1 or
-3 for ITAPE, then the run will fail with:
*** SYSTEM FATAL MESSAGE 2190 (INPTN2)

ILLEGAL VALUE FOR KEY =
2,
EXPECTED VALUE =
3.
Either write a label on the file when creating it, or do not use -1 or -3 for
ITAPE
1-5461571
answers
2004
Restarts - PARAM,RESVEC - Potential wrong
If residual vectors are requested on a restart run, the program will not
calculate them unless the eigenvalue solution is re-solved. There will be no
warning or information messages issued. If enforced motion is used (V2001+),
this may result in incorrect answers if a restart is made from SOL 103 to
perform the enforced motion solution.
Avoidance:
The following DMAP alter will force the program to re-calculate the residual
vectors on a restart (inlcuding any based on the new loading).
compile modefsrs
$
alter 'call resvec'(,-1)
type parm,,i,n,nophsa
dbstatus phsa//s,n,nophsa $
if(nophsa>0)then $
copy phsa/phsa0 $
copy lama/lama0 $
delete /phsa,lamas $
endif $
endalter
1-5467701
2004
Motion - SFE 4276 in DPD
Superelement Analysis - Enforced Dynamic
Superelement analysis may fail in DPD with the message:

SYSTEM FATAL MESSAGE 4276 (UNPACK)
when enforced dynamic motion is specified.
Avoidance: A workaround is available by including the following DMAP alter:
compile phase1b $
alter 'noys' $
paraml pg//'trailer'/1/s,n,noys $
endalter $
1-5469524
ng Answers
2001.0.9
Nonlinear Analysis - TET10 - Possible Wro
When using the nonlinear tet10 elements, if the material is elastic perfectly
plastic and the default grid option is used, then the stresses may be
incorrect.
Avoidance: Use the GAUSS option by specifying GAUSS in field 6 of the PSOLID
entry.
1-5500401
2004
- BIOMSG: ERROR 31
Optimization/Design Sensitivity - RESTART
Section 7.11 of the V68 MSC/Nastran User's Guide for Design Sensitivity and
Optimization illustrates how to use the restart feature of MSC.Nastran in SOL
200. This capablity is broken with the result that the example case does not
work and will result in a message such as:
BIOMSG: ERROR
31 HAS OCCURRED IN ROUTINE UNPACK
compile desopt
alter 'call predom'
DELETE /RSP2RG,CNTABRG,R1TABRG,DRSTBLG,FRQRPRG $
DELETE /R1VALRG,R2VALRG,CVALRG,wmidg,r3valrg $
DELETE /RESP3RG,rr2idrg,,, $
DELETE /DSCMG,DELW,DELV,DELB,DELF $
compile descon
alter 'dbstatus'
NR1OFFST = 0 $
NR2OFFST = 0 $
NCNOFFST = 0 $
1-5504006
2004
Acoustic Analysis - Modeling Errors lead
to Wrong Answers with No Warning or Fatal Messages
Fluid elements that have geometry should give a fatal message if stucture
points are connected to them but they do not. This includes all fluid elements
except the single GRID CAABSF, the CHACAB, and the CHACBR. The CHACAB and
CHACBR fluid elements have their own rules that must be followed where four
structure GRIDs must be on one side of the hex and four fluid GRIDs must be on
the other. Structure elements with geometry must give fatal errors when
connected to fluid GRIDs. This includes all structure elements except elements
such as CELASi, CDAMPi, CMASSi, CBUSH.
When the above modeling error was present, different results were obtained
between SOL 103 and SOL 111.
1-5509401
2001.0.3
oves 2 gig XDB File Size Limit
Postprocessing - MSC.Nastran 2001.0.3 rem
MSC.Nastran 2001.0.3 effectively removes the 2 gig XDB file size limit. The
default value for buffsize of 1024 will allow a file size of approximately 68
gig but any one object is still limited to 1 gig. While the need for a file
size greater than 68 gig is not likely, the need for an object greater than 1
gig is. Increasing the buffsize to 65535 with the following assign statement
will allow a single object to be 68 gig.
assign dbc='testb.xdb' status=new unit=40 recl=65535
1-5525601
2001.0.7
Mode Tracking - Poor Message
The message below which is output when mode tracking fails is of limited
usefullness and needs to be enhanced by output the filtered and unfiltered
"truth matrix".
TWO OR MORE MODES ARE NEARLY IDENTICAL, WHICH MAKES TRACKING THE MODES NOT
POSSIBLE.
USER ACTION: RERUN USING A SMALLER VALUE ON ONE OR MORE OF THE FOLLOWING:
1) DELXV PARAMETER OF THE DESVAR BULK DATA ENTRY
2) DELP PARAMETER OF THE DOPTPRM BULK DATA ENTRY
3) DELX PARAMETER OF THE DOPTPRM BULK DATA ENTRY

^^^ USER INFORMATION MESSAGE 9051 (FEA)
1-5533601
2004
Continuation Fields
Documentation/QRG - SYSTEM(357) - Ignore
SYSTEM(357) is not documented in the MSC.Nastran 2001 Quick Reference Guide.

This system cell was added for a user request. When set to 1 continuation
fields will be ignored and treated as blank.
1-5569401
2004
Elements - CWELD - Wrong Answers
Incorrect CWELD element forces are output if any of the attached grids (the
CWELD grids or the connecting shell grids) are in a global coordinate system.
1-5580011
70.7.2
Frequency Response - PBUSHT, GE, HP- NaN
On the HP machine, if a frequency-dependent GE value is used in version 70.7.0,

then the output may contain erroneous "NaN."
Avoidance: This problem has been fixed in Version 70.7.2
1-5623817
2004
Miscellaneous - Continuation Entries
The continuation fields are supposed to support a base of 36 (0-9, A-Z), which
allows a maximum of 36**7 continuation entries. However, when the continuation
fields are left blank, MSC.Nastran only generates the continuation field using
the numbers 0-9 and it starts with 1 and goes to +9999999 and then it starts
repeating. This will cause a fatal error if there are more than 9999999
continuation entries.
1. Set system cell 357 to 1. This is the recommended method.
2. Specify the continuation fields explicitly, then you can use all 36
numbers/characters. Start field 10 of the parent entry with +0000000 and
increment the right-most column first (starting from 0,1,2,...9,A,B,...Z).
Next increment the 2nd right-most column by 1 and repeat the same thing for
column 1. Repeat the same process until this is done for all 7 columns.
1-5643535
Eigenvalue Analysis - EIGRL - Missing Eigenvalues
If both F1 and ND are specified on an EIGRL entry, it is possible that the

number of eigenvalues in the output will be fewer than ND.
Avoidance: This has only been observed in one model and removing F1 from the
entry resulted in the correct number of roots being found.
1-5668101
2004
Aeroelastic Optimization - Multiple Bound
ary Conditions lead to GREAD Error in DSAL
Aeroelastic optimization with multiple boundary conditions may lead to a GREAD
error in the DSAL module.
compile respsen list
alter 'aug1x'
delta=true $
compile pslgdv
alter 'caseaa'(2),'caseaa'(2)
SSG1
SLT,BGPDVP,CSTMS,medge,ESTDV2F,MPTX,ETTDV,EDT,,
caseau,DIT,,,,gpsnts,cstm0,,/
aAG ,PTELMa,/
LUSETS/0/1/'ALL'/altshape $
alter 'caseaa'(3),'caseaa'(3)
SSG1
SLT,BGPDVb,CSTMS,,ESTDV2B,MPTXB,ETTDV,EDT,,
CASeau,DIT,,,,gpsnts,cstm0,,/
aAGB ,PTELMAB,/LUSETS/0/1/'ALL' $
alter 'pmg'(4),'pmg'(5)
dbstatus pma//s,n,nopma$
IF ( nopma<0 ) then $
compile fea
alter 'fluidse0'(2)
type parm,,i,n,
nsolga = 0
alter 'saersens'(,-1)
nsolga = nsolga + nsol $
alter 'psload'(6),'psload'(6)
IF ( FEAOPT='SENSITIVITY' AND
NOT ITOL( NOSEDV )
AND ( ITOL(-SAERODSA) OR ITOL(-STATDSA) )
AND PSLOAD
AND ( SAERCC AND NSOLGA>0 ) ) THEN $
1-5676909
UFM 7522
2004
Loads - TEMPD - Duplicate TEMPD ID causes
If an input file has multiple TEMPD entries with the same id, the program will
issue UFM 7522, incorrectly indicating that there are conflicts with DEFORM
entries.
Avoidance: If you get this error message, check all TEMPi, DEFORM, and TEMPD
entries for unique ids.
1-5684501
2004
ATTB - UFM 5628 (DSAD)
If a DRESP1 entry is defined with a function name in the ATTB field it is

considered as an implied DRESP2. If an implied DRESP2 selects an element
related response such as frstre or frforc, then the job will failed in the
DSAD module with UFM 5628.
1-5687106
2004
us Versions not Upward Compatible
External Superelements - DMIGOP2 - Previo
If an external superelement created using DMIGOP2 in a previous version is used

in V2001, the run will fail in various ways.
Avoidance: If possible, re-create the external superelement using V2001. If
not, contact MSC with this error number and request the DMAP avoidance.
1-5688001
Dynamics - enforced motion, restart - UFM 3046
When performing restarts in a dynamic response analysis with load changes using
the direct enforced motion (spcd option), the job will fail with the following
error messages:
*** USER FATAL MESSAGE 3046 (TRD1)

THIS TRANSIENT RESPONSE ANALYSIS HAS NO EXCITATION SPECIFIED FOR IT.
APPLIED LOADS, ENFORCED MOTION, INITIAL CONDITION AND NON-LINEAR FORCES
ARE ALL NULL.
THE RESULT WILL THEREFORE BE A ZERO SOLUTION.
0FATAL ERROR
Avoidance: Run the job as a cold start.
1-5704209
2004
Complex Lanczos
Complex Eigenvalues - EIGC - SFM 3002 in
If complex lanczos method is used and the EIGC entry does not have ND0
specified and has no continuation lines, the program will fail in the CEAD
module with:
BIOMSG: ERROR
Avoidance: Provide ND0 and/or continuation lines.

1-5735301
Nonlinear Analysis - TABPRT - Table ESTNC can not be printed
correctly with TABPRT
The ESTNC table can not be printed correctly with tabprt. could not be
processed properly with tabprt.
1-5735601
2001.0.7
Optimization/Design Sensitivity - PCOMP Insufficient memory in routine dsab1q
When an optimization task designs the property (thickness or ply angle) of a
PCOMP entry or the material properties (E, Rho) referenced by the PCOMP entry,
then the job may fail with insufficient memory in routine dsab1q. However, the
real problem is caused by an incorrect calculation of the memory requirement.
Avoidance: Specify as large an amount of memory as possible for the job using
the keyword MEM=aaa on the nastran command line. This may not work if the
number of designed PCOMP properties is very large.
MODULE = DSABO
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE DSAB1Q
18494 WORDS
PROGRAMMER INFORMATION: LOCATION KEY = move PCMP
1-5742601
2005.5
Documentation/QRG - Aeroelastic Analysis
- MONPNT1 - UFM 315 (IFPDRV) XYZ default not supported
The Quick Reference Guide indicates that there is a default value of 0.0 for X,
Y, and Z on the MONPNT1 entry but leaving any of these fields blank results in
the following fatal message
FORMAT ERROR ON BULK DATA ENTRY MONPNT1
1-5782201
2005
Documentation/QRG - MFLUID
The following remarks should be added to the description of the MFLUID entry in
the QRG.
10. A tolerance is computed for each wetted element, with the value of
0.01*sqrt(2.*A), where A is the area of the element. If any grid point
connected to the element lies within TOL below the free surface it is moved to
the free surface.
11. Any element that has all grids on or above the free surface, after the grid
points are moved by the procedure given in Remark 10, is removed from the
ELIST. It is not included in the VM effects, and will produce no pressure
output.
1-5784601
2004
Random Analysis - RANDPS with Cross Spect
rum - Possible Wrong Answers, SWM 3002 (RANDOM)
If a random analysis with a cross spectrum, requests random output for a
non-existing grid point, then the answers may be incorrect. The following
warning messages are issued:
EOF ENCOUNTERED WHILE READING DATA BLOCK OUGV2
SUBROUTINE RAND2
(FILE 104) IN
xxxx
Avoidance: Remove the output request for the non-existing grid point
1-5784622
SFM 3003
2004
Nonlinear Analysis - CRAC3D, TEMP(LOAD) -
In a nonlinear analysis is running on an NT and the model contains CRAC3D

elements and temperature loads, then the job may fail with the following
messages.
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK EST
(FILE 201) IN SUBROUTINE TA1NLE
0FATAL ERROR
1-5785604
2008.0.0 (MD R3)
HAS OCCURRED IN ROUTINE GXWRIT
Database - DBLOAD - BIOMSG: ERROR
3010
Attempting to DBLOAD a large database in neutral format may fail with errors
similar to the following:
BIOMSG: ERROR 3010 HAS OCCURRED IN ROUTINE GXWRIT
or
In V2005+ the error is given as follows:
*** USER FATAL MESSAGE 1129 (GNLOC)
THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR LOCATION
PARAMETER ADBX
= ADB
USER INFORMATION:
1. GNLOC PERFORMS MODULE FILE ALLOCATIONS
2. THE DBSET ADB

WAS NOT ALLOCATED FOR THIS RUN
THE FULL DBDIR RECORD CONTAINING THIS LOCATION PARAMETER IS:
67108
67140
71400ADBX
3
2ADB
0FATAL ERROR
1-5809604
g answers
2004
Elements - CWELD and PARAM,POST,-2 - Wron
If a CWELD element generates GRID points for the connection, the locations of
these new GRID points will be written into the OUTPUT2 file incorrectly if
PARAM,POST,-2 is used.
compile phase0
alter 'geom1qx'
call dbstore geom1qx,,,,//0/0/'
'/0 $
compile super3
alter 'gp1',''
call dbfetch /geom1qx,,,,/0/0/0/0/0 $
GP1
GEOM1qx,GEOM2,,,,,/
GPL,EQEXIN,GPDT,CSTM,BGPDT,SIL,,,/0/0/0 $
alter 'call.*out2g.*geom2'(2,),''
CALL OUT2GEOM,
CSTMs,GPL,GPDT,EPT,MPT,GEOM2s,GEOM3s,GEOM4s,
GEOM1s,DIT,DYNAMICS,BGPDTs,CASECC,MATPOOL,
AXIC//OUNIT1X/S,NP $ $
endalter
1-5818132
Model Checkout - UFM 9050
The error message

USER FATAL MESSAGE 9050 (SEKRRS)
RUN TERMINATED DUE TO EXCESSIVE PIVOT ....
should be accompanied by probable causes and guidance such as:
RUN TERMINATED DUE TO POSSIBLE INSTABILITIES OR MECHANISMS IN YOUR MODEL
LIST OF SOME POSSIBLE CAUSES AND RECOMMENDED ACTIONS:
(1)
LARGE LOCALISED ELEMENT STIFFNESSES CAUSING HIGH STIFFNESS RATIOS
ACTIONS:
CHECK MATERIAL AND PHYSICAL PROPERTY ENTRIES FOR EXCESSIVELY LARGE OR SMALL
PROPERTY SPECIFICATIONS OR INCOMPATIBLE UNITS.
CHECK FOR BAR/BEAM TO SHELL NORMAL CONNECTIONS IF PARAM,K6ROT IS NOT 0.0
CHECK FOR SEVERELY DISTORTED ELEMENTS
(2) MECHANISMS CAUSED BY ELEMENTS CONNECTED TO DOFS WITH LITTLE OR NO
STIFFNESS
ACTIONS:
CHECK FOR SECTIONS OF THE MODEL UNCONNECTED DUE TO ERRORS IN MODEL BUILDING
SUCH AS FAILURE TO EQUIVALENCE GRIDS IN PATRAN
CHECK CONNECTIONS OF ELEMENTS WITH DIFFERENT TYPES SUCH AS:
SHELL TO SOLID (SOLID ELEMENTS ROTATIONAL DOFS ARE NULL)
BAR/BEAM TO SHELL (SHELL ELEMENT DRILLING FREEDOMS ARE NULL)
CHECK PSHELL PROPERTY IS NOT MEMBRANE ONLY (IS THE MID2 (BENDING)
FIELD SPECIFIED?)
CHECK PIN FLAGS FOR BAR/BEAM ELEMENTS
(3)
MISSING SINGLE POINT CONSTRAINT (SPC) DEFINITION
ACTIONS:
CHECK SPC ENTRIES IN THE BULK DATA ARE PRESENT WITH CORRECT SET ID
CHECK CASE CONTROL SPC ENTRIES FOR ALL SUBCASES ARE PRESENT AND HAVE
CORRECT SET ID
(4)
NEGATIVE STIFFNESS SPECIFIED ON SCALAR ELEMENTS (CELAS, CBUSH...)
ACTIONS:
ENSURE ALL SCALAR ELEMENT STIFFNESSES ARE POSITIVE
(5)
MECHANISMS OR INSTABILITIES ARE VALID IN THE IDEALISATION
ACTIONS:
EITHER USE INERTIA RELIEF (TO PERFORM A STATIC SOLUTION) OR USE A DYNAMIC
SOLUTION SEQUENCE
TO OBTAIN A SOLUTION UNDER LOAD FOR AN UNSTABLE STRUCTURE.
GENERAL DIAGNOSTIC ADVICE
IF THERE IS A TABLE OF DOF FOLLOWING THIS MESSAGE THEN THIS REPRESENTS THE LAST
SET OF DOF
IN YOUR MODEL WHICH (IF CONSTRAINED) COULD HAVE PREVENTED THE INSTABILITIES.
IT IS NOT RECOMMENDED TO CONSTRAIN THESE DOF AND RUN AS THIS IS PROBABLY NOT
PHYSICALLY
MEANINGFUL. THE DOF SHOULD BE USED TO TRY TO DETERMINE WHAT THE MECHANISMS
(OR INSTABILITIES) ARE AND PREVENT THEM.
PAY ATTENTION TO ANY SPC'S, SCALAR ELEMENTS, RIGID ELEMENTS OR LOCAL ANALYSIS
COORDINATE
SYSTEMS USING THESE DOF.
INSPECT THE ELEMENTS CONNECTED TO THE DOFS FOR ERRORS AS DESCRIBED IN THE
POSSIBLE CAUSES
SECTION OF THIS MESSAGE. IF NO ERRORS ARE FOUND, CONSIDER REMODELLING THE
CONNECTION OF
THE ELEMENTS TO THESE DOFS, OR TRY THE METHODS BELOW.
DIAGNOSTIC ANALYSIS METHODS
RUN A SEPARATE SOL 101 RUN WITH A SUBCASE FOR EACH DOF LISTED. THEN IN EACH
SUBCASE, MOVE
ONE OF THE LISTED DOF 1.0 UNITS WHILE THE OTHERS ARE CONSTRAINED. THE RESULTING
DEFORMED SHAPES REPRESENT THE MECHANISMS (INSTABILITIES) WHICH ARE IN YOUR
MODEL
RUN THE MODEL IN SOL 103 AND ANY 0.0 HZ MODES FOUND REPRESENT THE
MECHANISMS/INSTABILITIES.
RUN A DIAGNOSTIC ANALYSIS TO ASSIST IN VISUALIZING MECHANISMS OR LARGE
LOCALISED
DISPLACEMENTS. DO THIS BY FORCING THE RUN TO CONTINUE PAST THE FATAL ERROR
POINT BY
SETTING PARAM,BAILOUT,-1 IN THE BULKDATA OR SETTING PARAM,MAXRATIO TO
A VALUE HIGHER THAN THE LARGEST MAXRATIO INDICATED ABOVE. BE AWARE THAT THE
RESULTS
OBTAINED USING EITHER OF THESE METHODS WILL ALMOST CERTAINLY BE IN ERROR AND
ARE FOR
DIAGNOSTICS ONLY- YOU HAVE BEEN WARNED
1-5821306
962
Heat Transfer - APP,HEAT - param,extout,dmigpch lead to UFM 6
Use of PARAM,EXTSEOUT,DMIGPCH in SOL 101 with APP HEAT leads to

*** UFM 6962 (MATGEN)
ILLEGAL VALUE FOR PARAMETER 3 = 33
*** SIM 1156 (XCLUNP)
GINO FILE 201 WAS LEFT OPEN AT PROGRAM TERMINATIONsee SR 157057011:
SOL 101
APP HEAT
diag 8,15
compile semg list noref
alter 'IF ( NOMGG>=0 ) THEN' (1,-1)
matpch kjjz$
$ Direct Text Input for Executive Control
CEND
1-5821710
2001.0.9
Fault in Lanczos
Eigenvalue Analsyis - READ - Segmentation
On the SGI, for a large problem, it has been observed that the job may
occasionally terminate in the READ module without any additional messages. The
following message may appear in the log file
Note that this is an intermittent problem and may or may not be repeatable.
The problem may go away by varying buffsize, memory, or even having different
loads on the machine.
Avoidance; Change BUFFSIZE or Memory.
This error can only be corrected by
changing to f90 compilers. A 2001.0.9 system built with f90 compilers has
been released to correct this problem. This system with a build date of
February 11, 2003 has been put out on the external MSC web site. Go to
www.mscsoftware.com, pick support, pick product Nastran, pick software updates.
Replace the analysis executables in the irix64 directory and place the
nast2001.lcl file in the bin directory. This latter file sets:
setenv FORMAT_TYPE_CHECKING RELAXED
which is required for this executable.
1-5824401
2001.0.7
Aeroelastic Analysis - TRIM - Nonlinear C
ontroller with Redundant Control may lead to SFM 3007 (ASG)
If a nonlinear controller exists that is not labeled as one of the standard
rigid body controllers, and the users attempts to trim with redundant controls,
then the following error message may appear:
*** SYSTEM FATAL MESSAGE 3007 (ASG)
ILLEGAL INPUT TO SUBROUTINE ASGNMD
0FATAL ERROR
1-5828001
2001.0.6
DBC - UFM 1250 issued in DBC module
Large nonlinear jobs may fail in MSC.Nastran 2001.0.4 in the DBC module with
the message:
*** USER FATAL MESSAGE 1250 (BLKRD)
STATUS =
6007, FILX = 40, LOGNAME = DBC
FILE = ./bi-metallic-plate.xdb
BLKNBR =
78533
ERROR MESSAGE IS -Read block number beyond End-of-file.
0FATAL ERROR
at SEDRCVR 596
DBC
, NSBUF3 =
1024
BEGN
Avoidance: Reducing the amount of data recovery or increasing the memory may
avoid the error.
1-5843101
9 (DOM9D)
2004
When an optimization task has more active and violated constraints than the
number of design variables, the optimization module may produce the error
message:
USER FATAL MESSAGE 6499 (DOM9D)
or may have difficulty converging.
Avoidance: Set METHOD to 3 (SQP) or 2 (SLP) on the DOPTPRM entry.
THE DOT OPTIMIZATION ALGORITHM HAS ENCOUNTERED AN ERROR THAT MAKES FURTHER
PROGRESS IMPOSSIBLE. SEE MESSAGES ABOVE.
1-5862001
Wrong Answers
2004
Nonlinear Transient Analysis - PLOADX1 -
Nonlinear transient analyis should treat the PLOADX1 as a follower force but
does not. This may lead to wrong answers.
1-5872004
2004
Nonlinear Analysis - PARAM,LGDISP - CBEAM
with Offsets may not produce UFM 6174.
A nonlinear analysis with BEAM elements with offsets should produce the
*** USER FATAL MESSAGE 6174 (TA1NLE)

BEAM ELEMENTS WITH OFFSETS ARE NOT SUPPORTED IN DIFFERENTIAL STIFFNESS
OR NONLINEAR ANALYSIS. REMODEL WITHOUT USING BEAMS WITH OFFSET.
However, if only some of the BEAMS in the model have offsets the message may
not be issued and poor answers may be produced.
1-5872801
2004
- UFM 6468 (GETCOL)
Optimization/Design Sensitivity - STATSUB
USER FATAL MESSAGE 6468 may occur in an optimization analysis when multiple
buckling subcases with separate STASUB requests are employed.
Avoidance: The following 2001 DMAP should avoid the problem:
compile respsen
alter 'casebuck','dsnokd'(3)
DSVG1
KDICTDSF,KELMDSF,BGPDTS,SILS,CSTMS,KDICT,
KELM,BUDG,,LBTAB,DSPT1/
EGKBK///2/0 $
IF ( cdifx='yes' ) THEN $
DSVG1
KDICTDSB,KELMDSB,bgpdts,sils,cstms,kdict,
kelm,budg,,lbtab,dspt1/
EGKBKB///2/0 $
ADD5
egkbk,EGKBKB,,,/EGKBKC/.5/-.5 $
EQUIVX EGKBKC/EGKBK/-1 $
ENDIF $ cdifx='yes'
if ( dsnokd<>0.0 ) then $
dbview casebuck=casers (where isolapp=2) $
IF ( SEID=0 ) THEN $
PARAML CASEBUCK//'DTI'/1/3 //S,N,SPC $
PARAML CASEBUCK//'DTI'/1/2 //S,N,MPC $
PARAML CASEBUCK//'DTI'/1/255//S,N,SUPORT $
PARAML CASEBUCK//'DTI'/1/5 //S,N,BMETH $
PARAML CASEbuck//'DTI'/1/256//S,N,STATSUB $
ENDIF $ SEID=0
GETCOL CASEbuck,CASE0//1/S,N,COLNO $
PARAML CASESX//'DTI'/1/7//S,N,TSET $
EMG
EST,CSTMS,MPTS,DIT,,UG,ETT,EDT,,,BGPDTS,
GPSNTS,,,,/KDELM,KDDICT,,,,/
1/0/0//1//Tset/-1//////COLNO $
1-5883813
Superelements - OLOAD, EPOINTS - Wrong Answers
If EPOINTs are used in a model with superelments, the applied load output may
be incorrect. This has been encountered when the EPOINT ids are less than the
highest GRID id and the number of EPOINTs is not a multiple of 6.
Avoidance: Always use id numbers for EPOINTs which are greater than the highest
GRID id.
1-5884008
nvergence
2004
Optimization/Design Sensitivity - Poor Co
An optimization job using the modified feasible method may encounter divergent
behavior when it starts with a feasible design and degrades to an infeasible
design.
Avoidance: It may help to scale the objective to unit.
1-5884017
2004
FM 4276 (NLTRD2)
Nonlinear Transiet Analysis - TSTEPNL - S
Nonlinear transient analysis may fail in the NLTRD2 module with SYSTEM FATAL
MESSAGE 4276 (as shown below) if multiple load cases exist and NO (the time
step interval for output) is set greater than 1 on the TSTEPNL entry.
FATAL 4276 ERROR CODE 1044 (BIOMSG: .....
1-5884049
2004.0.6
ECKOUT - SIM 6296 (EMGPOM)
Heat Transfer Analysis - CHBDYG, PARAM,CH
Heat transfer analysis, SOL 153, with CHBDYG elements and PARAM,CHECKOUT,YES
results in SYSTEM INFORMATION MESSAGE 6929(EMGPOM) for every CHBDYG element.
This message is misleading and does not indicate any problems with the model.
1-5884081
EC 1044
2004
Nonlinear Transient Analysis - SFM 4276
If output is not requested for all time steps in a nonlinear transient analysis
the job may fail with:
SYSTEM FATAL MESSAGE 4276 ERROR CODE 1044
Avoidance: Request output for all time steps.
1-5884092
Heat Transfer Analysis - SFM 3001 (RMG2)
If in radiation heat transfer analysis a TEMP(INIT) Case Control entry and TEMP
or TEMPD Bulk Data entries are not specified to define the initial temperature
vector the following fatal message will be issued:
SYSTEM FATAL MESSAGE 3001 (RMG2)
THE INPUT DATA BLOCK NAMED MUGNI
AT POSITION
3 DOES NOT EXIST.
1. THE DATA BLOCK WAS NEVER CREATED.
2. THE DATA BLOCK WAS DELETED.
3. THE DATA BLOCK IS SPECIFIED ON A TYPE STATEMENT IN THE CURRENT
SUBDMAP OR A HIGHER SUBDMAP BUT THE CURRENT QUALIFIER VALUES DO NOT MATCH THE
QUALIFIER VALUES OF THE DATA BLOCK(S) ON THE DATABASE.
USER ACTION: 1. IF YOU ARE EXECUTING AN MSC.SOFTWARE SUPPLIED SOLUTION
SEQUENCE AND NOT USING THE ALTER EXECUTIVE CONTROL STATEMENT, THEN CHECK FOR
BULK DATA AND/OR CASE CONTROL INPUT ERRORS.
1-5896512
2004
a Line added to puch output
Element Strain Energy - ESE(PUNCH) - Extr
In Version 2001, if ESE(PUNCH) is requested, an additional line has been added

to the output. This line identifies the mode number and eigenvalue for the
subsequent output. There are two known problems with this additional line:
1) This additional line might cause some post-processors to fail to read the
punch file.
2) It is possible that the printed eigenvalue may be incorrect
Avoidance:
1) Currently there is no way to obtain the old format, so the avoidance is to
edit the file or write a program to strip out the additional lines.
2) Verify the eigenvalues from the .f06 file

1-5905907
utput
2004
Superelements - EXTSEOUT(OTM) - Missing O
A SOL 111 external superelement creation run using the EXTSEOUT(OTM)

feature followed by a SOL 111 assembly run with six dynamic load cases gives
results for only the first five subcases for the external superelements in the
assembly run. The error only occurs when there is only one forcing frequency.
Avoidance: Specify more than one forcing frequency.
1-5905910
2004
Superelements - EXTSEOUT - Missing Output
A SOL 111 external superelement creation run using the EXTSEOUT feature
followed by a SOL 111 assembly run with two FREQ requests in the Case Control
does not produce any output for the external superelements in the assembly run.
compile super3
alter 'norec',''
paraml casers//'trai'/1/s,n,norec//s,n,nocasers $
if ( nocasers<0 ) paraml casers1//'trai'/1/s,n,norec $
compile semfreq
alter 'dloop=dloop',''
paraml casef//'trai'/1/s,n,norec $
dloop=dloop+norec $
endalter
1-5916231
2004
Postprocessing - CWELD - GPDT Table conta
ins incorrect locations for CWELD GRIDS
The table GPDT does not contain the correct locations for GRID points generated
by CWELD elements. This has no impact on MSC.Nastran, but if you have a program
which reads this table, it will get incorrect locations.
Avoidance: Use GEOM1S, which contains the correct locations.
1-5927813
16
2004
Miscellaneous - Large Element IDs - UFM 3
In MSC.Nastran 2001, if an element ID is equal to or greater than 100001001,

then the following fatal message will be issued
ILLEGAL DATA ON BULK DATA ENTRY CBAR ON SORTED ENTRY COUNT
USER INFORMATION:
ELEMENT ID xxxxxxxxx EXCEEDS MAXIMUM VALUE ALLOWED 100001001.
The error is that the avoidance is not given in the message.

Avoidance: If such a large value must be uses, then insert the following
NASTRAN statement at the top of the input file
NASTRAN SYSTEM(182)=nnn
where nnn is a number larger than the largest element id needed. See quality
5447 for related limits.
1-5930003
2001.0.7
Miscellaneous - ISHELL - Very large timeo
ut value for ISHELL causes error on Solaris
If a user specifies a very large timeout value for ISHELL (greater than
100,000,000) using system cell 275, the ISHELL run fails on Solaris with an
"Invalid Argument" system error code. Solaris allows a maximum timeout value
of 100,000,000 seconds (about 3.1 years) and fails the request if this value is
exceeded. Other UNIX systems quietly reset the timeout to the maximum
supported and continue.
The X-Open specified max is 31 days. ISHELL will be modified to quietly reset
user-specified timeout values to 31 days. If this is not long enough, the
"infinite" option can be used.
1-5931701
4551 (NCONVG)
2001.0.9
Nonlinear Analysis - TET10, PLASTIC - UFM
The TET10 element has problems converging in nonlinear analysis in the plastic
range. This problem may lead to the following fatal message:
*** USER FATAL MESSAGE 4551 (NCONVG)
Avoidance: The problems has been corrected in Version 2001.0.9 available on
the Nastran 2001 R4 CD.
1-5953201
2004
DMAP - Matrix density output from PARAML
If the PARAML module TRAILER option is used to output the density of a matrix
from trailer word 6 into the 3rd parameter position of PARAML and the density
is greater than 99.999%, but not full, then the value returned to the PARAMLs
3rd parameter will be 10000 which incorrectly indicates a full matrix.
Avoidance: Use PARAML's 4th parameter output which will give the density as a
real value with 1.0E0 indicating a full matrix.
1-5963032
2004
Documentation/QRG - ACCELERATION - Output
is available for SOL 103 for Response Spectrum Analysis
In the MSC.Nastran Quick Reference Guide, Remark 2 on the ACCELERATION case
control command incorrectly states that ACCELERATION output is only available
in Frequency response and Transient response. Table 4-5 in the QRG correctly
indicates that acceleration output is available in SOL 103. However,
acceleration output is only available when the response spectrum method is used.
1-5963501
(TPSPLD)
2001.0.7
Aeroelastic Analysis - SPLINEi - UFM 2260
The thin plate spline will fail due to a singular matrix for small models.
The message encountered is:
USER FATAL MESSAGE 2260 (TPSPLD)
SINGULAR MATRIX DEVELOPED WHILE PROCESSING SPLINE
0FATAL ERROR
1-5987106
2005
iles are Incompatible
100001
Postprocessing - ESE, GPFORCE - Output2 F
This report is written to document op2 format changes for clients and developer
of other post processors.

The following defines the changes to the ESE/GPFO and new EKE,EDE headers
between pre and post MSC.Nastran 2001 systems. The ESE type headers now
conform more closely to SDR2 headers, except for the eigenvalue locations.
Word Old Header New Header
1 1*10+Device (Approach Code)*10 + Device Code
2 MSC.Nastran OFP code ESE(18) EKE(36) EDE(37) GPFO(19)
3 Total Energy of all elements / Null for GPFO
4 "Pseudo Subcase" Subcase Number
5 Load Set Id /Mode/Time/Frequency/Load Factor/
6 Element Name (1) / 0 for GPFO
7 Element Name (2) / 0 for GPFO
8 0 Load Set ID
9 Approach Format Code (R=1/RI=2/MP=3)
10 Number of words per OFP data entry directly following header
11 Flags 0->Not Complex 1->Average 2->Amplitude 3->Peak
12 Element Energy Sub-Total
13 Element output Set Identification
14 Null Eigenvalue Real Part
15 Null Eigenvalue Imaginary Part
16 Null Natural Frequency
Supported Approach Codes for V2001
/1-STATICS/2-MODES/5-FREQUENCY/6-TRANSIENT/8-BLK1/9-CEIGEN/10-NON LINEAR/
Discussion:
The old word one always indicated STATICS and the real Approach was placed in
word nine. Since GPFO will eventually allow for Complex Grid Point Forces, the
Format Code will be needed. Therefore, like SDR2 headers, the true format will
be built into the approach area of word one. Therefore, when processing old
tables like ESE(18) and GPFO(19), an approach value not equal to "1" implies
that you are processing the V2001 and later header/table conventions. Since
STATICS(1) always has a "REAL" data format, the value in word nine is
consistent between releases, and nothing has to be considered unless the Load
Set Id information was important. The "Pseudo Subcase" number concept has been
replaced, where the first mode was the base Subcase Identification and the
Subcase was then incremented to delineate the next mode. In V2001, the Subcase
Number is not incremented.
1-6030001
2004
Nonlinear Analsyis - Incorrect Intermedia
te Composite Ply Stresses for Thermal Loads
When composite ply stresses are requested for SOL 106,
the contribution for the thermal strain may be calculated
incorrectly for intermediate load steps. It is correct for the
final load step.
1-6047016
2004
Documentation/QRG - GPFORCE
\The following line should be added to the end of Remarks 2 and 3 of the
MSC.Nastran Quick Reference Guide description of the GPFORCE entry.
See remark 4 for further details.
Furthermore, CQUAD4 should be added to the list of elements supported for the
output of grid point forces aligned with the edge of the element.
1-6047029
2004
s Direction Code not Documented
Documentation/QRG - Strain Failure Indice
When using the strain failure criteria for composite elements, the -1, -2, or
-12 output follows the failure indices printout. The intepretations of these
values are not documented anywhere. They can be intepreted as follows:
-1 - failure in the fiber direction
-2 - failure in the matrix direction
-12 - failure in the inplane shear.
1-6051920
SSSALTER - nlgyroa.vxx - UFM 5423
If the nlgyroa.vxx is used and m-set exists in the model (e.g., RBAR, RBE2,
etc.), then the job will fail with the following message:
USER FATAL MESSAGE 5423 (SADD5)
Avoidance: Replace the MPCs with a stiff BAR.
1-6054801
2005
or points, restart - SFM 3001
Optimization/Aeroelastic Analysis - monit
A restart run in SOL 200 can fail due to a missing MPSRV datablock when
attempting a static aeroelastic trim analysis. It appears that the failure
only occurs when the design variables change the analysis model from the cold
start to the restart.
Avoidance: The following dmap alter can be used in the restart run to avoid the
missing datablock:
compile phase0
alter 'if ( aero )','nlheat'(3,-1)
alter 'not(exter or image'(1,-1)
if ( aero ) then $
$
$ Create the aerodynamic model geometry and other data dependent
$ only on the model
$
GP1
GEOM1,GEOM2,,GDNTAB,MEDGE,,dynamics/
xGPL,EQEXIN,xGPDT,xCSTM,xBGPDT,xSIL,,,/
S,N,LUSET/0/s,n,nopoints $
$
if ( desopt0 ) then $
equivx casexxu/aecase/always $
else $
equivx casecc/aecase/always $
endif $
$
call aero0 aecase ,edt
,xcstm ,dmi
,dmindx ,
xbgpdt ,pcdb
,geom3 /
aebgpdts,aeusets ,aeboxs ,aecomp ,aero
,
acpt
,cstma ,trx
,control ,spline ,
mklist ,gpksk ,gdksk ,gpgk0 ,gdgk0 ,
mpjn2o ,mpjsfn2o,aempcomp,aemonpt ,saemprk ,
strucomp,monitor ,saerg0 ,aedbstdx,uxvst ,
pgvst0 /
false /aertyp /s,nk
/s,nj
/s,nx
/
s,bov
$
if ( ifpindx ) call xifpindx spline,,,,,,,,,//s,np $
endif $ aero
1-6077806
2004
Complex Eigenvalue Analysis - EIGC, NDJ -
Poor Message, BIOMSG Error 3002

As stated in the Quick Reference Guide, the NDJ field must not be left blank on
the EIGC entry when using the complex Lanczos method If the NDJ field is left
blank on the EIGC entry, then the job will fail with the following unclear
messages:
BIOMSG: ERROR
0.
STATUS =
, FILE INDEX =
Avoidance: Specify the appropriate NDJ field.

1-6077837
2004
n not supported
Documentation - WEIGHTCHECK - punch optio
The WEIGHTCHECK command does not support the punch option using the standard
case control
command
WEIGHTCHECK(punch...)=yes
as illustrated in the Quick Reference Guide.
Avoidance: If the WEIGHTCHECK output is desired to be send to the punch file,
request it in the print format and include the following alter.
$
compile semg1 $
alter 2 $
sys2=getsys(sys2,2) $
putsys(7,2) $
alter 'return'(,-1) $
putsys(sys2,2) $
$
compile semrm $
alter 'call.*semr2'(,-1) $
sys2=getsys(sys2,2) $
putsys(7,2) $
alter 'call.*semr2' $
putsys(sys2,2) $
$
1-6084723
2004.0.6
FM 4276, EC 3002
Aeroelastic Analysis - KE-Method, FA2 - S
A flutter analysis using the KE-method fails in the FA2 module with a FSM 4276,
EC 3002. The MKAERO1 contains 20 k values each separated by 0.05 in k for one
Mach number.
Avoidance: Modify the MKAERO1 entry to have fewer k values and a more commonly
used distribution.
1-6151702
2001.0.7
PBUSH1D - UFM 5074
A message similar to:
Optimization/Design Sensitivity - PWELD,
USER FATAL MESSAGE 5074 THE PROPERTY NAME PWELD

1 CAN NOT BE DESIGNED.(PBUSHID).
REFERENCED ON DVPREL1 ENTRY
will be produced when a PWELD or PBUSH1D is being designed and FID is used on
the fifth field of the DVPREL1 or DVPREL2 entry.
Avoidance: Input the PNAME in the fifth field. For example, for a PWELD
diameter, use D in the fifth field rather than 4.
1-6155301
2005
leration gives poor answers
Transient Analysis - TRLG - Enforced Acce
An enforced acceleration problem may exhibit strange behavior due to the mixed
precision computations in the TRLG module (specifically in the TRLGCD
subroutine).
1-6166948
2004
Kb field is wrong
Documentation/QRG - PGAP - Descripion of
The QRG description of the PGAP's Kb field should have the following default:
"Default = 10e-14*KA"
instead of:
"Default = MU1*KA"
1-6181949
2004
Nonlinear Analysis - PCOMP, Unsymmetric
Ply Thickness, Negative Factor Diagonal
QUAD4 elements using offsets fail to converge when using SOL4 for large
displacements.
The same model with QUAD4 elements runs correctly in SOL 106, also TRIA3
elements with offsets run correctly in SOL 4.
1-6197801
o add module.
DMAP - DECOMP, ADD - Address error for Cholesky factor sent t
The decomp module outputs a special form matrix when the active column cholesky
option is selected. Inputting this matrix to the ADD module will cause the job
to fail in various ways and a meaningful message is not output.
1-6229106
2004
Frequency Response/Random Analysis - STRA
IN(PSDF) - Wrong Answers for Strain PSDF.
When there are both XYPLOT requests for STRAIN PSDF and STRESS PSDF, the strain
results are incorrect and in fact are identical to the stress results.
Avoidance: Remove the XYPLOT commands for STRESS PSDF output.
1-6242809
2004
FORCE plot results with damping
Frequency Response - SPCD - Incorrect SPC
If modal damping is present in a modal frequency response analysis, then the

SPCFORCES generated by an XYPLOT request will be wrong unless there is a
corresponding SPCFORCE case control request.
See also quality 1-4672328.

1-6242834
2004
Dynamic Analysis - MPCFORCE, enforced mot
ion - Possible Incorrect mpcforce output
In a modal response analysis (SOLs 111, 112), if the new enforced motion method
(introduced in V2001) is used, then the MPCForce output at grid points which
are dependent upon the enforced motion dof will be incorrect.
Avoidance: Either use param,ddrmm,-1 (not recommended for performance
reasons), the direct solutions (SOLs 108,109), or apply the following alter
for V2001:
$v2001 avoidance for error 1-6242834
compile disprs
alter 'call cforce2 USET,rgm,Uhf1'
type db mmg,bmg,kmg $
if ( noypo>0 ) then $
call cforce2 USET,rgm,ygo,MMG,BMG,KMG,,fOL1,,,
vmpcg,/
Qmpfy/
APP/APP/'mpcforce'/true $
call xadd5 qmpfy,qmpf,,,/qmpfx/cu/cu/cz/cz/cz $
equivx qmpfx/qmpf/-1 $
endif $ noypo>0
endalter
keywords: spcd ddrmm mpcforce
1-6251701
2005
Licensing - FLEXlm - UFM 3060
MSC.Nastran cannot use the following valid license file:

SERVER server_host serverid 1700
USE_SERVER
If no line beginning with 'FEATURE' is found in the license file, Nastran
assumes SBCM nodelock licensing.
Avoidance:
line.
1-6273303
Add a line containing only the word 'FEATURE' AFTER the USE_SERVER
2004
Transient Analysis - TRD1 - Wrong Answers
Transient analysis SOL 109 may, in rare cases, produce wrong answers in
MSC.Nastran Versions 70.7 and 2001. This can only happen when the following
message appears: UIM 5222 (TRD1) COUPLED SOLUTION ALGORITHM USED. The model
that encountered this error had TF entries, which created a "BDD" matrix with
null columns.
Avoidance: If you suspect wrong answers you can apply the following dmap
avoidance or execute Version 70.5 to see if the answers change.
COMPILE SEDTRAN $ Avoid error in TRD1 coupled integration, v70.5 or v2001
ALTER 'TRD1 *CASET'(,-1) $
PARAML
BDD//'NULL'////S,N,NULLB $
IF
( NULLB > -1 ) THEN $
MATMOD BDD,,,,,/VBD,IBDD/12/S,N,NCOLB/1 $
IF
( NCOLB > 0 ) THEN $

MESSAGE //' NULL COLUMNS FOUND IN MATRIX BDD' $
ADD
BDD,IBDD/BIDD//(1.-30,0.) $
EQUIVX BIDD/BDD/ALWAYS $
ENDIF $
ENDIF $
1-6287901
2001.0.7
fails with memory error
Aeroelastic Analysis - Thin plate spline
The thin plate spline will fail if more that one spline is used because the
memory allocated to a previous spline is not freed.
1-6299601
2004
Documentation/QRG - CBUSH
The QRG does not list the tolerance for the minimum length requirement for a
BUSH element. The following remark be changed in the QRG.
6. If the distance between GA and GB is less than .0001, or if GB is blank,
then CID must be specified
1-6377201
Acoustic Analysis - Format error
Complex acoustic results incorrectly includes the phase results from the P
column under the P(RMS), DB, and DB(A) results. The phase should be blank.
1-6377906
2004
- Job with many dresp2 entries failed in xqaros or xqfnc7.
An optimization job may produce wrong sensitivity coefficients or fail in an
unexpected routine such as complaining that negative values are being used in a
SQRT function when the following conditions are met:
1) The job requests printing sensitivity coefficients and
2) A DRESP2 response is defined that also references to another DRESP2 3) or a
DRESP3 response is defined that also references to a DRESP2 response
4) and one design variable is referenced by more than one DVXREL1 entries,
Avoidance 1: Remove DSAPRT or OPTEXIT=+(-)4 request and replace it with
IPRINT = 7 on the DOPTPRM entry. The gradients printed from IPRINT=7 are for
constraints and have been scaled by the factor, SIGN(1/BOUND) where BOUND is
either the lower or upper bounds specified on a DCONSTR and SIGN is + for the
upper bound and SIGN is - for the lower bound.
Avoidance 2: Create dummy type 2 properties by referring to dummy design
variables whose lower and upper bounds are identical. The number of dummy type
2 properties plus number of independent design variables must be greater than
or equal to the number of type 1 properties in the task.
A SOL 200 job with dresp2 entries (around 540 entries) failed differently in
two machines:
On linux: it failed in xqfnc7 (dom6/dom61/dr2dx/xqaros) complaining that
negative values were being used in a sqrt function. On AIX, it failed in
xqaros indicating a floating point overflow.
/net/shere/shere/users/shz/csr/fd/icw1/test_01.dat (...)
1-6384209
incomplete
2004
Documentation/QRG - EIGR - Description is
The POINT option for the NORM field on the EIGR bulk data entry should include
the comment that it is not supported for METHOD=LAN

1-6410501
2004
Optimization/Design Sensitivities - DVGRI
D, DVSHAP, DVBSHAP, BNDGRID - Zero Sensitivies
When an optimization job meets the following conditions, the sensitivities with
respect to property variables may be zero:
1) the design model includes shape variables (dvgrid, dvshap, dvbshap or
bndgrid) and
2) the design model includes property variables (DViRELj) and
3) the analysis model includes rigid elements (R-type elements) and the grid
points associated with the r-ype elements are being designed by shape
variables,
The problem may be avoided with the following dmap alter:
Alter 1:
compile respsen
alter 'dum'(,1),'dum'(2)
type parm,,n,i,ndvs,ndvp
ndvs = 3
ndvp = ndvtot - ndvs
matgen ,/colpart/6/ndvtot/15/3 $
matprn colpart // $
partn
dum,colpart,/,,a12dum,/1 $
partn
umy,colpart,/a11umy,,,/1
merge
a11umy,,a12dum,,colpart,/mdum/1 $
delete /ugy,,,, $
umerge uset, uny, mdum / ugy / 'G'/ 'N'/ 'M' $
As long as the property variables proceed the shape variables, this will work
with any problem by adjusting ndvs, the number of shape variables in the
problem.
1-6419327
linux, 2001
2001.0.7
Restarts - large dball will not restart,
Restart jobs that attach a dball greater than 4GB will not restart on linux
systems. The .dball is shown as offline on the restart and the follow message
are encountered in the f06 and f04 respectively:
DMAP MODULE XSORT
IS ATTEMPTING TO ACCESS DATA BLOCK
BULK WHICH IS ON AN UNAVAILABLE DBSET
0FATAL ERROR
.f04 message
orb3.MASTER
OLD
32769
orb3.DBALL
OFF LINE
32769
1
1
MASTER
020307084253
DBALL
020307084254
102 NAME =
MASTER
DBALL
Avoidance: The problem is corrected with w/ Linux Kernel 2.4.6-1.msc GLIBC

2.2.3 in MSC.Nastran 2001.0.7 and RedHat with Kernel: 2.4.2-2smp glibc:
2.2.2.
1-6420213
2004
NREL,-2 - SFM 6424
In an optimization run, if the automatic inertia relief feature

(PARAM,INREL,-2) is used, then the job may fail with the following error
messages:
THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE INCOMPATIBLE
1. Use the manual inertia relief (param,inrel,-1)
or
2. Contact client support and obtain the alter ir200a.v2001 from the internal
SSSALTER web site.
1-6442501
2004
Heat Transfer Analysis - UFM 4016 (GETEMP
)
THERE ARE NO TEMPERATURES FOR RAD
Heat transfer analysis may fail with the following message:
THERE ARE NO TEMPERATURES FOR RADBC ELEMENT xx IN SET 1
0FATAL ERROR
Avoidance: Do not define radiation to space on the backside of the plate
elements. Go back in PATRAN and change the bottom to top. In the entries
below, the CHBDYG IDs should be positive instead of negative
$ Radiation Boundary Conditions of Load Set : core-rad-bottom
RADBC
1204
1.
0
-100109
RADBC
1204
1.
0
-100110
1-6467801
2004
ion - Wrong answers
Dynamics - Superelements and Enforced mot
When enforced motion is specified on an exterior point of a superelement then

wrong results are obtained in the superelement if the default DDRMM method of
dynamic data recovery is used.
Avoidance: Specify PARAM,DDRMM,-1.
1-6505241
rs
2004
Superelements - DMIG, INREL - Wrong Answe
If inertia relief analysis is requested for a superelement model and K2GG

and/or M2GG Case Control commands are requested for a given superelement then
the results for that superelement and all of its upstream superelements will be
incorrect.
compile sedisp
alter 'dbview crj0',''
dbview crj0=crj where (seid=0 and peid=0 and wildcard) $
endalter
1-6510414
2004
sults at Low Frequencies
Modal Frequency Response - SPCD - Poor Re
If enforced motion is used in SOL 111, it is possible that the SPCFORCE output
might be incorrect at low frequencies.
Avoidance: Use SOL 108 instead.
1-6518631
2004
Elements - CHEXA, MATTi - Wrong Answers
The 8 node chexa element, modified in v70.7, incorrectly uses a MATTi for
temperature dependent material properties.
Avoidance;
1) use nastran system(309)=1
2) use 20 noded chexa
3) use 10 nodes ctetra
1-6519201
- UFM 9086
2005
Nonlinear Analysis - RESTART, TEMP(LOAD)
Nonlinear analysis restarts (SOL 106) that change the thermal loads may fail
with the following fatal message:
USER FATAL MESSAGE 9086 (GETLOOP)
PARAM, LOOPID,
1 DOES NOT CORRESPOND TO A VALID LOOP IDENTIFICATION
NUMBER.
Avoidance:
In the restart deck replace:
ASSIGN master='_____.MASTER'
RESTART,version=1,keep
with:
ASSIGN x='______.MASTER'
dblocate logi=x
and insert the DMAP alter:
compile nlstatic
alter 'rstrt=',''
rstrt=true $
endalter
1-6521809
swers
2004
Heat Transfer Analysis - MATT5 - Wrong An
Any heat transfer element that has temperature dependent conductivity should
be nonlinear. It appears that if MAT5 records are used, and only KYY is
temperature dependent, the element is treated as linear.
Avoidance: Replace MATT5 entries as follows:
MATT5
Add:
MATT5 4
TABLEM2 2
+T2
0.
1
+T2
1.
1000.
1.
ENDT
Checked in the fix of ta1nle in system on May 6.

1-6521817
2001.0.9
Heat Transfer - RMG2 - SFM 4276, Tracebac
k
Very large heat transfer jobs that calculate large view factors may fail with a
traceback in rmg2.
Avoidance: The failure occurs when the memory requirement is calculated and
overflows. There is no avoidance.
1-6561701
M 3002
2004
Eigenvalue - ND field on EIGRL entry - SF
If on the EIGRL Bulk Data entry, ND is greater than problem (matrix) size, then
the run may fail with SFM 3002 in the READ module (subroutine reigl3).
Avoidance: Set ND to less than or equal to the problem size.
1-6599317
2004
) - Wrong Answers
Documentation - MATHP, TREF and TEMP(LOAD
TEMP(MATE) is not supported for hyperelastic elements in SOL 101. If SOL 101
is used with hyperelatic element (PLSOLID and MATHP) and the fields for AV and
TREF are input on the MATHP entry and TEMP(BOTH) is requested in the case
control, the results will be zero.
If TEMP(BOTH) is changed to TEMP(LOAD)
then plausible wrong answers are obtained.
Avoidance: Place a TEMP(INIT) above the subcase level pointing to a TEMPD
bulkdata entry with the TREF value specified. Put TEMP(LOAD) within a subcase.
1-6609014
rong Answers
2004
Acoustic Analysis - PARAM, GFL ignored, W
In an uncoupled acoustic analysis, PARAM, GFL is ignored in SOL 108.

1-6614001
2004
Elements - CTRIA3, MAT2, MAT8 - UFM 9050
The CTRIA3 element with orthotropic or anisotropic materials and a material

coordinate system defined by the projection of a coordinate system will often
have an incorrect stiffness matrix depending on how far the material coordinate
system is rotated to the element coordinate system. This may lead to the
USER FATAL MESSAGE 9050 (SEKRRS)
RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX KLL.
1-6646806
2004
being ignored and not used
When a DRESP3 entry in a SOL 200 job references to a combination of DRESP2 and
any other arguments except DRESP1, the expected to be retained DRESP3 response
is missing from the sensitivity calculation or optimization.
Avoidance: In V2001 R2 (2001.0.4) or R3 (2001.0.7) add a dummy DRESP1 argument
to each DRESP3
1-6697301
2004
d enforced motion - Wrong answers
Eigenvalue Analysis - PARAM,RESVEC,YES an
A SOL 103 deck with PARAM,RESVEC,YES and employing enforced motion data via
RLOADi and SPCD Bulk Data entries does not generate any augmented modes due to
residual vectors.
COMPILE SEMODES
ALTER 'CALL SETQ','' $
CALL SETQ CASESX//SEID/PEID/S,MTEMP/S,K2GG/
S,M2GG/S,B2GG/S,MPC/S,SPC/S,LOAD/
S,DEFORM/S,TEMPLD/S,P2G/S,DYRD/
S,METH/S,MFLUID $
1-6711505
ional Answers
2001.0.9
Dynamic Response - MEFFMASS - Wrong Rotat
Modal Effective Mass gives wrong rotational numbers.

1) Incorrect rotational participations in fracsum, meffm, partfac.
2) Incorrect 3x3 Inertia submatrices in Effective & A-set mass matrices.
Numbers are only slightly off
observing that:
a) In a free-free model where
should be "consumed" in first
b) When compared to Effective
1-6725801
(1%) but obvious to experienced clients by

100% of participations, including rotations,
6 rigid body modes but are not.
Mass sssalter results.
Acoustic Analysis - PARAM,DDRMM,-1 - Wrong DB(A) answers
If PARAM,DDRMM,-1 is specified in an acoustic run then the DB(A) column in

the "COMPLEX ACOUSTIC RESULTS" output may be incorrectly non-zero even though
the P column is zero.
Avoidance: Run with PARAM,DDRMM,0 which is the default.
1-6733944
2004
Superelements - SEP1X - SFM 6802
If more than 50 grids are at the same location in the residual structure then
the message below is issued. If 50 or fewer grids occur at the same location
then the message is not issued.
*** SYSTEM FATAL MESSAGE 6802 (SEPSUP)
SUPERELEMENT
0 HAS FAILED TO AUTOMATICALLY DERIVE A SEARCH KEY.
USER ACTION: REVIEW MODEL FOR REASONABLE GEOMETRY AND SELECT SEARCH KEY
VIA OVER-RIDE PARAMETER AND/OR REVIEW
GRID POINT LOCATIONS FOR REASONABLE GEOMETRY
1-6875104
2004
UXP/M DMP executable
Installation - MSC.Nastran 2001R3 Fujitsu
The following steps must be followed to install the Fujitsu UXP/M DMP
executable from the MSC.Nastran 2001 R3 cd:
After the uxpv cd installation completes.
1. cd "MSC_BASE"
(The installation directory)
2. tar xvf "cdrom_mount_point"/msc2001/uxpv/dmp.tar
3. /cdrom/tools/uxpv/gunzip "MSC_BASE"/msc2001/uxpv/MPMD.gz
4. /cdrom/tools/uxpv/gunzip "MSC_BASE"/msc2001/uxpv.analysis.dmp.gz
Note: If the installation is being done from a platform other than uxpv then
replace
../cdrom/tools/uxpv with the appropriate architecture.
1-6875107
mples
2004
Documentation/IOG - Incorrect INCLUDE Exa
The INCLUDE example on page 105 of the MSC.Nastran IOG is incorrect. The
example
include '/proj'
'/dept123'
'/sect456'
'/joe/flange.bdf'
should be
include '/proj
/dept123
/sect456
/joe/flange.bdf'
1-6889219
2004
Superelements - DMIGOP2 type superelement
s no longer work in main bulk data, CSUPER
In V2001, if an external DMIGOP2 type superelement is included as a main bulk
data superelement, then the job aborts with SFM 4252 because the upstream XAAV
is missing.
See activity for why.
Avoidance: Insert the following DMAP alter or use part superelements or use a
different type of external superelement
ECHOOFF $
COMPILE EXTIN NOLIST $
ALTER 'DBSTATUS XSOP2DIR' $
IF (NOOP2DIR<=0 AND SEID>0 AND PEID=0) THEN $
INPUTT2 /XSOP2DIR,,,,/0/INUNIT $
DBSTATUS XSOP2DIR//S,N,NOOP2DIR $
ENDIF $
ENDALTER $
ECHOON $
1-6941201
Nonlinear Analysis - Temperature Dependent Coefficient of Exp
ansion - Incorrect Intermediate Results
If the coefficient of thermal expansion is temperature-dependent in a SOL 106
analysis for CQUAD4, CTRIA3, and/or CBEAM elements, the intermediate load steps
may be incorrect. The final load step will be correct.
Avoidance: Define separate subcases for each load step for which the results
are desired.
1-6948901
2004
Optimization/Design Sensitivity - RANDPS
- Autocorrelation function may not be used for RMS response
The 2001 release allows for the design of rms responses. There is an
undocumented limitation that only one RANDPS ID can be used per subcase.
Therefore, if there is a desire to study the response to two separate input
spectra, separate subcases will have to be submitted. Each RANDPS ID can refer
to multiple subcases so that auto and cross correlations can be input for a
given RANDPS ID.
1-6953959
2001.0.9
Loads - OLOAD and SPCFORCE Resultant Outp
ut - Wrong Answersuse param,resltopt,1 to get correct
The oload and spcforce resultants are incorrect in v2001.0.4 and later systems
if global coordinate systems are present and loads and/or spcs are applied to
grid points that reference an output coordinate system.
Avoidance: Use param,resltopt,1 to get correct results but in the old format
1-6970301
2004
Postprocessing - PARAM,POST,-2 - Incorrec
t Displacements for Modal Response (SOL 111, 112) Analysis
The eigenvectors rather than the response vectors are incorrectly output to the
op2 file if post=-2 in modal dynamic response analysis.
In Version 2004 and beyond this error only occurs with PARAM,SPARSEDR,NO.
Avoidance: Three avoidances exist:
1. Add Param,DDRMM,-1 (not recommended)
2. Add PARAM,OUGCORD,GLOBAL
3. Insert following DMAP alter (tested with V2001.0.7 of MSC.Nastran).
Note: ALTER ONLY WORKS for CASE of DISP=ALL
compile sedrcvr
alter 'sdr2.*bougv1','' $
delete /ugb,,,, $
drmh1 ougv1,,,/tougv1,mougv1,,,,,,/ $
IF ( NOCSTMS>0 ) THEN $
MPYAD
TRANSG,mougv1,/UGB $
ELSE $
EQUIVX
ENDIF $
SDR2
mougv1/UGB/-1 $
CASEDR,CSTMS,,,EQEXINS,,,OL1,BGPDTN,,,
UGB,,,OINT,PELSETS,VIEWTB,,,,,,/
,,BOUGV1,,,,/APP///////ACOUT/PREFDB/-1./-1./
ADPTINDX/ADPTEXIT/FALSE $
ENDALTER
1-6973701
P)
2001.0.9
Aeroelastic Analysis - SDP - SFM 3001 (SD
If there are multiple subcases and one subcase has a supported boundary
condition, followed by a subcase with a clamped boundary condition, then the
SDP module will fail with the following error:
*** SYSTEM FATAL MESSAGE 3001 (SDP)
THE INPUT DATA BLOCK NAMED MPAEUV
AT POSITION
11 DOES NOT EXIST.
Avoidance: The workaround is to put the subcases with clamped boundary

conditions before the subcases with supported boundary conditions.
NOTE: This workaround will not work for optimization.
1-6991176
2004
Aeroelastic Analysis - CAERO1, SPLINE1 FPS Spline may lead to SFM 4276, Floating Point Exception
If a SPLINE1 with the FPS option is used to connect a CAERO1 entry that only
has one spanwise box, then a floating point exception may occur in the GI
module. This error will also occur if the spline connects to a chordwise
strip of elements on a CAERO1 that is one spanwise box wide.
Avoidance: Split the CAERO1 entry so that it has two span wise boxes, or use
the IPS option on the SPLINE1.
1-6997601
2004
WELD and fluid elements are present
Elements - CWELD - UFM 2007 occurs when C
USER FATAL MESSAGE 2007 occurs in MODGM2 when CWELD elements and fluid elements
are present. The CWELD generates grids GA anf GB which are considered
undefined.
1-6998602
2004
L 103 - SFM 3001
Acoustic Analysis - PARAM, FLUIDSE and SO
If PARAM,FLUIDSE,>0 is specified in a SOL 103 run and differential stiffness or

residual vectors are requested, then the run will fail with:
*** SYSTEM FATAL MESSAGE 3001 (MTRXIN)
POSITION
3 DOES NOT EXIST.
THE INPUT DATA BLOCK IN

compile phase0
alter 'endif \$ not(sebulk)'
equivx eqexin/eqexinq/-1 $
call dbstore eqexinq,,,,//0/0/'
'/0 $
compile aspline
alter 'makvgac',''
call dbfetch /eqexinq,,,,/0/0/0/0/0 $
call makvgac eqexinq,eqexins,uset0,drg/
vgxac,vgac/
seid/nsenqset/luset $
endalter
1-7055609
2001.0.9
sorted for the PKNL method
Aeroelastic Analysis - Flutter roots not
The sorting of flutter roots that is used for the PK and PKNL is disabled when
the density used in the analysis changes. Since the PKNL method is likely to
change the density value for each analysis triplet, this effectively means that
the roots are not sorted.
Avoidance: Use the PK method or perform the sorting as a post-processing
operation.
1-7162927
ecomputed
Restarts/Aeroelastic Analysis - RESTART- AJJ unnecessarilty r
A SOL 145 or SOL 146 aeroelastic analysis RESTART where only changes are made
to the structural model will unnecessarily recalculate the AJJ matrix even
though the aeroelastic model is unchanged.
Avoidance: Resusing the aerodyanmics by DBLOCATING the ADB dbset works as an
alternative to the automatic restart.

1-7186605
2004
ements, DRESP2 - UFM 7139 (DOPR3N)
When an optimization job with superelements references a nested DRESP2 entry,

the job fails with the following message although the responses are defined
correctly:
*** USER FATAL MESSAGE 7139 (DOPR3N)
22, DRESP2 ID =
1-7187822
ation
2005.5
Documentation/QRG - RFORCE- Incorrect equ
To clarify the sign convention of the forces created with the RFORCE entry,
the following is to be added to remark 1 of the QRG RFORCE entry
------------------The forces that are created in msc.nastran with the RFORCE entry act on the
structure as follows:
The forces that are defined with the RFORCE entry for a constant angular
velocity (A) , act in the positive radial direction. These forces would
represent the inertia forces on the structure due to a constant angular
velocity.
The forces that are defined with the RFORCE entry for a constant angular
acceleration (RACC), act in the same direction as the angular acceleration.
These forces would be opposite to the inertia forces on the structure due to a
constant angular acceleration.
1-7241319
ing Message
2004
Optimization/Design Sensitivity - Mislead
When an optimisation analysis (sol 200) with analysis=mfreq stops with a hard
convergence the message issued may be "no feasible solutions are found".
Avoidance: Tighten up either CONVDV or CONVPR (say one thenth of the current
one) should help.
1-7264401
TB=AVG
2004
sol 200 - ufm 5629 (dsad1c) - FRSTRE - AT
When setting ATTB to AVG on a DRESP1 entry with RTYPE=FRSTRE the following
error message will appear:
USER FATAL MESSAGE 5629 (DSAD1C)
THERE ARE DRESP1 ENTRIES FOR RESPONSE TYPE = FRSTRE BUT THERE ARE NO
CORRESPONDING OUTPUT RESPONSES.
USER ACTION: CHECK THAT THE ELEMENT ID'S LISTED ON THE DRESP1 ENTRIES EXIST.
Avoidance: There is no avoidance other than to build a DRESP2 response for the
average.
1-7301106
Answers
2005
Elements - CTRIA3, CQUAD4, SNORM - Wrong
If offsets are defined on a warped plate elements with thermal loads and SNORM
is turned on (default in v2001), then the results may be incorrect.
Avoidance: Set PARAM,SNORM to 0.
The problem is related to missing terms in thermal load calculation. This

problem is fixed in CR 1-11702631
1-7358135
2004
T2 files may lead to failure
Postprocessing - PARAM,POST - Large OUTPU
An analyis that generates very large OUTPUT2 files may fail with an error
message similar to the following in the log file:
"outpn2.f", line 543: truncate: chsize: [22] Invalid argument
In the case where this message was encountered the OUTPUT2 file was 6gb before
the job was aborted.
Avoidance; Other than breaking the output requests up into multiple runs,
there is no avoidance.
Comment from JAS: This error has been eliminated in versions of MSC.Nastran
starsting with V2004. In V2004, the size of OUTPUT2 files is only limited by
the maximum file size supported by the operating system, not by any internal
MSC.Nastran limits.
1-7421606
059(DIOMSG)
2004
DBC - PARAM,POST - UFM 1250(BLKRD), SFM 6
MSC.Nastran may fail in the DBC module when a large number of SPCD enties with
different set ids exist in the model. The fatal messsages encountered are:
USER FATAL MESSAGE 1250 (BLKRD)
Read block number beyond end-of-file.
SYSTEM FATAL MESSAGE 6059 (DIOMSG)
Avoidance: Use PARAM,LOADU,0 to avoid this problem.
1-7452105
- SFM 3001
2004
Optimization - rmsdisp, rmsvelo, rmsacce
In an optimization run, if random response is requested, and the model contains

superelements, then the job will fatal with one of the following error
messages:
SYSTEM FATAL MESSAGE 3001 (DSARMG)
THE INPUT DATA BLOCK NAMED DRDUTB AT POSITION 2 DOES NOT EXIST
or
NO DRESPI ENTRIES EXIST FOR DESOBJ ID=
xx
Avoidance: The only avoidance is to not use superelements.

1-7461013
e Nested
2004
Documentation/QRG - INCLUDE Command May b
Remark 1 of the INCLUDE Case Control Statement in Section 4A of the QRG

incorrectly states that INCLUDE statements may NOT be nested. It should say
INCLUDE statements MAY be nested. Section 5 for the bulk data needs correction
as well.
1-7472309
2005.0.2
time leads to incorrect message
Frequency Response - SPCD - Insufficient
If an enforced displacment dynamic analysis has insufficient time to complete

all frequency solutions the following warning message will correctly be output;
however, it is incorrectly followed by system fatal message 5423 indicating an
incompatible matrix multiply.
USER WARNING MESSAGE 3045 (FRRD1)
INSUFFICIENT TIME TO COMPLETE THE REMAINING
100 SOLUTION(S) IN MODULE FRRD1
USER INFORMATION: TIME ESTIMATE TO COMPLETE:
857 SECONDS
TIME REMAINING
42 SECONDS
1-7495101
2004
- UFM 7139, Failed to locate implied DRESP2 IDs
If an implied DRESP2, references a DRESP1 with a function name as input for
the ATTB field, then the job may fail with UFM 7139.
*** USER FATAL MESSAGE 7139 (DOPR3N)
10, DRESP2 ID =
Avoidance : Renumber the DRESP1 IDs such that the DRESP1 with function name in
the ATTB field has the the lowest ID among all DRESP1s.
1-7510324
2001.0.9
Solutions for Supersonic Speeds
Aeroelastic Analysis - Different Flutter
The AMG module generates a different aerodynamic matrix across different

machine types for supersonic Mach numbers. The largest difference was found on
Windows/NT and the HPUX(64-bit) machines.
1-7514301
2001.0.9
- Wrong Answers
Optimization/Design Sensitivities - PCOMP
A composite optimization job may produce incorrect sensitivities when the

following two conditions are met:
1) Any material properties referenced by PCOMP entries are being designed;
2) The designed PCOMPs are referenced by more than one composite elements.
In addition, when a dummy PCOMP is present, the sensitivity coefficients may
also be incorrect.
Avoidance: There is no avoidance for the first case. However, for the case of
a dummy PCOMP entry, rename the PID to the smallest number among all PCOMP IDs.
1-7627701
2004
Eigenvalue Analysis - residual structure
CMR - massless mechanism - SFM 6143
Residual structure component mode reduction will fail with SYSTEM FATAL MESSAGE
6143 if a massless mechanism exists in the a-set.
Avoidance: Apply the following dmap alter

compile moders
alter 'segoa'(,-1),''(,1) $ got is actually goa
SDR1 USET,,MECHA,,,GOt,GM,,,,/
MECHg,,/1/'STATICS' $
endalter
1-7656709
SFM 4276
2004
Optimization/Design Sensitivity - DSAL -
An optimization job may fail in the DSAL module with the following error
message:
*** SYSTEM FATAL MESSAGE 4276 (GREAD)
ERROR CODE
3001 PID= 0
Avoidance: Increase the memory space using the mem= option on the nastran
submit command so that module dsvg1 will only need a single pass to perform the
triple matrix product. The amount of memory required can be found from SYSTEM
INFORMATION MESSAGE 7502 printed in the f04 file.
1-7734165
utput
2001.0.9
Aeroelastic Analysis - AESURF - Missing O
The printed output of the INERTIAL nondimensional hinge moment derivative

coefficients may not print in the proper table of the output in the f06 file.
If some AESURF entries have associated AESURFS entries and there are other
AESURF entries without associated AESURFS entries having identification numbers
lower than the AESURF with AESURFS, then the printed output of the
nondimensional hinge moment derivative coefficients will NOT appear in the
appropriate table in the f06 results.
Avoidance: The only avoidance is to renumber the AESURF entries.
1-7734708
2004
annot build with RedHat Linux
Distrubuted Memory Parallel - LAM 6.3.1 c
MSC.Nastran V70.7 and 2001 require LAM 6.3.1 to run distributed memory
parallel. This version of LAM will NOT compile with RedHat 7.2. To avoid the
need to compile LAM, the binaries may be downloaded from
ftp://ftp.msclinux.com/contrib/jjg/nastran
This is not an issue in MSC.Nastran 2003.
For installation:
1) cd /tmp
2) download usr_local_lam631.tgz
3) cd /usr/local
4) tar xvzf /tmp/usr_local_lam631.tgz
5) rm /tmp/usr_local_lam631.tgz
6) modify /etc/csh.cshrc and /etc/profile to
have /usr/local/lam-6.3.1/bin in your path
1-7782902
2004
sign Sensitivity Coefficients
Optimization/Design Sensitivity - Null De
When an optimization task includes the design variable whose initial value is
zero, the sensitivity coefficients with respect to that design variable become
null.
Avoidance: Do not start a design with zero design values.

1-7785001
ing Output
2004
Miscellaneous - GROUNDCHECK(SET=A) - Miss
No output is printed for GROUNDCHECK(SET=A).

compile sekr
alter 'setbit',''
PARAML CASES//'DTI'//324//S,N,SETBIT $
endalter
1-7793712
Output
2004
Aeroelastic Analysis - MPCFORCE - Missing
Aeroelastic analysis (SOL 146) in Version 2001 does not honor the MPCFORCE
output request. The case control command does not yield any MPCFORCE output.
Version 70.7 works correctly.
compile seaero
alter 'call fdrmgen',''
call fdrmgen uset,vgfd,cases,usetd,gmd,gm,goa,phdh,
msf,m2sf,bsf,b2sf,ksf,k4sf,k2sf,
MMG,M2MG,BMG,B2MG,KMG,K4MG,K2MG,,,
MSS,M2Ss,BSS,B2Ss,KSS,K4Ss,K2Ss,,ys,
ects,bgpdts,sils,xy
1-7820401
2004
Rigid Elements - GP4 - Missing UFM 2101
A SOL 103 job may fail without printing any messages in the f06 or log files
when illegal rigid element connections exist but there is no SPC request.
Avoidance: Add a dummy spc request. If illegal rigid element connections
exist, UFM 2101 will be output.
1-7939303
PCAX - UFM 316
2004
Rigid Elements/Multipoint Constraints - M
MPCAX entry may result in UFM 316.

Avoidance: Add NASTRAN SYSTEM(357)=1.
1-7979705
5423
2004
Transient Analsyis - PRELOAD, MPCF - SFM
A linear or nonlinear transient analysis that has a static preload subcase and
requests mpcforces will fail with SYSTEM FATAL MESSAGE 5423.
compile super3
alter 'paraml qg',''
paraml qg//'trailer'/1/s,n,ncqq//s,n,nqg $
if ( nqg<0 ) paraml qmg//'trailer'/1/s,n,ncqq $
endalter
1-7980301
entries.
2004
System Limits - ECHO=SORT - Limited to 26
There is an undocumented limit that the number of bulk data entry names
included with the ECHO=SORT case control command cannot exceed 26. Items
exceeding that number are ignored.
Avoidance: Limit the list to to the 26 most critical names or do not use this
option on the ECHO=SORT command.
1-8002452
2004
DMAP - TABPRT and USET option - UWM 3059
The TABPRT DMAP module with the USET table print option does not allow DOF sets
with more than 2 characters to be output. For example given:
DEFUSET,K,LTMA
USET1
LTMA
123
111
And this TABPRT command:

tabprt uset, bgpdts//'USET'/10///'LTMA'/ $
Results in this warning message and no USET table output:
*** USER WARNING MESSAGE 3059 (TABPRT)
SET IDENTIFIER LT DOES NOT EXIST. ERROR DETECTED IN SUBROUTINE
*** USER WARNING MESSAGE 3059 (TABPRT)
SET IDENTIFIER MA DOES NOT EXIST. ERROR DETECTED IN SUBROUTINE
Prior to V70.7, the user could get output for LTMA set by entering the USET bit
string for the K set in this example. This was broken in V70.7.
Resolution: Printout of all DOF sets will include the 4 character user sets as
follows:
tabprt uset, bgpdts//'USET'/10/-1/// $
1-8004001
llel is missing
Parallel Processing - Vendor implementation of tfork for para
MSC.Nastran does not support SMP parallel on Primepower because the vendor
implementation of tfork is missing. Delivered tpl problems dxxtp10 and others
will fatal with the message:
vendor implementation of tfork is missing.
1-8010801
or Answers
2004
Acoustic optimization - DRESP1, PRES - Po
Frequency response acoustic optimization convergence problems may occour if

response type PRES is used on a DRESP1 entry. The problem may converge to a
poor solution.
If PRES is replaced by FRDISP the analysis yields better results. PRES and
FRDISP should give identical results.
Avoidance: Use FRDISP instead of PRES.
1-8076115
2004
Postprocessing - DBC - UFM 1250 (BLKRD)
MSC.Nastran Linux 2001 will issue the following message if an xdb file larger
than 2gigs is created.
STATUS =
FILE = TEST.xdb
BLKNBR = 1129465448
0FATAL ERROR
, NSBUF3 =
16384
Avoidance: This problems has been corrected in Version 2001.0.9 available on

the Nastran 2001 R4 CD.
1-8080013
CWELD - TEMP(LOAD), TEMP(INIT), TEMPD - UFM 4016
CWELDs that reference a GS point that is loaded with either TEMP(LOAD) or

TEMP(INIT) will results in UFM 4016.
This problem is common because TEMPD is commonly used to define initial or
final temperatures for all the GRIDs.
Avoidance: Either do not use GS on the CWELD or do not use TEMPD.
1-8130019
2004
- Hangs if Massless Mechanism Exist
Distributed Memory Parallel/Eigenvalues
If an eigenvalue problem is run with DMP and the model contains massless
mechanisms, the
job may hang. After the 1st eigensolution stops with FATAL factor errors, the
solution properly goes into the massless mechanism check, detects and
constrains the mechanism degrees of freedom. The run starts the 2nd
eigensolution in the master cpu but doesn't restart the slaves and the job
hangs.
Avoidance(s):
1) Run in serial.
2) Run with PARAM,MECHFIX,YES in dmp (as opposed to default MECHFIX,AUTO).
1-8137638
Nonlinear Analysis - MATT1, TABLEM1 - Inefficient Processing
If SOL 106 is used for a problem that has no nonlinearity, (i.e. no MATS1, no
contact elements, and no PARAM,LGDISP,+1) but contains an MATT1 that
references a TABLEM1. then the job will iterate.
Avoidance: Run sol 101.
1-8192502
2004
20, 2121, 2122, 2123, UWM 3059
DMAP - VEC, UPARTN, MATGPR, etc. - UFM 21
The use of "+" and "-" to form new dof sets (e.g.;
VEC USET/VGX/'G-A'/'M' $) as may be specified in the set name parameter inputs
in the MATGPR, VEC, UPARTN, UMERGE, and UMERGE1 modules will cause various
fatal errors like UWM 3059, UFM 2120, UFM 2121, UFM 2122, and UFM 2123. Also,
leading blanks in the set name parameters will cause similar fatal errors.
Also, MATGPR does not allow for set equations longer than 4 characters.
1-8219301
rs
2001.0.7
Frequency Response - Possible Wrong Answe
MSC.Nastran 2001.0.7 for AIX 5.1 64 bit systems with a build date of April 3,
2002 on the Nastran 2001 (R3) cd may produce wrong answers for complex data
recovery.
The error has been corrected on a subsequent build dated April 19,
2002. The updated system may be requested from MSC support.
Avoidance: This executable is not automatically selected and must be
explicitly requested by setting exe=/aix/analysis.64 Thus, the problem may be
avoided by simply not selecting this executable.
1-8227901
- UFM 7147
2004
An optimization job fails with the UFM 7147 complaining that the objective
function referernces a non-scalar number. Although the job appears to be
defining a correct scalar quantity, the quantity is defined by a nested DRESP2
entry that further refers to a DRESP1 entry with the MAX function.
1-8235901
2004
OCCURRED IN ROUTINE BLDPK
DMAP - ORTHOG - BIOMSG: ERROR
100 HAS
A user DMAP that uses the ORTHOG module may result in a fatal message. For
example the dmap sequence:
TYPE PARM,,I,,NEIGV $
MATGEN ,/O1/1/10
$
ORTHOG O1,/PHO,DR/1/1/0.0/0.707/0.0 $
CEAD O1,,,,,,/RCPHX,CLAMA,OCEIG,LCPHX,CLAMMAT/
S,N,NEIGV//-1/'SVD'//-1/// $
END $
CEND
Results in:
*** SYSTEM INFORMATION MESSAGE 6581 (ORTHOG)
PERFORMING HOUSEHOLDER ORTHOGONALIZATION
BIOMSG: ERROR
100 HAS OCCURRED IN ROUTINE BLDPK
Avoidance:
1-8267177
To avoid this error, use one of the matrix modules such as MATPRN.
Complex Eigenvalues - EIGC - Poor Results with SYSTEM(108)=1
If the Householder QR method is forced using system(108)=1, poor results may

be obtained.
Avoidance: If the Householder method was not forced the QZHESS method would
have been used on the problem that encountered the poor results. The QZHESS
method would have solved the problem accurately and more efficiently.
1-8275506
2004
ith FREQ4 failed in DSAH - SFM 3002
Optimization/Design Sensitivity - MFREQ w
SOL 200 with ANALYIS=MFREQ with FREQ4 failed in the DSAH module with the
following message:
*** SYSTEM FATAL MESSAGE 3002 (DSAH)
EOF ENCOUNTERED WHILE READING DATA BLOCK DFFDNF
SUBROUTINE
(FILE 118) IN
Prior to the above failure the following messages were issued in every cycle
from the second on:
*** USER WARNING MESSAGE 6644 (FRPROD)
SOME OR ALL COMPUTED EXCITATION FREQUENCIES ARE OUTSIDE THE RANGE F1 AND F2
FOR FREQ4 BULK DATA ENTRY WITH ID = 502
THESE COMPUTED EXCITATION FREQUENCIES ARE IGNORED.
Avoidance: Use a different FREQi entry to specify the frequencies of interest
but not that the error may also occur with a FREQ entry with only one frequency
specified.
1-8310201
2004
d EKE - Missing Output
Distributed Memory Parallel/ACMS - EDE an
The EDE and EKE output are not supported in ACMS.

1-8315703
2004
GPSTRESS - STRESS(CORNER) - Wrong Answers
Inaccurate grid point stresses may be output for quad4 elements in nonlinear
analysis (SOL 106) when stress(corner) is requested.
Avoidance: There is no avoidance other than not requesting corner stress
output.
1-8328301
2004
Optimization/Design Sensitivity - MODTRAC
K, PARAM,OPTEXIT - Misleading Message
See notes activitity dated 7/15/2003
If the user has requested mode tracking along with PARAM OPTEXIT <4, the DOM12
module will be called and a message like:
10.
will be produced even though no design cycles have been executed.

compile exitopt
alter 'dom12','dom12'
IF ( (optexit<>3) and
(optexit>3 or cnvflg>0 or descycl1=DESMAX OR numddv>0 or
dsprint or dsunform or dsexport or
modetrak>0 or badmesh)
) DOM12 ,,xval,,,propof,optprmg,his,destab,geom1,coordo,edom,mtrak,
ept,geom2,mpt,epttabf,dvptabf,xvalp,geom1p,,,,,pcompt/
,,dbcopt,/
descycl1///CNVFLG/3/OPTEXIT/desmax/mdtrkflg/
despch/despch1/modetrak/eignfreq/dsaprt/protyp/badmesh/
xyunit $
1-8349125
2005.0.2
Superelements - SEELT lets you assign the
same element to two different superelements
No warning is issued if the SEELT entry is used to assign an element to more
that one superelement. The SEMAP will indicate the superelement that the
element was assigned to. This can result in unexpected answers for boundary
matrices. .
1-8383704
in punch file
2004
Random Response - RANDOM - Wrong answers
In a random response run if the PSD is output to the output2 file the values
may be incorrect in the punch file.
The output from the XYPLOT is correct.
1-8424704
423 (SADD5)
2004
Parallel ACMS - MPCF, SPCF, OLOAD - UFM 5
Parallel ACMS may fail if all of the following conditions exist:

1.
2.
3.
DMP>1
MPCFORCEs are requested.
Loads are applied to dependent DOFs which
are also interior to a domain (superelement)
or:
1.
2.
3.
DMP>1
SPCFORCEs are requested.
Loads are applied to constrained DOFs which
are also interior to a domain (superelement)
If neither MPCF nor SPCF is requested but OLOAD is requested and loads are
applied to a dependent or constrained DOFs which are also interior to a
domain, then the OLOAD output will be incomplete for the slaves' forcing
frequencies.
compile semfreq
alter 'call super3'(2,-1)
equivx frl0/frl/-1 $
endalter
1-8439702
2005.1
PT, SPCD - Wrong Answers
Frequency Response - PBUSHT, PELAST, PDAM
In a frequency response (SOL 108 or SOL 111) analysis using SPCD enforced
motion, if frequency dependent properties are defined on a PDAMPT, PELAST, or
PBUSHT entry, the frequency dependence is incorrectly interpolated.
Avoidance: Request a dmap alter avoidance from Client Support
1-8448301
2004
Optimization/Design Sensitivity - CQUADP,
CTRIA3 unrecognizable Entries in Punch File
A p-element optimization run may produce user unrecognizable Bulk Data entries
in the punch file for all types of shell elements such as CQUAD4P, CTRIA3P etc.
These entries will lead to a fatal message if they are subsequently read back
in as bulk data.
Avoidance: Remove these entries before reading back in.
1-8448304
2004
Miscellaneous - IFP, PBEAML - Format erro
r in punch file
A pch file containing updated PBEAML entries written in the large field format
may fail when read back into MSC.Nastran due to format error.
Avoidance: Add a blank line to the end of the PBEAML entry if the number of the
existing lines is an odd number.
1-8516805
2004
Optimization/Design Sensitivity - PCOMP Incorrect composite element matrices in SOL 200
If there are differences in the design model with respect to the analysis model
and the differences arise from DVCRELi entries and from DVPRELi entries that
point to PCOMP's, the composite updates will be ignored for the initial
analysis. The result will be that the analysis, sensitivities and first
redesign will be in error. It's possible that subsequent design iterations,
which have the correct properties, will be able to recover, but it is also
possible that the initial errors will be such that recovery is not possible.
compile desopt
alter 'modgeom2'(4), 'geom2nn'(3,1)
alter 'modgeom2'(5,-1), 'modgeom2'(5)
IF ( MODGEOM2 ) THEN $
DESITER=1 $ INCREMENT QUALIFIER IF GEOM2 IS UPDATED
$ EXCEPT WITH MULTI-MASTER METHOD
EQUIVX GEOM2NN/GEOM2/ALWAYS $
else $
DBEQUIV DATABLK=GEOM2, WHERE (DESITER=0 AND WILDCARD) ,
CONVERT (DESITER=1) OVRWRT $
ENDIF $ MODGEOM2
1-8550605
Loads - TEMPPi - Unexpected Results
The QRG documents which elements the TEMPPi entries are applicable to. However,
the code does not perform any check. If a TEMPPi entries references an
element that is not supported no thermal load will be applied and unexpected
Avoidance: There
been referenced.
against GEOM2 for
improper elements
is no avoidance other than verifying that valid elements have

The code needs to be modified to have GP3 check GEOM3
proper TEMPxx vs element type and issue a fatal message if
are referenced.
1-8564404
2004
Documentation/QRG - UFM 6632 (PAABSF) occ
urs when small value used within TZIMID
The following fatal message may occur when the value for TZIMID on the PAABSF
entry is less than the machine's numerical zero.
*** USER FATAL MESSAGE 6632 (EASFD)
THE NORM OF IMPEDANCE IS TOO SMALL
Avoidance: Specify a larger value for TZIMID.
1-8581001
2004
Failed Convergence
Optimization/Design Sensitivity - PBUSH -
If a designed PBUSH is connected to a GRID that has a displacement coordinate

system specified (CD on field 7 of the GRID bulk data entry), the senstivity
with respect to the PBUSH properties are likely to be in error with the result
that the optimization will not be able to make progress and may terminate with
various messages indicating failed convergence or maximum number of design
cycles.
Avoidance: Remove the CD from the GRID entry or replace the PBUSH with an
equivalent CROD or CELAS entry.
1-8587906
2004
- SFM 3007 (DOPRAN)
Optimization/Design Sensitivity - RANDOM
In Sol 200, if there are more than four frequency response subcases being
combined for random response, then the following error message may occur:
SYSTEM FATAL MESSAGE 3007 (DOPRAN)
ILLEGAL INPUT TO SUBROUTINE DOPRN2
Avoidance: Until the error is fixed, limit random response in SOL 200 to four
or less combined subcases.
1-8629707
2004
Strains computed in DDRMM
Elements - QUAD4, TRIA3 - Wrong Principal
Principal strains are computed incorrectly in DDRMM and are off by a factor of
2.
Avoidance: Add param,ddrmm,-1 to the input.
1-8680201
oor Message
2004
Case Control - SET - SFM 6143 (DUPART), P
The following case control will result in SFM 6143:

SET 1 = 100
SUBCASE 1
SET 1 = 101
DISP = 1
if grid point 100 does not exist.
Avoidance: Remove the superfluous SET definition.
1-8748813
Rigid Elements - RBE3 - Poor Message, Bad m-set selection lea
ds to floating point exception.
When an RBE3 element is defined with a bad selection for the m-set, the element
matrix may be singular. This can cause a floating point exception message to
be issued from the VECPLOT module. The message does not indicate the cause of
the problem.
Avoidance: Other than verifying that the RBE3s reference a statically
determinate m-set, there is no avoidance.
1-8751074
2004
uces incorrect warping coefficient
Elements - CBEAM, PBEAML - Z-Section prod
The calculation for the warping coefficient of a Z-section beam (PBEAML) is

wrong.
1-8781636
2004
Large File - SGI - UFM 1250
On the SGI, if NFS mount is used for filesystems that are larger than 2 gig,
then the job may fail with the following messages:
USER FATAL MESSAGE 1250 (BIORD)
Specified record is beyond maximum for this filesystem.
1-8783605
2004
correct stresses
Elements - CHEXA, TEMP(LOAD), PSOLID - In
When 8 noded CHEXA elements have different element coordinate systems and
default values for the PSOLID entry are used along with TEMP(LOAD), incorrect
stresses are output at corner/gauss points.
Avoidance: Set NASTRAN SYSTEM(309)=1 to use pre 70.7 CHEXA or set IN=2 on the
PSOLID entry
1-8788202
Optimization - Unneeded Constraints Cause Confusing Printouts
, Unneeded Calculations
The MSC.Nastran 2001 release supports putting a frequency range of applicabity
on the DCONSTR entry. Currently, if the referenced response falls outside this
range an upper and lower bounds of plus and minus 1.0e20 are substituted.
These responses should be ignored with no constraint applied.
Avoidance: There is no avoidance, but the negative effects are minor. The
answers should not be affected and the decrease in performance due to the
unneeded calculations should be minor.
1-8789951
2004.0.3
Large Models - Large Models with many rig
id elements may fail with SWM 2072 (GP4)
Large Models with many rigid elements may fail in GP4 with the following
message:
SYSTEM WARNING MESSAGE 2072 (GP4)
CARD TYPE
0FATAL ERROR
1-8803801
2004
2 OR 3 - Poor Sensitivities
Optimization/Design Sensitivity - APRCOD=
An error has been discovered in the calculation of the gradient of a response

when using the mixed method or the convex method (APRCOD=2 or 3) with inverse
design variables. The "exact" sensitivity should be multiplied by (x0/x)**2.
Instead it is multiplied by x0/x. The approximate responses are calculated
correctly, so the error only influences the determination of the search
direction once the design variables have moved from their starting values.
Avoidance: APRCOD=1 will not have this error, but is not recommended since the
inverse approximation can significantly help with the approximate optimization
even with the error. The error appears benign in the typical case.
1-8817411
2007.1.0
Matrix Methods - REAL Sparse Unsym Decomp
- Wrong Answers for rank of update greater than 1
Real sparse unsymmetric decomp may exhibit wrong answers for large models when
the rank of update specified by system(220) is set to a value larger than 1.
In Version 2004 HPUX and Linux systems set this system(220)=32.
Avoidance: For
1 in the system
encountered the
also avoided by
1-8821267
on from IFPS
Linux and HP it is recommended that system(220) be changed to

rc file. The client problem that discovered this problem
error during inertia relief calculations.
The problem was
specifying param,inrel,-2.
2005.0.2
Materials - MAT8 - Floating Point Excepti
Specifying very large values, greater than e+40, for Yt on the MAT8 entry may
cause a floating point exception in the IFPS module.
1-8957303
2005.0.2
Aeroelastic Analysis - AMP module unneces
sarily re-executed for each flutter subcase
In SOL 145 and SOL 200, the AMP module, which generates the QHH family of
generalized aerodynamic matrices, is re-executed for each flutter subcase, even
if there are no changes in modes or boundary conditions. This results in
increased solution times.
compile flutter
alter 'dbstatus qhhl'(,-1)
type parm,,i,n,qf,qc $
type parm,nddl,i,n,cmeth,fmeth $
qf=fmeth $
qc=cmeth $
fmeth=0 $
cmeth=0 $
alter 'ENDIF \$ NOQHHL\>0'
fmeth=qf $
cmeth=qc $
alter 'FA1
KHH,BHH,MHH,QHHL',''
dbview qhhl0=qhhl where (fmeth=0 and cmeth=0) $
FA1
KHH,BHH,MHH,QHHL0,CASES,EDT/
FSAVE,KXHH,BXHH,MXHH/
S,N,FLOOP/S,N,TSTART/S,N,NOCEAD/LPRINT $
alter 'ADR
FPHH,CASEYY,QKHL',''
dbview qkhl0=qkhl where (fmeth=0 and cmeth=0) $
ADR
FPHH,CASEYY,QKHL0,FLAMA,AEBGPDT,AEUSET/
PKF/
BOV/MACH/'FLUTTER'/aeconfig/symxy/symxz $
compile flutsens
alter 'DSFLTE KHHx,BHHx,MHHx,QHHL,',''
dbview qhhl0=qhhl where (fmeth=0 and cmeth=0) $
DSFLTE KHHx,BHHx,MHHx,QHHL0,FLUTAB,r1tabr,casem,,/
CPHL,CPHR,VTQU0/1 $
endalter
1-8987307
rcentage
2008.0.0 (MD R3)
Element Strain Energy - ESE - Negative Pe
Negative percentages may be printed for element strain energy contribution if

param,tiny is set to 0. Negative percentages may be printed irrespective of
the value of Tiny. The percentage may be high because nastran computes the
percentages of two groups, all negative or all positive. Since most negative
strain energy are "computer noise", values like 1.0E-12, when values are much
larger, 1.0E-10, the percentage maybe -50%. Valid negative values only occur
with thermal loading, see param xflag for the equations
Notes about TINY. The "positive" ESE due to Mechanical and the Absolute Value
of the "negative" due to Thermal load are compared to TINY as the floor. Note
both list absolute floor for TINY is zero, therefore negatives are not
considered to be below the floor in the presence of thermal loads. The
criteria for negative and floor was modified to take into account the selection
of thermal loads to modify the collection of elements below TINY.
1-8995906
2005.5
Large Models - DECOMP - Integer Overflow
Very large models (millions of degrees of freedom) may overflow the integer,
where the non-zero terms of a sparse factor matrix is stored.
The integer overflow usually occurs during the reordering. Depending on the
context, it may be possible to avoid the integer overflow by using the DCMP
module rather than the DECOMP module, since DCMP uses grid-based or
supernode-based reordering, while DECOMP uses
dof-based reordering.
Avoidance: Since version 2005.5, one avoidance is to use mode=i8.
1-9007221
EPOINTs
2004
Dynamic Analysis - EPOINT - Null Loads at
A dynamic analysis using static loading entries ignores extra point (EPOINT)
loading in Version 2001.
1-9025316
2004
S4), Poor Message
Rigid Elements - RSSCON - SFM 6694 (GS4R
The SFM 6694 does not identify the GRID id or RSSCON element id that causes the
fatal message. It is extremely difficult to find the problem element in large
models with thousands of RSSCON elements.
1-9029611
2001.0.7
SSSALTERs - STATDIVA.V2001 errors
The SSSALTER named statdiva.V2001 has two problems associated with it. These
appear to be day 1 problems:
1) The Left handed complex eigenvector is plotted instead of the right handed
vector.
2) The displacements are incorrect if a SUPORT is present.
Resolution: Get the corrected alter from MSC technical support. The corrected
alter should be delivered with Nastran systems after V2001.0.7
1-9048033
k 9
2004
Documentation/QRG - PBEAML - Remove Remar
In the V2001 Quick Reference Guide, Remark 9 of the PBEAML entry states that
dimensions of the beam cannot be used directly as design variables in SOL 200.
This is no longer true as this capability was added into V70.7.
Remark 9 of the PBEAML should be removed.
1-9075705
2004
MID3 - Wrong Answers
Nonlinear Analysis - PSHELL, MID1, MID2,
In nonlinear analysis (SOL 106 and 129) the MID3 field on a PSHELL entry must
reference the same combination of nonlinear materials as the MID1 and MID2
fields else the element may behave in a linear manner and wrong answers will be
produced.
For example, when MID1 (and MID2) refer to MAT1, MATS1 and MATT1 but MID3 only
refers to MAT1 in a PSHELL card. Any plate element, QUAD4/QUADR/TRIA3/TRIAR,
uses this element property card will behavior like a linear element in the
nonlinear analysis.
[Avoidance]: Keep MID3 blank or refers to the same combination of material
properties like MID1 (and MID2) if it is possible. (Theoretically, MID3 cannot
tefer to MATS1 but NASTRAN will only issue a warning message and ignore the
reference of MATS1 for MID3 in V2001.)
1-9133301
unreadable
2004
Access - DBIO error causes database to be
The dbio libraries delivered with MSC.Nastran 2001.0.7 has an error which may
not allow new databases with user defined objects to be read after they are
created.
Avoidance: Use the dbio libraries delivered with Nastran 2001.0.9 on the 2001
R4 cd.
1-9145912
2004
or Flutter response output.
Optimization - Missing Density printout f
In SOL 200, when P2=8 is set on the DOPTPRM entry, the responses of DRESP data
are printed. For flutter damping responses, Nastran prints out the Mach number,
velocity, mode number and damping value. However, the density value is missing
and this is required in order to properly sort out the roots and establish the
altitude.
Avoidance: Print out the R1TABRG datablock after the DOM 10 module. Word 11 of
each record is the density. For example:
$V2001
COMPILE DESOPT
ALTER 'DOM10'
tabpt r1tabrg// $
MATPRN R1TABRG // $
ENDALTER
1-9153101
2004
s when end B data is not entered.
Elements - PBEAML - Possible Wrong Answer
Remark 5 for the PBEAML in the QRG states that if blanks are used in the
specification of end b data, the corresponding values from end a will be used.
It has been found that, at least in the case of the ROD section type, a blank
DIM1(B) input will result in a constant section beam being produced, but other
occurances of blank fields have also been shown to produce incorrect results.
Avoidance: Don't use blank fields. Don't assume Remark 5 for the PBEAML is
honored. Instead, enter the data explicitly.
1-9246401
2005.1
FM 6144, SFE 4276
Static Analysis - PARAM,INREL, QSETi - S
PARAM,INREL in the presence of a q-set leads to the following fatal message:
SYSTEM FATAL MESSAGE 6144 (MERGE1)

THE SIZE OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE
compile statrs
alter 'na6=',''(,1)
Na6=notset+6 $
Matgen ,/va6/6/na6/notset/6 $
alter 'Umerge1 uset,qra',''
Umerge1 uset,qra,,,/qrg/'g'/'t'//1 $ for spcforces
compile sedisp
alter 'umerge uset,uls,'(3),''
if ( noqset>-1 and nolset>-1
) umerge uset,uls,/uas/'l+q'/'l' $
endalter
1-9259910
2004
Eigenvalue Analysis - METHOD(FLUID), METH
OD(STRUCTURE) does not produce separate tables
In SOL 103 analysis for a fluid/structure model, when both METHOD(FLUID) and
METHOD(STRUCTURE) case control commands are present, uncoupled fluid and
uncoupled structural modes are calculated. But instead of having a separate
table for each, they are put together. There should be seperate tables.
1-9268801
2004
- Wrong Answers
When a T type section on the PBEAML is designed (SOL 200), the E1 stress
recovery point has a sign error.
Avoidance: Use the T1 or T2 type section when designing this type of section.
1-9341428
2004
ith STATSUB - UFM 3046
Dynamic Analysis - SPCD, Enforce Motion w
Direct enforced motion using SPCD with a pre-stressed static subcase (STATSUB)
containing a mechanical and temperature load fails in the FRRD1 module issuing
a User Fatal Message 3046 with SOL 108 or 111 when a temperature load is
applied. The run will complete normally if only the mechanical load is
selected.
Prior to the UFM 3046, UIM 9035, indicates that no static shapes were found to
augment mode shapes. However, the static subcase contains displacements. It
appears that thermal loading causes Residual Vectors to fail.
compile semfreq
alter 'lcgen',''
LCGEN
CASErS,SLT,ETT,dynamic,geom4s/
CASES2/S,N,DUMMY/'freqresp' $
alter 'dpd '(,-2)
dbview ysw=ys where (templd=0) $
equivx ysw/ys/-1 $
endalter
or use the large mass method.
1-9350803
Restart - OMODE, OUTPUT2 - Extra Output
If the OMODE Case Control is used in a restart run for data recovery using
output2 (e.g., param,post,-1) and the OMODE command does not appear in the
coldstart run, then the requested output may be written out twice to the
output2 file, or OMODE will not have an effect.
1-9360923
2004
Optimization/Design Sensitivity - Wrong
results for Flutter optimization with multiple subcases
IN SOL 200, if multiple flutter optimization subcases exist and the same
FMETHOD ID is referenced in both subcases, then the sensitivities for the
second subcase will be incorrect and hence the optimization will not likely
find a good solution.
Avoidance: Be sure each subcase references a different FMETHOD ID. The FLUTTER
entries selected by the two different FMETHOD IDs can be identical so long as
their IDs are not the same.
1-9391501
Answers
2004.0.3
Composites - PCOMP - Large Model, Wrong
Large models with composite elements that have a large number of plies may
encounter SYSTEM WARNING MESSAGE 3008 indicating that insufficient memory
exists in STRSORT. The job may continue and can give bad results with
incorrect element numbers and/or asterisks indicating an overflow in the ply
number field.
1-9468205
2004
NG - UFM 1126 (GNFIST)
Superelements/Frequency Response - SDAMPI
Multiple superelements run with SOL 108 using an SDAMPING request at the
superelement level will cause the program to terminate prematurely during
processing of the next superelement with a SDAMPING request.
*** USER
DMAP
MPHVX ,
USER

MODULE PHASE1B IS ATTEMPTING TO OUTPUT DATABLOCK
236 NAME =
ACTION: DELETE THE DATABLOCK, OR USE FILE MPHVX=OVRWRT
Avoidance: Replace the data block name MPHVX in the call to subDMAP SUPER1 in
SEDFREQ with MPHVZ.
1-9486601
Random Analysis - RANDOM - No Warning Message
If the RANDOM Case Control command requests a non-existent RANDPS entry, the
program skips the random analysis without issuing a message.
Avoidance: Add the necessary randps entry.
1-9550910
wers
2004
Rigid Elements - RSSCON, RBE2 - Wrong Ans
In MSC.Nastran Version 2001 wrong answers may occur if RBE2 and RSSCON elements
are used together.
Avoidance: Avoid using RSSCON and RBE2 elements together. Always verify the
model using GROUNDCHECK. In the model that discovered this problem,
GROUNDCHECK indicated a problem in the n-set.
1-9616409
2004
Complex Eigenvalues - STATSUB - UFM 5423
In SOL 107, if the SPC and/or MPC request in the STATSUB subcase is different
from the statics subcase then the run will fail with UFM 5423.
compile sedceig
alter 'call pmluset'(,-1)
PARAML CASErs//'DTI'/1/2//S,N,MPC $
PARAML CASErs//'DTI'/1/3//S,N,SPC $
PARAML CASErs//'DTI'/1/255//S,N,Suport $
endalter
1-9627001
2004
The RFORCE entry requires a vector to define the rotation axis. If the
components of this vector are defined as <0.0 0.0 0.0> (ie. no vector defined),
Nastran assumes a vector of <1.0 0.0 0.0>. This can lead to an incorrect load
application. If the vector is defined as <0.0 0.0 0.0>, a fatal error should
be issued.
For RFORCE records, we should accept < 0. ,0. ,0. > for the vector ONLY if
both "A" and "RACC" are zero. This can not lead to an error in the non-EMAS
code. For FORCE or MOMENT records, accept a zero vector ONLY if "F" or "M" is
zero.
1-9638401
2004.5
nfinite Loop in READ
Nonlinear Buckling Analysis - Lanczos - I
The READ Module may go into an infinite loop for non-linear buckling model when
using the Lanczos method.
1-9691321
2004
Miscellaneous - ddladd segmentation fault
on HP (v2001.0.4), doesn't work, V2001.0.9
Using ddladd from Nastran V2001.0.4 may produce a segmentation fault on HP.
Avoidance: Use ddladd from the V2001.0.9 (V2001r4) installation
1-9703728
d
2004
DMAP - DBVIEW, SCR=YES - Datablock Delete
If scr=yes is used in a run with a user-dmap that uses the DBVIEW module, then
the datablock referenced on the DBVIEW statement may be deleted at the end of
the modified subdmap.
Avoidance: Insert the following dmap alter to the main subdmap.
Compile whatever-the-main-subdmap
alter 2 $
putsys(0,192) $
1-9707301
Output
2004
Eigenvalue Analysis - GPSTRESS - Missing
In a modal analysis, Grip Point Stresses are only output for the first mode.
1-9731902
2004
or, line 963: truncate ...
Postprocessing - Windows Only - outpx2.f
On Windows, Nastran may terminate while writing an op2 file with the following
message:
line 963: truncate: lseek: [22] Invalid argument
logical unit 12, named './khaled.op2'
*** Execution terminated
This error has been corrected starting with MSC.Nastran V2004. There are no
limits in writing an OUTPUT2 file except those imposed by the operating system,
i.e., those related to file size limits.
1-9742614
k
2004
GPFORCE - GPFDR, ESE - UWM 4506, Tracebac
If the number of modes referenced by the MODES case control command is greater
than the number of eigenvalues calculated and GPFORCE or ESE data recovery is
requested, then the job will fail in GPFDR with a traceback or dump. The
failure may be precede the failure:
USER WARNING MESSAGE 4506 (GPFDEV)
Avoidance: Make the number of modes computed is equal to the number of modes
requested in case control
1-9754740
2004.5
DMAP - Poor Message, BIOMSG: ERROR 3001
A dmap that is missing a "/" such that the first parameter is in the output
slot failed with the message below which gives no indication of the problem.
0
Avoidance: Correct the problem dmap statement.

1-9853601
2004
ve a log option
Documentation/QRG - TABLEM1 - Does not ha
The TABLEM1 entry does not have a LOG option. This should be removed from the
QRG.
John said he gave fix to Lori.
1-9884901
2004
ments if GRAV entry is used
Aeroelastic Analysis - Incorrect hinge mo
The following two cases have identical trim results, but different hinge moment
values:
1. 1g trim, no grav card
2. 0g trim, grav card
The elastic increment due to statically applied loads is missing in the second
case.
1-9884904
2004
Aeroelastic Analysis - Missing Data from
aero monitor point total coefficient table
The second "RESTRAINED INCR." column is hardcoded to N/A. If static applied
loads are present, this column should contain nonzero data.
1-9884907
2004
Aeroelastic Analysis - Missing Aero Monit
or Point Output
If applied loads are present, then their aerodynamic elastic increment should
be printed.
1-9925101
subcase
2004
Nonlinear Analysis - Fails for zero load
SOL 106 fails with a 'No Load Increment Exists for Nonlinear Subcase' error
message when the load is null in a subcase. The null load may result from
user's input or computed zero load. SOL 106 needs to be changed to allow for
input and computed zero load.
1-9934302
2008.0.0 (MD R3)
Nonlinear Analysis - Wrong eigenvector fo
rces and stresses for restarts from SOL 106
Executing SOL 106 with NMLOOP and restarting into SOL 103 to calculate
eigenvalues will produce incorrect eigenvectors and associated stresses and
forces.
Avoidance: The following alter avodance is available for Version 2001. It
needs to be modfied for other versions.
$ alter.
COMPILE SUPER3 $
ALTER 'VECPLOT.*UGVBAS','MATMOD.*BGPDTN' $
CALL
NEWBGPDT UGNI,BGPDTS,CSTMS,CASEDR/BGPDTN $
ALTER 'SDR2.*IEF1','' $
SDR2
CASEDR,CSTMS,MPTS,DIT,EQEXINS,,ETT,OL2S,BGPDTN,,,UG2,ESTN,
XYCDBDR,OINT,PELSETS,VIEWTB,GPSNTS,DEQATN,DEQIND,DITID,PCOMPT,/
,,IUG1,IES1,IEF1,,/APP1/S,N,NOS2A/S,N,NCOMPS/////ACOUT/PREFDB/
TABS/SIGMA/ADPTINDX/ADPTEXIT/FALSE $
COMPILE NEWBGPDT $ AVOID TYPE NDDL RULE 8.
SUBDMAP NEWBGPDT UGNX,BGPDTS,CSTMS,CASEDR/BGPDTN $
TYPE
DB UGNI $
VECPLOT UGNI,BGPDTS,,CSTMS,CASEDR,,,,/UGVBAS,,,,/0/0/3 $
MATMOD UGVBAS,BGPDTS,,,,/BGPDTN,/11 $
RETURN $
END $
1-9936202
Nonlinear Analsyis - MID4, TEMP(BOTH) - Wrong Answers
When a nonlinear shell element has an MID4 specified,

either on a PSHELL or PCOMP, the corresponding coefficients of thermal
expansion may not be used in the calculation of the thermal strain. This
appears to occur only for temperature-dependent coefficients of thermal
expansion, and does not occur for stress-dependent materials, which enforce
MID4=0.
1-9975012
2004
ONROD - SWM 6065 (DBC)
Postprocessing/DBC - PARAM,POST,0 CROD, C
Models with CROD and/or CONROD elements that contains param,post,0 to generate
an .xdb file may issue the following warning message:
*** DBCMSG ERROR MESSAGE
1 FROM SUBROUTINE ELMBLK
UNABLE TO OPEN OUTPUT RELATION FCONR
RETURN CODE = 1.
and results from these elements may be missing during postprocessing.

Avoidance: Use an op2 file for post processing, param,post,-1, instead.
1-10013201
2004
Optimization/Design Sensitivity - PBEAML,
PBARL - Incorrect Torsional Sensitivity
The analytical calculation of the sensitivity of the torsional stiffness of the
BAR section type in the beam library (PBARL and PBEAML) is in error when the
aspect ratio (DIM1/DIM2) is less than 1.0.
Avoidance: One avoidance is to redefine the problem so that DIM1/DIM2 is
greater than 1.0. Another is to replace MSC's BAR cross section type with a
user defined BAR with the sensitivty corrected. When the torsional stiffness is
not important, the error in the sensitivity is also likely to be unimportant.
1-10021822
train Output
2004
Response Spectra - PARAM,POST - Missing S
To get strains in Response Spectra (SOL 103, PARAM SCRSPEC), the input file
must contain STRESS and STRAIN output requests as well as PARAM POST -1.
Otherwise the strains will not be calculated.
Avoidance: The following alter allows the STRAIN command to be honored
regardless of PARAM,POST:
compile postreig
alter 'if ( post=-1',''
alter 'OFP
DOSTR1'
if ( post=-1 and patver>=3. ) then $
alter 'dostr1',''
DDRMM
CASEXX,UHVR,,IPHIG1,IQG1,IESTR,,XYCDBDR/
OUPDUMMY,OQGDUMMY,DOSTR1,,/OPTION/3 $
endalter
1-10025339
2007.0.0
Aeroelastic Analysis - Unsymmetric Decomp
of Singular matrix - Poor Message, UFM 6136 (UDSNC)
If a singular matrix is presented to sparse unsymmetric decomposition, the
module issues the erroneous message:
*** USER FATAL MESSAGE 6136 (UDSNCD)
17 K WORDS
Increasing the memory results in the same message.
Avoidance: The model must be corrected so the the matrix is not singular.
1-10069515
2004
GPSTRESS - Missing Output
If the SURFACE requested has the ID = 110 or ID = 111 then the GPSTRESS
calculation may be skipped.
Avoidance: Change the id of the SURFACE
1-10073602
001 (DSAR)
2004
Superelements - EXTSEOUT, SOL 112 - SFM 3
If EXTSEOUT Case Control command is used to create an external superelement

then the subsequent assembly restart run may fail in Sol 109 and 112 with the
message:
SYSTEM FATAL MESSAGE 3001 (DSAR)
EXIST.
2 DOES NOT

compile super3
alter 'dsar',''
DSAR
uh2,,,/uh2d,j2,j3,,/-1 $
endalter
1-10077813
2004
swers using TPS Method
Aeroelastic Analysis - SPLINE4 - Wrong An
Static Aero (SOL 144) or Aeroelastic flutter analysis (SOL 145) in Version 2001
may produce wrong answers when SPLINE4 uses the TPS method.
Avoidance: Use the IPS or FPS method.
1-10090702
in IFP
2007.0.0
Elements - CBAR - Floating Point Overflow
On the CBAR element, if the value on the orientation vector is very large
(e.g., E268), then the job may fail in IFP with a dump or a floating point
overflow error.
On other machines, the job will continue and eventually
fail with a NaN output. The proper UFM 316 should have been issued instead of
the above unclear messages. This problem has been observed on the AIX, SUN,
Windows, and possibly other machines.
Avoidance: Modify the large number to a more reasonable number.
1-10106301
2004
d FREQ5 - SFM 3001 (DSAH)
Optimization/Design Sensitivity - SEs an
A SOL 200 job with traditional superelements and FREQ5 entry failed in DSAH
with the following fatal message.
*** SYSTEM FATAL MESSAGE 3001 (DSAH)
THE INPUT DATA BLOCK NAMED CSNMB
AT POSITION
12 DOES NOT EXIST.
SUBDMAP OR A HIGHER SUBDMAP
BUT THE CURRENT QUALIFIER VALUES DO NOT MATCH
THE QUALIFIER VALUES OF THE DATA BLOCK(S) ON THE DATABASE.
SEQUENCE AND NOT USING THE
ALTER EXECUTIVE CONTROL STATEMENT, THEN CHECK FOR BULK
DATA AND/OR CASE CONTROL INPUT
ERRORS. IF NO ERRORS CAN BE FOUND, THEN CONTACT
MSC.SOFTWARE CLIENT SUPPORT.
2. IF YOU ARE EXECUTING A DMAP PROGRAM NOT SUPPLIED BY
MSC.SOFTWARE, THEN FOR DEBUGGING PURPOSES
INSERT STATEMENT DIAGON(20) BEFORE THE MODULE SHOWN ABOVE.

PROGRAMMER INFORMATION: THE FIST NUMBER IS
112 AND SUBROUTINE IS GOPEN
Avoidance : Remove all bulk data entries for upstream SEs and run as a residual
only job
1-10125401
2004
Optimization/Design Sensitivity - Mislead
ing messages indicating geometry checks failed.
The design sensitivity phase of SOL 200 creates perturbed elements with
internally defined EID's that are meaningless to the user. If these perturbed
elements fail tolerance checks, a message is printed with this information that
is of no value to the user.
Avoidance: The misleading prints can be turned off by setting DMGCHK, the 27th
parameter in the EMG call, to FALSE in subDMAP pslgdv
User information: Typically, the user defined elements have violated the same
tolerances so that there is a message that is meaningful based on the original
elements and the messages on the perturbed elements can be ignored.
1-10183311
2004.0.4
Optimization/Design Sensitivities - DRESP
2 - Wrong Sensitivities for DRESP2 that use FUNC
The sensitivities of DRESP2 entries that use the FUNC feature in place of a
DEQATN and contain DVxRELy or DNODE data are incorrect for all but the last
design variable.
Avoidance: The FUNC feature cannot be used for DRESP2 entries that include
DVxRELy or DNODE data. Use the EQID instead.
1-10220502
2004.0.3
Optimization/Desgin Sensitivity - PBEAM Incorrect Punch Output, UFM 315 (IFPDRV)
SOL 200 punches designed PBEAMs but when they are used as input to nastran the
run fails with the message:
FORMAT ERROR ON BULK DATA ENTRY PBEAM
Nastran incorrectly writes mid-station information with SO=NO on PBEAM.
Avoidance: Change SO to YES or remove mid-station information.
1-10290318
rs
2004
Nonlinear Analysis - TEMPRB - Wrong Answe
When running a nonlinear analysis (SOL 106) with temprb (defining a beam
cross-section temp gradient) referencing a temperature dependent coefficient
of thermal expansion, the resulting lateral deflection is in the wrong
direction.
1-10303039
2004
- Floating Point Exception
Eigenvalue Analysis - READ, PARAM,RESVEC
In SOL 111 frequency response with direct enforced motion a singular mass
matrix will lead to a floating point overflow in the READ module if residual
vectors (param,resvec) are requested.
Avoidance: Provide a non-singular mass matrix.
1-10336801
s - SFM 3001
2004
Flutter Sensitivity Analysis/Superelement
A superelement flutter optimization task can fail with the message:

SYSTEM FATAL MESSAGE 3001 INPUT DATA DUG DOES NOT EXIST
if the residual superelelement contains no elements (i.e, it is a collector).
Avoidance: Make sure at least one finite element is present in the residual.
1-10342205
Nonlinear Analysis - RESTART - UFM 9086
In a nonlinear analysis, model changes are not allowed in a restart run. The
only allowables changes are boundary condition changes in SOL 106. If property
values are changed in a restart, then the job will fail with the following
misleading messages:
PARAM, LOOPID,
x DOES NOT CORRESPOND TO A VALID LOOP IDENTIFICATION
NUMBER.
Avoidance: Do not perform model changes in a nonlinear restart as it is not
supported in MSC.Nastran.
1-10344002
2004
Postprocessing - PARAM,POST - UFM 1250
If a model has only SPC type loading and param,post,0 is set to produce an xdb
file the following fatal message may occur:
STATUS =
FILE = .'test.xdb
BLKNBR =
199
*** SYSTEM FATAL MESSAGE 6059 (DIOMSG)
, NSBUF3 =
1024
Avoidance: The fatal message may be avoided by adding a dummy FORCE entry.
1-10372301
2004
Aeroelastic Analysis - SFM 7376 (MKCSTA)
If an aerodynamic database is reused, and the database contains a coordinate

system with the same ID as one in the bulk data, Nastran will compare the two
coordinate systems and check whether or not they are the same. This check is
overly restrictive and the following error may be produced:
*** SYSTEM FATAL MESSAGE 7376 (MKCSTA)
COORDINATE SYSTEM ID
11 WAS FOUND IN BOTH COORDINATE SYSTEMS
TABLES BUT DOES NOT DESCRIBE THE SAME COORDINATE SYSTEM.
USER INFORMATION: COORDINATE SYSTEMS TABLES TO MERGE WITH CONFLICTED
COORDINATE SYSTEMS IDS ARE NOT HANDLE AT THIS TIME.
USER ACTION: INPUT COORDINATE SYSTEM IDS TO ALLOW UNIQUESS AMONG AREO AND
STRUCTURAL MODELS COMBINED
1-10385207
2004
UX IA64 Nastran 2001 Installation
Installation - Insufficient Space for HP-
On some Itanium Workstations running HP-UX 11.22, the mscsetup script fails to
execute completely, and it gives an error saying "not enough space available
for decompressing files". This is due to the way the mscsetup script estimates
the available space on SOME itanium filesystems.
Avoidance: The HP IA-64 systems have not been consistent in the information
that is returned when the mscsetup script queries the system for the amount of
space available. Two distint problems have been found and they have required
different modifcations to the script to make it work.
The corrected script
is too long to list here but it is available through client support or at:
http://www.mscsoftware.com/support/software_updates/index.cfm#nastran.
Note that the corrected script will not solve all problems and on some
installations the user may still have to gunzip the files. The procedure for
completing the installation with the udpated script is:
A.. Copy the updated mscsetup script to /tmp/mscsetup
cp mscsetup /tmp/mscsetup
B. Execute /tmp/mscsetup
/tmp/mscsetup
C. Answer the rest of the installation questions.
1-10415448
2004
Superelements - DBEXT location parameter
to EXTDB datablock cannot be changed with a PARAM
The datablock EXTDB, used for automatic external superelements, has the
location parameter DBEXT. The default for this parameter in the NDDL is
'SCRATCH'. The parameter is forced to the DBALL in subdmap PHASE0.
This parameter should be available to change in the bulk data to allow the
EXTDB datablock to be written to another dbset (MASTER for instance) when using
the MATRIXDB option for external superelements. This would then only require
the much smaller MASTER file to be online at the external superelement
attachment phase, and the large omitted dof database could be off-line or even
deleted if no data recovery was needed.
Avoidance:
Insert the following DMAP alter in the run that generates the external data and
set PARAM,DBEXT1,MASTER in the bulkdata (or whichever dbset is desired)
COMPILE EXTOUT NOLIST $
ALTER 1 $
TYPE PARM,NDDL,CHAR8,N,DBEXT $
TYPE PARM,,CHAR8,Y,DBEXT1=' ' $
IF (DBEXT<>' ') DBEXT=DBEXT1 $
1-10441318
Complex Eigenvalue - CLAN - Possible Wrong Answers
Beginning in Version 70.7, when using complex Lanczos, the phase angles for the
complex eigenvectors may be inaccurate if they are small numbers.
Avoidance: There are two possible avoidances.
1. Use the Hess method.
2. Add the following system cell to the top of your input file
1-10469313
2005.0.2
Heat transfer - view factor - If CHBDYG I
D exceeds 1.0e8 then the view factor output is not printed
If a CHBDYG ID exeeds 1.E8 then the view factor output will contain ***** for
the id as shown below and the view factor output is not printed.
*******
*******
*******
*******
*******
*******
*******
*******
*******
*******
9.7893E-02
9.7893E-02
9.7893E-02
9.7893E-02
9.7893E-02
2.10642E-06
2.44702E-05
7.92138E-05
1.52525E-04
2.26236E-04
2.15175E-05
2.49968E-04
8.09187E-04
1.55808E-03
2.31105E-03
3.2974E-05
3.8119E-04
1.1879E-03
2.1771E-03
3.0770E-03
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
1-10470002
2004
Optimization/Design Sensitivity - Punch F
ile Produces Incorrect CQUAD4 Format - UFM 316 (IFPDRV)
When QUAD4 entries with thickness specified on the PSHELL or PCOMP entries are
designed in a SOL 200 run, the resulting CQUAD4 data written out in the PUNCH
file has -1.0000 placed in the 4 thickness fields on the continuation.
Subsequent use of these QUAD4 entries will result in:
ILLEGAL DATA ON BULK DATA ENTRY CQUAD4
Avoidance: Strip out the -1.0000 data from the QUAD4 data in the punch file
prior to using it in a subsequent run.
1-10474401
4
2004
Optimization/Design Sensitivity - SFM 614
The message:
SYSTEM FATAL MESSAGE 6144 THE SIZES OF THE INPUT MATRICES AND PARTITIONING
VECTORS ARE INCOMPATIBLE
has been encountered with static aeroelastic optimization with multiple
boundary conditions. TDVI and COL are the two input matrices to the merge dmap
module.
User Information: there have been a number of fixes to the static aeroelastic
optimization with multiple boundary conditions. This most recent error occurs
when one of three subcases does not contain any active constraints while the
other two share an mpc condition that is different from the deleted subcase.
Avoidance: The avoidance is to add the nsol parameter to the second call to the
gendv2p module in the respsen subdmap. This entails passing the NSOL parameter
into respsen, typing it and including it in the module call. Contact your MSC
Client Support for the dmap alter.
1-10479829
2004
Optimization - Punch file not preserving
XLB, XUB,DELXV and DDVAL fields on DESVAR entry
If the DELXV field of a DESVAR entry is left blank and SOL 200 is run, the
resulting .PCH file has replaced the blank DELXV field with the DELX value from
the original DOPTPRM entry. Therefore, if the user changes the DELX parameter
in a subsequent run that uses the DESVAR data from the .PCH file, the DELX
value is ignored because DELXV has already been explicitly set.
Avoidance: Manually replace the DELXV data with a blank field on the DESVAR
data in the .PCH file in order for the DELX setting from the DOPTPRM to be used.
1-10483401
2004
PCD - Wrong Answers
Superelements/Enforced Motion Results - S
Incorrect results are produced when the SPCD method of enforced motion is used
in a multi-superelement analysis.
Avoidance: Use the large mass method.
1-10501801
2004
SFM 3007 (DOPR3B)
The message:
SYSTEM FATAL MESSAGE 3007: ILLEGAL INPUT TO SUBROUTINE DOPR3B
can occur when a DRESP1 entry with a composite response type (CSTRESS,CSTRAIN
or CFAILURE) refers to a PCOMP ID that does not exist.
Avoidance: Check that the composite responses point to existing PCOMP property
id's.
1-10507402
2004
2 (DSDJ1D) VARIATIONAL
The message USER FATAL MESSAGE 5172 (DSDJ1D) may be issued when:
a. Material damping is present in the model
b. Multiple properties of a given finite element are independently designed
(e.g., K1 and B1 on a PBUSH)
c. The designed element does not have any material damping associated with it.
d. The adjoint method is automatically selected.
Avoidance: Make sure all three of the above conditions are not satisfied
simultaneously. This can be done by applying a small amount of material
damping to the design element.
Or insert param,cdif,yes in the BDF section
or apply the following alter:
compile pslgdv list
alter 'emg,'
type parm,nddl,i,n,zuzri1 $
zuzri1 = nok4gg
compile respsen list
alter 'EMG ',''
type parm,,i,n,nok4gg $
nok4gg = zuzri1 $
1-10509309
2004
Virtual Mass - MFLUID - Results are not i
ndependent of element's grid ordering
Eigenvalues results on elements wetted on both sides with virtual mass, such as
a baffle, are not independent of the grid numbering. That is slightly
different results may be obtained when an element is numbered 1, 2, 3, 4 versus
4, 3, 2, 1.
Results are not expected to vary by more than 10 percent.
Avoidance: Change the direction of the element normals of two sided elements,
rerun and average the eigenvalue results.
1-10515201
M 307 (IFPDRV)
2004
Miscellaneous - Preceding blank causes UF
MSC.Nastran 2001.0.9 for Nec Linux IA-64 may issue the following user fatal
message if a blank precedes a bulk data etnry:
ILLEGAL NAME FOR BULK DATA ENTRY RRDD
Avoidance: Remove the blank
1-10523001
Post Processing - PARAM,POST - Incorrect von Mises Stress cal
culated in Patran for plane strain
When using plane strain elements in MSC.Nastran sol 101, the von Mises stress
is calculated properly in Nastran, but Nastran does NOT store the Stress ZZ
component to the .op2 or .xbd and therefore Patran will show a wrong von Mises
stress because it calculates von Mises stress from a tensor with SZZ=0.
SOL 101 must be changed to be similar to SOL 106 so that it outputs the
sigma_zz for plane strain elements to the .xdb and .op2.
1-10539915
2004
6 in subDMAP PSLGVD for datablock GTBMN
If a solution 200 input contains both MFREQ (or DFREQ) and MTRAN analyses and
rigid element sensitivity for damping elements then USER FATAL MESSAGE 1126
(PSLGVD) will occur.
Avoidance: Add OVRWRT permission for datablock GTBMN
COMPILE PSLGDV LIST
ALTER 'FILE.*OVRWRT'
FILE GTBMN=OVRWRT/GTk4MN=OVRWRT $
1-10567705
and NT
2004
ESE - GPFDR - Traceback in GPFDR on HP-UX
MSC.Nastran 2001 may fail in the GPFDR module with a traceback (floating point
overflow) or a "Signal 8 error" on HP-UX and NT systems.
Avoidance:
Removing the rigid body modes may allow the job to run.
1-10603004
2004
r=yes causes UFM 477
File Management Section - DBLOCATE and sc
DBLOCATE restarts, like tpl test problem adb144r1, can not be run with scr=yes
else UFM 477 (GPFILX) will be encountered.
1-10618104
2004
Missing Output
Heat Transfer Analysis - PARAM,OMID,YES -
When using PARAM,OMID,YES in a heat transfer analysis consisting of plate

elements, the heat flux results are not output.
Avoidance: Do not use PARAM,OMID.
1-10636201
2005.0.2
nd 5 compute in single precision
DMAP - VECPLOT module options -1,1,2,3, a
VECPLOT module options -1,1,2,3, and 5 compute in single precision. Also

VECPLOT option -1 produces an output which is unprintable and causes a fatal
error when attempting to read or print the file.
1-10642607
2004
rong GE in PUNCH File
Optimization/Design Sensitivity - PBUSH W
In SOL 200, Analysis=MFREQ, the updated property cards in the punch file for
PBUSH are wrong for GE.
If a GE property was not updated, the value will be missing.
If a GE property was updated 0.0000 will be placed in the field where "GE"
belongs: Examples:
PBUSH*
*
*
*
PBUSH*
*
*
*
*
*
1501
K
1.46886547E+05 1.00000000E+06
RCV
1.00000000E+00 1.00000000E+00
1601
K
9.75584219E+04 1.00000000E+06
0.00000000E+00
RCV
1.00000000E+00 1.00000000E+00
1-10642623
2004
UWM 2070, Wrong Answers
2.00000000E+04 2.00000000E+04*
1.00000000E+06 1.00000000E+06*
1.00000000E+00 1.00000000E+00*
2.00000000E+04 2.00000000E+04*
1.00000000E+06 1.00000000E+06*
1.45218134E-01
*
*
1.00000000E+00 1.00000000E+00*
Optimization/Design Sensitivity - DMIG -
A sol 200 run with K2GG/M2GG (i.e. K2GG=KAAX1,KAAX2) will omit the X2GG
matrices in the final analysis. UWM 2070 will be printed:
*** USER WARNING MESSAGE 2070 (MTRXIN)
REQUESTED DMIG MATRIX KAAX1 IS UNDEFINED.
The GPWG table will be wrong and the final answers wrong.
Contact MSC Support for DMAP resolution.
(see attachments)
1-10647823
2004
Buckling - QUAD4, PARAM,SNORM - Traceback
A buckling analyis with quad4 elements and param,snorm may fail with a
floating point overflow in routine eqtxd.
Avoidance: Other than not specify param,snorm there is no avoidance.
1-10659704
2005
NER) - Wrong Answers
Elements - TEMP(LOAD), ZOFFS, STRESS(COR
In Version 2001.0.7 and 2001.0.9 corner stresses for quad4 and tria3 elements
are incorrect when temperature loads are applied and zoff are present.
Avoidance: There is no avoidance other than using the cetroidal stress.
Use the CUBIC or SGAGE option to obtain correct stresses .
1-10675401
2004
DBC/Plotting - Missing Output in xdb
In MSC.Nastran V2001.0.5 - V2001.0.9 data may be missing from the xdb. The
problem is dependent upon the number of datablocks written to the xdb. The
number of datablocks written is influenced by the number of data recovery
requests (i.e. STRESS, ELFORCE, GPSTRESS, DISP ...), the number of subcases,
and the number of different element types.
Avoidance: Reducing the number of subcases or performing data recovery of
different types in separate runs may resolve the problem.
1-10684101
2004
Rigid Elements - RSSCON, SNORM - Poor res
ults if solid element edge is not aligned with shell normal
The RSSCON connector element is used to connect solid and shell elements. If
the edge of the solid element is not aligned with the local shell normal, bad
answers may occur.
Avoidance: Use the SNORM bulk data entry for the shell point, with the vector
pointing along the solid element edge.
1-10687517
2005
ield View Factor Punch File
Heat Transfer - Format Error in a Large F
Large field view factor punch files may contain an incorrect extra line.
1-10695147
2004
GPFORCE - CELASi - Wrong Answers
If a model only contains scalar elements such as celasi then wrong GPFORCE
results may be produced.
Avoidance; Add a dummy quad4 element
1-10723901
SFM 3007
2004
Optimization/Design Senstivity - DRESP2 -
The fatal error:

SYSTEM FATAL MESSAGE 3007 ILLEGAL INPUT TO SUBROUTINE 911
is produced in optimization when there are multiple subcases that include a
frequency response and/or transient response as well as a statics/normal modes
subcases that contain dresp2's that reference dresp2's and the dynamic response
subcases do not.
Avoidance: Insert the following dmap alter
compile descon
alter 'maxrg'(3,-1),'rr2idi'(3)
append RSP2R,/RSP2Ri/2 $
paraml rr2idr//'trailer'/1/s,n,maxr//s,n,norr2id $
if ( norr2id>-1) then $
maxrg = maxrg + maxr
append RR2IDR,/RR2IDi/2 $
endif $
1-10725608
2004
65 CBUSH INVALID INDEX
Plotting/DBC - CBUSH, PARAM,POST - SWM 60
When PARAM,POST,0 is set to create an xdb and the input file has cbush elements
that only reference one grid then a message similar to the following will be
issued:
4 FROM SUBROUTINE CBUSH
ELEMENT
901 GRID POSITION
2 CONTAINS AN INVALID INTERNAL
INDEX.
1-10741302
2004
, FREQi - UFM 2109 (DPD)
Optimization/Design Sensitivity - SUPORT1
The message:
USER FATAL MESSAGE 2109 (DPD) NO GRID, SCALAR OR EXTRA POINT DEFINED.
can occur in a SOL 200 optimization run when:
a. There are multiple analysis types
b. A frequency response subcase has a SUPORT1 command and a different boundary
condition than the other analyses
c. FREQ3,4 or 5 is used in the specification of the excitation frequencies.
COMPILE PRESENS
ALTER 'TYPE' $
TYPE PARM,NDDL,I,N,SPC,SUPORT $
ALTER 'DPD'(,-1) $
IF ( SOLAPP='DFREQ' OR SOLAPP='MFREQ') ISOLAPP = 6 $
IF ( SOLAPP='MTRAN' ) ISOLAPP = 7 $
PARAML CASERS//'DTI'/1/3 //S,N,SPC $
PARAML CASERS//'DTI'/1/255//S,N,SUPORT $
1-10741307
2004
7 (DSABO) ILLEGAL INPUT TO SUBROUTINE DSAB1K
The system fatal message:
SYSTEM FATAL MESSAGE 3007 ( DSABO)
is encountered when using the plane strain option for a pshell (MID2=-1) and a
material property for the membrane portion (MID1) is being designed.
Avoidance: Do not use the plane strain option when designing membrane material
properties for a PSHELL.
1-10768221
2004
s non-physical results
Heat trasnfer - RADBC - Coarse Mesh yield
When a RADBC entry is used in a nonlinear solution with a coarse mesh in

problems where radiation heat transfer dominates conduction, non-physical
results have been observed. For most problems where radiation is modest, no
bad results will be observed.
1-10781711
2004
UCKLE - Unexpected Results
Nonlinear Analysis - PARAM,LGDISP PARAM,B
Whenever the parameter BUCKLE is used in a nonlinear static analysis, SOL 106,
the parameter LGDISP MUST be set to +1. Otherwise, unusual and unexpected
results are obtained.
1-10816801
2004
- Meaningless print of equation ID
The print of DRESP2 information based on DOPTPRM P2 parameter being set to 8

includes the EQID information. If a FUNC has been used in the place of integer
DEQATN ID, the print shows a meaningless negative integer.
Avoidance: NO avoidance is necessary, the negative integers -1 thru -6 refer

to FUNCtions SUM, AVG,SSQ,RSS,MAX and MIN, respectively.
1-10858001
RROR
2004
Submittal - OPEN CORE MEMORY ALLOCATION E
If a Nastran job is submitted on a 32 bit Unix system that has the ability to
perform an available memory check and more than 16gb of physical memory exist,
then the job will fail. The log file will indicate:
"OPEN CORE MEMORY ALLOCATION ERROR"
Avoidance: To date this problem has only been encountered on Fujitsu
Primepower. For Primepower an updated nastran driver is available for download
at:
http://www.mscsoftware.com/support/software_updates/primepower.cfm
If a critical need exists, drivers for other machines will be made available.
1-10869409
2004
PNPFL) GRFNUM ARRAY DBC XDB
Plotting/DBC - PARAM,POST,0 - SFM 1003 (O
A second run with an ASSIGN DBC of the form:

ASSIGN DBC='filename.xdb', RECL=1024, DELETE
may issue the following DBC message:
*** SYSTEM FATAL MESSAGE 1003 (OPNPFL)
UNIT
40 DOES NOT HAVE A CORRESPONDING VALUE IN GRFNUM ARRAY.
Avoidance: Manually remove the XDB file before the 2nd run.
1-10872513
t
MFLUID - EIGRL - SFM 3034 (LNNHERR), Failed orthogonality tes
Jobs with MFLUID elements may fail in SOL 103 with the following message
indicating an orthogonality failure in lanczos.
INTERNAL FAILURE IN THE LANCZOS PROCEDURE:
M-ORTHOGONAL QR PROCEDURE FAILED TO CONVERGE. PROBABLE CAUSE:
MASS MATRIX IS INDEFINITE (MODES) OR STIFFNESS MATRIX IS INDEFINITE
(BUCKLING).
*** SYSTEM INFORMATION MESSAGE 6470 (REIGL0)
1-10874504
2004
n - Wrong Answers
Transient Analysis - SPCD, Enforced Motio
A transient analysis deck employing enforced motion via SPCD gives very
different results when run on SOL 112 and SOL 109. Further, these results do
not match the results obtained from the corresponding large mass approach runs.
Avoidance: Other than using the large mass method, there is no avoidance.
1-10893903
2004
f dscmcol data block contains errors
Aeroelastic Analysis - NDDL Description o
Three aeroelasticity related records of the dscmcol datablock are incorrectly

described in dscmcol.ddl. The correct description for these records is:
OR,81,{ Aeroelastic divergence }
SUBCASE,I,{ Subcase identification number }
undef,1,{
}
root,I,{ Root }
MACH,RS,{ Mach number }
undef,1,{
}
SEID,i,{ Superelement identification number }
OR,82,{ Aeroelastic trim }
undef,1,{
}
xid,I,{
}
undef,2,{
}
OR,83,{ Aeroelastic stability derivative }
ru,I,{ R/U }
comp,I,{ Component number }
UNDEF,1,
xid,I,{
}
This error does not have any significant impact on the user. Only a print of
the dscmcol data that contains DIVERG, STABDER, OR TRIM responses is affected.
1-10978601
Frequency Response - CBUSH, CELASi, DAMPi, ESE - Wrong ESE wi
th frequency dependent material.
The BUSH, ELASi and DAMPi elements yield incorrect ESE results when frequency
dependant materials are used. The elements primary properties are used and are
not updated.
1-10993902
2004
Inefficient Database Size
The dsad module outputs a datablock named UG1. For superlements with the
upstream superelements participating in the design task, this is simply a copy
of the solution vector. Later, the original solution vectors are used and not
the ug1 copy. For a large model, this duplication can have a significant
impact on data base size.
Avoidance: The unneeded ug1 data block can be deleted using the following dmap
alter.
compile descon
alter 'dsad'
if (dmresd<>-1) delete /ug1,,,, $
1-11005809
Wrong Answers
2004
Nonlinear Analysis - SPCD, PARAM,LANGLE -
Enforced motion of rotational degrees of freedom using spcd in SOL 106 with
PARAM.LANGLE 1 or 2 may yield no enforced rotation.
1-11014028
Rigid Elements - RBE3 - Wrong Answers when fewer than 6 dof s
pecified at REFC
Using the RBE3 with fewer than all 6 dof for REFC may produce wrong results
unless the reference grid is located at the centroid of the attached grids
listed after the WTi fields.
Avoidance: Place the reference grid at the centroid of the grid ids listed
after the WTi fields.
1-11044501
2004
is Ignored when PARAM,SNORM is used.
Elements - CQUAD4, CTRIA3 - SNORM Entry
SNORM entry is ignored if PARAM,SNORM,0 is used.

Avoidance: In Version 2001 the default for SNORM is zero so remove the
PARAM,SNORM,0. entry.
1-11065201
2004
Heat Transfer - PCONVM - Wrong Answers
Changing the FORM field on the PCONVM entry between 0, 10 and 20 should not
affect the energy balance of the HBDY output unless temperature dependent
materials exist but it does.
1-11076301
2004
Conditions, Wrong Answers
Aeroelastic Analysis - Multiple Boundary
In static aeroelastic analysis, if there are multiple boundary conditions and

externally applied loads, results for the first boundary condition are correct.
Subsequent boundary conditions will start from the applied load from the first
subcase rather than from the current subcase. Consequently, results for
subsequent boundary conditions will be in error.
Avoidance: Do not use externally applied loads in any but the first boundary
condition or apply the following dmap alter:
compile fea
alter 'nloads'(10),'nloads'(10)
nloads = 0 $
nskip1 = nskip1 + nloads $
COMPILE AESTATRS
alter 'psg','psg'
type parm,,i,n,nskipt $ applied load position in PG vector
nskipt = nskip + nskip1
MATMOD PG,,,,,/PSG,/1/NSKIPt $
compile aestat
nloads = 0 $
alter 'nskip1'(2),'nskip1'(2)
nskip1 = nskip1 + nloads $
1-11076304
2004
Aeroelastic Analysis - UFM 1126 (GNFIST)
If a solution 144 flutter analysis has two identical trim subcases, with the
second subcase having applied loads, then Nastran will fail with the following
error message:
DMAP MODULE ASG
201 NAME = UX
USER ACTION: DELETE THE DATABLOCK, OR USE FILE UX=OVRWRT

1-11144638
External Superelements - PARAM EXTOUT DMIGOP2, PARAM,RESVEC UIM 9035, No Residual Vectors
Residual vectors may not be calculated when external superelements are used
with PARAM,EXTOUT,DMIGOP2
The assembly run may not calculate the load vectors for SE 0, thus the RESVEC
modes cannot be calculated. This will lead to the message:
USER INFORMATION MESSAGE 9035 (RESVEC )
NO STATIC SHAPES WERE FOUND TO AUGMENT MODE SHAPES
Avoidance: The following dmap alter may help avoid the error:
$ INCLUDE THIS ALTER ****ONLY**** IF
$ PARAM,RESVEC,YES in residual for EXTERNAL SUPERELEMENTS
compile phase1dr,nolist,noref
alter 'selr.*notl'
message //'seid='/seid
message //'xresvec='/xresvec
message //'SELG='/selg
message //'SELr='/selr
message //'***** MODIFIED ****'
IF (SEID=0) THEN
RESVEC='YES'
XRESVEC=RESVEC
SELG=TRUE
SELR=TRUE
ELSE
RESVEC='NO'
XRESVEC=RESVEC
SELG=false
SELR=false
ENDIF
message //'seid='/seid
message //'xresvec='/xresvec
message //'SELG='/selg
message //'SELr='/selr
ENDALTER
1-11160401
2004
mes in Execution Summary
Parallel Processing - PARALLEL=n - Bad Ti
HPUX OS kernel's problem. OS kernel is patched, and hptimer.c

is also fixed. Should give good times inf f04 now. 6/26
Shared Memory Parallel executions (sparse symmetric parallel decomp) on hpux
puts bad times in the f04 execution summary.
Avoidance: Other than using the times from the log file there is no avoidance.
1-11167802
2004
Invalid Charachters in punch file
Optimization/Design Sensitivity - PWELD -
SOL 200 with CWELD elements may write a punch file for the PWELD entry with
invalid charachters which if read into nastran will cause the job to abort.
PWELD*
*
501
CLAM
11 3.62326217E+00
OFF
FF *
RIGI*
SPOT
>L
Job aborting...
Allocating 0x06400000 ( 104857600) words
Signal caught, signal=11 job aborting
Address Error caught, errno=0
Address Error caught, errno=0
Command exited with non-zero status 1
1-11208609
EC 3021
2004
Case Control - SUBCOM, SUBSEQ - SFM 4276
Some machines may fail with SYSTEM FATAL MESSAGE 4276, EC 3021 if a SUBCOM
contains a SUBSEQ entry with a 0.0 coefficient.
SUBCOM 1001
LABEL = COMB 1.2*SC2 + 1.1*SC3
SUBSEQ = 0.00,1.20,1.10,0.00
Avoidance: Instead of 0.00 use a very small coefficient.
1-11221204
Optim - MODTRAK - FREQ3/4/5 - UFM 9068
If MODTRAK and FREQ3/4/5 are used in the same analysis (sol200), the job may
fail with the following error message:
USER
^^^
FATAL MESSAGE 9068 (PRESENS)

NO DRESPI ENTRIES EXIST FOR DESOBJ ID=
Avoidance: Disable FREQ3/4/5 or MODTRAK

1-11269001
2004
- Wrong MPC Forces
Frequency Response - SPCD Enforced Motion
At very low frequencies, a SOL 111 deck with modal damping using the SPCD
enforced motion approach gives MPC forces that are not in agreement with the
results from a corresponding deck using the large mass approach.
1-11282401
.2 - UFM 1126
2004
Nonlinear Statics - SOL 106; PARAM,BUCKLE
A nonlinear buckling analysis with param,buckle,2 terminates with USER FATAL

MESSAGE 1126 (GNFIST) if scr=no is specified.
Avoidance: Use scratch=yes or insert the following DMAP alter:
compile nlstatic
alter 'call moders'(,-1)
delete /blama,bpha,blama1,, $
dbdelete datablk=(bug,bqg,bqmg) where(wildcard) $
endalter
1-11299919
2005
not work, Unexpected Answers
Heat Transfer - RADLST - System(87) does
Nastran SYSTEM(87)=3 is intended to specify that no radiation energy is lost to

space when there is an open enclosure; however, this system cell setting is
ignored.
1-11336904
2008.0.0 (MD R3)
Buckling - EIGRL - SFM 7340
Lanczos may have trouble with some buckling problems and the jobs may fail
with SYSTEM FATAL MESSAGE 7340.
Avoidances: This problem is known to exist if more modes are requested than
exist in the structure. The problem may be caused by modelling errors such as
a massless mechanism but if the model has been verified other possible
avoidances include specifying system(273)=1, changing the frequency range of
interest or simply specifying ND, changing the maxset on the eigrl entry,
reversing the load and searching the positive range instead of the negative
range.
1-11340943
as an error
Documentation - Figure 4-35(a) in Linear Static Users Guide h
See figure 4-35 titled Force, Moments, and Stresses in Plate Elements,
specifically the (a) figure for Forces in the Linear Statics Users Guide PDF
version. The Fxy arrow at the top of the figure is in the wrong direction. It
shows pointing to the readers left and it should point to the readers right.
The correct figure is shown in the Reference Manual, Figure 3-30 Forces in
Shell Elements PDF version.
1-11353051
nswers
2004
Loads - PLOAD4 - Incorrect Loads, Wrong A
The PLOAD4 entry produces incorrect loads on warped CHEXA elements.
1-11399523
2005.0.2
Documentation/QRG - CQUAD4, GEOMCHECK
The QRG description of the taper ratio calculation is in error. The quad4
taper ratio calculations are designed to produce taper ratio factors between
0.0 (indicating square/rectangular) and 1.0 (indicating pure triangular). The
calculations are performed correctly. However, the discussion in the QRG fails
to mention the fact that the taper ratio includes the subtraction of 1.0 to
bring the ratio into the 0.0 to 1.0 range. The QRG discussion of the
GEOMCHECK Executive Control Statement Remark 2 taper ratio calculation
description (4th bullet) should be modified to state:
... is defined to be the absolute value of (the ratio of the area of the
triangle formed
at each corner grid point to one half of the area of the quadrilateral - 1.0).
1-11444506
2006
Insufficient Core
Large Models - DECOMP - UFM 6136 (DFMM),
When running a large model with solid elements, the job has been observed to
fail with the following messages even though the memory provided should be
sufficient to run the job using spill logic:
*** USER FATAL MESSAGE 6136 (DFMN)
USER ACTION: INCREASE CORE BY AN ESTIMATED
163986 K WORDS.
WARNING: THE ABOVE NUMBER IS ONLY AN ESTIMATE, THE ACTUAL CORE SIZE NEEDED
MAY BE HIGHER.
0FATAL ERROR
1. Increase the buffsize to 65537

2. Use the iterative solver and ipad=1
1-11444522
ut
2004
Optimization - DSCREEN,TRS - Missing Outp
The TRS value on the DSCREEN entry is ignored with RTYPE=FREQ. This may lead
to missing response output.
Avoidance: Use RTYPE=EIGN instead
1-11457306
d left blank
2005.5
Documentation/QRG - SPCD - Component fiel
A blank or 0 in the component field of the SPCD entry is treated the same as a
1.
1-11532104
Nonlinear Transient Analysis - CGAP, CELAS2 - Wrong Answers
Replacing the SPCs on the degrees of freedom on the fixed end of a CGAP element
caused a nonlinear transient analysis to yield a 0.0 solution.
Avoidance: Replace the two CELAS2 elements with a CBUSH and PBUSH element.
1-11535301
2004
Spotwelds - CWELD - No Message
If the area of the elements that the cweld connects to is too small, the job
may stop and messages are issued.
It's normal for an ill-conditioned model to fail in DCMP because of bad
stiffness matrix.
1-11540701
rly Formatted
2004
Aeroelastic Analysis - UFM 5264 Not Prope
USER FATAL MESSAGE 5264 (ASGLAB) is not properly formatted and will not
correctly identify the incorrect entries.
1-11542601
PVTS
2004
Superelements - EXTSEOUT - UFM 1126 with
An assembly using an external SE created using the EXTSEOUT Case Control

command and specified via the SEBULK entry fails with UFM 1126 (GNFIST) in the
IFP module if the assembly data includes partitioned Bulk Data for the external
SE with one or more parameters in it.
compile rdsebulk
alter 1
dbview ibulkx=ibulk where (peid=temp) $
alter 'if ( dbname=',''
dbstatus ibulkx//s,n,noibulk $
if ( dbname='geom1x' and noibulk<1 ) then $
alter 'if ( noxgeom1'(,-1),''(,0)
dbstatus xgeom1,ibulkx//s,n,noxgeom1/s,n,noibulk $
if ( noxgeom1>0 and noibulk<1 ) then $
endalter
1-11542604
0
2004
Superelements - EXTSEOUT, GPSP - UWM 450
If an external SE created from using the new EXTSEOUT feature is actually the
residual of a superelement tree, the assembly run using this external SE fails
to recognize the matrices associated with it. This will lead to a fatal
message. A likely fatal message is:
*** USER WARNING MESSAGE 4500 (GPSP)
STIFFNESS MATRIX PURGED, GRID POINT SINGULARITY NOT TESTED
Avoidance: Use the following alters in the external SE creation run to avoid
the above problem:
compile phase0
alter 'ENDIF \$ END CHECK' $
paraml cases//'dti'/1/378//s,n,extseout $
1-11548004
2004
d ASET/ASET1 Bulk Data entries.
ACMS - ACMS does not permit user-specifie
The ACMS capability does not permit user-specified ASET/ASET1 Bulk Data
entries. It is important to remove this severe restriction in order to allow
the new external SE creation feature which employs the EXTSEOUT Case Control
command to work with ACMS inputs.
1-11577404
2004
DMAP - ADD - Traceback
If the ADD module divides one matrix by another, and the denominator has packed
zeros a fatal error in the ADD module occurs followed by a traceback:
Traceback:
Offset
Offset
Offset
Offset
Offset
Offset
Offset
0x00001680
0x00000d84
0x00000700
0x00000098
0x00000140
0x0000005c
0x000009ac
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
bldpk_
add_
dadd_
xsem07_
xsemdr_
nastmon_
mainal
Avoidance: An avoidance for v2004 is to first run the denominator matrix

through matmod(39), which removes packed zeros.
1-11588604
1 (DOPFS)
2004
The error:
*** SYSTEM FATAL MESSAGE 3001 (DOPFS)
THE INPUT DATA BLOCK NAMED DESELM
AT POSITION
3 DOES NOT EXIST.
is caused by having a fully stressed design optimisation (FSDMAX>0) when there

are no designed elements. (No DVPRELS relating shell thickness or rod area to
DESVARs)
Avoidance: Remove the FSDMAX parameter or add designed properties related to
rod areas or shell thicknesses.
1-11600601
2004
Acoustic Analsyis/ACMS - UFM 3200 (SEQP)
Acoustic Analysis in ACMS may lead to the following fatal message:

*** USER FATAL MESSAGE 3200 (SEQP)
LOGIC ERROR DETECTED BY SUBROUTINEFM2ERFN 4 = LOCATE CODE OR VALUE.
0FATAL ERROR
Avoidance: There is no avoidannce.
1-11604109
rong Answers
2004
Nonlinear Transient Analysis - NOLIN2 - W
A SOL 129 nonlinear transient analysis with NOLIN2 entries may yield different
results depedning on the order of the input file.
1-11624727
2004
EKE output not supported
Complex Eigenvalue Analysis - EIGC - ESE,
As noted in the documentation, ESE and EKE are not output in Version 2001 for
SOL 107 and 110.
Avoidance:
This limitation can be avoided with a DMAP alter.
To obtain the ESE for SOL 107 or 110 the following alter is required.
compile sedrcvr souin=mscsou noref nolist
alter 'if.*gpfdr.*statics','' (1,0) $
IF ( GPFDR AND (STATICS OR APP='REIG' OR
APP='CEIGEN' OR APP1='FREQRESP') ) THEN $
alter 'if.*gpfdr.*statics'(2,0),''(2,0) $
IF ( GPFDR AND (STATICS OR APP='REIG' OR
APP='CEIGEN' OR APP1='FREQRESP') ) THEN $
1-11648005
2004
Parallel - DMP, OUTPUT2, ASCII, RCOUT2 -
When using DMP with formatted output2 request, depending on the number of CPUs
and memory request, the job may fail with one of the following error messages
when using RCOUT2 to convert the output2 file back to binary format:
*** SYSTEM FATAL MESSAGE RC0005 (RCOUT2)
ILLEGAL KEY VALUE DETECTED
USER INFORMATION:
EXPECTED KEY VALUE:
2
DETECTED KEY VALUE:
2000
FATAL ERROR CODE - INVALKEY 0002
*** SYSTEM FATAL MESSAGE RC0007 (RCOUT2)
INSUFFICIENT MEMORY AVAILABLE TO READ IN A FORTRAN LOGICAL RECORD
USER INFORMATION:
AVAILABLE SPACE IS
100000 WORDS.
REQUIRED SPACE IS
969070159 WORDS.
USER ACTION:
INCREASE PARAMETER 'LOPCOR' IN ROUTINE RCOUT2 AND REBUILD RCOUT2
EXECUTABLE.
FATAL ERROR CODE - INSUFFCORE
Avoidances: There are 2 possible avoidances.
1. Run the job in serial mode.

2. Reduce the number of cpu and memory request
The problem appears to be caused by a corruption of the RCOUT2 file when run in
DMP mode because the slave tasks are opening the .op2 file. The fix is to
suppress automatic opening of FORTRAN files when running in DMP slave tasks.
John Saunders.
1-11651704
2004
e gradient output
Heat Transfer - CHBDYI - Extra temperatur
MSC.Nastran generates extra temperature gradients and fluxes output for CHBDYi
elements, which should have heat flow output only.
Avoidance: Inser the following alter:
compile sedrcvr
alter 'IF ( (GETSYS(NH,56)',''
IF ( (GETSYS(NH,56)<>0) ) THEN $
endalter
1-11679124
2004
D), Wrong Answers
Frequency Response - DAREA - UWM 2075 (DP
In SOL 111, frequency response, if a DAREA entry references a nonexistant GRID

then the following message may be encountered and wrong answers may results.
*** USER WARNING MESSAGE 2075 (DPD)
EIGR ENTRY SET ID =
66 HAS UNDEFINED GRID OR SCALAR POINT
1005
Avoidance: Correct the DAREA entry to reference an existing grid point.

1-11700650
2004
Static Analysis - DEFORM - UWM 9058
If an analysis has two subcases and one of them has a DEFORM load and the SPC
ID does match the other subcase, the analysis will not run. There is no FATAL
message, only WARNING MESSAGE 9058; that indicates no loads in the residual
structure.
1-11725405
2005
Documentation/QRG - CBUSH - Remark 10 ref
erences Remark 2 instead of Remark 3.
Remark 10 of the CBUSH entry in the Quick Reference Guide says "When CID >= 0,
the element x-axis is set as in Remark 2..."
This should be changed to specify Remark 3 instead of remark 2. I.E. Change the
statement to "When CID >= 0, the element x-axis is set as in Remark 3..."
Also, the definitions on the TKIDi, TBIDi and TKNIDi fields on the PBUSHT can
use some extra clarification. A statement should be added indicating that the
data input corresponds to directions 1 through 6. For example, the TKIDi field
is defined as follows: "Identification number of a TABLEDi entry that defines
the stiffness vs. frequency relationship." This should be clarified to say:
"Identification number of a TABLEDi entry that defines the stiffness vs.
frequency relationship in directions 1 through 6."
1-11748419
Output
Nonlinear Output - NLPARM, INTOUT=NO, PARAM BUCKLE 2 - Extra
When using PARAM BUCKLE 2, even though the NLPARM entry requests NO for INTOUT
on the NLPARM entry, intermediate output will occur. The buckling mode plus
all the intermediate increments are output. Only the first increment is not
output.
1-11788602
utput
2004
Case Control/XYPLOT - MPFORCE - Missing O
The MPCFORCE psdf output is not created when requested using the xyplot,
xypeak, or xypunch option.
Avoidance: Add the mpcforce=n case control command.
1-11794410
Optimization/Design Sensitivity - PARAM EIGD with DVPREL and
DVMREL - UFM 6920 (MATMOD)
IF PARAM,EIGD,YES is set and property plus material sensitivities are
requested, the subdmap EIGVECDS will fail with the message:
SYSTEM FATAL MESSAGE 6920 (MATMOD)
The problem occurs because the DMAP logic in EIGVECDS has DVSG1 for DKPHI and
DVSG1 for DMPHI, then the variables are wrong for MATMOD.
Avoidance: Use ONLY property OR material sensitivity in one run. Results for
both cases can be combined externally
1-11794426
2004
Elements - QUAD4, TRIA3, FORCE(BILIN,CUBI
C) - Wrong moment forces when SNORM=0.
The FORCE(CUBIC) and FORCE(BILIN) data recovery options may produce incorrect
moment forces for models when SNORM=0..
Avoidance: Use the SGAGE option.
1-11794442
1305
2004.0.3
Nonlinear Analysis - RFORCE - SFM 4276 EC
In nonlinear analysis with follower forces, module EMAKFR fails to recognize

that there can be more that one RFORCE entry referenced to a single grid point.
If this condition exists the run will fail with SYSTEM FATAL MESSAGE 4276
ERROR CODE 1305 ENDPUT2.
Avoidance: Adding param,followk,no avoids the fatal message but also turns off
follower forces which will affect results. RFORCE entries must otherwise be
combined so that there is only one entry per grid point.
1-11805508
UMRGE1)
2004
Transient Analysis - GPFORCE - SFM 6143 (
The message:
SYSTEM FATAL MESSAGE 6143 (UMRGE1)
incompatible size of ISS matrix
is output in a SOL 109 Direct Transient with static preload when there is a
GPFORCE request ABOVE the subcase level and a change in SPC set size between
subcases.
Avoidance: Error may be avoided by putting the GPFORCE request in the static
preload subcase ONLY.

1-11859503
3007 (SEP1X)
Distributed Memory Parallel - BSET, CSET - Poor Message, SFM
If bset and/or cset entries are used with GDMODES the the following fatal
message that does not indicate the problem is issued:
SYSTEM FATAL MESSAGE 3007 (sep1x) - illegal input to subroutine sepomt
Avoidance: GDMODES does not support BSET, CSET or ASET entries.
1-11867901
2004
DMAP - PARAML - Poor Diagnostics
If the the value for the column index (p2) is set to a number larger than the
number of columns in the input matrix the following system fatal exit takes
place.
SYSTEM FATAL MESSAGE 4276 (UNPACK) ERROR CODE
31 PID=
The .f04 file shows that the program ends with the statement "UNPACK TERM".
It is not evident which module makes this .f04 entry. This makes it difficult
to debug the user error.
1-11909101
2004
- Wrong Answers
Superelement Analysis - PARAM,FOLLOWK,YES
Superelement analysis with follower forces (param,followk,yes) can lose

follower stiffness if a follower grid specified load such as a force1 is
associated with an external grid. This contribution is not currently computed
in SEKDR if no physical structure is downstream.
compile sekdr
alter 'IF ( NOKDJJ=',''
IF ( NOKDJJ=-1 ) THEN $
alter 'EMG
ESTx'(,-1)
if ( nogpect>0 ) then $
alter 'EMG
ESTx'(,2)
else $
equivx kfgg/kdjj/-1 $
endif $ nogpect>0
endalter
1-11917502
Frequency Response - Freq. Dep CBUSH, Enforced Motion, SPCD
- UFM 5423 (CFORCE2)
In SOL 108, frequency response, if the model contains frequency dependent CBUSH
elements and the excitation is direct enforced motion defined in the time
domain using TLOAD entries and results are requested in the time domain using
the TSTEP entry, SOL 108 usies the Fourier Transform Method but the data
recovery will fail and the following fatal message will be issued from the
CFORCE2 module:
USER FATAL MESSAGE 5423 (SADD5)
COLS ROWS FORM TYPE NZWD
DENS
TRAILER FOR QGX
833
IS
501
12
TRAILER FOR QSGF
IS
101
12
825
Avoidance: Insert the following DMAP alter in V2007/MDR2 or earlier:
compile sedfreq
alter 'IFT
udF'
IFT
qsgf,CASES,TRL,FOL/
qsgft,TOLx/IFTM $
delete /qsgf,,,, $
DSAR
qsgft,,,/qsgf,,,,/-1 $
and for V2008/MDR3:
compile sedfreq
alter 'IFT
PPF'
IFT
qsgf,CASES,TRL,FOL/
qsgft,TOLx/IFTM/false $
equivx qsgft/qsgf/-1 $
endalter
1-11943904
2004
rmat Error in Table
Direct Frequency Response - iter=yes - Fo
The iterative solver frequency summary table prints ***** for frequencies
greater than 999. 999.
1-11974803
2004
Wrong Answers with many subcases
Grid Point Force - GPFORCE, TEMP(LOAD) -
SOL 101 may generate wrong translational results in the grid point force
balance when more than 9 subcases exists with temp(load).
Avoidance: Duplicate the GPFO set and alternate in Case Control GPFO set
assignments between duplicated set every nine subcases.
1-11979905
2004
ng Data Recovery Output
External Superelements - EXTSEOUT - Missi
An assembly superelement run employing an external SE created using the

EXTSEOUT feature may fail to give data recovery output for the residual. See
also quality 1-12962601.
1-11981265
2004.5
Nonlinear Analysis - CTETRA(10) Yields Wr
ong Nonlinear Stress Output at grid points
The nonlinear TETRA(10) element does not extrapolate the Gauss point stresses
to the grid points correctly. In one analysis the nonlinear equivalent stress
output for a plastic analysis with TETRA(10) elements exceeded the yield stress
value at grid points but the same analysis with HEXA(8) elements did not exceed
the yield stress.
1-11989101
2004
Insufficient Memory
The DOT optimizer may overestimate the memory allocation for an optimization
job with the presence of DLINK entries due to a wrong variable reference. This
bug will not affect any result accuracy.
Avoidance: Request more memory.

1-12017009
2004
TSUB - Wrong Answers
Differential Stiffness/Superelements, STA
If superelements are present in a buckling analysis, or a dynamic analysis with

differential stiffness, and data recovery is not requested for all
superelements then wrong answers will be computed.
Avoidance: Make sure data recovery is requested for all superelements or
compile super3
alter 'dropt=3'
if ( app='bkl0' ) cntl='all' $
endalter
Bob Harder 10/25/05: I have studied the change made for Quality 1-12017009
and believe it is correct. The case I studied used a SEDR command for only the
residual structure. Using Version 2001 with SEDR=[residual], no displacements
were recovered for the upstream superelements, and hence no differential
stiffness. Without the SEDR command, this Quality fix caused no change. This
means that the SEDR=[residual] command used to eliminate the differential
stiffness from upstream superelements, but it no longer does. If someone is
doing a trick that requires no differential stiffness for upstream
superelements, then he should use an ALTER.
COMPILE SEKDR $
ALTER 'NOKDJJ=-1','' $
IF (NOKDJJ=-1 AND SEID=0 ) THEN $
1-12018401
low
2004
Parallel Processing - DMP - Integer Overf
During wrapup of a DMP analysis, jobs may fail with an integer overflow. This
may occur for large jobs that perform large amounts of message passing. It
occurs while computing message passing statistics. It does not affect the
results of the analysis.
1-12029513
T)
2004
Utilities - TRANS/RECEIVE - SIM T2 (CVTGE
If an xdb from a Windows V70.7 system is trans'd and received to a V2001 Unix
system the following message may occur:
*** SYSTEM INFORMATION MESSAGE T2 (CVTGET)
ERROR IN TRANSLATING DATA. CHARACTER = '
SUPERS
1
0
0
0
0
'
**** SYSTEM INFORMATION MESSAGE T1 (CVTEND)

1 ERRORS OCCURED DURING TRANSMISSION PROCESS
Avoidance: Use ascii ftp on the file before receiving
1-12029522
2004
R DDL and Data Base
Utilities - DDLADD, V70.7 xdb, Object CBA
ddladd may not work correctly for models with CBAR, CBEAM, CGAP, CBEND, and or
CBUSH elements between Version 70.7 and 2001.
See the MSC.Nastran 2004
Release Guide for the ddladd fix.
1-12055302
Optimization/Design Sensitivity - Dynamic loads in Supereleme
nts - Wrong answers or UFM 3046
If dynamic loads are applied to the interior points of superelements without
the use of the LOADSET Case Control command and LSEQ Bulk Data entries, then
the loads will be ignored or UFM 3046 will be issued in SQFREQ or SFM 3001 in
TRD2.
Avoidance: Respecify dynamic loads with LOADSET and LSEQ or insert the
compile presens
alter 'lcgen ',''
type parm,,char8,n,appx='reig' $
LCGEN
CASES,SLTx,ETTx,dynamic0,geom4s/CASESX//appx $
endalter
1-12061001
2008.0.0 (MD R3)
irst root is positive
Buckling - EIGRL - Uses bad shift when f
When f1 on the eigrl entry is blank, the Lanczos buckling solution computes a
good estimate of the first root prior to the Lanczos solution. If the root is
positive it discards it, and uses 1.0 as a first shift instead .
Avoidance: Change the sign of the loads to obtain a negative first root.
1-12072604
Bus Error
2004
Eigenvalue Analysis - IRIX 64 - Signal 10
The IRIX64 patch to correct Lanczos error 1-5821710, available for downloaded
from:
www.mscsoftware.com/support/software_updates
Requires that
setenv FORMAT_TYPE_CHECKING RELAXED
be set in nast2001t2.lcl or the .cshrc file else
Job aborting...
will be encountered. The system may also require new libftn.so, libfortran.so,
and libffio depending on the o/s. level.
1-12083006
6
2004
The following USER FATAL MESSAGE can occur in a job with fully stressed design
(FSDMAX>0) and the P2=16 print option is active.
DMAP MODULE WEIGHT IS ATTEMPTING TO OUTPUT DATABLOCK WMID WHICH ALREADY EXIST
Avoidance: Include the following DMAP alter
compile desopt
alter 'casdsn,casadj','casdsn,casadj'
dbdelete datablk=(r1val,r1tabr,r1valr,drstbl, RQATABR,
casdsn,casadj,wmid) ,
where(solapp=* and seid=*) $
1-12104806
2004
oor Performance
Acoustic Analysis - PARAM,MECHFIX,YES - P
Specifying PARAM,MECHFIX,YES in conjunction with acoustics (fluid-structure

interaction) results in SWM 3081. Results are unaffected but performance may
be slightly degraded.
compile xread
alter 'Equivx mxx\/mxx2'
equivx vaxf/vspc/-1 $
alter 'partn mxx,vspc,\/mxx2'
dbstatus vaxf//s,n,novaxf $
if ( novaxf>0 ) then $
partn vaxf,,vspc/vx,,,/1 $
equivx vx/vspc/-1 $
endif $
endalter
1-12122861
BSH)
2004
Documentation/QRG - CBUSH - UFM 6629 (TA1
The following remark should be added to the QRG description of the CBUSH entry:
If the distance betwen GA and GB is less than .0001, or if GB is blank, then CD
must be specified.
1-12122896
g Answers
2004
Grid Point Force - GPFORCE, CELAS2 - Wron
In Version 2001 wrong answers for grid point force output may occur when a
CELAS2 element connects components of the same grid. A symptom of the error is
repeasted a repeated element ID in the GPFORCE output. An example of a CELAS2
entry that causes this error is:
celas2,123,55.0,101,1,101,5
Avoidance: There is no avoidance. Version 70.7 gives correct answers.
1-12142116
6059
2004
Utilities - DDLADD, SFM 1001 (BLKRD), SFM
In rare cases the ddladd utility may fail with the message:
*** SYSTEM FATAL MESSAGE 1001 (BLKRD)
ERROR ENCOUNTERED READING BLOCK 758197808, ERROR CODE = 6007.
DATA BASE NUMBER = 1, UNIT = 40, MESSAGE IS -Read block number beyond End-of-file.
0*** SYSTEM FATAL MESSAGE 6059 (DIOMSG)
NO ERROR MESSAGE EXISTS FOR DIOMSG INTERNAL CODE NUMBER
999 CALLED
FROM BLKRD
FATAL ERROR DETECTED
Avoidance: There is no avoidance other than to recreate the database.

1-12168411
2005.0.2
Case Control - SDAMP, K2PP, M2PP, B2PP Unexpected Answers, Missing UFM 9041 for SOLs 118, 146, 200
Beginning in Version 2004 changes to TF, K2PP, M2PP, B2PP and SDAMPING between
subcases in SOL 107 through 112 are supported and UFM 9041 is no longer issued.
However, these changes are still not supported in SOLs 118, 146 and 200 and
beginning in Version 2004 they are ignored and unexpected answers result. The
following fatal message should still be issued:
^^^ THERE ARE CHANGES IN K2PP, M2PP, B2PP, SDAMP, OR TFL.
^^^ USER ACTION: SPECIFY K2PP, M2PP, B2PP, SDAMP, AND TFL ABOVE ALL
SUBCASES.
Avoidance: Other than not making these changes between subcases, there is no
avoidance.
1-12205901
2004
wers on Itanium HPUX
Elements - CTETRA, TEMP(LOAD) - Wrong Ans
Models with tetra elements, thermal loads, and local coordinate systems may
yield wrong results on the in Version 2001 on Itanium HPUX computers.
1-12222802
2004
File Management Section - DBVIEW
Using the DBVIEW statement to output a datablock does not work correctly if
the WHERE clause is omitted.
Avoidance: Add the WHERE clause to the DBVIEW statement.
1-12255710
2005.0.2
rt - UWM 2071 (dpd2)
Dynamics - SPCD/RESVEC - 111 to 103 resta
A sol 111 restart to a sol 103 run will fail with ufm 5423 (mpyad) when more
than one base motions are specified using more than one RLOADi cards and when
residual vectors are requested. However the ufm is only part of the problem.
Just before the ufm uwm 2071 (dpd2) shows up indicating that the RLOADis after
the first one will be ignored.
Avoidance: Use the large mass approach
This CR is related to 1-18217901. Please refer to the avoidance schemes given
under the description of that CR.
1-12263602
2008.0.0 (MD R3)
ing Eigenvalues
Buckling Analysis - EIGRL, Lanczos - Miss
In a buckling analysis, if more than one root is requested with the ND field
and both F1 and F2 are blanks, the higher roots may not be found
Avoidance: Specify a higher ND value than desired or put in the F2 value.
1-12265515
2007.0.0
Matrix Methods - DECOMP - Insufficient Me
mory, Receiving signal number 11: Segmentation fault
Large models with insufficient memory may fail in decomp with the only message
being issued to the log file:

Avoidance: Request more memory
1-12277506
2004
Missing Output
Frequency Response - FREQ, FREQ1, FREQ2 -
In frequency response analysis if a FREQ entry exists that explicitly defines

more than 9999 frequencies or there is a combination of FREQ1 and FREQ2 entries
that define more than 9999 frequencies, than not all frequencies will be solved
for. If 12000 frequencies are defined, then only the first 2000 frequencies
will be solved.
Avoidance: Either define the frequency steps with only a freq1 or only a freq2
entry, else break the frequency steps up and solve in separate runs.
1-12301602
2004
Groundcheck - CBEND - Fails Groundcheck
The CBEND element fails the Ground check.

1-12310701
Optimization/Design Sensitivity - Superelements, DCONSTR - Mi
ssing Fatal Message
If a DCONSTR points to a response that does not exist, it is typically a User
Fatal Error. However, if the the design task includes superelements, the user
input error is not detected and the DCONSTR that points to the nonexistent
response is simply ignored.
Avoidance: There is no avoidance except to carefully check that the referenced
responses exist or to remove the superelements from the job for purposes of
checking the user input.
1-12315301
2004
Nonlinear Analysis - TEMP(BOTH) - Plane s
train analysis yields incorrect out of plane rotations
A nonlinear plane strain analysis using CQUAD4 elements, with thermal loads and
temperature dependent material properties results in out-of-plane rotations
being calculated when they should be all zero.
1-12356001
2004
DMAP - INPUTT2 - SFM
The INPUTT2 module will fatal if an attempt is made to rewind ITAPE=-3 on an

unlabeled op2 file.
1-12388901
2005.0.2
superelements - Wrong answers
Superelements - enforced motion, external
If a boundary point of an external SE created using the EXTSEOUT feature

has enforced motion specified for it in a subsequent assembly run, then its
results come out OK as part of the residual output in the assembly run, but
come out as null values as part of the external SE output.
Avoidance: Specify PARAM,SPARSEDR,NO or insert the following DMAP alter:
compile spdr1
alter 'call xAdd5 vscg0,vmcg,vadr,z01dr0,vyg'
add5
v01z,vupse,,,/zzz $
equivx zzz/v01z/-1 $
compile super3
alter 'MPYAD
ULS,UH2,\/ULS1',''
MPYAD
ULS,UH2,yls0/ULS1 $
endalter
1-12460901
ading error
Aeroelastic Analysis - Poor Trim specification leads to misle
If a user create a trim case that has more supported degrees of freedom than
controllers (URDDs, to be specific), the following error may be generated:
SYSTEM FATAL MESSAGE 3008 (UTMCOR) MODULE = ASG
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ZZXHMD
7 WORDS
PROGRAMMER INFORMATION: LOCATION KEY = PI1
0FATAL ERROR
This message does not indicate the real problem, so it is of no use to the
user.
The fix is to put in an error check to test that the number of supported
degrees of freedom equals the number of URDD controllers. This check should be
located at the begining of ASGD.
1-12484501
2004
DMAP - MATMOD option 12 - Wrong answers
MATMOD option 12 with P4<0 sets P2 incorrectly and does not produce any output
when the input matrix is full.
1-12488007
answers
2004.5
Static Analysis - PARAM,INREL,-2 - Wrong
If PARAM,INREL,-2 is specified but the model has no mass then the run
will not fail and meaningless results may be obtained.
Avoidance:
Specify mass.
1-12576102
2004
ARAM,LGDISP - Wrong SPC Forces
Nonlinear Analysis - DMIG, CGAP, CBUSH, P
When DMIGs, CGAPS and CBUSHES exist and the GRID points are defined in a local
coordinate system, a nonlinear analysis with large displacement effects may
produce incorrect SPCFORCES.
Avoidance:
Move all the grid points into the basic system
1-12576121
2004
Material Properties - Job Hangs or Crashe
s instead of issuing UFM 5456 (NMEVD)
Jobs that should issue:
*** USER FATAL MESSAGE 5456 (NMEVD)
VALUE OF YOUNG'S MODULUS (E) IS LESS THAN OR EQUAL TO ZERO.
may hang or crash on Linux machines.
The messages is not printed because it is held in the buffer.

If you set
NASTRAN system(2)=0
you will get the error message in the log file but the job still hangs.
On windows you do get the error but then the job crashes rather than exitting
cleanly.
attached example a3.bdf
1-12576159
2004
Nonlinear Analysis - Incorrect interpolat
ion of temp. dep. properties in nonlinear analysis
In nonlinear elastic analysis (NLELAST), if the stress-strain curve is only
defined in tension (the 1st Quadrant), the incorrect result may be produced to
the 1-D elements (ex, ROD) when there is compression force on the 1D elements
whose material properties are temperature dependent.
Avoidance:
1. Always define the stress-strain curve in both tension and compression, or
2. Use 2D and 3D elements, instead of 1D elements.
1-12590601
be improved
2004
Miscellaneous - TABPRT - UWM 2094 should
The TABPRT module has been enhanced to allow more datablocks to be printed if
a nddl keyword is added AND iopt3=2. The UWM is oriented towards the old
status and currently reads:
*** USER WARNING MESSAGE 2094 (TABFMT)
KEYNAME GEOM1 NOT IN LIST OF AVAILABLE KEYNAMES.
The following line should be added so that the user is aware of the new option.
SET IOPT=3 TO GET OUTPUT FROM NDDL DATA BLOCKS.
1-12600022
OD)
Optimization/Design Sensitivity - PARAM,EIGD - UFM 6920 (MATM
In Design Optimization, SOL 200, if PARAM, EIGD, YES is specified and the
number of DESVAR is greater than the number of DVPREL, then the following
messagae may be issued:
SYSTEM FATAL MESSAGE 6920 (MATMOD)
FOR MATMOD OPTION 1, THE COLUMN NUMBER X IS INVALID. IT MUST BE GREATER THAN
ZERO AND LESS THAN Y.
Avoidance: Make sure that each design variable referenced by a DVPRELi exists
1-12622905
Optimization/Design Sensitivity - STRESS(CORNER) - SUBCOM's w
ith corner stresses may fail
Corner stress output is available only if the request is made in the first
subcase. In SOL 200 with SUBCOM's it is possible that the first subcase does
not have any retained stresses so that the option is not turned on during
sensitivity analysis. This results in incorrect sensitivities and a failed
optimization task.
Avoidance: The simplest avoidance is to avoid the use of corner stresses and
subcom's. A more complex avoidance is to force the retention of a response in
the first subcase through the use of the DSCREEN entry. For example, if a
dummy FORCE response is added in the first subcase that is always satisfied,
its retention can be forced using DSCREEN, FORCE,-1000.
1-12643507
2004
Documentation/QRG - PARAM,POSTEXT
In Nastran 2001 R4, the parameter POSTEXT isn't functioning as described in the
Quick Reference Guide for POST=-2. The documentation should indicate that
setting PARAM,POSTEXT,NO suppresses output of CASECC and BGPDT only under
PARAM,POST,-1.
1-12682901
2004
e ignored or UFM 4542
Nonlinear Analysis - Load DMIG entries ar
When mutiple load dmig entries are defined in a nonlinear analysis no load is
applied.
compile nlstatic $
alter 'mtrxin','' $
type parm,,i,n,nop2j=-1 $
CALL XMTRXIN CASESX2,MATPOOLS,EQEXINS,/
P2J,,/
'P2J '/LUSETS/S,NOP2J/0/0/ERROR $
$
1-12682926
2005.0.2
n-uniform thickness - Wrong Answers
Elements - TEMP(LOAD), STRESS(CORNER), no
The BILIN corner stresses for elements with non-uniform thickness are incorrect
for versions 2001r3 onwards with temperature loads.
In 2001r1 70.7 and 70.5 the corner stresses are ok. Using SYSTEM(173)=2 in
later versions gives the incorrect results.
The centroidal stresses are ok.
1-12696201
2004
276 (GPFDR), EC 3021
GPFORCE, ESE - SUBCOM, TEMP(LOAD) - SFM 4
Some machines may fail with SYSTEM FATAL MESSAGE 4276, EC 3021 in GPFDR if a
SUBCOM contains a SUBSEQ entry with a 0.0 coefficient and thermal loads.
Avoidance: Two possible avoidances exist.
1. Use a small factor for the SUBSEQ for the Subcase containing the thermal
loading.
2. If possible in the SUBCOM, comment out the TEMP(LOAD) = entry. This is only
possible for ESE/GPFO requests.
1-12698102
for CELAS
2004
Dynamics - CELAS, PARAM,G - Wrong Answers
In dynamic analysis, CELAS elements will get incorrect force data recovery if
param,g is in the deck.
1-12705302
Nonlinear Analysis - MAT1, MATT1 - Elements that are effecti
vely linear produce plastic strain

When temperature loads and elements refering to mat1/mats1 are present in a sol
106 nonlinear analysis run, it is possible that elements which are nonlinear
with respect to temperature dependency only (mat1/matt1) produce equivalent
plastic strain.
1-12711702
088 (SELG)
Parallel Processing - DMP, PARAM,INREL - Wrong Answers, UWM 9
A static analysis with dmp and inertial relief (PARAM,INREL) may yield the
following message and incorrect results.
USER WARNING MESSAGE 9088 (SELG)
PARAM,INREL,-1 OR -2 IS PRESENT BUT NO MASS IS DEFINED. THEREFORE THE INERTIA
RELIEF LOADS WILL NOT BE COMPUTED AND THE SOLUTION WILL ONLY REFLECT THE
APPLIED LOADS.
1-12738305
FMAM)
2004.5
Distributed Memory Parallel - SFM 7796 (D
Large dmp models may fail with the following message:

DECOMP ORDERING METHOD CHOSEN: BEND, ORDERING METHOD USED: BEND
*** SYSTEM FATAL MESSAGE 7796 (DFMAM)
THE MAXIMUM INTEGER VALUE IS ABOUT TO BE EXCEEDED.
USER INFORMATION: THE MAXIMUM INTEGER NUMBER ALLOWED ON YOUR
MACHINE IS 1073741823. HOWEVER, DFMAM NEEDS TO
DO THE OPERATION NFR*(NFR+1) WHERE NFR =
34851.
USER ACTION:
USE A DIFFERENT RE-ORDERING SCHEME VIA
SYSTEM(206), OR REDUCE THE SIZE OF YOUR MODEL.
1-12742610
2004
Elements - CBUSH with identical GRIDS A &
B does not fatal, unexpected answers
If both Grid A and Grid B of a CBUSH reference the same GRID ID, then Nastran
runs and produces a grounded CBUSH element. No warning or fatal messages are
issued. This is a user error that should be trapped with a FATAL. For CELAS
elements, Nastran issues USER FATAL MESSAGE 350 when the same GRID and DOF are
referenced for both Grid A and Grid B. The CBUSH should act similarly.
1-12774307
2004.5
Postprocessing - PARAM,POST,0 - PCOMPG: x
db results not readable by MSC.Patran.
XDB results for elements that reference the PCOMPG entry are incorrect when
read into MSC.Patran. The first results layer does not even exist, and
subsequent results appear incorrect.
XDB support for PCOMPG will be added when PATRAN supports the PCOMPG property
type.
The avoidance is to use an accending identification sequence for the ply
enumeration, although this might be inconvient and restrictive.
1-12809101
2004
Postprocessing/Access - Superelements, SE
LOC, SEMPLN - MSC.Access (xdb) SCSTM not being created

The SCSTM (Substructure Transformation Matrix) is not saved correctly in the
MSC.Access (xdb) database. This is a necessary object for parts with SELOC and
SEMPLN entries. Starting with with MSC.Nastran Version 2004 it is also created
for identical or mirror superelements to properly locate the primary geometry.
1-12852017
2004
ACMODL Omitted
Acoustic Analysis - SFM 4276 EC 1044 when
An acoustic only model using the large acoustic mass for enforced motion must
contain an ACMODL entry otherwise the GP5 module will issue a SFM 4276 EC 1044.
1-12854217
2004
ncorrect plot displacements
Postprocessing/External Superelements - I
When using the xdb file to display displacement results, the results for
interior grid points of external superelements may be incorrect even though the
f06 results are correct.
1-12856910
2005.5
Postprocessing - PARAM,OUGCORD,BASIC and
PARAM,POST,-1 - Global Displacements in op2 File
Global displacements are written to the op2 file even when parameter
OUGCORD=BASIC is used for PARAM,POST,-1.
In versions 2004 and beyond this error only occurs when PARAM,SPARSEDR,NO is
also specified.
Avoidance: Specify DISP=ALL and insert the following DMAP alter:
compile sedrcvr
alter 'ELSE IF ( NOT(post=-1',''
ELSE IF ( post>-3 and
OUGCORDX='BASIC' and not(exterse and noug<1) ) THEN $
alter 'sdr2.*ougv1pat','' $
delete /ugb,,,, $
drmh1 ougv1,,,/tougv1,mougv1,,,,,,/ $
IF ( NOCSTMS>0 ) THEN $
MPYAD
TRANSG,mougv1,/UGB $
ELSE $
EQUIVX mougv1/UGB/-1 $
ENDIF $
SDR2
CASEDR,CSTMS,,,EQEXINS,,,OL1,BGPDTN,,,
UGB,,,OINT,PELSETS,VIEWTB,,,,,,/
,,OUGV1pat,,,,/APP///////ACOUT/PREFDB/-1./-1./
ADPTINDX/ADPTEXIT/FALSE $
endalter
1-12862226
2005
Documentation/QRG - param,mmfil
The QRG description of the new parameter MMFI is incomplete. The information
in the V2004 Release Guide on this parameters use needs to be transferred to
the QRG.
Avoidance: Please see the V2004 Release Guide.
1-12864001
rong Answers
2007.0.0
Virtual Mass - vmopt=2 and resvec=no - W
When vmopt=2 and resvec=no (or param,resvec,no) are both selected, the run
will produce wrong answers.
Avoidance: Do not deactivate residual vectors.
1-12872802
2004
enerate floating point overflow
Miscellaneous - NEC - Singularities may g
On NEC machines, models with near singularities that ran successfully in

Version 70.7 may generate a floating point overflow in Version 2001.
Avoidance: The problem can be avoided by setting environment variable
F_ERROPT to "250,250,2,1,2,2,2,2".
1-12893301
2008.0.0 (MD R3)
RMS, PSD - Fatal Message in dom10f
Optimization/Design Sensitivity - DESSUB,
DESSUB which includes RMS/PSD response as constraints 'must not' appear above
subcase level. If DESSUB for RMS/PSD responses appears above the subcase
level, the job may fail with a generic fatal message from dom10f.
Avodiance: Move the DESSUB command with RMS/PSD to the subcase level. Note
that this problem exists only in multiple subcase scenarios.
1-12909901
2004
Auto Q-set - UFM 4423
ACMS - A-set processing incompatible with
ACMS now allows ASETi input. In addition, TIC, CAABSF, and CBUSH/PBUSHT inputs
will cause ACMS runs to automatically generate ASET data which avoids USER
FATAL MESSAGE 4423 indicating a nonlinear elements is attached to an omitted
degree of freedom. This only works with PARAM,AUTOQSET,NO.
1-12962601
2004
ACMS - SOL 103 - Missing Output
Data recovery output may be missing in ACMS SOL 103.

1-12982305
2004.0.3
- UFM 224, NUMGT and LTOI functions
A DEQATN containing LTOI and/or NUMGT functions may fail with the following
error message:
USER FATAL MESSAGE 224 (PRERMM) MIXED MODE USAGE BY THE ARITHMETIC OPERATOR IS
INVALID DURING DEQATN EQUATION PROCESSING.
Avoidance: In the problem deck the following equations in the deqatn entry had
to be changed from;
D1 = .25 +
+
+
+
D2 = .25 +
.03125*REAL(1
.03125*REAL(1
.03125*REAL(1
.03125*REAL(1
.03125*REAL(1
+
+
+
+
+
LTOI(NUMGT(T1,.500)))
LTOI(NUMGT(T1,1.00)));
LTOI(NUMGT(TC,.500)));
to:
H1 = REAL(1 + LTOI(NUMGT(T1,.500)));
H4 = REAL(1 + LTOI(NUMGT(T1,1.00)));
HC = REAL(1 + LTOI(NUMGT(TC,.500)));
D1 = .25 + .03125*H1 + .03125*H2
+ .03125*H3 + .03125*H4;
D2 = .25 + .03125*HC;
1-13083904
2005.0.2
UAD4 - UFM 4577 (GP3C)
SSSALTER/Interactive Nastran - PLOAD4, CQ
The interactive menu in Patran 2003r2 allows the user to generate a PLOAD4 on a
2D QUAD4 structure. If no stress request is made on the loaded elements the
restart job will fail with the message:
^^^FAST RESTART MESSAGE
PLOAD4 LOAD SET =
3 REFERENCES ELEMENT ID =
42
WHICH WAS NOT FOUND AMONG TRIA3, TRIA6, QUAD4, QUAD8, HEXA, PENTA OR
HYPERELASTIC SOLID ELEMENTS IN THE PROBLEM.
0FATAL ERROR
Avoidance: Add a stress output request for one of the elements loaded by
PLOAD4.
1-13116701
Postprocessing - PARAM, POST, 0 for GDACMS requires SORT2 out
put or XY plot request
Postprocessing of ACMS output is not possible in Patran unless SORT2 is
requested or an XY plot request is made.
1-13178016
Distributed Memory Parallel - Linux - SFM 6833 (PNRBRO)
If a Linux cluster mixes nodes of MSC.Linux or RedHat Linux with SuSe Linux,
dmp jobs may fail with the following fatal message:
*** SYSTEM FATAL MESSAGE 6833 (PNRBRO)
MPI ERROR ENCOUNTERED (INTERNAL ERROR CODE IS 2759):
USER ACTION: PLEASE VERIFY THAT THE PARALLEL OPERATING ENVIRONMENT (POE) IS
WORKING CORRECTLY.
IF IT IS VERIFIED AND THIS ERROR STILL OCCURS, PLEASE CONTACT
MSC CLIENT SUPPORT.
Avoidance: Do not allow dmp to point to nodes with different operating
systems.
1-13195002
2004.0.4
in SOL 108 with Structural Damping
Acoustic Analysis - MAT10 - Wrong Answers
Acoustic analysis in SOL 108, direct frequency response, will produce wrong
answers when MAT10 entries specify GE damping.
compile gma nolist noref $
alter 'if ( acsyml','' $
if ( acsyml and (app='tranresp' or soltyp='modal') ) then $
endalter
1-13206002
2004.0.3
G), UFM 3032 (READ)
Acoustics - METHOD(FLUID) - UWM 8592 (REI
When a fluid/structure model is run in SOL 103, the user is supposed to be able
to select structure mode ouput or fluid mode output or both by including one or
both of the following case control commands in a subcase:
METHOD(STRUCTURE)=m
METHOD(FLUID)=n
But when METHOD(FLUID) is used by itself, the following error occurs:
(REIG).
Avoidance: Also include a fake METHOD(STRUCTURE) pointing to a different EIGRL
bulk data entry that only requests a single structure mode. Then ignore the
first mode output which is a structural mode.
1-13218909
2005.0.2
Postprocessing - Interactive Dynamics in
Patran fails with SFM 6357 druing full g-set data recovery.
When interactive dynamics is used in Patran and all output is selected, then
nastran will stop and issue the message:
*** SYSTEM WARNING MESSAGE 3001 (SEP1X)
2 DOES NOT EXIST.
THE INPUT DATA BLOCK NAMED GEOM2S AT POSITION
3 DOES NOT EXIST.
and
*** SYSTEM FATAL MESSAGE 6357 (SEP1A)
NO GRID POINTS FOUND
The sssalter has been corrected in Version 2005; however, enforced motion is
not supported and the alter terminates.
1-13229301
2005
Distributed Memory Parallel - DOMAINSOLVE
R, EIGRL - Poor Message, Extra Eigenvalues
If a job is run with dmp=a and the EIGRL entry has ND=b and F1 and F2 are not
specified, then (a X b) modes are found. That is b modes at each segment. If
no DOMAINSOLVER entry is specified with F1 and F2 blank and dmp= is specified,
the job may fail with the message:
11 DOES NOT EXIST.
STATEMENT
BUT NOT ON THE CORRESPONDING CALL STATEMENT.

DMP requires that F1 and F2 be specified.
lead to the message:
^^^
^^^
^^^
^^^
THIS
^^^
In Version 2005 this input will
USER FATAL MESSAGE 9139 (PHASE0)

V2 (OR F2) ON THE SELECTED EIGRL
(OR EIGR) ENTRY IS BLANK OR ZERO.
USER INFORMATION: A NON-ZERO VALUE FOR V2 (OR F2) IS REQUIRED INPUT FOR
DOMAINSOLVER OPTION.
1-13233601
2004.0.4
Elements - CGAP - UFM 2025, Coordinate Sy
stem Field not sufficiently tested in IFP
As documented in the Quick Reference Guide, the CID field of CGAP must contain
an integer or blank. However if this requirement is violated and 0.0 is
entered, the basic coordinate system is taken. In the case of a real value
bigger than zero is entered UFM 2025 will be issued indicating the coordinate
system could not be found.
1-13251205
2005
Incorrect punched pcomp entries
Solution 200
the PCOMP LAM
punched PCOMP
punched PCOMP
may produce incorrect PCOMPs entries in the punched output when

field is set to "MEM" in the original deck. The generated
entries may have a blank MEM field.
Another problem with
entries that may be encountered is Ctrl-X in the SOUT field.
Avoidance: Edit the punched outut to correct the problem pcomp entries.
1-13254103
2004
with zero coefficients leads to SFM 3001 (DOPR4)
If all the COEFi values on all the DVxREL1 entries are 0.0 and there are
non-zero C0 value, the following obscure message is produced and the run is
halted.
THE INPUT DATA BLOCK NAMED DTOS2J AT POSITION
1 DOES NOT EXIST.
Avoidance: Either eliminate the DVxREL1 entries that contain zero coefficients
or set the coefficients to a non-zero value
1-13262201
ACMS - Multiple SPCs - SFM 3001 (MCE1)
ACMS in SOL 111 with multiple SPC sets may fail with the message:
:
*** SYSTEM FATAL MESSAGE 3001 (MCE1)
THE INPUT DATA BLOCK NAMED USET1
AT POSITION
1 DOES NOT EXIST.
or it may fail with no message.
Avoidance: Insert PARAM,AUTOQSET,NO, specify dummy DELAYs for those grid

points that are experiencing a change in boundary condition, and insert the
following alter:
compile phase1dr
alter 'ENDDO \$ BCFLAG and'(,-1)
if ( seid>0 ) bcflag=false $
endalter
1-13288001
2004.0.5
DESVAR entries may not be detected
Optimization/Design Sensitivity - Missing
With the addition of the DESVAR case control command in the 2004 release, a
hole has been opened that may result in a user input error going undetected.
If all the DESVAR's referenced on a DVPREL1 or DVPREL2 entry do not exist, the
DVPREL1 or DVPREL2 is discarded on the assumption that the referenced DESVAR's
have not been selected by the DESVAR case control command. A check needs to be
inserted if the referenced DESVAR exist in the input deck and a USER FATAL
MESSAGE should be issued if they do not.
1-13314303
RTN1)
2004.0.4
Acoustic Analysis - ACMODL - SFM 6144 (PA
Acoustic analysis with fluid to structure coupling may fail with the message:
SYSTEM FATAL MESSAGE 6144 (PARTN1)
THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE.
SPECIFICALLY:
The number of rows in VAXF is not equal to the number of rows in the row
partitioning vector VAXF1
User Information: Size of input matrix and partitioning vectors:
VAXF: Rows= 4059339 by Cols=1
VAXF1: Rows= 4040027
compile mmfind1
alter 'partn
vaxw,,r',''(,1)
endalter
1-13338503
2008.0.0 (MD R3)
sing or excessive output
Superelements - SUPER, normal modes - mis
In normal modes with superelements, if SUPER=ALL is specified above all

subcases and there is a mixture of subcases with SUPER>0 and SUPER=0 commands
then output requests may be missing for some eigenvectors or unwanted output
may be generated for some eigenvectors.
Avoidance: There are 3 posssible avoidances:
1. Remove SUPER=ALL.
2. In the residual strurcture subcase, use a set id to define the residual
structure, e.g.,
set 100 = 0
super = 100
3. Create a set that contains the grids and elements for the selective SEs
and request output for all SEs
1-13341101
2004.0.3
Cyclic Symmetry Analysis - ESE - Missing
Output
Element Strain Energy (ESE) output may be missing in cyclic symmetry analysis.
1-13358901
Optimization/Design Sensitivity - UFM 1126 (GNFIST), PSD resp
onse with multiple frequency sets
The 2004 release has added two features in dynamic response optimization:
a. Support for multiple excitation frequency sets and
b. Addition of PSD values as a response type.
An attempt to use both of these features at the same time results in the
following UFM:
DMAP MODULE PARTN
202 NAME = UCV1
USER ACTION: DELETE THE DATABLOCK, OR USE FILE UCV1=OVRWRT
Avoidance:
1-13372104
parameters
Use a single excitation frequency set.

2004.0.3
DMAP - WHERE clause references undefined
A where clause in a dbview statement that references a parameter that is not

defined in the current subdmap will always be evaluated as false and no warning
message will be issued.
1-13429201
2004.0.3
Optimization/Design Sensitivity - BOX1 PB
EAML - ONE OR MORE VIOLATED CONSTRAINTS HAS A ZERO GRADIENT
If the BOX1 type of the PBEAML is designed, it is possible to encounter a fatal
error from the DOT optimizer that the gradient of a violated constraint is zero
so that no progress is possible.
The I12 property of the BOX1 section type is incorrectly treated as being
invariant with respect to the dimensions, resulting in the fatal message.
Avoidance: Possible avoidances are to use a different section type, such as BOX
or to use the PBARL rather than the PBEAML when designing the BOX1.
1-13459501
2004.0.6
Support Adams MNF
Miscellaneous - ADAMSMNF - Cray Does Not
The Cray SV1 release of MSC.Nastran 2004.0 does not support the creation of an
MSC.Adams modal neutral file (mnf). The ADAMSMNF Case Control command wwill
result in the traceback shown below:
Beginning of
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Traceback:
line 42 (address 12026636a) in routine 'TRBK'.
line 112 (address 54204c) in routine 'sysrcv'.
address 12166657a in routine 'findmemarea'.
line 4543 (address 12171173a) in routine 'removememarea'.
line 4501 (address 12171076d) in routine 'releasememory'.
line 1229 (address 12163766c) in routine 'Release_Memory'.
line 464 (address 13372526d) in routine 'MNF_CreateModeFile'.
line 575 (address 13373114c) in routine 'MNF_SetModeVec'.
line 681 (address 13254356b) in routine 'MNF_SET_MODE_SHAPE_VEC'.
line 142 (address 13231560d) in routine 'AFSCMS'.
Called from line

Called from line
Called from line
Called from line
Called from line
Called from line
Called from line
Called from line
End of Traceback.
528 (address 13202711d) in routine 'AFGMNF'.

136 (address 13201120c) in routine 'XSEM16'.
133 (address 53323d) in routine '$SEGCALL'.
133 (address 226002b) in routine 'XSEMDR'.
66 (address 62003b) in routine 'NASTMON'.
379 (address 1372d) in routine 'MAINAL'.
343 (address 53300d) in routine '$SEGRES'.
343 (address 10124663d) in routine '$START$'.
1-13471801
Optimization/Design Sensitivity - PBEAM, BOX1 - Optimizer can
not make progress
It has been observed that SOL 200 tasks that include beam properties that are
physically close to zero may fail to make progress.
An example is the I12
property for a BOX1 section type that has dimensions that give I12 property
values that are many orders of magnitude smaller than the I1 or I2 properties.
In these cases, small changes in dimensions cause huge changes in the property,
resulting in a violated contraint that the optimizer may not be able to deal
with.
Avoidance: Avoid section types that have this behavior or pose the problem in
such as way that the properties are not expected to become small.
1-13476801
2004.0.3
n for AGG Matrix
Acoustic Analysis - AGG - Add punch optio
Advanced Acoustics needs to be able to punch the AGG matrix for re-use. PARAM,
AGGPCH has been added to perform this function.
1-13483901
2004.0.3
DMAP - COMPILE - Too many IF-THEN-ELSE s
tatements cause ENDI array to overflow
A user dmap with too many if-then-else clauses will overflow the ENDI array and
fail during compilation.
Avoidance: Substitute multiple if statements or break up the subdmap into
smaller subdmaps.
A
1-13494001
2004.0.1
format by default
Postprocessing - Windows outputs new op2
The MSC.Nastran 2004 release supports a new op2 format. The delivery was
suppose to be set the default in the nastran.lcl file as the old format but
the Windows delivery does not.
This may cause prior releases of Patran and
other post-processors that do not know how to read the new format to fail.
Avoidance: Add the following line at the top of ../i386/nastran.lcl
NASTRAN OP2NEW=0
1-13494006
2004.0.3
Buckling - RIGID=LAGRANGE - Job Hangs
A buckling job with rigid elements that uses the Lagrange multiplier method
RIDID=LAGRANGE may hang during decomposition in the READ module in MSC.Nastran
2004.0.0 on HPUX Itanium.
Avoidance: User RIGID-LGELIM
1-13494012
b3
2004.0.3
Miscellaneous - TABLEM2 - Traceback in ta
MSC.Nastran 2004 may give a traceback in routine tab3 when TABLEM2 entries
exist. The problem may be avoided by defining the table in the negative
range.
l_4buf(0x11fffb038,0x0,0x3ffc01b2e20,0x8,0xc00000007) L. 133
<<?? pc=0x3ff800cfbf4>>(0x3ffc01b2e20,0x8,0xc00000007,0x0,0x3cc73ce704fb7b23)
L. 133
<<?? pc=0x1220f3520>>(0x0,0x3ffc01b7a98,0x1,0x3ffc01b2e20,0x3ffc01b2e20) L. 133
tab3_(0x1,0x3ffc01b2e20,0x3ffc01b2e20,0x8000,0x0) L. 4
hmat1_(0x0,0x0,0x3ffc01b3078,0x80,0x0) L. 4
ehexd_(0x1407f6c1c,0x1407f6c24,0x1407f6c14,0x1407f6c74,0x190000010) L. 4
emgbrd_(0x140ef888c,0x140653378,0x1201c68a4,0x140f185f8,0x140e9947c) L. 4
emgpro_(0x1201c68a4,0x140f185f8,0x140e9947c,0x140e99498,0x12025f9b4) L. 4
emg_(0x154534552,0x120204554,0x454c4544,0x4e474542,0x20202054) L. 4
xsem09_(0x1201bda4c,0x17,0x0,0x100,0x1201b5ccc) L. 4
xsemdr_(0x0,0x100,0x1201b5ccc,0x1,0x1201a2de8) L. 4
nastmon_(0x1201a2de8,0x14100e310,0x190000000,0x2000000,0x1) L. 4
mainal_(0x190000000,0x2000000,0x1,0x0,0x0) L. 149
<<?? pc=0x1201a2de8>>(0x11fffc020,0x0,0x3ff00000000,0x100000001,0x800000) L.
149
<<?? pc=0x1201a2b6c>>(0x1,0x11fffe030,0x0,0x11fffe058,0x11fffe070) L. 149
.
1-13526312
2004.0.3
RADCAV - UFM in RMG2 Module
Radaition Heat Transfer - even numbers of
Jobs with an even number of referenced RADCAV bulk data entries that enter rmg2
module more than once will fail. 1-13557302
2004.0.3
Optimization/Design Sensitivity - PARAM X
YUNIT - Initial Design Variable Information is incorrect
The spreadsheet
for each design
Limit and Upper
Upper Limit and
produced with PARAM XYUNIT in a SOL 200 run prints out cells
variable that are said to represent : Initial Value, Lower
Limit. The numbers in these cells are actually Lower Limit,
DELX, respectively.
User Information: If design optimization has been performed, design variable

values are listed at the end of the spreadsheet with the DESIGN VARIABLE
HISTORY. If only a design sensitivity has been run, design variable values are
not available in the spreadsheet and must be determined from the input or .f06
file
1-13562313
2004.0.4
- SFM 3007 (DOPR3) ILLEGAL INPUT TO SUBROUTINE DPR3H2
The message:
SYSTEM FATAL MESSAGE 3007 (DOPR3) ILLEGAL INPUT TO SUBROUTINE DPR3H2
will occur in SOL 200 if a DRESP3 references a DRESP2 that does not exist.
1-13568201
2004.0.3
Eigenvalue Analysis - MATGEN
An error in the resmodes subdmap may in rare cases cause a job to fail at the
MATGEN line below.
Avoidance: The line

MATGEN ,/MODEPART/NOMODES/0/MAXMODES/ $
should be altered to be:
MATGEN ,/MODEPART/6/NOMODES/0/MAXMODES/ $
1-13574607
2004.5
ll buildsss.bat not recognized
Miscellaneous - buildsss on Windows - ca
The command to build the sss on the Windows V2001 delivery (msc2001 buildsss)
would not work because necessary files were delivered in the wrong directory.
Avoidance:
copy buildsss.bat.i386 to ..\i386\buildsss.bat
copy buildsss.bat.del to ..\nast\del\buildsss.bat
Then run the buildsss command as documented.
1-13604401
2004.0.4
ris, Received signal 10 SIGBUS
Iterative Solver - FRRD1, ITER - Sun Sola
The iterative solver may fail in Version 2004.0.0 on 32 bit Sun Solaris systems
in frrd1 with the following message in the log file. No other rmessage is
output.
*** TERMINATING /local/msc2004t2/solaris/analysis.ultra
*** Received signal 10 SIGBUS
1-13605801
2004.0.3
MAXMIN - Traceback in SDR2
If an analysis contains a MAXMIN request and an attempt is made to perform an

XYPLOT of output data that has not been selected for MAXMIN processing, then
the job may fail and issue a traceback in in the SDR2 module routine sdr2c2,
Avoidance: Either select the output for MAXMIN processing or perform the
xyplot in a restart.
1-13605804
nent.
ACMS - GDACMS - SFM 4252 issued if null stiffness for a compo
ACMS may fail with the following message if a domain contains no elastic
elements, and thus no stiffness.
SYSTEM FATAL MESSAGE 4252 (SEMA)
MATRIX XAAV
FOR UPSTREAM SUPERELEMENT
Avoidance: IInsert the following DMAP alter
compile sema1
alter 'SEMA
upfm=0 $
BGPDTS'
83 DOES NOT EXIST
endalter
1-13620201
2004.0.4
ies contain incorrect mode id
Aeroelastic Analysis - Flutter sensitivit
In the print of formatted design sensitivities for flutter responses, the

number listed for mode ID is actually the subcase ID.
User information: a comparison of the response value listed in the formatted
senstivity print and the flutter summary will indicate which mode the
sensitivity is being printed for.
1-13639903
2004.0.4
Acoustic Analysis - ACMODL - UFM 3060
If a user who does not have a new acoustic license for MSC.Nastran 2004
executes an acoustic job, the job will terminate with UFM 3060 indicating that
an acoustic license does not exist.
It was the design intent that users who
wanted to choose the old method and run without the new license would have to
explicitly modify the ACMODL entry in their decks to select the old CP method.
This was the design intent because the old method of interfacing the fluid
and the structure only provided good answers for identical meshes.
To allow the users to make this selection without modifying their tests,
SYSTEM(346)=2, a.k.a. keyword FLSTINT=2, has been added to MSC.Nastran 2004.0.4
in the 2004R2 release so that the user can select the old method in an rc file.
1-13649701
2004.0.4
Performance - Sparse Data Recovery
The dmap functions that allow sparse data recovery may be unnecessarily
executed in SOL 101 and ANALYSIS=STATICS in SOL 200 when data recovery for the
entire model is requested.
Avoidance: If data recovery for the entire model is being requested (i.e.
DISP=ALL, STRESS=ALL) the best avoidance is to include param,sparsedr,no to
completely avoid the additional operations. The following dmap avoidance will
allow automatic selection to occur but may not beat V2001 performance for all
conditions:
compile fdrmgen
alter 'call spdr1'
return $
compile sedisp
alter 'SDR1
USET'(,-1)
call genrga uset,goa,gm,vgdr,goq/
rga,rgq/
true/atqset/seid $
dbstatus rga//s,n,norga $
if ( norga>0 ) then
mpyad rga,uas,/ugi $
else $
alter 'SDR1
USET'
endif $
endalter
1-13659501
ACMS - GDACMS may fail if component has no mass - UFM 9104
GDACMS may fail with the message USER FATAL MESSAGE 9104 if a component has no
mass.

compile sekmr
alter 'atsprt=false'
dbstatus mgg//s,n,nomgg $
if ( nomgg<1 ) atsprt=false $
compile semr3
alter 'call semr1'
paraml mvv//'null'////s,n,nullmvv $
if ( nullmvv<0 ) then $
TYPE PARM,nddl,RS,Y,maxratio,FZERO $
TYPE PARM,nddl,I,Y,bailout $
EQUIVX KNN/KFF/NOSSET $
IF ( NOSSET>-1 ) UPARTN USET,KNN/KFF,,,/'N'/'F' $
UPARTN USET,KFF/KOO,,,/lfset/'O' $
UPARTN USET,knn/,,kox,/'n'/'o' $
UPARTN USET,kox/kot,,,/'t+s+q'/'t'/'s+q'/2 $
DCMP
USET,SILs,EQEXINs,Koo,,/
LYY,UYY,ORSEQ/
-1/0/BAILOUT/MAXRATIO/oSET/1.E-20/16//////
S,N,SING/S,N,NBRCHG/S,N,ERR $
FBS
Lyy,,KOt/GOT//-1 $
return $
endif $
1-13661505
External Superelements - EXTSEOUT - UFM 311, non-unique field
2 on GRID, External SE, .asm file
When using the .asm file generated by EXTSEOUT, if the boundary GRID IMAGES
don't match, then the following fatal message may be issued:
NON-UNIQUE FIELD 2 ON BULK DATA ENTRY GRID
ENTRY COUNT =
XXX
XXX
SORTED
The problem is that the IMAGE is searched, not the "equivalent". That is
GRID,101,0,1.,1.,1. and GRID,101,,1.,1.,1. are not considered the same, and the
fatal message is issued.
1-13679504
2004.0.3
D are not always translated to Marc.
SOL 600 - Dynamic loads specified by DLOA
For SOL 600, Dynamic loads specified by DLOAD (rather than FORCE, PLOAD, etc)
are not always translated to Marc. This particularly happens when DLOAD is the
only loading.
1-13686801
2004.0.3
Superelements - EXTSEOUT - Missing Output
for external superlements in SOL 109 AND 112
A SOL 109 or 112 assembly run employing an external superelement created using
the EXTSEOUT feature does not give displacements, velocities or accelerations
for the interior points of the external superelement.
Avoidance: For both SOL 109 and SOL 112 apply the following dmap alter.
compile super3
alter 'IF ( APP=\'TRANRESP\''(3),''
if ( false ) then $
alter 'IF ( APP=\'TRANRESP\''(4),''
if ( false ) then $
compile sedrcvr
alter 'drmh3'(,1)
DSAR uls1,,,/uls2,,,,/-1 $
equivx uls2/uls1/-1 $
endalter $
1-13691604
Miscellaneous - MEM, SFM 3062 - Module GP5
Submitting a job with too much memory may lead to a failure in the GP5 module:
0*** SYSTEM FATAL
FAILURE OCCURRED IN UTILITY GTXYZD CALLED IN SUBROUTINE NORMFD .
DATA RETRIEVAL.
In one case the job submitted with mem=1400mb or 1700mb failed but when
submitted with mem=1200mb the job ran.
Avoidance: Request less memory.
1-13694401
2004.0.2
less memory than requested
Miscellaneous - IA64/Linux - May run with
If more memory is requested than is available on a Linux IA64 system, then the
job is run with a reduced amount of memory. The job should be stopped instead.
1-13696116
FM
2005
Parallel - SYSTEM(107) - Wrong Answers, S
Shared memory parallel jobs (SMP), parallel=n or system(107)=n may fail or

produce wrong answers on Alpha in MSC.Nastran 2004.0.0
Avoidance: Do not use smp parallel on Alpha.
1-13704901
2004.0.3
orrect Loads, Wrong Answers
SOL 600/Implicit Nonlinear - TLOAD2 - Inc
In Version 2004.0.0, SOL 600 loads defined by TLOAD2 entries are incorrect.
The equation to calculate the loads has an error. In addition, the TABLED1
that is created is missing every third point.
1-13704904
ocessed
2004.0.3
SOL 600 - Multiple MATEP materials not pr
In SOL 600, multiple MATEP materials are sometimes not processed.

1-13708001
2004.0.3
Optimization/Design Sensitivity - FREQ4 Possible Wrong Answer or Divide by Zero when NFM=1.
If design sensitivity and optimization analysis includes a FREQ4 entry that
asks for only a single frequency per "spread," NFM=1, the code attempts a
divide by zero and that gives different results, depending on the platform.
The AIX traps the error, Linux proceeds and gives answers that are close, but
wrong, SGI and HP produce unknown (NaN) numbers that point to an obvious
problem.
Avoidance: The best avoidance is to use a FREQ5 entry with a single FRi value
set to 1.0 Using NFM>1 on the FREQ3 entry also avoids the error.
1-13711524
included.
2004.0.3
Miscellaneous - INCLUDE - .blk files not
In version V2004 the new output file named "filename.blk" is created for every
run which contains sorted bulk data for SOL 200. Thus, the
nastran command script renames the existing "filename.blk" to filname.blk.1"
during the run. IF the NASTRAN command line option OLD=NO is set
"filename.blk" will be deleted. To overcome this problem rename "filename.blk"
to "filename.xxx", where "xxx" is anything other than "blk".
Avoidance: Avoid using "blk" as a include file name extension.
1-13713263
2004.0.3
ect GEOM2X and GEOM3X Output2 data.
Postprocessing/DMAP - PARAM,POST - Incorr
In MSC.Nastran 2004.0.0 the data written in the OUTPUT2 GEOM2X and GEOM3X data
blocks is incorrect.
Avoidance: Apply the following dmap alter.
compile out2geom
alter 'output2 geom2x',''
OUTPUT2 GEOM2x,GEOM3x,GEOM4x,geom1x,bgpdtx//0/OUNIT1//OMAXR/
GEOM2 / GEOM3 / geom4 / geom1 / bgpdt /
'geom2'/'geom3'/'geom4'/'geom1'/'bgpdt' $
endalter
1-13715501
nswers
2004.0.1
Component Mode Synthesis - CSET - Wrong A
A small CMS job using CSET reduction gives erroneous results if all of the
component modes are employed. However, the same job gives good results if
PARAM,MHRED,NO is specified or if only a subset of the total component modes
are employed
In Version 2005 this condition is trapped with a message that instructs the
user how to avoid the problem.
1-13732901
rong Answers
2004.0.5
Component Mode Synthesis - CSET, QSET - W
Component Mode Synthesis should give exact results if all eigenvalues are
included. A small CMS job employing a part SE and CSET reduction and with
Q-set data defined in the part SE Bulk Data gives erroneous results if all of
the component modes are calculated. Furthermore, different erroneous results
are calculated if the Q-set data in the part SE Bulk Data are replaced by an
equivalent SENQSET entry in the Main Bulk Data.
1-13760301
2004.0.3
ocks in op2 file
SOL 600/Implicit Nonlinear - Extra Databl
SOL 600 is writng extra datablocks to the op2 file for the initial Nastran
2004 release. Programs such as Medina and Animator may have trouble handling
these extra geometry datablocks.
Avoidance: This can be avoided by the user employing his own DMAP to control
the datablocks written to the op2 file rather than specifying outr=op2 on the
SOL 600 entry.
1-13762804
2004.0.4
is missing shared object libraries.
Installation - Sun Solris64 installation
The MSC.Nastran V2004 installation for Sun Solaris 64 systems is missing

shared object libraries. The libraries are needed if the system does not have
Fortran compilers installed.
These libraries may be downloaded from the
MSC.Software web site:
http://www.mscsoftware.com/support/software_updates/index.cfm#nastran
and at:
http://www.engineering-e.com/download/?productid=15
1-13767914
2004.0.3
ESPCH1,-1 option fails for PBEAM entries
When a negative number is specifified for PARAM,DESPCH1 to indicate that small
field format is to be used and the analysis model contains PBEAM entries, the
job will fial with an error message in the log file.
Avoidance: Use a positive number, i.e. large field format.
1-13776201
2005
Documentation/QRG - RESVEC Keyword DMPLOD
, NODMP Lead to UFM 601, Should be DAMPLOD and NODAMP
The documented keywords for the RESVEC Case Control Command DMPLOD and NODMP do
not work. The correct spelling is DAMPLOD and NODAMP. The incorrect spelling
leads to UFM 601 (IFP1D) THE KEYWORD ON THE ABOVE CARD TYPE IS ILLEGAL OR
MISSPELLED.
1-13794801
6 EC 5 in UFBS
2004.0.3
Rigid Elements - PARAM,AUTOMSET - SFM 427
If the dependent node of an RBE is restrained and PARAM,AUTOMSET,YES is

specified, the analysis may fail with the message:
*** SYSTEM FATAL MESSAGE 4276 (UFBS2)
ERROR CODE
5 PID= 0
*** USER INFORMATION MESSAGE 4276 (UFBS2)
DMAP avoidance is:
compile autom
alter
'TRNSP
RMAL','' $
TRNSP
RMAL/RMALTx $
matmod RMALTx,,,,,/Rjunk,RMALTnz/12/s,n,NLnull/1 $
if (NLnull > 0) then $
add
rmaltx,RMALTnz/rmalt $
else $
equivx rmaltx/rmalt/-1 $
endif $
endalter $
1-13802801
rections
2005
Documentation - Release Guide - Minor Cor
The following modifications should be made to the MSC.Nastran 2004 Release

Guide. Release guides are not re-issued so this error report is being marked
as addressed in V2005.
On page 530, Table 13-1, the descriptor "SRESS" should be modified to "STRESS"
On page 533, the first K2PP should be modified to K2GG
On page 533, the first M2PP should be modified to M2GG
On page 349, the 3rd sentence in the second paragraph should read
"Solutions specified in table 3-3 of the standard SOL statement may be used."
On page 352, "MSC.Marcs" should be changed to "MSC.Marc"
On page 374, 'inlstrs5.DBALL' and 'inlstrs5.MASTER' should be modified to
'nlstrs5.DBALL' and 'nlstrs5.MASTER', respectively.
On page 353, MATT should be modified to MATF
On page 354, MATV should be modified to MATVE
On page 355, MARCSHLT and MARSUMY should be modified to MARCSLHT and MARCSUMY,
respectively.
On page 611, the description for word 8 of the CWELD should be "Coordinate
system for the
type of projection"
On page 594, the description for OSTR should be changed from stresses to
strains.
On page 572, the second sentence of the second paragragh should read " To
indicate conversion
to "OLD" entry structure, the character "O" is placed as the last character of
the Special
Version field.
1-13817704
2004.0.3
yond the first entry
ACMS - ASET1 - ACMS ignores ASET1 data be
In ACMS analysis grid points on ASET and ASET1 entries are moved into the
residual structure. However if there is more than one ASET1 entry in the bulk
data, the ASET1 data beyond the first entry is ignored.
1-13830101
3001 (MTRXIN)
2004.0.3
Miscellaneous - PARAM,CHECKOUT,YES - SFM
Jobs using the PARAM,CHECKOUT,YES feature could fail with SFM 3001 from the
MTRXIN module if there is a K2GG case control command selecting a stiffness
matrix and there is no M2GG command selecting a mass matrix.
Avoidance; The error can be avoiding the MTRXIN in with a dmap alter.
1-13860606
2004.0.3
s with Sparse Data Recovery
Superelements - MPCF, SPCF - Wrong Answer
In V2004, the new sparse data recovery can cause errors in the displacement
vector for superelements when displacements are requested for only some of the
GRID points in the model at the same time as MPCF or SPCF requests are made.
This error occurs only in the direct solution sequences; i.e., 101, 103, 108,
109, and 200 with ANALYSIS=DFREQ.
Resolution:
Either use PARAM,SPARSEDR,NO to deactivate sparse data recovery methods or
COMPILE SPDR1 NOLIST $
ALTER 189 $
DIAGONAL V01S/V01SX/'WHOLE'/0. $
EQUIVX V01SX/V01S/-1 $
ENDALTER $
1-13860635
2005.0.2
Sparse Data Recovery
Superelements - MPCF - Wrong Answers with
In V2004, in a superelement, if MPCF output is requested for only some of the

GRID points of the model, the MPCF output may be in error if sparse data
recovery is active, i.e. PARAM,SPARSEDR,YES (default). In addition, an SPCF
output request will be ignored. This error occurs only in the direct solution
sequences; i.e., 101, 103, 108, 109, and 200 with ANALYSIS=DFREQ.
Avodaince: Use PARAM,SPARSEDR,NO
1-13875001
4)
2004.0.6
Miscellaneous - INPUTT4 - UWM 6445 (INPTT
A formatted INPUTT4 read for more than one matrix will fail with the following
Fortran READ error:
UWM 6445 (INPTT4):
A FORTRAN FORMATTED READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = ...
USER INFORMATION: THE FILE WAS SPECIFIED IN AN ASSIGN FILE MANAGEMENT
STATEMENT
USER ACTION: VERIFY THE FILE ASSIGNMENT AND AND CONTENTS OR CONTACT
MSC.SOFTWARE.
VERIFY DATA AND FORTRAN SPECIFICATION.
PROGRAMMER INFORMATION: FORTRAN IOSTAT CODE = ...
1-13876601
2004.0.3
ly Process One Failure Criteria
Impicit Nonlinear (SOL 600) - MATF Can On
The SOL 600 MATF entry can only handle one failure criteria instead of three.
Avoidance: Enter MATF entry three times.
1-13894501
2007.1.0
to Open Input Relations
Postprocess - DBC, PARAM,FIXEDB - Unable
PARAM,FIXEDB in SOLs other than 101 and 103 forces an incorrect approach code
into the DBC module causing the following error:
" UNABLE TO OPEN INPUT RELATION TOL RETURN CODE = 1."
Avoidance: Remove PARAM.FIXEDB from the input file.
1-13897501
ecessary Input
2004.0.3
Implicit Nonlinear (SOL 600) - MATF - Unn
All continueation entries and all failure criteria constants are required for
the MATF entry even though only the frist constant is needed for the most
simple max stress criteria.
This needs to be changed so that only those constants required to satisfy the
failure criteria chosen need be entered. Thus, for the max stress criteria,
only the first entry is required and only the first constant needs to be
defined.
1-13915501
2004.0.3
- Wrong Answers
In MSC.Nastran Version 2004 an optimization job will produce incorrect

dimentions for an intermediate station or at end B of the PBEAML entry if the
following conditions are met:
1. PBEAML entry is used that has SO=NO on other stations,
2. Only end A is designed.
1-13915504
2004.0.3
DESPCH1 - UFM 315 (IFPDRV)
Optimization/Design Sensitivity - DESPCH,
When an optimization job designs any real value on a CBEAM, CQUAD4 and/or
CTRIA3 entry, bad punch output for these entries may be produced leading to
UFM315 (IFPDRV) when they are included in a cold restart job.
The same job may also fail with traceback of Segmentation Violation on AIX
machine.
Avoidance: No practical avoidance exists except to manually modifiy the
offending entries.
Keywords: DESPCH DESPCH1
1-13928902
2004.0.3
SFM 4276 (UNPACK) EC31
Dynamic Response - MCFRACTION, MEFMASS -
Modal dynamic response analysis that have multiple subcases that reference the
same FREQ set but different DLOAD sets and request modal participation factor
output may fail with the following message:
ERROR CODE
31 PID= 0
Avoidance: A possible avoidance is to define and reference a duplicate set of
FREQ data for the second and subsequent subcases.
1-13930009
2004.0.4
- UFM 7615 (MDG2RG)
Documentation/QRG - SOL400, RIGID=LGELIM
The case control command RIGID=LGELIM as described in the MSC.Nastran V2004

Quick Reference Guide produces the following error because the option should be
LNELIM.
*** USER FATAL MESSAGE 7615 (MDG2RG)
FOR NONLINEAR SOLUTION SEQUENCE, THE CASE CONTORL COMMAND 'RIGID=LGELIM'
IS ILLEGAL.
USER INFORMATION: THE LEGAL VALUE IS 'LNELIM' OR 'LAGR'.
*******ALSO the word CONTROL is spelled wrong.******
For SOL400, the RIGID=LGEL method is not available, therefore a fatal error is
issued. The wording 'USER INFORMATION: the legal value is 'LNELIM' or LAGR' is
corrected to 'USER INFORMATION: the legal value is LINEAR or LAGR'. Also the
word CONTROL is corrected.
1-13948931
2004.5
ve disk space and CPU
Dynamics/Enforced Motion - SPCD - Excessi
In V2004, enforced motion in dynamics may use excessive disk space and CPU.
Avoidance: Insert the DMAP alter in the attachment.
1-13987701
2004.0.3
Spotweld - CWSEAM - UFM 7549, Cannot find
projection points for CWSEAM elements
The default pcid of CWSEAM elements was not set appropriately. This error
results in USER FATAL MESSAGE 7549 indicating that it cannot find projection
points for the CWSEAM elements that are projected along the x-axis.
1-13989006
2004.0.2
ading shared libraries
Miscellaneous - XNASTRAN - Error while lo
The XNASTRAN interface may fail on some Linux operating systems with the
message:
"error while loading shared libraries: lib*: cannot open shared object file: No
such file or directory."
Avoidance: Use the nastran command.
From jjg 5/23/08
"XNASTRAN" is not built on x8664.
"XNASTRAN" works with MDR3 on my Linux IA32 system running RH 4.3
"XNASTRAN" should not be used on IA64 as the use of graphical interfaces on
IA64 systems is discouraged.
If this is still an issue, please note the hardware platform, version of
Nastran, and version of the OS you are using.
Joe Griffin (714) 445-5636
1-13998601
2005
Command Description Missing
Documentation/QRG - FMETHOD Case Control
The FMETHOD Case Control command was inadvertently deleted from the V2004 Quick
Reference Guide. Also remark 1 under the FLUTTER bulkdata entry description
should point to the FMETHOD command not the METHOD command
1-13998604
2005.5
Missing Parameter Description
Documentation/Aeroelastic Analysis/QRG -
The description of parameter supaero is missing from the Version 2004 Quick
Reference Guide. It should read:
SUPAERO Default=ZONA
If SUPAERO = ZONA, then the ZONA51 code is used for supersonic aerodynamic
calculations. If SUPAERO = CPM, then the CPM method is used. If ZONA51 is not
available at a particular installation, PARAM, SUPAERO,CPM must be specified to
avoid a fatal error when performing supersonic aerodynamic analyses. Only one
supersonic aerodynamics method can be selected in a given run.
This parameter is available in solution sequences 144,145,146 and 200 and can
be specified in either case control or as a bulk data entry.

1-13998611
orted
2005.5
Documentation/COG/DMP - ssh/scp not supp
The nastran init scripts currently have rsh and rcp hardcoded and will not work
in an environment that uses ssh. This will prevent distributed memory
parallel jobs from working in a network that only supports ssh and will also
prevent execution of any job on a remote node. If a client wants to use ssh
and scp, they either need to:
1. Change all the rsh/rcp to ssh/scp
2. make links between ssh/scp and rsh/rcp
From Joe Griffin.. Jun 23, 2008
Users can use "ssh" by adding "s.rsh=ssh" on the command line.
Admins can change the default by adding "s.rsh=ssh" to the
$MSC_BASE/bin/mdnast*.ini file.
If you run "mdnast2008 help s.rcp" is states:
s.rcp=command
Remote copy command for communicating with Windows/Linux/UNIX systems.
This keyword may only be specified on the command line or in the command
initialization file. The default is "scp" if "s.rsh" specifies "ssh"
and "rcp" otherwise.
So setting "s.rsh" should also set s.rcp. I verified the s.rsh works on
a system without rcp.
End of Joe's comments.
1-13998622
2005
rdynamics - Traceback in TRD1
Documentation/QRG - ROTORG, TSTEPNL, Roto
The new rotordynamics capability in MSC.Nastran 2004 includes nonlinear

effects which make the transient response algorithm not unconditionally stable.
As such rotordynamics analysis may fail with a traceback in trd1. If this
happens the user should specify a smaller timestep.
1-14045201
Optimization/Design Sensitivity - Poor Performance when DRESP
applies to more DOFs than DESVAR.
The perofrmance gain may be affected negatively for an optimization job with
design responses that cover more dofs of the structure than design variables.
Avoidance: Use the following dmap alter. Notice that the following alter
applies to the case of static/normal mode and buckling. It can be reapplied to
a different solution type by modifying the alter statement.
compile pslgdv
alter 'outprt'(1),''
if (spdm) outprt caseds,ects,bgpdts,sils,,,,,,,
tabevp0,tabevs0,,,/
vgdr,,,,/s,n,sdr/0/'auto'/spdmrat $
compile respsen
alter 'outprt'(1),''
if (spdm) outprt caseds,ects,bgpdts,sils,,,,,,,
tabevp0,tabevs0,,,/
vgdr,,,,/s,n,sdr/0/'auto'/spdmrat $
1-14051758
nux Itanium 2
Licensing - FlexLM uncounted nodelock codes on SGI Altix / Li
It has been reported in MSC.Nastran 2004 on SGI Altix Linux Itanium 2 computers
that uncounted nodelock FlexLM licenses do not work.
The nastran log file shows that the MSCID is different than lmhostid on a SGI
Altix computer (Linux - Itanium 2).
Avoidance: Use the MSCID reported by Nastran when generating the license.
1-14061906
Restarts - sparse data recovery - Wrong Answers
In a dynamic data recovery restarts, if only additional output is requested

at more points and/or elements then results related to the additional grids
and/or elements will be null, missing, or wrong.
Avoidance:
compile disprs
alter 'equivx upx\/upf'(,-1)
delete /upf,,,, $
endalter
1-14063502
2004.0.4
SOL 600/Implicit Nonlinear - Hyperelastic
Element with midside nodes not Properly Mapped to Marc.
The hyperelastic CHEXA element with mid-side nodes is not properly mapped to
the corresponding Marc element, instead it is mapped to the corresponding
8-node Marc hyperelasic hexa element. The net result is that deformed plots
show the mid-side nodes standing still and strange plots results.
1-14068501
DMP - Linux - LAM won't boot with BAT=YES
Starting w/ 2001R4 (2001.0.9) MSC.Nastran boots the LAM/MPI daemons for the
user. However, with RH7.3 and Slackware systems, the LAM daemons may not boot
if "BAT=YES" is specified.
Avoidance: Use BAT=NO
This problem does not occur w/ MSC.Linux. The problem is because when BAT=YES
is used, the first process completes, and the child processes become ZOMBIES.
We set a flg to ignore child zombies. Because of that flag, LAM daemons will
not start from within the shell. I think starting the lam daemons for the
users is more important then BAT=YES, so I am leaving the code as is.
1-14077901
2007.0.0
Optimization/Design Sensitivity - Eigenve
ctor Sensitivities Require PARAM SPARSEDR=no
Sparse data recovery in SOL 200 and eigenvector sensitivity analysis were both
introduced in the 2004 release. It has been found that these two capabilities
are not fully compatible.
Avoidance: When eigenvector sensitivities are required, set PARAM SPARSEDR NO
1-14116602
2004.0.5
K2PP, SPCD - UFM 1126 for K2GG
Dynamic Analysis - EPOINTS, M2PP, B2PP,
EPOINTS and enforced motion with K2PP, B2PP or M2PP input may cause USER FATAL
MESSAGE 1126 to be encountered.
compile gma
alter 'k2gg'(2,-1)
delete /k2gg,,,, $
endalter
1-14120001
2005.0.2
PCForces - SFM 6143
Frequency Response - freq-dep elements, M
SFM 6143 has been observed when performing a frequency response analysis in
SOLs 108, 111, 146, and 200 with frequency dependent elements and MPCForces are
being requested
User Avoidance: Specify PARAM SPARSEDR NO or insert the following DMAP alter:
compile fdrmgen
alter 'equivx rxmgx\/rxmg',''
alter 'paraml rmgg'
if ( spdrm ) then $
equivx rxmgx/rxmg/-1 $
delete /rgm,,,, $
trnsp
rxmg/rgm $
endif $
endalter
1-14125525
2005.0.2
Inertia Relief - PARAM,INREL, SUPORT - M
ultiple load case and DIMG,UACCEL, SFM 6144
Multiple boundary conditions with DMIG,UACCEL in SOL 101 will terminate with
compile statrs
alter 'urax'
type db pg $
PARAML pg//'TRAILER'/1/S,N,NCUL $ total no. of loads
if ( (ncul-6)<>nloads ) then $
ncul=ncul-6 $
nskip=nskip-1 $
MATGEN ,/COL/6/NCUL/NSKIP/NLOADS $
PARTN
urax,COL,/,,urax1,/1 $ loads
equivx urax1/urax/-1 $
endif $
endalter
1-14139801
2004.0.4
- SFM 6144 (PARTN1)
Acoustic Analysis/Enforced Motion - SPCD
In direct frequency response, sol 108, the new relative enforced motion
capability in MSC.Nastran Version 2004 will encounter a matrix incompatibility
fatal message when fluid is added to structure.
*** USER WARNING MESSAGE 2125 (VEC)
MODULE VEC - NZ=0, ONE OR MORE COLUMNS OF OUTPUT MATRIX WILL BE NULL.
*** SYSTEM FATAL MESSAGE 6144 (PARTN1)
SPECIFICALLY:
The number of rows in KAA is not equal to the number of rows in the row
partitioning vector VAY
The number of columns in KAA is not equal to the number of rows in the column
1-14144521
2006
when QSET omitted
Superelements - BNDFIX1 - Unexpected ASET
If BNDFIX1 degrees of freedom are specified, but no QSET is specified, then the
BNDFIX1 entry is ignored.
Avoidance: Use the ASET entry.
1-14155701
2004.0.5
not work on Primepower
Distributed Memory Parallel - DMP - Does
The 32 bit nastran driver program delivered with MSC.Nastran 2004.0.0 under the
Solaris achitecture will not work for Distributed Memory Parallel (DMP) on
Primepower systems.
Avoidance:
Download a new driver program from:
1-14176601
ing Output
2004.0.3
Dynamic Analysis - MCFRACTION, SET - Miss
If the MCFRAC case control command selects a SET that contains an implied thru
range, only the first degree of freedom in each of the ranges will be output.
The implied thru range is a continous range of degrees of freedom for a grid
point as in 969/T1,969/T2,969/T3.
Avoidance: An avoidance is to select grid/dof combinations that do not imply
thru and use restarts changing the MCFRACTION SET content to recover all of the
required data.
1-14180601
2004.0.4
SOL 600 - CQUAD4, CTRIA3 - Variable thick
nesses on continuation entry not translated correctly.
For SOL 600, thickness specified by continuation lines on CQUAD4 and CTRIA3
entries are not properly translated. There is also a priority conflict between
these thicknesses and those specified by the NTHICK option.
1-14186901
2004.0.4
Frequency Response Analysis - SPCD, DPD SFM 4276 when multiple subcases request different spc sets
A frequency response problem involving enforced motion fails with SFM 4276 in
the DPD module if there are multiple subcases and different spc sets are
selected in the case control.
Avoidance:
Apply the following dmap alter:
compile phase0
alter ' copy
yG1\/yG2'(,-1),''
$ create only the first yg2 for dynamics
ELSE if ( nskip=1 or app<>'freqresp' ) then $
1-14186907
2004.0.4
Dynamics - TLOADi, ACSRSE - Negative real
values for the DELAY and DPHASE fields - UFM 316
Use of negative real values for the DELAY or DPHASE fields on the ACSRCE or
TLOAD1 or TLOAD2 entries results in UFM 316 in the PREFACE module.
1-14191701
2004.0.4
Optimization/Design Sensitivity - DLINK Incorrect constraints for dependent design varaibles.
When an optimization job has specified a DLINK entry, the corresponding DESVAR
entry has a blank DELXV field and P2 on the DOPTPRM is set to 4, the
constraints for dependent design variables are printed in the f06 file
incorrectly. However, these constraints are computed correctly during the
approximate optimization.
Avoidance: Specify a non=blank DELXV field on the dependent DESVAR entries.
1-14210501
2004.0.4
Modes Unnecessarily Recalculated
Eigenvalue Analysis/Acoustics - RESTART -
In V2004, if a restart is performed from a SOL 103 run with acoustics, then
the fluid modes may be unnecessarily recalculated.
Avoidance: Insert the following alter in SOL 103 cold start:
compile semodes
alter 1
type parm,nddl,i,n,methf $
endalter
1-14222717
2004.0.4
calcualtes Modes
Superelement - RESTART - Unnecessarily Re
A superelement restart from sol 103 to 112 may unnecessarily recalculate

upstream modes for some superlements.
compile sekmr
alter 'endif \$ atsprt'(,-1)
kchng=false $
endalter
1-14223905
2004.0.4
RIAR - Wrong Answers
Nonlinear Analysis - TEMP(LOAD), QUADR, T
Temperature loads for the QUADR and TRIAR elements is not implimented correctly
for nonlinear analysis.
Avoidance: Use the QUAD4 and TRIA3 elements.
1-14233604
2005
Elements - CQUADR, PARAM,CHECKOUT,YES - I
ncorrect grid point weight generator output
Mass for the CQUADR element is not included in the grid point weight generator
results when param,checkout,yes is specified.
1-14238367
gy Results
2005.1
ESE - REPCASE - Wrong Element Strain Ener
If there is an ESE request in the REPCASE only, the results are wrong.
Avoidance: Request ESE for at least one element in the primary subcase.
1-14249707
2005
H - Incorrect Default
Documentation/QRG - SOL 600, PARAM,MARCPT
The MSC.Nastran V2004 indicates that the default for param,marcpth is 1. It is

not, it is 0. The value of 0 indicates that marc is run within nastran and
will look for the marc executable in the default installation directory.
1-14251001
rs
2004.0.4
Dynamics - CAXIFi, PARAM,G - Wrong Answe
If the old acoustic cavity method (see CAXIFi elements) is selected in SOL 108
or SOL 200 (with ANALYSIS=DFREQ) then PARAM,G will be ignored.
compile sedfreq
alter 'fonly=',''
endalter
1-14251410
2008.0.0 (MD R3)
Optimization/Design Sensitivity - RLOAD1
- Enforced Displacement, UWM 2071 (DPD2)
SOL 200, analysis=mfreq, may produce incorrect results for enforced
displacement specified with the RLOAD1 entry.
Avoidance: This problem can be avoided by expanding output request set to
include the grids with enforced motion.
1-14251416
2004.0.4
ma datablock missing from op2 file
Post Processing/ACMS - PARAM,POST,-1 - La
A distributed memory parallel (dmp) ACMS analysis does not write the lama table
to the op2 file when param,post,-1 and param,post,ext,yes are specified. This
data block is critical for post processing acoustic results and is produced in
a serial run.
1-14261401
2005
ng Output due to sparse data recovery
A SOL 103 assembly run employing an external superelement created using the
EXTSEOUT feature does not produce the requested output for the external SE.
Avoidance: Insert PARAM,SPARSEDR,NO.
1-14267003
2004.0.4
Elements - MFLUID - UFM 4257 (FMXACD)
User fatal message 4257 may erroneously appear for virtual mass elements
(MFLUID), if the distance between two element centers is exactly equal to the
RMAX value from the MFLUID record.
Avoidance: An avoidance is to modify RMAX (see MFLUID entry) slightly. It is
recommended that the default value always be used, and this error is very
unlikely.
1-14270665
Submittal - "\" in .rcf file, USER FATAL MESSAGE (pgm: nast
ran, fn: validate_lcl_key

A back slash in the rc file or submittal line to indicate a directory path
(i.e. D:\) may lead to the following fatal message
*** USER FATAL MESSAGE (pgm: nastran, fn: validate_lcl_keywords)
sdirectory=d:memory=500mb
(e:/msc/conf/nast2004.rcf[1])
Avoidance: This error can be avoided by changing the back slash to a forwared
slash or by adding a " $" after the back slash as follows:
sdir=d:/
or
sdir=d:\ $
Comment from JAS: This Windows only limitation will be documented in the IOG.
1-14273377
2004.0.4
3,FREQ4,FREQ5 - SFM 6833
Distributed Memory Parallel (DMP) - FREQ
FREQ3, FREQ4, and/or FREQ5 Bulk Data entries in a DMP analysis may lead to
compile semfreq
alter ' frlgen '(,-1)
if ( procid=1 ) then $
disutil lamas ,,,////3 $
else if ( procid>1 ) then $
delete /lamas,,,, $
disutil ,,,,/lamas ///3 $
endif $ procid>1
endalter
1-14284801
2005
converges slower
Optimization/Design Sensitivity - scr=no
SOL 200 with scr=no converges slower than with SCR=yes.

Further
investigation has found that the slow convergence was due to incorrect
sensitivity coefficients supplied to optimizer.
Avoidance : Insert the followng alters:
$ for v2001 compile pslgdv
alter 'if ( dmresd'(2,-2)
else $
if (seid=0) delete /delf1,,,, $
$ for v2004 and v2005
compile pslgdv
alter 'if ( nndgs'(2,-2)
else $
if (seid=0) delete /delf1,,,, $
1-14286512
2004.0.4
Distributed Memory Parallel (DMP) - SEP1X
- Free Floating Grids Cause DMP to Fail in SEP1X
In MSC.Nastran 2004.0.3 (released to only one client) a model with free
floating grids, meaning grids that are not attached to the structure, may cause
dmp jobs to fail. This includes models with grids that are only used as
reference points.
Avoidance: Set system(294)=2 (which will print the external IDs of those
free grids, search for FREE FLOATING, and then remove the grid entries. If
the grids were used as reference points, they have to be replaced by
coordinates. Grids that are referenced only on a PLOTEL element are not
considered free floating, so attaching the reference grids to PLOTELs is
another way to avoid the problem.
1-14299201
led correctly.
2004.0.4
ACMS - Multiple USETi,U6 entries not hand
In ACMS, unit load degrees of freedom on the USET1 entry are forced to the
residual structure. However, if there are more than one USET1 entry in the
input, it only forces the points from the first entry. DOF on subsequent
entries are not forced to the residual. This leads to fewer than the desired
number of residual vectors when those degrees of freedom are not put into the
residual structure by the automatic partitioner.
1-14305003
space
2004.0.4
SOL 600 - Large Jobs - Insufficient swap
Extremely large SOL 600 jobs may fail on some small computers with a message
that indicates that they have run out of swap space.
Avoidance: Other than running on a different platform, there is no avoidance.
1-14322801
2004.0.4
YUNIT - FORMAT ERROR 103
Optimization/Design Sensitivity - PARAM,X
The error message:

FORMAT ERROR 103: A POSITIVE VALUE IS REQUIRED HERE
may occur in SOL 200 when PARAM XYUNIT is used to create a CSV file of the
optimization results and the number of design variables is 3n+1 where n is any
integer starting from zero. To date this behavior has only been observed on
Linux platforms.
Avoidance: Run on a different platform or add a dummy variable such that the
number of variables is not 3n+1.
1-14348401
2004.0.4
RBAR - Wrong Answers
Nonlinear Analysis (SOL 400) - MPC, RBEi,
For SOL400, the solution will converge to wrong results if there are MPC
constraints or linear rigid elements (RIGID=LINEAR) in the model.
1-14352403
2004
Elements - CRAC3D - UFM 5469 (DUMK9D)
Input with more than one crac3d element will fail in Verison 2001.0.9 with UFM
5469 as follows:
*** USER FATAL MESSAGE 5469 (DUMK9D)

IN CRAC3D ELEMENT
21789 CONNECTION POINT G64 IS REQUIRED IF CONNECTION
POINT G55 IS SPECIFIED
*** USER FATAL MESSAGE 5467 (DMK9ND)
CONNECTION POINT G10 OF CRAC3D ELEMENT
21789 IS REQUIRED BUT NOT
DEFINED
*** USER FATAL MESSAGE 5467 (DMK9ND)
CONNECTION POINT G10 OF CRAC3D ELEMENT
21789 IS REQUIRED BUT NOT
DEFINED
*** USER FATAL MESSAGE 4660 (EHEXD)
FOR ELEMENT WITH ID =
0
THE CORNER POINTS HAVE NOT BEEN SUPPLIED CORRECTLY.
.
.
Avoidance: Use any other version, else analyse the cracks in separate runs.
1-14380804
2005.0.2
xpected Answers
Acoustic Analysis - SDAMPING(FLUID) - Une
In SOL 111, coupled fluid-structure analysis, with multiple subcases, multiple

specifications of SDAMPING(FLUID) are ignored and only the first is processed.
compile semfreq
alter 'caseg'(2),''
case
casem,pvtc/caseg/'comm'/s,n,nskip///////
'k2pp'/'m2pp'/'b2pp'/'tfl'/'sdamp'/'rgyro'/'sdampf'//////
'g'/'alpha1'/'alpha2' $
endalter
1-14382607
Optimization/Design Sensitivity - ANALYSIS=MODES and MFREQ wi
th SPCD - UFM 3046
An MFREQ shape optimization task that contains multiple subcases and SPCD type
loads will encounter:
*** USER INFORMATION MESSAGE 7559 (FRRD1A)
THIS FREQUENCY RESPONSE ANALYSIS INVOLVES THE FOLLOWING TYPES OF
EXCITATION -* ENFORCED ACCELERATION USING SPC / SPCD DATA
*** USER FATAL MESSAGE 3046 (SQFREQ)
THIS FREQUENCY RESPONSE ANALYSIS HAS NO EXCITATION SPECIFIED FOR IT.
APPLIED LOADS AND ENFORCED MOTION ARE BOTH NULL.
THE RESULT WILL THEREFORE BE A ZERO SOLUTION.
Avoidance: The subcases must be run separately or insert the following DMAP
alter:
$compile feamode $ uncomment in V2005
compile fea $ V2004
alter 'if ( nopha=',''
if ( true ) then $
compile modefsrs
alter 'call moders'(,-1)
dbstatus phsa//s,n,nophsa $
if ( nophsa=-1 ) then $
alter 'call moders'
endif $
alter 'call resveca'(,-1)
alter 'call resveca'(,7)
endif $
1-14397204
2004.0.4
e-Dependent Stress-Strain Curves
SOL 600 - MATTEP - Add General Temperatur
SOL 600 temperature-dependent stress-strain curves need to be supported for

general shapes. At present such curves are limited to scale with the same
slopes as the original curve vs temperature.
In MSC.Nastran 2004R2 (Version 2004.0.4 and beyond) new options have been added
to the MATTEP entry that allows support for general temperature-dependent
stress-strain curves in SOL 600.
1-14397207
2004.0.4
C.Nastran 2004R2
SOL 600 - DMIG - DMIG Support added to MS
Support for DMIG entries in SOL 600 has been added to MSC.Nastran 2004R2
(Version 2004.0.4 and beyond).
1-14397801
2004.0.4
Elements - CWSEAM - Incorrect Stiffness
The hexa type stiffness matrix for the CWSEAM element is computed in the wrong
coordinate system and this will lead to an incorrect stiffness matrix and wrong
answers. The stiffness should be computed in the basic coordinate system
instead of element coordinate system.
1-14405601
2004.0.4
y give wrong answers
Static Analysis - RBE3 - Lagrange RBE3 ma
The Lagrange RBE3 will give wrong results if the reference dof=123 for SOL 101.
Avoidance: Specify 123456 for the reference degrees of freedom.
1-14405604
2004.0.4
cause diverging solution
SOL 400 - CBEAM, RBAR - CBEAMs with RBARs
If CBEAM elements are used with RBAR elements in SOL400 the solution may
diverge.
1-14405901
Error
2004.0.4
Restarts - DBLOCATE - UFM 477, Timestamp
The following dblocate restart run will result in USER FATAL MESSAGE 477.
Run1 : create a database.
Run2 : dblocate, copy the contents of run1 and restart creating run2 database.
Delete run1's database.
Run3 : dblocate run2's database. This causes a UFM 477 error saying there is a
timestamp error on run2.dball.
Avoidance:
1) Use autoasgn=3 in run3 and manually assign the dblocated database, or
2) I did a dbdict, endjob directly into run2's database (dbs=run2) before
deleting run1's database. This also avoids the error.
1-14410701
SOL 400 - Solution diverges with SPCD loads and linear rigid
elements for LANGLE=1,2 and SOL400.

For SOL400, the solution diverges if there are SPCD loads and linear rigid
elements in the deck for LANGLE=1, or 2. However, the solution will converge if
LANGLE=3.
1-14412401
2004.0.4
for concentrated masses
SOL 600 - GRAV, CONMi - No gravity loads
SOL 600 gravity loading does not produce any loads for the concentrated masses
(CONMi) in the Marc input deck.
1-14441104
ng Answers
2006 (MD R1)
Grid Point Strain - GPSTRAIN, CORDi - Wro
Grid point strains are wrong if they are requested with respect to a different
reference system than the element strains. The equivalent grid point strains
are always wrong.
Avoidance: Don't request grid point strains respect to a different reference
system than the element strains
1-14461909
2004.0.4
SUB - UFM 3046 in TRD1
Transient Analysis/Enforced Motion - STAT
If enforced motion is specified and STATSUB is also requested in SOL 108 or 109
then the job may fail with USER FATAL MESSAGE 3046
compile sedtran
alter 'call autosprt'
else $
equivx lll/lyy/-1 $
ompile sedfreq
alter 'call autosprt'
else $
equivx lll/lyy/-1 $
endif $
endalter
1-14469102
2004.0.4
ACMS - UFM DISJOINT SUPERELEMENTS EXIST
Large ACMS jobs may fail incorrectly with a message that complains about the
existence of "DISJOINT SUPERELEMENTS".
1-14480201
2004.0.4
in rotor dynamic module
Rotor Dynamics - ROTORG - Unbalanced load
In rotor dynamic analysis , if multiple unbalanced loads are applied to points

not in the a-set then loads will be ignored and wrong answers will result.
Avoidance: If multiple unbalanced loads exist, then make sure that all load
points are in the analysis(a) set.
1-14485401
2004.0.4
SOL 600 - BEGINBULK Causes Failure in tre
lpl.F
SOL 600 jobs may fail with an error in trelpl.F if BEGINBULK rather than BEGIN
BULK is entered.
1-14487301
2005
Documentation/QRG - ECHO
The 2004 release has new options for the PUNCH portion of the ECHO command. The
QRG description of this command has errors in describing the new options. The
PUNCH and NEWBULK describers should be changed as follows:
PUNCH: The entire Bulk Data will be written to the punch file.
the "in sorted form")
(i.e,. omit
NEWBULK: In SOL 200, a complete unsorted bulk data deck is written to the
punch file with updated design model entries. (i.e., change "complete and
sorted" to "a complete unsorted"
1-14502701
M 6833 (PNBREC)
Distributed Memory Parallel - DOMAINSOLVER - Poor Message, SF
A large solid model with 128,000 HEXA elements fails in SOL 103, geometry
domain parallel, dmp=8 with the following message:
SYSTEM FATAL MESSAGE 6833 (PNBREC):
ERROR: 0032-117 user pack or receive buffer is too small
Avoidance: This deck ran successfully with dmp=2 and dmp=4.
1-14523741
Results in xdb
2004.0.5
Post Processing - PARAM,POST,0 - Missing
A combine heat transfer and thermal stress analysis with param,heatstat,yes

will not write both the heat transfer and thermal stress results to the xdb or
op2 file for postprocessing. If using param,post, 0 to write results to the xdb
file, only the temperature result are obtained. If using param,post,-1 to
write the results to the op2 file, only the thermal stress result are obtained.
Avoidance: Apply the following dmap avoidance;
compile phase0
alter 'output2'(,-1)
if ( not(heatstat='yes' and aprch=' ') ) then $
alter 'output2'
endif $
alter 'ELSE IF ( (OGEOM=',''
ELSE IF ( (OGEOM='YES' OR OGEOM=' ') AND not(dmpop2) and
not(heatstat='yes' and aprch=' ') and
((POST=-1 or patplus='yes') AND PATVER>=3.)
) THEN $
endalter
1-14533901
2004.0.4
Optimization/Design Sensitivity - NEWBULK
- Incorrect/Missing Bulk Data Echo Output
The NEWBULK describer on the ECHO case control command enables punching of a
complete unsorted bulk data deck at the end of a SOL 200 run with updated
design model data. If the original input deck contains design model data that
has been input in free field form and has a continuation that has a comma in
column one, the updated design model data is followed by an incorrect punch of
the continuation line. Also, if the user has placed comments at the end of a
line of data that is included in the design model, the comment does not get
written to the punch file.
Avoidance: A blank can be inserted in front of the comma on the continuation
line and the correct behavior will result. Comments that are at the end of
design model entries must be moved to their own line if they are to be retained.
1-14556901
2004.5
Matrix Methods - param,inrel,-2 - Lagrang
e Multipliers, Incorrect matrix to factor diagonal messages
When Lagrange Multipliers are used, as in param,inrel,-2, calculations in SOL
101 and several other places, large matrix to factor diagonal matrix ratios may
be prined out and they may be in error.
Avoidance: If the "MATRIX/FACTOR DIAG. RATIO" is identical to the "MATRIX
DIAGONAL" they can be safely ignored. If the run fatals, param,bailout,-1
can be used to avoid the fatal error.
1-14568012
h file output
2008.0.0 (MD R3)
Acoustic Analysis - ACMODL - Corrupted pc
Acoustic analysis that specifies the CP method on the ACMODL entry may produce
a corrupted (skinout) punch file.
1-14576201
2004.0.4
roduce Wrong Answers in Acoustics
Distributed Memory Parallel - ACMS May P
Distributed Memory Parallel (DMP) with ACMS may produce wrong answers in
Acoustics.
Avoidance: Use serial ACMS.
Contact MSC for DMAP avoidance.
1-14593609
2004.0.4
ed to Marc Correctly
SOL 600 - PCOMP - Composites not Translat
Composites, PCOMP entries, are not tranlated by SOL 600 to the marc input file
correctly.
1-14595809
2005
onse, WTMASS, NLLOAD, imbalance
Rotor Dynamics - UNBALNC, transient resp
PARAM,WTMASS does not change the load vector (NLLOAD output) leading to wrong
answers.
1-14600924
2005.0.2
T,YES, READ, MAT4 - SFM 4276
Static Analysis - APP HEAT, PARAM,HEATSTA
SOL 101 with APP HEAT or PARAM,HEATSTAT,YES may fail in the READ module with
SFM 4276
This is possible if the bulk data entry MAT4 has specific heat or density.
compile phase1a
alter 'if ( rvrvd )'(,-1)

rvdam=false $
rvrvd=false $
endalter
1-14602401
2008.0.0 (MD R3)
if QUE= is specified
Submittal - SDIR must be write accessible
If MSC.Nastran is submitted with QUE=NAME, then the script checks that "SDIR"
is writable. In the case of QUEUES, a user may be on a headnode of a cluster,
and not have write access to SDIR on the headnode, but only on the compute
nodes.
Avoidance: The check does NOT occur if the job is run with NODE=node_name.
The check should not be there if there are queues as well.
1-14607302
2004.0.5
Performance - EIGRL, READ - When use_aio
is on, incorrect cpu reporting leads to poor performance
When use_aio=yes is specified in a Nastran 2004.0.0 on HPUX 64 platforms, it
may cause inaccurate and even negative cpu usage. This may cause additional
shifts in Lanczos and lead to poor performance. This problem has been fixed in
Version 2004.0.5 and later system by linking against corrected libraries from
HP.
1-14626001
2004.0.5
Aeroelastic Analysis - UFM 5259 (MAKAUMD)
In aeroelastic analyis UFM 5259 may be issued without any text.

Avoidance: The text should read:
*** USER FATAL MESSAGE 5259 (MAKAUMD)
UXVEC BULK DATA ENTRY WITH ID
ENTRY DOES NOT EXIST.
1-14627054
xx INVOKED BY A AEPRESS BULK DATA
Nonlinear - PELAST, Kn - Possible Wrong Answers
If the load deflection capability (Kn) is used with PELAST in a nonlinear

analysis, then the results may be incorrect. The results are dependent on the
connectivity order.
Avoidance: Use the CBUSH/PBUSH/PBUSHT instead. If the length is non-zero, the
orientation vector method must be used instead of the CD field
1-14629706
Nonlinear Analysis - TEMP(LOAD) - Wrong Intermediate Results
Hi:
This is a general limitation.
For nonlinear static analysis with thermal load, all intermediate data recovery
of stress and strain is not correcrt to "LINEAR" elements.
The definition of "LINEAR" elements including 2 groups of elements
(1) All elements have no nonlinear capability, such as CBAR, CSHEAR,..., and
(2) All elements have nonlinear capability but there is no geometrical or
material nonlinearity behavior applied to them.
Please also see 1-16331802.
Regards,
Fisher
========================
In nonlinear analysis, sol 106, using temp(load) stresses and nonlinear
strains are incorrect for intermediate output (intout=yes on nlparm entry).
This is true for MAT1 and MAT1/MATT1 using param,epsilont,secant which is the
default.
Avoidance: Use param,epsilont,integral and make alfa temperature dependent if
not already the case.
1-14639801
2004.0.4
, PBUSH - No Warning Message Issued
When an optimization job designs a PBUSH property using a positive FID on a

DVPREL1 entry that is not allowed, the program does not stop the process. The
subsequent result may not be reliable.
Avoidance: Use the property name instead. Such as K1 or B4.
1-14641801
2004.5
GPFDR - Error set durational processing
When multi-Subcase processing was introduced to GPFDR for durational

performance issues, the criteria used was the set number, not a validation to
the set content. This violate the Case Control Processing re-usage for set id
within the a Subcase section.
An avoidance is to use unique set identification related to the set content.
This will be correct in V2005.
1-14646106
2005
also uninstalls Nastran 2001.
Installation - Uninstall of Nastran 2004
Uninstall of Nastran 2004 also uninstalls Nastran 2001. This has been
corrected with version 2005.0 installation/uninstall. (cdp 12/09/04)
.
1-14651801
2004.0.5
ontinuation cards
SOL 600 - RBE3 has a limit of about 450 c
For SOL 600 the RBE3 has a limit of about 450 continuation entries. Some
models mave large RBE3's that exceed this limit. For such models, a memory
over-run occurs and bad data is written to the appropriate section of the Marc
input deck
1-14651804
mance Problem
2004.0.5
SOL 600 - TEMP(LOAD), TEMP(INIT) - Perfor
SOL 600 has a performance problem for large models with thermal loading. This
occurs when TEMP(INIT) and TEMP(LOAD) are entered. On some computer systems,
such as Linux, the performance penalty is very small. On others, such as HP,
the performance penalty is large. This is caused by I/O that can be performed
in a different way. For the large where this error was discovered, the run
took more than 60 minutes to create the model on HP when it should have only
take a couple of minutes. The problem has been fixed in Nastran 2004.0.5 on
the Nastran 2004r2 cd.
1-14667001
rong Answers
2004.5
Elements - NSM1, PSHELL - Missing mass, W
The NSM1 command does not work on shell elements.

Avoidance: User the NSM or NSML2 commands.
1-14674804
Optimization/Design Sensitivity - CWELD - Projection not upda
ted, Poor Answers, Poor Convegence
A projection is made between the diameter of a CWELD element and its associated
shell elements to keep the symetrical connection between the weld and the shell
elements. The procedure is implemented by MODGM2 and carried out in the IFP
stage.
As the diameter of a CWELD element is designed during the optimization phase,
the projection of the CWELD needs be updated. Secondly, if the grid locations
of shell elements are designed, the projection of weld and shell elements also
needs to be updated during the design cycle. Therefore, the modgm2 module
should be included in the design cycle.
1-14717802
2004.5
or performance in wilvecd
Eigenvalue Analysis - EIGR, GIV, HOU - Po
Householder and Givens eigenvalue methods may get poor performance on HP and
Linux IA64 systems.
1-14720908
2005.0.2
Optimization/Design Sensitivity - OUTPUT4
- Extra records in the output4 dscm2 datablock
The rayleigh quotient approximation used for eigen/freq responses in SOL 200
results in three columns in the DSCM2 matrix for each response. When these
results are printed to the .f06 file, these additional columns are stripped off
but when they are written to a file using OUTPUT4, they are still there.
Avoidance: This alter moves the partitioning of the DSCM2 matrix so that is
applies to the OUTPUT4 requests as well.
COMPILE EXITOPT $
alter 'sdsc'
IF (RQANO) THEN
$
$ REMOVE SPAWNED GENERALIZED STIFFNESS AND MASS DSA FROM DSCM2
$
PARTN DSCM2,MRQA,/DSCM2NGS, DSCM2GS,,/1 $
EQUIVX DSCM2NGS/DSCM2/ALWAYS $
endif $
alter 'rqano'(3),'rqano'(3,3) $
endalter
1-14762201
pported
2004.0.5
SOL 600 - Marc CONTROL block 3a is not su
The SOL 600 Marc CONTROL block 3a is not supported. This was intentional in
SOL 600 versions before Nastran 2004.0.5 because some version of Marc did not
support it. This is only important if different tolerances for displacment and
residual are needed.
1-14762903
2005.0.2
ements - Slow Convergence

If an eigenvalue optimization task contains superlements and SCR=NO is used,
convergence to the optimum design will be slowed due to incorrect sensitivity
calculations in the DOM9 module. This only occurs if the Rayleigh quotient
approximation is used in the approximate optimization task for the eigenvalue
response.
Avoidance: Apply the direct (ATTB=1) or inverse (ATTB=2) approximation
technique for the eigenvalue response or insert the following alter:
compile desopt
alter 'cdelk,cdelm,cdelb'(3),''
delete /cdelk,cdelm,cdelb,delgs,delgm $
1-14763501
inate System
2004.0.5
Elements - QUADR - Incorrect Output Coord
The default stress/strain output coordinate system for QUADR is not the one
defined in Quick Reference Guide. It is the material coordinate system with
theta=0.0.
1-14777101
2004.5
SFM 4276 (READ) EC 3021 (DPD)
Large Problems/Frequency Response - DPD -
Very large SOL 111 jobs may fail with the message:
SYSTEM FATAL MESSAGE 4276 (READ) ERROR CODE 3021 (DPD)
1-14777104
2004.0.6
evice, job does not abort
Miscellaneous - linux, no space left on d
On linux systems, if there is no space left on device, the job does not abort
and the job may hang.
1-14779931
2005
to converge or wrong answers
Nonlinear Analysis - plasticity - Failure
In nonlinear analysis, sol 106, Nastran does not handle a hardening slope
change after the 1st hardening slope in plasticity analysis. This may lead to
a failure to converge or wrong answers.
1-14813801
2004.0.5
6 (QMATR) Unable to locate datablock dtos2j with
The message:
SYSTEM FATAL MESSAGE 6296 (QMATR) unaable locate datablock dtos2j attribute
dptye: xxxx
may occur if the bulk data file contains a mixture of DVPRELi, DVMRELi and
DVRELi entries and the DESVAR case control command is used to select a set of
design variables that do not includ any of a partcular property type.
Avoidance: Either remove the unneeded DVxRELi entries or include a DESVAR that
references each property type or apply the folowing dmap alter when DVMRELi's
are the unneeded entries and the deck contains needed DVPRELi's and DVCRELi's.
A similar dmap can be constructed for other scenarios:
compile predom
alter 'dopr1 '
message //'protyp = '/protyp $
$ For the case of all the DESVARs referenced on DVMREL1 entries are NOT
selected by DESVAR command
protyp = 3
$ For the case of all the DESVARs referenced on DVPREL1 entries are NOT
$protyp = 7 - 1
$ For the case of all the DESVARs referenced on DVCREL1 entries are NOT
$protyp = 7 - 2
1-14817201
2004.0.5
SOL 600 - Not all values for SOL 600 Marc
's AUTO INCREMENT are properly translated
Not all values for SOL 600 Marc's AUTO INCREMENT are properly translated form
NLSTRAT AIxxxxx entries.
Avoidance; Other than manually editing the marc input file there is no
avoidance.
1-14860909
2004.0.5
Nonlinear Analysis - CBUSH with local coo
rdinate systems cause convergence problems
A nonlinear analysis with CBUSH elements with their grid points defined in
local coordinate system may have convergence problems. with bushes that have
their grid points defined in loc
Avoidance: The displacement coordinate systems for points connected by cbush
elements in an nonlinear analysis should be the same.
1-14861414
2004.0.6
Rotordynamics - RSPINR, ROTORDR2 - Floati
ng Point Exception or Missing Message
If the SPEEDi
as an integer
error message
any messages.
exception.
field is defined incorrectly on the RSPINR entry (e.g., defined

instead of a real), then depending on the machine, the proper
may not be issued. On some machines, the job may stop without
On other machines, the job may stop with a floating point
Avoidance: Correct the offending entry.

1-14895708
2004.5
ated when model consists of on CBARs
SOL 600 - CBAR - Null OUTPUT2 file is cre
The SOL 600 t16op2 translator (outr=op2 option) requires that elements with
stress and strain be present. If a model consists entirely of CBAR and CBEAM
elements that only generate internal forces, the generated op2 file will be
null and the following message will be written to the f06 file:
*** SYSTEM FATAL MESSAGE 6551 (INPTX2)
0
0*** FATAL ERROR.
0
NO. FORTRAN RECORDS READ =
0
NO. FORTRAN WORDS READ =
0
0FATAL ERROR
1-14923601
2004.0.5
Optimization/Design Sensitivity/DMP - SOL
200 w/DMP Fails due to DISUTIL non-execution
A SOL 200 job with DMP, DOMAINSOLVER MODES (part=dof) failed due to
non-execution of a DISUTIL call on the master. The non-execution was caused by
the restart logic (sys109).
1-14928501
Part Superelements - TOL on SEBULK and SECONCT entries uses S
QRT(TOL) instead of TOL
For Part Superelement connections via SEBULK or SECONCT, the TOL field defines
the SQRT of the search distance instead of the linear search distance.
1-14932102
2004.0.5
l SE - SFM 4276
Optimization/Design Sensitivity - Externa
In a SOL 200 optimization analysis run with external superelements and shape
design variable, the job may fail in the 2nd design cycle with the following
messages:
*** SYSTEM FATAL MESSAGE 4276 (PACK)
ERROR CODE
105 PID= 0
Avoidance: Insert the following DMAP alter
$
compile update,list $
alter 'dbstatus selist'(,-1) $
alter 'if ( noselist',''(,1) $
if ( noselist<1 or rsonly or (noselist>=1 and zuzri1>0) ) then $
if ( begsup or (noselist>0 and zuzri1>0) ) then $
$
compile desopt,list $
alter 'call update'(,-1)
$
zuzri1 = shapeopt $
1-14949104
2005
- MODTRK - UFM 6458
Distributed Memory Parallel/Optimization
A DMP optimization job that requests mode tracking will fail in module MODTRK
with UFM 6458 (MTD0RD) complaining the requested mode does not exist.
compile fea list
alter 'IF ( MODETRAK>0 ) then',''
IF ( MODETRAK>0 and PROCID <= 1 ) then
alter 'IF ( MODETRAK>0 ) then'(2),''
IF ( MODETRAK>0 and PROCID <= 1 ) then
$
COMPILE moders list
alter 'disutil lama'(2,-1)
putsys(1,109)
alter 'disutil lama'(2)
putsys(0,109)
$
$
1-14970010
2004.0.5
Optimization/Design Sensitivity - DRESP2s
, DRESP1s span subcases - UFM 6553 (DOPR3M 6553 (DOPR3R)
SOL 200 job with DRESP2 refers to DRESP1s that span the subcases and weight or
volume will fail with ufm 6553 iin DOPR3R.
Avoidance: remove dresp1 ID for weight from DRESP2 if possible
1-14976512
Postprocessing - PARAM,POST,0 - xdb file missing pressure and
decibel results.
Acoustic pressures and decibels are not available in the xdb file.
Avoidance: Use the op2 file for pressures.
files are in attachments
Note data is in the xdb, this is a DRA issue or a design change in complex
eigtnalues.
1-15000431
es
Nonlinear Transient Analysis - CBUSH - Incorrect Element Forc
If Field 6 of the TSTEPNL is set to AUTO, the element forces for the CBUSH
element with PBUSHT will be incorrect in a SOL 129 run. Note that the AUTO and
TSTEP methods have been de-documented after version 70.5. Also SOL 109 yields
correct results for the test case.
The element forces are correct when using the ADAPT (default) method.
1-15002802
2004.5
sure Loads, Wrong Answers
SOL 600 - PLOADi, CPENTA - Incorrect Pres
SOL 600 pressure loads are applied to the wrong face ID in the Marc deck for
CPENTA elements.
1-15004301
2ed)
2004.5
Spotwelds - CWELD, ELPAT - UFM 7549 (mdg
A model with CWELD elements and curved shells may fail with the message:
USER FATAL MESSAGE 7549 (MDG2ED)
This error is caused by tight projection tolerance. In v2004 the default
projtol is set to 0.0 to avoid picking wrong elements for PARTPAT format. The
zero tolerance works for flat shells, but it causes errors for some curved or
warped shells.
Avoidance: Insert swldprm,projtol,0.01 to set the projtol to 1%. The default
projtol will be changed in version 2005 from 0.0 to 0.01. Note that the
projection tolerance in v2001 was set to 10% which was excessively large.
1-15028201
2004.0.5
Optimization/Design Sensitivity - HAT1 Incorrect sensitivities for end B responses
The HAT1 beam section type computes incorrect values for the sensitivity of
responses that are a function of the END B dimensions.
Avoidance: Substitute a HAT section type or do not use the tapered feature of
the HAT1.
1-15056901
2008.0.0 (MD R3)
R - Misleading Error Msg for ACMS w/ NUMDOM=1
Specifying NUMDOM=1 on the DOMAINSOLVER command, with ACMS, leads to an unclear
error message:
UFM 3200 (SEQP)
LOGIC ERROR DETECTED BY SUBROUTINEC2FREE
1000 = LOCATE CODE OR VALUE.
.
1-15068202
2004.5
Miscellaneous - Compaq Alpha v5.1a-5.1b SFM 4276 (tbk) EC 7777 on Compaq Alpha
A bug exists in V5.1a-b of the Compaq Alpha Unix operating system which may
cause the floating point stack to be corrupted. This may cause a traceback in
any version of MSC.Nastran and potentially could cause wrong answers.
All
clients must apply the 5.1B-1 patch.
Avoidance: This error will be marked fixed in V2005 even though there is
nothing MSC can do to fix the error.
1-15103324
ages
2005
ACMS - WELD - Job terminates without mess
If ACMS is used in a model with WELD element, the job may terminate in PHASE0.
The following messages may appear in the f04 or f06 file:
ACMS PHASE 0 BEGN
Avoidance: For some problems, the following system cells modifications
corrected the problem
NASTRAN BUFFPOOL=500
For SOL 103, GDMODES also avoided this error
1-15107501
2004.5
SOL 600 - Parallel, memory allocation bug
puts elements in the wrong domains - Wrong Answers
SOL 600 Parallel has a memory allocation bug which puts elements in the wrong
domains. This leads to Marc aborting or wrong answers.
1-15113501
- UFM 6144
2004.0.6
Eigenvalue Analysis - SOL 103, MPCforces
If MPCforces are requested on a subset of points in SOL 103 then the job may
fail with SFM 6144.
Avoidances: Request MPCFORCE=ALL or insert PARAM,SPARSEDR,NO or insert the
compile sedisp
alter 'CALL CFORCE USET,GM,UG,UH1',''
CALL CFORCE USET,GM,UG,UH1,MMG,M2MG,BMG,B2MG,KMG,K4MG,K2MG,,
PM,OLX,,/
QMG/
1-15130911
FM 9158
2004.0.6
Eigenvalue Analysis - zero c-set mass - S
If SYSTEM FATAL MESSAGE 9158 is encountered due to zero c-set mass, then the
run may not terminate immediately but instead proceeds to the next
superelement.
compile mhred
alter 'error'(2),''
endalter
1-15141101
2004.0.6
t can cause incorrect solution
Rigid Elements - PARAM,AUTOMSET - automse
PARAM,AUTOMSET can select the wrong o-set which can lead to wrong answers.
1-15150301
2004.0.6
ACMS/Optimization/Design Sensitivity - D
VCRELi, DVMREL1 - SFM 4276, EC 3021 (DSAL)
In a superelement optimization including acms optimization job, if the DESVARs
are only referenced by DVCRELi or DVMRELi entries, the job may fail
unexpectedly with SYSTEM FATAL MESSAGE 4276, ERROR CODE 3021 in the DSAL
module. This is caused by a missing EDOMS table from module SDSA.
Avoidance: Add a dummy DVPREL1 entry as show below.
Assuming the job has a PSHELL 100 with the thickness = 2.0
DESVAR
1010
DUMMY
2.0
2.0
2.0
DVPREL1 9999
PSHELL
100
T
1010
1.0
1-15159405
2004.0.6
GIV, HOU - UNPACK error in DSAH2
If an optimization analysis has a DRESP1 entry that request an EIGN or FREQ

response for a mode number whose eigenvalue has been extracted but whose
eigenvector has not been calculated (e.g, the eigenanalysis was performed using
GIV or HOU up to a specified frequency) the job may fail with an UNPACK error.
in DSAH2.
Avoidance: Check to see if eigenvectors have been extracted for all the mode
numbers invoked on a DRESP1 entry (i.e., that there are non-zero generalized
mass and stiffness values). If they have not, either discard the DRESP1
request or modify the EIGR entry to extract more eigenvectors
1-15168101
2005
- Write operation tried to write a record that was too long
A SOL 200 job on sgi irix that was writing a long DSAPRT record failed with the
message "Write operation tried to write a record that was too long".
1-15182901
2004.5
- No message when modes are referenced that do not exist
If the user requests an eigenvector response on a DRESP1 entry that designates

a mode number that is higher than the number of modes extracted, the request is
ignored. This is regarded as an error in the design of the eigenvector
sensitivity calculation and the code is to be changed to make this a USER FATAL
MESSAGE.
Avoidance: There is no avoidance, the burden is on the user to make sure
referened modes exist.
1-15214414
gnal 15 Error
2005
DMP - MDMODES, EIGRL - Hang in SEMR2, Si
If distributed memory parallel (dmp) mdmodes job is executed but f2 on the

eigrl entry is not specified, the job may hang in SEMR2 or fail in various ways
including a signal 15 error on HPUX Itanium.
Avoidance: Specify f2 on the eigrl entry. In Version 2005 and beyond this
condition is trapped with a user fatal message.
1-15217604
r large models
2005
SOL 600 - Excessive Memory is Required fo
Excessive memory is required for large SOL 600 model.

1-15238701
2005
DESVAR - UFM 7008
Optimization/Design Sensitivity - DLINK,
If a DLINK entry references DESVAR entries that are not selected by a DESVAR
command, the program issues USER FATAL MESSAGE 7008 (THE NUMBER OF DLINK
ENTRIES EXCEEDS THE NUMBER OF DESVAR ENTRIES.
USER INFORMATION: THE NUMBER OF DEPENDENT DESIGN VARIABLES MUST BE LESS
THAN THE TOTAL NUMBER OF DESIGN VARIABLES).
Avoidance: Remove the offending DLINK entry from the input file.
1-15242901
2005.0.2
EFFMASS - UFM 5423
Acoustic (Fluid Structure) Analsysis - M
A fluid-structure model job with an MEFFMASS Case Control request fails with
UFM 5423 (Attempt to multiply incompatible matrices) in the EFFMAS module when
it is performing modal effective mass calculations for the structure.
compile modefsrs
alter 'EFFMAS CASEs,MsAA,PHsA,',''
merge msaa,,,,vafs,/msaa1 $
merge phsa,,,,,vafs/phsa1/1 $
EFFMAS CASEs,MsAA1,PHsA1,LAMAs,USET,BGPDTS,,
CSTMS,vsgq/
EFMFSMs,EFMASSs,RBMASSs,EFMFACs0,MPFACs,
MEFMASs,MEFWTs/
0/WTMASS $
endalter
1-15245201
s
2004.5
Acoustic Analysis - EPOINT - Wrong answer
If EPOINTs are specified in a fluid-structure model and some of the structural

grid points in the a-set are numbered higher than the fluid grid points in the
a-set then the results will be wrong.
compile gma
alter 'GKAM
MERGE
GKAM
USETD,PHSA,',''
PHSA,,,,,VAFS/PHSAF/1 $
USETD,PHSAf,mis,lamas,DIT,M2SS1,B2SS1,,CASES,lammats/
MSHH0,B2SHH0,K1SHH,PHDSH0,MODELSTS,modselsv,LAMASN/
NOUE/LMODES/lfreq/hfreq/-1/-1/-1/0/S,N,FMODE/
KDAMP/false//APP $
endalter
1-15247204
2004.5
SOL 600 - SOL600,106 - Error number 1030
Models that run successfully in SOL106 may fail when using SOL 600,106 when
QUAD4 elements exist that are translated into the uu plane.
1-15251748
swers
2004.5
Rotordynamics - RGYRO, UNBALNC - Wrong An
If RGYRO with UNBALNC are included in the static subcase, the nonlinear
transient response subcase will calculate different answers on different
machines.
1-15269705
nd 4278
2005
Superelements - PARAM,CONFAC - UFM 4277 a
PARAM,CONFAC specifies the tolerance factor used in checking the congruence of

the location of the boundary points between image superlements. In some models
USER FATAL MESSAGE 4277 (SEP1ED)an d USER FATAL MESSAGE 4278 may be issued
indicating that the tolerance has been exceeded when in fact it hasn't.
Avoidance: An unrealistically large value of PARAM,CONFAC for example 1.0,
may need to be specified to avoid the fatal message.
1-15278401
Answers
2004.5
SOL 600 - CBEAM - Offsets Ignored, Wrong
SOL 600 beam offsets are sometimes ignored and not reflected in the SOL 600
marc input deck.
1-15279201
2005
on on Windows V2004
Elements - CWELD - Floating Point Excepti
Client model with CWELD elements that runs successfully on other platforms
fails with a floating point exception on Windows Verison 2004. The problem is
resolved in Version 2005.
Avoidance: Other than using Version 2005 or running on a different operating
system, there is no known avoidance.
1-15279901
2004.5
complex matrices
DMAP - MATMOD(21) gives wrong answers on
Matmod option 21 converts a sparse factor matrix from the DCMP module into 3
true matrices.
When multiplied together properly they reform the input matrix to the DCMP
module.
The true matrices are easier to understand than the packed factor, where they
are all in one data block.
True matrices can be input to any matrix processing module, but the packed
factor cannot.
The option 21 has been demonstrated to behave well on real matrices. It can
give wrong answers on complex matrices.
Avoidance: No avoidance is known.
1-15287606
Superelements/Dynamics - SPCD - Wrong answers
If enforced motion (SPCD) is applied to a superelement's interior points in

dynamic analysis then the results will be wrong.
Avoidance: Assign the SPCD points to the residual structure.
1-15297201
2005.0.2
Transient Response - MAXMIN - PARAM,POST,
-1 or 2, PARAM,OUGCORD,BASIC - SFM 5423
If a modal transient response requests MAXMIN output, the solution may fail
with the following error:
The error will occur for the following conditions:
1. Either PARAM,POST,-2 or both PARAM,POST,-1 and PARAM,OUGCORD,BASIC are
defined
2. Modal transient (SOL 112)
3. Coordinate systems are present in the model
4. PARAM,MODACC<0 (default)
ECHOOFF $
COMPILE SEDRCVR NOLIST $
ALTER 'MPYAD
TRANSG'(,-1) $
IF ( SORT2MM ) THEN $
TRNSP UG/UGTX$
EQUIVX UGTX/UG/-1 $
ENDIF $
ENDALTER $
$
COMPILE SUPER3 NOLIST $
ALTER 'MPYAD
TRANSG'(,-1) $
TRNSP UG2/UGTX$
EQUIVX UGTX/UG2/-1 $
ENDIF $
ENDALTER $
ECHOON $
Example files attached. Details available in activity...Mark R
1-15305906
FM
2004.5
Nonlinear Analysis - NLITER - Signal 8, S
Nonlinear analysis may fail in the NLITER module and issue a SYSTEM FATAL
MESSAGE 4276 indicating an overflow or a SIGNAL 8 error.
Avoidance: This error occurs because some error tolerance calculations are
performed in single precision, modifying the convergence criteria on the nlparm
entry may help avoid this problem.
1-15309511
2004.5
Spot Weld Element - CWELD - UFM
When two or more CWELD elements that have angles that fail the tolerance test,
nastran aborts after reporting the first element and fails to check and report
on any other elements.
Avoidance: Set CHKRUN to 1 on the SWLDPRM entry.
1-15323213
2005.0.2
EAS universal file
SOL 600 - Not writing displacements to ID
SOL 600 does not support writing output output to the IDEAS universal file.
Beginning in v2005r2 this output may be obtained by using MARCIN to specify
Marc's SDRC option. For example:
MARCIN,0,0,SDRC,40,3
1-15334301
4276 EC 31
2004.5
Heat Transfer - UFM 4551 followed by SFM
If a heat transfer job fails to converge (USER FATAL MESSAGE 4551) may be
followed by SYSTEM FATAL MESSAGE 4276 (GETCOL) ERROR CODE 31 because matrix
IFSH has an incorrect trailer.
1-15340905
issing Output
2004.5
Postprocessing - CWELD, PARAM,POST,-1 - M
The op2 file generated in MSC.Nastran Version 2004 using param,post,-1 can not
be used to postprocess CWELD element results in Patran
1-15341502
2004.5
DMAP - MODTRL - SFM 4276 EC 31
User DMAP errors may result in the following fatal message:

*** SYSTEM FATAL MESSAGE 4276 (GETCOL)
ERROR CODE
31 PID= 0
*** USER INFORMATION MESSAGE 4276 (GETCOL)
that identifies the routine GETCOL even though the problem routine is GTIDMC.
1-15352406
Complex eigenvalue - Eigenvalue Output not Sorted
The complex eigenvalues have been sorted by magnitude by default since version
70.7.
The eigenvalues will be sorted by frequency when SYSTEM(108)=65536.
In a complex eigenvalue analysis, the output should be sorted by frequency.
However, for some modal complex eigenvalue problems the output is not sorted
and is output in a random order.
1-15372203
2005.1
Data Recovery - STRAIN, PCOMP - UFM 3005
(SDR2)
Similar to error report q1-8126205 which reported that UFM 3005 occurs when
STRESS(CORNER) is requested with composites, it has been found that a request
for STRAIN(CORNER) output which should be ignored for composite elements, will
lead to the messages:
*** USER WARNING MESSAGE 6418 (SDR2A)
THE BILIN OPTION FOR STRESSES OVERRIDES ALL OTHER OPTIONS IN STRAIN AND
FORCE COMMANDS.
ATTEMPT TO OPERATE ON THE SINGULAR MATRIX (NONE) IN SUBROUTINE SQD43D
Avoidance: Limit the strain request to non-composite elements by specifying a
SET.
1-15378701
2005
Installation - Using 'this_host' on SERVE
R line of the license file prevents installer from working
This issue has been resolved. (BNC)
If the host name on the SERVER line of a FLEXlm license file is set to
'this_host', lmstat does not return the correct vendor daemon status. The
Nastran installer relies on correct operation of lmstat. This error will cause
the installer to assume no nastran licenses are being served.
This problem has been reported to Marcrovision.
Avoidance: Change the host name on the SERVER line to a valid host alias for
the target system.
The Macrovision problem id is P7078: lmstat -a fails to report vendor daemon
status when run "remotely"
1-15388102
2005.5
ion, UFM 614 (IFP1D)
Case Control - K2PP, K2GG - Access Violat
A K2PP or K2GG case control request that applies factors that requires more
than a single line of input such as:
k2gg = 1.*k1,2.*k2,3.*k3,4.*k4,5.*k5,6.*k6,7.*k7,8.*k8,9.*k9,
10.*ka,1.*kb,1.*kc,1.*kd,1.*ke,1.*kf,1.*kg,1.*kh,
1.*ki,1.*kj,1.*k0,1.*kk
May fail with an access violation or issue the following fatal message:
USER FATAL MESSAGE 614 (IFP1D)
Avoidance: The only avoidance is to use DMAP to combine the matrices or
combine them outside MSC.Nastran.
1-15388155
, EC 30, TRD
2005
Rotordynamics - RGYRO, STATSUB - SFM 4276
Rotodynamics models, RGYRO, with static subcases in transient analysis may fail
in the TRD1 module with SYSTEM FATAL MESSAGE 4276 ERROR CODE 30.
1-15398609
r lapack method
Eigenvalue Analysis - CDMAPi - SFM 3008, Insufficient core fo
In eigenvalue analysis (SOL 103, 111, 112) a model with a lot

elements may fail with insufficient core during the Housholder
even though a significant amount of memory is requested.
The
solution is used during the residual vector calcualtion and the
dampers affects the size of the problem.
of damper
Eigensolution
HOU eigenvalue
number of
Avoidance: Specify RESVEC(NODAMP)=YES or pply the following alter with

param,resvec,no.
compile phase1a $ only use when RESVEC=NO
alter 332 $ 2004.0.0
beigrd = false $
rvdam = false $
endalter $
For sols 103 and 111 with RESVEC=YES (in 111 default) param,resmeth,lan should
work.
1-15399501
2005.0.2
EPOINT - SFM 6144 (PARTN1)
Dynamics - MCFRACTION in the presence of
In a modal transient or frequency response analysis, if the model contains one

of more EPOINTs (lagrange multiplier, for example) and the case control has an
MCFRACTION request, the solution will fail with the following message:
SPECIFICALLY:
where matrix RPHMC0 has more rows that VMCFG
ECHOOFF $
COMPILE FDRMGEN NOLIST $
ALTER 'DELETE .*VAD,VGP','' $
MERGE VMCFG,,,,,VGP/VMCFGX/1 $
EQUIVX VMCFGX/VMCFG/-1 $
DELETE /VAD,VGP,IEE,, $
ENDALTER $
ECHOON $
1-15422604
2004.5
Segmentation Violation
When a large scale optimization job (having million DOFs) takes the non-adjoint
path, the job may fail in DSVG1 with a segmentation violation.
Avoidance: Specify as large a mem as possible.
1-15426513
2005.0.2
Restarts - RESTART, MODTRL - Attaching a
read only database may lead to fatal error in MODTRL.
Dynamic restarts may be inefficient and SubDMAPs PHASE1A. PHASE1DR, GMA and
FREQRS may be executed unnecessarily. Furthermore, if the cold start database
is attached read-only a fatal error may be issued in the MODTRL module.
Avoidance: Insert the following DMAP alter in your cold start run:
compile gma
alter 'ENDIF \$ fastfr='(,-1)
else $
xfastfr=false $ for restart efficiency
endalter
Or insert the following alter in your restart run:
compile gma
alter 'modtrl.*bdd'(,-2)
dbstatus bdd//s,n,nobdd $
alter 'modtrl.*bdd',''
if ( nobdd<1 ) modtrl bdd////6 $
alter 'modtrl.*k4hh'(,-9)
if ( false ) delete /k4hh,,,, $
dbstatus k4hh//s,n,nok4hh $
alter 'modtrl.*k4hh',''
if ( nok4hh<1 ) modtrl k4hh////6 $
endalter
1-15432813
2004.5
(MHRED), UFM 9032 (ERRPH1)
Component Mode Synthesis - CSET -SFM 9158
MSC.Nastran 2004 may fail with the message below and setting param,zrocmas,yes
as suggested in the message may not avoid the error. This problem is
demonstrated with tpl deck edr2n on the Cray SV1 platform but it could occur on
other systems as well.
^^^ SYSTEM FATAL MESSAGE 9158 (MHRED)
^^^ THE C-SET FLEXIBILITY MATRIX IS SINGULAR.
^^^ USER ACTION: SPECIFY PARAM,ZROCMAS,YES TO REMOVE THE MASS ON THE C-SET
DURING COMPONENT MODES.
Avoidance: In addition to param,zrocmas,yes insert param,fzero,XXX where XXX
is a real value just below the lowest flexible mode and above all "rigid body"
modes. This causes the correct rigid body modes to be used for inertia relief
supports in the autosprt subdmap. Other avoidances are to add the parameters:
param,mhred,no and param,respath,old
or
param,mhred,no and param,fzero,xxx
1-15449956
with UFM 5423
External Superelements - RELEASE - Sparse Data Recover Fails
An external superelement created by reading MAA and KAA with INPUTT4 and
storing on the database fails in MPYAD during sparse data recovery with UFM
5423 when RELEASE entries are included.
Avoidance: Specify PARAM,SPARSEDR,NO or removing the RELEASE entries.
1-15463011
translator
2005
SOL 600 - TEMPD is not recognized by the
In SOL 600 TEMPD is not recognized by the translator.

missing temperature loads and wrong answers.
This will lead to
Avoidance: The only avoidance is to specify the initial temperature on TEMP
entries.
1-15466201
n Fault
2004.0.6
Installation - RedHat AES 3 - Segmentatio
When MSC.Nastran is submitted on an IA64 system with the RedHat AES 3

opterating system, the following message will appear:
Segmentation fault (core dumped)
Avoidance:
Download the new "nastran" driver from ftp.mscsoftware.com and place in
$MSC_BASE/msc2004/linux64/nastran
1-15474215
2005.5
SOL 400 - NLRESTART - SFM 1032 when NLR
ESTART refers to load step that doesn't exist.
A fatal error will be encountered in a SOL400 restart if the Case Control
command 'NLRESTART SUCASE 1 STEP 2' is used and there is only one step in the
cold start.
*** SYSTEM INFORMATION MESSAGE 482 (LCDRVR)
NO DATA HAS BEEN LOCATED ON THE MASTER DATABASE.
0*** SYSTEM FATAL MESSAGE 1032 (XIO)
ATTEMPT TO READ PAST END OF DATA
Avoidance: This problem can be avoid by using the case control command
'NLRESTART' or 'NLRESTART SUBCASE 1 STEP 1 LOADFAC 1.0'
1-15477101
Wrong Answers
2005
Nonlinear Analysis - TEMP(INIT), PCOMP -
For nonlinear analysis of temperature dependent composite materials, the

initial stiffness matrix should be computed based on the initial temperature
referenced by Case Control command TEMP(INIT)=N. However, for Version 2004, the
initial stiffness matrix is computed based on the TREF on the bulk data entry
PCOMP. This is wrong.
1-15487601
2004
_2.2, Itanium, IA64, SGI Altix
RedHat AES 3, Propack 3.0 - CRASH - GLIBC
If V2001 of MSC.Nastran for Itanium Linux is run on RedHat AES 3, then the
following error will occur:
analysis: relocation error: $MSC_BASE/msc2001/linux64/analysis: symbol
_dl_loaded, version GLIBC_2.2 not defined in file ld-linux-ia64.so.2 with link
time reference
Avoidance: The problem has been corrected in a special build that is to be
made available on the external web at:
This dowload must be applied to a full 2001R4 (a.k.a. version 2001.0.9)
installation. I addition the following environmental varibles must also be
set on SGI Altix for all releases, serial and dmp, prior to 2005r2:
setenv LD_ASSUME_KERNEL 2.4.19
setenv LD_PRELOAD /usr/lib/sgi-compat-preload.so
The build date of this system is February 19, 2004. Download analysis.aes3,
place in $MSC_BASE/msc2001/linux64, and submit with "proc=aes3". A new nastran
driver is also required and is included in the download.
Please note that there have been a subsequent release of v2001r4 (a.k.a
2001.0.9) with performance improvements for Altix Itanium users. The latest
2001 system for Altix is also available at the product update site. It is
executed with proc=sgi. These systems do not support dmp under AES3 or
Propack 3.0. Like all other 2001 Linux IA64 releases, these updates are
statically linked with LAM 6.5.6 and will not support DMP under RedHat AES3 and
Propac 3.0.
LAM 7.0 , which is not used until the version 2005 release,
is needed to support dmp for AES 3 and Propac 3.0. A special 2004 SGI Altix
only Linux IA64 release which supports dmp under Propack 3.0 is available from
the product update site. Please also see quality 1-16270201.
1-15497401
2004
ens checked out.
Licensing - SMP - UFM 3060, Excessive tok
The special release of MSC.Natran 2001.0.9 for Linux IA64 that added support
for ffio with title page date of November 19, 2003 contains a licensing error
that causes the executable to search for a SMP (shared memory parallel) license
during every execution.
Avoidance: This error has been corrected in a special release of 2001.0.9 with
title page date of January 26, 2004. This system may be obtained from MSC's
external software update web site or the user can revert back to the standard
Linux IA64 2001.0.9 system that does not support ffio.
1-15502121
3012
2004.5
Spotwelds - Missing UFM 7549, SFM 4276 EC
Models with spot welds that should fail with the message:
USER FATAL MESSAGE 7549 (SEPWLD)
indicating that the projection of GS GRID ID=xxxxx onto the surface cannot be
found or lies outside the plane, may fail to issue this message and isntead
fail with SYSTEM FATAL MESSAGE 4276 (QOPEN) EC 3012.
1-15518520
2004.5
ceback in AMSMI2
Miscellaneous - ADAMSMNF - Cray Only, Tra
Some adamsmnf jobs that create an Adams modal neutral file may fail in Version
2004.0.6 on Cray SV!
Beginning of
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Called from
Traceback:
line 42 (address 13710276a) in routine 'TRBK'.
line 112 (address 55361c) in routine 'sysrcv'.
address 13740534a in routine 'AFSMI2'.
address 15101264b in routine 'AFGMNF'.
line 136 (address 15077120c) in routine 'XSEM16'.
line 133 (address 54500d) in routine '$SEGCALL'.
line 133 (address 225677b) in routine 'XSEMDR'.
line 66 (address 63175b) in routine 'NASTMON'.
line 379 (address 1372d) in routine 'MAINAL'.
line 343 (address 54455d) in routine '$SEGRES'.
line 343 (address 12005663d) in routine '$START$'.
End of Traceback.
1-15525703
2005
order dependent
Data Recovery - MAXMIN(DEF) results are
If a MAXMIN(DEF) definition for a MAGnitude (either Translation or Rotation)

follows a MAXMIN(DEF) for a specific component (i.e. T3), then the reported
MAGnitude results will all be zero. If the order of the MAXMIN(DEF)s are
reversed (MAG first, then component) the results are correct.
This order gives zeros for the MAGT results:
MAXMIN(DEF) ACCE T3
MAXALG=2
MAXMIN(DEF) ACCE MAGT MAXALG=3
whereas this order does not:
MAXMIN(DEF) ACCE T3
MAXALG=2
MAXMIN(DEF) ACCE MAGT MAXALG=3
1-15525713
ong Answers
2004.0.7
Data Recovery - STRAIN, DISP, COORDi - Wr
With Version 2004.0.0 if the Case Control includes an output request for
STRAIN, then the CID option for grid-type responses (DISP, SPCF, MPCF) will be
ignored and the output coordinate system will not show up in the printed .f06
output. Requests for other element-based output such as STRESS or FORCE do not
affect the grid-based output, just the STRAIN request.
Verified fixed as of 2004r3
1-15537101
2004.5
se angle has wrong sign
Dynamics - Modal Participation Factor pha
The sign of the phase angle of the modal participaltion factor results may be
in error.
compile mpf nolist
alter 'PARTN
ABE,VGXFS',''
PARTN
ABE,VGXFS,/,,ABESFP, $
ADD ABESFP,/ABESF/(-1.0,0.0)//3 $ NEGATE ABE MATRICES
alter 'SMPYAD PHGXFH'(1,0),''
SMPYAD PHGXFH,ABESF,PHGXSH,,,/ABEH/3/1///1/1 $
alter 'SMPYAD PHGXFH'(2,0),''
SMPYAD PHGXFHX,ABESFXX,PHGXSHX,,,/ABEH/3/1///1/1 $
1-15550901
2005.1
Optimization/Design Sensitivity - SPCD Incorrect Responses for Enforced Motion
TPL deck d200rd15 demonstrates this error and correction in verison 2005.
If a SOL 200 design task includes enforced motion using SPCD's, the final
response and element data recovery results are incorrect. The optimization
results are correct as are the sensitivities.
Avoidance: If PARAM NASPRT 1 is used, all data recovery results will be
correct. Alternatively, one can simply ignore the final response results and
create an input deck from the final design. TPL deck d200rd15 demonstrates
this error and correction in verison 2005.
1-15553302
2004.5
when no MPF output is requested
Acoustics - Data Recovery - Excessive CPU
Even if no modal participation factor output is requested, the data recovery

is still performed on all fluid-structure interface points; thereby defeating
the benefits of sparse data recovery.
compile spdr1
alter 'ajp'(2,-1)
type parm,nddl,i,y,fluidmp,structmp $
if ( fluidmp<>0 or structmp<>0 ) then $
alter 'ajp'(2)
else $
call xAdd5 vp,vky,vmy,vby,/vpx/cu/cu/cu/cu/cz $
endif $
compile semfreq
alter 'if ( structmp',''
if ( structmp<>0 or fluidmp<>0 ) then $
compile fea $ feafreq in V2004r2
alter 'if ( structmp',''
if ( structmp<>0 or fluidmp<>0 ) then $
compile spdr0
alter 'if ( fluidmp',''
if ( fluidmp<>0 or structmp<>0 ) then $
endalter
1-15561701
2005
ements - SFM 3001 (SEP2DR)
SOL 200 jobs with the design model in tip superelements and collectors between
the designed tip superelements and the residual may fail during pseudo-load
data recovery. Data recovery for collectors are skipped which causes the data
recovery for tip superelements to fail.
*** USER INFORMATION MESSAGE 7321 (SEDRDR)
*** SYSTEM FATAL MESSAGE 3001 (SEP2DR)
THE INPUT DATA BLOCK NAMED SLIST
AT POSITION
1 DOES NOT EXIST.
Avoidance: For ACMS, use 'TREE=SINGLE' in DOMANSOLVER. For regular
superelements, remove the collector definition.
1-15567801
2004.5
arse data recovery - Wrong Answers
Acoustics - Enforced Motion, SPCD, and sp
If sparse data recovery is activated in fluid-structure analysis with enforced

motion wrong answers may be produced.
Avoidance: Specify PARAM,SPARSEDR,NO or insert the following DMAP alter
compile cforce1
alter 1,1
SUBDMAP CFORCE1 MXY,mqxy,M2XY,m2qxy,BXY,bqxy,B2XY,b2qxy,KXY,
K4XY,k4qxy,K2XY,k2qxy,PHY,KDXY,kdqxy,axy,aqxy,
yx,vxpc,uset/
MXY1,BXY1,KXY1,pmyy,pbyy,pkyy,vxcg/
alter 'add
Matmod
add
add
alter 'add
Matmod
add
add
alter 'add
Matmod
add
add
APP/APP1/forctype $
vy1,vy2',''
axy,aqxy,,,,/vy3,/12/s,n,nonull/2/-1 $
vy1,vy2/vy2a $
vy2a,vy3/vy $
vy1,vy2'(2),''
vy1,vy2/vy2a $
vy2a,vy3/vy $
vy1,vy2'(3),''
vy1,vy2/vy2a $
vy2a,vy3/vy $
compile gma
alter 'umerge1 usetd,adya,,,'
call dbstore a1sf,adsf,,,//0/0/'
'/0 $
compile spdr1
alter 'call cforce1',''(,1)
call dbfetch /a1sf,adsf,,,/0/0/0/0/0 $
CALL CFORCE1 MSF,mysf,M2SF,m2ysf,BSF,bysf,B2SF,b2ysf,KSF,K4SF,k4ysf,
K2SF,k2ysf,,KDSF,kdysf,a1sf,adsf,,vspc,uset/
MSF1,BSF1,KSF1,,,,vscg/
APP/app/'spcforce' $
if ( noyg>0 ) CALL CFORCE1 MSs,,M2Ss,,BSs,,B2Ss,,KSs,K4Ss,,
K2Ss,,,KDSs,,,,,vspc,uset/
MSs1,BSs1,KSs1,,,,/
APP/app/'spcforce' $
if ( dompcf
) CALL CFORCE1 MMG,,M2MG,,BMG,,B2MG,,KMG,K4MG,,K2MG,,,KDMG,,,
,,Vmpc,uset/
MMG1,BMG1,KMG1,,,,vmcg/
APP/app/'mpcforce' $
compile fdrmgen
alter 'call cforce1',''(,1)
call CFORCE1 MSF,,M2SF,,BSF,,B2SF,,KSF,K4SF,,K2SF,,phif,kdsf,,,
,,vspc,uset/
msf1,bsf1,ksf1,,,,/
APP/APP1/'spcforce' $
if ( noyg>0 ) call CFORCE1,
MSS,,M2Ss,,BSS,,B2Ss,,KSS,K4Ss,,K2Ss,,,kdss,,,
,,vspc,uset/
mss1,bss1,kss1,,,,/
APP/APP/'spcforce' $
CALL CFORCE1 MMG,,M2MG,,BMG,,B2MG,,KMG,K4MG,,K2MG,,phig,kdmg,,,
,,vmpc,uset/
MMG1,BMG1,KMG1,,,,/
APP/APP1/'mpcforce' $
CALL CFORCE1 MMy,,M2My,,BMy,,B2My,,KMy,K4My,,K2My,,,
kdmy,,,,,,uset/
MMy1,BMy1,KMy1,,,,/
APP/APP/'mpcforce' $
compile cforce
alter 'call cforce1',''

call CFORCE1 MXY,,M2XY,,BXY,,B2XY,,KXY,K4XY,,K2XY,,uy,kdxy,,,,,
vxpc,uset/
mxy1,bxy1,kxy1,,,,vxpc1/
APP/APP1/forctype $
endalter
1-15573108
Nonlinear - CBUSH1D, shocka - Possible Wrong Answers
When using the "shocka" option on the CBUSH1D entry, the damping may be
ignored.
Avoidance: If large displacement is not important, replace the CBUSH1D with a
NOLIN entry.
1-15641036
SOL 400 - PARAM,POST,0, DBC Module - SWM 6065 (DBC)
There are two problems in this CSR --(1) The subDMAP, nonlin, of SOL 400 does not handle the NLSTRESS correct in DBC
module(s) in the PHASE 2 before calling SUPER3 module when ANALYSIS=NLSTAT.
(2) The current logic of DBC does not recognize "SUBCASE-STEP" case control
structure that only uses in SOL 400.
I have already fixed problem (1) in V2006t1. We may need DBC expert in problem
(2) - I have talked to KKK and sent some outputs to him for suggestion. I will
hold this CSR before KKK has time to look into it.
04/21/2005 CJY
================================================================================
====
SOL 400 encounters a problem processing results in the DBC module and issues
the following message:
RETURN CODE =
RETURN CODE =
1.
1.
Avoidance: Use PARAM, POST, -1 and the output2 file.

1-15653501
ults in xdb
ACMS - DISPL(PLOT)=ALL, PARM,POST,0 - Missing Eigenvector res
If "param,post,0" is specified with ACMS (serial or parallel), and

"DISPL(PLOT)=ALL" is specified, then the XDB file will not contain the
EIGENVECTORS. Note, that the EIGENVALUES are there, but not the mode shapes.
Avoidance: The eigenvectors will be written to the output2 file if
param,post,-1 is selected.
1-15654005
2004.5
SOL 600 - RBE2/RBE3 nodes are not include
d in all SOL 600 domains for Parallel Processing
RBE2/RBE3 nodes are not included in all SOL 600 domains for Parallel
Processing. Usually all REB2/RBE3's must be included in all domains and all
grid points associated with them must also be included in all domains, othewise
the job will diverge.
1-15664507
t
2005
Nonlinear Heat Transfer - Excessive Outpu
Heat transfer, sol 159, may place the:

N O N - L I N E A R
I T E R A T I O N
M O D U L E
O U T P U T
for each timestep on a different page. If printed this wastes paper and it
also has the potential of doubling the output because page header information
is repeated for each page.
1-15689201
c properly
2004.5
SOL 600 - RFORCE is not translated to Mar
SOL 600 RFORCE is not translated to Marc properly. It needs distributed load
code 105 rather than 100 or 103.
1-15689204
2004.5
ata - Nastran aborts
SOL 600 - MARCIN (include file) missing d
The SOL 600 MARCIN (include file) may result in missing data and may cause
Nastran to abort.
1-15721126
2004.5
ements only - UFM 4016
Heat Transfer Analysis - axi-symmetric el
Radiation heat transfer analysis with axi-symmetric elements may fail with the
following messages:USER FATAL MESSAGE 4016.
^^^ LINEAR ELEMENTS ARE CONNECTED TO THE
ANALYSIS SET (A-SET).
THERE ARE NO TEMPERATURES FOR RADBC ELEMENT 100011 IN SET 1
Avoidance: Add a dummy property entry as follows:
pshell,1,1,1.0
1-15721173
2005.1
- Divide by Zero
Nonlinear Heat Transfer - CHBDYG, NLITER
A message was added by Jenny Fang about increasing the initial guessed
temperature.
In SOL 153 with radiation, if the initial temperature guess is not close to the
final temperature, the analysis may fail with a divide by zero or the Nonlinear
Iteration Output will indicate extremely large epsilons as follows:
1 9.9000E+01 1.2246E+49 1.2246E+49 1.0000E-01 2.3162E+49 1.0000E+00
-1.2212E+49 -1.2212E+49
0
0
2
1
2 9.9000E+01++++++++++++++++++++++++++++++++++++ 5.1517+245 1.0000E+00
0.0000E+00 0.0000E+00
0
0
1
1
3 9.9000E+01???????????????????????????????????????????????? 1.0000E+00
0.0000E+00 0.0000E+00
0
0
0
1
Avoidance: Specify a better value for tempd.
1-15731520
3 (DUPART)
Rigid Elements/Superelements - QSET, RIGID=LAGRANGE - SFM 614
Using the new Lagrangian rigid elements (RIGID=LAGRANGE) together with QSET
entries will give
*** SYSTEM FATAL MESSAGE 6143 (DUPART)
SPECIFICALLY:
The number of columns in KVF is not equal to the size of the S+Q+B-set
Using RIGID=LAGRANGE with superelements gives the message:
BIOMSG: ERROR
0.
201 HAS OCCURRED IN ROUTINE WRITE
, FILE INDEX =
Avoidance: Do no use RIGID=LAGRANGE with superelements or qsets.

1-15738901
d in SE models
2005
Documentation/QRG - EQUILIBRIUM - Ignore
Remark 3 of the EQUILIBRIUM Case control command in the QRG should indicate
that the EQUILIBRIUM commnad produces no output in the presense of
superelements.
1-15742849
2005
ting point exception
Rotor Dynamics - UNBALNC - UFM 7813, floa
When the correction option (CFLAG) is used on the UNBALNC entry in rotor
dynamics, the grid specified on the UNBALNC entry must be in the aset.
Otherwise, UFM 7813 will be issued in some cases, which is the correct message.
In other cases, the job will fail with floating point exception.
Avoidance: Make sure that the specified grid point is in the aset
1-15742867
2004.0.7
DDAM - missing output in MSC.FEA
When using the new DDAM option in MSC.FEA, the results are missing.
Avoidance: The DDAM and DDAMOUT subdmaps need to be replaced. The error is
corrected in Version 2004.0.7 which is only available on the FEA 2004 R2 that
is scheduled to be released by the end of May 2004. The error is also
corrected in MSC.Nastran 2004.5 scheduled to be released June 15, 2004.
1-15795828
2004.5
mb friction is not translated
SOL 600 - BCPARA - FTYPE default of coulu
If FTYPE is not specified on the BCPARA entry no Defaults are used even though
the Quick Reference Guide mentions indicates that the default is Coulomb.
Avoidance: Explicitly specify FTYPE on the BCPARA entry.
1-15831209
with INTOUT
2005.0.2
Nonlinear Analysis - ESE - Wrong Answers
SOL 106, nonlinear analysis, may create incorrect nonlinear ESE when the 9th
field of NLPARM bulk data card, INTOUT, is not set to ALL in Version 2004 and
earlier releases.
Avoidance: Specify INTOUT=ALL.

It has been fixed in V2005.0.0
1-15831507
d 6144
2005
Frequency Response - SUPORT - SFM 6424 an
Direct Frequency response with SUPORT entries may fail with the messages:
THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE INCOMPATIBLE
LOAD VECTOR ROWS =
2536
FACTOR MATRIX ROWS =
2537
SPECIFICALLY:
The number of rows
in DAY is not equal to the number of zeros
in
User Information: Size of input matrices and partitioning vectors:
DAY
: Rows=
2537 by Cols=
1
VAY
: Rows=
2537
no. of non-zeros=
1 no. of zeros=
2536
0
Avoidance:
compile sedfreq
alter 'call mmfind1',''
type parm,nddl,char8,n,ltset,llset $
UPARTN USET,Kaa/KLL,,,/ltset/llset $
UPARTN USET,maa/mLL,,,/ltset/llset $
CALL MMFIND1,
Kll,Mll,USET,SILS,EQEXINS,,bgpdts/
MECHA,phir,vspc,lll/
s,mmech/'l
'/false $
endalter
1-15842401
2004.5
in fatal message
SOL 600 - Multiple NLSTRAT entries result
Even though multiple NLSTRAT entries are legal, SOL 600 gets a FATAL ERROR when
more than one NLSTRAT is defined. Normally there needs to be one NLSTRAT per
subcase with an additional one with ID=0 for Marc's phase zero if any at all
are entered.
1-15847916
Nonlinear Analysis - NLPARM - Incorrect Convergence Message
Nonlinear analysis, SOL 106, may issue the message that the "SOLUTION HAS
CONVERGED" even though there are large residual forces which is evidence that
the solution is not converged.
1-15848202
2004.5
led / RSSCON not supported
SOL 600 - Memory request of ... words fai
In Version 2004 solution 600 may fail with the message: memory request of
83137782 words failed during the translation phase - no Marc input file gets
created.
Avoidance: Increasing the memory may not allow the problem to be solved.
Running with a very large memory requested resulted in a marc input deck being
created and the following message being written to the f06 file:
TRANSL WARNING - RSSCON is not supported by the internal Marc translator. Marc
will not be executed.
1-15848212
2004.5
Elements - STRESS, PSOLID, CHEXA - Stress
at Gauss points not available for c IN=2
Writing out the stresses of CHEXA elements at the Gauss points for IN=2 is not
possible. Stress at the grid points will be output.
1-15854501
2005
nastran.rmt file
Submittal - node= - V2004 Windows missing
The PC version of v2004 (both r1 and r2) does not include the nastran.rmt file
(.../msc/msc2004/i386). This means that the "node=" option does not function.
Workaround is to copy the one from v2001 (however there are issues with that
file as well as you need to include a line that reads:
jidtype=%jidtype%
as a minimum - this is addressed in a separate CSR - see 1-15854504)
1-15854504
t
2005
Submittal - UFM, Input file does not exis
While using "node=" command to submit from Windows to unix, the job will fail
if the extension of the input file ( .bdf for example) does not match the
"jidtype" setting on the remote machine. This error persists even if the
"jidtype=bdf" keyword is used on the launching PC side.
Avoidance: If the following line is added to the PC's nastran.rmt file, then
the jidtype keyword is passed thru correctly and the job recognizes the
keywords and will run correctly:
jidtype=%jidtype%
Note that the "nastran.rmt" file itself is missing completely from the 2004 (r1
or r2) installations. The jidtype command above is in the standard nastran.rmt
file for Windows. When it is included in the delivery, this error will be
eliminated.
1-15862001
2004.5
a nastran nonlinear license
SOL 600 - SOL 600 incorrectly checks out
A SOL 600 job may incorrectly check out a nastran nonlinear license as
evidenced by the following message in the log file.
Acquired 100 licenses for Group CAMPUS (MSC.Nastran Nonlinear)
1-15879701
2004.5
SOL 600 - TEMPP1 & TEMPRB may produce inc
orrect POINT TEMP Marc input leading to wrong answers
SOL 600 TEMPP1 & TEMPRB may produce the wrong POINT TEMP in the Marc deck
leading to wrong answers.
1-15895505
g Answers
2005
Complex Eigenvalue Analysis - CLAN - Wron
In Version 2004, complex Lanczos may produce bad answers if the block size is
automatically augmented. The block size is only augmented when the number of
repeated roots is greater than the block size or the solver is unable to
converge and this rarely occurs in real world models.
Avoidance: The problem can be avoided by setting system(108)=8.
1-15907201
2004.5
SOL 600 - Eigenvalue analysis after a non
linear solution with contact gives wrong results
SOL 600 eigenvalue analysis after a nonlinear solution with contact gives wrong
results for the nonlinear portion of the job as well as the eigenvalue portion.
1-15923905
2004.5
Documentation/SOL 600 - BCBODY - UFM 316
If the documented text of "3D" is entered into the "DIM" field (field 3) of the
BCBODY entry, then MSC.Nastran 2004 and 2004r2 fatal out with a UFM 316 format
error as it tries to read the "d" as part of an exponent instead of as a
character as documented.
Avoidance: Leave this blank (since 3 is the default) or specify just the
number "3".
BCBODY,1
$ Default is OK
BCBODY,2,3 $ Using a number is OK
BCBODY,3,3D $ Gives UFM on "3D" field
Running even SOL 100 with the above as the bulk data file will demonstrate the
problem
1-15925501
2004.5
276 (BLDPK) EC 211
Large external superelement jobs may fail in the MERGE1 module with the
message:
SYSTEM FATAL MESSAGE 4276 (BLDPK) ERROR CODE 211 PID=
EXTOUT 166
UMERGE1 BEGN BLDPK TERM
1-15940601
)
0; f04:
Optimization/Design Sensitivity - BUFFSIZE - UFM 1126 (GNFIST
A SOL 200 job with a large number of bulk data entries and Nastran
BUFFSIZE=16385, failed with the following message:
DMAP MODULE PHASE0 IS ATTEMPTING TO OUTPUT DATABLOCK
DESOPT , WHICH ALREADY EXISTS.
233 NAME =
Avoidance: The error is under investigatation and is not completely understood;

however, lowering the buffsize allowed the specific test that failed to run.
Requesting more memory may also be an avoidance.
_____________________________________________
From: Shenghua Zhang
Sent: Thursday, March 13, 2008 4:31 PM
To: Vinh Lam
Subject: RE: CSR 1-15940601

Hi Vinh,
I can not find anything for you to investigate. It was 2004.
I suggest you cancel it with a notice something you described in your email.
We can revisit if it shows up later. Thanks.
Shenghua
_____________________________________________
From: Vinh Lam
Sent: Thursday, March 13, 2008 3:15 PM
To: Shenghua Zhang
Subject: CSR 1-15940601
Hi Shenghua,
I m looking in the above CSR quality 1-15940601, but can not start from any
where to investigate for a possible fix, since there is no attached bdf file.
Could you provide the deck if is available? The possible error could be fixed
already, but we do not have any mean to confirm.
Regards,
Vinh Lam
1-15944704
88, SFM 6144
2004.5
Frequency Response - QSET, ASET1 - UIM 75
In SOL 108 with modal reduction (ASET1, QSET) the GKAM module issues USER
INFORMATION MESSAGE 7588 indicating the number of modes that are retained.
The number of modes indicated retained is actually the number of modes
calculated and the then number of modes calculated is actually the number of
q-set degrees of freedom.
The residual vectors are subsequently thrown away
and later in the solution MERGE1 fails because of incompatibility of datablocks
DAY and VAY.
1-15950512
2004.0.7
SSSALTER - ddam - Wrong Answers
The NRL summing convention may not be used due to an inconsistent parameter
name used in the ddam* sssalter
Avoidance: Download the latest v2001 alter (ddamall.v2001) from our website.
This alter replaces the ddama and ddamba alters.
1-15950532
el
2005
Elements - CTRIAX6 - Incorrect Stress Lab
When using axisymmetric elements, vonmises stresses are labelled as octahedral

stresses. Only the labels are incorrect, the values are correct.
1-15962101
2004.5
Elements - CWELD, CFAST, PFAST - Wrong ma
ss when lumped mass specified in field MASS
If the MASS field of the PFAST entry is populated with a value, the mass added
is much larger than the lump mass specified. PARAM,GRDPNT,0 reports different
masses in different directions and the eigenvalue analysis fails.
1-15972201
2007.0.0
Complex Eigenvalue Analysis - EIGC - 3003
(CEAD)
Complex Inverse Power may fail with the message below when the bulk data input
also contains an EIGC entry that references the CLAN method.
*** SYSTEM FATAL MESSAGE 3003 (CEAD)
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA
BLOCK SCRATCH (FILE 310) IN SUBROUTINE CINVPR
FATAL ERROR
Avoidance:
Remove the unused EIGC entry.
1-15994609
EC 3021
2004.5
P-elements - GMINTC and GMINTS - SFM 4276
If GMINTC and GMINTS Bulk Data entries are both present in the model then the
run will terminate in the GP0 module with:
ERROR CODE
3021 PID= 0
1-16017810
ontrol Command
2005.5
Documntation/QRG - RCROSS - RCROSS Case C
In the QRG, there is an error in the description of the RCROSS case control
command. It must read CORF instead of CROF.
If CORF is mistyped, then the default PSDF is used, and no message is issued.
1-16026003
2004.5
SOL 600 - Gasket materials combined with
other solid element materials generate error in Marc
SOL 600 Gasket materials, MATG, combined with other solid element materials
generate error in Marc.
1-16028004
2004.5
1: Datablock CASEDM does not exist
The fatal message

USER FATAL MESSAGE 3001 DATABLOCK CASEDM DOES NOT EXIST
can result when eigenvector senstivities are requested and the only RTYPE that
is used is FORCE.
Avoidance: An avoidance is to add other RTYPE's (DISP,STRAIN,ESE,STRESS or
TOTSE) that invoke eigenvectors with an id that is equal to or greater than the
highest ID appearing on a DRESP1 with RTYPE=FORCE
1-16028303
2005
with sparse data recovery.
Transient Analysis - SPCD - Wrong Answers
Sparse data recovery usage in transient analysis (both SOL 109 and SOL 112)
employing SPCD enforced motion will give wrong answers if the base displacement
or velocity is non-zero. This should not affect enforced acceleration
scenarios, but may seriously affect enforced displacement or enforced velocity
scenarios.
Avoidance: Specify sparsedr=no.

1-16038804
2005
Documentation - DMAP Programmer's Guide A
erodynamic Module examples are obsolete
In the DMAP Programmers Guide, the description of the aerodynamic modules is up
to date. However, most of the examples still show the old argument lists, e.g.
ADG, AMG, ...
1-16060036
2004.5
Frequency Response - METHOD - UFM 9056, M
ETHOD Command required in all subcases
In all previous versions of Nastran, under sol 111, the METHOD command was
required only in the first subcase. In Version 2004 if multiple subcases are
specified in frequency response but a METHOD command is not specified in all
subcases the job will fail with the message:
USER FATAL MESSAGE 9056 ( MODEFSRS)
NO METHOD COMMAND WAS SPECIFIED IN THE CASE CONTROL SECTION.
1-16074001
2005
SFM 6144 (PARTN1)
Dynamics/Enforced Motion/DMP/Acoustics -
Acoustic models with enforced motion in DMP may fail with the message:
SFM 6144 (PARTN1)
Size of input matrices & partitioning vector incompatible
Columns of PHSA0 not equal to rows of VR
Avoidance: Apply the following dmap avoiance:
compile modefsrs
alter 'if ( relmtn )'(2),''
if ( relmtn and not(procid>1 and (fdmodes or mdmodes)) ) then $
endalter
1-16090301
2004.5
ignores paging, uses CARDNO
DMAP - MATOFP module - no print control,
The MATOFP module has several deficiencies:

1.
2.
3.
no print control.
ignores paging
uses old CARDNO processing

1-16096104
2005
ikes in Acceleration
Enforced Motion, SOL 109 - Unexpected Sp
Direct enforced motion with prescribed displacements (SOL 109) may result in
unexpected acceleration spikes at the beginning and end of the enforced
displacement. Enhancements to enforced motion have corrected this problem in
version 2005.
1-16107901
Optimization/Design Sensitivity - SPCD, MTRAN - Wrong answers
The new relative motion formulation is not supported in SOL 200 for
ANALYSIS=MTRAN.
(This is because the TRD2 module does not support the new
initial condition capabilities).

Avoidance: A direct transient solution should be selected.
1-16107905
2004.5
d wrong answers
DMAP - MATMOD Option 40 - Poor message an
MATMOD Option 40 has several errors:

1. Incorrectly issues the following message in the f04:
*24* Wrttrl Warning - Trailer type of terms for indexed matrix 201 is
incorrect: 0. An automatic update has been made. *24*
2. Incorrectly issues SWM 7598 when doing parameter conversion from single to
double precision.
3. Does not ouptut the matrix in machine precision if I1 is purged and TYPE
parameter is not consistent with machine precision.
4.
SFM 6918 and 6920 are fatal errors but do not terminate the run.
5.
If output is purged then there is no fatal.
6.
NZWDS and DENSITY in the trailer may be incorrect.

1-16109501
2004.5
Documentation/QRG - Nonlinear, PSOLID, TE
TRA - Nonlinear Supports 5-10 noded TETRA
The PSOLID entry description in the V2001 and V2004 Quick Reference Guide
incorrectly indicate that nonlinear is not supported for the 5-10 noded TETRA
element.
1-16128001
2004.5
Performance - matmod option 16 on hpux
Bad performance of matmod option 16 to punch DMIG has been reported for Nastran
2004 HPUX 2004 systems.
1-16132601
g with SETP
2004.5
Data Recovery - ESE ouput for DMIG missin
When SETP case control is used to combine existing sets in a model with
DMIG(s), the DMIG output maybe be missing in the ESE output.
1-16132609
2004.5
ice when SETP used
Data Recovery - ESE/EKE output printed tw
When the SETP case control command is used to combine existing SETs, and more
than one type of output is requested among ESE, EKE and EDE, the output may be
printed twice.
1-16143401
2004.5
alized coordinates are discarded.
Multilevel Superelements - Upstream gener
If KOA is null, which can happen on collector superelements that have no

physical boundary points, the coefficients for the generalized coordinates of
the upstream superelements may be discarded.
Avoidance: An alter that avoids this problem for non-inertia relief runs
follows:
$ remove line 72 in sekr
$ 72 IF ( NOT(STATICS) AND
$((XRESVECO='NO' AND XRESVIRO='NO' AND $ INRLM>-1)OR
$ SEID=0 OR SEID=FLUIDSE) ) THEN $
alter 72,72 $
if (not statics or seid=0) then $
1-16148146
Plane Strain
Nonlinear Analysis - CREEP, tref, PSHELL - Poor Answers with
In nonlinear analysis, plain strain elements give slightly different results

with different reference temperatures, tref, even though the creep is set to
zero.
The observed differences are small.
1-16148301
2004.5
FREQ, Superelements - Infinite Loop
The exact cause is under investigation.

Optimization/Design Sensitivity - MFREQ/D
MFREQ/DFREQ SOL 200 optimization jobs may encounter an infinite loop condition
if the number of records in FRQPRP is larger than NZ1. This scenario is most
likely to happen when superelements are utilized and the number of subcases is
high.
Avoidance : Use the following DMAP alter only if the design model is in the
residual (debug_dsad2.alter).
compile descon $
alter 'dsad ','' $
DSAD
RSP1CT,R1TAB,RESP12,OBJTAB,CONTAB,BLAMAX,LAMASX,
CLAMAX,DIVTAB,AUXTAB,STBTAB,FLUTAB,OUGVS1,OESS1,
,OEF1AA,
,
,
,OQGS1,DSCREN,XINIT,
tabdeq,COORDN,OLX, FRLSE, FRQRSP,CASEDS,CASEm, ,
OPTPRM,DVPTABF,PROPIF,BGPDTS,DNODEL,WGTM,
,
,
,resp3,rmstab,rmsval,
UGXF, QGXF, QMPXF, UHXF,
,
,
,
,MODRSP,CASEDMX,PHGX,
,
,
,upsdtx, RQATAB,RESP12X,RESP3X/
R1VAL,R2VAL,RSP2R,R2VALR,CVAL,CVALR,OBJTBR,CNTABR,
R1TABR,R1VALR,DRSTBL,FRQRPR,UG1,AUG1,R1MAPR,R2MAPR,
CASDSN,CASDSX,DRDUG,DRDUTB,CASADJ,LCDVECI,rr2idr,
r3val,r3valr,resp3r,rmstbr,rmsvlr,FRLR,FOLR,
UGM21, QGM21, QMPM21, UHM21,MODRPR,upsdt, RQATABR,
RSP2XR,RSP3XR/
vols/vol/S,N,OBJVAL/S,N,NR1OFFST/S,N,NR2OFFST/
S,N,NCNOFFST/APP/
-1/SEID/DESITER/EIGNFREQ/
S,N,ADJFLG/PEXIST/MBCFLG/RGSENS/protyp/autoadjx/
fsdcyc/s,n,nr3offst/inrel/s,n,tadjc/PEID/s,n,ACTFREQ/
s,n,FREQ1/s,n,DLOADDS/FRQ345/DISCYC $
endalter $
1-16149704
2005
SFM 7467, SFM 6144
Distributed Memory Parallel (DMP - ASET -
This is now fixed. (Remember don't test MDMODES on tiny job for now.)
DMP does not support the use of ASET/ASET1 entries. If ASET/ASET1 is used,
SYSTEM FATAL MESSAGE 7467 is issued correctly in version 2001. In version
2004, SFM 6144--the sizes of the input matrices and partitioning vectors are
incompatible--is issued. Since ASET is not supported in DMP, this also implies
that DMP does not support ADAMSMNF.
Avoidance: For models using DMP, remove the ASET/ASET1 entries. ASET/ASET1
entires are supported in MDACMS and MDMODES and Freq Domain Modes in V2005.
GDACMS and GDMODES are not supported.
1-16158821
wrong answers.
Heat Transfer Analysis - TEMPBC - Unreferenced TEMPB leads to
In nonlinear heat transfer analysis if input includes TEMPBC entries that are
not referenced by DLOAD entries at the same degrees of freedom for which there
are other TEMPBC entries that are referenced, then wrong answerws will result.
Avoidance:
Remove the unreferenced TEMPBC entries.
Developer's comments: Use SOL 400 can avoid this problem.

1-16163101
Answers
2005
Elements - QUAD4, TEMP, MAT2, MAT8 - Poor
In MSC.Nastran a single precision transformation is performed for non-isotropic

2D materials (MAT2 and MAT8). This may lead to poor answers and is especially
noticable when zero stresses are expected for a free expansion under thermal
loads.
Avoidance: Use the QUADR element.
1-16170315
Optimization/Design Sensitivty/Superelements - SFM 3001 (DSAD
J), SFM 4276 (GREAD)
Multi-database SOL 200 superelement jobs that use the adjoint method to compute
sensitivities will fail with the messages below unless PARAM,AUTOADJ,NO is
added to the deck to avoid the adjoint method.
Version 2005 issues:
AN APPENDABLE OUTPUT FILE ARVEC CANNOT BE ACCESSED WITH THE DBLOCATE
COMMAND.
USER ACTION: REMOVE THIS DATABLOCK NAME FROM THE DBLOCATE COMMAND AND
RERUN JOB
Version 2004 Issues
*** SYSTEM FATAL MESSAGE 3001 (DSADJ)
THE INPUT DATA BLOCK NAMED UG21
AT POSITION
7 DOES NOT EXIST.
DSAL is producing:
*** SYSTEM FATAL MESSAGE 4276 (GREAD)
ERROR CODE
3021 PID= 0
*** USER INFORMATION MESSAGE 4276 (GREAD)
TO OBTAIN A NASTRAN DUMP RESUBMIT JOB WITH DIAG 44 INSERTED IN THE
EXECUTIVE CONTROL SECTION.
1-16181301
FM TA1
2004.5
Elements - CRAC2D, CRAC3D, MAT8, MAT9 - U
If the crac2d or crac3d elements reference mat8 or mat9 orthotropic/anisotropic

materials the job will fatal in Version 2004.
1-16230501
2004.5
etic energies are incorrect
Rotordynamics - ROTSEKE - Strain and kin
There are error in the ROTSEKE subDMAP that lead to

1) Rotor numbers on output do not change
2) Energies are not calculated correctly.
1-16267101
2004.5
- Unexpected failure in DSTAp2 for DRESP3 optimization job
An external response optimization job (DRESP3) may fail in DSTAP2 without an
error message.
1-16270201
2004.5
PI error - IA64, SGI Altix, Itanium
Distributed Memory Parallel (DMP) - LAM/M
Distributed Memory Parallel (DMP) will not work with MSC.Nastran Versions
70.7-2004.0 on IA64 systems running RHEL 3.0 (Red Hat Enterprise). A message
stating that the LAM Deamons will not boot will appear. The issues are related
to RHEL 3.0 being based on glibc 2.3 which is incompatible with glibc 2.2 that
versions of Nastran prior to Version 2004.5 were built with.
Note that SGI
Altix Propack Version 3.0 is also based on glibc 2.3.
The special Version
70.7 Altix system requires the avoidance for serial jobs as well. However the
special SGI Altix V2004.0.7 system is built with SGI's proprietary MPI
libraries which support Propac 3.0. These special release are only available
at: http://www.mscsoftware.com/support/software_updates/index.cfm
Avoidance: Use MSC.Nastran V2004.5 (a.k.a. MSC.Nastran 2004 R3)
or
Install an OS that uses GLIBC 2.2.
or
Download the updated drivers from:
that support glibc2.3 for Linux 64.
On SGI Altix ia64 the following environmental varibles must also be set on all
releases prior to 2005r2:
setenv LD_ASSUME_KERNEL 2.4.19
setenv LD_PRELOAD /usr/lib/sgi-compat-preload.so
1-16270204
2004.0.3
Memory - Unable to Allocate - IA64/Linux
V2004.0.0 IA64/Linux systems cannot allocate more than 2.0 Gb on the "mem"
parameter. V2001.0.9 allowed memory allocation over 2Gb. This error was
corrected in V2004.0.3.
1-16306501
2004.5
DISUTIL option 10 Bus Error
Distributed Memory Parallel/ACMS - DMP -
DISUTIL option 10 may incur a Bus Error. This could affect distributed memory
parallel ACMS, which is where DISUTIL option 10 is used most.
1-16320101
2005
, GPFORCE - SFM 5423
Aerostatic Analysis - SPCFORCE, MPCFORCE
If GPFORCE, SPCFORCE, or MPCFORCE is specified in SOL 144 then the job may
fail with SFM 5423.
Avoidance: Specify PARAM,SPARSEDR,NO OR insert the following DMAP alter:
compile fdrmgen
alter 'IF ( not((AERO ',''
IF ( noa>-1 ) then $
endalter
This is linked with 1-16241417
1-16323801
2004.5
SOL 600 - MATEP - MATEP workhardening slo
pe, H, is not translated to Marc, Wrong Answers
In SOL 600 the MATEP workhardening slope, H, is ignored and is not translated
to Marc.
1-16323804
2005
SOL 600 - CORDi - Loads applied in cylin
derical coords are sometimes incorrect
SOL 600 loads applied in cylinderical coordinates are sometimes incorrect.
This can happen even if the loads are in the basic coordinate system but the
grids have specified a cylindrical output coordinate system in field 7 of the
GRID entry. In most cases, the loads are correct. Only in unusual
circumstances are the loads incorrect.
1-16326601
- UFM 7105
2005
When an optimization job specifies DESVAR IDs > 1 million and the DESVAR
command is used to select part of DESVAR entries, the job may fail with the
message:
USER FATAL MESSAGE 7105 (DOPR3F)
The Fiedl DVID aaaa on DVPREL1 Entry ID = yyyy is not selected by the DESVAR
Case Control command.
Avoidance: Specify DESVAR IDs < 1 million.
1-16332103
050
2004.5
Static Analysis - PARAM,INREL,-2 - UFM 9
In Version 2004, when param,inrel,-2, is specified to select inertia relief

without the need to specify a SUPORT entry the analysis may fail with USER FATA
MESSAGE 9050.
Avoidance: Specify param,inrel,-1 and specify a suport entry.

[JoeM] Recommed scaling of DRA (or DRG in the SELG PJ calc's), such that
DRA(T)*MAA*DRA diagonal is in the KAA-diag avg range. High augmented KLL
factor-diag's should disappear.
1-16336101
Body Mode
2005.5.2
Eigenvalue Analysis - EIGRL - Extra Rigid
For one particular model, a slight variation of the mass matrix caused
Lanczos to calculate an extra erroneous rigid body mode. The cause of the
error is under investigation.
Avoidance: For this particular problem, perturbing the model's mass matrix
and/or specifying F1 and F2 on the eigrl entry avoided the extra, erroneous
rigid body mode.
1-16420502
2004.5
SOL 600 - Missing SPCs
In SOL 600, an array in a is dimensioned 6 but values are set up to 8. This

may cause Linux systems to fail to write SPCs resulting in an unconstrained
model or wrong answers.
1-16442912
2004.5
M leading to wrong answers.
Matrix Methods - DCMP - Fails to issue UF
Version 2004 uses Lagrange multipliers in static analysis and hence negative
factor diagonals can now be common and the stiffness well conditioned. Thus, in
Version 2004 DECOMP may ignore negative maxratio values and fail to issue a
fatal message when it should.
1-16443309
2005
(PLOT), UFM 2025 (SDR2)
External Superelements - EXTSEOUT, OUTPUT
If an external superelment, EXTSEOUT, superelement contains a displacement

output request. and OUTPUT(PLOT) commands are used, the following FATAL message
will occur:
UNDEFINED COORDINATE SYSTEM ID = 268435455
Avoidance: Removing the OUTPUT(PLOT) section will eliminate the error.
1-16455901
2005
Optimization/Design Sensitivity - Eigenve
ctor sensitivity with multiple boundary condtions broken
Eigenvector sensitivity analysis based on DRESP1 entries was introduced in the
2004 release of MSC.Nastran. The original release supported multiple boundary
conditions, but this capability was broken in the 2004.0.3 release (a.k.a
2004r2) when support for multiple boundary conditions in frequency response
optimization was integrated.
Avoidance: Use 2004.0.0 or version 2005.
1-16470701
2005
e Boudary Conditions not robust with multipl analysis types
Mutiple boundary conditions with frequency response analysis was introduced
into SOL 200 in Version 2004.0.3 (a.k.a. 2004R2). Testing has shown problems
when there are multiple disciplines as well as multiple boundary conditions.

In particular, runs with ANALYSIS = MODES and ANALYSIS= MFREQ with different
boundary condition can produce fatal messages. Quality report 1-1655901 is
related.
Avoidance: The dmap changes required to support analysis =MFREQ and
analysis=MODES and multiple boundary conditions are extensive so this
capability is not considered to be operational. It will be operational in
Version 2005.
1-16470704
2005
Optimization/Design Sensitivity - Extra r
esponses in formatted sensitivity prints
Generalized mass and stiffness responses are "spawned" when the Rayleigh
Quotient approach is applied to eigenvalue sensitivity analysis. These
response are typically suppressed when formatted design senstivities are
printed, but they appear if two different subcases share a DRES[1 id with type
= eign or freq and the sensitivity is computed for both. In this case, the
senstivities of the generalized matrices can appear following the eigenvalue
sensitivities.
Avoidance: An avoidance is to not share a DRESP1 ID for multiple subcases.
1-16474104
2004.5
Nonlinear Buckling Analysis - DCMP - Miss
ing UIM 4698 to identify instabilities
To identify instabilities and isolate buckling, the user should look for UWM
4698. However, in Version 2004 DCMP does not print the message making it
impossible to identify buckling phenomena.
The following is an example of the missing message:
STATISTICS FOR DECOMPOSITION OF MATRIX K(appropriate) .
GRID POINT ID
DEGREE OF FREEDOM MATRIX/FACTOR DIAGONAL RATIO
MATRIX DIAGONAL
102
R2
-1.93940E+03
2.14680E+04
Verified this message has been restored. Tested in V2004.5 and V2005.0.0.
lproctor 12/6/04,
sorry for delay didn't know it was assigned to me, I guess this can be closed.
1-16479901
01
2008.0.0 (MD R3)
MDACMS fails for all fluid model - SFM 30
If ACMS is attempted on a model with only fluid elements and no structural

elements then the run will fail with:
*** SYSTEM FATAL MESSAGE 3001 (MDENZO)
THE INPUT DATA BLOCK NAMED MKXX
AT POSITION
Avoidance:
compile modefsrs
alter 'mdacms=', '' $
paraml vafs//'null'//s,n,full $
1 DOES NOT EXIST.
mdacms=(NDOM>0 and full=0) $ all fluid models not allowed

endalter
1-16498001
2005.5
External Superelements - UFM 6802
It has been observed on an external superelement run that the job failed in
finding the boundary points with the following messages:
UFM 6802 - SE 0 has failed to automaticaly derive a search key - user action to
review model or override search key.
Avoidance: Run the reduction run with the DMIGPCH option and include the DMIG
entries without using the .asm file.
1-16500402
PRT
2004.5
Superelements - Print Format error in TAB
The Superelement Summary Output in the f06 filem may contain asterisks for
large integer grid id's (******).
1-16503108
d Ouput
2005
Acoustics - FLSPOUT, STRUCTMP - Mislabele
Modal participation factors are calculated for each subcase but are mislabled
as the first subcase.
1-16567604
2005.5
- SFM 3007 GPFDR
Rigid Elements - RIGID=LAGRANGE, GPFORCE
RIGID=LAGRANGE may cause jobs to fail in the GPFDR module with SYSTEM FATAL
MESSAGE 3007.
1-16603701
stic
2005.0.2
DMAP - NOT, AND, OR - SFM 223 poor diagno
If the name of an expression like NOT or AND is used as a variable name, it is

accepted in some statements but causes a message that is difficult to
understand when it appears.
An error report is attached to the back of the test problem, along with some
suggested fixes.
mag
1-16606402
2005
SSSALTER - spc101a alter missing
In Nastran 2004 the spc101a alter was not included.

Avoidance: SSSALTERs are posted to the web at:
http://www.mscsoftware.com/support/prod_support/nastran/sssalters/v2004/toc.cfm
1-16630701
2005
Optimization - DRESP1 - Transient respons
e types on the DRESP1 do not support multiple components.
Rermark 7 for the DRESP1 entry in the QRG indicates that TDISP, TVELO, TACCL
and TSPCF support multiple components. A code bug blocks this to a single
component less than or equal to 6.
Also for GPFORCP. the ATTA input is a grid id. therefore there are
documentation errors in table 8-9 on the DRESP1 entry in the QRG and in Remark
7, GPFORCP should be omitted.
Avoidance: Single components can be used for the transient responses with no
loss of functionality. Mutiple components only simplify the input.
1-16634301
2005.0.2
Eigenvalue Analysis - RESTART, SOL 106, m
ultiple subcases, stress stiffened normal modes
If a normal modes (SOL 103) analysis is restarted from a nonlinear static
solution (SOL 106) which contained more than one subcase, the eigenvalues
calculated may be incorrect.
Avoidance:
Insert the following DMAP alter in the SOL 103 restart run
ECHOOFF $
COMPILE SEMG LIST $
ALTER 'PARAML.*CASESR','' $
PARAML CASESR//'DTI'/recno/4//S,N,LOADID $
ENDALTER $
ECHOON $
1-16658001
2005
ritten to op2 file
Postprocessing - MCFRACTION - No output w
No MCFRACTION results are written to the op2 file.

1-16663924
2005
WM 6174 leads to wrong answers
Differential Stiffness - CBAR - Missing U
Solutions that use differential stiffness (105, 106 and any SOL with STATSUB)
that have CBEAM elements with offsets will correctly issue the message below.
However; this message may not be issued for similar models with CBAR elements.
*** USER WARNING MESSAGE 6174 (EBEMD)
BEAM ELEMENT (EID=110) WITH OFFSETS ARE NOT SUPPORTED IN DIFFERENTIAL
STIFFNESS
OR NONLINEAR ANALYSIS. REMODEL WITHOUT USING BEAMS WITH OFFSET.
0FATAL ERROR
1-16663960
2007.1.0
ments for differential stiffness
Documenation/QRG - CQUAD4/CTRIA3 enhance
The following paragraph under remark 3 of the CTRIA3 description and remark 6
under the CQUAD4 description is no longer true and should be removed:
The differential stiffness for the offset vectors is not computed. Therefore,
solution sequences (SOLs 105 and 200; SOLs 103 and 107 through 112 with
STATSUB) that require differential stiffness to get correct result, give wrong
results. However, for the nonlinear solution sequences (SOLs 106, 129, and
400), the differential stiffness is not required to give correct results,
therefore, the results are correct, if the solution converges.
1-16700702
op2 file
2005
Postprocessing - POST - Missing Output in
If POST NODISP is specified in one subcase then results may be missing from the
op2 files in subsequent subcases.
1-16723804
2005
MEFFMASS command
---------SIGNAL CAUGHT:
Signal number
Signal code
Signal tid
Fault addr
FP inexact
FP divide0
FP underflow
FP overflow
FP invalid
may lead to the following error on Nastran 2004 HPUX systems:

=
=
=
=
=
=
=
=
=
Frequency Response - MEFFMASS - signal 8
8
14
1
4000000001352823
0x0
0x8000
0x0
0x10000
0x0
Avoidance: Either remove the MEFFMASS command or run on another machine.

1-16761101
2005
Superelments - EXTSEOUT - Double Field Gr
ids result in SFM 3002 in the BDRYINFO module.
External superelements, EXTSEOUT, may fail with SYSTEM FATAL MESSAGE 3200
(LOGIC ERROR 28) in the BDRYINFO module if double field GRID entries are used.
Avoidance: Use single field GRID entries or double field GRID entries with the
grid IDs in columns 9-16
1-16769901
ide - UMERGE1
2005
Documentation - V2004 DMAP Programmers Gu
The Version 2004 DMAP programmers guide shows the following for the format of
the UMERGE1 module:
UMERGE1 USET,A11,A21,A12,A22/MAJOR/SET1/SET2/IOPT $
It should be:
UMERGE1 USET,A11,A21,A12,A22/A/MAJOR/SET1/SET2/IOPT $
1-16771901
2005
Composites - PCOMPG - Strength Ratio may
cause composite stress & failure index output error
When PCOMPG bulk data entries are used (with a blank FT field) and Strength
Ratio output request is turned on (PARAM,SRCOMPS,YES), the composites stress,
failure index and strength ratio output may be either missing or incorrect.
1-16815502
2005
Composites - PCOMP - Nastran fails with s
ignal 11 if duplicate IDs for MAT entries exist
If a PCOMP entry references a MAT8 entry that has the same ID as another MAT
entry, i.e. MAT1, Nastran fails with signal 11 in the log file. No other error
messages are given.
1-16821701
2004.5
o update RC file
Installation - HPUX 11 - ERROR: Unable t
MSC.Nastran Version 2004.5 may have trouble installing on older versions of ksh
on HPUX 11. If the following messages are encountered during installation
then upgrade the ksh to at least 82.10.1.48 which was released in 2002. The
error is considered fixed by this upgrade.
Begin configuring MSC.Nastran 2004.5

Creating default version links...
Configuring licensing...
makercentry[4]: /tmp/./msc/conf/nast20045rc: cannot create
ERROR: Unable to update RC file "/tmp/./msc/conf/nast20045rc"
Setting user configuration items...
1-16855001
2005
Output in PUNCH File
Nonlinear Analysis - STRESS(PUNCH) - Bad
In SOL 106, nonlinear analysis, a request for nolinear stresses to be output to

the punch file, STRESS(PUNCH), will lead to NanQ or ????? in the punch file.
1-16857203
2005
Transient Analyis - SOL 112, SE, No Physi
cal Residual, BIOMSG 1044, UFM 4276 QOPEN
If CMS is performed on Superelement, and enforced motion is performed on
Residual with ALL physical dof constrained, then TRD1 will fail with
*** USER INFORMATION MESSAGE 5222 (TRD1)
UN COUPLED SOLUTION ALGORITHM USED.
0.
STATUS =
0
...
*** SYSTEM FATAL MESSAGE 4276 (QOPEN)
ERROR CODE
1044 PID= 0
*** USER INFORMATION MESSAGE 4276 (QOPEN)
, FILE INDEX =

malter 'paraml.*icspcd.*icspcdx'
ICSPCDX=0 $
1-16858013
2005
ide - MTRXIN description for NOMATi
Documentation - V2004 DMAP Programmers Gu
The Version 2004 DMAP Programmer's Guide MTRXIN description for the NOMATi
flags indicates that the flags are set to a value of +1 whether the matrix is
present or not. The description indicates:
NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is
generated; 1 otherwise.
this should read:
NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is
generated; -1 otherwise.
1-16877703
2005
leads Access Violation
Miscellaneous - Disk full on Windows 2000
A "DISK FULL" condition may lead to an access violation on Windows 2000.

Avoidance: This error can be avoided by specifying "sysfield=mapio=no" in a
.rcf file or on the command line when the MSC.Nastran job is submitted.
1-16888416
2005
Installation - Installation Errors on AIX
5.2 - mscinfo[281]: ram+= : syntax error
A "full" installation of MSC.Nastran 2004r2 on for AIX 5.2. fails with the
following message while the installation is unloading the install script:
mscinfo[281]: ram+= : syntax error
1-16901604
Elements - CBUSH, PBUSHT, MPC - Wrong Answers
When MPCs are connected to CBUSH elements that reference a PBUSHT property
entry, values in the table may be ignored and incorrect mpc force results will
be output.
1-16903301
ex matrices
DMAP - DECOMP - DET method yields incorrect results for compl
The DET function of DEC0MP yields incorrect results for complex matrices.
scaled determinant is correct but the power term is returned as zero.
1-16903901
ng Output
2005
The
An assembly run employing an external superelement created using the EXTSEOUT

feature does not give any output for the external SE if the creation run has no
DISP request.
Avoidance: Apply the following dmap alter to the assembly run:
compile extotmin
alter 'dbstatus x_tug,x_rga',''(,1) $
dbstatus x_tug,x_tef,x_tes,x_tqg,x_rga//
s,n,notug/s,n,notef/s,n,notes/s,n,notqg/s,n,norga $
if ( notug>0 or notef>0 or notes>0 or notqg>0 or norga>0 ) then $
endalter $
1-16917801
2005
e Boundary Conditions, Output labelled incorrectly.
For SOL 200 with ANALYSIS=MFREQ and multiple boundary conditions, BC=, the
output for 2nd subcase onwards are labelled incorrectly.
Avoidance: Request DMAP alter from client support.
1-16917806
2005
DRESP1 - UFM 3007 (dopr3)
SOL 200 jobs may fail if DRESP2 entries that reference DRESP2 entires coexist
with DRESP2 entries that reference DRESP1 entries.
1-16924801
2005
Miscellaneous - Include may not working o
n Windows 2000 if file attributes are chaned from default
On Windows 2000, if a nastran include data file has the attributes (properties,
Advanced, uncheck the "file is ready for archiving" and uncheck the "For fast
searching") Then the job aborts.
1-16936701
2005
.5) does not work on Windows systems
SOL 700 - SOL 700 in Natran 2004r3 (2004
SOL 700 for Natran 2004r3 (2004.5) does not work on Windows systems because the
latest Intel compilers provide full path names for the dytran-lsdyna input file
and dytran-lsdyna is not able to accept full path names.
1-16937701
2005
hen there is no SUBCASE command
Case Control - ESE THRESH does not work w
The THRESH option of the ESE Case Control command does not work if a SUBCASE
command is not present.
Avoidance: Add a SUBCASE command.
1-16938101
s specified
2005
SOL 600 - PCOMP - Wrong Answers when Z0 i
When translating the Nastran PCOMP enty into a Marc deck, if the Z0 field is
specified, then the resulting Marc COMPOSITE entry will be wrong.
The current action is to take whatever value is in the PCOMP Z0 field and map
it directly into the Marc's COMPOSITE 3rd datablock 4th field. The 'meaning'
of the Z0 on the PCOMP entry and this field in Marc are incompatible. In
NASTRAN, Z0 on a PCOMP entry defines the distance from the reference plane to
the bottom surface of the laminate. In Marc, the field it is mapped to
represents the position of the user-defined reference plane. This is the value
of the local z-coordinate of the user-defined plane with respect to the
geometric midplane.
1-16959902
FS)
2005
Superelements - SEEEXCLD - UFM 6788 (SEPM
A model that has duplicate boundary grids in the residual structure may fail to
exclude the duplicate grid and may fail with the message:
*** USER FATAL MESSAGE 6788 (SEPMSF)
SUPERELEMENT
1 GRID
3 AND SUPERELEMENT
13 HAVE CONFLICTING MANUAL DIRECTIVES.
1-16969464
0 GRID
Miscellaneous - SYSTEM(55)=0 - UFM 315 (IFPDRV)
If SYSTEM(55) is set to 0, Nastran will likely fail in ifpdrv with the message:
FORMAT ERROR ON BULK DATA ENTRY GRID
SYSTEM(55), a.k.a. IPREC, only expects a value of 1 for single precision or two
for double precision. The user is never expected to set this system cell.
1-16978601
Frequency Response - Enforced Motion, SPCD - UWM 2108, UFM 30
46, SFM 3003, SFM 5423

If multiple boundary conditions are specified with enforced motion in dynamic
analysis then the following errors may occur:
V2004r1 and V2004r2 : UWM2108,UFM3046
V2004r3 and V2005 : UWM2108,SFM3003 or SFM 5423
compile phase0
alter 'if ( appc='(2),''
type parm,,char8,n,blank $
IF ( APP='FREQRESP' ) THEN
alter 'LCGEN.*CASE1X',''
LCGEN CASE1X,SLT,ETT,DYNAMIC0,GEOM4S/CASE1//APP $
alter 'if ( seid=0 and (app='(2),''
if ( false ) then $
alter 'if ( appc='(3),''
IF ( APP='FREQRESP' ) THEN
alter 'gp4.*caseq'
paraml casew//'dti'/nskip/1//s,n,subcid $
call dbstore yg1,,,,//subcid/0/blank/0 $
compile phase1dr
alter 'call phase1b'(,-1)
paraml casew//'dti'/nskip/1//s,n,subcid $
call dbfetch /yg1,,,,/subcid/0/0/0/0 $
equivx yg1/yg/-1 $
compile semfreq
alter 'nzyg0',''(,1)
alter ' dpd '(,-1)
paraml casem//'dti'/1/1//s,n,subcid $
equivx yg1/yg/-1 $
matmod yg,,,,,/nzyg0,/6 $
diagonal nzyg0/nzyg/'whole'/0. $ ones at non-null YS rows
compile sedfreq
alter 'nzyg0',''(,1)
alter ' dpd '(,-1)
paraml casem//'dti'/1/1//s,n,subcid $
equivx yg1/yg/-1 $
matmod yg,,,,,/nzyg0,/6 $
diagonal nzyg0/nzyg/'whole'/0. $ ones at non-null YS rows
endalter
1-16989601
2004.0.7
s > 2Gb - UFM 398
Miscellaneous - IA32 Linux - Include file
Input files greater than 2Gb may not be included in a data file in Versions
2004.0.6 and prior on IA32 Linux systems. Version 2004.0.7 and later systems
allow include files greater than 2Gb.
Avoidance: If you must use version 2004.0.6 or earlier, then break the include
file into separate files each less than 2Gb
1-17005701
2005.1
External Superelements - EXTSEOUT , SOL 1
01 - Wrong Answers
EXTSEOUT usage in SOL 101 gives wrong results for the external SEs in
the assembly run if the external SE has loads applied to its interior
points. In other words, the fixed-boundary o-set displacements are not
included in the external SE data recovery.
Avoidance: Use the following DMAP alters in the external SE creation
runs as well as in the assembly run.
compile super3
alter 'call extotmin'(,-2),''(,0)
file tug1=ovrwrt/tes1=ovrwrt/tef1=ovrwrt/tqg1=ovrwrt $
call dbfetch /dtis,dtindxs,dmis,dmindxs,/seid/0/0/0/0 $
dtiin
dtis,dtindxs/
tug1,tes1,tef1,tqg1,,,,,,/
s,n,notug/s,n,notes/s,n,notef/s,n,notqg $
exterse=(exterse or notug or notes or notef or notqg) $
if ( exterse ) then $
call extotmin maps,dmis,dmindxs,uset,eqexins,
xsop2dir,matpools/
tug1,mug1,tqg1,mqg1,tes1,mes1,tef1,mef1,
rga,ugo,mug1o,mqg1o,mes1o,mef1o/
statics $
call dbstore mug1o,mqg1o,mes1o,mef1o,//seid/0/'
'/0 $
compile phase0
alter 'call ifps'
call dbstore dmindxs,dtindxs,dmis,dtis,//seid/0/'
'/0 $
compile sedrcvr
alter 'MPYAD.*mug1,uls1,',''
call dbfetch /mug1o,mqg1o,mes1o,mef1o,/seid/0/0/0/0 $
if ( notug1>0 ) MPYAD mug1,uls1,mug1o/iugx $
alter 'MPYAD.*mef1,uls1',''
MPYAD mef1,uls1,mef1o/iefx $
alter 'MPYAD.*mes1,uls1',''
MPYAD mes1,uls1,mes1o/iesx $
alter 'MPYAD.*mqg1,uls1',''
MPYAD mqg1,uls1,mqg1o/iqgx $
compile extotmin
alter 1,1
subdmap extotmin maps,dmis,dmindxs,uset,eqexins,
xsop2dir,matpools/
tug1,mug1,tqg1,mqg1,tes1,mes1,tef1,mef1,rga,ugo,
mug1o,mqg1o,mes1o,mef1o/
statics $
alter 'dbview'
dbview x_mugo=extdb where (seid=temp and xname='mug1o' and wildcard)
dbview x_meso=extdb where (seid=temp and xname='mes1o' and wildcard)
dbview x_mefo=extdb where (seid=temp and xname='mef1o' and wildcard)
dbview x_mqgo=extdb where (seid=temp and xname='mqg1o' and wildcard)
alter 'if ( xname=',''
if ( xname='matrga' or
xname='tug1' or xname='mug1' or
xname='tes1' or xname='mes1' or
xname='tef1' or xname='mef1' or
xname='tqg1' or xname='mqg1' or
xname='mug1o' or xname='mes1o' or
xname='mef1o' or xname='mqg1o' ) then $

alter 'equivx.*x\_tqg',''(,3)
if ( statics ) then $
equivx x_mugo/mug1o/-1 $
equivx x_meso/mes1o/-1 $
equivx x_mefo/mef1o/-1 $
equivx x_mqgo/mqg1o/-1 $
endif $ statics
else $
dmiin
dmis,dmindxs/mug1,mes1,mef1,mqg1,,,,,, $
if ( statics
) dmiin
dmis,dmindxs/mug1o,mes1o,mef1o,mqg1o,,,,,, $
matmod tug1,,,,,/tug1x,/32/1 $
equivx tug1x/tug1/-1 $
matmod tef1,,,,,/tef1x,/32/1 $
equivx tef1x/tef1/-1 $
matmod tes1,,,,,/tes1x,/32/1 $
equivx tes1x/tes1/-1 $
matmod tqg1,,,,,/tqg1x,/32/1 $
equivx tqg1x/tqg1/-1 $
mtrxin ,,matpools,eqexins,,/vax,,,,/lusets $
merge
,,,mug1,,vax,/mug1x/1 $
equivx mug1x/mug1/-1 $
merge
,,,mef1,,vax,/mef1x/1 $
equivx mef1x/mef1/-1 $
merge
,,,mes1,,vax,/mes1x/1 $
equivx mes1x/mes1/-1 $
merge
,,,mqg1,,vax,/mqg1x/1 $
equivx mqg1x/mqg1/-1 $
compile extout
alter 'SDR2.*CASEs'
dbstatus uoo//s,n,nouoo $
if ( nouoo>0 ) then $
umerge uset,uoo,/ugo/'g'/'o' $
dbstatus v01s//s,n,nov01s $
if ( nov01s>0 ) then $
Partn
ugo,,v01s/,ugo1,,/0 $
delete /ugo,,,, $
merge
,,ugo1,,,,v01s/ugo/0 $
endif $ nov01s>0
SDR2
CASEs,CSTMS,MPTS,DIT,EQEXINS,,ETT,nulllama,BGPDTS,,qg,
ugo,EST,XYCDBs,,,,,,,,,,,,,,/
,iqg1o,IUG1o,IES1o,IEF1o,,,,,,,/
'reig'/S,N,NOS2A/S,N,NCOMPS $
DRMH1
Iug1o,Iqg1o,Ies1o,Ief1o/
TUG1o,MUG1xo,TQG1o,MQG1xo,TES1o,MES1xo,TEF1o,MEF1xo/
/1/7/3/1005/1004 $
add5
mug1xo,,,,/mug1o $
add5
mqg1xo,,,,/mqg1o $
add5
mes1xo,,,,/mes1o $
add5
mef1xo,,,,/mef1o $
endif $ nouoo>0
alter 'EQUIVX mug1\/EXTDB'
xname = 'mug1o' $
EQUIVX mug1o/EXTDB/-1 $
alter '15.*\'mug1'
append ,,/xsop2dir/15///////'mug1o' $
alter 'EQUIVX mqg1\/EXTDB'
xname = 'mqg1o' $
equivx mqg1o/extdb/-1 $
alter '15.*\'mqg1'
append ,,/xsop2dir/15///////'mqg1o' $
alter 'EQUIVX mes1\/EXTDB'
xname = 'mes1o' $
equivx mes1o/extdb/-1 $
alter '15.*\'mes1'
append ,,/xsop2dir/15///////'mes1o' $
alter 'EQUIVX mef1\/EXTDB'
xname = 'mef1o' $
equivx mef1o/extdb/-1 $
alter '15.*\'mef1'
append ,,/xsop2dir/15///////'mef1o' $
alter 'matpch mug1'
matpch mug1o,mqg1o,mes1o,mef1o/ $
alter 'xname=\'mug1\''(,2)
xname='mug1o' $
dbstatus extdb//s,n,noextdb $
if ( noextdb>0 ) output2 extdb//0/outunit///'matrix'
alter 'xname=\'mqg1\''(,2)
xname='mqg1o' $
alter 'xname=\'mes1\''(,2)
xname='mes1o' $
alter 'xname=\'mef1\''(,2)
xname='mef1o' $
endalter
1-17011701
2005
- Illegal Input to dopr3j
When a DRESP2 response in a SOL 200 job intends to reference an existing DRESP1
entry but precedes with a DRESP2 flag, the job fails in DOPR3 with the fatal
message "illegal input to subroutine DOPR3J".
Avoidance: Specify the correct DRESP1 flag for the referenced entries.
1-17013601
2005
or quadratic shell mid-side nodes
ADAMS/Flex - MNF grid point stress null f
The ADAMS/Flex modal neutral file's modal grid point stress/strain results are
null for mid-side nodes of quadratic shell elements due to the fact that
nastran does not compute grid point stress results for mid-side nodes of quad8
and tria6 elements. The ADAMS/Flex element face information for elements of
these types should contain only the corner grid data and not the mid-side
nodes.
1-17025310
2005.1
ails; cannot determine disk space
Installation - mscsetup - Linux install f
Nastran 2004 "mscsetup" script fails on Mandrake Linux 9.1/ 10.0 because it
cannot determine the amount of free disk space.
Suggestions:
"mscsetup" uses "df -k" to determine disk space.

However, if "df -k" outputs multiple lines, the "awk" procedure cannot
determine the actual disk space.
Avoidance:
Replace the following line in mscsetup
linux* )
set -- $(df -k $dir 2>/dev/null | awk 'NR==2{printf("%d
%d\n",$4/1024,$2/1024)}')
with:
linux* )
set -- $(df -k $dir | awk 'NR==2 && NF>1{printf("%d
%d\n",$4/1024,$2/1024);exit}
NR==3{printf("%d
%d\n",$3/1024,$1/1024);exit}')
1-17055508
2005
In solution 103 if param,methcmrs references an EIGR set id, the job may fail
with the message:
(REIG).
2000) IN TABLE (EED )
IN SUBROUTINE

compile phase0
alter 'SEP2.*nGEOM1,GEOM2,GEOM3,GEOM4'(2)
if ( seid=0 ) equivx dynamic/dynamics/-1 $
endalter
1-17064430
2005
pecify F2 on EIGR entry
Distributed Memory Parallal - User must s
If a dmp job only specifies ND on the EIGR entry using method LAN and the
DOMAINSOLVER entry specifies the partopt=freq option the job may attempt to
solve all frequencies on all processors.
Avoidance: The user must select F2 on the eigr entry.
1-17071801
2005
Miscellaneous - INPUTT2 - OP2 files with
matrices and tables may lead to UFM in INPUTT2
OP2 files with intermixed tables and matrices that were correctly read in
MSC.Nastran V2004.0.6 fail in V2004.5. The problem is caused because code
handling end of matrix condition did not properly accept all valid conditions.
1-17081504
NT
2005
Submittal - node=machine does not work on
The node=machine nastran submit line option cannot be used from NT to a

dissimilar machine.
1-17098601
DMAP - Can't set qualifier value in DMAP if the qualifier nam
e starts with 'COND'

If the qualifier name starts with 'COND', then its value cannot be set in DMAP.
1-17101614
2005.5
ct Default Value
Documentation/QRG - PARAM,ERROR - Incorre
The default value of "0" for the parameter ERROR as shown in the QRG is
incorrect. The correct default value is -1
1-17101627
gnored
2005.0.2
Frequency Response - ESE, OFREQ - OFREQ i
If there are multiple subcases with different OFREQ callouts, the OFREQ command
is ignored for ESE output.
Avoidance: Either don't use OFREQ or only use one subcase when ESE output is
desired
1-17104601
not useable
2005
SOL 600, SOL 700 - Windows Version 2004.5
The switch to Intel Version 8 compiler in MSC.Nastran Version 2004.5 for

Windows caused many problems in SOL 600 and SOL 700. Thus, this release should
not be used for SOL 600 and 700 on Windows.
1-17148302
2005
Optimization/Design Sensitivity - DOPR1,
PCOMP - Poor Message, Illegal input to DOPR1I
A composite optimization job fails in DOPR1 with "Illegal Input to Subroutine
DOPR1I" if the following two conditions are met:
1. The integer input with FID option is used to sepcify a designed laminate
thickness or ply angle on a DVPREL1/2 entry and
2. The laminate thickness or ply angle that the FID represents is Not defined
on a PCOMP entry.
For example, only two laminates are defined on a PCOMP entry but the FID field
on a DVPREL1 entry references the thickness for the third laminate.
Avoidance: Only design the laminate thickness or ply angle on a DVPRELi entry
that is defined on a PCOMP entry.
1-17172902
2005
cf file not created.
Installation - Nastran 2004r3 nast20045.r
The rcf file for Version 2004.5 (2004r3) on for Windows is created as a file
named "nast2004.rcf" which is ignored.
Avoidance: The program will recognize the rc file if it is renamed to
"nast20045.rcf".
1-17172908
ignored
2005
Installation - Path to License server is
During installation on Windows, the user is asked to enter authorization

information. Inputting a valid "port@host" entry is ignored and the default
"authoirz.dat" is entered into the rc file for the AUTH= keyword.
Avoidance: The user must manually edit to rc file.
1-17177340
2005.0.2
tion, wrong results
Aeroelastic Analysis - Direct Enforced Mo
Solution 146 produces wrong results showing when direct enforced motion is
used. The call to subDMAP SUPER3 with AULF is missing data block RGY
(penultimate input data block). This may cause some grids to deflect
incorrectly.
Avoidance: PARAM,DDRMM,-1 will also avoid the data recovery error.
1-17194201
2005
ESE - UWM 4506, UIM 4507, subcase, TOTAL
ENERGY OF ALL ELEMENTS IN PROBLEM = 0.0
If a job incorrectly specifies SUBCASE1 with no space instead of SUBCASE 1, the
subcase number is read as zero. If ESE output is requested, UWM 4506 and UIM
4507 may be issued indicating the total strain energy is zero. No warning
message is given that the SUBCASE entry is in error. The ESE output shows
TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM
= 0.000000E+00 and no list of
strain energies by element is output
Avoidance: Correct the SUBCASE entry to leave a space between the word SUBCASE
and the 1
1-17202601
2005
Acoustics - DAREA entries not converted t
o static loads if they reference fluid points
Currently, DAREA entries are not converted into equivalent static load entries
if they reference fluid grid points.
1-17203001
2005
ESE fails if PARAM,POST specified
Distributed Memory Parallel - MDACMS with
Parallel MDACMS with ESE request and PARAM,POST will fail since slave processes
are not prevented from attempting to write to the output2 file. Solution is to
modify the DMAP to call OUTPUT2 only on the master. (Alter can be generated on
request.)
1-17210346
2005
ble not output2 with post,-2
Post Processing - PARAM,POST,-2 - Lama ta
The llama table is not output2 to the op2 file with param,post,-2.
Avoidance: Use param,postext,yes.
1-17234402
ge output2
2005.1
Postprocessing - UFM 1004 (CLSPFL) for hu
Postprocssing that creates extremely large op2 files may fail with the
message:
*** USER FATAL MESSAGE 1004 (CLSPFL)
FORTRAN UNIT CLOSE ERROR.
USER INFORMATION:
IOSTAT =
180, Invalid argument (errno=22)

LOGICAL = OUTPUT2
FILE = ./topo_02_015.op2
1-17242803
2005
Post Processing - Incomplete XDB File
The DBC/XDB object in the dictionary does not contain the correct control
information, it contains the original object template when the create function
completes. This may lead to an incomplete xdb file which may cause post
processers to fail. This error has only been observed for one test file that
contained 55 subcases.
Avoidance: A possible avoidance is to change the block size of the xdb in the
FMS section.
1-17252901
2005
ock GOA already exists
External Superelements - UFM 1126, Databl
In Version 2004.5 an external superelement reduction run with ACMS results in

the following fatal message:
DMAP MODULE UMERGE1 IS ATTEMPTING TO OUTPUT DATABLOCK
201 NAME = GOA
compile phase1b
alter 'call segoa'(9,-1)
delete /goa,,,, $
endalter
1-17256104
2005.5
description of wtmass
Documentation/QRG - MEFFMASS - Incorrect
The MSC.Nastran Quick Reference Guide incorrectly indicates the Modal

Effective Weight is the Modal Effective Mass multipled by the parameter
WTMASS. This is incorrect, it is divided by WTMASS.
1-17278455
ils in SOL 146
2005.0.2
Aeroelastic Analysis - OLOAD - Request Fa
The OLOAD output request for SOL 146 is not being honored when only frequency
response analysis is performed.
Avoidance: Apply the folloiwng alter which changes the fifth input datablock
in the final super3 call from ppf1 to pgf1
compile seaero
alter 'super3'(3),''
CALL SUPER3 CASECC ,
PSF1
,frl
,
,PCDB
EMAP
,MAPS
SLT
,ETT
,
USET
,SILS
GM
,
,
DYNAMICS,BGPDTS
EST
,GEOM2S
INDTA ,KELM
,ditid
,GEOM4S
,AULF
,LAMA
,
,XYCDB
,EQEXINS
,GOT
,
,PJ
,KFS
,
,CSTMS
,GEOM3S
,KDICT
,pvtbc
,PG
,FOL1
,AUHF1
,
,POSTCDB
,PVTS
,GOQ
,
,EDTs
,KSS
,MAR
,MPTS
,ECTS
,GPECT
,scstm
,
,PgF1
,DLT
,
,
,CASES
,
,GPLS
,YS
,QR
,MEA
,DIT
,EPTS
,VELEM
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,EPT
,GEOM4
,
bgpdtvu ,gpsnts
gdntab ,oint
MMG
,MSF
K4SF
,K2MG
M2SF
,B2SF
,
,
folt
,
mss
,bss
,
xsop2dir,
mmcdb ,geom1qx
DESE0f ,kaa
,
rgy
,
AUPF
,AQPF
iQG1
,iEF1
iQG2
,iEF2
ies1mc ,ief1mc
iee2mc ,
APP
/APP1
AERO
/dropt
0
/FALSE
false /freqdep
soltyp /false
false $
GEOM3
1-17280829
- Output2
2005
,MPT
,PTELEM
,medge
,pvt
,pelsets
,BMG
,M2MG
,qsgf
,
,matpool
,
,k4ss
,
,
,meh
,maa
,
/
,aqmpf
,iES1
,iES2
,iee1mc
/
/RSONLY
/FALSE
/0
/false
/false
,GEOM1 ,GEOM2
,MELM
,MDICT
,viewtb ,
,deqatn ,deqind
,KSF
,KMG
,BSF
,K4MG
,B2MG
,K2SF
,qmgf
,
,
,
,
,
,
,
,ypfo1 ,
,
,vgq
,
,
,SESE0f ,KESE0f
,baa
,cmlama1
,matpools,gei
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,iEE1
,iEE2
,ies2mc
,iUG1
,iUG2
,
,ief2mc
,
,
,
,
/FALSE
/S,PFILE
/pexist
/0
/false
/FALSE /
/S,CARDNO/
/0
/
/false /
/spdr
/
Documentation/QRG - Release Guide, ASSIGN
Example 4 under the ASSIGN FMS statement is incorrect. The current example is
as follow:
assign op2 bigendian'
...
assign op2='test_op2.12' unit=12
assign op2='test_op2.35' unit=35 form=formatted
The op2 logical name is assigned to unit 12 and this unit number should not be
changed on the assign statement. This is usually used for param,post-1 and
param,post,-2. The example should be modified as follow:
assign op2 bigendian
...
assign op2='test_op2.12'
assign output2='test_op2.35' unit=35 form=formatted
1-17280840
2005.0.2
Superelement - SELR, method - SFM 9104
In a static supelement analysis run, if case commands METHOD=n and seqset1

entries are included in the model, the job may fail with the following unclear
messages:
^^^ USER FATAL MESSAGE 9104 (SELR)
^^^ THERE IS NO COUPLING BETWEEN INTERIOR POINTS
OF THIS SUPERELEMENT AND
ITS BOUNDARY POINTS.
^^^ USER ACTION: ADD SOME ELEMENTS CONNECTING THE INTERIOR AND BOUNDARY
POINTS.
Avoidance: Removing either the method command or the seqset1 entries will
avoid the error. Note that neither one of these entities are used in sol 101
so the error is very unlikely.
1-17282301
1013
2005
File Management Section - DBLOCATE - SFM
Three successive DBLOCATE commands, the first 2 with NOCOPY and the last one
with the COPY option, results in the following fatal message:
*** SYSTEM FATAL MESSAGE 1013 (GBKMGX)
BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGX , FILE INDEX
=
0.
STATUS =
0
Avoidance: Do not mix COPY and NOCOPY options.
1-17297801
2005
SFM 3008 UTMCOR
Distributed Memory Parallel - EXTSEOUT -
In MSC.Nastran 2004r3(2004.5) a dmp run with external superlements may fail

with the message:
MODULE = MDENZO
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ENZO2
PROGRAMMER INFORMATION: LOCATION KEY = READ IN P
Avoidance: Run without dmp or apply the following alter:
compile cmpmode
alter 'call mdacms ' (,-1) $
if( nproc>0 ) putsys(nproc,231) $
alter 'if ( fdcmrrs', '' $
if ( fdcmrrs OR mdacms ) then $
alter 'paraml cmphixz', '' $
paraml cmphixz//'trai'/1/s,n,nozset $
1-17297961
2005
ndled correctly on hpia64
Installation - FLEXlm installation not ha
The current 'mscsetup' script correctly accounts for the hpuxia64 being
distinct from hpux, as far as Patran and Nastran installs are concerned,
however, when installing a FLEXlm server, the scripts in the .../msc/bin
directory (flexlm, lm*) are based off an older mscsetup that does NOT account
for the distinction as such, running those scripts on an IA64 will still search
for the default 'hpux' location, when the install actually created an
'hpuxia64' folder, and the script will fail
1-17303819
2005
rong results for complex matrices
DMAP/Matrix Methods - SMPYAD method ABA w
The SMPYAD module ABA method produces wrong results for complex matrices under
the following conditions:
1. Spill (multiple passes) used.
2. Triple loop kernels used.
Avoidance: Set sys129=1 to bypass the ABA method.

1-17303823
2005
t and wrong answers
Acoustics - METHOD(FLUID) - Missing outpu
For acoustics, if a METHOD(fluid) entry is not present in the Case Control, the
fluid eigensolution is not performed. This conflicts with design intent and
Remark 3 under the METHOD command in the QRG.
Avoidance: Specify a METHOD(FLUID) entry in Case Control.
1-17322311
2005
cases - UWM 73, Wrong answers
In buckling
subcases in
1. SOL 105
2. SOL 200
Buckling Analysis - multiple buckling sub
analysis UWM 73 will be issued if there are more than two buckling
the following solution sequence:
with scr=no
with ANALYSIS=BUCK regardless of scr keyword

compile super3
alter 'DBVIEW qGFs=qG'
DBVIEW UGFb=UG WHERE ((
(seid>0 and peid>0 and spc=* and mpc=* and
suport=* and bmeth=* and mtemp=* and
p2g=* and k2gg=* and m2gg=*) or
(seid=0 and peid=0 and spc=cspc and mpc=cmpc and
suport=csuport and bmeth=cmeth1 and
p2g=cp2g and k2gg=ck2gg and m2gg=cm2gg and
mtemp=cmtemp)
)) $
DBVIEW qGFb=qG WHERE ((
mtemp=cmtemp)
)) $
alter 'SEP4
CASESEP4'
else if ( app1='bkl1' ) then $
SEP4
CASESEP4,PCDB,EMAP,XYCDB,UGFb,PUGF,QGFb,mmcdb/
DRLIST/
APP4/'SEID'/S,N,NODRALL/S,N,SEID0/S,N,NOUPL/CNTL $
alter 'DBVIEW UGs=UG '
DBVIEW UGb=UG WHERE ((
mtemp=cmtemp)
)) $
alter 'NUGDWN=(NOGO=-1'
else if ( app1='bkl1' ) then $
SEDR
EMAPX,CASEX,PCDB,DRLIST,XYCDB,SLT,ETT,
MAPSF,UGb,BGPDTSD,GDNTAB,,/
ULS,CASEDR,PCDBDR,XYCDBDR,,/
APP4/SEID/S,N,NOUP/S,N,NOSRT1//S,N,NOOUT/
S,N,NOPLOT/S,N,NOXYPLOT/'SEID'/NCUL $
NUGDWN=(NOGO=-1 AND SEID<>0) $ must appear right after sedr
endalter
1-17370601
2005
DFREQ, scr=no - Wrong Answers
Optimization/Design Sensitivity - MFREQ,
Direct or modal frequency response optimization may produce different

optimization results if scr=no is used.
Avoidance : Use scr=yes
A related problem has surfaced with a external se deck from GM. The client
deck itself is not available. However, the problem can be reproduced with
d200pe3 with resvec=no.
Adding adelufx to the dbdelete fxied the problem. Or, scr=yes also does the
trick.
1-17373002
2005
Enforced Motion - SPCD - Enforced motion
in a subset of subcases results in SFM 5423.
If a frequency response job with more than one subcase has an SPCD enforced
motion specified in only a subset of the subcases, the job terminates with
SYSTEM FATAL MESSAGE (SFM) 5423 in the MPYAD module.
Avoidance: If a frequency response job with more than one subcase is to have
SPCD enforced motion specified in only a subset of the subcases, define VERY
SMALL enforced motion in those subcases where such enforced motion is not
really needed.
1-17373523
2005
issing UFM 2113
Elements - PBEAML, MAT8 - Poor Message, M
If a pbeaml entry incorrectly references a MAT8 entry a "Fatal Error" without

any further information will be output in V2004.0.6. In V2001.0.9 the same job
produces a better message*** USER FATAL MESSAGE 2113 (EMG)
ELEMENT
1 REFERENCED MATID
1 WHICH CANNOT BE USED TO
OBTAIN REQUIRED PROPERTIES.
Avoidance: Other than correcting the input there is no avoidance.
1-17378501
rong Answers
2005
Nonlinear Analysis - PCOMP, TEMP(MAT) - W
Unsymmetric composite layups with temperature-dependent materials may produce

wrong answers in nonlinear analysis.
1-17384835
2005.5
h no mass matrix.
Aeroelastic Analyis - Attempt to trim wit
If a solution 144 trim analysis is executed on a model with no mass the

following fatal message that does not describe the problem will occur:
SPECIFICALLY:
The number of columns in PUXLRPV is not equal to the number of rows in the
column partitioning vector PVPR
PUXLRPV : Rows=
2 by Cols=
9
PVPR
: Rows=
11
An attachment contains a version of the AEMR.dmap that traps the missing mass
matrix.
Note: This same error can occur if the PARAM, WTMASS is set to zero or 0.0. It
is the same effect as not having mass. This error may be slightly more
prevalent in Flight Loads. The reason being is the ability to use equations on
some of the flight loads forms is not available. An example would be for the
Forward Swept Wing airplane. The direction say to use feet instead of inches
for acceleration. So instead of WTMASS being 1/386 or the common .00259, one
should be able to enter `1/32.14`. In regular Patran this is acceptable, and
will return 0.031081. Flight Loads just writes .0
1-17386627
r message
2005
Miscellaneous - SWM 6498 UFM (1) - Unclea
Corrected usrmsg.F to increase dimension of array from 9 to 10. (cdp 8/24/04)

If degrees of freedom are defined illegally in a set (e.g., constraining an
dependent dof), the job should fail with a message similar to the following
messages:
USER FATAL MESSAGE 2101 (GP4)
+165
GRID POINT
530 COMPONENT 1 ILLEGALLY DEFINED IN SETS
US
UM
However, in v2004.5, the job may fail with the following unclear messages
Windows machine.
*** SYSTEM WARNING MESSAGE 6498 (MsgGen)
Message number was not found.
Check call to MSGPOP from GP4 with message number 538976288.0.
Severity is 'USER FATAL MESSAGE' (1)
%1: '
530'
%2: ' 1'
%3: ' UM'
%4: ' US'
%5: '
'
%6: '
'
%7: '
'
%8: '
'
%9: '
'
%10: ''
Avoidance: Correct the offending entry
1-17395103
2005
DMAP - MPYAD - incorrect data in UFM 5423
If the MPYAD module issues SFM 5423, the message may contain an incorrect data
block name specified in a prior execution of MPYAD. For example,
in the following DMAP:
MATGEN
MATGEN
MATGEN
MPYAD
MPYAD
,/A/4/4/3 $
,/B/4/3/4 $
,/C/4/3/3 $
A,B,C/D $
A,B, /E/1 $
the 1st multiply runs OK but the 2nd mpyad fails and references the C matrix in
the first mpyad.
1-17417801
2005
Complex Eigenvalue - CEAD - Eigenvector s
pill logic in complex Lanczos causes hard crash.
The multishift logic in the complex branch of the complex Lanczos method
suffers a hard crash when the eigenvectors spill.
Avoidance: The avoidance is to increase memory or to use the old single vector
complex Lanczos.
1-17432001
2005
DOPR3 - SFM 4276
Optimization/Design Sensitivity - DRSPAN,
When an optimization job includes both DRSPAN subcases mixed with non-DRSPAN
subcases, the job may fail with SFM 4276 with error code = 3001 in the DOPR3
module.
Avoidance: Rearrange the subcases so that the non-DRSPAN subcases are put at
the top of the DRSPAN subcases.
1-17434501
Distributed Memory Parallel - DMP, PACMS fails on SGI Altix 3
300 with SFM 6833 (PNBSND)
ACMS has difficulty subdividing large, dense, solid models (such as engine
blocks) into balanced components.
ACMS performance for these types of models
is not good, so ACMS is not recommended. If attempted, poor load balancing may
cause one process to run much longer than another and the job may fail with an
MPI time-out error.
SYSTEM FATAL MESSAGE 6833 (PNBSND)
USER ACTION: PLEASE VERIFY THAT THE PARALLEL OPERATING ENVIRONMENT (POE) IS
WORKING CORRECTLY.
IF IT IS VERIFIED AND THIS ERROR STILL OCCURS, PLEASE CONTACT MSC CLIENT
SUPPORT.
0FATAL ERROR
1-17446201
2005.0.2
Aeroelastic Analysis - DMIK
The DMIK bulk data input provides a convient way of entering correction data
related to the aerodynamic model. At present, this is supported only in SOL
144 and SOL 200 and is not supported in SOL's 145 and 146.
Avoidance: The DMI equivalents of these matrices can be input or the following
dmap avoidance can be applied to add the MATPOOL datablock in the call to
PFAERO. The alter below applies to SOL 145 with a similar alter required for
146:
CALL PFAERO cases
DMINDX
mklist
aecomp
aeusets
lajjt
D2JK
,EDTS
,ects
,bgpdts ,DMI
,PCDBS ,acpt
,aero
,matpool
,aempcomp,aemonpt ,saemprk ,control
,cstma ,aebgpdts,mpjsfn2o,mpjn2o
/
,uajjt ,ajj0
,wskjf ,D1JK
,d1je
,d2je
,skj
,
,
,
,
,
,WKK
,
,
,
,
,
/
'DYNAMICS'/IMACHNO/IKBAR /S,PFILE /SKPAMP
1-17446504
2005
,
,
,
,
,
,
,
,
$
Rotordynamics - TRD1 - Traceback in TRD1
Rotordynamcis may fail in trd1 with a traceback.

1-17446507
2005
Rotordynamics - ROTORG, NLTRD2, CDAMPi, C
VISCi, UNBALNC - Wrong Answers, Damping Ignored
The rotor damping (CDAMPi, CVISCi) should add instability to transient response
but damping is effectively not included.
1-17469004
2005
K - HPUX IA64 under Nastran 2004r3
Rigid Elements - AUTOMSET, DECOMP, UFMPAC
Large models with automset may fail with the message below on Itanium running
HPUX.
From the f04 file
Your use or distribution of UMFPACK or any modified version of
UMFPACK implies that you agree to this License.
THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY
EXPRESSED OR IMPLIED. ANY USE IS AT YOUR OWN RISK.
From the log file:
FATAL ERROR:
thread: 1
routine: sysrcv
reason: signal recvd
error: -4
Avoidance: The only avoidance is to use version 2005.
1-17482902
2005
exe= specified with no directory
Submittal - libpath set incorrectly when
Fixed in round 16.

When using nastran script with exe= keyword to override the default executable,
if the pathname of the executable does not have any directory compoment
specified, then the libpath will not include the correct directory path.
1-17497305
2005.5
RIGID=LAGRAN 3000 grid limit
Rigid Elements - RIGID=LAGRAN - SFM 5483
Models with RIGID=LAGRAN and more than 3000 points attached to a rigid element
will fail with the following message:
*** SYSTEM FATAL MESSAGE 5483 (TA1H)
ROUTINE NEEDS TO BE UPDATED, IT DOES NOT SUPPORT ELEMENTS WITH GRIDS MORE
THAN =
3000
1-17497318
ceback in EMG
2005.1
Rigid Elements - RIGID=LAGRAN, RBE3 - Tra
Models with RBE3s and RIGID=LAGRAN may fail with a traceback in EMG.
Traceback:
Offset 0x000000ec in procedure
Offset 0x00000a2c in procedure
--- End of call chain --1-17505001
2005.5
ent ID - missing connection
dminit_
dmnewb_
emgsoc_
emg_
xsem09_
xsemdr_
nastmon_
mainal
External Superelements - EXTSEOUT, differ
For external superelement using the EXTSEOUT command, the boundary points for
the assembly structure at which the components will be attached are generated
in the ASMBULK file. It is also assumed that the boundary IDs for the
component and the assembly structure are the same. If the boundary IDs are not
the same, then the structure may not be connected as intented.
Avoidance: If the boundary IDs for the component and assembly structure are
different, do not use the ASMBULK file, but create a SEBULK entry using the
automatic feature instead. This problem has been resolved in Version 2006 by
the incorporation of a new option called ASMBULK=AUTO for the EXTSEOUT Case
Control command.
1-17506102
5266 (ASGPRS)
2001.0.9
Aeroelastic Analysis - TRIM, AELINK - UFM
In aeroelastic analysis the following misleading message may be issued:

USER FATAL MESSAGE 5266 (ASGPRS)TOO MUCH DATA ON TRIM OR AELINK BULK DATA
ENTRIES.
when the message that should be issued is:
*** USER FATAL MESSAGE 7526 (ASGPRD)
AN INVALID TRIM TASK HAS BEEN POSED. THERE ARE
2 FREE AESTAT
DEGREES OF FREEDOM BUT
ONLY
1 SUPPORTED DEGREES OF FREEDOM.
USER ACTION: SPECIFY A VALID TRIM TASK BY EITHER ADDING SUPPORTED
DEGREES OF FREEDOM OR BY
REDUCING THE NUMBER OF FREE AESTAT DEGREES OF FREEDOM.
1-17510409
2005
Miscellaneous - MEM - 'Unable to allocate
/XNSTRN/ Open Core (memory) on Windows XP
MSC.Nastran requires that contiguous memory be allocated.

MSC.Nastran
requires dlls be loaded and these dlls use open core. The various Windows o/s
may allocate the required open core differently causing more or less memory to
be available for nastran. Windows XP has been found to allocate the memory in
such a way that only 1100mb of contiguous space is left for nastran.
MSC.Nastran V2005 dummys out unneeded FLEXlm dlls and this allows more memory
to be allocated. Thus, this problem is considered partially addressed in
Version 2005. MSC will continue to investigate more efficient ways to allocate
memory.
Note that it is a limitation of all Windows based operating systems that other
applications that are executing will impact the amount of open core that can be
allocated.
MSC.Nastran V2005 has been further enhanced to improve dll management to
maximize the available open core. Currently, it appears that MSC.Nastran can
now access approximately 1.8GB of open core on all versions of Windows XP.
1-17527801
2008.0.0 (MD R3)
Superelements - PARAMs AUTOQSET and Bulk
Data entries SECSETi and SEBSETi - Possible wrong answers
When using the autoqset feature (PARAM,AUTOQSET,YES) , the system modes may be
incorrect if one of the component modes is free-free or fixed-free (see
SECSETi, SEBSETi).
Avoidance: Insert PARAM,MHRED,NO and, if running V2005r2 or earlier, the
$ alter is needed for only V2005r2 or earlier
compile semr3
alter 'call semr4'(3),''
call semr4 pg,uset,gm,ksf,bsf,msf,ys,drg,mff,cmpho,lyy,kyy,
cmlama,moo,koo,got,cmphrc,vvfs,cmmi,vyv,,bjj,sils,
eqexins,rvg,cmeigmat,vgq,pmyg,pbyg,pkyg,cases,,
resldo,vvy,gotf,vgfs/
goq,cmlama1,cmemat,mq/
norc/nomvjjs/s,dotrip/fluid/nasout/0/error/
genrldo/splitfs $
endalter
1-17557511
2004.5
Nonlinear Analysis - CTETRA, MATT - Tempe
rature-dependent material , sdr2 - job aborts
In version 2004, if a nonlinear model contains tetra elements and
temperature-dependent material properties are used, then the job may abort in
SDR2 with the following unclear messages:
MAIN: For reference, A(MAINAL) = 73C3B0,
This error is fixed in Version 2004.5.
Avoidance: Removing either the temperature-dependent material or replacing the
tetra elements with hexa elements avoids this error.
1-17575313
- SFM 6551
2004.0.7
File Management Section - ASSIGN, INPUTT2
An FMS ASSIGN statement to UNIT=300 may fail on linux with the message:

A READ ERROR WAS DETECTED ON UNIT 300 DURING BINARY INPUTT2 PROCESSING
1. A KEY VALUE WAS NOT BEING READ
2
3. THE FORTRAN READ IOSTAT CODE IS
154
Avoidance: Use a different unit number
1-17581703
SFM
Optimization/Design Sensitivity - scr=no, param,soladjc,-1 -
SOL 200 job may fail if following condition exists,

a. scr=no
b. adjoint load method activated
c. resvec=yes
Avoidance : Change one of the conditions, such as scr=yes
1-17584301
2005
etric FBS for uncoupled matrices
Performance - Poor performance for unsymm
The performance for unsymmetric FBS is poor when the matrices have very little
coupling (i.e. very sparse RHS matrix). In this case, the code should select
the special "MCE1-only" sparse FBS.
1-17604301
output
2005
Data Recovery - GPFORCE, SUBCOM - Missing
If GPFORCE is requested in a SUBCOM then "F-OF-SPC" may not be printed in the

SUBCOM's grid point force balance output.
COMPILE sedrcvr
alter 'GPFDR
CASEDR,UG,KELMX'(,-1)
paraml qmg//'null'////s,n,nullqmg $
if ( nullqmg=-1 ) delete /qmg,,,, $
endalter
1-17620501
2005
Superelements/Frequency Response - DELA
Y, SPCD - SFM 4276 in DPD (in SEDLG subdmap)
A SOL 111 superelement job employing DELAY data and SPCD enforced motion fails
with SYSTEM FATAL MESSAGE 4276 (ERROR CODE 3021) on a call to the DPD module in
the SEDLG subdmap during data recovery.
1-17647514
2005
Postprocessing - PARAM,POST,0 - GRIDX is
not present in XDB for Collector Superelements
THE GRIDX datablock is not present in the XDB when the superelement is a
collector containing no elements.
1-17663601
2005
Missing PSDF output in assembly run.
External Superelements - EXTSEOU, PSDF -
When using the EXTSEOUT feature, the assembly run does not output the PSDF
responses for velocities and accelerations for the external superelement.

Avoidance: Insert the following DMAP alter in the assembly run:
compile sedrcvr
alter 'Multiply OTM'
splitdva=-1 $
endalter
1-17664010
2005
ith no mass does not issue UFM
Inertia Relief - param,inrel,-2 - Model w
A model with no mass defined may only issue a max ratio warning message and
continue when using param,inrel,-2. The job should issue a meaningful fatal
message.
+++++++++++++++++++++++++
A correct warning message is found in V2005.0.0. -TIN^^^ USER FATAL MESSAGE 9088 (SELG)
^^^ PARAM,INREL,-2 IS PRESENT BUT NO MASS IS DEFINED.
1
1-17670502
2005
Size Limitation - DCMP - Floating point e
xception error in DCMP for large models
In MSC.Nastran Version 2004.5, large models may fail in decomp on 64 bit aix
systems (AIX 5 and above).
Signal generated for floating-point exception:
FP invalid operation.
1-17673201
2005.0.2
File Management Section - ASSIGN with DEL
ETE option fails - UFM 1277 or UFM 773
In Version 2004.0.7 and 2004.5.0 only: If the DELETE option is used on an
ASSIGN MASTER statement and the file already exists, then the file assigned to
MASTER is NOT deleted and UFM 1277 is issued.
ASSIGN MASTER='model.MASTER', DELETE
ASSIGN DBALL='model.DBALL', DELETE
$
*** USER FATAL MESSAGE 1277 (DBDEF)
THE FILE ASSIGNED TO LOGICAL NAME = MASTER IS NOT A VALID MASTER DBSET
FOR A PRIMARY DATABASE.
USER ACTION : VERIFY THE FILE NAME SPECIFIED ON THE ASSIGN MASTER
STATEMENT.
0FATAL ERROR
In Version 2004.0.7 and 2004.5.0 only; If the DELETE option is used on an
ASSIGN for a non-MASTER file (e.g. DBALL) and that file exists, then the DELETE
is ignored and UFM 773 is issued:
ASSIGN MASTER='model.MASTER'
ASSIGN DBALL='model.DBALL', DELETE

ENDJOB
THE FOLLOWING PHYSICAL FILE ALREADY EXISTS.
LOGICAL NAME = DBALL
PHYSICAL FILE = model.dba
USER INFORMATION: NO ASSOCIATED DEFAULT FILES OR ASSIGNED DBSETS CAN EXIST
PRIOR TO THE DATA BASE INITIALIZATION RUN.
USER ACTION: DELETE THIS FILE AND RESUBMIT THE JOB.
Behavior corrected after 2004r3 - 2005r3, 2007r1, MDr2 all honor the DELETE
entry. Verified 6/7/07 JSwan
Avoidance: Manually remove all files used on ASSIGN statements prior to run
1-17706203
2005.5
Materials - MCSID - UFM 2025
Large, eight digit, MCSID IDs may incorrectly lead to UFM 2025.
50500099
Avoidance: Use smaller ids.

1-17724607
- SFM 1126
2005.0.2
Optimization/Design Sensitivity - MFLUID
If an optimization model contains MFLUID entries, the job will fail with the
following messages.
DMAP MODULE MGEN
USER ACTION: DELETE THE DATABLOCK, OR USE FILE MAR=OVRWRT
204 NAME = MAR
Avoidance: Insert the following alter.

compile phase1a
alter 'delete.*\/belm'
delete /mar,,,, $
endalter $
1-17727701
2005
Dynamics - DELAY - SFM 3002 (DPD), Specif
ying DELAY for dof with no excitation
Specifying DELAY data for DOFs without any excitation may lead to SYSTEM FATAL
MESSAGE 3002 on a call to SKPREC in the DPD module.
1-17733738
2005.5
=1, Wrong Description
Documentation/QRG - PBEND - Remark 3, FSI
Remark 3 under the PBEND description in the QRG incorrectly and incompletely
describes the equation for FSI=1.
It should read as follows:
The flexibility factor is set to unity. The stress intensification factor in
plane 2 using the general or alternate format is set to unity and for plane 1
it is set as follows:
[equation]
where r-elem is C1, D1, E1 or F1 of the stress points. If any of these values
are exactly zero, then S1 is set to unity.
1-17749511
2005
Loads - TEMP - Wrong Answers
Remark 2 under the QRG description of the TEMP entry indicates that; Set ID
MUST be unique w.r.t all other LOAD-type entries if TEMP(LOAD) is used.
However, this is not enforced as a fatal error and can lead to wrong answers.
1-17764701
2005.1
e Static Aero Subcases - Incompatible Matrices, SFM 4276
If a SOL 200 run is made with multiple static aero boundary conditions and the
subcases have different externally applied loads, the sensitivity analysis can
produce either wrong answers and go down paths that cause the solution to fail
with a message that indicates incompatible matrices or a divide by zero errors.
Avoidance: One avoidance is to remove the external loads. A more complete
avoidance is to make the following NDDL change:
PATH ULNDEL
SEID,PEID,MPC,SPC,SUPORT,
DESITER,PVALID,APRCH,HIGHQUAL,
AUXMID,ADJOINT,DESINC,DISCRETE $ METH
and make the following dmap alters:

compile fea
alter 'bcdr'(5),'bcdr'(5)
BCDR
CASEM//SEID/' '/0//true/
S,N,SPC/S,N,MPC/S,N,SUPORT/s,n,load///S,N,BC $
compile pslgdv
BCDR
CASEM//SEID/' '/0//true/
BCDR
CASEbc//SEID/' '/s,n,nskip//s,n,bcflag/
alter 'segoa'(2)
dbstatus auads//s,n,noaua $
alter 'nopa'(8),''
if ( nopa<1 and noaua> 0) then $
alter 'pav'
NSKIPL=NLOADS+NSKIPL $ LOADS ACCUMULATOR
alter 'pmav'
nskplm=nloada+nskplm $ unrestrained loads accumulator
alter 'nskplm'(4,-1),'nskplm'(4)
compile gendv2p
alter 'nddl','nddl'
TYPE PARM,NDDL,I,N,MPC,SPC,suport,templd,deform ,load $
alter 'bcdr','bcdr'
BCDR
CASE0//0/' '/
S,N,NSKIP/S,N,NLOADS/S,N,BCFLAG/
S,N,SPC/S,N,MPC/S,N,SUPORT/s,n,load////-1 $
compile xsedrdr
alter 'bcdr','bcdr'
BCDR
CASEbc//SEID/' '/s,n,nskip//s,n,bcflag/
1-17766002
c
Documentation/Case Control - SET - Possible Traceback in sdr2
Depending on the use, the SET Case Control command may contain a list of
integers or a list of real numbers. However, there is no application where the
list would contain both integers and real numbers. MSC.Nastran does not know
the intent of the set until it is referenced. If a set contains integers when
it should contain real numbers or vice versa, nastran may issue a traceback.
A traceback has been encountered in sdr2c but other routines are possible.
1-17767304
2005.1
Documentation/QRG - ADAMSMNF - SWM 7804 No stresses/strains written to ADAMS mnf file
Attempt to output solid element strains (CHEXA, CPENTA, CTETRA) into the Adams
mnf file using the ADAMSMNF command will not work and will result in the
message:
SYSTEM WARNING MESSAGE 7804 (AFERRM)
THE ADAMS/FLEX MNF GENERATION MODULE INPUT GRID POINT STRAIN DATA BLOCK OFP
TABLE CODE IS NOT RECOGNIZED.
OFP TABLE CODE IS 28. REQUEST FOR GRID POINT STRAIN OUTPUT IS IGNORED.
No stresses or strains are written.
Avoidance: Do not use PRINCIPAL on the VOLUME command. Explicitly use DIRECT
to output stresses/strains into the mnf file. It is a restriction in the
ADAMS/Flex interafce that it accepts only direct stresses and not principal.
The ADAMSMNF command in the QRG needs a comment to this effect.
1-17769313
2005
olation on Window
Submittal - Estimate fails with Access Vi
Estimate may fail with an Access Violation message on Windows.

Avoidance:
not run.
Specify mem= on the nastran submittal line so that estimate does
1-17776102
2005
er due to DOF-based ordering
Performance - Krylov performance may suff
The Krylov solver uses CFACTR to do the decomp for frequency response. This
path to decomp uses degree-of-freedom based ordering. It should call CFACTR2
instead which uses grid based ordering.
1-17777901
rect
2005
Performance - FASTFR check in GMA not cor
If any structural matrices are missing, for example there are no fluid
elements, the check in GMA to determine if FASTFR can be used is not correct.
This may lead to slower run times.
dfbella>>> New checking implemeted.
1-17790001
2005
ives wrong results
SOL 600 - Temperature Loading with offs g
For SOL 600 an option has been added to apply thermal loading at the original
node, the offset node or both. This is activated by a new parameters in
Nastran 2005 named marcofft and moffcore. The defaults for these new
parameters cause the temperature loading to be applied at both nodes. Models
now gets the same thermal strains using SOL 600 and 106.
1-17793896
Not Work
2005
Nonlinear Analysis - PARAM SRCOMPS Does
Nastran PARAM SRCOMPS, strenth ratio for composite analysis, does not work for
nonlinear analysis.
1-17812511
ss Violation
2005.0.2
DBC - PARAM,NOCOMPS,-1 - DBC Module, Acce
Data decks with param,nocomps,-1 may fail in the DBC module in routine dbcgps.
Avoidance: Do not use param,nocomp,-1 for 2004 and later systems since it has
no meaning any more. The only valid number are 0,1,2.
1-17812519
R2)
2005.0.2
Composites - STRAIN, PCOMP - SFM 3005 (SD
A request of only strain output for composite elements causes SDR2 to issue
Avoidance: Add a STRESS request.
1-17818401
2005.0.2
G, BGE, or BEE is specified for OFFT
Elements - CBAR, CBEAM - UFM 2026 when BG
UFM 2026 indicating illegal geometry is generated for CBAR/CBEAM elements when
the orientation vector for the element is defined using the reference grid
point (G0) option and the OFFT (field 9) value specifies BASIC (Bxx codes) for
the orientation vector.
Avoidance: Specify GLOBAL (Gxx) code for the orientation vector.
1-17835201
2005
FM 3002 in GPSP
Buckling - Multiple buckling subcase - S
Solution 105, buckling, may fail in MSC.Nastran 2004 with SYSTEM FATAL MESSAGE
3002 in the GPSP module if multiple buckling subcases exist.
1-17845802
ers
2005
Rotordynamics - LOAD, RFORCE - Wrong Answ
In a static analysis with rotors, the gyroscopic moments may be missing from
the load vecotr if the LOAD Case Control Command references a LOAD Bulk Data
Entry.
Avoidance: The LOAD Case Control Command should reference the RFORCE Bulk Data
Entry directly without using the LOAD Bulk Data Entry.
1-17865308
2005
Optimization/Design Sensitivity - PARAM,X
YUNIT,PUNCH(NEWBULK) - No punch file written, csv incomplet
The DOM12F subroutine does not place any limits on the length of a record
created that is to be written to the csv file. Machine limits exist and the
program needs to be redesigned to write within these limits.
Error message on AIX:
1525-005 The formatted I/O statement on the internal file cannot be completed
because the end of the record was reached. The program will recover by
ignoring the remaining data items in the I/O statement.
XL Fortran (initialization): Out of memory.
Error on 32bit Linux:
Input/Output Error 154: Wrong length record
In Procedure: dom12f
At Line: 319
Statement: Formatted WRITE
Unit: Internal File
Record Number: 1
1-17867401
2005
Acoustics - param,panelmp - Panel grid Mo
de Participation Factor output incorrect
Structure Mode Participation Factor output for panel grid points is incorrect
if any fluid grid point id is less than the largest id of the structural grid
points in the problem. All other MPF output is accurate.
Avoidance: Make sure that all fluid points have IDs greater than the largest
ID of the structure grid points.
1-17870204
E1)
2005.0.2
Rotordynamics - SPARSEDR - SFM 6143 (UMRG
SOL 108 with superelements and rotordynamics may fail with the folloiwng
message:
*** SYSTEM FATAL MESSAGE 6143 (UMRGE1)
SPECIFICALLY:
The number of rows
in RXMG is not equal to the size of the M-set
User Information: Size of input matrices and DOF sets:
RXMG
: Rows=
129 by Cols=
153
Set sizes: Major (G-set)=
5796
Set0 (M-set)=
1988
Set1 (COMP-set)=
3808
Avoidance: Insert param,sparsedr,no or following DMAP alter
compile fdrmgen
alter 'equivx rxmgx\/rxmg',''
alter 'paraml rmgg'
if ( spdrm ) then $
equivx rxmgx/rxmg/-1 $
delete /rgm,,,, $
trnsp
rxmg/rgm $
endif $
endalter
1-17883701
2005.0.2
MAT8, DVMREL - UFM 316
Punched output from a SOL 200 analysis that uses DVMREL optimize PCOMP and
MAT8 may contain invalid data and cause a subsequent nastran job to fail with
USER FATAL MESSAGE 316.
1-17889001
2005
Rigid Elements - PARAM,AUTOMSET,YES fail
s with multiple boundary conditions or SOL105
Runs with PARAM,AUTOMSET,YES could fail in SOL 105 or with multiple BC with UFM
1126 (GNFIST) (matmod attempting to output GM which already exists).
Avoidance:
compile sekr0
alter 'xmce1',''(,1)
TYPE PARM,NDDL,CHAR8,Y,automset $
IF ( NOGM=-1 or automset='yes' ) then $
if ( automset='yes' ) delete /gm,,,, $
call xmce1 USET1,RMG1,KGG/GM,nuset/rsonly $
dbstatus nuset//s,n,nonuset $
IF ( getsys(np,400)<>0 and nonuset>0 ) equivx nUSET/uset1/always $
endif $
1-17889901
2005.0.2
GEOM2 NDDL descriptions
Elements - CWSEAM - TABPRT, conflicts in
The format of the CWSEAM entry is changed after MODGM2 module. This results in
conflicts in NDDL descriptions for this element type and the TABPRT contents of
GEOM2 data block won't match the labels.
1-17907360
2005.1
Rigid Elements - RIGID(LAGRAN) - Lagrange
RBE2 with TEMPD and TEMP produces SFM 3003
Lagrange RBE2 with TEMPD and TEMP causes the following error.
*** SYSTEM FATAL MESSAGE 3003 (SSG1)
1-17976601
2005.0.2
Documentation/QRG - MCFRACTION
Remark 7 of the Quick Reference Guide description of the MCFRACTION case

control command states that the filter applies to the sorting KEY item.
However, this is incorrect. The filter is always applied to the RESPONSE
magnitude, regardless of which item has been used to produce the sorted
listing. 1-17983301
ut
Optimization/Design Sensitivity - ANALYSIS=MFREQ - Extra Outp
An optimization job with analysis=MFREQ that requests response data recovery,

for example spcforce, not only outputs the complex dynamic responses but also
prints out the real SPCFORCE obtained from the Normal Modes analysis.
1-18016846
2009.0.0 (MD R4)
KAM - Poor Message, SFM 3001
Frequency Response - SDAMPING, TABDMP1, G
If a SDAMPING request is made in the case control but no TABDMP1 entry is

supplied in the bulk data, the analysis will fail in the GKAM module and the
following message will be issued:
*** SYSTEM FATAL MESSAGE 3001 (GKAM)

THE INPUT DATA BLOCK NAMED DIT
1-18048305
2005
missing in V2004
AT POSITION
5 DOES NOT EXIST.
Installation/Documentation - buildsss.bat
The Version 2004 delivery is missing \msc\msc2004\nast\del\buildsss.bat

Avoidance: Copy the attachment buildsss.bat.del to \nast\del\buildsss.bat.
The IOG Documentation indicates: "msc2004 buildsss src=." However, for
Windows, the "src=" is an improper format. The correct format for Windows
should be: msc2004 buildsss full_path_of_source
1-18070913
2005.5
Documentation/QRG - MAXMIN(def), QUAD4, T
RIA3, Corner Stresses - Missing Documentation
The MAXMIN(DEF) for corner stresses of a CQUAD4 or CTRIA3 requires the element
specifation to be CQUAD4C or CTRIA3C.
1-18076410
Heat Transfer - CTETRA - Fails to Converge
Nonlinear heat transfer models with CTETRA 10 elements may fail to converge.
Avoidance: Do not use the CTETRA 10 noded element in nonlinear heat transfer.
Use the 12 noded CTETRA or the CHEXA element.
1-18089601
2005
Optimization/Design Sensitivity - PCOMP Z
ero sensitivity coffecients for composites
A composite optimization job may produce zero sensitivity coefficients if the
following conditions are met:
1) two or more material properties are being designed,
2) one of the designed material properties is referenced by the PCOMP entry.
Avoidance: Design a material property either being referenced by a PCOMP entry
or by other property types, not both.
1-18108004
Superelements - SPARSEDR, SPCD - Wrong Answers
When SPCD enforced motion is employed in an environment that involves part

superelements or traditional superelements, data recovery in the superelements
gives wrong results for the interior points of upstream superlements.
Avoidance: Two possible avoidances exist. Either turn off sparse data
recovery by setting:
param,sparsedr,no
or apply the following dmap alter.
compile spdr1
alter 'call xAdd5 vscg0,vmcg,vadr,z01dr0,vyg'
add5
v01z,vupse,,,/zzz $
equivx zzz/v01z/-1 $
endalter $
1-18126001
2005
Data Recovery - SORT2 in static and trans
ient analysis - Excessive disk space usage
IIn static and transient analysis when SORT2 or XYPLOT output is requested an
unnecessary SDR3 operation occurs. On large problems this can require large
amounts of disk space.
compile sedrcvr
alter 'strsort'
if ( not sort2mm ) sdr3
oes2s,,,,,/oes1x1,,,,, $
alter 'strsort'(,1)
if ( not sort2mm ) equivx oes1x/oes1x1/-1 $
alter 'sdr3
oes2s,,,,,',''
1-18136004
2005.0.2
es - Wrong Answers
Data Recovery - MAXMIN(DEF) two item cod
The following format of the maxmin(def) commands cause incorrect data recovery.
The RMS for the second item code was zero. Also, the Z2 von mises stress was
wrong for Z2.
MAXMIN(DEF) STRESS QUAD4 9 MAXALG(1) RMS
MAXMIN(DEF) STRESS QUAD4 17 MAXALG(1) RMS
Avoidance: Combine the items requested on one command, as shown below.
MAXMIN(DEF) STRESS QUAD4 9 17 MAXALG(1) RMS
1-18137202
2005.0.2
Missing Monitor Point Output
Aeroelastic Analysis - AECOMP, MONPNT1 -
No Error message is issued when the COMP field on the MONPNT1 entry points to a
nonexistent AECOMP entry. Instead, the MONPNT1 entry is just ignored and no
output is generated for it.
1-18154902
2005.0.2
es and scr=no - UFM 1126
Frequency Response - Multiple FREQ subcas
When using scr=no with multiple frequency subcases with one of the subcase
having the same DLOAD and FREQ request as a prior subcase the run will fail
with:
DMAP MODULE FRLG
USER ACTION: DELETE THE DATABLOCK, OR USE FILE PPF=OVRWRT
DMAP MODULE FRLG
USER ACTION: DELETE THE DATABLOCK, OR USE FILE FOL=OVRWRT
201 NAME = PPF
204 NAME> > = FOL

compile semfreq
alter 'IF ( NOT NOPH2 and extdr',''
dbstatus uhf//s,n,nouhf $
IF ( nouhf<1 and NOT(NOPH2) and extdr='no' ) THEN $
endalter
1-18177902
2005.0.2
PARAM AKMPOST - SFM 6144
Acoustics - PARAM,FLUIDSE or GDACMS with
If PARAM,AKMPOST,YES is requested in a run with GDAMCS or PARAM,FLUIDSE then

the run will fail with SFM 6144.
Avoidance: Insert the following DMAP alter or use MDACMS (domainsolver
acms(partopt=dof)):
compile mpf
alter 'call akmpost',''
if ( akmpost='yes'
) call akmpost lamas,lamaf,mpfmap,sils,eqexins,fmpfz,smpfz,
pmpfz,lmpfz,vafs,usetd,phdh,uhfs,vphfs,agg,
vgfs,uset,phgg,casef,ogx,fol1,mfhh,bfhh,kfhh,
bgpdts,sil,vgxfs,usetg,PHGXFH1,uhfs/
scratch/
noue/nophfa/nophsa/noog/noa/noload/nofreq/
noshset $
compile akmpost
alter 1,1
subdmap akmpost lamas,lamaf,mpfmap,sils,eqexins,fmpfz,smpfz,
pmpfz,lmpfz,vafs,usetd,phdh,uhf1,vphfs,agg,
vgfs,uset,phgg,cases,ogx,fol1,mfhh,bfhh,kfhh,
bgpdts,sil,vgxfs,usetg,PHGXFH1,uhfs/
scratch/
noue/nophfa/nophsa/noog/noa/noload/nofreq/
nosehset $
type parm,,i,n,nosehset $
alter 'if ( nophfa=-1',''(,9)
equivx uhf1/uhfs/-1 $
equivx phdh/phdfh/-1 $
else $
partn
PHDH,VPHFS,VAFSE/,,,PHDFH/1 $
endif $
alter 'matmod v6d,sils',''
matmod v6d,sil,,,,/v6g,/5 $
alter 'PARTN
RPHSA,,VGFS',''(,2)
MATGEN ,/ROT456x/6/6/0/3/3 $
PARTN
RPHSA,,VGxFS/RPHST,,,/1 $
MATMOD ROT456x,SIL,,,,/O1x,/4 $
DELETE /ROT456x,RPHSA,,,/ $
PARTN
O1x,,VGxFS/ROT456x,,,/1 $
PARTN
RPHST,,ROT456x/,RPHSA,,/1 $
alter 'EQUIVX VAFS\/OA',''(,7)
equivx phgxfh1/phdfh1/-1 $
compile super3
alter 'if ( rsonly or sebulk',''
if ( rsonly or (sebulk and not(acms)) ) then $
1-18182101
2005.1
External Superelements - EXTSEOUT(DMIGPCH
) - Missing output for interior points of external SE.
If the DMIGPCH option is employed in the EXTSEOUT command to create an external
SE, the subsequent assembly run fails to give output for interior points of the
external SE. The output is obtained only for the boundary points of the
external SE.
compile super3
alter 'call extotmin'(,-2),''(,0)
file tug1=ovrwrt/tes1=ovrwrt/tef1=ovrwrt/tqg1=ovrwrt $
call dbfetch /dtis,dtindxs,dmis,dmindxs,/seid/0/0/0/0 $
dtiin
dtis,dtindxs/
tug1,tes1,tef1,tqg1,,,,,,/
s,n,notug/s,n,notes/s,n,notef/s,n,notqg $
exterse=(exterse or notug or notes or notef or notqg) $
if ( exterse ) then $
call extotmin maps,dmis,dmindxs,uset,eqexins,
xsop2dir,matpools/
tug1,mug1,tqg1,mqg1,tes1,mes1,tef1,mef1,
rga,ugo,mug1o,mqg1o,mes1o,mef1o/
statics $
call dbstore mug1o,mqg1o,mes1o,mef1o,//seid/0/'
'/0 $
compile phase0
alter 'call ifps'
call dbstore dmindxs,dtindxs,dmis,dtis,//seid/0/'
'/0 $
compile sedrcvr
alter 'MPYAD.*mug1,uls1,',''
call dbfetch /mug1o,mqg1o,mes1o,mef1o,/seid/0/0/0/0 $
if ( notug1>0 ) MPYAD mug1,uls1,mug1o/iugx $
alter 'MPYAD.*mef1,uls1',''
MPYAD mef1,uls1,mef1o/iefx $
alter 'MPYAD.*mes1,uls1',''
MPYAD mes1,uls1,mes1o/iesx $
alter 'MPYAD.*mqg1,uls1',''
MPYAD mqg1,uls1,mqg1o/iqgx $
compile extotmin
alter 1,1
subdmap extotmin maps,dmis,dmindxs,uset,eqexins,
xsop2dir,matpools/
tug1,mug1,tqg1,mqg1,tes1,mes1,tef1,mef1,rga,ugo,
mug1o,mqg1o,mes1o,mef1o/
statics $
alter 'dbview'
dbview x_mugo=extdb where (seid=temp and xname='mug1o' and wildcard)
dbview x_meso=extdb where (seid=temp and xname='mes1o' and wildcard)
dbview x_mefo=extdb where (seid=temp and xname='mef1o' and wildcard)
dbview x_mqgo=extdb where (seid=temp and xname='mqg1o' and wildcard)
alter 'if ( xname=',''
if ( xname='matrga' or
xname='tug1' or xname='mug1' or
xname='tes1' or xname='mes1' or
xname='tef1' or xname='mef1' or
xname='tqg1' or xname='mqg1' or
xname='mug1o' or xname='mes1o' or
xname='mef1o' or xname='mqg1o' ) then $
alter 'equivx.*x\_tqg',''(,3)
if ( statics ) then $
equivx x_mugo/mug1o/-1 $
equivx x_meso/mes1o/-1 $
equivx x_mefo/mef1o/-1 $
equivx x_mqgo/mqg1o/-1 $
endif $ statics
else $
dmiin
dmis,dmindxs/mug1,mes1,mef1,mqg1,,,,,, $
if ( statics
) dmiin
dmis,dmindxs/mug1o,mes1o,mef1o,mqg1o,,,,,, $
matmod
equivx
matmod
equivx
matmod
equivx
matmod
equivx
mtrxin
merge
equivx
merge
equivx
merge
equivx
merge
equivx
tug1,,,,,/tug1x,/32/1 $
tug1x/tug1/-1 $
tef1,,,,,/tef1x,/32/1 $
tef1x/tef1/-1 $
tes1,,,,,/tes1x,/32/1 $
tes1x/tes1/-1 $
tqg1,,,,,/tqg1x,/32/1 $
tqg1x/tqg1/-1 $
,,matpools,eqexins,,/vax,,,,/lusets $
,,,mug1,,vax,/mug1x/1 $
mug1x/mug1/-1 $
,,,mef1,,vax,/mef1x/1 $
mef1x/mef1/-1 $
,,,mes1,,vax,/mes1x/1 $
mes1x/mes1/-1 $
,,,mqg1,,vax,/mqg1x/1 $
mqg1x/mqg1/-1 $
compile extout
alter 'SDR2.*CASEs'
dbstatus uoo//s,n,nouoo $
if ( nouoo>0 ) then $
umerge uset,uoo,/ugo/'g'/'o' $
dbstatus v01s//s,n,nov01s $
if ( nov01s>0 ) then $
Partn
ugo,,v01s/,ugo1,,/0 $
delete /ugo,,,, $
merge
,,ugo1,,,,v01s/ugo/0 $
endif $ nov01s>0
SDR2
CASEs,CSTMS,MPTS,DIT,EQEXINS,,ETT,nulllama,BGPDTS,,qg,
DRMH1
Iug1o,Iqg1o,Ies1o,Ief1o/
TUG1o,MUG1xo,TQG1o,MQG1xo,TES1o,MES1xo,TEF1o,MEF1xo/
/1/7/3/1005/1004 $
add5
mug1xo,,,,/mug1o $
add5
mqg1xo,,,,/mqg1o $
add5
mes1xo,,,,/mes1o $
add5
mef1xo,,,,/mef1o $
endif $ nouoo>0
alter 'EQUIVX mug1\/EXTDB'
xname = 'mug1o' $
EQUIVX mug1o/EXTDB/-1 $
alter '15.*\'mug1'
append ,,/xsop2dir/15///////'mug1o' $
alter 'EQUIVX mqg1\/EXTDB'
xname = 'mqg1o' $
equivx mqg1o/extdb/-1 $
alter '15.*\'mqg1'
append ,,/xsop2dir/15///////'mqg1o' $
alter 'EQUIVX mes1\/EXTDB'
xname = 'mes1o' $
equivx mes1o/extdb/-1 $
alter '15.*\'mes1'
append ,,/xsop2dir/15///////'mes1o' $
alter 'EQUIVX mef1\/EXTDB'
xname = 'mef1o' $
equivx mef1o/extdb/-1 $
alter '15.*\'mef1'
append ,,/xsop2dir/15///////'mef1o' $
alter 'matpch mug1'
matpch mug1o,mqg1o,mes1o,mef1o/ $
alter 'xname=\'mug1\''(,2)
xname='mug1o' $
alter 'xname=\'mqg1\''(,2)
xname='mqg1o' $
alter 'xname=\'mes1\''(,2)
xname='mes1o' $
alter 'xname=\'mef1\''(,2)
xname='mef1o' $
endalter
1-18187316
rong answers
2005.0.2
Elements - CBUSH, PBUSH and PBUSHT (KN) w
In Version 2004, if K1 is left to be blank on the PBUSH or PBUSHT entries, the

default value should be zero; however, an error in ifp may results in
unexpected values being used resulting in wrong answers..
Avoidance: If a zero stiffness is desired, explicitly specify 0.0, do not
leave the k1 field blank.
1-18192403
2005
mp , SYSTEM(221) - Wrong Answers
Matrix Methods - Complex Unsymmetric Deco
MSC.Nastran HPUX systems are the only ones that set the rank of update for
complex unsymmetric sparse decomp to greater than 1. This can lead to wrong
answers.
Avoidance: On HP system set system(221)=1 in the nastran rc file. On all
other systems do not set this system cell.
1-18215901
Temperature Loads - CHEXA - Non uniform temperature on HEXA e
lement - UFM 4661
HEXA models with constant material values defined on the MATT1 entry may fail
to converge even though the same models converge when the MATT1 entry is
removed or a constant temperature is applied. Other elements have not
demonstrated this behavior.
Avoidance: If there is no temperature depencency, remove the MATT1 entry.
1-18217901
423
2005.0.2
Dynamic Response - RESTARTS, SPCD - UFM 5
Dynamic response restart jobs (SOL 108, 109, 111, and 112) may not handle
enforced motion correctly. This may result in wrong answers in V2001 and
V2004, but causes termination of the job with UFM 5423 in the FRLG module in
V2005.
Avoidance: Two avoidance schemes exist.

------------1. Use a dummy (unused) FORCE or DAREA Bulk Data entry in the restart job.
2. Employ the following DMAP alter in the restart job:
compile semfreq $ for sol 111 (use sedfreq for sol 108, sedtran for sol109 and
semtran for sol112)
alter 'dpd '(,-1) $
paraml yg//'trailer'/1/s,n,ygcols $
paraml pg//'trailer'/1/s,n,pgcols $
type parm,,i,n,extracol $
extracol = ygcols - pgcols $
$ append extracol null columns to pg
append pg,/pgnew/1//extracol $
delete /pg,,,, $
equivx pgnew/pg/-1 $
1-18228729
00
2005.0.2
Miscellaneous - Unicode text causes UFM 3
If a file is saved as unicode text, the nastran job may fail with the following
message
*** USER FATAL MESSAGE 300 (RCARD)
DATA ERROR IN FIELD UNDERLINED.
EMBEDDED BLANK.
If you look at the file in Nodepad, it appears to look ok. However, if you
look at it in a vi editor, you will see blanks between each character
Avoidance: Save the file in standard text format
1-18235402
2005.0.2
or CWELD elements
CWELD Elements - Wrong Bearing Stresses f
The bearing stress should equal the resultant of the shear forces divided by
the (cweld diameter x minimum thickness of the connected shell elements).
However, the dependency on the minimum thickness TMIN is broken and the output
for the bearing stress is equal to simply the Shear Force divided by the
Weld Diameter.
This error has been verified by the initiator.
1-18239502
2005.0.2
ices and DTI tables are allowed
Size Limitation - Maximum of 120 DMI matr
A maximum of 120 unique DMI matrices and 120 tables are allowed in the input.
In Version 2001 an attempt was made to increase the limit to 1000 but the
change was incomplete.
1-18291503
2005
Superelements - EXTSEOUT - SFM 3002 (Lo
gic Error 29) in the BDRYINFO module.
Double field GRID entries for interior points of exterior superlements may
result in:
*** SYSTEM FATAL MESSAGE 3200 (BDYINP)
LOGIC ERROR
29 ENCOUNTERED IN SUBROUTINE BDYINP
USER ACTION: REPORT THIS PROBLEM TO MSC CLIENT SUPPORT

in the BDRYINFO module.
Avoidance: Use single field GRID entries or double field GRID entries with the
grid IDs in columns 9-16
Alternatively, as indicated above, first get the Bulk Data deck punched out by
Nastran and then use this punched deck as input. This will cause the GRID IDs
in the double field entries to be left justified (in columns 9-16).
1-18300703
Elements - Different Warping Coefficients for PBEAML with BOX
and BOX1 Cross Section
The BOX and BOX1 cross sections of the MSCBML0 group yield inconsistent warping
coefficients for the same cross section. The BOX cross section yields a 0.0
value for the warping coefficient while the BOX1 will be nonzero. To include
warping included, use the BOX1 cross section. The problem is also present in
Patran and its Beam Library so ensure that the fix gets to both programs.
1-18300741
(DPD)
2005.0.2
Modal Transient Analysis - TIC - UFM 2133
In SOL 112, when a degree of freedom is specified on a TIC entry that is not in
the a-set the job will fail appropriately with the message:
USER FATAL MESSAGE 2133 (DPD)
*** USER FATAL MESSAGE 2133 (DPD)
INITIAL CONDITION IN SET
1 SPECIFIED FOR POINT NOT IN ANALYSIS SET.
However, the message does NOT indicate the grid and component. When a large
number of TIC are present in the input file it is difficult to identify the
problem input.
1-18419669
2005.0.2
Postprocessing - MPC data in GEOM4 databl
ock created by module MAKEOLD is not in single precision
If the model contains MPC entries, and the MAKEOLD module is used to convert
the MPC entries in the GEOM4 datablock to single precision, the conversion does
not take place. This happens for instance when PARAM,POST,-1 or -2 are
requested and PARAM,OGEOM,YES (default) is used. The error was reported
because IDEAS was terminating when reading an op2 file created using
PARAM,POST,-2.
In addition to being corrected in the 2005r2 release, this
error was corrected in a special build of 2004.5.1 on AIX, IRIX, and Sunos
only. This system was not written to cd and is only availalbe from MSC's
internal ESD site.
Avoidance: Insert the following DMAP alter for 2004.5. This alter wil create
an op2 file compatible with V2001 when either PARAM,POST,-1 or -2 is specified
and NASTRAN OP2NEW=0. The alter deletes the erroneous MPC data from the GEOM4
datablock so it does not get written to the op2 file.
An alter is also available that converts the double precision MPC data to
single precision using the table insert functions of the PARAML module to
create a single precision MPC data record which is then added to the GEOM4
datablock after MAKEOLD processing.
NASTRAN OP2NEW=0
ECHOOFF $
$ V2004.5 op2 in 2001 format, post -1 and post -2
$
COMPILE OUT2GEOM NOLIST $
ALTER 'MAKEOLD GEOM4','' $
TYPE PARM,,I,N,RECNUM=1 $
$
$ remove MPC entries from GEOM4
DO WHILE (RECNUM>0) $
PARAML GEOM4//'DTI'/S,N,RECNUM,/1//S,N,ID1 $
PARAML GEOM4//'DTI'/S,N,RECNUM,/2//S,N,ID2 $
EQUIVX GEOM4/GEOM4Z/RECNUM $
IF (ID1=4901 AND ID2=49) THEN $
PARAML GEOM4/GEOM4Z/'TABDEL'/RECNUM/0 $
RECNUM=-1 $
ELSE $( RECNUM=4901 AND ID2=49)
RECNUM=RECNUM+1 $
ENDIF $ (RECNUM=4901 AND ID2=49)
ENDDO $ (RECNUM>0)
MAKEOLD GEOM4Z,GEOM3,,,/GEOM4X,GEOM3X,,,/
'GEOM4'/'GEOM3'////'GEOM4'/'GEOM3' $
$
$ for post -2
$
ALTER 'OUTPUT2 CSTMX' $
TYPE PARM,,I,N,NP $
IF (GETSYS(NP,403)=0) THEN $
MATMOD GEOM2X,,,,,/IGEOM2X,/13 $
matprn geom4,geom4x // $
$ OUTPUT2 IGEOM2X,GEOM3X,GEOM4X,GEOM1X,BGPDTX//0/OUNIT1//OMAXR/
$
'GEOM2'/'GEOM3'/ GEOM4 / GEOM1 / BGPDT /
$
'GEOM2'/'GEOM3'/'GEOM4'/'GEOM1'/'BGPDT' $
OUTPUT2 IGEOM2X,GEOM3X,GEOM1X,BGPDTX//0/OUNIT1//OMAXR/
'GEOM2'/'GEOM3'/ GEOM1 / BGPDT /
'GEOM2'/'GEOM3'/'GEOM1'/'BGPDT' $
ELSE $
ALTER 'OUTPUT2 GEOM2X' $
ENDIF $
$
$ for post -1
$
ALTER 'ELSE IF ( POST=-1' $
IF (GETSYS(NP,403)=0) THEN $
MATMOD GEOM2X,,,,,/IGEOM2X,/13 $
OUTPUT2 GEOM1X,IGEOM2X,GEOM3X,GEOM4X,EPTX//OTAPE2/OUNIT1//OMAXR/
GEOM1 / GEOM2 / GEOM3 / GEOM4 / EPT /
'GEOM1S'/'GEOM2S'/'GEOM3S'/'GEOM4S'/'EPTS' $
OUTPUT2 MPT,DIT,DYNAMICS//0/OUNIT1//OMAXR $
IF ( POSTEXT='YES'
) OUTPUT2 BGPDTX//0/OUNIT1//OMAXR/BGPDT/////'BGPDTS' $
ELSE $
ALTER 'OUTPUT2 BGPDTX' $
ENDIF $
ENDALTER $
ECHOON $
1-18435118
Miscellaneous - ASSIGN OUTPUT2 - Poor Messages, UWM 333, UWM
334, SWM 3001 (SEP1X)
If the ASSIGN OUTPUT2 statement is NOT specified correctly, various fatal
messages that do not point to the problem may be issued. For example, the
following assign statement:
ASSIGN OUPUT2=.op2', UNIT =12, FORM = FORMATTED

lead to the following messages in the f06 file. :
*** USER WARNING MESSAGE 333 (GETLIN)
THE BEGIN BULK STATEMENT IS MISSING. A BEGIN BULK STATEMENT WILL BE
INSERTED BY THE PROGRAM
*** USER WARNING MESSAGE 334 (GETLIN)
THE ENDDATA STATEMENT IS MISSING. AN ENDDATA STATEMENT WILL BE INSERTED BY
THE PROGRAM
0
INPUT BULK DATA ENTRY COUNT =
1
0
TOTAL COUNT=
1
2 DOES NOT EXIST.
102 AND SUBROUTINE IS SEP1X
This is not specifically an ASSIGN statement problem but a more general problem
with MSC.Nastran input file processing. When it encounteres mis-matched
quotes, unusual results can occur. In the example, all entries after the
ASSIGN statement with the mis-matched quote at the end of the OUTPUT2=op2'
string causes MSC.Nastran to collect all subsequent records as part of the
ASSIGN definitilon until it encounters a quote character that terminates the
ASSIGN statement.
1-18435641
2005.0.2
SOL 600/installation - Long Installation
Paths - ** Severe Marc Translator Warning **
For SOL 600, long path names for the location of the marc executable will cause
a failure on Windows. The default installation paths for MSC.Nastran V2005
are longer and thus this problem is exacerbated.
** Severe Marc Translator Warning ** Script to run Marc not in expected
directory
\\benelux1\applic\windows\msc.software\msc.nastran\2005\msc2005\marc\tools\run_m
1-18450701
2005.1
Nonlinear Analysis - CBAR, CBEAM with off
sets and param,lgdisp fails with UFM 6174
USER FATAL MESSAGE 6174 is incorrectly issued when a nonlinear model contains
bar or beam elements with offsets and param,lgdisp,-1. When param,lgdisp,-1
is specified the differential stiffness is not required, thus the fatal should
not be issued.
1-18482126
2005.0.2
- SFM 3001 (DOPR4) indicating DTOS2J does not exist
An optimization job that has a DESVAR Case Control command that only activates
shape variables but both sizing and shape variables are present, may fail in
DOPR4 with SYSTEM FATAL MESSAGE 3001 indicating that DTOS2J does not exist.
compile predom list
alter 'dopr1'
type parm,,i,n,protyp $
protyp = 0
1-18491202
2005.0.2
scription of Item SCALED
Documentation/QRG - MCFRACTION - Wrong De
Under the QRG description of the MCFRACTION Case Control Command, SCALED should
be described as the " PROJECTION DIVIDED BY THE LARGEST MAGNITUDE OF MODAL
RESPONSE".
1-18491296
2005.0.2
ALED RESPONSE MAGNITUDE" in the f06
MCFRACTION - Incorrect description of "SC
Description of the "SCALED RESPONSE MAGNITUDE" under the MODAL CONTRIBUTION

FACTORS output in the f06 is not correct. It should read:
PROJECTION MAGNITUDE DIVIDED BY THE LARGEST MAGNITUDE OF THE MODAL RESPONSE.
1-18501346
2005.0.2
a-set is comprised entirely of q-set
Dynamic Analysis - MEFFMASS fails if the
The modal effective mass calculation (MEFFMASS Case Control command) will
terminate with the following message if the a-set is comprised entirely of
q-set.
SYSTEM FATAL MESSAGE 3007 (3007)
ILLEGAL INPUT TO SUBROUTINE MPYAD
In GDACMS (domainsolver acms) and PARAM,AUTOQSET,YES, it is typically the case
that the a-set of the residual structure is comprised entirely of q-set.
This condition can also occur with component mode analysis.
Avoidance:
1. For non-GDACMS problems, insert some physical degrees-of-freedom on the
ASETi entries.
2. For GDACMS problems or PARAM,AUTOQSET,YES problems, either switch to
MDACMS (domainsolver acms (partopt=dof))
or insert the following DMAP alter:
compile augqset
alter 'usetq'(2)
type parm,,logi,n,npl $
moduset ,,usetq/usetz/'move'/'l'/'o' $
equivx usetz/usetq/-1 $
compile phase0
alter ' gp4 '(,-1)
if ( seid=0 ) atqset=false $
endalter
If you are running PARAM,AUTOQSET,NO with GDACMS then insert SENQSET,0,0 in the
Bulk Data section.
1-18504349
2005.0.2
elled as "MSC.Nastran 2004"
Online Documentation - V2005 Index is lab
The "start point" for the MSC.Nastran v2005 documentation on the Online
Documentation cd is labled "MSC.Nastran 2004 Books". The links for the
Installation & Operations Guide, QRG, and Release Guide DO bring up the v2005
documentation. The link to the DMAP Guide is missing.
New graphic pages without the year are to be used for future releases.
1-18511311
2005.0.2
FRACTION with MDACMS
MDACMS - MCFRACTION - Wrong Answers for M
If MCFRAC is requested with MDACMS (DOMAINSOLVER ACMS(PARTOPT=DOF)) then wrong

answers may result in the MCFRAC output.
1. Specify an additional output request, like DISP, for the same points
specified on the MCFRAC command.
compile semfreq
alter 'call fdrmgen',''
if ( sparseph='yes' and mdacms ) CALL FDRMGEN,
USET,VGFD,CASERS,USETD,GM,GOt,goq,,
MSF,,,,BSF,,,,KSF,K4SF,,,,asf,adsf,
MMG,,BMG,,KMG,K4MG,,KDMG,KDSF,,
MSS,,BSS,,KSS,K4Ss,,kdss,yg,
ects,bgpdts,sils,xycdb,matpool,pg,dynamics,casecc,
slist,emap,maps,,,,,mmcdb,oint,pelsets,
pmyg,pbyg,pkyg,ajp,,nzyg,/
,,,,,,,
MSF1,BSF1,KSF1,mss1,bss1,kss1,MMG1,BMG1,KMG1,,,,
vspcg,vmpcg,v01p,v01dr,vpg,vgdr,vmcfg,,,/
APP/APP/SOLTYP/FALSE/false/NOOSET/NOA/NOMSET/
S,DOMPCF/S,DOSPCF/NOSSET/NOUE/S,DOMPCFFD/
S,DOSPCFFD/FALSE/FALSE/rsonly/'
'/
s,spdrs/s,spdrm/pexist/false/s,spdr/adptindx/true $
type parm,nddl,logi,n,seindr $
seindr=true $
add5 vpg,vmcfg,v01p/vxx $
equivx vxx/v01p/-1 $
endalter
1-18516872
2005
-UX 13.1), SFM7620 occurs.
Submittal - mem=2800mb on NEC SX-6(SUPER
MSC.Nastran 2004.0.6 (2004r2) and 2005.0.0 (2005 R1) on Nec SX-6 computers may
fail with the fatal message shown below when a large memory request
(mem=2800mb) is made. This error has been corrected in 2005.0.1 delivered on
the 2005R1a cd.
*** SYSTEM FATAL MESSAGE 7620 (GP3D)

Dynamic memory block has incorrect checksum
1-18527891
2005.0.2
LED, Possble Wrong Answers
MDACMS - DMP, NUMDOM - K-PARTITIONING FAI
If the user specifies a relatively large value for the number of domains,
numdom, for a small problem in mdacms, the partitioner may fail and in rare
cases produce wrong answers.
When failure does happen the only message is
"K-PARTIONING FAILED". Nevertheless MDACMS continues.
Avoidance: Do no specify high values of numdom for small problems. Do not
deviate significantly from the defaults.
1-18540430
2005
Documentation - V2005 online CD may not
read properly on some CDs - Cannont Copy basic functions
The CD has been remanufactured and an installation has been added to eliminate
the cyclic redundency error. Please test out the new CD.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------It has been observed that the 2005 combined documentation CD may not load
properly on some CD drives. The following error will occur in this case:
Cannot copy basic_functions:
Data Error (cyclic redundancy check)
Avoidance: If available, use another CD drive.

1-18561858
ints
2005.5
Documentation/QRG - CELAS - Coincident Po
The following remark should be added under the celasi QRG description.
It is recommend that for most applications
entries be coincident and the displacement
congruent. Connecting non-coincident grids
systems can lead to models that do not pass
GROUNDCHECK case control).
1-18562191
2005.1
H - Extra Output
that the grids connected by celas

coordinate systems of each grid be
and/or noncongruent coordinate
strain energy checks (see
External Superelements - EXTSEOUT, DMIGPC
An EXTSEOUT SE creation run may output the stiffness matrix even though the
EXTSEOUT command explicitly requested only the LOADS to be DMIGPCH.
Avoidance: Apply the alter avoidance scheme given under the description of
error number 1-18908795.
1-18569569
2005.0.2
Model Checkout/Superelements - RBE3, PARA
M,CHECKOUT,YES - Bad diagnostics with SELOC
PARAM,CHECKOUT,YES may give bad diagnostic information when SELOC is present.
The bad diagnostics is for the EMH matrix which is an equilibrium check on MPCs
and constraint elements. The bad diagnostics will indicate a modeling error
when no error exists. .
Avoidance: Use another checking procedure, such as applying SPCDs in static
analysis that should move the structure as a rigid body. If the MPCs and
constraint elements pass this test they meet the equilibrium requirement.
1-18570326
LD)
2005.0.2
Elements - CWELD - Missing UFM 7549 (SEPW
Impropely defined cweld elements where the projection onto the surface cannot
be found may not be trapped and the job may fail unexpectedly.
1-18573051
2005.5
null unbalanced load output
Rotor Dynamics - NLRGAP - Wrong Answers,
If an NLRGAP entry is used in a rotor dynamics analysis (SOL129), then the

unbalanced force that is output with the NLLOAD command is equal to zero.
1-18589051
2005.0.2
with BETAMATCH referenced by DESSUB - SFM 3001
When an optimization job with BETA/MATCH DRESP2 response, it may fail in DOPR1
with SFM 3001 when the response is referenced by a DESSUB command.
Avoidance: Remove the offending DESSUB entry.
1-18602293
2005.5
MESSAGE 4405 (PRTPRN)
Eigenvalue Analysis - EIGRL - USER FATAL
For most real world problems the CRAY X1 Unicos system's acrhitecture is such
that it realizes a performance gain when MAXSET on the EIGRL entry is set to 12
rather than to default value of 7 used on most other machines. One small test
problem (s6821) diverged when trying to solve the eigenvalue problem. This
small test completes when MAXSET is changed to 7.
1-18612550
th NO = 2
Nonlinear Transient Analysis - TSTEPNL - UFM 5423, TSTEPNL wi
The entry:
TSTEPNL 2
2000
.0005
resulted in the following fatal message:

COLS ROWS FORM TYPE
NZWD DENS
2
58
TRAILER FOR PST1
IS 1002
TRAILER FOR IFS
IS 1001
Avoidance:
TSTEPNL 2
or
TSTEPNL 2
Use either:
2000
.0005
1-18622044
oor Message
2005.0.2
2001
.0005
1
2
Topology Optimization - TOPVAR, PWELD - P
MSC.Nastran 2005 topology optimization does not have a good fatal error message
if the PID entry referenced on a TOPVAE entry does not exist.
1-18625541
2005.0.2
Postprocessing - param,post - UIM 4114 w
hen writing large data blocks written to op2 file
When writing data blocks larger than 1GW to an op2 file in binary format, the
UIM 4114 data fields will overflow, causing '*********' to be put in the
messages. The correction is to accumulate the values in INTEGER*8 variables
and to change the format statements to I12. This will allow data blocks up to
1TW to be written to the op2 files without any UIM 4114 data field overflow.
For binary mode OP2 files, this was fixed as part of the code turned in to fix
quality number 1-18605381. For the time being, other possible error locations
have not been fixed because it has been determined that the possibility of the
error occurring is very low.
1-18635621
2005.0.2
Mass - NSM1 and NSML1 have alternate form
s which do not allow continuation - Missing Fatal Message
Tthe alternate forms of the nsm1 and nsml1 entries were designed and documented
not to allow for continuation entries.
If the user does have a continuation entry, the entire entry is processed as
the basic form with a single ID.
1-18636381
2005.0.2
Optimization/Design Sensitivity - Problem
s when a designed property is zero in SOL 200
The design optimization capability in SOL 200 of MSC.Nastran applies move
limits to the properties when solving the approximate optmization problem.
If the baseline property is 0.0, the move limits can be very small with the
result that a small movement in the design variables will result in a violated
constraint.
Avoidance: Avoid starting designs that result in a zero property value.
Examples are the design of an I12 term in a beam starting from a cross setcion
that has a plane of symmetry or the warping coefficents in a PBEAML with a box
section type that is square.
1-18640031
2005
Eigenvalue Analysis - EIGRL, MAXSET - Nan
values in Eigenvalue Table on Nec SX6
For most real world problems the NEC SX6 system's architecture is such that it
realizes a performance gain when MAXSET on the EIGRL entry is set to 15 rather
than the default value of 7 used on most other machines. For small problems,
nastran will automatically lower the MAXSET value. One small test problem
has been found that contained two static subcases (STATSUB) followed by two
eigenvalue analysis where the value was lowered to 8 and it should have been
lowered to 7. This resulted in Nan's being printed in the Eigenvalue summary
table.
Avoidance: If this problem is encountered, manually set the MAXSET value to
one lower than what is reported for "BLOCK SIZE USED". Solving the
eigenvalues for the two sucases in separate runs also avoided the problem.
This problem has been corrected in 2005.0.1 delivered on the 2005 R1a cd.
1-18642547
2005
Cyclic Frequency Response - SOL 118, REST
ART - Output Labled as Real instead of Complex on Nec SX6
A restart of SOL 118, Cyclic Direct Frequency Response in Version 2005 on Nec
SX6, may result in output being labled as Real instead of Complex.
Avoidance: Run the job as a cold start. This error is fixed in Versin
2005.0.1 delivered on the 2005 R1a cd.
1-18642630
2005
Superelement Component Mode Synthesis - P
ARAM,METHDCRMS - UWM 8592 (REIG), V2005 Nec SX6 Only
If param,methcrms is specified in a superelement eigenvalue analysis on V2005
Nec SX6, then the job may fail with the message:
(REIG).
Avoidance:
Other than not specifying this parameter, there is no avoidance.
1-18642659
on Nec SX6
2005
Miscellaneous - mem= = - SFM 7620 (GP3D)
If a mem= is specified to be greater than 2800mb on MSC.Nastran 2004r2 or 2005

on Nec SX 6 the job may fail with the message:
*** SYSTEM FATAL MESSAGE 7620 (GP3D)
Dynamic memory block has incorrect checksum
Avoidance: Make a smaller memory request
1-18643741
2005.0.2
l Normals (SNORM) - Wrong Answers
Superelements - Multi-MASTER method, Shel
Shell normals computed in the "SEMAP" run are not being saved for the
subsequent restart run and this may lead to poor answers.
Avoidance: Insert the following DMAP alter in all runs:
compile phase0
alter 1
type db gpsnt $
endalter
1-18678552
2005.1
ct updated PBEAM entries written to the punch file
In design optimization Incorrect updated PBEAM entries are written to the punch
file.
1-18679258
Nonlinear Analysis - GPFORCE, TEMP(LOAD) - GPFORCE incorrect
in nonlinear with thermal load
The GPFORCE balance is incorrect in SOL 106 when there is thermal load because
the themal load contribution is included twice. SOL 400 is correct.
Avoidance:
(1) Replace "SOL 106" by "SOL 400"

(2) Add "ANALYSIS=NLSTAT" in the case control deck (you really need
not do it in this deck since the default of ANALYSIS is NLSTAT in SOL 400.),
(3) Replace "SUBCASE" by "STEP" in the case control deck (you can also
skip this change since this test deck is single SUBCASE only.).
1-18688331
2005.0.2
Elements - CQUAD4, TRIA3, K6ROT - Incorre
ct drilling stiffness for membrane only elements.
In MSC.Nastran Version 2004, the default for K6ROT was changed from 0. to
100. The new default works well for most models, but membrane only elements
should use a K6ROT of 0.0.
Avoidance: For models created entirely of membrane only elements, set
param,k6rot,0.0.
1-18691831
2005.0.2
with PARTOPT=GRID
ACMS - UFM 740 (RDASGN) when using PACMS
In MSC.Nastran Version 2004.5 (2004r3) and Version 2005 if PACMS is used with
PARTOPT=GRID then the job may fail with USER FATA MESSAGE 740 (RDASGN).
*** USER FATAL MESSAGE 740 (RDASGN)
UNIT NUMBER
12 HAS ALREADY BEEN ASSIGNED TO THE LOGICAL NAME OP2
USER ACTION: CHANGE THE UNIT NUMBER ON THE ASSIGN STATEMENT AND IF THE
UNIT IS USED FOR
PARAM,POST,<0 THEN SPECIFY PARAM,OUNIT2 WITH THE NEW UNIT
NUMBER.
AVOID USING THE FOLLOWING UNIT NUMBERS THAT ARE ASSIGNED TO
SPECIAL FILES IN MSC.NASTRAN:
1 THRU 12, 14 THRU 21, 40, 50, 51, 91, 92. See the
MSC.NASTRAN INSTALLATIONS/OPERATIONS
GUIDE section on MAKING FILE ASSIGNMENTS for reference.
:
compile phase0 $
alter 'OUTPUT2 EQEXIN//0/OUNIT2//OMAXR', '' $
if (procid=1) OUTPUT2 EQEXIN//0/OUNIT2//OMAXR $
endalter
1-18693301
2005.0.2
ption of DOPTPRM is incomplete
Postprocessing/Optimization - NDDL descri
The NDDL description of the DOPTPRM is incomplete and this may cause the entry
to be mis-translated by the UGS/I-Deas translator.
1-18693701
eled
2005.0.2
Elements - CQUADR - Stress output mis-lab
In MSC.Nastran2005, if STRESS (CENTER) is specified for a CQUADR entry, "von

mises" stress output in the f06 file, will be outputted as "max shear."
STRESS(CENTER,VONMISES)
L E M E N T S
S T R E S S E S
( Q U A D R )
I N
Q U A D R I L A T E R A L
ELEMENT
FIBER
STRESSES IN ELEMENT COORD
PRINCIPAL STRESSES (ZERO SHEAR)
MAX
ID.
DISTANCE
NORMAL-X
NORMAL-Y
ANGLE
MAJOR
MINOR
SHEAR
0
3300 -5.000000E-02
2.400000E+04 2.400000E+04
90.0000
2.400000E+04
2.400000E+04 2.400000E+04
5.000000E-02
2.400000E+04 2.400000E+04
90.0000
2.400000E+04
2.400000E+04 2.400000E+04
SYSTEM
SHEAR-XY
0.0
0.0
STRESS(CENTER,MAXS)
S T R E S S E S I N Q U A D R I
L E M E N T S ( Q U A D R )
ELEMENT
FIBER
STRESSES IN ELEMENT COORD
PRINCIPAL STRESSES (ZERO SHEAR)
MAX
ID.
DISTANCE
NORMAL-X
NORMAL-Y
ANGLE
MAJOR
MINOR
SHEAR
0
3300 -5.000000E-02
2.400000E+04 2.400000E+04
90.0000
2.400000E+04
2.400000E+04 6.511982E-10
5.000000E-02
2.400000E+04 2.400000E+04
90.0000
2.400000E+04
2.400000E+04 6.511982E-10
1-18709438
L A T E R A L
SYSTEM
SHEAR-XY
0.0
0.0
Old Sensitivity - CBUSH, PBUSH - Incorrect sensitivities
When using the old sensitivity method, the sensitivity coefficients for the
CBUSH elements are incorrect.
Avoidance: Use the new sensitivity method. Note that beginning with version
2004, the old sensitivity method is no longer maintained or supported.
1-18710151
2005.0.2
ut when insufficient memory.
Data Recovery - MCFRACTION - Missing Outp
If insufficient memory is allocated, MCFRACTION output may be missing.

Avoidance: Allocate more memory.
1-18712781
2005.0.2
Distributed Memory Parallel - Frequency D
omain Lanczos may hang on 32 bit linux
Jobs running SOL 103 Distributed Memory Parallel (DMP) in the frequency domain
on 32-bit Linux systems may fail. The symptom of failure is that the parallel
processes hang indefinitely until killed manually. Frequency domain parallel
is invoked via the following DOMAINSOLVER command:
DOMAINSOLVER MODES (PARTOPT=FREQ)
No other MSC.Nastran platform exhibits this behavior.
Avoidance: Change the number of DMP processes assigned to the task. For
example, if the job fails (hangs) with "dmp=4" then resubmit the job with
"dmp=3" or "dmp=2".
1-18723414
2005.5
Documentation/QRG -MODALKE and MODALSE ca
se command descriptions for SORT1 & SORT2 are interchanged
The descriptions of the SORT1 and SORT2 output formats for the MODALKE and
MODALSE case control commands are interchanged. The MODLAKE SORT1 description
actually shows SORT2 output and the MODLASE SORT2 output actually shows SORT1
output.
1-18746291
Optimization - MODTRAK - Poor Message, UFM 6677
When using mode tracking in SOL 200, the modes that are being tracked are
specified on the DRESP1 entry. However, at least 2 modes need to be specified
on the MODTRAK entry even if you are only interested in one mode as the program
needs to have a mode to track against. This is implied in the QRG with LOWRNG
< HIGHRNG. However, if LOWRNG is set to HIGHRNG, then the job will fail with
the following unclear messages:
*** USER FATAL MESSAGE 6677 (MTFTRD)
MODES CANNOT BE TRACKED:
IN ORDER TO TRACK THESE MODES, IT MAY BE APPROPRIATE TO:
1. REDUCE MOVE LIMITS (DELP,DPMIN,DELX,DELXV,DXMIN), OR
2. DECREASE THE FILTERING PARAMETER, MTFILTER, OR
3. BOTH 1 AND 2
Avoidance: Specify at least 2 modes on the MODTRAK entry.
1-18756447
2005.5
Postprocessing - Undesired printed output
, PLOT command ignored for Failure Index and Strength Ratio
MSC.Nastran ignores the PLOT command for the OEFIT and OESRT datablocks. For
large models this results in a large amount of data being written to the f06
file.
1-18761971
2005.5
Documentation/QRG - PARAM,INREL,-2 - Buck
ling with PARAM,INREL,-2 may lead to fatal error
PARAM,INREL,-2 allows inertia relief without having to explicitly specify
SUPORT points. This method leads to indeterminate matrices which are not
supported by buckling.
If attempted the solution will fail in the READ
module.
Avoidance: Use param,inrel,-1 and specify 6 determinate degrees of freedom.
Note that if a rotation degree of freedom is specified, the rotational
stiffness should not be entirely from k6rot.
1-18769661
SEDRDR)
Optimization/Design Sensitivity - GDACMS, SCR=NO - UFM 1126 (
When a GDACMS optimization job is submitted with the scr=no option, it may fail
with the message
DMAP MODULE DISUTIL IS ATTEMPTING TO OUTPUT DATABLOCK
USER ACTION: DELETE THE DATABLOCK, OR USE FILE EPT=OVRWRT
201 NAME = EPT
Avoidance: Restarts are not supported in dmp, submit with scr=yes.

1-18775551
LCGEN
2005.5
Documentation - DMAP Programmer's Guide -
All reference to the IOPT parameter under the description of the LCGEN module
should be removed from DMAP documentation
1-18781681
2005.0.2
Optimization/Design Sensitivity - Job fai
led with PNAME/PBxSECT combo not supported

For PBMSECT/PBRSECT, thcikness(es) for the CP and OP forms can be selected as
design variable in SOL 200 job. Except the default thickness, all other
thickness must be given an ID number. SOL 200 jobs without ID'd thickness as
design variable failed with PNAME and PBxSECT combination not supported
message.
Avoidance: There is no workaround for this problem.
1-18784311
Elements - CCONEAX, PRESAX - Wrong Answers
When the CCONEAX element is loaded with PRESAX, the displacements for the
points attached to the end elements may be incorrect.
Avoidance: Use FORCEAX or use the QUAD4 element with cyclic symmetry.
1-18791521
2005.0.2
with FUNC=BETA - SFM 3002 (DSTAP2 if DSA print is turned on
When an design sensitivity job (DSAPRT(END=SENS) or PARAM,OPTEXIT,4) has a
DRESP2 response with FUNC=BETA/MATCH, it may fail in DSTAP2 with SFM 3002.
Avoidance: Use the combination of DRESP2 and DEQATN to perform Min/Max or
matching data tasks.
1-18805654
2005
Large Jobs - MEM greater than 2 gig leads
to Terminating, Received signal 11 SIGSEGV
MSC.Nastran 2005 may fail on Sunos and issue the message below if more than 2
gig of memory is requested.
*** TERMINATING /usr/local/msc/msc2005/solaris/analysis
Avoidance:
at:
Either request less than 2 gig of mem or obtain a corrected system
1-18809018
2005.5
Incorrect punch file
Optimization/Design Sensitivity - MCID -
In an optimization run, if the MCID is used in a plate element, the punch

output will contain an incorrect MCID.
Avoidance: Define the angle using the theta field instead of MCID.
1-18809851
2005.0.2
Postprocessing - RBE1, MAKEOLD, PARAM,POS
T - BE1 is not being converted by MAKEOLD module
The RBE1 element is not being converted by the MAKEOLD module under
PARAM,POST,-1 or -2. This may result in the RBE1 element not being properly
read in or ignored by post-processors.
Avoidance: Use RBE2 or RBE3 element.
1-18811286
2005.5
Documentation/QRG - UFM 718
Section 2.2 of the Quick Reference Guide describes how to continue FMS entries
that are greater than 72 characters. However, keywords can not be broken on
different lines. In the example below the keyword "unit" is broken between
lines this will lead to the fatal messge that follows. The documentation
should be updated to state, "keywords cannot be broken across lines"
ASSIGN INPUTT2='k:/strength/fem/rel_PC_superelement/unbal_nospc.op2',un,
it=39,status=old
*** USER FATAL MESSAGE 718 (RDASGN)
UNIT SPECIFICATION IS MISSING ON THIS ASSIGN CARD.
USER INFORMATION:
1-18811301
2005.0.2
PBEAML dimensions are incorrectly defined for the BOX.
Table 2-5 of the MSC.Nastran User's Guide for Design Sensitivity and
Optimization lists the constraints that are generated interrnally for different
beam section types in the beam library (PBARL and PBEAML). The constraints are
incorrect for the BOX section type. These should be:
2.0 * DIM4 - DIM1
2.0 * DIM3 - DIM2
The code has implemented the constraint specified in the table and, hence, is
incorrect as well. The results is that it is possible for the optimizer to
think the cross section dimensions are okay when in fact, they are producing
physically meaningless beam properties (e.g, negative cross sectional areas).
Avoidance: If possible, put limits on the design variables that preclude it
from achieveing designs where DIM1 < 2 * DIM4 or DIM2 < 2*DIM3. Alternatively,
DRESP2 entries can be used to supply the correct constraint conditions.
1-18815731
2005.0.2
ssing documentation
Documentation/QRG - CBUSH - grounded - mi
A remark should be added to the Quick Reference Guide description of the CBUSH
element that that is similar to remark 1 of the CELASi element that states that
that a grounded terminal will develop when GA or GB is missing.
1-18826341
2005.0.2
SOL 600 - PLOAD4 - Wrong Answers
This problem has been fixed in more recent versions. The user should update to
the 2005r3, MD R1 or MD R2 versions.
In MSC.Nastran 2005 SOL 600, "PLOAD4" entries are converted to "0" type loads
as defined on the Marc "DIST LOADS" entry regardless of which face is being
loaded.
Using the CTETRA element (element type 127 of MSC.Marc) as an example, the
MSC.Marc "DIST LOADS" entry has the definition for the 1st field of 3rd data
block:.
0--> Uniform pressure on face 1-2-3
1--> Nonuniform pressure on face 1-2-3
3--> Nonuniform pressure on face 1-2-4
.
1-18826551
2005.0.2
Optimization/Design Sensitivity - Formatt
ed Prints of Total Strain Energy Sensitivity - SFM 3007
If the DSAPRT case control request is used to ask for formatted design
sensitivty output and one of the responses is TOTSE (total strain energy),
system fatal message 3007 is encountered.
Avoidance: Unformatted design sensitivity output can be requested using OPTEXIT
= 4 or 7
1-18828854
2005.0.2
rs, US0 and VS0 values ignored
Transient Analysis - TLOAD1 - Wrong Answe
The new Version 2005 US0 and VS0 fields on the TLOADi entries for specifying
initial displacement and velocity are not recognized on the TLOAD1 entry and
thus give wrong answers. TLOAD2s do recognize these fields.
1-18829138
2005.0.2
Superelements - PARAM,AUTOQSET - SFM 3007
(EFFMAS) issued when AUTOQSET is used
Superelement models using PARAM, AUTOQSET, YES will fail with *** SYSTEM
FATAL MESSAGE 3007 (EFFMAS) / ILLEGAL INPUT TO SUBROUTINE MPYAD if the Case
Control includes a MEFFMASS request and PARAM, AUTOQSET, YES is included in the
model.
Avodiance: Revert to explicitly specifiying SPOINT/SEQSETi .
1-18831941
2005.0.2
- Response ID not found
Optimization/Design Sensitivity - DRSPAN
In SOL 200, DRSPAN can be utilized to select DRESP1s from multiple SUBCASEs for
referencing on DRESP2 or DRESP3. This is an advanced capability to generate
synthetic responses. However, SOL 200 job may fail with a message that
indicates response ID not found if the DRSPAN did not appear in the first few
SUBCASEs.
Avoidance : Move SUBCASEs without DRSPANs to the bottom of the case control
deck
1-18835942
2005.0.2
Documentation/QRG - PBUSH
Remarks 4 and 5 under the PBUSH description in the Quick Reference Guide should
be improved to read as follows:
4. The element stresses are computed by multiplying the stress coefficients
with the recovered element forces. Stress = F * SA, or M*ST.
5 The element strains are computed by multiplying the strain coefficients with
the recovered element displacements. Strain = El_disp*EA or El_rot*ET.
1-18843198
2005.5
Error 476 on linux64 Itanium
Miscellaneous - mem=4gb - Allocate Common
Specifying exactly mem=4gb produces the following error message on IA64 Itanium
systems:
Allocate Common Error 476: Inconsistent Common Size
The current size of dynamic common XNSTRN is 24 bytes
but its declared size in procedure getlini is 96 bytes
in log file.
Avoidance: Virtually any other memory request will work. For example 3gb,
5gb, 6gb will work, the request need only be at least 100mb greater or lesser
that 4gb. This error is fixed in 2005.5
1-18859441
2005.0.2
M,GRDPNT,0 - Wrong inertia values
Adams Modal Neutral File - ADAMSMNF, PARA
The nastran to adams flex interface, ADAMSMNF command, with param,grdpnt,0

and coordiantes will cause wrong inertia values
compile admflex $
alter 'TYPE PARM,,LOGI'
TYPE PARM,,RS,N, W $
TYPE PARM,,CS,N, CW $
alter 'GPWG BGPDTS,CSTMS',''
IF ( GRDPNT>=0 ) THEN $
$
REMOVE WTMASS:
W = 1./WTMASS $
CW = CMPLX(W) $
ADD MGG,/MGGBW/CW $
CHECK MASS IN BASIC COORDINATES, WITH WTMASS REMOVED:
IF ( ADMCHECK<>0 ) THEN $
MESSAGE //' MJJEW CHECKOUT:' $
MATGPR GPLS,USET,SILS,MGGBW//'G'/'G' $
ENDIF $
GPWG BGPDTS,CSTMS,,MGGBW,,/OGPWGW/
0/1.0//SEID $ CALL HARDWIRED TO ORIGIN OF BASIC SYSTEM WITH WTMASS=1.0
ENDIF $ GRDPNT>=0
$
1-18874231
2005.1
MDACMS - EIGRL - UFM 3034, 7340, 9160
The following error messages may be avoided in MDACMS by increasing MAXSET on

the EIGRL entry.
SYSTEM FATAL MESSAGE 3034 (LNNHERR)
MASS MATRIX IS INDEFINITE (MODES) OR STIFFNESS MATRIX IS INDEFINITE (BUCKLING).
WARNING REPORTED BY SUBROUTINE LNNDRVD (IER= 728)
USER INFORMATION: GRAM-SCHMIDT DID NOT CONVERGE.
SYSTEM FATAL MESSAGE 9160 (MDACMS)
PROBLEM ENCOUNTERED IN CALCULATING MDACMS DOMAIN MODES.
USER ACTION:
IF LARGE MASS IS BEING USED FOR ENFORCED MOTION THEN REPLACE
LARGE MASS METHOD WITH DIRECT METHOD USING THE SPCD BULK DATA ENTRY. IF THE
LARGE MASS METHOD IS NOT BEING USED THEN MASSLESS MECHANISMS MAY EXIST.
PARAM,MECHFIX,YES MAY BE USED TO IDENTIFY MASSLESS MECHANISMS.
MDACMS has been modified to handle this case. Default MAXSET is 15 now for all
components at all levels.
1-18890681
wers (STRESS)
2005.5
Elements - CQUADR and TEMPP1 - Wrong Ans
A simple plate, modeled with with CQUADR elements, that is subjected to a

linearly varying temperature gradient through the thickness using TBAR and
TPRIME on the TEMPP1 entry, will not result in the correct zero stress field.
Avoidance: Use the CQUAD4 element.
1-18892014
2005.0.2
Aeroelastic Analysis - AEPARM -
In the Quick Reference Guide, Remark 2 for the AEPARM entry states the UNITS
label is optional. However, IFS13P produces a fatal error unless character
data is entered.
Avoidance: Place data in the UNITS field. This is used for labelling and does
not effect numerical results.
1-18893229
2009.0.0 (MD R4)
oduces poor results.
Documentation/QRG - ACMODL - CP Method pr
A new remark will be added to the ACMODAL QRG description that indicates CP
is not recommended for complex acoustic cavities such as body in white models.
CP - is an old algorithm that for complex structures such as body in white
tends to be slow, miss fluid-structure interface and as a result gets poor
solutions(which are indicated in the FL./STR. INTERFACE CHECK). This method has
been replaced with the BW method and the CP method is no longer supported for
error fixes or enhancements.
1-18895621
2005.1
r does not work
Element Strain Energy - ESE, TINY - Filte
PARAM,TINY is being ignored after the first subcase and the summaries are not
prined. Negative strain energies due to roundoff cause the associated elements
to produce a large percent of the "negative energy".
1-18905291
2005.0.2
Superlements - EXTSEOUT - Bad DMIG matrix
leads to UFM 316 in a subsequent assembly run
An external superlement (EXTSEOUT) run may produce a bad K4AAX DMIG matrix,
leading to failure with USER FATAL MESSAGE 316 in a subsequent assembly run.
1-18907271
2005.0.2
ACMS - SOL 103 with Matrix Domain ACMS ma
y fail (System Fatal Message 4276, QOPEN)
SOL 103 with Matrix Domain ACMS may fail with SYSTEM FATAL MESSAGE 4276 (QOPEN)
if no loads are pressent.
Avoidance: Include the following DMAP alter:
compile modefsrs
alter 'if (novasprc = -1)', '' $
paraml pg//'null'////s,n,nullpg $
if (novasprc = -1 and nullpg > -1) then $
endalter
1-18908795
2005.0.2
Superelements - EXTSEOUT - Extra Output
An EXTSEOUT SE creation run outputs the K4 damping matrix even though only the
stiffness and mass matricies were explicitly requested to be output. Similar

problems occur if the user requests only stiffness or mass matrix to be output
(NOTE BY P. R. PAMIDI: Please also see related QD 1-18562191)
compile phase1dr
alter 'extfs' $
type parm,,logical,n,extstif $
alter 'extmass'(2,-1) $
extstif =(MOD(extseout
,2)>0) $
alter 'extmass'(3,-1) $
extstif=true $
alter 'call extout','' $
if (extstif) then $
equivx kaa/kaax/-1 $
else $
delete /kaax,,,, $
endif $
if (extmass) then $
equivx maa/maax/-1 $
else $
delete /maax,,,, $
endif $
if (extdamp) then $
equivx baa/baax/-1 $
else $
delete /baax,,,, $
endif $
if (extk4) then $
equivx k4aa/k4aax/-1 $
else $
delete /k4aax,,,, $
endif $
if (extloads) then $
equivx pa/pax/-1 $
else $
delete /pax,,,, $
endif $
call extout kaax,maax,baax,k4aax,pax,gpak,gdak,
eqexins,uset,bgpdts,cases,got,goq,gm,msf,
bsf,ksf,k4sf,cmlama,ects,sils,uoo,cstms,
mpts,dit,ett,est,ibulk,vgfs,aaa/
dum/lusets $
1-18917928
n BIOWRT
2005.1
Restart - read only restart - UFM 1245 i
A read-only restart may fail in subDMAP resload with the following error:
*** USER FATAL MESSAGE 1245 (BIOWRT)
AN ALLOCATION ERROR HAS OCCURRED FOR A DATABASE FILE, FILX =
WRITE ATTEMPTED ON FILX WHICH WAS OPENED FOR READONLY.
compile resload
alter 'modtrl.*lamax'(2),''
if ( np>0 and nmodes1>-1 ) modtrl
lamax//nmodes1/////np $
10.
endalter
1-18922365
n op2 file
2005.1
SOL 400 - PARAM,POST - Missing results i
In SOL 400, results from the last subcase only are available in the op2.
1-18926554
2005.0.2
Loads - GRAV, TEMP(INIT) - Wrong Answers
In MSC.Nastran Version 2004, if a TEMP(INIT) references a temperature load with

the same ID as a GRAV load the GRAV load will be doubled.
Avoidance: Remove TEMP(INIT) or use a unique load id for TEMP(INIT).
1-18933661
hod
2005.0.2
SOL 600 - Missing output for adaptive met
Through both the MSC.Patran and MSC.Nastran SOL 600 interface, when the user
asks for output for "each increment" of results, SOL600 will only produce the
1st and final increment of results.
1-18935320
Documentation/QRG - GPRSORT - Missing Documentation
GPRSORT Case Control command is undocumented

Avoidance: See Nastran V2005 Release notes for an example. For the QRG
additional examples of non-default values need to be added.
1-18936651
1
Dynamic Analysis - PARAM,INREL, STATSUB - UFM 1126 or SFM 300
If PARAM,INREL is specified with STATSUB in SOLs 108 or 109 then the run will
fail with:
DMAP MODULE PHASE1C IS ATTEMPTING TO OUTPUT DATABLOCK
205 NAME = MR
Or:
*** SYSTEM FATAL MESSAGE 3001 (MPYAD)
1 DOES NOT EXIST.
Avoidance: Insert the following DMAP alter for SOL 109 in V2007:
compile sedtran
alter 'call super1',''
type db mr,mrr,mlr,qr,mll $
CALL SUPER1 /CASECC ,USET
DYNAMIC ,GPLS
CASES ,EQEXINS
BGPDTS ,CSTMS
LLL
,KLL
EMAP
,XYCDB
KFS
,KSS
GEOM2S ,GEOM3S
INDTA ,KELM
FORCE ,CASERS
SPSEL ,
PA
,YS
,GOT
,SILS
,MATPOOL
,EST
,ULL
,MAPS
,KSF
,POSTCDB
,KDICT
,SCSTM
,PJ
,qr
,KAA
,DYNAMICS,
,SLT
,DAR
,
,GM
,DITS
,
,MPTS
,XYCDBS ,
,
,PCDB
,
,ETT
,PVTS
,
,EDT
,EDOM
,
,ECTS
,EPTS
,
,GPECT ,VELEM ,
,MATPOOLS,DITID ,
,PTELEM ,PG
,
,UOO
,PSS
,
PL
KGG
K4GG
MRR
MR
MAR
,
,GPSNTS ,
,KJJ
,
,EDTS
,LOO
,BJJ
,BGG
,
,MJJ
,
,MLR
,MLL
,
,CMLAMA ,CMPHA ,CMPHO ,
,
,GOQ
,
,
,MAA
,
,MEA
,BAA
,K4AA
,MGG
,
,
,
,
,GEOM4S ,
VGFS
,PCDBS ,ESTL
,ESTNL ,AGG
,
DMIS
,DMINDXS ,DTIS
,DTINDXS ,CONTACT ,
BTOPO ,GPDTS ,MELM
,MDICT ,GEOM1 ,
GEOM2 ,GEOM3 ,GEOM4 ,EPT
,MPT
,
SLIST ,KMG
,MMG
,MSF
,BMG
,
BSF
,K4MG
,K4SF
,
,PVT
,
OINT
,DEQATN ,DEQIND ,MEDGE ,GDNTAB ,
PELSETS ,VIEWTB ,BGPDTVU ,ORSEQ ,
,
VGFD
,EHT
,GEOM1S ,PVTBC ,
,
,
,
,
,VGQ
,
,
,
,MMCDB ,
,
,
,
,
,AXIC
,
,
,
,
,
,
EPSSEO ,DRG
,MPHVZ ,BK4ZZ ,PCOMPTS ,
PVAL
,ELEMVOL ,PMYG
,PBYG
,PKYG
,
MSS
,BSS
,K4SS
,BELM
,BDICT ,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,XSOP2DIR,RVG
,
GEOM1QX ,CEE
,MEE
,GGE
,BEC
,
MEC
,CMLAMA1 ,AJP
,GEI
,PVT0
,
KAY
,BAY
,MAY
,K4AY
,GOY
,
YG
,PHBA
,AAA
,AAY
,ASF
,
PGGRV ,
,
,
,
,
,YM
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
K4JJ
,
,ACTNODS ,MDOTMO ,
,
THETAM ,PHBG
/
S,APP /DMAPNO /S,RSONLY/SOLTYP /FALSE /
FALSE /FALSE /FALSE /APRCH /S,SEID /
S,PEID /S,MTEMP /S,LOAD /S,TEMPLD/S,DEFORM/
S,MPC /S,SPC /S,SUPORT/S,K2GG /S,M2GG /
S,B2GG /S,P2G /S,DYRD /S,METH /S,MFLUID/
S,NLOOP /S,LASTSEID/S,PFILE/S,LUSETS/S,FSCOUP/
ENFMETH /AUTOSPC /S,NOPH2 /FALSE /S,PVALID/
S,PEXIST/FALSE /S,KDIFF /'
' /0
/
0
/0
/0.0
/S,NOPH1 /S,ADPTINDX /
FALSE /'NO ' /'NO ' $
For V2008, insert the following DMAP alter
compile sedtran
type db mr,mrr,mlr,qr,mll $
DYNAMIC ,GPLS
CASES ,EQEXINS
BGPDTS ,CSTMS
lll
,kll
EMAP
,XYCDB
,GOT
,SILS
,MATPOOL
,EST
,ull
,MAPS
,KAA
,SLT
,GM
,MPTS
,
,ETT
,DYNAMICS,
,dar
,
,DITs
,
,XYCDBS ,
,PCDB
,
,PVTS
,
KFS
GEOM2S
INDTA
FORCE
SPSEL
PA
PL
KGG
K4GG
MRR
MR
MAR
,KSS
,KSF
,EDT
,EDOM
,
,GEOM3S ,POSTCDB ,ECTS
,EPTS
,
,KELM
,KDICT ,GPECT ,VELEM ,
,casers ,SCSTM ,matpools,ditid ,
,
,PJ
,PTELEM ,PG
,
,YS
,qr
,UOO
,PSS
,
,
,gpsnts ,
,KJJ
,
,edts
,LOO
,BJJ
,BGG
,
,MJJ
,
,MLR
,MLL
,
,
,GOQ
,
,
,MAA
,
,MEA
,BAA
,K4AA
,MGG
,
,
,
,
,GEOM4S ,
VGFS
,PCDBS ,ESTL
,ESTNL ,AGG
,
DMIs
,DMINDXs ,DTIs
,DTINDXs ,CONTACT ,
btopo ,GPDTS ,MELM
,MDICT ,GEOM1 ,
,MPT
,
SLIST ,KMG
,MMG
,MSF
,BMG
,
BSF
,K4MG
,K4SF
,
,pvt
,
oint
,deqatn ,deqind ,medge ,gdntab ,
pelsets ,viewtb ,bgpdtvu ,orseq ,
,
vgfd
,eht
,geom1s ,pvtbc ,
,
,
,
,
,vgq
,
,
,
,mmcdb ,
,
,
,
,
,axic
,
,
,
,
,
,
epsseo ,drg
,mphvz ,bk4zz ,pcompts ,
pval
,elemvol ,pmyg
,pbyg
,pkyg
,
mss
,bss
,k4ss
,belm
,bdict ,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,xsop2dir,rvg
,
geom1qx ,cee
,mee
,gge
,bec
,
mec
,cmlama1 ,ajp
,gei
,pvt0
,
kay
,bay
,may
,k4ay
,goy
,
yg
,phba
,aaa
,aay
,asf
,
pggrv ,
,
,
,
,
,ym
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
K4JJ
,
,actnods ,mdotmo ,
,
thetam ,phbg
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
/
s,APP /DMAPNO /S,RSONLY/SOLTYP /FALSE /
s,nloop /S,LASTSEID/S,PFILE/S,LUSETS/S,FSCOUP/
enfmeth /AUTOSPC /S,NOPH2 /FALSE /s,pvalid/
s,pexist/false /s,kdiff /'
' /0
/
0
/0
/0.0
/s,noph1 /s,adptindx /
false /'no ' /'no ' $
1-18959967
6
2005.5
Documentation/QRG - TEMPERATURE - Remark
In the Quick Reference Guide, last bullet item of remark 6 under the
TEMPERATURE Case Control Command should be modified from
o
If neither TEMPERATURE(INITIAL) nor TEMPERATURE(MATERIAL) is present, Tref
will be used to calculate both the load and the material properties.
to
o
If neither TEMPERATURE(INITIAL), TEMPERATURE(MATERIAL), nor
TEMPERATURE(BOTH) is present, Tref will be used to calculate the load and the
material properties will be obtained from the MATi entry. The MATTi is not
used in this case.
1-18973169
orner Stresses
2005
Elements - SNORM, CQUAD4 - Inconsistent C
The default value of SNORM was changed to 20.0 in Version 2001. Setting SNORM
to 0.0 in Version 2001.0.7 (2001r3) through Version 2004.5 (2004r3) could lead
to incorrect QUAD4 corner stresses.
Avoidance: Leave SNORM to the default value, do not set to 0.0.
1-18976345
2005.0.2
impropely translated in SOL 600
SOL 600 - PARAM,TSTATIC, NLAUTO - NLAUTO
In SOL 600,129 NLAUTO should not be used for SOL 600 dynamics problems except
in the special case where there are no dynamic loads (initial conditions only).
In that case it is acceptable (but not recommended) to use NLAUTO.
Furthermore, in SOL 600,129 it is not possible to handle TSTATIC, so it is
skipped after issuing the approporate warning.
1-18988374
2005.0.2
AR LOAD not supported
SOL 600 - Severe translator error NONLINE
If the 1st word AFTER a "$" comment demarkation in the Case Control is the word
"Nonlinear" as in:
SUBCASE 100 $ Nonlinear Subcase
Then SOL 600 in v2005 will have a SEVERE translator error and complain that you
have a NONLINEAR Load Case Control request when in fact there isn't one.
Avoidance: Have ANYTHING else as the 1st word - or add a "-" or other
charachter in front.
1-18989384
2005.0.2
GPFORCE - Duplicate entries for Grid Poin
t Forces for K2GG matrix contribution.
Under multiple load cases, the contribution from K2GG referenced matrices is
accounted for at least twice in the Grid Point Force Output thus creating
incorrect totals. The information written to output files or databases will
also be incorrect. An avoidance in DMAP is to purge the contribution from the
K2GG matrices for the grid point force calculations.
1-18998425
2005.1
AD), RIGID = LAGRAN
Rigid Elements - RBE, TEMP(INIT), TEMP(LO
Models with temperature loads on rigid elements, rbes, with thermal coefficient
of expansion defined, may fail in the routine getemp on Solaris and possibly
other machines.
1-19000411
2005.0.2
SOL 600 - Gravity Loads, Cylindrical or S
pherical Coordinate System leads to Wrong Answers.
SOL 600 does not support material coordinate systems specified in cylindrical
or spherical systems. A fatal message should be issued but instead the job
continues and gives unexpected results.
Furthermore gravity loads may be
translated incorrectly and lead to wrong answers.
1-19005078
Distributed Memory Parallel - GDACMS, DOMAINSOLVER ACMS(PART=
GRID) - Incorrect MPCFORCEs
Incorrect mpc force results, requested by MPCFORCE=n where SET n is not ALL,
may be generated with GDACMS, which is requested with DOMAINSOLVER
ACMS(PART=GRID).
Avoidance: Request MPCFORCES=ALL or insert the following DMAP alter:
compile spdr0
alter ' outprt '
type db msf,bsf,ksf,k4sf,mmg,bmg,kmg,k4mg $
call spdr2 cases,xycdbs,uset,mmcdb,,adrdug,gm,,
msf,bsf,ksf,k4sf,ksf,mmg,bmg,kmg,k4mg,,
vmpcg,vspcg/
vmcg,vscg/
'freqresp'/false/false/'
' $
equivx vmcg/vmpcg/-1 $
matgpr bgpdts,uset,,vmpcg//'h'/'g' $
alter 'if ( noup=-1 and ',''
if ( noup=-1 and nov01s>0 and sdrs=-1 ) then $
endalter
1-19006294
2005.5
EXTSEOUT, MAXMIN - SFM 5423
Modal Transient/External Superelements -
The following conditons will lead to SYSTEM FATAL MESSAGE 5423 (DMPYAD),
ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES:
1. Modal transient response (SOL 112)
2. External superelement when external superelements are attached using the
EXTSEOUT case control command.
3. MAXMIN data recovery is requested
4. DISP=n where SET n is only some of the GRID points.
5. Sparse data recovery is active (default) - PARAM,SPARSEDR,NO will deactivate
Avoidance: Specify PARAM,SPARSEDR,NO
Avoidance:
Insert the following alter
ECHOOFF $
COMPILE SEDRCVR NOLIST $
$
ALTER 'SDR3
OUG1'(,-1),'' $
IF ( NOT(SORT2MM) OR EXTERSE ) THEN $
$
ALTER 'SDR3
OUG2','' $
DBSTATUS OUG1,OVG1,OAG1,OPG1,OQG1,OQMG1//
S,N,NOOUG1/S,N,NOOVG1/S,N,NOOAG1/
S,N,NOOPG1/S,N,NOOQG1/S,N,NOOQMG1 $
IF ( NOOUG1<0 ) SDR3
OUG2,,,,,/OUG1,,,,, $
IF ( NOOVG1<0 ) SDR3
OVG2,,,,,/OVG1,,,,, $
IF ( NOOAG1<0 ) SDR3
OAG2,,,,,/OAG1,,,,, $
IF ( NOOPG1<0 ) SDR3
OPG2,,,,,/OPG1,,,,, $
IF ( NOOQG1<0 ) SDR3
OQG2,,,,,/OQG1,,,,, $
IF ( NOOQMG1<0 ) SDR3
OQMG2,,,,,/OQMG1,,,,, $
$
ALTER 'SDR3
OUG2'(2,0),'' $
DBSTATUS OUG1,OVG1,OAG1,OPG1,OQG1,OQMG1//
S,N,NOOUG1/S,N,NOOVG1/S,N,NOOAG1/
S,N,NOOPG1/S,N,NOOQG1/S,N,NOOQMG1 $
IF ( NOOUG1<0 ) SDR3
OUG2,,,,,/OUG1,,,,, $
IF ( NOOVG1<0 ) SDR3
OVG2,,,,,/OVG1,,,,, $
IF ( NOOAG1<0 ) SDR3
OAG2,,,,,/OAG1,,,,, $
IF ( NOOPG1<0 ) SDR3
OPG2,,,,,/OPG1,,,,, $
IF ( NOOQG1<0 ) SDR3
OQG2,,,,,/OQG1,,,,, $
IF ( NOOQMG1<0 ) SDR3
OQMG2,,,,,/OQMG1,,,,, $
$
ALTER 'IF ( NOOEF'(1,0),'IF ( NOOSTR'(1,0) $
IF ( NOOEF<0 ) SDR3
OEF2,,,,,/OEF1X,,,,, $
IF ( NOOEF<0 ) SDR3
OES2,,,,,/OES1X1,,,,, $
IF ( NOOSTR<0 ) SDR3
OSTR2,,,,,/OSTR1X,,,,, $
ALTER 'IF ( NOOEF'(3,0),'IF ( NOOSTR'(2,0) $
IF ( NOOEF<0 ) SDR3
OEF2,,,,,/OEF1X,,,,, $
IF ( NOOEF<0 ) SDR3
OES2,,,,,/OES1X1,,,,, $
IF ( NOOSTR<0 ) SDR3
OSTR2,,,,,/OSTR1X,,,,, $
$
ENDALTER $
$
ALTER 'MPYAD
ULS'(,-1) $
TRNSP UH2/UH2T$
EQUIVX UH2T/UH2/-1 $
ENDIF $
$
ENDALTER $
ECHOON $
1-19006951
2005.5
utput for ESE referencing SET
Nonlinear Analysis - ESE, SET - Missing O
Nonlinear analysis, SOL 106, may ignore an ESE request that references a SET.
Avoidance:
Request ESE=ALL
1-19007725
2005.5
Superelements - BNDFIXi, BSETi entries o
r BNDFREEi/CSETi should be allowed in the same run
The current restriction of not allowing usage of BNDFIX entries in conjunction
with BSET entries or BNDFIX1 entries in conjunction with BSET1 entries or

BNDFREE entries in conjunction with CSET entries or BNDFREE1 entries in
conjunction with CSET1 entries must be removed.
This enhancement has been implemented in V2006. In order to illustrate the
enhancement, Nastran test problem s5169004 has been modified to demonstrate
usage of the following types of mixed Bulk Data entries:
BSET and BNDFIX
BSET1 and BNDFIX1
CSET and BNDFREE
CSET1 and BNDFREE1
1-19044574
2005.0.2
EL, echo=punch(newbulk) - UFM 1126
Optimization/Design Sensitivity - AUXMOD
The echo=punch(newbulk) feature is intended to produce a new bulk data deck

with updated bulk entries following a SOL 200 design optimizaton task.
If there are multiple begin bulk statements in the input deck, USER FATAL
MESSAGE 1126 is issued.
Avoidance: Apply the following dmap alter. This will provide an updated main
bulk data section with the new designed quantities in the .pch file. It will
not punch out the unchanged bulk data associated with the auxiliary models.
compile ifpl
alter 'ubulk'(2),'ubulk'(3,1)
XSORT
FORCE,
/IBULK,ubtmp/
S,N,NOGOXSRT/S,N,QUALNAM/S,N,NEXTID/
S,N,LASTBULK/s,n,eqvblk $
else $
XSORT
FORCE,bulk/IBULK,ubtmp/
S,N,NOGOXSRT/S,N,QUALNAM/S,N,NEXTID/
S,N,LASTBULK/s,n,eqvblk $
endif $ noxsort
paraml ubulk//'pres'////s,n,noubulk $
if ( noubulk=-1 ) equivx ubtmp/ubulk/always $
1-19047395
2007.0.0
- Wrong stresses
Optimization/Design Sensitvity - AUXMODEL
When an Analytic Boundary Shape optimization job also includes SPCD entries in
its primary Bulk Data section, it may produce wrong element responses such as
stress for the final analysis at the last design cycle.
compile desopt
alter 'call fea'(2,-1)
if ( ambs or gmbs ) bndshp=true $
alter 'call fea'(4,-1)
if ( ambs or gmbs ) bndshp=true $:
1-19053169
2005.1
t exception caused by large alpha
Rigid Elements - RBE3 - FPU floating poin
Extremely large values for the alpha field on RBE3 entries may cause some
system to issue a floating point exception while other machines correctly trap
the input and issue a meaningful message that indicates the value is out of
range.
MAIN: For reference, A(MAINAL) = 4012FE, A(/SYSTEM/) = 1FD0A00
MAIN:
A(/XNSTRN/) = 3950020
MAIN: "Floating point overflow" (C0000091) exception encountered.
MAIN: Exception occurred at address 0043ECDE.
1-19073811
2005.0.2
- SFM 6036 (XQAERR)
Nonlinear Analysis - PARAM,FKSYMFAC, NLKR
Nonlinear analysis may fail with a divide by zero in the nlkr subdmap. This
problem is caused by the change in the default value of the parameter FKSYMFAC
from 1.0 in V2001 to 0.024 in V2004+. The message issued is:
*** SYSTEM FATAL MESSAGE 6036 (XQAERR)
ATTEMPT TO DIVIDE BY REAL, DOUBLE PRECISION ZERO
USER INFORMATION:
1. PROCESSING ASSIGNMENT STATEMENT: RATUNSYM AT DMAP SEQUENCE NUMBER:
51
lproctor: based on a 'diff' between the broken/fixed, the following dmap
avoidance should work
compile nlkr,nolist
alter 'norm.*kggnl1',''
norm
kggnl1/////1/s,n,xnorm1 $ norm1 of stiffness
norm
kfggu/////1/s,n,xnorm2 $ norm2 of stiffness
alter 'ratunsym.*sngl',''
ratunsym = sngl(xanorm/(xnorm1+xnorm2)) $
endalter
1-19077491
2005.0.2
- Missing Output, Missing UFM
When the DSAPRT Case Control command is not placed with or above the first
SUBCASE command, the requested Design Sensitivity output will not be written to
the f06 file. This condition should be treated as a user input error and the
job should fail.
1-19082580
2005.0.2
h PARAM,FLUIDSE - UFM 9139
Acoustic Analysis - MDACMS and/or DMP wit
In MDACMS and/or DMP dynamic runs, if the first subcase is assigned to the
fluid superelement (METHOD(FLUID)), then UFM 9139 may be issued incorrectly.
For example,
subcase 1
super = 1
METHOD(FLUID)
subcase 2
METHOD(STRUCTURE)
DLOAD
FREQUENCY
= 120
= 110
= 10
= 2
Avoidance: Move the METHOD(STRUCTURE) command above the subcases or Reverse the
order of the subcases above.
1-19082619
Acoustic Analysis - PARAM,FLUIDSE or ACMS - SFM 6143
If the fluid superelement method is used and there are physical fluid points on
the boundary of the fluid superelement, then UFM 6143 may occur.
This error can also occur in GDACMS.
Avoidance: Specify CSUPEXT entries for the physical fluid points on the
boundary of the fluid superelement.
The following DMAP alter will help to identify these points.
compile phase0
alter 'if ( acms and fluidse',''
if ( fluidse>0 ) then $
alter '
SELA
,,SLIST'(,-1),''(,0)
SELA
,,SLIST,EMAP,BGPDTS,PAUP,MAPUP,GDNTAB/
vgfs1/
SEID/'SEID'/0/1/false $
if ( acms ) then $
equivx vgfs1/vgfs/-1 $
else ( nogsetf>ncag0 ) then $
paraml ag0//'trai'/1/s,n,ncag0 $
add
vgfs,vgfs1/vgdiff//-1. $
message //' '
MESSAGE //' USER'/FTL/'MESSAGE 91xx (PHASE0)' $
message //
' The following fluid point(s) is not exterior to'/
' the fluid superelement' $
message //' user action: specify the point(s) on'/
' csupext entry(ies).' $
matgen ,/v6/6/6/0/1 $ 1 0 0 0 0 0
matmod v6,,,,,/v6d,/28 $
matmod v6d,sils,,,,/v6g,/5 $
$ t1 t2 t3 r1 r2 r3
diagonal v6g/v6gd $ 1 0 0 0 0 0 at each grid points
$ 1
at each scalar and fluid grid
paraml v6gd//'trai'/5/s,n,nrow $
paraml v6gd//'trai'/4/s,n,prec $
nrow=nrow/prec $
matgen ,/ig/4/nrow/1 $ 1 2 3 4 ... no. of points
merge
,,,ig,,v6gd,/igg/1 $ matrix of internal grid id
$ numbers at t1 location
partn
igg,vgdiff,/,,iog,/1 $ Selected grids
paraml iog//'trai'/1/s,n,ncol $
type parm,,i,n,ii=1,indx $
Do while ( ii<=ncol ) $
paraml iog//'dmi'/ii/1/s,n,rintgid $
indx=int(rintgid)*2 $
paraml eqexins//'dti'/2/indx//s,n,silpos $
indx=indx-1 $
paraml eqexins//'dti'/2/indx//s,n,gridid $
message //'
fluid grid id='/gridid $
ii=ii+1 $
enddo $ ii<=ncol
message //' '
call errph0 //s,np $
endif $
1-19083581
mand - SMEM
2005.5
Documentation/QRG - nastran submittal com
The Quick Reference Guide documentation of the smem parameter on the nastran
command fails to indicate that the amount of scratch memory may also be
specified in terms of words or bytes if followed by a unit modifier. Valid
unit modifiers are B, W, KB, KW, K, MB, MW, M, GB, GW, G.

1-19094121
2005.0.2
Restarts - UWM 9026, DBTRANS, no case con
trol was found, incorrect message, SFM 9061 on restart
In V2004.5 or 2005, if you try to dbunload or dbload using SOL DBTRANS, the
following message may be issued erroneously:
^^^ USER WARNING MESSAGE 9026 (DBTRANS)
^^^ NO CASE CONTROL WAS FOUND AND THE QUALIFIERS CANNOT BE SET PROPERLY.
THIS PROJECT AND VERSION WILL BE SKIPPED.
and the dbunloaded file is not complete. Restart from the dbloaded database
generates SFM 9061
Avoidance:
Insert the following DMAP alter in all SOL DBTRANS runs:
ECHOOFF $
COMPILE DBTRANS NOLIST $
ALTER 'IF ( ITOL(NOHEAT) ) THEN','' $
IF ( ITOL(NOHEAT) AND ITOL(NOCASE) ) THEN $
ENDALTER $
ECHOON $
1-19100640
Postprocessing - PARAM,POST,0 - Composite failure indices are
not available in the xdb file
Composite failure indices are missing from the xdb file.
strains are available.
Ply stresses and
Avoidance: The op2 file (param,post,-1) may be used instead. However, this
limits the model size since Patran reads all of the op2 into memory and the
current limitation is around 2 gb. Whereas only what is needed is read from
the xdb.
see also CR 1-3075406
1-19104750
2005.1
Composites - STRAIN(BILIN), PCOMP - UFM 3
005 (SDR2), Attemp to Operate on Singular Matrix
A model with composites that requests strain(bilin) or strain(corner) but does
not request stress will fail with the message:
ATTEMPT TO OPERATE ON THE SINGULAR MATRX NONE IS SUBROUTINE SQD43D
1-19117011
2005.0.2
f dependent DOF
MDACMS - MPC - Wrong Answers for output o
MDACMS may produce wrong answers when output is requested at dependent degrees
of freedom. This occurs when equal and opposite MPC coefficients are present
in the same MPC equation. The answers at these DOF will be zero.
Avoidance: Specify PARAM,SPARSEPH,NO.
1-19124784
2005.5
entation on new V2005 capability
Documentation/QRG - CWELD - Missing docum
Beginning in V2005, CWELD is able to connect elements that share a common node.
1-19126081
ncomplete.
2005.0.2
SOL 700 - SPCD, TLOAD1 translation is i
SOL 700 will not translate multiple SPCD and TLOAD1 entries.
1-19126815
Optimization/Design Sensitivity - DRESP2/DCONSTR - Poor Messa
ge, sfm 3007 (dom10)
When a DRESP2 entry is referenced by more than one DCONSTR entry (which is not
allowed) the following message is issued:
ILLEGAL INPUT TO SUBROUTINE DOM10G
This message should be improved to be like the message below issued when this
user error is encountered with the DRESP1 entry.
*** USER FATAL MESSAGE 7143 (DOPR3H)
DRESP1 ENTRY ID = # IS REFERENCED BY MORE THAN ONE DCONSTR ENTRY IN
SUBCASE = #.
1-19136143
Nonlinear Analysis - CBEAM, PARAM,LGDISP - Zero Shear Factors
K1, K2, wrong answers
In nonlinear analysis with large displacement, a CBEAM element with zero shear
factors will produce incorrect axial displacements under shear load.
Avoidance: Specify non-zero shear factors.
********************************************************************************
********************************************************************
Comment(NJ Teng):
For linear beam elements, K1=K2=0.0 leads to Euler-Bernoulli beam, degenerated
from Timoshenko beam theory. We get the same displacements if we have K1=K2=1.0
and a big shear modular G, such as 1.0E+15, in MAT1 card. In both cases, the
beam cross-sectional shears reduce to zero.
For nonlinear beam elements(with large displacement), it seems that only
Timoshenko beam theory works. K1=K2=0.0 does not represent the Euler-Bernoulli
beam.
As of 03/18/08:
Is this a limitation or an error? Need to review the original documents, such
as SRS, to see if the formulations of the nonlinear CBEAM include the
Euler-Bernoulli beam.
********************************************************************************
********************************************************************
1-19136734
Superelements - PARAM,EXTDR - SFM 3002 (GKAM)
The use of PARAM,EXTDR,YES may cause the following fatal message:

EOF ENCOUNTERED WHILE READING DATA BLOCK LAMAS
SUBROUTINE SKPREC
(FILE 104) IN
Avoidance: Insert PARAM,SPARSEDR,NO in the assembly run (which should also

contain PARAM,EXTDROUT).
1) insert PARAM,EXTDR,YES in the bulk data section

2) insert the following dmap in the assembly run (V2005.0.0 line numbers)
compile super3,nolist
alter 323 $
IF ( SOLTYP='MODAL' AND EXTDROUT<>'
' ) THEN $
dbview lama00=lama where (seid=0 and wildcard)
equivx lama00/ol1m/always $
$ matprn ol1m//$
ENDIF $
alter 674,674
IF ( SOLTYP='MODAL' AND SPDR and EXTDROUT<>'
' ) THEN $
1-19151111
ported'
2005.0.2
SOL 600 - job fails with 'statsub not sup
In SOL 600, when a data deck is translated from sol 400 and contains
analysis = nlstatics
SOL 600 will terminate and the following message is issued:
** severe warning in sol 600 translator - STATSUB not supported for sol 600
please revise your input so it does not need STATSUB
This message is misleading since there is no STATSUB command present in the
input deck.
1-19151215
ted directory
2005.0.2
SOL 600 - Script to run Marc not in expec
When the string consisting of the default path for the Marc tools directory
plus run_marc is more than 80 characters long sol 600 will terminate and the
following message will be issued in f06:
directory
Since some clients use rather long home directories for their Nastran
installation this 80 character limit should be removed.
Avoidance: Define the path in the marcrun.pth file.
1-19153862
2005.0.2
g's modulus specified
SOL 600 - MAT1 - termination when no youn
On the nastran MAT1 entry, it is possible to specify only two of the three
material properties: young's modulus, shear modulus and poisson's ratio.
However when doing this in sol 600 no warning will be issued and the job will
fail in Marc with exit 13. In order to be compatible with the other Nastran
solutions, the sol 600 translator should calculate the third value and provide
it to marc.
Avoidance: Specify all three material values on the MAT1 entry.
1-19167555
2005.0.2
MASTER - UFM 1277
FMS - ASSIGN DELETE keyword ignored for
If an analyis with SCR=NO and explicit ASSIGN statements using the DELETE
keyword is repeated, the job will fail with the message:

THE FILE ASSIGNED TO LOGICAL NAME = MASTER IS NOT A VALID MASTER DBSET
FOR A PRIMARY DATABASE.
USER ACTION : VERIFY THE FILE NAME SPECIFIED ON THE ASSIGN MASTER
STATEMENT.
For example an analysis with:
ASSIGN DBALL='stress.DBALL',DELETE
ASSIGN MASTER='stress.MASTER',DELETE
is repeated without first deleting the dball and master, the job will fail with
the message above.
1-19168318
2005.0.2
nd has no effect on MPCForces
Postprocessing - POST case control comma
The POST case control command, introduced in V2004, does has no effect on
MPCForces output. This output will always be written to the standard unit 12.
1-19183701
2005.0.2
SIGN - UFM 740 (RDASGN)
Distributed Memory Parallel - INPUTT2, AS
The INPUTT2 module will fail on DMP slave processes if an ASSIGN statement is
used. USER FATAL MESSAGE 740 (RDASGN) is issued.
Avoidance: Do not use ASSIGN. Copy the INPUTT2 file to the default Fortran
unit file (e.g. "fort.60" or "ftn60" for unit 60 on Unix).
1-19192460
2005.5
Postprocessing - RANDOM, SORT1 for DISP
and ACCE - SORT1 Request Ignored in Random Analysis
The following request in Nastran 2004 and 2005 will generate OP2 results in
the incorrect format. OUGPSD2 is written to the op2 file instead of OUGPSD1.
DISPLACEMENT(SORT1,PLOT,PHASE,PSDF) = ALL
ACCELERATION(SORT1,PLOT,PHASE,PSDF) = ALL
This is a limitation in releases prior to Version 2005R3. Nastran only
generates SORT2 random results because the original design required all results
to be output though the XY-PLOT module which only supports SORT2.
1-19198771
2005.0.2
Frequency Response - SPCD, PARAM,RESVEC Null Results for multiple load cases
If SOL 111, modal frequency response, is restarted from SOL 103 with resvec=yes
and there are multiple dynamic SPCD load cases, the results for the 2nd and
subsequent subcases will be null.
Avoidance: Do not submit the job as a RESTART or only analyze one subcase in
each restart.
1-19201391
2005.1
ncy Response - Missing Output
External Superelements - EXTSEOUT, Freque
A SOL 111 assembly run employing external superelements created using the
EXTSEOUT feature does not give output for the external SE if the creation run
had only velocity and/or acceleration output requests.
Avoidance: Make a displacement request when creating the external

superelements.
1-19203339
2005.1
ng answers in dynamic analysis
Dynamic Analysis - GPFORCE=set yields wro
Although the Version 2005 QRG Case Control table 4-5 shows that the GPFORCE
request is not supported in SOL 108,109, 111, and 112, including it in the Case
Control produces GPFORCE output. If the GPFORCE request references a SET then
the resulting numbers are incorrect. If the GPFORCE references "ALL" then the
results are correct.
1-19203341
2005.0.2
Utilities - f04rprt
The f04rprt utility is missing from the v2004 and v2005 installations.
Avoidance: Either user the utility from the v2001 installation or download the
utility from MSC's external web site at:
1-19209144
2005.5
Heat Transfer Analysis - View factor calc
ulation with CHBDYG,AREA8 - Wrong Answers
Coarse mesh models with curved surfaces will produce incorrect view factor
calculations with CHBDYG elements using the AREA8 option.
Avoidance: Refine the mesh using CHBDYG,AREA8 with CQUAD8 elements or use
CHBDYG,AREA4 with cquad4 elements.
To address this problem the code is
modified to use corner grids to compute view factors for warped elements.
1-19210511
2005.1
mset=on - Poor Accuracy.
MDACMS - DOMAINSOLVER, CWELD, PWELD with
A SOL 200 analysis using mdacms gave incorrect answers with cwelds and mset=on
unless upfact was turned up to 3.0 from the default value of 2.0 on the
DOMAINSOLVER entry. .
1-19210562
Answers
2005.0.2
Superelements/ MDACMS - EXTSEOUT - Wrong
MDACMS may produce wrong answers when used on the residual structure of a
superelement model and thus should not be used.
1-19227541
2005.1
Superelements - BEGIN(SUPER), PARAM,POST,
-2 - SFM 6352, MAKoG2TD, logic error, kerror, 132
If a model contains part superelements (BEGIN SUPER=) and PARAM,POST,-2 is
specified, the job may fail with the following error:
*** SYSTEM FATAL MESSAGE 6352 (MAKoG2TD)
132.
The error is present in v2004, v2004.5, and v2005.0.0
compile phase0
alter 'dbdelete datablk=(bulk)'
peid=-1 $
seid=-1 $
endalter $
1-19246291
2005.0.2
iinte Loop, Missing Fatal Message
Spot Weld Elements - CWSEAM, MODGM2 - Inf
If a CWSEAM element is oriented normal to the sheets, the projection plan

algorithm may go into an infinite loop.
Avoidance: Correct the orientation of the CWSEAM elements.
1-19254994
2005.1
Nonlinear Analysis - GPFDR - Incorrect re
sults from SOL 106 GPFORCE Output with TEMP(LOAD)
An error is present in the GPFDR module when a mechanical load is applied in
the first subcase and then a temperature load is added to the mechanical load
in a second subcase. The displacements and element stresses are correct but
the grid point forces are obviously in error since the totals contain
excessively large values instead of computed zeros.
An avoidance is to add a TEMP(LOAD) in the pressure only first subcase that
uses the initial temperature load id. This will cause the solution to do a
little more work and there will be no temperature load effect since the
temperature difference is 0.0. In the combined.bdf file I added one case
control statement as shown below.
$ Direct Text Input for Global Case Control Data
TEMPERATURE(INITIAL) = 1
SUBCASE 1
$ Subcase name : Pressure
SUBTITLE=Pressure
NLPARM = 1
SPC = 2
temp(load)=1 $ added to avoid GPFORCE error.
LOAD = 3
Test case is in /msc/app.etl/q1-19254994.dat
1-19256131
2005.0.2
ct Boundary Connection, Poor Answers
Superelements - SECONCT, LOC=NO - Incorre
When the LOC=NO option is specified on the SECONCT entry, grids may be lost
during the automatic search procedure.
Avoidance: Use the default value of LOC=YES.
1-19271241
2005.0.2
d unnecessarily
Restarts - FREQi, RESVEC - Decomp execute
If a modal solution (110, 111, 112, and 200) restart is executed from a modal
solution run and then DECOMP may be unnecessarily executed for the RESVEC
calculation.
Avoidance: Insert the following alter in the cold start run:
compile modefsrs
alter 'purgex \/day,bdsf,mdsf,k4dsf,kdds'
purgex /adsf,,,,/-1 $
alter 'purgex \/day,bdsf,mdsf,k4dsf,kdds'(2)
purgex /adsf,,,,/-1 $
endalter
1-19278741
2005.0.2
ssure output - Wrong answers
Acoustic Analysis - STATSUB, acoustic pre
If STATSUB is employed in SOL 108 or 111 with an acoustic model, then the
acoustic pressure results will be null except for DB(A).
Avoidance: Insert the following DMAP alter avoidance
compile phase0
alter 'IF ( FSCOUP AND not(desopt) and',''
IF ( FSCOUP AND not(desopt) and not(kdiff) and
(STATICS OR CYCLIC OR NLHEAT OR AERO)) THEN $
1-19283941
ssembly run
External Superelements - EXTSEOUT - GRAV loading ignored in a
An assembly run employing an external SE created using the EXTSEOUT feature

ignores GRAV loading specified in the assembly run.
compile phase1dr
alter 'call extin'(3)
CALL SELG SLT
,BGPDTS
MPTS
,ETT
DIT
,MATPOOL
DEQIND ,USET0
MEDGE ,drg
mgg
,kgg
PJ
,PTELEM
STATICS /SEID
GRDPNT /ERROR
NLHEAT /IMAGE
pexist $
add5
pj,pa,,,/xxx $
equivx xxx/pa/-1 $
,CSTMS
,EDTs
,EQEXINS
,GPLS
,geom4s
/
,newslt
/LUSETS
/pardcmp
/NONLNR
,SILS
,Maa
,CASES
,GPSNTS
,estl
,EST
,
,CASEw ,
,DEQATN ,
,scstm ,
,dynamics,
,
/(1.,0.)
/IRES
/NASOUT
/
/(1.,0.) /
/PRPJ
/
/0
/
1-19287331
2005.5
551 (INPTX2) caused by multiple frequency requests
A job that includes external superelements that has multiple subcases with
different frequency requests may fail with the following message:
USER INFORMATION MESSAGE 7321 (SEDRDR)
AN END-OF-FILE WAS DETECTED ON UNIT 141 DURING BINARY INPUTT2
Avoidance: Apply the following dmap avoidance in v2005
compile super3
alter 'if ( exterse'
type parm,nddl,i,n,zuzr1 $
type parm,nddl,logi,n,zuzrl1 $
zuzr1=seid $
if ( not zuzrl1 ) then
alter 'call extotmin'
call dbstore tug1,mug1,tqg1,mqg1,//seid/0/'
'/0 $
call dbstore tes1,mes1,tef1,mef1,//seid/0/'

'/0 $
zuzrl1=true $
else
call dbfetch /tug1,mug1,tqg1,mqg1,/seid/0/0/0/0 $
call dbfetch /tes1,mes1,tef1,mef1,/seid/0/0/0/0 $
endif $
1-19306232
2005.1
External Superelements - DMIGOP2, RESTART
- SFM 4252 matrix XAAV does not exist
Restarting an external superlement analysis from SOL 103 to 111 with DMIGOP2
may fail with the message;
1-19307471
2005.1
- Misleading Message, UFM 6482 (DOPR3R)
The following message is given when an integer value is used for ATTB in an
ANALYSIS = STATICS subcase for response types DISP,STRAIN,STRESS or FORCE.
*** USER FATAL MESSAGE 6482 (DOPR3R)
FOR SUBCASE
1, THE ANALYSIS TYPE IS STATICS BUT THE DESSUB
COMMAND REFERENCES AN INCOMPATIBLE
DRESP1 ENTRY WITH RID =
24 AND RTYPE = STRAIN.
The message needs to be updated to indicate that a non-zero ATTB value is not
allowed for these response types. The message should also be added for
response types of ESE,TOTSE,SPCFORCE,GPFORCE,GPFORCP. Currently, an integer
value of ATTB is permitted for these latter entries, but it should be blocked
so that the user does not set it with the expectation it will do something.
Avoidance: Remove the non-zero value of ATTB.
1-19325591
2005.1
Nonlinear Heat Transfer Analysis - CHBYDE
, CHBDYG - Coarse Mesh, poor results or non-covergence
Heat transfer analysis models with CHBDYE and CHBDYG elements with coarse
meshes as can be found in tpl problem ht15306 may fail to converge or produce
poor results.
Avoidance:
1) Model using CHBDYP with view view factor instead of CHBDYE or CHBDYG
elements.
2) Refine the mesh.
3) Insert the DMAP alter
COMPILE NLKR $
ALTER 'RMG2.*RGG' $
$ MODIFY THE RADIATION TO AVOID TEMPERATURE OVERSHOOT WITH COARSE MESH
$
VERSION 2005
FEBRUARY 25, 2005
BY BOB HARDER
ECHOOFF
$RMG2
EST,MPOOL,MUGNI,KGGNL, MPTS, DIT, BGPDTS,SILS,USET1/
$
RDEST,RECM,RGG,KGGPNL/TABS/SIGMA/S,N,NORADMAT/LUSETS $
$ MOVE POSITIVE OFF-DIAGONAL MATRIX TERMS TO DIAGONAL
$
PARAML RGG//'TRAILER'/1/S,N,GSIZE $
DIAGONAL RGG/DRGG/'SQUARE'/1. $
DIAGONAL TERMS
ADD
RGG,DRGG/ORGG/(1.,0.)/(-1.,0.) $ OFF-DIAGONAL TERMS
DIAGONAL
ADD
MATGEN,
MPYAD
MATMOD
ADD5
EQUIVX
MESSAGE
ADD
TRNSP
DIAGONAL
ADD
DIAGONAL
ADD
MPYAD
MATMOD
ADD5
DELETE
TRNSP
ADD
MESSAGE
ECHOON
ORGG/ARGG/'WHOLE'/1. $
ABS(OFF-DIAGONAL TERMS)
ORGG,ARGG/XRGG/(.5,0.)/(.5,0.) $ OFF-DIAGONAL TERMS .GT. 0
/ONES/6/V,N,GSIZE/0/V,N,GSIZE $
COLUMN OF ONES
XRGG,ONES,/SRGG $
ROW SUM(OFF-DIAGONAL TERMS .GT. 0)
SRGG,,,,,/IRGG,/28 $
VECTOR TO DIAGONAL MATRIX
RGG,XRGG,IRGG,,/NRGG/(1.,0.)/(-1.,0.)/(1.,0.) $
NRGG/RGG/ALWAYS $
//'^^^ RADIATION MATRIX HAS BEEN MODIFIED' $===================
KGGPNL,KGGNL/RGGNL/(1.,0.)/(-1.,0.) $
RGGNL/TGG $
TGG/DTGG/'SQUARE'/1. $
TGG,DTGG/OTGG/(1.,0.)/(-1.,0.) $
OTGG/ATGG/'WHOLE'/1. $
OTGG,ATGG/XTGG/(.5,0.)/(.5,0.) $
XTGG,ONES,/STGG $
STGG,,,,,/ITGG,/28 $
TGG,XTGG,ITGG,,/NTGG/(1.,0.)/(-1.,0.)/(1.,0.) $
/RGGNL,KGGPNL,,, $
NTGG/RGGNL $
KGGNL,RGGNL/KGGPNL/(1.,0.)/(1.,0.) $
//'^^^ NL-CONDUCTION MATRIX HAS BEEN MODIFIED' $===============
1-19349544
2005.1
MAXMIN - Access Violation, Sort 1 Output
When MAXMIN(DEF) output is requested for Grid response using the BRIEF output
format an access violation will occur. By using the FULL directive, the
access voilation can be avoided.
1-19354641
Acoustic Analysis - fluid-only model with SPCD - UFM 3046 in
FRRD1 because of null excitation
A fluid-only SOL 111 model with SPCD specification fails with UFM 3046 in the
FRRD1 module complaining of null excitation.
Avoidance; The problem runs successfully if PARAM,ENFMETH,ABS is specified.
(This used to be PARAM,ENFPATH,OLD in pre-V2005 versions.)
1-19361520
2005
formatted file.
DMAP - INPUTT4 - SFM 6445 when reading un
INPUTT4 may fail with the following message when attempting to read unformatted
files:
*** SYSTEM FATAL MESSAGE 6445 (INPTT4)
READ REQUESTED RETURNED INCORECT DATA LENGTH WHILE PROCESSING UNIT = 11
FOR LOGICAL NAME INPUTT4
EXPECTED
4 WORDS, ACTUALLY READ
5 WORDS
USER ACTION: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT
In a test case which attempts to read in the GM, GOT, KFS and KSS matrices, the
fatal error was encountered on both a SGI and PC machine. Tests on 2004.0.6
and 2005 were successful.
Avoidance: Possible avoidance is to try using a formatted fortran file or use
version 2005.4 or later systems where this problem has been addressed.
op4util -fc inputfilename outputfilename
1-19362761
2005.1
Spot Weld - CWELD - ERROR IN SORTC ROUTIN
E, TASNP2
The fatal error below is encountered in TASNPT if a model has spot weld
elements with point to patch connections combined with the elpat/partpat
format.
ERROR IN SORTC ROUTINE, NBRWDS =
LENTRY =
5
66 IS NOT AN INTEGRAL MULTIPLE OF
1-19369064
2005.5
T(XYPLOT) - Extra Printed Output
Frequency Response - STRESS=set id, OUTPU
If a model contains a STRESS=set id request but also contains an XYPLOT type

request for different element ids, then printed output may be generated for the
elements with an XYPLOT request.
1-19372191
2005.5
DMAP - MATPRN - Matrices
The MATRPN module can only print 6 digits for rows and columns, ****** will be
printed for matrices greater than one million rows and columns.
1-19374101
FM 7558
2005.1
Dynamics - PARAM,AUTOQSET,YES , CWELD - U
If PARAM,AUTOQSET,YES is specifed with CWELD elements with MSET=ON on the PWELD

entry, then the run may fail with UFM 7558.
compile extduset
alter 'equivx.*geom1\/geom1qs',''
1-19381619
ck, Overflow
2005.1
Nonlinear Heat Transfer - TEMPD - Traceba
The solution for nonlinear steady state thermal analysis with radiation
enclosures is depedent on the initial guess for TEMPD. If the initial guess is
incorrect by a large amount it may cause the solution to have trouble
converging as evidenced by extremely large convergence factors and the job may
end in a floating point exception. .
.
MAIN:
A(/XNSTRN/) = 3CF0020
MAIN: Exception occurred at address 00524C15.
1-19385474
2005.1
upling of internal free fluid faces
Acoustic Analysis - ACMODL - Erroneous co
Nastran couples internal free fluid faces which is wrong.

1-19390023
lete
Documentation/QRG - CQUAD4 differential stiffness remark obso
Remark 6 for CQUAD4 should now read:

..."The specification of offset vectors gives wrong results in solution
sequences with geometric nonlinear
analysis (SOL 106, 129, 153, 159 with PARAM LGDISP>0) The differential
stiffness is computed correctly in
V2004 and higher (SOLs 5, 16, 105 and 200 and SOL 106 with PARAM LGDISP <=0)
1-19393769
2005.1
ues for multiple shifts
Complex Lanczos - EIGC - Missing Eigenval
When mutliple shifts are specified on the EIGC entry for complex Lanczos, the
module only provide the number of eigenvalue pairs requested for the first
shift.
1-19394948
2005.5
nostics for an ill conditioned model
CDITER - Infinite CPU Loop, No FATAL diag
On rare occasions for ill-conditioned models, the round off error in

caluculating the QR1 matrix used for testing convergence in CDITER will make it
difficult to find a new random vector and an infinite loop may be encountered.
The problem can be diagnosed by setting PARAM,CDPRT,YES which will print the
QRI terms. Tthe symptom is a very small negative (tensile) force on the order
of E-4 or smaller.
1-19406406
2005.5
Documentation/QRG - params CWDIAGP and C
WRANDEL - Descriptions have been swapped
The text describing the PARAMs CWDIAGP and CWRANDEL have been swapped.
Current Version 2005 MSC.Nastran QRG:
CWDIAGP Default = NO
For CWELD element: if not zero, then it specifies as a decimal percent
the number of fasteners to randomly delete.
CWRANDEL Default = 0
For CWELD element: prints elements randomly deleted if set to YES.
Should be:
CWDIAGP Default = NO
For CWELD element: prints elements randomly deleted if set to YES.
CWRANDEL Default = 0.0
For CWELD element: if not zero, then it specifies as a decimal percent
the number of fasteners to randomly delete.
1-19415074
2005.1
SOL 600 - Incorrectly translated DIST LO
AD entry in Parameter section of marc input - EXIT 13
DIST LOAD entry in Parameter section of the marc input deck is not written
correctly. The 4th field in the DIST LOAD entry in the PARAMETER section is
the Maximum number of nodes with point loads applied. When Gravity load is
applied in a model with Point Mass elements, the Marc input deck is created
with POINT LOAD entries in the model and/or history sections. But the 4th
field in the DIST LOAD entry is not given a large enough number. The Marc run
exits with the EXIT 13 indicating the following error:
*** error - attempt to define too many point loads
0.000E+00 0.000E+00-0.208E-04 0.000E+00 0.000E+00 0.000E+00
a list of nodes given below
3749
1-19418098
2005.1
correctly into DIST LOAD
SOL 600 - Gravity Loads are not converted
Gravity Loads are not converted correctly in to DIST LOAD. For example, the
following entries in the .bdf are converted to .marc.dat incorrectly:
$ Loads
LOAD
$ Loads
LOAD
for Load Case : GRAV_0.10_RELIEF.SC2

51
1.
.1
46
1.
for Load Case : GRAV_0.20.SC3
55
1.
.2
46
1.
72
1.
73
72
1.
73
Converted gravity loads may have an incorrect sign. Only one load case has the
correct sign (-ve) and value of gravity. The other load cases have an incorrect
sign (+ve) and wrong values for gravity.
1-19420301
2005.0.2
LUIDSE , scr=no - UFM 1126
Optimization/Design Sensitivity - PARAM,F
If the fluid superelement capability is employed in SOL 200 with scr=no then
UFM 1126 will be issued for data block AG in subDMAP SELA1.
Avoidance: Run with scr=yes.
1-19429021
2005.1
Model Checkout - ELSUM - Element summary
may contain "??????" for mass contribution fields
The printed output from the ELSUM case control command may include "???????" in
the mass contribution fields for the solid element when there are solid
elements (HEXA, PENTA, TETRA etc.) and non-structural mass (NSMx) entries
present in the bulk data. The problem has been traced to a negative subscript
into an element properties array, that on most machines, contains binary zero
and thus does not cause any problems with the ELSUM output. So far, the SGI
Altix machine is the only one that exhibits the error. The error affects the
element summary output only and does not affect other results.
1-19429671
2005.5
Elements - CBAR - UFM 2007 (GP2), OFFT re
ferences "B" and either "E" or "O" with vector V specified
In v2005.0.0, bars and/or beams will issue UFM 2007 complaining that an
undefined grid point 0 has been referenced if all of the following conditions
are met:
- The OFFT field starts with a "B" to designate an orientation vector in the
BASIC system
- The orientation Vector option (e.g. 0. 1. 0. ) is specified
- Either "E" or "O" is used to designate one or both of the shear center
offset coordinate systems
1-19434861
2005.1
R, SUPORT - SFM 3007 (READ)
MDMODES will fail in the READ moduel when the input contains SUPORT entries
with the message:
Avoidance: Use a DMAP alter in the MDMODES subDMAP to omit the MR data block
from the call to READ.

1-19439341
SFM 5423
2005.0.2
Optimization/Design Sensitivtiy - SPCD -
If SOL 200, desisgn optimization, is executed with enforced displacements and

the job employs sparse data recovery the job will fail with a SYSTEM FATAL
MESSAGE 5423 indicating and incompatible matrix multiply:
TRAILER FOR RPH1
TRAILER FOR UHF1
TRAILER FOR YPO1
IS
IS
IS
101
102
103

980 1856
2
2 3664 9760
142 980
2
4 3920 10000
142 2384
2
4 8864 9295
Avoidance: Either set PARAM SPARSEDR NO or set PARAM NASPRT 1. Else apply
the following dmap alter:
compile desopt
alter 'call fea'(2),''
CALL FEA,
$..Input Data Blocks:
abe,acpt,,aebgpdts,aecomp,aero,aeusets, , ,bgpdtvu,
,CASECC,
caseds,casem,CASERS,CASES,casesx,
,control,cstma,CSTMS,
,
DEQATN,DEQIND,
,DIT, ,DMI,DMINDX,drg,
,
DYNAMIC,DYNAMICS,ectas,
,EDT,eht,
ehta,elemvol,EMAP,EPT,epta,EPTS,eqexin,EQEXINS,ETT,extdb,,,FORCE,
gdgk0,gdksk,gdntab,GEOM1,geom1qx,geom1s,GEOM2,GEOM2S,GEOM3,GEOM3S,
GEOM4,GEOM4S,,gpgk0,gpksk,GPLS,gpsnts,,INDTA,,MAPS,matpool,matpools,
medge,mklist,mmcdb,MPT,MPTS, ,oint,PCDB,PCDBS,pcompts,pelsets, ,
POSTCDB,
,pval,PVT,pvtbc,PVTS, ,
,scstm,SILS,SLIST,SLT,
spline,SPSEL,tabdeq,tabevp,tabevs, ,trx,
,
,
,
,VGFS,
vgq,viewtb,XYCDB,XYCDBS,yg,mpjn2o,mpjsfn2o,aempcomp,aemonpt,saemprk,
strucomp,monitor,saerg0,aedbstdx,uxvst,pgvst0,,,,,,xsop2dir,,,
geom1qs,geom4qs,selist,pvt0/
$..Output Data Blocks:
, , , , ,AQG,AUA,AUG,
,
B2DD,B2MG,B2SF, ,bdict,belm, ,BGPDTS,bgpdt,BHH,
, ,BLAMA,
BLAMA1,BMG,BPHA,BSF,BUG,
,CB2DD,
,
CK2DD,clama,CMDD,CMLAMA,CMPHA,CMPHO,cphd,cphh,cphp,
crj,crx,
,
,
,
,Dar,
,
,DFFDNF,
ditid,
,dlt,ECTS,epsse,
,
,EST,
,FLAMA,
,FOL,FOL1,FPHH,frl,
,
,
,
, ,GM,GOQ,GOT,
,GPECT,
,
,
,
K2DD,k2mg,
,K2SF,
,
,
,
,K4MG,K4SF,
,
,
,
,KDICT,
,KELM,
KFS,KHH, , ,KMG,KSF,KSS,
,
,
,LAMA,LAMA1,LAMAF,LAMAS,LLL, ,
lphd,lphh,lphp, ,
,
M2MG,M2SF,MAR, ,MDICT,MEA,MELM,MHH,
,
,mjj,
, ,MMG, , ,MSF,MTRAK,
, , ,PDF,PDT,PDTDS,PG, ,PHA,
,PHDH,PHF,
PHFA,PHG,
,
,
,
,PHQG,PHSA,PJ,
, ,PNLH,PPF,PPF1,PPT,PPTDS,PP1DS,PSF,PSF1,PSS,PST,
,PSTDS,PTELEM,QG, ,
, ,
, ,
,
,
, ,
,qmg,qmpf,qmpt,QPF,QPT,QR,
, ,
,TOL,TOL1,TOL2,TR,
,
,
,UDF,UG,
,,UHF,UHT,UHTDS,UL,
ULF, ,ULTDS,UOO,UPF,UPT,
,
,USET,USETD,
VAFS,VELEM,ypf1,vgfd,VPHFS,WKK,
,
,
,YS,ypo ,
,
,
, ,,,,,,,,,,,,,,,,,,mdphiq,mdgot,mdgoq,mdvft,mdmap,
mdgrdrm/
$..Input Parameters:
AERO/adjflg/AERTYP/ALTRED/APP/AUNITS/AUTOSPC/BUCKCC/cnvflg/true/
CYCLIC/dceigcc/DESCYCLE/deseig/desmax/DFRQCC/DFRQDSA/dfrspcf/DMRESD/
DROPT/
DROPTDS/dstspcf/DVRGCC/dtrspcf/ERROR/EXTERSE/FEAOPT/FIXEDB/fluidse0/
FLUTCC/FSCOUP/G/GUSTAERO/HFREQ/IKBAR/IMACHNO/INREL/IQ/KDAMP/0
/
LASTSEID/LFREQ/LMODES/LUSETS/mceigcc/MFRQCC/MFRQDSA/MODACC/MODECC/
MTRNDSA/MTRNCC/NASOUT/nk/NLHEAT/NOPH1/NOPH2/NOSEDV/
OPTIMIZE/PEXIST/PSLOAD/rgsens/RSONLY/SAERCC/SAERODSA/SEKR/
SELG/SELR/SEMG/SEMR/SKPAMG/SKPAMP/SOLTYP/STATCC/STATDSA/
$..I/O Parameters:
S,ADPTEXIT/S,ADPTINDX/s,BOV/s,BMETH/s,CARDNO/s,freqdep/
s,FS/s,luset/s,METHF/s,MDTRKFLG/s,MODETRAK/s,NMSOL/s,NORSET/
s,NOSASET/s,NSOL/s,PFILE/S,PVALID/s,STATSUB/s,SUPORT/0 $
1-19456411
2005.1
AD) - Poor Answers
Elements - CHEXA, CTETRA, CPENTA, TEMP(LO
If a solid element model has a temperature rise which is linear in (x,y,z),

then there should be zero thermal stress if the constraints are nonredundant.
Due to limitations imposed by the isoparametric shape functions, MSC.Nastran's
elements give poor results for displacements and stresses. This occurs for
HEXA, PENTA, and TETRA elements, especially if there are no midside nodes. A
new theory is now available that lets us eliminate this limitation. This
implementation gives exact displacements and zero stresses for bodies modelled
with HEXA, PENTA, and TETRA elements if the temperature is linear and the
constraints are nonredundant. This is even true for a TETRA-4 element which is
notoriously inaccurate.
This revised theory was released in version 2005r2i (2005.1). If you want to
compare with the old method, you can use NASTRAN,SYSTEM(428)=1 to get the old
answers.
1-19458251
Documentation - MSC.Documentation (pdf files) crash with Acro
bat reader version 7
The MSC.Documentation (pdf files) can be properly browsed with Acrobat Reader
version 5 and 6, but when using version 7, Acrobat reader crashes.
1-19459484
2008.0.0 (MD R3)
Documentation/QRG - PCOMP - Remark 11 obs
olete, kdiff is now calculated for unsym layup
Remark 11 under the PCOMP Quick Reference Guide description that indiates that
it is not recommended to use an unsymmetric layup in solutions that require
differential stiffness is not longer applicable.
1-19485913
2005
R - Poor Message, SFM 6833 (PNBREC)
A large solid model with 128,000 HEXA elements fails in SOL 103, geometry
domain parallel, dmp=8 with the message:
SYSTEM FATAL MESSAGE 6833 (PNBREC):
ERROR: 0032-117 user pack or receive buffer is too small
Avoidance: In this case the model was able to be run successfully with dmp=2
and dmp=4.
1-19491251
2005.1
Distributed Memory Parallel - Small jobs
eigenvalue jobs may fail with SFM 9160 (MDACMS)
Very small eigenvalue problems that specify Lanczos, automatically revert to
the AHOU eigenvalue method. If this occurs during a DMP execution the model
^^^ SYSTEM FATAL MESSAGE 9160 (MDACMS)
^^^ PROBLEM ENCOUNTERED IN CALCULATING MDACMS DOMAIN
MODES.
^^^ USER ACTION:
IF LARGE MASS IS BEING USED FOR ENFORCED MOTION THEN
REPLACE LARGE MASS METHOD WITH DIRECT METHOD
USING THE SPCD BULK DATA ENTRY.
^^^ IF THE LARGE MASS METHOD IS NOT BEING USED THEN MASSLESS MECHANISMS MAY
EXIST. PARAM,MECHFIX,YES
MAY BE USED TO IDENTIFY MASSLESS MECHANISMS.
1-19522131
2005.1
External Superelements - EXTSEOUT, SPOINT
s - SFM 3001 in the BDRYINFO module.
An external SE creation run employing the EXTSEOUT feature with only scalar
points fails with SFM 3001 in the BDRYINFO module.
1-19522212
2005.1
Superelements - AUTOQSET and only scalar
points on boundary fails with SFM 3003 in GP1.
An external SE creation run employing the EXTSEOUT feature with the DMIGOP2
option, PARAM,AUTOQSET,YES and only scalar points on the boundary fails with
SFM 3003 in the GP1 module in the EXTOUT subDMAP.
1-19522273
2005.1
External Superlements - Assembly SE run
with only SPOINTS on boundary issues SFM 4276 in GP1.
An assembly run employing an external SE created using the EXTSEOUT feature
with manual QSETi data and only scalar points on the boundary fails with SFM
4276 (Error Code 3001) on a call to GREAD in the GP1 module.
1-19528421
2005.1
for STRESS(punch,center)
Elements - SYSTEM(370)=5 - Wrong Answers
If nastran system cell(370)=5 is used to convert CQAUD4/CTRIA3 to

CQAUDR/CTRIAR, and (STRESS(punch,print,SORT1,REAL,VONMISES,CENTER) is selected
the punch output will be incorrect.
1-19529350
2005.1
Optimization/Design Sensitivity - PARAM,
DESPCH - Incorrect values in punched bulk data - HP only
Optimization, SOL 200, may produce incorrected punched bulk data on HPUX. AIX,
Sun also produce different punched bulk data. Problems might be in PBAR
elements.
Avoidance: Setting param,despch,-1 outputs the bulk data in small field format
and avoids the problem.
1-19531550
2005.1
Superelements - Job consisting of only SP
OINTs fails with SFM 3001 in the SEP1X module.
A part superelement job consisting of only SPOINTs fails with SFM 3001 in the
SEP1X module. The same job runs successfully if the boundary SPOINT is
replaced by an equivalent GRID point.

1-19535231
2005.5
Optimization/Design Sensitivity - PCOMP SFM 4276, EC =3061, UFM 2042 (DSABO)
When an optimization job specifies identical PID on a designed PCOMP entry and
another designed property entry such as PBEAML, it may fail with a misleading
USER FATAL MESSAGE 2042 (DSABO): Missing Material Table ***** for Element 1.
Avoidance: Use unique PIDs among all designed property entries.
1-19557001
2005.1
nd Qy for plate elements are wrong.
Frequency Response - CQUAD4 - Corner Qx a
Frequency response analysis produces incorrect QX and QY CQUAD4 complex corner

stresses.
Avoidance: Other than using the results from the center of the element, there
is no avoidance.
1-19557090
2008.0.0 (MD R3)
Density Label missing
Random Analysis - RANDPS - Power Spectral
When a corner output request is made for plate elements, the label "POWEWR
SPECTRAL DENSITY FUNCTION" is missing.
1-19579411
2005.1
Case Control - K2GG, M2GG, B2GG, K42GG, A
2GG (etc.) - Continuation Lines lead to UFM 614 (IFP1D)
If the case control command K2GG (or any of its variants) calls up more
matrices than can be specified on one line, and a continuation line is added,
the solution may fail with the following message:
THE ABOVE SET IS BADLY SPECIFIED.
Avoidance: If the list of matrices does NOT contain scale factors, place the
list of matrices on a SET entry and call the SET from K2GG. For example:
SET 992 = KX1, KX2, KX3, KX4, KX5, KX6, KX7, KX8, KX9, KX10,
KX11, KX12, KX13, KX14, KX15, KX16, KX17
K2GG = 992
If the list has scale factors, there is no avoidance.
1-19600121
2005.1
anslated correctly - Wrong Answers
SOL 600 - CBUSH/PBUSH elements are not tr
The CBUSH element property orientation is not translated correctly in SOL 600.
This may lead to wrong answers.
1-19603931
2005.1
Optimization/Design Sensitivity - SPCD,
MODESELECT scr=yes - Wrong Answers, Poor Convergence
SOL 200 with scr=yes for ANALYSIS=MTRAN,MFREQ,MCEIG, or FLUTTER may differ from
a scr=no run in the following areas:
1. Wrong answers in enforced motion
2. Different convergence behavior or no convergence
3. SFM 3200 in GKAM1C if MODESELECT based on effective mass fractions is
requested.
Avoidance: Run with scr=no or insert the following DMAP alter:

compile fea
alter 'call feamode',''
call feamode,
$..Input Datablocks:
adrdug,ag0,ajp,bgpdtvu,CASECC,caseds,casem,CASERS,
CASES,CASESX,CASEXX,cstms,DEQATN,DEQIND,dit,drg,
DYNAMIC,DYNAMICS,ectas,edom,EDT,eht,ehta,elemvol,
EMAP,EPT,epta,EPTS,EQEXINS,ETT,extdb,FORCE,gdntab,
GEOM1,geom1qx,geom1s,GEOM2,GEOM2S,GEOM3,GEOM3S,GEOM4,
GEOM4S,GM,GPDTS,GPLS,gpsnts,ibulk,INDTA,MAPS,matpool,
matpools,medge,mgg,mmcdb,MPT,MPTS,oint,PCDB,PCDBS,
pcompts,pelsets,POSTCDB,pval,PVT,pvtbc,PVTS,R1TABR,
rmg,rvg,scstm,SILS,SLIST,SLT,tabevp,tabevs,tempall,
USET0,VGFS,vgq,viewtb,XYCDB,YG,xsop2dir,pvt0,
asf,aay,aaa,day,kdmg,kdss,gei,pmyg,pbyg,pkyg,
mss,bss,cee,mee,gge,bec,mec,meh,cmlama1,epsseo,mphvz,bk4zz,phqmg,
kgg,kay,may,bay,k4ay,k4ss,phba/
$..Output Datablocks:
AGG,BAA,bdict,belm,BGG,BGPDTS,bgpdt,BJJ,BMG,BSF,
CMLAMA,CMPHA,CMPHO,Dar,DFFDNF,ditid,ects,error,
errorg,EST,frl,GOQ,GOT,GPAK,GPECT,K4AA,K4JJ,K4MG,
K4SF,kaa,KDICT,KELM,KFS,KJJ,KLL,KMG,KSF,KSS,L2RR,
LAMA,LAMAF,LAMAS,LLL,LOO,LRSEQ,MAR,MDICT,MDSF,MEA,
MELM,mjj,MLL,MLR,MMG,MR,MRR,MSF,MTRAK,orseq,PG,PHA,
pharef,PHFA,phg,PHGref,PHQG,PHSA,PJ,PSS,PTELEM,QR,
USET,VAFS,VELEM,vgfd,YS,maa,mdphiq,mdgot,mdgoq,mdvft,
mdmap,mdgrdrm,adsf,lammats,lammatf,mis,mif,mechg,
bdsf,kdsf,k4dsf,efmfacf,efmfacs/
AERTYP/ALTRED/APP/AUTOSPC/cnvflg/conv/DELTA/DESCYCLE/
DESCYCL1/deseig/desmax/DFREQ/DFRQCC/DMRESD/DROPT/ERROR/
EXTERSE/FEAOPT/FIXEDB/fluidse0/FSCOUP/INREL/LUSETS/
MODACC/NASOUT/nk/NOPH2/NSKIP/PEID/pexist/ploop/pmode/
PSTAT/RSONLY/SEKR/SELG/SELR/SEMG/SEMR/SOLTYP/desiterp/
$..I/O PARAMETERS:
ADPTEXIT/ADPTINDX/CARDNO/freqdep/FS/luset/METHF/
MDTRKFLG/s,modetrak/NORSET/NOSASET/PFILE/PVALID/
SLAVEJOB/SUPORT $
compile feamode
alter 1,1
SUBDMAP FEAMODE,
$..INPUT DATABLOCKS:
adrdug,ag0,ajp,bgpdtvu,CASECC,caseds,casem,CASERS,CASES,CASESX,
CASEXX,cstms,DEQATN,DEQIND,dit,drg,DYNAMIC,DYNAMICS,ectas,edom,
EDT,eht,ehta,elemvol,EMAP,EPT,epta,EPTS,EQEXINS,ETT,extdb,FORCE,
gdntab,GEOM1,geom1qx,geom1s,GEOM2,GEOM2S,GEOM3,GEOM3S,GEOM4,
GEOM4S,GM,GPDTS,GPLS,gpsnts,ibulk,INDTA,MAPS,matpool,matpools,
medge,mgg,mmcdb,MPT,MPTS,oint,PCDB,PCDBS,pcompts,pelsets,POSTCDB,
pval,PVT,pvtbc,PVTS,R1TABR,RMG,rvg,scstm,SILS,SLIST,SLT,
tabevp,tabevs,tempall,USET0,VGFS,vgq,viewtb,XYCDB,
YG,xsop2dir,pvt0,asf,aay,aaa,day,kdmg,kdss,gei,pmyg,pbyg,pkyg,
mss,bss,cee,mee,gge,bec,mec,meh,cmlama1,epsseo,mphvz,bk4zz,phqmg,
kgg,kay,may,bay,k4ay,k4ss,phba/
$..OUTPUT DATABLOCKS:
AGG,BAA,bdict,belm,BGG,BGPDTS,bgpdt,BJJ,BMG,BSF,
CMLAMA,CMPHA,CMPHO,Dar,DFFDNF,ditid,ects,
error,errorg,EST,frl,GOQ,GOT,GPAK,GPECT,
K4AA,K4JJ,K4MG,K4SF,kaa,KDICT,KELM,
KFS,KJJ,KLL,KMG,KSF,KSS,L2RR,LAMA,LAMAF,LAMAS,LLL,LOO,
LRSEQ,MAR,MDICT,mdsf,MEA,MELM,mjj,MLL,MLR,MMG,MR,MRR,MSF,MTRAK,
orseq,PG,PHA,pharef,PHFA,PHG,phgref,PHQG,PHSA,PJ,PSS,PTELEM,
QR,USET,VAFS,VELEM,vgfd,YS,maa,mdphiq,mdgot,mdgoq,mdvft,mdmap,
mdgrdrm,adsf,lammats,lammatf,mis,mif,mechg,bdsf,kdsf,k4dsf,
efmfacf,efmfacs/
$..INPUT PARAMETERS:
AERTYP/ALTRED/APP/AUTOSPC/cnvflg/conv/DELTA/DESCYCLE/DESCYCL1/
deseig/desmax/DFREQ/DFRQCC/DMRESD/DROPT/ERROR/EXTERSE/FEAOPT/
FIXEDB/fluidse0/FSCOUP/INREL/LUSETS/MODACC/NASOUT/nk/NOPH2/NSKIP/
PEID/pexist/ploop/PMODE/PSTAT/RSONLY/SEKR/SELG/SELR/SEMG/SEMR/
SOLTYP/desiterp/
$..I/O PARAMETERS:
ADPTEXIT/ADPTINDX/CARDNO/freqdep/FS/luset/
METHF/MDTRKFLG/modetrak/NORSET/NOSASET/PFILE/PVALID/slavejob/suport $
alter 'type db',''(,3)
TYPE DB ophfa,ophsa,rph,rpd,rsgg,rmgg,gpke,msf1,bsf1,ksf1,
vgdr,vspcg,vmpcg,MMG1,BMG1,KMG1 $
endalter
1-19623877
2005.5
CQUAD4 and CTRIA3 Supported
Documentation/QRG - MFLUID, ELIST - Only
The QRG should note that the ELIST entry only apply to the ctria3 and the
cquad4 elements.
1-19624041
2008.0.0 (MD R3)
Krylov Solver - ILP64 systems may fail wi
th message Incurable breakdown in initial vectors.
The KRYLOV solver may fail on ILP64 (a.k.a. i8) systems with the message
incurable breakdown of initial vectors.
1-19631175
2005.1
Nonlinear Analyis - Restart, GPFORCE Dat
a Recovery Yields No Results, UWM 2354
Nonlinear static analysis, SOL 106, fails to produce grid point force data
recovery during a restart run. The GPFDR module issues UWM 2354:
THIS ERROR OCCURRED IN CODE WHERE THE VARIABLE -NERROR- WAS SET = 4
Avoidance for GPFDR is to restart at SUBCASE intervals rather than at a load
increment.
1-19644046
2005.5
Superelements - Missing OLOAD RESULTANTS
The OLOAD RESULTANTS output for the upstream SE is equal to zero for all
components.
compile phase1dr,nolist
alter 'type.*parm.*nddl'
TYPE PARM,NDDL,I,Y,RESLTOPT $
TYPE PARM,,I,Y,ALTSHAPE $
alter 'ENDIF.*SETYPE=.*EXTRNA'
IF (SETYPE = 'EXTRNA') THEN
$ expand PA to Jsize
UMERGE USET0,PA,/PJext/'G'/'A'/'O' $
message //'OLOADS from external se follow' $

VECPLOT PJext,BGPDTS,SCSTM,CSTMS,CASESX,,MEDGE,,/
,PJRESext,PJHDext,,/
GRDPNT/S,N,ZERO/RESLTOPT/'OLOAD'///ALTSHAPE//SEID $
ENDIF $
1-19650401
2005.1
ile that has been read to its end.
DMAP - INPUTT2 - INPUTT2 won't rewind a f
INPUTT2 won't rewind a file that has been read to its end, if attempted the job
will fail in the INPUTT2 module and the only message will be in the log file:
forrtl: severe (24): end-of-file during read
1-19654201
mplemented
2005.5
Dynamics - Rayleigh Damping Incorrected i
The current Rayleigh damping is not implemented correctly in GMA. Only the
structural matrices should be scaled, but the final matrices are scaled (after
param, G, k4, tf, *2pp are added). Beginning in 2005r3
- Alpha1 and Alpha2 will affect only the structure
- New Alpha1fl and new Alpha2fl will affect the fluid.
1-19680181
UFM 2258
2005.1
Aeroelastic Analysis - MONPNTt3, SET1 -
If a monpnt3 entry references a non-existant set1 id, USER FATAL MESSAGE

2258 is issued, however the monpnt3 id is in the wrong slot of the error
message and the set1 id may or may not be the id of the bad set1. In addition,
this type error should not be a fatal, but a warning message because the
checking is done late in the analysis.
1-19689679
2007.1.0
G lead to UFM 300
Case Control - Scale Factor applied to P2
Attempting to apply a scale fact to P2G, (i.e. P2G = 1.25*PAX) may lead to user
fatal message 300 in the case control section or the factors may be ignored.
1-19702867
2008.0.0 (MD R3)
UFM 4377 (IXPCOMP)
Composites - PCOMPG and Lam SYM option -
If PCOMPG is used with LAM option and SYM the following fatal errors will be
encountered.
*** USER FATAL MESSAGE 4377 (IXPCOMP)
PCOMP ID. 201 HAS NO PLY DATA.
USER ACTION: VERIFY EXISTENCE AND/OR UNIQUENESS OF CONTINUATION FIELD(S)
ILLEGAL DATA ON BULK DATA ENTRY PCOMPG
This input combination is corrected by issuing the message:
ILLEGAL DATA ON BULK DATA ENTRY PCOMPG
PCOMPG 12
5000. HILL
+000005
++000005100000 1
.0054 45.
YES
0.0
SYM
+000006
USER/PROGRAMMER INFORMATION:
BULKNM = PCOMPG (Name of the Bulk Data Entry)
KM =
0 (0:First Line, >0: Continuation Lines)
J+1 =
9 (Data Field Number, 1 through 10)
MF() =
3=BCD, 4=Double,
M() =
CALLSB =
NOTE :
3 (Field Data Format: 0=Blank, 1=Integer, 2=Real,

-32767=End-of-Data)
SYM
(Field Data Value)
IXPCOMP (Name of subroutine)
LAM=SYM is not supported for PCOMPG
1-19722224
2005.1
001 in the BDRYINFO module.
External Superelements - SPOINTS - SFM 3
An external SE creation run employing only SPOINTS fails with SYSTEM FATAL
MESSAGE 3001 in the BDRYINFO module.
1-19744067
2005.1
g Title and Label information
SOL 600 - TITLE, SUBTITLE, LABEL - Missin
In SOL 600 titling information is not carried through in the f06 output.
Avoidance: Add param,mop2titl,-1.
1-19747531
2005.1
Elements - CHEXA8 with bubble functions
and bad geometry - Missing Fatal Message, Poor Answers
A CHEXA8 element should have a Jacobian determinant with the same sign at all
integration points. Failure to do so indicates an invalid mapping to
parametric space caused by an extremely skewed element, which could yield bad
results. This should but does not cause a fatal message.
Avoidance: There is no affect for well shaped elements. Check the element
geometry using IN 2 or 3 on the PSOLID entry.
1-19749179
2005.1
BEAML - UFM 7190 (DOPR1I)
Optimization/Design Sensitivity - PBAR, P
When an optimization job designs both properties on PBAR and PBEAML entries and
no PBEAM entry is present, the job fails in module DOPR1 with the following
error message.
*** USER FATAL MESSAGE 7190 (DOPR1I)
PTYPE PBEAM
DEFINED ON A DVPREL3
0 ENTRY CAN NOT BE FOUND ON A
PROPERTY ENTRY.
USER ACTION: DELETE THE DVPREL3 ENTRY OR INCLUDE AN ADDITIONAL PROPERTY
ENTRY.
Avoidance: Add a dummy PBEAM entry.
1-19753920
2007.0.0 (MD R2)
tion in XCSA, PREFOPT=2
Nonlinear Analysis - Preface Access Viola
A SOL 106 input file with nastran prefopt=2 and two identical mat1 entries
failed with an access violation in the XCSA module.
1-19769081
2005.1
Miscellaneous - INCLUDE - Missing Input
If an INCLUDE statement is missing and the statement is near the end of the
input stream, for example,

INCLUDE 'platest.dat
ENDDATA
the include file is skipped and only a warning about a missing ENDDATA
statement is produced.
1-19780791
2005.1
3 (DSADJ) ATTEMPT TO READ PAST THE END OF FILE in DSDJ2D
An optimization job may fail in DSDJ2D with SFM 3003 when it meets the
following three conditions:
1) GE is present on a MATi entry associated with the designed element group A
2) GE is not present on a MAT entry associated with designed element group B
where both group A and B belong to the same element type.
3) One design element is touched by more than one design variable. For
example, one design variable designs one PBARL or PBEAML dimension,.it will
spawn multiple non-linear design properties that are also treated as design
variables. So one element is touched by more than one design variable.
Avoidance: Use Param,cdif,yes.
1-19780814
2005.5
SFM 3001 in DSDJ1D
Optimization/Design Sensitivity - PBUSH -
An optimization job may fail in DSDJ1D (or DSDJ3D or DSVG1D) with SYSTEM FATAL
MESSAGE 3001 when the input contains one or more PBUSH entries that have
non-zero values in the GE's 2-6 fields and none of these PBUSH entries are
designed.
Avoidance: Create a dummy desvar and dvprel1 entry to design one PBUSH
property where the dummy desvar has the same lower and upper bounds.
1-19791494
2005.1
Elements - PBUSH, TABLED1 - Wrong Answers
Version 2004 and 2005 do not provide the correct results for a bush element if
pbusht/tabled1 is used. The stiffness in the pbush entry is used instead of the
force-displacement curve defined in the pbusht/tabled1 entry.
1-19795091
ong Answers
2005.1
Superelements - SEP1X, CSUPEXT, THRU - Wr
Superelements using CSUPEXT entries containing THRU ranges may produce

incorrect results.
Avoidance: Use delineated grids instead of THRU range.
1-19822213
2005
when Large Memory Requested
Frequency Response - FRLG - Wrong Answers
Frequency response analysis that request more than 2 gig of memory may yield
incorrect results. In the cases that have been observed, the response results
contained spikes.
Avoidance: Either always run with less than 2 gig of memory or plot the
response for all frequency steps and do not trust the results if it contains
unexplained spikes in the response. This problem is fixed in Version 2005.
1-19823963
2005.1
Aeroelastic Analysis - FA1, FLFACT, PKS,
PKNLS - Wrong Answers

Wrong flutter results are computed by the PKS and PKNLS flutter analysis
methods if MAX or POINT normalization is specified on the eigr or eigrl
entries.
Futhermore, if flutter eigenvectors are requested for the PKS or PKNLS methods
using negative velocities on the FLFACT entries, the eigenvetors are not
computed or printed.
Avoidance: To obtain correct flutter results, use the MASS normalization on the
EIGR or EIGRL entry. If flutter eigenvectors are required, the PK or PKNL
method should be chosen.
1-19859061
2005.5
11 - Prestress affects not included.
Acoustics - RESTART from SOL106 into SOL1
If a modal frequency response acoustic analysis restarts from a geometric

nonlinear analysis, the prestress affects are not included on the fluid.
1-19887421
2005.5.2
Elements - QUAD4, TRIA3, K6ROT - Differe
nt behavior for membrane only elements in V2005R2
At the request of a few clients, a new NASTRAN keyword has been added to
Version 2005r3b (a.k.a. version 2005.5.2) and MD Nastran 2006r1a that allows
users to obtain old answers with membrane elements and k6rot. Note that MSC
does not believe that k6rot should ever be used with membrane elements and the
correction to error 1-18688331 blocked its use in V2005r2. The user interface
to obtain the old answers is:
NASTRAN K6ROTMEM=1
1-19901299
2008.0.0 (MD R3)
lysis yields wrong GPForces
Nonlinear Analysis - PELAST in SOL106 ana
In nonlinear analysis, GPForces outputs don't take into account the CELAS
forces that that reference PELAST.
1-19903501
2005.5
SOL600 - Cross section orientation of CBE
AM/PBEAML is not correctly translated
In SOL600, the cross section orientation of the CBEAM/PBEAML entry is not
translated correctly and this leads to wrong answers. Please also see related
quality 1-19558101.
1-19903564
2005.1
SOL600 - Torsional constant J of PBEAML
entry is not tranlated correctly - Wring Answers
In SOL600, the torsional Constant J of the PBEAML entry is not tranlated
correctly and this will lead to wrong answers.
1-19914786
2005.1
Miscellaneous - INPUTT4 Fails to Read a M
atrix written to a Binary Fortran File
A binary fortran file that is written with the utility subroutines to produce
and OUTPUT4 file cannot be read into MSC.Nastran with INPUTT4. The
unformatted writes are writing more information than INPUTT4 will read. When
attempting to read the file with INPUTT4, a message such as follows may be
encountered:
*** SYSTEM FATAL MESSAGE 6445 (INPTT4)

EXPECTED
2523 WORDS
In Version 2005.1 the op4util has been extended to ignore the extra data
(generating a warning) and a new option, fconvert, has been added that allows
the conversion of a file, correcting the long record problem, while preserving
the file's endian format.
1-19919211
2005.5
Connector Elements - CWELD - SFM 7558
Nastran CWELD elements may have a problem projecting the GS node on SHELL
elements. This may lead to SYSTEM FATAL MESSAGE 7588.
1-19947997
2005.1
SOL 600 - CQUADX - Wrong Answers
SOL 600 with axisymmetric CQUADXC elements does not correctly translate the
constraints. This lead to failure or incorrect answers.
1-19948321
cient Restart
2005.5
External Superelements - CSUPER - Ineffi
If CSUPER elements are attached in an assembly restart run, then the

downstream modes maybe un-necessarily recomputed.
Avoidance: Insert the following DMAP alter in the assembly run cold start:
compile extin
alter 'putsys'(,-1)
endif $
if ( setype='extrna' or exter ) then $
endalter
1-19951511
2005.1
a field incorrectly identified.
Postprocessing - param,post,0 - MCID/Thet
The XDB identification always indicates not used or NULL incorrectly. The
checks were bypassed when the Hyperelastic TRIA elements were added during the
MSC.Nastran 70.7 development activities.
1-19969821
2005.1
DMAP - INPUTT2 and INPUTT4 generate scram
bled erorr messages when an I/O error is encountered
The INPUTT2 and INPUTT4 modules generate error messages using MSGPOP where the
arguments do not match the text in ANALYSIS.TXT. Also, the order of the
message lines in ANALYSIS.TXT may generate incomplete messages.
1-19978074
2005.1
Optimization/Design Sensitivity - p2rset
on doptprm may fail in dom10 module with illegal input.
SOL 200 job with p2rset specified on the doptprm entry may fail in the dom10
module with a fatal message that indicates illegal input to the domcb
subroutine.
Avoidance: Remove p2rset from the doptprm entry.
1-19980541
M 979 (XYTRAN)
2008.0.0 (MD R3)
Plotting - XYTRAN *** SFM 4276 (tbk), UW
If an input deck contains an xyplot command that references a non-existent grid

point, the analysis may fail on alpha systems with SYSTEM FATAL MESSAGE 4276
and a traceback in the XYTRAN module.
1-19980761
2005.1
and CAERO5 - SWM 6065
Aeroelastic Postprocessing - PARAM,POST,0
If PARAM, POST,0 is specified along with CAERO5 entries, then the following
warning message may be issued and the xdb file corrupted.
UNDEFORMED GEOMETRY RECOVERY FOR SUPERELEMENT
0
GRIDX
1
0
2
0
0
0
0
0
0
0
CAQ4
1
0
2
0
0
0
0
0
0
0
4 FROM SUBROUTINE CAQ4
ELEMENT
406 GRID POSITION
3 CONTAINS AN INVALID INTERNAL
INDEX.
LIMITS
1
0
2
0
0
0
0
0
0
0
EQEXING
1
0
2
0
0
0
0
0
0
0
EQEXINE
1
0
2
0
0
0
0
0
0
0
1-19981679
cess Violation
2005.1
Plotting - OUTPUT(PLOT) - PLOT Module, Ac
A large static analysis input file encounters an access violation in the PLOT
module in version 2005.0.0.
Job aborting...
User signal caught, errno=0
Command exited with non-zero status 1
Avoidance: Remove the OUTPUT(PLOT) request.
1-19990290
lated
2005.5
SOL 600 - RBE3 Elements Incorrectly Trans
SOL 600 may incorrectly translate RBE3 elements and this leads to wrong answers.
1-19992961
2005.1
UTOMSET - UFM 2101 (GP4)
If PARAM automset is used in sol 200, the job will execute one design cycle and
then fail on the update step before the next design cycle with a message
similar to:
GRID POINT
User Avoidance: apply the following dmap alter:
compile update
UM
US
alter 'gp4',''
GP4
CASESX,GEOM4S,EQEXINS,SILS,GPDTS,BGPDTS,CSTMS,
MEDGE,MFACE,,geom2s,gdntab,,gpsnts,geom1s/
RMG,YG1,USET0,gpsntn/
LUSETS/S,N,NOMSET/0/S,N,NOSSET/0/S,N,NORSET/
NSKIPX/0/0/0/0/0/ALTSHAPE/sebulk/automset/snormprt/
s,n,newgpsn $
1-20009232
2005.5
Rotordynamics - UNBALNC - Null Load
If the vector components (X1, X2, X3) on the UNBALNC entry aligns with the
GRIDA and GRIDB direction defined on the RSPINT entry, then a null solution is
obtained. This should result in a fatal error rather than continuing the
execution.
Avoidance: The avoidance is to correct the UNBALNC X1, X2 and X3 components.
1-20032521
2005.5
Distributed Memory Parallel - EIGRL, DOMA
INSOLVER, STATSUB - UFM 9139 in PHASE0
DMAP checks for fmax on the eigr and/or eigrl entries do not take a static
subcase (statsub) into account and the job may incorrectly fail with USER FATAL
MESSAGE 9139 in PHASE0.
2005r1:
compile phase0
alter 34,49 $
2005r2:
compile phase0
alter 'IF ( (NFOUND\<0 OR FMAX', '' $
1-20049736
2005.5
tiple subcases - Wrong answers
Buckling, Superelements - TEMP(LOAD), mul
If superelements exist in SOL 105 and multiple load cases are analyzed, the
results may be incorrect. The results may vary depending on the order of the
subcases. The use of superelements is not recommened in SOL 105 because the
upstream shapes may not be correct. However, if superelements are used and
multiple subcases exist the results should not depend on the ordering of the
subcases.
compile sekdr
alter 'setq',''
case cases,/case1/'tran'/colno $
call setq case1//seid/peid/s,mtemp/s,k2gg/s,m2gg/
s,b2gg/s,mpc/s,spc/s,load/s,deform/s,templd/
s,p2g/s,dyrd/s,meth/s,mfluid $
1-20066405
2005.5
Optimization/Design Sensitivity - MODE TR
ACKING and SCR=NO - SFM 4276, EC 3001 GREAD
A SOL 200 job that includes mode tracking and eigenvector responses may fail in
the DOM10 module with a message similar to:
BIOMSG: ERROR
0.
STATUS =
3001 HAS OCCURRED IN ROUTINE GREAD
, FILE INDEX =
This error only occurs if SCR=NO is used.

Avoidance: Run with SCR=YES or apply the following DMAP alter:
compile desopt
alter 'RESP3rg,rr2idrg',' '
DELETE /RESP3RG,rr2idrg,wgtmg,RQATABRG,modrprg $
1-20081221
2005.5
Postprocessing - DBC, PARAM,POST,0 - XDB
CBUSH object orientation vector is incorrectly translated
The items within the CBUSH MSC.Access object contain incorrect values for the
orientation information.
1-20088574
ted
2005.1
Heat Transfer - View Factor Output trunca
View factor output may be incorrectly truncated. The output below

demonstrates the problem where the exponent in the last line of the FIJ column
is incomplete.
*** VIEW FACTOR MODULE *** OUTPUT DATA *** CAVITY ID =
***
ELEMENT TO ELEMENT VIEW FACTORS
PARTIAL
SURF-I
SURF-J
ERROR SHADING ERROR SCALE
100001 -
AREA-I
AI*FIJ
C*
FIJ
100002
6.5403E-03 1.36031E-05 2.07989E-03 2.1633E-03
100003
6.5403E-03 7.94674E-06 1.21504E-03 1.3356E-03
100002
6.5403E-03 1.32132E-05 2.02027E-0
NO
YES
NO
100001
YES
100001
240/256
1-20107532
2005.5
Postprocessing - XDB file missing when j
ob is submitted to AIX 5 using "node" option from Windows
MSC.Nastran 2005
Local Computer: Win2000
Remote Computer: AIX 5.1
Hostname = dcadsi03
When user submits job to remote computer:
nastran test1.bdf node=dcadsi03
all Nastran output files are copied (rcp) back to the local WinPC except for
the xdb file.
The mscrsh.exe is being used on the local WinPC when the Nastran job
communciates with the remote computer.
This was verified by looking at the Task Manager on the local WinPC, and seeing
the mscrsh.exe process.
When sumbitting from Windows to a unix machine using the "node" option, the XDB
file is not copied back to the Windows machine. The following warning message
appears after submital:

MSC.Nastran beginning job test1.T2368_12.
The filename, directory name, or volume label syntax is incorrect.
MSC.Nastran job test1@dcadsi03.vought.com completed.
1-20135551
Miscellaneous - param usetprt integer overflow ****** with mo
re than 1 million DOFs
An integer will occur in USETPRT output for inputs greater than one million
DOFs.
1-20135658
2005.5
ect structural damping GE
Dynamic Response - PBUSH, PSHELL - Incorr
Variable GE damping on the PBUSH or PSHELL entries may lead to incorrect

damping and thus wrong answers in Version 2004 and Version 2005.
Avoidance:
Although the error is only likely to occur for large models,
there is no avoidance other than not using this capability. The error has been
fixed in version 2005.1.2. Requested platforms have been put to the Training
and Support - Nastran Product Update web site.
1-20143203
M 2170
2005.5
Frequency Response Analysis - PARTN - UF
A frequency response analysis, SOL 108 , with no null columns in the damping
matrix (BJJX) may fail with USER FATAL MESSAGE 2170 in the PARTN module in the
PHASE1A subDMAP.
compile phase1a
alter 'if ( nonull\<',''
dbstatus vb//s,n,nullvb $
if ( nonull<>-1 and nullvb>-1 ) then $
alter 'if ( nonull\<'(2),''
if ( nonull<>-1 and nullvb>-1 ) then $
endalter
1-20160681
2009.0.0 (MD R4)
th out of plane flexibility
Buckling - QUAD8, TRIA6 - Poor Results wi
CQUAD8 and CTRIA6 may provide poor buckling results when out of plane shear
flexibility is included. This problem is addressed in MD R4 Version 2009.0.0.
SYSTEM(448)=1 may be specified to obtain old results.
1-20164298
2005.5
Incorrect or Missing Punch Output
When a SOL 200 input file includes PBEAM entries with the NO option, the
updated PBEAM entries are not all written correctly to the .PCH file.
Avodiance: There is no avoidance other than manually creating the PBEAM entries.
1-20166404
sing Output
2008.0.0 (MD R3)
Transient Response - SOL 146, OLOAD - Mis
OLOAD output is not supported in SOL 146 for transient reponse.
Avoidance: To request OLOAD output for transient response in SOL 146, add the
compile seaero
alter 'delete \/ppf,psf',''
delete /psf,,,, $
IFT
ppf,CASES,TRL,FOL/
pxf,fol3/IFTM $
equivx pxf/ppf/-1 $
1-20171152
2005.5
Aeroelastic Analysis - PERQ field on the
AEFORCE bulk data entry is not supported
The 2005 Quick Reference Guide indicates that field 9 of the AEFORCE entry can
be used to specify that the associated data is PERQ (that is, per unit of
dynamic pressure). This feature is not supported until Version 2005R3
(2005.5).
Avoidance: Include the dynamic pressure factor in the loads and leave the PERQ
attribute blank
The following alter can be applied in the tier1 version of 2005 or 2006. I
have not checked 2005r2
compile aestatrs list
alter 'pavst'(2),''
type parm,,i,n,nopvperq $
dbstatus pvperq//s,n,nopvperq $
if ( nopvperq > 0 ) then $
$ partition the v-set into those to be scaled by Q and those
$ that are absolute. Then, scale and remerge
partn pavst,pvperq,/paast,,paqst,/1
ADD paqst,/qpaqst/CQ $ scale by q
merge paast,,qpaqst,,pvperq,/pavstf/1 $
$
partn pgvst,pvperq,/pgast,,pgqst,/1
ADD pgqst,/qpgqst/CQ $ scale by q
merge pgast,,qpgqst,,pvperq,/pgvstf/1 $
else $
equivx pavst/pavstf/always $
equivx pgvst/pgvstf/always $
endif $
call appndadb aedbstdx,uxvst,,,,pavstf,pgvstf/
mrgindx,mrguxv,mrgwjv,mrgfjv,mrgqkv,mrgqav,mrgqgv $
PARAML mrgindx//'TRAILER'/1/S,N,NvTERMS $
delete /pavstf,pgvstf,,, $
1-20172731
2005.5
C - Wrong Answers, Primepower Only
Complex Eigenvalue Analysis - CHACBR, EIG
Models with acoustic barrier CHACBR elements may yield incorrect complex
eigenvalues In MSC.Nastran 2005.1 on Fujitsu Primepower machines.
1-20184226
UFM 4016
2005.5
Connector Elements - CWELD, TEMP(LOAD) -
A model which has cweld elements and temperature loading terminates with USER
FATAL MESSAGE 4016 (GETEMP)
Avoidance: A TEMPD must be defined. Temperature loading is not supported for

cweld, cfast, and cwseam elements. The problems has been addressed by
skipping the nodal temperature check for these elements.
1-20194247
2005.5
- Missing Punch Output
Optimization/Design Sensitivity - PBRSECT
An optimization analysis, SOL 200, with designed PBRSECT entries may fail to
punch the complete PBRSECT entry. For some entries, only the outer loop
definition was punched, the inner loop definition was missing. Furthermore,
the outer loop definition was that of the original definition and not the
optimized definition.
Avoidance: There is no avoidance other than manually creating the entries.
1-20216437
2007.0.0
S A NULL TIME STAMP
Restarts - SFM 478 (GPFLIX) DATA BASE, HA
Client ran restart job on Intel Linux and obtained a message indicating that
the attached master file had a null timestamp.
*** SYSTEM FATAL MESSAGE 478 (GPFILX)
THE FOLLOWING LOGICAL NAME, PART OF THE LOCATED DATA BASE, HAS A NULL TIME
STAMP.
USER INFORMATION: LOGICAL NAME = SE1
---------------------Assign master='modes-r1.master' should have been
Assign master='modes-r1.MASTER' (on linux you must specify the correct
uppercase and lowercase spelling.
The above SFM 478 is confusing and should indicate that the assigned file could
not be found and to look toward possible misspelling of the file name and/or
upper/lower case mismatch.
1-20218686
2005.5
Loads - Combining load cases with refere
nces to non-existant loads - Wrong answers
If a reference is made to a non-existant load the following warning message is
issued.
*** USER WARNING MESSAGE 3204 (SSG1)
UNABLE TO FIND SELECTED SET ( 16064) IN TABLE (SLT ) IN SUBROUTINE
(SSG1).
However, if an attempt is made to combine non-existant load cases with existing
load cases, wrong answer result.
Avoidance: Remove the reference to the non-existant load cases.
1-20220161
cision Loads
2005.5
Frequency Response - DPHASE - Single Pre
A SOL 108 run with DPHASE data generates loads in single precision on short
word machines. Loads should be generated with double precision accuracy.
This may lead to results that do not contain the fidelity expected by the user.
Avoidance:
1-20221811
2005.5
Distributed Memory Parallel Processing -
Acoustic with Akusmod input, DMP=1 - SFM 3007

When an Acoustics job (with Akusmod input) is submitted with dmp=1 the job
fails with the message:
SYSTEM FATAL MESSAGE 3007 (DISUTIL)
ILLEGAL INPUT TO SUBROUTINE DISUTIL
Avoidance: DMAP avoidance for SOL 111 version 2005.
compile read70 $
alter 'if ( nproc','endif $ nproc' $
if ( nproc>1 ) then $
disutil agg0,,,////3 $
else if ( procid>1 ) then $
delete /agg0,,,, $
disutil ,,,,/agg0///3 $
endif $
endif $
endalter $
1-20221988
2005.5
S - Missing Output in Punch File.
Nonlinear Analysis - CGAP, PUNCH, NLSTRES
If an NLSTRESS and STRESS output request is made in the same run, GAP FORCES
are not written to the PUNCH file.
Avoidance: Remove the NLSTRESS request form the output.
1-20222042
2005.5
Dynamic Response - PARAM,LFREQ, PARAM,SCR
SPEC - Response spectrum SPCFORCES are incorrect
Response Spectra analysis produces incorrect SPC forces when param,lfreq or the
MODESELECT command is used. All other results are correct.
compile postreig
alter 'sdr1' $
equivx qgh/phqg/-1 $
1-20240253
2005.5
Elements - CHEXA, TEMP(INIT) - Wrong Answ
ers for Temperature Dependent Materials
In a linear static thermal stress analysis with a temperature dependent
material wrong results may be generated if
- HEXA elements are present and a
- TEMP(INIT) Case Control Command is used
1. Use a TEMP(MATERIAL) or TEMP(BOTH) Case Control Command instead of
TEMP(INIT) and specify TREF on the material entry.
2. Setting NASTRAN SYSTEM(309)=1 also avoids the error and still allows the
usage of TEMP(INIT). But this second avoidonce should not be used for highly
skewed HEXA8.
1-20240331
2005.5
A SOL 200 optimization job with DRESP1 that references a missing GRID may fail
with SYSTEM FATAL MESSAGE 3062 instead of a USER FATAL MESSAGE that identifies
the missing GRID.
Avodiance: Use PARAM,SOLADJC,-1
1-20258966
ly
2005.5
Cyclic Symmetry - UFM 4319 on AIX 5.1 on
SOL 114, cyclic symmetry, jobs may fail in Version 2005 on IBM AIX 5.1 with
USER FATAL MESSAGE 4319.
Avoidance: Run on a different platform or use an earlier version.
1-20275134
2007.0.0
are not trapped
Case Control - MAXMIN - User input errors
When the following incorrect case control commands are used:

maxmin(def) disp
maxmin(def) stress quad4
maxmin=all
Nastran will fail without issuing a meaningful message.
1-20275644
2005.5
T - SFM 6352 (TDCINI)
Nonlinear Analysis - PCOMP, PARAM,COMPMAT
If a nonlinear analysis, SOL 106, contains a PCOMP entry with LAM="SYM"

specified in field 9 and parameter COMPMATT is set to "YES" or "NONSMEAR" the
analysis may fail with the message:
*** SYSTEM FATAL MESSAGE 6352 (TDCINI)
350.
USER ACTION: CONTACT MSC.SOFTWARE CLIENT SUPPORT.
PROGRAMMER INFORMATION: IPTR= 10916, ENDREC= 10900
PROGRAMMER INFORMATION: THE PARENT SUBROUTINE IS NLINIT
OR
MAIN:
MAIN:
MAIN:
MAIN:
MAIN:
"Access violation" (C0000005) exception encountered.

For reference, A(MAINAL) = 4012FE, A(/SYSTEM/) = 1FD0A00
A(/XNSTRN/) = 3DF0020
Exception occurred at address 00C35C86.
Program attempted to access data at location E346AA1C.
Avoidance:
Other than removing PARAM,COMPMATT, no avoidance exists.
1-20277571
2005.5
Frequency Response - NLRGAP - SFM 3001
in the DPD module in XRANDOM subDMAP
A SOL 108 deck with an unused NLRGAP entry in the input fails with SYSTEM FATAL
MESSAGE 3001 in the DPD module in the XRANDOM subDMAP.
Avoidance: Remove the unused NLRGAP entry.
1-20290197
2005.5
Enforced Motion - CBUSH - UFM 2170
The enforced motion example attached contains two CBUSH and two CONM2 elements.
It used to run in nastran 2005r1 but is failling during restart in 2005r2 with
the following message:
USER INFORMATION MESSAGE 7559 (FRRD1A)
THIS FREQUENCY RESPONSE ANALYSIS INVOLVES THE FOLLOWING TYPES OF EXCITATION -ENFORCED DISPLACEMENT USING SPC / SPCD DATA
USER FATAL MESSAGE 2170 (PARTN2)
BOTH THE ROW AND COLUMN PARTITIONING VECTORS ARE PURGED AND ONLY ONE MAY BE.
Avoidance: Insert the following DMAP alter into the restart run:
compile semfreq
alter 'freqdep='(,-1)
putsys(0,109) $
alter 'freqdep='
putsys(1,109) $
1-20375480
2005.5
pt,2 - Wrong Answers
Acoustic Analysis - MFLUID and param,vmo
Starting in V2004r3, PARAM,VMOPT,2 gives wrong answers.

compile mgen2a
alter 'mpyad phsa,phh'
equivx eh/lammat/-1 $
endalter
1-20375725
2005.5
- SFM 3007 (DOM9)
If a DVPREL2 (or DVCREL2 or DVMREL2) references more desvar id than there are
desvar entries and optimization is performed, a non-useful fatal message is
produced. This can also happen when the user calls out the same desvar id on a
dvprel2 entry more than once.
On windows, the job ends with:
MAIN:
A(/XNSTRN/) = 3BF0020
While on AIX the job ends with the message:
ILLEGAL INPUT TO SUBROUTINE DOM63
User Avoidance: Remove the duplicate reference to the same ID on the DVPREL2
entry or add dummy desvar entries to make the number of desvar's greater than
the maximum number of DESVAR's called out on a DVxREL2.
1-20425054
2008.0.0 (MD R3)
le SEP1X, Subroutine SEPMC2
Superelements - SECONCT - UFM 6782, Modu
If a nonexistent grid is identified on a SECONCT entry for a part SE model, the

Module SEP1X will issue the following message:
*** USER FATAL MESSAGE 6782 (SEPMC2)
THE FOLLOWING GRIDS OR SCALAR POINTS SPECIFIED ON SECONCT ENTRIES COULD
NOT BE LOCATED IN SUPERELEMENT 0

204
The module also identifies all other grids identified after the nonexistent
grid as being unlocatable.
1-20491407
2008.0.0 (MD R3)
979 (XYTRAN), Missing Output
Nonlinear Analysis - CBUSH, XYPLOT - UWM
In SOL 106, a request for xyplot output of cbush element forces results in no
data and the following warning message:
1503
-FORC- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA
BLOCK
106
1-20500621
e
2005.5
Elements - CPENTA, SDR2 - Poor Performanc
Large problems with large number of PENTA elements could experience significant
performance issues in SDR2 element data recovery.
Avoidance: The only avoidance is to use other elements or do not include the
PENTA's in the output set unless necessary.
1-20523074
2005.5
Elements - CGAP, TEMP(LOAD) - UFM 4016
Temperature loading is not supported for CGAP elements. If temperature loading

exists in a model with CGAP elements, NASTRAN incorrectly performs a check of
the nodal temperatures of the grids attached to the gap elements too. If
there is no temperature specified, Nastran terminates with USER FATAL MESSAGE
4016 (TA1ETD) indicating that there is no temperature data for the gap element.
1-20580861
2005.5
Incorrect Memory Management
Large Models - SSG1 - UFM 6827 (PLOAD4D),
If there is a large model with many grid points and elements, the job may fail
with an inappropriate USER FATAL MESSAGE 6827 indicating a problem with
geometry.
Avoidance: Increase 'mem' on the Nastran command.
1-20595728
ordinate system
Elements - CONM2 - Poor Message, UFM 2025 (EMG), Undefined co
If a conm2 entry references an undefined coordinate system UFM 2025 (EMG) is

output but the element(s) in error is not identified.
1-20609309
2005.5
Elements - PSHELL referencing MAT10 - No
connection between structure and fluid
If a PSHELL entry references a MAT10 entry, Nastran should issue a fatal
message that indicates that a shell element cannot reference fluid materials.
1-20622051
2005.5
work if LAM="SMEAR", Extra Output
Composites - PCOMP - PRTPCOMP=0 does not
PRTPCOMP=0 [same as SYSTEM(361)=0] should supress the printout of equivalent

PSHELLs and MAT2s for PCOMP entries. However, it does not work when
LAM="SMEAR" on the PCOMP record.

1-20632561
2005.5
Acoustics - RBE1, RBE2, RBAR, RBE3 etc.
- Wrong Answer if rigid elements attached to fluid dof
If a rigid element (RBE1, RBE2, RBAR, RTRPLT, RSPLINE, RBR3, etc) is connected
to a fluid degree of freedom, no message is given, and wrong answers occur. The
rigid element family was not intended for fluid degrees of freedom; a fatal
message should have been issued.
Avoidance: Use MPC equations for fluid constraints. Always refer to component
"1".
1-20647414
nt Exception
2005.5
Nonlinear Analysis - TEMPD - Floating Poi
A nonlinear analysis, which includes nonlinear heat transfer, may fail with a
floating point exception. The error has only been encountered on Windows and
was the result of a poor guess for TEMPD.
MAIN: For reference, A(MAINAL) = 401304, A(/SYSTEM/) = 21A4920
MAIN:
A(/XNSTRN/) = 3A00000
Avoidance:
Make a better guess on TEMPD for the initial temperature.
1-20748432
2008.0.0 (MD R3)
Elements - PBEAM entries with 2 identical
stations yields incorrect mass properties
PBEAM entries with two identical stations yields incorrect mass properties.
For example;
PBEAM
21001
+000001
+000002
+000003
+000004
+000005
+000006
NO
NO
NO
NO
NO
.5
1
.1282
.1282
.8718
.8718
1.
.5
47.1 21145. 21145.
42290.
+000001
47.1
28.2
28.2
47.1
47.1
42290.
25374.
25374.
42290.
42290.
+000002
+000003
+000004
+000005
+000006
21145.
12687.
12687.
21145.
21145.
21145.
12687.
12687.
21145.
21145.
gives the correct answer

Avoidance: Remove the duplicate station.
1-20752361
2008.0.0 (MD R3)
Optimization/Design Sensitivity - Poor Me
ssage, DRESP2 references a custom DRESP1 (MAX or RSS)
test deck in /nast/app/etl/fixed_qds/q1-20752361. GDC
If a DRESP2 entry uses Flag DRESP1 to reference a custom DRESP1 such as MAX or
RSS DRESP1, then the job will fail with USER FATAL MESSAGE 7147.
Avoidance: The message should be improved to direct the user to use Flag DRESP2
instead of DRESP1.
Hi David,
I remember I opened this quality to keep a record. It may as well be fixed.

Now I am assigning to your for further investionation. Thanks.
Shenghua
1-20780764
2005.5
sive Disk Space
External Superelements - EXTSEOUT - Exces
Solution 101 requires excessive disk space when reducing an external

superelement model to aset. The excessive disk space is required because the
RFA matrix is unnecessarily created.
Avoidance: Apply the folloiwng DMAP avoidance:
compile extout
alter 'call genrga'(,-1)
if ( sdrs<>1 ) then $
alter 'call genrga'
endif $ sdrs<>1
1-20798001
Message
2005.5
Elements - PBRSECT, PBMSECT, EMG - Fatal
If on the PBRSECT or PBMSECT entry a straignt segments, the job may fail in the
element generation routines in the EMG module.
Avodiance: Do not split a straight segement into multiple l segments.
1-20798063
2008.0.0 (MD R3)
Acoustics - IDENT, CP - UWM 6152, 6209
The IDENT, CP, and BW are 3 distinct fluid-structure interface methods. When
IDENT is used, the METHOD field (CP or BW) should be ignored. However, if CP
is entered on the METHOD field when the IDENT option is used, a default NORMAL
of -.001 is passed to the IDENT method. This will cause the job to fail with
UWM 6152 and 6209 stating that acoustic coupling matrix is not created for this
model.
Avoidance: Explicitly enter .001 for the NORMAL.
1-20805090
2005.5
ACMS - CAABSF - Wrong Answers
Nastran 2005r2 gives wrong answers when absorbers (CAABSF) are used together
with MDACMS. This error only occurs for models which contain frequency
dependent elements attached to fluid points. At this time only CAABSF elements
have this feature
compile fdrmgen
alter 'partn
mdotm,,vgfd',''
add5
rph,mdotm,,,/mdotm1 $
partn
mdotm1,,vgfd/,rgxfd,,/1 $
delete /mdotm1,,,, $
endalter
1-20868511
Documentation/IOG, QRG - SYSTEM(319) - Messages Documentation
System cell 319 provides a mechanism to allow users to print additional

information associated with warning, information and fatal message. The V2005
QRG contains a description of this system cell but it should also be included
in Section 6.6 of the IOG.

system(319)
keyword=XMSG
type=Integer
This is used by MSGAPIC.C to switch on/off
additional user/system information for messages output to the f06.
SYSTEM(319) = 0 (Default) Do not show extra information.
= 1 Show extra information. (Default=0)
1-20891501
2007.0.0
DMAP - SOLVE - Wrong Answers
The SOLVE module "invert" option (SYM=3) is broken. It only works for small
problems; if FBS has to do multiple passes, it will produce wrong answers for
the last pass.
Avoidance: Generate an identity matrix, and use the identity matrix as the
second input (rhs matrix). E.g.
paraml
matgen
solve
kaa//'trailer'/2/s,n,NCOL $
,/ident/1/NCOL $
KAA,ident,,,/KAAINV1/ $
1-20899028
ers
Acoustic Analysis - ACMODL, ALLSET=yes - possible wrong answ
John, Please attach a test deck that demonstrates the wrong answers. Thanks.
-- Joe Cole 3/20/2008
Joe, the files are available in 2 places
1. attached under the referenced SR 1208394401 (click on Service Requests
below, click on attachment, there is a zip file)
2. it is also available in /nast/app/etl/q1-20899028
Thanks,
John
In an acoustic analysis, if ALLSET is set to yes on the ACMODL entry, then the
results may be incorrect.
Avoidance: Remove ALLSET and use the default value.
1-20900111
2076
2005.5
Nonlinear Analysis - MATS1, TABLES1 - UFM
User fatal message 2076 may be encountered incorrectly if a model contains a

very large number of material entries that reference temperature dependent
tables.
TABLES1 BULK DATA ENTRY ID 52020,
WHICH IS REFERENCED BY MATS1 ENTRY ID48490980, IS INCORRECTLY DEFINED FOR
NONLINEAR ANALYSIS
1-20944681
2005.5
erating systems
Access - DEMO1 component fails on some op
The MSC.Access DEMO1 program has shown a FATAL traceback on some platforms and
operating systems. This error was due to libdbio dependencies not being in the
makefile. The Platforms affected are Linux64 and IRIX64.
1-20954421
2005.5
lead to Wrong Answers
MDACMS - F1 specified on EIGR/EIGRL may
For MDACMS, if F1 is specified on the selected EIGR or EIGRL entry, and if F1

is less than 1.0, and if there are eigenvalues between F1 and 1.0 Hertz, then
the eigenvalues in [F1,1.0] will be recovered twice.
Avoidance: Do not specify F1 less than 1.0 for ACMS.
1-20979791
2005.5
, PENAL- Incorrect dependent design variable constraints
The DOPTPRM parameter PENAL can be used to transform an infeasible design task
to a feasible one. If this is used with the DOT optimizer and there are
dependent design variables, the constraints on the first dependent design
variable as seen by DOT are incorrect. This error should not affect the
results unless the dependent design variable is close to or exceeding its
bounds.
Avoidance: Use the MSCADS optimization algorithm in place of DOT
1-21038768
2005.5
Nonlinear Analysis - RIGID=Lagrange Fails
in SOL 106 with SFM 4017 from NLCOMB
Lagrange rigid element RBE2 is not available for SOL106. If used the following
fatal message is encountered in the NLCOMB module
*** USER FATAL MESSAGE 4017 (NLCKDT)
ESTNL AND FILE (103) ARE NOT PROPERLY ALIGNED
ILLEGAL INPUT TO SUBROUTINE NLCKDT
In Version 2005R3 as documented in the QRG, the RIGID=LAGRANGE command will be
ignored in SOL 106 and RIGID=LINEAR will be used. Model ran to completion on
2004 without issuing any message.
Avoidance: A possible avoidance is to replace the RBE2 elements with stiff
CBEAM elements. Else use SOL 400 in MD Natran.
1-21115634
2005.5
LITTLEENDIAN - UFM 659 (IFP1PO)
Postprocessing - ASSIGN FORM=BIGENDIAN or
If a run has multiple subcases and multiple assign statements that specify a
non-native form of the output file, i.e. bigendian on a little endian machine
or littleendian on a bigendian machine, the job may fail. For example the
following input leads to the fatal message below:
ASSIGN output2 = '12_little.op2', UNIT = 12,form=bigendian
SOL 103
CEND
post patran tofile 12
SUBCASE 1
METHOD = 1
$ modes=5
disp(plot)=all
post displace tofile 61
SUBCASE 6
METHOD = 2
$ modes=10
stress(plot)=all
post stress tofile 62

*** USER FATAL MESSAGE 659 (IFP1PO)
THE FORTRAN LOGICAL UNIT REFERENCE NUMBER 61 ON THE ABOVE POST COMMAND
REFERENCES A FILE THAT HAS A
FORM=FORMATTED ATTRIBUTE. A PREVIOUS POST COMMAND SPECIFIES FILE UNIT 12
FOR FORMATTED OUTPUT.
THE POST COMMAND DOES NOT ALLOW A FILE UNIT CHANGE FOR FORM=FORMATTED
FILES.
1-21152384
(GP4RG)
Superelements - RIGID=LAGRANGE and TEMP(LOAD) - GP4, UFM 5289
A superelement model executing SOL 101 with a TEMP(LOAD) that specifies a

coefficient of thermal expansion, alpha, on the RBE2 entry and the case
control command RIGID=LAGRANGE or LGELIM fails in the GP4 module with the
following fatal message.
*** USER FATAL MESSAGE 5289 (GP4RG)
AN MPC OR RIGID ELEMENT BULK DATA ENTRY WITH DEPENDENT DEGREE-OF-FREEDOM
GRID ID =
0 AND COMPONENT = 1 CONTAINS
AN INDEPENDENT DEGREE-OF-FREEDOM --GRID ID =
101 AND COMPONENT = 1-THAT IS SPECIFIED MORE THAN ONCE.
Avoidance: Grids 0 and 101 are not specified on the RBE2 entries. Removal of
the RIGID case control command allows the input file to run as expected but
without the thermal expansion for the RBE2.
1-21221351
2005.5
Optimization/Design Sensitivity - temp(l
oad) and buckling response may have incorrect sensitivity
Sensitivity coefficenet for a SOL 200 job may be in error if the following
conditions are met.
a. has buckling eigenvalue as constraint
b. has temp(load) in static subcase
c. has 'PARAM,DSNOKD,1.0'
Aovoidance : attached following DMAP alter
compile response $
alter ' bdiag,budg,dkdgg,budg'(,-2),''(,-2) $
EMG
EST,CSTMS,MPTX,DIT,,ugb,ETT,
EDT,,,BGPDTS,GPSNTS,,,,,/
KDELMDg,KDDTDg,,,,/
1/0/0/-1/-1/-1/ 0 /-1//////1 $
1-21243388
- SFM 3001
2005.5
A SOL 200 job will fail with system fatal message 3001 if it has a DESVAR
command in the Case Control section referencing a SET ID to select design
variables and that SET covers all DESVAR entries in the input deck.
Avoidance : Either use DESVAR = ALL or remove DESVAR in case control
1-21249491
2005.5
Executive System - RESTART - SFM 1013
SYSTEM FATAL MESSAGE 1013 may occur in a restart if the solution sequence is
large enough to exceed an array size. For example, the index to FREDBD in
common block DBFREX is out of bound. That array is sized to 300, but in
OPNDBS, the FREPTR is calculated to be 303 (outside the array bounds).
Avoidance: Execute the job as a cold start.
1-21251041
2005.5
Transient Analysis - DDRMM,
RSEDR=NO - Missing Output for multiple subcases
SORT2, SPA
If PARAM,SPARSDR,NO is set, the second and subsequent subcases in a transient

analysis will not produce SORT2 output.
1-21289481
- LD_PRELOAD
2005.5
installation - linux - Missing Libraries
LD_PRELOAD was set on Linux systems in 2005.1. This setting may cause a
message in the log file about missing libraries.
Avoidance:
Replace the following line in $MSC_BASE/bin/nast20051.lcl and
$MSC_BASE/bin/nast20051.dmp:
%MSC_ARCH=linux:% export LD_PRELOAD
with
%MSC_ARCH=linux:%# export LD_PRELOAD
1-21298401
2005.5
mat not supported by DBC
Postprocessing - CQUADR/CTRIAR center for
The CQUADR/CTRIAR center format was not supported by DBC

1-21304451
2005.5
pendent failure
MPYAD - Arithmetic Exception - machine de
The MPYAD module may fail for large problems in which the first matrix has a
large number of rows and a small number of columns. This error only occurs
when a very large memory is specified.
Avoidance: Reduce the memory request.
1-21317981
2005.5
AUTOMSET - UFM 9163 (SEKR0)
Models that contain redundant, i.e over constrained, rigid elements will fail
with USER FATAL MESSAGE 9163 if PARAM,AUTOMSET,YES is specified.
An avoidance is available in the following DMAP alter:
compile sekr0
alter '9163', 'RETURN' $
message //' user'/wrn/'message 9163 (sekr0)' $
message //' The following mpc and/or rigid element '/
' equations are redundant and will be discarded ' $
matgpr bgpdts,uset1,,rax//'h'/'a' $
endalter
1-21318011
2005.5
AUTOMSET - Wrong Answers for Multiple BC
If PARAM,AUTOMSET,YES is specified for any job with multiple boundary

conditions (BC), results for the second and subsequent BCs will be wrong.
An avoidance is available via DMAP alter:
compile sekr0
alter 'DBSTATUS knn'(,-1)
delete /knn,,,, $
1-21345191
2005.5
Optimization/Design Sensitivity - FLUTTER
, Superelements - EOF on vtqu in dsfltf.
SOL 200 job with flutter response and design model covers more than one
upstream SE will fail in DSFLTF module with EOF on vtqu. This problem does not
affect SOL 200 job with residual only or design models that span only one
upstream SE.
Avodiance : use following alter to avoid the problem
ompile respsen,list $
alter 'lpflg=0' $
type parm,,i,n,lpflgcu $
lpflgcu=0 $
alter 'call flutsens','' $
IF ( DOFLUTDG>0 ) then $
lpflgcu = lpflgcu + 1 $
call flutsens,
KDICTDSF,KELMDSF,BGPDTS,SILS,CSTMS,KDICT,
KELM,DSPT1,MDICTDSF,MELMDSF,MDICT,MELM,EST,
MPTS,DIT,ett,GPSNTS,BDICTDSF,BELMDSF,
KDICTDSB,KELMDSB,MDICTDSB,MELMDSB,BDICTDSB,
BELMDSB,CASEM,EDT,PHDH,EMAP,CASEXX,SLT,
MAPS,USET,GOAT,GOAQ,GM,CASES,KHH,BHH,MHH,
QHHL,FLUTAB,R1TABR/
DELFL,VDKU,cdelk,cdelm,cdelb,dug,dvg/
LPFLGcu/DMRESD/SEID/RSONLY/CDIFX/NOPSLG/
IMAGE/shapeopt $
endif $
1-21368688
Documentation/Installation - MSC_LICENSE_DISCRETE - Mixed Mas
terkey and Concurrent Licenses
Beginning with version v2005r2, both MSC.Nastran and MSC.Patran incorporate the
new LAPI layer (v5.4.0) which introduces an additional environment variable,
MSC_LICENSE_DISCRETE. It is necessary to set this variable when mixing
Masterkey with concurrent license servers. This variable may be used to
manipulate the default license path behavior, essentially instructing LAPI to
reset the license search type between each server. The environment variable is
necessary so that by default queuing is not inadvertently affected in
homogeneous license installations. Subsequent releases of other MSC products,
once they include the LAPI update, will have MSC_LICENSE_DISCRETE available to
address the limitation as well.
1-21377192
2005.5
SFM 4276 EC 3021
When an optimization job includes DVPREL1 entries with a single DESVAR

entry and PMIN and PMAX is specified on some but not all of the DVPREL1s than
the job may fail with SYSTEM FATAL MESSAGE 4276 EC 3021 in the DOM9 module.
Avoidance:
1) Use ADSCOD = 1 on the DOPTPRM or
2) Either leave all PMIN/PMAX fields blank on the DVxREL1 entry and reference a
single DESVAR or add a non-zero number to all PMIN/PMAX fields of DVxREL1
entries.
1-21389158
2005.5
RTRPLT missing from xdb
Postprocessing - RTRPLT, PARAM,POST,0 -
RTRPLT information is missing from the XDB.

1-21431967
2005.5
Model Checkout - Singularities not identi
fied, UFM 9050 Not Issued on Windows PC
MSC.Nastran 2005r2 (version 2005.1.0) on Windows may fail to identify
singularities and not issue USER FATAL MESSAGE 9050. The analysis may procede
and issue very bad answers that contain rigid body motion.
Avoidance: The error has been corrected in Version 2005.1.2 (a.k.a 2005r2a).
Either run the problem in Version 2005.0.0 or get the latest release. The
updated 2005.1.2 Windows analysis.exe executable is available online at:
1-21462191
2005.5
tanium CD - RHEL 3.0 - Memory Error
SOL 600/Marc Executables - 2005R2 Linux/I
The SOL 600 marc executables on the MSC.Nastran 2005r2 Linux/ Itanium CD will
not work on Red Hat Enterprise Linux (RHEL) 3.0. They will work with RHEL 2.1
A Marc memory allocation error will appear in the log files when trying to run
a Nastran SOL 600 analysis using RHEL 3.0.
Avoidance: Download the file linux64_rhel3.tar.gz from MSC ftp site. This
zip file contains the SOL 600 marc
binaries for the RHEL 3.0 / Itanium platform.
1. unzip and untar the file in the
/msc/nastran/msc20051/marc
directory.
It will create a linux_rhel3 directory.

2. Rename the current linux64 directory to linux64_rhel2.
The Marc binaries in the current linux64 were valid for RHEL 2.1
3. Rename
linux64_rhel3 to linux64.
Now, the default Marc binaries are for RHEL 3.0

The problem with the wrong Marc executables for RHEL 3.0 / Itanium also applies
to the Nastran 2005 installation CDs. This zip file will be posted at the
following site.
1-21475421
2005.5
SEOUT - SFM 4276 (PACK), EC 105
Optimization/External Superelements - EXT
When a shape optimization job includes Part External SE, it will fail in DOPR2
at 2nd design cycle with the following error message:
SYSTEM FATAL MESSAGE 4276 (PACK)

ERROR CODE
105 PID= 0
Avoidance: Apply the following dmap alter.
compile desopt
alter 'desiter=desiter+1'
luset = luset0
1-21553341
2007.1.0
ith the traceback at SDR2
Elements - CBEND, TEMP(INIT) - SFM 4276 w
A model with a CBEND element that only defines the Initial Temperature for the
thermal load failed with SFM 4276 in the SDR2 module followed by a traceback.
Avoidance: Add TEMP(LOAD) command in the case control.
See attachment for the model.
Traceback:
Offset 0x00002a60 in procedure
2005.5
- SFM 6551in EXTOTMIN module
pthread_kill
_p_raise
raise
tracbak_
osexit_
nsexit_
pexit_
gperr_
ginit_
ginoa_
getemp_
sqr2d_
s2ebrd_
sdr2e_
sdr2d_
sdr2_
xsem13_
xsemdr_
nastmon_
mainal
Optimization/Design Sensitivty - EXTSEOUT
A SOL 200 job employing an external superelement created by using EXTSEOUT

with a DISP request fails with SYSTEM FATAL MESSAGE 6551 while reading the OP2
file in the EXTOTMIN module.
Avoidance: The same job runs successfully to completion if the external SE is
created without the DISP request.
1-21572991
5423
2005.5
Superelements - EXTSEOUT for fluid - SFM
If the EXTSESOUT command is used to create an external superelement with fluid

elements and fluid grid points exist on the boundary the assembly may
terminate in the MPYAD module with SFM 5423.

1-21602236
2005.5
UFM 3005 (FA1)
Aeroelastic Analysis - Flutter Analysis -
The PK and PKE flutter methods use an eigensolution which requires an

invertible mass matrix. This may lead to the following fatal message:
*** USER FATAL MESSAGE 3005 (FA1)
ATTEMPT TO OPERATE ON THE SINGULAR MATRIX MHH
1-21699761
IN SUBROUTINE PKINIT
Documentation/QRG - RSSCON, AUTOMSET - Wrong Answers
AutoMset is not compatible with RSSCON input and will lead to wrong answers.
This is a known limitation that must be documented.
Avoidance: Remove PARAM,AUTOMSET,YES.
1-21724661
Answers
2005.5
Enforced Motion - SPCD - UWM 4152, Wrong
If more than one degree of freedom is specified on a SPCD entry and USER
WARNING MESSAGE 4152 (G4SPCDR) is issued, wrong answers may result.
Avoidance: Only specify one dof on the SPCD entry.
1-21737131
2005.5
T - Wrong Answers / Missing Output
Distributed Memory Parallel/ACMS - FLSPOU
Incomplete FLSPOUT (Fluid/Structure Panel Participation) output is produced

when MDACMS is used with Distributed Memory Parallel (DMP).
verified with v2005.5.2 round 12 q1-21737131.dat 5/12/06 run. abb
There are two avoidances:
1. Run in serial; do not use DMP for MDACMS with FLSPOUT.
2. Employ the following DMAP alter:
compile freqrs
alter 'if ( acms and fdfreqr',''
if ( (acms or mdacms) and fdfreqr and nproc>1 and nfreqt>1 ) then $
endalter
1-21764817
2005.5
7 (DSABO) ILLEGAL INPUT TO SUBROUTINE DSAB1I
When an optimization job designs a temperature independent material property
while specifying temperature dependent material property entrIes, MATT9 or
MATT2, it will fail with the following error message: *** SYSTEM FATAL MESSAGE
3007 (DSABO)
Avoidance: Do not include MATT9 or MATT2 entry in the job. Use MATT1, MATT3 or
MATT5 instead.
1-21857794
2005.5
Acoustic Analysis - CHEXA, MAT10 - Incorr
ect complex acceleration and pressure
Acoustic analysis produces incorrect complex acceleration velocities and

pressure levels.
1-21857803
TA1
2005.5
Topology Optimization - PCOMP - UFM 2025
A topology optimization job with composite elements encounters a USER FATAL

MESSAGE 2025 in the TA1 module, stating that there is an UNDEFINED COORDINATE
SYSTEM ID = 3000002 even though a coordinate system with that id is present in
the input file.
Avoidance: Other than removing the composite elements, there is no avoidance.
1-21860501
2005.5
Restarts - PSD - Wrong Answers
The psd response calculated in a RESTART may be incorrect in Version 2005.1.

Avoidance: In the RESTART run apply the following DMAP alter:
ECHOOFF $
COMPILE SEMFREQ NOLIST $
ALTER 'IF ( NOUHF\<1','' $
IF ( NOT(NOPH2) AND EXTDR='NO' ) THEN $
ENDALTER $
ECHOON $
1-21869596
2005.5
- UFM 2025 (TA1), UWM
Topology Optimization - Multiple Subcases
If there are CQUADx/CTRIAx referencing MCID the job may fail with one of the
messages below:
3000002

CARD TYPE
ELEMENT
201 REFERENCES UNDEFINED PROPERTY ********
Avoidance:
Either use a single subcase or apply the following dmap alter:
compile predom
alter 'ta1
,,ec', ''
ta1
,,ect,ept,bgpdt,sil,,CSTM,,,/
estx,,,gpect,,,,,/
luset/-1/0/1/0/0 $
1-21892107
2005.5
SET Spill AREA HAS BEEN EXCEEDED.
Case Control - GPFORCE SFM 2362 (SETA2L)
The following Error message was issued in V2005.0 in a run with more than 1200
subcases and GPFORCE requests in each subcase.
*** SYSTEM FATAL MESSAGE 2362 (SETA2L)
SET Spill AREA HAS BEEN EXCEEDED.
USER ACTION: CALL MSC CLIENT SUPPORT.
MODULE IS UNABLE TO CONTINUE AND HAS BEEN TERMINATED DUE TO ERROR
MESSAGE PRINTED ABOVE OR BELOW THIS MESSAGE.

THIS ERROR OCCURRED IN CODE WHERE THE VARIABLE -NERROR- WAS SET = -99
Avoidance: Add a SUBCASE with a different set request for any GPF output.
1-21895337
2005.5
Optimization/Design Sensitivity - MAT9 Incorrect design sensitivity coefficients
Design sensitivity coefficients for MAT9 entries are incorrect.
1-21901601
M 4276 (FREAD)
2005.5
Aeroelastic Analysis - DMIG, AEPRESS - SF
If an aeroelastic analysis has an AEPRESS entry that references an undefined

DMIG entry than the job will fail with SFM 4276 in the FREAD module.
Avoidance: Correct the input.
1-21957121
2005.5
UFM 1126 (FNFIST)
Adams Integration - ADAMSMNF, AUTOQSET -
A SOL 103 run that combines param,autoqset with a ADAMSMNF FLEXBODY request
DMAP MODULE GP4
1-22012914
2005.1
.8664.exe Not Found
202 NAME = YG
Installation - nastran command - analysis
The nastran command delivered with the MSC.Nastran 2005r2a Windows cd will
attempt to find the non-existant analysis.8664.exe on em64t and opteron systems
running Windows XP64. When MSC.Nastran version 2005.1.2 is executed on a
Window XP64 system it fails to find the file, analysis.8664.exe, and the run
terminates. An updated delivery, MSC.Nastran 2005r2b, is available on the
internal ESD site and a copy will be made and sent on request.
Avoidance: Although the executable for the XP64 system is not currently
available, the 32 bit executable should run by using the EXE keyword to point
to the analysis.exe executable or renaming the analysis.exe to
analysis.8664.exe.
1-22013693
2005.5
Case Control - CMSENERGY - UFM 601
The CMSENERGY command must be abbreviated with 4 charachters, i.e. CMSE, else
the job will fail with USER FATAL MESSAGE 601.
1-22050590
2 (DOM9)
2005.5
An optimization job may fail in DOM9 with SYSTEM FATAL MESSAGE 3002 with and
"END OF FILE" error message if the following conditions are met:
1) Either DVCREL1 or DVMREL1 is present and it references more than one design
variable or it specifies non-zero PMIN/PMAX;
2) DVxREL2 is present (or is internally spawned by designed BEAM properties),
Avoidance:
1) Replace DVCREL1 or DVMREL1 with DVCREL2 or DVMREL2
or
2) Remove PMIN/PMAX from DVxREL1
1-22053652
utput
Transient Analysis - OTIME, GPFORCE - Missing Output, Extra O
OTIME in transient (direct or modal) does not work correctly for GPFORCE output
request. When fewer time steps than exist are specified, all timesteps are
output. If more time steps are specified than exist, gpforce results are
output for the first time step only.
1-22059227
2005.5
ent force output
Connector Elements - CWELD - Missing elem
If CWELD elements connect points defined using a local coordinate system, then
element force requests for the element will be ignored.
1-22063271
2005.5.1
ser Fatal Message, UFM 4508 (MTRXIN)
Miscellaneous - DMIG, DMIK - Inadequate U
The following user fatal message has been improved in Version 2005r3b to help
identify the grid and component that has been identified twice.
A GRID AND COMPONENT HAS BEEN SPECIFIED TWICE ON DMIK WKK
1-22099431
2005.5
POST,0 - Missing data in xdb
Dynamics - PARAM,AUTOQSET,YES and PARAM,
When PARAM,AUTOQSET,YES is used then any grid/scalar point results will be

incomplete on the xdb file. The following warning message will be
issued.
DATA BASE READ RELATION PROBLEM FOR EQEXING RETURN CODE =
0.

compile extduset
alter 'call augqset'
TYPE PARM,NDDL,I,N,CP,DBCPATH $
TYPE PARM,NDDL,CHAR8,Y,DBCCONV,DBCOVWRT $
TYPE PARM,NDDL,I,Y,GEOMU,LOADU,POSTU,DBCDIAG,POST $
if ( post=0
) DBC
BGPDTS,GPLS,GEOM1S,EQEXINS,,,,,,,,,,,,,,//
'BGPDT'/'GPL'/'GEOM1'/'EQEXIN'/////////////////
-1/DBCPATH/S,N,CP/'reig'/0/GEOMU/LOADU/
POSTU/DBCDIAG/DBCCONV/DBCOVWRT/0 $
endalter
1-22164401
2005.5
Connector Elements - CWELD elements with
PARTPAT option connect shell elements with wrong PSHELL IDs
If the shell element that includes the projection point GA or GB is connected
to several shell elements with different PSHELL IDs,
the CWELD elements with PARTPAT option may connect shell element with wrong
PSHELL IDs.
1-22166731
2005.5
, Insuffucient Memory in DSAB1J
Optimization/Design Sensitvity - SFM 3008
A large optimization job that has many designed elements may fail in DSAB1J
with a fatal error indicating insufficient memory.
Avodiance: The amount of memory required has likely been overestimated but
the only avoidance is to increases the memory.
1-22182521
Nonlinear Analysis - SOL 106 with Rigid Elements, RBE2, PARAM
,LGDISP,1 - Wrong Answers
SOL 106 with rigid elements such as RBE2 may give wrong answers when
PARAM,LGDISP,1 is included even if the structure exhibits linear behavior.
Avoidance:
Do not use rigid elements in SOL 106 with PARAM,LGIDSP,1
1-22194181
2005.5
Optimization/Design Sensitvity - Static S
uperelements may not utilize adjoint load method
Adjoint load method may not be utilized in Statics SOL 200 job with SEs. The
jobs will still run to the completion with correct results. The impact of this
problem is, if any, in the performace.
Avoidance: insert following alter
$
compile descon,list $
alter ' if ( doeigv\>0 )'(2,-1) $
IF ( APP='STATICS' ) THEN $
TCOLADJS = TCOLADJS + COLADJ $
IF ( TADJC<0 ) THEN $
GADJFLGS = 0 $
ELSE IF ( ADJFLG>0 AND GADJFLGS=0 ) THEN $
GADJFLGS = ADJFLG $
ENDIF $ TADJC<0
COLADJ = 0 $
TADJCS = TADJC $
ENDIF $ APP='STATICS'
$
1-22195429
2005.5
RSSCON, MPC - SMF 2104 (GP4)
Multipoint Constraints & Rigd Elements -
A SOL101 model with MPCs/SPOINTs and RSSCONs may fail with the message:
GRID OR SCALAR POINT ID= 300740 COMPONENT =
ENTRY IS ILLEGAL.
USER ACTION: CHECK MPC ENTRIES.
1-22266681
RGE1), Job Hangs
0 FOUND ON THE MPC
Distributed Memory Parallel - GDMODES, MDMODES - SFM 6144 (ME
GDMODES is not designed to support component mode reduction with external

superelements. If attempted the job will fail with SYTEM FATAL MESSAGE 6144
(MERGE1).
MDMODES should work but may hang.
Avoidance: Run without DMP.

1-22331531
YINFO module
2005.5
External Superelements - SFM 3200 in BDR

^^^ THERE ARE NO BOUNDARY GRID POINTS DEFINED FOR EXTERNAL SUPERELEMENT
CREATION.
^^^ USER ACTION: SPECIFY ASMBULK=MANQ OR CHECK ASETI, BSETI, CSETI, BNDFIXI,
AND BNDFREEI ENTRIES.
An external SE creation run with no T-set DOFs, but only Q-set DOFs, terminates
with SYSTEM FATAL MESSAGE 3200 (Logic Error 11) in the BDRYINFO module.
1-22398781
2005.5
DMAP - MATMOD option 47 - SFM 4276
If the input matrix to MATMOD option 47 is null then the module will fail with
Avoidance: Check for a null matrix using the PARAML module before executing
this option.
1-22403461
2007.0.0
rror Message 51, Subroutine DBCUGM
Aeroelastic Analysis - SWM 6065, DBCMSG E
In MSC.Nastran Version 2005.1, SOL 145 Flutter analysis fails to write to the
xdb file and generates the following message:
*** DBCMSG ERROR MESSAGE 51 FROM SUBROUTINE DBCUGM
MATRIX COLUMN CONSISTENCY CHECK FALUIRE; MATRIX
144 TABLE
210.
This prevents Patran users from plotting interpolated mode shapes on the
aerodynamic model.
The same input file runs correctly In version 2005.0.0.
1-22407911
2005.5
SOL 600 - NSTATE of NLAUTO entry is not
translated to .marc.dat file correctly with DYNAMIC
The value of the NSTATE field of NLAUTO is not translated to the .marc.dat
file in Transient Dynamic Analysis.
1-22408855
2008.0.0 (MD R3)
PBEAML, DVPREL1 - SFM 3007 (DOPR1)
When an optimization job designs either PBARL or PBEAML and the DVPREL1
references a non-existing PBARL or PBEAML entry, the job fails in DOPR1 with
SYSTEM FATAL MESSAGE 3007 with the following message: "Illegal Input to
Subroutine DOPR1C"
Avoidance: Do not reference non-existent entries.
1-22416502
Transient Analysis - Enforced Motion, SPCD, PARAM,MODACC,0
- SFM 3001 in MODACC
A SOL 112 deck with SPCD enforced motion and PARAM,MODACC,0 fails with SFM 3001
in MODACC module as indicated below.
*** SYSTEM FATAL MESSAGE 3001 (MODACC)

THE INPUT DATA BLOCK NAMED PDF0
AT POSITION
4 DOES NOT EXIST.
104 AND SUBROUTINE IS MODACC
0FATAL ERROR
1-22445937
2005.5
DGM2), Undefined Coordinate Cystem
Connector Elements - PFAST - UFM 2025 (MO
If a large number is used for the MCID that is referenced on the PFAST entry
the job may with USER FATAL MESSAGE 2025 being issued from the MODGM2 module
indicating an undefined coordinate system.
Avoidance:
User smaller ids for the coordinate system.
1-22461444
2005.5
uest - UFM 5423
Eigenvalue Analysis - MEFFMASS output req
An MEFFMASS request for an analysis that produces very large, very sparse
matrices by fail with USER FATAL MESSAGE 5423.
The model that experienced
this fatal message had a density on the order of 1.0e-6.
1-22502406
2005.5
INPUT TO SUBROUTINE MCFRAC
MCFRACTION - Fluids - SFM 3007 - ILLEGAL
If MCFRACTION is used for a model that includes fluid nodes, the modal
contribution output is missing, and the following error message is issued:
*** SYSTEM FATAL MESSAGE 3007 (MCFRAC)
ILLEGAL INPUT TO SUBROUTINE MCFRAC
Avoidance: Remove the MCFRACTION request.
1-22505311
Documentation/DMAP - RANDOM - Error in Equations
The following corrections should be made to the DMAP Dictionary equations for
the RANDOM Module:
Eqn 4-26 shoud have power 1/2 out side curley bracket.
Eqn 4-27 a) missing 1/2 power out side square bracket. b) denominator (w)dw
should be w Sj (w) (Sj missing).
Eqn 4-29 - Alpha and Beta are defined but never used anywhere.
1-22519011
2008.0.0 (MD R3)
Response Spectrum Analysis - FORCE, OP2,
PARAM,-1 - UWM 6286

In resposnse spectrum analysis, the following message may be issued when
param,post,-1 is set and FORCE output is requested.
*** USER WARNING MESSAGE 6286 (ZREAD)
THE NDDL DESCRIPTION OF DATA BLOCK=DOEF1 , RECORD=DATA
,DOES NOT HAVE
AN EITHER/OR TO MATCH OPT= 4.
ITEMS ARE ASSUMED TO BE UNDEFINED.
USER INFORMATION: PROBABLE CAUSE IS WRONG NDDL DESCRIPTION CODED, OR ,
WRONG GENERIC DATABLOCK USED (E.G. OES INSTEAD OF OEF).
Avoidance: The user warning message should be ignored.
1-22539420
2005.5
Postprocessing - PARAM,POST,0, DBC - Mis
sing Output in xdb, SWM 6065 DBCMSG 14
SOL106 restarts using 'PARAM,POST,0' produces an .xdb file that is missing
output. The f6 output contains the following warning messages:
In the run that produces .xdb nastran gives this SYSTM WARNING MESSAGE,
RETURN CODE =
RETURN CODE =
1.
1
Avoidance:
There is no avoidance for the xdb file other than running a cold
start. Restarts with PARAM,POST,-1 produce a complete op2 file.
1-22555556
2005.5
Optimization/Design Sensitivity - Designi
ng ZOFFS on CQUADR and CTRIAR - UFM 7193
If an optimization job designs ZOFFS of a CQUADR or CTRIAR, the job fails
with USER FATAL MESSAGE 7193.
Avodiance: Use CQUAD4 or CTRIA3 to design ZOFFS.
1-22611621
2005.5
H, K4AAX - UFM 4353 (MTRXIN)
External Superelements - AUTOQSET, DMIGPC
Creating an external superelement (SOL 103, DMIGPCH option) using 'PARAM,

AUTOQSET, YES' produces an unsymmetric K4AAX matrix. The following assembly
(SOL 111) run then fails with the message:
DMIG MATRICES SELECTED BY K2GG, M2GG, B2GG OR K42GG DO NOT HAVE SYMMETRIC
FORM (IFO=6).
Running the job with SPOINT and QSET1 entries instead of PARAM AUTOQSET
produces a symmetric K4AAX matrix and the assembly run works fine.
Avoidance:
compile phase1b
alter 'UMERGE1 uset,k4QQ,k4TQ'
modtrl k4aa////6 $
alter 'UMERGE1 uset,bQQ,bTQ'

modtrl baa////6 $
endalter
1-22614794
2007.0.0
UFM 2101 and SFM 6143
Dynamics - PARAM,AUTOMSET and AUTOQSET -
Input decks that combine AUTOQSET and AUTOMSET may fail with
GRID POINT
...
GRID POINT
UM
UB
UM
UB
*** SYSTEM FATAL MESSAGE 6143 (UMRGE1)

SPECIFICALLY:
The number of columns in KNN is not equal to the size of the COMP-set
The number of rows
in KNN is not equal to the size of the COMP-set
KNN
: Rows=
17136 by Cols=
17136
Set sizes: Major (N-set)=
17196
Set0 (COMP-set)=
17148
Set1 (Q-set)=
48
Avoidance: The fatal exit can be avoided by either replacing AUTOMSET by UM
feature or replacing AUTOQSET by SPOINT, QSET1 or by applying the following
alter:
compile findm
alter 'call zmce1' $
call dbstore zgpart,,,,//0/0/'
'/0 $
zuzri1=newmsize $
compile augqset
alter 'gp4 ',''
GP4
CASE,GEOM4,eqexin,SIL,GPDT,BGPDT,CSTM,,,,,,,,/
RMG,Yg1,USET0,/
LUSET/S,N,NOMSET/0/S,N,NOSSET/0/S,N,NORSET/
nskip/0/0/0/0/SEID//sebulk/automset $
alter 'PARAML USET1'(,-1)
call dbfetch /zgpart,,,,/0/0/0/0/0 $
umerge uset1,zgpart,/gparq/'g'//'q' $
MODUSET GPARq,USET1/tUSET/'NEWMSET'////zuzri1 $
equivx tuset/uset1/-1 $
ENDALTER
1-22618721
2005.5
Distrubuted Memory Parallel - DMP, PARAM
OUGCORD BASIC - Missing Results in op2 file
Distributed memory parallel jobs that use PARAM,OUGCORD,BASIC will only have
partial results output to the op2 file.
Avoidance:
compile sedrcvr
alter 'OUTPUT2.*OUGV1PAT'(,-1)
if ( disofp and not(acms) ) then $
$ distributed and high level parallel
IF ( procid<>1 ) THEN $
disofps ougv1pat,,,,,,, $
ELSE $
disofpm ougv1pat,,,,,,,/
ougv1ptt,,,,,,,/
mpibuff $
equivx
ougv1ptt/ougv1pat/-1 $
ENDIF $ procid<>1
ndisofp=ndisofp+1 $
endif $ disofp
1-22653481
2005.5
lid in Version 2004 & 2005
Adams Integration - param,cmsortho not va
The nastran/adams interface in Version 70.7 and 2001 had a param,cmsorthono

option. This option was removed in Version 2004.
1-22716666
2007.0.0
_SNMP=1 missing from nast20051.rcf
Installation - Windows Only, symbol=LM_NO
The symbol=LM_NO_SNMP=1 missing from the nast20051.rcf. This may cause

problems with the flexlm licensing on older Windows operating systems.
1-22716859
2005.5
MDACMS
- EIGRL, ND - Extra Eigenvalues
MDACMS ignores ND on the EIGRL entry and will output more eigenvalues than
specified by ND.
Version 2005R3 will issue a warning message that ND is
ignored.
1-22717058
bort
2008.0.0 (MD R3)
Buckling Analysis - EIGRL - SOL 105 may a
In rare cases buckling problems may abort.

Avoidance: This issue may be avoided by specifying a shift scale of 0.1 in the
8th field of the EIGRL entry.
1-22732561
2005.5
___' - Access violation
DMAP - PARAML Options 'VERS___' or 'COMP_
The VER__ and COMP___ options of the PARAML module may fail with an access
violation on some operating systems; e.g., Linux RedHat 9 and Windows.
1-22832921
2005.5
QR set is not parsed correctly
Aeroelastic Analysis - TRIM entry with AE
If a TRIM entry contains an AEQR value that is a real number 0 < AEQR <= 1.0
and one or both of the label fields on the parent TRIM entry are blank, the
AEQR value will be reset to 0.0 with the result that there is no aeroelastic
feedback.
Avoidance: If AEQR=1.0 is desired, leaving the AEQR field blank will result in
the default of AEQR=1.0 being used. It some value other than 1.0 is desired,
the only avoidance is to create dummy aerodynamic extra points (AESTAT or

AEPARM) and constrain them to 0.0 on the TRIM entry so that there are no blank
label fields on the parent.
1-22840061
2005.5
External Superelements - EXTSEOUT - OUTP
UT2, SFM 6551 (INPTX2), AN END-OF-FILE WAS DETECTED
If element forces are requested in the external component reduction run using
EXTSEOUT and the DMIGOP2 option, the datablock IEF1O may be erroneously
identified (in the XSOP2DIR record) as one of the datablocks that are to be
written to the op2 file. This will cause SFM 6551 in the assembly run that
tries to read the op2 file when the datablock MEF1O was not written to the op2
file.
SYSTEM FATAL MESSAGE 6551 (INPTX2), AN END-OF-FILE WAS DETECTED
Avoidance:
ECHOOFF $
COMPILE EXTOUT NOLIST $
ALTER 'XNAME = \'MEF1O'(,-1),'' $
IF ( NOIEF1o>0 ) THEN $
ENDALTER $
ECHOON $
1-22850801
k in dop1x6
2005.5
Topology Optimization - TOPVAR - Tracebac
Topology optimization jobs with symmetric constraints specified on the TOPVAR

entry may fail with a traceback in dop1x6.
1-22912575
2005.5
s run with MDACMS and DMP may hang
Distributed Memory Parallel - Large model
Large models that are executed with a large memory request that use MDACMS and
DMP may hang.
The matrix partition process (module PRESOL) may attempt to acquire extra
(dynamic) memory it needs to partition the model. If there is insufficient
memory available on the system to complete the memory allocation successfully,
the DMP Slave process may hang.
Avoidance: There are two possible workarounds:
1. Reduce the amount of memory given to Nastran with the "mem=" command line
option. For most models, "mem=1gb" should be sufficient.
2. Increase the amount of memory given to Nastran.
Option (1) is preferable, since the amount of extra memory may be much more
than is truly needed to solve the problem.
For option (1), there must be sufficient memory available on the system to
satisfy the request. Exercise this option on a lightly loaded system.
1-22916281
2005.5
EDU- SFM 3007, MATREDU
Aeroelastic Analysis/Rotordynamics - MATR
Rotordynamics problems may fail in SOL 146 (aeroelastic analysis) in the

GENGYRO subDMAP with SFM 3007 from the MATREDU module.

1-22941687
GPFORCE - Missing output when model contains CFASTs exist for
both "PROP" and "ELEM" types
GPFORCE output for CFAST elements defined using the "ELEM" option (field 4) is
missing if the model contains CFASTs defined with both the "PROP" and "ELEM"
types. If the model contains only one type (i.e. all "PROP" or all "ELEM")
then the GPFORCE output lists the CFAST contributions.
In the case of the mixed
specify which element is
identify the element ID.
lines of output PER GRID
PROP/ELEM model, UIM 2351 is issued, but it does not

being ignored (only says "FASTP" ) nor does it
It also may lead to excessive output as it produces 3
involved in the fastener.
*** USER INFORMATION MESSAGE 2351 (GPFDFA)

A FORCE CONTRIBUTION DUE TO ELEMENT TYPE = FASTP , ON POINT ID =
101
WILL NOT APPEAR IN THE GRID-POINT-FORCE-BALANCE SUMMARY.
1-22955943
2005.5
ide by Zero, UFM 4658 (NHEXD)
Nonlinear Analysis - NLITER, CGAP - Div
A nonlinear analysis with CGAP entries and large displacement may encounter a
divide by zero or
*** USER FATAL MESSAGE 4658 (NHEXD)
DIFFICULT GEOMETRY PREVENTS FURTHER COMPUTATIONS FOR ELEMENT WITH ID =916
User information:
Difficult geometry for solid elements occurs when faces have zero
areas, or when Jacobians at integration points do not all have the
same sign, which signifies that the edges are crossed. In geometric
nonlinear analysis, tests are made for initial and deformed geometry.
Elements should be modeled such that their faces are as nearly equilateral
as possible and midside nodes should be positioned close to the center
of their edges.
1-23000557
2005.5
Acoustic Analysis - PARAM,AKMPOST and GRI
DMP keyword on FLSPOUT command - Wrong Answers
If PARAM,AKMPOST,YES is specified and PANELs are present and the GRIDMP keyword
is specified on the FLSPOUT command then the results written to Fortran unit 90
will be incorrect.
Avoidance: Remove the GRIDMP keyword from the FLSPOUT command or insert the
compile akmpost
alter 'numfgrid'(2)
PARAML mpfmap//'TRAILER'/6/S,N,numgrdmp $
alter 'rowmap = rowmap + 1'(4),''
rowmap = rowmap + 1 + numgrdmp $
endalter
1-23040291
2005.5
SOL 600 - ISTRESS - Initial Stress Entry
is not Translated Correctly for solid elements
The initial stress entry "ISTRESS" for SOL 600 will be translated to "INIT
STRESS" of Marc. Unfortunately, it is not translated correctly.
1-23061191
2005.5
SOL 600 - Stress free initial contact of
BCTABLE not translated correctly - Wrong Answers
Stress free initial contact of BCTABLE is not translated correctly into
marc.dat file in Nastran 2005r2 SOL 600.
If multiple contact pairs are defined and stress free initial contact
definition is not same for them in BCTABLE, this happens.
For example:
Nastran input deck:
BCTABLE 0
SLAVE 2
0
MASTERS 1
SLAVE 3
0
MASTERS 2
0.
1
2
0.
0
0.
0.
0.
0.
0
0.
0
0.
0.
0.
Marc input deck translated by SOL 600:

CONTACT TABLE
2,
2, 0.000000E+00, 0.000000E+00, 0.000000E+00, 0.000000E+00,
0.000000E+00, 1, 0, 1, 0,
1,
3, 0.000000E+00, 0.000000E+00, 0.000000E+00, 0.000000E+00,
0.000000E+00, 2, 0, 1, 0,
2,
Marc correct input deck
CONTACT TABLE
2,
2, 0.000000E+00, 0.000000E+00, 0.000000E+00, 0.000000E+00,
0.000000E+00, 1, 0, 1, 0,
1,
3, 0.000000E+00, 0.000000E+00, 0.000000E+00, 0.000000E+00,
0.000000E+00, 2, 0, 0, 0,
2,
1-23086666
2005.5
ARAM,INREL,-2 - SFM 3001
Transient Analysis - IC(STATSUB) with P
In SOL 109, direct transient analysis, if IC(STATSUB) references a subcase with

PARAM,INREL,-2 , the job will fail with the message:
*** SYSTEM FATAL MESSAGE 3001 (TRNSP)
1 DOES NOT EXIST.
Avoidance: This error does not occur in SOL 112.

compile sedtran
dynamic ,GPLS
CASES ,EQEXINS
BGPDTS ,CSTMS
lll
,kll
EMAP
,XYCDB
KFS
,KSS
,GOT
,SILS
,MATPOOL
,EST
,ull
,MAPS
,KSF
,KAA
,SLT
,GM
,MPTS
,
,ETT
,EDT
Apply the following dmap:
,DYNAMICS,
,dar
,
,DIT
,
,XYCDBS ,
,PCDB
,
,PVTS
,
,EDOM
,
GEOM2S
INDTA
FORCE
SPSEL
PA
PL
KGG
K4GG
MRR
MR
MAR
,GEOM3S ,POSTCDB ,ECTS

,EPTS
,
,KELM
,KDICT ,GPECT ,VELEM ,
,casers ,SCSTM ,matpools,ditid ,
,
,PJ
,PTELEM ,PG
,
,YS
,qr
,UOO
,PSS
,
,
,gpsnts ,
,KJJ
,
,edts
,LOO
,BJJ
,BGG
,
,MJJ
,
,MLR
,MLL
,
,
,GOQ
,
,
,MAA
,
,MEA
,BAA
,K4AA
,MGG
,
,
,
,
,GEOM4S ,
VGFS
,PCDBS ,ESTL
,ESTNL ,AGG
,
DMIs
,DMINDXs ,DTIs
,DTINDXs ,CONTACT ,
btopo ,GPDTS ,MELM
,MDICT ,GEOM1 ,
,MPT
,
SLIST ,KMG
,MMG
,MSF
,BMG
,
BSF
,K4MG
,K4SF
,
,pvt
,
oint
,deqatn ,deqind ,medge ,gdntab ,
pelsets ,viewtb ,bgpdtvu ,orseq ,
,
vgfd
,eht
,geom1s ,pvtbc ,
,
,
,
,
,vgq
,
,
,
,mmcdb ,
,
,
,
,
,axic
,
,
,
,
,
,
epsseo ,drg
,mphvz ,bk4zz ,pcompts ,
pval
,elemvol ,pmyg
,pbyg
,pkyg
,
mss
,bss
,k4ss
,belm
,bdict ,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,xsop2dir,rvg
,
geom1qx ,cee
,mee
,gge
,bec
,
mec
,cmlama1 ,ajp
,gei
,pvt0
,
kay
,bay
,may
,k4ay
,goy
,
yg
,phba
,aaa
,aay
,asf
,
pggrv ,
,
,
,
,
,ym
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
/
s,APP /DMAPNO /S,RSONLY/SOLTYP /FALSE /
s,nloop /S,LASTSEID/S,PFILE/S,LUSETS/S,FSCOUP/
enfmeth /AUTOSPC /S,NOPH2 /FALSE /s,pvalid/
s,pexist/false /s,kdiff /'
' /0
/
0
/0
/0.0
/s,noph1 /s,adptindx /
false /'no ' /'no ' $
1-23097181
2005.5
Optimization/Design Sensitivity - DESSUB,
DFREQ, MFREQ, DSAD - Fatal Message, Wrong Answers
If a frequency response (ANALYSIS=DFREQ or MFREQ) with multiple subcases is
submitted with the first frequency response subcase lacking a dessub request,
the job can fail with system fatal messages in the dsad module or it can
complete with wrong answers for the design responses and sensitivities.
Avoidance: Remove the subcase that lacks a DESSUB command or place this
subcase after a frequency response subcase that does have a dessub request.
1-23105401
2008.0.0 (MD R3)
nditions - No error/warning message
Transient Response - Multiple boundary co
Multiple boundary conditions are not allowed in direct transient response--SOL

109. If multiple boundary conditions are defined in this SOL, only the first
boundary condition will be used for all subcases and no fatal or warning
messages will be issued.
Avoidance: None.
1-23113802
2005.5
tiple subcases - SFM 6912
Buckling - multiple superelements and mul
A linear buckling solution with more than one superelement and more than one
buckling subcase may fail with the following message issued by the SEDR module:
*** SYSTEM FATAL MESSAGE 6912 (SEDRML)
THE BASIC GRID POINT DEFINITION TABLE NAMED BGPDTS AND THE DISPLACEMENT
MATRIX NAMED BUG
FOR SUPERELEMENT
20 ARE INCONSISTENT.
USER ACTION: IF THIS IS AN EXTERNAL SUPERELEMENT DATA RECOVERY, ENSURE
THAT THE BGPDTS TABLE
AND NOT THE EQEXINS TABLE IS DBLOCATE'D.
PROGRAMMER INFORMATION: THE NUMBER OF DEGREES OF FREEDOM IN THE BASIC
GRID POINT DEFINITION TABLE IS
36.
THE NUMBER OF DEGREES OF FREEDOM IN THE
DISPLACEMENT MATRIX IS
60.
Avoidance: Use the following DMAP alter.
compile super3
alter 'ugb',''
DBVIEW UGb=UG WHERE ((
(seid=np2 and seid>0 and peid>0 and spc=* and mpc=* and
(seid=np2 and seid=0 and peid=0 and spc=cspc and mpc=cmpc and
mtemp=cmtemp)
)) $
1-23128147
2005.5
Optimization/Design Sensitivity - Buckli
ng with external superelements - UWM 6911, Wrong Answers
If buckling sensitivity analysis with superelements is performed with multiple
subcases UWM 6911 (as shown below) is issued indicating there are multiple
copies of a requested datablock. This may lead to wrong answers.
*** SYSTEM WARNING MESSAGE 6911 (QCBFIN)
THE DBVIEW HAS YIELDED MORE THAN ONE DATA BLOCK BUG
.
THE PROGRAM WILL SELECT THE "FIRST" DATA BLOCK FOUND.
PROGRAMMER ACTION: TO FIND THE DUPLICATES, SPECIFY THE WHERE CLAUSE FROM
THE DBVIEW STATEMENT ON THE DBDICT STATEMENT
AND THEN MODIFY THE WHERE CLAUSE ON THE DBVIEW
STATEMENT TO REMOVE THE DUPLICATES.
Avoidance: External superelements can be replaced with DMIGPCH and K2GG instead
of DMIGOP2. This avoids the SE processing. Else the following dmap alter may
be used:
:
compile respsen
alter 'dbview bugx=bug',''
dbview bugx=bug
where (seid=temp and wildcard) $
1-23153166
Submittal - acct=yes - Accounting Program Error, mscact.c goe
s into an infinite loop
An incomplete f04 file that contains only 2-3 columns of data in the last line
may cause the accounting program to go into an infinite loop in the strtok
function.
1-23241691
Superelements/Buckling - EXTSE - SFM 6551 (INPUTT2), during
upstream buckling data recovery
Beginning in Version 2005r3, a SOL 105 job with part external superelements may
fail with the message below during buckling eigenvector data recovery for
upstream superelements.
SYSTEM FATAL MESSAGE 6551 (IINPUTT2) module in subDMAP EXTOTMIN
1-23241901
2005.5
o an illegal dof
Large Models - GP4 - SFM 2101 pointing t
A large model, more than 3 million dof, failed in GP4 with SFM 2101 indicating
that an illegal degree of freedom existed on an mpc entry.
.
GRID OR SCALAR POINT ID= 16700047 COMPONENT =
2 FOUND ON THE MPC
ENTRY IS ILLEGAL.
USER ACTION: CHECK MPC ENTRIES.
0FATAL ERROR
1-23267428
2005.5
ting Point Overflow
Aeroelastic Analysis - GI, SPLINEi - Floa
A floating point exception can occur due to an attempt to divide by zero when
processing aerodynamic spline input.
Avoidance: The problem may be avoided by running on a different platform.
The only other avoidance is to use a release prior to Version 2005.1.
There is no avoidancethere is not avoidance other than to use a different
platform (linux seems to work okay) or to use a version of Nastran earlier than
2005.1
1-23313501
2005.5.2
SFM 5423 in subsequent assembly run
External Superelements - SPCF, EXTOUT -
In Version 2005.1, an SPCF request in an external SE creation run results in

failure with SYSTEM FATAL MESSAGE 5423 in a subsequent assembly run. In
previous versions, the job ran, but resulted in incorrect SPCF results for
interior points of the external SE.
This error has been corrected in MSC.Nastran 2005.5.1 and MD Nastran 2006.0.1
Avoidance: Employ the following alters:

compile extout
alter 'extunit','' $
type parm,nddl,i,y,extunit,spdrrat $
alter 'outprt','' $
outprt casex,ects,bgpdts,sils,xycdbs,,,,,,,,,,,edts,/
v01dr0,vspcg,vmpcg,junk,/
s,n,sdrs/0/'sparse'/spdrrat $
dbstatus vspcg//s,n,novspcg $
if ( novspcg>0 ) then $
upartn uset,vspcg/vspc,,,/'g'/'s'//1 $
paraml vspc//'trailer'/5/s,n,nzspc $
CALL CFORCE1 MSF,,,,BSF,,,,KSF,K4SF,,
,,,,,,,,vspc,uset/
MSF1x,BSF1x,KSF1x,,,,vscg/
'reig '/'reig '/'spcforce' $
endif $ novspcg>0
call xAdd5 vscg,v01dr0,,,/v01s0/cu/cu/cz/cz/cz $
diagonal v01s0/v01s/'whole'/0. $
paraml
v01s//'trai'/6/s,n,dens//s,n,nov01s $
$ if it's full (sdrs=0) then leave it full
if ( sdrs<>0 ) then $
if ( nov01s<0 ) then $
sdrs =1 $ none
else if ( dens/100<spdrrat ) then $
sdrs=-1 $ sparse
else $
sdrs= 0 $ full
endif $ nov01s<0
endif $ sdrs<>0
alter 'call xadd5','' $
alter 'nouoo','nouoo'(1,1) $
paraml uoo//'null'////s,n,nulluoo $
if ( nulluoo>-1 ) then $
alter 'sdr2'(2),'' $
if ( nosset>-1 ) then $
upartn uset,ugo/ufo,,,/'g'/'f'//1 $
CALL CFORCE USET,,ufo,,MSF,,BSF,,KSF,K4SF,,,,cmlama,,/
QGo/
'reig '/'reig '/'spcforce'/false/false $
endif $ nosset>-1
SDR2
CASEx,CSTMS,MPTS,DIT,EQEXINS,,ETT,nulllama,BGPDTS,,qgo,
alter 'nouoo'(3),'' $
endif $ nulluoo>-1
1-23354553
2005.5
SET 2 = AERO1 Fails
QRG/Aeroelastic Analysis - Plotting with
In aeroelastic analysis, the plotting of the AERO1 elements are no longer

available from the PLOT module using SOL 145 or 146. The Quick Reference Guide
SET description Remark 1 needs to be updated to reflect this If AERO1 is used
then the program issues the message:
ERROR MESSAGES FROM THE PLOT SET DEFINITION MODULE (PLTSET)
AERO1
ELEMENTS CANNOT BE PLOTTED BY THE STRUCTURAL PLOTTER
Avoidance: Use Patran with PARAM,OPPHIPA,0 and PARAM,POST,0 and request

displacement output. Create a new patran db and access both (model and
results) from the xdb file.
1-23474784
2006 (MD R1)
Optimization/Design Sensitivity - Multip
le types of MATTi entries leads to SFM 3003 (EMG)
When an optimization job includes more than one type of MATTi entries, or
temperature Dependent Material propertiy entries, the job may fail in EMG at
design sensitivity phase as follow:
*** SYSTEM FATAL MESSAGE 3003 (EMG)
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK MPTX
(FILE 103) IN SUBROUTINE PREMAT
Avoidance: Include only a single type of MATTi entry in an optimization job.
1-23481533
2007.0.0
- SFM 4276, EC 3001 (gread) - DOPR1
When an optimization job includes a DESVAR command that selects all the DESVAR
entries and also includes DLINK entries, the job may fail in DOPR1 with
SFM4276/3001.
Avoidance: Use DESVAR = ALL or remove DESVAR command.
1-23482561
2005.5
1 - Incorrect LTLEND/BIGEND format
File Management Section - ASSIGN, OUGPSD
If the LTLEND describer is used on the ASSIGN statement to write a

little-endian format op2 file on a big-endian machine in a random response
analysis, the OUGPSD1 datablock will have the first 3 words of the case control
record written in big-endian order.
The error is caused because OUTPX2 did not properly detect that there is no
valid NDDL description for OUGPSD1 and other datablocks for the same OUTPUT2
DMAP statement. Just as for FORM=FORMATTED (neutral format), OUTPX2 shoud
issue a UIM and skip the data block. The same problem would affect INPUTT2.
1-23494381
2005.5
999 HAS OCCURRED IN ROUTINE alxa2
Matrix Methods - ADD5 - BIOMSG: ERROR
The following error occurs in the ADD5 module when scaling a matrix when the
input datablock is from a database with a smaller buffsize.
BIOMSG: ERROR
1-23504486
error
999 HAS OCCURRED IN ROUTINE alxa2

2008.0.0 (MD R3)
Documentation/QRG - PBEAML entry for DBOX
The figure for PBEAML type DBOX in the QRG has a typo. What is shown as DIM12
should be DIM2.
1-23509651
2005.5.2
Elements - GPSTRAIN - Wrong Answers
The GPSTRAIN ouptut "PRINCIPAL STRAINS AT GRID POINTS" is wrong for all solid
elements (CHEXA, CPENTA, CTETRA). The Von Mises and Max Shear strain output is
incorrect for shell elements.
Avoidance:
There is no avoidance other than to use the element strain
output. The error is corrected in MD Nastran 2006r1.
1-23548203
2005.5
3 - Contact Model, Access Violation
SOL 600 - CQUAD4, CHEXA, CBEAM, RBE2, RBE
A contact model with CQUAD4, CHEXA, CBEAM, RBE2 and RBE3 elements fails during
processing the input file with an Access Violation.
1-23573231
2005.5
Optimization/Design Sensitivity - Uniquen
ess on DRESP2 IDs in SOL 200 is not checked
Uniqueness of DRESP2 IDs in SOL 200 jobs is not checked for MSC.Nastran v2005
onwards. The last verion that the check is performed is v2004r2. Users must
manualy make sure there is no duplication on DRESP2 IDs. If duplication on
DRESP2 IDs exists and the ID is selected as a constraint or objective, the
optimization results may be based on the unintended constraints.
Avoidance - There is no avoidance.
1-23623711
2005.5
7 (DSFLTF), Misleading message
If a design response is associated with a complex eigenvalue (RTYPE = FLUTTER

or CEIG) and the eigenvalue is 0.0,0.0, the following message is produced:
ILLEGAL INPUT TO SUBROUTINE DSFLTF
Avoidance: Determine and remove the cause of the zero eigenvalue.
A UFM message such as the following needs to be added:
The sensitivity of a complex eigenvalue that is exactly zero (0.0,0.0) is
being requested. The sensitivity algorithm does not permit this and indicates
a problem with the underlying analysis or the prescribed design task.
User Avoidance: Determine the cause of the zero eigenvalue and remove it.
1-23825097
2005.5.2
train Energy with DMIGs/K2GG
Elements - ESE - Wrong Answer for Total S
The values reported for the TOTAL and all elements in set ESE are wrong if
there is more than one subcase and K2GG / DMIGs are present. Jobs with a
single subcase work correctly.
The value reported for TOTAL STRAIN ENERGY in the 1st subcase apparently sums
in the DMIG STRAIN ENERGRY contributions from ALL subcases, the remaining
subcases include zero STRAIN ENERGRY contribution from the DMIGs.
1-23956243
2007.1.0
MESSAGE 7635 (MDG2ED)
Fastener Elements - CFAST *** USER FATAL
Models with CFAST elements may fail inexplicably with the following message:
*** USER FATAL MESSAGE 7635 (MDG2ED)
FOR CFAST ELEMENT ID= 177459, WITH FORM=ELEM OR PROP
, THE SPOT WELD
AREA LIES OUTSIDE THE DEFINED SHELL SURFACE.

USER INFORMATION: THE NUMBER OF PAIRS OF CONNECTING SHELL ELEMENTS IS 0
BUT 4 PAIRS ARE REQUIRED.
THE SHELL ELEMENT ID WHERE GA IS LOCATED=
37585
THE SHELL ELEMENT ID WHERE GB IS LOCATED=
40980
1-23993922
2007.0.0 (MD R2)
27 (MTMD34) - CKDDF1 is not complex
Acoustic Analysis - AABSElements - ufm 69
When frequency dependend AABS elements, FASTFR=YES and material structural

damping GE is used, the following fatal message is issued:
*** USER FATAL MESSAGE 6927 (MTMD34)
ATTEMPT TO CONVERT REAL MATRIX CKDDF1 INTO A COMPLEX MATRIX.
USER ACTION: USE THE ADD OR ADD5 MODULE; FOR EXAMPLE: ADD CKDDF1
,/CKDDF1R//(0.0,1.0) $
compile freqrs
alter 'matmod ckddf1,,,,,',''
paraml ckddf1//'trai'/4/s,n,type $
if ( type>2 ) then $
matmod ckddf1,,,,,/ckddf1r,ckddf1i/34 $
else $
equivx ckddf1/ckddf1r/-1 $
endif $
endalter
1-24030411
2008.0.0 (MD R3)
- Poor Message, SFM 3002(DSAD) and UFM6492(DOPR3R)
In a SOL 200 analysis the ATTB field of the DRESP1 entry is blank for static
displacement response but must contain the mode number for modes. If a SOL
200 analysis contains a static subcase and modes subcase that reference DRESP1
displacement, DRSPAN must be used to indicate the DRESP1s for each subcase. If
it is not used, the job may fail with the messages below and not clearly
indicate the problem.
SYSTEM FATAL MESSAGE 3002 (DSAD)
Avoidance: Use the DRSPAN entry and reference proper DRESPR1 entries for each
subcase.
1-24036963
Complex Eigenvalue - ESE, EKE, EDE, data recovery rules for
subcases - Missing results
If multiple subcases are specified in complex modes analysis then each subcase
is assigned to each mode for the purposes of controlling eigenvector, stress,
strain, and element force output on a per mode basis.
However this rule does
not extend to EDE, ESE, and EKE output in complex modes analysis for SOL 107 or
110.
Avoidance:
Specify EDE, ESE, and EKE above the subcase level.
1-24056699
2006.0.1
Elements - CBEAM, PBEAML- nsm varies fro
m end a to end b, ONLY end a is used. ELSUM is wrong
When using different NSM at end A and end B on the PBEAML, only NSM at end A is
used. The mass at the grid points is correct, only the ELSUM output is wrong
1-24063037
g Answers
2007.0.0
Acoustic Analysis - STATSUB, MAT10 - Wron
A model with a static subcase and fluid structure interaction fails to include
the fluid effects and/or the preload effects.
Avoidance: In Version 2005.1.0 apply the following alter:
compile phase1b
alter 'purgex /aa,aay,aaa,asf,',''
dbstatus aaa//s,n,noaaa $
if ( noaaa<1 ) purgex /aa,aay,aaa,asf,/-1 $
Version 2004.0.6
compile phase0
alter 'FSCOUP=FALSE',''
1-24081681
2005.5
nd Element IDs - Wrong Answers
External Superelements - Duplicate GRID a
If one or more grid point IDs and element IDs are the same in an external
superelement, then output requests for displacements and stresses in the
creation run for grid points and elements with the same IDs may lead to
erroneous results in a subsequent assembly run. Specifically, displacement
output requests for grid points in the creation run may lead to erroneous
element stress output for elements with the same IDs in a subsequent assembly
run. Similarly, element stress output requests for elements in the creation
run may lead to erroneous displacement output for grid points with the same IDs
in a subsequent assembly run.
Avoidance: Make the following two changes to the input data of the external SE
creation:
(1) If there are any VELO or ACCE requests in the Case Control, be certain to
consolidate those sets with a DISP request.
(2) Employ the following DMAP alter:
compile extout
alter 'sdr2','' $
SDR2 CASEx,CSTMS,MPTS,DIT,EQEXINs,,ETT,nulllama,BGPDTS,,qg,
rga,EST,XYCDBs,,,,,,,,,,,,,,/
,iqg1,IUG1,IES1,IEF1,,,,,,,/
1-24087243
2007.0.0
motion in a fluid-structure model
MDACMS - May be inefficient for enforced
The combined use of MDACMS and enforced motion in a fluid-structure model may
consume large resources unnecessarily. The problem arises when there are no
applied loads and no data recovery requested on any structural grid points.
One indication of the problem is the large "A-set" compute requirement for
MDACMS eigenvector recovery.
1. Apply a dummy load to, or request data recovery for, at least one
structural grid point.

OR
2. A DMAP alter avoidance is being tested.
1-24090441
2005.5.2
INVLAN may produce wrong answers
Eigenvalue Analysis - Special decomp for
The special decomp used for invlan on wide frequency ranges factors the dynamic
matrix using a block (or submatrix) algorithm.
It pivots only within each submatrix, but does not pivot among the matrix
blocks. For this reason, the algorithm is less stable than sparse decomp.
When the special decomp is used, and an ill-conditioned submatrix is
encountered, the Lanczos procedure may fail with orthogonalization error, or it
may produce incorrect answers.
There are two avoidances:
1) Set user parameter MDLGDEF to 99999999, which forces Lanczos to use the
standard sparse decomp, rather than the special INVLAN decomp. There may be a
significant performance penalty on problems with very wide frequency ranges.
2) Use the following alter, which "balances" the input matrices to READ.
Matrix balancing is implemented in the READ module for v2005R3, and has been
observed to significantly improve the overall condition number of the dynamic
matrix, as well as the condition number of the submatrices:
compile invlan, list $
alter 'READ
ABSKXX,MXX','READ
ABSKXX,MXX'
$
type parm,,i,n,nonullk $
$
$ find any locations where abskxx has null rows/columns
$
matmod abskxx,,,,,/ncvec,ncmat/12/s,n,nonullk/1 $
$
$ compute inf norm of cols of kxx
$
matmod abskxx,,,,,/infnrms,/7 $
$
if (nonullk > 0 ) then
add ncvec,infnrms/sfsqd $
else
equivx infnrms/sfsqd/always $
endif
$
diagonal sfsqd/sf/'whole'/-0.5 $
$
matmod sf,,,,,/balfac,/28$
$
smpyad balfac,abskxx,balfac,,/kxxbal/3 $
smpyad balfac,mxx,balfac,,/mxxbal/3 $
$
READ
kxxbal,mxxbal,MR,DXR,DYNAMICS,USET,CASES,VAXF,SILS,,
,LLL,EQEXINS,/
LAMA1,PHIXbal,MIX1,OEIGS1,ROOTS1,/
READAPPx/S,N,NEIGV1/NSKIP/METHF/CMSET/SIDx/
METHTYPx/F1x/F2x/NE//mdmsglv0/maxset0//'MASS'//
MAXRATIO/MDLGDEF $
$
mpyad balfac,phixbal/phix1$
1-24090721
2005.5
T - UFM 3007 in dompftn.
Optimization/Design Sensitivity - PBMSEC
A SOL 200 job with pbmsect entries may fail with USER FATAL MESSAGE 3007 in
dompftn if some pbmsect are not included in the design model.
Avoidance: Include all PBMSECT in the design model. If some pbmsect should
not be altered buring the optimization process, use the XINIT field of the
DESVAR entry to specify an appropriate XLB and XUB.
1-24121027
2008.0.0 (MD R3)
LAGR and TEMP=n and ALPHA
Rigid Elements - Wrong Results for RIGID=
Static analyis with thermal loads will produce incorrect results with
RIGID=LAGRANGE.
Part of the correction to this error is to issue a fatal
message if TEMP(INIT) is specified in a run with TEMP(MATE) or TEMP(BOTH).
1-24173515
2005.5.2
SOL 600 - PBEAML - PBEAML I-beam property
with large field format does not translate correctly
For the large format, the job with I-beam cross section is not translated
correctly to marc input file.
$ Elements and Element Properties for region : i-sect
PBEAML* 1
1
I
*
*
.8
.4
.4
.1
*
.1
.1
$ Pset: "i-sect" will be imported as: "pbeaml.1"
Marc input file was generated:
BEAM SECT
PBEAML
1I SHAPE
5, 10,6,10,6,10
-2.000000E-01, -5.960464E-09, 0.0,0.0, 2.000000E-01,
4.000000E-01, 1.000000E-01, 1.000000E-01,
2.000000E-01, -5.960464E-09, 0.0,0.0, 0.000000E+00,
2.000000E-01, 0.000000E+00, 0.000000E+00,
0.000000E+00, -5.960464E-09, 0.0,0.0, 0.000000E+00,
7.500000E-01, 1.000000E-01, 1.000000E-01,
0.000000E+00, 7.500000E-01, 0.0,0.0, -2.000000E-01,
2.000000E-01, 0.000000E+00, 0.000000E+00,
-2.000000E-01, 7.500000E-01, 0.0,0.0, 2.000000E-01,
4.000000E-01, 0.000000E+00, 0.000000E+00,
-5.960464E-09, 0.0,0.0,
-5.960464E-09, 0.0,0.0,
7.500000E-01, 0.0,0.0,
7.500000E-01, 0.0,0.0,
7.500000E-01, 0.0,0.0,
Avoidance: Use the short format.

1-24206471
2005.5.2
SOL 600 - RBE2 and SPC1 written in large
field format is not translated correctly
RBE2 and SPC1 written in large field format are not translated into marc input
correctly in SOL 600.
Avoidance: Use small field format
1-24229901
2007.0.0
tics with traceback
Iterative Solver - SMETHOD - Fails in sta
If the input matrix contains null columns, the BIC iterative solver could fail
with a meaningless traceback rather than producing an informative message.
Avoidance: Ensure that the model is properly constrained using AUTOSPC or

direct application of SPC.
1-24239871
2007.0.0
Label from VG xyplot
Plotting - Missing Title, Subtitle, and
The TITLE, SUBTI and LABEL information is missing from the flutter VG xyplots
for version 2005.0 and 2005.1. TCURVE information appears in the xyplot
output. Version 2004 and earlier releases are correct.
Avoidance: A dmap alter is available on request.
1-24246501
T
2007.0.0
Elements - P-Element - SFM 3011 in VECPLO
P-Element jobs may encounter SYSTEM FATAL MESSAGE 3011 in VECPLOT.

1-24262578
2005.5.2
Large Models - IA64 Linux - Signal 11
Fixed in round 15. Verified in round 16.

A signal 11 may occur on large models on IA64 Linux systems if the stack size
is limited.
Avoidance:
increase stack size with either:
- The command "ulimit -s unlimited"
or
- modifying /etc/security/limits.conf
The stacksize may be displayed with "unlimit -a"
1-24268315
n FBS
2007.0.0
Parallel - SOL 101, AUTOMSET - SFM 3011 i
In SOL 101 and dmp>1 with PARAM,AUTOMSET,YES the run will terminate with:
SFM 3011 (FBS) ATTEMPT TO WRITE A TRAILER ON FILE 201 WHEN IT HAS BEEN PURGED
compile phase1dr
alter 'call disph1b',''
call disPH1b,
CASES ,EDT
,EQEXINS ,GEOM4S
KGG
,PG
,RMG
,SILS
YG
,mgg
,spcpart ,cstms
rxg
,yxg
/
GM
,USET
,KSF
,KFS
dkff
,kmg
,dpf
,pss
mmg
,msf
,dmff
,rxa
ym
/
error /nskip /nloads /semr
compile disph1b
alter 1,1
SUBDMAP disPH1b,
CASES ,EDT
,EQEXINS ,GEOM4S ,GPLS
,
KGG
,PG
,RMG
,SILS
,USET0 ,
,GPLS
,
,USET0 ,
,bgpdts ,
,KSS
,ys
,yxa
$
,
,
,
YG
rxg
GM
kff
mmg
ym
error
type db pym $
,mgg
,yxg
,USET
,kmg
,msf
/
/nskip
,spcpart
/
,KSF
,pf
,mff
,cstms
,bgpdts ,
,KFS
,pss
,rxa
,KSS
,ys
,yxa
/nloads /semr
,
,
,
alter 'call sekr0',''

CALL SEKR0 KGG,USET0,RMG,GEOM4S,EQEXINS,SILS,GPLS,spcpart,
,,cstms,bgpdts,cases,,yg,rxg,yxg/
GM,USET,knn,kmg,rxa,yxa,pym,ym/
ERROR/SEID/AUTOSPC/0/false/true/NSKIP/true $
alter 'endif \$ ncul=nloads or'
paraml pym//'null'////s,n,nullpym $
if ( nullpym>-1 ) then $
add5
pg1,pym,,,/pgy//-1. $
equivx pgy/pg1/-1 $
endif $ nullpym>-1
SOL 101
DMP = 4
PARAM,AUTOMSET,YES
approx 2 million dof's
Using v2005.1, and v2005.5, job fails
with
*** SYSTEM FATAL MESSAGE 3011 (FBS)
ATTEMPT TO WRITE A TRAILER ON FILE 201 WHEN IT HAS BEEN PURGED
f04 shows it failed in the:
MCE1S 12
FBS
BEGN
Using v2005.0, job runs successfully.
1-24287255
2007.0.1
ported in SOL 106
Documentation/QRG - PARAM OMID is not sup
Parameter OMID is not supported in SOL 106 as indicated in Table 5-1 of the
PARAM section
1-24332591
2005.5.2
incorrect OP2 fortran record size
File Management Section - ASSIGN, FORM -
The 'FORM=' specification is used for OP2 files that are to be processed on a
platform other than current platform. When used, USER INFORMATION MESSAGE
4114 that is output for op2 files may indicate that the 'MAXIMUM SIZE OF
FORTRAN RECORDS WRITTEN' exceeds the 'MAXIMUM POSSIBLE FORTRAN RECORD SIZE'
It seems that each word of the datablocks are the same between different FORMs.
This may cause problems when the client uses the (small) fixed fortran record
size to process OP2 files with an in-house post-processor.
This error has been fixed in MSC.Nastran 2005r3b
1-24374298
Superelements - SEBULK EXTOP4 - UFM 4156 SEMA
If the KAA matrix in OP4 format is not Gsize (i.e. GRIDs on EXTERN <> 123456)
then the following error will occur during the assembly run:
*** USER FATAL MESSAGE 4156 (SEMA)
DIMENSIONS OR TYPE OF DATA BLOCK XAAV
, SUPERELEMENT
10
TRAILER=(
22
22
6
2
12 992) ARE INCONSISTENT WITH
SUPERELEMENT MAP.
0FATAL ERROR
Avoidance: User must merge the matrix to Gsize with dmap.
This error is fixed in MSC.Nastran 2005.5.1 and MD Nastran 2006.0.1
1-24400047
2007.0.0
MDACMS - EPOINT and TF - UFM 1126
MDACMS will terminate with UFM 1126 on data block XHSE if the model contains
EPOINTs and transfer functions (TFL)
compile get2pp
subdmap get2pp cases,dits,usetd,rotor,rotmat,matpool,eqdyn,
tfpool,bgpdts,cstms,kpp,bpp,mpp/
k2pp,b2pp,m2pp/
app/noue/lusetd/soltyp/nlheat/fs $
type parm,,i,n, nok2pp=-1,nob2pp=-1,nom2pp=-1,lusetd,noue $
type parm,,logi,n,freqdepr,acsyml,abfl,nlheat,fs $
type parm,nddl,char8,y,acsym $
type parm,,char8,n,app,soltyp $
TYPE PARM,,cS,n,cmu=(-1.,0.),cu=(1.,0.),cz $
PARAML cases//'DTI'/1/446//S,N,IRGYRO $
$ If no Campbell, do gyro terms here otherwise in sedceig
PARAML cases//'DTI'/-1/495//S,N,ICAMP $
IF ( IRGYRO>0 and
not(icamp=-1 and app='ceigen' and soltyp='direct') and
(app='freqresp' or app='ceigen' or app='tranresp') ) then $
CALL GENGYRO cases,dits,USETD,ROTOR,ROTMAT/
MGPP,BGPP,KGPP,VGFDr/
APP/s,freqdepr/noue $
endif $ IRGYRO>0
call xmtrxin cases,matpool,eqdyn,tfpool,/
k2pp,m2pp,b2pp,,,/
'x2pp '/lusetd/s,nok2pp/s,nom2pp/s,nob2pp/0/0/0 $
$
$
$ Add Matrices of Acoustic Infinite Elements
$
DBSTATUS KPP,MPP,BPP//S,N,NOKPP/S,N,NOMPP/S,N,NOBPP $
IF ( NOKPP=1 ) THEN $
IF ( NOK2PP>-1 ) THEN $
CALL XADD5 KPP,K2PP,,,/K2PPX/CU/CU/CZ/CZ/CZ $
EQUIVX K2PPX/K2PP/ALWAYS $
ELSE $
EQUIVX KPP/K2PP/ALWAYS $
NOK2PP = 1 $
ENDIF $
ENDIF $
IF ( NOBPP=1 ) THEN $
IF ( NOB2PP>-1 ) THEN $
CALL XADD5 BPP,B2PP,,,/B2PPX/CU/CU/CZ/CZ/CZ $

EQUIVX B2PPX/B2PP/ALWAYS $
ELSE $
EQUIVX BPP/B2PP/ALWAYS $
NOB2PP = 1 $
ENDIF $
ENDIF $
IF ( NOMPP=1 ) THEN $
IF ( NOM2PP>-1 ) THEN $
CALL XADD5 MPP,M2PP,,,/M2PPX/CU/CU/CZ/CZ/CZ $
EQUIVX M2PPX/M2PP/ALWAYS $
ELSE $
EQUIVX MPP/M2PP/ALWAYS $
NOM2PP = 1 $
ENDIF $
ENDIF $
$
IF ( IRGYRO>0 and icamp<>-1 ) then $
PARAML MGPP//'NULL'////S,N,NOMGPP $
IF ( NOMGPP<>-1 ) THEN $
call xADD5 MGPP,M2PP,,,/M2PPX/cu/cu/cz/cz/cz $
EQUIVX M2PPX/M2PP/-1 $
NOM2PP= 1 $
ENDIF $
PARAML BGPP//'NULL'////S,N,NOBGPP $
IF (NOBGPP <> -1) THEN $
call xADD5 BGPP,B2PP,,,/B2PPX/cu/cu/cz/cz/cz $
EQUIVX B2PPX/B2PP/-1 $
NOB2PP= 1 $
ENDIF $
PARAML KGPP//'NULL'////S,N,NOKGPP $
IF (NOKGPP <> -1) THEN $
call xADD5 KGPP,K2PP,,,/K2PPX/cu/cu/cz/cz/cz $
EQUIVX K2PPX/K2PP/-1 $
NOK2PP= 1 $
ENDIF $
endIF $ IRGYRO>0
$
acsyml=(app='freqresp' and acsym='yes' and fs) $
IF ( SOLTYP='DIRECT ' AND NOT(NLHEAT) ) THEN $
$
PARAML MATPOOL//'PRESENCE'////S,N,NOMPOOL $
IF ( NOMPOOL>=0 ) THEN $
BMG
MATPOOL,BGPDTS,CSTMS/
BDPOOL/
S,N,NOKBFL/S,N,NOABFL/S,N,MFACT $
ABFL = NOTL(NOABFL) $
IF ( ABFL OR NOTL(NOKBFL) ) THEN $
NOK2PP=1 $
MTRXIN, ,BDPOOL,EQDYN,,/
ABFL,KBFL,,,/
LUSETD/NOABFL/NOKBFL/0 $
call xADD5 ABFL,KBFL,K2PP,,/K2DPP/cmu/cu/cu/cz/cz $
EQUIVX K2DPP/K2PP/ALWAYS $
IF ( ABFL ) THEN $
NOM2PP=1 $
TRNSP
ABFL/ABFLT $
ADD
ABFLT,M2PP/M2DPP/MFACT $
EQUIVX M2DPP/M2PP/ALWAYS $
ENDIF $ ABFL
ENDIF $ FL
ENDIF $ NOMPOOL>=0
ENDIF $ SOLTYP=DIRECT AND NOT(NLHEAT)
$
return $
end $ get2pp
compile semfreq
alter 'if ( nokpp=-1',''(,6)
alter 'call fdrmgen'(,-1)
call get2pp casem,dits,usetd,rotor,rotmat,matpools,eqdyn,
tfpool,bgpdts,cstms,kpp,bpp,mpp/
k2pp,b2pp,m2pp/
app/noue/lusetd/soltyp/false/fs
MATMOD K2pp,b2pp,m2pp,,,/Vpr,xx/25/S,N,NOvpr/3 $
upartn usetd,vpr/vpr1,,,/'p'/'g'//1 $
MATMOD vpr1,,,,,/vpr2,/47 $
diagonal vpr2/vpaie/'whole'/0.0 $
compile semceig
alter 'call modefsrs',''
call get2pp casem,dits,usetd,rotor,rotmat,matpools,eqdyn,
tfpool,bgpdts,cstms,,,/
k2pp,b2pp,m2pp/
app/noue/lusetd/soltyp/false/fs
Matmod k2pp,b2pp,m2pp,,,/vy1,/12/s,n,nonull/3/-1 $
upartn usetd,vy1/vy2,,,/'p'/'g'//1 $
diagonal vy2/v01p/'whole'/0.0 $
type parm,nddl,logi,n,seindr $
seindr=true $
IF ( DOPH2M ) CALL MODEFSRS,
MR
,USET
,Dar
,casem ,DYNAMICS,
MAA
,mKAA
,GPLS
,SILS
,EED
,
EQEXINS ,VAFS
,pg
,gm
,got
,
ksf
,yg
,lll
,kll
,drg
,
bgpdts ,cstms ,vgq
,goq
,
,
bjj
,rvg
,cee
,mee
,gge
,
bec
,mec
,bsf
,msf
,pmyg
,
pbyg
,pkyg
,pvt0
,mgg
,vgfs
,
,
,
,
,
,
,
,
,
,
,
,v01p
,
,
,
/
PHA
,LAMA
,PHFA
,LAMAF ,PHSA
,
LAMAS ,mechg ,lammats ,lammatf ,mis
,
mif
,meh
,
,
,
,
,
,efmfacf ,efmfacs ,mdphiq ,
mdgot ,mdgoq ,mdvft ,mdmap ,mdgrdrm ,
mdgotmap,
,
/
app
/NORSET /NOASET /FS
/NOFASET /
NOSASET /METH
/METHF /TRUE
/NOQSET /
1
/0
/'no ' $
delete /v01p,,,, $
compile mdddtohh
alter 'PARTN PHDSH,,VDE',''
type parm,,i,n,nohset $
PARAML phdsh//'TRAILER'/1/S,N,NOHeSET $
nohset=noheset-noue $
MATGEN ,/VHE0/6/NOHESET/NOHSET/NOUE $
PARTN PHDSH,vhe0,VDE/PHDSH0,,,/1 $
alter 'TRNSP XEHST\/XHSE',''

TRNSP XEHST/Xesh $
endalter
1-24412204
2008.0.0 (MD R3)
Error 31) in the BDRYINFO module
External Superelements - SFM 3200 (Logic
An external SE creation run that employs other external superelements or part

SEs may terminate with SYSTEM FATAL MESSAGE 3200 (Logic Error 31) in the
BDRYINFO module if those superelements have been modally reduced.
The following ALTER package will cause the job to terminate with a meaningful
UFM rather than the unhelpful SFM mentioned above:
compile phase0
alter 'equivx geom2s/geom2x'(,-1) $
PARAML BGPDTS//'TRAILER'/6/S,N,MAXPNTID $
IF (EXTSEOUT > 0 AND MAXPNTID > 99999999) THEN $
MESSAGE //' ' $
MESSAGE //'USER FATAL MESSAGE XXXX (PHASE0)' $
MESSAGE //'*** ONE OR MORE POINT IDS ENCOUNTERED IN THIS' $
MESSAGE //'
EXTERNAL SUPERELEMENT CREATION RUN ARE GREATER' $
MESSAGE //'
THAN 99999999' $
MESSAGE //' ' $
MESSAGE //'USER INFORMATION:' $
MESSAGE //' ' $
MESSAGE //'THE MOST LIKELY CAUSE OF THE ABOVE ERROR IS THAT' $
MESSAGE //'THIS JOB INVOLVES THE USE OF ONE OR MORE MODALLY' $
MESSAGE //'REDUCED EXTERNAL OR PART SUPERELEMENTS.' $
MESSAGE //'RE-RUN THIS JOB BY MODALLY REDUCING SUCH' $
MESSAGE //'SUPERELEMENTS BY USING THE' $
MESSAGE //'EXTSEOUT (ASMBULK=MANQ,....)' $
MESSAGE //'OPTION AND EMPLOYING THE RESULTING .ASM FILES' $
MESSAGE //'FOR THIS JOB.' $
MESSAGE //' ' $
CALL PRTSUM/RSTJUNK $
EXIT $
ENDIF $
Avoidance: Re-run the external SE creation job by modally reducing those other
SEs using the EXTSEOUT (ASMBULK=MANQ,....) option and employing the resulting
.asm files.
1-24494561
2005.5.1
LPHA1 and ALPHA2 - Wrong answers
Dynamics - SPCD enforced motion, PARAMs A
If Rayleigh damping (PARAMs ALPHA1 and ALPHA2) is requested with SPCD enforced
motion then the answers will be wrong. This error has been fixed in
MSC.Nastran 2005.5.1 and MD Nastran 2006.0.1.
compile cforce1
alter 1
TYPE PARM,NDDL,CS,Y,ALPHA1,ALPHA2 $ Rayleigh Damping
TYPE PARM,,CS,N,ALPHA1N,ALPHA2N $
ALPHA1N=ALPHA1 $
ALPHA2N=ALPHA2 $
alter 'call xADD5
BXY,B2XY,KXY,K4XY'
CALL XADD5 mxy,kxy,bxy1,,/bxyx/alpha1n/alpha2n/cu/cz/cz $
equivx bxyx/bxy1/-1 $
alter 'call xADD5
BXY,B2XY,,,'
CALL XADD5 mxy,kxy,bxy1,,/bxyx/alpha1n/alpha2n/cu/cz/cz $
equivx bxyx/bxy1/-1 $
endalter
1-24507921
2007.0.0
Riged Elements - RBE2GS with IIRBE2 optio
n fails with segmentation violation in sep1x
RBE2GS with IIRBE2 option fails with segmentation violation in the SEP1X module
1-24510816
2007.0.0
Documentation - PCOMP - Composite Element
s with Temperature Dependent Material Properties
For layered composites, neither the TREF specified on the material entries or
TEMP(INIT) or TEMP(MATE) are used to determine ply reference temperature. The
TREF on the PCOMP or PCOMPG entries is used for all plies of the element. This
is true for both linear and nonlinear analysis.
SOL 106 looks up a new ply temperature at each incremental load step.
PARAM,COMPMATT,YES is for shape memory which is only in SOL 106.
1-24524111
2006
ELD - Does not work
Optimization/Topology - TOPVAR, CWELD, PW
In the QRG, the TOPVAR entry allows specification of PWELD for a topological
optimization analysis. However, if PWELD is specified no error message is
written in f06 file and no results for CWELD is written in the DES file.
1-24584517
2008.0.0 (MD R3)
UFM 7138 in DOPR3H
Optimization/Design Sensitivity - FRSTRE-
In SOL 200 if only element FRSTRE response is requested, NFRQ is not set and
the job will fail in DOPR3H with USER FATAL MESSAGE 7138.
Avoidance: When a dummy DRESP1 with RTYPE=FRDISP/MAX is added, the problem
can be avoided.
1-24604261
2005.5
SOL 600 - op2 file output capability does
not work correctly if DDM with PARAMARC - SFM 6352
The op2 file output capability of SOL 600 does not work correctly if single
input DDM with PARAMARC and PARAM,MARCOUTR,1 is used. The fatal message below
is output to the f06 file.
*** SYSTEM FATAL MESSAGE 6352 (GETENT)
LOGIC ERROR: KERROR= 7
PROGRAMMER INFORMATION: RECORD NAME = iElmGid
PROGRAMMER INFORMATION: RECORD LENGTH (LREC= 10009) IS NOT A MULTIPLE OF
ENTRY LENGTH (NWD=
9).
PROGRAMMER INFORMATION: THE PARENT SUBROUTINE IS T6OUTS3
0FATAL ERROR
1-24607467
2005.5.2
Elements - GPSTRAIN, STRAIN - Von Mises a
nd Max Shear Strain is Wrong for plane strain condition.
The Von Mises and Max Shear strain output is incorrect for the plane strain
condition.
Avoidance: Other than calculating the invariant by hand, there is no

avoidance. This error has been corrected in MD.Nastran 2006r1 abd MSC.Nastran
2005r3b for all elements except the QUADR and TRIAR.
1-24618141
2007.0.0
Aeroelastic Analysis - UWM 7343 (MRBE3D
THE ERROR VALUE FOR MONDSP1 ENTRY EXCEEDS 1.0e-10
The following message:
*** USER WARNING MESSAGE 7343 (MRBE3D)
THE ERROR VALUE FOR MONDSP1 ENTRY D_NG_UPR IS 1.126E-09, WHICH
EXCEEDS THE TEST CRITERION OF 1.000E-10.
may be encounted as the result of too tight a tolerance on a matrix inversion.
The code will be changed to a value of 1.e-06.
1-24674065
ation
Eigenvalue Analysis - READ, MFLUID Virtual Mass - Access Viol
The error is in the ACTIVE COLUMN decomp, which is used

when the reordering fails (due to insuficient memory).
More useful avoidances include:
Do not set sys166=1.
Do use more memory.
A simple model with MFLUID virtual mass elements fails in the READ Module with
an Access Violation.
Avoidance: Do not use "extreme" reordering, use metis by setting SYS206=8.
1-24741081
2007.0.0
- MAT2 - Wrong Answers
Restarts, Optimization/Design Sensitivity
There is an error in the way dependencies for Gij terms on the MAT2 entry are
defined with the result that restarts that only change this data will not
compute new element stiffness matrices. If these are the only entries that are
changed, the results for the original submittal are likely to be repeated.
This has implications in SOL 200. If the only designed properties are MAT2
terms and SCR=NO is used, the analysis will not use the updated properties and
the analysis results will be unchanged from a previous iteration.
Avoidance: For SOL 200, the avoidance is to use SCR=yes. For other solution
sequences, one avoidance would be to make an addtional change in some other
input value that will trigger computation of new stiffness matrices.
1-24850088
2007.0.0
non structural mass
Elements - PCOMP - Incorrect answers for
When ifp processes NSM, NSM1, NSML, and NSML1 entries it is supposed to
replace:
1) PCOMP with PSHELL
2) PBCOMP with PBEAM
3) PBEAML with PBEAM
4) PBARL with PBAR
5) PRAC2D with PDUM8
in the TYPE field
For the NSM and NSML entries it fails to replace PCOMP with PSHELL (item 1).
Items 2-5 are done correctly for NSM, NSM1, NSML, and NSML1 entries
1-24917119
2007.0.0
PUT=n - No Preload Effects
Cyclic Modes - STATSUB, HARMONIC=m, HOUT
If cyclic symmetry eigenvalue analysis, SOL 115, is run with a static preload
subcase, STATSUB, and a request for HARMONIC and HOUTPUT using a set id is
included, then the preload effect of the STATSUB is missing and the eigenvalues
calculated are those with no preload.
To avoid use either request for ALL on the HARMONIC and HOUTPUT requests or use
the following DMAP alter:
compile cycmode
alter 'call statcyc'
equivx uxv/cyul/-1 $
1-24978987
2007.0.0
Optimization/Topology - TOPVAR - SFM 4276
(GREAD) in DOPR1 for TOPVAR used with Beta function
Topology optimization using function BETA on the DRESP2 entry fails with the
message:
SYSTEM FATAL MESSAGE 4276 (GREAD) ERROR CODE
3001 PID= 0 in DOPR1.
1-24992231
2007.0.0
Optimization/Design Sensitivity - Labelin
g errors for unfomatted design sensitivity prints
If param optexit 4 is used to produce prints of unformatted sensitivities that
include eigenvector responses, the following erroneous labeling is produced:
----- STATICS RESPONSES --------------------------------------------------------------------------------------------------------------------------COLUMN
DRESP1
RESPONSE
GRID/ELM
VIEW
COMPONENT
SUB
PLY/GRID
NO.
ENTRY ID
TYPE
ID
ELM ID
NO.
CASE
NO.
----------------------------------------------------------------------------------------------------------------------3
302
DISP
302
1
1
1
4
302
DISP
302
1
2
1
There are a number of things wrong with this output:
a. eigenvector sensitivity does not support composites, so the last column is
unnecessary
b. View elm id is a p-element output and should the number should be blank
unless this is a stress, force or strain response on a p-element
c. The Mode id is printed in the view elm id slot
d The mode id should be printed in the last slot and MODE should take the place
of PLY/GRID
User Action: Ignore the "Static Responses" when these are "Eigenvector
Response" and obtain the Mode id from the View Elm ID column.
1-25080130
2008.0.0 (MD R3)
Documentation/QRG - PARAM description doe
s not indicate that they can be used in rc and ini files
The Parameter section in the QRG currently says:
"Parameters are used extensively in the solution sequences for input of scalar
values
and for requesting special features. Parameters values are specified on PARAM
Bulk
Data entries or PARAM Case Control commands. The PARAM Bulk Data entry is
described in the Bulk Data Entries
on page 851. The PARAM Case Control
command is described in the Case Control Commands
on page 177. A complete
alphabetical list of PARAMeter names and their functions is given in this
section."
It should be changed as follows to note the fact that it is often very useful
to set parameters in an rc or ini file.
"Parameters are used extensively in the solution sequences for input of scalar
values
and for requesting special features. Parameters values are specified on PARAM
Bulk
Data entries or PARAM Case Control commands. The PARAM Bulk Data entry is
described in the Bulk Data Entries
on page 851. The PARAM Case Control
command is described in the Case Control Commands
on page 177. PARAMs may
also be used in .rc and .ini files as described in the MSC Nastran Installation
and
Operations Guide, Section 3.8 "Specifying Parameters". A complete
alphabetical list of PARAMeter names and their functions is given in this
section.
1-25108891
2005.5.2
fixed field is used - Wrong Answers
SOL600 - PARAM,WTMASS may be ignored if
In SOL 600, param WTMASS is ignored and is not translated if the fixed field
format is used and WTMASS doesn't start in fields 9,11, or 16. This will cause
errors if mass is important in the solution.
Avoidance is to use FREE field format, or ensure the W in WTMASS exits in
fields 9,11,16.
1-25202690
ut
2007.0.0
Case Contol - REPCASE- Missing Punch Outp
A job writes no punch if repcases are present and subcase has sort2 output
request
1-25259262
2007.0.0
multiple DMIG entries
Case Control - K2GG, M2GG - Error reading
K2GG and M2GG entries in the case control that span more than 72 characters
are not read correctly.
Avoidance: The avoidance is to place the DMIG names in a SET and reference the
SET on the K2GG and M2GG entries. As shown SET entries that continue to the
next line should end in a comma before column 72.
SOL 101
CEND
$-------2-------3-------4-------5-------6-------7-------8-------9-------0------set 100 = KA1,KA2,KA3,KA4,KA5,KA6,KB1,KB2,KB3,KB4,KB5,

KB6,KC1,KC2,KC3,KC4,KC5,KC6
K2GG = 100
set 200 = MA1,MA2,MA3,MA4,MA5,MA6,MB1,MB2,MB3,MB4,MB5,
MB6,MC1,MC2,MC3,MC4,MC5,MC6
M2GG = 200
1-25264891
2007.0.0
Rigid Elements - Incorrect SPCFORCES are
produced if load is applied to dependent DOF
Wrong SPCFORCES occur if load is applied to dependent degrees of freedom.
Avoidance: Use "param,sparsedr,no"
Or use the following alter inversion 2005+ which is much more efficient.
compile spdr1
alter 'if ( novspcg'(3)
upartn uset,vpg/vpm,,,/'g'/'m'//1 $
paraml vpm//'null'////s,n,nlvpm $
if ( nlvpm>-1 ) then $
upartn uset,vspcg/vspcn,,,/'g'/'n'//1 $
partn
gm,vspcn,vpm/,,,xxx/1 $
paraml xxx//'null'////s,n,nlxxx $
if ( nlxxx>-1 ) then $
matmod xxx,,,,,/xxx1/6 $
diagonal xxx1/xxx2/'whole'/0.
merge
,,xxx2,,,,vpm/vpm1/1 $
umerge1 uset,vpm1,,,/vpmg/'g'/'m'//1 $
call xadd5 vspcg,vpmg,,,/vyx/cu/cu/cz/cz/cz $
equivx vyx/vspcg/-1 $
endif $ nlxxx>-1
endif $ nlvpm>-1
endalter
1-25272631
2007.0.0
SSSALTER - SEGYRO alter is missing in sss
alter library since Nastran Version 2004
EGYRO alter is missing in sssalter library since Nastran Version 2004. This
alter is required for calculating flexible rotating structures like helicopter
rotor blades. The rotor dynamic feature doesn't support this.
1-25277451
2008.0.0 (MD R3)
for interior angles of 180 degrees
Elements - CQUADR may give wrong results
If a model contains CQUADR elements with an interior angle of180 degrees or

more, USER FATAL MESSAGE 4297 will not be issued and the results may be
incorrect.
Avoidance: Check your model with CQUAD4 elements.
1-25287241
2007.0.0
Frequency Response - Summary Table in FRR
D1 prints zeroes for 51st and subsequent frequencies
If there are more than 50 frequencies in the job, the Frequency Response
Summary Table in FRRD1 prints the correct values only for the first 50
frequencies. After that, all frequencies are printed as 0.0. This does NOT
effect the results. It is just a cosmetic error in the Summary Table.
1-25306330
2007.0.0
try - Wrong answers
Axisymmetric Analysis - AXIC Bulk Data en
If the AXIC entry is present and a limited set of ouput is requested such that
sparse data recovery is activated then output will be wrong.
Avoidance: Insert PARAM,SPARSEDR,NO or specify ALL on at least one Case
Control output command.
1-25307074
2007.0.0
Axisymmetric Analysis - SFM 6406 (G4SPC),
AXIC and SPCAX entry higher than 100 and SPCAX
An axisymmetric analysis with AXIC and SPCAX defined greater than 100 leads to
the following fatal message:
*** SYSTEM FATAL MESSAGE 6406 (G4SPC)
GRID POINT ID= 102000001 ON AN SPCP/SPCDP ENTRY HAS COMPONENT= 23 GREATER
THAN MAX. NDOF= 6
PROGRAMMER ACTION:
CHECK SPCP/SPCDP ENTRIES CREATED IN GP0 MODULE.
*** SYSTEM FATAL MESSAGE 6406 (G4SPC)
GRID POINT ID= 101000001 ON AN SPCP/SPCDP ENTRY HAS COMPONENT= 23 GREATER
THAN MAX. NDOF= 6
PROGRAMMER ACTION:
CHECK SPCP/SPCDP ENTRIES CREATED IN GP0 MODULE.
*** USER INFORMATION MESSAGE 4110 (OUTPX2)
1-25476171
g Output
2007.0.0
Case Control - SUBSEQ - UWM 2092, Missin
If a SUBSEQ entry contains a factor for each of the preceding subcases but ends
in a comma, UWM 2092 may be issued and the output for the SUBSEQ may be missing.
1-25478961
t GPFORCEs
Nonlinear Analyis - CBUSH - Grounded CBUSH may yield incorrec
A model with a grounded cbush element in SOL 106 may give incorrect GPFORCE
data. This error occurs when not all six stiffnes values for the grounded
CBUSH.
1-25479301
2007.0.0
M,POST,-1 - inefficient
Data Recovery - PARAM,SPARSDR,NO and PARA
If PARAM,SPARSDR,NO and PARAM,POST,-1 are specified in a run where SORT2

output is computed, the run will perform unnecessary operations.
compile sedrcvr
alter 'if ( not(sort2) or post',''
if ( not(sort2) and not(POST=-1 OR POST=-2 OR POST=-6) ) then $
alter 'IF ( sort2mm and (POST=-1',''
IF ( (sort2mm or app1='mmreig') and
(POST=-1 OR POST=-2 OR POST=-6) and
not(acms) and fullsedr='no' ) THEN $
delete /opg1,,,, $
endalter
1-25660161
2008.0.0 (MD R3)
of BCBODY is incorrect
Documentation/QRG - Description of ISTYP
The QRG incorrectly states that the default for the BCBODY ISTYP field is 2 for
deformable. The defautl is 0. Furthermore the following remark should be
added:
BCONTACT=ALLBODY is to be defined when ISTYP=2 is specified.
1-25697761
2007.0.0
SOL 600 - MARCIN written in small field f
ormat is not translated into marc.dat file correctly
MARCIN written in small field format is not translated into marc.dat file
correctly.
For example:
If marcin entry below is in the input deck, "feture,6701" should be in the
parameters section of marc.dat file, but it does not.
marcin -1
0
feature,6701
If marcin entry below is in the input deck, "feture,6701" is in the parameters
section of marc.dat file.
marcin,-1,0,feature,6701
Avoidance:
Use free field format.
1-25716447
2007.0.0
FM 3001, RBMG4, SOL 101
Rotordynamics - Linear Gap Constraing - S
Attempting to run a SOL 101 with the rotordynamic and linear gap constraint
will result in the following fatal message:
*** SYSTEM FATAL MESSAGE 3011 (RBMG4)
ATTEMPT TO WRITE A TRAILER ON FILE 201 WHEN IT HAS BEEN PURGED
Avoidance: Include one of the two following DMAP alters.
$ for Version 2005.5.0
compile sestatic
alter 'call phase1c','' $ Version 2005.5.0
IF ( nouset>0 and not(mdstat) and
( (dbrcvx='scratch' and not(pardcmp)) or
(pardcmp and hlpmethx=1 and procid=1) )
) CALL PHASE1C KAA
,USET
,SILS
,EQEXINS
PA
,
,
,cases
drg
,
,
,
KLL
,LLL
,Dar
,ULL
mlr
,mll
,mrr
,QR
LRSEQ ,
,
,
/
SEKR
/SEMR
/SELR
/NOLSET
true
/ERROR /FIXEDB /NOQSET
'
'/TRUE
/false /false
false $
,maa
,
/
,mr
,PL
,
,
,
,
,
,
/NORSET /
/NOTSET /
/noa
/
$ for versions 2005.1.0 and 2005.0.0

compile sestatic
alter 'call phase1c','' $ tested on version 2005.1.0 and 2005.0.0
IF ( nouset>0 and not(mdstat) and
) CALL PHASE1C KAA
,USET
,SILS
,EQEXINS ,
,
PA
,
,
,cases ,
,
drg
,
KLL
,LLL
mlr
,mll
LRSEQ ,
SEKR
/SEMR
true
/ERROR
'
'/TRUE
false $
,
,Dar
,mrr
,
/SELR
/FIXEDB
/false
/
,ULL
,QR
,
/NOLSET
/NOQSET
/false
,mr
,PL
,
/NORSET
/NOTSET
/noa
,
,
/
/
/
/
Test file place on /msc/app/etl as q1-25716447.dat

1-25721381
d of UFM 12
2007.0.0
DMAP - DMAP compiler issues UWM 1 instea
A DMAP compile may issue UWM 1 instead of UFM 12:

# *** USER FATAL/WARNING MESSAGE 12 (XGPIDG)
ERROR IN DMAP INSTRUCTION NO. %1, ILLEGAL CHARACTER IN DMAP INSTRUCTION
NAME.
1-25750061
2007.0.0
Connector Elements - PFAST with MCID=-1 a
nd MFLAF=1 may yield strange element coordinate system
PFAST entry with MCID=-1 and MFLAG=1 may yield strange elemet coordinate system
for force recovery. If MCID=-1, MFLAG should always be blank or 0.
The fix will set MFLAG to if MCID=-1 regardless of value specified.
1-25759747
Shear Strain
2006.0.1
GPSTRAIN - CQUADx, CTRIAx - Incorrect MAX
MD Nastran 2006 (r1) introduced an error that causes the maximum shear strain
for shell elements to be twice it should be. The error has been corrected in
MD Nastran 2006 (r1a).
1-25765441
2008.0.0 (MD R3)
Connector Elements - CFAST, CWELD may not
find projection and may fail to connect
If gridA and gridB are specified on a CFAST or CWELD and grid GS is left blank
for the attached model the algorithm may be unable to project.
1-25765671
rs
2006
Acoustic Analysis - PFPANEL - Wrong Answe
1. If Keyword "PHAS" is specified on the PFPANEL command, the real and

imaginary part printed in the .f06 are wrong.
Avoidance: Do not specifiy "PHAS" keyword.
2. If there are panels that are not part of the wetted surface, the panel names
in OAPPF1 and in the .f06 are wrong.
Avoidance: Do not define panels that are not on the wetted surface.
1-25773137
Superelements - PARAM,SESDAMP,YES does not work correctly whe
n PARAM,AUTOQSET,YES is also specified.
Attempting to apply different damping to different superelements using
PARAM,SESDAMP,YES combined with PARAM,AUTOQSET,YES leads to wrong answers.
Avoidance 1: Use manual Q-set entries instead of employing PARAM,AUTOQSET,YES

Avoidance 2: Employ the DMAP alter given below when using PARAM,AUTOQSET,YES
compile phase1b
alter 'call semrb'(9)
np=noqset-xnoq $
delete /vq,,,, $
matgen ,/vq/6/noqset/xnoq/np $
matgen ,/vq1/6/noqset/np/xnoq $
partn
mbqq,vq,/mbqq0,,, $
delete /mbqq,,,, $
merge
,,,,mbqq0,vq1,/mbqq $
1-25775091
2007.0.0
8 (ILMP1) Insuficient entry _MONPNT2
Aeroelastic Analysis - MONPNT2 - SFM 300
The message:
SYSTEM FATAL MESSAGE 3008 (ILMP1) Insuficient entry _MONPNT2
can be produced if a MONPNT2 bulk data entry invokes an element that is
connected to the highest numbered grid point in the model.
Avoidance: Do not select an element on a MONPNT2 that is connected to the
highest numbered grid point in the model. Else renumber the grids associated
with the element so that the grid is not the highest in the model.
1-25797677
RMG2)
2005.5.2
Heat Transfer - VIEW, RADSET - SFM 3002 (
When the number of cavities defined on a RADLST entry exceed the number of
cavities specified on the RADSET entry the following fatal message will be
issued:
*** SYSTEM FATAL MESSAGE 3002 (RMG2)
EOF ENCOUNTERED WHILE READING DATA BLOCK EST
SUBROUTINE RMG2
0FATAL ERROR
1-25801752
2008.0.0 (MD R3)
6062 (DBC), Poor Message
(FILE 101) IN
Postprocessing - DBC, PARAM,POST,0 - SFM
If the XDB size is exceeded the following fatal message is issued.

*** SYSTEM FATAL MESSAGE 6062 (DBC)
*** DIOMSG ERROR MESSAGE
6 FROM SUBROUTINE WRTLST
OVERFLOW OF DICTIONARY PRIMARY INDEX FOR DATA BASE UNIT
1.
This message should be improved to instruct the user to increase the default
RECL for the xdb file on an ASSIGN statement.
1-25860601
pened by Ani
SOL 700 - Does not work on SunOs - duplicate see 1-25836331 o
SOL 700 does not work on Solaris and Primepower in MD Nastran 2006r1.
is no avoidance.
The f06 file will contain the message:
Running MSC.Dytran LS-DYNA step 1
*** Elapsed Time - step 1: 0.0u 0.0s 0:00 0% 0+0k 0+0io 0pf+0w
There
Error(s) occured during step 1

- See file: jid.dytr_prep.out
- Search for string: *** Error
*** ISHELL PROGRAM '/local/msc2006t2/dyna/solaris/run_dytran' COMPLETED ***
The jid.dytr_pre.out file will contain the message:
ld.so.1: dytran-lsdyna: fatal: /local/msc2006t2/dyna/solaris/libfui.so.2: wrong
ELF class: ELFCLASS32
Job cre.5362 on delagoa: received signal KILL.
1-25895411
2005.5.2
Miscellaneous - INPUTT2 - ILP-64 version,
Akusmod Interface Fails with UFM 1206 (INPTX2)
Nastran ILP-64 systems (mode=i8) will fail reading the Akusmod "Fort.70"
coupling matrix with USER FATAL MESSAGE 1206 in INPTX2.
compile read70
alter 'inputt2',''
INPUTT2 /CASE0,CASESTR,CASEWET,CASELU,CTRFLDA/-1/IUNIT//
s,n,name1/s,n,name2/s,n,name3/s,n,name4/s,n,name5//
'akmlist'/'akmlist'/'akmlist'/'akmlist'/'akmctrf' $
alter 'inputt2'(2),''
INPUTT2 /casep,,,,/0/IUNIT////////'akmpanel' $
INPUTT2
/omegaz2,,,,/0/IUNIT////////'akmomega' $
INPUTT2
/case2ab,,,,/0/IUNIT////////'akmlist' $
INPUTT2
/omegaz3,,,,/0/IUNIT////////'akmomega' $
INPUTT2
/case3ab,,,,/0/IUNIT////////'akmlist' $
1-25925548
2007.0.0
for the BEND option
Elements - PCOMP yields Incorrect results
When the BEND option is added to the pcomp entry, the generated mat2 entry has
the Gij terms for membrane instead of the Gij terms for bending .
1-25945741
2008.0.0 (MD R3)
for modal preload analysis.
Nonlinear Analysis - EKE is not available
EKE is not available for a modal preload analysis in SOL 106.

Avoidance: Supply a dummy linear element
1-25986051
2007.0.0
Superelements - SFM 3007 (BNDSPC), BNDSP3
A job with many superelements may fail with the following error message:
*** SYSTEM FATAL MESSAGE 3007 (BNDSPC)
ILLEGAL INPUT TO SUBROUTINE BNDSP3
Avoidance: Possible DMAP avoidance is to test for the presence of coordinate
systems and/or SPC's on boundary points of the superelement. If neither of
these exists, the call to the BNDSPC module may be skipped with DMAP as neither
YS nor USET is updated.
1-26047321
2007.0.0
44 (DSAD13) Issued in error
The following error message may be issued in error when a DRESP1 requests a
CFAILURE response with item code 7 (interlaminar shear) and this is the last
response applied to the element.
*** USER FATAL MESSAGE 7544 (DSAD13)
DRESP1 ID 7 IS A CFAILURE RESPONSE WITH ITEM CODE 7: INTERLAMINAR
STRESS/STRAIN.
USER INFORMATION: THIS RESPONSE IS BEING APPLIED TO PLY NUMBER
7, WHICH IS THE FINAL PLY. INTERLAMINAR STRESS/STRAIN
RESPONSES ARE NOT AVAILABLE FOR THE FINAL PLY
USER ACTION: DO NOT APPLY ITEM CODE 7 TO THE FINAL PLY
User Information: Responses are ordered by element id, ply no and item code.
If the last cfailure response for an element has item code 7, the above fatal
message is produced regardless of the ply no. it is associated with. The
message is only correct when the ply is the highest numbered ply for the
element.
Avoidance: An avoidance is to request an additional CFAILURE response for the
element that has a higher item code (8 or 9) or is applied to a higher numbered
ply than the item code 7 request.
1-26122929
uter
2008.0.0 (MD R3)
Restarts - UFM 4276 on Digital Alpha comp
An error in the restart module may cause restarts to fail on Digital Alpha
computers. It is believed that there is an error in an nddl description but
the exact entry causing the problem is not known.
The alpha platform is
dropped so this problem has been mark fixed in version 2008.
Avoidance:
Execute a cold start.
1-26140321
Transient Analysis - IC - UFM 5423 (SADD5)
A modal transient analysis, SOL 112, that specifies an initial condition of the
form:
IC(statsub,diffk)=
may fail with the message:
ATTEMPT TO ADD INCOMPATIBLE MATRICES
FILE#
COLS
ROWS
TRAILER FOR ICSTSBYY IS
101
1200
TRAILER FOR ICSPCD
102
1200
FORM TYPE NZWD DENS

2
2 2400 10000
2 2400 6667
IS
Avoidance: Insert the following DMAP alter or use SOL 109.

compile semtran
alter 'call xadd5.*icphysyy,icspcd,,,',''
add icphysyy,icspcd/icphysy1 $
alter 'call xadd5.*icstsbyy,icspcd,,,',''
add icstsbyy,icspcd/icstsby1 $
1-26152834
2005.5.2
Aeroelastic Analysis - AEUXREF - Referenc
e stability derivatives incorrect if aeuxref=trim
If the user puts "aeuxref=trim" in the case control for a sol144 analysis, the
resulting stability derivatives for the reference point will be wrong.
1-26411375
2008.0.0 (MD R3)
Nonlinear Analysis - NLPARM Defaults diff
er with BLANK continuation vs No Continuation
PARAM,NTOL provides incorrect values for the error tolerance when the NLPARM
continuation entry is included and the EPSU, EPSP, AND EPSW fields are blank.
Avoidance: Either explicitly set the error tolerances or delete the NLPARM
continuation entry.
1-27310471
2005.5.2
HP IA64 V2005.5.0 (a.k.a 2005r3)
Performance - DCMP - Poor Performance on
The performance in the DCMP module of Version 2005.5.0 HP IA-64 systems may
be severely degraded. Since this is a performance critical module, MSC
recommends that the analysis executable be replaced.
A corrected executable
may be found on the product update site at:
1-27318160
2007.0.0
ncorrect direct shear stresses
Elements - PBMSECT - Arbitrary Section, I
The direct shear stresses are off by a factor of the area. The forces sent to
the routines that calculate cross section stresses are inadvertantly divided by
the area prior to the stress calculation.
1-28171504
2008.0.0 (MD R3)
of PBAR in QRG
Documentation/QRG - description for K1/K2
Remark 5 under the QRG description for the PBAR entry should read transverse
shear stiffness times unit length instead of per unit length.
1-28310299
2007.0.0
, AUTOQSET- SFM 6143
Superelements - EXTSEOUT, acoustic cavity
When creating an external superelement with an acoustic cavity and

PARAM,AUTOQSET,YES the run may fail with SFM 6143. For example:
SYSTEM FATAL MESSAGE 6143 (UMRGE1)
SPECIFICALLY:
The number of columns in EXTDB is not equal to the size of the A-set
EXTDB : Rows=
248 by Cols=
33
278
Set0 (A-set)=
248
Set1 (COMP-set)=
30
Avoidance: Insert the folowing DMAP alter:
compile extout
alter 'MPYAD
INTEXTA,AA,'(,3),''
umerge1 usetx,extdb,,,/temp/'g'/'a'//1 $
1-28316191
2007.0.0
Aeroelastic Analysis - MONDPS1 - Output
missing in SOL 144 runs

The MONDPS1 feature was added in Version 2005R3. Due to a dmap error, the
prints associated with this entry are not produced in a static aeroelastic run.
User Avoidance: Insert the following dmap alter in the run:
compile mnpntdr list
alter 'aero'(3,-1)
IF ( DSP1=-1 and (statics or app='reig') ) THEN $
MPYAD
SDMPIVa,Ua,/UMONDISP/1 $
mppstatc casedr,dispmon,umondisp,//'MONDISP' $
ENDIF $ DSP1=-1
existing tpl deck msimpms.dat shows the affect of this fix. EHJ 5/24/2006
alter 'umondisp'(1,-1),'umondisp'(1,3)
1-31110515
Topology Optimization - MAT2 - Poor Message
In topology optimization, when a PSHELL entry references a non-supported

material such as a mat2 entry which is not, UFM 2042 is issued from routine
ifp10e and indicates an undefined material property id. The message should
indicate that the material is not supported in topology optimization.
1-31899071
2008.0.0 (MD R3)
es wrong eigen vectors in SOL 103
ACMS - MDACMS with PARAM,SPARSEDR,NO caus
MDACMS causes zero eigen vectors for all grids and all modes if
PARAM,SPARSEDR,NO is used.
GDACMS with PARAM,SPARSEDR,NO seems correct except the xdb problem reported as
Quality #1-31899102.
Avoidance:
compile modefsrs
alter 'if ( mdacms and',''
TYPE PARM,NDDL,CHAR8,Y,sparsedr $
if ( mdacms and ((sparseph='yes' and app<>'reig') or
(sparsedr='yes' and app='reig')) ) then $
1-31899102
Post-processing - param,post,0- Eigen vectors in xdb file are
wrong in SOL 103 GDACMS
Eigenvectors in the xdb file are wrong if GDACMS is used in SOL 103.
Avoidance: op2, f06, and punch files are correct
1-32732801
ge problems
2005.5.2
MDACMS - READ - Poor Performance for lar
Assumptions made inside the READ module are may be too conservative and may
result in poor performance in MDACMS for large models.
Fix was made to reigl0.F.
c if the mass matrix is small and dense, store it in core
IF (MSGLVL .GT. 0) WRITE(NF04,1111) N, IFILE(7), LCORE, LCORE/3
1111 FORMAT(' Reigl0: ',4i15)

IF (N .LT. 20000) THEN
c make this test first so as to not square N unnecessarily and have it
c overflow
ldm = ior( n, 1 )
mincor = ldm*ldm*iprec
IF (IFILE(7).GE.9000 .AND. MINCOR.LT.LCORE/3) THEN
DENMAT = LCORE - MINCOR - 5
DENMAT = IOR( DENMAT, 1 )
LCORE = DENMAT - 10
CALL GOPEN( IFILE, 0, RDREW )
MPTR = DENMAT
DO I = 1,N
CALL UNPACK( *54, IFILE, Z(MPTR) )
GO TO 56
54
CALL ZEROC( Z(MPTR), LDM*IPREC )
56
MPTR = MPTR + LDM*IPREC
END DO
CALL CLOSE(IFILE, 1)
1-32941641
2008.0.0 (MD R3)
- Wrong Answers
SOL 400 - TTEMP, TID, CROD, CONROD, CTUBE
If time dependent loads are defined on TTEMP entry in SOL 400 for CROD, CONROD,
or CTUBE elements wrong answers will result.
1-33238331
Optimization - mattx associated with a matx referenced by a d
vmrel1 - Wrong Sensitivies
If a dvmrel1 (or dvmrel2) references a matx entry (e.g., a mat1) that has an
affiliated mattx entry (e.g., a matt1) the senstivities will be wrong whenever
the value determined from the mattx entry differs from that given on the matx
entry.
User information: It has never been possible to design a material property that
varies as a function of temperature provide by a tablem1 entry. However, it
should be possible to support desiging a material property that is not a
function of temperature when other properties are a function of temperature.
For example, if the Young's module is a function of temperature, but the
density is not, it should be possible to design the density. Because of a bug,
the sensitivities in this case will be incorrect.
User avoidance: There is no avoidance except to not use temperature dependent
properties for any material id that has designed properties.
1-33441861
2008.0.0 (MD R3)
ge XDB with no results
ADAMSMNF - FLEXONLY=YES option gives lar
An analysis in Version 2006 or 2007 with ADAMSMNF FLEXONLY=YES may produce a

large xdb file that the direct results access code in Patran is unable to read.
Avoidance: The error may be avoided in some situattions by applying the
following dmap alter:
alter 'dbcapps'
dbcapp='reig
'
dbcapps='stat
'
1-33515609
External Superelements - No q-set - UFM 6962 (MATGEN)
An extseout SOL 103 run to output the acoustic-structure coupling matrix AAAX
in DMIG using the FSCOUP option, fails with the message:
*** USER FATAL MESSAGE 6962 (MATGEN)
ILLEGAL VALUE FOR PARAMETER 2 =
-1
Avoidance: Specify undocumented paramter PARAM,AGGPCH,YES or insert the

following alter:
COMPILE PHASE1B
ALTER 'IF ( SPLITFS )',''
IF ( SPLITFS AND NOQSET>-1 ) THEN $
1-33793531
2007.0.0
SOL 600 - Translation of BCBODY LINE sect
ion into CONTACT option is wrong if 8 or more points
When there are 8 or more points in the LINE section of a BCBODY the translation
of the BCBODY LINE section into the CONTACT option is wrong.
1-34254660
Nonlinear Analysis - CQUAD4 with offsets and MATS1 Plastic Ma
terial - Wrong Answers
An input file with plastic material properties where the highest stress is well
below the yield point fails to produce correct stress results when compared to
results without the MATS1/TABLES1 entries. SOL 106 and 400 yield the same bad
results. The problem is that the presence of a MATS1 entry turns off the
effects of the offsets.
1-34278877
2007.0.0
PBAR, PBEAM, PBEAML - Missing entries in punch file
When an optimization job includes both PBARL and PBAR entries and PBAR
properties are being designed, no updated PBAR entries are written to the
punch file at the end of the design. This shows up either with the
DESPCH/DESPCH1 request or the ECHO=PUNCH(NEWBULK) request.
Avoidance: Add a dummy pbrsect entry if the input deck has PBARL (or dummy
PBMSECT if has PBEAML). An example as follows
POINT
POINT
set1
pbrsect
80001
0.0
80002
1.0
80003 80001 80002
80004 1
OP
OUTP=80003,t=1.0
0.0
0.0
1-34626031
2007.1.0
Parallel Processing - SYSTEM(107), PARALL
EL -Shared Memory Parallel is not functioning on Windows 64
Shared Memory Parallel is not functioning on Windows 64 in MD Nastran R1.
1-34778999
2007.0.0
to fail without any messages.
SOL 600 - CBUSH1D element causes SOL 600
The CBUSH1D element causes SOL 600 to fail without any messages.
1-34831285
2007.0.0
Aeroelastic Analysis - Labelling for iner
tial derivatives in static aeroelasiticity is incorrect
The trim results for rotational accelerations currently show units of

length/s/s when PARAM ANITS=1.0 (default) is used. This should be radians/s/s
When PARAM AUNITS has some value other than 1.0, the rotational accelerations
are labled as LOAD FACTOR. This should be radians/s/s_per_g
1-34885331
2006.0.1
fined Node Number
SOL 700 - BSURF - Translation Error, Unde
A BSURF entry with many elements may result in the dytran-lsdyna executable
failing due to a translation error. The error message will indicate:
0 *** Error undefined node #
280
0
0
1.000E+00
1-34885375
ectly
0 near input line

3275
0 0.000E+00 0.000E+00 1.000E+00
2007.0.0
SOL 700 - CTETRA10 - Not translated corr
CTETRA10 is not supported in SOL700. If inlcuded the translation will cause an

error in the explicit solver.
1-34974981
2007.0.0
or Floaing Point Overflow in xqd4pd
SOL 400 - QUAD4, PARAM,LGDISP - UFM 4551
SOL 400 with CQUAD4 elements and PARAM,LGDISP may fail with UFM 4551 or a
floating point overflow in xqd4pd.
1-34997021
in TA1
2007.0.0
Dynamics - PARAM,AUTOQSET,YES - SFM 3001
If PARAM,AUTOQSET,YES is requested with nonstructural mass specified on the

NSM* entry then the run will terminate with:
9 DOES NOT EXIST.

compile phase1dr
alter ' ta1 ',''
TA1
1-35331198
2007.0.0
c-set - SFM 5423
mpts,ECTS,EPTS,BGPDTS,SILS,ETT,CSTMS,
dit,ectas,eht/
EST,,GEI,GPECT,,vgfd,ditid,,nsmest/
LUSETS/-1/S,N,NOSIMP/1/S,N,NOGENL/0///
s,n,freqdeps/shldamp/s,n,mge/nsm $
Superelements/Acoustics - PARAM FLUIDSE,
A model with PARAM,FLUIDSE and some or all of the fluid superelement's

boundary is in the c-set then the run will fail with:
*** SYSTEM FATAL MESSAGE 5423 (MPYAD1)
FILE#
COLS
ROWS
FORM TYPE NZWD DENS

2
2 1212 9665
2 1838 10000
TRAILER FOR MOT1
IS
101
313
606
TRAILER FOR GOQ
IS
102
10
919

0
0
TRANSPOSE FLAG IS 1
Avoidance: Insert PARAM,MHRED,NO or insert the following DMAP alter:

compile semr3
alter 'if (mhred='(2),''
IF ( MHRED='YES' AND NOT(FLUID) ) THEN $
endalter
1-35436091
2007.0.0
2nd rigid body represented by NURBS
SOL 600 - BCBODY to CONTACT is wrong for
The 2nd (and perhaps all except the 1st) rigid body represented by NURBS is
wrong. The Nastran-to-Marc translator does not write the "data" section from
BCBODY to CONTACT. Note that the translation of the "application region"
section (i.e., NURBS section) is correct for all the rigid bodies.
1-35546885
rong Answers
2007.0.0
Eigenvalue Analysis - OMODES, RESTART - W
The OMODES Case Control command is ignored on restart.

compile super3
alter 'call sedisp'(,-1)
delete /UG,QG,QMG,OL1S,gpke $
endalter
1-35665271
2007.0.0
Aeroelastic Analysis - MONPNT2 results mi
ssing when AECONFIG request is present - UFM 2170 (PARTN2)
A MONPNT2 bulk data entry in an input file that also contains an AECONFIG case
control command produces the following error message:
*** USER FATAL MESSAGE 2170 (PARTN2)
BOTH THE ROW AND COLUMN PARTITIONING VECTORS ARE PURGED AND ONLY ONE MAY
BE.
0FATAL ERROR
User Information: This is caused by a datablock qualifer not being set.
User Avoidance: The easiest avoidance is to omit the AECONFIG case control
command so that the default value of AECONFIG=AERO2GSD is used.
:
1-35683049
2007.0.0
namics - RGYRO, UNBALNC - SFM 3001
Nonlinear Transient Analysis with rotordy
If there are multiple subcases in SOL 129 with RGYRO command and UNBALNC loads
then the run may fail with SFM 3001 for UNBVECD.
compile nltran
alter 1
file UNBVECD=save $
alter 'call gyrotran'
DELETE /UNBVECD,,,, $
endalter
1-35833199
2008.0.0 (MD R3)
BRSECT - SFM 4276, EC 7777
Optimization/Design Sensitivity - DOM9, P
A SOL 200 analysis with arbitrary beam (PBRSECT) failed in the DOM9 with
SYSTEM FATAL MESSAGE 4276 Error Code 7777
1-35917921
2007.0.0
Case Control - Scale Factor applied to P2
G lead to UWM 2070, followed by UFM 300
Attempting to apply a scale fact to P2G, (i.e. P2G = 1.25*PAX) may lead to user
fatal message 300 in the case control section.
1-35963377
ACMS - DOMAINSOLVER - UWM 7795 refers to obsolete methods "M
DMODES", "GDMODES", "FDMODES"
"MDMODES", "GDMODES", "FDMODES" are still used in output messages (these are
v2001 heritage domainsolver terms), yet the DOMAINSOLVER terms have been
updated to STAT, MODES and FREQ, with partitioning options DOF, GRID, and FREQ.
*** USER WARNING MESSAGE 7795 (PREDRV)
AUTOMATIC MODEL PARTITIONER WAS UNABLE TO PARTITION THE MODEL.
USER ACTION:
1. SELECT A DIFFERENT NUMBER OF PROCESSORS OR RUN THE JOB SERIALLY,
OR
2. IF DOMAINSOLVER MDMODES WAS SELECTED, THEN SWITCH TO DOMAINSOLVER
GDMODES, ACMS OR FDMODES.
^^^ SYSTEM FATAL MESSAGE 9130 (MDMODES)
^^^ AN ERROR HAS OCCURRED WHILE CREATING THE PARTITIONS,
THE PERMUTATION
MATRIX AND THE MAPS IN PRESOL, WHICH
ARE NECESSARY FOR MDMODES. THE READ MODULE WILL BE EXECUTED IN PARALLEL
USING FDMODES INSTEAD OF MDMODES.
1-35970568
2008.0.0 (MD R3)
3-1 GEOM/GRID option
Documentation/ QRG - DOMAINSOLVER - Table
Table 3-1 under the QRG documentation for the DOMAINSOLVER commdand refers to
the GEOM option. This should be the GRID option.
1-36038197
von Mises.
Transient Response - XYPUNCH has a default of MaxShear, not
If a transient response analysis requests stress printout and also xypunch

stress output for item code 9, 17, the xypunch stress output will be
von Mises stress, because the default for the stress printout in the .f06 is
von Mises. However, if printed output is not requested the XYPUNCH output will
be Max Shear.
The default XYPUNCH stress will be changed to von MIses to match that of
printed output.
1-36066967
2008.0.0 (MD R3)
Optimization - SOL 200 with SE and TEMP(L
OAD) - UFM 3003 (SDR2) or (SSG1) Data Block ETT
SOL 200 with superelements and analysis = buck and temperature loads with
SCR=NO may fail in data recovery with

0FATAL ERROR
or with SCR=YES, may fail with:
NOTE SCR=NO is more efficient for design optimization with SE because the SE
does not have to be recomputed and re-reduced at each cycle if there are no
design variables in the SE.
compile update,list $
alter 'gp3','' $
IF ( NOT EXTER ) GP3,
GEOM3s,BGPDTS,GEOM2s,EDT,UGH,ESTH,BGPDTH,CASEHeat,mpts,/
SLT,ETT/0/0/0 $
compile desinit $
alter 'lpflg = 0' $
tabpt slist,emap,,, // $
alter ' sdsa '(,-1) $
if ( seid=0 ) then $
alter ' sdsa ' $
else $
desvar = 0 $
dresp = 0 $
endif
1-36079438
2005.5
Composites - PRTPCOMP (sys 361) ignored
if "MEM" option used on PCOMP - Extra Output
If PCOMP has "MEM" option, the equivalent PSHELL/MAT2 are printed regardless of
the PRTPCOMP value
1-36316035
ets, ZOFF
2007.0.0
Documentation/QRG - CQUAD4, CTRIA3 - Offs
Remark 6 of the QRG CQUAD4 and CTRIA3 description is in error. For CQUAD4 and
CTRIA3 with offset (due to ZOFFS and/or unsymmetric plies and/or z0 defined on
PCOMP or PCOMPG) the differential stiffness is incorrect. Hence solutions with
the need for differential stiffness (dynamic analysis with prestress, linear
and nonlinear buckling) will produce incorrect results. However solutions with
nonlinear geometric behavior (param,lgdisp,1) will produce correct results when
the solution has converged. Please note that QUADR and TRIAR with offset will
give incorrect results in any case.
1-36462622
2008.0.0 (MD R3)
and MFLAG=0 is missing
Documentation - QRG - PFAST - case MCID=0
Remark 5 under the PFAST description in the QRG should be change to read:
If MCID>=0 ... instead of MCID>0 ...
1-37202949
2008.0.0 (MD R3)
Documentation/QRG - MCFRACTION - UWM 3001
A request of MCFRACTION output for a SET that contains no degrees of freedom in

the analysis set, will result in the message:
*** SYSTEM WARNING MESSAGE 3001 (MCFRAC)
THE INPUT DATA BLOCK NAMED RPHMCS AT POSITION
5 DOES NOT EXIST.
For example:
SET 98765 = 61/t1
SET 88765 = 0.1,0.2 $
mcfraction(structure,print,punch,solution=88765,
sort=absd,key=fraction,filter=0.0,null=12,
items=(fraction,scaled)) = 98765
where t1 of grid 61 is constrained in the s-set will result UWM 300.
1-37227076
2007.0.0
correctly applied
SOL 600 - Loads in SOL 600 subcase get in
TIN - Do not re-open qualities that are already fixed. These two cases work
fine for MDR3. Please note that SOL 600 uses differential loads rather than
total loads for all versions up to and including MDR3. The distributed loads
form the first subcase are subtracted out and the new ones are added. For the
smalltest1 model since the loads are the same, the same load is subtraced and
added. The results are correct for both smalltest1 and smalltest2 - E.
Dickerson 7/11/2008.
For SOL 600, If the same load is applied in two subcases you must use
PARAM,MRDISCMB,1
At the request of Marc development, this parameter was
introduced together with an algorithm to combine distributed loads with the
same magnitudes. This algorithm fails in problems where just one distributed
load of the same magnitude is applied in two subsequent load cases. The
default for PARAM,MRDISCMB will be changed to zero for such loadings. The
avoidance is to apply slightly different distributed loads. It is unlikely
likely that In a practical problem with many loads of varying magnitude that
this problem will be encountered.
1-37426759
2007.0.0
Parallel Processing/Frequency Response Poor DMP Performance with multiple load cases
The code change was
For any SOL 111 modal frequency response analysis with multiple load cases, DMP
performance will suffer during MPI communication of the dynamic load matrix.
Avoidance: apply the following DMAP alter:
compile freqrs
alter 'DISUTIL ppfe', '' $
type parm,,i,n,iproc $
iproc=2 $
do while ( iproc<=nproc ) $
disutil ppfe,,,/ppftmp/iproc/-1/10 $ send to master
add ppfe,ppftmp/ppfx $
if ( iproc=nproc ) then $
equivx ppfx/ppf0/-1 $
else $
equivx ppfx/ppfe/-1 $
endif $
delete /ppftmp,ppfx,,, $ avoid ufm 1126
endif $
iproc = iproc + 1 $
enddo
endalter
1-37426959
2008.0.0 (MD R3)
points to port@IP_Address
Installation/Licensing - MSC_LICENSE_FILE
When auth points at 1700@ip_address the following fatal may occur:

*** USER FATAL MESSAGE (pgm: nastran, fn: validate_authorize)
authorize=1700@172.16.1.145
(Env: MSC_LICENSE_FILE)
Host "172.16.1.145" is unknown in this network.
1-37445491
SOL 600 - Stops without any message if not enough memory
A SOL 600 run using DDM may fail without any message if there is insufficient
memory available. The example problem failed without any message with ddm=2
but issued SYSTEM FATAL MESSAGE 3004 when run with DDM=4.
1-37590653
ith PBARL
2007.0.0
Elements - CBAR, PBARL - Incorrect mass w
With Nastran 2005.5, also known as 2005r3, if a PBARL is defined with non
structural mass, the mass of the element doesn't include the non structural
mass.
Avoidance: Activate the previous element formulation of pbarl with nastran
twbrbml=1
1-37706137
2005.5.2
BUCKLING - UFM 4016 (GETEMP)
Optimization/Design Sensitivity - TEMP,
A SOL 200 job with part superelements and temperature loads may fail with the
message:
^^^ USER INFORMATION MESSAGE 9049 (SEKDR)
^^^ SUPERELEMENT DIFFERENTIAL STIFFNESS GENERATION, ASSEMBLY, AND REDUCTION.
THERE ARE NO TEMPERATURES FOR FASTP ELEMENT 900001 IN SET 1051250
0FATAL ERROR
Avoidance: Add a TEMPD entry to the input.
Since this is in SOL 105, I am reaasinging it to Mike - EHJ 7/27/06
1-37797311
2007.0.0
Distributed Memory Parallel - SOL 103 ACM
S with DMP does excessive MPI - Poor Performance
DMP performance will be degraded when using ACMS with SOL 103 due to an MPI
broadcast of the full (A-set size) PHI matrix from Master to all Slave
processes. This broadcast should not be necessary.
compile modefsrs
alter 'if ( (acms or mdacms) and nproc',''

if ( (acms or mdacms) and nproc>1 and
not(fdmodes or app='reig') ) then $
alter 'if ( (acms or mdacms) and nproc'(2),''
if ( (acms or mdacms) and nproc>1 and
not(fdmodes or app='reig') ) then $
compile semodes
alter 'call modefsrs'
if ( procid>1 and mdacms ) then $
exit $
endif $
endalter
1-37948581
2007.0.0
DMAP - MATMOD Option 16 to process a KAA
matrix gives DMIG output with an invalid grid point ID
Use of MATMOD Option 16 to process a KAA matrix gives DMIG output with an
invalid grid point ID, making it impossible to subsequently use this DMIG
output properly.
1-37949081
2008.0.0 (MD R3)
SOL 700 - Names longer than 22 charachter
s for the Dyt.prep.out file cause error.
In SOL 700 names longer than 22 charachters for the dyt.pre.out file will cause
an error.
1-38453316
2008.0.0 (MD R3)
ing CBUSH forces with LGIDSP
Documentation/QRG - CBUSH - SOL 106, miss
In sol 106, nonlinear, with PARAM,LGDISP,+1 cbush forces are missing from the
output.
Avoidance: Request STRESS and the forces will be in the nonlinear stress block.
A comment should be added to the Quick Reference Guide:
10. In SOL 106 with PARAM,LGDISP,1 the force recovery is part of the nonlinear
stress recovery. This means that the FORCE request will not provide CBUSH
forces; instead, appropriate STRESS/NLSTRESS are required to obtain the
nonlinear force and stress in bush elements.
1-38620791
2007.0.0
Superelements - Restarts of external SE a
ssembly runs fail with SFM 4276 in the GP1 module
Restarts of assembly runs employing external SEs (using the EXTSEOUT feature)
fail with SFM 4276 in the GP1 module.
compile phase0
alter 'if ( not(noxsort) and not(selist)',''
if ( false ) then $
endalter
1-38982011
2007.0.0
S=BUCK - SFM 3001 CASEXX does not exist
If SOL 200 runs with a single subcase the ANALYSIS = BUCK, the following system
fatal message is produced:
*** SYSTEM FATAL MESSAGE 3001 (SEP3)

THE INPUT DATA BLOCK NAMED CASEXX
AT POSITION
1 DOES NOT EXIST.
This is caused by the fact that there is no subcase with ANALYSIS=STATICS to

obtain the static deflection to drive the buckling analysis.
User Information: In SOL 105, a buckling subcase without a statics subcase
produces the somewhat more meaningful message:
*** USER FATAL MESSAGE 4683 (LNNRIGL)
KDIF MATRIX NEEDED FOR EIGENVALUE ANALYSIS
User Avoidance: Add a static subcase to the input deck
1-39271221
ors
2007.0.0
Installation - Install notes have two err
The "Install Notes" have two errors:

1. The notes state that linux does not support SMP. Linux does support SMP
2. The notes state that 2005.5 runs on RedHat 7.3, RH 8, and SuSE 8. Please
change to it has been run on RedHat 9, RH 3, RH 4, SuSE 9, Fedora Core 2
1-39297485
2007.0.0
Superelements - Superelement with zero ma
ss in residual elements leads to UFM 9088 (SELG)
In superelement analysis, if there is zero mass in the residual elements, the
following error will be reported (attachment internal.dat)
^^^ USER FATAL MESSAGE 9088 (SELG)
^^^ PARAM,INREL,-2 IS PRESENT BUT NO MASS IS DEFINED.
Avoidances:
1) add a dummy grid to the residual with low mass.
or,
2) use param,inrel,-1 and SUPORT entry
or,
3) use the following dmap in V2005.5.0:
compile selg
alter 76,87 $ v2005.5.0
IF ( NULLMJJ=-1 ) THEN $
MESSAGE //' USER'/WRN/'MESSAGE 9088 (SELG)' $
MESSAGE //' PARAM,INREL,-1 or PARAM,INREL,-2 IS PRESENT BUT'/
' NO element MASS IS DEFINED for SEID='/seid $
MESSAGE //' USER INFORMATION: The loads will pass'/
' to the assembled residual for final processing and '/
' inertia relief calculations' $
ELSE $
compile statrs
alter 'nullqrr'
if (nullqrr=-1) then
message//'no mass present in residual processing of inertia relief'
message//'-- fatal'
exit
endif $
1-39313301
Documentation/QRG - RBE2A - Incorrect Example
The example under the MD QRG documentation for the RBE2A entry indicates an RID
entry of "R23". This will not work, it should be "MR23" as indicated in the
field description.
1-39313341
2007.0.0
Acoustic Analysis - Exterior acoustics wi
th DMP - ACFPMRESULT - Missing Output
If DOMAINSOLVER FREQ is requested with exterior acoustic analysis in sol108
then ACFPMRESULT data recovery will be missing output.
1-39507540
2007.0.0
ency dependent elements - SFM 5423
Frequency Response - DMP and ACMS - frequ
If DMP and ACMS are requested in frequency response with frequency dependent
elements, then the run may fail withSFM 5423.
compile freqrs
alter 'frrd1'
alter 'merge
merge
merge
alter 'DISUTIL
DISUTIL
DISUTIL
alter 'DISUTIL
DISUTIL
DISUTIL
alter 'DISUTIL
DISUTIL
DISUTIL
alter 'equivx
equivx
equivx
alter 'equivx
equivx
equivx
endalter
1-39801126
ption in QRG
,,,ppf,,'
,,,qsgf,,expand,/qsgfe/1 $
,,,qmgf,,expand,/qmgfe/1 $
ppfe,,,'
qsgfe,,,/qsgf0///-8 $
qmgfe,,,/qmgf0///-8 $
ypf1,,,'
qsgf,,,/qsgf0///9 $
qmgf,,,/qmgf0///9 $
ypf10,,,'
qsgf0,,,/qsgf2///3 $
qmgf0,,,/qmgf2///3 $
ypf10'
qsgf0/qsgf/-1 $
qmgf0/qmgf/-1 $
ypf12'
qsgf2/qsgf/-1 $
qmgf2/qmgf/-1 $
2008.0.0 (MD R3)
Documentation/QRG - SORT1 vs SORT2 descri
The description of SORT1/SORT2 in Remark2 of the QRG does not describe that for
Statics, ANY SORT2 request will result in all output in SORT2.
Proposed update: (highlighted by ***
2. The defaults for SORT1 and SORT2 depend on the type of analysis:
SORT1 is the default in static analysis, frequency response, steady state
heat transfer analysis,
real and complex eigenvalue analysis, flutter analysis, and buckling analysis.
transfer). SORT2 is
not available for real eigenvalue (including buckling), complex eigenvalue, or
flutter analysis.
If SORT1 is selected in a transient solution for one or more of the commands
ACCE, DISP,
ENTH, FORC, HDOT, MPCF, OLOA, SPCF, STRA, STRE, and VELO then the remaining
commands will also be output in SORT1 format. If SORT2 is selected in a
***static or **** frequency response

solution for one or more of the commands ACCE, DISP, FORC, MPCF, OLOA, SPCF,
STRA, STRE, and VELO then the remaining commands will also be output in SORT2
format.
XY plot requests forces SORT2 and overrides SORT1 requests!
1-40022971
ssing
2008.0.0 (MD R3)
SOL 400 - Superelements, data recovery mi
In a SOL 400 run where superelements are present, and the STEP history for the
residual structure runs NLSTAT and then NLTRAN, there will be no data recovery
for the superelement(s) for the NLSTAT STEP.
Avoidance:
Insert the following DMAP alter.
ECHOOFF $
ALTER 'IF.*NOCASRS1.*SEID','' $
IF ( (NOCASRS1>-1 OR APP='NLST') AND SEID=0 ) THEN $
ENDALTER $
ECHOON $
1-40036154
2007.0.0
MCFRACTION - Missing output or unexpected
output when degree of freedom not specified.
The MCFRACTION Case Control command produces unexpected results if the grid
point's degree of freedom is not specified as required in the set. For
example:
SET 1000=92
MCFRACTION(sort=absa,print)=1000
produces modal contribution factor output for grid 9 degree of freedom 2.
Specifying a grid 97 will produce no output without a warning message.
1-40041100
utput
2007.0.0
Buckling - STATSUB(BUCKLING) - Missing O
In sol 105 buckling analysis contains two buckling subcases that have different
preloads but the same buckling load, the second buckling subcase will be
skipped.
1-40102391
2007.0.0
results for AUTOMSET=YES
Superelements - AUTOMSET - Possible wrong
If rigid elements/MPCs connect DOF on the boundary of a superelement with

AUTOMSET=YES then wrong answers may be produced.
Avoidance: The following alter can be used to avoid the error --compile mce1s $
alter 'imm,ym','' $
mpyad imm,ym,/rinvym//-1 $
alter 'i11,yy','' $
mpyad i11,yy,/y//-1 $
The attached input data file demonstrates the error.
1-40254921
MEFFMASS - MEFFMASS with DMIG may lead to SFM 3007 (EFFMAS)
A run with a DMIG type superelement that requests MEFFMASS=ALL will fail with
the message:
*** SYSTEM FATAL MESSAGE 3007 (EFFMAS)
ILLEGAL INPUT TO SUBROUTINE MPYAD EN
0FATAL ERROR
1-40265587
Superelements - Incorrect Modal Complex Eigenvalues
Modal complex eigenvalue analysis using superelements produces incorrect

damping coefficients.
1-40401601
2007.0.0
Matrix Methods - Sparse decomp may hang d
uring the reordering in a specific memory range
It is possible for the sparse decomp to hang during the reordering phase
provided that all of the following conditions occur:
1) Either BEND or AMF reordering is specified (BEND is the default)
2) Grid compression is feasible (that is, the EQXIN, SILS, and USET tables are
available).
3) Enough memory is available for the grid compression
4) Not enough memory is available for BEND or AMF
The offending routine is DFMSYN, which, under these conditions, and only under
these conditions, tries to perform MMD
reordering by calling DFMMD1 with the wrong data structures.
Usually the job will hang, but it may also produce a segmentation fault or an
error message like:
DECOMP ORDERING METHOD CHOSEN: MMD, ORDERING METHOD USED: MMD
*** SYSTEM WARNING MESSAGE 6705 (DFMAGC)
LOGIC ERROR 2 IN SYMBOLIC PHASE OF SPARSE DECOMPOSITION
USER INFORMATION: PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE
REQUIRED IF THE MATRIX HAS NOT BEEN RESEQUENCED
PROPERLY
This error can be reproduced in released systems starting with v2001. Using
the tpl deck bst80a, the error can be reproduced
in v2001 and v2004 by specifying mem=1754kw, in v2005 by specifying mem=1865kw,
and in v2006R1 by specifying mem=2000kw.
The amount of memory needed to cause the error can be estimated from the
diagnostic output produced by setting sys166=2. For bst80a,
one sees the following message in the f06 file:
GRID MATCHING COMPRESSION USED:
NUMBER OF COLUMNS IN MATRIX
NUMBER OF NONZEROES IN FULL MATRIX
NUMBER OF COMPRESSED COLUMNS IN MATRIX
NUMBER OF COMPRESSED NONZEROES
If we let
IWFR = NUMBER OF COMPRESSED NONZEROS
N
= NUMBER OF COLUMNS IN MATRIX
NEWN= NUMBER OF COMPRESSED COLUMNS IN MATRIX
=
=
=
=
32015
654646
6403
50252
then if specify memory so that the USER OPENCORE (as reported in the f04 file)
is approximately
15*NEWN + IWFR + 9*N
the error should occur. This is not an exact formula, so it may be necessary
to alter the value a bit.
The avoidance is to specify enough memory so that USER OPENCORE (as reported in
the f04 file) is at least 17*NEWN + IWFR +10*N .
Another avoidance is to specify a reordering method besides BEND or AMF, by
setting sys206=8, or setting sys206=9, or setting sys206=2.
1-40506427
M 3034
2007.0.0
Eigenvalue Analysis - RIGID=LAGRANGE - SF
Lanczos eigenvalue problems with rigid=lagrange may fail with the message:
(BUCKLING).
1-40535203
2007.0.0
and SCR=NO - Wrong answers
Optimization/Design Sensitivity - BUCKLE
If running SOL 200 with ANALYSIS=BUCKLE and SCRATCH = NO, then wrong answers
occur. This is only detected by running a buckling solution using the output
from PUNCH NEWBULK feature. The eigensolution is different between the final
SOL 200 and NEWBULK SOL 105.
Avoidance:
either run the SOL 200 with SCRATCH = YES
or
insert this dmap alter
compile sekdr
alter 'DBSTATUS KDJJ,'(,-1)
delete /kdjj,,,, $
endalter
1-40553791
2007.0.0
SOL 700 - MATD024 & TABLEDR causes error
in d3hsp - TABLEDR has TABLE 0 that was not found
MATD024 & TABLEDR to define strain rate effect causes the following error in
d3hsp.
*** Error DYTRAN Input
TABLEDR has TABLE
0 that was not found.
1-40553852
or in d3hsp
2007.0.0
SOL 700 - KU field of MATDS08 casuses err
KU field of MATDS08 casuses an error in d3hsp.

%E *** Error DYTRAN Input
42
MATDS08 1
2
0.
1.
MATDS08 (MID =
1) - has wrong KU value 0.
1-40553875
2007.0.0
differ for each nodes
SOL 700 - PSHELL - Shell thickness cannot
If the thickness specified on a PSHELL entry is not same for all nodes of a
shell element element, it causes an error in d3hsp.
1-40553914
d3hsp
SOL 700 - BCPROP - Alternate format of BCPROP causes error in
The alternate format of the BCPROP entry to define optional thicknesses is not
translated to BCPROPC for dytran-lsdyna executuion and this leads to the
following error in d3hsp:
%E *** Error DYTRAN Input
187
+
0.04
1.
1.
invalid integer (0.04) in field 2
1-40558687
2007.0.0
Optimization/Design Sensitivity - ADS9P4
- SFM 3008 (UTMCOR), Insufficient Core
The following message should be improved to indicate the additional memory
required:
SYSTEM FATAL MESSAGE 3008 (UTMCOR)
MODULE = DOM9
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ADS9P4
PROGRAMMER INFORMATION: LOCATION KEY = ADS9P4
FATAL ERROR
Avoidance: Request more memory or use OPTCOD=DOT on the DOPTPRM entry
1-40638031
t
SOL 700 - DYTIMHS does not output an effective jid.dytr.d3thd
DYTIMHS is not effective by itself to output jid.dytr.d3thdt. DYPARAM,

LSDYNA,BINARY,D3THDT,real must also be specified or the jid.dytr.d3thdt output
will be empty.
1-40643851
2007.0.1
SOL 700 - Initial velocity is incorrect i
f analysis coordinate is defined in GRID
If analysis coordinate of GRID is defined using a local coordinate which is
based on another local coordinate, the initial velocity is incorrect in SOL
700.
For example:
GRID
2
TIC
1
CORD2R 1
.707107
CORD2S 2
1.
1.
2
1
2
0.
.707107 0.
0.
0.
45.
0.
0.
0.
1.
0.
1.
0.
0.
0.
0.
0.
0.
1.
1-40726454
2007.0.0
Optimization/Design Sensitivity - GPFORC
E, ESE sensitivities incorrect with TEMP(LOAD)
GPFORCE and Element Strain Energy response sensitivities are incorrect in the
presence of thermal loads.
1-40726656
2009.0.0 (MD R4)
Temperature Loads - TEMP - Missing Messa
ge, Unexpected Answers

If TEMP=xx is specified, but there is no TEMP ID xx in the bulk data, there is
no warning or fatal issued.
1-40803671
2007.0.0
Heat Transfer Analysis - SOL 101 153 or 1
59 - Rigid Elements result in UFM 5419 (CHKRGD)
If a heat transfer analysis contains rigid elements, the run will fail in
v2005.5+ with the message:
*** USER FATAL MESSAGE 5419 (CHKRGD)
RBE2 ELEMENT ID = 0, REFERENCES FLUID GRID POINT ID = XX.
Avoidance: The only avoidance is to replace the rigid connections with MPC
equivalents.
1-40956673
2006
not support a default value for DZ
Aeroelastic Analysis - SPLINE4 entry does
A blank DZ field on the SPLINE4 entry should result in a

does on the spline1,2 and spline5 entries. Currently, a
in a BAD DATA and an error in IFP. The documentation for
SPLINE1,2 and 4 entry need to be updated to reflect this
DZ value of 0.0, as it
blank DZ field results
this field on on
default.
Avoidance: Specify DZ=0.0 explicitly when no linear attachment flexibility is

desired.
1-40966401
nce
2007.0.0
Dynamics - PARAM,AUTOQSET - Poor performa
Poor performance may be experienced when PARAM,AUTOQSET,YES is specified and

structural (e.g., GE on MATi) or viscous damping (e.g., CDAMPi, CVISCi) are
present.
compile phase1b
alter 'smpyad.*rgt,bgg ,rgq,,,','smpyad.*rgq,k4gg,rgq,,,\/'(,1)
matmod k4gg,,,,,/nzk4,/12/s,n,nzk4/1 $
if ( nzk4>0 ) then $
partn
k4gg,nzk4,/k4xx,,, $ remove null columns/rows
partn
rgq,,nzk4/rxq,,,/1 $ and corresponding rows
partn
rgt,,nzk4/rxt,,,/1 $
smpyad rxq,k4xx,rxq,,,/k4qq/3////1////6 $
smpyad rxt,k4xx,rxq,,,/k4tq/3////1 $
delete /rxt,rxq,,, $
else $
smpyad rgq,k4gg,rgq,,,/k4qq/3////1////6 $
smpyad rgt,k4gg,rgq,,,/k4tq/3////1 $
endif $
if ( not beigrd ) then $
matmod bgg,,,,,/nzb,/12/s,n,nzb/1 $
if ( nzb>0 ) then $
partn
bgg,nzb,/bxx,,, $ remove null columns/rows
partn
rgq,,nzb/rxq,,,/1 $ and corresponding rows
partn
rgt,,nzb/rxt,,,/1 $
smpyad rxq,bxx,rxq,,,/bqq/3////1////6 $
smpyad rxt,bxx,rxq,,,/btq/3////1 $
delete /rxt,rxq,,, $
else $
smpyad rgq,bgg,rgq,,,/bqq/3////1////6 $
smpyad rgt,bgg,rgq,,,/btq/3////1 $
endif $
endif $ not beigrd
dbstatus mbqq//s,n,nombqq $
if ( nombqq>0 ) then $
if ( kdampx>-1 ) then $
add5
bqq,mbqq,,,/mbqq1 $
equivx mbqq1/bqq/-1 $
else $
add5
k4qq,mbqq,,,/mk4qq1 $
equivx mk4qq1/k4qq/-1 $
endif $
endalter
1-40966515
2007.0.0
Elements - Multiple element types with ma
ny property entries - Poor performance in TA1
If there are multiple element types and at least one element type has many
property entries then poor performance may be observed in the TA1 module
executed in subDMAP PHASE1A. This error can occur if there is a TOPVAR entry
present or there is a unique property entry assigned to each element.
compile phase1a
alter ' ta1 '(2,-1)
putsys(1,56) $
alter ' ta1 '(2)
putsys(0,56) $
endalter
1-41130517
2007.0.0
07 (DSAD) ILLEGAL INPUT TO SUBROUTINE DSAD6, UFM 6553
The message:
SYSTEM FATAL MESSAGE 3007 (DSAD)
appears when a scaled weight constraint is invoked in a subcase other than the
first. This occurs in combination with the message:
A WEIGHT RESPONSE HAS BEEN INVOKED BY THE DESSUB COMMAND IN SUBCASE
WHICH IS NOT THE FIRST SUBCASE.
22,
It is possible that this UFM will not cause the run to stop due to a
programming bug.
Avoidance: Constraints on weight or volume must be placed above the subcase
level or in the first subcase
1-41330851
2007.0.0
Optimization/Design Sensitivity - tpl tes
t dtrustr2 fails in DOM10 - SFM 4276 on AIX
An optimization job with an active Trust Region request may fail in DOM10 with
Avoidance: use the dmap alter below:

compile desopt
alter 'if ( trustR ) D',''
if ( trustR ) THEN
DBEQUIV DATABLK=(XINIT/XINITR,DESTAB/DESTABR,
OPTPRMG/OPTPRMGR,R1VALRG/R1VALRGR,R2VALRG/R2VALRGR,
RSP2RG/RSP2RGR,R3VALRG/R3VALRGR,
R1TABRG/R1TABRGR,CNTABRG/CNTABRGR,DSCMG/DSCMGR,
OBJTBG/OBJTBGR,RR2IDRG/RR2IDRGR,
RESP3RG/RESP3RGR,RQATABRG/RQATBGR,
DRSTBLG/DRSTBLGR,WMIDG/WMIDGR,
MODRPRG/MODRPRGR,GEOM1/GEOM1R,GEOM2/GEOM2R,
GEOM1QS/GEOM1QSR,GEOM2QS/GEOM2QSR,
GEOM4QS/GEOM4QSR,FRQRPRG/FRQRPRGR,
R1MAPR/R1MAPRR,R2MAPR/R2MAPRR,MTRAK/MTRAKR),
WHERE (DESITER=DESCYCLP AND WILDCARD) ,
CONVERT (DESITER=DESCYCLP+1) OVRWRT $
DELETE /RSP2RG,CNTABRG,R1TABRG,DRSTBLG,FRQRPRG $
DELETE /R1VALRG,R2VALRG,CVALRG,wmidg,r3valrg $
DELETE /RESP3RG,rr2idrg,wgtmg,RQATABRG,modrprg $
DELETE /DSCMG,DELW,DELV,DELB,DELF $
endif
1-41392631
2007.0.0
rrectly converted
SOL 600 - MARCPRNH and MARCPR99 cannot co
In SOL600, MARCPRNH and MARCPR99 cannot BE correctly converted to PRINT ELEMENT

by the CQUAD4 element.
For example the input cquad4.bdf with:
--param,marcprnh,1
param,marcpr99,-1
--cquad4.marc.dat:
--PRINT ELEMENT
STRESS CAUCHY STRAIN PLASTIC
PR999999
1 to 1
1 to 1
--This input file outputs only point1 and layer1.
1-41448459
2007.1.0
Single Point Constraints - AUTOSPC, INPUT
T4 - Incorrect Constraints when negative terms on diagonal
A matrix that is brought in via INPUTT4 and has negative numbers on the
diagonal may cause the wrong degrees of freedome to be constrained by the
AUTOSPC gpsp module.
1-41458341
2007.0.0
t datablock via dbview fails
File Management Section - APPEND - Outpu
The following simple deck fails in gnfist die to an append datalock geom1
that using the alias dbviewname VIEW0001
ASSIGN inputt2='../complex_107.op2',unit=25 status=old
acquire nddl
sol mysol
compile mysol list
subdmap mysol
TYPE PARM,,I,Y,IUNIT=25 $
INPUTT2 /,,,,/-1/IUNIT $
TYPE DB GEOM1,GEOM168 $
FILE GEOM1=APPEND $
DBVIEW VIEW0001=GEOM1 WHERE(AUXMID=1;AFPMID=2;DESITER=3;HIGHQUAL=0)
INPUTT2 /GEOM168,,,,/0/IUNIT////////'GEOM168' $
MAKENEW
GEOM168,,,,/VIEW0001,,,,/'GEOM1'/////'GEOM1' $
IFPINDX /VIEW0001 $
DBDIR $
end
cend
*** USER
DMAP
GEOM1 ,
USER
1-41585731

MODULE IFPINDX IS ATTEMPTING TO OUTPUT DATABLOCK
201 NAME =
ACTION: DELETE THE DATABLOCK, OR USE FILE GEOM1=OVRWRT
2007.0.0
Documentation/QRG - SOL 400 - PARAM,KDIAG
The description for user parameter KDIAG requires updating.

1. It does not include SOL 400 in the list of applicable solution sequences.
2. For SOL 400, it does not apply only to nonlinear statics but to nonlinear
transient analysis as well.
Suggested updated description:
Default = -1.0 (SOLs 106, 400 and 153 only)
In SOL 106 (nonlinear static analysis), 400 (both nonlinear static and
transient analysis) and 153 (steady state heat transfer), KDIAG may be used to
eliminate spurious mechanisms and singularities in the nonlinear stiffness
matrix. The absolute value of KDIAG will be added to some or all of the
diagonal terms in the nonlinear stiffness matrix according to the following:
If KDIAG < 0.0, then add the absolute value of KDIAG to the null diagonal terms
only. (Default)
If KDIAG = 0.0, then no action is taken.
If KDIAG > 0.0, then add the value of KDIAG to all diagonal terms.
1-41729401
2007.0.0
Documentation/SOL 600 - MARCOUT Defalt
The code was revised to make the default t16 file smaller, but the QRG was not
revised accordingly.
MD Nastran Quick Reference Guide ch.8 MARCOUT Remarks 6,
6. If this entry is not used, the following defaults are entered automatically:
E1, E11, E18, E27, E301, E321, E341, E401, E47, E48, N1, N2, N5, N35, N37, N39.
In MD Nastran 2006, if this entry is not used, only E301, E341, E47, N1, N2,
N35, N37, N38 and N39 are output.
1-41737627
2007.0.0
PARAM, MRFOLLOW
SOL 600/Documentation - QRG incorrect for
The electronic 2005r3 QRG indicates:

MRFOLLOW Integer, Default = 0, MSC.Nastran Implicit Nonlinear (SOL 600) only
MRFOLLOW=1, FORCE1, FORCE2, MOMENT1, MOMENT2 will act as non-follower forces.
This option must be entered if MSC.Marc versions prior to 2003 r1 are to be
used.
MRFOLLOW=0, follower forces entered using FORCE1, FORCE2, MOMENT1, MOMENT2 will
be mapped to MSC.Marc s new follower force option available starting with
MSC.Marc version 2003r1.
MRFOLLOW=-1, follower forces will be turned off even if requested to be on
using other options. This is sometimes necessary for multiple load cases where
pressures are applied to different elements in the different load cases.
==========================================
This is incorrect, the doucmentation should indicate:
==========================================
MRFOLLOW Integer, Default = 0, MSC.Nastran Implicit Nonlinear (SOL 600) only
MRFOLLOW=0, FORCE1, FORCE2, MOMENT1, MOMENT2 will act as non-follower forces.
This option must be entered if MSC.Marc versions prior to 2003 r1 are to be
used.
MRFOLLOW=1, follower forces entered using FORCE1, FORCE2, MOMENT1, MOMENT2 will
be mapped to MSC.Marc s new follower force option available starting with
MSC.Marc version 2003r1.
MRFOLLOW=-1, follower forces will be turned off even if requested to be on
using other options. This is sometimes necessary for multiple load cases where
pressures are applied to different elements in the different load cases.
==========================================
The actual action is opposite what the manual indicates.
1-41752101
2008.0.0 (MD R3)
Frequency Response - OLOAD is ignored in
a frequency response analysis when TSTEP is present
OLOAD is ignored in a frequency response analysis when TSTEP is present.
COMPILE SEMFREQ $ INVERSE FOURIER TRANSFORM OLOAD, SPCFO, AND MPCFO
ALTER 'CALL FDRMGEN'(2,-1) $
APP
= 'TRANRESP' $
ALTER 'CALL FDRMGEN'(2) $
APP
= 'FREQRESP' $
ALTER 'DELETE.*PPF.*PSF' $
IFT
PPFSAVE,CASEF,TRL,FOL/PP147,FOLXXX/IFTM $
MATMOD PP147,,,,,/PPF,/1/1//3 $
COMPILE SEdFREQ $ INVERSE FOURIER TRANSFORM OLOAD, SPCFO, AND MPCFO
ALTER 'CALL FDRMGEN'(,-1) $

APP
= 'TRANRESP' $
ALTER 'CALL FDRMGEN' $
APP
= 'FREQRESP' $
ALTER 'DELETE.*PPF.*PSF' $
IFT
PPFSAVE,CASEF,TRL,FOL/PP147,FOLXXX/IFTM $
MATMOD PP147,,,,,/PPF,/1/1//3 $
endalter
1-41808171
2007.0.0
Aeroelastic Analysis - FLFACT - Floating
point exception, divide by zero, subroutine FASORT
A divide by zero fatal message will occur for the pk or pknl methods when two
consecutive dynamic pressures (= 1/2 density * velocity**2) are the same.
User Avoidance: adjust the flfact input for densities and velocities to avoid
the duplicate dynamic pressure.
1-41822251
16 output
2007.0.0
Documentation/QRG - SOL 600 - PARAM,MARCT
The description of Quick Reference Guide(MARCT16) is not correct. It has been

updated for the MD Nastran R2 and MSC.Nastran 2007 releases.
1-41822276
ument
2007.0.0
Documentation/QRG - SOL 600 - MARCT16 doc
The QRG needs to be modified to indicate that MARCOUT should not be entered
when PARAM,MARCT16 is used.
1-41832822
2007.0.0
and missing reference to SPC2
Documentation/QRG - SPC Case Control Comm
The QRG description of the SPC case control command needs to be updated to
indicate that it can reference a SPC2 bulk data entry.
1-41883251
2007.0.0
ILP-64 AIX Fails
Matrix Methods - SMETHOD - CASI solver on
The element based iterative solver (CASI) will fail on IBM AIX platforms with a
Traceback similar to the one reproduced below. Note that this only occurs with
the ILP-64 version ("mode=i8").
Avoidance: A possible workaround is to rerun the job with mode=i4.
Traceback:
Offset 0x00000ca4 in procedure
casiFree
deleteFMatrix_159_128
pcgsl
pcglss
xqcasi_
itscas_
solvit_
xsem07_
xsemdr_
nastmon_
mainal
1-41884101
2007.0.0
not recognized by Casi solver
Matrix Methods - SMETHOD - CSEAM element
The casi element-based iterative solver interface does not currently allow the
CSEAM element.
1-41885454
2007.0.0
lement incorrectly translated.
SOL600 - PSHELL, CQUAD4 - Membrane only e
In the nastran bulk data a membrane only shell element is defined with a CQUAD4
entry with the MID1 field of the PSHELL entry defined, but MID2, MID3 and MID4
are left undefined. When SOL600 translates this type of element into a Marc
element, it uses type 75, a full shell element. This is incorrect, Marc's
membrane-only element is type 18.
1-41927461
rks 7
2007.0.0
Documentation/QRG - SOL 600 - BRKSQL Rema
Remark 7 of the Quick Reference Guide BRKSQL entry description has been updated
to reflect the actual code.
In MD Nastran 2006, if METH =1 and ICORD=0 or 1, an MSC.Marc t19 file will
automatically be produced.
If METH =0 and ICORD=0 or 1, an MSC.Marc t19 file not generate.
1-42002359
Answers
2007.0.0
Loading - TEMP(INIT), TEMP(BOTH) - Wrong
Specifying both TEMP(INIT) and TEMP(BOTH) can lead to wrong answers as follows:
1) if TEMP(INIT) and TEMP(BOTH) -> WRONG ANSWERS (Delta-T is wrong)
2) TREF will NEVER perform table lookup
3) If TEMP(BOTH) and TEMP(LOAD) are specified, only the last request will be
honored
4) In SOL 105 ONLY: If TEMP(BOTH) is specified in the subcase, it does not
perform
This condition will be trapped with a new fatal message beginning in version
2007.
USER FATAL MESSAGE XXX (IFP1D)
MULTIPLE TEMP(BOTH) OR COMBINATIONS OF TEMP(BOTH) AND TEMP(INIT) ARE NOT
ALLOWED.
1-42059473
2007.0.0
Matix Methods - SMETHOD - Casi iterative
solver does not support K2GG input matrix data
The casi element-based iterative solver interface does not does not support
K2GG input matrix data.
1-42074241
2007.0.0
Documentation/QRG - DOBJ2, DPMIN, FSDALP
and FSDMAX missing from DOPTPRM description
The 2005R3 QRG inadvertantly deleted fsdmax, fsdalp,dobj2 and dpminfrom the
DOPTPRM entry.
User Information: Refer to the 2005 Quick Reference Guide for information on
these parameters.
1-42173286
ran
Postprocessing - POST TOFILE - op2 file cannot be read by Pat
When POST TOFILE is being used to control the results output to the op2 file,
Patran or other postprocessors cannot read the geometry. This error is caused
by CASECCR being written before the results are output.
compile super3 $
alter 'OUTPUT2.*CASECCR','' $
1-42236771
converted
2007.0.0
SOL600 - MATHE-K, MOONEY - Not correctly
The values of MATHE-K(bulk modulus) is converted to the "coefficient of thermal

expansion" and the "bulk modulus" of MOONEY in the marc data.
The value of MATHE-Texp is disregarded.
[nastran.dat]
MATHE, 2, MOONEY, , 33.0E6, .0003, 2.5E-6, 70.5, .015
, 5.5E6, 1.0E6
, 4.0E6, 0.8E6
, 2.0E6
[marc.dat]
MOONEY
COMMENT, MATHE
2
1,
2,
5.500000E+06, 1.000000E+06, 7.770000E-07, 3.300000E+07, 8.000000E+05,
4.000000E+06, 2.000000E+06, 3.300000E+07,
1-42267596
2007.0.0
DMAP - MATPRN, DUPVH - SFM 4276, EC 3021
The following MATPRN caused EMG to fail with SYSTEM FATAL MESSAGE 4276 (READ)
ERROR CODE 3021
compile NONLIN LIST
alter 'EMG .*ESTNL.*UGNIX'(1,-1) $
MATPRN DUPVH// $
1-42405257
Optimization/Design Sensitivity - DRESP1, FORCE, STRESS(BILIN
) - Incorrect Item Code
A DRESP1 entry that references a force, stress, and/or strain item code for a
CQUAD4 element may use the wrong response if the FORCE output request is
different than the STRESS or STRAIN output request. For example STRESS(BILIN)
is requested and FORCE(CENTER) is requested.
1-42425397
2007.0.0
FM 2044, UFM 3007
Nonlinear Analysis - CGAP, TEMP(LOAD) - U
Nonlinear analysis with CGAP entries and TEMP(LOAD) may fail with the following
fatal messages:
DECOMP ORDERING METHOD CHOSEN: BEND, ORDERING METHOD USED: BEND
*** USER FATAL MESSAGE 2044 (NLCOMB)
UNDEFINED TEMPERATURE SET

104
ILLEGAL INPUT TO SUBROUTINE NLCETT
0FATAL ERROR
1-42507691
2007.0.0
SOL 600 - SPC Incorrectly Translated
In Versions 2005.5.2 and 2006.0.1 enforced displacement of SPC is not

translated correctly, though SPCD+SPC is correctly translated.
1-42792171
2007.0.0
SOL 700 - CBEAM - Orientation vector is n
ot correctly translated if BEAMOR is used to define it.
If BEAMOR is used to define the orientation vector of a CBEAM, it is not
translated correctly.
For example,
BEAMOR
1.
CBEAM 1910002 1000009 1000044 1000045
0.
0.
are translated as shown below into dyt.dat file.

CBEAM 1910002 1000009 1000044 1000045 1.00000
and it casuses Error in dytran-lsdyna as shown below.
%E *** ErrorMD Nastran Input 153733
CBEAM 1910002 1000009 1000044 1000045 1.00000
invalid integer (1.00000) in field 6
The correct translation for this example is:
CBEAM 1910002 1000009 1000044 1000045 1.00000 0.0
1-42803355
(DFMSYN)
2007.0.0
0.0
Matrix Methods - DECOMP, METIS - UFM 6413
If metis reordering is specified by sys206=8, and more than 2gb of memory is

given, the job will always fail with a message similar to:
*** USER FATAL MESSAGE 6413 (DFMSYN)
INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION
(METIS).
USER ACTION : INCREASE MEMORY BY AN ESTIMATED
524680801 WORDS.
1-42936851
2007.0.0
- SFM 3007 (DSAD) writh RMS or PSD responses
The message "SYSTEM FATAL MESSAGE 3007 (DSAD)" can occur when a SOL 200 job
contains DREPSP1 entries with RTYPE = PSDXXX and/or RMSxxx and all of the
computed response are zero. This typically indicates an error in the user
input.
Avoidance: Review the specification of the DRESP1 entries with RTYPE = PSDxxxx
and/or RMSxxxx to make sure that the requested quantities are non-zero.
1-43084871
2007.0.0
is not correctly converted
SOL 600 - CHEXA (with PSOLID and PLSOLID)
If a model contains CHEXA elements that reference PSOLID entries and others
that reference the PLSOLID entry, the input is not translated correctly and the
following message is issued:
--error message-** Severe Warning in SOL 600 trnslator - CHEXA must have 8 or 20 nodes to be
used in SOL 600
1-43300972
2007.0.0
Nonlinear Analysis - RFORCE and LOAD(wit
h negative scale factor) - NaN or UFM 4296 (NQD4D)
If a SOL 106 run has a LOAD bulk data that references an RFORCE entry with a
negative scale factor, either a "NaN" will occur during the first nonlinear
iteration or a fatal message will be issued for every quad element in the
model.
Avoidance: Avoid negative scale factors on the LOAD entry for the RFORCE id.
1-43365991
d in SOL 600
2007.0.0
SOL 600 - CBUSH1D element is not supporte
The CBUSH1D entry is not supported by SOL 600. This entry may cause the sol
600 translator to crash without issuing an error message.
1-43440601
2007.0.0
ignal 11, Overflow
Matrix Methods - DECOMP, Large Models - S
Large dense models over 3 million DOF may cause a signal 11 in DCMP. The error
is related to an integer overflow.
Avoidance: Submit with more or less memory
1-43448777
2007.0.0
Nonlinear Transient Analysis - CMS - UFM
1126 Module UMERGE1 outputtingt GOA which already exists
In V2005+, a SOL 129 model with CMS (QSETi) may fail with:
DMAP MODULE UMERGE1 IS ATTEMPTING TO OUTPUT DATABLOCK
USER ACTION: DELETE THE DATABLOCK, OR USE FILE GOA=OVRWRT
201 NAME = GOA
Also, if there are unused QSETi degrees-of-freedom then the run may fail with:
*** USER WARNING MESSAGE 6137 (UDSNRD)
0*** UNSUCCESSFUL MATRIX DECOMPOSITION.
*** SYSTEM FATAL MESSAGE 3007 (NLTRD2)
24
Avoidance: Insert PARAM,SMALLQ,1.e-10 and the following DMAP alter

compile nltran
alter 'call segoa'(,6)
delete /goa,,,, $
1-43465661
2007.0.0
ssive stress failure criteria
SOL 600 - MATF - Incorrect maximum compre
The maximum compressive stress in the x and y directions as specified on the

MATF entry which defines the failure criteria are translated incorrectly.
1-43537471
2007.0.0
Excessive Output
Aeroelastic Analysis - SPLINE6 - UWM 328,
SPLINE6 entries that do no explicitly define a continuation entry will produce

UWM 328 for each entry. This may lead to excessive output.
1-43604151
2007.0.0
Nonlinear Analysis - UWM 3057, UFM 3007,
for MATS1, NLELAST, TABLES1 w/o origin defined
For a material nonlinear run with MATS1 NLELAST and TABLES1, if the origin is
not defined on the TABLES1, then the model may go several decomps before
finally failing with the following message.
*** USER WARNING MESSAGE 3057 (NLITER)
MATRIX IS NOT POSITIVE DEFINITE.
This should be trapped as a user input error. The rule is defined in the Quick
Ref Guide, MATS1 Remark 3, bullet 2.
1-43735881
2007.0.0
with 2 contacts
SOL 600 - BCMOVE limitation when BCTABLE
The BCTABLE implementation in Nastran Version 2006.0.1 and earlier releases

does not allow no contact to be defined between a rigid and flexible body. This
prevent modelling the contact force from being released gradually.
1-43778881
2007.0.0
CH - Incorrect time label.
Transient Analysis - GPSTRESS, SORT2, PUN
Punched GPSTRESS SORT2 output from a transient analysis may contain incorrect
time labels.
1-43779004
GE1)
Modal Effective Mass - MODESELECT, MEFFMASS - UFM 6144 (MER
If MODESELECT is used with MEFFMASS using modal effective mass criterion for
mode selection then the run may fail with UFM 6144 (MERGE1):
*** SYSTEM FATAL MESSAGE 6144 (MERGE1)
SPECIFICALLY:
The number of rows
in EFMFACS0 is not equal to the number of non-zeros
in partitioning vector PARTVECS
EFMFACS0: Rows=
4 by Cols=
123
PARTVECS: Rows=
6
no. of non-zeros=
6 no. of zeros=
0
Avoidance: A temporary DMAP avoidance:
compile modefsrs
alter 'noefm' $
noefm=-1 $
A permanent solution to the problem will require code changes to the EFFMAS
module.
0FATAL ERROR
1-43807221
2006.0.1
Optimization - ANALYSIS=AERO, DRESP1- SF
M 3007 (DSAD) Illegal input to Subroutine DSAD14
The message "SYSTEM FATAL MESSAGE 3007 (DSAD) Illegal input to Subroutine
DSAD14" has been observed when DRESP1 entries with RTYPE=FLUTTER are attemped
and the flutter method is either PKS or PKNLS. In the case reported, the
message was a result of a program bug, but it could also occur properly if a
requested flutter root was not extracted.
User Avoidance: Use the PK or PKNL flutter methods
1-43834511
xport,by=1)
Optimization/Design Sensitivity - Missing output for DSAPRT(e
When keywords export and by=n (n>1) are specified on a DSAPRT Case Control
command , the sensitivity data only at the last design cycle is output to the
external binary file.
Avoidance: use the following dmap alter
compile exitopt list
alter 'OUTPUT2 D'(1,-1)
if ( dsexport) then
MESSAGE //'DESIGN CYCLE = '/DESCYCL1 $
if (zuzri1 = 0) then
MESSAGE //'=========DSAPRT START =========='/ $
$
alter 'OUTPUT4 D'
$
$ Output DSCMCOL And DSCM2 :
$
OUTPUT2 DSCMCOL,,,,//-1/IUNIT/'DSCMCOL'/OMAXR $
$
OUTPUT4 DSCM2,,,,//-2/IUNIT $
zuzri1 = 1
else if (zuzri1 >0 and not(lastcyc)) then
MESSAGE //'=========DSAPRT MIDDLE =========='/ $
OUTPUT4 DSCM2,,,,//0/IUNIT $
else if (zuzri1 >0 and lastcyc) then
MESSAGE //'=========DSAPRT END =========='/ $
OUTPUT4 DSCM2,,,,//-2/IUNIT $
endif
$
For QA test, need to ensure the sensitivity data is written out at each design
cycle (or given design cycle).
1-43943079
2007.0.0
agged with param,asing,-1
Matrix Methods - Singular matrices not fl
PARAM,ASING,-1 should cause nastran to issue a fatal message when a singular

matrix is encountered. However, when param,asing,-1 is specified along with
autospc=no, a high max ratio may be reported but the execution continues and
the offending degrees of freedom are not identified.
1-44040531
2006 (MD R1)
Documentation/SOL 700 User's Guide - Desc
ription of WALL/WALLGEO is incorrect.

The description of WALL/WALLGEO in the SOL 700 User's Guide is incorrect.
Avoidance: Refer to the MD Nastran Quick Reference Guide for the correct
description.
1-44225671
on is wrong.
2007.0.0
Documentation/QRG - RBE2/RBE2D descripti
The remark 4 of the RBE2D entry in the Quick Reference Guide shown below is
wrong. RBE2 without the FULLRIG option can simulate rotations.
4. For modeling a nodal rigid body that undergoes rotations, use RBE2D or
RBE2 with the FULLRIG option. Note that the RBE2 without the FULLRIG
option can not properly simulate rotations.
1-44265142
2008.0.0 (MD R3)
NOLIN - SPOINT - Wrong Answers
A NOLIN1 may produce wrong answers when it references an spoint that has its
displacement defined using an mpc equation.
Avoidance: Insert PARAM,ENFMETH,ABS.
1-44398314
2008.0.0 (MD R3)
s, PLOAD4 - Wrong Answers
Nonlinear Analysis - LOAD, Follower Force
In SOL 106, if a LOAD bulk data entry references a follower-force type loading
(e.g. PLOAD4) and another load set ID that does not exist, AND that missing
load set ID is LOWER than the follower force load set's ID, then the follower
force loading acts like a linear load and no longer follows the structure as it
deforms. If the missing load set ID is higher than the follower force's, then
the follower force acts as expected.
1-44744683
2007.1.0
Optimization/Design Sensitivity - MATT1,
MATT9,MATT8 - UFM 2018 (EMG) and/or Wrong Answers
1) When an optimization job includes more than one MATTi types (say MATT1 and
MATT9 or MATT1 and MATT8), the job may fail in EMG with UFM2018 or gives wrong
sensitivities.
2) When only a sigle MATTi entry exists in a SOL200 job and when some of the
property names on its asssoicated MATi entry is also being designed, the
resulting sensitivity coefficients may be wrong.
The avoidance: do not design MATi that is also associated with a temperature
dependent material entry (MATTi). This error is corrected in Version 2007.0.4
1-44800991
2008.0.0 (MD R3)
MATT9 - UFM 2019
Optimization/Design Sensitivity - MATT1,
A SOL 200 analysis with MATT1 or MATT9 entries will lead to USER FATAL MESSAGE
2019.
1-44900725
blapi.sl'.
2007.0.0
Installation - Unable to find library 'li
In Version 2005.5 with a MINIMUM install, the following error might occur when
attemting to run Nastran:
MSC.Nastran started Wed Oct 25 09:50:52 CDT 2006
/usr/lib/pa20_64/dld.sl: Unable to find library 'liblapi.sl'.

Avoidance: Select a full install
1-45244091
2)
2007.0.0
SOL 700 - PSHELLD* causes UFM 6440 (MODGM
PSHELLD* causes the fatal error shown below in the MODGM2 module.
*** USER FATAL MESSAGE 6440 (MODGM2)
ELEMENT
2620121 REFERS TO AN INVALID PROPERTY ENTRY.
USER ACTION: SPECIFY APPROPRIATE PROPERTY ENTRY.

0FATAL ERROR
Avoidance: Use the dmap alter below to skip MODGM2 module in SOL 700
MODGM2
IEPT.11,IGEOM2.6,IGEOM1.5,IGEOM4,XBGPDT,XCSTM,IMPT.10/
IGEOM2,IGEOM1Q,IGEOM2DL,IEPT,IMPT/
/OSWPPT/OSWELM/S,N,NSWPPT/S,N,NSWELM/S,N,SWEXIST/
S,N,NOGOMGM2/S,N,RGDEXIST/RIGID/ORIGID/S,N,NLRIGID/
LMFACT/PENFN/NONLNR/CWRANDEL/CWDIAGP/CFRANDEL/CFDIAGP/
S,N,NOEPT/S,N,NOMPT/S,N,NOGEOM1/SOFFSET/CSRANDEL/CSDIAGP $
IF ( NOEPT=-1 ) EQUIVX IEPT.11/IEPT/-1 $
IF ( NOMPT=-1 ) EQUIVX IMPT.10/IMPT/-1 $
IF ( NOGEOM1=-1 ) EQUIVX IGEOM1.5/IGEOM1Q/-1 $
IF ( NOGO=0 ) THEN $
IF ( NOGOMGM2 ) THEN
$ SPOT WELD CHECK RUN
EXIT $
ENDIF $ NOGOMGM2
ENDIF $ NOGO=0
1-45244156
2007.0.0
SOL 700 - MATD003 can not be used with PB
EAMD ELFORM=3 while it is allowed in LS-Dyna.
MATD003 can not be used with PBEAMD ELFORM=3 else the following error is output
to the dytr_prep.out file.
%E *** Error MD Nastran Inpu
pbeamd (= 999999) references wrong material type (=
3)
This combination is allowed in LS-Dyna.

1-45325022
RTPCOMP)
2008.0.0 (MD R3)
Documentation/QRG - System Cell 361(aka P
The description of the SYSTEM(361), PRTPCOMP does not state that ECHO=NONE will
suppress the printing of the PSHELL/MAT2 equivalent of the PCOMP/MAT8 when it
is set to a value of 1. If NASTRAN SYSTEM(361)=1 is used the user must remove
the ECHO=NONE to obtain the printed information in the f06 file.
1-45325136
2008.0.0 (MD R3)
to poor message - UFM 2042 (IFP6)
Materials - Missing material entry leads
A missing material entry in a large input file issued the following message:
*** USER FATAL MESSAGE 2042 (IFP6)

MISSING MATERIAL TABLE
11 FOR ELEMENT
*** USER FATAL MESSAGE 2042 (IFP6)
11 FOR ELEMENT
160
161
The message should have indicated that the ids were for the PCOMP not element
ids.
1-45605382
UFM 1126
2007.0.0
Complex Eigenvalue Analysis - CEAD Module
A complex eigenvalue analysis to obtain Campbell diagram data with the keyword
scr=no, fails in the CEAD module with:
*** USER
DMAP
CLAMA ,
USER

MODULE CEAD
202 NAME =
ACTION: DELETE THE DATABLOCK, OR USE FILE CLAMA=OVRWRT
Avoidance: Set scr=yes and the attached job runs. Or insert the following
DMAP alter:
compile sedceig
alter 'if ( gcase\>1 or ccase\>1',''
if ( gcase>1 or ccase>1 or ddval>0.
) delete /CPHD,CLAMA,lphd,, $
alter 'call super3'
if ( ddval>0.
) dbdelete datablk=(cphp,cphqp,cphqmp) ,
where(wildcard) $
1-45630951
- UFM 4392
2007.0.0
Miscellaneous - RSEQCONT or SYSTEM(357)
The NASTRAN keyword RSEQCONT=1 (a.k.a. NASTRAN SYSTEM(357)=1) should cause

Nastran to ignore all continuation fields. This is very advantageous when you
have lots of input decks or pieces of decks coming from different sources. For
the most part this feature works. However, in the case where this is an
include file, for instance a file with only MAT8 s and the second row is
missing (generally left out as it is often all zero) Nastran will issue a USER
FATAL MESSAGE 4392. To message doesn t list the MAT8. It will indicate the
problem is with the next entry it finds..
Avoidance:
Explicitly enter the continuation entry as follows
MAT8
1020009 2.0600+71.1300+6.340000 580000.00.0
+000001
MAT8
1020014 1.0030+71.0000000.0
1.0000000.0
+000003
0.0
.0
0.0
.0
0.0
.0
0.0
.0 +000003
needs to be changed to:

MAT8
1020009 2.0600+71.1300+6.340000 580000.00.0
+000001
+000001 0.0
0.0
MAT8
1020014 1.0030+71.0000000.0
1.0000000.0
1-46023346
2008.0.0 (MD R3)
Documentation/QRG - MONPNT3 error in QRG
Remark 1 of MONPNT3 description in the Nastran QRG indicates that MONPNT3 is
available for SOL 101, 144 and 146. This is incorrect, SOL 146 is not
supported.
1-46027846
effective.
2007.0.0
SOL 700 - DYPARAM,LSDYNA,HOURGLASS is not
DYPARAM,LSDYNA,HOURGLASS to control hourglass is not effective in SOL 700.

Avoidance: Use PARAM,DYHRGIHQ or DYHRGQH
1-46027901
DMP - DMIG, K2GG, M2GG - UWM 2070 (MTRXIN)
DMIG input is not supported in the geometric domain decomposition methods for
statics and normal modes.
This may result in jobs failing with the messages:
"*** USER WARNING MESSAGE 2070 (MTRXIN)
REQUESTED DMIG MATRIX xxx IS UNDEFINED."
"*** USER WARNING MESSAGE 3204 (SSG1)
UNABLE TO FIND SELECTED SET ( 311) IN TABLE (SLT ) IN SUBROUTINE (SSG1)."
"***** RECEIVED SIGNAL 15, ABORTING ..."
Avoidance: The avoidance is to use the matrix-based domain decomposition
methods by using one of the following Executive Section entries:
DOMAINSOLVER STAT (PARTOPT=DOF)
for statics or
DOMAINSOLVER MODES (PARTOPT=DOF)
for normal modes
1-46052930
71 (DPD2)
Optimization/Design Sensitivity - MFREQ with RANDOM - UWM 20
In SOL 200, with MFREQ and RANDOM, after the 1st design cycle the following
message is issued. This message appears to be superfluous and does not affect
the answers:
V2004 message
*** USER WARNING MESSAGE 2071 (DPD2)
DAREA SET
221 REFERENCED IN DYNAMIC LOAD RLOAD2 ENTRY
DEFINES NULL ENFORCED MOTION
V2005 message
EXCITATION SET
221 REFERENCED IN DYNAMIC LOAD RLOAD2 ENTRY
DEFINES NULL ENFORCED MOTION
1-46077402
SPC sets
111
111
External Superelements - EXTSEOUT - SFM 3200 BDYINF, Multiple
If EXTSEOUT is requested with multiple SPCs, then only the 1st set of SPCs will
be used to generate KAA/PA and the following fatal message will be issued:
*** SYSTEM FATAL MESSAGE 3200 (BDYINF)
LOGIC ERROR 29 ENCOUNTERED IN SUBROUTINE BDYINF
USER ACTION: REPORT THIS PROBLEM TO MSC CLIENT SUPPORT
0FATAL ERROR
Avoidance: Reduce each SPC set one at a time.: This error may occur for MPC
sets.
1-46095441
2007.0.0
SOL600 - BEAM SECT Error
If Type=ROD of the pbarl/pbeaml is specified, the Effective transverse shear

area (As) in the tranlated marc.dat input is wrong. The marc default is
As=A, the nastran default is 0.857*A(K=0.857 for MDLPRM,TWBRBML,0) or
0.9*A(K=0.9 for MDLPRM,TWBRBML,1). The effective transverse shear area of
marc.dat is 0.5*A.
The effective transverse shear area for marc is not the reference area factor
for shear(nastran) of the pbar/pbeam entry. If SOL600 data is K=0.9, marc.dat
should be As=K*A=0.9*A. However, the effective transverse shear area of
marc.dat is As=0.85*A.
1-46119514
Nonlinear Analysis - MATS1 Kinematic hardening or Combined ha
rdening - Wrong Answers
A SOL 106 quad4 model with MATS1 PLASTIC TABLES1 and von mises yield criteria
with the kinematic hardening rule (HR=2 on MATS1) will report a maximum
equivalent stress as the LIMIT1 (i.e., Y1 aka initial yield) even though the
loading increases beyond yield. The combined hardening rule (HR=3) will
continue to increase the equivalent stress, but it is not the same as Von Mises
stress above the yield point.
1-46245072
2007.0.0
ues with MFLUID and PARAM,VMOPT,2
Fluid Analysis - Wrong effective mass val
Modal effective mass output will be wrong with PARAM,VMOPT,2

COMPILE MODEFSRS
ALTER 'EFFMAS.*PHSA,LAMAS,'(,-1)
IF ( VMOPT=2 AND NOCEE>0 ) THEN $
CALL MGEN1 GGE
,USET
,GM
BEC
,CEE
,MEE
MEA
,MvAA
/
0
/NOA
/0
EQUIVX MvAA/MSAA/-1
ENDIF $
,GOt
,MEC
,goq
,msaa
,
/
/false $
1-46342723
2007.0.0 (MD R2)
External Superlement - SFM 4276 (FREAD) E
C 3002, with large include file - resourse issue
This External superelement models with extremely large include files may fail
with the message:
*** SYSTEM FATAL MESSAGE 4276 (FREAD)
ERROR CODE
3002 PID= 0
1-46486346
SOL 400 - BCPARA, FTYPE=6 - Core Dump by computing E8x97 Vol.
E when FTYPE 6 is used
SOL 400 with contact with FTYPE=6 (bilinear coulomb friction) specified on the
BCPARA entry may fail with a traceback.
1-46507156
2007.1.0
DBCMSG ERROR MESSAGE 22, SUBROUTINE ELM
BLK - Missing quad4 element stress/strain in xdb
The stress and strain output for quad4 elements may be missing from the xdb
when CFAST elements are present. The message:
DBCMSG ERROR MESSAGE
22 FROM SUBROUTINE ELMBLK
is a clue that this condition may exist.

The element type in DBCEQE needs to be changed from 55 to 68 for FASTP.
1-46561555
2007.0.0
when TOPVAR bulk data is present
Topology - CASI solver performance issue
SOL 101 SOLVIT module performance is adversely affected when the casi
element-based iterative solver is selected and
1) the model contains a large number of 10-node TET elements to be processed
in implicit mode (the SOLVIT default)
2) a TOPVAR bulk data entry is present that selects a PSOLID entry that is
referenced by CTETRAs
An avoidance is to remove the TOPVAR bulk data entries.
1-46581521
2007.0.0
Documentation/QRG - PARAM,AUTOMSET
In QRG of MD 2006r1, the description of PARAM,AUTOMSET is "MD Nastran Implicit

Nonlinear (SOL 600) only".
The description for other supported solutions such as SOL 101, is missed.
1-46584431
ly Translated
2007.0.0
SOL 600 - Multiple subcase SPCD Incorrect
In multiple subcase, the enforced displacement of SPCD+SPC1 with SPC not

translated correctly.
For SOL 600 do not enter SPC or SPC1 for dof's where SPCD is specified. For
the MD R2 and MSC.Nastran 2007 releases, if this is done the SPC or SPC1 will
be placed before the SPCD at the same dof in the Marc input so it will be
ignored.
1-46592824
2007.0.0
Aeroelastic Analysis - SOL 146 fails with
UFM 5423 when several subcases are defined
When several subcases are defined in SOL 146, Nastran fails with the message
UFM 5423:
FILE#
COLS
ROWS
TRAILER FOR SCRATCH IS
306
81
11
TRAILER FOR PHF
110
162
11
FORM TYPE NZWD DENS

2
22 9877
2
4
0
0FATAL ERROR
1-46727939
23 (MPYAD1)
IS
0
2008.0.0 (MD R3)
An optimizatoin job with a static SPCFORCE response may fail at MPYAD in

subdmap RESPSEN with the following message:
FILE#
COLS
ROWS
FORM TYPE NZWD DENS

2
8 1111
2 10000
TRAILER FOR QG
IS
101
36
TRAILER FOR SPAWQ
IS
102
16
TRAILER FOR QG1X
IS
103
16
36
174
TRANSPOSE FLAG IS 0

compile respsen
alter 'diagonal spaw2'(,1),''(,4)
dbview lcdvec0=lcdvec where(ncase=0) $
dbstatus lcdvec0//s,n,nolcdvec $
paraml lcdvec0//'trai'/6/s,n,density $
if ( nolcdvec>0 and density<10000 ) then $
merge
,,spawn3,,,,lcdvec0/spawq/1 $
endalter
1-46739381
2007.0.0
Matrix Methods - Integer overflows in spa
rse decomp yields incorrect diagnostic information
There are several places where diagnostics, such as the estimated number of
words in a factor matrix, or the actual number of words in a factor matrix,
exceed the maximum 32-bit signed integer, leading to overflow. The diagnostic
information printed in UIM 4157 is incorrect and can be misleading. In
particular, the MINIMUM MEMORY REQUIREMENT, the MEMORE REQR'D TO AVOID SPILL,
the SPARSE DECOMP MEMORY USED, SPARSE DECOMP SUGGESTED MEMORY, and the time
estimate are incorrect.
1-46823292
2007.0.0
OST=0 - incomplete xdb
Postprocessing - Nastran system(143)=2, P
If Nastran system(143) is specified to indicate that the bulk data is being

obtained via the dblocate statement along with PARAM,POST,0 then the resulting
xdb file will be incomplete. Specifically CSTM, EPT and MPT tables are not
written to the xdb.
compile phase0
alter 'if ( (POST=0 or post',''
if ( (POST=0 or post=-1) and
not(disofp and (parfreq or segmode) and procid>1) and
(not(sebulk) or ((disofp or procid<=1) and (pardcmp or acms)))
) then $
endalter
1-46863451
dary - UFM 7556
External Superelements - extseout(dmigpch), fluid on the boun
If the EXTSEOUT(DMIGPCH) option is used in the reduction run for the external
superelement with fluid/structure coupling and there are fluid poinits on the
superelement boundary (i.e., specifed on the ASETi entries), then the job will
fail in the assembly run with the following messages:
*** USER FATAL MESSAGE 7556 (SEPMAB)
*** USER FATAL MESSAGE 7556 (SEPMAB)
SUPERELEMENT xx HAS BOTH INTERIOR STRUCTURAL AND FLUID GRID POINTS.
USER ACTION: REASSIGN GRID POINTS AND/OR ELEMENTS SO THAT THE
SUPERELEMENT'S INTERIOR AND EXTERIOR POINTS ARE ALL
FLUID OR ITS INTERIOR POINTS ARE ALL STRUCTURAL.
Avoidance: Remove the fluid points from the ASETi entries or use one of the
other methods (e.g., dmigop2)
1-46887171
2008.0.0 (MD R3)
Rigid Elements - RBE3 - SFM 4276 EC 211
A model with an incorrectly defined RBE3 element that specifies a degree of

freedom as independent and dependent may fail with the following message rather
than issuing a proper user fatal message if param,automset, yes is specified.
BIOMSG: ERROR
211 HAS OCCURRED IN ROUTINE BLDPRD , FILE INDEX =
0.
STATUS =
0
*** SYSTEM FATAL MESSAGE 4276 (BLDPRD)
ERROR CODE
211 PID= 0
*** USER INFORMATION MESSAGE 4276 (BLDPRD)
THE DIAG 44 RELATED A NASTRAN DUMP IS SENT TO LOG FILE.
USER ACTION: THIS INFORMATION MAY BE USEFUL TO MSC FOR DEBUGGING YOUR
PROBLEM.
PLEASE CONTACT MSC CLIENT SUPPORT.
Avoidance: If the param,automset is not specified a fatal message identifying
the problem will be issued so that the user input error can be corrected.
1-46890597
2007.0.0
- SFM 3001 (MODACC)
External Superelements - CSUPER, DBLOCATE
If data recovery is attempted on an external superelement using the old-style

CSUPER type superelements and DBLOCATE with the user parameter EXTRCV, the
solution will fail with the following message:
*** SYSTEM FATAL MESSAGE 3001 (MODACC)
THE INPUT DATA BLOCK NAMED OL1M
AT POSITION
2 DOES NOT EXIST.
102 AND SUBROUTINE IS MODAC1
0FATAL ERROR
This is because the LAMA datablock which is DBLOCATEd from the system (AKA
assembly or residual) run is not equivalenced to the LAMA2 datablock in SEMODES
Avoidance:
Insert the following DMAP
COMPILE SEMODES NOLIST $
ALTER 'PERFORM PHASE III'(,-2) $
ELSE IF (EXTRCV>0) THEN $
EQUIVX LAMA/LAMA2/-1 $
ENDALTER $
1-47037011
2008.0.0 (MD R3)
t d200pe7 UFM 4646 (REIG)
Optimization/Design Sensitivity - TPL tes
TPL optimization test d200pe7 may produce an indefinite mass matrix on some
machines and fail during the eigensolution with the following message:
*** USER FATAL MESSAGE 4646 (REIG)
THE MASS MATRIX INPUT TO THE REAL EIGENSOLVER IS INDEFINITE.
1-47123337
External Superelements - EXTSEOUT- Statics with TEMP(LOAD),
OTM stresses incorrect in assembly
In static analyis, for EXTSEOUT external superelements, the assembly run with
TEMP(LOAD) will give incorrect results for Forces and Stresses on the external
superelement.
NOTE: The residual is correct and the displacements/spcforces on the external
are correct.
Avoidance: : Use PARAM,EXTDROUT and use the 3-step process to recover stresses
in the upstream superelements.
1-47128492
2007.0.0
ck) ec 20 - casi solver
Matrix Methods - SMETHOD - SFM 4276 (unpa
When no loads are applied in a linear statics sol 101 run and the casi solver
is requested (smethod = element) then the following error message appears in
the f06:
ERROR CODE
20 PID= 0
and the job fails. A more meaningful message should be output.
1-47162343
2007.0.0
DMP - DOMAINSOLVER STAT(PARTOPT=DOF) wit
h SUPORT and INREL - SFM 4276 in MRGCOL
SYSTEM FATAL MESSAGE 4276 in MRGCOL may be issued with SUPORT and interial
relief if used with DMP.
Avoidance:
compile sekrrs
alter '216'(,-1)
return $
compile sestatic
alter 'call phase1c',''
IF ( nouset>0 and NOT(NONLNR) and

) CALL PHASE1C KAA
,USET
,SILS
,EQEXINS
PA
,
,
,cases
drg
,
,
,
KLL
,LLL
,Dar
,ULL
mlr
,mll
,mrr
,QR
LRSEQ ,
,
,
/
SEKR
/SEMR
/SELR
/NOLSET
true
/ERROR /FIXEDB /NOQSET
'
'/TRUE
/false /false
false $
,maa
,
/
,mr
,PL
,
,
,
,
,
,
/NORSET /
/NOTSET /
/noa
/
alter 'or mdstat',''

if ( not(gmconv or pardcmp or NONLNR) ) then $
alter 'call statrs',''
IF ( NOT(NOPH2) AND (NOLLL>0 OR GETSYS(NP,216)<>0 or mdstat)
) CALL STATRS LLL
,KLL
,PL
,GPLS
,USET
,
SILS
,QR
,MATPOOL ,EQEXINS ,DRG
,
Dar
,GM
,GOT
,
,LRSEQ ,
EDTs
,CASES ,kgg
,kaa
,kelm
,
kdict ,bgpdts ,cstm
,mpts
,dit
,
est
,ys
,pg1
/
UL
,CRX
,PRECON ,epssex ,qrg
/
IRES
/INREL /LUSETS /NSKIP /NLOADS /
NORSET /NOA
/PVALOLD /ADPTINDX/PEXIST /
s,nullsol $
compile statrs
alter 'fbs '(2),''
call mdstat kll,pli,uset,sils,eqexins/
ul $
putsys(0,307) $ mergeofp=no -- deactivate distributed data recovery
endalter
1-47165003
2007.0.0
Installation - Support for Windows Vista
The Nastran Windows Installshield based installation does not recognize the
Windows Vista operating system and will not allow the installation to continue.
Avoidance: The only avoidance is to install nastran on another machine and
copy the installation to the Vista machine. Beyond the installation nastran
has been certified on Windows.
1-47167162
2007.0.0
nformation - time: error waiting
Miscellaneous - Linux RHE 4.0 - No Time I
MSC.Nastran or MD Nastran V2006.0.1 or ealier on linux, linux8664, or linux64

with the RHEL4 or SuSE 10 (or later) distribution, may have the following
message in the log file:
time: error waiting for child process: No child processes
The results of the analysis are correct. The timing information which is
normally in the log file is not there though.
Avoidance: Upgrade the "nastran" driver in $MSC_BASE/$MSC_VERSD/$MSC_ARCH to a
newer version of Nastran.
1-47218191
2007.0.0
Acoustics - PANEL PARTICIPATION FACTORS
are not correct if a panel does not coupled with fluid
ACOUSTIC PANEL PARTICIPATION FACTORS are not correct if one of panels does not
coupled with fluid as shown below.
Example:
4 panels are defined and a panel named "bottom" does not coupled with fluid.
Then PANEL RESPONSE of "bottom" should be zero, but it is not zero, and
"top_right" does not appear.
panel,bottom,2
panel,top_left,3
panel,top_cent,4
panel,top_righ,5
set1,2,16367,thru,16402
set1,3,16246,thru,16300
set1,4,16301,thru,16311
set1,5,16312,thru,16366
A C O U S T I C
N
P A N E L
P A R T I C I P A T I O
F A C T O R S
GRID POINT =
37,
TOTAL RESPONSE (R/I) = 3.05356E+00 /
-5.16123E-03, (M/P) = 3.05357E+00 /
359.90
LOAD FREQUENCY = 1.00000E+00, (SUBCASE
1, DLOAD =
4)
MAXIMUM PANEL RESP = 1.85680E+00 FOR PANEL = TOP_LEFT, SORTKEY = PANEL
SORT = ALPHANUMERIC
, FILTER = 1.00000E-16
PANEL NAME
PROJECTION
REL.
MAGNITUDE PHASE
BOTTOM
5.98435E-01 -358.97
TOP_CENT
5.98456E-01 -358.97
TOP_LEFT
1.85668E+00 -0.66
PANEL RESPONSE
PANEL RESPONSE
PANEL SCALED RESPONSE
REAL
IMAGINARY
MAGNITUDE PHASE
FRACTION
MAGNITUDE
5.98452E-01 9.71956E-03 5.98531E-01
0.93
1.95979E-01 3.22294E-01
5.98473E-01 9.71655E-03 5.98552E-01
0.93
1.95986E-01 3.22305E-01
1.85664E+00 -2.45973E-02 1.85680E+00 359.24
6.08035E-01 9.99933E-01
1-47236346
2007.0.0
Acoustic Analysis - CACINF4 - External Ac
oustics may yield incorrect Panel Participation Factors
External Acoustics may yield incorrect Panel Participation Factors
1-47324010
2007.0.0
T, ANAL=DFREQ or MFREQ - UFM 9104
Optimization/Design Sensitivity - EXTSEOU
If an external superelement is attached in a SOL 200 run with ANALYSIS=MFREQ or

DFREQ then the job may fail with:
^^^ USER FATAL MESSAGE 9104 (SELR)
^^^ THERE IS NO COUPLING BETWEEN INTERIOR POINTS
ITS BOUNDARY POINTS.
compile feafreq
alter 'sep2dr slist,emap',''
OF THIS SUPERELEMENT AND
sep2dr
slist,emap//
s,n,seid/s,n,peid/s,n,sedwn/s,n,lpflg/////
s,n,noup/s,n,scndry/s,n,extrn//'all'//-1/
s,n,partse/s,n,setype/s,n,reid $
alter 'if ( seid\>0',''

if ( seid>0 and not(extrn<>-1 or setype='extrna') ) then $
1-47446533
2007.0.0
10: bus error in Decomp
Matrix Methods - DECOMP - signal number
Default changes to system 219 may cause models that ran in previous versions to
fail in DECOMP module with the message:
Job aborting...
Avoidances include:
1) set sys219=32
2) set sys206=10
3) increase memory. The recommendation would be to use the value from
the UIM 4157:
MEMORY REQR'D TO AVOID SPILL =
20228 K WORDS
and increase it by at least 10%.

1-47649211
sued in error
2006.0.1
Aeroelastic Analysis - UFM 6975 can be is
The nonlinear trim algorithm regards it as an error if a supported degree of

freedom does not have any control surfaces that affect it. This is too
stringent in that other free parameters in addition to control surfaces can
control these degrees of freedom.
1-47688921
2007.0.0
PCD does not work
Documentation/QRG - SOL 600 - PARAM,MARCS
PARAM,MARCSPCD is documented in the QRG but is not supported.

documentation will be removed.
1-47711601
r in fa1pke
2007.0.0
The
Aeroelastic Flutter Analysis - Logic erro
When a singular mass matrix is used in flutter analysis, the job may fail with
the message
*** USER FATAL MESSAGE 3200 (FA1)
LOGIC ERROR DETECTED BY SUBROUTINEFA1PKE
1-47738693
2007.0.0
, NLTRD2 - SFM 1282 (SLCDRV)
1 = LOCATE CODE OR VALUE.
Nonlinear Transient Analysis - SE and CMS
A nonlinear transient analysis with CMS fails in the NLTRD2 module with:
*** SYSTEM FATAL MESSAGE 1282 (SLCDRV)
AN ATTEMPT WAS MADE TO OPEN A NON EXISTENT ASSOCIATED FILE ULNTH
,FNUMERIC, TO READ.
PROGRAMMER INFORMATION: CHECK THE NAME OF THE ASSOCIATED FILE TO OPEN.
The same message appears when only CMS is used without the SE.
1-47879121
2007.0.0
Matrix Methods - CASI Solver, TET10, TEMP
(LOAD) - Incorrect stresses CASI solver temperature loads
When TET10 elements are present in the input file, the default behavior of the
casi solver is to use the "implicit" formulation for the element. This means
that the element stiffness matrix is formulated internally by the casi
software. The nastran generated stiffness matrices are not used for the
TET10s. This is usually acceptable, unless the applied loads are
element-based, as in this case, where temperature loads are used. Furthermore,
in this case, in order to achieve stress-free thermal expansion, it is
essential that the element stiffness and loads be compatible. Implicit element
formulation should not be used. This can be achieved by placing a
PARAM,ITOPTX,4032 entry in the bulk data section.
Avoidance: insert PARAM,ITOPTX,4032 in the bulk data section to prevent
implicit TET10 usage.
1-47911501
2008.0.0 (MD R3)
ZERO vs. NONZERO
Documentatio/QRG - AUTOSPC describer - NO
References to "NONZERO' in the QRG description of the AUTOSPC case control

command should be "NOZERO".
1-48031006
2007.0.0
6 or 400 causes SFM 3001
Nonlinear Analysis - Using NSM in sol 10
Using NSM in sol 106 or 400 results in the message:

9 DOES NOT EXIST.
STATEMENT
Avoidance: Use the following alter.
compile phase1a
alter ' ta1 ',''
TA1
MPTS,ECTS,EPTS,BGPDTS,SILS,ETT,CSTMS,DIT,,/
EST,ESTNL,GEI,GPECT,ESTL,vgfd,ditid,nfdict,nsmest/
LUSETS/S,N,NOESTL/S,N,NOSIMP/2/S,N,NOGENL/SEID/
LGDISP0/NLAYERx/s,n,freqdeps/shldamp/s,n,mge/nsm $
1-48240611
2007.0.0
Frequency Response - Wrong Answers (SOL
108 and 111) with K4 & TFL, and Multiple Subcases
Wrong answers will result in SOL 108 or SOL 111 when structural damping (K4) is
combined with transfer functions.
Avoidance: use the following DMAP alter:
compile sedfreq
alter 'EQUIVX.*K4AA\/K4DD',''(,1)
alter 'call gma'(,-1)
EQUIVX K4AA/K4DD/NOUE $
IF ( NOUE>-1 ) UMERGE1 USETD,K4AA,,,/K4DD/'D'/'A' $
compile semfreq
alter 'EQUIVX.*K4AA\/K4DD',''(,1)
alter 'call gma'(,-1)
EQUIVX K4AA/K4DD/NOUE $
IF ( NOUE>-1 ) UMERGE1 USETD,K4AA,,,/K4DD/'D'/'A' $
1-48291201
2007.0.0
Documentation/QRG - Aeroelastic Analysis
- aedw, aepress, aeforce do not support MACH=0.0
The Quick Reference Guide specifies that the MACH input must be .ge. 0.0, but
if the user sets this input to 0.0, is is marked as an illegal data.
Avoidance: The MACH must be set to a number .gt. 0.0
1-48291704
2008.0.0 (MD R3)
Structural Damping
MDACMS - SDAMPING - Wrong Answers with K4
Modal Frequency response (SOL 111) with MDACMS may produce wrong answers with
structral (K4) damping.
Avoidance: The workaround is to include PARAM,MDK4OPT,0
1-48302021
Optimization/Design Sensitivity - SFM 6043 (XQAERR) - unable
to evaluate expressions of oscar type 2
When a DRESP2 response with the EQID field = FUNC (such as SUM) is followed by
another DRESP2 response with EQID=Integer the job may fail with the message:
SYSTEM FATAL MESSAGE 6043 (XQAROS)
UNABLE TO EVALUATE EXPRESSIONS OF OSCAR TYPE 2
Avoidance: The avoidance is to assign the largest RID to those DRESP2s with
EQID=FUNC so that they will always be placed in the last.
1-48326271
2007.0.0
otion fails with PARAM,ENFMETH,ABS
MDACMS - SOLs 111 and 112 with Enforced M
MDACMS in SOLs 111 and 112 with Enforced Motion fails with PARAM,ENFMETH,ABS.
The following message may be issued:
SYSTEM FATAL MESSAGE 5423 (MPYAD1)
FILE#
COLS
ROWS FORM
TYPE NZWD DENS

2
60 4615
2 10000
TRAILER FOR MHS1
IS
101
26
30
TRAILER FOR ACCE
IS
102
202
0
TRANSPOSE FLAG IS 0

compile getpyh
alter 'call xADD5.*mhs','mpyad.*khs1,disp,pmbh'(,1)
equivx yst/disp/-1 $
call xADD5 mhs,m2hs,,,/mhs1/cu/cu/cz/cz/cz $
call xADD5 Bhs,B2hs,,,/Bhs1/cu/cu/cz/cz/cz $
c1g=CMPLX(1.,G) $
CALL xADD5 Khs,K4hs,K2hs,kdhs,/Khs1/C1G/ci/cu/cu/cz $
else $
$ transient response
dsar
yst,,,/disp,velo,acce,,/-1 $
call xADD5 BHS,B2HS,,,/BHS1/cu/cu/cu/cz/cz $
call xADD5 KHS,K2HS,kdhs,,/KHS1/cu/cu/cu/cz/cz $
call xADD5 mhs,m2hs,,,/mhs1/cu/cu/cz/cz/cz $
endif $ app='freqresp'
$
if ( enfmeth='abs' and nonzys>-1 ) then $
partn
bhs1,nzys,/,,bhs2,/1 $
partn
mhs1,nzys,/,,mhs2,/1 $
partn
khs1,nzys,/,,khs2,/1 $
mpyad
mhs2,acce, /pmh $
mpyad
bhs2,velo,pmh/pmbh $
mpyad
khs2,disp,pmbh/pyxt $
else $
mpyad
mhs1,acce, /pmh $
mpyad
bhs1,velo,pmh/pmbh $
mpyad
khs1,disp,pmbh/pyxt $
endif $
1-48629874
2007.0.0
M 4276 (PFCALC)
Modal Participation Factors - PFMODE - SF
Jobs using the PFMODE case control command may fail in the PFCALC module with a
SFM 3007 illegal input into mpyad message or a GINO message trying to open a
matrix data block if any grid point resequencing has taken place and the
internal grid point order is no longer in external sort. This can occur during
superelement processing for example. There is no known avoidance.
ERROR CODE
1044 PID= 0
Traceback:
Offset 0x000022cc in procedure
Offset 0x000005ec in procedure
Offset 0x00000adc in procedure
2007.0.0
f MONPNT is in the deck
gtdens_
mpyad_
mpyadk_
pfcalc_
xsem07_
xsemdr_
nastmon_
mainal
Aeroelastic Analysis - SOL 145 may fail i
SOL 145 does not support MONPNT. However, SOL 145 job may fail if MONPNT is
simply in the deck.
Avoidance: 1. remove or comment out MONPNT entry
2. use attached DMAP alters (add dmonpta/dmonpts to call of
SUPER1)
1-48873671
ol 144
2007.0.0
Aeroelastic Analysis - infinite loop in s
If a Solution 144 (static aeroelasticity) run is submitted that does not have
any TRIM or DIVERG case control commands in any of the subcases, an infinite
loop will result in the PFAERO subdmap.
Avoidance: Make sure the required TRIM and DIVERG case control commands are
included in case control
1-48879511
2007.0.0
Miscellaneous - ISHELL jobs terminate abn
ormally when run using a job scheduler
If Nastran starts an ISHELL job that is suspended by a job scheduler (using a
"kill -STOP"), the ISHELL processing routine (doit.c) does not properly
recognize this situation and terminates processing with an error.
1-48996563
2007.0.0
orrectly, Wrong Answers
SOL 600 - BCBODY - Friction not written c
The marc CONTACT entry is not written correctly when the BCBODY entry contains
a friction coefficient.
1-49085732
2006.0.1
arbitrary beam elements may fail
Elements - PBMSECT - Stress recovery of
Stress data recovery of abitrary beam elements may enter an infinite loop if a
FORCE Case Control command is not present.
1-49086447
N statement.
2007.0.0
Docuementation/QRG - Remark 12 for ASSIG
The following limitation documented in remark 12 of the QRG for the ASSIGN
statement was removed in V2005.5.
"Note, however, that the DBLOAD and INPUTT2 modules cannot process input files
in other than the native binary format. That is, a binary file in BIGNENDIAN
format cannot be processed on a LITTLEENDIAN platform and vice-versa".
The MD R2 and MSC.Nastran 2007 QRG has been updated.
1-49098315
2008.0.0 (MD R3)
Rotordynamics - Hybrid Damping in Rotordy
namics SOL 107 or 108 w/ no SE - SFM 3001 (GKAM)
A rotordynamics model with hybrid damping and no superelements fails in the
call to the READ module in subDMAP HYBRID with the message:
4 DOES NOT EXIST.
STATEMENT
1-49118561
2008.0.0 (MD R3)
Nastran (acct=yes)
Utilities - Acounting does not work in MD
Acounting does not work in MD Nastran (acct=yes). It does work in MSC.Nastran

2005r3.
1-49161431
nux8664)
2008.0.0 (MD R3)
Performance - TAUCS - ILP64 (linux64 / li
If TAUCS (sys166=8192) is used on ILP64 systems, then the perfomance is very

bad.
Avoidance:
- Run without TAUCS
- Create a BLAS shared object containing SSYRK and STRSM and use
BLASLIB=New_Blas_lib.so
- fixed in MDR3 on x8664 and IA64 ILP64 systems.
1-49381161
2007.0.0
SOL 700 - EOSGAM entry error
EOSGAM entry gives the following FATAL ERROR : Illegal name for bulk data
entry.
Avoidance : Use the TODYNA- ENDDYNA entry to bypass this entry.
1-49477782
Elements - PCOMP Z0 vs ZOFFS - Slightly different answers
A CQUAD4 element that references a PCOMP entry that specifies an offset Z0

will provide slightly different answers than modelling the offset using QUAD4
with ZOFFS. The differences are attributed to a small difference in the way
the transverse shear stiffness is calculated. .
1-49495686
2007.0.3
Rotordynamics - SOL 108 or 129, RSDAMP Hybrid Damping READ Module, UFM 4683
A 3D rotordynamics model fails in the READ module with the following error
*** USER FATAL MESSAGE 4683 (REIG)
MASS MATRIX NEEDED FOR EIGENVALUE ANALYSIS
when hybrid damping is requested in the case control with RSDAMP command.
Quality 1-49098315 may be related since it is a similar setup but without a
superelement.
1-49496581
2007.0.0
Aeroelastic Analysis - IFP - AECOMP with
a continuation with data in field 9 cause an IFP error
The AECOMP entry supports an open-ended list of set ids for the component. If
the list of set id's ends with the 9th field of a continuation entry (i.e.,
there are exactly 14, 23,32, etc. ID's) the job will fail with an invalid data
message.
Avoidance: The AECOMPL entry can be used to collect multiple AECOMPs so this
provides a way to avoid the above liimitation.
1-49502651
2008.0.0 (MD R3)
24(GKAM) in stress recovery run
ADAMS Integration - SPOINT/QSETi - SFM 76
The following message occurs in stress recovery, when the number of

SPOINT/QSETi are specified greater
than needed in MNF file creation run.
THE NUMBER OF EIGENVECTORS (
42) IN THE PHSA
MATRIX IS GREATER
THAN THE NUMBER (
38) OF COMPUTED EIGENVALUES IN THE LAMMATS MATRIX
Avoidance: Set same values for SPOINT/QSETi.
1-49509805
results
2007.0.0
SSSALTER - glforce alter gives incorrect
MSC.Nastran Version 2004 and 2005 versions of the

answers. In the previous versions KAA was called
In 2004 and 2005 KAA is in the datablock list for
called datablocks. This produces a null datablock
1-49522526
error
2008.0.0 (MD R3)
glforce alter give incorrect

up with a type,db statement.
the subroutine but not in the
and hence incorrect results.
Documentation/QRG - EPOINT documentation
The Quick Reference Guide indicates that there is a ID limit of ID<1,000,000

for EPOINTS. This is a typo and should be ID<100,000,000
1-49543841
2007.0.0
SOL 400 - Strain Output is inconsistent.
Hi Hassan,
is this your?
Thanks
Alois
In SOL 400 total strains need to be converted into True strains to be
consistent with other nastran solutions.
1-49693111
2007.1.0
ess output for SOL 400 QUAD4 models
SOL 400 - CQUAD4 - Infinity von MIses str
The von Mises stresses for CQUAD4 elements in SOL 400 may be output as NaN.
1-49703571
2007.0.0
Aeroelastic Analysis - SPLINE6 - INSUFFI
CIENT CORE AVAILABLE FOR SUBROUTINE F6GD
A deck that included spline6 entries that invoked over a thousand structural
and aerodynamic grids produced the message:
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE F6GD
A review of the code indicates that the required amount of memory can be
reduced drastically and the UFM avoided. The error occured for the spline6,but
similar memory inefficiencis exist for all the spline type elements.
User Avoidance: Run with the additional memory requested by the message or
break the large splines into a number of smaller splines to get past the error.
1-50014537
2007.1.0
when UWM 2047 is issued
Multipoint Constraints - Missing UFM 2101
When a datadeck contains a conflict between UM and US membership normally user

fatal message 2101 is issued and the job stops. However when an MPCADD entry
also exists referring to more than 100 nonexisting MPC sets 100 uwm's 2047 are
issued and the job stops without printing the ufm 2101.
1-50027590
2007.0.0
- UFM 6656 (MODTRK)
The message "USER FATAL MESSAGE 6656 (MODTRK) THE TRACKED SUBSET PHGREF OF
MODES FROM A PREVIOUS DESIGN CYCLE" can be produced whenever the user specifies
a MODTRAK command in a SOL 200 subcase that contains a METHOD command but is
not an ANALYSIS=MODES subcase. E.g, using MODTRAK with ANALYSIS = MCEIG,
MTRAN, MFREQ or FLUTTER can produce the error.
Avoidance: Remove the MODTRAK case control command from subcases that do not
also have an ANALYSIS =MODES command.
1-50098347
2008.0.0 (MD R3)
Documentation/QRG - File Management Secti
on - Assign Statement documentation is wrong
The QRG documentation for the ASSIGN statement in the File Management section
contains examples for "ASSIGN OP2" that should be "ASSIGN OUTPUT2".
1-50289995
es
2007.0.0
Utilities - dr3srv build on linux64 crash
When compiling dr3srv to use DRESP3 entries using the MSC provided makefile
(dr3srv.ksh), the following error will occur.
ld: Warning: size of symbol `main' changed from 128 in
/opt/intel_fc_80/lib/for_main.o to 192 in
/appl/msc.software/msc.nastran/msc20055/linux64/dr3srv.o
/appl/msc.software/msc.nastran/msc20055/linux64/libdr3srv.a(memmgmt.o)(.
text+0x21e2): In function `Get_Temporary_Name':
: the use of `tempnam' is dangerous, better use `mkstemp'
/opt/intel_fc_80/lib/for_main.o(.text+0x42): In function `main':
: undefined reference to `MAIN__'
make: *** [dr3serv] Error 1
===
Resolution:
Modify dr3srv.ksh to include "-nofor_main". The build script will look like
this for the linux64 section:
linux64 )
targets="CC=/opt/intel_cc_80/bin/icc FC=/opt/intel_fc_80/bin/ifort"
FFLAGS="-nbs -w -w90 -cm -WB -pad_source -W0 -save -zero -Vaxlib -ftz"
export FFLAGS
LDFLAGS="-nofor_main -Vaxlib"
export LDFLAGS
;;
1-50337802
2008.0.0 (MD R3)
Case Control - Input error leads to misle
ading UFM 392 (XSORSO) and UFM 9002 (IFPL)
When a FREQ1 or other bulk data entry which begin in the first column has been
erroneously put into the case control deck the following error occurs:
*** USER FATAL MESSAGE 392 (XSORSO)
THE AUXMID OR SEID ON THE FOLLOWING BEGIN BULK COMMAND IS NOT GREATER THAN
0.
and at the end of the f06 file:
^^^ USER FATAL MESSAGE 9002 (IFPL)
^^^ SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN
MODULE XSORT.
These error messages are misleading. Normally when an illegal case control
command is specified the following error message will be issued:
THE KEYWORD ON THE ABOVE CARD TYPE IS ILLEGAL OR MISSPELLED.

Attached is a data deck which shows the problem.
The message 392 has been updated as follow to check the statement(s) defined
before the "BEGIN BULK".
*** USER FATAL MESSAGE 392 (XSORSO)
THE AUXMID OR SEID ON THE FOLLOWING BEGIN BULK COMMAND IS NOT GREATER THAN
0.
BULK ENTRY: BEGIN BULK
USER INFORMATION: THIS ERROR MAY OCCURE DUE TO BULK DATA ENTRIES BEING
DEFINED BEFORE THE "BEGIN BULK" STATEMENT.
1-50362721
2007.0.0
Mass Matrix - NSM, NSM1 - Wrong Answers
In a very large model with 6 million degrees of freedom which included

correspondingly large NSM sets, the non structural mass included in the
analysis was truncated leading to wrong answers.
1-50504311
2007.1.0
XYPLOT, XYPUCH - Infinite CPU loop for XY
PUNCH request with an illegal item code
If an xyplot or xypunch request is made for an invalid element code, the
program may go into an infinitel cpu loop.
An avoidance is to supply YMIN and YMAX before the XYPUNCH command. YMIN and
YMAX are for ploting, and should not be needed for XYPUNCH.
1-50522550
2008.0.0 (MD R3)
Elements - CELAS2 - UFM
The CELAS2 entry fails in version 2005 and later when using mixed double field
and single field continuation entries. format on line 2
1-50605180
2007.0.0
SOL 600 - MAT9, MATORT - solids/shells ca
nnot reference cylindrical CS for material CS
In SOL 600, solid element material properties may only reference a single
rectangular coordinate system for the enitire model. Shell elements may
reference multiple rectangular coordinate systems.
1-50608531
2007.0.0
VCCT case control ID - UFM 311
SOL 400, 600 - Multiple cracks using same
Multiple VCCT cracks, such as "VCCT,1,1,...." and "VCCT,1,2,...." on the same

VCCT Case Control command results in the following fatal message:
NON-UNIQUE FIELD 2 ON BULK DATA ENTRY VCCT 1
5036
1-50617151
2007.0.0
ting Campbell Diagram
SORTED ENTRY COUNT =
Rotordynamics - UFM 3032 (CAMPREP) genera
Rotordynamics analysis may fail when generating the Campbell diagram with the
following message:
*** USER FATAL MESSAGE 3032 (CAMPREP)
UNABLE TO FIND SELECTED SET ( 301) IN TABLE (DDVAL ) IN
SUBROUTINE (NO_DDVAL_SELECTED).
0FATAL ERROR
1-50698031
2007.0.0
n in sparse decomp
Matrix Methods - Floating Point exceptio
Sparse decomp may crash with a floating point exception

Signal received: SIGTRAP - Trace trap
Signal generated for floating-point exception:
FP invalid operation
Traceback:
Offset 0x000010f4 in procedure
Offset 0x00001f1c in procedure
Offset 0x00000adc in procedure
tmgino_
dfmsym_
dfmsa_
sdcomp_
facdrvo_
facdrv_
reigla_
lnnrigl_
reig_
xsem06_
xsemdr_
nastmon_
mainal
The problem has been traced to an integer overflow in the routine DFMSA.
Input files are in /nast/app/etl/q1-50698031.zip
1-50698089
2007.0.0
ment to DGEGV when using QZ HESS
Complex Eigenvalues - HESS - Illegal argu
When using QZ HESS in complex eigenvalue analysis, if more than 4 Gb of memory

is given and if the problem is too large to fit in core, the eigenvalue
analysis is attempted, leading to an error message from the LAPACK routine
DGEGV (or ZGEGV if the matrices are complex).
Avoidance: An avoidance for v2005.5+ is to specify mode=i8.
1-50714854
2009.0.0 (MD R4)
Elements - A SingleCQUAD4 produces Incorr
ect corner stress for tapered thickness
The isoparametric theory for the CQUAD4 element assumes bilinear shape
functions for displacement. This is wrong for tapered elements. The error is
acceptable for stiffness and element center data recovery. The error is large
for element corner data recovery in a coarse model.
Avoidance: This is not a significant issue for real world models. The data
recovery has been modified in MD R4 2009.0.0 to improve the results for coarse
models.
1-50714931
rror
2007.1.0
SOL 600 - BCPARA, GP1 - Marc Translator e
The following input bulk data error was not trapped in IFP and caused nastran
to fail in GP1 as shown below.
BCPARA,ERROR,.010
should have been
BCPARA,,ERROR,.010
forrtl: severe (64): input conversion error, unit -5, file Internal Formatted
Read
The same job aborted on Linux dmp=4 with the following error...
forrtl: severe (64): input conversion error, unit -5, file Internal Formatted
Read
time: error waiting for child process: No child processes
1-50731974
2006.0.1
Element - bar, beam, non structural mass
- missing mass polar moment of inertia
If non structural mass is defined on the beam or bar element, the mass polar
moment of inertia is not included.
Avoidance: Use structural mass instead.
1-50779321
2007.0.0
ents - SFM 6144
Dynamics - PARAM,AUTOQSET, Part Superelem
If PARAM,AUTOQSET,YES is specified with part superelements and there are SPCi

specified in part superelement bulk data sections then the job may fail with
something similar to:
*** SYSTEM FATAL MESSAGE 6143 (UMRG1PR)
SPECIFICALLY:
The number of columns in KSF is not equal to the size of the COMP-set
KSF
: Rows=
12 by Cols=
60
Set sizes: Major (F-set)=
167
Set0 (COMP-set)=
68
Set1 (Q-set)=
99
Avoidance: Insert the following DMAP alter (which also avoids CR 1-50779328)
compile phase0
alter ' bndspc '(,-1)
if ( seid=0 ) call dbstore ysd,,,,//0/0/'
compile extduset
alter 'xemap\/emap'
call dbstore xemap,,,,//0/0/'
'/0 $
'/0 $
compile augqset
alter 1
call dbfetch /xemap,ysd,,,/0/0/0/0/0 $
alter 'gp4 '
bndspc xemap,uset0,bgpdt,,ysd/
uset01,ysd1/
seid/0 $
equivx uset01/uset0/-1 $
compile phase1dr
alter 1
type db kqqu,mqqu,bqqu,k4qqu,pqu,rvqu,aqu,phbqu,
gpqku,gdqku,sdsrqu $
1-50779728
2007.0.0
Dynamics - PARAM,AUTOQSET, multilevel sup
erelement trees - SFM 6144 or Wrong Answers
If PARAM,AUTOQSET,YES is specified with multilevel superelement trees with
branches longer than one superelement then the job may fail with something
similar to:
*** SYSTEM FATAL MESSAGE 6144 (MERGE1PR)
SPECIFICALLY:
The number of columns in MTQ is not equal to the number of non-zeros in
partitioning vector VQ
MTQ
: Rows=
12 by Cols=
13
VQ
: Rows=
105
no. of non-zeros=
35 no. of zeros=
70
Avoidance: Insert the following DMAP alter (which also avoids CR 1-50779321)
compile phase0
alter ' bndspc '(,-1)
if ( seid=0 ) call dbstore ysd,,,,//0/0/'
compile extduset
alter 'xemap\/emap'
call dbstore xemap,,,,//0/0/'
'/0 $
'/0 $
compile augqset
alter 1
call dbfetch /xemap,ysd,,,/0/0/0/0/0 $
alter 'gp4 '
bndspc xemap,uset0,bgpdt,,ysd/
uset01,ysd1/
seid/0 $
equivx uset01/uset0/-1 $
compile phase1dr
alter 1
type db kqqu,mqqu,bqqu,k4qqu,pqu,rvqu,aqu,phbqu,
gpqku,gdqku,sdsrqu $
1-50888831
2007.0.0
Rotordynamics - RSPINR - ROTOR superlemen
t with structural damping, GR, gives wrong answers
A rotordynamics superlement analysis with structural damping (GR) specified on
the RSPINR entry will yield wrong answers.
1-50916991
2007.1.0
DESSUB, DESOBJ - SFM
If a DRESP1 entry with RTYPE = RMSxxxx or PSDxxxx is selected by a DESSUB or

DESOBJ entry that is in a subcase other than the first subcase referenced on
the RANDPS entry iinvoked by the DRESP1, a system fatal message will occur.
User information: RMS or PSD responses in SOL 200 that are created using the
DRESP1 entry can span multiple subcases based on the RANDPS entry that is
invoked by the DRESP1 entry. Case control reference (DESSUB/DESOBJ) can only
be from the first subcase selected on the RANDPS entry.
1-50932651
Complex Eigenvalues - EIGC, CLAN - Wrong Answers
Complex Lanczos produces roots for unsymmetric fluid-structure interaction

problems (such as tpl/ac10704)
which have a non-zero real part; however, when there is no damping, the roots
should be pure imaginary.
Avoidances include:
1) force the computations to be performed in complex arithmetic by specifying
sys108=16384
2) use old single-vector Lanczos by specifying sys108=2
3) use SOL 110 in place of SOL 107, and use HESS for the complex eigensolution.
1-50984175
2007.0.2
SOL 600 - PLOAD - Possible wrong answers
It is not recommended that PLOAD be used in SOL 600. All PLOAD entries should
be changed to PLOAD4 entries.
The PLOAD sign convension is different in NASTRAN than MARC. Nastran assumes
positive pressure to be acting in the positive element normal direction,
whereas marc assumes that positive pressure is acting in the direction opposite
to the element normal ( ie into the element).
1-51008491
2007.1.0
Restart - enforced motion - SFM 6144
If a restart is performed on an enforced motion restart then the following

error may occur:
SPECIFICALLY:
The number of rows
in DAY is not equal to the number of rows in the row
partitioning vector VYA
DAY
: Rows=
XXX by Cols=
YYY
VYA
: Rows=
ZZZ
Avoidance:
Insert the following DMAP alter (any version or Nastran)
compile getay
alter 'fbs.*lyy,,kay1',''(,11)
fbs
lyy,,kay1/day0//-1 $
if ( nullvay>-1 ) then $
merge
day0,,,,,vay/day1/1 $
else if ( nullvya>-1 ) then $
partn
day0,,vya/day1,,,/1 $
else
equivx day0/day1/-1 $
endif $
merge
day1,,,,,vafs/day/1 $
else $
equivx day1/day/-1 $
endif $
endalter
1-51018492
ARTN1)
2007.0.0 (MD R2)
Frequency Response - MDACMS - SFM 6144 (P
If a frequency response MDACMS analysis has enforced motion that results in

null loads the job may fail with the message:
SPECIFICALLY:
The number of columns in YST is not equal to the number of rows in the
column partitioning vector CP

YST
: Rows=
4 by Cols=
31
CP
: Rows=
1
Avoidance: Run the job without MDACMS.
1-51035307
2007.1.0
utoqset results in UFM 3001 in GP4
Superelements - param,extout with param,a
Using param,autoqset will result in the following fatal message when used in
combination with param,extout.
THE INPUT DATA BLOCK NAMED EQEXINX AT POSITION
3 DOES NOT EXIST.
Avoidance: 1. Use the case control command EXTSEOUT
or
2. Use the following alter
compile extout
alter 'if ( atqset','' $
if ( atqset and extseout>0 ) then $
1-51120736
2008.0.0 (MD R3)
Matrix Methods - Insufficient core for F
BSMEM; sfm 7340 (LNNRIGL) - unknown internal error
This was fixed as part of project tad02586.
Lanczos now issues SFM 3008 and the job is aborted.
Defining FBSMEM/system(146) to a large value, for example 100, can lead to the
following messages:
INSUFFICIENT CORE FOR FBSMEM IN REIGL
INCREASE MEMORY BY AT LEAST 1111366876 WORDS
*** SYSTEM FATAL MESSAGE 7340 (LNNRIGL)
UNKNOWN INTERNAL ERROR OCCURRED.
The problem is that Nastran does not stop at this point. Instead Nastran
proceeds with MMFIND1 and thereafter tries to find a solution again. But the
same error happens again and a solution cannot be found (ufm 4405).
1-51128594
2007.0.2
l to find marc executable
SOL 600 - Submittal on Linux IA64 may fai
SOL 600 jobs in MSC.Nastran 2005r2 on Linux IA64 may fail to find marc
executable and may fail with the message:
Machine architecture to use comes from

MSC_ARCHM=linux_rh9
Check default script
/opt/cae/msc/msc20051/marc/linux_rh9/marc2005/tools/run_marc
Check default script /opt/cae/msc/msc20051/marc/linux_rh9/tools/run_marc

directory
1-51152461
2007.1.0
ncorrect Documented Default Value
Documentation/SOL 600 - BCPARA,FTYPE - I
The type of inte QRG will be fixed - the default will be changed to 0 instead
of 2 - Ed Dickerson 2/22/2007
In SOL 600, NLTRAN, the documented efault of BCPARA-FTYPE is incorrect. The
default is 0 not 2.
1-51434272
2008.0.0 (MD R3)
058, Wrong Answers
Documentation/QRG - SMETHOD, ITER - UFM 9
The iterative solver methods do not work in the presence of SUPORTi entry, this
is documented in a remark under the ITER bulk data entry. It should be noted
that param, inrel uses the SUPORT entry and therefore the iterative solver may
not be used with this parameter. If attempted either the message:
USER FATAL MESSAGE 9058 (SUPER3)
THE SOLUTION FOR THE RESIDUAL STRUCTURE DOES NOT EXIST.
or incorrect results will occur.
1-51437479
2008.0.0 (MD R3)
d design variable ids
Topology - asterisks for material ids an
Topology optimization jobs output asterisks for material ids and design
variable ids.
----- COMPARISON BETWEEN INPUT MATERIAL PROPERTY VALUES FROM
ANALYSIS AND DESIGN MODELS -----------------------------------------------------------------------------------------------------------------MATERIAL MATERIAL MATERIAL
ANALYSIS
DESIGN
LOWER
UPPER
DIFFERENCE
TYPE
ID
NAME
VALUE
VALUE
BOUND
BOUND
FLAG
-------------------------------------------------------------------------------------------------------------MAT1
********
E
1.000000E+07
1.250000E+06
1.000000E-15
1.000000E+20 WARNING
MAT1
********
RHO
1.000000E-01
5.000000E-02
1.000000E-15
1.000000E+20 WARNING
-----
DESIGN VARIABLES
-----------------------------------------------------------------------------------------------------------INTERNAL
DESVAR
LOWER
UPPER
ID
ID
LABEL
BOUND
VALUE
BOUND
-------------------------------------------------------------------------------------------------------1
1
X1
1.0000E-02
2.0000E+00
1.0000E+02
2
2
X2
1.0000E-02
2.0000E+00
1.0000E+02
3
3
X3
1.0000E-02
2.0000E+00
1.0000E+02
4
4
X4
1.0000E-02
2.0000E+00
1.0000E+02
5
5
DG3
1.0000E-02
1.0000E+00
2.0000E+00
6
********
TOPVAR
1.0000E-03
5.0000E-01
1.0000E+00
7
********
TOPVAR
1.0000E-03
5.0000E-01
1.0000E+00
8
********
TOPVAR
1.0000E-03
5.0000E-01
1.0000E+00
MAT1
1.000000E-15
********
1.000000E+20
E
1.000000E+07
WARNING
1-51495308
2007.1.0
- CSUPER - ufm 5423 (MPYAD)
1.250000E+06
Optimizaton/Design Sensitivity - EXTSEOUT
In sol 200 when using external superelements which refer to CSUPER cards the
following error may occur:
*** USER FATAL MESSAGE 5423 (MPYAD)
FILE#
COLS
ROWS
301
55182
15
TRAILER FOR PXG
IS
101
1872
FORM TYPE NZWD DENS

2
6 1324
2 1248 3333
0
TRANSPOSE FLAG IS 0
Avoidance: use the following DMAP alter for 2005r3 and 2006:
compile EXTIN $
alter 'DBSTATUS
if (nokaa>0 and
EQUIVX X_K
EQUIVX X_M
EQUIVX X_B
X_K' $
iostat=0
/KXX /-1
/MXX /-1
/BXX /-1
) then $
$
$
$
EQUIVX X_K4/K4XX/-1 $
EQUIVX X_P /PX /-1 $
EQUIVX X_V /VX /-1 $
EQUIVX X_GP/GPX /-1 $
EQUIVX X_GD/GDX /-1 $
EQUIVX X_VF/VXFS/-1 $
EQUIVX X_A /AX /-1 $
return
endif
alter 'if ( nouset',''
if ( nouset>0 and not(exter) ) then $
COMPILE spdr1
alter 'PEID=SEID' $
type parm,,i,n,np2 $
type parm,nddl,i,n,desiter $
np2 = desiter $
if ( peid>0 ) desiter = 0 $
alter 'NOASET=LUSETS' $
if ( peid>0 ) desiter = np2 $
COMPILE phase0
alter 'SELIST=(NOSELIST>0)','' $
SELIST=(auxmid<1 and NOSELIST>0) $
COMPILE phase1dr
alter 'SEP2DR SLIST' $
if ( auxmid>0 ) noup = -1 $
alter 'IF ( NOKAA','' $
if( nokaa<1 or descycle>1 ) then $
and use the following DMAP alter for 2007:
compile EXTIN $
alter 'if ( nouset',''
if ( nouset>0 and not(exter) ) then $
COMPILE spdr1
alter 'PEID=SEID' $
type parm,,i,n,np2 $
type parm,nddl,i,n,desiter $
np2 = desiter $
if ( peid>0 ) desiter = 0 $
alter 'NOASET=LUSETS' $
if ( peid>0 ) desiter = np2 $
COMPILE phase0
alter 'SELIST=(NOSELIST>0)','' $
SELIST=(auxmid<1 and NOSELIST>0) $
COMPILE phase1dr
alter 'SEP2DR SLIST' $
if ( auxmid>0 ) noup = -1 $
alter 'IF ( NOKAA','' $
if( nokaa<1 or descycle>1 ) then $
1-51517141
2008.0.0 (MD R3)
Documentation/QRG - PSOLID - TETRA(5-10 n
ode) supported in SOL 106, 129 and 400
In Table 8-43 at the end of the PSOLID description in the Quick Reference Guide
it incorrectly indicates that the TETRA 5-10 is not supported in SOL 106, 129
and 400.
1-51544187
2007.1.0
Connector Elements - CWELD - UFM 6599 (SE
P1C), CWELD with ELEMID, Superelements
When the PWELD entry specifies that MSET is on, USER FATAL MESSAGE 6599
(SEP1C) may be incorrectly output.
.
1-51552281
SOL 600 w/ COORD SYSTEMS - DDM - Parallel does not work
This is a Marc limitiation. In order to add coord sys

cylindrical/spherical system MCID's the new Marc COORD
used. For models without CBUSH coordinate orientation
coordinate, enter the following parameters
PARAM,MRCOORDS,1
PARAM,MRORINTS,1
Starting with tier 1 systems as of 6/22/2007 the above
automatically. E Dickerson 6/22/2007
capability for CBUSH and

SYS option needed to be
or MCID's specified by a
will happen
Starting with MD R2, SOL 600 analyses with COORD SYSTEMS will not run parallel.
Avoidance: Convert local coordinate systems to the global coordinate system.
1-51564461
2007.1.0
Output, Incorrect Element ID
Aeroelastic Analysis - AERODYNAMIC FORCE
The aerodynamic force table can sometimes have a 0 as the element ID in the
last row of data rather than the highest aerodynamic element ID.
User Information: the missing id is confined to the printout and does not
affect any other output.
1-51589547
2007.0.0
SOL 600 - MSC_LICENSE_DISCRETE - Nastran
Tokens/ALUs are not released before marc is executed
When running an MD R1 Nastran or MSC.Nastran 2005r3, SOL600 job with
MSC_LICENSE_DISCRETE set to 1, then Nastran doesn't release licenses.
The next table shows MD Nastran token usage for a SOL600 job:
Application
Normal Discrete
MD Nastran
Translator
Marc
MD Nastran
Translator
288
334
184
288
334
288
334
518
518
518
As you can see with MSC_LICENSE_DISCRETE=1 , most of the time 518 tokens are
checked out! (this represents 518 tokens * Euro 400 = Euro 200,000 !!!!! (so
more than 200K US$ ))
1-51706467
2007.1.0
SFM 4276, EC 3001
Rotordynamics - SOL 109, Module ROTRUTL,
A linear transient solution, SOL 109, fails with the following message for
version MD R2 (aka 2007) but runs successfully with MSC.Nastran 2005r3b.
*** SYSTEM FATAL MESSAGE 4276 (FREAD)
ERROR CODE
3001 PID= 0
The failure occurs because there are no RSPINTs entries defined.
interpretation of this should be that the rotors do not spin.
The
1-51854251
2007.1.0
Acoustic Analysis - Grid Point Participat
ion Factor - wrong grid id in punch file
Grid IDs in the punch file of an acoustic analysis with grid point
participation factor requests will have a value of "4" appended to the end.
The error happens when only the punch file is requested by case control command
disp(punch).
Avoidance: Request disp(print,punch).
1-51861461
nswers
Restarts/External Superelements - EXTSEOUT(DMIGPCH) - Wrong A
A SOL 111 restart from a previous sol 111 job which contains an external SE
created with EXTSEOUT(DMIGPCH) produces incorrect results when K2GG and M2GG
have been omitted in the restart. The results are the same as for the cold
start. This happens because KAA is available from the restart database.
1-51884991
2007.0.1
SOL 600 - Certain shell elements with MCI
D using new COORD SYS option - Missing orientation vectors
Certain shell elements with MCID using the new COORD SYS option are missing
orientation vectors in the Marc deck in MDR2.
See external web: MD R2 update for HPUX IA64
1-51919711
2007.1.0
Frequency Response - FRF run with an RLO
AD1 entry with null excitation fails with SFM 3200 in DPD
An FRF generation run with an RLOAD1 entry with null excitation will fail with
SFM 3200 (Logic error 14) in subroutine DPD9 in the DPD module.
1-51942339
2007.0.2
SOL 600 - CONM, GRAVi - PARAM,WTMASS mult
iplier is ignored for conm and density for gravity
PARAM,WTMASS multiplier is ignored for conm and mass density used in gravity
loading in SOL 600.
1-51945401
ethod
2007.1.0
Documetation/IOG - FFIO - New Selection M
Starting with MSC Nastran 2007.0.0 R1 FFIO is no longer selected by setting

only FF_IO_OPTS. The addtional new setting is also required:
LD_PRELOAD=$MSC_BASE/$MSC_VERSD/linux64/libFFIO.so
for example:
export LD_PRELOAD=/opt/msc/msc2007/linux64/libFFIO.so
This change will allow FFIO libraries to be dynamically set.
Note that the msc2007.0.0 R1 shared object has been tested on ProPack 4 and
ProPack 5. It does not work with ProPack 3.
1-51995261
2007.1.0
SOL 400 - Incorrect Message, UFM 4512
If there is an error for the NLPARM ID for SOL 400, module ST2DYN give UFM
4512, which is for the DEFORM entry.
1-52043741
2007.0.2
SOL 600 - Tables in large field format ma
y not be correct or may be missing

SOL 600 may incorrectly translated table entries that input in large field
format or may fail to translate them at all.
1-52044231
2007.1.0
Optimization/Design Sensitivity - sensiti
vity descrepancy between dresp1 and dresp2
The frequency response sensitivity for the following DRESP1 with RSS should
have an identical value and sensitivity with its derived DRESP2 entry when
there is a single forcing frequency.
dresp1 10001
dresp1 10002
pres
pres
PRES
PRES
1
1
RSS
RSS
1001
1021
The above statement is not true for cases with very small response value,
<1.e-6.
Avoidance : If feasible, increase loading by several order of magnitude to
boost the response value.
1-52048361
2007.0.2
CPU times - SGI ProPack 5 - bad F04 file
The CPU times printed in the F04 are off by roughly a factor of 4 on SuSE 10
IA64 systems. This OS is usually installed with Altix ProPack 5 systems.
Avoidance: Use the times reported in the log file for an accurate time of the
entire run.
1-52060201
2007.1.0
Optimization/Design Sensitivity - Missing
EIGR entry results in poor message, SFM 3001 (DOPR3)
The message "SYSTEM FATAL MESSAGE 3001 (DOPR3) datablock edoms does not exist"
is given in error when the user has a DRESP1 entry with RTYPE=EIGN or FREQ but
has not included an EIGR or EIGRL entry to perform a normal modes
eigenanalysis.
the message should be:
THE INPUT DATA BLOCK NAMED DYNAMIC AT POSITION
1-52101228
19 DOES NOT EXIST.
Documentation/DMAP Programmer's Guide - OUTPUT4 Record.
There is an error in the DMAP Programmer's Guide documentation of the OUTPUT4

record. In ASCII mode, word 3 in record 2 of each matrix is the number of
TERMS in the column, not the number of WORDS. In the binary format, word 3 of
record 2 is, in fact, the numbr of words in the column. The TERMS and WORDS
values are the same for RS and CS matrices, the TERMS value is WORDS/2 for RD
and CD matrices. The documentation of the OUTPUT4 file format in the DMAP
Module Programmer's Guide must be corrected. Note that the format of the ASCII
OUTPUT4 file (at least in this regard) has not changed since Version 65.
1-52145229
y Overflows
2008.0.0 (MD R3)
Elements - Model Summary - Element Summar
The Model Summary output will overflow when the number of any one element is
greater than 99999.
For example:
THERE ARE ***** HEXA
ELEMENTS. FIRST EID =
923513 LAST EID = 50685656

1-52233471
2007.1.0
Optimization/Design Sensitivity - Null we
ight sensitivity when MATi referenced with zero density
An optimization job may produce null weight sensitivity coefficients for i-th
design variable while some shell elements (CQUAD4,8,R,CTRIA3,6,R) are being
designed by design varaible j that reference a MATi entry with zero density.
Avoidance: place numerical small number (1.E-12) in the zero density field of
a MATi entry.
1-52240428
2007.0.2
FM 316 (IFPDRV) DMIG
External Superelements - SOL600,101 - U
SOL 600 with external superelements will fail with the message:
ILLEGAL DATA ON BULK DATA ENTRY DMIG
DMIG *KAAX
5
1
+000001
*+000001
5
1 2.347553830D+05
+000002
1-52299341
2007.1.0
Optimization - DVxREL1 references a desig
n variable ID more than once - Job Fail in DOPR1C
DVxREL1 is NOT allowed to reference a design variable ID more than once. This
user input error will cause the analysis to fail in DOPR1C without a meaningful
message. This should be trapped as a user input error and the following
message should be output:
*** USER FATAL MESSAGE 7610 (DOPR1C)
DVPREL1 entry ID =
20 reference a design variable ID more than once.
User INformation: The Dvxrel1 entry does not support multiple references to
the
same design variable ID.
User Action: Remove the duplicate reference to the same design varible ID.
1-52301750
2007.0.2
SOL 600 - memory error in gpforce transla
tion to op2 - Sever Warning in Nastran/Marc postprocessing
A memory management error in the SOL 600 t16op2 translator for grid point
force may cause an analysis to fail with the following message:
T6GPFRC2: iLINE=
49
** Severe Warning in Nastran/Marc postprocessing - Logic error #

subroutine T6GPFRC2
-
Must stop

1-52301828
SOL 600 - CBUSH, GPFORCE - Wrong Answers
9214 in
When using CBUSH elements in either MSC.Nastran 2005r3 or MD Nastran R2 SOL600,

there is an error in the grid spring forces:
For v2005r3, the spring force output takes the form:
node 36 spring force from spring id 1
-0.3779E-05 0.0
0.0
-0.3779E-05 0.3576E-08 0.0
-0.3779E-05 0.3576E-08 0.5531E-03
As seen in this examplet, it repeats the results for the previous response in
each of the other directions... this should have been:
0.0
0.5531E-03
-0.3779E-05 0.0
0.0
0.0
0.0
0.3576E-08
0.0
This happens as above when PARAM,MARCBUSH,1 is used for either 2005r3 or MD R2.
If in MD R2 PARAM,MARCBUSH,-1 is used, then the output in the f06 is:
node 36 internal force from element 26
0.0000E+00 0.0000E+00 0.0000E+00
0.0000E+00 0.0000E+00 0.0000E+00
Which is, of course, incorrect.

Files are attached for v2005r3 and MD R2.
1-52308971
2007.1.0
3D Contact - SOL 101 or 400, the 3D Conta
ct job failed with SFM 4289 (SPEND1D)
When running 3D Contact in SOL 101 or 400 with linear behavior solid elements,
job may fail with the following message
*** SYSTEM FATAL MESSAGE 4289 (SPEN1D)
CORE IS INSUFFICIENT BY A BASE10
1-52374131
2007.1.0
Dynamics - FRF and DMP - SFM 6144
If DMP is requested in a SOL 111 run with FRF generated loads then the run will
fail with SFM 6144 in the MERGE module.
compile freqrs
alter 'merge
,,,ppf,,expand',''
merge
,,,frfppf,,expand,/ppfe/1
compile semfreq
alter 'equivx frfppf\/pxf',''
equivx ppf/pxf/-1 $
endalter
1-52415018
e
2007.0.1
Installation - SGI ProPack 5 - end of fil
The following error may occur in MSC Nastran or MD Nastran during installation
on an SGI ProPack Altix system:
./mscsetup: line 14976: syntax error at line 14976: ènd of file' unexpected
The error is caused by a bad version of "KSH" on the OS. It is known that
ksh-93r-12.9 has this problem. You can determine the version of ksh installed
with the command "rpm -qa | grep ksh".
Avoidance:
1) Backup the current ksh on the system.
2) Install the ksh in the attachment.
1-52425192
SET - UFM 3001
2007.1.0
Component modes - PARAMs FIXEDB and AUTOQ
If both PARAMs FIXEDB and AUTOQSET are specifed then UFM 3001occurs in the
UPARTN module in subDMAP SUPER3.
compile super3
alter 'if ( seid=0 )'(3),''
if ( seid=0 and fixedb>-1 ) then $
1-52459991
2007.0.2
ncorrect Default values
Documentation/QRG - SOL 600 - DMIGOUT - I
The default value of "1" for the DMIGOUT-ICTRL, IFREQ and ICORD as shown in
the QRG(MD Nastran R2) is incorrect.
The correct default value is 2, 1 and 2 respectively for these fields.
ICTRL Controls type of matrix. (Integer; Default = 2)
1=element matrices
2=global matrices
3=element and global matrices
IFREQ Controls how often the matrices are output (Integer; Default = 1)
1=output at every increment
2=output every other increment, etc.
-1=output only at end of the subcase.
ICORD Controls matrix output coordinate system (Integer; Default = 2)
1=Nastran basic coordinate system
2=current transformed coordinate system (at the start of the run, this is the
Nastran
global coordinate system).
1-52650292
2008.0.0 (MD R3)
Linear Contact - BCONTACT - Wrong Answers
Linear contact may lead to incorrect results.

Avoidance:
Too rigorous convergence criteria may lead to false results or
divergence. Set the CONV field of the NLPARM entry to P instead of its
default, UPW.
1-52657971
s
2007.1.0
DMP - SuSE 10 / IA64 - mpirun: Bad addres
Some, but not all, SuSE 10 IA64 systems get an error while running DMP:
mpirun: Bad address
It is unknown what specific configuration or package causes this error.

Avoidance:
- Upgrade to MD 2007 and use either HP/MPI ("proc=hp hpmpi=yes" on the command
line) or Intel/MPI ("proc=intel intelmpi=yes").
- Use MD R2.1
1-52721371
2008.0.0 (MD R3)
RAM,LFREQ - UFM 3047 (GKAM)
DMP/Frequency Response - DOMAINSOLVER, PA
Use of PARAM,LFREQ in a DMP modal frequency response analysis may result in the
fatal message:
*** USER FATAL MESSAGE 3047 (GKAM)
NO MODES HAVE BEEN SELECTED FOR USE IN THE ANALYSIS. THEREFORE A MODAL
FORMULATION CANNOT BE MADE.
0FATAL ERROR
1-52721829
Eigenvalue Analysis - WEIGHTCHECK(SET=(G,A))=YES and PARAM,MH
RED,YES - Wrong answers
If PARAM,MHRED,YES is active then the WEIGHTCHECK printout for the A-set will
show a reduction in mass from the G-set printout. But this will not affect
the subsequent results in the run or in a subsequent restart.
Avoidance: Insert PARAM,MHRED,NO.
1-52750618
2007.0.2
ID, Unexpected Answers
Elements - PBUSHT and PBUSH with the same
No errors are produced if PBUSHT and PBUSH with the same ID are entered. When
this happens, the PBUSH entry can wipe out the intended PBUSHT entry and
produce incorrect results.
1-52791051
g data in XDB
2007.1.0
Composites - PCOMP, PARAM,POST,0 - Missin
Layered composite stress results may be missing from the xdb for SOL 106.
1-52819821
2008.0.0 (MD R3)
Miscellaneous - Incorrect ReplicatorSymbo
l lead to UFM307 ILLEGAL NAME FOR BULK DATA ENTRY
When using the record replicator an input of a "-" instead of an "=" lead to
the fatal message:
USER FATAL MESSAGE 307 (IFPDRV) ILLEGAL NAME FOR BULK DATA ENTRY
which made it difficult to find the actual input error.
1-52841658
sing Output
2007.1.0
Modal Participation Factor - PFMODE - Mis
Modal participation factor (PFMODE) is not output when even one meaningless
direction is specified. For example, if there is no response in the T1 and
the T2 direction and a set references either as shown below, the participation
factor for the T3 direction will not be output.
$ structure gird
set 2 = 105/T3, 104/T1
$set 2 = 104/T1
$set 2 = 104/T3
$ not ok
$ not ok
$ ok
$set 2 = 105/T3, 104/T3 $ ok

$ fluid grid
set 3 = 1020, 1021, 1022
pfmode(structmp=all) = 2
1-52953651
rect GPFORCES
2007.1.0
SOL 400 - GPFORCE, CQUADR, CTRIAR - Incor
In SOL 400, the GPFORCE outputs computed for the nonlinear analysis are wrong.
Any deck with GPFORCE output request for QUADR and/or TRIAR in SOL 400 will
show that the GPFORCEs are not balanced.
1-53071681
2008.0.0 (MD R3)
quencies Output
Element Strain Energy - OFREQ - Wrong Fre
A memory overrun processing the OFREQ list may result in incorrect frequencies
beign out and/or strange characters in the output.
1-53135565
2007.1.0
PTX4) on ILP64(mode=i8)
MODE=I8 - OUTPUT4, INPUTT4 - SFM 6445 (IN
INPUTT4 may fail on i8 systems with the following message:

EXPECTED
78 WORDS
1-53159901
2008.0.0 (MD R3)
66)=8192 - TAUCS Solver may crash
Numeric Methods - Decomp, SOLVE, SYSTEM(1
I can get xx0rst0 to crash. That is VVPR 1-60306461. Other jobs now work
though, So I will mark this as verified... jjg3/21/08
There have been many fixes imported since this original report, and I have
not been able to get the solver to crash in R3. I am marking this as fixed.
...trk
If the TAUCS solver is selected by setting SYS166=8192, then an analysis may
crash.
Avoidance: Do not use taucs.
1-53172511
2007.1.0
DBC - PARAM,POST,0 - DBC Module GPSTRAIN,
STRFIELD, Access Violation (Signal 11)
A model requesting STRFIELD=ALL and GPSTRAIN=ALL fails in the DBC module with
an access violation during data recovery of the superelements.
Avoidance: Remove the STRFIELD request.
1-53345233
orrectly.
2007.0.2
SOL 600 - NLAUTO - Loads not translated c
This example has the final time specified using NLAUTO. For SOL 600 dynamics
problems, the fianl time is goverened by a combination of TSTEPNL and TABLED1
entries, any final time specified by NLAUTO is ignored. This also applies to
the intial time step. For SOL 600 dyanmics, most other entries specified on
NLAUTO are used with the exception of NRECYC, IDTAB, DAMP, IDMPFLG adn IPHYS.
For statics, the initial time step and final time from NLAUTO overrides that
provided by NLPARM. The QRG will be revised to clarify this situation. For
the attachments provided, using the MD R3 released version, the Marc input
decks correctly reflect the philosophy used in SOL 600 - E Dickerson 7/11/2008
Patran 2006 created a SOL 600 input deck that contains NLAUTO and TSTEPNL
cards that span the same time. Whent the job is submitted, the point load is
not properly translated into the MARC input deck. It only has a point load
list that are numerical zeroes. It does not creat the second list showing the
full load.
Avoidance: NLAUTO should not be used. Manually changing the number of
increments in the TSTEPNL from 100 to 101, the MARC deck is translated with
both lists of point loads.
1-53444861
2007.1.0
SOL 400 - CQUADR, CTRIAR, PCOMP - Layer s
trains/stresses are wrong for composites in SOL 400
The layer stresses and strains computed for composite QUADR/TRIAR are wrong in
SOL 400.
1-53562418
2007.1.0
Single and Multipoint Constraints - PARAM
,AUTOMSET - SFM 4276, EC (bldpk) in GP4
Conflicts between an independent or dependent set membership of dofs can lead
to the following error message:
ERROR CODE
211 PID= 0
when param,automset,yes is being used.
Avoidance: Omitting this parameter can help in finding the problem.
1-53658793
2007.1.0
del with QUAD and HEXA Elements
GPSTRAIN - Missing GPSTRAIN Output for Mo
The Z1 and Z2 strain output is missing from the output of a model with QUAD4 or
QUADR and a HEXA element is present. However the MID and CURV results are
output. Removing the HEXA element allows the Z1, Z2 and MID results to be
output. A model with only QUADR elements using cylindrical coordinates
demonstrates similar symptoms to the QUADR/HEXA model, i.e., only MID and CURV
output is obtained.
Avoidance: The STRAIN request set must be limited to shell elements and then
GPSTRAIN=ALL will provide the correct results for the FIBRE option in the
surface declaration, otherwise nastran only provides MID and CURV strain
output. We have confirmed this on multiple models.
1-53723270
2007.0.1
ADAMSMNF - Missing mnf file on AIX
MD Nastran R2 and MSC.Nastran 2007r1 contain an error on AIX platform which for
some variations of the ADAMSMNF case control command results in no mnf output
and the following messages:
*** USER FATAL MESSAGE 7811 (MNF_Error)
*** SYSTEM WARNING MESSAGE 7810 (AFERRM)
The known variation of the ADAMSMNF command that causes the error includes the
keywords FLEXONLY and MINVAR. This problem has been corrected in Version
2007.0.2 and subsequent releases.
Avoidance: Avoid these keywords.
1-53795821
2007.1.0
Connection Elements - CWELD, SWLDPRM - PR
OJTOL is not recognized for CWELD with MSET=ON
The projection tolerance parameter PROJTOL specified on the SWLDPRM Bulk Data
entry is not recognized for CWELD elements with MSET=ON option.
1-53832781
2007.1.0
ecks nltsr03 and nltsub03
SOL 400 - UFM 1126 with scr=post in tpl d
If scr=post (or scr=no with NASTRAN SYSTEM(316)=7 or 19), then SOL 400 may fail
with USER FATAL MESSAGE 1126.
1-53887611
DMP/Eigenvalue Analysis - SFM 3034 in Lanczos
Lanczos sometimes has a problems detecting rank-deficient sets of Lanczos

vectors and this may lead to the folloiwng fatal message:
Avoidance: Not running dmp or setting system(166)=48 may avoid the problem.
1-53894031
2007.1.0
Elements - CBEAM3 - Stress recovery for c
beam3 referencing pbmsect may fail in SDR2 or GPSTRPBX
Full stress recovery for CBEAM3 element referencing PBMSECT entry with
isotropic or composite material, may fail in SDR2 or GPSTRPBX module.
Avoidance : If possible, turn off full stress recovery by removing
'param,arbmss,yes' in the input deck.
1-53923901
2007.0.0 (MD R2)
c matrix - Inefficient runtime
External Superelements - k4 , unsymmetri
In version 2005.5, if an external superelement is used in an acoustic cabin

analysis, and element structural damping is included in the reduction run, the
k4 matrix may be generated as unsymmetric which may cause substantial increase
in the runtime.
Avoidance: Add the following alter in the assembly run.
COMPILE EXTIN NOLIST $
ALTER 'EQUIVX.*X\_K4'
MODTRL K4XX////6 $
ENDALTER $
1-53986469
2007.1.0
tion or Signal 11
Eigenvalue Analysis - READ - Access Viola
A dense large mass matrix (~95000 dof and 0.5 dense) will cause the default
ordering method to encounter an access violation on PC Windows 32 bit systems
and a Signal 11 on unix system.
Avoidance: Use NASTRAN SYSTEM(206)=132 in the input file or sys206=132 on the
command line as an optional keyword.

1-54149209
2007.1.0
Connection Elements - CFAST, CWELD - Bad
TBEmatrix if all three GS, GA, and GB are specified
If GS, GA, and GB are all specified on the CFAST or CWELD elements a bad TBE
matrix occurs. In future releases GS will be ignored if GA and GB are
specified.
1-54228489
2007.1.0
Composites - PLCOMP, PCOMPLS - Blank DIRE
CT field causes entire bulk data entry to be ignored
If the DIRECT field on the PLCOMP or PCOMPLS bulk data entry is BLANK, then the
entire entry is ignored. .
1-54239221
2007.1.0
d to SFM 7620 (EMG)
SOL 400 - RBE and no differential may lea
In SOL 400, if there are kinematic elements (RBEs) and the differential
stiffness is not required to be updated, SYSTEM FATAL MESSAGE 7620 will be
issued by the EMG module.
1-54248591
for SOL 600
2008.0.0 (MD R3)
Documentation/QRG - MATF format incorrect
The MD R2 QRG failed to update the MATF entry for fields that are relevant to
SOL 600.
Avoidance: Please refer to the MD R2 Release Guide or MD R3 QRG.
1-54255321
2008.0.0 (MD R3)
causes SFM 5423 (MPYAD1)
MDACMS - DOMAINSOLVER, EXTSEOUT and CSETi
An MDACMS analysis with external superelements and CSETi (or BNDFREEi) will
fail with
compile phase1dr
alter 'if ( seid=0 and mdacms and nooset',''
PARAML USET0//'USET'//////'c'/S,N,NOcSET/
'r'/S,N,NOrSET
$
if ( seid=0 and mdacms and nooset>-1 and
nocset<0 and norset<0 ) then $
1-54260851
2008.0.0 (MD R3)
envectors if MDACMS is used
ACMS - DOMAINSOLVER, EXTSEOUT - Wrong eig
EXTSEOUT outputs wrong eigenvectors if MDACMS is used. One symptom is that

the following case control resulted in a vector of only the first mode being
printed and this vector was all zeroes. This results in zero eigenvectors for
every mode in the assembly run.
***Case Control Command***
EXTSEOUT(ASMBULK,EXTBULK,EXTID=1)
SUBCASE 1
METHOD = 1 SET 1=1080794

VECTOR(PRINT,CID,SORT1)=1
compile mdphs1b
alter 'if ( dens=0',''
paraml
vxsparse//'null'////s,n,nullvxp $
if ( nullvxp<0 ) then $
1-54337337
2007.1.0
SOL600 - Large Field Format PBUSH fails Severe Warning in SOL 600 translator
Iin SOL600 a PBUSH that is defined using the large field format fails during
translation with following message:
** Severe Warning in SOL 600 translator - there appears to be no PBUSH
associated with CBUSH
1
1-54353683
2007.1.0
envector output
Acoustics - METHOD(STRUCTURE) - Extra eig
In a fluid-structural analysis, if only structural modes are requested with

METH(STRUC) then the eigenvector data recovery contains extraneous modes and
displacements for the fluid degrees of freedom. This error does not affect the
answers in a frequency or transient response analysis.
compile modefsrs
alter 'if ( nseig',''(,8)
IF ( NSEIG>0 AND NFEIG>0 ) THEN $
alter 'paraml mif',''
paraml mif//'trai'/1/s,n,nomif//s,n,nomifx $
if ( nomifx>-1 ) then $
alter 'merge
lammats'
else $
equivx mis/mi/-1 $
equivx lammats/lammat/-1 $
endif $
compile semr3
alter 'splitfs=',''
splitfs=(seid=0 and novgfs>0 and not(fluid)) $
alter 'trnsp.*vvfs'(,-1)
if ( methfl>0 ) then $
endif $
alter 's,n,nmf',''
paraml cmphof//'trai'/1/s,n,nmf//s,n,nocmphof $
if ( nocmphof>-1 ) then $
alter 'diagonal cmmif'(,-1),''
if ( splitfs and nocmphof>-1 ) then $
alter 'merge.*cmphof'
else $
merge
,
,goq,,, ,vofx/goqq/1 $
endif $
alter 's,n,nmf'(2,-1),''(2,0)
if ( splitfs and nocmphof>-1 ) then $
alter 'call newlamax'

else if ( splitfs ) then $
merge
,
,,,cmpho, ,vofx/cmphoxx/1 $
equivx cmphoxx/cmpho/-1 $
merge
,
,,,cmpha, ,vafx/cmphaxx/1 $
equivx cmphaxx/cmpha/-1 $
endalter
1-54367171
2007.1.0
be incorrectly issued
Elements - UWM 7651 for QUADR elment may
The UWM 7651 for QUADR is issued to warn user that a QUADR element may have
very small angle between two sides of the element so that a gird point normal
vector is unable to be defined. However, this message may be incorrectly issued
for very small retangular elements (1.0-4 on each side).
1-54371211
ess Violation
2008.0.0 (MD R3)
Linear Contact - BCONTACT, RBE, MPC - Acc
A linear contact model in SOL 101 that contains RBE elements or MPC equations
will fail with an access violation.
1-54381101
(UPARTPR)
2008.0.0 (MD R3)
External Superelements - CSET - SFM 6143
An external superelement analysis with C-Set specified wll fail with the
message:
*** SYSTEM FATAL MESSAGE 6143 (UPARTPR)
SPECIFICALLY:
The number of rows
in KSVV is not equal to the size of the V-set
The number of columns in KSVV is not equal to the size of the V-set
User Information: Size of input matrix and DOF sets:
KSVV
: Rows= 4408578 by Cols= 4408578
Set sizes: Major (V-set)= 4443956
Set0 (O-set)= 4443394
Set1 (COMP-set)=
562
Avoidance:
Insert the following DMAP alter
$ alter avoidance for CR 1-54381101

compile mhred
alter 'merge.*gots,,,gotf'
partn
kvv,vvfx,/koo,,, $
partn
mvv,vvfx,/moo,,, $
call modmodes uset,phio,phic,kv,moo,koo,gots,mv,vvfx,vtfx/
goq,mqq,kqq/norc/1/true/false $
alter 'endif \$ novvfs'(4),''
alter 'call modmodes',''
call modmodes uset,phio,phic,kv,moo,koo,got,mv,,/
goq,mqq,kqq/norc/1/true/false $
endif $ novvfs>0
compile semr3
alter 'merge.*kqqf,,,kqq,vfs'(,-1)
if ( norc>-1 ) then $
partn
kqq,vfs,/kqqf0,,,kqqs $
merge
kqqf,,,kqqs,vfs,/kqqw $
matprn kqqf0,kqqf/ $
else $
alter 'merge.*kqqf,,,kqq,vfs'
endif $
compile modmodes
alter 1,1
SUBDMAP MODMODES USET, CMPHO, CMPHRC, LAMMAT, MOO, KOO, GOT, MI,
vvfx,vtfx/
CMPHOX, MIX, KIX/
NORC/NOMVJJS/DOTRIP/uim5490 $
alter 'umerge.*uset'(,-1)
dbstatus vvfx//s,n,novvfx $
if ( novvfx>0 ) then $
merge cmpho,cmphrc,,,,vvfx/cmphv/1 $
NORM
CMPHV/CMPHVN $
delete /cmphv,,,, $
partn cmphvn,,vvfx/cmphon,cmphrcn,,/1 $
delete /cmphvn,,,, $
partn got,vtfx,/,,gorc,/1 $
else $
alter 'UPARTN.*USET,GOT'
endif $
1-54407131
2007.1.0
vergence problems in SOL600
SOL 600 - Material orientation causes con
Specifying a material orientation angle by referening a coordinate system may

cause convergence problems in SOL 600.
1-54412161
2007.1.0
matrix reordering routines
Large Models - SEQP - Integer overflow in
Large models that request more than 4gb of memory may fail with an integer
overflow in the metis or bend ordering routines.
1-54538461
External Superelements - PARAM,FIXEDB,-1 but no output reque
st fails with SFM 3001 in MODACC
A SOL 103 external superelement run with PARAM,FIXEDB,-1 but no output request
fails with SFM 3001 in the MODACC module in the SEDISP sudDMAP.
1-54580661
2007.1.0
External Superelements - A large external
SE job fails with SFM 4276 in the INDXBULK module
A large external SE job fails with SYSTEM FATAL MESSAGE 4276, Error Code 3002
in the INDXBULK module due to an integer overflow in the SAVPS3 c all.
1-54629137
Heat Transfer - CQUAD8 - Wrong Answers
Steady state thermal analysis (SOL 153) of a plate structure with radiation
enclosures and a heat flux boundary conditions (Workshop 14 from the NAS104
training) produces wrong answers in MSC.Nastran 2007r1 and MD R2
Bob Harder May 1, 2008: The radiation matrix was modified for version 2007.
The change was made to avoid overshoot with a coarse mesh. This change should
affect mostly models with a coarse mesh. You can get the pre-version 2007
results by using PARAM,RADMOD,NO.
1-54644041
2007.1.0
SOL 600 - Access Violation in trgp1cx.F
A large SOL 600 resulted in a memory overflow in trgp1cx.F resulting in a

fatal message indicating an access violation.
1-54647811
2009.0.0 (MD R4)
SOL 400 - BCONTACT - SIM 8100 (NL3INT), S
FM 4276 (PACKI) or UFM 2010 (MCNTCOL)
SOL 400 contact problems may fail on some machines with the message:
*** SYSTEM INFORMATION MESSAGE 8100 (NL3INT)
No Lagrange Multiplier Degrees-of-freedom were found in Contact analysis..
% 0.4000 4 1 3.08E-01 2.49E-03 2.77E-02 1.000 0 1 0 5.73E-02
9.124E+01 6.46E-03 -5.296E-01
18536 2 1.00 0 5 0
9
analysis ends because of
2 errors in stress recovery
*** FATAL NON-LINEAR ELEMENT ERROR
or SYSTEM 4276 (PACKI) or USER FATAL MESSAGE 2010 (MCNTCOL)
Avoidance: For contact problems the PFNT rather than the AUTO method is
recommended. If the AUTO method is selected then switch to PFNT. If the
problem is being run on an i8 system, running on i4 may allow the problem to
complete.
No other messages are printed. Thanks.
1-54657775
ion
2007.1.0
SOL 600 - Incorrect Thermal Load Translat
When converting thermal loads, SOL 600 may create distributed flux entries that
reference tables that do not exist. This may lead to wrong answers.
1-54740198
Design Optimization - External Superelement and MODTRAK - Sys
tem Fatal Message 6551 (INPTX2)
If an external superelement is assembled into a SOL 200 run which also requests
mode tracking with MODTRAK and data recovery is requested for the external
superelement then the run may fail with SFM 6551 in the INPUTT2 module. This
error has been fixed in MD R2.1 when scr=yes; however, when scr=no the same
error occurs.
compile super3
alter 'IF ( DLOOP'(2,0),'IF ( DLOOP'(2,0) $
CALL EXTIN ,,,,,,XSOP2DIR,EXTDB,,,/
,,,,,,,,/
SEID/SETYPE/LUSETS/FALSE/S,NP $
1-54884981
2007.1.0
tion that has spaces in its path.
SOL 600 - Fails when running from a loca
SOL 600 fails when running from a location that has spaces in its path which
is allowed and common on Windows systems.
1-55020351
2007.1.0
Elements - PBRSECT/PBMSECT with CP/OP incorrect propeties when segments are nearly parallel
PBRSECT/PBMSECT with CP/OP may produce incorrect properties when segments are
nearly parallel and having different thickness. In addition, the properties
could be wrong if the length of segment is shorter than the thickness of the
segment.
Avoidance: merge two nearly parallel segments into one if possible

Analysis: 1. nearly parallem problem will be solved with new logic which is
more robust
2. a fatal message will be issued for segments with length
shorter than thickness
3. additional logic will be implemented to make sure first loop
is indeed the outmost of the cross section
1-55046437
2007.1.0
Incorrect element identified
Connection Elements - CFAST - UFM 2007,
The MODGM2 module does not identify the correct poorly specified CFAST element
id when the module issues a UFM 2007,
*** USER FATAL MESSAGE 2007 (EPTBED)
CFAST ELEMENT 110015 ORIENTATION VECTOR YIELDS BAD PROJECTION
Avoidance: If the CFAST definition has the GS field and GA/GB fields specified,
as needed for Patran, then try running with only GS specified and the GA/GB
fields blank.
1-55077699
s
2008.0.0 (MD R3)
Elements - TEMPP1, CTRIAX6 - Wrong Answer
TEMPPi entries are not designed to work with CTRIAX6 elements and will produce
incorrect results.
Avoidance: Define the temperature loading with TEMPD
1-55088236
Thermal Stress - TEMPP1 cannot be apply to CTRIAX6 - Unexpect
ed Answers, Missing UFM 4016
The CTRIAX6 element does not understand TEMPP1 data. It the data as zero and
no warning messages are issued. USER WARNING MESSAGE 4012 followed by USER
FATAL MESSAGE 4016 should have been issued.
See the documentation on TEMPP1 where CTRIAX6 is NOT on the types.
1-55090064
2007.0.2
g jid.ink contact interface file
SOL 600 - SOL 600, 153, BCONTACT - Missin
The contact interface file (jid.ink) that is created in a SOL 600, 153
analysis is missing on big endian machines. This causes the nastran analysis
to fail with the message: " ** Error in SOL 600 thermal contact iname=blank".
Avoidance: Other than running the analysis in a previous release or on a
little endian machine, there is no avoidance.
1-55104451
2007.1.0
st increment is linear.
SOL 400 - Lmfact is incorrect if the fir
The Lagrange multiplier factor LMFACT and PENFN is computed in NLSOLV for SOL
400 module by default. These values are not correctly computed if the first
increment is linear (converged imediately)
1-55106821
2007.1.0
essage, UFM 7019 in DSFLTF
Aeroelastic Analysis - Misleading error m
If the user attempts to constrain a flutter root that has both real and
imaginary parts as zero, the following message is produced:
*** USER FATAL MESSAGE 7019 (DSFLTF)
RETAINED FLUTTER EIGENVALUE NO. 0 HAS A VALUE OF (0.0,0.0)
USER INFORMATION: IT IS IMPOSSIBLE TO DETERMINE THE SENSITIVITY OF A ZERO
EIGENVALUE
USER ACTION: DETERMINE THE CAUSE OF THIS ZERO EIGENVALUE AND EITHER REMOVE
THE CAUSE OR DO NOT
SPECIFY THIS ROOT ON A DRESP1 ENTRY.
this message has two flaws:
a. the count on the retained flutter eigenvalue is low by 1
b. the message repeats for each design variable so that if there are 100 desgn
varibles the same message is printed 100 times.
User Avoidance: there is no avoidance and basic message is correct but somewhat
misleading and should not be repeated.
1-55217661
Optimization/Design Sensitivity - SSG2 - ATTEMPTING TO OUPUT
DATABLOCK WCHIH ALREADY EXISTS
DMAP MODULE SSG2
, WHICH ALREADY
The above error message appeared in a SOL 200 run with
multiple boundary conditions, some of which had design
not.
A SOL 200 analysis with multiple subcases and multiple
some of which have design responses and others that do
message;
204 NAME = FPA

three subcases with
response and others did
boundary conditions,
not may fail with the
DMAP MODULE SSG2

, WHICH ALREADY EXISTS
204 NAME = FPA
Avoidance: The dmap changes required to remedy the problems would be

extensive. The best option would be to contact MSC when it appears that a job
of the type described above is failing in an way that cannot be diagnosed.
1-55221261
2007.0.1
Miscellaneou - Missing Timing Constants l
eads to UWM 6080 (TMALOC) - IA64 mode=i8 - Montecito
Users may encounter "USER WARNING MESSAGE 6080 (TMALOC)" on Montecito systems
running ILP64 (i9).
Avoidance: Create Timing constants as descriped in the IOG.
1-55221287
chips
2007.1.0
SMP - Tjoin error - IA64 ILP64 Montecito
Fixed in rnd 33 with INTEGER used instead of "int" in the parallel.c routines.
MD Nastran may abort on an SMP parallel runs on Montecito chips running ILP64
mode=8. with:
FATAL ERROR:
thread: 3664992
routine: tjoin
reason: tid_index_lookup
error: -999
Avoidance:
No know avoidance at this time.
1-55226901
2007.1.0
(TA1NLM2), LOGIC error 9301
SOL 400 - Nonlinear Materials - SFM 6352
The following error message occurs with a big model using a large buffize of
655537.
*** SYSTEM FATAL MESSAGE 6352 (TA1NLM2)
LOGIC ERROR: 9301
PROGRAMMER INFORMATION: NastType= 33, EID=
100, PID=
60
Avoidance: To avoid the fatal, run with smaller BUFFSIZE, for example,
BUFFSIZE=32897
1-55227367
2007.1.0
tressed design - UWM 7531
Optimization/Design Sensitivity - Fully s
For an optimization model, if the model does not contain PROD, PSHEAR, PSHELL,
or PCOMP or if the model contains one of the aforementioned entries, but a
property is not defined for a fully stressed design, the following warning
message (UWM 7531)
NO DESIGNED PROPERTIES IN FULLY STRESSED DESIGN
will be issued.
Avoidance: If you are not using Fully stressed design, the above warning
message can be ignored. If you are using fully stressed design, check your
model to make sure that designed properties are deifned for fully stressed
design
1-55310851
2008.0.0 (MD R3)
rrect Default Value
Documentation/QRG - PARAM,MARVFCUT - Inco
In QRG of 2007r1 and MD r2, the description "Default is 0.001" of

PARAM,MARVFCUT is incorrect.
The default is 0.0001.
1-55343290
on of RTHRESH
2008.0.0 (MD R3)
Documentation/QRG - GROUNDCHECK Descripti
The QRG description of the value of the describer RTHRESH incorrectly states
that the default value is 10%. This value needs to be change to a fraction,
e.g., the 10% must be changed to 0.10. Otherwise the grounding forces will NOT
be output. In fact, if RTHRESH is greater than 1.0, no grounding forces are
output.
Avoidance: Always have the RTHRESH value less the 1.0 and DATAREC=YES will
generate output.
1-55358201
2007.1.0
SOL 400 - RBE2, RBAR, and RJOINT give div
ergent results if cylindrical coordinate system is used.
In SOL 400, the solution will diverge if a cylindrical coordinate system is
used for RBE1, RBE2, RBAR, and RJOINT elements.
1-55378981
2007.0.2
SOL 600 - Translation error for MAXITER p
arameter of NLSTRAT with multiple SUBCASEs
When multiple SUBCASEs are defined in the case control section, the maximum
number of iterations that is defined in the MAXITER parameter of the NLSTRAT
is not translated correctly.
1-55412111
only
2007.1.0
SOL 400 - SFM 4276 (UNPACK), EC 31 aix i8
SOL 400 jobs may fail on aix i8 systems with the message
ERROR CODE
31 PID= 0
*** USER INFORMATION MESSAGE 4276 (UNPACK)
BIOMSG: ERROR
31 HAS OCCURRED IN ROUTINE UNPACK , FILE INDEX =
0.
STATUS =
0
Avoidance: Run on the default i4 system.
1-55442675
2007.1.0
SOL 400 - SFM 4549 (NBEM2S) on aix i8 sys
tems in job nlstl01b in redseai8 system.
SOL 400 jobs may fail on aix i8 systems with the message:
*** SYSTEM FATAL MESSAGE 4549 (NBEM2S)
SINGULAR (C+KBRR) MATRIX ENCOUNTERED FOR BEAM ELEMENT 4
Avoidance: Run on the default i4 system.
1-55443121
2007.1.0
ing duplicate TABLED id
SOL 700 - Incorrect error message indicat
SOL 700 may incorrectly output the following error message:

*** ErrorMD Nastran Input 103103
TABLED1
2
repeated load curve id (
2)
Avoidance: The error may be avoided by renumbering TABLES entry.
1-55502466
2007.1.0
ect Default for RIGID command
SOL 400 - ANALYSIS=NLTRAN, RIGID - Incorr
In SOL 400, the default for the RIGID case control command should be
RIGID=LAGR not LINEAR when ANALYSIS=NLTRAN.
Avoidance: Explicitly set RIGID=LAGR
1-55735063
2008.0.0 (MD R3)
FM 5423 (MPYAD1)
ADAMSMNF - PARAM,AUTOQSET, SPCFORCES - S
If PARAM,AUTOQSET,YES is requested with ADAMSMNF command and SPCForces are

requested then the run will fail with UFM 5423 in the MPYAD module.
compile phase1b
alter 'ksf1'(2)
delete /kfs,,,, $
trnsp ksf/kfs $
1-55799501
2007.1.0
SOL 400 - OUTPUT(POST), SDR2 - UFM 2025
There is an error in SDR2 that affects SOL 400 jobs such that UFM 2025 will be
issued if there are kinematic elements and the OUTPUT(POST) Case Control
command is present.
1-55830681
2007.1.0
OR ON BULK DATA ENTRY UXVEC
Aeroelastic Analysis - UFM 315 FORMAT ERR
If the continuation of a UXVEC bulk data entry ends in field 9, the code
assumes there is more data for the entry and the next parent entry is processed
as a continuation. This will lead to USER FATAL MESSAGE 315, FORMAT ERROR ON
BULK DATA ENTRY UXVEC.
User Avoidance: A suggested avoidance is to add an additional LABEL and value
on an additional continuation vector with the value at 0.0.
1-55839394
2007.1.0
Miscellaneousl - DMIG - UFM 4508 (MTRXIN)
- a grid and component has been specified twice
If a DMIG entry defines the same component twice it will lead to USER FATAL
MESSAGE 4508. However, this message may not correctly identify the duplicate
components.
1-55876341
s Results
2008.0.0 (MD R3)
SOL400 - CQUADX, PSDNL1 - Incorrect Stres
Please see following message from Shiva.

Changhong
----------------------HI Sanjay, Changhong
This bug was initially assigned to me - I fixed it in cls 42966, 42974, 42983
and 42984. It should be working fine now. I thought I had closed it in Siebel.
Thanks.
Shiva
================================================================================
===========================
In SOL 400, the STRESS result of the nonlinear axisymmetric element CQUADX that
references property entry PSDNL1 is incorrect.
1-55892751
2008.0.0 (MD R3)
SOL 400 - SPC - Analysis may fail when th
ere is enforced motion in the upstream superelement
When there is enforce motion in the upstream superelement(s), SOL 400 job may
fail in the Phase 3 - data recovery.
Avoidance: There is no avoidance when there is non-zero enforced motion.
However, if Ys is null on the SPC entry, the error may be avoided by
substituting the SPC1 entry for the SPC entry.
1-55897608
2007.1.0
SOL 400 - NLIC - UFM 4533 (NLICLP)
In a nonlinear transient subcase the user want to reference a step from a

previous subcase (NLSTAT). If he use the first step as NLIC all works fine.
But if he uses the second step as NLIC two FATAL occure. (No initial conditions
found.)
If a SOL 400 nonlinear transient analysis references any step other than the
first step as an initial condition, NLIC, the analysis will fail with the
message:
*** USER FATAL MESSAGE 4533 (NLICLP)
THE SPECIFIED INITIAL CONDITION CANNOT BE FOUND IN SUBCASE 1141 STEP 1.
*** SYSTEM FATAL MESSAGE 3007 (NLICLOOP)
ILLEGAL INPUT TO SUBROUTINE NLICLP
0FATAL ERROR
1-55913381
2007.1.0
SOL 400 - QUADR, PLOAD4 - Follower force
stiffness symmetrical factor is wrong
In SOL 400, the computation of symmetrical factor for follower stiffness matrix
is wrong for the QUADR element. This leads to an unsymmetrical decomp rather
than a symmetrical decomp. Thus, the solution iis very inefficient for QUADR
with PLOAD4.
1-55934951
2008.0.0 (MD R3)
ponse - SFM 3001
Rotordynamics - UNBALNC for Frequence res
If an UNBALNC entry is used where MASS is set to a real value and therefore
there are no TABLEDij entries in the Bulk Data section then the job will
terminate with
*** SYSTEM FATAL MESSAGE 3001 (FRLG)
THE INPUT DATA BLOCK NAMED DITS
Avoidance:
AT POSITION
7 DOES NOT EXIST.
Insert a dummy TABLEDij entry.
1-55974341
2007.1.0
does not lead to UFM
Case Control - GROUNDCHECK - Format error
This form of the GROUNDCHECK command:

GROUNDCHECK(SET=ALL,DATAREC=ALL,RTHRESH=0.9)=YES
should trigger a UFM as DATAREC should not recognize "ALL" as only options YES
or NO exist.
1-55986678
2008.0.0 (MD R3)
tems in the TA1M Module
SOL 400 - May fail on ilp64 (mode=i8) sys
SOL 400 may fail on ilp64 systems (mode=i8) in the TA1M Module with the
followng fatal error.
*** FATAL NON-LINEAR ELEMENT ERROR
Avoidance: There is no avoidance other than running the default i4 system.
1-55992511
2008.0.0 (MD R3)
Documentation/QRG - Error in Table of Con
tents (affects SOL700, SPARSESOLVER and TIME entries)
There is an error in the Table of Contents (Bookmarks tab) of the MD Nastran R2

Quick Reference Guide. This pertains to the PDF file, not the printed book.
Under the Executive Control Statement Descriptions, the SOL700, SPARSESOLVER
and TIME entries are incorrectly buried under "Restrictions and Limitations of
MD Nastran Implicit Nonlinear".
1-56030282
41
2008.0.0 (MD R3)
Heat Transfer Analysis - TEMPBC - DBCMSG
The following error message may appear when TEMPBC entries are specified:
*** DBCMSG ERROR MESSAGE 41 FROM SUBROUTINE DBCEQE
ELEMENT
1000001 WAS PREVIOUSLY ELAS2
AND IS CURRENTLY A HEXA
THE DBC MODULES ASSUMPTIONS ARE UNIQUE ELEMENT IDENTIFICATIONS WITHIN A
SUPERELEMENT OR RESIDUAL STRUCTURE.
This error is caused by the internal generation of CELAS2 entries with element
ids of existing elements.
1-56095478
2007.1.0
Optimization/Design Sensitivity - BUCKLIN
G - Missing Follower Force leads to wrong answers.
When an optimization job perform linear buckling response optimization, the
follower force is not included due to a missing table. The eigenvalues do not
match with that produced in a SOL105 run.
Avoidance: Use the following alter:
compile fea
alter 'l sekdr',''
CALL SEKDR,
SLIST,EMAP,PVT,CASES,CASEM,USET,GPECT,EST,
CSTMS,MPTS,DITS,UG,ETT,EDTS,BGPDTS,SILS,MAPS,
EQEXINS,GM,GOT,GPSNTS,slt,,SCSTM,MJJ,DEQATN,
DEQIND,,,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,THETAM /
KDAA,KDMG,KDSF,KDJJ,KDGG,KDSS,
/
RSONLY/ERROR/LUSETS/COLNO/'BKL0 '/FALSE/FOLLOWK/
'ALL ' $
1-56095773
ng Answers
2008.0.0 (MD R3)
SOL 400 - CQUADX, PLPLANE - UFM 6348, Wro
A SOL 400 job with CQUADX elements that reference a PLPLANE entry that
reference MAT1 rather than the required MATHP material will issue the correct
fatal message:
*** USER FATAL MESSAGE 6438 (MAT)
MATHP ENTRY ID =
1 CAN NOT BE FOUND FOR FINITE DEFORMATION
(HYPERELASTIC) ELEMENT ID =
1.
but the job will continue and produce incorrect results.
1-56123220
2007.1.0
SOL 400 - RBE1 - SFM 6935 (EMGPOM)
SOL 400 with an RBE1 that ran in SOL 106 may fail with a message of the form:
*** SYSTEM FATAL MESSAGE 6935 (EMGPOM)
ELEMENT-ID =
5390411 FILE TYPE = 1
15
14
196
0
INCONSISTENT NUMBER OF COLUMNS OR TERMS SENT BY ELEMENT ROUTINE FOR
PACKING OUT BY EMGPOM, OR INVALID
INFORM-OUFORM COMBINATION.
6
1-56149641
2008.0.0 (MD R3)
e Command Not Documented
Documentation/QRG - SPARSESOLVER Executiv
The MSC.Nastran 2007 SPARSESOLVER Executive Statement is not documented in the

MSC.Nastran 2007r1 Quick Reference Guide.
Avoidance: Use the MD Nastran R2 Nastran Quick Reference Guide for information
on the SPARSESOLVER Executive Statement. System Cell 206 (DCMPSEQ) also needs
to updated to reflect the default change from method 4 to method 8.
1-56172081
2007.1.0
SOL 400 - Kinematice elements (RBAR etc.)
and superelements results in UFM 5217
For SOL 400, if the kinematic elements are used in conjunction with
superelements, the job will aborts with USER FATAL MESSAGE 5217 in the GP1
module.
1-56172149
2007.1.0
ic elements (RROD)
SOL 400 - Missing MPCF output for kinemat
For SOL 400, under certain condition, the MPCF output will not be printed in
f06 file for a model with RROD elements and 3D contact.
1-56172177
2007.1.0
entry cannot be mixed.
SOL 400 - CONV=UPW and CONV=PV on NLPARM
For SOL 400, if step 1 specifies CONV=UPW, and step 2 specifies CONV=VP on
NLPARM entry, the CONV used for both step 1 and step 2 is CONV=VP.
1-56189563
2007.1.0
297 (TQD4D) Incorrectly issued
Rigid Elements - TEMP(LOAD), SSG1 - UFM 4
For a model with many RBE2s and/or RBE3s that use the Lagrange rigid elements
with thermal load, the following misleading error message may be issued. The
problem is due to the BGPDT table being corrupted.
*** USER FATAL MESSAGE 4297 (TQD4D)
QUAD4 ELEMENT WITH ID =xxxxxx
In this case, the element that is referenced by the fatal message does not
have an interior angle anywhere close to 180 degree.
Avoidance: There are 2 partial avoidances:
1. The job will run with mechanical loads.
2. The job will run with thermal loads provided alpha is not used on the
rtype elements
1-56470203
2007.1.0
ARL - Incorrect Punch File
Optimization/Design Sensitivity - PBAR/PB
When both PBARL and BAR are designed in an optimization job and
ECHO=PUNCH(NEWBULK) is specified, the PBAR values may be the original property
values. Furthermore, internally generated PBAR entries that should be written
to the punch file as a comment, may be missing the preceding "$".
Avoidance: Manually update the PBAR entries and comment out the internally
generated PBAR entries.
1-56475731
2007.1.0
Documentation/IOG - FLEXlm - License Serv
ers separated by colon on windows not allowed
The IOG on page 39 fails to document that unix and windows require different
separators between the specification of multiple license servers.
Windows
requires the use of a semicolon while unix requires a colon. No error message
will be displayed on windows unless pause=yes is sepcified.
1-56544651
2007.1.0
DMAP - MAT3 contains incorrect descriptio
n in the NDDL - Inefficient restarts, Incorrect table print
The MAT3 record in the MPT table description in the NDDL is incorrect. This
may result in inefficient restarts if MAT3 entries are used and an incorrect
neutral or non-native file transfers involving the MPT data block.
1-56597055
2007.1.0
CD - UFM 6144 (PARTN1PR)
Exterior Acoustic - DOMAINSOLVER ACMS, SP
An exterior acoustic analysis that uses ACMS and applies enforced displacements
via SPC may fail with USER FATAL MESSAGE 6144 (PARTN1PR).
1-56614331
2007.1.0
SOL600 - DMIGOUT, KIND=1 - Does not work
DMIGOUT with KIND=1 specified is to output dmig matrices for those elements
specified; however, no elements will be output.
Avoidance: The only avoidance is to output all elements by using the default
KIND=2.
1-56627786
2007.1.0
d to Converge or Incorrect Result
SOL 400 - PARAM,LGDISP, BCONTACT - Failue
In SOL 400 3D contact analysis with large displacement, the job may fail to
converge or produce wrong results when there is a large rotation increment with
no contact occuring, followed by a subase with contact.
1-56636361
2007.1.0
FRFORC, ATTB=MAX - Incorrect Response, Failure DOPR3
SOL 200 jobs with FRFORC specified for RTYPE and MAX specified in the ATTB
field of the DRESP1 entry may produce incorrect response values if the enhanced
DRESP1 is itself slected as a constraint. The analysis may fail in the DOPR3
module if the enhanced DRESP1 is further referenced on a DRESP2 entry.
Avoidance: The enhanced DRESP1 must be expanded with one dresp1 for each
forcing frequency and, a separate DRESP2 entry with MAX in the EQID field to
include all DRESP1 must be used.
1-56636931
2007.1.0
Performance - MMD Reordering selected for
dense structures results in poor performance.
When METIS reordering is selected, it may failure due to any number of reasons,
including insufficient memory or too dense a structure. When METIS
fails because of a too-dense structure, MMD is selected, which gives very poor
performance. BEND should be selected rather than MMD.
1-56637009
ilure occurs.
2007.1.0
DMP - PRESOL may hang when a partition fa
When running DMP, the PRESOL module may hang on the slave nodes if it is unable
to partition the model into the required number of domains.
1-56679235
2008.0.0 (MD R3)
" contains bad contact definition
SOL 700 - "WORKSHOP 1 TAPERED BEAM IMPACT
The SOL 700 WORKSHOP 1 TAPERED BEAM IMPACT model contained an incorrect
contact definition and would not run. This has been corrected in MD R3.
1-56780151
2008.0.0 (MD R3)
sing Documentation
Multipoint Constraints - LOAD, MPCD - Mis
The MD R2 QRG for the LOAD Case Control command was not updated to indicate
that it may reference and MPCD bulk data entry. Remark 2 under the
documentation for the MPCD bulk data entry indicates that in dynamic analysis
the EXCITE ID is selected by the EXCITE ID of the ROAD1, RLOAD2, TLOAD1, or
TLOAD2, entries but this capability is not yet functional.
1-56880211
2008.0.0 (MD R3)
ments and UFM 9067 - Wrong answers
Shape Optimization - BNDGRID and superele
If shape optimization is requested in the presence of superelements then UFM

9067 will be issued but the run is not terminated. This may result in wrong
answers.
Avoidance: Insert following alter:
compile desopt
alter 'ENDIF \$ (AMBS'(,-1)
call prtsum /rstjunk $
exit $
endalter
1-56885001
bit Linux
2007.1.0
ADAMSMNF - Incorrect Inertia Tensor - 32
If ADAMSMNF is used on an x8664 computer with a 32 bit Linux OS, then the
Inertia Tensors may be wrong.
Avoidance:
1) Install the 64 bit version of the OS on x8664
2) Install MD R2.1 when it becomes available.
Note that the way to determine if an OS is 32 or 64 bits is with the "uname -m"
command. If the output is "x86_64" then the OS is 64 bits. If the output is
"i386" or "i686" then the OS is
32 bits
1-56928981
2007.1.0
Optimization/Design Sensitivity - RIGID=
LAGR - Lanczos with SFM7349 (LNNHERR)
Three independent bugs are identified in the report for a SOL200 job with
RIDID=LAGR Case Control command;
A Lanczos eigenvalue analysis in SOL 200 with RIGID=LAGR may fail with the
message:
being issued from the READ module. Several problems exist:
1) The differential stiffness matrix is not created.
2) Tthe Lagrange rigid element approach is not supported in SOL200 when the
grid points connecting rigid elements are being designed. A user fatal error
message should be issued.
Avoidance: Use the following dmap alter to avoid the first problem:
compile fea
CALL SUPER3,
CASEcc ,
,
crx
,
,PCDB
EMAP
,MAPS
SLT
,ETT
crj
,
USET
,SILS
GM
,PSS
,
DYNAMICS,BGPDTS
EST
,GEOM2S
INDTA ,KELM
,ditid
,GEOM4S
,EPT
GEOM3 ,GEOM4
CASERS ,errorn
BGPDTVU ,gpsnts
GDNTAB ,OINT
,
,
,
,
lcdvec ,
,errorg
,
,
xsop2dir,vgdr
mmcdb ,geom1qx
,kaa
kgg
,
,
ym
,
dtis
,dtindxs
,
UG
,QG
,
,
,
,
APP
/APP
FALSE /DROPT
DESCYCL1/FALSE
,UL
,
,qrg
,XYCDB
,EQEXINS
,GOT
,UOO
,PJ
,KFS
,
,CSTMS
,GEOM3S
,KDICT
,pvtbc
,PG
,MPT
,PTELEM
,MEDGE
,pvt
,PELSETS
,
,
,
,
,matpool
,
,
,
,
,
,
,
,
,
,pbrmsd
,
,qmg
,
,
,
/
/RSONLY
/FALSE
/DMRESD
,
,
,
,
,
,
,POSTCDB ,FORCE
,PVTS
,CASES
,
,LOO
,
,GPLS
,EDTs
,YS
,KSS
,QR
,
,
,MPTS
,DIT
,ECTS
,EPTS
,GPECT ,VELEM
,SCSTM ,
,
,
,GEOM1 ,GEOM2
,
,
,VIEWTB ,
,DEQATN ,DEQIND
,KSF
,KMG
,
,
,
,
,
,eht
,
,
,
,
,
,pcompts
,
,
,
,vgq
,vspcg ,vmpcg
,
,
,
,
,matpools,gei
,
,
,dmis
,dmindxs
,pbrms ,
/
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
/FALSE /FALSE /
/S,PFILE /S,CARDNO/
/PEXIST /ADPTINDX/
ADPTEXIT/false
'
'/dstspcf
false $
CALL SUPER3,
CASEcc ,
,
crx
,
,PCDB
EMAP
,MAPS
SLT
,ETT
crj
,
USET
,SILS
GM
,PSS
,
DYNAMICS,BGPDTS
EST
,GEOM2S
INDTA ,KELM
,ditid
,GEOM4S
,EPT
GEOM3 ,GEOM4
CASERS ,errorn
BGPDTVU ,gpsnts
GDNTAB ,OINT
,
,
,
,
lcdvec ,
,errorg
,
,
xsop2dir,
mmcdb ,geom1qx
,kaa
kgg
,
,
ym
,
,
,
UG
,QG
,
,
,
,
APP
/APP
FALSE /DROPT
DESCYCL1/FALSE
ADPTEXIT/false
'
'/dstspcf
false $
endalter
1-57011098
2007.1.0
routine TRANSD Divide By Zero
/true
/0
/rgsens /false
,UL
,
,qrg
,XYCDB
,EQEXINS
,GOT
,UOO
,PJ
,KFS
,
,CSTMS
,GEOM3S
,KDICT
,pvtbc
,PG
,MPT
,PTELEM
,MEDGE
,pvt
,PELSETS
,
,
,
,
,matpool
,
,
,
,
,
,
,
,
,
,pbrmsd
,
,qmg
,
,
,
/
/RSONLY
/FALSE
/DMRESD
/true
/rgsens
/false
/false
,
,
,
,
,
,
,POSTCDB ,FORCE
,PVTS
,CASadj
,
,LOO
,
,GPLS
,EDTs
,YS
,KSS
,QR
,
,
,MPTS
,DIT
,ECTS
,EPTS
,GPECT ,VELEM
,SCSTM ,
,
,
,GEOM1 ,GEOM2
,
,
,VIEWTB ,
,DEQATN ,DEQIND
,KSF
,KMG
,
,
,
,
,
,eht
,
,
,
,
,
,pcompts
,
,
,
,vgq
,
,
,
,
,
,
,matpools,gei
,
,
,
,
,pbrms ,
/
,
,
,
,
,
,
,
,
/FALSE
/S,PFILE
/PEXIST
/0
/false
/
/
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
/FALSE /
/S,CARDNO/
/ADPTINDX/
/false /
/false /
Elements - CSHEAR, MAT1 - EMG Module, Sub
The CSHEAR element may cause the EMG module to encounter a divide by zero when
material properties E and G exceed too large a range and NU is left blank on
the MAT1 entry.
This problem occurs on all shortword (32 bit) operating
systems. A long word (64 bit) operating system allows the job to run.
Avoidance:
Either specify an acceptable value for NU or reduce the range of
the E and G values on MAT1 entries that have large E and G.
1-57027307
ed.
2007.1.0
SOL 400 - M2PP case control command ignor
In SOL 400, a STEP with ANALYSIS=NLTRAN will not process the M2PP case control.
Avoidance: insert the following alter
compile nonlin
alter 'IF ( TSTATnew\<\>1 and NOMPP\>-1',''
if ( true ) then $
1-57050333
2008.0.0 (MD R3)
exception error
SOl 400 - ANALYSIS=NLTRAN, floating point
In SOL 400 with ANALYSIS=NLTRAN, with RBE2 elements and the RIGID=LAGRAN case
control option, the job fails with a floating point exception error. ents.
*** USER INFORMATION MESSAGE 6191 (nl3con)
*** UNABLE TO ACHIEVE CONVERGENCE FOR THE CURRENT INCREMENT OR TIME STEP,
TRY TO FIND THE BEST SOLUTION ***
*** REPEAT ITERATION, STOPPING AT LOWEST ERROR ***
%1.06250E-02
4 5 0.0313 4 2.54E+00 1.00E+00 1.25E+01 0.80 6 0 2.4E+03
2.020E+05 6.19E-02 -3.054E+00
431 6 0 9 38
*** BEST ATTAINABLE SOLUTION HAS BEEN FOUND ***
MAIN: For reference, A(MAINAL) = 401436, A(/SYSTEM/) = 36C4D20
MAIN:
A(/XNSTRN/) = 6C20000
MAIN: Exception occurred at address 01B91D42.
Although the model was apparently failing to converge a floating point
exception error should not be occur and Nastran should exit with a more
appropriate message.
Avoidance: Manually constrain degrees of freedom 456 on the solid elements
when using rigid elements.
1-57124547
Static Analysis - 3d surface contact - spcforces do not inclu
de contact forces
When using the new 3d surface contact in sol 101 and when the contact area
contains constrained grids then the equilibrium might be incorrect. The reason
is that the contact forces are not included in the spcforces. Please note that
this defect does not show up in sol 400.
1-57125046
functionable
Static Analysis - GROUNDCHECK - punch and noprint option not
The groundcheck options for noprint and punch do not work. In each case the
results are printed to the f06 file.
GROUNDCHECK(PUNCH) = YES
1-57178664
2008.0.0 (MD R3)
Eigenvalue Analysis - RESVEC - SWM 9142
( RESMODES )
When the following warning message is issued in the f06:
> ^^^
> ^^^ SYSTEM WARNING MESSAGE 9142 ( RESMODES)
> ^^^ THERE WERE PROBLEMS DURING THE RESIDUAL VECTOR EIGENVALUE EXTRACTION
> ^^^ USER INFORMATION: THE RUN WILL CONTINUE WITHOUT RESIDUAL VECTORS
> FOR THIS SET OF MODES.
> ^^^ USER ACTION: POSSIBLE AVOIDANCES:
> ^^^
1. SET F1<=0. ON EIGR OR V1<=0. ON EIGRL.
> ^^^
2. SPECIFY PARAM,RESVINER,NO.
> ^^^
residual vectors should not be calculated at all. However in this case
eigenvalues were calculated having negative generalized mass and infinite
stiffness:
48
48
1.000000E+35
3.162278E+17
5.032921E+16
-1.000000E+00
-1.000000E+35
49
49
1.000000E+35
3.162278E+17
5.032921E+16
-1.000000E+00
-1.000000E+35
compile resmodes
alter 'neigv1'(3,-1)
return $
endalter
1-57199497
2007.1.0
IFPDRV) in other solutions
SOL 600 - BRKSQL entry causes a UFM 307 (
The BRKSQL entry will cause solutions other than SOL 600 to fail with the
message:
ILLEGAL NAME FOR BULK DATA ENTRY BRKSQL
MDR3 beta (V2008.0.0) issues this message
POSSIBLE ERROR IN EXPONENT.
. 1 .. 2 .. 3 .. 4 .. 5 .. 6 ..
.. 10 .
++000002C:\MSC_APPS\MDR3B\BIN\MDNASTRANW.EXE
+000003
7 ..
8 ..
========
it should be ignored.
1-57203529
2007.1.0
h MPCY, Wrong Answers
MPCD - MPCD with RSSCON does not work wit
MPCD entries combined with RSSCON entries may not work correctly and may lead
to wrong answers. The MPCY value of Ym on the MPCY entry was not replaced by
that of MPCD entry.
1-57215871
2007.1.0
SOL 400 - UFM 9103 (NL3INT)
MD R2 Nastran SOL 400 nonlinear static simulation may fail with the following
message when there is insufficient memory:
*** USER FATAL MESSAGE 9103 (NL3INT)

A LOGIC ERROR was encountered WHILE writing data from 3D Contact Component
Database to DBALL
*** JOB DOES NOT CONVERGE AT THE CURRENT TIME STEP OR INCREMENT.
*** FATAL ERROR ENCOUNTED.
*** USER FATAL MESSAGE 1133 (GNXFST)
INVALID INPUT FIST NUMBER = 0
Avoidance: This message shows up when code try to write data from 3D Contact
Component Databast to Nastran Database but INSUFFICIENT MEMORY exists. The
message may also be output "INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE
NL3INT". Increase memory and rerun.
1-57215920
2008.0.0 (MD R3)
SOL 400 - MATORT - UFM 2042
SOL 400 does not support MATORT and if referenced by a PSOLID entry will fail
with the message:
*** USER FATAL MESSAGE 2042 (M3DCONT1)
1 FOR ELEMENT
1-57219403
D only model.
51585
Acoustic Analysis - PARAM,ASCOUP - UFM 6148 (GP5A1) with FLUI
A fluid only model will lead to the following fatal message and including
PARAM,ASCOUP,NO as directed will not solve the problem.
*** USER FATAL MESSAGE 6148 (GP5A1)
NO STRUCTURAL ELEMENTS FOUND IN THE BULK DATA FOR FLUID-STRUCTURE COUPLING.
USER ACTION: INCLUDE STRUCTURE OR USE PARAM,ASCOUP,NO TO AVOID FLUID-STRUCTURE
COUPLING.
compile phase0
alter 'acoustic=2','' $
if( ascoup='yes' and acoustic=2 ) then $
endalter $
1-57219431
2007.1.0
directory "c:/04_appl/scratc"
SOL 600 - marc command -
error, scratch
In SOL 600, nastran may truncate the sratch directory name specified on the
marc submittal command and this may lead to the message:
*** ISHELL PROGRAM
'c:\04_appl\nastran\md_r2_ccs\md2007\marc_8664\\tools\run_marc' STARTED ***
error, scratch directory "c:/04_appl/scratc"
does not exist
1-57297901
2007.1.0
ion fails, UFM 7681 (SOPMPD)
SOL 400 - QUADR, TRIAR - Element formulat
SOL 400 with QUADR or TRIAR elements may fail with the message:
*** USER FATAL MESSAGE 7681 (SOPMPD)
IN PLASTIC ANALYSIS, THE DELTA EFFECTIVE STRAIN ( -1.151181E-07 ) IS NEGATIVE
FOR ELEMENT ID = xxxx.

THIS MAY BE CAUSED BY UNRESONABLE MATERIAL PROPERTIES.
1-57309391
2007.1.0
Frequency Response Analysis - DLOAD entry
referencing null enforced motion - UFM 5423
A frequency response job with a DLOAD Bulk Data entry referencing null enforced
motion fails with UFM 5423 on a call to MPYAD in the FRLG module.
Avoidance: Remove reference to null enforced motion from the DLOAD Bulk Data
entry.
1-57340784
2007.1.0
SFM 4016 (TA1ETD), UFM 2016
Nonlinear Analysis - PCOMP, TEMP(LOAD) -
Nonlinear analysis with composites and temperature loads may fail in

MSC.Nastran 2007r1 and MD Nastran R2 with SYSTEM FATAL MESSAGE 4016 (TA1ETD)
indicating that there are missing temperature entries for some elements or
USER FATAL MESSAGE 2016 indicating no material properties exist.
Not sure why this CR was assigfned back to me.
I came across with other data file (CGAP with thermal load) and Nastran issue
SFM 4106 (TA1ETD) - there is not temperature data for cgap elements - even
though temp is defined at both end- See bdf file 'thermal-cgap.dat'
1-57406941
2007.0.2
SOL 400 - Moment-carrying Glued Contact f
ailed when contacting grids have coordinate transformation
In SOL 400, moment-carrying glued contact may fail when contacting grids have
a coordinate transformation and LGDISP is specified.
1-57475308
2008.0.0 (MD R3)
recovery missing
External Superelements - DMIGPCH - data
If more than one external superelement is created with DMIGPCH then in the
assembly run, the data recovery may be incomplete for one or more of the
external superelements.
Avoidance: There is no good avoidance other than to not use DMIGPCH or to use
it on only one external superelement.
1-57683171
2007.1.0
Nonlinear Analysis - AUTOSPC is deactivat
ed with glued (permament) contact in non-static solutions
AUTOSPC is deactivated with glued (permament) contact in non-static solution
sequences.
Compile sekr0
Alter nocont
Nocont=0 $
Endalter
1-57697805
2007.1.0
Submittal - Nastran Command Processor doe
s not handle the j.env keyword properly
The Nastran Command Processor does not handle the "j.env" keyword as per its
documentation and it does not allow "path" specifications as part of an
environment variable value definition. It must be extended to properly handle

the "j.env=<name>=<value>:<name>=<value>:..." specification and to allow
colon/semi-colon separated directories as part of the value strings. The
colon/semi-colon in the value string mumst be "escaped" by preceding it with a
caret (^) on Windows and a backslasn (\) on Linux/UNIX.
1-57703594
(MPYAD1)
Optimization/Design Sensitivity - PARAM,INREL,-2 - SFM 5423
A SOL 200 optimization analysis using the INREL, -2 inertia relief capability
will fail. With SUBCASEs that only invoke inertia relief and INREL,-2 is in
the BULK or defined in each SUBCASE the SFM 5423 (MPYAD1) is issued after
entering design cycle 1. If all subcases invoke inertia relief with
parm,inrel,-2 or the parameter is in the bulk data , the job will fail with SFM
5423 in (MPYAD1) indicating an incompatible matrix multiply. See also related
CR 1-73356415.
FILE#
COLS
ROWS FORM
TYPE NZWD DENS

2
654 9909
12 10000
TRAILER FOR PT6
IS
101
330
TRAILER FOR QRX
IS
102
Avoidance: Insert the following DMAP alter (also includes avoidance for
1-73356415)
compile phase1dr
alter 'PVT
PVTS,'(3),''
compile dstatrs
alter 'Paraml pl'(2),''(2,4)
dbview pl6=pl
where (inertia) $
if ( ndvar>1 ) then $
paraml pl6//'trai'/1/s,n,ncol $
matgen ,/spaw1/4/ncol/6/0/1/6/1/1/6 $
diagonal spaw1/spawn/'whole'/0. $
smpyad pl6,spawn,qrx,,,/qra/3/-1////1 $
else $
Mpyad
pl6,qrx,/qra//-1 $ sign change
endif $
1-57808041
2007.1.0
Elements - CFAST element may cause job to
fail with Signal=11 job aborting in MODUG
In certain cases, CFAST element may cause job to fail with Signal=11 job
aborting in MODUG
Fix has been imported and verified.
1-57898528
2007.1.0
Superelements - SOL 400 and 101 with con
tact will fail with SFM 2007 when superelements are defined
SOL 400 and 101 with contact will fail in CNTLSTR with SYSTEM FATAL MESSAGE
2007 in CNTLSTR when superelements are defined. The message indicates that an
element references an undefined grid point 0.
1-58051631
2007.1.0
nts in SOL 400 leads to UFM 6599
SOL 400 - RBE1, RBE2, RBE3 with Superleme
If there are RBE1, RBE2, or RBE3 rigid elements in a model with superelements
in SOL 400, the job will fail with USER FATAL MESSAGE 6599.
1-58051791
2008.0.0 (MD R3)
MIGPCH - Zero Fluid Response
External Superelements/Fluid Response - D
The fluid response of grid points that are interior to the fluid cavity and
interior to fluid-structure superelement, are zero in an assembly run using
DMIGPCH external superelement. Response on DISP output request in Sol 103
EXTSE creation run produces correct response using DMIGOP2 method. An assembly
run also produces correct, distinct structure and fluid eigentables with
DMIGPCH, so the VAFSX & AAX DMIG's are being processed, but the fluid modal
solution is not calculated.
1-58071249
2008.0.0 (MD R3)
Acoustic analysis - FLSPOUT and XYplot co
mmands - Wrong output for PHASE and IMAGINARY values
Although FLSPOUT outputs MAGNITUDE/PHASE and REAL/IMAGINARY values, acoustic
XY-plot outputs MAG or REAL values only.
Avoidance: Specify the item code as follows:
For MAGNITUDE and PHASE ;
FLSPOUT ...
:
OUTPUT(XYPLOT)
XYPUNCH FMPF(5) MODE / 1041(T1RM)
XYPUNCH FMPF(5) MODE / 1041(T2)
$ to get the magnitude part punched

$ to get the phase part punched
For REAL and IMAGINARY ;

FLSPOUT ... PSORT=(REAL,DESCENDING)
:
OUTPUT(XYPLOT)
XYPUNCH FMPF(5) MODE / 1041(T1RM) $ to get the real part punched
XYPUNCH FMPF(5) MODE / 1041(T2)
$ to get the imag part punched
1-58109626
db file
Nonlinear Analysis - Missing NLSTRESS for SOLID elements in x
A SOL 106 analysis with multiple restarts that selected a NLSTRESS that
referenced a SET ID as shown below that contained CHEXA and PENTA elements
NLSTRESS=3
SET 3 =700701 THRU 700717,700801 THRU 700848,700901 THRU 701188, 715973 THRU
716404,716645 THRU 717045,800001 THRU 808008
encountered a message in patran that there were no stress results for the
target elements.
1-58109847
2007.1.0
sitive for Puck and Hashin criteria
SOL 600 - MARF entries Fxy field my be po
In prior releases Fxy on the MARCF entry was required to be negative.

This
restriction has been removed in MD R2.1 to allow for Puck and Hashin criteriea.
1-58120430
2008.0.0 (MD R3)
rts using UNIT=21
DDAM - UFM 740 (RDASGN), DDAM example abo
In SOL 187, the default Fortran unit number of 21 for the DDAM input file will
cause UFM 740.
Avoidance: Reassign unit 21 to 24 in the FMS ASSIGN statement and specify
PARAM,IUNIT3,24 in the Bulk Data section.
1-58361626
answers
2007.1.0
SOL 400 - QUADR with offsets gives wrong
A model of QUADR elements with offset gives wrong answers in SOL 400.
1-58536061
103
Acoustic Analysis - MFLUID, VMOPT,2 - SFM 5423 (MPYAD1), SOL
If a model contains both an acoustic cavity (fluid mesh) and also uses virtual
mass (MFLUID + ELIST entries) and the user parameter VMOPT is set to 2, a SOL
103 analysis may fail with the following message:
FILE#
COLS
ROWS
FORM TYPE NZWD DENS

2
* 10000
TRAILER FOR GAE
IS
101
TRAILER FOR PHSA
IS
102
100
where the * characters represnet numbers that are problem dependent.

Avoidance:
For V2005r3 (2005.5), insert the following DMAP alter:
ECHOOFF $
COMPILE MODEFSRS NOLIST $
ALTER 'CALL.*MGEN2A','' $
IF ( VMOPT=2 AND NOCEE>0
) CALL MGEN2A CASES,USET,GOA,GM,DRG,PHSA,LAMAS,CEE,MEE,GGE,
BEC,MEC,LAMMATS,MIS,vafs/
MEH/
NASOUT $ PHSA,LAMAS UPDATED WITH VM EF
ENDALTER $
$
COMPILE MGEN2A NOLIST $
ALTER 1,1 $
SUBDMAP MGEN2A CASES,USET,GOA,GM,DRG,PHSA,LAMAS,CEE,MEE,GGE,
BEC,MEC,LAMMAT,MI,vafs/
MEA/
NASOUT $
ALTER 'MPYAD.*GAE','' $
DBSTATUS VAFS//S,N,NOVAFS $
EQUIVX PHSA/PHSFA/NOVAFS $
IF (NOVAFS>0) MERGE PHSA,,,,,VAFS/PHSFA/1 $ if explicit fluid is defined
MPYAD
GAE,PHSFA,/GEH/1 $
$
ENDALTER $
ECHOON $
For V2006r2 (MD R2) insert the following alter:

ECHOOFF $
COMPILE MODEFSRS NOLIST $
ALTER 'CALL.*MGEN2A','' $
IF ( VMOPT=2 AND NOCEE>0
) CALL MGEN2A CASES,USET,GOA,GM,DRG,PHSA,LAMAS,CEE,MEE,GGE,
BEC,MEC,LAMMATS,MIS,THETAM,vafs/
MEH/
NASOUT $ PHSA,LAMAS UPDATED WITH VM EF
ENDALTER $
$
COMPILE MGEN2A NOLIST $
ALTER 1,1 $
SUBDMAP MGEN2A CASES,USET,GOA,GM,DRG,PHSA,LAMAS,CEE,MEE,GGE,
BEC,MEC,LAMMAT,MI,THETAM,vafs/
MEA/
NASOUT $
ALTER 'MPYAD.*GAE','' $
DBSTATUS VAFS//S,N,NOVAFS $
EQUIVX PHSA/PHSFA/NOVAFS $
IF (NOVAFS>0) MERGE PHSA,,,,,VAFS/PHSFA/1 $ if explicit fluid is defined
MPYAD
GAE,PHSFA,/GEH/1 $
$
ENDALTER $
ECHOON $
1-58549878
MFLUID - VMOPT,2 RVDOF - UFM 1126 (GNFIST)
If a job defines virtual mass (MFLUID + ELIST) and the user parameter VMOPT is
set to 2, if RVDOF entries are present the job may fail with the following
message:
DMAP MODULE APPEND IS ATTEMPTING TO OUTPUT DATABLOCK
USER ACTION: DELETE THE DATABLOCK, OR USE FILE RVJ=OVRWRT
201 NAME = RVJ

COMPILE PHASE1A NOLIST $
ALTER 'APPEND RVJ1','' $
APPEND RVJ1,PVMG/RVJ2 $
EQUIVX RVJ2/RVJ/-1 $
ENDALTER $
1-58564001
2007.1.0
MDLPRM parameter - SFM 6704
SOL 400 - Roll out the open core with new
In SOL 400, if there is insufficient open core to allow the stiffness matrix
decomposition, the job may fail with SYSTEM FATAL MESSAGE 6704.
A new "MDLPRM,MINCORE,factor " to seclect the factor for which the open core
data will be rolled out is implemented in MD R2.1. If the open data is rolled
out, the whole open core will be available for decomposition.
1-58619601
2007.1.0
Documentation/QRG - SOL 600 - MINSTAT
The following changes should be made to the QRG descripton of the MINSTAT
entry:
1) The NSET field is not needed for the MINSTAT bulk data entry because the
Marc's INITIAL STATE (2,6) is not used.
It's only needed for the MCHSTAT bulk data entry.
2) There INIT1 and INIT2 fields in the "Format" section should be labled as
INT1 and INT2.
1-58619657
2007.1.0
Documentation/QRG - SOL 600 - MCHSTAT
There is an error in the QRG description of the MCHSTAT entry.

The FILE field is described as follows:
Enter the character string ELEM if IOPT=3. (Character, no Default; Required if
IOPT=3)
It should be:
Enter the character string FILE if IOPT=3. (Character, no Default; Required if
IOPT=3)
1-58713386
2006 in GP1
2007.1.0
SOL 700 - GP1, CORD2RX is ignored - UFM
The CORD2RX entry is ignored in SOL 700, this will likelly lead to USER FATAL
MESSAGE 2006 indicating an undefined coordinate system has been referenced.
1-58713429
2007.1.0
causes unexpected material failure
SOL 700 - Themal expansion coeff for MAT8
the failure occurs in LsDyna. The MAT8 entry is correct in jid.dytr.dat.

Quality will be re-assigened to Walter - E. Dickerson 9/25/2008
When the thermal expansion coefficient for MAT8 entry is set to 0., elements
may fail unexepctedly.
1-58746801
2008.0.0 (MD R3)
rce item codes(CELAS1)
Documentation/QRG - Incomplete complex fo
The complex force item code for the CELAS1 element in the QRG are missing and
should be as follow:
Item Code
2
3
Item
Real/Mag. or Imag/Phase
force
RM
force
IP
1-58837502
2008.0.0 (MD R3)
,GUSTAERO - SFM 4276 EC 31
Aeroelastic Analysis - AMP Module, PARAM
The presence of PARAM,GUSTAERO,-1 when using Strip Theory aerodynamics will

cause the AMP module to fail with a System Fatal Message 4276, Error Code 31.
Avoidance: Remove the PARAM,GUSTAERO,-1
Kevin, I recommend making this a limitation. However, Erwin Johnson should
have a say on this too.
1-58951871
2007.1.0
SOL600 - MATT, TABLEM1 - translator writ
es incorrect temperature dependent material table
The SOL 600 translator writes an incorrect temperature dependent material

table. This will lead to wrong answers.
1-58984913
Nonlinear Analysis - OLOAD RESULTANT output using geometrical
ly updated load vectors
In SOL 106 and 400, the OLOAD RESULTANT is printed at the beginning of each
subcase for the UNUPDATED geometry. For loads that change because of geometric
deformations (PLOADi, FORCE2, etc.) the output does not match the SPCFORCE
RESULTANT.
The following DMAP will print the OLOAD RESULTANTS using force vectors based on
the updated geometry.
$ alter to print OLOAD in the updated geometric location to account for
follower forces
$ i.e FORCE1, PLOAD4, etc.
$ this alter will print the OLOAD-NL RESULTANT just prior to the SPCFORCE
RESULTANT.
compile sedrcvr
alter 'if.*PRTRESLT.*yes'
IF (app='NLST' and NONLNR) THEN
MESSAGE//'OLOAD base on FOLLOWER FORCE UPDATES'
VECPLOT pj1,BGPDTN,SCSTM,CSTMS,CASEDR,,MEDGE,,/,pjRESx,pjHDx,,/
GRDPNT/S,N,ZERO/RESLTOPT/'OLOAD-NL'///ALTSHAPE//SEID $
ENDIF
1-59001648
2007.1.0
FORCD) followed by UFM 3003 SLT1
Nonlinear Analysis - RFORCE - UWM 6584 (R
A sol 106 model with an RFORCE entry may fail with:

*** USER WARNING MESSAGE 6584 (RFORCD)
METHOD = 1 IS SPECIFIED ON THE RFORCE ENTRY IN COMBINATION WITH
P-ELEMENTS.
USER INFORMATION: METHOD = 1 DOES NOT YIELD CORRECT RESULTS WITH
P-ELEMENTS AND/OR CONSISTENT(NON-LUMPED) MASS.
ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK SLT1
(FILE 113) IN SUBROUTINE NLSLTD
Avoidance: The model that this was observed for had LOAD=1 and RFORCE 1.
Changing to LOAD=11 and RFORCE 11 avoided the error. .
1-59166049
2008.0.0 (MD R3)
r stress for Vz load
Elements - CBAR, PBRSECT - Incorrect shea
The stress recovery for a CBAR element that references a PBRSECT entry is
incorrect for VZ shear force.
1-59181381
2007.1.0
fied on the NLPARM entry will fail
SOL 400 - 3D Contact with Bisection speci
For SOL400, if there is 3D contact, the solution will fail if bisection is

specified on the NLPARM entry.
1-59185711
2008.0.0 (MD R3)
, MDACMS - SFM 6143
Superelements - EXTSEOUT, acoustic cavity
If EXTSEOUT is requested with acoustic cavity in an external superelement and

using MDACMS then the job will fail with SFM 6143:
*** SYSTEM FATAL MESSAGE 6143 (UPARTPR)
SPECIFICALLY:
The number of rows
in VGFS is not equal to the size of the G-set
User Information: Size of input matrix and DOF sets:
VGFS
: Rows=
3828 by Cols=
1
4022
Set0 (A-set)=
258
Set1 (COMP-set)=
3764
1-59206949
2008.0.0 (MD R3)
Elements - PBRSECT - Arbitrary Beam coord
inate system incorrect, bending stress incorrect.
Arbitrary beam produce incorrect bending stress data recovery.
1-59215380
2008.0.0 (MD R3)
Elements - PBRSECT - Stress recovery stre
ss tensor mapping leads to wrong vonmises in Patran
The MSC.Nastran 2005R3 Release Guide for arbitrary beam cross sections has the
following mapping.
(Chapter 4, Arbitrary Beam Cross-Section, subsection "stress recovery for whole
cross-section")
Op2
Sx
Sy
Sxy
Stress Tensor | Recovered ABCS Direct Stress

| Sx
| Sxy
| Szx
This mapping will lead to incorrect stress derivations when the op2 is read
into Patran. and it is non-intuitive that the stresses displayed in Patran are
not what you think they should be.
The op2 file should contain a direct mapping so that patran post-processing
will be correct.
1-59225891
SGIR14K
2008.0.0 (MD R3)
SOL 400 - SDR2 - SOL 400 jobs may fail on
SOL 400 jobs may fail on SGI Irix systems in the SDR2 module during data
recovery.
Avoidance: Other than running on a different platform, there is no avoidance.
1-59287753
External Superelements - EXTERSE - DTI,TUG1 in residual cause
s UFM 5423 MPYAD1
If DTI,TUG1 or DTI,TES1, or DTI,TEF1, or DTI,TQG1 are present in the residual
structure, then EXTERSE will be set to TRUE and improper processing in SEDRCVR
will generate the following error:
FILE#
COLS
ROWS
FORM TYPE NZWD DENS
TRAILER FOR MUG1
IS 101
60
60
1
2
2 167
TRAILER FOR ULS1
IS 102
5
30
60 10000
0
0
TRANSPOSE FLAG IS 0
0FATAL ERROR
1
* * * END OF JOB * * *
Avoidances:
1) Remove DTI entries described above
2) Insert the following DMAP ALTER:
$ IF user removes the BEGIN SUPER and treats the DMIG as a DMIG
$ instead of an external SE, then an error can occur trying to process DRMH3.
$ to avoid this, only mark EXTERSE as TRUE when NOTUG, NOTES, NOTEF, NOTQG
$ exist for SEID that are >0
compile super3,nolist
alter 'exterse=','exterse='
IF(SEID>0) EXTERSE=(SETYPE='EXTRNA' OR SETYPE='EXTRNG' OR
NOTUG OR NOTES OR NOTEF OR NOTQG) $
1-59294257
2008.0.0 (MD R3)
Acoustic Analysis - PFMODE, PFPANEL - Out
put may be wrong with a "phase" request.
PFMODE and PFPANEL case control commands that request PHASE output may result
in incorrect output.
Avoidance: Request only REAL, IMAG output.
1-59419426
2008.0.0 (MD R3)
SOL 600 - NLAUTO is not effective to cont
rol time stepping if MCHSTAT is also used
The following scenario will result in the NLAUTO entry not controlling the time
stepping:
1. Run a SOL 600, 159 (transient thermal anlaysis), and get temperatures in
t16 file.
2. Run a SOL 600, 106 (static structural analysis) using initial temperature
and temperature load of the t16 file from step 1.
In the second run, NLAUTO is used to control time stepping, but it is not
effective to control time stepping since the translator uses "AUTO THERM"
instead of "AUTO STEP" ignoring parameters defined on the NLAUTO entry such as
total time.
"NLAUTO" should be tranlated into "AUTO STEP" in marc.dat as written in Quick
Reference Guide while "MTHERM" is translated into "AUTO THERM" in marc.dat.
1-59529106
Connection Elements - CINTC on curved geometry does not pass
GROUNDCHECK or PARAM CHECKOUT YES
A model with curved geometry (a cylinder for example) and a CINTC line
interface will fail the GROUNDCHECK at the NSET level. Other indications are
EMH is not null from PARAM,CHECKOUT, YES. The CINTC algorithm must be refined
to preserve the rigid-body modes, while retaining the flexibility of CINTC
connection.
1-59626733
2007.1.0
ements, PCOMP, PCOMPG - may fail in cmpzpr
Module cmpzpr uses system cell 93 (NPCOMP) to store the number of PCOMP/PCOMPG
bulk data entries.. In general, this is not a problem for list superelements.
However, for part superelements, it is possible that each part has its own
NPCOMP. When cmpzpr reserves memory space in opencore based on NPCOMP in
system cell 93, the job may fail if the NPCOMP is not equal to the actual
NPCOMP of a part se. This is only a potential problem in SOL 200.
1-59682791
2007.1.0
fail in SOL 600 for PBEAM
SOL 600 - PBEAM - Large field format may
PBEAM large field format may fail in SOL 600 for certain combinations of input.
Avoidance: Use small field format.
1-59690996
2008.0.0 (MD R3)
y, Should not be in MSC.Nastran QRG.
Documentation/QRG - RBJOINT - SOL 700 Onl
The RBJOINT is a SOL 700 only entry and it should not be included in the
MSC.Nastran QRG.
1-59692231
Buckling - buckling or preload subcase with boundary conditio
n change - Inefficient
In SOL 105, if the buckling or preload subcase is specified with a change in
the boundary condition then an uncessary matrix decomposition will be
performed.
compile phase1dr
alter 'call phase1c'(,-1)
PARAML CASEw//'DTI'/1/256//S,N,STATSuB $
PARAML CASEw//'DTI'/1/241//S,N,STATpre $
if ( statsub=0 and statpre=0 ) then $
alter 'call phase1c'
endif $
1-59715698
A1ETD)
2008.0.0 (MD R3)
Eigenvalue Analysis - CGAP - UFM 4016 (T
Nastran 2005r3 and earlier releases may fail with the message:
USER FATAL MESSAGE 4016 (TA1ETD)
when an eigenvalue analyis contains gap elements and TEMP entries.
Avoidance: Include a TEMPD entry.
1-59796301
2008.0.0 (MD R3)
Complex Eigenvalues - SOL 110 with ACMS p
roduced wrong answers with K2PP, M2PP, B2PP or TFL
If K2PP, M2PP, and B2PP are used in SOL 110 along with ACMS then the run will
produce wrong answers.
compile semceig
alter 'dbdelete datablk=vgdr',''
delete /vgdr,,,, $
compile fdrmgen
alter 'return'(2),''
if ( app='ceigen' and not(mdreig) ) return $
compile spdr1
alter 'return'(2),''
endalter
1-59863480
2008.0.0 (MD R3)
Documentation/QRG - DMP, Param,POST,-5
DMP geometric doman and frequency domain do not support param,post,-5.

1-59906396
2008.0.0 (MD R3)
Tolerance is too tight
Aeroelastic Analysis - CAERO1, MONCNCM -
The moncncm entry provides output on aeroelastic strips. the logic for
determining whether aero boxes share a strip has been found to incorrectly
designate more strips than intended. this has been traced to a tolerance that
is too tight for the accuracy that is available from the input bdf file.
User Avoidance: Check the CAERO1 entries to check that abutting panels are
aligned exactly
1-59911241
rge.
Linear Contact - Missing Message when solution does not conve
Linear contact in SOL 101 does not issue a fatal message if it does not
converge. A message similar to that issued in SOL 400 shown below needs to be
added.
*** USER FATAL MESSAGE 4551 (nl3con)
*** STOPPED PROBLEM DUE TO FAILED CONVERGENCE.
1-59955051
2008.0.0 (MD R3)
FRF - CONM2 - SFM 307 in FRFINFO module
An FRF generation run with stress requests and CONM2 elements fails with the
message:
SYSTEM FATAL MESSAGE 307 in the FRFINFO module.
1-59961781
2008.0.0 (MD R3)
SOL 700 - D2RAUTO is not translated.
The D2RAUTO entry is not translated to the dytr.dat file and there are no
warning messages.
1-60037683
2008.0.0 (MD R3)
Logic Error 27) in FRFINFO module
FRF - PLOTEL entries result in SFM 3200 (
An FRF generation run with PLOTEL entries and a stress request for a
non-existent element fails with the message:
SYSTEM FATAL MESSAGE 3200 (Logic Error 27) in the FRFINFO module.
Avoidance: Add a stress or force output request for a valid element
1-60037787
2008.0.0 (MD R3)
Logic Error 12) in FRFINFO module
FRF - PLOTEL entries result in SFM 3200 (
An FRF generation run with PLOTEL entries and no stress or force output
requests fails with the message
SYSTEM FATAL MESSAGE 3200 (Logic Error 12) in the FRFINFO module.
Avoidance: Add a stress or force output request for a valid element
1-60162658
2008.0.0 (MD R3)
SOL 600 - Multiple MOMENT or FORCE entrie
s for the same grid leads to incorrect loads
For all versions of SOL600 (through mdr2 and v2007), when multiple MOMENT or
FORCE entries for the SAME grid are combined using the LOAD Bulk Data Entry,
there is a problem during translation that leads to incorrect loads.
Avoidance: To get the correct results using current SOL 600, all moments and
forces at the same grid which are applied in the same load case must be
combined onto one FORCE or MOMENT entry.
1-60164831
2008.0.0 (MD R3)
d into SOL400 correctly.
SOL 400 - Hybrid Damping is not implemete
The Hybrid Damping for the transient analysis is implemented in SOL129. It is

found that this damping is not implemented correctely in SOL 400.
1-60164849
2007.1.0
SOL 400 - NOLIN2 - UFM, Fails to converge
SOL 400 will diverge if there are NOLIN2 entries in the model together with
'PARAM,TSTATIC,1"
1-60165121
2008.0.0 (MD R3)
SOL 400 - Iterative Solver, SMETHOD, MPC
- tpl nlc006a_casi, fails to coverge on i8
SOL 400 with rigid elements and/or mpcs using the Casi iterative solver may
fail to converge on i8 systems leading to the following messages. This error
was discovered with tpl problem nlc006a_casi on ia64 systems. This error has
been corrected in MD R2.1.1(version 2007.1.1) which has been posted to the
product update web site at:
http://www.mscsoftware.com/support/software_updates/mdr211.cfm
*** SYSTEM INFORMATION MESSAGE 4172 (ITSCAS)
CASI ITERATIVE SOLVER SOLUTION ERROR ESTIMATION STATISTICS FOLLOW FOR LOAD
CASE NUMBER:
1
INPUT ERROR CONVERGENCE EPSILON VALUE
=
1.000000E-04
REDUCTION IN 2-NORM OF THE RESIDUAL
=
7.239659E-05
REDUCTION IN INFINITY NORM OF THE RESIDUAL =
3.959844E-05
REDUCTION IN PRECONDITIONED NORM OF RESIDUAL =
1.012917E-04
ESTIMATE OF NORMALIZED ENERGY NORM OF ERROR =
2.811392E-04
*** USER WARNING MESSAGE 4675 (NMEPS)
EXCESSIVE INCREMENTAL LOAD IS APPLIED IN ELEMENT ID = 201
REDUCE THE LOAD INCREMENT BY A FACTOR OF 2.747758E+02
FOR BETTER
SOLUTION .
*** USER FATAL MESSAGE 4676 (NMEPS)
ERROR EXCEEDS 2.000000E+01
PERCENT OF YIELD STRESS IN ELEMENT ID=201
*** USER WARNING MESSAGE 4675 (NMEPS)
EXCESSIVE INCREMENTAL LOAD IS APPLIED IN ELEMENT ID = 1001
REDUCE THE LOAD INCREMENT BY A FACTOR OF 1.434823E+02
FOR BETTER
SOLUTION .
*** USER FATAL MESSAGE 4676 (NMEPS)
ERROR EXCEEDS 2.000000E+01
PERCENT OF YIELD STRESS IN ELEMENT ID=1001
1-60220811
SOL 400 - PSLDN1 - Incorrect Shear Stress
The shear stress is incorrect when using the nonlinear extension PSLDN.
1-60222617
2008.0.0 (MD R3)
s in Complex Data Output
Aeroelastic Analysis - MONITOR=ALL result
A request for MONITOR point output should result in REAL/IMAGINARY output by

default as the Quick Reference Guide states. However, the request:
MONITOR=ALL
is the same as MONITOR(PHASE)=ALL.
Avoidance: To obtain the REAL/IMAGINARY output, one must specify
MONITOR(REAL)=ALL.
1-60261551
rs
Nonlinear frequency response - non convergecing - wrong answe
When using the nonlinear frequecy response (sol 128), a pre-release capability
in Version 2007/MD R2, and the solution fails to converge, the results may be
incorrect. An indication of this error is the reponse value being set to zero
for one frequency and the appearance of 2 resonance peaks when there should
only be one.
Avoidance:
1-60302368
ode=i8
None
SOL 400 - TA1M - FATAL NON-LINEAR ELEMENT ERROR on Solaris m
SOL 400 jobs, such as TPL test nclevrbm.dat, may fail in the TA!M module on to
Solaris ilp64 (a.k.a i8) system with the message FATAL NON-LINEAR ELEMENT
ERROR.
1-60303381
2008.0.0 (MD R3)
Eigenvalue Analysis - Modal analysis with
ACMS and F1>0.0 may yield results outside the range
If the F1 field on the EIGRL bulk data entry is greater than 0.0, ACMS will
ignore the F1 entry and possibly produce eigenvalues between 0.0Hz and "F1"
Hertz.
compile invlan
alter 'ufmin\<', '' $
IF ( UFMIN<FMAX ) THEN $
1-60309591
2008.0.0 (MD R3)
Dynamics - Part superelements OLOAD, SPCF
, MPCF - UFM 4346 and Missing results
If part superelements are specified in a dynamic analysis and one or more of
OLOAD, SPCF, and MPF are requested then the run may fail with UFM 4346 and then
produce missing output.
compile sedlg
alter 1
dbview dit0=dit where (seid=0 and wildcard) $
alter ' trlg ',''(,1)
TRLG
CASE0,USETD,DLTS,,bgpdts,SILS,cstms,TRL,DIT0,GMD,,,,,,,
APPLOD,,,,ENFMOTN/
PPal,PSal,,,,OL,,yptal,ypxal, $
TRLG
CASE0,USETD,DLTS,,bgpdts,SILS,cstms,TRL,DIT0,GMD,,,,,,,
APPLOD,,,,ENFMOTN/
PPdv,PSdv,,,,OLdv,,yptdv,ypxdv,//////////////2 $
alter ' frlg ',''

FRLG
CASE0,USETD,DLTS,FRL,GMD,,DIT0,,APPLOD,,,,ENFMOTN,
rotort,unbvecg,,,/
PP,PS,,OL,,ypx,,,,,,/
'DIRECT' $
1-60701307
2007.0.0 (MD R2)
and SCR=no produces diff. answers
Optimization/Design Sensitivity - SCR=yes
SCR=yes and SCR=no produces different answers in SOL 200.

Avoidance: The scr=yes answers are more conservative and thus scr=yes is
recommended.
1-60704752
2008.0.1
ws FBS "Access violation"
SOL 400 - TPL test nlc019a fails on Windo
TPL test nlc019a fails on Windows and ilp64 (a.k.a. i8 systems) with FBS
"Access violation"
1-60734541
ing in decomp
Matrix Methods - MFLUID, Decomp - Traceback during reorder
A very similar error occurs with the attached model bhead21.dat.

Models with very dense compressed matrices may crash in decomp during the
reordering phase with the traceback show below.
Avoidances: Use supernodal compression in place of grid compression, by
setting
sys206=132 or sys206=136. Else run with no compression by (setting sys206=260
or sys206=264)
Traceback:
Offset 0x0000011c
Offset 0x00000028
Offset 0x00000060
Offset 0x00000190
Offset 0x0000001c
Offset 0x000006d8
Offset 0x00000464
Offset 0x00000120
Offset 0x000000bc
Offset 0x00005864
Offset 0x00000520
Offset 0x00000f5c
Offset 0x00000134
Offset 0x00000a90
Offset 0x000003dc
Offset 0x00001150
Offset 0x00000d74
Offset 0x0000000c
Offset 0x00000120
Offset 0x000001b4
Offset 0x00000064
in
in
in
in
in
in
in
in
in
in
in
in
in
in
in
in
in
in
in
in
in
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
procedure
1-60803879
2008.0.0 (MD R3)
T entry - SFM 3007 in SOLVE
releasememory
Release_Memory
KillClique
FormNewClique
EliminateNode
PSLDLT_AMF
Reorder
PSLDLT_WExtreme
dfmext_
mreordr_
dfmsym_
dfmsa_
sdcomp_
facdrvo_
facdrv_
frrd1c_
sqfreq_
freq_
xsem10_
xsemdr_
nastmon_
Elements - PARAM CDITER without any SUPOR
Running Solution 101 with PARAM,CDITER and without any SUPORT entry results in
SYSTEM FATAL MESSAGE 3007 in the SOLVE module.
1-60820088
2008.0.0 (MD R3)
Documentation/QRG - SOL 600 - NLSTRAT
There is an error in the QRG description of the NLSTRAT entry.

The RCK1 field is described as follows:
Used for Relative Checking - Maximum residual force ratio (maximum value of
residual force divided by maximum residual force)
or displacement ratio (maximum allowable value of displacement increment
divided by displacement increment)
depending on convtyp (Real>=0) CONTROL(3,1); Default = 0.1
It should read:
Used for Relative Checking - Maximum residual force ratio (maximum allowable
value of maximu residual force divided by maximum reaction force)
or displacement ratio (maximum allowable value of the change in displacement
increment divided by displacement increment)
depending on convtyp (Real>=0) CONTROL(3,1); Default = 0.1
1-60830288
rameter
2008.0.0 (MD R3)
Documentation/QRG - SOL 600 - MARCSAME Pa
According to the example on page 718 and Parameter Applicability Table on page
839, the QRG indicates that PARAM,MARCSAME must be specified in the bulk
data. In fact it must be specified in the case control above the first subcase
else the folloiwng warning message is issued:
Severe Warning in SOL 600 translator - Case Control load ID
999
Appears in more than one subcase. For SOL 600, this may lead to
wrong results.
The subcases are
2 and
1
If you are sure the results will be acceptable, re-run with Case
Control
PARAM,MARCSAME,1 above the first subcase
1-61001551
2008.0.0 (MD R3)
SOL 400 - XYPLOT - XYPLOT request fails w
ith segmentation violation in SOL 400.
If there are too many subcases or steps in SOL 400, the xyplot request in case
control packet may fail with a segmentation violation.
1-61083720
2008.0.0 (MD R3)
ADAMSNMF - UFM 7811 (MNF_Error)
Specification of the ADAMSMNF command without the "PSETID" option may result in
USER FATAL MESSAGE 7811 (MNF_Error).
Avoidance: Add the PSETID option to the command.
1-61168951
2008.0.0 (MD R3)
es not translated
SOL 700 - PEULER1, SET1, and EOSGAM entri
PEULER1, SET1, and EOSGAM entries not translated

1-61169010
2008.0.0 (MD R3)
SOL 700 - SET1 entry is not translated
SET1 entry is not translated

1-61169048
2008.0.0 (MD R3)
SOL 700 - EOSGAM entry is not translated
The EOSGAM entry is not translated.

1-61207401
2008.0.0 (MD R3)
ct bodies fails
SOL600 - Axisymmetric analysis with conta
The translator rotates an axisymmetric model by 90 degrees to meet Marc

convention (X is the symmetric axis), but rigid contact bodies are not rotated.
1-61236481
2008.0.0 (MD R3)
, poor convergence
SOL 400 - PARAM,LGDISP,1 - Large rotation
If PARAM,LGDISP,1 is requested in SOL 400, the solution may have difficulty

converging if the grid point rotataion is larger than 180 degree.
1-61280131
2008.0.0 (MD R3)
External Superelements - Frequency Respon
se, Multiple Subcases - Wrong Answers
A frequency response assembly run employing external SEs and with multiple
subcases and ACCE requests or combinations of DISP, VELO and ACCE requests
gives wrong answers for the external SEs.
compile sedrcvr
alter 'drmh3'(2),''
file oug1a=append $
type parm,,i,n,nskip=0,nr $
paraml ol1//'trailer'/1/S,N,nfreq $
np=1 $
do while ( notug1>0 and nskip>=0 ) $
case
casedr,/case1/'tran'/s,n,nskip $
nr=nfreq+np-1 $
matmod iugx/iugxx/1/np/nr $
np=np+nfreq $
drmh3
tug1,iugxx,,,,,,,ol1,case1/oug1x,,,/app $
append oug1x,/oug1a/2 $
enddo $
equivx oug1a/oug1/-1 $
1-61280226
2008.0.0 (MD R3)
SOL 400 - Casi Iterative Solver - UFM 300
5 (NLSOLV), Attempt to operate on a singular matrix
SOL 400 with the casi iterative solver specified by "SMETHOD=ELEMENT" may
*** USER FATAL MESSAGE 3005 (NLSOLV)
ATTEMPT TO OPERATE ON THE SINGULAR MATRIX SCRATCH IN SUBROUTINE SOLVEZ
FATAL ERROR
This error has been corrected in MD R2.1.1(version 2007.1.1) which has been
posted to the product update web site at:
1-61419147
r 615.
2008.0.0 (MD R3)
Case Control - IFP - K2GG User Fatal Erro
If too many DMIG matrix names are placed on the K2GG case control command, such
as:
k2gg = 1.*k1,2.*k2,3.*k3,4.*k4,5.*k5,6.*k6,7.*k7,8.*k8,9.*k9,
10.*ka,1.*kb,1.*kc,1.*kd,1.*ke,1.*kf,1.*kg,1.*kh,
1.*ki,1.*kj,1.*k0,1.*kk,1.*kl,1.*km,1.*kn,1.*ko,1.*kp,
1.*kq,1.*kr,1.*ks,1.*kt,1.*ku,1.*kv,1.*kw,1.*kx,1.*ky,
1.*kz,1.*kz1,1.*kz2,1.*kz3,1.*kz4
The program terminates with the following message.
AN IMPROPER OR NO NAME GIVEN TO THE ABOVE SET.
The problem is that IFP1PC has a hardcoded limit of 200, and NO bounds checking.
1-61423891
2008.0.0 (MD R3)
External Superelements - PARAM,FULLSEDR random analyis and XY produces missing results
Missing results may occur in XY plotting and random analysis if
PARAM,FULLSEDR,YES is specified in a run with external superelement data
recovery.
Avoidance: Insert the following DMAP alter: (this alter also contains the
avoidance for CR 1-61280131)
compile sedrcvr
$ avoidance for CR 1-61280131 begins here
alter 'drmh3'(2),''
file oug1a=append $
type parm,,i,n,nskip=0,nr $
paraml ol1//'trailer'/1/S,N,nfreq $
np=1 $
do while ( notug1>0 and nskip>=0 ) $
case
casedr,/case1/'tran'/s,n,nskip $
nr=nfreq+np-1 $
matmod iugx/iugxx/1/np/nr $
np=np+nfreq $
drmh3
tug1,iugxx,,,,,,,ol1,case1/oug1x,,,/app $
append oug1x,/oug1a/2 $
enddo $
equivx oug1a/oug1/-1 $
$ avoidance for 1-61423891 begins here
alter 'splitdva'
splitdva=-1 $ force residual's SDR2 output to be compatible with DRMH3 output
compile xmergofp
alter 'splitdva'
splitdva=-1 $
alter 'xyplot '(2)
call xrandom frl,oug2m,ovg2m,oag2m,
spsel,xycdb,dynamics,dit,bgpdt,
OPG2m,OQG2m,OES2m,OEF2m,CASEcc,ostr2m,oqmg2m//
app/app1/s,cardno/s,pfile/ocid/s,otape2/
0/0/0/splitdva $
endalter
1-61792201
2008.0.0 (MD R3)
Aeroelastic Analysis - SPLINE6, AELIST w
ith duplicate element ids causes memory failure - SFM 3008
If a SPLINE6 uses an AELIST to define the virtual surface, and that AELIST
contains more element ids than the total number of existing elements (as can
happen if the element ids are duplicated), then a memory error will occur:

MODULE = GI
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE CRPMDD
USER ACTION: INCREASE OPEN CORE BY AT LEAST 841 WORDS
PROGRAMMER INFORMATION: LOCATION KEY = MNVSG
1-61793688
2008.0.0 (MD R3)
Case Control - CMSENERGY format error
Specifiying CMSENERGY Case Control command: in V2005 will cause a format error:
Avoidance: Specify CMSE or CMSENRGY in V2005+ (note the 2nd "E" needs to be
dropped.)
1-61872481
LYSIS=NLTRAN
2007.0.2
SOL 400 - Inefficient processing when ANA
When ANALYSIS=NLTRAN in SOL 400 and job is run without a maxtrix update and has
many time steps, the processing may be very inefficient.
1-61993931
2007.0.2
STYP may cause jobs to fail
SOL 400 - BCBODY - Incorrect default to I
The documented default for the ISTYP field on the BCBODY entry is 0, but it is
not 0 in the codes. This may cause some jobs to fail.
Avoidance:
Explicity specify 0.
1-61996691
2008.0.0 (MD R3)
Elements - IFP, PBARL - "Floating point
zero divide" (C000008E) exception encountered.
IFP9 processing of PBARL entries may fail with a floating point divide by zero
or it may hang.
Avoidance : Insert MDLPRM,TWBRBML,1 to switch to default beam equations.
1-62054981
2007.0.2
ass and damping matrices
SOL 400 - AUTOSPC leads to incompatible m
The AUTOSPC was implemented in SOL 129. However, when it is used in the
transient analyis of SOL 400, it will fail with imcompatible matrix for mass
and damping matrices.
1-62064821
2008.0.0 (MD R3)
Dynamics - TFL command, TF entry - Ineffi
cient Processing of Symmetric Matrices
There is no checking for symmetric matrices produced by the TFL Case Control
command. The program then assumes the matrices are unsymmetric and this
assumption causes the selection of unsymmetric methods in complex eigenvalue,
frequency response, and transient response even if the matrices are actually
symmetric.
1-62175861
2008.0.0 (MD R3)
try fails with more than one point.
Miscellaneous - IFP - UFM 316, SUPORT1 en
The SUPORT1 entry is documented in the QRG as allowing three (IDi,Ci) pairs per
record. If you give more than one you get UFM 316 (IFPDRV) ILLEGAL DATA ON
BULK DATA ENTRY SUPORT1.
1-62178001
2008.0.0 (MD R3)
Miscellaneous - User-defined PARAM keywor
ds capability is broken
The user-defined PARAM keywords capability was broken when enhancements to the
"remote query" capability were added.
1-62228981
rameter
2008.0.0 (MD R3)
Documentation/QRG - SOL 600 - MRFOLOW1 Pa
There seems to be an error in the QRG about PARAM,MRFOLWO1,1.

It is now described as follows:
if follower force stiffness due to distributed loads is to be included.
But according to the Marc Vol.C, it should be:
if follower force stiffness due to distributed loads is not required.
1-62247741
2008.0.0 (MD R3)
SOL 600 - NLPARM and NLPCI are not transl
ated to AUTO INCREMENT option correctly
When SUBTITLE case control command is entered before SUBCASE case control
command, NLPARM and NLPCI will not be translated to AUTO INCREMENT option in
Marc input file. If the SUBTITLE case control command is commented out, NLPARM
and NLPCI will be translated to AUTO INCREMENT option in Marc input file.
When SUBTITLE case control command is NOT entered before SUBCASE case control
command and either TITLE or LABEL case control command is entered in a subcase,
NLPARM and NLPCI will not be translated to AUTO INCREMENT option in Marc input
file.
1-62347011
2008.0.0 (MD R3)
DMAP - Inconsistent rules for under-typed
real and complex constant parameter in modules - UFM 6
Currently, the DMAP compiler permits a RS constant for a CS parameter in a
module parameter list. However, UFM 6 will occur when inputting a CS or RD
constant for a CD parameter; a RS constant for a CS parameter; or a RS constant
for RD parameter. The DMAP compiler should "up-type" all constants.
Avoidance: Convert the constant to the correct type with appropiate DMAP
function.
1-62456460
2008.0.0 (MD R3)
B specified - Wrong answers
Connector Elements - CFAST with GS, GA, G
In V2007, if GS, GA, and GB and GA or GB are at the corner of an element, then
the CFAST will generate wrong answers.
Avoidance: Remove GA/GB from the input file or insert the following dmap alter
in V2007:
compile sedisp list
alter 'if ( connect '(1,),'endif $ connect'(1,)
alter 'if ( connect '(2,),'endif $ connect'(2,)
compile super3 list
alter 'if ( cfastp or cweldc','endif $ connect'
endalter
The alter turns off the displacement option DISP(connector=) option so you can
not get displacement data recovery on GA and GB if they were not specified.
This error has been fixed by avoiding updating the displacements of GA or GB if

it is a physical grid and is attached to a structure.
Code is in the tier 1 system on 10/19.
1-62457277
2008.0.0 (MD R3)
3 Option on Surface entry
GPSTRAIN - Incorrect Answers for NORMAL X
If NORMAL X3 is specified on the SURFACE command and SYSTEM CORD is changed

from 0 to a coordinate system opposite to the element coordinate system then
the GPSTRESS output flips sign as expected but the GPSTRAIN output will have
all positive strain values.
1-62515278
2008.0.0 (MD R3)
Nonlinear Analysis - MATS1, TYPE=PLASTIC,
TABLEST - UFM 6840, TA1 Module, Premat Subroutine
A nonlinear temperature dependent material MATS1 with TYPE=PLASTIC that

references a TABLEST, causes the following fatal message to be issued by the
TA1 module.
*** USER FATAL MESSAGE 6840 (PREMAT)
THE SECOND POINT (X2,Y2) SPECIFIED ON THE TABLES1 BULK DATA ENTRY ID = 100
IS NOT AT THE INITAIL YIELD
POINT (LIMIT1) ON THE MATS1 BULK DATA ENTRY ID = 10 WHEN THE TYPE OF
MATERIAL NONLINEARITY IS PLASTIC.
The message that should be issued is:
USER FATAL MESSAGE xxxx, A MATS1 RECORD MAY NOT REFERENCE A TABLEST RECORD IF
THE TYPE = PLASTIC.
1-62540156
2008.0.0 (MD R3)
m cell information in the UFM 316
Miscellaneous - Large Field - Wrong syste
The folloiwng message:

ILLEGAL DATA ON BULK DATA ENTRY %1 ON SORTED ENTRY COUNT %2
USER INFORMATION:
%3 ID %4 EXCEEDS MAXIMUM VALUE ALLOWED %5.
USER ACTION: IF THE ID VALUE GREATER THAN THE MAXIMUM VALUE MUST BE USED,
ADD
NASTRAN STATEMENT ( NASTRAN SYSTEM(182)= nnn ) TO THE INPUT
FILE.
should refer to SYSTEM(175) not (182).
1-62552681
2008.0.0 (MD R3)
2 - Wrong answers
External Superelements - SOL 109 / SOL 11
Velocity and acceleration results will be that of the displacement vector in

transient analysis with external superelements for the following output
requests:
Request
--------VELO only
ACCE only
Result
---------------Wrong: VELO=DISP
Wrong: ACCE=DISP
VELO and ACCE only
Wrong: VELO=DISP but ACCE is OK.
Avoidance: Insert a DISP request.

1-62754560
2008.0.0 (MD R3)
TS does not exist
Part Superelements - RANDOM - SFM 3001 DI
If a RANDOM case control exists for a Part Superelement, the following message
may be issued:
*** SYSTEM FATAL MESSAGE 3001 (RANDOM)
THE INPUT DATA BLOCK NAMED DITS
AT POSITION
2 DOES NOT EXIST.
Avoidance:
Copy the TABRND1 entires into the part's bulk data section or
insert the following DMAP alter:
malter 'call xrandom'(1,-1)
IF (SEID>0) THEN
dbview ditz=dit (where seid=seid and wildcard=TRUE)$
equivx ditz/dit/always $
ENDIF $
1-62754729
2008.0.0 (MD R3)
Virtual Mass - PARAM AUTOQSET, PARAM VMOP
T - SFM 6144 in MERGE, SFE 4276 in MDATA
Depending on the value of PARAM,VMOPT, various fatal errors may occur in
virtual mass with PARAM,AUTOQSET,YES when no t-set exists.
PARAM,VMOPT,0 causes:
*** SYSTEM FATAL MESSAGE 6144 (MERGE1)
SPECIFICALLY:
The number of rows
in GQE is not equal to the number of non-zeros in
partitioning vector VA
GQE
: Rows=
7 by Cols=
72
VA
: Rows=
6
no. of non-zeros=
0 no. of zeros=
6
ERROR CODE
1044 PID= 0
SPECIFICALLY:
The number of rows
in GTEQ is not equal to the number of non-zeros in
partitioning vector VA
GTEQ
: Rows=
8 by Cols=
72
VA
: Rows=
7
no. of non-zeros=
0
no. of zeros=
7
Avoidance: Insert the following DMAP alter for V2005r3:
compile phase1b
alter 'dbstatus drg'(,-1)
dbstatus gge//s,n,nogge $
if ( nogge>0 ) then $
umerge1 uset,gge,,,/gge1/lgset//'q'/1 $ append actual q-set

equivx gge1/gge/-1 $
endif $ nodrg>0
compile mgen2o
alter 's,n,noqset0'
if ( notset>0 ) then $
alter 'merge.*gtet,gteq'
else $
equivx gteq/gae/-1 $
endif $
alter 'merge
met,,meq'(,-1)
alter 'merge
met,,meq'
else $
equivx meq/mea/-1 $
endif $
compile mgen1
alter 'noqset'(2,-1)
alter 'merge.*gte,gqe'
else $
equivx gqe/gae/-1 $
endif $
compile semrm
alter 'ssg2t',''
call ssg2t uset,gm,goa,goq,mje/
mea/
nomset/nosset/nooset/atqset $
alter 's,n,noqset'
alter 'equivx.*mtqx'
else $
equivx mvaa/mvqq/-1 $
endif $
endalter
1-62884428
2008.0.0 (MD R3)
SOL 600 - MSC.Nastran 2007r1 Windows 32 b
it delivery contians wrong mpich for marc dmp.
SOL 600 in the 32 bit Windows MSC.Nastran 2007 r1 release uses the 32 bit Marc
solver that works with the old MPICH libs/service. Unfortunately, Nastran
2007r1 is distributed with the newer MPICH2 libs, not the older mpich. This
will cause SOL 600 dmp jobs to fail.
A possible workaround is to install mpich from Marc 2005r3 or Nastran 2005r3
installation CDs
1-62884471
2008.0.0 (MD R3)
t ID's are used in steps in SOL400
SOL 400 - UWM 602 issued if non-unique se
In SOL 400, if non-unique set ID's are used in multple steps, then UWM 602 will
be issued and the last defined set is used. However for multiple subcases,
all defined sets are used, not just the last defined one. Sets defined in steps
should behave the same as sets defined in subcases.
1-62886781
2008.0.0 (MD R3)
ailed in ROTOR of subdmap GYROBASE
Optimization/Design Sensitivity - RGYRO f
SOL 200 job with RGYRO failed in ROTOR module in subdmap GYROBASE due to
missing EDOM.
Avoidance:
Apply the folloiwng alter:
compile desopt $
alter 'call fea'(3,),''(3,) $
IF ( NOSEDV>-1 and nopaload>-1 ) CALL FEA,
$.............Input Data Blocks:
abe,acpt,,aebgpdts,aecomp,aero,aeusets, , ,bgpdtvu,casadj,CASECC,
caseds,casem,casers,CASdsn,CASdSn,CASEXX,control,cstma,CSTMS,
,
DEQATN,DEQIND,DFFDV,DIT,dits,DMIs,DMINDXs,drg,DRSTBL,
DYNAMIC,DYNAMICS,ectas,EDOM,EDT,eht,ehta,elemvol,
EMAP,EPT,epta,EPTS,eqexin,EQEXINS,ETT,extdb,FPA,FPG,FORCE,
gdgk0,gdksk,gdntab,GEOM1,geom1qx,geom1s,GEOM2,GEOM2S,GEOM3,GEOM3S,
GEOM4,GEOM4S,GPDTS,gpgk0,gpksk,GPLS,gpsnts,,INDTA,lcdvec,MAPS,,,
medge,mklist,mmcdb,MPT,MPTS,MXOMEG,oint,PCDB,PCDBS,pcompts,pelsets,
PMA,POSTCDB,ptga,pval,PVT,pvtbc,PVTS,,R1TABR,scstm,SILS,SLIST,SLT,
spline,SPSEL,tabdeq,tabevp,tabevs,TPG,trx,ufoo,UG1PVT,
,utoo,
VGFS,vgq,viewtb,XYCDB,XYCDBS, ,mpjn2o,mpjsfn2o,aempcomp,aemonpt,
saemprk,strucomp,monitor,saerg0,aedbstdx,uxvst,pgvst0,adbindx,
adbuxv,adbwjv,adbfjv0,adbqkv0,xsop2dir,CASEDM,LVTABI,
geom1qs,geom4qs,selist,pvt0,dmonpta,dmonpts,sdsrg0,sdark,pvperq,,,
pbrmsd,pbrms,mp1,mpd1,mp3,strplab,edts,ymu,xinit,dvptab,,,
ifexpnt,vefs,afpmlist,/
$.............Output Data Blocks:
,aeqgdka,aeqgdkl,
,
,AQG,AUa,AUG,
,
B2DD,B2MG,B2SF, ,bdict,belm, ,BGPDTS,bgpdt,BHH,
, ,BLAMA,
BLAMA1,BMG,BPHA,BSF,BUG,CBDD,CB2DD,CKDD,
CK2DD,clama,CMDD,CMLAMA,CMPHA,CMPHO,cphd,cphh,cphp,
crj,crx,
,d1jk,
,d2jk,Dar,DELS,DELX,DFFDNF,
ditid,
,dlt,ECTS,epsse,
,
,est,
,FLAMA,
,FOL,FOL1,FPHH,frl,
gdak,
,
,gdkl, ,GM,GOQ,GOT,gpak,GPECT, GPGK,gplk,iuxlr,
K2DD,K2MG,KZRR,K2SF,
,
,
,
,K4MG,K4SF,
, ,KALV,KAzr,KDICT,
,KELM,
KFS,KHH, ,kll,KMG,KSF,KSS,L2RR,
lajj,lajjt,LAMA,LAMA1,LAMAF,LAMAS,LLL, ,
lphd,lphh,lphp,
,LSALL,
M2MG,M2SF,MAR, ,MDICT,MEA,MELM,MHH,
,MIRR,mjj,
, ,MMG, , ,MSF,MTRAK,
,PA,PD,PDF,PDT,PDTDS,PG, ,PHA,
,PHDH,PHF,
PHFA,
,PHG,
,
,
,
,philz,PHQG,PHSA,PJ,
PL,PLR,PNLH,PPF,PPF1,PPT,PPTDS,
,PSF,PSF1,PSS,PST,
pst1ds,PSTDS,PTELEM,QG, ,
, ,
, ,
,qkks,
,
,qmg,qmpf,qmpt,QPF,QPT,QR,
,skj,
,TOL,TOL1,TOL2,TR,
U2RR, uajj, uajjt,UDF,UG,
,,UHF,UHT,UHTDS,UL,
ULF, ,ULTDS,UOO,UPF,UPT,urlr,USALL,USET,USETD,
VAFS,VELEM,
,vgfd,VPHFS,WKK,wskj,wskjf,XTMADJ,YS,
,
saerg ,saera,saerl, , ,plvst,aedbuxv,
mpaerv,mpserv,mpsirx, prbdofs,aedbindx,aerrv,aeurv,
uergv,ueugv,uxdifv,wqkv,,mdphiq,mdgot,mdgoq,mdvft,mdmap,
mdgrdrm,mp2slab,mp2st,mp2ugcp,mp3int,mp3lab,mp3gpf,
mp2a,mp3a,mp2sa,mp3sa,s2a,s3a,sdsa,sdsra,sdsrl,vgfdt,thetam,
aciect,sild/
AERO/adjflg/AERTYP/ALTRED/APP/AUNITS/AUTOSPC/BUCKCC/cnvflg/false/
CYCLIC/dceigcc/DESCYCLE/deseig/desmax/DFRQCC/DFRQDSA/dfrspcf/DMRESD/
DROPT/DROPTDS/dstspcf/DVRGCC/dtrspcf/ebis/ERROR/EXTERSE/
'sensitivity'/FIXEDB/fluidse0/FLUTCC/FSCOUP/G/GUSTAERO/HFREQ/IKBAR/
IMACHNO/INREL/IQ/KDAMP/enfmeth/LASTSEID/LFREQ/LMODES/LUSETS/mceigcc/
MFRQCC/MFRQDSA/MODACC/MODECC/domtran/MTRNCC/NASOUT/nk/NLHEAT/NOPH1/
NOPH2/NOSEDV/OPTIMIZE/PEXIST/PSLOAD/rgsens/RSONLY/SAERCC/dosaero/
SEKR/SELG/SELR/SEMG/SEMR/SKPAMG/SKPAMP/SOLTYP/STATCC/dostatic/
$..I/O Parameters:
S,ADPTEXIT/S,ADPTINDX/s,BOV/s,BMETH/s,CARDNO/s,freqdep/
s,FS/s,luset/s,METHF/s,MDTRKFLG/s,MODETRAK/s,NMSOL/
s,NORSET/s,NOSASET/s,NSOL/s,PFILE/S,PVALID/s,STATSUB/
s,SUPORT/NNDFRQ/deltab $
1-62947313
2008.0.0 (MD R3)
ct CWELD element forces
Connector Elements - SET, CWELD - Incorre
Patch to patch CWELD element forces may be incorrect when data recovery is
performed on a subset of the CWELD elements.
1-63123040
2007.0.1
FM 4016 (TA1ETD)
Nonlinear Analysis - CGAP, TEMP(LOAD) - U
If a nonlinear analysis, SOL 106, contains GAP elements with temperature loads
the analysis may fail with
USER FATAL MESSAGE 4016 (TA1ETD)
Avoidance: Ttemeratures must be assigned to all grid points in the model. If
an element does not have temperature load (e.g. GAP), then tempature load will
not computed for that element but a temperature must still be assigned to the
connecting grid points.
1-63209211
2007.1.0
um Linux only V2007.0.0
Miscellaneous - Signal 11 from EMG, Itani
An error in subroutine PREMAT may cause jobs on Version 2007.0.0 Itanium Linux
to fail in the EMG module with a Signal 11 error in the log file.
1-63212781
2008.0.0 (MD R3)
=16 - Wrong Answers
Frequency Response - UMFPACK, SYSTEM(209)
When using the UMFPACK solver option, "system(209)=16", the FRRD1 module, i.e.
frequency response, will produce wrong answers when the dynamic matrix is real
and the load matrix is complex.
1-63278281
on IA64
2008.0.0 (MD R3)
Performance - Unsymmetric Decomp is slow
In MDR3 rnd 0 I optimized TXUYRD (-O3), the time went from over 8 hrs to less
than 3 hrs. jjg 12/07/07
If an analysis is exhibiting poor performance in unsymmetric decomp (UPSD) in
MSC.Nastran Version 2007r1 or MD R2.1 compared to prior releases or other
systems, then a new shared object is avaible for download that should rectify
the problem.
The download is available at:
Another aviodance is too run with "mode=i8"
This error is fixed in MSC r1a (rnd 36). I am leaving the quality open until
MD is fixed.
1-63338536
2008.0.0 (MD R3)
SOL 600 - "CONSTANT" gets written to marc
deck which may lead to wrong answers
SOL 600 may incorrectly write "CONSTANT" to the translated marc input deck.
For elastic analysis with elements that offer constant dilatation option
(elements 7, 10, 11, etc.), use of CONSTANT is wrong and can change the results
significantly. CONSTANT should only be used in conjunction with elasto-plastic
analysis.
Avoidance: Specify STOP on the SOL 600 entry, edit the marc.dat file and
remove the CONSTANT entryt and submit directly to marc,
1-63369252
2008.0.0 (MD R3)
Optimization/Design Sensitivity - dresp3
referecning dresp1 that span subcases may fail
SOL 200 job with a dresp3 that references a dresp1 that spans subcases may
fail with UFM rtype not supported for a solution type. The subcases are of
different solution types and DRESP1s of DRESP3 covers only a type.
Avoidance: Insert following dmap alter.
$
$ DMAP_1001b.alter - intend to fix a problem for dresp3 spans
$
subcases where the input deck has both
$
static and dfreq subcases.
compile presens,list $
alter 'dopr3'$
PARAML resp3x//'TRAILER'/1/S,N,N3x//S,N,NOR12x $
if (solapp='STNMBK' ) then $
if ( nor12x>-1 and desglb>0 ) desglb = -desglb $
else $
if ( nor12x=-1 ) delete /resp3xm,,,, $
endif $
$
compile descon $
alter 'dsad ' $
PARAML rsp3xr//'TRAILER'/1/S,N,N3x//S,N,NOR12x $
if (solapp<>'STNMBK' and nor12x=-1 ) then $
delete /rsp3xm,,,, $
n3xt = 0 $
endif $
1-63482165
DMP/Eigenvalue Analysis - SFM 3034 in Lanczos
This may be related to known limitations of the Lanczos method when the
mass/differential stiffness
matrix has coupled singularities.
Lanczos sometimes has a problems detecting rank-deficient sets of Lanczos
vectors and this may lead to the folloiwng fatal message:
eigenvalue location information from factorization
-------------------------------------------------shift at: 1.1844D+06
there are
852 eigenvalues to the left of 1.1844D+06
block size used
:
7
no. of eigenvalues to compute on the right: 167
no. of eigenvalues to compute on the left : 192
number of steps
:
0
eigenvalues found
:
0
total no. eigenvalues:
168
(BUCKLING).
*** fatal error no. -728 *** subroutine lnnp2cd
unrecoverable termination from lanczos iteration
internal error code: -6
the following
82 computed eigenvalue(s) comprise all the eigenvalues
in the region between the least and the greatest in this list
Avoidance: Not running dmp or setting system(166)=48 may avoid the problem.
1-63602119
Miscellaneous - IFP - UFM 4392, Continuation Card Errors
This CR is canceled until the user can reproduce the error with no user-defined
continuation fields. --Mike R 2/19/08
It has been reported that nastran automatically created duplicate continuation
fields for a DMIG and CORD2R and the run subsequently failed with the message:
*** USER FATAL MESSAGE 4392. CONTINUATION CARD ERRORS. EXPLANATIONS FOLLOW
LIST OF CARDS IN ERROR.
ERROR
NUMBER
. 1 .. 2 .. 3 .. 4 .. 5 .. 6 ..
9 .. 10 .
1++0025PQ41.5994 7.8873 2.339
+0025PR
2*+0025PQ8712658
1
8.3534777760D-01
*+0025PR
0EXPLANATION OF ERROR CODES ABOVE FOLLOWS...
1- FIELD 1 IS NOT UNIQUE
2- MORE THAN ONE CARD HAS A FIELD 10 WHICH IS THE SAME AS FIELD 1 OF THIS
CARD
3- CARD IS AN ORPHAN( I.E. NO PARENT CARD EXISTS )
TOO MANY CONTINUATIONS FOR BULK DATA ENTRY CORD2R 7621
SORTED ENTRY
COUNT = 7731
7 ..
Avoidance:
entries.
8 ..
1-63608373
Order the deck and specify system(357) to ignore continuation

2008.0.0 (MD R3)
Rotordynamics - SDR1 - UFM 1126 (GNFIST)
When a multiple subcase SOL 107 analysis with rotordynamic is run with the
keyword scr=no, the run will fail in the second subcase with the following
fatal error.
DMAP MODULE SDR1
CPHP
201 NAME =
USER ACTION: DELETE THE DATABLOCK, OR USE FILE CPHP=OVRWRT

Avoidance: Set the keyword scr=yes or input a unique CMETHOD request for each
subcase.
1-63659021
2008.0.0 (MD R3)
matic element in the model
SOL 400 - AUTOSPC fails if there are kine
For SOL400, If there are rigid elements with RIGID=LAGR case control command,
the AUTOSPC command will not work correctly.
1-63684101
ut for BEAM3
2008.0.0 (MD R3)
Composites - FAILURE THEORY show bad outp
If the PCOMP FT field is blank, FAILURE THEORY output of "STRESSES IN LAYERED

COMPOSITE ELEMENTS (BEAM3)" shows bad charactes in the output for the BEAM3
element.
1-63716721
2008.0.0 (MD R3)
ment Summary Table
Elements - CBUSH, ELSUM - Bad Data in Ele
The CBUSH element may lead to illegal characters in the ELEMENT PROPERTY
SUMMARY table.
1-63833183
2008.0.0 (MD R3)
Gaps - SFM 3007 (SOLVE)
Optimization/Design Sensitivity - Linear
In a SOL200, when linear gaps are defined, then if internal iterations are
required the analysis aborts with the following error :
^^^ END ITERATION 1
, CHANGES 2
*** SYSTEM FATAL MESSAGE 3007 (SOLVE)
ILLEGAL INPUT TO SUBROUTINE FACDRV
Avoidance: SSSALTER cditer200a.alt has been developed to avoid this error.
1-63950251
2008.0.0 (MD R3)
Elements - PBRSECT - Arbitrary Beam faile
d with intersecting segments message in the log file
Arbitrary Beam problems, PBRSECT, may fail with a message indicating
"intersecting segments" in the log file
Avoidance:
1. The "intersecting" message typically is caused by short segments with thick
varying thicknesses.
If possible, keep the thickness of short segments
constant.
2. For multiple cells reverse the sequence of the divider.
1-63982967
2008.0.0 (MD R3)
AX in KE-Method of Flutter
Aeroelastic Analysis - XYPUNCH ignores XM
The XYPUNCH of the vg data in the KE-method of flutter may ignore the XMAX
statement, leading to a much larger punch file. The nature of the error
appears to be rather erratic between machines and releases. i
1-64029075
rs
2008.0.0 (MD R3)
SOL 600 - FORCE - Wrong Load, Wrong Answe
Multiple FORCE entries for the same grid point leads to incorrect loads in SOL
600 when multiple subcases exist. For example, the entries
FORCE
FORCE
FORCE
1
1
1
96
96
96
0
0
0
10.
12.
14.
-1.
0.
0.
0.
-1.
0.
0.
0.
-1.
lead to an incorrect load in the marc soltution that doubles the Y load and
triples the Z load.
1-64138511
2008.0.0 (MD R3)
ence Messages Misleading
Optimization/Design Sensitivity - Converg
SOL 200 may issue messages to the affect that hard convergence has not been
achieved but then subsequent output indicates the convergence criteria is
satisfied. There are two convergence criteria provided in the output: The
objective should not have changed by greater than a specified amount and the
maximum constraint value must be lesss that a certain value. There is a third
criteria that is not listed in the output and that leads to the misleading
message: The previous design cycle must have achieved a feasible design.
The feasible design criteria needs to be added to the output so that it is
clear why hard convergence is not achieved.
1-64164481
2008.0.0 (MD R3)
664 Linux machines using HP/MPI
Parallel Processing - DMP OMP error on x8
Use of the HP/MPI on x8664 Linux systems may result in the following message:
OMP abort: Initializing libguide.a, but found libguide.so already initialized.
This may cause performance degradation and correctness issues.
Set environment variable KMP_DUPLICATE_LIB_OK=TRUE to ignore
this problem and force the program to continue anyway.
Please note that the use of KMP_DUPLICATE_LIB_OK is unsupported
and using it may cause undefined behavior.
For more information, please contact Intel(R) Premier Support.
1-64426459
2008.0.0 (MD R3)
translated correctly
SOL 600 - NLPARM Case Control Command not
SOL 600 input with multiple subcases may incorrectly increment the referenced
nlparm id and not translate the entry correctly. .
1-64508068
)
2008.0.0 (MD R3)
Composites - PCOMPLS - UFM 6352 (IFP6NLM
If PCOMPLS defaults are taken for the DIRECT and CORDM fields the following
error occurs.
*** SYSTEM FATAL MESSAGE 6352 (IFP6NLM)
LOGIC ERROR: KERROR=9317.
0FATAL ERROR
Avoidance: Explicitly enter the defaults for DIRECT and CORDM fields on the
PCOMPLS entry.
1-64535990
2008.0.0 (MD R3)
Optimization/Desing Sensitivity - dmp>1 a
nd scr=no - UFM 1126 in DISUTIL for EPT
SOL 200 optimization runs with dmp>1 and scr=no may fail with the message:
DMAP MODULE DISUTIL IS ATTEMPTING TO OUTPUT DATABLOCK

USER ACTION: DELETE THE DATABLOCK, OR USE FILE EPT=OVRWRT
201 NAME = EPT

compile desopt
alter 'delete.*scstm,pval,epta'
delete /ept,geom2,geom3,geom4,mpt $
endalter
1-64550902
2008.0.0 (MD R3)
D/PWELD formulation
SOL 600 - Marc translator error with CWEL
In SOL 600, if the "PARAM,MARCWELD,1" is set, analysis with CWELDs & Type
ELEMID, the shell element identification numbers
of elements on patch A and B (i.e., SHIDA, SHIDB) will not be translated into
the marc.dat file correctly.
1-64573838
SFM 3007 (GI)
2008.0.0 (MD R3)
Aeroelastic Analysis - SPLINRB, SPBLND2 -
The recently introduced SPBLND1 and SPLBLND2 entries do not work when one or
both of the splines being blended is a SPLINRB. Further, the SPBLND2 entry
can result in the following fatal error
*** SYSTEM FATAL MESSAGE 3007 (GI)
ILLEGAL INPUT TO SUBROUTINE GIB32D
This fatal occurs because the AELIST data has not been sorted into ascending
order. It's possible this error can be avoided by renumbering the AELIST
entries, but this is not reliable.
Finally, the SPRELAX entry has an IFP limit that the field 2 data must be
unique. This is an unnecessary restriction.
1-64697639
nswers
2008.0.0 (MD R3)
Modal Frequency Response - B2PP - Wrong A
Nastran incorrectly selects the uncoupled soltution algorithm when an

unsymmetric B2PP matrix with no diagonal term is entered in modal frequency
response. This leads to wrong answers.
Avoidance:
Put a small term on the diagonal of the B2PP entry.
1-64762002
2008.0.0 (MD R3)
l body properties
ADAMSMNF - Fluid in a tank gives wrong
Current ADAMS code can not handle coupled mass formulations of which virtual
mass is a subset, and will incorrect "Global Body Properties". In MD R3
(version 2008.0.0) the DMAP will issue a fatal message similar to the one
issued if param,coupmass is present for virtual mass in an adams flex MNF run.
1-64783158
2008.0.0 (MD R3)
Composites - PCOMP - Improve UFM 315
A PCOMP entry that specifies FT and not SB will fail with a message similar to
the one below. Note: this error is first trapped in V2005.1, prior versions
allow the model to run. In MD R3 (version 2008.0.0) this message will be
improved by adding "SB field is required when FT field is specified."
Globa

FORMAT ERROR ON BULK DATA ENTRY PCOMP
PCOMP 1000
-.06859 0.0
TSAI
70.0
0.0
+000001
++000001
10
2.30
35
0.40
+000002
USER/PROGRAMMER INFORMATION:
BULKNM = PCOMP (Name of the Bulk Data Entry)
KM =
J+1 =
0 (0:First Line, >0: Continuation Lines)

5 (Data Field Number, 1 through 10)
MF() =
0 (Field Data Format: 0=Blank, 1=Integer, 2=Real,
3=BCD, 4=Double, -32767=End-of-Data)
M() = <BLANK> (Field Data Value)
CALLSB = IXPCOMP (Name of subroutine)
1-64932461
2008.0.0 (MD R3)
DRESP2, DRESP1 - Illegal Input to dsad5
If a SOL 200 optimization analysis contains a DESGLB case control command that
references DRESP2 entries that references a DRESP1 with weight as one of the
arguments, the analysis may fail with a message that indicates illegal input
to dsad5.
Avodiance: Reference dresp1 of weight directly on DRESP2 solves the problem
with 20055. However, it does not work on 2006t1.
1-65037771
OFFT
2008.0.0 (MD R3)
Documentation/QRG - SOL 600 - PARAM, MARC
The QRG documentation for PARAMETER MARCOFFT references a PARAM "MOFFOCRE"

this should be "MOFFCORE".
1-65037789
CORE
2008.0.0 (MD R3)
Documentation/QRG - SOL 600 - PARAM, MOFF
The QRG description of PARAM MOFFCORE contains a reference to "MARCOFFFT".

The reference should be to "MARCOFFT"
1-65049111
2008.0.0 (MD R3)
Nonlinear - CASI solve fails in NLSOLV w
hen "save/restore memory" option is turned off by user
The NLSOLV module implementation of the CASI iterative solver interface
includes an option to save/restore NLSOLV memory used around the call to the
CASI solver. The default action is to perform the save/restore. This option
can be disabled by the user. When disabled, very large problems may fail with
a segmentation error in the NLSOLV module.
Avoidance: Do not disable the save/restore option.
1-65063971
2008.0.0 (MD R3)
ADAMSMNF - PARAM,COUPMASS,0 - Virtual MAS
S should not be allowed with Nastra/ADAMS interface
The nastran-adams interface does not currently support a coupled virtual mass
formulation. Thus, if param,coupmass,0 is specified in combination with
ADAMSMNF flexbody=yes is specified a fatal message is issued. .
1-65153748
2008.0.0 (MD R3)
ct labels for PFMODE and PFPANEL
Frequency Response - MODESELECT - Incorre
The modeselect command may lead to incorrect mode id, and frequency labels in
the PFMODE output.
Avoidance: Use the following DMAP alter
compile semfreq $
alter 'call gmax','' $
CALL GMAx,
CASEg ,MATPOOLs,EQDYN ,TFPOOL ,bgpdts ,
,cstms ,MAA
,GOt
,goq
,
GM
,USETD ,KAA
,BAA
,K4DD
,
PHsA
,LAMAs ,DITs
,VAFS
,PHFA
,
lamaf ,Aaa
,kddd
,mechg ,lammats ,
lammatf ,mis
,mif
,dynamic ,vgfd
,
rotor ,rotmat ,day
,nzyg
,goy
,
phba
,efmfacf ,efmfacs ,mdphiq ,mdgot ,
mdgoq ,mdvft ,mdmap ,mdgrdrm ,VEFS
,
KPP
,MPP
,BPP
,uset
/
,
,CMDD
,CK2DD ,CB2DD ,
MHH
,BHH
,KHH
,PHDH
,VPHFS ,
K2MG
,M2MG
,B2MG
,K2SF
,M2SF
,
B2SF
,k2ss
,m2ss
,b2ss
,btab
,
modselsv,MODELSTS,MODELSTF,vgfdt ,
,
b2dsf ,m2dsf ,k2dsf ,k4hh
,phbh
,
lamasn ,lamafn /
LUSETD /SOLTYP /APP
/NOUE
/NOA
/
FALSE /S,FMODE /FALSE /FALSE /FS
/
NOMSET /fonly /S,FMODEF/freqdep /s,xfastfr/
mdotm0 /rsonly $
alter 'call pfact','' $
CALL PFACT CASEF ,BGPDTS ,USET
,USETD ,SILS
GOT
,GOQ
,GM
,PHDH
,LAMASn
LAMAFn ,UHF
,FOL
,PHF
,VGFS
VPHFS ,KHH
,BHH
,MHH
,ABE
AGG
,mdotm ,YPF1
,RPY
,YPF
SMPF
,SMPFD ,OSMPF1 ,AFMPF ,AFMPFD
OAFMPF1 ,ASMPF ,ASMPFD ,OASMPF1 ,APMPF
APMPFD ,OAPMPF1 ,APPF
,APPFD ,OAPPF1
AGPF
,AGPFD ,OAGPF1 /
NOASET /NOOSET /NOQSET /NOTSET /NOMSET
NOA
/NOUE
/APP
/SOLTYP /FS
FONLY $
compile gmax $
alter 1,1 $
SUBDMAP GMAx CASES ,MATPOOL ,EQDYN ,TFPOOL ,BGPDTS ,
EQEXINS ,CSTMS ,MMAA
,GOT
,GOQ
,
GM
,USETD ,MKAA
,BAA
,K4DD
,
PHSA
,LAMAS ,DIT
,VASF
,PHFA
,
LAMAF ,AAA
,KDDD
,MECHG ,LAMMATS ,
LAMMATF ,MIS
,MIF
,DYNAMIC ,VGFD
,
ROTOR ,ROTMAT ,DAY
,NZYG
,GOY
,
PHBA
,EFMFACF ,EFMFACS ,MDPHIQ ,MDGOT ,
MDGOQ ,MDVFT ,MDMAP ,MDGRDRM ,VESF
,
KPP
,MPP
,BPP
,USET
/
KDD
,BDD
,MDD
,KDDMACC ,BDDMACC ,
MHH
,BHH
,KHH
,PHDH
,VPHSF ,
K2MG
,M2MG
,B2MG
,K2SF
,M2SF
,
,
,
,
,
/
,
,
,
/
/
B2SF
,K2SS
,M2SS
,B2SS
,BTAB
,
MODSELSV,MODELSTS,MODELSTF,VGFDT ,UNUSED3 ,
B2DSF ,M2DSF ,K2DSF ,K4HH
,PHBH
,
LAMASN ,LAMAFN /
LUSETD /SOLTYP /APP
/NOUE
/NOA
/
NONLNR /FMODE /NLHEAT /CYCLIC /FS
/
NOMSET /FONLY /FMODEF /FREQDEP /XFASTFR /
DOOTM /RSONLY $
alter 'call gmam','' $
CALL GMAM MSAA
,BSAA
,KSAA
,K4SAA ,KDSAA ,
PHBSA ,MFAA
,BFAA
,KFAA
,K4FAA ,
PHBFA ,AAA
,VASF
,M2DD
,B2DD
,
K2DD
,VESF
,USETD ,PHSA
,LAMAS ,
MIS
,LAMMATS ,EFMFACS ,PHFA
,LAMAF ,
MIF
,LAMMATF ,EFMFACF ,DIT
,MDPHIQ ,
MDGOT ,MDGOQ ,MDVFT ,MDMAP ,MDGRDRM ,
CASES ,DYNAMIC ,USET
,GM
,GOT
,
ROTOR ,ROTMAT /
MHH
,BHH
,KHH
,K4HH
,PHDH
,
VPHSF ,BTAB
,MODSELSV,MODELSTS,MODELSTF,
PHBH
,LAMASN ,LAMAFN /
APP
/SOLTYP /FS
/FONLY /ACSYMl /
UE
/NOUE
/DOOTM /S,FMODE /S,FMODEF/
S,XFASTFR/rsonly $
compile gmam $
alter 1,1 $
SUBDMAP GMAM MSAA
,BSAA
,KSAA
,K4SAA ,KDSAA ,
PHBSA ,MFAA
,BFAA
,KFAA
,K4FAA ,
PHBFA ,AAA
,VASF
,M2DD
,B2DD
,
K2DD
,VESF
,USETD ,PHSA
,LAMAS ,
MIS
,LAMMATS ,EFMFACS ,PHFA
,LAMAF ,
MIF
,LAMMATF ,EFMFACF ,DIT
,MDPHIQ ,
MDGOT ,MDGOQ ,MDVFT ,MDMAP ,MDGRDRM ,
CASES ,DYNAMIC ,USET
,GM
,GOT
,
ROTOR ,ROTMAT /
MHH
,BHH
,KHH
,K4HH
,PHDH
,
VPHSF ,BTAB
,MODSELSV,MODELSTS,MODELSTF,
PHBH
,LAMASN ,LAMAFN/
APP
/SOLTYP /FS
/FONLY /ACSYMl /
UE
/NOUE
/DOOTM /FMODE /FMODEF /
XFASTFR /rsonly $
1-65322401
2007.1.0
translator error
SOL 600 - CBUSH using CID gets incorrect
If a NASTRAN input file using CBUSH elements that reference a local coordinate
system (the CID filed) is run in NASTRAN v2007r1, the translator stops with the
following message:
** Severe Warning in SOL 600 translator - CBUSH G0, X1, X2, X3, CID for CBUSH
1 is not fully supported. To ignore these fields, enter bulk data
param,marcbush,1
This message is inappropriate, as in version 2007r1, Marc has an equivalent
CBUSH that can use the local coordinate system. Setting PARAM,MARCBUSH,-1
allows the translator to translate the element correctly. The message should
indicate that marc can not be run using dmp with this element is used.
1-65390757
2008.0.0 (MD R3)
UFM 1126 for PHFAHX
MDACMS - acoustics, modeselect(fluid) -
In an mdacms acoustic run using sol 111 the following error message can occur
when modeselect(fluid) requests a subset of the fluid modes:
DMAP MODULE PARTN
PHFAHX , WHICH ALREADY EXISTS.
201 NAME =
Avoidance: Use PARAM,GMA,OLD or insert the following DMAP alter:

compile gmam
alter 1
file phfahx=ovrwrt $
1-65434816
2008.0.0 (MD R3)
SOL 600 - Beam offset for SOL 600
Beams with offsets are translated incorrectly in SOL 600. The offset is
ignored and this may lead to wrong answers.
1-65662259
2008.0.0 (MD R3)
on is incorrect
Documentation/QRG - SOL 600 Continue opti
The SOL 600 entry CONTINUE options 3-5 are not supported and will be removed
from the QRG.
1-65900127
2008.0.0 (MD R3)
does not print associated subcases for DRESP3
DSAPRT does not print associated subcases for DRESP3
1-65930441
2008.0.0 (MD R3)
SOL 400 - DMAP modification fails with SF
A 427 - LOPBLK table has exceeded its maximum entries
When modifying the SOL 400 DMAP with addtional DO-WHILE loops, the job will
fail with SFA 427 - The LOPBLK tabe has exceeded its maximum 1200 number of
entries.
1-65936901
SOL 400, Linear Contact - SFM 4192 with mode=i8
TPL test deck cnt2super which demonstrates linear contact in SOL 101 wil fail
on ILP64 (a.k.a. i8) systems with the message:
^^^ PHASE 1 - SUPERELEMENT GENERATION, ASSEMBLY AND REDUCTION.
GRID POINT
20 IN SUPERELEMENT
1-65937261
2008.0.0 (MD R3)
rigid body is incorrect
SOL 400 - BCONTACT - Position control of
In SOL 400 if a deformable body and a rigid body are in initial contact, the
position control is incorrect.
1-65983571
2008.0.0 (MD R3)
mentation Violation
Numerical Methods - DCMP - Signal 11, Seg
The combination of low available Open Core memory and large Nastran BUFFSIZE
may lead to a Segmentation Violation (Signal 11) in the DCMP or READ modules
during matrix factorization. This non-standard termination causes Nastran to
halt with no Fatal message. Error messages generated by the operating system
may appear in the log file.
Avoidance: There are two potential avoidances:
1. Increase memory via the "mem=" command line keyword.
2. Reduce the BUFFSIZE.
1-66000287
2008.0.0 (MD R3)
SOL 600 - PLOAD4(or any mechanical loads)
& MARCIN entries - Incorrect translation
When PLOAD4 or any mechanical loads are applied coupled with user specified
MARCIN entries for the history data, the MARCIN entry translations will be
written in the wrong location.
1-66004372
2009.0.0 (MD R4)
p64 (i8) systems
DBC - CMASS, CFAST- SFM 6062 (DBC) on il
CMASS and/or CFAST elements may lead to the following fatal message on ilp64
(i8) systems when param,post,0 is specified.
19 FROM SUBROUTINE BLKFIX
OBJECT PFAST ENTRY LENGTH AND DATA DEFINITION IS INCONSISTENT FOR
HETEROGENOUS OPERATIONS.
TRANSMIT AND RECEIVE MUST BE USED TO MIGRATE XDB BETWEEN PLATFORMS.
1-66013381
2008.0.0 (MD R3)
SOL 600 - Marc's parameter option LUMP wi
ll not be applied in transient heat transfer analysis
According to the MD Nastran R2.1 Quick Reference Guide, the "PARAM,MARCLUMP,0
or 1 selects whetherr the lumped specific heat matrix will be used in a
transient SOL 600 heat transfer analyses. However, marc's parameter option
LUMP will not be applied in transient heat transfer analysis and a consistent
specific heat matrix will be used.
1-66013451
2008.0.0 (MD R3)
SOL 600 - NLHEATC entry is not translated
The NLHEATC entry is not translated for SOL 600 transient heat transfer
analysis. it is only translated for steady state heat transfer analyisis.
1-66013500
2008.0.0 (MD R3)
SOL 600 - MARCIN entries for subcases not
translated in heat transfer analysis
MARCIN entries for SUBCASES will not be converted into Marc input for SOL 600
heat transfer analyses
1-66026575
2008.0.0 (MD R3)
Optimization - DSAD - BIOMSG: ERROR
300
The DSAD module attempts to identify grid id's on the dresp1 entry that do not
exist. If the missiing grid is called out in the final subcase and there are
no other grids invoked by this subcase, the message:
BIOMSG: ERROR
0.
, FILE INDEX =
wil be output from the DSAD module.

Avoidance: When the above message occurs in the DSAD module, a check should be
made to inusre that all the GRID id's referenced on DRESP1 entries exist.
1-66026799
2008.0.0 (MD R3)
, DESGLB and DESSUB may fail in dsad module - SFM 6926
A SOL 200 job with DRSPAN and DESGLB/DESSUB that point to the same constraint
set may fail in the DSAD module with SFM 6296 unable to allocate a data block.
Avodiance: This is a user input error which can be avoided by removing the
desglb command in the case control. The presence of drspan turns off the
checking logic for usage of DRESP1 in DESGLB. The checking logic should be
active for those DRESP1s that have nothing to do with DRSPAN.
1-66195125
2008.0.0 (MD R3)
Dynamic Analysis - EPOINTs and DELAY entr
ies in dynamic response, wrong answers, UWM 4193 (DPD7)
If a model contains EPOINTs where at least one EPOINT has an id lower than a
loaded GRID point and the model contains DELAY entries, the answers may be
wrong.
The f06 file contains the warning message:
NO EXCITATION HAS BEEN SPECIFIED FOR ANY OF THE COMPONENTS SPECIFIED ON DELAY
SET
X REFERENCED ON
TLOADi ENTRY
X
where X are integer values.
Avoidance: Renumber the epoints.
Ensure the EPOINT ids are always higher than the largest GRID poiint or SPOINT
ids.
1-66224284
2008.0.0 (MD R3)
PBLNDi - Incorrect Results
Aeroelastic Analysis - SPLINE, SPRELAX, S
There are two errors that affect spline processing with the spline relax
feature and the spline blend feature.
1. If the blend region does not cover the entire overlap region, the splines
are averaged in the unblended area when they should take their value from:
f_1(x) = 1 and f_2(x) = 0 for x < -D1
f_1(x) = 0 and f_2(x) = 1 for x > D2
2. If the same spline is relaxed on two different SPRELAX entries it is
possible that neither is entry is processed.
1-66226424
2008.0.0 (MD R3)
Aeroelastic Analysis - No velocity input
on a AERO entry leads to wrong answers or poor message
In aeroelastic analysis if the user neglects to specify a velocity value on the
AERO bulk data entry the analysis may fail with the message below or wrong
answers may be produced.
The FPU has been reset after floating point exception
1-66267651
2008.0.0 (MD R3)
Optimization/Design Sensitivity - PBMSECT
- UFM 7602 (DOPR1I) with arbitrary beasm cross section
SOL 200 with arbitrary beam cross sections, PBMSECT, may encounter the message:
USER FATAL MESSAGE 7602 (DOPR1I)
1-66309821
2008.0.0 (MD R3)
ith null method type
Acoustic Analysis - GP5 issues UIM 6207 w
The GP5 module issues USER INFORMATION MESSAGE 6207 when there is no ACMODL
bulk data entry defined. The message is supposed to indicate the method that
will be used, but the field is blank becuase it has not been initialized prior
to the message being issued.
1-66309911
2008.0.0 (MD R3)
rrect when MODESELECT used
Dynamic Analysis - MCFRACTION output inco
When the MODESELECT case control command is used to select modes to be used in
the modal analysis and the MCFRACTION command is also present in the case
control, the structure's natural frequency value in the MCFRACTION output may
be incorrect. The value is wrong if the number of modes selected is less than
the number of modes actually found in the eigenvalue analysis. The mode number
is correct when it is only the natural frequncy value that is wrong.
1-66384331
2008.0.0 (MD R3)
ommdand STRUCTMP keyword
Acoustic Analysis - PFMODE case control c
The PFMODE case control command requests modal participation factor output
(MPF). The format of the command allows for specification of either STRUCTURE
or FLUID. The STRUCTURE option produces structural MPF output using structural
natural frequencies. The FLUID option produces acoustic MPF output using
structural natural frequencies for acoustic structure MPF and fluid natural
frequncies for acoustic fluid and panel MPF. For both cases, the STRUCTMP
keyword is used to define the number of structural modes that are used during
MPF calculations. When both PFMODE(STRUCTURE...) and PFMODE(FLUID...) are
present in the input case control, the STRUCTMP keyword is not interpreted
according to the QRG description. Rather, the value used in the structure MPF
computations is the maximum of the STRUCTMP keyword values supplied in the two
commands.
1-66552807
6 node element
2008.0.0 (MD R3)
Acoustics - CHACAB - Incorrect mass for 1
The mass matrix for the 16 node CHACAB acoustic barrier element is not correct.
1-66624921
2008.0.0 (MD R3)
for entry that should be ignored
Eigenvalue Analysis - NLRSFD - UFM (DPD4)
An incorrect NLRSFD entry in eigenvalue analyis will cause the DPD4 module to
be executed and a User Fatal Message to be issued.
Avoidance: Correct the entry.
1-66661307
swers
2008.0.0 (MD R3)
SOL 600 - ISTRESS not honored - Wrong An
The NASTRAN ISTRESS is not translated into the Marc input file and the job
runs to completion without warning yielding results without the ISTRESS effects.
1-66825861
2008.0.0 (MD R3)
Eigenvector Contraints, SFM GREAD
A SOL 200 job with eigenvector constraints combined with other analysis types
may fail in the DSAD module with an error during GREAD.
Avodiance: None. If possible, run SOL 200 job with mode and eigenvector
constraints only.
1-66833371
2008.0.0 (MD R3)
CQUAD8 - UFM 7632 (EWLDPD)
Connect Elements - CWELD, CFAST, CQUAD4,
If CWELD or CFAST elements are used to connect a patch of CQUAD4 elements with
CQUAD8 the following fatal message may be issued:
*** USER FATAL MESSAGE 7632 (EWLDPD)
FOR CWELD ELEMENT ID=
102, A CONNECTION TO ONE OF THE SHELL SURFACES
CANNOT BE MADE.
USER INFORMATION: THE FIRST THREE SHELL GRIDS ARE
51
53
61
*** USER FATAL MESSAGE 2026 (EMG)
ELEMENT
102 GEOMETRY YIELDS UNREASONABLE MATRIX.
SEMG
1-66916611
2008.0.0 (MD R3)
WBULK - Incorrect punched bulk data
Optimization/Design Sensitivity - ECHO NE
A SOL 200 model with DVGRID and ECHO = PUNCH(NEWBULK) may contain incorrect
information in the punched bulk data deck.
Avoidance: The output produced using the despch parameters is correct and can
be used to construct a new bulk data deck.
1-66918399
2008.0.0 (MD R3)
Documentation/QRG - BCTABLE
In the MDR2 QRG, the description of the BCTABLE entry indicates that it is for
SOL100, it should indicate SOL 101.
1-66941791
2008.0.0 (MD R3)
-set - SFM 6144 (PARTN1PR)
External Superelements and Acoustics - C
An external superelement creation with an acoustic cavity and C-set will result
in SFM 6144 (PARTN1PR):
*** SYSTEM FATAL MESSAGE 6144 (PARTN1PR)
SPECIFICALLY:
The number of columns in KOA is not equal to the number of rows in the
column partitioning vector VFT
KOA
: Rows= 4443394 by Cols=
2561
VFT
: Rows=
562
VFO
: Rows= 4443394
Avoidance:
compile semr3
alter 'vfo',''(2)
partn
koa,vafs,vofs/,,,kotf/1 $
endalter
1-66953461
)
2008.0.0 (MD R3)
SOL 400 - RIGID=LINEAR - SFM 4370 (SDCPRF
SOL 400 with RIGID=LINEAR may fail with SYTEM FATAL MESSAGE 4370 (SDCPRF)
1-66984621
2008.0.0 (MD R3)
Connector Elements - MODGM2, CWELD, CFAST
, PARAM,CHKRUN,2 does not funciton correctly
An analysis with CWELD and/or CFAST elements will not be stopped after checking
the connector elements when PARAM,CHKRUN,2 is set.
1-66988471
Virtual Mass - PARAM,SOLVIT,YES + PARAM,VMOPT,2 does unneces
sary DECOMP of CEE
In a dynamic analysis, if MFLUID and ELIST entries are present to model virtual
mass and the iterative solver is selected, the solution performs an unnecessary
expensive factorization of the CEE matrix.
ECHOOFF $
COMPILE VMDEC NOLIST $
$
ALTER 'PARAML.*USET','' $
TYPE PARM,,CHAR8,Y,SOLVIT='NO' $
TYPE PARM,,I,N,NP $
$
ALTER 'PUTSYS.*209'(,-1) $
IF (SOLVIT='YES' AND GETSYS(NP,216)=1) RETURN $
ENDALTER $
ECHOON $
1-67131007
2007.1.1
Submittal - mem=estimate does not work af
ter updating MSC.Nastran to version 2007.1.1
After updating MSC.Nastran 2007.0.0 to 2007.1.1 (2007 r1a) by
installing the update from:
http://www.mscsoftware.com/support/software_updates/nastran200711.cfm
a Nastran job with mem=estimate will output the following error messages:
nastran instest.dat mem=estimate
MSC.Nastran V2007.1 (Intel Windows .NET 5.2 (Build 3790)) Thu Dec 20 10:55:55
2007
*** SYSTEM INFORMATION MESSAGE (pgm: nastran, fn: estimate_job_requirements)
Starting ESTIMATE, please wait...
*** SYSTEM FATAL MESSAGE (pgm: estimate, fn: main)
MSC.Nastran Version 2007.1 is not supported. Supported releases: 68.2,
70.7, 2001.0, 2004.0, 2004.5, 2005.0, 2005.5, 2006.0, 2007.0
*** SYSTEM WARNING MESSAGE (pgm: nastran, fn: estimate_job_requirements)
a.estimate=c:/msc.software/msc.nastran/2007r1a/msc20071/i386/estimate.exe
(program default)
ESTIMATE processing failed.
*** SYSTEM INFORMATION MESSAGE (pgm: nastran, fn: estimate_job_requirements)
Assuming "memory=8MW" as specified by the "memorydefault" keyword.
Avoidance: A compatible estimate program has been put to the product update
site.
MSC.Nastran beginning job instest.

1-67131791
2008.0.0 (MD R3)
AUTOMSET - RBE3 - SFM 4276 (BLDPRD)
A simulation with RBE3 s that incorrectly define degrees of freedom as

dependent and independent produces the follwing unsatisfactory fatal message if
used with AUTOMSET (PARAM,AUTOMSET,YES).
ERROR CODE
211 PID= 0
*** USER INFORMATION MESSAGE 4276 (BLDPRD)
USER ACTION: THIS INFORMATION MAY BE USEFUL TO MSC FOR DEBUGGING YOUR
PROBLEM.
PLEASE CONTACT MSC CLIENT SUPPORT.
1-67191021
ERROR
201
2008.0.0 (MD R3)
External Superelement - DMIGPCH - BIOMSG:
During an assembly run using the external superelement feature, the job may
fail with the following unclear message in IFP if the DMIGPCH option and data
recovery is requested for the external superelement. This error is fixed in
MDR3.
BIOMSG: ERROR
0.
STATUS =
201 HAS OCCURRED IN ROUTINE WRITE
, FILE INDEX =

INDEX LOGNAME
1 SCRATCH
STREAM_ID
00000001
NAME
c:/scratch/assembly.T3284_17.SCRATCH
Avoidance: There are 2 possible avoidances.

1. Use the op2 file option.
2. If data recovery is not needed for the external superelements, remove the
DMI and DTI entries from the .pch file.
1-67273981
2008.0.0 (MD R3)
r=no - UFM 1126 (QQGNI)
Nonlinear Statics - ANALYSIS=HOT2COLD, sc
If scr=no is requested along with ANALYSIS=HOT2COLD and rigid elements or MPCs

are present the run may terminate with UFM 1126 on data block QQGNI.
Avoidance: Run with scr=yes and insert the following DMAP alter:
compile nlstatic
alter 1
file qqgni=ovrwrt $
endalter
1-67375341
2008.0.0 (MD R3)
nsistent Results
Complex Eigenvalue Analysis - HESS - Inco
A complex eigenvalue analysis using the Hess method where the mass matrix is
many orders of magnitude different that the stiffness matrix may produce
inconsistent results.
Avoidance: Use the CLAN method as follows:
EIGC
+EIGC
104
1.0
CLAN
0.0
+EIGC
50
50
500
or to run HESS with the following alter:

compile ceigrs, list
alter 65
matprn ckdxx,cbdxx,cmdxx//'long' $
add ckdxx,/ckdyy/1.e-8 $
add cbdxx,/cbdyy/1.e-8 $
add cmdxx,/cmdyy/1.e-8 $
equivx ckdyy/ckdxx/always$
equivx cbdyy/cbdxx/always$
equivx cmdyy/cmdxx/always$
1-67457421
2008.0.0 (MD R3)
T/PBMSECT may fail in DOM9
Optimization/Design Sensitivity - PBRSEC
a SOL 200 analysis with PBRSECT/PBMSECT entries in the design model may fail
in the VKI code with intersecting boundary segments. This failure may occur as
the element is designed since the segment may intersect each other as segments
becoming thicker.
Avoidance: Allow ample space for segments in abitrary beam elements to "grow"
without intersecting.
1-67610541
2008.0.0 (MD R3)
d - Incorrect example
Documentation/QRG - CBAR, CBEAM OFFT fiel
The example in the QRG for both the CBEAM and CBAR shows an "O" as the 1st
letter for the OFFT field. Remark 8 documents the allowed specifications.
1-67661477
2008.0.0 (MD R3)
Aeroelastic Analysis - Multiple SPRELAX e
ntries that share relaxed grids give wrong results.
If there are multiple SPRELAX entries and the same grids are "relaxed" by two
of more of these entries, the job runs but the results are incorrect.
Avoidance: Do not attempt to relax the same aerodynamic grid from differing
SPRELAX enties.
1-67677181
2008.0.0 (MD R3)
Optimization/Design Sensitivity - PBMSECT
, PBRSECT, DOM9 - Inefficient Processing
SOL 200 with a large number of PBMSECT or PBRSECT, arbitrary beam cross
section, and design variables may consume a large amount of cpu time in the
DOM9 module. The time is spent updating sensitivity for nonlinear relations
between design variable and properties.
1-67685315
2008.0.0 (MD R3)
ription incorrect
Documentation/QRG - OPGEOM parameter desc
The parameter description for OPGEOM reads, "OPGEOM < *1 prints the set
definition for all degrees-of-freedom, including the aerodynamic
degrees-of-freedom."
This should be:,
OPGEOM > -1 prints the set definition for all degrees-of-freedom, including
the aerodynamic degrees-of-freedom.

1-67685627
2009.0.0 (MD R4)
SYSTEM FATAL MESSAGE 2007 (CNTLSTR)
SOL 400 - tpl test nbolt02b fails with
The tpl test deck nbolt02b may fail on some platforms with the message:
*** SYSTEM FATAL MESSAGE 2007 (CNTLSTR)
ELEMENT 3165 REFERENCES UNDEFINED GRID POINT 0
1-67694384
Superelements - PARAM,DBUP, PARAM,DBDN UFM 1127(GNFIST)
Running superelements, using param,dbup and dbdn. On the restart the dbup
database is moved to a different diectory or just deleted. The job fails with
the following message.
DMAP MODULE OUTPRT IS ATTEMPTING TO ACCESS DATA BLOCK
WHICH IS ON AN UNAVAILABLE DBSET
117 NAME = GPECT
Avoidance: The following alters will correct the problem.

In Version 2005.5 - 2006.
compile SPDR1 list noref
alter 154,154
$alter 158,158
OUTPRT CASES,ECTS,BGPDTS,SILS,XYCDBS,,,,VUPSE,
CASEDS,TABEVP,TABEVS,MMCDB,OINT,PELSETS,
EDTS/
V01DR0,VSPCG,VMPCG,JUNK,/
S,N,SDRS//'SPARSE'/SPDRRAT/ADPTINDX/
ADPTEXIT $
endalter
In version 2007r2
compile SPDR1 list noref $v2007r2
alter 157,157
EDTS,
,FRFlabel/
ADPTEXIT $
The following alter fixes prereleased v2007r3/2008
compile SPDR1 list noref
alter 158,158
EDTS,
,FRFXITZG/
ADPTEXIT $
endalter
1-67750169
Output
2008.0.0 (MD R3)
Elements - STRAIN, CTRIA6 - Null Strain
If only STRAIN output is requested with PARAM,OMID,YES and CTRIA6 elements are
present in the model, the STRAIN results for all the CTRIA6 elements are output
as 0.0 when they should be nonzero. With PARAM,OMID,NO (default) the STRAIN
results are nonzero.
Avoidance: A request of STRESS output will cause the STRAIN results for the
TRIA6 elements to be correct.
1-67770500
2008.0.0 (MD R3)
anslate properly
SOL 600 - CBEAM - Orientation does not tr
SOL 600 does not translate beams whose orientation references other than the
basic coordinate system correctly.
1-67775400
6062 in DBC
SOL 400 - PARAM,POST,0 - All i8 systems, mode=i8, produce SFM
SOL 400 with mode=i8 and param,post,0 may fail in the DBC module with the
19 FROM SUBROUTINE BLKFIX
OBJECT NQD4R ENTRY LENGTH AND DATA DEFINITION IS INCONSISTENT FOR
HETEROGENOUS OPERATIONS.
TRANSMIT AND RECEIVE MUST BE USED TO MIGRATE XDB BETWEEN PLATFORMS.
0FATAL ERROR
1-67780355
2008.0.0 (MD R3)
ansion coefficients is incorrect.
SOL 600 - Translation of MAT9 thermal exp
In SOL 600 the translation of MAT9's thermal expansion coefficients is

incorrect.
The old and new mapping is as follows:
11
12
13
22
23
33
New
A1
A4
A6
A2
A5
A3
Old
A1
A2
A3
A4
A5
A6
1-67838600
2008.0.0 (MD R3)
External Superelements - EXTSEOUT, MDACMS
, and PARAM,FLUIDSE - SFM 6144 for MQQ
External superelements, EXTSEOUT, combined with mdacms and param,fluidse will
lead to the following fatal message:
SPECIFICALLY:
The number of columns in MQQ is not equal to the number of non-zeros in
partitioning vector VFS
The number of rows
in MQQ is not equal to the number of non-zeros in
partitioning vector VFS
MQQ
: Rows=
116 by Cols=
116
VFS
: Rows=
2
no. of non-zeros=
1 no. of zeros=
1
compile mdphs1b
alter 'EQUIVX aG',''(,18)
alter 'UPARTN USET, PF'
EQUIVX aG/aN/nomset $
if ( nomset>-1 ) then $
UPARTN USET,aG/aNBAR,aM,,/LGSET/LNSET//1 $
MPYAD
GM,am,aNBAR/aN/1 $
endif $
equivx an/af/nosset $
if ( nosset>-1 ) UPARTN USET,aN/aF,aS,,/LNSET/LFSET//1 $
UPARTN USET, aF/aO,aA1,,/LFSET//LASET/1 $
EQUIVX aA1/aT1/noqset $
alter 'UPARTN USET,PA1'
UPARTN USET,aA1/aT1,,,/LASET/LTSET//1 $
alter 'partn po,,vofs'
partn bot,vtfs,vofs/bsot,,,bfot/1 $
alter 'partn btt1,vtfs,'
partn at1,,vtfs/ast1,aft1,,/1 $
equivx ast1/at1/-1 $
partn ao,,vofs/aso,,,/1 $
alter 'solve
kfoo,kfot',''
dbstatus kfoo//s,n,nokfoo $
if ( nokfoo>0 ) solve
kfoo,kfot,,,/gotf $
alter 'cmpmode'(,-1)
if ( methfl>0 ) then $
ENDIF $
alter 'paraml cmphof',''
paraml cmphof//'trai'/1/s,n,nmf//s,n,nocmphof $
alter 'merge
cmphof,,,gsoqx,'
else $
merge
,,gsoqx,,,,vofx/goqq/1 $
endif $
alter
if
alter
endif
'diagonal cmmif'(,-1)
( nocmphof>-1 ) then $
'equivx kqqw'
$
alter 'mpyad at'(,-1)

if ( false ) then $
alter 'mpyad aq'(2)
endif $
alter 'paraml cmphof'(2)
alter 'call newlamax'(,-1)
else $
merge
,,,,cmphso,,vofx/cmphoxx/1 $
equivx cmphoxx/cmpho/-1 $
merge
,,,,cmphsa,,vafx/cmphaxx/1 $
equivx cmphaxx/cmpha/-1 $
equivx eigvmats/lammat/-1 $
equivx cmmi/mi/-1 $
endif $
alter 'merge
ktt,,,kftt,vtfs,'
merge
at,,,,,vtfs/at2/1 $
equivx at2/at/-1 $
alter 'merge
mqtf,,,'(,-1)
alter 'equivx bqtr\/bqt'
else $
merge
,,,mqt,,vtfx,/mqtr/1 $
equivx mqtr/mqt/-1 $
merge
,,,k4qt,,vtfx,/k4qtr/1 $
equivx k4qtr/k4qt/-1 $
merge
,,,bqt,,vtfx,/bqtr/1 $
equivx bqtr/bqt/-1 $
endif $
alter 'MERGE
,,PQ,,,,VQ'
MERGE
,,aQ,,,,VQ/aQ1/1 $
alter 'UMERGE USET, PQ1, PT'
UMERGE USET, aQ1, aT/aA/LASET/'Q' $
alter 'umerge uset,atfs,aqfs',''
endalter
1-67870768
was set to -98
2008.0.0 (MD R3)
GPFORCE - SET - UWM 2354 (GPFDR), NERROR
If a GPFORCE request is made in different subcases where each request specifies

a different set, processing may be inefficient of the job may fail with the
message:
THIS ERROR OCCURRED IN CODE WHERE THE VARIABLE -NERROR- WAS SET = -98
*** SYSTEM WARNING MESSAGE 3002 (GPFDR)
SUBROUTINE GPFDFR
1-67922591
2008.0.0 (MD R3)
swapped y/z axes
Elements - CBEAM3, PBMSECT using VAM has
A composite beam defined using the CBEAM3 and PBMSECT entries will swap the y/z
axes.
Avodiance: if possible, turn the orientation vector for CBEAM3 90 degree in YZ
plan.
1-68046176
2008.0.0 (MD R3)
ontain an i8 version for HP MPI
Installation - MD Nastran R2.1 does not c
MD Nastran R2.1 does not contain an i8 version for HP MPI. Critical clients
have requested this system and it has been added for MD R3.
1-68288009
2008.0.0 (MD R3)
TET4 element Produces Wrong Answer
Acoustic, Fluid Analysis - CETRA - PFLUID
The lack of a coupled mass matrix for the fluid formulation of the four noded
CTETRA element can result in wrong answers and spurious modes. Setting
NASTRAN,SYSTEM(446)=1 will result in the old answers.
1-68343941
2008.0.0 (MD R3)
t lead to Illegal input to DSAH31
Topology Optimization - Stress constrains
A message that indicates illegal input to DSAH31 will be issued in a SOL 200
topology optimization run when stress constraints are included.
Avoidance: Remove the stress constraint from the problem definition
1-68477767
2008.0.0 (MD R3)
Parallel Processing - DMP - DFMFR*: MAXIM
UM ESTIMATED FRONT SIZE MAY BE EXCEEDED.
When dmp processing is selected with MDMOES the ordering method must be Extreme
(BEND). However, an error in the code may allow METIS to be chosen this may
lead to poor performance and the following message:
*** SYSTEM INFORMATION MESSAGE 6916 (MREORDR)
DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: METIS
DFMFR*: MAXIMUM ESTIMATED FRONT SIZE MAY BE EXCEEDED.
1-68554289
2008.0.0 (MD R3)
SOL 600 - CHEXA20 - *** error - alias set
up on element type 150 which is not on sizing card
SOL 600 may translate the CHEXA20 element incorrectly. The translated alias
entry may point to elment type 20 instead of 21. This may lead to the error
message:
*** error - alias set up on element type 150 which is not on sizing card
1-68655761
2008.0.0 (MD R3)
Aeroelastic Analysis - SPLINE7 - Splining
nearly coincident points produces bad spline matrix
Splining two coincident points with a SPLINE7 produces good results. However,
if one of the points is moved by a very small amount, the resulting spline
matrix is bad.
1-68672091
2008.0.0 (MD R3)
n for addrad method
SOL600 - QRG MATEP - Missing documentatio
The QRG description of the MATEP "addrad" method was inadvertantly removed
from the QRG. The addrad method should be described as:
addrad for additive decomposition using the radial return process (SOL 600 only)
1-68799191
2008.0.0 (MD R3)
CEIG, LAMA, EiGN, FLUT - Zero Sensitivity
Optimization, SOL 200, with superelements where DRESP2 entries reference a
global response via a DRESP1 entry, such as CEIG/LAMA/EIGN/FLUT, may fail due
to zero sensitivity on violated constraints.
1-68834573
2009.0.0 (MD R4)
the nlsolv module on Windows
SOL 400 - Casi iterative solver hangs in
SOL 400 using the casi solver, see tpl test pt400casi, have been observed to
hang in the nlsolv module.
1-68928401
tput
2008.0.0 (MD R3)
DMP - PFMODE, PFPANEL, PFGRID - Extra ou
The modal participation commands PFMODE, PFPANEL, and PFGRID will result in
extra output for the slave processes.
Avoidance: The following alter can be used to avoid the problem:
compile feafreq $
alter 'call pfact'(1,-1) $
alter 'IF ( NOAFPM=1 ) CALL AFPMDRCV' $
endif $
compile sedfreq $
endif $
alter 'IF ( NOAFPM=1 ) CALL AFPMEND','' $
IF ( NOAFPM=1 and procid<=1 ) CALL AFPMEND
PVT,AFPMLIST $
compile semfreq $
endif $
alter 'IF ( NOAFPM=1 ) CALL AFPMEND','' $
IF ( NOAFPM=1 and procid<=1 ) CALL AFPMEND
PVT,AFPMLIST $
1-68986819
UFM 9139
2009.0.0 (MD R4)
External Superelements - assembly run -
User Fatal Message 9139 is produced in the assembly (restart) run of an

External Superelement analysis, if a METHOD entry refers to a new EIGR/L entry.
Avoidance: use the following DMAP alter:
compile phase0
alter 'if ( nocasew',''
if ( nocasew>0 and not(app='bkl0' and isolapp=1) and
(seid=0 and
(acms or mdacms or numseg>1 or nclust>1)) ) then $
endalter
1-69034400
2007.0.2
ases - UFM 5423
Aeroelastic Analysis - Multiple GUST subc
Since V2005 and through V2005r3, if there are multiple GUST subcases then the
job will fail with the following message. The error was fixed by DMAP in
V2007r1 but the code error still exists in the GUST module.
FILE#
COLS
ROWS FORM
306
501
54
TRAILER FOR PHF
110
2004
54
TYPE NZWD DENS

3
108 10000
216 10000
IS

compile freqrs
alter 'gust.*cases'(,-1)
type parm,,i,n,quit
paraml fol//'trailer'/1/S,N,nfreq $
file pdfg=save $
paraml cases//'trailer'/1/s,n,nrec $
if ( nrec=1 ) then $
alter 'gust.*cases'
else $
DO WHILE ( QUIT>=0 ) $
CASE
CASES,/CASE1/'TRAN'/S,N,QUIT $
GUST
CASE1,DLT,FRL,DIT,QHJL,,,ACPT,CSTMA,,
APPLOD,ENFLODK,ENFLODB,ENFLODM,ENFMOTN/
Pdfj,wjj,qhjkj,ppj/
S,N,NOGUST/BOV/MACH/Q $
if ( quit=2 ) then $
$ first subcase
paraml pdf//'trai'/2/s,n,nrow//s,n,nopdf $
if ( nogust<0 and nopdf>-1 ) then $
paraml pdf//'trai'/4/s,n,ntype $
matgen ,/pdfg/7/nrow/nfreq//ntype $
else $
equivx pdfj/pdfg/-1 $
endif $
else $
$ second and subsequent subcases
append pdfg,pdfj/pdfh/1//nfreq $
equivx pdfh/pdfg/-1 $
endif $ quit=2
enddo $
call xadd5 pdfg,pdf,,,/pdfx/cu/cu/cz/cz/cz $
endif $ nrec=1
The above temporary DMAP avoidance scheme was needed for V2005. This scheme
was built into the freqrs subDMAP in MDR2/V2007. With the code changes made as
part of the resolution of this CR, this built-in avoidance scheme has been
removed from the freqrs subDMAP in post-MDR3/V2008 releases
1-69091628
2008.0.0 (MD R3)
Acoustic Analysis - BNDFREEi or CSETi, a
nd PARAM,SESDMAP and QSETi or PARAM,AUTOQSET - SFM 3001
If component modes and PARAM,SESDAMP,YES is requested on a fluid-structure then
the run will terminate in subDMAP cmpmode with: SFM 3001 MPYAD SOL103
datablock 201
Compile cmpmode
Alter 'IF ( NZBK4ZZ',''
Paraml /mphvz/'name'////s,n,nomphvz $
IF ( NZBK4ZZ>0 and nomphvz>-1 ) then $
alter 'mpyad
mvv,phivz'
merge mphvz,,,,,vvfx/mphvz1/1 $
equivx mphvz1/mphvz/-1 $
1-69113343
2008.0.0 (MD R3)
UFM723(RDINIT)
File Management Section - INIT in RC(F) -
If INIT statement spans two or more lines in RC(F) file, MSC.Nastran 2007r1 and
MD R2 will read only the first line and the folloiwng fatal message will be
issued:
INIT SCRATCH LOGICAL=(SCR1(2000MB),SCR2(2000MB),SCR3(2000MB),
NASTRAN REAL=902037504 $(PROGRAM DEFAULT)
*** USER FATAL MESSAGE 723 (RDINIT)
LOGICAL= EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES
Avoidance:
Enter the INIT lines directly in the input deck.
1-69161608
2008.0.0 (MD R3)
rminates without message
DMAP - INPUTT4, sparse, ASCII format - te
When inputting an OUTPUT4 file created using the sparse format (IUNIT<0) and
ASCII format (ASSIGN ... FORMATTED) the run may terminate in INPUTT4 without
message. Specifically it occurs if the matrix has a string word length such
that when it is multipied by the word size (e.g, 1 word for real single, 2 for
real double and complex single, and 4 for complex double) exceeds 99,999,999.
Avoidance: There is no known avoidance other than to not use the sparse format
or switch to the binary format.
1-69175341
2008.0.0 (MD R3)
Composites - Temperature-Dependent compos
ites may cause wrong result or infinite loop in SDRCOMP
Temperature-Dependent composite materials will cause either wrong result or an
infinite loop in SDRCOMP
Avoidance: Use param,nocomps,-1
1-69398011
2008.0.0 (MD R3)
Optimization/Design Sensitivity - Complex
Eigenvalue with Static Displacement Constraints Fails
A SOL 200 job with complex eigenvalues and static displacement constraints may
fail if a semi-analytical method is utilized for sensitivity computation.
AVoidance: Use the adjoint load method which is the default. Specify
'param,autoadj,no' to turn on semi-analytical method.
1-69423731
2008.0.0 (MD R3)
(DBC), Poor Message
Postprocessing - PARAM,POST,0 - SFM 6062
The fatal message below indicates that the run failed while writig to the xdb
file a primary index overflow. The xdb file may be corrupt.
**** DIOMSG ERROR MESSAGE
6 FROM SUBROUTINE WRTLST
OVERFLOW OF DICTIONARY PRIMARY INDEX FOR DATA BASE UNIT
1.
Avoidnace: . The avoidance is to rerun the job and include the following assign
statement in the File Management Section of the input fie...
ASSIGN DBC='YourFileName.xdb',RECL=32768,UNIT=40,DELETE
1-69539261
2008.0.0 (MD R3)
Dynamics - auto-suport - wrong answers
If the stiffness matrix is slightly ill-conditioned and non-singular the
auto-suport feature may mistakenly assume the model is free-free and include
Lagrange multipliers to support the structure and produce wrong answers.
Avoidance: Insert PARAM,AUTOSPRT,NO the following DMAP alter:
compile autosprt
alter 'diagonal dk\/dk1',''(,4)
type parm,,i,n,irow,xovr2 $
PARAML KXX1//'TRAILER'/1/S,N,NOXSET $
matmod dk,,,,,/srtlst,srtbool/35/1//2 $
xovr2 = noxset/2 $
paraml srtlst//'dmi'/1/xovr2/s,n,medrow $
irow = int(medrow) $
paraml dk//'dmi'/1/irow/s,n,kavsq $
kfilt=kavsq*kzero $
endalter
1-69578457
2008.0.0 (MD R3)
Composites - CQUADR with PCOMP not pickin
g up ply direction correctly leads to bad transverse shear
CQUADR with PCOMP is not picking up the ply direction correctly and this may
lead to incorrect transverse shear stiffness.
Avoidance:
Uset the CQUAD4.
1-69604951
2008.0.0 (MD R3)
SOL 400 - VCCT - Incorrect defaults docum
ented for GCII and GCIII field leads to UFM 315 (IFPDRV)
Incorrect defaults for various fields of the VCCT entry may lead to the
message:
FORMAT ERROR ON BULK DATA ENTRY VCCT
The following discrepancies are noted:
IDCR: QRG indicates default=1, currently these is no default
Code will be change to default to 1.
INCM: QRG indicates default=2, default=1
Documentation will be corrected.
TIME: QRG has no default & SOL-600 only, current default=0.0
QRG will be corrected.
GC-II: not supported
GC-III: not supported
TABGC-II: not supported
TABGC-III: not supported
Code will be changed to support:
GC-II: added with default=0.0 (QRG changed accordingly)
GC-III: added with default=0.0 (QRG changed accordingly)
TABGC-II: added with default=0
TABGC-III: added with default=0
1-69734486
2009.0.0 (MD R4)
terminated abnormally
Aerelastic Analyis - SPLINE Metrics - GI
TPL test asm4b and inputs with spline4 or spline5 entries that employ automatic
blending may fail in the GI module on Solaris, HPUX, AIX and Windows.
Avoidance: Run on Linux.

1-69735046
2009.0.0 (MD R4)
) on HPUX ILP64 (i8)
Arbitrary Beam - PBMSECT - SFM 3007 (IFP9
Arbitrary beam problems may fail on hpux ilp64 (i8) systems with the following
fatal message:
*** SYSTEM FATAL MESSAGE 3007 (IFP9)
ILLEGAL INPUT TO SUBROUTINE VAB2
0FATAL ERROR
Avoidance: Run the analysis on another system or use the lp64 default
executable.
1-69900403
2008.0.0 (MD R3)
Optimization/Design Sensitvity - Static a
nd Complex Eigenvalue Subcases may lead to fatal message
A SOL 200 job with static and mceig subcases may fail with a message indicating
a missing CPHP, comple eigenvectors
compile ceigsens $
alter 'paraml.*cases','' $
paraml casem//'dti'/1/5//s,n,meth $
1-69917277
2009.0.0 (MD R4)
MPRES output when SET specified
Acoustic Analysis - Incorrect Results for
Data recovery for Pressures in elements on the Fluid/Structure Boundary may be

incorrect if the MPRES case control request specifies a SET that does not
contain all of the elements referenced in the MFLUID ELIST data and there is no
other case control request that causes all of the displacements to be
recovered. If sparse data recovery operations are active, the element
pressures could be wrong. An avoidance is to specify MPRES=ALL and/or to
specify full displacement data recovery at all points as with DISP(PLOT)=all.
Avoidance: Apply the following DMAP avoidance. :
compile semg $
alter 'MGEN
CASES,MATPOOL,EST,CSTMS' $
PARAML CASES//'DTI'/-1/194//S,N,mpreq $
if ( mpreq=-1 ) then $
matmod gge,,,,,/pvgzrow,/47 $
paraml pvgzrow//'trailer'/2/s,n,gsize $
matgen ,/unitpv/4/1/gsize//gsize $
add
unitpv,pvgzrow/pvecnz/(1.0,0.0)/(-1.0,0.0) $
matmod pvecnz,,,,,/pvgnzrow,/2/1///0.1 $
upartn uset0,pvgnzrow/pvnzga,,,/'g'/'a'//1 $
umerge uset0,pvnzga,/pvmpres/'g'/'a' $
call dbstore pvmpres,,,,//0/0/'dball'/0 $
endif $ mpreq=-1
compile spdr1 $
alter 'call xadd5 vupse,vgfd','' $
call dbfetch /pvmpres,,,,/0/0/0/0/s,i $
call xadd5 vupse,vgfd,pvmpres,,/vg/cu/cu/cu/cz/cz $
1-69922401
2007.0.1
Documentation/QRG - TABLEM1 - Remark is n
ot Correct for Heat Transfer

Remark 6 under the Quick Reference Guide description of the TABLEM1 entry is
not correct for heat transfer analysis. For heat transfer analysis, the
values returned by the table are a factor that are multiplied by the value from
the MAT4 entry, y=z*yT(x)
MAT1+MATT1 : y=yT(x)
MAT4+MATT4 : y=z*yT(x)
1-69947571
2008.0.0 (MD R3)
ith Fortran IO error
Restarts - DBLOCATE /DBDICT job crashes w
A DBLOCATE job fails with the following system mesage on AIX system:
"1525-002 The I/O statement on the internal file cannot be completed because
the end of the internal file was reached.
The program will stop."
Other system may fail with differerent system message.
Avoidance: re-run the job with more memory.
1-70102379
Plotting - XYPUNCH- Poor Message, UWM 979 (XYTRAN)
If an XYPUNCH case control command references a subcase that does not exist the
resulting message that follows may reference an element id that does exist.
AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID 89004117
-DISP- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA
BLOCK
104 SUBCASE
46
1-70170479
2008.0.0 (MD R3)
Optimization/Design Sensitivity - DFREQ Wrong sensitivities for multiple boundary conditions
SOL 200 with DFREQ and multiple boundary condition static subcases may produce
incorrect sensitivity coefficient.
Avoidance: Inclue the following DMAP alters
compile pslgdv $
alter 'dbview.*case0','' $
DBVIEW CASE0=casdsn WHERE (SEID=0 ) $
$
compile respsen $
alter 'dbview.*case0','' $
DBVIEW CASE0=casdsn WHERE (SEID=0 ) $
1-70251161
2008.0.0 (MD R3)
Complex Matrices
DMAP - MATMOD Option 12 has problems with
For complex matrices, if a column's first entry is of the form ( 0.0, i ) then
this column is mistakenly identified by MATMOD Option 12 as a null column when
all other entries in the column are 0.0.
Avoidance: Use MATMOD option 34 to divide the complex matrix into two real
matrices and search these two matrices for null columns.
1-70311681
2008.0.0 (MD R3)
Static Analysis - MONTPNT1 - Results wit
h multiple boundary conditions can be in error

If a sol 101 run is made that includes monpnt1 entries and multiple boundary
conditions, only the a-set from the final subcase is used in reducing the loads
to the a-set with the result that the monpnt1 results can be in error for the
preceding subcases.
1-70386662
2008.0.0 (MD R3)
Optimization/Design Sensitivity - PLOAD1
or PLOAD4 - UFM 2268 or UFM 3001 in subdmap UPDATE
A SOL 200 model with both SAERO and STATIC subcases and PLOAD1 or PLOAD4
entries, will fail with the messages:
*** USER FATAL MESSAGE 2286 (SSGSLB)
ELEMENT 869689 REFERENCED ON PLOAD1 2 NOT FOUND
5 DOES NOT EXIST.
STATEMENT
compile update
alter ' ssg1 ',''
paraml cases//'dti'/1/394//s,n,nsm $
TA1
,,ECTS,EPTs,BGPDTS,SILS,ETT,CSTM0,,,,,/
EST0,,GEI,GPECT0,,,ditid,,nsmest/
LUSETS/-1/S,N,NOSIMP/1/S,N,NOGENL/0//////nsm $
SSG1
SLT,BGPDTS,CSTMS,medge,EST0,MPTS,ETT,EDT,,CASESX,
DIT,,DEQATN,DEQIND,gpsnts,cstm0,scstm,geom4s,,,,,,/
pg,,,,/luset/1//'allids '///seid
$$
1-70446681
2008.0.0 (MD R3)
SOL 600 - MATEP - Ryield field is ignore
In SOL 600, the Ryield field of MATEP entry is ignored. The user can not
select yield criteria.
1-70645371
s
SOL 400 - Rigid Body enforced displacement yields null result
SOL 400 with rigid body enforced displacement yields null results.
1-70704881
2008.0.0 (MD R3)
Splines - SPLINEX - UFM 2330 (GIMAPX)
If SPLINEX is the only spline type in the input file, then it is possible that
the SET1 entries from the independent element component be added to the SET1
record of the SPLINE datablock in MKSPLINE. These SET1 entries are already
processed in the MAKECOMP module and their data are already in the SPLINE
datablock on the AECOMP record. The GI module processing of SPLINEX does not
need these SET1 entries. However, the GI module also performs error checking on
the SET1 entries and assumes that the data are all grid IDs. Having element IDs
in the SET1 list can lead to the following fatal error:
*** USER FATAL MESSAGE 2330 (GIMAPX)
USER INFORMATION: SET1 OR SPLINE3 ENTRY NO. 100001 REFERENCES EXTERNAL ID
NO. 8000001 WHICH DOES NOT EXIST.
Avoidance: The workaround is to create a dummy grid with the same ID as the
'missing' element.
1-70821471
2008.0.0 (MD R3)
- SFM 3007 Illegal input to DOM10L with DRESP3 and P2CR set
If an attempt is made to limit the print of the most critcal constraints and
their associated responses using the P2CR parameter on the DOPTPRM entry and
there are DRESP3 responses, the following error will be output:
ILLEGAL INPUT TO SUBROUTINE DOM10L
User Avoidance: Remove the P2Cr request or modify the P2 value so that
responses are not reported. Suppressing the print as suggested above does not
affect the optimzation task.
1-70999911
2008.0.0 (MD R3)
Elements - NSML and NSML1 area calculatio
ns sensitive to element order - Wrong Answers
NSML and NSML1 area calculations have been provend to be sensitive to element
order and this can lead to wrong answers.
1-71075451
2008.0.0 (MD R3)
Splines - SPRELAX can give wrong answers
The SPRELAX entry is used to smooth a spline based on an adjacent spline.

Wrong answers may result when this is used to perform relaxation based on
multiple adjacent splines
User Avoidance: Do not attempt to perform the relaxation based on multiple
adjacent splines.
1-71200197
2008.0.0 (MD R3)
SOL 600 - NSTATE specification ignored, I
ncorrect number of states in post file.
SOL 600 in Version 2007.0.0 does not process the AUTO STEP entry correctly and
all calculated states may be written to the post file even though NSTATE is
specified.
1-71254171
SOL 600 - Command Line can not redirect output to different d
irect when the jid has a "-"
The command line for a SOL 600 job can not redirect the output to a different
directory using out= if the jid contains a "-".
1-71296521
Dynamics - DOMAINSOLVER ACMS, AUTOQSET, ADAMSMNF - UFM 5423
If ACMS is requested with ADAMSMNF Case Control and PARAM,AUTOQSET,YES then the
run will fail with:
USER FATAL MESSAGE 5423 (SMPYAD)

ATTEMPT TO MULTIPLY OR ADD INCOMPATIBLE MATRICES
FILE#
TRAILER FOR TRANS
IS 101
TRAILER FOR MJJBW
IS 102
TRAILER FOR TRANS
IS 103
COLS
6942
6936
6942
ROWS
6942
6936
6942
Avoidance: Replace PARAM,AUTOQSET,YES with user-specified q-set or insert the

compile mdphs1b
alter 'MATGEN ,\/VxSPARSE'(,-1)
delete /vxsparse,,,, $
compile phase1dr
alter 'call mdphs1b'
type parm,nddl,i,n,xnoq,xnoqt $
xnoq=xnoqt $
np=xnoqt-xnoq $
matgen ,/vq/6/xnoqt/np/xnoq $
paraml mgq//'null'////s,n,nlmgq $
if ( nlmgq>-1 ) then $
merge
mgq ,,,,vq,/mxq/1 $
delete /mgq,,,, $
$ include mgq in mgg for correct resviner vect
trnsp
mxq/mxqt $
umerge1 uset,mgg,mxqt,mxq,/mgg1/lgset//'q' $
equivx mgg1/mgg/-1 $
umerge1 uset,mxq,,,/mga/lgset//'q'/1 $ append
else $
umerge1 uset,mgg,,,/mgg1/lgset//'q' $ append
equivx mgg1/mgg/-1 $
endif $ nlmgq>-1
paraml kmg//'null'////s,n,nlkmg $
if ( nlkmg>-1 ) then $
umerge1 uset,kmg,,,/kmg1/lgset//'q'/2 $
equivx kmg1/kmg/-1 $
endif $ nlkmg>-1
$ Form MMG and MSF
equivx mga/mna/nomset $
if ( nomset>-1 ) then $
umerge1 uset,mmg,,,/mmg1/lgset//'q'/2 $
upartn uset,mga/mna1,mma,,/lgset/lnset//1 $
mpyad
gm,mma,mna1/mna/1 $
paraml mma//'null'////s,n,nlmma $
if ( nlmma>-1 ) then $
umerge1 uset,mma,,,/mmag/lgset/'q'//2 $
delete /mmg,,,, $
add5
mmg1,mmag,,,/mmg $
else $
equivx mmg1/mmg/-1 $
endif $ nlmma>-1
endif $ nomset>-1
1-71435731
Elements - PELAST - Wrong Answers
Starting with version 2007r1, Nastran may ignore the PELAST entry and only
uses the nominal stiffness given on the PELAS entry.
Avoidance: Add dummy, unused PBUSHT, PDAMPT and PELAST entries with IDs one
greater than the largest PBUSHT, PDAMPT and PELAST IDs currently in the bulk
data.
1-71544413
2009.0.0 (MD R4)
SOL 400 - mode=i8 - jobs may hang
SOL 400 runs, including delivered tpl problems nla009u.dat,nla009v.dat, and

nla009t may hang if submitted with mode=i8 on SGI Irix systems.
Avoidance: Submit without mode=i8.
1-71680471
2009.0.0 (MD R4)
mode=i8, pcomp - SFM 6352 (OXOCOMPH)
SOL 400/Heat Transfer - analysis=hstat,
SOL 400 heat transfer analysis with composites may fail in the ilp64
executables, mode=i8, with the message below:
*** SYSTEM FATAL MESSAGE 6352 (OXOCOMPH)
LOGIC ERROR: 9104
PROGRAMMER INFORMATION: PLYID,NINTP=**********
0FATAL ERROR
Avoidance: Run the analysis without mode=i8.

GINO FILE
103 WAS LEFT OPEN AT PROGRAM TERMINATION.
No Symbolic Replacement variables or values were specified.
1-71790021
nd - UFM 1126
Post processiong - SCR=NO or POST and POST Case Control comma
If SCR=POST (or NO) is used with the POST Case Control command then the run may
fail with:
*** USER
DMAP
OUG1
,
USER

MODULE SDR2
203 NAME =
ACTION: DELETE THE DATABLOCK, OR USE FILE OUG1=OVRWRT
Avoidance: Specify a unique value for TOCASE on all POST command

specifications.
1-71931011
ers
2008p
Aeroelastic Analysis - SPLINE- Wrong Answ
If an aero grid is included in three or more splines and these splines are
included in two or more blends and the overlap in the splines includes grids
that are outside the D1/D2 bounds of the blends, incorrect results will be
produced. This error is being corrected in Version 2008.0.2 which will be
delivered in a patch to analysis.exe on the product update web site at:
http://www.mscsoftware.com/support/software_updates/2008r1.cfm
1-72004541
Normal modes - UIM 9119, MECHFIX - UFM 4405
The massless mechanism check may improperly fail to detect massless mechanisms.
See PARAM,MECHFIX in the QRG.
compile mmfind1
alter 'mmfil1'(2),''
mmfil1=-mmfil $
compile linind
alter 1
type parm,,logi,n,mmfind=true $
alter 'smalleig'(2)
mmfind=(smalleig<0.) $
smalleig=abs(smalleig) $
alter 'MPYAD
U,U,'(,-1)
if ( mmfind ) then
MPYAD
U,U,/U22x/1////6 $
DIAGONAL U22x/U2D/'SQUARE' $
DIAGONAL U2D/UINVSQRT/'WHOLE'/-0.5 $
SMPYAD UINVSQRT,U22x,UINVSQRT,,,/U221/3////1////6 $ U22(I,I) = 1.0
else $
alter 'MPYAD
U,U,'
endif $
alter 'DIAGONAL U221'(,-1)
if ( mmfind ) then $
equivx u221/u22/-1 $
else $
alter 'SMPYAD UINVSQRT,U221'
endif $
alter 'SMPYAD U,UINVSQRT,PHI2'(,-1)
if ( nom1=-1 or not(mmfind) ) then $
alter 'SMPYAD U,UINVSQRT,PHI2'
ELSE $
MPYAD
U,PHI2,/U2 $
ENDIF $
1-72137291
2009.0.0 (MD R4)
d , memory - SFM 3008
SOL 400 - Heat Transfer , hemi-cube metho
When using the hemi-cube method for calculating radiation, this particular job
failed with the following error message in the VIEW module when requesting
1.6gb of memory
*** SYSTEM FATAL MESSAGE 3008 (VIEW)
INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE VIEWD
0FATAL ERROR
Avoidance: The job ran with a smaller memory request of 1gb
1-72219606
2009.0.0 (MD R4)
th radaition, infinite cpu loop
SOL 400 - NLMOPTS - Transient thermal wi
SOL 400 thermal transient analysis with radiation may issue NaNs in the message
below and fail or go into an infinite loop if the explicit factor on the
nlmopts entry is set to a value other than the default of zero.
*** IN-CORE MATRIX CALCULATION USED FOR CAVITY

780180 WORDS
iteration number =
1 MEMORY USED =
1 error = NaN
Avoidance: Set field 7, the explicit factor, on the nlmopts entry be the
default of 0.0.
1-72248673
2009.0.0 (MD R4)
ed for CWELD elements
Connector Elements - CWELD - UFM 7595 iss
"USER FATAL MESSAGE 7595" may be encountered due to CWELD elements producing an
incorrect projection of the piercing points.
1-72278576
Nonlinaer Analysis - PCOMP with MEM option fails to converge
when using PARAM,COMPMATT
Nonlinear Analysis, SOL 106, may fail to converge when temperature dependent
material properties for composites using the MEM flag are requested to be
updated with each iteration by setting PARAM,COMPMATT,YES.
Avoidance: If MD is available, use CQUADR instead of CQUAD4 and run in SOL400.
1-72340381
Acoustics - MECHFIX - Wrong answers or UFM 6144
If masslass mechanisms are detected in a fluid-structure model and the

constraint modes are printed with PARAM,MECHPRT,YES will be wrong and the
SPCForces will be wrong in versions prior to MDR3. But all other results are
unaffected by this error. In MDR3 and V2008, the run will fail with UFM 6144
for matrix MECHG.
compile moders
alter ' sdr1 '(,-1)
dbstatus vafs//s,n,novafs $
MERGE
mecha,,,,,VAFS/mecha1/1 $
equivx mecha1/mecha/-1 $
endif $ novafs>0
1-72340620
DMAP - MATGEN option 6 - Wrong answers
If P4, P6, or P8 are zero under MATGEN option 6 will produce an incorrect
vector.
Avoidance: Remove the zero and respecify P3 thru P8.
1-72344531
2008.0.0 (MD R3)
Feature Checkout, UFM 3060
Licensing - MSC_LICENSE_DISCRETE - Double
Setting the variable MSC_LICENSE_DISCRETE is necessary for correct license

processing when two license servers, one with concurrent and one with Masterkey
or EALU tokens, is used.
An error exists in license processing when the
MSC_LICENSE_DISCRETE variable is set that may result in a double checkout of
the same feature. The error only occurs when the features on the first server
are concurrent, i.e. not Masterkey or EALU, and the license check for the
feature exists in multiple places in the code. Although all products make use
of MSC_LICENSE_DISCRETE, only nastran tends to check for the same feature in
multiple locations, so it is much more likely to encounter the problem. A

second problem may result in a failed license checkout when a license feature
does not exist at all on the first server but does on the second.
Avoidance: If unsetting MSC_LICENSE_DISCRETE or pointing to the token based
server first is not practical, then the system may be corrected by updating the
lapi.so file in the delivery with a corrected version available at:
http://www.mscsoftware.com/support/software_updates/lapi.cfm
http://www.mscsoftware.com/support/software_updates/.
Please note that due
to quality 1-72344531, this problem is not resolved on SGI Irix in Verison 2008.
1-72420191
Database - PARAM,DBALL,MASTER and DBSETDEL DBALL - UFM 1124
If PARAM,DBALL,MASTER is specified along with DBSETDEL DBALL then the run will
fail with UFM 1124.
compile ifpl
alter 1
type parm,nddl,char8,n,ifpx $
ifpx='master' $
endalter
1-72589921
7.3.0 and above
Licensing - Lapi, Discrete - SGI Irix will not work with Lapi
MD Nastran R3 on SGI Irix has reached the operating system limit of the dso
table size and this prevents upgrading the Lapi FLEXlm licensing layer to 7.3
or above. Until this is resolved the DISCRETE double check out problem,
quality 1-72344531, can not be addressed on this platform.
1-72804117
2009.0.0 (MD R4)
Documentation/QRG - SOL 700, BCTABLE - E
rror in QRG entry for BCTABLE, METHOD field
The MD 2.1 QRG that is delivered with the software installation has two items
transposed in the description of the METHOD field on the BCTABLE entry. It
currently appears as follows: "SS1WAY: Surface to Surface Two Way" and "SS2WAY:
Surface to Surface One Way." It should be switched so that SS1WAY indicates
one-way contact and SS2WAY indicates two-way contact.
1-72962981
2007.0.1
Illegal input to subroutine APD12
Aeroelastic Analysis - PAERO1 - SFM 3007
The above message will be issued if the user inadvertently places an integer in
fields 3 thru 8 of a PAERO1 entry when a preceding field has been left blank.
Avoidance:Correct the paero1 entry.
1-73000881
tion
Documentation/QRG - NLADAPT SOL 400) - Incorrect field defini
The QRG descriptionn of the NLAPAPT entry incorrectly references a DMAP field
in addition to the correct field description which is IDAMP. This reference
should be removed.
1-73001428
SOL 700 - Errors with initial stress (ISTRSSH) output created
from implicit (PRESTRS) simulation.
When running a prestress (PRESTRS) simulation with composite shell elements the
resultant initial stress information (ISTRSSH) written to the .nastin file has
errors. See below for details.
Some of the items in the ISTRSSH option are known to be wrong based upon the
LS-Dyna documentation, however some options are not documented so the status is
not known. However, it is known that using the default .nastin file on a
rotating composite shell simulation causes it to diverge early in the
simulation while removing the ISTRSSH history variables allows the simulation
to complete.
Notes on results:
Significant stress/strain oscillations are present in both cases (reference
CR ).
However, these oscillations worse for the case that includes the default
.nastin file
Negative internal energy
is indicated in the .d3hsp files for both cases,
(again this is significantly worse for the case that includes the default
.nastin file)
Negative strain energy density
is visible in some elements for both cases;
using Patran to post process results (.d3plot files).
(again this is significantly worse for the case that includes the default
.nastin file)
1-73052213
SOL 700 - RFORCE requires grid (G) reference for rotation axi
s (requirement is not documented)
RFORCE (angular velocity/acceleration load) has an optional grid (G) entry to
define the center of rotation. In SOL 700 if the grid (G) entry is not
entered on the RFORCE a fatal message occurs in the .dytr_prep.out file.
This grid option is not required in standard MSC/MD Nastran solution sequences
but is required in SOL 700; however this requirement is not documented.
Avoidance: Create a grid at the center of rotation and reference this grid on
the RFORCE entry.
1-73228870
Buckling or Preload - STATSUB, REPCASE - SFE 4276 in EMG
If STATSUB references a static subcase which appears below a REPCASE then the
job will terminate in EMG with SFE 4276.
Avoidance: Re-arrange the subcases so that the subcase referenced by STATSUB
appears above REPCASE.
1-73336021
DMAP - MATGEN option 6 - SFE 4276
If any of the parameters P3, P5, P7, or P9 are negative with MATGEN option 6
(P1=6) then the run may terminate in a later module that uses the MATGEN
output. If P2, P4, P6, or P8 are set to a negative number, then the run will
assume zero and this should not be allowed because the zero assumption may not
apply to all platforms.
1-73356415
44 or UFM 9050
Reduction - PARAMs INREL or FIXEDB - Wrong answers or UFM 61
If PARAMs INREL or FIXEDB are specified in the second or greater subcases with
non-default values but not in the first subcase then they will be ignored
during the stiffness and mass reduction to the l-set--computing KLL, MLL, etc.
resulting in fatal errors or wrong answers. The error occurs in SOL 200 and
in SOL 101 with scr=no. See also related CR 1-57703594.

compile phase1dr
alter 'PVT
PVTS,'(3),''
endalter
1-73371791
2009.0.0 (MD R4)
SOL 700 - PBEAM with tapered cross sectio
n translated as constant cross section, Wrong Answers
In SOL 700, the PBEAM elements referencing a varying (tapered) cross section
is not translated correctly. The tapered PBEAM is translated to SOL 700 as a
constant cross section beam (based on the first cross section entered) and no
warning message is indicated to inform the user that the tapered beam is not
being translated.
Avoidance: Since a tapered cross section is not supported in the dytran-lsdyna
solver, the only avoidance is to input an average constant cross section. MD
R4 will be enhanced to automatically calculate the average cross section.
1-73429260
2009.0.0 (MD R4)
SOL 400 - View factor computation failed
to converged using the Hemi-cube method
The SOL 400 view factor calculation may fail to converge using the hemi-cube
method.
Avoidance: Do no select the hemi-cube method on the NLMOPTS entry.
1-73545872
2009.0.0 (MD R4)
mpatible Matrix Multiple
SOL 400 - RFORCE - SFM 5423 (MPYAD), Inco
When there is RFORCE type follower force, SOL 400 may fail in MPYAD with SYSTEM
FATAL MESSAGE 5423 indicating an incompatible matrix multiple when the model
also has either 3D Cotnact or nonlinear RBE elements.
Avoidance: There is no practical avoidance except to turn off follower forces
by setting LGDISP=-1.
1-73626721
2008.0.1
Parallel Processing - PARALLEL, SYSTEM(10
7) - Vendor implementation of subroutine TFORK is missing
Shared memory parallel processing does not work on Windows 32 MD R3 Nastran
(Version 2008.0.0). If attempted (setting parallel (system(107) keyword on
the nastran or submittal line) the job will fail with the message:
system fatal: Vendor implementation of
subroutine TFORK is missing
Avoidance: The MD R3 delivery will be corrected with Version 2008.0.1.
1-73726361
2009.0.0 (MD R4)
Documentation/IOG - Get garbled of MD Nas
tran R3 Installation and Operations Guide
Page 61 and 169 of the MD R3 IOG have mangled text.
Avoidance: The mangled text is not significant to the understanding of the
section. No avoidance is necessary
The first The text is not t
1-73816550
Documentation/QRG - PBRSECT - Composites are not supported
The QRG documentation for the PBRSECT entry incorrectly indicates that it
supports composites and can reference Core and/or Layer. This capability is
only supported with PBMSECT and if attempted with PBRSECT will lead to an error
in IFP indicating illegal format.
1-73873851
u information
2008.0.1
Miscellaneous - f04 file missing delta cp
The MD R3 Verson 2008.0.0 f04 file (Execution Summary) on Windows 32 indicates

0.0 for DEL I/0, CPU and DEL CPU. The MD R3 delivery will be corrected in
2008.0.1.
1-73880221
2009.0.0 (MD R4)
SOL 400 - tpl test nlsqa468 fails wit ufm
9196, A REQUEST IS MADE TO CHAIN WITH NLIC
tpl test nlsqa468 fails wit the message:
USER FATAL MESSAT 9196
A REQUEST IS MADE TO CHAIN FROM NLIC FROM STEP NLIC TO STEP NLIC.
1-73960321
ocessing
Exterior Superelements - EXTSEOUT with ACMS - Inefficient Pr
SOL 103 with EXTSEOUT and ACMS could perform unneeded operations under the
following conditions:
1. No data recovery is specified.
2. A sparse data recovery request is made, and the grid points in the data
recovery request all reside in the A-set.
In either of the two above cases, the program reacts as if FULL data recovery
has been requested. This results in significant unnecessary operations taking
place.
Avoidnace: Workaround is to use the following DMAP alter:
compile mdphs1b
alter 'bdryinfo' $
dbstatus caseo//s,n,nocaseo $
if (nocaseo = -1) equivx cases/caseo/-1 $
endalter
For one user model, this change resulted in a 33% decrease in runtime (from 412
minutes to 274 minutes).
1-74077245
Optimization/Design Sensitivity - PART SE and missing inlcud
e file does exit - UFM 398
A SOL 200 run with PART superelements and missing include files will issue a
fatal message but continue to process.
*** USER FATAL MESSAGE 398 (GETLIN)
A REQUESTED INCLUDE FILE WAS NOT FOUND.
FILE 'missingfile.dat'
1-74123421
Frequency Response - frequency-dependent elements, CBUSH, enf
orced motion, acoustics - SFM 6144
In SOL 111 with frequency-dependent elements, enforced motion, and acoustics
the following message may be issued

SPECIFICALLY:
The number of columns in KFDSH is not equal to the number of rows in the
column partitioning vector VYFS
KFDSH : Rows=
12 by Cols=
5080
VYFS
: Rows= 6571022
VXFS
: Rows=
12
compile freqrs
alter 'call cforce',''
call CFORCE USETd,,ysti,,,,Bfdsh,,kfdsh,k4fdsh,
,,,foli,,,cases,dynamics,dit,vgfs,vphfs,nzyg/
pyfdi/
APP/APP/'enforce'/true/false/fs/fonly $
endalter
1-74141249
2008.0.1
Licensing - MD R3 Windows 32, Linux x866
4, prog= - UFM 3060 (SCA Service Loader)
The MD R3 (2008.0.0) Windows 32 and Linux x8664 SCA enabled builds can not be
used with vertical application licensing such as SimXpert or SimDesigner unless
a full MD Nastran License also exists. If attempted the run will fail with
the message:
*** USER FATAL MESSAGE 3060 (SCA Service Loader)
- AUTHORIZATION ERROR ***
UNABLE TO OBTAIN LICENSES FOR SCA.MDSolver.System.PrintServer
PLEASE REFER TO THE LOG FILE FOR ADDITIONAL DETAILS
1-74205731
Vista 64
controls
percent,
generate
there is
Performance - Windows Vista 64, Server 2008
and Server 2008 64 have removed a system tuning parameter that

memory usage. Without this option, when memory usage approaches 100
I/O intensive applications, especially those such as Nastran that
very large data files overwhelm the system cache, to the point that
no physical memory left and the machine will appear to hang.
Avoidance: The work-around is to tell the various I/O intensive applications

to bypass the use of system caching for their very large files. This is done
by specifying the FILE_FLAG_NO_BUFFERING option in the FlagsAndAttributes
argument specified for CreateFile when the file is opened. For MSC.Nastran and
MD Nastran, the files for which this bypass is necessary are the SCRATCH and
SCR300 files. In nastran this is accomplished by specifying RAW=YES as a SYS
keyword for the appropriate files. Note that RAW=YES also requires that BUFFIO
be requested instead of the default of MAPIO=YES.) Unfortunately, through a
documentation oversight, the use of RAW=YES for Windows is not documented in
the IOG. This will be corrected. These SYS options may also be specified by
using the SYSFIELD command line or RC File keyword option. Example of these
specification on the nastran command is
nastran jid MEM=4GB SYSFIELD=SCR*(RAW=YES,BUFFIO=YES,WNUM=32,WSIZE=16MB)
1-74419791
Linear Contact - BCONTACT - UFM 9058 with SCR=NO
Linear contact jobs will fail with the following message when SCR=NO:
^^^ USER FATAL MESSAGE 9058 (SESTATIC)
^^^ THE SOLUTION FOR THE RESIDUAL STRUCTURE AND THE CURRENT SUBCASE DOES NOT
EXIST
Avoidance:
1) run with SCR=YES
2) insert the following dmap alter:
compile phase1dr $ fix for CR 1-74419791
alter 'lnrcont=(app',''
paraml ACTNODS//'trailer'/6/s,n,n3dclgd $
lnrcont=(app='statics' and nocont>0 and
not(nonlnr and seid=0) and n3dclgd>0) $
1-74429111
2009.0.0 (MD R4)
SOL 700 - MATDERO with MXPRES or MNPEPS
causes failure in dytran-lsdyna - Incorrect Translation
MATDERO with the MXPRES field or MNPEPS field defined is transferred directly
(as is) to dytran-lsdyna and this leads to failure in dytran-lsdyna.
1-74460921
44 (MERGE1PR)
Acoustics - Exterior acoustics with ACMS and ACPOWER - SFM 61
Exterior acoustics in SOL 111 with ACMS and ACPOWER output request resulted in
the following Fatal Error message:
SPECIFICALLY:
The number of columns in MDOTMA is not equal to the number of zeros
in
partitioning vector VSFHE
MDOTMA : Rows=
8714 by Cols=
27
IUE
: Rows=
5502 by Cols=
5502
VSFHE : Rows=
8471
no. of non-zeros=
5502 no. of zeros=
2969
VDAE
: Rows=
14216
no. of non-zeros=
5502 no. of zeros=
8714
Avoidance: Insert PARAM,MDOTM,NO in the bulk data.
1-74513523
Documentation/QRG - PBCOMP - SFM 4548 (NBEM1D)
Remark 8 of the PBCOMP description of the PBCOMP bulk data entry is incomplete
and should have the following sentence added,
All of the points (input plus mirrored) should not lie on a straight line.
Otherwise the NLITER module issues the following SFM:
*** SYSTEM FATAL MESSAGE 4548 (NBEM1D)
SINGULAR (C-KRR) MATRIX ENCOUNTERED FOR BEAM ELEMENT 1
Avoidance: Input values that are not colinear for the Y or Z positions for
SYMOPT=5 on the PBCOMP entry.
1-74542868
2008.0.0 (MD R3)
2 (ROTOR) unable to find DDVAL
A design optimization model with RSPINR referencing DDVAL entries may fail with
the following error:
UNABLE TO FIND SELECTED
(ROTOR).
(ROTOR).
(ROTOR).
0FATAL ERROR
(ROTOR)
SET (
66) IN TABLE (DDVAL ) IN SUBROUTINE
(ROTOR)
SET (
(ROTOR)
SET (
This error occurs in DESOPT and is caused by a call to FEA with missing
datablock EDOM.
Avoidance: This alter will provide a proper work-around for V2005.5 and 2007.0
compile desopt list deck
alter 'l fea'(2),''
CALL FEA,
$..INPUT DATA BLOCKS:
ABE,ACPT,,AEBGPDTS,AECOMP,AERO,AEUSETS,
CASEDS,CASEM,CASERS,CASES,CASESX,
, ,BGPDTVU,
DEQATN,DEQIND,
,CASECC,
,CONTROL,CSTMA,CSTMS,
,DIT,DITS,DMIS,DMINDXS,DRG,
DYNAMIC,DYNAMICS,ECTAS,edom,EDT,EHT,
EHTA,ELEMVOL,EMAP,EPT,EPTA,EPTS,EQEXIN,EQEXINS,ETT,EXTDB,,,FORCE,
GDGK0,GDKSK,GDNTAB,GEOM1,GEOM1QX,GEOM1S,GEOM2,GEOM2S,GEOM3,GEOM3S,
GEOM4,GEOM4S,,GPGK0,GPKSK,GPLS,GPSNTS,,INDTA,,MAPS,MATPOOL,MATPOOLS,
MEDGE,MKLIST,MMCDB,MPT,MPTS, ,OINT,PCDB,PCDBS,PCOMPTS,PELSETS,
POSTCDB,
,PVAL,PVT,PVTBC,PVTS,
SPLINE,SPSEL,TABDEQ,TABEVP,TABEVS,
,SCSTM,SILS,SLIST,SLT,
,TRX,
,VGFS,
VGQ,VIEWTB,XYCDB,XYCDBS,YG,MPJN2O,MPJSFN2O,AEMPCOMP,AEMONPT,SAEMPRK,
STRUCOMP,MONITOR,SAERG0,AEDBSTDX,UXVST,PGVST0,,,,,,XSOP2DIR,,,
GEOM1QS,GEOM4QS,SELIST,PVT0,DMONPTA,DMONPTS,SDSRG0,SDARK,PVPERQ,
DTIS,DTINDXS,PBRMSD,PBRMS,MP1,MPD1,MP3,STRPLAB,EDTS,YMU,,,,/
$..OUTPUT DATA BLOCKS:
,
B2DD,B2MG,B2SF,
,AQG,AUA,AUG,
,BDICT,BELM,
BLAMA1,BMG,BPHA,BSF,BUG,
,
,BGPDTS,BGPDT,BHH,
,CB2DD,
,BLAMA,
CK2DD,CLAMA,CMDD,CMLAMA,CMPHA,CMPHO,CPHD,CPHH,CPHP,
CRJ,CRX,
,D1JK,
DITID,
,DLT,ECTS,EPSSEDSN,
,EST,
KFS,KHH,
LAJJ,
,GPECT,
,KMG,KSF,KSS,
,LAMA,LAMA1,LAMAF,LAMAS,LLL,
M2MG,M2SF,MAR,
,
,
,MJJ,
,MSF,MTRAK,
, , ,PDF,PDT,PDTDS,PG, ,PHA,
PHFA,PHG,
,MDICT,MEA,MELM,MHH,
,MMG, ,
,K4MG,K4SF,
,KELM,
LPHD,LPHH,LPHP, ,
,FOL,FOL1,FPHH,FRL,
,KDICT,
,DFFDNF,
,GM,GOQ,GOT,
,K2SF,
,FLAMA,
K2DD,K2MG,
,DAR,
,PHDH,PHF,
,PHQG,PHSA,PJ,
,PNLH,PPF,PPF1,PPT,PPTDS,PP1DS,PSF,PSF1,PSS,PST,
,PSTDS,PTELEM,QG,
,QMG,QMPF,QMPT,QPF,QPT,QR,
,UAJJ,
ULF,
,UDF,UG,
,ULTDS,UOO,UPF,UPT,
,
,
, ,
,
,TOL,TOL1,TOL2,TR,
,,UHF,UHT,UHTDS,UL,
,
VAFS,VELEM,YPF1,VGFD,VPHFS,WKK,WSKJ,
,USET,USETD,
,
,YS,YPO ,
, ,,,,,,,,,,,,,,,,,,MDPHIQ,MDGOT,MDGOQ,MDVFT,MDMAP,
MDGRDRM,MP2SLAB,MP2ST,MP2UGCP,MP3INT,MP3LAB,MP3GPF,
MP2A,MP3A,MP2SA,MP3SA,S2A,S3A,SDSA,,,,THETAM/
AERO/ADJFLG/AERTYP/ALTRED/APP/AUNITS/AUTOSPC/BUCKCC/CNVFLG/TRUE/
CYCLIC/DCEIGCC/DESCYCLE/DESEIG/DESMAX/DFRQCC/DFRQDSA/DFRSPCF/DMRESD/
DROPT/DROPTDS/DSTSPCF/DVRGCC/DTRSPCF/EBIS/ERROR/EXTERSE/FEAOPT/
FIXEDB/FLUIDSE0/FLUTCC/FSCOUP/G/GUSTAERO/HFREQ/IKBAR/IMACHNO/INREL/
IQ/KDAMP/ENFMETH/LASTSEID/LFREQ/LMODES/LUSETS/MCEIGCC/MFRQCC/
MFRQDSA/MODACC/MODECC/MTRNDSA/MTRNCC/NASOUT/NK/NLHEAT/NOPH1/NOPH2/
NOSEDV/OPTIMIZE/PEXIST/PSLOAD/RGSENS/RSONLY/SAERCC/SAERODSA/SEKR/
SELG/SELR/SEMG/SEMR/SKPAMG/SKPAMP/SOLTYP/STATCC/STATDSA/
$..I/O PARAMETERS:
S,ADPTEXIT/S,ADPTINDX/S,BOV/S,BMETH/S,CARDNO/S,FREQDEP/
S,FS/S,LUSET/S,METHF/S,MDTRKFLG/S,MODETRAK/S,NMSOL/S,NORSET/
S,NOSASET/S,NSOL/S,PFILE/S,PVALID/S,STATSUB/S,SUPORT/0/DELTAB $
alter 'l fea'(3),''
IF ( NOSEDV>-1 AND NOPALOAD>-1 ) CALL FEA,
$.............INPUT DATA BLOCKS:
ABE,ACPT,,AEBGPDTS,AECOMP,AERO,AEUSETS,
, ,BGPDTVU,CASADJ,CASECC,
CASEDS,CASEM,CASERS,CASDSN,CASDSN,CASEXX,CONTROL,CSTMA,CSTMS,
DEQATN,DEQIND,DFFDV,DIT,DITS,DMIS,DMINDXS,DRG,DRSTBL,
DYNAMIC,DYNAMICS,ECTAS,EDOM,EDT,EHT,EHTA,ELEMVOL,
EMAP,EPT,EPTA,EPTS,EQEXIN,EQEXINS,ETT,EXTDB,FPA,FPG,FORCE,
GDGK0,GDKSK,GDNTAB,GEOM1,GEOM1QX,GEOM1S,GEOM2,GEOM2S,GEOM3,GEOM3S,
GEOM4,GEOM4S,GPDTS,GPGK0,GPKSK,GPLS,GPSNTS,,INDTA,LCDVEC,MAPS,,,
MEDGE,MKLIST,MMCDB,MPT,MPTS,MXOMEG,OINT,PCDB,PCDBS,PCOMPTS,PELSETS,
PMA,POSTCDB,PTGA,PVAL,PVT,PVTBC,PVTS,,R1TABR,SCSTM,SILS,SLIST,SLT,
SPLINE,SPSEL,TABDEQ,TABEVP,TABEVS,TPG,TRX,UFOO,UG1PVT,
,UTOO,
VGFS,VGQ,VIEWTB,XYCDB,XYCDBS, ,MPJN2O,MPJSFN2O,AEMPCOMP,AEMONPT,
SAEMPRK,STRUCOMP,MONITOR,SAERG0,AEDBSTDX,UXVST,PGVST0,ADBINDX,
ADBUXV,ADBWJV,ADBFJV0,ADBQKV0,XSOP2DIR,CASEDM,LVTABI,
GEOM1QS,GEOM4QS,SELIST,PVT0,DMONPTA,DMONPTS,SDSRG0,SDARK,PVPERQ,,,
PBRMSD,PBRMS,MP1,MPD1,MP3,STRPLAB,EDTS,YMU,XINIT,DVPTAB,,/
$.............OUTPUT DATA BLOCKS:
,AEQGDKA,AEQGDKL,
B2DD,B2MG,B2SF,
,AQG,AUA,AUG,
,BDICT,BELM,
,BGPDTS,BGPDT,BHH,
BLAMA1,BMG,BPHA,BSF,BUG,CBDD,CB2DD,CKDD,
CK2DD,CLAMA,CMDD,CMLAMA,CMPHA,CMPHO,CPHD,CPHH,CPHP,
CRJ,CRX,
,D1JK,
,DAR,DELS,DELX,DFFDNF,
,BLAMA,
DITID,
,DLT,ECTS,EPSSE,
,EST,
GDAK,
,FLAMA,
,GDKL,
,GM,GOQ,GOT,GPAK,GPECT, GPGK,GPLK,IUXLR,
K2DD,K2MG,KZRR,K2SF,
,
,KALV,KAZR,KDICT,
KFS,KHH,
,K4MG,K4SF,
,KELM,
,KLL,KMG,KSF,KSS,L2RR,
LAJJ,
,LAMA,LAMA1,LAMAF,LAMAS,LLL,
LPHD,LPHH,LPHP,
,LSALL,
M2MG,M2SF,MAR,
,
,FOL,FOL1,FPHH,FRL,
,MDICT,MEA,MELM,MHH,
,MMG, ,
,MIRR,MJJ,
,MSF,MTRAK,
,PA,PD,PDF,PDT,PDTDS,PG, ,PHA,
PHFA,PHG,
,PHDH,PHF,
,PHILZ,PHQG,PHSA,PJ,
PL,PLR,PNLH,PPF,PPF1,PPT,PPTDS,
PST1DS,PSTDS,PTELEM,QG,
,QMG,QMPF,QMPT,QPF,QPT,QR,
U2RR,UAJJ,
ULF,
,UDF,UG,
,PSF,PSF1,PSS,PST,
,
,
,
,
,QKKS,
,TOL,TOL1,TOL2,TR,
,,UHF,UHT,UHTDS,UL,
,ULTDS,UOO,UPF,UPT,URLR,USALL,USET,USETD,
VAFS,VELEM,
,VGFD,VPHFS,WKK,WSKJ,
,XTMADJ,YS,
SAERG ,SAERA,SAERL, , ,PLVST,AEDBUXV,

MPAERV,MPSERV,MPSIRX, PRBDOFS,AEDBINDX,AERRV,AEURV,
UERGV,UEUGV,UXDIFV,WQKV,,MDPHIQ,MDGOT,MDGOQ,MDVFT,MDMAP,
MDGRDRM,MP2SLAB,MP2ST,MP2UGCP,MP3INT,MP3LAB,MP3GPF,
MP2A,MP3A,MP2SA,MP3SA,S2A,S3A,SDSA,SDSRA,SDSRL,VGFDT,THETAM/
AERO/ADJFLG/AERTYP/ALTRED/APP/AUNITS/AUTOSPC/BUCKCC/CNVFLG/FALSE/
CYCLIC/DCEIGCC/DESCYCLE/DESEIG/DESMAX/DFRQCC/DFRQDSA/DFRSPCF/DMRESD/
DROPT/DROPTDS/DSTSPCF/DVRGCC/DTRSPCF/EBIS/ERROR/EXTERSE/
'SENSITIVITY'/FIXEDB/FLUIDSE0/FLUTCC/FSCOUP/G/GUSTAERO/HFREQ/IKBAR/
IMACHNO/INREL/IQ/KDAMP/ENFMETH/LASTSEID/LFREQ/LMODES/LUSETS/MCEIGCC/
MFRQCC/MFRQDSA/MODACC/MODECC/DOMTRAN/MTRNCC/NASOUT/NK/NLHEAT/NOPH1/
NOPH2/NOSEDV/OPTIMIZE/PEXIST/PSLOAD/RGSENS/RSONLY/SAERCC/DOSAERO/
SEKR/SELG/SELR/SEMG/SEMR/SKPAMG/SKPAMP/SOLTYP/STATCC/DOSTATIC/
$..I/O PARAMETERS:
S,ADPTEXIT/S,ADPTINDX/S,BOV/S,BMETH/S,CARDNO/S,FREQDEP/
S,FS/S,LUSET/S,METHF/S,MDTRKFLG/S,MODETRAK/S,NMSOL/
S,NORSET/S,NOSASET/S,NSOL/S,PFILE/S,PVALID/S,STATSUB/
S,SUPORT/NNDFRQ/DELTAB $
$
1-74563841
ce
2009.0.0 (MD R4)
SOL 400 - Fails in in SDR2 after divergen
When a divergent condition is detected, SOL 400 always packs the final
iteration resuts for output and post-processing before leaving the NLSOLV
module. However, in some cases, such as when a job fails because of material
divergence, it may leave NLSOLV without saving all required data. In this
case, the job will fail later in the SDR2 module. .
1-74623771
MDR3 - BCTABLE - Segmentation Error in SOL700 ...
SOL 700 may fail with a segmentation error in dytran-lsdyna or may hang on
other systems.
Avoidance: Modifying the BCTABLE from 3 pairs instead of 6 allowed the job to
run.
1-74676639
(LNNRIGL)
2009.0.0 (MD R4)
ACMS - EIGR, EIGRL - SFM 3008, SFM 7340
It has been observed in an ACMS eigenvalue analysis with high modal density
and a small F2 value specified on the EIGR entry that the job failed with the
following misleading error messages:
SYSTEM FATAL MESSAGE 7340 (LNNRIGL)
UNKNOWN INTERNAL ERROR OCCURRED.
SYSTEMM FATAL MESSAGE 30008 (UTMCOR)
MODULE - MDENZO
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ENZ02
PROGRAMMER INFORMATION: LOCATION KEY = READ IN PHQ
0 FATAL ERROR
Avoidance: The avoidance is to add the following parameter to your input file
param,ifzero,x
where "x" is lower than min(1.0,F2).
where x is a small value like 0.1. X must be less than F2.
1-74887341
2009.0.0 (MD R4)
Optimization - D/MFREQ job with PARAM,OPT
EXIT,2 may print asterisk for FREQ/TIME of DRESP2

SOL 200 DFREQ or MFREQ job with PARAM,OPTEXIT,2 may print asterisk for
FREQ/TIME of DRESP2. DRESP3 has the same problem.
1-74910381
2009.0.0 (MD R4)
Optimization/Aeroelastic Flutter Analysis
- Traceback in FA1 module on Windows 32 only
The tpl test cpmopt.dat will fail with a traceback in the fa1 module in the
Windows 32 MD R3 Nastran release.
Avoidance: Run on another platform or version.
1-74935310
2008.0.0 (MD R3)
7 (DOM9), ILLEGAL INPUT TO SUBROUTINE ADS9P4D
A model with a large number of design variables and constraints may fail with
the message:
ILLEGAL INPUT TO SUBROUTINE ADS9P4D
Avoidance: Use the DOT optimizer instead. This can be selected by specifying
OPTCOD DOT on the DOPTPRM entry.
1-74941232
SOL 700 - DYPARAM,VELMAX,,NO/YES does not work as documented
In SOL 700 the options YES/NO on the DYPARAM entry are not working in MD R3.
Only the value for VELMAX will work properly.
1-74961191
1 in DSAD8
2009.0.0 (MD R4)
SOL 200 jobs with multiple subcases defining multiple frequency sets but a
single boundary condition may fail with USER FATAL MESSAGE 3001 in DSAD8.
Avoidance: Applying a dummy SPC set avoids the error at the cost of
performing an additional eigenvalue analysis.
1-75044221
2009.0.0 (MD R4)
dule on SGI Irix
Adaptivity - HADAPT - Bus Error in MBG mo
Looks like the compiler optimization error on routine mbg_construct.F.

Fixed in tier1 system. (7/3/08 jou)
Jobs with h-adaptivity (HADAPT) on sgi irix will fail in the MBG module with
the message:
Job aborting...
Avoidance: Run the analysis with mode=i8 or run on another machine.
1-75215571
FP1D)
2009.0.0 (MD R4)
SOL 400 - NLSTRESS(NLOUT=10) - UFM 608 (I
In SOL 400, an (NLOUT=nlout id) request under a STEP Case Control Command will
incorrectly lead to:
THE SET ID SPECIFIED ON THE ABOVE CARD MUST BE DEFINED PRIOR TO THIS CARD.
An example of this input is:

STEP 1
NLSTRESS(NLOUT=10)=ALL
1-75237351
2009.0.0 (MD R4)
- Poor Message, SFM 3001, Missing EDOM in Module DOPR1
In SOL 200, the DOPR1 module can issue SYSTEM FATAL MESSAGE 3001 complaining
about a missing EDOM datablock when the actual problem is a missing a SET1 when
the DOPTPRM parameter P2RSET specifies a SET1 entry that does not exist.
Avoidance: If a message about a missing EDOM appears, check if the P2RSET
parameter is specified and, if so, that the associated SET1 exists.
1-75374331
2009.0.0 (MD R4)
External Superlements - EXTSEOUT usage wi
thout any A-set, B-set or C-set - SFM 3012, SFM 3200
Writing of the DMIGPCH or EXTBULK info in Sol 103 EXTSEOUT using ASMBULK=MANQ,
under free-free conditions (no Aset, no Bset), results in the following fatal
messages:
a) With DISP data recovery: BIOMSG ERROR 3012 (QOPEN), after resvec eigenvalue
solution.
b) With out DISP: SFM 3200 Logic error 5 in BDYINC, after resvec eigenvalue
solution.
Notes:
1) Works fine w/ DMIGOP2 no EXTBULK
2) Works fine w/ Bset's added
3) Same errors w/ manual SPOINT/Qsets vs AUTOQSET
4) Same errors w/ versions 2005.5.2, 2007.1.1, 2008.0.0
5) Similar errors (BIOMSG 3021 vs 3012) w/ DMIGOP2 & EXTBULK (2nd attachment)
Avoidance: Use DMIGOP2 without EXTBULK.
1-75553921
2009.0.0 (MD R4)
not effective.
SOL 700 - DYPARAM,LSDYNA,BINARY,D3PLOT is
DYPARAM,LSDYNA,BINARY,D3PLOT to control output time interval isn't effective in

SOL 700.
Avoidance: Use PARAM,DYDTOUT.
1-75641588
2007.0.0 (MD R2)
cases in sol159 may fail in TAHT
Nonlinear Heat Transfer - Large # of load
A SOL 159 with a large number of load cases may fail in TAHT.
SJF's comments: this is a user error cause by a duplicated TLOAD1 ID.
We cannot trapped this error because this is pass ifp already.
1-75737851
2009.0.0 (MD R4)
, 112, 145, 146, 200 - Wrong Answers
Dynamics - viscous damping, SOLs 110, 111
If a model contains a very small number of elements with viscous damping such
that the density of the reduced damping matrix is less than .01% then the
viscous damping will be ignored resulting in wrong answers.

compile atbc
alter 'PARAML NZBV'
PARAML NZBV//'null'//S,N,fullnzbv $
IF ( DENSbV=10000 and fullnzbv<1 ) densbv=0 $
1-75786151
2009.0.0 (MD R4)
Frequency Response - Null loads leads to
a "FATAL ERROR" in the DPD module with no other information
A SOL 108 job with null loads and unreferenced LSEQ and DAREA entries
terminates with a cryptic "FATAL MESSAGE" in the DPD module without giving any
explanation for the failure.
1-75807472
(FILPS2)
2009.0.0 (MD R4)
Topography Optimization - RBE2 - SFM 4276
If RBE2 (or other rigid body elements) are used in topography optimization the
following fatal message is issued:
*** SYSTEM FATAL MESSAGE 4276 (FILPS2)
ERROR CODE
1044 PID= 0 *** USER INFORMATION MESSAGE 4276 (FILPS2)
Avoidance: Renumber all the grid IDs in the model so that they are consecutive
beginning with 1. Renumber the grids associated with the RBE2s such that they
are larger than the total number of grid points in the model. Else, SET
SKIP=NONE but use DGSET/SET1 on the bulk data entry BEADVAR to remove the
grids associated BC and.or LOADS from the desgin space.
1-75809061
2009.0.0 (MD R4)
Optimization/Design Sensitivity - MODTRA
K can change answers even when no mode tracking occurs
It has been found that eigenvalues are recomputed by the mode tracking module
even when the modes have not shifted. Since this is done in single precision,
the new eigenvalues can be slightly different, which can lead to different
final answers in a SOL 200 design task.
Avoidance: Don't specify mode tracking if it is known that it is not
necessary. Alternatively, specifying DRESP1 type FREQ rather than EIGEN should
avoid the problem since eigenfrequencies are not recomputed.
1-75956005
2009.0.0 (MD R4)
Equation 5-9 is incorrect
Documentation/Linear Static User Guide -
In the Linear Static Analysis User Guide, Section 5.6 equation 5-9, the terms
G12 and G23 as well as Delta are incorrect.
G12=(v23 + v31*v23) / (E2*E3*D) wrong, first v23 should be v21
G23=(v32 + v12*v31) / (E1*E3*D) wrong, first v12 should be v23
Delta=(1-v12v21-v23v32-v31v13-2v21v32v13) / (E1*E3*E3) wrong, should be E1E2E3
in denominator
The key are the relationships below v12 is NOT the same as v21 you can
convert between the 2 correct forms below.
v12E2=v21E1
v23E3=v32E2
v31E1=v13E3
These are the correct formulations, according to Schaffer's Nastran Primer, 1st
edition and Jones (Mechanics of Composite Materials, Robert M. Jones, Professor
of Engineering Science and Mechanics, Virginia Polytechnic, Blacksburg, VA,
Copyright 1975, Section 2.3 Engineering Constants for Orthotropic Materials,
Page 37).
G12=(v21 + v31*v23) / (E2*E3*D) = (v12 + v32*v13) / (E1*E3*D)
G23=(v32 + v23*v31) / (E1*E3*D) = (v23 + v21*v13) / (E1*E2*D)
Delta=(1-v12v21-v23v32-v31v13-2v21v32v13) / (E1*E2*E3)
1-75989361
2009.0.0 (MD R4)
Eigenvalue Analysis - PARAM,ENFMETH not h
onored in RESVEC calculations in SOL 103
The MD R3 Quick Reference Guide indicates that PARAM,ENFMETH,REL is the
default. This is honored in the SOL 111 RESVEC calculations, but in SOL 103,
the calculations are performed as if ABS is the default.
This may lead to
different residual vectors being calculated in SOL 111 vs 103 which in turn
leads to slightly different eigenvalues being caclulated.
Avoidance: The work around for MDR3/2008.0 is to insert the attached DMAP
(ask MSC Support for the attachment).
1-76308076
2008.0.1
ause msmpi.dll not found
SOL 700 - Application Failed to Start bec
The SOL 700 dytran-lsdyna executable will fail on Windows x8664 with the
message "The application has failed to start because msmpi.dll was not found".
This dll was intentionally left off of the delivery because it was unclear
whether MSC had been granted the right to deliver it by Microsoft. Microsoft
has granted this right and the delivery has been updated and is labeled MD R3b.
Alternatively, existing installations may be updated by downloading only the
missing dll from
http://www.mscsoftware.com/support/software_updates/
and copying to:
installdir:\MSC.Software\MD_Nastran\md2008\dyna
1-76504911
Documentation/QRG - BCPARA NLGLUE contact parameter
In the MD QRG, the BCPARA entry refers to the NGLUE paramter and this should be
the NLGLUE paramter.
1-76508424
2008.0.1
a supported platform
Installation - Windows server 2003 is not
Installation of MSC.Nastran 2008r1 on 32 bit Windows Server 2003 will fail and
indicte that this is not a supported platform. The MD R3 Installation was
corrected with the MD R3b release.
Avoidance: Install on any other windows os and then copy/drag-drop the folder
to the Windows 2003 32-bit server machine.
1-76613897
d Motion.
Documentation/Basic Dynamics User Guide - Section 7.5 Enforce
In the electronic copy of Basic Dynamics User Guide the label on Figure 7.7
should read Input Displacement Time History
and the label Figure 7-8 should
read Response for Enforced Displacement (With the Rigid-Body Mode)
1-76658371
2009.0.0 (MD R4)
o SPCs may lead to SFM 4276 in FRLG
Superelements - MPC, Rigid Elements but N
A frequency response SE assembly job may fail in the FRLG module if there are
MPCs and/or rigid elements, but no SPC and ASET data. Whether it fails or not
depends upon the particular method it chooses for internal multiply/add
operations in the FRLG module and is thus highly machine dependent.
FRLG
36 SCR 301
43
138 2 2
130
43
130
133
0 *8**
0.
STATUS =
0
ERROR CODE
3012 PID= 0
266 9.42198D-01
1-76665401
, FILE INDEX =
Documentation - Missing TPL Include File.
The files delivered with the Windows Documentation download do not match the
files delivered with the Nastran installation.
For Nastran, the unwanted references to TPLDIR1 and clever5.alt are removed
prior to delivery. I am not sure who creates the
Windows Documentation dleivery so I will reassign to Don Truit and he can
reassign as necessary. (cdp 09/15/08)
Some MD User's Guide example problems contain the following include statement
and the file does not exit.
include 'TPLDIR1:clever5.alt'
Avoidance This specific include statement may be removed. .
1-76735127
2009.0.0 (MD R4)
iles - wrong answers
External Superelements - Unattached op2 f
When assembling external superelement created with dmigop2 and the unit numbers
on the ASSIGN INPUTT2 statements do not correspond to the unit numbers
specified on the SEBULK entry and there is no BEGIN SUPER section specified (or
no included pch file from the creation run) for the externals, then the
external superelements are ignored, no message is issued and the answers will
be wrong.
Avoidance: None.
1-76752521
data entries
SOL 700 - UFM 300 (RCARD) referencing LOAD nonexistent bulk
The f06 file shows a series of the following error messages and then stops:
POSSIBLE ERROR IN EXPONENT.
. 1 .. 2 .. 3 .. 4 .. 5 ..
.. 10 .
LOAD
99****** 1.0
1.0 99000000
However there is no LOAD entry in the input deck.
6 ..
7 ..
8 ..
1-76778601
2009.0.0 (MD R4)
swers for free-free structure
Dynamic Analysis - EIGRL, V1>0 - Wrong An
Incorrect infinite (massless) residual vector modes may be generated for

unconstrained structures when V1>0. on the EIGRL entry.
Avoidance: Set V1 on the EIGRL entry to blank or 0.0. Altenatively use LFREQ
or MODESELECT to remove the residual vector modes from the dynamic solution.
1-76893031
DocumentationQRG - QRG, BCTABLE - Missing Description
In MD R3, the discription of QRG BCTABLE for BGST contains the descriptiion for
BGSN and vice-versa. The documentation currently reads:
BGST Maximum normal stress for breaking glue. See Remark 23. (Real,Default =
0.0)
BGSN Maximum tangential stress for breaking glue. See Remark 23. (Real,
Default= 0.0)
and it should be:
BGST Maximum tangential stress for breaking glue. See Remark 23. (Real,
Default= 0.0)
BGSN Maximum normal stress for breaking glue. See Remark 23. (Real,Default =
0.0)
1-76943618
Element Strain Energy - Incorrect frequency label
When requesting ESE output in a normal modes analysis, the frequency label for
some of the modes for ESE are incorrectly labelled as "0.000000E+00". The
eigenvalue is correct and the corresponding ESE values are also correct.
EIGENVALUE = 7.772340E+04
CYCLES = 0.000000E+00
E L E M E N T
1-76962371
S T R A I N
E N E R G I E S
SOL 600 - Implicit creep analysis may give wrong results
SOL 600 with a perfect plastic material with yield stress 165 is given, however
equivalent stresses (von Mises) of increments exceeds yield stress. This is not
correct.
1-77037052
Documentation/QRG - PARAM,DSO not documented
Documentation for PARAM,DSO is missing from the QRG. PARAM DSO controls which
DBset NDDL datablocks for design sensitivity and optimization are assigned to
DBALL or to other datasets.
Suggested QRG addition:
PARAM, DSO
Default = value of PARAM,DBALL
See DBALL.
Also, the DBALL parameter description should be updated to include DSO
1-77135941
2009.0.0 (MD R4)
Aeroelastic Analysis - Multiple GUST Load
subcases with MONPNT may fail with SFM 6144
A multiple subcase run with GUST loads in SOL 146 including MONPNT may fail
with message below in version 2007.

SPECIFICALLY:
The number of columns in PGR3T is not equal to the number of rows in the column
partitioning vector D
PGR3T : Rows=
36 by Cols=
297
D
: Rows=
891
Avoidance: 1. Use only single subcase or,
2. Use the following alter:
compile mpseaero
alter 'Structural load' $
TYPE PARM,,I,N,QUIT,QUITX $
FILE PGRFA=APPEND/WJ=APPEND/QRJK=APPEND/PPA=APPEND/ $
FILE AGRFA=APPEND/WJX=APPEND/QRJKX=APPEND/PPXA=APPEND/ $
PARAML FOL//'TRAILER'/1/S,N,NFREQ $
alter 'gust
be FIVE
case','' $ The number of spaces between "gust" and "case" must

PARAML
CASES//'TRAILER'/1/S,N,NREC $
IF ( NREC=1 ) THEN $
GUST
CASES,DLT,FRL,DIT,QRJL,,,ACPT,CSTMA,,,,,,/
PGRF,WJ,QRJK,PP/
ELSE $
$ TEMPORARY UNTIL GUST CAN HANDLE MULTIPLE SUBCASES
DO WHILE ( QUIT>=0 ) $
CASE
CASES,/CASE1/'TRAN'/S,N,QUIT $
GUST
CASES,DLT,FRL,DIT,QRJL,,,ACPT,CSTMA,,,,,,/
PGRFA,WJ,QRJK,PPA/
IF ( QUIT=2 ) THEN $
$ FIRST SUBCASE
EQUIVX
PGRFA/PGRF/-1 $
EQUIVX
PPA/PP/-1 $
ELSE $
$ SECOND AND SUBSEQUENT SUBCASES
APPEND
PGRF,PGRFA/PGRFB/1//NFREQ $
EQUIVX
PGRFB/PGRF/-1 $
APPEND
PP,PPA/PPB/1//NFREQ $
EQUIVX
PPB/PP/-1 $
ENDIF $ QUIT=2
ENDDO $
ENDIF $ NREC=1
alter 'gust
must be FIVE
case'(2),'' $ The number of spaces between "gust" and "case"

PARAML
CASES//'TRAILER'/1/S,N,NRECX $
IF ( NRECX=1 ) THEN $
GUST
CASES,DLT,FRL,DIT,QARJL,,,ACPT,CSTMA,,,,,,/
AGRF,WJX,QRJKX,PPX/
ELSE $
$ TEMPORARY UNTIL GUST CAN HANDLE MULTIPLE SUBCASES
DO WHILE ( QUITX>=0 ) $
CASE
CASES,/CASE1X/'TRAN'/S,N,QUITX $
GUST
CASES,DLT,FRL,DIT,QARJL,,,ACPT,CSTMA,,,,,,/
AGRFA,WJX,QRJKX,PPXA/
IF ( QUITX=2 ) THEN $
$ FIRST SUBCASE
EQUIVX
AGRFA/AGRF/-1 $
EQUIVX
PPXA/PPX/-1 $
ELSE $
$ SECOND AND SUBSEQUENT SUBCASES
APPEND
AGRF,AGRFA/AGRFB/1//NFREQ $
EQUIVX
AGRFB/AGRF/-1 $
APPEND
PPX,PPXA/PPXB/1//NFREQ $
EQUIVX
PPXB/PPX/-1 $
ENDIF $ QUITX=2
ENDDO $
ENDIF $ NRECX=1
1-77270183
2009.0.0 (MD R4)
with RESTART - Inefficient Restarts
Component Modes - ACMS, ASETi (or OMITi)
The component modes may be recomputed in a restart if the cold start employed
ACMS to compute the component modes.
Avoidance: In the restart run change the RESTART FMS statement to DBLOCATE for
a read-only restart and insert PARAM,SERST,SEMI into the Case Control.
1-77292677
2009.0.0 (MD R4)
Superelements - Shell normals cause diffe
rent answers in superelement vs non-superelement models
Part superelements will use unique grid point normals at the boundaries
regardless of the setting of param,snorm. This may lead to different answers
for superelement versus non-superelement models.
1-77498351
2009.0.0 (MD R4)
Documentation/Topology UG - Figure 5-48 i
n Topology Optimization User Guide is wrong
The figure 5-48 in Topology User Guide should show the plate with load and
boundary condition, but it shows the optimized shape related to another deck.
1-77566461
2009.0.0 (MD R4)
SOL 400 - Virtual Cract, VCCT = SFM 6352
The following fatal message is issued by IFP when there're more than one
continuation lines of grid IDs specified on the VCCT bulk data entry.
*** USER WARNING MESSAGE 4124 (IFS3P)
THE SPCADD OR MPCADD UNION CONSISTS OF A SINGLE SET.
*** SYSTEM FATAL MESSAGE 6352 (IXVCCT)
LOGIC ERROR: KERROR=9300.
1-77623079
Documentation/QRG - GROUNDCHECK - Missing Remark, Output Coor
dinate for Forces
The description of the GROUNDCHECK case control command does not specify the
output coordinate system for the forces output by the request. The SPCFORCE
case control command description shows Remark 6 specifying the displacement
coordinate system is used to define the component directions. The GROUNDCHECK
case control command needs a remark similar to Remark 6 of the SPCFORCE request
since these forces are also output relative to the displacement coordinate
system.
1-77805830
Rotor Dynamics - Case Control Command RGYRO=NO - UFM 6278
The Quick Reference Guide description of the RGYRO case control command states:
"Setting RGYRO to NO will deactivate gyroscopic effects in all solutions."
However, a SOL 109 or SOL 129 run will proceed and include the rotordynamic
gyroscopic effects when RGYRO=NO is used. SOL 108 yields USER FATAL MESSAGE
6278 indicating that RGYRO=538988366 was not found when RGYRO=NO is included in
the case control section of the input file.
Avoidance: Remove the RGYRO case control command from the input file.
1-78048375
Documentation/QRG - GROUNDCHECK Documentation Error
Remark 2 under the documentation of the GROUNDCHECK case control command in

the Quick Reference Guide indicates the dofs as being "N+AUTOSPC". It should
be N-AUTOSPC because the rows and columns are zeroed out. Use of the logical
minus (-) is more consistent with the set notation. Both the command format in
the QRG and Remark 2 use the + notation and logically it is a minus (set
elimination) operation.
1-78146078
2009.0.0 (MD R4)
Mass - CONM2, NSMLi, CORDi - UFM 2025, Un
defined Coordinate System

A model that contains CONM2 entries that reference a non-basic coordinate
system and NLMLi entries fails with UFM 2025 in the GP2 module as shown below:
UNDEFINED COORDINATE SYSTEM 2260303 IS REFERENCED BY ELEMENT CONM2
ID=2264000.
The referenced coordinate does exist in the input data. This error is caused
by a combination of NSMLi and CONMi with non-zero CID and was introduced in
V2008.
compile ifps
alter ' gp2 ',''
GP1
IGEOM1Q,IGEOM2,Igeom3,,,,Idynamic,casexx,/
zGPL,zEQEXIN,zGPDT,zCSTM,zBGPDT,zSIL,,,,/
S,N,LUSET/0/0 $
GP2
iGEOM2,zEQEXIN,iEPT,,,zbgpdt,zcstm,impt/ECT, $
1-78529481
SOL 400 - CWELD, ANALYSIS=LNSTAT - Wrong Answers
The input "rigid=linear" in sol400 currently causes the cwelds to be ignored,

noy the fact that "analysis-lnstatic". A woraround in sol400 is not to use
"rigid=linear". (Ap)
In SOL 400 with analysis=lnstat, MD R3 Nastran will ignore the cweld elements.
This is evident by the fact that element forces will be zero.
Avoidance: Run the linear static analysis in SOL 101.
1-78764211
for EXTSEOUT
External Superelements - Changed format of the MATOP4 option
The format has been changed between Version 2007 and Version 2008 for the
MATOP4 option on the EXTSEOUT command. It has been changed from the non-sparse
format to the sparse format. This was done via Quality 1-56154005 and was
documented in the 2008 Release Guide. The sparse OUTPUT4 format option is now
used for EXTSEOUT (MATRIXOP4=unit) Case Control command and will result in
significant disk space reduction of the resulting op4 file. However, this
creates a problem for users that work with the OP4 file outside of NASTRAN and
need the format to be the same as before. An option to obtain the old format
should have been made available.
Avoidance:
Insert the following ALTER to obtain the non-sparse format:
$ ALTER to switch the output4 matrices from EXTSEOUT MATOP4

$ back to pre-v2008 format (non-sparse format)
MALTER 'ELSE IF ( EXTMEDIA=\'MATRIXOP\' ) THEN', 'OP4UNIT=-OUTUNIT'
ELSE IF ( EXTMEDIA='MATRIXOP' ) THEN
OP4UNIT=OUTUNIT $
ENDALTER
1-78785121
2009.0.0 (MD R4)
DMAP - PARAML module - Wrong Answers
The PARAML module returns bad values under the trailer option when the input
data block is purged.
Avoidance: Always output the fifth parameter and check for its presence before
accepting the other output parameters. For example:
paraml db//'trailer'/1/s,n,ncol//s,n,nodb $
if ( nodb<0 ) ncol=0 $
1-78969247
Documentation/QRG - SESET - Incorrect Remark
Remark 3 under the Quick Reference Guid documentation for the SESET entry
indicates that SPOINTS are ignored. This remark should be changed or removed.
SPOINTS can be used and assigned to a superelement.
1-79018800
e
Rotor Dynamics - UNBALANC - Access Violation in NLTRD2 Modul
A rotordynamics analysis with UNBALANC and EPOINT entries executing SOL 129
encounters an access violation in the NLTRD2 module when NONLINEAR case control
command references a SET but no NOLINi or NLRGAP entries exist.
Avoidance: Remove the NONLINEAR case control command.
1-79124817
6
Documentation/QRG - Scaling/Selction of P2G vector in SOL 10
Remark 5 of the the QRG for the P2G case control command description is
incomplete and not accurate for using the P2G request within SOL 106. An
addition to the remark should be added as follows
For SOL 106 the P2G functions according to these comments
a. Only the first colum of a DMIG such as PAX where multiple columns are
present will be used
b. Each subcase may select a different DMIG with the P2G case control command.
For example:
SUBCASE 10
p2g=pax1
SUBCASE 20
p2g=pax2
SUBCASE 30
p2g=pax3
c. Parameter CP2 may be changed between subcases to scale the selected P2G DMIG
vector. For example:
p2g=pax
$
SUBCASE 10
param,cp2,1.0,0.0
SUBCASE 20
param,cp2,10.0,0.0
SUBCASE 30
param,cp2,100.0,0.0
or
SUBCASE 10
p2g=1.0*pax1
SUBCASE 20
p2g=10.0*pax1
SUBCASE 30
p2g=100.0*pax1
will accomplish the same scaling if the second setup is run on 2007.1 or later.
1-79811428
SOL 400- Corrupt XDB, SWM 6065 DBC, EC 23, GRIDBK, NLLF
Additional output requests in subsequent steps in SOL 400 as shown below will
result in a corrupt XDB File.
Example:
SUBCASE 1
STEP 1
NLPARM=1
LOAD = 1
STEP 2
NLPARM=2
LOAD = 2
DISPL=ALL
The following warning message will be printed to the f06 and the xdb file will
be corrupt.
OUTPUT LIST SYNCHRONIZATION PROBLEM FOR NLLF
VALUE =
POSITION =
0.
1.5000E+00,
Avoidance:
1) request the output in all STEPs
2) use OP2
3) use MASTER/DBALL
1-80134711
Installation - SuSE 10.2 - Nastran will not start, System out
put on submittal Prompt <81> mdnast200
If output similar to the following is printed when submitting Nastran on a SuSE
10.2 or higher system, then the system has an unsupported ksh.
Output:
Prompt <81> mdnast2008 JOB
MSC_BASE=/opt/msc
MSC_VERSD=md2008
MSC_ARCH=linux64
The problem is a result of an unsupported ksh ( ksh-93s-59.7 ). Theproblem can
be demonstrated in a small test case:
#! /bin/ksh
prod=md
[[ mdnast2009t1 = $prod[1-9][0-9]* ]] && echo Bad ksh
If "Bad ksh" is printed, then the ksh will not work.
Avoidance: Change the line in $MSC_BASE/bin/mdnast2008
Prompt <89> diff mdnast2008.org mdnast2008
485c485
< [[ $cmdname = $prod[1-9][0-9]* && -n $1 ]] && {
--> [[ $cmdname = ${prod}[1-9][0-9]* && -n $1 ]] && {
493c493
< [[ $cmdname = $prod[1-9][0-9]* ]] && {

--> [[ $cmdname = ${prod}[1-9][0-9]* ]] && {
1-80142500
Documentation/QRG - AXIC - H=0 Should be allowed
The documentation for AXIC entry indicates H must be greater than 0. A value
of 0 indicating that only results for the 0th harmonic are desired is allowed.
1-95056651
2008.0.4
rong Answers on Windows 32.
Aeroelastic Analysis - CAERO1, CAERO2 - W
The Windows 32 release of MD R3 Nastran and MSC.Nastran V2008 may produce wrong
answers or fail in AMG with a floating point exception error for subsonic
aerodynamics using the default value of quarticdlm=0 for doublet lattice
aerodynamics (CAERO1 and/or CAERO2 bulk data entries exist).
Avoidance: Set NASTRAN QUARTICDLM=1 in a system rc file to insure avoidance
for all runs. The quarticdlm =1 answers may be slightly different than the
quarticdlm=0 answers, but the quarticdlm=1 answers are considered to be more
accurate.
1-105794811
SOL 400 - BCONTACT, UNGLUE - Stress based contact separation
does not work in this example
If stress based contact separation is selected by specifying IBSEP on the
BCPARA entry, incorrect results may occur. In one example the contract
stresses were unexpectedly zero and no separation took place.
Avoidnace: Use force based seperation.
1-107539213
P
Parallel Processing - SYSTEM(107) - Traceback in READ with SM
The Windows 32 bit version of MD Nastran R3 (Version 2008.0.0 and 2008.0.1) may
fail in the READ module with a traceback when SMP parallel is selected by
setting SYSTEM(107) greater than 1.
Avoidance: Do not set SYSTEM(107) greater than 1.

Nastran Errors List

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Nastran Errors List

Загружено:

Авторское право:

Доступные форматы

MD Nastran/MSC.

Nastran Current Error List

Eigenvalue Analysis - CEAD, QRG - Unexpec

Complex eigenvalue analysis with

the inverse power method of eigenvalue

Miscellaneous - PUNCH - Incorrect Format

Grid Point Force - GPFDR - UFM 3008

Dynamic Response - TRD, TRD1, FRRD, FRR -

If the MGIV method of real eigenvalue extraction computes modes for

Aeroelastic Analysis - GI - Poor Accuracy

The linear splines used to connect structural and aerodynamic degrees of

Dynamic Response - VDR - No Output

If an OUTPUT(XYPLOT) command is in case control, but there are no other

Elements - QUAD4,TRIA3 - Wrong Answers

element centerline from the grid

Frequency Response Analysis - RANDOM - SW

If a non-existent point is referenced in an output request when there are

Grid Point Stress - Preface - UFM 603

DMAP - DIAG 4 - Addressing ERROR

Cyclic Symmetry - Restarts - Various

SET N = 0, residual only

Plotting - RF24D20, Superelement - Wrong

Cyclic Symmetry - CYCLIC2 - UFM 3005, UFM

Plotting - PLOT - SFM 4276

Miscellaneous - Preface - CPU Loop

Elements - PQUAD4 - UFM 2010

Superelements - SELA - Wrong Answers

Elements - PCOMP - Wrong Answers

For layered composite materials with an unsymmetric layup, the generated

Database - LOAD/UNLOAD - Wrong Answers

If a database is unloaded to a sequential file using the DBMGR //3

Matrix Methods - FBS, Method 2 - Wrong An

If a passive group appears within the first 20 columns of a matrix, some

Database - DBSTORE - DBM 288

Heat Transfer - HBDY - Wrong Answers

Elements - Midside Nodes - Wrong Answers

Dynamic Response - SDR3 - UFM 4605

Miscellaneous - Multiple Runs - ITRENT 11

Response Spectra - PARAM,RSPECTRA,0 - Wrong Answers

Matrix Methods - MPYAD - Overflow

Dynamic Response - XYPUNCH - Missing Outp

The PCHRESP parameter described on p. 4.3-23 (2/15/82) of the MSC/NASTRAN

Material Nonlinearity - SOL 66 - Wrong An

Transient Response - TRD1 - UFM 3050

If an IC card is selected in case control in SOL 31, which is illegal, the

Elements - EMG - EMGPOM

Database - DBSTORE - SFM 4167

The maximum number of database dictionary entries is influenced by the

Superelements - Documentation - Wrong Ans

sign. The second to last statement on

Material Nonlinearity - MID3 - Wrong Answ

Miscellaneous - 1VARY - UFM, CARD TO VARY

Matrix Routines - Method 3 - Various GINO

If Method 3 matrix multiplication is selected, and there is not sufficient

Elements - Punched Output - Extra Output

If output is requested in punched format, elements whose printed formats

Cyclic Symmetry - SOL 77 - Parameter Prin

If illegal loads are requested in buckling analysis using cyclic symmetry,

Grid Point Stress - Branched Surface - Wr

When requesting stresses for a surface with branches using geometric

Heat Transfer - CFTUBE - Wrong Answers

Database - DBMGR, DBSTORE - IO6600 F.E.

Aeroelastic Analysis - FA1 - Wrong Answer

The ATEIG subroutine for eigenvalue solution has a limit of 30 iterations.