This file contains the errors corrected in MD Nastran R3 (Version 2008.0.0)

30147          2008.0.0 (MD R3)      Nonlinear Analysis - NLPCI, CRIS - Negative Load Factors

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    2     LOOPID   29     LOAD STEP   -6.389     LOAD FACTOR-7.38852477
 SUBID    2     LOOPID   30     LOAD STEP   -7.891     LOAD FACTOR-8.89144518
 SUBID    2     LOOPID   31     LOAD STEP  -10.059     LOAD FACTOR***********

Avoidance:  Use the RIKS method or SOL 400.

30578          2008.0.0 (MD R3)      Nonlinear Analysis - PARAM,LGDISP, PLOADX1, LOAD - Wrong Answers

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.

33401          2008.0.0 (MD R3)      Case Control - SEALL, SEMG, SEKR, etc. - UFM 9015, Poor Message

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.

35508          2008.0.0 (MD R3)      Eigevalue Analysis - READ - UIM 4158, Massless Mechanisms

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)
 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)
     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.

38096          2008.0.0 (MD R3)      Miscellaneous - Accounting file, Solution type and CPU time are not written

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 ../<

38907          2008.0.0 (MD R3)      Complex Eigenvalue Analysis - CEAD - UWM 5411 (REIGL8)

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. 


41387          2008.0.0 (MD R3)      Parallel Processing - DMP, GPWG - Wrong Answers for GPWG

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.

1-3477406      2008.0.0 (MD R3)      Eigenvalue Analsyis - PARAM,SNORM - SFM 3007 (MERGE)

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-4273414      2008.0.0 (MD R3)      Optimization/Design Sensitivity - DVMRELi - SFM 4276 EC 3001 from DSAB0

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-4405034      2008.0.0 (MD R3)      ACMS - fluid/structure - Extra Erroneous Output

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-4807929      2008.0.0 (MD R3)      Miscellaneous - PARAM, AENLTOL - Missing Output

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-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-5785604      2008.0.0 (MD R3)      [KCR:3039] Database - DBLOAD - BIOMSG: ERROR   3010 HAS OCCURRED IN ROUTINE GXWRIT

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
MAIN: "Access violation" (C0000005) exception encountered.

Avoidance:  There is no avoidance.

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
     PROGRAMMER INFORMATION:
          THE FULL DBDIR RECORD CONTAINING THIS LOCATION PARAMETER IS:
               67108     67140     71400ADBX             3         2ADB
0FATAL ERROR

1-8987307      2008.0.0 (MD R3)      Element Strain Energy - ESE - Negative Percentage

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.

Need to consider DEFORM loads. kkk

Note: When numerical zeros are the only contributions for the element type the 
element lines are eliminated but the TOTAL line and headers are retained.

1-9934302      2008.0.0 (MD R3)      Nonlinear Analysis - Wrong eigenvector forces 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-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-12061001     2008.0.0 (MD R3)      Buckling - EIGRL -  Uses bad shift when first root is positive

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-12263602     2008.0.0 (MD R3)      Buckling Analysis - EIGRL, Lanczos - Missing Eigenvalues

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-12893301     2008.0.0 (MD R3)      Optimization/Design Sensitivity - DESSUB, RMS, PSD - Fatal Message in dom10f

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-13338503     2008.0.0 (MD R3)      Superelements - SUPER, normal modes - missing or excessive output

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-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-14568012     2008.0.0 (MD R3)      Acoustic Analysis - ACMODL - Corrupted pch file output

Acoustic analysis that specifies the CP method on the ACMODL entry may produce 
a corrupted (skinout) punch file.

1-14602401     2008.0.0 (MD R3)      Submittal - SDIR must be write accessible if QUE= is specified

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-15056901     2008.0.0 (MD R3)      Distributed Memory Parallel - DOMAINSOLVER - 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-16479901     2008.0.0 (MD R3)      MDACMS fails for all fluid model - SFM 3001

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      1 DOES NOT EXIST.

Avoidance:

compile modefsrs
alter 'mdacms=', '' $
paraml   vafs//'null'//s,n,full $
mdacms=(NDOM>0 and full=0) $ all fluid models not allowed
endalter

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 
following DMAP alter:

$ 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-19459484     2008.0.0 (MD R3)      Documentation/QRG - PCOMP - Remark 11 obsolete, 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-19557090     2008.0.0 (MD R3)      Random Analysis - RANDPS - Power Spectral Density Label missing

When a corner output request is made for plate elements, the label "POWEWR 
SPECTRAL DENSITY FUNCTION" is missing.

1-19702867     2008.0.0 (MD R3)      Composites - PCOMPG and Lam SYM option - UFM 4377 (IXPCOMP)

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)
 *** USER FATAL MESSAGE 316 (IFPDRV)
     ILLEGAL DATA ON BULK DATA ENTRY PCOMPG  

This input combination is corrected by issuing the message: 

 *** USER FATAL MESSAGE 316 (IFPDRV) 
     ILLEGAL DATA ON BULK DATA ENTRY PCOMPG
 PCOMPG  12                      5000.   HILL    0.0             SYM      
+000005
 ++000005100000  1       .0054   45.     YES                              
+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 (Field Data Format: 0=Blank, 1=Integer, 2=Real, 
3=BCD, 4=Double, -32767=End-of-Data)                  
           M() = SYM      (Field Data Value)
        CALLSB = IXPCOMP  (Name of subroutine)
          NOTE : LAM=SYM is not supported for PCOMPG

1-19901299     2008.0.0 (MD R3)      Nonlinear Analysis - PELAST in SOL106 analysis yields wrong GPForces

In nonlinear analysis, GPForces outputs don't take into account the CELAS  
forces that that reference PELAST.

1-20166404     2008.0.0 (MD R3)      Transient Response - SOL 146, OLOAD - Missing Output

OLOAD  output is not supported in SOL 146 for transient reponse.  

Avoidance:  To request OLOAD output for transient response in SOL 146, add the 
following DMAP alter:

compile seaero
alter 'delete   \/ppf,psf',''
      delete   /psf,,,, $
      IFT      ppf,CASES,TRL,FOL/
               pxf,fol3/IFTM $
      equivx   pxf/ppf/-1 $

1-20425054     2008.0.0 (MD R3)      Superelements -  SECONCT - UFM 6782, Module SEP1X, Subroutine SEPMC2

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-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          1    47.1  21145.  21145.          42290.        +000001 

+000001 NO      .1282       47.1  21145.  21145.          42290.        +000002
+000002 NO      .1282       28.2  12687.  12687.          25374.        +000003
+000003 NO      .8718       28.2  12687.  12687.          25374.        +000004
+000004 NO      .8718       47.1  21145.  21145.          42290.        +000005
+000005 NO      1.          47.1  21145.  21145.          42290.        +000006
+000006 .5      .5

gives the correct answer

Avoidance:  Remove the duplicate station.

1-20752361     2008.0.0 (MD R3)      Optimization/Design Sensitivity - Poor Message, 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-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-22408855     2008.0.0 (MD R3)      Optimization/Design Sensitivity -  PBARL, 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-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-22717058     2008.0.0 (MD R3)      Buckling Analysis - EIGRL - SOL 105 may abort

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-23105401     2008.0.0 (MD R3)      Transient Response - Multiple boundary conditions - No error/warning message

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-23504486     2008.0.0 (MD R3)      Documentation/QRG - PBEAML entry for DBOX error

The figure for PBEAML type DBOX in the QRG has a typo.  What is shown as DIM12 
should be DIM2.

1-24030411     2008.0.0 (MD R3)      Optimization/Design Sensitivity - DRSPAN - 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) 
USER FATAL MESSAGE 6492 (DOPR3R)

Avoidance:  Use the DRSPAN entry and reference proper DRESPR1 entries for each 
subcase.

1-24121027     2008.0.0 (MD R3)      Rigid Elements - Wrong Results for RIGID=LAGR and TEMP=n and ALPHA

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-24412204     2008.0.0 (MD R3)      External Superelements - SFM 3200 (Logic Error 31) in the BDRYINFO module

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-24584517     2008.0.0 (MD R3)      Optimization/Design Sensitivity - FRSTRE-  UFM 7138 in DOPR3H

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-25080130     2008.0.0 (MD R3)      Documentation/QRG - PARAM description does 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-25277451     2008.0.0 (MD R3)      Elements - CQUADR may give wrong results for interior angles of 180 degrees

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-25660161     2008.0.0 (MD R3)      Documentation/QRG - Description of ISTYP of BCBODY is incorrect

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-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-25801752     2008.0.0 (MD R3)      Postprocessing - DBC, PARAM,POST,0 - SFM 6062 (DBC), Poor Message

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-25945741     2008.0.0 (MD R3)      Nonlinear Analysis - EKE is not available for modal preload analysis.

EKE is not available for a modal preload analysis in SOL 106.

Avoidance:  Supply a dummy linear element

1-26411375     2008.0.0 (MD R3)      NLPARM Defaults differ 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-28171504     2008.0.0 (MD R3)      Documentation/QRG - description for K1/K2 of PBAR in QRG

Remark 5 under the QRG description for the PBAR entry should read transverse 
shear stiffness times unit length instead of per unit length.

1-31899071     2008.0.0 (MD R3)      MDACMS with PARAM,SPARSEDR,NO causes wrong eigen vectors in SOL 103

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:   Insert the following DMAP alter:

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-32941641     2008.0.0 (MD R3)      SOL 400 - TTEMP, TID, CROD, CONROD, CTUBE - Wrong Answers

If time dependent loads are defined on TTEMP entry in SOL 400 for CROD, CONROD, 
or CTUBE elements wrong answers will result.

1-33441861     2008.0.0 (MD R3)      ADAMSMNF -  FLEXONLY=YES option gives large XDB with no results

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-35833199     2008.0.0 (MD R3)      Optimization/Design Sensitivity - DOM9, PBRSECT - SFM 4276, EC 7777

A SOL 200 analysis with arbitrary beam (PBRSECT)  failed in the DOM9 with 
SYSTEM FATAL MESSAGE 4276 Error Code 7777

1-35970568     2008.0.0 (MD R3)      Documentation/ QRG - DOMAINSOLVER - Table 3-1 GEOM/GRID option

Table 3-1 under the QRG documentation for the DOMAINSOLVER commdand refers to 
the GEOM option.   This should be the GRID option.

1-36066967     2008.0.0 (MD R3)      Optimization - SOL 200 with SE and TEMP(LOAD) - 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
 *** SYSTEM FATAL MESSAGE 3003 (SDR2)
     ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK ETT      
(FILE  107) IN SUBROUTINE GETEMP
0FATAL ERROR

or  with SCR=YES, may fail with:

*** SYSTEM FATAL MESSAGE 3003 (SSG1)
     ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK ETT      
(FILE  107) IN SUBROUTINE GETEMP

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.

Avoidance:  Apply the following dmap alter:

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-36462622     2008.0.0 (MD R3)      Documentation - QRG - PFAST - case MCID=0 and MFLAG=0 is missing

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 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-37426959     2008.0.0 (MD R3)      Installation/Licensing - MSC_LICENSE_FILE points to port@IP_Address

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-37949081     2008.0.0 (MD R3)      SOL 700 - Names longer than 22 charachters 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)      Documentation/QRG - CBUSH - SOL 106, missing CBUSH forces with LGIDSP

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-39801126     2008.0.0 (MD R3)      Documentation/QRG - SORT1 vs SORT2 description in QRG

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.
• 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 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     2008.0.0 (MD R3)      SOL 400 - Superelements, data recovery missing

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 $
COMPILE SUPER3 NOLIST $
ALTER 'IF.*NOCASRS1.*SEID','' $
IF ( (NOCASRS1>-1 OR APP='NLST') AND SEID=0 ) THEN $
ENDALTER $
ECHOON $

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. 

Avoidance:  Apply the following dmap alter:

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-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)      Nonlinear Analysis - LOAD, Follower Forces, PLOAD4 - Wrong Answers

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-44800991     2008.0.0 (MD R3)      Optimization/Design Sensitivity - MATT1, MATT9 - UFM 2019

A SOL 200 analysis with MATT1 or MATT9 entries will lead to USER FATAL MESSAGE 
2019.

1-45325022     2008.0.0 (MD R3)      Documentation/QRG - System Cell 361(aka PRTPCOMP)

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)      Materials - Missing material entry leads to poor message - UFM 2042 (IFP6)

A missing material entry in a large input file issued the following message:

 *** USER FATAL MESSAGE 2042 (IFP6)
     MISSING MATERIAL TABLE       11 FOR ELEMENT      160
 *** USER FATAL MESSAGE 2042 (IFP6)
     MISSING MATERIAL TABLE       11 FOR ELEMENT      161

The message should have indicated that the ids were for the PCOMP not  element 
ids.

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-46727939     2008.0.0 (MD R3)      Optimization/Design Sensitivity - SFM  5423 (MPYAD1)   ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES

An optimizatoin job with a static SPCFORCE response may fail at MPYAD in 
subdmap RESPSEN with the following message: 

*** SYSTEM FATAL MESSAGE 5423 (MPYAD1)
     ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES
                                                   FILE#     COLS     ROWS  
FORM  TYPE  NZWD  DENS
                           TRAILER FOR QG       IS   101        2       36     
2     2     8  1111
                           TRAILER FOR SPAWQ    IS   102       16        1     
2     2     2 10000
                           TRAILER FOR QG1X     IS   103       16       36     
2     2     4   174
                           TRANSPOSE FLAG IS 0

Avoidance:  Insert the following DMAP alter:

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-46887171     2008.0.0 (MD R3)      BIOMSG Error 211 BLDPRD 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. 

SYSTEM FATAL MESSAGE 4276
     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-47911501     2008.0.0 (MD R3)      Documentatio/QRG - AUTOSPC describer - NOZERO vs. NONZERO

References to "NONZERO' in the QRG description of the AUTOSPC case control 
command should be "NOZERO".

1-48291704     2008.0.0 (MD R3)      MDACMS - SDAMPING - Wrong Answers with K4 Structural Damping

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-49098315     2008.0.0 (MD R3)      Rotordynamics - Hybrid Damping in Rotordynamics 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: 

 *** SYSTEM FATAL MESSAGE 3001 (GKAM)
     THE INPUT DATA BLOCK IN POSITION      4 DOES NOT EXIST.
     USER INFORMATION: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING:
          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 CALL STATEMENT.

1-49118561     2008.0.0 (MD R3)      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-49161431     2008.0.0 (MD R3)      Performance - TAUCS - ILP64 (linux64 / linux8664)

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-49502651     2008.0.0 (MD R3)      ADAMS Integration - SPOINT/QSETi - SFM 7624(GKAM) in stress recovery run

The following message occurs in stress recovery, when the number of 
SPOINT/QSETi are specified greater 

than needed in MNF file creation run.

 *** SYSTEM FATAL MESSAGE 7624 (GKAM)
     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-49522526     2008.0.0 (MD R3)      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-50098347     2008.0.0 (MD R3)      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 "ASSIGN OP2" that should be "ASSIGN OUTPUT2".

1-50337802     2008.0.0 (MD R3)      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.

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-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-51120736     2008.0.0 (MD R3)      Matrix Methods -  Insufficient core for FBSMEM; 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).    

Avoidance:  Increase memory.

1-51434272     2008.0.0 (MD R3)      Documentation/QRG - SMETHOD, ITER - UFM 9058, Wrong Answers

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)      Topology -  asterisks for material ids and design variable ids

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       ********          E    1.000000E+07    1.250000E+06    
1.000000E-15    1.000000E+20   WARNING

1-51517141     2008.0.0 (MD R3)      Documentation/QRG - PSOLID - TETRA(5-10 node) 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-52145229     2008.0.0 (MD R3)      Elements - Model Summary - Element Summary Overflows

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

Avoidance:  There is no avoidance

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-52721371     2008.0.0 (MD R3)      DMP/Frequency Response - DOMAINSOLVER, PARAM,LFREQ - UFM 3047 (GKAM)

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-52819821     2008.0.0 (MD R3)      Miscellaneous - Incorrect ReplicatorSymbol 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-53071681     2008.0.0 (MD R3)      Element Strain Energy - OFREQ - Wrong Frequencies Output

A memory overrun processing the OFREQ list may result in incorrect frequencies 
beign out and/or strange characters in the output.

1-53159901     2008.0.0 (MD R3)      Numeric Methods - Decomp, SOLVE, SYSTEM(166)=8192 - TAUCS Solver may crash

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-54248591     2008.0.0 (MD R3)      Documentation/QRG - MATF format incorrect for SOL 600

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)      MDACMS - DOMAINSOLVER, EXTSEOUT and CSETi causes SFM 5423 (MPYAD1)

An MDACMS analysis  with external superelements and CSETi (or BNDFREEi) will 
fail with 

SYSTEM FATAL MESSAGE 5423 (MPYAD1)

Avoidance:  Insert the following DMAP alter:

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)      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-54371211     2008.0.0 (MD R3)      Linear Contact - BCONTACT, RBE, MPC - Access Violation

A linear contact model in SOL 101 that contains RBE elements or MPC equations 
will fail with an access violation.

1-54381101     2008.0.0 (MD R3)      External Superelements - CSET - SFM 6143 (UPARTPR)

An external superelement analysis with C-Set specified wll fail with the 
message:

 *** SYSTEM FATAL MESSAGE 6143 (UPARTPR)
     THE SIZES OF THE INPUT MATRICES AND THE DOF SETS ARE INCOMPATIBLE.  
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-55077699     2008.0.0 (MD R3)      Elements - TEMPP1, CTRIAX6 - Wrong Answers

TEMPPi entries are not designed to work with CTRIAX6 elements and will produce 
incorrect results. 

Avoidance:  Define the temperature loading with TEMPD

1-55310851     2008.0.0 (MD R3)      Documentation/QRG - PARAM,MARVFCUT - Incorrect Default Value

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     2008.0.0 (MD R3)      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-55735063     2008.0.0 (MD R3)       ADAMSMNF - PARAM,AUTOQSET, SPCFORCES - SFM 5423 (MPYAD1)

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. 

Avoidance:  Insert the following DMAP alter:

compile phase1b
alter 'ksf1'(2)
delete /kfs,,,, $
trnsp ksf/kfs $


Dear Sir,
 If client run the data that is including SPC and PARAM,AUTOQSET,YES  cards to 
make MNF file, Nastran stopped with "SFM5423 (MPYAD1)".
Ver2005r2(2005.1) was no problem, but Ver2005r3 and over(2006, MD R2) will be 
stopped with SFM5423. I attached input datas.
Thank you for your help.

jun

1-55876341     2008.0.0 (MD R3)      SOL400 - CQUADX, PSDNL1 - Incorrect Stress Results


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 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-55934951     2008.0.0 (MD R3)      Rotordynamics - UNBALNC for Frequence response - SFM 3001

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     AT POSITION      7 DOES NOT EXIST.

Avoidance:   Insert a dummy TABLEDij entry.

1-55986678     2008.0.0 (MD R3)      SOL 400 - May fail on ilp64 (mode=i8) systems in the TA1M Module

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 Contents  (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     2008.0.0 (MD R3)      Heat Transfer Analysis - TEMPBC - DBCMSG 41

The following error message may appear when TEMPBC entries are specified:

 *** SYSTEM WARNING MESSAGE 6065 (DBC)
 *** 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-56095773     2008.0.0 (MD R3)      SOL 400 - CQUADX, PLPLANE - UFM 6348, Wrong Answers

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-56149641     2008.0.0 (MD R3)      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-56679235     2008.0.0 (MD R3)      SOL 700 - "WORKSHOP 1 TAPERED BEAM IMPACT" contains bad contact definition

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)      Multipoint Constraints - LOAD, MPCD - Missing Documentation

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)      Shape Optimization - BNDGRID and superelements and UFM 9067 - Wrong answers

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-57050333     2008.0.0 (MD R3)      SOl 400 - ANALYSIS=NLTRAN, floating point exception error

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 ***
 *** USER INFORMATION MESSAGE 6189 (nl3con)
     *** 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
 *** USER INFORMATION MESSAGE 6189 (nl3con)
     *** BEST ATTAINABLE SOLUTION HAS BEEN FOUND ***
 MAIN: The FPU has been reset after floating point exception.
 MAIN: For reference, A(MAINAL)   =   401436, A(/SYSTEM/) =  36C4D20           
 MAIN:                A(/XNSTRN/) =  6C20000                                   
 MAIN: "Floating point overflow" (C0000091) exception encountered.
 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-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

Avoidance:  Insert the following dmap alter:
compile resmodes
alter 'neigv1'(3,-1)
return $
endalter

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)
     MISSING MATERIAL TABLE        1 FOR ELEMENT    51585

1-57475308     2008.0.0 (MD R3)      External Superelements -  DMIGPCH - data recovery missing

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-58051791     2008.0.0 (MD R3)      External Superelements/Fluid Response - DMIGPCH - Zero Fluid Response

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 commands - 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)   $ to get the magnitude part punched 
  XYPUNCH FMPF(5) MODE / 1041(T2)     $ 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-58120430     2008.0.0 (MD R3)      DDAM - UFM 740 (RDASGN), DDAM example aborts using UNIT=21

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-58746801     2008.0.0 (MD R3)      Documentation/QRG - Incomplete complex force item codes(CELAS1)

The complex force item code for the CELAS1 element in the QRG are missing and 
should be as follow: 

Item Code     Item       Real/Mag. or Imag/Phase  
        2            force                   RM
        3            force                   IP

1-58837502     2008.0.0 (MD R3)      Aeroelastic Analysis -  AMP Module, PARAM,GUSTAERO - SFM 4276 EC 31

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-59166049     2008.0.0 (MD R3)      Elements - CBAR, PBRSECT - Incorrect shear stress for Vz load

The stress recovery for a CBAR element that references a PBRSECT entry is 
incorrect for VZ shear force.

1-59185711     2008.0.0 (MD R3)      Superelements - EXTSEOUT, acoustic cavity, MDACMS - SFM 6143

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)
     THE SIZES OF THE INPUT MATRICES AND THE DOF SETS ARE INCOMPATIBLE.  
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
     Set sizes:  Major (G-set)=     4022
                 Set0  (A-set)=      258
                 Set1  (COMP-set)=     3764

1-59206949     2008.0.0 (MD R3)      Elements - PBRSECT - Arbitrary Beam coordinate system incorrect, bending stress incorrect.

Arbitrary beam produce incorrect bending stress data recovery.

1-59215380     2008.0.0 (MD R3)      Elements - PBRSECT - Stress recovery stress 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 Stress Tensor |  Recovered ABCS Direct Stress
Sx  | Sx
Sy  | Sxy
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-59294257     2008.0.0 (MD R3)      Acoustic Analysis - PFMODE, PFPANEL - Output 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 control 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-59690996     2008.0.0 (MD R3)      Documentation/QRG - RBJOINT - SOL 700 Only, Should not be in MSC.Nastran QRG.

The RBJOINT is a SOL 700 only entry and it should not be included in the 
MSC.Nastran QRG.

1-59715698     2008.0.0 (MD R3)      Eigenvalue Analysis - CGAP -  UFM 4016 (TA1ETD)

******** dvw model seems to run fine in md2007t1 **************
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 produced 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.

Avoidance:  Insert the following DMAP alter

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)      Aeroelastic Analysis - CAERO1, MONCNCM - Tolerance is too tight

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-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)      FRF - PLOTEL entries result in SFM 3200 (Logic Error 27) in FRFINFO module

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)      FRF - PLOTEL entries result in SFM 3200 (Logic Error 12) in FRFINFO module

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 entries 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)      SOL 400 - Hybrid Damping is not implemeted into SOL400 correctly.

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-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-60222617     2008.0.0 (MD R3)      Aeroelastic Analysis - MONITOR=ALL results in Complex Data Output

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-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.

Avoidance:  Insert the following DMAP alter.

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.

Avoidance:  Insert the following DMAP alter:

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-60803879     2008.0.0 (MD R3)      Elements - PARAM CDITER without any SUPORT entry - SFM 3007 in SOLVE

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     2008.0.0 (MD R3)      Documentation/QRG - SOL 600 - MARCSAME Parameter

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 with 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)      SOL 700 - PEULER1, SET1, and EOSGAM entries not translated

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)      SOL600 - Axisymmetric analysis with contact bodies fails

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)      SOL 400 - PARAM,LGDISP,1 - Large rotation, poor convergence

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 Response, 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.

Avoidance:  Apply the following dmap avoidance: 

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 3005 (NLSOLV), Attempt to operate on a singular matrix

SOL 400 with the casi iterative solver specified by  "SMETHOD=ELEMENT"  may 
fail with the message:

*** 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:

http://www.mscsoftware.com/support/software_updates/mdr211.cfm

1-61419147     2008.0.0 (MD R3)      Case Control - IFP - K2GG User Fatal Error 615.

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.  

 *** USER FATAL MESSAGE 615 (IFP1D)
     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 with 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:

 *** SYSTEM FATAL MESSAGE 3008 (UTMCOR)
     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-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-62064821     2008.0.0 (MD R3)      Dynamics - TFL command, TF entry - Inefficient 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)      Miscellaneous - IFP - UFM 316, SUPORT1 entry fails with more than one point.

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 keywords capability is broken

The user-defined PARAM keywords capability was broken when enhancements to the 
"remote query" capability were added.

1-62228981     2008.0.0 (MD R3)      Documentation/QRG - SOL 600 - MRFOLOW1 Parameter

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 translated 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)      Connector Elements - CFAST with GS, GA, GB specified - Wrong answers

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)      GPSTRAIN - Incorrect Answers for NORMAL X3 Option on Surface entry

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)      Miscellaneous - Large Field - Wrong system cell information in the UFM 316

The folloiwng message:

      USER FATAL MESSAGE 316  (IFPDRV)
      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)      External Superelements - SOL 109 / SOL 112 - Wrong answers

Velocity and acceleration results will be that of the displacement vector in 
transient analysis with external superelements for the following output 
requests:

Request              Result
---------            ----------------
VELO only            Wrong: VELO=DISP
ACCE only            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)      Part Superelements - RANDOM - SFM 3001 DITS does not exist

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 VMOPT - 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)
    THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE.  
SPECIFICALLY:
    The number of rows    in GQE is not equal to the number of non-zeros in 
partitioning vector VA
    User Information:  Size of input matrices and partitioning vectors:
                       GQE     :  Rows=        7 by   Cols=       72
                       VA      :  Rows=        6      no. of non-zeros=        
0 no. of zeros=        6

PARAM,VMOPT,1 causes:
*** SYSTEM FATAL MESSAGE 4276 (QOPEN)
    ERROR CODE     1044 PID=   0

PARAM,VMOPT,2 causes:
SYSTEM FATAL MESSAGE 6144 (MERGE1)
THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE.  
SPECIFICALLY:
The number of rows    in GTEQ is not equal to the number of non-zeros in 
partitioning vector VA
User Information:  Size of input matrices and partitioning vectors:
                   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)
if ( notset>0 ) then $
alter 'merge    met,,meq'
else $
   equivx  meq/mea/-1 $
endif $

compile mgen1
alter 'noqset'(2,-1)
if ( notset>0 ) then $
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'
if ( notset>0 ) then $
alter 'equivx.*mtqx'
else $
   equivx  mvaa/mvqq/-1 $
endif $
endalter

1-62884428     2008.0.0 (MD R3)      SOL 600 - MSC.Nastran 2007r1 Windows 32 bit 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)      SOL 400 - UWM 602 issued if non-unique set ID's are used in steps in SOL400

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)      Optimization/Design Sensitivity - RGYRO failed in ROTOR of subdmap GYROBASE

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/
   $..Input Parameters:
   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)      Connector Elements - SET, CWELD - Incorrect CWELD element forces

Patch to patch CWELD element forces may be incorrect when data recovery is 
performed on a subset of the CWELD elements.

1-63212781     2008.0.0 (MD R3)      Frequency Response - UMFPACK, SYSTEM(209)=16 - Wrong Answers

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     2008.0.0 (MD R3)      Performance - Unsymmetric Decomp is slow on IA64

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:

http://www.mscsoftware.com/support/software_updates/index.cfm#nastran

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-63608373     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.

 *** USER FATAL MESSAGE 1126 (GNFIST)
     DMAP MODULE SDR1     IS ATTEMPTING TO OUTPUT DATABLOCK      201 NAME = 
CPHP    , WHICH ALREADY EXISTS.
     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)      SOL 400 - AUTOSPC fails if there are kinematic element in the model

For SOL400, If there are rigid elements with RIGID=LAGR case control command, 
the AUTOSPC command will not work correctly.

1-63684101     2008.0.0 (MD R3)      Composites - FAILURE THEORY show bad output for BEAM3

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)      Elements - CBUSH, ELSUM - Bad Data in Element Summary Table

The CBUSH element may lead to illegal characters in the ELEMENT PROPERTY 
SUMMARY table.

1-63833183     2008.0.0 (MD R3)      Optimization/Design Sensitivity - Linear Gaps - SFM 3007 (SOLVE)

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 failed 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)      Aeroelastic Analysis - XYPUNCH ignores XMAX in KE-Method of Flutter

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     2008.0.0 (MD R3)      SOL 600 - FORCE - Wrong Load, Wrong Answers

Multiple FORCE entries for the same grid point leads to incorrect loads in SOL 
600 when multiple subcases exist.  For example,  the entries

FORCE    1       96      0       10.     -1.      0.      0.
FORCE    1       96      0       12.      0.     -1.      0.
FORCE    1       96      0       14.      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)      Optimization/Design Sensitivity - Convergence Messages Misleading

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-64426459     2008.0.0 (MD R3)      SOL 600 - NLPARM Case Control Command not translated correctly

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.
     USER ACTION: CONTACT MSC.SOFTWARE CLIENT SUPPORT.
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 and scr=no - UFM 1126 in DISUTIL for EPT

SOL 200 optimization runs with dmp>1 and scr=no may fail with the message:
 *** USER FATAL MESSAGE 1126 (GNFIST)
     DMAP MODULE DISUTIL  IS ATTEMPTING TO OUTPUT DATABLOCK      201 NAME = EPT 
    , WHICH ALREADY EXISTS.
     USER ACTION: DELETE THE DATABLOCK, OR USE FILE EPT=OVRWRT

Avoidance:  Insert following DMAP alter:

compile desopt
alter 'delete.*scstm,pval,epta'
delete /ept,geom2,geom3,geom4,mpt $
endalter

1-64550902     2008.0.0 (MD R3)      SOL 600 - Marc translator error with CWELD/PWELD formulation

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     2008.0.0 (MD R3)      Aeroelastic Analysis - SPLINRB, SPBLND2 - SFM 3007 (GI)

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     2008.0.0 (MD R3)      Modal Frequency Response - B2PP - Wrong Answers

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)      ADAMSMNF - Fluid in a tank gives wrong ‘Global body properties’

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."

 *** USER FATAL MESSAGE 315 (IFPDRV)
     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 =        0 (0:First Line, >0: Continuation Lines)                

           J+1 =        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)      Optimization/Design Sensitivity - DESGLB, 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     2008.0.0 (MD R3)      Documentation/QRG - SOL 600 - PARAM, MARCOFFT

The QRG documentation for PARAMETER MARCOFFT references a PARAM "MOFFOCRE"   
this should be  "MOFFCORE".

1-65037789     2008.0.0 (MD R3)      Documentation/QRG - SOL 600 - PARAM, MOFFCORE

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  when "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 MASS 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)      Frequency Response - MODESELECT - Incorrect labels for PFMODE and PFPANEL

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-65390757     2008.0.0 (MD R3)      MDACMS - acoustics, modeselect(fluid)  -  UFM 1126 for PHFAHX

In an mdacms acoustic run using sol 111 the following error message can occur 
when modeselect(fluid) requests a subset of the fluid modes:

*** USER FATAL MESSAGE 1126 (GNFIST)
     DMAP MODULE PARTN    IS ATTEMPTING TO OUTPUT DATABLOCK      201 NAME = 
PHFAHX  , WHICH ALREADY EXISTS.

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)      Documentation/QRG - SOL 600 Continue option is incorrect

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)      [KCE:3039] Optimization/Design Sensitivity - DSAPRT 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 SFA 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-65937261     2008.0.0 (MD R3)      SOL 400 - BCONTACT - Position control of rigid body is incorrect

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)      Numerical Methods - DCMP - Signal 11, Segmentation Violation

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-66013381     2008.0.0 (MD R3)      SOL 600 - Marc's parameter option LUMP will 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   3001 HAS OCCURRED IN ROUTINE GREAD

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   3001 HAS OCCURRED IN ROUTINE GREAD   , FILE INDEX =            
0.

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)       Optimization/Design Sensitivity - DRSPAN, 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 entries 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:
*** USER WARNING MESSAGE 4193 (DPD7)
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)      Aeroelastic Analysis - SPLINE, SPRELAX, SPBLNDi - Incorrect Results

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)      Acoustic Analysis - GP5 issues UIM 6207 with null method type

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)      Dynamic Analysis - MCFRACTION output incorrect when MODESELECT used

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)      Acoustic Analysis - PFMODE case control commdand STRUCTMP keyword

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     2008.0.0 (MD R3)      Acoustics - CHACAB - Incorrect mass for 16 node element

The mass matrix for the 16 node CHACAB acoustic barrier element is not correct.

1-66624921     2008.0.0 (MD R3)      Eigenvalue Analysis - NLRSFD - UFM (DPD4) for entry that should be ignored

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     2008.0.0 (MD R3)      SOL 600 -  ISTRESS not honored - Wrong Answers

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)      Optimization/Design Sensitivity - DSAD - 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)      Connect Elements - CWELD, CFAST, CQUAD4, CQUAD8 - UFM 7632 (EWLDPD)

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.
 ^^^ USER   WARNING MESSAGE 9031 (ERRPH1)
 ^^^ NOGO ENCOUNTERED IN SUBDMAP    SEMG

1-66916611     2008.0.0 (MD R3)      Optimization/Design Sensitivity - ECHO NEWBULK -  Incorrect punched bulk data

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)      External Superelements and Acoustics -  C-set - SFM 6144 (PARTN1PR)

An external superelement creation with an acoustic cavity and C-set will result 
in SFM 6144 (PARTN1PR):

*** SYSTEM FATAL MESSAGE 6144 (PARTN1PR)
     THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. 
 SPECIFICALLY:
     The number of columns in KOA is not equal to the number of rows in the 
column partitioning vector VFT
     User Information:  Size of input matrix and partitioning vectors:
                        KOA     :  Rows=  4443394 by   Cols=     2561
                        VFT     :  Rows=      562
                        VFO     :  Rows=  4443394

Avoidance:    Insert the following DMAP alter:

compile semr3
alter 'vfo',''(2)
partn    koa,vafs,vofs/,,,kotf/1 $
endalter

1-66953461     2008.0.0 (MD R3)      SOL 400 - RIGID=LAGRANGE - SFM 4370 (SDCPRF)

SOL 400 with RIGID=LAGRANGE 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-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).

 *** 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.

1-67273981     2008.0.0 (MD R3)      Nonlinear Statics - ANALYSIS=HOT2COLD, scr=no - UFM 1126  (QQGNI)

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)      Complex Eigenvalue Analysis - HESS - Inconsistent Results

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    104     CLAN                                                    +EIGC
+EIGC   1.0     0.0      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)      Optimization/Design Sensitivity -  PBRSECT/PBMSECT may fail in DOM9

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)      Documentation/QRG - CBAR, CBEAM OFFT field - Incorrect example

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 entries 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)      Documentation/QRG - OPGEOM parameter description incorrect

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-67750169     2008.0.0 (MD R3)      Elements - STRAIN, CTRIA6 -  Null Strain Output

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)      SOL 600 - CBEAM - Orientation does not translate properly

SOL 600 does not translate beams whose orientation references other than the 
basic coordinate system correctly.

1-67780355     2008.0.0 (MD R3)      SOL 600 - Translation of MAT9 thermal expansion coefficients is incorrect.

In SOL 600 the translation of MAT9's thermal expansion coefficients is 
incorrect.

The old and new mapping is as follows:

                        New      Old
            α11       A1        A1
            α12       A4        A2
            α13       A6        A3
            α22       A2        A4
            α23       A5        A5
            α33       A3        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:

*** SYSTEM FATAL MESSAGE 6144 (MERGE1PR)
     THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. 
 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
     User Information:  Size of input matrices and partitioning vectors:
                        MQQ     :  Rows=      116 by   Cols=      116
                        VFS     :  Rows=        2      no. of non-zeros=        
1 no. of zeros=        1

1-67870768     2008.0.0 (MD R3)      GPFORCE - SET - UWM 2354 (GPFDR), NERROR w