This file contains all errors corrected since the release of MSC.Nastran 2004.0.0 That is all errors corrected in 2004.0.1-2004.5.0 and Version 2005.0.0 6378 2004.0.4 Element - GENEL - UFM 316 If the [S] matrix is left out (to be generated automatically by MSC/NASTRAN) when using the GENEL element, then {ud} must contain six and only six degrees of freedom. This fact is documented in the MSC/NASTRAN Quick Reference Guide under the GENEL entry description. However, if less than six degrees of freedom are defined when using the Z option, then the following unclear error messages is issued: USER FATAL MESSAGE 316 (IFPDRV) ILLEGAL DATA ON BULK DATA CARD GENEL x SORTED CARD COUNT = y On the other hand, if the K option is used, no error message is issued. The job most likely fails downstream with other error messages. Avoidance: If the [S] matrix is to be generated automatically by MSC/NASTRAN, define six and only six degrees of freedom for the {ud} vector. 6521 2004.0.4 Nonlinear Analysis - TABLES1 - UFM 2076, Poor Message In nonlinear analysis, USER FATAL MESSAGE 2076 is issued if the MATS1 entry is type PLASTIC and the slopes of the first two segments of the stress-strain curve on the referenced TABLES1 entry are the same. The message: USER FATAL MESSAGE 2076, ELEMENT 0 REFERENCES TABLES1 4 WHICH IS THE INCORRECT FORM FOR NONLINEAR ELASTIC ANALYSIS does not clearly indicate the problem and incorrectly references element 0. 27833 2005 Documentation - Getting Started with MSC/NASTRAN The "Getting Started with MSC/NASTRAN User's Guide" states that "In any coordinate system, all angular input is in degrees, but output ... is in radians". This statement needs clarification. The "input" refers only to geometric locations. If an angular enforced displacement is specified the input is in radians. 30010 2005 Superelements - BEGIN BULK SUPER, RESTART - SFM 3001 A restart of a superelement problem will result in the fatal message shown below, if the cold start contains superelements defined in the main bulk data section as well as other superelements defined in the partitioned bulk data sections. *** SYSTEM FATAL MESSAGE 3001 (SEP1X ) THE EXECUTIVE FILE 0 DOES NOT EXIST. PROGRAMMER INFORMATION: SUBROUTINE SEPMAB Avoidance: Define all superelements in either the main bulk data section or the partitioned bulk data section, but not both. 34940 2005 Nonlinear Heat Transfer - RADBC, NLITER - SFM 4276, Traceback In the radiation dominate problem, the stiffness term is approximately equal to 4*T**3. Therefore, if the guess at the initial temperature value is too low for the problem, the temperature may rapidly exceed an infinite value and the traceback that follows will occur: Trap encountered: SIGTRAP - Trace trap FP overflow Traceback: Offset 0x00000014 in procedure zerod_ Offset 0x00000564 in procedure nrdbcd_ Offset 0x00001124 in procedure nlemg_ Offset 0x00000780 in procedure nliter_ Offset 0x00000088 in procedure xsem15_ Offset 0x00000990 in procedure mainal --- End of call chain --- Avoidance: Make a better estimate of the initial temperature on the TEMPD bulk data entry. In general it is safer to have a very high initial temperature than too low The deck with default temperature=0.0 ran to the end without errors on v2005t1 of AIX and LINUX platforms. 35314 2004.5 Buckling Analysis - Insufficient memory - SFM 3001,1015, Out of range, Error 924 I tested this example and it runs now in V2004.5. We cleaned up a lot of things in this area recently. PJS 24may2004 In a buckling analysis and possibly other eigenvalue solutions, if insufficient memory is allocated, then depending on the machine and number of cpus requested, the job may fail with any one of the following unclear messages: 1. *** SYSTEM FATAL MESSAGE 3001 () THE INPUT DATA BLOCK IN POSITION xx DOES NOT EXIST 2. *** SYSTEM FATAL MESSAGE 1015 (GBKMGR) PHYSICAL FILE NOT FOUND IN FILE ASSIGNMENT TABLE BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGR , FILE INDEX (FILEX) = 0 STATUS = 0 3. BIORD ERROR - FILX = 0(00000000 HEX) OUT OF RANGE BIOMSG: ERROR 924 HAS OCCURRED IN ROUTINE IONAST , FILE INDEX (FILEX) = 0 BIOWRT ERROR - FILX = 0(00000000 HEX) OUT OF RANGE 0*** SYSTEM FATAL M 37038 2004.0.5 Nonlinear Analysis - NLTRD2 - Poor Performance in Unsymmetric Decomp The nltrd2 module may exhibit poor performance while performing an unsymmetric decomposition. Avoidance: The following dmap alter will allow a factor of four performance improvement. compile nltran alter ' kjjnl, ' trnsp kjjnl/kjjnlt $ add5 kjjnl,kjjnlt,,,/xxx//-1. $ norm xxx/////1/s,n,xnorm $ if ( xnorm<=1.d-6 ) modtrl kjjnl////6 $ endalter 37642 2004.5 Restarts - CBUSH, CAABSF, GMINTS, GMINTC - SWM 2072 If a model contains CBUSH elements, then upon RESTART SYSTEM WARNING MESSAGE 2072 will be issued by the RESTART module when it compares the GEOM2 data block. A similar error can occur if the model contains CBEND, CAABSF, GMINTS, or GMINTC entires. Avoidance: No avoidance is necessary, ignore the message. 37969 2005 Superelements - Poor Message, UFM 6790 (SEPO21) UFM 6790 shown below is output when a list superelement has no points that can be identified as boundary points. The fatal message is followed by table print which may be ignored. *** USER FATAL MESSAGE 6790 (SEPO21) THE FOLLOWING SUPERELEMENTS ARE DETACHED: 1 3 62000000007 52000000008 212000000002 222000000003 232000000004 242000000005 252000000006 61101529088 71102053376 81102577664 91103101952 101103626240 11 22000000001 42000000007 52000000008 212000000002 22 2000000003 232000000004 242000000005 252000000006 -1 0 0 0 0 0 I believe I fixed this message during 1-4266901 ACMS issues. kkk 38308 2005 Heat Transfer Analysis - CHBDYE, QUAD4 - UFM 6285 If a heat transfer analysis attempts to calculate view factor from the edge of plate elements using CHBDYE with sides from 2 to 5, then you will get UFM 6285 Avoidance: Define the line segment with CHBDYP, LINE boundary elements. 110595 2004.0.3 Superelements - SELOC, POINT - UFM POINT entires can not be used to locate a superelement (on the SELOC entry). If attempted the run will fail. Avoidance: User GRID entries instead of POINT entries. 1-3751401 2004.0.5 Post Processing - param,post,0 - Patran can not view postprocess results in the xdb If a linear heat transfer analysis is followed by a stress analysis in SOL 101, the Patran can only view the temperature output and can not view the displacement output from the xdb. Avoidance: There is no avoidance. 1-4266901 2004.0.4 Distributed Memory Parallel - SPCD, DAREA - Wrong Answers for Frequency Response Sol 111 DMP returns incorrect responses for the responses for all slave processes when both SPCD and DAREA/LOAD type subcases are mixed within same run. 1-5204241 2004.0.5 Heat Transfer - VIEW - Poor Efficiency-unsymmetric decomp In nonlinear heat transfer solution with view factor calculations, unsymmetric decomp is unnecessarily used. Since all the matrices are symmetric, sparse symmetric decompositon should be used by default. Unsymmetric decomp requires twices the memory to run and frequently will encounter UFM 6136, insufficient core for numeric phase of sparse decomposition. Avoidance: Set NASTRAN SYSTEM(209)=0 This forces the unsymmetric decomposition with active columns which requires less memory to run as compared to the newer sparse unsymmetric decomp. dmap avoidance: using symmetric solver SOL 153 compile nlstatic list noref alter 'IF ( DCMPKLLT ) DCMP' (1,-1)$ modtrl kllrh////6/$ CEND Mike, Please fix it from the DMAP level. Set the default KLLRH to be symmetric, and set it to unsymmetric if either CONVM exists or RGG is unsymmetric. -Jenny -------------------------------------------------------------------------------- --------- Jenny, I feel that the RMG2 module should be fixed to make KGGPNL symmetric if RGG is symmetric and no CONVM exist--instead of DMAP. The RMG2 module has all the necessary info to make this decision. Mike -------------------------------------------------------------------------------- -------- The DMAP has been fixed. Jenny should proceed with the RMG2 fix. Mike 1/8/04 Dan, please verfify the fixes. Jenny 1/15/04 1-5884049 2004.0.6 Heat Transfer Analysis - CHBDYG, PARAM,CHECKOUT - SIM 6296 (EMGPOM) Heat transfer analysis, SOL 153, with CHBDYG elements and PARAM,CHECKOUT,YES results in SYSTEM INFORMATION MESSAGE 6929(EMGPOM) for every CHBDYG element. This message is misleading and does not indicate any problems with the model. 1-6155301 2005 Transient Analysis - TRLG - Enforced Acceleration gives poor answers An enforced acceleration problem may exhibit strange behavior due to the mixed precision computations in the TRLG module (specifically in the TRLGCD subroutine). 1-6519201 2005 Nonlinear Analysis - RESTART, TEMP(LOAD) - UFM 9086 Nonlinear analysis restarts (SOL 106) that change the thermal loads may fail with the following fatal message: USER FATAL MESSAGE 9086 (GETLOOP) PARAM, LOOPID, 1 DOES NOT CORRESPOND TO A VALID LOOP IDENTIFICATION NUMBER. Avoidance: In the restart deck replace: ASSIGN master='_____.MASTER' RESTART,version=1,keep with: ASSIGN x='______.MASTER' dblocate logi=x and insert the DMAP alter: compile nlstatic alter 'rstrt=','' rstrt=true $ endalter 1-8789951 2004.0.3 Large Models - Large Models with many rigid elements may fail with SWM 2072 (GP4) Large Models with many rigid elements may fail in GP4 with the following message: SYSTEM WARNING MESSAGE 2072 (GP4) CARD TYPE 7201 NOT FOUND ON DATA BLOCK. 0FATAL ERROR 1-9391501 2004.0.3 Composites - PCOMP - Large Model, Wrong Answers Large models with composite elements that have a large number of plies may encounter SYSTEM WARNING MESSAGE 3008 indicating that insufficient memory exists in STRSORT. The job may continue and can give bad results with incorrect element numbers and/or asterisks indicating an overflow in the ply number field. Andrew, Can you please provide a testdeck that demonstrates this problem. Hemant 1-9638401 2004.5 Nonlinear Buckling Analysis - Lanczos - Infinite Loop in READ The READ Module may go into an infinite loop for non-linear buckling model when using the Lanczos method. 1-9754740 2004.5 DMAP - Poor Message, BIOMSG: ERROR 3001 A dmap that is missing a "/" such that the first parameter is in the output slot failed with the message below which gives no indication of the problem. BIOMSG: ERROR 3001 HAS OCCURRED IN ROUTINE FREAD , FILE INDEX (FILEX) = 0 Avoidance: Correct the problem dmap statement. 1-10183311 2004.0.4 Optimization/Design Sensitivities - DRESP2 - Wrong Sensitivities for DRESP2 that use FUNC The sensitivities of DRESP2 entries that use the FUNC feature in place of a DEQATN and contain DVxRELy or DNODE data are incorrect for all but the last design variable. Avoidance: The FUNC feature cannot be used for DRESP2 entries that include DVxRELy or DNODE data. Use the EQID instead. 1-10220502 2004.0.3 Optimization/Desgin Sensitivity - PBEAM - Incorrect Punch Output, UFM 315 (IFPDRV) SOL 200 punches designed PBEAMs but when they are used as input to nastran the run fails with the message: *** USER FATAL MESSAGE 315 (IFPDRV) FORMAT ERROR ON BULK DATA ENTRY PBEAM Nastran incorrectly writes mid-station information with SO=NO on PBEAM. Avoidance: Change SO to YES or remove mid-station information. 1-11794442 2004.0.3 Nonlinear Analysis - RFORCE - SFM 4276 EC 1305 In nonlinear analysis with follower forces, module EMAKFR fails to recognize that there can be more that one RFORCE entry referenced to a single grid point. If this condition exists the run will fail with SYSTEM FATAL MESSAGE 4276 ERROR CODE 1305 ENDPUT2. Avoidance: Adding param,followk,no avoids the fatal message but also turns off follower forces which will affect results. RFORCE entries must otherwise be combined so that there is only one entry per grid point. 1-11981265 2004.5 Nonlinear Analysis - CTETRA(10) Yields Wrong Nonlinear Stress Output at grid points The nonlinear TETRA(10) element does not extrapolate the Gauss point stresses to the grid points correctly. In one analysis the nonlinear equivalent stress output for a plastic analysis with TETRA(10) elements exceeded the yield stress value at grid points but the same analysis with HEXA(8) elements did not exceed the yield stress. 1-12488007 2004.5 Static Analysis - PARAM,INREL,-2 - Wrong answers If PARAM,INREL,-2 is specified but the model has no mass then the run will not fail and meaningless results may be obtained. Avoidance: Specify mass. 1-12738305 2004.5 Distributed Memory Parallel - SFM 7796 (DFMAM) Large dmp models may fail with the following message: *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN) DECOMP ORDERING METHOD CHOSEN: BEND, ORDERING METHOD USED: BEND *** SYSTEM FATAL MESSAGE 7796 (DFMAM) THE MAXIMUM INTEGER VALUE IS ABOUT TO BE EXCEEDED. USER INFORMATION: THE MAXIMUM INTEGER NUMBER ALLOWED ON YOUR MACHINE IS 1073741823. HOWEVER, DFMAM NEEDS TO DO THE OPERATION NFR*(NFR+1) WHERE NFR = 34851. USER ACTION: USE A DIFFERENT RE-ORDERING SCHEME VIA SYSTEM(206), OR REDUCE THE SIZE OF YOUR MODEL. Avoidance: There is no avoidance. 1-12774307 2004.5 Postprocessing - PARAM,POST,0 - PCOMPG: xdb results not readable by MSC.Patran. XDB results for elements that reference the PCOMPG entry are incorrect when read into MSC.Patran. The first results layer does not even exist, and subsequent results appear incorrect. XDB support for PCOMPG will be added when PATRAN supports the PCOMPG property type. April 15, 2004: problem still exists on Patran v013-015. bdf file attached. The avoidance is to use an accending identification sequence for the ply enumeration, although this might be inconvient and restrictive. 1-12982305 2004.0.3 Optimization/Design Sensitivity - DEQATN - UFM 224, NUMGT and LTOI functions A DEQATN containing LTOI and/or NUMGT functions may fail with the following error message: USER FATAL MESSAGE 224 (PRERMM) MIXED MODE USAGE BY THE ARITHMETIC OPERATOR IS INVALID DURING DEQATN EQUATION PROCESSING. Avoidance: In the problem deck the following equations in the deqatn entry had to be changed from; D1 = .25 + .03125*REAL(1 + LTOI(NUMGT(T1,.500))) + .03125*REAL(1 + LTOI(NUMGT(T1,.625))) + .03125*REAL(1 + LTOI(NUMGT(T1,.750))) + .03125*REAL(1 + LTOI(NUMGT(T1,1.00))); D2 = .25 + .03125*REAL(1 + LTOI(NUMGT(TC,.500))); to: H1 = REAL(1 + LTOI(NUMGT(T1,.500))); H2 = REAL(1 + LTOI(NUMGT(T1,.625))); H3 = REAL(1 + LTOI(NUMGT(T1,.750))); H4 = REAL(1 + LTOI(NUMGT(T1,1.00))); HC = REAL(1 + LTOI(NUMGT(TC,.500))); D1 = .25 + .03125*H1 + .03125*H2 + .03125*H3 + .03125*H4; D2 = .25 + .03125*HC; 1-13195002 2004.0.4 Acoustic Analysis - MAT10 - Wrong Answers in SOL 108 with Structural Damping Acoustic analysis in SOL 108, direct frequency response, will produce wrong answers when MAT10 entries specify GE damping. Avoidance: Insert the following DMAP alter: compile gma nolist noref $ alter 'if ( acsyml','' $ if ( acsyml and (app='tranresp' or soltyp='modal') ) then $ endalter 1-13206002 2004.0.3 Acoustics - METHOD(FLUID) - UWM 8592 (REIG), UFM 3032 (READ) When a fluid/structure model is run in SOL 103, the user is supposed to be able to select structure mode ouput or fluid mode output or both by including one or both of the following case control commands in a subcase: METHOD(STRUCTURE)=m METHOD(FLUID)=n But when METHOD(FLUID) is used by itself, the following error occurs: *** USER WARNING MESSAGE 8592 (REIG) THE METHOD RECORD IN CASE CONTROL IS MISSING OR INCORRECT. THIS WILL CAUSE THE FOLLOWING FATAL ERRORS. USER ACTION: PUT A METHOD ENTRY IN CASE CONTROL WHICH POINTS TO AN EIGR, EIGRL, OR EIGB RECORD IN BULK DATA. *** USER FATAL MESSAGE 3032 (READ) UNABLE TO FIND SELECTED SET ( 0) IN TABLE (EED ) IN SUBROUTINE (REIG). Avoidance: Also include a fake METHOD(STRUCTURE) pointing to a different EIGRL bulk data entry that only requests a single structure mode. Then ignore the first mode output which is a structural mode. 1-13233601 2004.0.4 Elements - CGAP - UFM 2025, Coordinate System Field not sufficiently tested in IFP As documented in the Quick Reference Guide, the CID field of CGAP must contain an integer or blank. However if this requirement is violated and 0.0 is entered, the basic coordinate system is taken. In the case of a real value bigger than zero is entered UFM 2025 will be issued indicating the coordinate system could not be found. 1-13251205 2005 Optimization/Design Sensitivity - PCOMP - Incorrect punched pcomp entries Solution 200 may produce incorrect PCOMPs entries in the punched output when the PCOMP LAM field is set to "MEM" in the original deck. The generated punched PCOMP entries may have a blank MEM field. Another problem with punched PCOMP entries that may be encountered is Ctrl-X in the SOUT field. Avoidance: Edit the punched outut to correct the problem pcomp entries. 1-13288001 2004.0.5 Optimization/Design Sensitivity - Missing DESVAR entries may not be detected With the addition of the DESVAR case control command in the 2004 release, a hole has been opened that may result in a user input error going undetected. If all the DESVAR's referenced on a DVPREL1 or DVPREL2 entry do not exist, the DVPREL1 or DVPREL2 is discarded on the assumption that the referenced DESVAR's have not been selected by the DESVAR case control command. A check needs to be inserted if the referenced DESVAR exist in the input deck and a USER FATAL MESSAGE should be issued if they do not. 1-13314303 2004.0.4 Acoustic Analysis - ACMODL - SFM 6144 (PARTN1) Acoustic analysis with fluid to structure coupling may fail with the message: SYSTEM FATAL MESSAGE 6144 (PARTN1) THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY: The number of rows in VAXF is not equal to the number of rows in the row partitioning vector VAXF1 User Information: Size of input matrix and partitioning vectors: VAXF: Rows= 4059339 by Cols=1 VAXF1: Rows= 4040027 Avoidance: Apply the following dmap avoidance: compile mmfind1 alter 'partn vaxw,,r',''(,1) endalter 1-13341101 2004.0.3 Cyclic Symmetry Analysis - ESE - Missing Output Element Strain Energy (ESE) output may be missing in cyclic symmetry analysis. 1-13372104 2004.0.3 DMAP - WHERE clause references undefined parameters A where clause in a dbview statement that references a parameter that is not defined in the current subdmap will always be evaluated as false and no warning message will be issued. 1-13459501 2004.0.6 Miscellaneous - ADAMSMNF - Cray Does Not Support Adams MNF The Cray SV1 release of MSC.Nastran 2004.0 does not support the creation of an MSC.Adams modal neutral file (mnf). The ADAMSMNF Case Control command wwill result in the traceback shown below: Beginning of Traceback: Called from line 42 (address 12026636a) in routine 'TRBK'. Called from line 40 (address 76375d) in routine 'RECOVR'. Called from line 112 (address 54204c) in routine 'sysrcv'. Called from address 11512176a in routine '__handlr'. Called from address 12166657a in routine 'findmemarea'. Called from line 4543 (address 12171173a) in routine 'removememarea'. Called from line 4501 (address 12171076d) in routine 'releasememory'. Called from line 1229 (address 12163766c) in routine 'Release_Memory'. Called from line 464 (address 13372526d) in routine 'MNF_CreateModeFile'. Called from line 575 (address 13373114c) in routine 'MNF_SetModeVec'. Called from line 681 (address 13254356b) in routine 'MNF_SET_MODE_SHAPE_VEC'. Called from line 142 (address 13231560d) in routine 'AFSCMS'. Called from line 528 (address 13202711d) in routine 'AFGMNF'. Called from line 136 (address 13201120c) in routine 'XSEM16'. Called from line 133 (address 53323d) in routine '$SEGCALL'. Called from line 133 (address 226002b) in routine 'XSEMDR'. Called from line 66 (address 62003b) in routine 'NASTMON'. Called from line 379 (address 1372d) in routine 'MAINAL'. Called from line 343 (address 53300d) in routine '$SEGRES'. Called from line 343 (address 10124663d) in routine '$START$'. End of Traceback. 1-13476801 2004.0.3 Acoustic Analysis - AGG - Add punch option for AGG Matrix Advanced Acoustics needs to be able to punch the AGG matrix for re-use. PARAM, AGGPCH has been added to perform this function. 1-13483901 2004.0.3 DMAP - COMPILE - To many IF-THEN-ELSE statements cause ENDI array to overflow A user dmap with too many if-then-else clauses will overflow the ENDI array and fail during compilation. Avoidance: Substitute multiple if statements or break up the subdmap into smaller subdmaps. A 1-13494001 2004.0.1 Postprocessing - Windows outputs new op2 format by default The MSC.Nastran 2004 release supports a new op2 format. The delivery was suppose to be set the default in the nastran.lcl file as the old format but the Windows delivery does not. This may cause prior releases of Patran and other post-processors that do not know how to read the new format to fail. Avoidance: Add the following line at the top of ../i386/nastran.lcl NASTRAN OP2NEW=0 1-13494006 2004.0.3 Buckling - RIGID=LAGRANGE - Job Hangs A buckling job with rigid elements that uses the Lagrange multiplier method RIDID=LAGRANGE may hang during decomposition in the READ module in MSC.Nastran 2004.0.0 on HPUX Itanium. Avoidance: User RIGID-LGELIM 1-13494012 2004.0.3 Miscellaneous - TABLEM2 - Traceback in tab3 MSC.Nastran 2004 may give a traceback in routine tab3 when TABLEM2 entries exist. The problem may be avoided by defining the table in the negative range. l_4buf(0x11fffb038,0x0,0x3ffc01b2e20,0x8,0xc00000007) L. 133 <>(0x3ffc01b2e20,0x8,0xc00000007,0x0,0x3cc73ce704fb7b23) L. 133 <>(0x0,0x3ffc01b7a98,0x1,0x3ffc01b2e20,0x3ffc01b2e20) L. 133 tab3_(0x1,0x3ffc01b2e20,0x3ffc01b2e20,0x8000,0x0) L. 4 hmat1_(0x0,0x0,0x3ffc01b3078,0x80,0x0) L. 4 ehexd_(0x1407f6c1c,0x1407f6c24,0x1407f6c14,0x1407f6c74,0x190000010) L. 4 emgbrd_(0x140ef888c,0x140653378,0x1201c68a4,0x140f185f8,0x140e9947c) L. 4 emgpro_(0x1201c68a4,0x140f185f8,0x140e9947c,0x140e99498,0x12025f9b4) L. 4 emg_(0x154534552,0x120204554,0x454c4544,0x4e474542,0x20202054) L. 4 xsem09_(0x1201bda4c,0x17,0x0,0x100,0x1201b5ccc) L. 4 xsemdr_(0x0,0x100,0x1201b5ccc,0x1,0x1201a2de8) L. 4 nastmon_(0x1201a2de8,0x14100e310,0x190000000,0x2000000,0x1) L. 4 mainal_(0x190000000,0x2000000,0x1,0x0,0x0) L. 149 <>(0x11fffc020,0x0,0x3ff00000000,0x100000001,0x800000) L. 149 <>(0x1,0x11fffe030,0x0,0x11fffe058,0x11fffe070) L. 149 This error is same as quality 1-13320013. It has been fixed on 9/23/03. Verified the fix by running s31076.dat on 6/7/04. 1-13557302 2004.0.3 Optimization/Design Sensitivity - PARAM XYUNIT - Initial Design Variable Information is incorrect The spreadsheet produced with PARAM XYUNIT in a SOL 200 run prints out cells for each design variable that are said to represent : Initial Value, Lower Limit and Upper Limit. The numbers in these cells are actually Lower Limit, Upper Limit and DELX, respectively. User Information: If design optimization has been performed, design variable values are listed at the end of the spreadsheet with the DESIGN VARIABLE HISTORY. If only a design sensitivity has been run, design variable values are not available in the spreadsheet and must be determined from the input or .f06 file 1-13562313 2004.0.4 Optimization/Design Sensitivity - DRESP3 - SFM 3007 (DOPR3) ILLEGAL INPUT TO SUBROUTINE DPR3H2 The message: SYSTEM FATAL MESSAGE 3007 (DOPR3) ILLEGAL INPUT TO SUBROUTINE DPR3H2 will occur in SOL 200 if a DRESP3 references a DRESP2 that does not exist. 1-13568201 2004.0.3 Eigenvalue Analysis - MATGEN An error in the resmodes subdmap may in rare cases cause a job to fail at the MATGEN line below. Avoidance: The line MATGEN ,/MODEPART/NOMODES/0/MAXMODES/ $ should be altered to be: MATGEN ,/MODEPART/6/NOMODES/0/MAXMODES/ $ 1-13574607 2004.5 Miscellaneous - buildsss on Windows - call buildsss.bat not recognized The command to build the sss on the Windows V2001 delivery (msc2001 buildsss) would not work because necessary files were delivered in the wrong directory. Avoidance: copy buildsss.bat.i386 to ..\i386\buildsss.bat copy buildsss.bat.del to ..\nast\del\buildsss.bat Then run the buildsss command as documented. 1-13604401 2004.0.4 Iterative Solver - FRRD1, ITER - Sun Solaris, Received signal 10 SIGBUS The iterative solver may fail in Version 2004.0.0 on 32 bit Sun Solaris systems in frrd1 with the following message in the log file. No other rmessage is output. *** TERMINATING /local/msc2004t2/solaris/analysis.ultra *** Received signal 10 SIGBUS time: command terminated abnormally. 1-13605801 2004.0.3 MAXMIN - Traceback in SDR2 If an analysis contains a MAXMIN request and an attempt is made to perform an XYPLOT of output data that has not been selected for MAXMIN processing, then the job may fail and issue a traceback in in the SDR2 module routine sdr2c2, Avoidance: Either select the output for MAXMIN processing or perform the xyplot in a restart. 1-13620201 2004.0.4 Aeroelastic Analysis - Flutter sensitivities contain incorrect mode id In the print of formatted design sensitivities for flutter responses, the number listed for mode ID is actually the subcase ID. User information: a comparison of the response value listed in the formatted senstivity print and the flutter summary will indicate which mode the sensitivity is being printed for. 1-13639903 2004.0.4 Acoustic Analysis - ACMODL - UFM 3060 If a user who does not have a new acoustic license for MSC.Nastran 2004 executes an acoustic job, the job will terminate with UFM 3060 indicating that an acoustic license does not exist. It was the design intent that users who wanted to choose the old method and run without the new license would have to explicitly modify the ACMODL entry in their decks to select the old CP method. This was the design intent because the old method of interfacing the fluid and the structure only provided good answers for identical meshes. To allow the users to make this selection without modifying their tests, SYSTEM(346)=2, a.k.a. keyword FLSTINT=2, has been added to MSC.Nastran 2004.0.4 in the 2004R2 release so that the user can select the old method in an rc file. 1-13649701 2004.0.4 Performance - Sparse Data Recovery The dmap functions that allow sparse data recovery may be unnecessarily executed in SOL 101 and ANALYSIS=STATICS in SOL 200 when data recovery for the entire model is requested. Avoidance: If data recovery for the entire model is being requested (i.e. DISP=ALL, STRESS=ALL) the best avoidance is to include param,sparsedr,no to completely avoid the additional operations. The following dmap avoidance will allow automatic selection to occur but may not beat V2001 performance for all conditions: compile fdrmgen alter 'call spdr1' return $ compile sedisp alter 'SDR1 USET'(,-1) call genrga uset,goa,gm,vgdr,goq/ rga,rgq/ true/atqset/seid $ dbstatus rga//s,n,norga $ if ( norga>0 ) then mpyad rga,uas,/ugi $ else $ alter 'SDR1 USET' endif $ endalter 1-13679504 2004.0.3 SOL 600 - Dynamic loads specified by DLOAD are not always translated to Marc. For SOL 600, Dynamic loads specified by DLOAD (rather than FORCE, PLOAD, etc) are not always translated to Marc. This particularly happens when DLOAD is the only loading. 1-13686801 2004.0.3 Superelements - EXTSEOUT - Missing Output for external superlements in SOL 109 AND 112 A SOL 109 or 112 assembly run employing an external superelement created using the EXTSEOUT feature does not give displacements, velocities or accelerations for the interior points of the external superelement. Avoidance: For both SOL 109 and SOL 112 apply the following dmap alter. compile super3 alter 'IF ( APP=\'TRANRESP\''(3),'' if ( false ) then $ alter 'IF ( APP=\'TRANRESP\''(4),'' if ( false ) then $ compile sedrcvr alter 'drmh3'(,1) DSAR uls1,,,/uls2,,,,/-1 $ equivx uls2/uls1/-1 $ endalter $ 1-13694401 2004.0.2 Miscellaneous - IA64/Linux - May run with less memory than requested If more memory is requested than is available on a Linux IA64 system, then the job is run with a reduced amount of memory. The job should be stopped instead. 1-13704901 2004.0.3 SOL 600/Implicit Nonlinear - TLOAD2 - Incorrect Loads, Wrong Answers In Version 2004.0.0, SOL 600 loads defined by TLOAD2 entries are incorrect. The equation to calculate the loads has an error. In addition, the TABLED1 that is created is missing every third point. 1-13704904 2004.0.3 SOL 600 - Multiple MATEP materials not processed In SOL 600, multiple MATEP materials are sometimes not processed. 1-13708001 2004.0.3 Optimization/Design Sensitivity - FREQ4 - Possible Wrong Answer or Divide by Zero when NFM=1. If design sensitivity and optimization analysis includes a FREQ4 entry that asks for only a single frequency per "spread," NFM=1, the code attempts a divide by zero and that gives different results, depending on the platform. The AIX traps the error, Linux proceeds and gives answers that are close, but wrong, SGI and HP produce unknown (NaN) numbers that point to an obvious problem. Avoidance: The best avoidance is to use a FREQ5 entry with a single FRi value set to 1.0 Using NFM>1 on the FREQ3 entry also avoids the error. 1-13711524 2004.0.3 Miscellaneous - INCLUDE - .blk files not included. In version V2004 the new output file named "filename.blk" is created for every run which contains sorted bulk data for SOL 200. Thus, the nastran command script renames the existing "filename.blk" to filname.blk.1" during the run. IF the NASTRAN command line option OLD=NO is set "filename.blk" will be deleted. To overcome this problem rename "filename.blk" to "filename.xxx", where "xxx" is anything other than "blk". Avoidance: Avoid using "blk" as a include file name extension. 1-13713263 2004.0.3 Postprocessing/DMAP - PARAM,POST - Incorrect GEOM2X and GEOM3X Output2 data. In MSC.Nastran 2004.0.0 the data written in the OUTPUT2 GEOM2X and GEOM3X data blocks is incorrect. Avoidance: Apply the following dmap alter. compile out2geom alter 'output2 geom2x','' OUTPUT2 GEOM2x,GEOM3x,GEOM4x,geom1x,bgpdtx//0/OUNIT1//OMAXR/ GEOM2 / GEOM3 / geom4 / geom1 / bgpdt / 'geom2'/'geom3'/'geom4'/'geom1'/'bgpdt' $ endalter 1-13732901 2004.0.5 Component Mode Synthesis - CSET, QSET - Wrong Answers Component Mode Synthesis should give exact results if all eigenvalues are included. A small CMS job employing a part SE and CSET reduction and with Q-set data defined in the part SE Bulk Data gives erroneous results if all of the component modes are calculated. Furthermore, different erroneous results are calculated if the Q-set data in the part SE Bulk Data are replaced by an equivalent SENQSET entry in the Main Bulk Data. 1-13760301 2004.0.3 SOL 600/Implicit Nonlinear - Extra Datablocks in op2 file SOL 600 is writng extra datablocks to the op2 file for the initial Nastran 2004 release. Programs such as Medina and Animator may have trouble handling these extra geometry datablocks. Avoidance: This can be avoided by the user employing his own DMAP to control the datablocks written to the op2 file rather than specifying outr=op2 on the SOL 600 entry. 1-13762804 2004.0.4 Installation - Sun Solris64 installation is missing shared object libraries. The MSC.Nastran V2004 installation for Sun Solaris 64 systems is missing shared object libraries. The libraries are needed if the system does not have Fortran compilers installed. These libraries may be downloaded from the MSC.Software web site: http://www.mscsoftware.com/support/software_updates/index.cfm#nastran and at: http://www.engineering-e.com/download/?productid=15 1-13767914 2004.0.3 Optimization/Design Sensitivity - PARAM,DESPCH1,-1 option fails for PBEAM entries When a negative number is specifified for PARAM,DESPCH1 to indicate that small field format is to be used and the analysis model contains PBEAM entries, the job will fial with an error message in the log file. Avoidance: Use a positive number, i.e. large field format. 1-13794801 2004.0.3 Rigid Elements - PARAM,AUTOMSET - SFM 4276 EC 5 in UFBS If the dependent node of an RBE is restrained and PARAM,AUTOMSET,YES is specified, the analysis may fail with the message: *** SYSTEM FATAL MESSAGE 4276 (UFBS2) ERROR CODE 5 PID= 0 *** USER INFORMATION MESSAGE 4276 (UFBS2) Avoidance: Apply the following dmap avoidance: DMAP avoidance is: compile autom alter 'TRNSP RMAL','' $ TRNSP RMAL/RMALTx $ matmod RMALTx,,,,,/Rjunk,RMALTnz/12/s,n,NLnull/1 $ if (NLnull > 0) then $ add rmaltx,RMALTnz/rmalt $ else $ equivx rmaltx/rmalt/-1 $ endif $ endalter $ 1-13817704 2004.0.3 ACMS - ASET1 - ACMS ignores ASET1 data beyond the first entry In ACMS analysis grid points on ASET and ASET1 entries are moved into the residual structure. However if there is more than one ASET1 entry in the bulk data, the ASET1 data beyond the first entry is ignored. 1-13830101 2004.0.3 Miscellaneous - PARAM,CHECKOUT,YES - SFM 3001 (MTRXIN) Jobs using the PARAM,CHECKOUT,YES feature could fail with SFM 3001 from the MTRXIN module if there is a K2GG case control command selecting a stiffness matrix and there is no M2GG command selecting a mass matrix. Avoidance; The error can be avoiding the MTRXIN in with a dmap alter. 1-13860606 2004.0.3 Superelements - MPCF, SPCF - Wrong Answers with Sparse Data Recovery In V2004, the new sparse data recovery can cause errors in the displacement vector for superelements when displacements are requested for only some of the GRID points in the model at the same time as MPCF or SPCF requests are made. This error occurs only in the direct solution sequences; i.e., 101, 103, 108, 109, and 200 with ANALYSIS=DFREQ. Resolution: Either use PARAM,SPARSEDR,NO to deactivate sparse data recovery methods or insert the following alter: COMPILE SPDR1 NOLIST $ ALTER 189 $ DIAGONAL V01S/V01SX/'WHOLE'/0. $ EQUIVX V01SX/V01S/-1 $ ENDALTER $ 1-13860635 2004.0.4 Superelements - MPCF - Wrong Answers with Sparse Data Recovery In V2004, in a superelement, if MPCF output is requested for only some of the GRID points of the model, the MPCF output may be in error if sparse data recovery is active, i.e. PARAM,SPARSEDR,YES (default). In addition, an SPCF output request will be ignored. This error occurs only in the direct solution sequences; i.e., 101, 103, 108, 109, and 200 with ANALYSIS=DFREQ. Avodaince: Use PARAM,SPARSEDR,NO 1-13875001 2004.0.6 Miscellaneous - INPUTT4 - UWM 6445 (INPTT4) A formatted INPUTT4 read for more than one matrix will fail with the following Fortran READ error: UWM 6445 (INPTT4): A FORTRAN FORMATTED READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = ... USER INFORMATION: THE FILE WAS SPECIFIED IN AN ASSIGN FILE MANAGEMENT STATEMENT USER ACTION: VERIFY THE FILE ASSIGNMENT AND AND CONTENTS OR CONTACT MSC.SOFTWARE. VERIFY DATA AND FORTRAN SPECIFICATION. PROGRAMMER INFORMATION: FORTRAN IOSTAT CODE = ... 1-13876601 2004.0.3 Impicit Nonlinear (SOL 600) - MATF Can Only Process One Failure Criteria The SOL 600 MATF entry can only handle one failure criteria instead of three. Avoidance: Enter MATF entry three times. 1-13897501 2004.0.3 Implicit Nonlinear (SOL 600) - MATF - Unnecessary Input All continueation entries and all failure criteria constants are required for the MATF entry even though only the frist constant is needed for the most simple max stress criteria. This needs to be changed so that only those constants required to satisfy the failure criteria chosen need be entered. Thus, for the max stress criteria, only the first entry is required and only the first constant needs to be defined. 1-13915501 2004.0.3 Optimization/Design Sensitivity - PBEAML - Wrong Answers In MSC.Nastran Version 2004 an optimization job will produce incorrect dimentions for an intermediate station or at end B of the PBEAML entry if the following conditions are met: 1. PBEAML entry is used that has SO=NO on other stations, 2. Only end A is designed. 1-13915504 2004.0.3 Optimization/Design Sensitivity - DESPCH, DESPCH1 - UFM 315 (IFPDRV) When an optimization job designs any real value on a CBEAM, CQUAD4 and/or CTRIA3 entry, bad punch output for these entries may be produced leading to UFM315 (IFPDRV) when they are included in a cold restart job. The same job may also fail with traceback of Segmentation Violation on AIX machine. Avoidance: No practical avoidance exists except to manually modifiy the offending entries. Keywords: DESPCH DESPCH1 1-13928902 2004.0.3 Dynamic Response - MCFRACTON, MEFMASS - SFM 4276 (UNPACK) EC31 Modal dynamic response analysis that have multiple subcases that reference the same FREQ set but different DLOAD sets and request modal participation factor output may fail with the following message: *** SYSTEM FATAL MESSAGE 4276 (UNPACK) ERROR CODE 31 PID= 0 Avoidance: A possible avoidance is to define and reference a duplicate set of FREQ data for the second and subsequent subcases. 1-13930009 2004.0.4 Documentation/QRG - SOL400, RIGID=LGELIM - UFM 7615 (MDG2RG) The case control command RIGID=LGELIM as described in the MSC.Nastran V2004 Quick Reference Guide produces the following error because the option should be LNELIM. *** USER FATAL MESSAGE 7615 (MDG2RG) FOR NONLINEAR SOLUTION SEQUENCE, THE CASE CONTORL COMMAND 'RIGID=LGELIM' IS ILLEGAL. USER INFORMATION: THE LEGAL VALUE IS 'LNELIM' OR 'LAGR'. *******ALSO the word CONTROL is spelled wrong.****** For SOL400, the RIGID=LGEL method is not available, therefore a fatal error is issued. The wording 'USER INFORMATION: the legal value is 'LNELIM' or LAGR' is corrected to 'USER INFORMATION: the legal value is LINEAR or LAGR'. Also the word CONTROL is corrected. -- Harry 1-13948931 2004.5 Dynamics/Enforced Motion - SPCD - Excessive disk space and CPU In V2004, enforced motion in dynamics may use excessive disk space and CPU. Avoidance: Insert the DMAP alter in the attachment. 1-13987701 2004.0.3 Spotweld - CWSEAM - UFM 7549, Cannot find projection points for CWSEAM elements The default pcid of CWSEAM elements was not set appropriately. This error results in USER FATAL MESSAGE 7549 indicating that it cannot find projection points for the CWSEAM elements that are projected along the x-axis. 1-13989006 2004.0.2 Miscellaneous - XNASTRAN - Error while loading shared libraries The XNASTRAN interface may fail on some Linux operating systems with the message: "error while loading shared libraries: lib*: cannot open shared object file: No such file or directory." Avoidance: Use the nastran command. 1-14063502 2004.0.4 SOL 600/Implicit Nonlinear - Hyperelastic Element with midside nodes not Properly Mapped to Marc. The hyperelastic CHEXA element with mid-side nodes is not properly mapped to the corresponding Marc element, instead it is mapped to the corresponding 8-node Marc hyperelasic hexa element. The net result is that deformed plots show the mid-side nodes standing still and strange plots results. 1-14116602 2004.0.5 Dynamic Analysis - EPOINTS, M2PP, B2PP, K2PP, SPCD - UFM 1126 for K2GG EPOINTS and enforced motion with K2PP, B2PP or M2PP input may cause USER FATAL MESSAGE 1126 to be encountered. 1-14139801 2004.0.4 Acoustic Analysis/Enforced Motion - SPCD - SFM 6144 (PARTN1) In direct frequency response, sol 108, the new relative enforced motion capability in MSC.Nastran Version 2004 will encounter a matrix incompatibility fatal message when fluid is added to structure. *** USER WARNING MESSAGE 2125 (VEC) MODULE VEC - NZ=0, ONE OR MORE COLUMNS OF OUTPUT MATRIX WILL BE NULL. *** SYSTEM FATAL MESSAGE 6144 (PARTN1) THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY: The number of rows in KAA is not equal to the number of rows in the row partitioning vector VAY The number of columns in KAA is not equal to the number of rows in the column partitioning vector VAY 1-14155701 2004.0.5 Distributed Memory Parallel - DMP - Does not work on Primepower The 32 bit nastran driver program delivered with MSC.Nastran 2004.0.0 under the Solaris achitecture will not work for Distributed Memory Parallel (DMP) on Primepower systems. Avoidance: Download a new driver program from: http://www.mscsoftware.com/support/software_updates/index.cfm#nastran 1-14176601 2004.0.3 Dynamic Analysis - MCFRACTION, SET - Missing Output If the MCFRAC case control command selects a SET that contains an implied thru range, only the first degree of freedom in each of the ranges will be output. The implied thru range is a continous range of degrees of freedom for a grid point as in 969/T1,969/T2,969/T3. Avoidance: An avoidance is to select grid/dof combinations that do not imply thru and use restarts changing the MCFRACTION SET content to recover all of the required data. 1-14180601 2004.0.4 SOL 600 - CQUAD4, CTRIA3 - Variable thicknesses on continuation entry not translated correctly. For SOL 600, thickness specified by continuation lines on CQUAD4 and CTRIA3 entries are not properly translated. There is also a priority conflict between these thicknesses and those specified by the NTHICK option. 1-14186901 2004.0.4 Frequency Response Analysis - SPCD, DPD - SFM 4276 when multiple subcases request different spc sets A frequency response problem involving enforced motion fails with SFM 4276 in the DPD module if there are multiple subcases and different spc sets are selected in the case control. Avoidance: Apply the following dmap alter: compile phase0 alter ' copy yG1\/yG2'(,-1),'' $ create only the first yg2 for dynamics ELSE if ( nskip=1 or app<>'freqresp' ) then $ 1-14186907 2004.0.4 Dynamics - TLOADi, ACSRSE - Negative real values for the DELAY and DPHASE fields - UFM 316 Use of negative real values for the DELAY or DPHASE fields on the ACSRCE or TLOAD1 or TLOAD2 entries results in UFM 316 in the PREFACE module. 1-14191701 2004.0.4 Optimization/Design Sensitivity - DLINK - Incorrect constraints for dependent design varaibles. When an optimization job has specified a DLINK entry, the corresponding DESVAR entry has a blank DELXV field and P2 on the DOPTPRM is set to 4, the constraints for dependent design variables are printed in the f06 file incorrectly. However, these constraints are computed correctly during the approximate optimization. Avoidance: Specify a non=blank DELXV field on the dependent DESVAR entries. 1-14210501 2004.0.4 Eigenvalue Analysis/Acoustics - RESTART - Modes Unnecessarily Recalculated In V2004, if a restart is performed from a SOL 103 run with acoustics, then the fluid modes may be unnecessarily recalculated. Avoidance: Insert the following alter in SOL 103 cold start: compile semodes alter 1 type parm,nddl,i,n,methf $ endalter 1-14222717 2004.0.4 Superelement - RESTART - Unnecessarily Recalcualtes Modes A superelement restart from sol 103 to 112 may unnecessarily recalculate upstream modes for some superlements. Avoidance: Apply the following dmap alter: compile sekmr alter 'endif \$ atsprt'(,-1) kchng=false $ endalter 1-14223905 2004.0.4 Nonlinear Analysis - TEMP(LOAD), QUADR, TRIAR - Wrong Answers Temperature loads for the QUADR and TRIAR elements is not implimented correctly for nonlinear analysis. Avoidance: Use the QUAD4 and TRIA3 elements. 1-14233604 2005 Elements - CQUADR, PARAM,CHECKOUT,YES - Incorrect grid point weight generator output Mass for the CQUADR element is not included in the grid point weight generator results when param,checkout,yes is specified. 1-14251001 2004.0.4 Dynamics - CAXIFi, PARAM,G - Wrong Answers If the old acoustic cavity method (see CAXIFi elements) is selected in SOL 108 or SOL 200 (with ANALYSIS=DFREQ) then PARAM,G will be ignored. Avoidance: Insert the following DMAP alter: compile sedfreq alter 'fonly=','' endalter 1-14251416 2004.0.4 Post Processing/ACMS - PARAM,POST,-1 - Lama datablock missing from op2 file A distributed memory parallel (dmp) ACMS analysis does not write the lama table to the op2 file when param,post,-1 and param,post,ext,yes are specified. This data block is critical for post processing acoustic results and is produced in a serial run. 1-14261401 2005 External Superelements - EXTSEOUT - Missing Output due to sparse data recovery A SOL 103 assembly run employing an external superelement created using the EXTSEOUT feature does not produce the requested output for the external SE. Avoidance: Insert PARAM,SPARSEDR,NO. 1-14267003 2004.0.4 Elements - MFLUID - UFM 4257 (FMXACD) User fatal message 4257 may erroneously appear for virtual mass elements (MFLUID), if the distance between two element centers is exactly equal to the RMAX value from the MFLUID record. Avoidance: An avoidance is to modify RMAX (see MFLUID entry) slightly. It is recommended that the default value always be used, and this error is very unlikely. 1-14273377 2004.0.4 Distributed Memory Parallel (DMP) - FREQ3,FREQ4,FREQ5 - SFM 6833 FREQ3, FREQ4, and/or FREQ5 Bulk Data entries in a DMP analysis may lead to SYSTEM FATAL MESSAGE 6833. Avoidance: Insert the following DMAP alter: compile semfreq alter ' frlgen '(,-1) if ( procid=1 ) then $ disutil lamas ,,,////3 $ else if ( procid>1 ) then $ delete /lamas,,,, $ disutil ,,,,/lamas ///3 $ endif $ procid>1 endalter 1-14286512 2004.0.4 Distributed Memory Parallel (DMP) - SEP1X - Free Floating Grids Cause DMP to Fail in SEP1X In MSC.Nastran 2004.0.3 (released to only one client) a model with free floating grids, meaning grids that are not attached to the structure, may cause dmp jobs to fail. This includes models with grids that are only used as reference points. Avoidance: Set system(294)=2 (which will print the external IDs of those free grids, search for FREE FLOATING, and then remove the grid entries. If the grids were used as reference points, they have to be replaced by coordinates. Grids that are referenced only on a PLOTEL element are not considered free floating, so attaching the reference grids to PLOTELs is another way to avoid the problem. 1-14299201 2004.0.4 ACMS - Multiple USETi,U6 entries not handled correctly. In ACMS, unit load degrees of freedom on the USET1 entry are forced to the residual structure. However, if there are more than one USET1 entry in the input, it only forces the points from the first entry. DOF on subsequent entries are not forced to the residual. This leads to fewer than the desired number of residual vectors when those degrees of freedom are not put into the residual structure by the automatic partitioner. 1-14305003 2004.0.4 SOL 600 - Large Jobs - Insufficient swap space Extremely large SOL 600 jobs may fail on some small computers with a message that indicates that they have run out of swap space. Avoidance: Other than running on a different platform, there is no avoidance. 1-14322801 2004.0.4 Optimization/Design Sensitivity - PARAM,XYUNIT - FORMAT ERROR 103 The error message: FORMAT ERROR 103: A POSITIVE VALUE IS REQUIRED HERE may occur in SOL 200 when PARAM XYUNIT is used to create a CSV file of the optimization results and the number of design variables is 3n+1 where n is any integer starting from zero. To date this behavior has only been observed on Linux platforms. Avoidance: Run on a different platform or add a dummy variable such that the number of variables is not 3n+1. 1-14348401 2004.0.4 Nonlinear Analysis (SOL 400) - MPC, RBEi, RBAR - Wrong Answers For SOL400, the solution will converge to wrong results if there are MPC constraints or linear rigid elements (RIGID=LINEAR) in the model. Avoidance: There is no avoidance. 1-14397204 2004.0.4 SOL 600 - MATTEP - Add General Temperature-Dependent Stress-Strain Curves SOL 600 temperature-dependent stress-strain curves need to be supported for general shapes. At present such curves are limited to scale with the same slopes as the original curve vs temperature. In MSC.Nastran 2004R2 (Version 2004.0.4 and beyond) new options have been added to the MATTEP entry that allows support for general temperature-dependent stress-strain curves in SOL 600. 1-14397207 2004.0.4 SOL 600 - DMIG - DMIG Support added to MSC.Nastran 2004R2 Support for DMIG entries in SOL 600 has been added to MSC.Nastran 2004R2 (Version 2004.0.4 and beyond). 1-14397801 2004.0.4 Elements - CWSEAM - Incorrect Stiffness The hexa type stiffness matrix for the CWSEAM element is computed in the wrong coordinate system and this will lead to an incorrect stiffness matrix and wrong answers. The stiffness should be computed in the basic coordinate system instead of element coordinate system. 1-14405601 2004.0.4 Static Analysis - RBE3 - Lagrange RBE3 may give wrong answers The Lagrange RBE3 will give wrong results if the reference dof=123 for SOL 101. Avoidance: Specify 123456 for the reference degrees of freedom. 1-14405604 2004.0.4 SOL 400 - CBEAM, RBAR - CBEAMs with RBARs cause diverging solution If CBEAM elements are used with RBAR elements in SOL400 the solution may diverge. 1-14405901 2004.0.4 Restarts - DBLOCATE - UFM 477, Timestamp Error The following dblocate restart run will result in USER FATAL MESSAGE 477. Run1 : create a database. Run2 : dblocate, copy the contents of run1 and restart creating run2 database. Delete run1's database. Run3 : dblocate run2's database. This causes a UFM 477 error saying there is a timestamp error on run2.dball. Avoidance: 1) Use autoasgn=3 in run3 and manually assign the dblocated database, or 2) I did a dbdict, endjob directly into run2's database (dbs=run2) before deleting run1's database. This also avoids the error. 1-14412401 2004.0.4 SOL 600 - GRAV, CONMi - No gravity loads for concentrated masses SOL 600 gravity loading does not produce any loads for the concentrated masses (CONMi) in the Marc input deck. 1-14461909 2004.0.4 Transient Analysis/Enforced Motion - STATSUB - UFM 3046 in TRD1 If enforced motion is specified and STATSUB is also requested in SOL 108 or 109 then the job may fail with USER FATAL MESSAGE 3046 Avoidance: Insert the following alter: compile sedtran alter 'call autosprt' else $ equivx lll/lyy/-1 $ ompile sedfreq alter 'call autosprt' else $ equivx lll/lyy/-1 $ endif $ endalter 1-14469102 2004.0.4 ACMS - UFM DISJOINT SUPERELEMENTS EXIST Large ACMS jobs may fail incorrectly with a message that complains about the existence of "DISJOINT SUPERELEMENTS". Avoidance: There is no avoidance. 1-14480201 2004.0.4 Rotor Dynamics - ROTORG - Unbalanced load in rotor dynamic module In rotor dynamic analysis , if multiple unbalanced loads are applied to points not in the a-set then loads will be ignored and wrong answers will result. Avoidance: If multiple unbalanced loads exist, then make sure that all load points are in the analysis(a) set. 1-14485401 2004.0.4 SOL 600 - BEGINBULK Causes Failure in trelpl.F SOL 600 jobs may fail with an error in trelpl.F if BEGINBULK rather than BEGIN BULK is entered. 1-14523741 2004.0.5 Post Processing - PARAM,POST,0 - Missing Results in xdb A combine heat transfer and thermal stress analysis with param,heatstat,yes will not write both the heat transfer and thermal stress results to the xdb or op2 file for postprocessing. If using param,post, 0 to write results to the xdb file, only the temperature result are obtained. If using param,post,-1 to write the results to the op2 file, only the thermal stress result are obtained. Avoidance: Apply the following dmap avoidance; compile phase0 alter 'output2'(,-1) if ( not(heatstat='yes' and aprch=' ') ) then $ alter 'output2' endif $ alter 'ELSE IF ( (OGEOM=','' ELSE IF ( (OGEOM='YES' OR OGEOM=' ') AND not(dmpop2) and not(heatstat='yes' and aprch=' ') and ((POST=-1 or patplus='yes') AND PATVER>=3.) ) THEN $ endalter 1-14533901 2004.0.4 Optimization/Design Sensitivity - NEWBULK - Incorrect/Missing Bulk Data Echo Output The NEWBULK describer on the ECHO case control command enables punching of a complete unsorted bulk data deck at the end of a SOL 200 run with updated design model data. If the original input deck contains design model data that has been input in free field form and has a continuation that has a comma in column one, the updated design model data is followed by an incorrect punch of the continuation line. Also, if the user has placed comments at the end of a line of data that is included in the design model, the comment does not get written to the punch file. Avoidance: A blank can be inserted in front of the comma on the continuation line and the correct behavior will result. Comments that are at the end of design model entries must be moved to their own line if they are to be retained. 1-14556901 2004.5 Matrix Methods - param,inrel,-2 - Lagrange Multipliers, Incorrect matrix to factor diagonal messages When Lagrange Multipliers are used, as in param,inrel,-2, calculations in SOL 101 and several other places, large matrix to factor diagonal matrix ratios may be prined out and they may be in error. Avoidance: If the "MATRIX/FACTOR DIAG. RATIO" is identical to the "MATRIX DIAGONAL" they can be safely ignored. If the run fatals, param,bailout,-1 can be used to avoid the fatal error. 1-14576201 2004.0.4 Distributed Memory Parallel - ACMS May Produce Wrong Answers in Acoustics Distributed Memory Parallel (DMP) with ACMS may produce wrong answers in Acoustics. Avoidance: Use serial ACMS. Contact MSC for DMAP avoidance. 1-14593609 2004.0.4 SOL 600 - PCOMP - Composites not Translated to Marc Correctly Composites, PCOMP entries, are not tranlated by SOL 600 to the marc input file correctly. 1-14595809 2005 Rotor Dynamics - UNBALNC, transient response, WTMASS, NLLOAD, imbalance PARAM,WTMASS does not change the load vector (NLLOAD output) leading to wrong answers. 1-14607302 2004.0.5 Performance - EIGRL, READ - When use_aio is on, incorrect cpu reporting leads to poor performance When use_aio=yes is specified in a Nastran 2004.0.0 on HPUX 64 platforms, it may cause inaccurate and even negative cpu usage. This may cause additional shifts in Lanczos and lead to poor performance. This problem has been fixed in Version 2004.0.5 and later system by linking against corrected libraries from HP. 1-14626001 2004.0.5 Aeroelastic Analysis - UFM 5259 (MAKAUMD) In aeroelastic analyis UFM 5259 may be issued without any text. Avoidance: The text should read: *** USER FATAL MESSAGE 5259 (MAKAUMD) UXVEC BULK DATA ENTRY WITH ID xx INVOKED BY A AEPRESS BULK DATA ENTRY DOES NOT EXIST. 1-14639801 2004.0.4 Optimization/Design Sensitivity - DVPREL1, PBUSH - No Warning Message Issued When an optimization job designs a PBUSH property using a positive FID on a DVPREL1 entry that is not allowed, the program does not stop the process. The subsequent result may not be reliable. Avoidance: Use the property name instead. Such as K1 or B4. 1-14651801 2004.0.5 SOL 600 - RBE3 has a limit of about 450 continuation cards For SOL 600 the RBE3 has a limit of about 450 continuation entries. Some models mave large RBE3's that exceed this limit. For such models, a memory over-run occurs and bad data is written to the appropriate section of the Marc input deck 1-14651804 2004.0.5 SOL 600 - TEMP(LOAD), TEMP(INIT) - Performance Problem SOL 600 has a performance problem for large models with thermal loading. This occurs when TEMP(INIT) and TEMP(LOAD) are entered. On some computer systems, such as Linux, the performance penalty is very small. On others, such as HP, the performance penalty is large. This is caused by I/O that can be performed in a different way. For the large where this error was discovered, the run took more than 60 minutes to create the model on HP when it should have only take a couple of minutes. The problem has been fixed in Nastran 2004.0.5 on the Nastran 2004r2 cd. 1-14667001 2004.5 Elements - NSM1, PSHELL - Missing mass, Wrong Answers The NSM1 command does not work on shell elements. Avoidance: User the NSM or NSML2 commands. 1-14717802 2004.5 Eigenvalue Analysis - EIGR, GIV, HOU - Poor performance in wilvecd Householder and Givens eigenvalue methods may get poor performance on HP and Linux IA64 systems. procedures. 1-14762201 2004.0.5 SOL 600 - Marc CONTROL block 3a is not supported The SOL 600 Marc CONTROL block 3a is not supported. This was intentional in SOL 600 versions before Nastran 2004.0.5 because some version of Marc did not support it. This is only important if different tolerances for displacment and residual are needed. 1-14763501 2004.0.5 Elements - QUADR - Incorrect Output Coordinate System The default stress/strain output coordinate system for QUADR is not the one defined in Quick Reference Guide. It is the material coordinate system with theta=0.0. 1-14777101 2004.5 Large Problems/Frequency Response - DPD - SFM 4276 (READ) EC 3021 (DPD) Very large SOL 111 jobs may fail with the message: SYSTEM FATAL MESSAGE 4276 (READ) ERROR CODE 3021 (DPD) Avoidance: There is no known avoidance. 1-14779931 2005 Nonlinear Analysis - plasticity - Failure to converge or wrong answers In nonlinear analysis, sol 106, Nastran does not handle a hardening slope change after the 1st hardening slope in plasticity analysis. This may lead to a failure to converge or wrong answers. 1-14813801 2004.0.5 Optimization/Design Sensitivity - SFM 6296 (QMATR) Unable to locate datablock dtos2j with The message: SYSTEM FATAL MESSAGE 6296 (QMATR) unaable locate datablock dtos2j attribute dptye: xxxx may occur if the bulk data file contains a mixture of DVPRELi, DVMRELi and DVRELi entries and the DESVAR case control command is used to select a set of design variables that do not includ any of a partcular property type. Avoidance: Either remove the unneeded DVxRELi entries or include a DESVAR that references each property type or apply the folowing dmap alter when DVMRELi's are the unneeded entries and the deck contains needed DVPRELi's and DVCRELi's. A similar dmap can be constructed for other scenarios: compile predom alter 'dopr1 ' message //'protyp = '/protyp $ $ For the case of all the DESVARs referenced on DVMREL1 entries are NOT selected by DESVAR command protyp = 3 $ For the case of all the DESVARs referenced on DVPREL1 entries are NOT selected by DESVAR command $protyp = 7 - 1 $ For the case of all the DESVARs referenced on DVCREL1 entries are NOT selected by DESVAR command $protyp = 7 - 2 1-14817201 2004.0.5 SOL 600 - Not all values for SOL 600 Marc's AUTO INCREMENT are properly translated Not all values for SOL 600 Marc's AUTO INCREMENT are properly translated form NLSTRAT AIxxxxx entries. Avoidance; Other than manually editing the marc input file there is no avoidance. 1-14860909 2004.0.5 Nonlinear Analysis - CBUSH with local coordinate systems cause convergence problems A nonlinear analysis with CBUSH elements with their grid points defined in local coordinate system may have convergence problems. with bushes that have their grid points defined in loc Avoidance: The displacement coordinate systems for points connected by cbush elements in an nonlinear analysis should be the same. 1-14861414 2004.0.6 Rotordynamics - RSPINR, ROTORDR2 - Floating Point Exception or Missing Message If the SPEEDi field is defined incorrectly on the RSPINR entry (e.g., defined as an integer instead of a real), then depending on the machine, the proper error message may not be issued. On some machines, the job may stop without any messages. On other machines, the job may stop with a floating point exception. Avoidance: Correct the offending entry. 1-14895708 2004.5 SOL 600 - CBAR - Null OUTPUT2 file is created when model consists of on CBARs The SOL 600 t16op2 translator (outr=op2 option) requires that elements with stress and strain be present. If a model consists entirely of CBAR and CBEAM elements that only generate internal forces, the generated op2 file will be null and the following message will be written to the f06 file: *** SYSTEM FATAL MESSAGE 6551 (INPTX2) AN END-OF-FILE WAS DETECTED ON UNIT 11 DURING BINARY INPUTT2 PROCESSING PROGRAMMER INFORMATION: 1. A KEY VALUE WAS BEING READ 2. THE LAST KEY VALUE READ: 0 0*** FATAL ERROR. 0 NO. FORTRAN RECORDS READ = 0 NO. FORTRAN WORDS READ = 0 0FATAL ERROR 1-14932102 2004.0.5 Optimization/Design Sensitivity - External SE - SFM 4276 In a SOL 200 optimization analysis run with external superelements and shape design variable, the job may fail in the 2nd design cycle with the following messages: *** SYSTEM FATAL MESSAGE 4276 (PACK) ERROR CODE 105 PID= 0 Avoidance: Insert the following DMAP alter $ compile update,list $ alter 'dbstatus selist'(,-1) $ type parm,nddl,i,n,zuzri1 $ alter 'if ( noselist',''(,1) $ if ( noselist<1 or rsonly or (noselist>=1 and zuzri1>0) ) then $ if ( begsup or (noselist>0 and zuzri1>0) ) then $ $ compile desopt,list $ alter 'call update'(,-1) $ type parm,nddl,i,n,zuzri1 $ zuzri1 = shapeopt $ 1-14949104 2005 Distributed Memory Parallel/Optimization - MODTRK - UFM 6458 A DMP optimization job that requests mode tracking will fail in module MODTRK with UFM 6458 (MTD0RD) complaining the requested mode does not exist. Avoidance: Apply the following dmap alter compile fea list alter 'IF ( MODETRAK>0 ) then','' IF ( MODETRAK>0 and PROCID <= 1 ) then alter 'IF ( MODETRAK>0 ) then'(2),'' IF ( MODETRAK>0 and PROCID <= 1 ) then $ COMPILE moders list alter 'disutil lama'(2,-1) putsys(1,109) alter 'disutil lama'(2) putsys(0,109) $ $ 1-14970010 2004.0.5 Optimization/Design Sensitivity - DRESP2s, DRESP1s span subcases - UFM 6553 (DOPR3 M 6553 (DOPR3R) SOL 200 job with DRESP2 refers to DRESP1s that span the subcases and weight or volume will fail with ufm 6553 iin DOPR3R. Avoidance: remove dresp1 ID for weight from DRESP2 if possible 1-15002802 2004.5 SOL 600 - PLOADi, CPENTA - Incorrect Pressure Loads, Wrong Answers SOL 600 pressure loads are applied to the wrong face ID in the Marc deck for CPENTA elements. 1-15004301 2004.5 Spotwelds - CWELD, ELPAT - UFM 7549 (mdg2ed) A model with CWELD elements and curved shells may fail with the message: USER FATAL MESSAGE 7549 (MDG2ED) This error is caused by tight projection tolerance. In v2004 the default projtol is set to 0.0 to avoid picking wrong elements for PARTPAT format. The zero tolerance works for flat shells, but it causes errors for some curved or warped shells. Avoidance: Insert swldprm,projtol,0.01 to set the projtol to 1%. The default projtol will be changed in version 2005 from 0.0 to 0.01. Note that the projection tolerance in v2001 was set to 10% which was excessively large. 1-15028201 2004.0.5 Optimization/Design Sensitivity - HAT1 - Incorrect sensitivities for end B responses The HAT1 beam section type computes incorrect values for the sensitivity of responses that are a function of the END B dimensions. Avoidance: Substitute a HAT section type or do not use the tapered feature of the HAT1. 1-15068202 2004.5 Miscellaneous - Compaq Alpha v5.1a-5.1b - SFM 4276 (tbk) EC 7777 on Compaq Alpha A bug exists in V5.1a-b of the Compaq Alpha Unix operating system which may cause the floating point stack to be corrupted. This may cause a traceback in any version of MSC.Nastran and potentially could cause wrong answers. All clients must apply the 5.1B-1 patch. Avoidance: This error will be marked fixed in V2005 even though there is nothing MSC can do to fix the error. 1-15103324 2005 ACMS - WELD - Job terminates without messages This is now fixed - F2 missing on EIGRL now flagged in phase0 properly. PJS 8/24/04. If ACMS is used in a model with WELD element, the job may terminate in PHASE0. The following messages may appear in the f04 or f06 file: ACMS PHASE 0 BEGN Avoidance: For some problems, the following system cells modifications corrected the problem NASTRAN SYSTEM(360)=2000 NASTRAN BUFFPOOL=500 For SOL 103, GDMODES also avoided this error 1-15107501 2004.5 SOL 600 - Parallel, memory allocation bug puts elements in the wrong domains - Wrong Answers SOL 600 Parallel has a memory allocation bug which puts elements in the wrong domains. This leads to Marc aborting or wrong answers. 1-15113501 2004.0.6 Eigenvalue Analysis - SOL 103, MPCforces - UFM 6144 If MPCforces are requested on a subset of points in SOL 103 then the job may fail with SFM 6144. Avoidances: Request MPCFORCE=ALL or insert PARAM,SPARSEDR,NO or insert the following DMAP alter: compile sedisp alter 'CALL CFORCE USET,GM,UG,UH1','' CALL CFORCE USET,GM,UG,UH1,MMG,M2MG,BMG,B2MG,KMG,K4MG,K2MG,, PM,OLX,,/ QMG/ 1-15130911 2004.0.6 Eigenvalue Analysis - zero c-set mass - SFM 9158 If SYSTEM FATAL MESSAGE 9158 is encountered due to zero c-set mass, then the run may not terminate immediately but instead proceeds to the next superelement. Avoidance: Insert the following DMAP alter: compile mhred alter 'error'(2),'' endalter 1-15150301 2004.0.6 ACMS/Optimization/Design Sensitivity - DVCRELi, DVMREL1 - SFM 4276, EC 3021 (DSAL) In a superelement optimization including acms optimization job, if the DESVARs are only referenced by DVCRELi or DVMRELi entries, the job may fail unexpectedly with SYSTEM FATAL MESSAGE 4276, ERROR CODE 3021 in the DSAL module. This is caused by a missing EDOMS table from module SDSA. Avoidance: Add a dummy DVPREL1 entry as show below. Assuming the job has a PSHELL 100 with the thickness = 2.0 DESVAR 1010 DUMMY 2.0 2.0 2.0 DVPREL1 9999 PSHELL 100 T 1010 1.0 1-15159405 2004.0.6 Optimization/Design Sensitivity - DRESP1, GIV, HOU - UNPACK error in DSAH2 If an optimization analysis has a DRESP1 entry that request an EIGN or FREQ response for a mode number whose eigenvalue has been extracted but whose eigenvector has not been calculated (e.g, the eigenanalysis was performed using GIV or HOU up to a specified frequency) the job may fail with an UNPACK error. in DSAH2. Avoidance: Check to see if eigenvectors have been extracted for all the mode numbers invoked on a DRESP1 entry (i.e., that there are non-zero generalized mass and stiffness values). If they have not, either discard the DRESP1 request or modify the EIGR entry to extract more eigenvectors 1-15168101 2005 Optimization/Design Sensitivity - DSAPRT - Write operation tried to write a record that was too long A SOL 200 job on sgi irix that was writing a long DSAPRT record failed with the message "Write operation tried to write a record that was too long". Avoidance: There is no avoidance. 1-15182901 2004.5 Optimization/Design Sensitivity - DRESP1 - No message when modes are referenced that do not exist If the user requests an eigenvector response on a DRESP1 entry that designates a mode number that is higher than the number of modes extracted, the request is ignored. This is regarded as an error in the design of the eigenvector sensitivity calculation and the code is to be changed to make this a USER FATAL MESSAGE. Avoidance: There is no avoidance, the burden is on the user to make sure referened modes exist. 1-15214414 2005 DMP - MDMODES, EIGRL - Hang in SEMR2, Signal 15 Error If distributed memory parallel (dmp) mdmodes job is executed but f2 on the eigrl entry is not specified, the job may hang in SEMR2 or fail in various ways including a signal 15 error on HPUX Itanium. Avoidance: Specify f2 on the eigrl entry. In Version 2005 and beyond this condition is trapped with a user fatal message. 1-15217604 2005 SOL 600 - Excessive Memory is Required for large models Excessive memory is required for large SOL 600 model. Avoidance: There is no avoidance. 1-15238701 2005 Optimization/Design Sensitivity - DLINK, DESVAR - UFM 7008 If a DLINK entry references DESVAR entries that are not selected by a DESVAR command, the program issues USER FATAL MESSAGE 7008 (THE NUMBER OF DLINK ENTRIES EXCEEDS THE NUMBER OF DESVAR ENTRIES. USER INFORMATION: THE NUMBER OF DEPENDENT DESIGN VARIABLES MUST BE LESS THAN THE TOTAL NUMBER OF DESIGN VARIABLES). Avoidance: Remove the offending DLINK entry from the input file. 1-15245201 2004.5 Acoustic Analysis - EPOINT - Wrong answers If EPOINTs are specified in a fluid-structure model and some of the structural grid points in the a-set are numbered higher than the fluid grid points in the a-set then the results will be wrong. Avoidance: Insert the following DMAP alter: compile gma alter 'GKAM USETD,PHSA,','' MERGE PHSA,,,,,VAFS/PHSAF/1 $ GKAM USETD,PHSAf,mis,lamas,DIT,M2SS1,B2SS1,,CASES,lammats/ MSHH0,B2SHH0,K1SHH,PHDSH0,MODELSTS,modselsv,LAMASN/ NOUE/LMODES/lfreq/hfreq/-1/-1/-1/0/S,N,FMODE/ KDAMP/false//APP $ endalter 1-15247204 2004.5 SOL 600 - SOL600,106 - Error number 1030 Models that run successfully in SOL106 may fail when using SOL 600,106 when QUAD4 elements exist that are translated into the uu plane. 1-15251748 2004.5 Rotordynamics - RGYRO, UNBALNC - Wrong Answers If RGYRO with UNBALNC are included in the static subcase, the nonlinear transient response subcase will different answers on different machines. 1-15269705 2005 Superelements - PARAM,CONFAC - UFM 4277 and 4278 PARAM,CONFAC specifies the tolerance factor used in checking the congruence of the location of the boundary points between image superlements. In some models USER FATAL MESSAGE 4277 (SEP1ED)an d USER FATAL MESSAGE 4278 may be issued indicating that the tolerance has been exceeded when in fact it hasn't. Avoidance: An unrealistically large value of PARAM,CONFAC for example 1.0, may need to be specified to avoid the fatal message. 1-15278401 2004.5 SOL 600 - CBEAM - Offsets Ignored, Wrong Answers SOL 600 beam offsets are sometimes ignored and not reflected in the SOL 600 marc input deck. 1-15279901 2004.5 DMAP - MATMOD(21) gives wrong answers on complex matrices Matmod option 21 converts a sparse factor matrix from the DCMP module into 3 true matrices. When multiplied together properly they reform the input matrix to the DCMP module. The true matrices are easier to understand than the packed factor, where they are all in one data block. True matrices can be input to any matrix processing module, but the packed factor cannot. The option 21 has been demonstrated to behave well on real matrices. It can give wrong answers on complex matrices. Avoidance: No avoidance is known. Verified by Paresh for t2: The ferror matrix is numerically zero 1-15305906 2004.5 Nonlinear Analysis - NLITER - Signal 8, SFM Nonlinear analysis may fail in the NLITER module and issue a SYSTEM FATAL MESSAGE 4276 indicating an overflow or a SIGNAL 8 error. Avoidance: This error occurs because some error tolerance calculations are performed in single precision, modifying the convergence criteria on the nlparm entry may help avoid this problem. 1-15309511 2004.5 Spot Weld Element - CWELD - UFM When two or more CWELD elements that have angles that fail the tolerance test, nastran aborts after reporting the first element and fails to check and report on any other elements. Avoidance: Set CHKRUN to 1 on the SWLDPRM entry. 1-15334301 2004.5 Heat Transfer - UFM 4551 followed by SFM 4276 EC 31 If a heat transfer job fails to converge (USER FATAL MESSAGE 4551) may be followed by SYSTEM FATAL MESSAGE 4276 (GETCOL) ERROR CODE 31 because matrix IFSH has an incorrect trailer. 1-15341502 2004.5 DMAP - MODTRL - SFM 4276 EC 31 User DMAP errors may result in the following fatal message: *** SYSTEM FATAL MESSAGE 4276 (GETCOL) ERROR CODE 31 PID= 0 *** USER INFORMATION MESSAGE 4276 (GETCOL) that identifies the routine GETCOL even though the problem routine is GTIDMC. 1-15372203 2004.5 Data Recovery - STRAIN, PCOMP - UFM 3005 (SDR2) Similar to error report q1-8126205 which reported that UFM 3005 occurs when STRESS(CORNER) is requested with composites, it has been found that a request for STRAIN(CORNER) output which should be ignored for composite elements, will lead to the messages: *** USER WARNING MESSAGE 6418 (SDR2A) THE BILIN OPTION FOR STRESSES OVERRIDES ALL OTHER OPTIONS IN STRAIN AND FORCE COMMANDS. *** USER FATAL MESSAGE 3005 (SDR2) ATTEMPT TO OPERATE ON THE SINGULAR MATRIX (NONE) IN SUBROUTINE SQD43D Avoidance: Limit the strain request to non-composite elements by specifying a SET. 1-15388155 2005 Rotordynamics - RGYRO, STATSUB - SFM 4276, EC 30, TRD Rotodynamics models, RGYRO, with static subcases in transient analysis may fail in the TRD1 module with SYSTEM FATAL MESSAGE 4276 ERROR CODE 30. 1-15422604 2004.5 Optimization/Design Sensitivity - DSVG1 - Segmentation Violation When a large scale optimization job (having million DOFs) takes the non-adjoint path, the job may fail in DSVG1 with a segmentation violation. Avoidance: Specify as large a mem as possible. 1-15426513 2004.5 Restarts - RESTART, MODTRL - Attaching a read only database may lead to fatal error in MODTRL. Dynamic restarts may be inefficient and SubDMAPs PHASE1A. PHASE1DR, GMA and FREQRS may be executed unnecessarily. Furthermore, if the cold start database is attached read-only a fatal error may be issued in the MODTRL module. Avoidance: Insert the following DMAP alter in your cold start run: compile gma alter 'ENDIF \$ fastfr='(,-1) else $ xfastfr=false $ for restart efficiency endalter Or insert the following alter in your restart run: compile gma alter 'modtrl.*bdd'(,-2) dbstatus bdd//s,n,nobdd $ alter 'modtrl.*bdd','' if ( nobdd<1 ) modtrl bdd////6 $ alter 'modtrl.*k4hh'(,-9) if ( false ) delete /k4hh,,,, $ dbstatus k4hh//s,n,nok4hh $ alter 'modtrl.*k4hh','' if ( nok4hh<1 ) modtrl k4hh////6 $ endalter 1-15432813 2004.5 Component Mode Synthesis - CSET -SFM 9158 (MHRED), UFM 9032 (ERRPH1) MSC.Nastran 2004 may fail with the message below and setting param,zrocmas,yes as suggested in the message may not avoid the error. This problem is demonstrated with tpl deck edr2n on the Cray SV1 platform but it could occur on other systems as well. ^^^ SYSTEM FATAL MESSAGE 9158 (MHRED) ^^^ THE C-SET FLEXIBILITY MATRIX IS SINGULAR. ^^^ USER ACTION: SPECIFY PARAM,ZROCMAS,YES TO REMOVE THE MASS ON THE C-SET DURING COMPONENT MODES. Avoidance: In addition to param,zrocmas,yes insert param,fzero,XXX where XXX is a real value just below the lowest flexible mode and above all "rigid body" modes. This causes the correct rigid body modes to be used for inertia relief supports in the autosprt subdmap. Other avoidances are to add the parameters: param,mhred,no and param,respath,old or param,mhred,no and param,fzero,xxx 1-15463011 2005 SOL 600 - TEMPD is not recognized by the translator In SOL 600 TEMPD is not recognized by the translator. This will lead to missing temperature loads and wrong answers. Avoidance: The only avoidance is to specify the initial temperature on TEMP entries. 1-15466201 2004.0.6 Installation - RedHat AES 3 - Segmentation Fault When MSC.Nastran is submitted on an IA64 system with the RedHat AES 3 opterating system, the following message will appear: Segmentation fault (core dumped) Avoidance: Download the new "nastran" driver from ftp.mscsoftware.com and place in $MSC_BASE/msc2004/linux64/nastran 1-15477101 2005 Nonlinear Analysis - TEMP(INIT), PCOMP - Wrong Answers For nonlinear analysis of temperature dependent composite materials, the initial stiffness matrix should be computed based on the initial temperature referenced by Case Control command TEMP(INIT)=N. However, for Version 2004, the initial stiffness matrix is computed based on the TREF on the bulk data entry PCOMP. This is wrong. 1-15502121 2004.5 Spotwelds - Missing UFM 7549, SFM 4276 EC 3012 Models with spot welds that should fail with the message: USER FATAL MESSAGE 7549 (SEPWLD) indicating that the projection of GS GRID ID=xxxxx onto the surface cannot be found or lies outside the plane, may fail to issue this message and isntead fail with SYSTEM FATAL MESSAGE 4276 (QOPEN) EC 3012. 1-15518520 2004.5 Miscellaneous - ADAMSMNF - Cray Only, Traceback in AMSMI2 Some adamsmnf jobs that create an Adams modal neutral file may fail in Version 2004.0.6 on Cray SV! Beginning of Traceback: Called from line 42 (address 13710276a) in routine 'TRBK'. Called from line 40 (address 77535d) in routine 'RECOVR'. Called from line 112 (address 55361c) in routine 'sysrcv'. Called from address 13373636a in routine '__handlr'. Called from address 13740534a in routine 'AFSMI2'. Called from address 15101264b in routine 'AFGMNF'. Called from line 136 (address 15077120c) in routine 'XSEM16'. Called from line 133 (address 54500d) in routine '$SEGCALL'. Called from line 133 (address 225677b) in routine 'XSEMDR'. Called from line 66 (address 63175b) in routine 'NASTMON'. Called from line 379 (address 1372d) in routine 'MAINAL'. Called from line 343 (address 54455d) in routine '$SEGRES'. Called from line 343 (address 12005663d) in routine '$START$'. End of Traceback. 1-15525703 2005 Data Recovery - MAXMIN(DEF) results are order dependent If a MAXMIN(DEF) definition for a MAGnitude (either Translation or Rotation) follows a MAXMIN(DEF) for a specific component (i.e. T3), then the reported MAGnitude results will all be zero. If the order of the MAXMIN(DEF)s are reversed (MAG first, then component) the results are correct. This order gives zeros for the MAGT results: MAXMIN(DEF) ACCE T3 MAXALG=2 MAXMIN(DEF) ACCE MAGT MAXALG=3 whereas this order does not: MAXMIN(DEF) ACCE T3 MAXALG=2 MAXMIN(DEF) ACCE MAGT MAXALG=3 1-15525713 2004.0.7 Data Recovery - STRAIN, DISP, COORDi - Wrong Answers With Version 2004.0.0 if the Case Control includes an output request for STRAIN, then the CID option for grid-type responses (DISP, SPCF, MPCF) will be ignored and the output coordinate system will not show up in the printed .f06 output. Requests for other element-based output such as STRESS or FORCE do not affect the grid-based output, just the STRAIN request. 1-15537101 2004.5 Dynamics - Modal Participation Factor phase angle has wrong sign The sign of the phase angle of the modal participaltion factor results may be in error. compile mpf nolist alter 'PARTN ABE,VGXFS','' PARTN ABE,VGXFS,/,,ABESFP, $ ADD ABESFP,/ABESF/(-1.0,0.0)//3 $ NEGATE ABE MATRICES alter 'SMPYAD PHGXFH'(1,0),'' SMPYAD PHGXFH,ABESF,PHGXSH,,,/ABEH/3/1///1/1 $ alter 'SMPYAD PHGXFH'(2,0),'' SMPYAD PHGXFHX,ABESFXX,PHGXSHX,,,/ABEH/3/1///1/1 $ 1-15550901 2005 Optimization/Design Sensitivity - SPCD - Incorrect Responses for Enforced Motion If a SOL 200 design task includes enforced motion using SPCD's, the final response and element data recovery results are incorrect. The optimization results are correct as are the sensitivities. Avoidance: If PARAM NASPRT 1 is used, all data recovery results will be correct. Alternatively, one can simply ignore the final response results and create an input deck from the final design. TPL deck d200rd15 demonstrates this error and correction in verison 2005. 1-15553302 2004.5 Acoustics - Data Recovery - Excessive CPU when no MPF output is requested Even if no modal participation factor output is requested, the data recovery is still performed on all fluid-structure interface points; thereby defeating the benefits of sparse data recovery. Avoidance: Insert the following alter: compile spdr1 alter 'ajp'(2,-1) type parm,nddl,i,y,fluidmp,structmp $ if ( fluidmp<>0 or structmp<>0 ) then $ alter 'ajp'(2) else $ call xAdd5 vp,vky,vmy,vby,/vpx/cu/cu/cu/cu/cz $ endif $ compile semfreq alter 'if ( structmp','' if ( structmp<>0 or fluidmp<>0 ) then $ compile fea $ feafreq in V2004r2 alter 'if ( structmp','' if ( structmp<>0 or fluidmp<>0 ) then $ compile spdr0 alter 'if ( fluidmp','' if ( fluidmp<>0 or structmp<>0 ) then $ endalter 1-15567801 2004.5 Acoustics - Enforced Motion, SPCD, and sparse data recovery - Wrong Answers If sparse data recovery is activated in fluid-structure analysis with enforced motion wrong answers may be produced. Avoidance: Specify PARAM,SPARSEDR,NO or insert the following DMAP alter compile cforce1 alter 1,1 SUBDMAP CFORCE1 MXY,mqxy,M2XY,m2qxy,BXY,bqxy,B2XY,b2qxy,KXY, K4XY,k4qxy,K2XY,k2qxy,PHY,KDXY,kdqxy,axy,aqxy, yx,vxpc,uset/ MXY1,BXY1,KXY1,pmyy,pbyy,pkyy,vxcg/ APP/APP1/forctype $ alter 'add vy1,vy2','' Matmod axy,aqxy,,,,/vy3,/12/s,n,nonull/2/-1 $ add vy1,vy2/vy2a $ add vy2a,vy3/vy $ alter 'add vy1,vy2'(2),'' Matmod axy,aqxy,,,,/vy3,/12/s,n,nonull/2/-1 $ add vy1,vy2/vy2a $ add vy2a,vy3/vy $ alter 'add vy1,vy2'(3),'' Matmod axy,aqxy,,,,/vy3,/12/s,n,nonull/2/-1 $ add vy1,vy2/vy2a $ add vy2a,vy3/vy $ compile gma alter 'umerge1 usetd,adya,,,' call dbstore a1sf,adsf,,,//0/0/' '/0 $ compile spdr1 alter 'call cforce1',''(,1) call dbfetch /a1sf,adsf,,,/0/0/0/0/0 $ CALL CFORCE1 MSF,mysf,M2SF,m2ysf,BSF,bysf,B2SF,b2ysf,KSF,K4SF,k4ysf, K2SF,k2ysf,,KDSF,kdysf,a1sf,adsf,,vspc,uset/ MSF1,BSF1,KSF1,,,,vscg/ APP/app/'spcforce' $ if ( noyg>0 ) CALL CFORCE1 MSs,,M2Ss,,BSs,,B2Ss,,KSs,K4Ss,, K2Ss,,,KDSs,,,,,vspc,uset/ MSs1,BSs1,KSs1,,,,/ APP/app/'spcforce' $ alter 'call cforce1'(3),'' if ( dompcf ) CALL CFORCE1 MMG,,M2MG,,BMG,,B2MG,,KMG,K4MG,,K2MG,,,KDMG,,, ,,Vmpc,uset/ MMG1,BMG1,KMG1,,,,vmcg/ APP/app/'mpcforce' $ compile fdrmgen alter 'call cforce1',''(,1) call CFORCE1 MSF,,M2SF,,BSF,,B2SF,,KSF,K4SF,,K2SF,,phif,kdsf,,, ,,vspc,uset/ msf1,bsf1,ksf1,,,,/ APP/APP1/'spcforce' $ if ( noyg>0 ) call CFORCE1, MSS,,M2Ss,,BSS,,B2Ss,,KSS,K4Ss,,K2Ss,,,kdss,,, ,,vspc,uset/ mss1,bss1,kss1,,,,/ APP/APP/'spcforce' $ alter 'call cforce1'(3),'' CALL CFORCE1 MMG,,M2MG,,BMG,,B2MG,,KMG,K4MG,,K2MG,,phig,kdmg,,, ,,vmpc,uset/ MMG1,BMG1,KMG1,,,,/ APP/APP1/'mpcforce' $ alter 'call cforce1'(4),'' CALL CFORCE1 MMy,,M2My,,BMy,,B2My,,KMy,K4My,,K2My,,, kdmy,,,,,,uset/ MMy1,BMy1,KMy1,,,,/ APP/APP/'mpcforce' $ compile cforce alter 'call cforce1','' call CFORCE1 MXY,,M2XY,,BXY,,B2XY,,KXY,K4XY,,K2XY,,uy,kdxy,,,,, vxpc,uset/ mxy1,bxy1,kxy1,,,,vxpc1/ APP/APP1/forctype $ endalter 1-15654005 2004.5 SOL 600 - RBE2/RBE3 nodes are not included in all SOL 600 domains for Parallel Processing RBE2/RBE3 nodes are not included in all SOL 600 domains for Parallel Processing. Usually all REB2/RBE3's must be included in all domains and all grid points associated with them must also be included in all domains, othewise the job will diverge. 1-15664507 2005 Nonlinear Heat Transfer - Excessive Output Heat transfer, sol 159, may place the: N O N - L I N E A R I T E R A T I O N M O D U L E O U T P U T for each timestep on a different page. If printed this wastes paper and it also has the potential of doubling the output because page header information is repeated for each page. 1-15689201 2004.5 SOL 600 - RFORCE is not translated to Marc properly SOL 600 RFORCE is not translated to Marc properly. It needs distributed load code 105 rather than 100 or 103. 1-15689204 2004.5 SOL 600 - MARCIN (include file) missing data - Nastran aborts The SOL 600 MARCIN (include file) may result in missing data and may cause Nastran to abort. 1-15738901 2005 Documentation/QRG - EQUILIBRIUM - Ignored in SE models Remark 3 of the EQUILIBRIUM Case control command in the QRG should indicate that the EQUILIBRIUM commnad produces no output in the presense of superelements. 1-15742867 2004.0.7 DDAM - missing output in MSC.FEA When using the new DDAM option in MSC.FEA, the results are missing. Avoidance: The DDAM and DDAMOUT subdmaps need to be replaced. The error is corrected in Version 2004.0.7 which is only available on the FEA 2004 R2 that is scheduled to be released by the end of May 2004. The error is also corrected in MSC.Nastran 2004.5 scheduled to be released June 15, 2004. 1-15795828 2004.5 SOL 600 - BCPARA - FTYPE default of coulumb friction is not translated If FTYPE is not specified on the BCPARA entry no Defaults are used even though the Quick Reference Guide mentions indicates that the default is Coulomb. Avoidance: Explicitly specify FTYPE on the BCPARA entry. 1-15831209 2005 Nonlinear Analysis - ESE - Wrong Answers with INTOUT SOL 106, nonlinear analysis, may create incorrect nonlinear ESE when the 9th field of NLPARM bulk data card, INTOUT, is not set to ALL in Version 2004 and earlier releases. Avoidance: Specify INTOUT=ALL. 1-15831507 2005 Frequency Response - SUPORT - SFM 6424 and 6144 Direct Frequency response with SUPORT entries may fail with the messages: SYSTEM FATAL MESSAGE 6424 (DFNSB) THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE INCOMPATIBLE LOAD VECTOR ROWS = 2536 FACTOR MATRIX ROWS = 2537 SYSTEM FATAL MESSAGE 6144 (MERGE1) THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY: The number of rows in DAY is not equal to the number of zeros in partitioning vector VAY User Information: Size of input matrices and partitioning vectors: DAY : Rows= 2537 by Cols= 1 VAY : Rows= 2537 no. of non-zeros= 1 no. of zeros= 2536 0 Avoidance: compile sedfreq alter 'call mmfind1','' type parm,nddl,char8,n,ltset,llset $ UPARTN USET,Kaa/KLL,,,/ltset/llset $ UPARTN USET,maa/mLL,,,/ltset/llset $ CALL MMFIND1, Kll,Mll,USET,SILS,EQEXINS,,bgpdts/ MECHA,phir,vspc,lll/ s,mmech/'l '/false $ endalter 1-15842401 2004.5 SOL 600 - Multiple NLSTRAT entries result in fatal message Even though multiple NLSTRAT entries are legal, SOL 600 gets a FATAL ERROR when more than one NLSTRAT is defined. Normally there needs to be one NLSTRAT per subcase with an additional one with ID=0 for Marc's phase zero if any at all are entered. 1-15848202 2004.5 SOL 600 - Memory request of ... words failed / RSSCON not supported In Version 2004 solution 600 may fail with the message: memory request of 83137782 words failed during the translation phase - no Marc input file gets created. Avoidance: Increasing the memory may not allow the problem to be solved. Running with a very large memory requested resulted in a marc input deck being created and the following message being written to the f06 file: TRANSL WARNING - RSSCON is not supported by the internal Marc translator. Marc will not be executed. 1-15848212 2004.5 Elements - STRESS, PSOLID, CHEXA - Stress at Gauss points not available for c IN=2 Writing out the stresses of CHEXA elements at the Gauss points for IN=2 is not possible. Stress at the grid points will be output. 1-15854501 2005 Submittal - node= - V2004 Windows missing nastran.rmt file The PC version of v2004 (both r1 and r2) does not include the nastran.rmt file (.../msc/msc2004/i386). This means that the "node=" option does not function. Workaround is to copy the one from v2001 (however there are issues with that file as well as you need to include a line that reads: jidtype=%jidtype% as a minimum - this is addressed in a separate CSR - see 1-15854504) 1-15854504 2005 Submittal - UFM, Input file does not exist While using "node=" command to submit from Windows to unix, the job will fail if the extension of the input file ( .bdf for example) does not match the "jidtype" setting on the remote machine. This error persists even if the "jidtype=bdf" keyword is used on the launching PC side. Avoidance: If the following line is added to the PC's nastran.rmt file, then the jidtype keyword is passed thru correctly and the job recognizes the keywords and will run correctly: jidtype=%jidtype% Note that the "nastran.rmt" file itself is missing completely from the 2004 (r1 or r2) installations. The jidtype command above is in the standard nastran.rmt file for Windows. When it is included in the delivery, this error will be eliminated. 1-15862001 2004.5 SOL 600 - SOL 600 incorrectly checks out a nastran nonlinear license A SOL 600 job may incorrectly check out a nastran nonlinear license as evidenced by the following message in the log file. Acquired 100 licenses for Group CAMPUS (MSC.Nastran Nonlinear) 1-15879701 2004.5 SOL 600 - TEMPP1 & TEMPRB may produce incorrect POINT TEMP Marc input leading to wrong answers SOL 600 TEMPP1 & TEMPRB may produce the wrong POINT TEMP in the Marc deck leading to wrong answers. 1-15895505 2005 Complex Eigenvalue Analysis - CLAN - Wrong Answers In Version 2004, complex Lanczos may produce bad answers if the block size is automatically augmented. The block size is only augmented when the number of repeated roots is greater than the block size or the solver is unable to converge and this rarely occurs in real world models. Avoidance: The problem can be avoided by setting system(108)=8. 1-15907201 2004.5 SOL 600 - Eigenvalue analysis after a nonlinear solution with contact gives wrong results SOL 600 eigenvalue analysis after a nonlinear solution with contact gives wrong results for the nonlinear portion of the job as well as the eigenvalue portion. Fixed using 1-15862001 1-15923905 2004.5 Documentation/SOL 600 - BCBODY - UFM 316 If the documented text of "3D" is entered into the "DIM" field (field 3) of the BCBODY entry, then MSC.Nastran 2004 and 2004r2 fatal out with a UFM 316 format error as it tries to read the "d" as part of an exponent instead of as a character as documented. Avoidance: Leave this blank (since 3 is the default) or specify just the number "3". BCBODY,1 $ Default is OK BCBODY,2,3 $ Using a number is OK BCBODY,3,3D $ Gives UFM on "3D" field Running even SOL 100 with the above as the bulk data file will demonstrate the problem 1-15925501 2004.5 External Superelements - EXTSEOUT - SFM 4276 (BLDPK) EC 211 Large external superelement jobs may fail in the MERGE1 module with the message: SYSTEM FATAL MESSAGE 4276 (BLDPK) ERROR CODE 211 PID= 0; f04: EXTOUT 166 UMERGE1 BEGN BLDPK TERM 1-15931801 2005 SOL 600 - out= leads to UFM 1019, SFM 6551, SFM 1004 If SOL 600 requests that marc results be output in the f06 (OUTR=f06) and out= is specified on the nastran submittal command, nastran will fail. *** USER FATAL MESSAGE 1019 (OPNPFL) or *** SYSTEM FATAL MESSAGE 6551 (INPTX2) AN END-OF-FILE WAS DETECTED ON UNIT 11 DURING BINARY INPUTT2 PROCESSING OR *** SYSTEM FATAL MESSAGE 1004 (INPTYP) UNABLE TO CREATE FORTRAN FILES ENTRY FOR UNIT 11 FOR LOGICAL NAME INPUTT2 USING DEFAULT FILE NAME. ERROR CODE = 1. 1-15944704 2004.5 Frequency Response - QSET, ASET1 - UIM 7588, SFM 6144 In SOL 108 with modal reduction (ASET1, QSET) the GKAM module issues USER INFORMATION MESSAGE 7588 indicating the number of modes that are retained. The number of modes indicated retained is actually the number of modes calculated and the then number of modes calculated is actually the number of q-set degrees of freedom. The residual vectors are subsequently thrown away and later in the solution MERGE1 fails because of incompatibility of datablocks DAY and VAY. 1-15950512 2004.0.7 SSSALTER - ddam - Wrong Answers The NRL summing convention may not be used due to an inconsistent parameter name used in the ddam* sssalter Avoidance: Download the latest v2001 alter (ddamall.v2001) from our website. This alter replaces the ddama and ddamba alters. 1-15950532 2005 Elements - CTRIAX6 - Incorrect Stress Label When using axisymmetric elements, vonmises stresses are labelled as octahedral stresses. Only the labels are incorrect, the values are correct. 1-15962101 2004.5 Elements - CWELD, CFAST, PFAST - Wrong mass when lumped mass specified in field MASS If the MASS field of the PFAST entry is populated with a value, the mass added is much larger than the lump mass specified. PARAM,GRDPNT,0 reports different masses in different directions and the eigenvalue analysis fails. 1-15994609 2004.5 P-elements - GMINTC and GMINTS - SFM 4276 EC 3021 If GMINTC and GMINTS Bulk Data entries are both present in the model then the run will terminate in the GP0 module with: *** SYSTEM FATAL MESSAGE 4276 (READ) ERROR CODE 3021 PID= 0 Avoidance: There is no avoidance. 1-16026003 2004.5 SOL 600 - Gasket materials combined with other solid element materials generate error in Marc SOL 600 Gasket materials, MATG, combined with other solid element materials generate error in Marc. 1-16028004 2004.5 Optimization/Design Sensitivity - UFM 3001: Datablock CASEDM does not exist The fatal message USER FATAL MESSAGE 3001 DATABLOCK CASEDM DOES NOT EXIST can result when eigenvector senstivities are requested and the only RTYPE that is used is FORCE. Avoidance: An avoidance is to add other RTYPE's (DISP,STRAIN,ESE,STRESS or TOTSE) that invoke eigenvectors with an id that is equal to or greater than the highest ID appearing on a DRESP1 with RTYPE=FORCE 1-16028303 2005 Transient Analysis - SPCD - Wrong Answers with sparse data recovery. Sparse data recovery usage in transient analysis (both SOL 109 and SOL 112) employing SPCD enforced motion will give wrong answers if the base displacement or velocity is non-zero. This should not affect enforced acceleration scenarios, but may seriously affect enforced displacement or enforced velocity scenarios. Avoidance: Specify sparsedr=no. 1-16038804 2005 Documentation - DMAP Programmer's Guide Aerodynamic Module examples are obsolete In the DMAP Programmers Guide, the description of the aerodynamic modules is up to date. However, most of the examples still show the old argument lists, e.g. ADG, AMG, ... 1-16060036 2004.5 Frequency Response - METHOD - UFM 9056, METHOD Command required in all subcases In all previous versions of Nastran, under sol 111, the METHOD command was required only in the first subcase. In Version 2004 if multiple subcases are specified in frequency response but a METHOD command is not specified in all subcases the job will fail with the message: USER FATAL MESSAGE 9056 ( MODEFSRS) NO METHOD COMMAND WAS SPECIFIED IN THE CASE CONTROL SECTION. 1-16074001 2005 Dynamics/Enforced Motion/DMP/Acoustics - SFM 6144 (PARTN1) Acoustic models with enforced motion in DMP may fail with the message: SFM 6144 (PARTN1) Size of input matrices & partitioning vector incompatible Columns of PHSA0 not equal to rows of VR Avoidance: compile modefsrs alter 'if ( relmtn )'(2),'' if ( relmtn and not(procid>1 and (fdmodes or mdmodes)) ) then $ endalter 1-16090301 2004.5 DMAP - MATOFP module - no print control, ignores paging, uses CARDNO The MATOFP module has several deficiencies: 1. no print control. 2. ignores paging 3. uses old CARDNO processing Avoidance: There is no avoidance. 1-16096104 2005 Enforced Motion, SOL 109 - Unexpected Spikes in Acceleration Direct enforced motion with prescribed displacements (SOL 109) may result in unexpected acceleration spikes at the beginning and end of the enforced displacement. Enhancements to enforced motion have corrected this problem in version 2005. 1-16107905 2004.5 DMAP - MATMOD Option 40 - Poor message and wrong answers MATMOD Option 40 has several errors: 1. Incorrectly issues the following message in the f04: *24* Wrttrl Warning - Trailer type of terms for indexed matrix 201 is incorrect: 0. An automatic update has been made. *24* 2. Incorrectly issues SWM 7598 when doing parameter conversion from single to double precision. 3. Does not ouptut the matrix in machine precision if I1 is purged and TYPE parameter is not consistent with machine precision. 4. SFM 6918 and 6920 are fatal errors but do not terminate the run. 5. If output is purged then there is no fatal. 6. NZWDS and DENSITY in the trailer may be incorrect. Avoidance: There is no avoidance. 1-16109501 2004.5 Documentation/QRG - Nonlinear, PSOLID, TETRA - Nonlinear Supports 5-10 noded TETRA The PSOLID entry description in the V2001 and V2004 Quick Reference Guide incorrectly indicate that nonlinear is not supported for the 5-10 noded TETRA element. 1-16128001 2004.5 Performance - matmod option 16 on hpux Bad performance of matmod option 16 to punch DMIG has been reported for Nastran 2004 HPUX 2004 systems. 1-16132601 2004.5 Data Recovery - ESE ouput for DMIG missing with SETP When SETP case control is used to combine existing sets in a model with DMIG(s), the DMIG output maybe be missing in the ESE output. 1-16132609 2004.5 Data Recovery - ESE/EKE output printed twice when SETP used When the SETP case control command is used to combine existing SETs, and more than one type of output is requested among ESE, EKE and EDE, the output may be printed twice. 1-16143401 2004.5 Multilevel Superelements - Upstream generalized coordinates are discarded. If KOA is null, which can happen on collector superelements that have no physical boundary points, the coefficients for the generalized coordinates of the upstream superelements may be discarded. Avoidance: An alter that avoids this problem for non-inertia relief runs follows: $ remove line 72 in sekr $ 72 IF ( NOT(STATICS) AND $((XRESVECO='NO' AND XRESVIRO='NO' AND $ INRLM>-1)OR $ SEID=0 OR SEID=FLUIDSE) ) THEN $ alter 72,72 $ if (not statics or seid=0) then $ 1-16148301 2004.5 Optimization/Design Sensitivity - MFREQ/DFREQ, Superelements - Infinite Loop MFREQ/DFREQ SOL 200 optimization jobs may encounter an infinite loop condition if the number of records in FRQPRP is larger than NZ1. This scenario is most likely to happen when superelements are utilized and the number of subcases is high. Avoidance : Use the following DMAP alter only if the design model is in the residual (debug_dsad2.alter). compile descon $ alter 'dsad ','' $ DSAD RSP1CT,R1TAB,RESP12,OBJTAB,CONTAB,BLAMAX,LAMASX, CLAMAX,DIVTAB,AUXTAB,STBTAB,FLUTAB,OUGVS1,OESS1, ,OEF1AA, , , ,OQGS1,DSCREN,XINIT, tabdeq,COORDN,OLX, FRLSE, FRQRSP,CASEDS,CASEm, , OPTPRM,DVPTABF,PROPIF,BGPDTS,DNODEL,WGTM, , , ,resp3,rmstab,rmsval, UGXF, QGXF, QMPXF, UHXF, , , , ,MODRSP,CASEDMX,PHGX, , , ,upsdtx, RQATAB,RESP12X,RESP3X/ R1VAL,R2VAL,RSP2R,R2VALR,CVAL,CVALR,OBJTBR,CNTABR, R1TABR,R1VALR,DRSTBL,FRQRPR,UG1,AUG1,R1MAPR,R2MAPR, CASDSN,CASDSX,DRDUG,DRDUTB,CASADJ,LCDVECI,rr2idr, r3val,r3valr,resp3r,rmstbr,rmsvlr,FRLR,FOLR, UGM21, QGM21, QMPM21, UHM21,MODRPR,upsdt, RQATABR, RSP2XR,RSP3XR/ vols/vol/S,N,OBJVAL/S,N,NR1OFFST/S,N,NR2OFFST/ S,N,NCNOFFST/APP/ -1/SEID/DESITER/EIGNFREQ/ S,N,ADJFLG/PEXIST/MBCFLG/RGSENS/protyp/autoadjx/ fsdcyc/s,n,nr3offst/inrel/s,n,tadjc/PEID/s,n,ACTFREQ/ s,n,FREQ1/s,n,DLOADDS/FRQ345/DISCYC $ endalter $ 1-16149704 2005 Distributed Memory Parallel (DMP - ASET - SFM 7467, SFM 6144 This is now fixed. (Remember don't test MDMODES on tiny job for now.) DMP does not support the use of ASET/ASET1 entries. If ASET/ASET1 is used, SYSTEM FATAL MESSAGE 7467 is issued correctly in version 2001. In version 2004, SFM 6144--the sizes of the input matrices and partitioning vectors are incompatible--is issued. Since ASET is not supported in DMP, this also implies that DMP does not support ADAMSMNF. Avoidance: For models using DMP, remove the ASET/ASET1 entries. ASET/ASET1 entires are supported in MDACMS and MDMODES and Freq Domain Modes in V2005. GDACMS and GDMODES are not supported. 1-16163101 2005 Elements - QUAD4, TEMP, MAT2, MAT8 - Poor Answers In MSC.Nastran a single precision transformation is performed for non-isotropic 2D materials (MAT2 and MAT8). This may lead to poor answers and is especially noticable when zero stresses are expected for a free expansion under thermal loads. Avoidance: Use the QUADR element. 1-16181301 2004.5 Elements - CRAC2D, CRAC3D, MAT8, MAT9 - UFM TA1 If the crac2d or crac3d elements reference mat8 or mat9 orthotropic/anisotropic materials the job will fatal in Version 2004. 1-16230501 2004.5 Rotordynamics - ROTSEKE - Strain and kinetic energies are incorrect There are error in the ROTSEKE subDMAP that lead to 1) Rotor numbers on output do not change 2) Energies are not calculated correctly. 1-16267101 2004.5 Optimization/Design Sensitivity - DRESP3 - Unexpected failure in DSTAp2 for DRESP3 optimization job An external response optimization job (DRESP3) may fail in DSTAP2 without an error message. Avoidance: There is no avoidance. 1-16270201 2004.5 Distributed Memory Parallel (DMP) - LAM/MPI error - IA64 Distributed Memroy Parallel (DMP) will not work with MSC.Nastran on IA64 systems running RHEL 3.0 (Red Hat Enterprise). A message stating that the LAM Deamons will not boot will appear. Avoidance: Use MSC.Nastran V2004.5 (a.k.a. MSC.Nastran 2004 R3) or Install an OS that uses GLIBC 2.2. 1-16270204 2004.0.3 Memory - Unable to Allocate - IA64/Linux V2004.0.0 IA64/Linux systems cannot allocate more than 2.0 Gb on the "mem" parameter. V2001.0.9 allowed memory allocation over 2Gb. This error was corrected in V2004.0.3. 1-16306501 2004.5 Distributed Memory Parallel/ACMS - DMP - DISUTIL option 10 Bus Error DISUTIL option 10 may incur a Bus Error. This could affect distributed memory parallel ACMS, which is where DISUTIL option 10 is used most. 1-16323801 2004.5 SOL 600 - MATEP - MATEP workhardening slope, H, is not translated to Marc, Wrong Answers In SOL 600 the MATEP workhardening slope, H, is ignored and is not translated to Marc. 1-16323804 2005 SOL 600 - CORDi - Loads applied in cylinderical coords are sometimes incorrect SOL 600 loads applied in cylinderical coordinates are sometimes incorrect. This can happen even if the loads are in the basic coordinate system but the grids have specified a cylindrical output coordinate system in field 7 of the GRID entry. In most cases, the loads are correct. Only in unusual circumstances are the loads incorrect. 1-16326601 2005 Optimization/Design Sensitivity - DESVAR - UFM 7105 When an optimization job specifies DESVAR IDs > 1 million and the DESVAR command is used to select part of DESVAR entries, the job may fail with the message: USER FATAL MESSAGE 7105 (DOPR3F) The Fiedl DVID aaaa on DVPREL1 Entry ID = yyyy is not selected by the DESVAR Case Control command. Avoidance: Specify DESVAR IDs < 1 million. 1-16332103 2004.5 Static Analysis - PARAM,INREL,-2 - UFM 9050 In Version 2004, when param,inrel,-2, is specified to select inertia relief without the need to specify a SUPORT entry the analysis may fail with USER FATA MESSAGE 9050. Avoidance: Specify param,inrel,-1 and specify a suport entry. 1-16420502 2004.5 SOL 600 - Missing SPCs In SOL 600, an array in a is dimensioned 6 but values are set up to 8. This may cause Linux systems to fail to write SPCs resulting in an unconstrained model or wrong answers. 1-16442912 2004.5 Matrix Methods - DCMP - Fails to issue UFM leading to wrong answers. Version 2004 uses Lagrange multipliers in static analysis and hence negative factor diagonals can now be common and the stiffness well conditioned. Thus, in Version 2004 DECOMP may ignore negative maxratio values and fail to issue a fatal message when it should. 1-16443309 2005 External Superelements - EXTSEOUT, OUTPUT(PLOT), UFM 2025 (SDR2) If an external superelment, EXTSEOUT, superelement contains a displacement output request. and OUTPUT(PLOT) commands are used, the following FATAL message will occur: *** USER FATAL MESSAGE 2025 (SDR2) UNDEFINED COORDINATE SYSTEM ID = 268435455 Avoidance: Removing the OUTPUT(PLOT) section will eliminate the error. 1-16455901 2005 Optimization/Design Sensitivity- Eigenvector sensitivity with multiple boundary condtions broken Eigenvector sensitivity analysis based on DRESP1 entries was introduced in the 2004 release of MSC.Nastran. The original release supported multiple boundary conditions, but this capability was broken in the 2004.0.3 release (a.k.a 2004r2) when support for multiple boundary conditions in frequency response optimization was integrated. Avoidance: Go back to the earlier 2004 release or wait for the 2005 release. 1-16470701 2005 Optimization/Design Sensitivity - Multiple Boudary Conditions not robust with multipl analysis types Mutiple boundary conditions with frequency response analysis was introduced into SOL 200 in Version 2004.0.3 (a.k.a. 2004R2). Testing has shown problems when there are multiple disciplines as well as multiple boundary conditions. In particular, runs with ANALYSIS = MODES and ANALYSIS= MFREQ with different boundary condition can produce fatal messages. Quality report 1-1655901 is related. Avoidance: The dmap changes required to support analysis =MFREQ and analysis=MODES and multiple boundary conditions are extensive so this capability is not considered to be operational. It will be operational in Version 2005. 1-16470704 2005 Optimization/Design Sensitivity - Extra responses in formatted sensitivity prints Generalized mass and stiffness responses are "spawned" when the Rayleigh Quotient approach is applied to eigenvalue sensitivity analysis. These response are typically suppressed when formatted design senstivities are printed, but they appear if two different subcases share a DRES[1 id with type = eign or freq and the sensitivity is computed for both. In this case, the senstivities of the generalized matrices can appear following the eigenvalue sensitivities. Avoidance: An avoidance is to not share a DRESP1 ID for multiple subcases. 1-16474104 2004.5 Nonlinear Buckling Analysis - DCMP - Missing UIM 4698 to identify instabilities To identify instabilities and isolate buckling, the user should look for UWM 4698. However, in Version 2004 DCMP does not print the message making it impossible to identify buckling phenomena. The following is an example of the missing message: *** USER WARNING MESSAGE 4698 (DCMPD) STATISTICS FOR DECOMPOSITION OF MATRIX K(appropriate) . THE FOLLOWING DEGREES OF FREEDOM HAVE FACTOR DIAGONAL RATIOS GREATER THAN 1.00000E+07 OR HAVE NEGATIVE TERMS ON THE FACTOR DIAGONAL. GRID POINT ID DEGREE OF FREEDOM MATRIX/FACTOR DIAGONAL RATIO MATRIX DIAGONAL 102 R2 -1.93940E+03 2.14680E+04 1-16500402 2004.5 Superelements - Print Format error in TABPRT The Superelement Summary Output in the f06 filem may contain asterisks for large integer grid id's (******). 1-16503108 2005 Acoustics - FLSPOUT, STRUCTMP - Mislabeled Ouput Modal participation factors are calculated for each subcase but are mislabled as the first subcase. 1-16548801 2005 Heat Transfer - RMG2 - SFM 3008 (RMG2) Heat transfer jobs with large view computations may fail with the message: *** SYSTEM FATAL MESSAGE 3008 (RMG2) INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE RMG2 0FATAL ERROR 1-16606402 2005 SSSALTER - spc101a alter missing In Nastran 2004 the spc101a alter was not included. Avoidance: SSSALTERs are posted to the web at: http://www.mscsoftware.com/support/prod_support/nastran/sssalters/v2004/toc.cfm 1-16630701 2005 Optimization - DRESP1 - Transient response types on the DRESP1 do not support multiple components. Rermark 7 for the DRESP1 entry in the QRG indicates that TDISP, TVELO, TACCL and TSPCF support multiple components. A code bug blocks this to a single component less than or equal to 6. Also for GPFORCP. the ATTA input is a grid id. therefore there are documentation errors in table 8-9 on the DRESP1 entry in the QRG and in Remark 7, GPFORCP should be omitted. Avoidance: Single components can be used for the transient responses with no loss of functionality. Mutiple components only simplify the input. 1-16658001 2005 Postprocessing - MSFRACTION - No output written to op2 file No MSFRACTION results are written to the op2 file. 1-16663924 2005 Differential Stiffness - CBAR - Missing UWM 6174 leads to wrong answers Solutions that use differential stiffness (105, 106 and any SOL with STATSUB) that have CBEAM elements with offsets will correctly issue the message below. However; this message may not be issued for similar models with CBAR elements. *** USER WARNING MESSAGE 6174 (EBEMD) BEAM ELEMENT (EID=110) WITH OFFSETS ARE NOT SUPPORTED IN DIFFERENTIAL STIFFNESS OR NONLINEAR ANALYSIS. REMODEL WITHOUT USING BEAMS WITH OFFSET. 0FATAL ERROR 1-16700702 2005 Postprocessing - POST - Missing Output in op2 file If POST NODISP is specified in one subcase then results may be missing from the op2 files in subsequent subcases. 1-16723804 2005 Frequency Response - MEFFMASS - signal 8 MEFFMASS command may lead to the following error on Nastran 2004 HPUX systems: ---------- SIGNAL CAUGHT: Signal number = 8 Signal code = 14 Signal tid = 1 Fault addr = 4000000001352823 FP inexact = 0x0 FP divide0 = 0x8000 FP underflow = 0x0 FP overflow = 0x10000 FP invalid = 0x0 Avoidance: Either remove the MEFFMASS command or run on another machine. 1-16761101 2005 Superelments - EXTSEOUT - Double Field Grids result in SFM 3002 in the BDRYINFO module. External superelements, EXTSEOUT, may fail with SYSTEM FATAL MESSAGE 3200 (LOGIC ERROR 28) in the BDRYINFO module if double field GRID entries are used. Avoidance: Use single field grid entries 1-16769901 2005 Documentation - V2004 DMAP Programmers Guide - UMERGE1 The Version 2004 DMAP programmers guide shows the following for the format of the UMERGE1 module: UMERGE1 USET,A11,A21,A12,A22/MAJOR/SET1/SET2/IOPT $ It should be: UMERGE1 USET,A11,A21,A12,A22/A/MAJOR/SET1/SET2/IOPT $ 1-16771901 2005 Composites - PCOMPG - Strength Ratio may cause composite stress & failure index output error When PCOMPG bulk data entries are used (with a blank FT field) and Strength Ratio output request is turned on (PARAM,SRCOMPS,YES), the composites stress, failure index and strength ratio output may be either missing or incorrect. 1-16815502 2005 Composites - PCOMP - Nastran fails with signal 11 if duplicate IDs for MAT entries exist If a PCOMP entry references a MAT8 entry that has the same ID as another MAT entry, i.e. MAT1, Nastran fails with signal 11 in the log file. No other error messages are given. 1-16821701 2004.5 Installation - HPUX 11 - ERROR: Unable to update RC file MSC.Nastran Version 2004.5 may have trouble installing on older versions of ksh on HPUX 11. If the following messages are encountered during installation then upgrade the ksh to at least 82.10.1.48 which was released in 2002. The error is considered fixed by this upgrade. Begin configuring MSC.Nastran 2004.5 Creating default version links... Configuring licensing... makercentry[4]: /tmp/./msc/conf/nast20045rc: cannot create ERROR: Unable to update RC file "/tmp/./msc/conf/nast20045rc" Setting user configuration items... makercentry[4]: /tmp/./msc/conf/nast20045rc: cannot create ERROR: Unable to update RC file "/tmp/./msc/conf/nast20045rc" makercentry[4]: /tmp/./msc/conf/nast20045rc: cannot create ERROR: Unable to update RC file "/tmp/./msc/conf/nast20045rc" 1-16855001 2005 Nonlinear Analysis - STRESS(PUNCH) - Bad Output in PUNCH File In SOL 106, nonlinear analysis, a request for nolinear stresses to be output to the punch file, STRESS(PUNCH), will lead to NanQ or ????? in the punch file. 1-16858013 2005 Documentation - V2004 DMAP Programmers Guide - MTRXIN description for NOMATi The Version 2004 DMAP Programmer's Guide MTRXIN description for the NOMATi flags indicates that the flags are set to a value of +1 whether the matrix is present or not. The description indicates: NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is generated; 1 otherwise. this should read: NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is generated; -1 otherwise. 1-16877703 2005 Miscellaneous - Disk full on Windows 2000 leads Access Violation A "DISK FULL" condition may lead to an access violation on Windows 2000. Avoidance: This error can be avoided by specifying "sysfield=mapio=no" in a .rcf file or on the command line when the MSC.Nastran job is submitted. 1-16903901 2005 External Superelements - EXTSEOUT - Missing Output An assembly run employing an external superelement created using the EXTSEOUT feature does not give any output for the external SE if the creation run has no DISP request. Avoidance: Apply the following dmap alter to the assembly run: compile extotmin alter 'dbstatus x_tug,x_rga',''(,1) $ dbstatus x_tug,x_tef,x_tes,x_tqg,x_rga// s,n,notug/s,n,notef/s,n,notes/s,n,notqg/s,n,norga $ if ( notug>0 or notef>0 or notes>0 or notqg>0 or norga>0 ) then $ endalter $ 1-16917806 2005 Optimization/Design Sensitivity - DRESP2, DRESP1 - UFM 3007 (dopr3) SOL 200 jobs may fail if DRESP2 entries that reference DRESP2 entires coexist with DRESP2 entries that reference DRESP1 entries. 1-16924801 2005 Miscellaneous - Include may not working on Windows 2000 if file attributes are chaned from default On Windows 2000, if a nastran include data file has the attributes (properties, Advanced, uncheck the "file is ready for archiving" and uncheck the "For fast searching") Then the job aborts. 1-16936701 2005 SOL 700 - SOL 700 in Natran 2004r3 (2004.5) does not work on Windows systems SOL 700 for Natran 2004r3 (2004.5) does not work on Windows systems because the latest Intel compilers provide full path names for the dytran-lsdyna input file and dytran-lsdyna is not able to accept full path names. 1-16937701 2005 Case Control - ESE THRESH does not work when there is no SUBCASE command The THRESH option of the ESE Case Control command does not work if a SUBCASE command is not present. Avoidance: Add a SUBCASE command. 1-16938101 2005 SOL 600 - PCOMP - Wrong Answers when Z0 is specified When translating the Nastran PCOMP enty into a Marc deck, if the Z0 field is specified, then the resulting Marc COMPOSITE entry will be wrong. The current action is to take whatever value is in the PCOMP Z0 field and map it directly into the Marc's COMPOSITE 3rd datablock 4th field. The 'meaning' of the Z0 on the PCOMP entry and this field in Marc are incompatible. In NASTRAN, Z0 on a PCOMP entry defines the distance from the reference plane to the bottom surface of the laminate. In Marc, the field it is mapped to represents the position of the user-defined reference plane. This is the value of the local z-coordinate of the user-defined plane with respect to the geometric midplane. 1-16959902 2005 Superelements - SEEEXCLD - UFM 6788 (SEPMFS) A model that has duplicate boundary grids in the residual structure may fail to exclude the duplicate grid and may fail with the message: *** USER FATAL MESSAGE 6788 (SEPMSF) SUPERELEMENT 1 GRID 3 AND SUPERELEMENT 0 GRID 13 HAVE CONFLICTING MANUAL DIRECTIVES. 1-16989601 2004.0.7 Miscellaneous - IA32 Linux - Include files > 2Gb - UFM 398 Input files greater than 2Gb may not be included in a data file in Versions 2004.0.6 and prior on IA32 Linux systems. Version 2004.0.7 and later systems allow include files greater than 2Gb. Avoidance: If you must use version 2004.0.6 or earlier, then break the include file into separate files each less than 2Gb 1-17011701 2005 Optimization/Design Sensitivity - DRESP2 - Illegal Input to dopr3j When a DRESP2 response in a SOL 200 job intends to reference an existing DRESP1 entry but precedes with a DRESP2 flag, the job fails in DOPR3 with the fatal message "illegal input to subroutine DOPR3J". Avoidance: Specify the correct DRESP1 flag for the referenced entries. 1-17013601 2005 ADAMS/Flex - MNF grid point stress null for quadratic shell mid-side nodes The ADAMS/Flex modal neutral file's modal grid point stress/strain results are null for mid-side nodes of quadratic shell elements due to the fact that nastran does not compute grid point stress results for mid-side nodes of quad8 and tria6 elements. The ADAMS/Flex element face information for elements of these types should contain only the corner grid data and not the mid-side nodes. 1-17055508 2005 Superelements - PARAM,METHCMRS - UFM 3032 In solution 103 if param,methcmrs references an EIGR set id, the job may fail with the message: *** USER FATAL MESSAGE 3032 (READ) UNABLE TO FIND SELECTED SET ( 2000) IN TABLE (EED ) IN SUBROUTINE (REIG). Avoidance: Insert the following DMAP alter: compile phase0 alter 'SEP2.*nGEOM1,GEOM2,GEOM3,GEOM4'(2) if ( seid=0 ) equivx dynamic/dynamics/-1 $ endalter 1-17064430 2005 Distributed Memory Parallal - User must specify F2 on EIGR entry If a dmp job only specifies ND on the EIGR entry using method LAN and the DOMAINSOLVER entry specifies the partopt=freq option the job may attempt to solve all frequencies on all processors. Avoidance: The user must select F2 on the eigr entry. 1-17071801 2005 Miscellaneous - INPUTT2 - OP2 files with matrices and tables may lead to UFM in INPUTT2 OP2 files with intermixed tables and matrices that were correctly read in MSC.Nastran V2004.0.6 fail in V2004.5. The problem is caused because code handling end of matrix condition did not properly accept all valid conditions. corrected inputt2 per jas. 1-17081504 2005 Submittal - node=machine does not work on NT The node=machine nastran submit line option cannot be used from NT to a dissimilar machine. 1-17104601 2005 SOL 600, SOL 700 - Windows Version 2004.5 not useable The switch to Intel Version 8 compiler in MSC.Nastran Version 2004.5 for Windows caused many problems in SOL 600 and SOL 700. Thus, this release should not be used for SOL 600 and 700 on Windows. 1-17148302 2005 Optimization/Design Sensitivity - DOPR1, PCOMP - Poor Message, Illegal input to DOPR1I A composite optimization job fails in DOPR1 with "Illegal Input to Subroutine DOPR1I" if the following two conditions are met: 1. The integer input with FID option is used to sepcify a designed laminate thickness or ply angle on a DVPREL1/2 entry and 2. The laminate thickness or ply angle that the FID represents is Not defined on a PCOMP entry. For example, only two laminates are defined on a PCOMP entry but the FID field on a DVPREL1 entry references the thickness for the third laminate. Avoidance: Only design the laminate thickness or ply angle on a DVPRELi entry that is defined on a PCOMP entry. 1-17177340 2005 Aeroelastic Analysis - Direct Enforced Motion, wrong results Solution 146 produces wrong results showing when direct enforced motion is used. The call to subDMAP SUPER3 with AULF is missing data block RGY (penultimate input data block). This may cause some grids to deflect incorrectly. Avoidance: PARAM,DDRMM,-1 will also avoid the data recovery error. 1-17194201 2005 ESE - UWM 4506, UIM 4507, subcase, TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 0.0 If a job incorrectly specifies SUBCASE1 with no space instead of SUBCASE 1, the subcase number is read as zero. If ESE output is requested, UWM 4506 and UIM 4507 may be issued indicating the total strain energy is zero. No warning message is given that the SUBCASE entry is in error. The ESE output shows TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 0.000000E+00 and no list of strain energies by element is output Avoidance: Correct the SUBCASE entry to leave a space between the word SUBCASE and the 1 1-17202601 2005 Acoustics - DAREA entries not converted to static loads if they reference fluid points Currently, DAREA entries are not converted into equivalent static load entries if they reference fluid grid points. 1-17203001 2005 Distributed Memory Parallel - MDACMS with ESE fails if PARAM,POST specified Parallel MDACMS with ESE request and PARAM,POST will fail since slave processes are not prevented from attempting to write to the output2 file. Solution is to modify the DMAP to call OUTPUT2 only on the master. (Alter can be generated on request.) 1-17210346 2005 Lama table not output2 with post,-2 lama table not output2 with param,post,-2 avoidance is to also use param,postext,yes. However, this writes more files. Also PVT0 is missing from op2 file. 1-17242803 2005 Post Processing - Incomplete XDB File The DBC/XDB object in the dictionary does not contain the correct control information, it contains the original object template when the create function completes. This may lead to an incomplete xdb file which may cause post processers to fail. This error has only been observed for one test file that contained 55 subcases. Avoidance: A possible avoidance is to change the block size of the xdb in the FMS section. 1-17252901 2005 External Superelements - UFM 1126, Datablock GOA already exists In Version 2004.5 an external superelement reduction run with ACMS results in the following fatal message: *** USER FATAL MESSAGE 1126 (GNFIST) DMAP MODULE UMERGE1 IS ATTEMPTING TO OUTPUT DATABLOCK 201 NAME = GOA , WHICH ALREADY EXISTS. Avoidance: Insert following DMAP alter: compile phase1b alter 'call segoa'(9,-1) delete /goa,,,, $ endalter 1-17280829 2005 Documentation/QRG - Release Guide, ASSIGN - Output2 Example 4 under the ASSIGN FMS statement is incorrect. The current example is as follow: assign op2 bigendian' ... assign op2='test_op2.12' unit=12 assign op2='test_op2.35' unit=35 form=formatted The op2 logical name is assigned to unit 12 and this unit number should not be changed on the assign statement. This is usually used for param,post-1 and param,post,-2. The example should be modified as follow: assign op2 bigendian ... assign op2='test_op2.12' assign output2='test_op2.35' unit=35 form=formatted 1-17282301 2005 File Management Section - DBLOCATE - SFM 1013 Three successive DBLOCATE commands, the first 2 with NOCOPY and the last one with the COPY option, results in the following fatal message: *** SYSTEM FATAL MESSAGE 1013 (GBKMGX) CANNOT FIND CORRECT CLUSTER POINTER RECORD BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGX , FILE INDEX = 0. STATUS = 0 Avoidance: Do not mix COPY and NOCOPY options. 1-17297801 2005 Distributed Memory Parallel - EXTSEOUT - SFM 3008 UTMCOR In MSC.Nastran 2004r3(2004.5) a dmp run with external superlements may fail with the message: *** SYSTEM FATAL MESSAGE 3008 (UTMCOR) MODULE = MDENZO INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ENZO2 PROGRAMMER INFORMATION: LOCATION KEY = READ IN P Avoidance: Run without dmp or apply the following alter: compile cmpmode alter 'call mdacms ' (,-1) $ if( nproc>0 ) putsys(nproc,231) $ alter 'if ( fdcmrrs', '' $ if ( fdcmrrs OR mdacms ) then $ alter 'paraml cmphixz', '' $ paraml cmphixz//'trai'/1/s,n,nozset $ 1-17297961 2005 Installation - FLEXlm installation not handled correctly on hpia64 The current 'mscsetup' script correctly accounts for the hpuxia64 being distinct from hpux, as far as Patran and Nastran installs are concerned, however, when installing a FLEXlm server, the scripts in the .../msc/bin directory (flexlm, lm*) are based off an older mscsetup that does NOT account for the distinction as such, running those scripts on an IA64 will still search for the default 'hpux' location, when the install actually created an 'hpuxia64' folder, and the script will fail 1-17303819 2005 DMAP/Matrix Methods - SMPYAD method ABA wrong results for complex matrices The SMPYAD module ABA method produces wrong results for complex matrices under the following conditions: 1. Spill (multiple passes) used. 2. Triple loop kernels used. Avoidance: Set sys129=1 to bypass the ABA method. 1-17303823 2005 Acoustics - METHOD(FLUID) - Missing output and wrong answers For acoustics, if a METHOD(fluid) entry is not present in the Case Control, the fluid eigensolution is not performed. This conflicts with design intent and Remark 3 under the METHOD command in the QRG. Avoidance: Specify a METHOD(FLUID) entry in Case Control. 1-17322311 2005 Buckling Analysis - multiple buckling subcases - UWM 73, Wrong answers In buckling analysis UWM 73 will be issued if there are more than two buckling subcases in the following solution sequence: 1. SOL 105 with scr=no 2. SOL 200 with ANALYSIS=BUCK regardless of scr keyword Avoidance: Insert the following DMAP alter: compile super3 alter 'DBVIEW