@ 5802; ; Material Nonlinear Analysis - TEMP(LOAD) - Superelements vs. Non -Superelements If superelements are used in a nonlinear run with temperature dependent material properties, the superelement properties are calculated using the TEMP(INIT), rather than the TEMP(LOAD). This is a limitation since superelements are linear, their material properties are not changed during the analysis. This can lead to different answers when comparing superelement models to non-superelement models. Avoidance: In order to use the TEMP(LOAD) for the material properties, use the following DMAP alter in Version 68: COMPILE SELG, SOUIN=MSCSOU, NOLIST, NOREF ALTER 11,11 SSG1 SLT,BGPDTS,CSTMS,SILS,EST,MPTS,ETT,EDT,MJJ,CASESX, DIT,,,,/PJX,PTELEM,/LUSETS/1//'NLST' $ @ 5803; 69; Miscellaneous - GINO - SYSTEM FATAL ERROR (bio_c.read) UNIX versions of MSC/NASTRAN Version 68 and MSC/EMAS Version 3 may report a SYSTEM FATAL ERROR (bio_c.read) in the LOG file but will complete the job normally. Avoidance: No avoidance is necessary, the error message can be ignored. @ 5804; 7 "NSINIT ERROR 20 *** SYNTAX ERROR IN CONTROL FILE"or "UFM 17 UNIDENTIFIED NASTRAN CARD KEYWORD" occurs if NASTRAN OLDQ4K is placed in a runtime configuration file or the data deck. Refer to section 3.4 of the MSC/NASTRAN Version 68 Installation and Operation Instructions for information on the location and format of the runtime configuration files. Avoidance: Two avoidances exist. Either OLDQ4K can not be the first system cell on the NASTRAN command line or the equivalent system cell, SYSTEM(173), must be used in place of the keyword. @ 5805; , UIM 4550 ; Nonlinear Transient Analysis - NLTRD, RESTART - SFM 4276 EC 1044 69; Miscellaneous - RC File - NASTRAN OLDQ4K, NSINIT ERROR 20, UFM 1

IF a model containing superelements is executed in solution 106, and then restarted into solution 129 (using PARAM, SLOOPID), and the "METHOD" field on the TSTEPNL entry is set to AUTO, then the job fails and the following fatal message is issued: SYSTEM FATAL MESSAGE 4276 ERROR CODE 1044 (BIOMSG: ERROR 1044 HAS OCCURRED IN ROUTINE OPEN FILE INDEX (FILEX) = 0) Immediately preceeding this fatal message, USER INFORMATION MESSAGE 4550, NEW STIFFNESS MATRIX REQUIRED is issued. This error may happen even though the nonlinear iteration module output indicates that all time-steps have been successfully completed.

Avoidance: Use the default ADAPT method. @ 5807; 70; DMAP - COMPILE - UFM 423 If a user attempts to compile a user dmap where the name of the dmap begins with the letter "E", the job may fail with the message "USER FATAL MESSAGE 423 (ATTDBS) THE FOLLOWING PHYSICAL FILE DOES NOT EXIST /msc/msc68/emas3/sunos/del/ESS.MASTERA". Avoidance: Change the main dmap and SOL name so that it does not begin with "E". This apparent error is the result of an MSC/NASTRAN feature that will run MSC/EMAS if a deck with a 'SOL 300' or 'SOL E*' entry is submitted. If such a SOL entry is found, the script attempts to attach the MSC/EMAS Solution Sequences. This delivery database does not exist in a pure MSC/NASTRAN installation. @ 5808; 68.2; Differential Stiffness and Buckling - EIGRL, EIGB - Wrong Answe rs or UFM 4683 If the a-set and g-set are the same (no SPCs, MPCs, or reduction) in any superelement or the residual structure, then the differential stiffness matix used in solution 105 (buckling) or the buckling option in solution 200 will not be correct. The error may lead to wrong answers or "USER FATAL MESSAGE 4683, DIFF. STIFFNESS MATRIX NEEDED FOR EIGENVALUE ANALYSIS". DMAP avoidance: COMPILE SEKDR, SOUIN=MSCSOU, NOLIST, NOREF $ ALTER 42, 42 $ EQUIVX KDGGX/KDAA/-1 $ @ 5819; 69; Static Analysis - TEMP(LOAD), LSEQ - UFM 9058 If the LOADSET, LSEQ combination and TEMP(LOAD) are specified in MSC/NASTRAN Version 68, then "USER FATAL MESSAGE 9058" may be issued in SOL 101. This error occurs when there are unreferenced LSEQ entries. Avoidance: Remove the unreferenced LSEQ entries or insert the following alter: compile sestatic souin=mscsou noref nolist alter 59 $ PARAML CASEsx//'DTI'/nskip/7//S,N,TEMPLD $ @ 5820; 68.2; Optimization/Design Sensitivity - ANALYSIS=SAERO - Wrong Answers Applied loads, for example to simulate subcase dependent fuel loads, are ignored and wrong answers are produced if a static aeroelastic design task is submitted in solution 200. Avoidance: Insert the following DMAP avoidance: compile phase1dr souin=mscsou nolist noref alter 81,81 alter 89 equivx casesx/casew/-1 $

@ 5823; forces 68.1; Inertia Relief - Multiple Subcases, SUPORT1 entries - Wrong SPC If inertia relief is used in conjunction with multiple subcases each referencing a different set of SUPORT DOFs, then the spcforces will be incorrect. This is a Version 68 error since prior versions do not support multiple inertia relief sets. This feature is activated with the use of the SUPORT1 entries. Avoidance: Insert the following DMAP alter avoidance. compile sestatic souin=mscsou nolist noref alter 100,100 $ CALL SUPER3 CASECC, ,UL, , , , , , , , CRX, , ,,,, PCDB,XYCDB,POSTCDB,FORCE,EMAP,MAPS,EQEXINS, PVTS,CASES,SLT,ETT,GOAT,,LOO,CRJ,LAO,UOO,UOX,GPLS,USET, SILS,PJ,EDT,YS,GM,PSS,KFS,KSS,QR,,,,,, DYNAMICS,BGPDTS,CSTMS,MPTS,DIT,EST,GEOM2S,GEOM3S,ECTS, EPTS,INDTA,KELM,KDICT,GPECT,VELEM,,SILX,EQEXINX,ECTX, BGPDTX,,GEOM4S,PG,,,,EPT,MPT,GEOM1,GEOM2,GEOM3,GEOM4, PTELEM,,, ,,MEDGE,VIEWTB,ESTVU,GEOM1VU,SILVU, CSTMVU,DEQATN,DEQIND,GDNTAB,OINT,PELSETS, KSF,KMG,,,,,,,,,,,,/ UG,QG,CASEDR,XYCDBDR,PUG,GPSF, , OUG1,OPG1,OQG1,OEF1,OES1,OEE1,OGPS1, OUG2,OPG2,OQG2,OEF2,OES2,OEE2,OGPS2, OESM1,OESG1,OEEM1,OEEG1,GPS,ONRGY,OGPFB/ APP/APP/RSONLY/FALSE /FALSE /FALSE/DROPT/FALSE/ S,PFILE/S,CARDNO/0/FALSE/0/PEXIST/ ADPTINDX/ADPTEXIT $ $ @ 5829; 69; Plotting - SEUPPLOT - Missing Plot Output In SOL 103, if the SEUPPLOT command is used to generate assembly plots, plots will be available for only the first half of the modes in the solution. Avoidance: Apply the following DMAP avoidance in Version 68: compile semodes, souin=mscsou, nolist, noref alter 1 $ disable scratch LTU logic - otherwise the datablocks will $ not be there when needed for plotting putsys(0,192) $ compile sedrcvr, souin=mscsou, list, noref alter 1 type db,phidlg $unused datablocks in SOL 103 $ alter 48 $ after sdr2 copy ug/ugcopy $ append ug,ugcopy/ugtwice $ get "double" set of solutions $ SDR2 to get "double plot vectors"

message //'seid='/seid $ SDR2 CASEDR,CSTMS,MPTS,DIT,EQEXINS,,ETT,OL2,BGPDP, PJ1,QG,UGtwice,EST ,XYCDBDR,OINT,PELSETS,VIEWTB/ ,,OUGVxxx,,,phidlg/APP1/S,N,NOSORT2xx/ NOCOMPS/////ACOUT/PREFDB/-1./-1./ ADPTINDX/ADPTEXIT/FALSE $ $ compile super3, souin=mscsou, list, noref alter 227,227 $ replace PLTVEC type db,phidlg dbdict datablk=(phidlg,phidrg,pug), select(name,size,seid,peid,zname,version) $ DBVIEW PhidlgF=Phidlg (WHERE SEID=* AND WILDCARD=TRUE) $ PLTVEC EMAP,DRLIST,PCDB,EQEXINX,SILX,SILSF,GPLSF,phidlgf/ PUGX,PCDBX/SEID/'SEID' $ @ 5831; 68.2; DMAP - MATMOD, FBS, TRNSP - Wrong Answers, SFM There is a special form of an identity matrix called a form 8. Conventional identity matrices are form 6. This type of matrix can be generated with MATMOD option 2, or may be generated internally in modules. The new sparse options may have trouble with this form of matrix. Troubles observed to date include: Wrong answers from FBS when more than one pass is required. The symptoms for the FBS problem found to date include a solution which has about 50% more non-zero terms than it should. A SYSTEM FATAL MESSAGE in the TRNSP module. Avoidance: The error in FBS may be avoided by switching back to the non sparse methods by setting SYSTEM(126)=1. It is recommended this be done only locally around the offending module with PUTSYS statements. The error in TRNSP may only be avoided by producing a form 6 identity matrix. MATMOD option 1 outputs a conventional identity matrix. @ 5835; 68.0.2; Miscellaneous - RC File - Directory Does Not Exist If a scratch directory is specified in an RC File that does not exist, the run fails even though a directory that does exist is specified in a subsequent RC File that is meant to take precedence over the first specification. Avoidance: Change the directory specification to a directory that exists. @ 5838; 69; Loads - TEMP(LOAD) - UWM 4012, UFM 4017 When doing a static analysis with temperature loads in Version 68, it is necessary to specify the temperature for all grid points in the model. If this is not done, the following messages will be issued, "USER WARNING MESSAGE 4012, THERE IS NO ELEMENT, GRID POINT, OR DEFAULT TEMPERATURE DATA FOR TEMPERATURE SET 102, WITH RESPECT TO ELEMENT ID = 0","USER FATAL MESSAGE 4017. THERE IS NO TEMPERATURE DATA FOR ELEMENT 15 IN SET 2". Unfortunately, the element ID and set numbers are incorrect. Avoidance: Always include a TEMPD bulk data entry in any static analysis with temperature loads.

@ 5839; 68.2; Heat Transfer - heatconv, SPC - Cannot Convert Large Field Forma t, Wrong Answers The heatconv program does not correctly handle all large field SPC entries. In particular, given the following large format SPC entry: SPC* 2.00000000E+01 1 1 1

heatconv will incorrectly copy this to a small format entry as follows: SPC 1 1 1 2.000000

Whenever the temperature fields, i.e., fields 5 & 8, exceed eight characters in length, incorrect results will occur.

@ 5841; 2001.0.1; Composites - PCOMP, MAT2 - UFM 4291 Certain MAT2 entries that are referenced from a PCOMP are not checked for correctness. In particular, if 13 and/or 23 terms are non-zero and the 33 term is zero, the matrix is not positive definite. In this case MSC/NASTRAN will create potentially incorrect PSHELL/MAT2 combinations from the PCOMP/MAT2 inputs. Avoidance: Enter a positive definite MAT2 entry. @ 5843; 68.2; P-Elements - RFORCE - Wrong Answers or SFM 4276 Although it is not documented, RFORCEs are not implemented for p-elements. If RFORCES are applied to p-elements either wrong answers or a SYSTEM FATAL MESSAGE 4276 results. Avoidance: Do not apply RFORCEs to p-elements. @ 5844; 69; P-Elements - HEX20, PENTA15, TETRA10 - Missing Documentation The CHEXA element with 20 grids, the CPENTA element with 15 grids, and the CTETRA element with 10 grids may not be used as p-elements by referencing the PVAL entry. If attempted, the following message is issued: *** USER FATAL MESSAGE 6390, (GP0A), ELEMENT ID = 1 TYPE HEXA20 OR PENTA15 AND/OR TETRA10 ARE NOT SUPPORTED IN P-ELEMENT ANALYSIS. USER ACTION: CHECK ELEMENT CONNECTION ENTRY OR SET ENTRY. @ 5848; 68.2; Optimization/Design Sensitivity - DSCREEN - Poor Convergence The DSCREEN entry permits the user to override default screening parameters for design optimization. This capability does not work for responses TDISP,TVELO,TACCL,TSPC,TSTRE,TFORC,TRIM,STABDER and FLUTTER. Avoidance: The only avoidance is to do a TABEDIT on the DSCREN datablock. The following words correspond to the data locations for the responses

TDISP TVELO TACCL TSPC TSTRE TFORC TRIM STABDER FLUTTER

TRS 179 182 185 188 191 194 245 248 251

NSTR 180 183 186 189 192 195 246 249 252

A candidate DMAP for performing the TABEDIT is: compile desopt souin=mscsou nolist noref alter 41 $ call dbstore dti,dtindx,,,//1/2/'dball'/0 $ compile predom souin=mscsou nolist noref alter 12 $ call dbfetch /dti,dtindx,,,/1/2/0/0/0 $ dtiin dti,dtindx/control,,,,,,,,, $ tabedit dscren,control,,,/ndscren/-1 $ equivx ndscren/dscren/always $ $ $ the following dti modifies word 195 as required $ for a TFORC request and nstr $ dti,control,0 dti,control,1,cr,1,dw,195,195,1 ,1 dti,control,2,er,endrec $ @ 5849; 68.1; Matrix Methods - FBS - UWM 4398, Wrong Answers MSC/NASTRAN Version 67.7 and 68 on the CRAY C90 computer may produce wrong answers for models where FBS method 2 is selected. The error may be evidenced by "USER WARNING MESSAGE 4398" which indicates "DEGREES OF FREEDOM DO NOT PASS SYMMETRY CHECK". The error only occurs when there are strings in the factor that are longer than 64 terms. Note that except in superelement models, that FBS method 2 is rarely selected. Avoidance: FBS Method 2 should be deselected by setting "FBSOPT=-1" in the system RC file on Version 67.7 and 68 CRAY C90 computers. @ 5850; Buffer 68.1; Miscellaneous - IFP, XRCARD - Infinite CPU Loop, Overflow Input Some invalid bulk data input may result in an infinite cpu loop in the routine XRCARD. Although the exact type of input that results in this error is not known, the specifics of the input line that resulted in this error is that the line was over 80 characters, contained many leading blanks and included an embedded negative, "-", sign. The infinite cpu loop has only been reproduced on the CRAY computer but may occur on other systems. Avoidance: There is no practical avoidance. @

5852; x

; Documentation - DMAP Module Dictionary, MODTRL - Bad Input Matri If the MODTRL module is used to increase the number of columns in a matrix, the resulting matrix is unusable in most modules, including matprn and ADD. The cause of the error is that the matrix does not have column headers for the added null columns. Avoidance: The MATGEN and ADD module should be used to increase the number of columns in a matrix. An example follows: matgen ,/nullab/7/rn/cn $ null matrix with rn rows and cn cols. user must set rn and cn above. add nullab,oldmat/newmat $ trailer will match first input equivx newmat/oldmat $ oldmat is now 'bigger'

@ 5858; 68.2; Optimization/Design Sensitivity - SPCFORCE and MPCFORCE - Wrong Answers If scr=yes is used in SOL 200 with dynamic optimization or sensitivity, then MPCFORCE and SPCFORCE output does not include mass and damping effects after the first design cycle. (Version 68 only) Avoidance: Specify scr=no. An extensive DMAP alter is also available if scr=yes is desired. @ 5860; 69; Aeroelastic Analysis - GI, CAERO1, CAERO2 - Wrong Answers MSC/NASTRAN Version 68 on Sun computers may produce wrong answers for aeroelastic flutter problems when aerodynamic bodies, i.e. CAERO1 or CAERO2 elements, are present. Avoidance: There is no avoidance. @ 5861; 69; Dynamics - PARAM,MODACC - Poor Displacement Results The mode acceleration method is intended to improve element stress data recovery in dynamic solutions using modal formulations. However an error may occur in the total displacements when free-body motions are present. This error will NOT affect strains, stresses or constraint forces. The major problem is that the angular displacements or pointing directions will be affected. The problem occurs because the "improved" relative displacements are not orthogonal to the free-body modes and create small additional displacements and rotations. The error is proportional to the local frexibility of the SUPORT degrees of freedom. This error is considered fixed in Version 69 by the addition of a new mode acceleration option which is selected by setting PARAM,MODACC,1 instead of PARAM,MODACC,0. The avoidance is to use conventional dynamic recovery methods in a modal formulation when free-body modes are present. The "Residual Vector" method is an accurate alternative. @ 5862; ; Database - DBUNLOAD - UFM 3007, illegal input to subroutine PVT If the dbunload is done on a long word machine such as Cray and dbload is

attemted on a short word machine, then UFM 3007, illegal input to subroutine PVT may be issued. This error occurs only if the initial run which created the databases had parameter specifications in the Case Control. This occurs since the diliminator for the parameter in the Case Control is machine dependent. Avoidance: There are two avoidances: 1. Remove the parameter specifications from the initial run which creates the databases. or. 2. Use the following alter in the dbload run. ACQUIRE NDDL ASSIGN DBLOAD='neutrala.cray',FORM=FORMATTED DBLOAD FORMAT=NEUTRAL $ $ avoidance is to add the following alter $ $ SOL DBTRANS TIME 5 compile dbtrans souin=mscsou list noref alter 114,114 CEND BEGIN BULK ENDDATA @ 5863; 68.2; P-Elements - GP4 - UFM 4276, CSTM DOES NOT EXIST (GP4) If a model contains p-elements and there is insufficient memory in the GP4 module the message "USER FATAL MESSAGE 4276, CSTM DOES NOT EXIST (GP4) may be output. Avoidence: Request more memory and rerun the job. @ 5864; atives 68.2; Aeroelastic Analysis - DIAG 50 - Unsplined Rigid Stability Deriv For Version 68, static aeroelastic analyses (SOLs 144 and/or 200) produce Unsplined Rigid Stability Derivatives. These data are presented only to provide a check of the splining and are not used in the solution. For antisymmetric models and models with no symmetry (SYMXZ = -1 or 0), the numbers may be in error. For sideforces the error is likely to be simply one of sign. For yawing and rolling moments, the error is less obvious. @ 5866; 68.2; Heat Transfer - RADMTX - Duplicate Continuation Entry with Multi ple Cavities For the multiple cavity radiation view factor calculation, each cavity will have a RADLST and RADMTX entry associated with it. The punch file which contains the MSC/NASTRAN calculated RADMTX entries for each cavity contains duplicate RADMTX continuation identifiers. Thus, subsequent restarts using the punch file fail.

Avoidance: Since continuation identifiers are not necessary if the input is in sequential order, blank out all the continuation identifiers in field 10 and field 1 of the RADMTX entries. @ 5867; s The Quick Reference Guide indicates that the DTOR value input on the SPLINE2 entry must be greater than 0.0. However, this requirement is never checked. If the user leaves DTOR field blank the run could give wrong answers or fail due to a singular spline matrix. Avoidance: Specify a value greater than 0.0 for DTOR. @ 5868; d List 68.1; Installation - Authorization - UFM 3060, BUCKLING not in Approve An authorization code for the workstation option is suppose to include statics, normal modes and buckling. An error in the authorization code generator resulted in workstation options not including buckling. Avoidance: The error in the authorization code generator has been corrected. Contact MSC for a new code. @ 5870; 68.2; Multipoint Constraint - SPOINT - UFM 2101A DOF, Wrong Answers. If the user inadvertently specifies a degree of freedom greater than 1 for an SPOINT in an MPC equation, then wrong answers may result or the message "USER FATAL MESSAGE 2101A, GRID POINT xxx COMPONENT yyy ILLEGALLY DEFINED IN SETS zzz" may be output referring to the wrong grid point/degree of freedom. Avoidance: Other than correcting the SPOINT degree of freedom, there is no avoidance. @ 5871; 68.2; Restarts - RESTART PROJECT - Inefficient Restart In Version 68, the PROJECT keyword is ignored on the RESTART statement which will result in an inefficient restart. For example, 1. The initial run creates project A: PROJECT='A' ASSIGN MASTER='A.MASTER', DELETE 2. The subsequent run restarts from project A into project B: PROJ='B' ASSIGN MASTER='A.MASTER' RESTART PROJECT='A',KEEP Avoidance: For SOLs 101 through 200 insert the following DMAP alter: compile ifpl souin=mscsou noref nolist alter 80,80 type parm,,i,,projid=1,versid=1 $ projid=1 $ set the projid to the integer equivalent of the project you are restarting from. versid=1 $ set the versid to the version you are restarting from $ dbdict datablk=geom1q $ 68.2; Mulitpoint Constraints - SPLINE2 - Singular Matrix, Wrong Answer

alter 118,131 DBVIEW GEOM1R=GEOM1Q(WHERE version=versid and PROJECT=PROJID) $ DBVIEW GEOM2R=GEOM2(WHERE version=versid and PROJECT=PROJID) $ DBVIEW GEOM3R=GEOM3(WHERE version=versid and PROJECT=PROJID) $ DBVIEW GEOM4R=GEOM4(WHERE version=versid and PROJECT=PROJID) $ DBVIEW EPTR=EPT(WHERE version=versid and PROJECT=PROJID) $ DBVIEW MPTR=MPT(WHERE version=versid and PROJECT=PROJID) $ DBVIEW EDTR=EDT(WHERE version=versid and PROJECT=PROJID) $ DBVIEW DITR=DIT(WHERE version=versid and PROJECT=PROJID) $ DBVIEW DYNAMICR=DYNAMIC(WHERE version=versid and PROJECT=PROJID) $ DBVIEW AXICR=AXIC(WHERE version=versid and PROJECT=PROJID) $ DBVIEW PVTR=PVT(WHERE version=versid and PROJECT=PROJID) $ DBVIEW MATPOOLR=MATPOOL (WHERE version=versid and PROJECT=PROJID) $ DBVIEW caseccrr=caseccr (WHERE version=versid and PROJECT=PROJID) $ DBVIEW EDOMR=EDOM WHERE (version=versid and PROJECT=PROJID) $ compile phase0 souin=mscsou noref nolist alter 281,297 type parm,,i,,projid=1,versid=1 $ projid=1 $ set the projid to the integer equivalent of the project you are restarting from. versid=1 $ set the versid to the version you are restarting from $ DBVIEW CASESR=CASES (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW GEOM1SR=GEOM1S (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW GEOM2SR=GEOM2S (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW GEOM3SR=GEOM3S (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW USET0R=USET0 (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW RMGR=RMG (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW YGR=YG (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW DYNAMCSR=DYNAMICS (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW EPTSR=EPTS (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW MPTSR=MPTS (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW MAPSR=MAPS (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW PVTSR=PVTS (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW BACKR=BACK (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW HARMR=HARM (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW KVALR=KVAL (WHERE version=versid AND PROJECT=PROJID) $ DBVIEW FORER=FORE (WHERE version=versid AND PROJECT=PROJID) $ alter 352,352 DBVIEW EQEXINSR=EQEXINS (WHERE version=versid AND PROJECT=PROJID) $ @ 5876; , SCR300 69; File Management Section - EXPAND, RESTART - SFM 4276 XIO, EXPAND

An attempt to expand a database fails when restart is attempted in the same run. A sample File Management Section demonstrating the error follows: assign dbup1a='scr7a.dbup1a' expand dbup1, logical=(dbup1a(100)) restart version=1 keep The sample input leads to the following fatal message due to the scr300 file being improperly defined: "SYSTEM FATAL MESSAGE 1030 (XIO) BLOCK NUMBER MISMATCH IN READ SYSTEM FATAL ERROR 4276.XIO ERROR CODE 4276"

Avoidance: 1) run an "expand" job only (i.e. expand and endjob) 2) run the restart job @ 5877; 67.5.0.1; Miscellaneous - SCO/UNIX - UFM 3060 The SCO/UNIX Version 67.5 of MSC/NASTRAN may issue "USER FATAL MESSAGE 3060" indicating authorization code violation during long running job with many module changes (e.g. nonlinear). Avoidance: There is no avoidance. This problem will be fixed on a rerelease version (MSC/NASTRAN v67.5.0.1 for SCO/UNIX). @ 5878; 69; Sequencer - SEQP - SFM 3008, Insufficient Memory A small p-element model ( 1 Hexap and 2 Pentap ) fails in the sequencer, module SEQP, with the following error message from subroutine seqos: SYSTEM FATAL MESSAGE 3008 MODULE = SEQP 0INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE SEQOS Avoidance: Avoid the sequencer by setting PARAM,NEWSEQ,-1. @ 5880; 68.2; P-Elements - TEMP - UFM 4017 All p-version models which contain thermal loads via TEMP entries and more than one type of solid element (HEXA, PENTA, TETRA), fail with the following fatal message, "USER FATAL MESSAGE 4017. THERE IS NO TEMPERATURE DATA FOR ELEMENT y IN SET x". Avoidance: If the thermal loading is a uniform temperature increase throughout the entire structure, use a TEMPD Entry. Otherwise, the user must use an equivalent TEMPF Entry. Also, it may be possible to use only one element type in the model. @ 5881; 69; Documentation - PARAM,BAILOUT - Missing Documentation MSC/NASTRAN Version 68 supports multiple boundary conditions in the structured solution sequences. However, PARAM BAILOUT cannot be changed between subcases. @ 5889; 68.2; Optimization/Design Sensitivity - DRESP2 - Wrong Answers If a DRESP2 entry refers to two or more DRESP1 entries and there are DVPREL2 entries in the input file, then the sensitivities printed in the columns of the DSCM2 matrix associated with the DRESP2 entry are in error. Avoidance: There is no avoidance other than to recast the problem so that it does not require the offending DRESP2,DRESP1,DVPREL2 combination. @ 5891; 70.5.1; Elements - PENTA - Possible Wrong Answers, UFM 4654 If a pyramid-shaped degenerate PENTA element is input to MSC/NASTRAN, USER

FATAL MESSAGE 4654 is issued warning of two corner points with the same coordinates but the run will continue. Pyramid-shaped PENTA elements are not supported and should not be used. @ 5893; 002 69; Sequencer - SEQP, PARAM,NEWSEQ,6 PARAM,OLDSEQ,6 - SFM 4276, EC 3 It is possible that jobs that request param,newseq,6 prior to Version 69 or param,oldseq,6 in Version 69 and after may encounter SYSTEM FATAL MESSAGE 4276, ERROR CODE 3002 in the SEQP module. By default sequencing in the SEQP module was turned off in Version 69 and beyond. PARAM,NEWSEQ was changed to PARAM,OLDSEQ to force the user to go out of his way to request sequencing. Thus, this error is considered corrected in Version 69 by the fact that sequencing is no longer recommended. @ 5894; 2001; Transient Response Analysis - TIC - Initial Conditions Not Refle cted in Results An initial velocity, V0, TIC (transient initial condition) is not properly reflected in the Velocity (first time derivative) results. The discrepancy between the value specified and the value output occurs because the program uses a central difference approach. The displacements are correct. @ 5896; 68.2; Miscellaneous - NASTRAN SYSTEM(i) - Bad Processing Order MSC/NASTRAN processes systems cells specified by the format "NASTRAN SYSTEM(i)=value" before those specified by "SYSTEM(i)=value". Thus system cells specified in the latter format will take precedence regardless of where they are specified. Avoidance: Always use the format "NASTRAN SYSTEM(i)=value" in the system, architecture, user, and local RC files. @ 5900; GL; Material Nonlinear Analysis - RESTART, NLPARM - DIM 9005, UFM 20 44, SFM 3007 If thermal loads are applied in a SOL 106 cold start, and, if in the restart, PARAM,LOOPID is not the last loop id for the subcase prior to PARAM, SUBID then the program will issue various misleading fatal messages. In one example the message "USER FATAL MESSAGE 2044 UNDEFINED TEMPERATURE SET, SYSTEM FATAL MESSAGE 3007 MODULE=NLCOMB ILLEGAL INPUT TO SUBROUTINE NLCPTM" was encountered. Avoidance: Other than specifying the correct LOOPID, there is no avoidance. @ 5901; 68.2; Installation - Multiple Auth Codes - Only One Code in Auth File If authorization codes for MSC/EMAS and MSC/NASTRAN are entered at different times during the same installation, only the last code entered is placed in the authorize.dat file. Avoidance: Enter all codes for all products at the same time in the installation. The installation script allows you to enter a series of codes. If one of the products is using an existing authorize.dat file, modify the appropriate /conf/"rc file" to have the AUTH

keyword point to the correct file. @ 5911; 68.2; Complex Eigenvalue Analysis - SPCForces - Wrong answers In MSC/NASTRAN Version 68, the SPCForce results are incorrect in SOLs 107, 110, and 145 only. The SPCForces do not include the effects of the imaginary part of the eigenvalue which results in "undamped" SPCforces. Avoidance: Insert the following DMAP alter. COMPILE CFORCE SOUIN=MSCSOU noLIST NOREF $ ALTER 47,47 $ replace DSAP PARAML OL//'TRAILER'/1/S,N,NFREQS $ NUMBER OF Eigenvalues TYPE PARM,,I,N,II=0,iip3,iip4 $ LOOP COUNTER TYPE PARM,,CS,N,IOMEGAX,MOMEGX $ FILE qx1=APPEND $ DO WHILE (II-1) then $ MPYAD A,B,C/D $ else $ EQUIVX C/D/-1 $ endif $ @ 5974; 68.2; Miscellaneous - Accounting Files do not Include the Time Zone The accounting files generated on some versions of AIX will not include the time zone when LANG="". Since the various scripts must set this to function properly, the only recourse is for the execution and accounting summary scripts to account for this potential discrepancy. Avoidance: The running summary written by the execution script, i.e., nast68 or emas3, will be incorrect. The accounting summary script can be corrected by manually editing the accounting file to insert the time zone parameter into each line as appropriate. The accounting summary script will then report correct summary information. @ 5977; 69; Buckling Analysis - SPCD - Wrong Answers If SPCD entries are used in SOL 105 and the SUBCASE used for the buckling analysis does not contain a call for a LOAD set using the SPCDs, the SPCD entries are ignored in the solution. Avoidance: Either use different SPC sets for each SUBCASE, or include a LOAD command in the buckling SUBCASE pointing to the SPCD set. @ 5980; 68.2; Executive - XEQUIV - SFM 4276 EC 7777 If during the equivalence of a local scratch datablock the PVA table runs out of space, the expansion of the PVA table may corrupt open core. Jobs

that encounter this error may fail in many unpredictable ways. The most likely failure will be "SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777". The job that encountered this error is an optimization analysis with image superelements. Avoidance: Increase or decrease the size of RAM with the INIT FMS statement. @ 5981; ; Optimization/Design Sensitivity - DSAD, FRRD1 - Insufficient Tim e, SFM 4276 If an optimization run encounters an "INSUFFICIENT TIME" type message during the finite element part of the solution (the example encountered was insufficient time to complete the frequency response solution, FRRD1) it is possible the run will continue into the optimization process and fail in the optimizer (the example fails in DSAD with SFM 4276, ERROR CODE 3001). If an unexplained error occurs during optimization, check the output file for other messages. Avoidance: Specify sufficient time on the TIME statement in the executive control section. @ 5982; 69; Eigenvalue Analysis - AGIV, AHOU - SDCOMP FATAL ERROR, UIM 5458 If an eigenvalue analysis specifies either the AGIV or the AHOU method, then standard GIV and standard HOU are attempted first. If the mass matrix is singular, an unnumbered fatal message "SDCOMP FATAL" is issued even though the problem continues and the program switches to the modified Givens or Householder method. Avoidance: If the problem runs, ignore the FATAL message. @ 5983; 69; Optimization/Design Sensitivity - DOPTPRM, DOM10 - SFM 3001 An optimization run with P1=1 and P2=15 on the DOPTPRM entry fails and issues "SYSTEM FATAL MESSAGE 3001" from the DOM10 module even though the run works fine without these parameters. These are output control parameters and should not effect the solution. Avoidance: If P1 and P2 have been used on the DOPTPRM and the run fails, try the run again without specifying P1 and P2. @ 5984; 68.2; Nonlinear Analysis - PARAM,NMLOOP , SE's - Missing Output When using the nonlinear normal modes option in Sol 106, no modal analysis is performed when there are superelements and PARAM,NMLOOP is specified in the Case Control. Avoidance: Place the PARAM,NMLOOP statement in the bulk data. or Use SUPER=ALL in the case control. or DMAP alter:

compile nlstatic souin=mscsou nolist noref $ alter 480 $ seid= 0 $ pvt pvts,cases/pvtxx/ $ endalter $ @ 5986; 68.2; Superelements - PARAM, EXTRCV - Wrong Answers When using PARAM, EXTRCV with the RESTART FMS statement, wrong answers result if the residual structure subcase qualifiers (LOAD, SPC, MPC, etc.) differ from those specified in the residual structure subcase of the run which generates the external superelement. Avoidances: 1. Maintain the same residual structure subcase qualifiers in all runs. 2. Insert the following alter in the PARAM, EXTRCV run: COMPILE IFPL souin=mscsou, noref nolist alter 152,152 3. Use the multi-MASTER approach in the PARAM, EXTRCV run. Assuming that the external superelement data base is called extse1.master, replace: RESTART and ASSIGN MASTER, if any, with the following: nastran system(143)=1 assi extse1=extse1.master dbloc logi=extse1 ASSIGN MASTER, if any, with the following: nastran system(143)=1 assi extse1=extse1.master dbloc logi=extse1 Insert PARAM, SERST, SEDR into the Case Control or Bulk Data. @ 5987; 68.2; Postprocessing - PARAM,POST,-2 - IDEAS Dataloader Abort In MSC/NASTRAN Version 68, the structured solution sequences with PARAM.CHECKOUT,YES and PARAM,POST,-2 do not write an END-OF-DATA on the FORTRAN file. Avoidance: COMPILE PHASE0 SOUIN=MSCSOU NOREF NOLIST ALTER 527 $ Before CALL PRTSUM OUTPUT2 //-9/OUNIT1//OMAXR $ write END-OF-DATA CEND @ 5992; 68.2; Grid Point Stress - GPSTRESS, SURFACE, QUAD4 - Missing Output Certain setids (120 thru 138, 148 thru 159, 174 thru 181) may cause incomplete output for GPSTRESS when used in combination with the SURFACE

case control command. An example case control which results in the error follows: SET 21=120 STRFIELD=21 GPSTRESS=21 OUTPUT(POST) SET 95=19,20,21,59,60,61 SURFACE 120 SET 95 NORMAL Z SYSTEM ELEMENT BEGIN BULK @ 5993; 69; Documentation - PBEAM - Continuation Entries The documentation for the PBEAM entry in the MSC/NASTRAN Version 68 Quick Reference Guide states that the fields "SO" and "X/XB" on the second continuation entry are required. A footnote should be included (as was in the Version 66 User's Manual) that states that these fields are only required when the second continuation entry is desired to request intermediate stress output. @ 5995; ; Elements - QUAD4, TEMP(LOAD) - Wrong answers Warped QUAD4 elements with thermal loads give wrong answers. This error is similar to the thermal expansion error in elements with rigid offsets, there is no expansion for the offset. If offsets and orthotropic materials are present, the errors are magnified. @ 5998; ut ; Documentation - Linear Static Analysis User's Guide - Wrong outp Incorrect output result files are included in Figures 11-2 and 11-3 of the MSC/NASTRAN Linear Static Analysis User's Guide. Due to a missing carriage control character, a pload1 entry for element # 2 is missing for the inertia2.dat file that is delivered with the delivery tape. Furthermore, due to error 5522, PLOAD1 yields incorrect results for the BAR, BEAM, or BEND elements when used in conjunction with inertia relief. Thus, this example (using PLOAD1) should not be emulated until error 5522 is corrected. Avoidance: Replace the PLOAD1 with equivalent grid point loads and regenerate the output file. @ 6000; 2001; Transient Analysis - RESTART, PARAM,NOAP - Poor Answers If TIC entries are used to set initial velocity values, the computed initial velocity will be slightly different from the specified initial velocity. On a case where v0 was set to 1.0, the output velocity was computed as 0.9969. This model has a dt of 0.1 Avoidance: An avoidance is to run the model once to determine the c omputed initial velocity, and increase the input initial velocity enough so that the computed intital velocity is the value desired on a second run. @ 6004; 68.2; SSSALTER Library - ZFREQ - Wrong Answers

The ZFREQ alter delivered in the Version 68 SSSALTER library allows frequency dependent springs and dampers to be defined. However, the nominal spring stiffness is not updated in the data recovery phase. Thus, element force output for these elements is incorrect. This is a known limitation of the alter that should have been documented in the ZFREQ.RDM file. The information contained in this error report is to be included in the Version 68.2 ZFREQ.RDM file and the error is considered corrected. Avoidance: An avoidance is to place a stiff spring in series with the mount, the forces in the stiff spring represent the correct element force for the mount spring. The error introduced by this technique is proportional to the ratio of the stiff spring rate to the mount spring rate. For example, if the ratio is 1000:1, the overall mount spring rate across both devices is 0.1% lower than the actual mount rate. The user may modify his mount spring rate data to account for this effect. In most instances the mount spring rates are not known to this level of accuracy, so that the effect may be ignored. To avoid numerical difficulties the stiff spring should be of the same order of stiffness as the structural elements to which it attaches. In most instances the structure to which the mount attaches is much stiffer than the mount. @ 6007; ut 69; Documentation - PARAM, USETPRT PARAM, USETEL - K-set is not Outp The MSC/NASTRAN Quick Reference Guide incorrectly states that the parameters usetprt and usetsel can be used to print k-set degrees of freedom. That is, the k-set decimal equivalent is listed as an option in table 1 of the usetprt parameter description. @ 6010; 68.2; Nonlinear Slide Line Contact - BCONP, BLSEG - Wrong Answers An overhang slave node is not considered as "overhang" if the overhang value is less than 5% of the master segment length. For models with large master segments, this may lead to wrong answers. Typical symptoms include the printout of a wrong slip code (e.g., SLIDE instead of OVERHANG) and incorrect surface coordinates. Avoidance: Use smaller master segments when modeling overhang situations. @ 6011; 70; Security - NAO - UFM 3060, Segmentation Fault, Signal Number 11 in Log File Large jobs that use Network Authorization (NAO) may fail in various moudules on the DEC/ALPHA OSF with the message, "Receiving signal number 11: Segmentation fault", in the MSC/NASTRAN log file. Similarly, if using node lock authorization, and running a looping solution sequence like nonlinear and a large problem, then User Fatal Message 1019 "Fortran Unit Open Error" pointing to the authorization file may be issued. This message is followed by USER FATAL MESSAGE 3060. The problem occurs because a socket (file) is left open each time MSC/NASTRAN checks the authorization code and when the system reaches the open sockets limit, the job fails as indicated above. Avoidance: Edit the system configuration table (sysconfigtab) and increase

the value of the OPEN_MAX parameter. (This is a system administrator job that may require assistance from DEC.) Then reboot the machine. To determine the curren OPEN_MAX value, execute the command: getconf OPEN_MAX @ 6012; 69; Dynamic Response Analysis - EPOINT - Single Precision Accuracy If there are EPOINT entries in the bulk data file, the eigenvalue matrix PHIA is expanded to the d-set matrix PHIDH in the GKAM module. On short-word machines PHIA is double precision. At present PHIDH is single precision. As this matrix is used to reduce load matrices and expand modal solutions to physical DOFs this may reduce the precision of the solution. Avoidance: An avoidance is to discard the PHIDH matrix output by the GKAM module and build an alternate matrix with DMAP. The equations defining how PHIDH is formed from PHIA are given in the MSC/NASTRAN REFERENCE MANUAL. @ 6013; 69; DMAP - DMIG - Wrong Answers If a DMIG entry references a degree of freedom which does not exist, the corresponding coefficients are assigned to another degree of freedom, without any diagnostic messages. In one example, an open set was used to define a series of scalar points. A DMIG term referenced a point that was not defined on an SPOINT entry which occurred between two points which were listed on SPOINT entries. The coefficient was placed on the last DOF. @ 6015; 68.2; Documentation - Aeroelastic Users' Guide - UFM 2268 (FA1) Example HA145I in the Version 68 Aeroelastic User's Guide alter that is in error. The alter inserts a MATPRN after should be after line 45. If submitted as documented, the issues the message "USER FATAL MESSAGE 2268 (FA1) FMETHOD FOUND". contains an line 50. It run fails and SET 0 NOT

The data deck delivered in the tpl has been made current. The documentation will be updated to reflect the latest version when it is updated. @ 6016; 50) 68.2; P-Elements - HEXA, PENTA - Excessive Pivot Ratios at p=2 (UFM 90 If a model consists of HEXAs or PENTAs at a p-level=2 or higher connected end-to-end, the following message may occur: DMAP FATAL MESSAGE 9050 (SEKRRS) - RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX KLL. USER PARAMETER BAILOUT MAY BE USED TO CONTINUE THE RUN. This fatal message is caused by the reduced integration used at a p-level=2 and higher. Reduced integration is the current default. Avoidance: SYSTEM(212)=1 may be set to work around the problem. @ 6017; 68.2; Nonlinear Slide Line Contact - BCONP, BLSEG - Extraneous Output The following parameters are printed in the "LINE CONTACT REGION" output

when using the slide line contact capability. CONT BEHA TYPE FO CO

These values should be ignored as they are not implemented in the program. Avoidance: These values have no effect on the rest of the output and they can be safely ignored. @ 6018; 69; Acoustic Analysis - SORTi - SORT2 Output in Place Of SORT1 In solution 108, a request for SORT1 output in an acoustic analysis results in SORT2 output. Avoidance: Add PARAM,CURVPLOT,1 to the bulk data. @ 6024; 68.2; Optimization/Design Sensitivity - DLINK - Wrong Answers If the user inputs a nonzero value for C0 on the DLINK entry, it is incorrectly processed by the optimization algorithm. Values used by the optimizer for the dependent design variables will be incorrect. This will directly affect constraint calculations from the upper and lower bounds input on the associated DESVAR entry. These constraints may not be critical and and the optimization results may be valid. The printed summary values for the dependent design variables will be incorrect. Avoidance: There is no avoidance. @ 6025; 68.2; Plotting - XYPLOT(TEMP) - Infinite Loop If the SET1 entry references non-existing grid IDs, then the XYPLOT command which reference this SET1 entry cannot identify the missing grid point(s), which causes the program to go into an infinite loop. Avoidance: Check all the grid points on the SET1 entry and make sure they exist. @ 6030; 68.2; Optimization/Design Sensitivity - MPCFORCE, PARTN, DSAP - UFM 21 66, UFM 5901 In Version 68, if MPC forces are requested in an optimization run under static analysis, the program fails at line 121 of subDMAP SEDISP with UFM 2166 stating that the number of columns in the partition vector is incorrect. Under frequency response analysis, UFM 5901 will be issued from the DSAP module. Avoidance: Either remove the MPCFORCE output request or apply the following DMAP alter to avoid the error: $for statics approach: compile sedisp, souin=mscsou, nolist, noref alter 109 noqmg=ltoi(delta) $ $ For Frequency approach: compile sedisp, souin=mscsou, nolist, noref alter 238 if (not delta ) then $

alter 239 endif $ @ 6031; 68.2; Documentation - gentim2.dat - Data File Not Found The MSC/NASTRAN V68 Installation and Operation Instructions implies that the gentim2.dat file used to update timing constants is in the same directory with the SSS.MASTERA and USS.MASTERA (ie /msc68/nast68/aix/del) but it is not. The file is located in the /msc68/nast68/del directory. The install guide should be clarified to tell users where the data file is located. @ 6033; 68.2; Elements - TETRA(10), TEMP(LOAD) - Wrong Answers for TETRA(10) S tresses If the temperature at the grid points of a TETRA(10) element vary (i.e. they are not constant), then the stresses for the element are incorrect. Avoidance: The error is proportional to the variance of temperature within the element; however, refining the mesh so that the temperature within each element is near a constant is not considered a practical avoidance. Stresses requested at the gauss points are correct. @ 6034; 3.2; Documentation - Installation and Operation Instructions - Timing Constants Section 3.6 of the MSC/NASTRAN Version 68 Installation and Operation Instructions explains how to install the timing constants. Step 2 of the documented procedure states: "2. The timing data are generated or changed by running gentim2.dat (delivered in the "del" library)..." Later in this step you are instructed to change to the directory install-dir/msc68/{prog}/{mach}/del where the files *SS.MASTERA, etc are stored. In other words, there are two "del" directories 1) install-dir/msc68/{prog}/{mach}/del and 2) install-dir/msc68/{prog}/del The first directory contains the *SS.* files and the second contains the gentim* files. The installation procedure should be more clear. Avoidance: Copy the file install-dir/msc68/{prog}/del/gentim2.dat to install-dir/msc68/{prog}/{mach}/del @ 6035; 69; Nonlinear Analysis - NLITER, NLPARM, INTOUT=NO - UFM 4551 Nonlinear jobs have been found that converge successfully when INTOUT=YES but fail to converge and issue "USER FATAL MESSAGE 4551 STOPPED PROBLEM DUE TO FAILED CONVERGE" when INTOUT=NO. The exact cause of the problem is under investigation. @

6036;

68.2; P-Elements - Punch Output not Supported When stresses and strains are output in the punch file, they are output in the print file (F06) format, with titles and labels, rather than a format suitable for the punch file.

@ 6038; 69; Elements - CTRIA3, TA1 - No Message, Trap Encountered If a CTRIA3 element references a nonexistent material coordinate system (field 7), the job should issue USER FATAL MESSAGE 2025 UNDEFINED COORDINATE SYSTEM. The IBM RS/6000 versions of MSC/NASTRAN do not issue this message. The job stops without a message being issued. The f04, Execution Summary, indicates that the last module executed is either TA1 or PHASE1DR and the log file contains a "Trap Encountered" message. @ 6042; GL; Elements - PENTA(6), TEMP(LOAD) - Wrong Answers for Stresses If the temperature at the grid points of a PENTA(6) element vary (i.e. they are not the same at all points), then the stress output is wrong. Both corner point (default) and Gauss location (selected on PSOLID) options give wrong answers. The stress error is proportional to the amount of temperature change within the element. Avoidance: This is a limitation of the element. The only avoidance is to refine the mesh so that the variation of temperature within the element is minimal. @ 6044; 68.2; Optimization/Design Sensitivity - Incorrect Sensitivities for Su perelements Incorrect design sensitivities are computed for superelement models in which a superelement has design variables but no design responses. This error occurs only in statics. Avoidance: The avoidance is to specify WEIGHT=ALL (for all superelements) as a design response. @ 6045; 2001; Installation - Timing Constants - UWM 6080 The text of "USER WARNING MESSAGE 6080 (SETKRN), THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY DATABASE" refers the user to "AM 7.6". This reference should changed to the a more generic term, such as machine dependent documentation. @ 6046; n Setting PARAM,DESPCH to a negative value will not prevent DESVAR and GRID Entries from being written to the PUNCH file. Avoidance: The following DMAP alter may be used to avoid the problem: compile exitopt nolist noref souin=mscsou alter 24 $ just before executing module DOM11 68.2; Optimization/Design Sensitivity - PARAM,DESPCH - Incorrect Actio

type parm,,i,n,desitert if (despch < 0) then desitert = desiter desiter = 0 endif alter 25 $ right after execution of module DOM11 if (despch < 0) then desiter = desitert endif $$$ end of alter @ 6047; 68.2; SSSALTER Library - RESFLEXR - Wrong Answers The alter to add residual vectors into a dynamic solution delivered in the sssalter directory with Version 68 does not handle SUPORT entries properly for free-free structures. If a SUPORT entry is present, residual vectors are not generated for the residual structure. Avoidance: Call MSC for an updated version of the alter. @ 6050; 68.2; P-Elements - GMLOAD in convective coordinate systems If a GMLOAD is applied in a convective coordinate system defined on a GMCURV or GMSURF where the CIDIN is other than basic coordinate system, then the following message is output from SSG1: USER FATAL MESSAGE 2025, UNDEFINED COORDINATE SYSTEM FATAL ERROR 2

Avoidance: Possible avoidances include defining the GMCURV or GMSURF in the basic coordinate system, and applying the load in a non-convective system, or using PLOAD4. @ 6051; 69; Documentation - MAT1 - Programs Action not Clear Remark 3 under the documentation for the MAT1 entry in the Quick Reference Guide states that the relationship between E, G and NU "must be satisfied". It should be clarified that satisfying the relationship is merely a recommendation, rather than a requirement. The values furnished are used as indicated in Table 1. and if the relationship is not satisfied the program proceeds but issues USER WARNING MESSAGE 2251A and 2251B. Furthermore, the relationship indicates ">" when it should indicate " 101) Avoidance: Remove Diag 14 and/or Diag 64. @ 7013; ries ; Miscellaneous - COMIFP, PUNCH - Produces Incorrect Bulk Data Ent The comifp module has been modified for Version 69 to support the part superelement concept. It can take ifp-like files from the sep2 module and punch bulk data files which may then be used as part files. At present, the RBE2 and RBE3 elements are punched incorrectly. Avoidance: An avoidance is to separate the elements not properly

processed by hand. @ 7014; 69; Heat Transfer Analysis - MAT4, CONVM, EMG - FATAL ERROR, Bad Dia gnostic Message If the user fails to define a dynamic viscosity in field 7 of the MAT4 entry for a forced convection analysis the job fails in the EMG module with no indication of the cause of the error. Avoidance: Make sure the dynamic viscosity is input on the MAT4 card if the problem has CONVM bulk data entries. @ 7015; 69; Material Nonlinear Analysis - TEMP(LOAD), CLOAD - Wrong Answers In Version 68.2 and SOL 106 only, thermal loads applied to upstream superelements results in incorrect stresses and forces. Avoidance: Use SOL 66 or apply the following alter to SOL 106: compile super3 noref nolist alter 'IF ( NOCASRS1>-1 AND SEID=0 )','' IF ( (NOCASRS1>-1 AND SEID=0) or app='nlst' ) THEN $

@ 7021; 69; Optimization/Design Sensitivity - DSCM2 - Wrong Ordering In design sensitivity analysis, there is a table printed just prior to the DSCM2 (design sensitivities matrix) which specifies the ordering of the columns in the matrix. If some of the design responses specified on the DRESP1 entry are the eigenvalues, then the table claims that the eigenvalue responses are in ascending order by DRESP1 entry ID. However, the matrix is actually in ascending order by mode number. Avoidance: The only avoidance is to be aware that the output is in ascending order by mode number. @ 7024; ; IDENT option on ACMODL entry If INTER=IDENT on the ACMODL data entry is used in acoustic analysis, then only two fluid grids per structural grids at the fluid/structure inter face. This precludes modeling structures such as t-sections stiffeners in tanks or t-sections immersed in fluid. @ 7040; 69; Documentation - DRESP1 - UFM 316 The documentation for the DRESP1 entry in the MSC/NASTRAN Version 68 Quick Reference Guide states that the SPC force component is chosen with the RTYPE=FRSPC or RTYPE=TSPC. However, if either of these RTYPEs are used, the following fatal message is issued, "USER FATAL MESSAGE 316 (IFPDRV) ILLEGAL DATA ON BULK DATA CARD DRESP1 331 SORTED CARD COUNT = ***". The documentation should say the the SPC force component is chosen with RTYPE=FRSPCF or RTYPE=TSPCF. Avoidance: Use RTYPE=FRSPCF or RTYPE=TSPCF not FRSPC or TSPC when the SPC force component is desired as a response type.

@ 7041; 69; Nonlinear Analysis - EMG - Poor Performance NO EXTERNAL ERROR REPORT When there are no linear elements in a model, the EMG module is unnecessarily executed. This appears to be a minor performance improvement, I see no need to publish to clients. @ 7044; s Scaling by other than 1. of a vector flux QVECT load by a DLOAD bulk data entry produces wrong results in the "APPLIED-LOAD" column of the "Heat Flow into HBDY Elements" table. The actual load vector generated is correct and therefore the temperatures are correct. Avoidance: Use only scale factors 1 on the DLOAD entry. @ 7045; 69; Case Control - SUBCASE - Poor Message The message " *** USER FATAL MESSAGE 609 (IFP1D) SUBCASE DELIMITER CARDS MUST HAVE A UNIQUE IDENTIFYING INTEGER " which does not accurately describe the input error is issued for the following situation: 1. When the subcase id exceeds 9999999. 2. In solution 200 when the subcase id of the preceding subcase is higher than the id of subsequent subcase. @ 7047; 69; Aeroelastic Analysis - Unwanted Output in the Flutter Summary In the pk flutter solution, all combinations of velocity, Mach number and density are used. In certain situations (e.g., if analyses are only required at 50 velocity-density combinations) it would be preferable to only do ordered combinations. Avoidance: The current avoidance is to put each required combination in its own subcase. For the example given above, this would require 50 subcases, but it would reduce the number of flutter analyses from 2500 to 50. @ 7048; 69; Submittal Script - node - Error With node Keyword When the "node" keyword is used along with the "user" keyword ( i.e. nastran ..... node=pelee user=ssp) then job will not get submitted to remote node and the following message will be displayed on the console: nast68: (W) node=pelee specified, setting app=yes bat=no scr=yes nast68: (E) node=pelee: no execute permission on remote node. Avoidance: The following line in the nastran shell script should be changed. The shell script is $MSC_INSTALLDIR/bin/nastran. 69.1; Nonlinear Transient Heat Transfer - QVECT, DLOAD - Wrong Answer

rx="$remcmd $tuser $node" should be changed to rx="$remcmd $node $tuser" @ 7050; h file 69; Multipoint Constraint - MPCFORCE Output - Labeled as SPCF in .pc MPCFORCE output when printed to a punch file, is mis-labeled as SPCF. The data is correct however. Confusion may arise when both SPCFORCE and MPCFORCE are printed to the punch file. The user must use care to read the correct results. The error is considered fixed in Version 69; however, setting of SYSTEM(210)=1 is required. Avoidance: Print and punch the data so that the output can be compared and correlated.

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

integer and this is normally a huge number. The IFP module should stop the execution with "User Fatal Message 327" in case that the input for NCOL is not an integer. @ 7065; 69; P-Elements - Wrong Adaptivity Analysis - Poor Answers If a data deck contains different TYPEs of P-elements (e.g. a HEXA and a PENTA), the adaptivity error analysis likely to be in-accurate leading to poor answers. Avoidance: There is no avoidance. @ 7073; 69; Heat Transfer - PARAM,POST,-2 - SDRC Cannot Read TEMP Vector SDRC is not able to read the temperature vector in the output2 file produced with PARAM,POST,-2. Avoidance: Use EQUIVX instead. @ 7076; ; Timing Estimate - DECOMP - UIM 4157 The CPU time estimates issued in USER INFORMATION MESSAGE 4157 for sparse decomposition can be overstated by a factor of 7 to 15 times on some machines. This is due to the fact that the timing estimates do not take into account the high rank performance update enhancement which was introduced beginning in Version 68.1. By overstating the CPU time estimates the job may fail with a message that it does not have enough time to complete Decomposition. Avoidance: Include an extra large value for time on the TIME executive control entry or remove the TIME entry. @ 7085; 70.5.2; Cyclic Symmetric - Dihedral, LOADCYH, DSYM - UFM 4342 A cyclic symmetry analysis using dihedral symmetry and centrifugal loads may issue the following message: USER FATAL MESSAGE 4342, THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALYSIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE. LOADCYH 20 0CSTAR 2000004 The message occurs when a SS (Symmetric=Symmetric) boundary condition is specified on the DSYM case control command and the LOADCYH bulk data requests an 'RLOAD' for the HTYPE field. In this condition the code generates too many load vectors. Avoidance: One avoidance is to change the HTYPE field to 'C' on the LOADCYH bulk data entry. A better avoidance is to eliminate the DSYM request in the case control. @ 7088; ned 70; Documentation - PSHELL, MID4, ZOFFS - MID4 and ZOFF may be combi Remark 6 under the description of the PSHELL entry in the Version 68 Quick Reference Guide states that "Only one of the options MID4 or ZOFFS may be

used". This is a guideline to prevent users from offsetting the element twice. Depending on the intent of the user these affects may be combined and correct answers achieved. @ 7093; 70.5; Complex Eigenvalues - CLAN - Wrong Answers For one model, the complex lanczos eigenvalue method in solution 107 produced erroneous eigenvalues on the CRAY computer. The same model produced consistent real eigenvalues across all machines so there does not appear to be anything wrong with the model. MSC/NASTRAN Version 70.5 introduces the new Block Complex Lanczos method. This method correctly solves this problem on CRAY and all other machines. This method must be selected in Version 70.5 by setting system(108)=4 on the NASTRAN entry or rc file. Avoidance: Until the error is better understood, use SOL 110, modal complex eigenvalues, with the Hessenberg Method. @ 7100; 69; Static Analysis - SPC - UFM 5423 A DMAP error exists in multiple boundary condition with non-zero SPC in SOL 101. The error is triggered when the same boundary conditions are not grouped together, i.e., the same SPC is selected again following a SUBCASE with a different SPC. The error is detected by the SSG2 module with a UFM 5423 "attempt to multiply incompatible matrices." This error is related to error 5977 which is detected when SPCD is used instead of non-zero SPC. Avoidance: 1. Shuffle the Subcases so that the same boundary conditions are grouped together (to appear consecutive Subcases). 2. Use SOL 106 with unsorted SUBCASE set-up and run it as a linear problem without any nonlinearity. @ 7108; 69; Acoustic Analysis - SDR1, MPYAD - Insufficient Time Acoustic Analysis in MSC/NASTRAN does not support the matrix method of data recovery. Thus, the data recovery performed by the modal displacement method for small sets of data is very inefficient. This deficiency is complicated by poor timing estimates in MPYAD. MPYAD, which is called by SDR1 during the data recovery, may yield a time estimate that overflows the machine. Version 69 will support data recovery in the DDRMM module, i.e., the matrix method. Avoidance: There is no simple avoidance. Perform modal reduction on the fluid and limit the number of frequencies in the analysis. The following alter can be applied to recover pressure only by the matrix method. compile semfreq souin=mscsou noref nolist alter 74 lamx ,,lamas/mlamas/-1 $ lamx ,,lamaf/mlamaf/-1 $ matgen ,/cp0/6/5/2/2/1 $ matgen ,/cp1/6/3/0/1/1/1 $ $

partn mlamas,cp0,/,,emats0,/1 $ merge ,,,emats0,,cp1,/emats1/1 $ trnsp emats1/emats $ $ partn mlamaf,cp0,/,,ematf0,/1 $ merge ,,,ematf0,,cp1,/ematf1/1 $ trnsp ematf1/ematf $ $ append emats,ematf/emat $ lamx emat,/lamax $ ofp lamax/ $ ALTER 112,112 IF (DDRMM>=0) APP1='MMREIG' alter 117 equivx lamax/lama/-1 $ $ compile super3 souin=mscsou alter 24,24 IF ( APP1='MMREIG' ) THEN $ compile sedrcvr souin=mscsou noref alter 61 if ( app1='mmreig' ) then $ equivx oes1/qes1/-1 $ equivx oef1/qef1/-1 $ delete /ougv1,oqg1,oes1,oef1, $ DDRMM CASEdr,UH1,OL1,qugv1,qQG1,qES1,qEF1,XYCDBdr/ OUGV1,OQG1,OES1,OEF1, $ EQUIVX OQG1/QQG1/ALWAYS $ EQUIVX OUGV1/QUGV1/ALWAYS $ endif $ alter 159,159 IF ( sort2 ) THEN $ SORT2 @ 7109; 70.5; DMAP - MATMOD OPTION 17 - Wrong Answers MATMOD option 17 generates a g-size partitioning vector from a user-defined set of grid and/or scalar points. If the 3rd parameter (SETFLG) is set to 1, it is supposed to look for the PARTN case control command and put a value of 1.0 in the vector for grid points listed in the set defined by the PARTN case control command. If there is no PARTN case control command, it is supposed to use the sets defined by the 2nd parameter (UBIT). However, the above operation returned a vector with all values set to 1.0 instead. Depending on subsequent operations, this can either lead to fatal errors or wrong answers. Avoidance: Include the appropriate PARTN case control command. @ 7110; 69; SSSALTERS - evds.v682 - Fails to Converge When using the eigenvector sensitivity dmap alter (evds.v682) delivered with the sssalter library in Version 68.2, and the model does not contain any elements which references a mass property entry, then the job may fail to converge. Avoidance: Replace the following dmap statement in evds.v682 subdmap fox: TYPE PARM,,I,N,NULLDM $

with TYPE @ 7118; 69; Documentation - ADUMi, PDUMi - Undocumented Limits, User Modifia ble NASTRAN The number of additional fields "NP" on the PDUMi entry is limited to 24 words. This limit is not documented in the description of th NP field of the ADUMi bulk data entry description. @ 7127; le TA1 69; Optimization/Design Sensitivity - PARAM,SNORM - UFM 2025 in modu If in SOL 200, parameter SNORM is greater than or equal to 0.0 and if a coordinate system is specified in the MCID field of the connectivity entry in the run then the following fatal message will be issued. *** USER FATAL MESSAGE 2025 MODULE = TA1 UNDEFINED COORDINATE SYSTEM 3 This error might also occur in SOL 101 and 103 if p-element adaptive analysis is performed. Avoidance: Two avoidances exists: 1. Remove the SNORM parameter. 2. Add the following alter. compile update souin=mscsou nolist noref alter 51,51 $ TA1 ,,ECT,EPTX,BGPDTSCR,SIL,,CSTMSCR,/ ESTJNK,,,GPECT0,/ LUSETS/-1/S,N,NOSIMP/1/S,N,NOGENL/0 $ @ 7136; t There is an error in the nddl for the MCSID field of the MAT2 entry. The nddl types the field as real when it should be an integer. If this field is changed in a RESTART the execution will fail. The message "time: command terminated abnormally" is issued in the log file. Avoidance: The run should be executed as a cold start. @ 7137; 69; Postprocessing - PARAM,POST,-2, SOL 112 - Extra Output In SOL 112 with PARAM, POST, -2, the geometry tables are written twice to the OUTPUT2 file. However, this does not seem to negatively affect the IDEAS translator. 69; Restarts - MAT2, IFPL, RESTART - DEC Alpha Only Aborts on Restar PARM,,I,N,NULLDM,NZWD $

Avoidance: There is no avoidance. @ 7138; 70; Documentation - Common Questions and Answers - Incorrect Problem Descriptions The problem description on page 103 of the Common Questions and Answers ,2nd Edition, does not match figure 40 on the same page. The acceleration should be negative, as is reflected in fig. 40 and the 3 in field 5 of the RLOAD2 entry should be moved to field 6. The title for figure 39 on page 101 of the Common Questions and Answers book refers to point loads when in fact the example discusses pressure loads (PLOAD4s). @ 7139; 69; Executive System - COMPILE - Segmentation or Access Violation NO EXTERNAL ERROR REPORT IS NECESSARY MAR VERIFIES THIS EVERY TIME HE REBUILDS THE DELIVERY DATABASES. An attempt to compile the NDDL and more than 75 subDMAPs in a single run causes a segmentation or access violation. The limit in Version 69 has been expanded to allow for at least 100 subdmaps. Avoidance: Split the job into two runs. @ 7141; 70.7.2; Nonlinear Transient Analysis - CBEAM - UFM 4551 (NL2CON) It has been found that in rare cases when then the a beam element is exactly normal to the axis of the exhibit a round-off error that leads to convergence ultimately USER FATAL MESSAGE 4551, STOPPED PROBLEM CONSECUTIVE DIVERGING TIME STEPS. @ 7142; 69; Optimization/Design Sensitivity - DOPR3 - SFM 4276 If the user provides constraints for multiple DRESP1 entries in a single flutter subcase, then SYSTEM FATAL MESSAGE 4276 GREAD ERROR CODE 3001 will occur in the DOPR3 module. Avoidance: If it is not possible to define all the flutter responses on a single DRESP1 entry, multiple flutter subcases are required, each with a single referenced DRESP1 entry. @ 7144; ; Nonlinear Transient Analysis - OTIME - Missing Output In nonlinear transient analysis (SOLs 129 and 159), the solution vectors (SDISP, SVELO, and SACCEL) should be output for each subcase independently. However, SDISP, SVEL, or SACCEL does not appear in the output unless the request is specified above the subcase. Avoidance: Specify the output request for SDISP, SVELO, or SACCEL above the subcase level. @ orientation vector for beam, the Cray may difficulties and DUE TO FIVE

7147;

69; Utilities - OPTCONV - Fails On Windows NT If the OPTCONV program delivered with the Windows NT version of NASTRAN is used to convert an old optimization deck to the current format, the following message is obtained in a pop-up window: "The instruction at 004147cc referenced memory at 0d4212b9 The memory could not be written Click on OK to terminate the application". Therefore, it is not possible to convert any old optimization decks on Windows NT. Avoidance: Convert the decks by hand or have them converted on a different machine variation.

@ 7156; 69; P-Elements - PARAM,USETPRT,0 - Incorrect Output PARAM,USETPRT,0 produces incorrect output for P-Elements. Avoidance: @ 7163; 69; Nonlinear Static Analysis - ASETi, OMITi, AUTOSPCR - UWM 5225, W rong Answers In nonlinear static analysis, any nonlinear degree of freedom in the o-set (via ASETi or OMITi entries) may result in a singularity in the o-set linear stiffness matrix (UWM 5225). Also, if PARAM,AUTOSPCR is used, all the nonlinear degrees of freedom will be constrained and the resulting solution will be incorrect. Avoidance: Include all the active nonlinear degrees of freedom in the A-set. @ 7165; 69; Optimization/Design Sensitivities - CTRIAX6 - Wrong Answers When CTRIAX6 elements without mid-side nodes are used in an optimization job which includes specification of temperature loads, the thermal displacement/stress sensitivities may show wrong signs which may result in strange convergence behaviors. Avoidance: Use CTRIAX6 elements with midside nodes. @ 7167; 69; Nonlinear Heat Transfer - UIM 6194, UIM 6193, UFM 4551 Nonlinear Heat Transfer jobs with more than one subcase may fail to converge and issue UIM 6194, UIM 6193 and USER FATAL MESSAGE 4551. This error was experienced in a job where the second subcase was the same as the first. The job should have converged immediately in the second subcase since there was no change. USER INFORMATION MESSAGE 6194, STOPPED ITERATIONS DUE TO REACHING MAXIMUM ITERATION LIMIT WITHOUT CONVERGENCE *** USER INFORMATION MESSAGE 6193, MAXIMUM NUMBER OF BISECTIONS OR MINIMUM LOAD STEP HAS BEEN REACHED. USER FATAL MESSAGE 4551, Use PARAM,USETPRT,1 instead.

STOPPED PROBLEM DUE TO FAILED CONVERGENCE @ 7170; 69; Heat Transfer - CHBDYP, LINE with midpoint node option Currently there is a design limitation using CHBDYP,LINE to represent thhigher order CQUAD8 or CTRIA6 for the edges with midpoint option. Therefore, the weighting on the mid-side node is misrepresented if the two node LINE option is used. Avoidance: Use CHBDYE to represent the CQUAD8 or CTRIA3 element with midsidenodes. Please note that without the midside node, the CHBDYP,LINE can be used. @ 7171; 2001; Documentation - Reference Manual - Large Field description There is an error in the Reference Manual documentation for the description of the Small/Large/Free field format of the bulk data entries as follows: pp 3.7.1-2 Bottom of the page, Large Field example. The first field of the parent card should be TYPE* not TYPE. The continuation of the parent card should be QED123 not QED124. pp 3.7.1-3 Top of the page, Large field with large field continuation example. This is shown as all small fields. There should only be 4 (double wide) fields between the first and last fields. @ 7173; 69; P-elements - CHEXA - UFM 9050 CHEX p-Elements can have singularities in the stiffness for the default integration options. This error only occurs in a model with a single layer of elements. In particular the default reduced integration order with rectangular elements with p values of [2,2,3] in the three directions may be singular. This error may lead to the following fatal message: USER FATAL MESSAGE 9050 (SEKRRS) - RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX KLL. USER PARAMETER BAILOUT MAY BE USED TO CONTINUE THE RUN. Avoidance: Specify a different p value.

@ 7175; 70.5; Documentation - CALL DBFETCH - DMAP Module Dictionary The description of the DBFETCH command in the DMAP Module Dictionary should enhanced to state "if you are using DBFETCH in a Sol 100 (USER DMAP) to get data blocks from a previous run, include a RESTART FMS statement to specify the version number on which the data blocks were written". @ 7176; 69; Direct Frequency Response - CHACAB - Wrong Answers The damping terms for the acoustic absorber element, CHACAB, are "lost" in solution 108 resulting in null damping from this element.

Avoidance: Place equivalent CDAMP or CVISC elements across the structural boundary points. @ 7179; 69; Documentation - QRG - Inconsistent E,G, NU with MAT1 Table 1 under the MAT1 description in the Version 68 Reference Guide indicates that "E" and "NU" are used properties for "Membrane and Bending" of the CQUADi, elements. This should be clarified to state "should "Membrane, Bending and Inplane Shear". @ 7182; 69; Post Processing - SOL 103 and 105, OUTPUT2 - Missing Output When multiple subcases are used in SOL 103 or 105 and PARAM,POST,-1/-2 is chosen, the output2 file is written over with each subcase and only the last subcase remains in the output2 file for post processing. Avoidance: Request different output2 units in each subcase using param,ounit2 or the following DMAP alters may be used for some post processors (PATRAN3 v5) For SOL 103: COMPILE SUPER3 SOUIN=MSCSOU NOLIST NOREF $ ALTER 'IF ( POST=-1 AND OUNITX\OUN','IF ( ( ((DROPT=0 OR DROPT=4)' PARAML CASECC//'DTI'/1/1//S,N,SUBC1 $ PARAML CASEDR//'DTI'/1/1//S,N,SUBCNO $ IF ( POST=-1 AND SUBCNO=SUBC1 AND OUNITXOUNIT2 AND NOT(PEXIST) AND NOT((APP='NLST' OR APP='TRANRESP') AND PATVER>=3.) AND (((DROPT=0 OR DROPT=4) AND APP1'BKL1') OR APP='BKL0') ) OTAPE2=-1 $ IF ( ( ((DROPT=0 OR DROPT=4) AND APP1'BKL1') OR APP='BKL0') AND (OGEOM='YES' OR OGEOM=' ') AND SUBCNO=SUBC1 AND ((POST=-1 AND PATVER>=3. AND NOT(APP='NLST' OR APP='TRANRESP')) OR POST=-2 OR POST=-4) ) THEN $ $ ALTER 'IF ( ((DROPT=0 OR APP1=','IF ( ((DROPT=0 OR APP1=' PARAML CASECC//'TRAILER'/1/S,N,NSUBC $ PARAML CASECC//'DTI'/NSUBC/1//S,N,LASTNO $ IF ( (SUBCNO=LASTNO OR APP'REIG ') AND (((DROPT=0 OR APP1='BKL1') OR (PEXIST AND ADPTEXIT)) AND POST-4 AND NOT(POST=-1 AND PATVER>=3.0 AND SCRSPEC>-1)) ) OUTPUT2 //-9/OUNIT2//OMAXR $ ENDALTER $ For SOL 105: compile super3 alter '-9'(2),'' compile sebuckl alter 'dbdict1' type parm,nddl,i,y,ounit2 $ type parm,,i,y,omaxr $ OUTPUT2 //-9/OUNIT2//OMAXR $ @ 7184; 69; Postprocessing - PARAM,OUGCORD,BASIC, PATVER,3 - Incorrect Defor MSC/NASTRAN Quick to define the CTRIAi and CCONEAX be clarified to

med Shape PATRAN 3 will display an incorrect deformed shape when PARAM OUGCORD is set to BASIC and the gridpoint output coordinate systems (field 7, CD) is anything other than the basic (coordinate system ID 0). SubDMAP SEDRCVR transforms the displacement vector into the basic coordinate system based on the value of the parameter OUGCORD and PATVER. In Version 67.5 the DMAP IF test includes the value of the parameter PATVER which prevents transformation if PATVER=3.0 (default for PATVER is 3.0). 66 67 ELSE IF ( NOT(PATVER>=3.) AND OUGCORD='BASIC' ) THEN $ VECPLOT UGVS,BGPDP,EQEXINS,CSTMS,CASEDR,/UGVSB//0/1 $

The reason for preventing this transformation is that PATRAN 3 understands the CD field for the GRID entry. In Version 68 the DMAP test for PATVER is not present: 70 71 ELSE IF ( OUGCORDX='BASIC' ) THEN $ VECPLOT UG,BGPDP,EQEXINS,CSTMS,CASEDR,,MEDGE,SIP/UGB/ /0/1/' PARAM,'/'OUGCORD,'/' BASIC '/ALTSHAPE $

This causes the displacement vector to be transformed into the basic coordinate system for post processing by PATRAN 3. However, PATRAN 3 is expecting the output in the output coordinate system of the gridpoints. If the transformed displacement datablock is used by PATRAN 3, the displaced shape is wrong. The description in the Quick Reference Guide, Section 6 (parameters) also needs to be updated under the section 'POST,POST,-1: Results Data Blocks'. The PATVER description needs to include the interaction between parameter OUGCORD and PATVER. Avoidance: Do not specify the value of parameter OUGCORD as BASIC if you are using PATRAN 3. PATRAN 3 expects the displacements to be expressed in the CD value of the gridpoint (analysis coordinate system in PATRAN 3.) You can transform displacements to different coordinate systems inside P3. @ 7185; 66; Response Spectra - SDR2 - Wrong Answers The response spectra summation process for the NRL and SRSS methods handle the CBAR and CBEAM elements differently. Both the NRL and SRSS methods involve taking the square root of the sum of the squares of the value of interest, in this case stress. For the BEAM element the summation is made for the combined bending and axial stress, while for the BAR element the bending and axial stress is summed independently to coincide with the BAR's output which prints the axial stress separately. This leads to incorrect results for the output of the maximum and minimum stress. Avoidance: The CBEAM element should be used for Response Spectra Analysis whenever stress results are desired. @ 7186; 70.6; Documentation - INCLUDE - Include File Not Found The Installation and Operations manual Section 4.5 states that the default directory for an include file is the input file's directory. The default directory is actually the current directory.

Avoidance: Place the file to be included in the current directory or specify the complete path name of the file to be included. @ 7191; 69; Optimization/Design Sensitivity - TEMP(LOAD), TEMP(MATERIAL), SH PCAS - SFM 3001 When a TEMP(LOAD) and/or TEMP(MATERIAL) entry is used in the primary Subcase Control section of a shape optimization job using the analytic shape boundary shape approach in MSC/NASTRAN Version 68.2, the job will fail in module SHPCAS with the message "SYSTEM FATAL MESSAGE 3001". Avoidance: Apply the following DMAP alter. compile bndshp nolist noref souin=mscsou alter 'auxmid'(2) dbview ugx=ug (where mtemp=*) $ alter 'partn','partn' PARTN UGx,,AXMVEC/UGA,,,/1 $ alter 'equivx','equivx' EQUIVX UGx/UGA/ALWAYS $ @ 7193; wers ; Miscellaneous - Wrong continuation format - UFM 313 or Wrong Ans If column 1 of the continuation entry is blank, then the continuation entry is interpreted as a continuation of the last sorted bulk data entry. The error is likely to result in USER FATAL MESSAGE 313 ILLEGAL NUMBER OF WORDS ON CONTINUATION" or in rare cases possibly even wrong answers. An example follows: . Begin Bulk . . tic,100,101,1,0.,0. $ grid,1000,,0.,2.5,2.5 $ grid,101,,0.,0.,0. grid,102,,10.,0.,0. $ 2 3 cbar 1 1 +000015 +000015 $ . . enddata will be interpreted as BEGIN BULK . . CBAR 1 4 101 0.25 5 102 0. 6 1000 0. 7 0.25 8 0. 9 0. 10

1

101

102

1000

+000015 . GRID GRID . GRID . . TIC +000015 +000015 . . ENDDATA

101 102 1000 100 101

0. 10. 0. 1 0.25 0.

0. 0. 2.5 0. 0.

0. 0. 2.5 0. 0.25 0. 0.

Avoidance: Correct the offending continuation entry. @ 7196; 2001; Miscellaneous - GP2, GENEL - Poor Message, SFM 3003 When at least one entire line is missing from a GENEL element, GP2 issues the message: SFM 3003 ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK GEOM2S (FILE 101) IN SUBROUTINE GP2. Avoidance: Correct any offending GENEL elements. At a minimum the Reference Manual documentation should cite incorrect GENEL input as a possible cause of the error message. @ 7199; ; Nonlinear Transient Analysis - PARAM,LGDISP - Poor Answers In MSC/NASTRAN Version 68 nonlinear transient analysis, solutions 99 and 129, were improved to correct error 2665 which stated that in nonlinear transient analysis the damping matrix is not updated. The damping forces for the large displacement solution now use the current "updated" damping matrix, which may have been calculated at an unconverged solution. This approach was intended to provide better directionality to the damping forces when they rotate. However, every time the damping matrix is updated for convergence, a change will occur in the force balance which will cause an erroneous step in the converged accelerations. ( It causes very large errors. - DNH) @ 7201; ision 70; Element - CELASi - Forces/Stresses are Calculated in Single Prec Scalar spring and damper element's (ELASi and DAMPi, 1=1,2..4) stress and force outputs are calculated with only single-precision arithmetic. If a scalar element connects two points with small differences in displacements, relative to the total displacements, some numerical roundoff will occur. Since the stiffness and damping matrices are calculated in double precision the overall results will not be affected. The problem also does not occur on large-word, 64-bit computers such as CRAY and NEC. Avoidance: More precise results for the ELASi elements may be obtained from the GPFORCE output request. @ 7202; 69; Case Control - MPCFORCE=NONE - Extra Output

The mpcf=none command does not turn off mpcforce output in a subcase when it has been requested above the subcase level. Avoidance: Define set 1 = [x], where x is a nonexistent grid or scalar point and use mpcf=1 instead. @ 7206; 69; Heat Transfer Analysis - CHBDYE,TUBE PHBDY - Wrong Answers The convection area used by the CHBDYE for the structure TUBE element is incorrect whenever D2 is left blank. In Version 69 the code is changed so that if D2 is left blank then D2 is set to D1. Avoidance: Use CHBDYP,TUBE option to represent the tube convection area or explicitly set D2. @ 7207; 69; Restart - SPCFORCE - Missing Output SPC force output request is ignored during automatic restarts in dynamic structured solution sequences. See related Error 3119 which was fixed for SOL 101 only. Avoidance: Include the entry PARAM, SERST, SEDR in the bulk data section of the restart deck. @ 7213; ; DMAP - FBS, SYSTEM(72)=1 - Wrong Answers Left handed fbs solves the equation of the form: t t [X] [L][U]=[B] In addition left handed fbs has an option of solving T [X] L U = [B] This option is only documented in the MSC/NASTRAN Numerical Methods Guide and is selected by setting SYSTEM(72)=1. This option produces wrong answres when B is rectangular. The left hand fbs method is not used in the delivered solution sequences for non symmetric matrices. Thus, only user DMAPs may encounter this error. Avoidance: Use right hand fbs. @ 7215; ; Cyclic Symmetry - SECSET1, VAXW, GIV, MGIV - UWM 3034, UFM 4645 Massless degrees of freedom that are placed in the c-set are not properly removed before entering the READ Module in Cyclic Symmetry component mode synthesis. Attempts to remove these degrees of freedom by explicitly constraining them will also be ignored. This may lead to "USER WARNING MESSAGE 3034, ORTHOGONALITY TEST FAILED" followed by a fatal message, "USER FATAL MESSAGE 4645---- THE SHIFTED STIFFNESS MATRIX IS NOT POSITIVE DEFINITE IN MGIVENS METHOD" or "USER FATAL MESSAGE 4646---- THE MASS MATRIX IS NOT POSITIVE DEFINITE, USING THE GIVENS METHOD. USE MGIV INSTEAD". Avoidance: Do not put the degrees of freedom in the c-set, specify Lanczos instead of a transformation method or add a small amount of mass to the massless degrees of freedom. @

7219;

69; Miscellaneous - IFP - Infinite CPU Loop The following continuation entries while legal when using the NASTRAN MESH option result in an infinite cpu loop in IFP when the NASTRAN MESH command is removed. SPC1 = DESVAR =2 10 *1 20 *1 10 *-1 ABC = 11 *1 1. *1.

Avoidance: Add the NASTRAN MESH command or correct the continuation entries in error. @ 7220; 69; Postprocessing - PARAM,POST - Missing Output If the ASSIGN statement is not used or if the complete path is not specified on the ASSIGN statement for an OUTPUT2 file on the Windows NT Version of MSC/NASTRAN, the file is not written to the jid directory but is instead written to the "bin" directory. Avoidance: Specify a complete path on the ASSIGN statement. @ 7231; ut 69; Optimization/Design Sensitivity - XSORT - Incomplete Sorted Outp The XSORT Module may encounter errors for large input files, when it is executed more than once during a run. The messages encountered are various, but the sorted file will be incomplete in every case. The error occurs only on large files, and only on the second and subsequent bulk data files. The errors occur when the bulk data to be sorted does not fit into memory. In Version 68 this error occurs only in design optimization analysis. Avoidance: Increase the memory request so that the file will fit into memory, or reduce the size of the file. @ 7232; 69; Miscellaneous - IFP, RBEi- UFM 4276 EC 7777 When the RBE3 bulk data entries contains illegal data in the REFC field, USER FATAL MESSAGE 316 should be issued to identify the offending entry. USER FATAL MESSAGE 4276 ERROR CODE 7777 is issued instead, which does not identify the illegal data. Avoidance: Other than locating the input in error and correcting it, there is no avoidance. @ 7233; 69; Matrix Methods - FBS, MPYAD - UFM 4547 FBS may set the density of GOAT incorrectly for some large models. The density should be between 0 and 10000 (i.e., 100%). However, it sometimes overflows this field and is printed in the f04 as *******. In this case the run will fail in the MPYAD module with the message "USER FATAL MESSAGE 4547" Avoidance: Use the following alter to re-set the trailer to a value of 80% (or any value they desire).

compile sekr, souin=mscsou, nolist, noref alter 106 $ the line which creates GOAT in his run modtrl goat///////8000 $ @ 7234; 69; Loads - PLOAD1 - Missing Documentation, Unexpected Answers If on the TYPE field of the PLOAD1 entry, the element coordinate system direction (e.g. TYPE=FYE) option is selected, then the projection (i.e. SCALE=FRPR or LEPR) option is ignored and the result is the same as the SCALE=FR (or LE) option. Avoidance: There is no avoidance. @ 7237; 70.5; Documentation - DMAP Module Dictionary, OUTPUT2, INPUTT2 - SFE 4 276 EC 1401 MSC/NASTRAN Version 68 may not be able to handle an OUTPUT2 file of a matrix generated from an external client written computer program that follows MSC's documentation description of proper OUTPUT2 format. It is not the INPUTT2 step that is crashing, it is any subsequent operation on the datablock, such as TABPT, OUTPUT4, ADD, MATPRN or the like. Avoidance: Use V67.5 to convert the OUTPUT2 file to an OUTPUT4, and then read in the OUTPUT4 file into V68.

@ 7238; 69; p-Elements - DATAREC, OUTPUT - UWM 6514 (SDRPOP) When there are any OUTPUT bulk data entries, but no DATAREC case control keywords, the following warning is produced: *** USER WARNING MESSAGE 6514 (SDRPOP) THE DATAREC= 0 CASE CONTROL COMMAND REFERENCES UNDEFINED OUTPUT BULK DATA ENTRY. USER INFORMATION: THE DATAREC COMMAND WILL BE IGNORED. USER INFORMATION: THERE WILL BE NO ERROR-ESTIMATE OUTPUT FOR THE ADAPTIVITY ANALYSIS. Avoidance: To avoid the warnings, the OUTPUT entries should be removed. @ 7242; ; p-Elements - GMCORD - Inefficient Processing If a GMCORD coordinate system is used for the material, load, or displacement coordinate system, execution may be inefficient since the coordinate system is processed independently for each integration point. Avoidance: Other than not using GMCORDs there is no avoidance. @ 7243; 70.5; Documentation - TABPT, BGPDTS - DMAP Module Dictionary According to the DMAP module dictionary "TABPT may occasionally misidentify real numbers or character values on the IBM/MVS-like computers". This problem is not limited to the IBM/MVS-like computers.

Avoidance: Use TABPRT instead of TABPT. @ 7244; Answers 69; Optimization/Design Sensitivity - ANALYSIS=FLUTTER, DMIG - Wrong

For flutter design sensitivity and optimization, the sensitivity results will be in error if there are multiple subcases and a second or subsequent subcase includes a different M2PP, K2PP or B2PP request in the case control. The sensitivity analysis is based on the generalized matrices from the first subcase and will therefore be incorrect for the subsequent subcases. Avoidance: There is no avoidance. @ 7253; 69; Nonlinear Analysis - MPCFORCE - Missing Output MPCforces are not output in nonlinear analysis, solution 106. Avoidance: Insert the following DMAP alter in Version 68.2: compile nlstatic alter 'ADD DELCVECT,CVECT0'(,-1) add5 qqgni,qgni,,,/qmgni//-1. $ call dbstore qmgni,,,,//nloop/0/' '/0 $ alter 'DBVIEW CVECTH' call dbfetch /qmgni,,,,/solcuri/0/0/0/0 $ call dbstore qmgni,,,,//solcur/0/' '/0 $ alter 'APPEND QGNI,/QGNR' $ file qmgni=ovrwrt $ $ call dbfetch /qmgni,,,,/nloop/0/0/0/0 $ file qmgnr=append $ APPEND QmGNI,/QmGNR/2 $ APPEND MPC FORCE VECTORS alter 'EQUIVX QGNR/QGN' call dbstore qmgnr,,,,//0/0/' '/0 $ compile super3 alter 'ADD PG,PJ/DPJ' call dbfetch /qmgnr,,,,/0/0/0/0/0 $ equivx qmgnr/qmg/-1 $ COMPILE SEDISP ALTER 'MPYAD PSS,CRX'(2) MPYAD PG,CRX,/PGX $ $ ALTER 'IF ( NOQMG>-1 ','' $ IF ( NOQMG>-1 AND NOMSET>-1 AND NOT(DELTA) ) THEN $ $ ALTER 'UPARTN USET,PG','' $ IF ( APP 'NLST' ) EQUIVX PG/PGX/ALWAYS $ UPARTN USET,PGX/PM0,,,/'G'/'M'/'S'/1 $ $ COMPILE CFORCE ALTER 'MPYAD KXY,UY,PX','' $ IF ( APP='STATICS' or APP='NLST' OR APP='BKL0' OR (APP='CYC' AND APP1='STATICS') ) MPYAD KXY,UY,PX/QX///-1 $ @ 7260; 69.1; Nonlinear Transient Heat Transfer - DELAY, CHBDY - Incorrect Loa d Output

If the DELAY bulk data entry is used to define an offset in time for the applied load. The actual heat load is applied correctly, and the resultant temperature value is correct. However in the data recovery for the heat flux of the HBDY element the load is applied incorrectly. Avoidance: Ignore the applied load output for the HBDY elements. @ 7266; 69; DMAP - MALTER - Extra output The MALTER statement produces a listing of the altered subDMAP. This printout cannot be suppressed even if COMPILER NOLIST is specified. However, COMPILER REF and COMPILER DECK produce the correct results. Avoidance: There is no avoidance. @ 7270; 69; Acoustic Analysis - PARAM,WTMASS - Wrong Answers PARAM,WTMASS is applied to both the fluid and the structure, even though the mass of the fluid is in different units. Avoidance: a. use mass density for density values and ensure that all mass input values are in mass units. b. or insert the following DMAP alter in V68.2: compile semg noref nolist alter 'MJJX,/-1/WTMASS','' $ type parm,,cs,n,cwtmass,mwtmass $ IF (NOMGG>=0) then $ dbstatus VGFS//S,N,NOVGFS $ IF ( NOVGFS>0 and wtmass1.0 ) THEN $ EMA GPECT,MDICT,MELM,BGPDTS,SILS,CSTMS,MDICTP,MELMP/ MJJX1,/-1 $ MASS matgen ,/ig/6/lusets/0/lusets $ gx1 matrix cwtmass=cmplx(wtmass) $ add ig,vgfs/wtmass/cwtmass//3 $ matmod wtmass,,,,,/wtmassg,/28 $ gxg mpyad mjjx1,wtmassg,/mjjx $ ELSE $ EMA GPECT,MDICT,MELM,BGPDTS,SILS,CSTMS,MDICTP,MELMP/ MJJX,/-1/WTMASS $ MASS ENDIF $ endIF $ NOMGG>=0 @ 7276; ; Composites - PARAM,NOCOMP - Inconsistent Stresses Homogeneous stresses, output when using 0 or -1 for PARAM,NOCOMPS, for PCOMP-based elements are calculated inconsistently between linear and non-linear solutions. Since homogeneous stresses are based upon smeared laminate properties, both calculations yield only approximate the lamina stresses (see also current error list number 1818) but both solutions should use the same method. The two methods currently being used are: For linear analysis:

S(z) = G1 * E - z * G2 * C while for nonlinear analysis: S(z) = G1 * ( E - z * C ) where: C = curvature (chi) E = reference plane strain (epsilon) G = modulus matrix S = stress z = distance from reference plane @ 7284; (2)

(1)

69; Miscellaneous - DIAG - DIAGs Out of Range Not Checked I don't think this needs to be an external error report. Please read text below for error.

@ 7288; 69; Nonlinear Buckling - MPC, RBE*, RBA