MD Nastran/MSC.Nastran
Error List Update October 11, 2007
1-19390023 Documentation/QRG - CQUAD4 differential stiffness remark obsolete
Remark 6 for CQUAD4 should now read:
...\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-19689679 2007.1.0 Case Control - Scale Factor applied to P2G lead to 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 or the factors may be ignored.
1-19948040 Elements - PSHEAR with MAT1 and Nu=-1 gives traceback
If a PSHEAR entry references a MAT1 entry with a value nu=-1, the job will fail
with a traceback since formulation of the element contains the term (1+nu).
1-21553341 2007.1.0 Elements - CBEND, TEMP(INIT) - SFM 4276 with the traceback at SDR2
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 0x00000080 in procedure pthread_kill Offset 0x00000060 in procedure _p_raise Offset 0x00000030 in procedure raise Offset 0x0000005c in procedure tracbak_ Offset 0x000000d8 in procedure osexit_ Offset 0x00000168 in procedure nsexit_ Offset 0x00000310 in procedure pexit_ Offset 0x00003c84 in procedure gperr_ Offset 0x00000084 in procedure ginit_ Offset 0x00001470 in procedure ginoa_ Offset 0x00000960 in procedure getemp_ Offset 0x00000644 in procedure sqr2d_ Offset 0x00000648 in procedure s2ebrd_ Offset 0x000011ac in procedure sdr2e_ Offset 0x00002a60 in procedure sdr2d_ Offset 0x0000023c in procedure sdr2_ Offset 0x00000174 in procedure xsem13_ Offset 0x00000228 in procedure xsemdr_ Offset 0x0000005c in procedure nastmon_ Offset 0x00000a50 in procedure mainal --- End of call chain ---
1-22716666 2007.0.0 Installation - Windows Only, symbol=LM_NO_SNMP=1 missing from nast20051.rcf
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-23956243 2007.1.0 Fastener Elements - CFAST *** USER FATAL MESSAGE 7635 (MDG2ED)
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
Avoidance: There is no avoidance.
1-24287255 2007.0.1 Documentation/QRG - PARAM OMID is not supported in SOL 106
Parameter OMID is not supported in SOL 106 as indicated in Table 5-1 of the
PARAM section
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-34626031 2007.1.0 Parallel Processing - SYSTEM(107), PARALLEL -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 SOL 600 - CBUSH1D element causes SOL 600 to fail without any messages.
The CBUSH1D element causes SOL 600 to fail without any messages.
1-36316035 2007.0.0 Documentation/QRG - CQUAD4, CTRIA3 - Offsets, ZOFF
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-37202949 Documentation/QRG - MCFRACTION - UWM 300
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-37426759 2007.0.0 Parallel Processing/Frequency Response - Poor DMP Performance with multiple load cases 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 if ( procid=1 ) then $ 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-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-40643851 2007.0.1 SOL 700 - Initial velocity is incorrect if 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 1. 0. 0. 1 TIC 1 2 1 1.
CORD2R 1 2 0. 0. 0. 1. 0. 0.
.707107 .707107 0.
CORD2S 2 0. 0. 0. 0. 0. 1. 1. 0. 45.
1-41448459 2007.1.0 Single Point Constraints - AUTOSPC, INPUTT4 - 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-41585731 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-41885454 2007.0.0 SOL600 - PSHELL, CQUAD4 - Membrane only element incorrectly translated.
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-43440601 2007.0.0 Matrix Methods - DECOMP, Large Models - Signal 11, Overflow
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-46584431 2007.0.0 SOL 600 - Multiple subcase SPCD Incorrectly Translated
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-46739381 2007.0.0 Matrix Methods - Integer overflows in sparse 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-47446533 2007.0.0 Matrix Methods - DECOMP - signal number 10: bus error in Decomp
Default changes to system 219 may cause models that ran in previous versions to
fail in DECOMP module with the message:
Receiving signal number 10: Bus error 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-48629874 2007.0.0 Modal Participation Factors - PFMODE - SFM 4276 (PFCALC)
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.
*** SYSTEM FATAL MESSAGE 4276 (QOPEN) ERROR CODE 1044 PID= 0
*** USER INFORMATION MESSAGE 4276 (QOPEN)
THE DIAG 44 RELATED A NASTRAN DUMP IS SENT TO LOG FILE.
Traceback:
Offset 0x00000110 in procedure gtdens_ Offset 0x00000108 in procedure mpyad_ Offset 0x000002a4 in procedure mpyadk_ Offset 0x000022cc in procedure pfcalc_ Offset 0x000005ec in procedure xsem07_ Offset 0x00000190 in procedure xsemdr_ Offset 0x00000064 in procedure nastmon_ Offset 0x00000adc in procedure mainal --- End of call chain ---
1-49086447 2007.0.0 Docuementation: QRG Remark 12 for ASSIGN statement. The following limitation documented in remark 12 of the QRG for the ASSIGN statement was removed in V2005.5.
\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-49118561 2007.1.0 Utilities- Acounting does not work in MD Nastran (acct=yes)
Acounting does not work in MD Nastran (acct=yes). It does work in MSC.Nastran 2005r3.
1-49509805 2007.0.0 SSSALTER - glforce alter gives incorrect results
MSC.Nastran Version 2004 and 2005 versions of the glforce alter give incorrect
answers. In the previous versions KAA was called up with a type,db statement.
In 2004 and 2005 KAA is in the datablock list for the subroutine but not in the
called datablocks. This produces a null datablock and hence incorrect results.
1-49522526 Documentation/QRG - EPOINT documentation error
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.
In SOL 400 total strains need to be converted into True strains to be consistent with other nastran solutions.
1-49693111 2007.1.0 SOL 400 - CQUAD4 - Infinity von MIses stress output for SOL 400 QUAD4 models
The von Mises stresses for CQUAD4 elements in SOL 400 may be output as NaN.
1-50014537 2007.1.0 Multipoint Constraints - Missing UFM 2101 when UWM 2047 is issued
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-50098347 Documentation/QRG - File Management Section - Assign Statement documentation is wrong
The QRG documentation for the ASSIGN statement in the File Management section
contains examples for \
1-50289995 2007.0.0 Utilities - dr3srv build on linux64 crashes
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 \like
this for the linux64 section:
linux64 )
targets=\FC=/opt/intel_fc_80/bin/ifort\ FFLAGS=\-w -w90 -cm -WB -pad_source -W0 -save -zero -Vaxlib -ftz\ export FFLAGS
LDFLAGS=\ export LDFLAGS ;;
1-50337802 2007.1.0 Case Control - Input error leads to misleading 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)
^^^ ERROR(S) ENCOUNTERED IN THE MAIN BULK DATA SECTION ^^^ 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:
*** USER FATAL MESSAGE 601 (IFP1D)
THE KEYWORD ON THE ABOVE CARD TYPE IS ILLEGAL OR MISSPELLED.
Attached is a data deck which shows the problem.
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 XYPUNCH 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-50605180 2007.0.0 SOL 600 - MAT9, MATORT - solids/shells cannot 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 SOL 400, 600 - Multiple cracks using same VCCT case control ID - UFM 311
Multiple VCCT cracks, such as \and \on the same
VCCT Case Control command results in the following fatal message:
*** USER FATAL MESSAGE 311 (IFPDRV)
NON-UNIQUE FIELD 2 ON BULK DATA ENTRY VCCT 1 SORTED ENTRY COUNT = 5036
1-50617151 2007.0.0 Rotordynamics - UFM 3032 (CAMPREP) generating Campbell Diagram
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 Matrix Methods - Floating Point exception in sparse decomp
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 0x00000038 in procedure tmgino_ Offset 0x000012e8 in procedure dfmsym_ Offset 0x00001168 in procedure dfmsa_ Offset 0x00000134 in procedure sdcomp_ Offset 0x00000a88 in procedure facdrvo_ Offset 0x00000d10 in procedure facdrv_ Offset 0x000010f4 in procedure reigla_ Offset 0x00001f1c in procedure lnnrigl_ Offset 0x00003d60 in procedure reig_ Offset 0x000001b0 in procedure xsem06_ Offset 0x00000184 in procedure xsemdr_ Offset 0x00000064 in procedure nastmon_ Offset 0x00000adc in procedure mainal --- End of call chain ---
The problem has been traced to an integer overflow in the routine DFMSA.
1-50698089 2007.0.0 Complex Eigenvalues - HESS - Illegal argument to DGEGV when using QZ HESS
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-50714931 2007.1.0 SOL 600 - BCPARA, GP1 - Marc Translator error
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-50779321 2007.0.0 Dynamics - PARAM,AUTOQSET, Part Superelements - SFM 6144
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)
THE SIZES OF THE INPUT MATRICES AND THE DOF SETS ARE INCOMPATIBLE. SPECIFICALLY:
The number of columns in KSF is not equal to the size of the COMP-set User Information: Size of input matrices and DOF sets:
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/' '/0 $ compile extduset alter 'xemap\\/emap'
call dbstore xemap,,,,//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 superelement 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)
THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY:
The number of columns in MTQ is not equal to the number of non-zeros in
partitioning vector VQ
User Information: Size of input matrices and partitioning vectors: 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/' '/0 $ compile extduset alter 'xemap\\/emap'
call dbstore xemap,,,,//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 superlement 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 Optimization/Design Sensitivity - DRESP1, 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-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:
*** SYSTEM FATAL MESSAGE 6144 (PARTN1)
THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY:
The number of rows in DAY is not equal to the number of rows in the row
partitioning vector VYA
User Information: Size of input matrix and partitioning vectors: 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 $
if ( novafs>0 ) then $
merge day1,,,,,vafs/day/1 $ else $
equivx day1/day/-1 $ endif $ endalter
1-51035307 2007.1.0 Superelements - param,extout with param,autoqset results in UFM 3001 in GP4
Using param,autoqset will result in the following fatal message when used in
combination with param,extout.
*** SYSTEM FATAL MESSAGE 3001 (GP4)
THE INPUT DATA BLOCK NAMED EQEXINX AT POSITION 3 DOES NOT EXIST.
USER INFORMATION: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING:
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-51128594 2007.0.2 SOL 600 - Submittal on Linux IA64 may fail to find marc executable
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 Check default script
/opt/cae/msc/msc20051/marc/linux_rh9/marc91/tools/run_marc
Check default script
/opt/cae/msc/msc20051/marc/linux_rh9/marc2006/tools/run_marc Check default script
/opt/cae/msc/msc20051/marc/linux_rh9/marc2007/tools/run_marc Check default script
/opt/cae/msc/msc20051/marc/linux_rh9/marc2008/tools/run_marc Check default script
/opt/cae/msc/msc20051/marc/linux_rh9/marc2009/tools/run_marc
** Severe Marc Translator Warning ** Script to run Marc not in expected directory
/opt/cae/msc/msc20051/marc/linux_rh9/marc2005/tools/run_marc
1-51152461 2007.1.0 Documentation/SOL 600 - BCPARA,FTYPE - Incorrect Documented Default Value 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-51495308 2007.1.0 Optimizaton/Design Sensitivity - EXTSEOUT - CSUPER - ufm 5423 (MPYAD)
In sol 200 when using external superelements which refer to CSUPER cards the
following error may occur:
*** USER FATAL MESSAGE 5423 (MPYAD)
ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES
FILE# COLS ROWS
FORM TYPE NZWD DENS
TRAILER FOR SCRATCH IS 301 55182 15
2 2 6 1324
TRAILER FOR PXG IS 101 1 1872
2 2 1248 3333
TRAILER FOR (NONE) IS 0 0 0
0 2 0 0
TRANSPOSE FLAG IS 0
Avoidance: use the following DMAP alter for 2005r3 and 2006:
compile EXTIN $
alter 'DBSTATUS X_K' $
if (nokaa>0 and iostat=0 ) then $ EQUIVX X_K /KXX /-1 $ EQUIVX X_M /MXX /-1 $ EQUIVX X_B /BXX /-1 $ 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-51544187 2007.1.0 Connector Elements - CWELD - UFM 6599 (SEP1C), 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 capability for CBUSH and
cylindrical/spherical system MCID's the new Marc COORD SYS option needed to be
used. For models without CBUSH coordinate orientation or MCID's specified by a
coordinate, enter the following parameters PARAM,MRCOORDS,1 PARAM,MRORINTS,1
Starting with tier 1 systems as of 6/22/2007 the above will happen automatically. E Dickerson 6/22/2007
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 Aeroelastic Analysis - AERODYNAMIC FORCE Output, Incorrect Element ID
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 288 288 Translator 334 334 Marc 184 518 MD Nastran 288 518 Translator 334 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 Rotordynamics - SOL 109, Module ROTRUTL, SFM 4276, EC 3001
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. The interpretation of this should be that the rotors do not spin.
1-51854251 2007.1.0 Acoustic Analysis - Grid Point Participation 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 \end.
The error happens when only the punch file is requested by case control command
disp(punch).
Avoidance: Request disp(print,punch).
1-51884991 2007.0.1 SOL 600 - Certain shell elements with MCID 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
http://www.mscsoftware.com/support/software_updates/index.cfm#nastran
1-51919711 2007.1.0 Frequency Response - FRF run with an RLOAD1 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 multiplier is ignored for conm and gravity entries
PARAM,WTMASS multiplier is ignored for conm and gravity entries in SOL 600.
1-51945401 Documetation/IOG - FFIO - New Selection Method
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 may 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 - sensitivity 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 pres PRES 1 RSS 1001 dresp1 10002 pres PRES 1 RSS 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 \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:
*** SYSTEM FATAL MESSAGE 3001 (DOPR3)
THE INPUT DATA BLOCK NAMED DYNAMIC AT POSITION 19 DOES NOT EXIST.
1-52233471 2007.1.0 Optimization/Design Sensitivity - Null weight 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 External Superelement, SOL600,101- UFM 316 (IFPDRV) DMIG
SOL 600 with external superelements will fail with the message:
*** USER FATAL MESSAGE 316 (IFPDRV)
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 design 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 memory problem in gpforce translation to op2 (SOL600)
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 # 9214 in
subroutine T6GPFRC2
- Must stop
MAIN: \
1-52308971 2007.1.0 3D Contact - SOL 101 or 400, the 3D Contact 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.
Avoidance: Insert the following DMAP alter:
compile freqrs
alter 'merge ,,,ppf,,expand','' merge ,,,frfppf,,expand,/ppfe/1 compile semfreq
alter 'equivx frfppf\\/pxf','' equivx ppf/pxf/-1 $ endalter
1-52415018 2007.0.1 Installation - SGI ProPack 5 - end of file
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: `end of file' unexpected
The error is caused by a bad version of \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 \
Avoidance:
1) Backup the current ksh on the system. 2) Install the ksh in the attachment.
1-52425192 2007.1.0 Component modes - PARAMs FIXEDB and AUTOQSET - UFM 3001
If both PARAMs FIXEDB and AUTOQSET are specifed then UFM 3001occurs in the
UPARTN module in subDMAP SUPER3.
Avoidance: Insert the following DMAP alter:
compile super3
alter 'if ( seid=0 )'(3),''
if ( seid=0 and fixedb>-1 ) then $
1-52459991 2007.0.2 Documentation/QRG - SOL 600 - DMIGOUT - Incorrect Default values
The default value of \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-52657971 2007.1.0 DMP - SuSE 10 / IA64 - mpirun: Bad address
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 (\command
line) or Intel/MPI (\ - Use MD R2.1
1-52750618 2007.0.2 Elements - PBUSHT and PBUSH with the same ID, Unexpected Answers
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 2007.1.0 Composites - PCOMP, PARAM,POST,0 - Missing data in XDB
Layered composite stress results may be missing from the xdb for SOL 106.
1-52841658 2007.1.0 Modal Participation Factor - PFMODE - Missing Output
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 $ not ok $set 2 = 104/T1 $ not ok $set 2 = 104/T3 $ ok $set 2 = 105/T3, 104/T3 $ ok $ fluid grid
set 3 = 1020, 1021, 1022 pfmode(structmp=all) = 2
1-52953651 2007.1.0 SOL 400 - GPFORCE, CQUADR, CTRIAR - Incorrect GPFORCES
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-53135565 2007.1.0 MODE=I8 - OUTPUT4, INPUTT4 - SFM 6445 (INPTX4) on ILP64(mode=i8)
INPUTT4 may fail on i8 systems with the following message:
*** SYSTEM FATAL MESSAGE 6445 (INPTX4)
READ REQUESTED RETURNED INCORECT DATA LENGTH WHILE PROCESSING UNIT = 49
FOR LOGICAL NAME INPUTT4
EXPECTED 156 WORDS, ACTUALLY READ 78 WORDS
USER ACTION: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT MSC.SOFTWARE CLIENT SUPPORT.
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 2007.0.2 SOL 600 - NLAUTO - Loads not translated correctly.
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 strains/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:
*** SYSTEM FATAL MESSAGE 4276 (BLDPRD) 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 GPSTRAIN - Missing GPSTRAIN Output for Model with QUAD and HEXA Elements
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.
Kevin, I added an activity with comments of avoidance found by the user.
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 - PROJTOL 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 SOL 400 - UFM 1126 with scr=post in tpl decks nltsr03 and nltsub03
If scr=post (or scr=no with NASTRAN SYSTEM(316)=7 or 19), then SOL 400 may fail
with USER FATAL MESSAGE 1126.
Avoidance: There is no simple avoidance.
1-53894031 2007.1.0 Elements - CBEAM3 - Stress recovery for cbeam3 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 External Superelements - k4 , unsymmetric matrix - Inefficient runtime
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 Eigenvalue Analysis - READ - Access Violation or Signal 11 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 DIRECT 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 SOL 400 - RBE and no differential may lead to SFM 7620 (EMG)
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-54260851 2007.0.0 ACMS - DOMAINSOLVER, EXTSEOUT - Wrong eigenvectors if MDACMS is used
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
Avoidance: Insert the following DMAP alter:
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 Acoustics - METHOD(STRUCTURE) - Extra eigenvector output
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.
Avoidance: Insert the following DMAP alter:
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 $ alter 'call cmpmode' 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 Elements - UWM 7651 for QUADR elment may be incorrectly issued
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-54407131 2007.1.0 SOL 600 - Material orientation causes convergence problems in SOL600
Specifying a material orientation angle by referening a coordinate system may
cause convergence problems in SOL 600.
1-54412161 2007.1.0 Large Models - SEQP - Integer overflow in matrix reordering routines
Large models that request more than 4gb of memory may fail with an integer overflow in the metis or bend ordering routines.
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-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-54657775 2007.1.0 SOL 600 - Incorrect Thermal Load Translation
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 2007.1.0 Design Optimization - External Superelement and MODTRAK - System 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.
Avoidance: Insert the following DMAP alter:
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 SOL 600 - Fails when running from a location that has spaces in its path.
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 Connection Elements - CFAST - UFM 2007, Incorrect element identified
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-55090064 2007.0.2 SOL 600 - SOL 600, 153, BCONTACT - Missing jid.ink contact interface file
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: \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 SOL 400 - Lmfact is incorrect if the first increment is linear.
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 Aeroelastic Analysis - Misleading error message, UFM 7019 in DSFLTF
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 IS ATTEMPTING TO OUTPUT DATABLOCK 204 NAME = FPA
, WHICH ALREADY
The above error message appeared in a SOL 200 run with three subcases with multiple boundary conditions, some of which had design response and others did not.
A SOL 200 analysis with multiple subcases and multiple boundary conditions,
some of which have design responses and others that do not may fail with the
message;
DMAP MODULE SSG2 IS ATTEMPTING TO OUTPUT DATABLOCK 204 NAME = FPA
, WHICH ALREADY EXISTS
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 leads to UWM 6080 (TMALOC) - IA64 mode=i8 - Montecito
Users may encounter \systems
running ILP64 (i9).
Avoidance: Create Timing constants as descriped in the IOG.
1-55221287 2007.1.0 SMP - Tjoin error - IA64 ILP64 Montecito chips
Fixed in rnd 33 with INTEGER used instead of \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 SOL 400 - Nonlinear Materials - SFM 6352 (TA1NLM2), LOGIC error 9301
The following error message occurs with a big model using a large buffize of
655537.
*** SYSTEM FATAL MESSAGE 6352 (TA1NLM2) LOGIC ERROR: 9301
USER ACTION: CONTACT MSC.SOFTWARE CLIENT SUPPORT.
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 Optimization/Design Sensitivity - Fully stressed design - UWM 7531
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 Documentation/QRG - PARAM,MARVFCUT - Incorrect Default Value
In QRG of 2007r1 and MD r2, the description \PARAM,MARVFCUT is incorrect. The default is 0.0001.
1-55343290 Documentation/QRG - GROUNDCHECK Description of RTHRESH
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 divergent 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 parameter 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 2007.1.0 SOL 400 - SFM 4276 (UNPACK), EC 31 aix i8 only
SOL 400 jobs may fail on aix i8 systems with the message
*** SYSTEM FATAL MESSAGE 4276 (UNPACK) 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 systems 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 SOL 700 - Incorrect error message indicating duplicate TABLED id
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 SOL 400 - ANALYSIS=NLTRAN, RIGID - Incorrect Default for RIGID command
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-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 Aeroelastic Analysis - UFM 315 FORMAT ERROR ON BULK DATA ENTRY UXVEC
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 2007.1.0 SOL400 - CQUADX, PSDNL1 - Incorrect Stress Results In SOL 400, the STRESS result of the nonlinear axisymmetric element CQUADX that
references property entry PSDNL1 is incorrect.
1-55892751 2007.1.0 SOL 400 - SPC - Analysis may fail when there 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-55974341 2007.1.0 Case Control - GROUNDCHECK - Format error does not lead to UFM
This form of the GROUNDCHECK command:
GROUNDCHECK(SET=ALL,DATAREC=ALL,RTHRESH=0.9)=YES
should trigger a UFM as DATAREC should not recognize \options YES or NO exist.
1-56095478 2007.1.0 Optimization/Design Sensitivity - BUCKLING - 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-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
6 0
INCONSISTENT NUMBER OF COLUMNS OR TERMS SENT BY ELEMENT ROUTINE FOR PACKING OUT BY EMGPOM, OR INVALID INFORM-OUFORM COMBINATION.
1-56149641 Documentation/QRG - SPARSESOLVER Executive Command Not Documented
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 SOL 400 - Missing MPCF output for kinematic elements (RROD)
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 SOL 400 - CONV=UPW and CONV=PV on NLPARM entry cannot be mixed.
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.
Avoidance: There is no avoidance.
1-56189563 2007.1.0 Rigid Elements - TEMP(LOAD), SSG1 - UFM 4297 (TQD4D) Incorrectly issued
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
HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR EQUAL 180 DEGREES.
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 Optimization/Design Sensitivity - PBAR/PBARL - Incorrect Punch File
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 Servers 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 description 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.
Avoidance: There is no avoidance.
1-56597055 2007.1.0 Exterior Acoustic - DOMAINSOLVER ACMS, SPCD - UFM 6144 (PARTN1PR)
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 SOL 400 - PARAM,LGDISP, BCONTACT - Failued to Converge or Incorrect Result
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 Optimization/Design Sensitivity - DRESP1, 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 2007.1.0 DMP - PRESOL may hang when a partition failure occurs.
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-56885001 2007.1.0 ADAMSMNF - Incorrect Inertia Tensor - 32 bit Linux
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 \-m\
command. If the output is \then the OS is 64 bits. If the output 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:
SYSTEM FATAL MESSAGE 7349 (LNNHERR)
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
alter 'call super3'(2),'' CALL SUPER3,
CASEcc , ,UL , , , , , , , , crx , ,qrg , , , ,PCDB ,XYCDB ,POSTCDB ,FORCE , EMAP ,MAPS ,EQEXINS ,PVTS ,CASES , SLT ,ETT ,GOT , ,LOO , crj , ,UOO , ,GPLS ,