This file contains all errors corrected in MSC.Nastran 2004.0.x releases. The MSC.Nastran 2004R2 CD will contain Version 2004.0.6 with all these error corrections. 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. 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 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-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. 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-12738305 2004.0.4 Distributed Memory Parallel - SFM 7796 (DFMAN) 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-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-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-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 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-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 othe 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.3 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 = ... Data is in /nast/app/etl/v2004 (two input files a and b). 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. 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.6 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 - Missing output If the MCFRAC case control command selects a SET that contains and 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-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 2004.0.4 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-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-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-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-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. 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-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-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-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-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