MSC.Nastran Error List Update August 29, 2004 1-4299402 Documentation/QRG - NLRGAP Contents Description Incorrect The MSC.Nastran Quick Reference Guide incorrectly describes the TABK field of the NLRGAP entry when it is set to less than zero. When TABK<0 the description under the Contents heading on the NLRGAP entry should be "force vs penetration" NOT "stiffness vs pentration". 1-5742601 Documentation/QRG - Aeroelastic Analysis - MONPNT1 - UFM 315 (IFPDRV) XYZ default not supported The Quick Reference Guide indicates that there is a default value of 0.0 for X, Y, and Z on the MONPNT1 entry but leaving any of these fields blank results in the following fatal message USER FATAL MESSAGE 315 (IFPDRV) FORMAT ERROR ON BULK DATA ENTRY MONPNT1 1-6084723 Aeroelastic Analysis - KE-Method, FA2 - SFM 4276, EC 3002 A flutter analysis using the KE-method fails in the FA2 module with a FSM 4276, EC 3002. The MKAERO1 contains 20 k values each separated by 0.05 in k for one Mach number. Avoidance: Modify the MKAERO1 entry to have fewer k values and a more commonly used distribution. 1-6155301 2005 Transient Analysis - TRLG - Enforced Acceleration gives poor answers An enforced acceleration problem may exhibit strange behavior due to the mixed precision computations in the TRLG module (specifically in the TRLGCD subroutine). 1-7162927 Restarts/Aeroelastic Analysis - RESTART- AJJ unnecessarilty recomputed A SOL 145 or SOL 146 aeroelastic analysis RESTART where only changes are made to the structural model will unnecessarily recalculate the AJJ matrix even though the aeroelastic model is unchanged. Avoidance: Resusing the aerodyanmics by DBLOCATING the ADB dbset works as an alternative to the automatic restart. 1-8004001 Parallel Processing - Vendor implementation of tfork for parallel is missing MSC.Nastran does not support SMP parallel on Primepower because the vendor implementation of tfork is missing. Delivered tpl problems dxxtp10 and others will fatal with the message: vendor implementation of tfork is missing. Avoidance: There is no avoidance. 1-8267177 Complex Eigenvalues - EIGC - Poor Results with SYSTEM(108)=1 If the Householder QR method is forced using system(108)=1, poor results may be obtained. Avoidance: If the Householder method was not forced the QZHESS method would have been used on the problem that encountered the poor results. The QZHESS method would have solved the problem accurately and more efficiently. 1-8550605 Loads - TEMPPi - Unexpected Results The QRG documents which elements the TEMPPi entries are applicable to. However, the code does not perform any check. If a TEMPPi entries references an element that is not supported no thermal load will be applied and unexpected answers will result. Avoidance: There is no avoidance other than verifying that valid elements have been referenced. The code needs to be modified to have GP3 check GEOM3 against GEOM2 for proper TEMPxx vs element type and issue a fatal message if improper elements are referenced. 1-9638401 2004.5 Nonlinear Buckling Analysis - Lanczos - Infinite Loop in READ The READ Module may go into an infinite loop for non-linear buckling model when using the Lanczos method. 1-9754740 2004.5 DMAP - Poor Message, BIOMSG: ERROR 3001 A dmap that is missing a "/" such that the first parameter is in the output slot failed with the message below which gives no indication of the problem. BIOMSG: ERROR 3001 HAS OCCURRED IN ROUTINE FREAD , FILE INDEX (FILEX) = 0 Avoidance: Correct the problem dmap statement. 1-10509309 2004 Virtual Mass - MFLUID - Results are not independent of element's grid ordering Eigenvalues results on elements wetted on both sides with virtual mass, such as a baffle, are not independent of the grid numbering. That is slightly different results may be obtained when an element is numbered 1, 2, 3, 4 versus 4, 3, 2, 1. Results are not expected to vary by more than 10 percent. Avoidance: Change the direction of the element normals of two sided elements, rerun and average the eigenvalue results. 1-10523001 Post Processing - PARAM,POST - Incorrect von Mises Stress calculated in Patran for plane strain When using plane strain elements in MSC.Nastran sol 101, the von Mises stress is calculated properly in Nastran, but Nastran does NOT store the Stress ZZ component to the .op2 or .xbd and therefore Patran will show a wrong von Mises stress because it calculates von Mises stress from a tensor with SZZ=0. As is done for sol 106, change NASTRAN sol 101 so it outputs the sigma_zz for plane strain elements to the .xdb and .op2. A 1-11336904 Buckling - EIGRL - SFM 7340 Lanczos may have trouble with some buckling problems and the jobs may fail with SYSTEM FATAL MESSAGE 7340. Avoidances: This problem is known to exist if more modes are requested than exist in the structure. The problem may be caused by modelling errors such as a massless mechanism but if the model has been verified other possible avoidances include specifying system(273)=1, changing the frequency range of interest or simply specifying ND, changing the maxset on the eigrl entry, reversing the load and searching the positive range instead of the negative range. 1-11725405 Documentation/QRG - CBUSH - Remark 10 references Remark 2 instead of Remark 3. Remark 10 of the CBUSH entry in the Quick Reference Guide says "When CID >= 0, the element x-axis is set as in Remark 2..." This should be changed to specify Remark 3 instead of remark 2. I.E. Change the statement to "When CID >= 0, the element x-axis is set as in Remark 3..." Also, the definitions on the TKIDi, TBIDi and TKNIDi fields on the PBUSHT can use some extra clarification. A statement should be added indicating that the data input corresponds to directions 1 through 6. For example, the TKIDi field is defined as follows: "Identification number of a TABLEDi entry that defines the stiffness vs. frequency relationship." This should be clarified to say: "Identification number of a TABLEDi entry that defines the stiffness vs. frequency relationship in directions 1 through 6." 1-11981265 2004.5 Nonlinear Analysis - CTETRA(10) Yields Wrong Nonlinear Stress Output at grid points The nonlinear TETRA(10) element does not extrapolate the Gauss point stresses to the grid points correctly. In one analysis the nonlinear equivalent stress output for a plastic analysis with TETRA(10) elements exceeded the yield stress value at grid points but the same analysis with HEXA(8) elements did not exceed the yield stress. 1-12061001 Buckling - EIGRL - Uses bad shift when first root is positive When f1 on the eigrl entry is blank, the Lanczos buckling solution computes a good estimate of the first root prior to the Lanczos solution. If the root is positive it discards it, and uses 1.0 as a first shift instead . Avoidance: Change the sign of the loads to obtain a negative first root. 1-12122861 2004 Documentation/QRG - CBUSH - UFM 6629 (TA1BSH) The following remark should be added to the QRG description of the CBUSH entry: If the distance betwen GA and GB is less than .0001, or if GB is blank, then CD must be specified. 1-12277506 2004 Frequency Response - FREQ, FREQ1, FREQ2 - Missing Output In frequency response analysis if a FREQ entry exists that explicitly defines more than 9999 frequencies or there is a combination of FREQ1 and FREQ2 entries that define more than 9999 frequencies, than not all frequencies will be solved for. If 12000 frequencies are defined, then only the first 2000 frequencies will be solved. Avoidance: Either define the frequency steps with only a freq1 or only a freq2 entry, else break the frequency steps up and solve in separate runs. 1-12310701 Optimization/Design Sensitivity - Superelements, DCONSTR - Missing Fatal Message If a DCONSTR points to a response that does not exist, it is typically a User Fatal Error. However, if the the design task includes superelements, the user input error is not detected and the DCONSTR that points to the nonexistent response is simply ignored. Avoidance: There is no avoidance except to carefully check that the referenced responses exist or to remove the superelements from the job for purposes of checking the user input. 1-12315301 2004 Nonlinear Analysis - TEMP(BOTH) - Plane strain analysis yields incorrect out of plane rotations A nonlinear plane strain analysis using CQUAD4 elements, with thermal loads and temperature dependent material properties results in out-of-plane rotations being calculated when they should be all zero. 1-12356001 2004 DMAP - INPUTT2 - SFM The INPUTT2 module will fatal if an attempt is made to rewind ITAPE=-3 on an unlabeled op2 file. 1-12460901 Aeroelastic Analysis - Poor Trim specification leads to misleading error If a user create a trim case that has more supported degrees of freedom than controllers (URDDs, to be specific), the following error may be generated: SYSTEM FATAL MESSAGE 3008 (UTMCOR) MODULE = ASG INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ZZXHMD USER ACTION: INCREASE OPEN CORE BY AT LEAST 7 WORDS PROGRAMMER INFORMATION: LOCATION KEY = PI1 0FATAL ERROR This message does not indicate the real problem, so it is of no use to the user. The fix is to put in an error check to test that the number of supported degrees of freedom equals the number of URDD controllers. This check should be located at the begining of ASGD. 1-12705302 Nonlinear Analysis - MAT1, MATT1 - Elements that are effectively linear produce plastic strain When temperature loads and elements refering to mat1/mats1 are present in a sol 106 nonlinear analysis run, it is possible that elements which are nonlinear with respect to temperature dependency only (mat1/matt1) produce equivalent plastic strain. 1-12774307 2004.5 Postprocessing - PARAM,POST,0 - PCOMPG: xdb results not readable by MSC.Patran. XDB results for elements that reference the PCOMPG entry are incorrect when read into MSC.Patran. The first results layer does not even exist, and subsequent results appear incorrect. XDB support for PCOMPG will be added when PATRAN supports the PCOMPG property type. The avoidance is to use an accending identification sequence for the ply enumeration, although this might be inconvient and restrictive. 1-12862226 Documentation/QRG - param,mmfil The QRG description of the new parameter MMFI is incomplete. The information in the V2004 Release Guide on this parameters use needs to be transferred to the QRG. Avoidance: Please see the V2004 Release Guide. 1-12893301 Optimization/Design Sensitivity - DESSUB, RMS, PSD - Fatal Message in dom10f DESSUB which includes RMS/PSD response as constraints 'must not' appear above subcase level. If DESSUB for RMS/PSD responses appears above the subcase level, the job may fail with a generic fatal message from dom10f. Avodiance: Move the DESSUB command with RMS/PSD to the subcase level. Note that this problem exists only in multiple subcase scenarios. 1-13251205 2005 Optimization/Design Sensitivity - PCOMP - Incorrect punched pcomp entries Solution 200 may produce incorrect PCOMPs entries in the punched output when the PCOMP LAM field is set to "MEM" in the original deck. The generated punched PCOMP entries may have a blank MEM field. Another problem with punched PCOMP entries that may be encountered is Ctrl-X in the SOUT field. Avoidance: Edit the punched outut to correct the problem pcomp entries. 1-13471801 Optimization/Design Sensitivity - PBEAM, BOX1 - Optimizer can not make progress It has been observed that SOL 200 tasks that include beam properties that are physically close to zero may fail to make progress. An example is the I12 property for a BOX1 section type that has dimensions that give I12 property values that are many orders of magnitude smaller than the I1 or I2 properties. In these cases, small changes in dimensions cause huge changes in the property, resulting in a violated contraint that the optimizer may not be able to deal with. Avoidance: Avoid section types that have this behavior or pose the problem in such as way that the properties are not expected to become small. 1-13574607 2004.5 Miscellaneous - buildsss on Windows - call buildsss.bat not recognized The command to build the sss on the Windows V2001 delivery (msc2001 buildsss) would not work because necessary files were delivered in the wrong directory. Avoidance: copy buildsss.bat.i386 to ..\i386\buildsss.bat copy buildsss.bat.del to ..\nast\del\buildsss.bat Then run the buildsss command as documented. 1-14068501 DMP - Linux - LAM won't boot with BAT=YES Starting w/ 2001R4 (2001.0.9) MSC.Nastran boots the LAM/MPI daemons for the user. However, with RH7.3 and Slackware systems, the LAM daemons may not boot if "BAT=YES" is specified. Avoidance: Use BAT=NO This problem does not occur w/ MSC.Linux. The problem is because when BAT=YES is used, the first process completes, and the child processes become ZOMBIES. We set a flg to ignore child zombies. Because of that flag, LAM daemons will not start from within the shell. I think starting the lam daemons for the users is more important then BAT=YES, so I am leaving the code as is. 1-14233604 2005 Elements - CQUADR, PARAM,CHECKOUT,YES - Incorrect grid point weight generator output Mass for the CQUADR element is not included in the grid point weight generator results when param,checkout,yes is specified. 1-14286512 2004.0.4 Distributed Memory Parallel (DMP) - SEP1X - Free Floating Grids Cause DMP to Fail in SEP1X In MSC.Nastran 2004.0.3 (released to only one client) a model with free floating grids, meaning grids that are not attached to the structure, may cause dmp jobs to fail. This includes models with grids that are only used as reference points. Avoidance: Set system(294)=2 (which will print the external IDs of those free grids, search for FREE FLOATING, and then remove the grid entries. If the grids were used as reference points, they have to be replaced by coordinates. Grids that are referenced only on a PLOTEL element are not considered free floating, so attaching the reference grids to PLOTELs is another way to avoid the problem. 1-14487301 Documentation/QRG - ECHO The 2004 release has new options for the PUNCH portion of the ECHO command. The QRG description of this command has errors in describing the new options. The PUNCH and NEWBULK describers should be changed as follows: PUNCH: The entire Bulk Data will be written to the punch file. (i.e,. omit the "in sorted form") NEWBULK: In SOL 200, a complete unsorted bulk data deck is written to the punch file with updated design model entries. (i.e., change "complete and sorted" to "a complete unsorted" 1-14556901 2004.5 Matrix Methods - param,inrel,-2 - Lagrange Multipliers, Incorrect matrix to factor diagonal messages When Lagrange Multipliers are used, as in param,inrel,-2, calculations in SOL 101 and several other places, large matrix to factor diagonal matrix ratios may be prined out and they may be in error. Avoidance: If the "MATRIX/FACTOR DIAG. RATIO" is identical to the "MATRIX DIAGONAL" they can be safely ignored. If the run fatals, param,bailout,-1 can be used to avoid the fatal error. 1-14667001 2004.5 Elements - NSM1, PSHELL - Missing mass, Wrong Answers The NSM1 command does not work on shell elements. Avoidance: User the NSM or NSML2 commands. 1-14717802 2004.5 Eigenvalue Analysis - EIGR, GIV, HOU - Poor performance in wilvecd Householder and Givens eigenvalue methods may get poor performance on HP and Linux IA64 systems. procedures. 1-14777101 2004.5 Large Problems/Frequency Response - DPD - SFM 4276 (READ) EC 3021 (DPD) Very large SOL 111 jobs may fail with the message: SYSTEM FATAL MESSAGE 4276 (READ) ERROR CODE 3021 (DPD) Avoidance: There is no known avoidance. 1-14779931 2005 Nonlinear Analysis - plasticity - Failure to converge or wrong answers In nonlinear analysis, sol 106, Nastran does not handle a hardening slope change after the 1st hardening slope in plasticity analysis. This may lead to a failure to converge or wrong answers. 1-14895708 2004.5 SOL 600 - CBAR - Null OUTPUT2 file is created when model consists of on CBARs The SOL 600 t16op2 translator (outr=op2 option) requires that elements with stress and strain be present. If a model consists entirely of CBAR and CBEAM elements that only generate internal forces, the generated op2 file will be null and the following message will be written to the f06 file: *** SYSTEM FATAL MESSAGE 6551 (INPTX2) AN END-OF-FILE WAS DETECTED ON UNIT 11 DURING BINARY INPUTT2 PROCESSING PROGRAMMER INFORMATION: 1. A KEY VALUE WAS BEING READ 2. THE LAST KEY VALUE READ: 0 0*** FATAL ERROR. 0 NO. FORTRAN RECORDS READ = 0 NO. FORTRAN WORDS READ = 0 0FATAL ERROR 1-15002802 2004.5 SOL 600 - PLOADi, CPENTA - Incorrect Pressure Loads, Wrong Answers SOL 600 pressure loads are applied to the wrong face ID in the Marc deck for CPENTA elements. 1-15004301 2004.5 Spotwelds - CWELD, ELPAT - UFM 7549 (mdg2ed) A model with CWELD elements and curved shells may fail with the message: USER FATAL MESSAGE 7549 (MDG2ED) This error is caused by tight projection tolerance. In v2004 the default projtol is set to 0.0 to avoid picking wrong elements for PARTPAT format. The zero tolerance works for flat shells, but it causes errors for some curved or warped shells. Avoidance: Insert swldprm,projtol,0.01 to set the projtol to 1%. The default projtol will be changed in version 2005 from 0.0 to 0.01. Note that the projection tolerance in v2001 was set to 10% which was excessively large. 1-15068202 2004.5 Miscellaneous - Compaq Alpha v5.1a-5.1b - SFM 4276 (tbk) EC 7777 on Compaq Alpha A bug exists in V5.1a-b of the Compaq Alpha Unix operating system which may cause the floating point stack to be corrupted. This may cause a traceback in any version of MSC.Nastran and potentially could cause wrong answers. All clients must apply the 5.1B-1 patch. Avoidance: This error will be marked fixed in V2005 even though there is nothing MSC can do to fix the error. 1-15107501 2004.5 SOL 600 - Parallel, memory allocation bug puts elements in the wrong domains - Wrong Answers SOL 600 Parallel has a memory allocation bug which puts elements in the wrong domains. This leads to Marc aborting or wrong answers. 1-15113501 2004.0.6 Eigenvalue Analysis - SOL 103, MPCforces - UFM 6144 If MPCforces are requested on a subset of points in SOL 103 then the job may fail with SFM 6144. Avoidances: Request MPCFORCE=ALL or insert PARAM,SPARSEDR,NO or insert the following DMAP alter: compile sedisp alter 'CALL CFORCE USET,GM,UG,UH1','' CALL CFORCE USET,GM,UG,UH1,MMG,M2MG,BMG,B2MG,KMG,K4MG,K2MG,, PM,OLX,,/ QMG/ 1-15168101 2005 Optimization/Design Sensitivity - DSAPRT - Write operation tried to write a record that was too long A SOL 200 job on sgi irix that was writing a long DSAPRT record failed with the message "Write operation tried to write a record that was too long". Avoidance: There is no avoidance. 1-15214414 2005 DMP - MDMODES, EIGRL - Hang in SEMR2, Signal 15 Error If distributed memory parallel (dmp) mdmodes job is executed but f2 on the eigrl entry is not specified, the job may hang in SEMR2 or fail in various ways including a signal 15 error on HPUX Itanium. Avoidance: Specify f2 on the eigrl entry. In Version 2005 and beyond this condition is trapped with a user fatal message. 1-15217604 2005 SOL 600 - Excessive Memory is Required for large models Excessive memory is required for large SOL 600 model. Avoidance: There is no avoidance. 1-15238701 2005 Optimization/Design Sensitivity - DLINK, DESVAR - UFM 7008 If a DLINK entry references DESVAR entries that are not selected by a DESVAR command, the program issues USER FATAL MESSAGE 7008 (THE NUMBER OF DLINK ENTRIES EXCEEDS THE NUMBER OF DESVAR ENTRIES. USER INFORMATION: THE NUMBER OF DEPENDENT DESIGN VARIABLES MUST BE LESS THAN THE TOTAL NUMBER OF DESIGN VARIABLES). Avoidance: Remove the offending DLINK entry from the input file. 1-15245201 2004.5 Acoustic Analysis - EPOINT - Wrong answers If EPOINTs are specified in a fluid-structure model and some of the structural grid points in the a-set are numbered higher than the fluid grid points in the a-set then the results will be wrong. Avoidance: Insert the following DMAP alter: compile gma alter 'GKAM USETD,PHSA,','' MERGE PHSA,,,,,VAFS/PHSAF/1 $ GKAM USETD,PHSAf,mis,lamas,DIT,M2SS1,B2SS1,,CASES,lammats/ MSHH0,B2SHH0,K1SHH,PHDSH0,MODELSTS,modselsv,LAMASN/ NOUE/LMODES/lfreq/hfreq/-1/-1/-1/0/S,N,FMODE/ KDAMP/false//APP $ endalter 1-15247204 2004.5 SOL 600 - SOL600,106 - Error number 1030 Models that run successfully in SOL106 may fail when using SOL 600,106 when QUAD4 elements exist that are translated into the uu plane. 1-15251748 2004.5 Rotordynamics - RGYRO, UNBALNC - Wrong Answers If RGYRO with UNBALNC are included in the static subcase, the nonlinear transient response subcase will different answers on different machines. 1-15269705 2005 Superelements - PARAM,CONFAC - UFM 4277 and 4278 PARAM,CONFAC specifies the tolerance factor used in checking the congruence of the location of the boundary points between image superlements. In some models USER FATAL MESSAGE 4277 (SEP1ED)an d USER FATAL MESSAGE 4278 may be issued indicating that the tolerance has been exceeded when in fact it hasn't. Avoidance: An unrealistically large value of PARAM,CONFAC for example 1.0, may need to be specified to avoid the fatal message. 1-15278401 2004.5 SOL 600 - CBEAM - Offsets Ignored, Wrong Answers SOL 600 beam offsets are sometimes ignored and not reflected in the SOL 600 marc input deck. 1-15279901 2004.5 DMAP - MATMOD(21) gives wrong answers on complex matrices Matmod option 21 converts a sparse factor matrix from the DCMP module into 3 true matrices. When multiplied together properly they reform the input matrix to the DCMP module. The true matrices are easier to understand than the packed factor, where they are all in one data block. True matrices can be input to any matrix processing module, but the packed factor cannot. The option 21 has been demonstrated to behave well on real matrices. It can give wrong answers on complex matrices. Avoidance: No avoidance is known. Verified by Paresh for t2: The ferror matrix is numerically zero 1-15305906 2004.5 Nonlinear Analysis - NLITER - Signal 8, SFM Nonlinear analysis may fail in the NLITER module and issue a SYSTEM FATAL MESSAGE 4276 indicating an overflow or a SIGNAL 8 error. Avoidance: This error occurs because some error tolerance calculations are performed in single precision, modifying the convergence criteria on the nlparm entry may help avoid this problem. 1-15309511 2004.5 Spot Weld Element - CWELD - UFM When two or more CWELD elements that have angles that fail the tolerance test, nastran aborts after reporting the first element and fails to check and report on any other elements. Avoidance: Set CHKRUN to 1 on the SWLDPRM entry. 1-15334301 2004.5 Heat Transfer - UFM 4551 followed by SFM 4276 EC 31 If a heat transfer job fails to converge (USER FATAL MESSAGE 4551) may be followed by SYSTEM FATAL MESSAGE 4276 (GETCOL) ERROR CODE 31 because matrix IFSH has an incorrect trailer. 1-15341502 2004.5 DMAP - MODTRL - SFM 4276 EC 31 User DMAP errors may result in the following fatal message: *** SYSTEM FATAL MESSAGE 4276 (GETCOL) ERROR CODE 31 PID= 0 *** USER INFORMATION MESSAGE 4276 (GETCOL) that identifies the routine GETCOL even though the problem routine is GTIDMC. 1-15372203 2004.5 Data Recovery - STRAIN, PCOMP - UFM 3005 (SDR2) Similar to error report q1-8126205 which reported that UFM 3005 occurs when STRESS(CORNER) is requested with composites, it has been found that a request for STRAIN(CORNER) output which should be ignored for composite elements, will lead to the messages: *** USER WARNING MESSAGE 6418 (SDR2A) THE BILIN OPTION FOR STRESSES OVERRIDES ALL OTHER OPTIONS IN STRAIN AND FORCE COMMANDS. *** USER FATAL MESSAGE 3005 (SDR2) ATTEMPT TO OPERATE ON THE SINGULAR MATRIX (NONE) IN SUBROUTINE SQD43D Avoidance: Limit the strain request to non-composite elements by specifying a SET. 1-15378701 Installation - Using 'this_host' on SERVER line of the license file prevents installer from working If the host name on the SERVER line of a FLEXlm license file is set to 'this_host', lmstat does not return the correct vendor daemon status. The Nastran installer relies on correct operation of lmstat. This error will cause the installer to assume no nastran licenses are being served. This problem has been reported to Marcrovision. Avoidance: Change the host name on the SERVER line to a valid host alias for the target system. The Macrovision problem id is P7078: lmstat -a fails to report vendor daemon status when run "remotely" 1-15388155 2005 Rotordynamics - RGYRO, STATSUB - SFM 4276, EC 30, TRD Rotodynamics models, RGYRO, with static subcases in transient analysis may fail in the TRD1 module with SYSTEM FATAL MESSAGE 4276 ERROR CODE 30. 1-15422604 2004.5 Optimization/Design Sensitivity - DSVG1 - Segmentation Violation When a large scale optimization job (having million DOFs) takes the non-adjoint path, the job may fail in DSVG1 with a segmentation violation. Avoidance: Specify as large a mem as possible. 1-15426513 2004.5 Restarts - RESTART, MODTRL - Attaching a read only database may lead to fatal error in MODTRL. Dynamic restarts may be inefficient and SubDMAPs PHASE1A. PHASE1DR, GMA and FREQRS may be executed unnecessarily. Furthermore, if the cold start database is attached read-only a fatal error may be issued in the MODTRL module. Avoidance: Insert the following DMAP alter in your cold start run: compile gma alter 'ENDIF \$ fastfr='(,-1) else $ xfastfr=false $ for restart efficiency endalter Or insert the following alter in your restart run: compile gma alter 'modtrl.*bdd'(,-2) dbstatus bdd//s,n,nobdd $ alter 'modtrl.*bdd','' if ( nobdd<1 ) modtrl bdd////6 $ alter 'modtrl.*k4hh'(,-9) if ( false ) delete /k4hh,,,, $ dbstatus k4hh//s,n,nok4hh $ alter 'modtrl.*k4hh','' if ( nok4hh<1 ) modtrl k4hh////6 $ endalter 1-15432813 2004.5 Component Mode Synthesis - CSET -SFM 9158 (MHRED), UFM 9032 (ERRPH1) MSC.Nastran 2004 may fail with the message below and setting param,zrocmas,yes as suggested in the message may not avoid the error. This problem is demonstrated with tpl deck edr2n on the Cray SV1 platform but it could occur on other systems as well. ^^^ SYSTEM FATAL MESSAGE 9158 (MHRED) ^^^ THE C-SET FLEXIBILITY MATRIX IS SINGULAR. ^^^ USER ACTION: SPECIFY PARAM,ZROCMAS,YES TO REMOVE THE MASS ON THE C-SET DURING COMPONENT MODES. Avoidance: In addition to param,zrocmas,yes insert param,fzero,XXX where XXX is a real value just below the lowest flexible mode and above all "rigid body" modes. This causes the correct rigid body modes to be used for inertia relief supports in the autosprt subdmap. Other avoidances are to add the parameters: param,mhred,no and param,respath,old or param,mhred,no and param,fzero,xxx 1-15463011 2005 SOL 600 - TEMPD is not recognized by the translator In SOL 600 TEMPD is not recognized by the translator. This will lead to missing temperature loads and wrong answers. Avoidance: The only avoidance is to specify the initial temperature on TEMP entries. 1-15466201 2004.0.6 Installation - RedHat AES 3 - Segmentation Fault When MSC.Nastran is submitted on an IA64 system with the RedHat AES 3 opterating system, the following message will appear: Segmentation fault (core dumped) Avoidance: Download the new "nastran" driver from ftp.mscsoftware.com and place in $MSC_BASE/msc2004/linux64/nastran 1-15477101 2005 Nonlinear Analysis - TEMP(INIT), PCOMP - Wrong Answers For nonlinear analysis of temperature dependent composite materials, the initial stiffness matrix should be computed based on the initial temperature referenced by Case Control command TEMP(INIT)=N. However, for Version 2004, the initial stiffness matrix is computed based on the TREF on the bulk data entry PCOMP. This is wrong. 1-15487601 2004 RedHat AES 3 - CRASH - GLIBC_2.2 If V2001 of MSC.Nastran is run on RedHat AES 3 on Itanium systems, then the following error will occur: analysis: relocation error: $MSC_BASE/msc2001/linux64/analysis: symbol _dl_loaded, version GLIBC_2.2 not defined in file ld-linux-ia64.so.2 with link time reference Avoidance: The problem has been corrected in a special build that is to be made available on the external web at: http://www.mscsoftware.com/support/software_updates/index.cfm#nastran The build date of this system is February 19, 2004. Download analysis.aes3, place in $MSC_BASE/msc2001/linux64, and submit with "proc=aes3" 1-15497401 2004 Licensing - SMP - UFM 3060, Excessive tokens checked out. The special release of MSC.Natran 2001.0.9 for Linux IA64 that added support for ffio with title page date of November 19, 2003 contains a licensing error that causes the executable to search for a SMP (shared memory parallel) license during every execution. Avoidance: This error has been corrected in a special release of 2001.0.9 with title page date of January 26, 2004. This system may be obtained from MSC's external software update web site or the user can revert back to the standard Linux IA64 2001.0.9 system that does not support ffio. 1-15502121 2004.5 Spotwelds - Missing UFM 7549, SFM 4276 EC 3012 Models with spot welds that should fail with the message: USER FATAL MESSAGE 7549 (SEPWLD) indicating that the projection of GS GRID ID=xxxxx onto the surface cannot be found or lies outside the plane, may fail to issue this message and isntead fail with SYSTEM FATAL MESSAGE 4276 (QOPEN) EC 3012. 1-15518520 2004.5 Miscellaneous - ADAMSMNF - Cray Only, Traceback in AMSMI2 Some adamsmnf jobs that create an Adams modal neutral file may fail in Version 2004.0.6 on Cray SV! Beginning of Traceback: Called from line 42 (address 13710276a) in routine 'TRBK'. Called from line 40 (address 77535d) in routine 'RECOVR'. Called from line 112 (address 55361c) in routine 'sysrcv'. Called from address 13373636a in routine '__handlr'. Called from address 13740534a in routine 'AFSMI2'. Called from address 15101264b in routine 'AFGMNF'. Called from line 136 (address 15077120c) in routine 'XSEM16'. Called from line 133 (address 54500d) in routine '$SEGCALL'. Called from line 133 (address 225677b) in routine 'XSEMDR'. Called from line 66 (address 63175b) in routine 'NASTMON'. Called from line 379 (address 1372d) in routine 'MAINAL'. Called from line 343 (address 54455d) in routine '$SEGRES'. Called from line 343 (address 12005663d) in routine '$START$'. End of Traceback. 1-15525703 2005 Data Recovery - MAXMIN(DEF) results are order dependent If a MAXMIN(DEF) definition for a MAGnitude (either Translation or Rotation) follows a MAXMIN(DEF) for a specific component (i.e. T3), then the reported MAGnitude results will all be zero. If the order of the MAXMIN(DEF)s are reversed (MAG first, then component) the results are correct. This order gives zeros for the MAGT results: MAXMIN(DEF) ACCE T3 MAXALG=2 MAXMIN(DEF) ACCE MAGT MAXALG=3 whereas this order does not: MAXMIN(DEF) ACCE T3 MAXALG=2 MAXMIN(DEF) ACCE MAGT MAXALG=3 1-15525713 2004.0.7 Data Recovery - STRAIN, DISP, COORDi - Wrong Answers With Version 2004.0.0 if the Case Control includes an output request for STRAIN, then the CID option for grid-type responses (DISP, SPCF, MPCF) will be ignored and the output coordinate system will not show up in the printed .f06 output. Requests for other element-based output such as STRESS or FORCE do not affect the grid-based output, just the STRAIN request. 1-15537101 2004.5 Dynamics - Modal Participation Factor phase angle has wrong sign The sign of the phase angle of the modal participaltion factor results may be in error. compile mpf nolist alter 'PARTN ABE,VGXFS','' PARTN ABE,VGXFS,/,,ABESFP, $ ADD ABESFP,/ABESF/(-1.0,0.0)//3 $ NEGATE ABE MATRICES alter 'SMPYAD PHGXFH'(1,0),'' SMPYAD PHGXFH,ABESF,PHGXSH,,,/ABEH/3/1///1/1 $ alter 'SMPYAD PHGXFH'(2,0),'' SMPYAD PHGXFHX,ABESFXX,PHGXSHX,,,/ABEH/3/1///1/1 $ 1-15550901 2005 Optimization/Design Sensitivity - SPCD - Incorrect Responses for Enforced Motion If a SOL 200 design task includes enforced motion using SPCD's, the final response and element data recovery results are incorrect. The optimization results are correct as are the sensitivities. Avoidance: If PARAM NASPRT 1 is used, all data recovery results will be correct. Alternatively, one can simply ignore the final response results and create an input deck from the final design. TPL deck d200rd15 demonstrates this error and correction in verison 2005. 1-15553302 2004.5 Acoustics - Data Recovery - Excessive CPU when no MPF output is requested Even if no modal participation factor output is requested, the data recovery is still performed on all fluid-structure interface points; thereby defeating the benefits of sparse data recovery. Avoidance: Insert the following alter: compile spdr1 alter 'ajp'(2,-1) type parm,nddl,i,y,fluidmp,structmp $ if ( fluidmp<>0 or structmp<>0 ) then $ alter 'ajp'(2) else $ call xAdd5 vp,vky,vmy,vby,/vpx/cu/cu/cu/cu/cz $ endif $ compile semfreq alter 'if ( structmp','' if ( structmp<>0 or fluidmp<>0 ) then $ compile fea $ feafreq in V2004r2 alter 'if ( structmp','' if ( structmp<>0 or fluidmp<>0 ) then $ compile spdr0 alter 'if ( fluidmp','' if ( fluidmp<>0 or structmp<>0 ) then $ endalter 1-15567801 2004.5 Acoustics - Enforced Motion, SPCD, and sparse data recovery - Wrong Answers If sparse data recovery is activated in fluid-structure analysis with enforced motion wrong answers may be produced. Avoidance: Specify PARAM,SPARSEDR,NO or insert the following DMAP alter compile cforce1 alter 1,1 SUBDMAP CFORCE1 MXY,mqxy,M2XY,m2qxy,BXY,bqxy,B2XY,b2qxy,KXY, K4XY,k4qxy,K2XY,k2qxy,PHY,KDXY,kdqxy,axy,aqxy, yx,vxpc,uset/ MXY1,BXY1,KXY1,pmyy,pbyy,pkyy,vxcg/ APP/APP1/forctype $ alter 'add vy1,vy2','' Matmod axy,aqxy,,,,/vy3,/12/s,n,nonull/2/-1 $ add vy1,vy2/vy2a $ add vy2a,vy3/vy $ alter 'add vy1,vy2'(2),'' Matmod axy,aqxy,,,,/vy3,/12/s,n,nonull/2/-1 $ add vy1,vy2/vy2a $ add vy2a,vy3/vy $ alter 'add vy1,vy2'(3),'' Matmod axy,aqxy,,,,/vy3,/12/s,n,nonull/2/-1 $ add vy1,vy2/vy2a $ add vy2a,vy3/vy $ compile gma alter 'umerge1 usetd,adya,,,' call dbstore a1sf,adsf,,,//0/0/' '/0 $ compile spdr1 alter 'call cforce1',''(,1) call dbfetch /a1sf,adsf,,,/0/0/0/0/0 $ CALL CFORCE1 MSF,mysf,M2SF,m2ysf,BSF,bysf,B2SF,b2ysf,KSF,K4SF,k4ysf, K2SF,k2ysf,,KDSF,kdysf,a1sf,adsf,,vspc,uset/ MSF1,BSF1,KSF1,,,,vscg/ APP/app/'spcforce' $ if ( noyg>0 ) CALL CFORCE1 MSs,,M2Ss,,BSs,,B2Ss,,KSs,K4Ss,, K2Ss,,,KDSs,,,,,vspc,uset/ MSs1,BSs1,KSs1,,,,/ APP/app/'spcforce' $ alter 'call cforce1'(3),'' if ( dompcf ) CALL CFORCE1 MMG,,M2MG,,BMG,,B2MG,,KMG,K4MG,,K2MG,,,KDMG,,, ,,Vmpc,uset/ MMG1,BMG1,KMG1,,,,vmcg/ APP/app/'mpcforce' $ compile fdrmgen alter 'call cforce1',''(,1) call CFORCE1 MSF,,M2SF,,BSF,,B2SF,,KSF,K4SF,,K2SF,,phif,kdsf,,, ,,vspc,uset/ msf1,bsf1,ksf1,,,,/ APP/APP1/'spcforce' $ if ( noyg>0 ) call CFORCE1, MSS,,M2Ss,,BSS,,B2Ss,,KSS,K4Ss,,K2Ss,,,kdss,,, ,,vspc,uset/ mss1,bss1,kss1,,,,/ APP/APP/'spcforce' $ alter 'call cforce1'(3),'' CALL CFORCE1 MMG,,M2MG,,BMG,,B2MG,,KMG,K4MG,,K2MG,,phig,kdmg,,, ,,vmpc,uset/ MMG1,BMG1,KMG1,,,,/ APP/APP1/'mpcforce' $ alter 'call cforce1'(4),'' CALL CFORCE1 MMy,,M2My,,BMy,,B2My,,KMy,K4My,,K2My,,, kdmy,,,,,,uset/ MMy1,BMy1,KMy1,,,,/ APP/APP/'mpcforce' $ compile cforce alter 'call cforce1','' call CFORCE1 MXY,,M2XY,,BXY,,B2XY,,KXY,K4XY,,K2XY,,uy,kdxy,,,,, vxpc,uset/ mxy1,bxy1,kxy1,,,,vxpc1/ APP/APP1/forctype $ endalter 1-15654005 2004.5 SOL 600 - RBE2/RBE3 nodes are not included in all SOL 600 domains for Parallel Processing RBE2/RBE3 nodes are not included in all SOL 600 domains for Parallel Processing. Usually all REB2/RBE3's must be included in all domains and all grid points associated with them must also be included in all domains, othewise the job will diverge. 1-15664507 2005 Nonlinear Heat Transfer - Excessive Output Heat transfer, sol 159, may place the: N O N - L I N E A R I T E R A T I O N M O D U L E O U T P U T for each timestep on a different page. If printed this wastes paper and it also has the potential of doubling the output because page header information is repeated for each page. 1-15689201 2004.5 SOL 600 - RFORCE is not translated to Marc properly SOL 600 RFORCE is not translated to Marc properly. It needs distributed load code 105 rather than 100 or 103. 1-15689204 2004.5 SOL 600 - MARCIN (include file) missing data - Nastran aborts The SOL 600 MARCIN (include file) may result in missing data and may cause Nastran to abort. 1-15738901 2005 Documentation/QRG - EQUILIBRIUM - Ignored in SE models Remark 3 of the EQUILIBRIUM Case control command in the QRG should indicate that the EQUILIBRIUM commnad produces no output in the presense of superelements. 1-15742867 2004.0.7 DDAM - missing output in MSC.FEA When using the new DDAM option in MSC.FEA, the results are missing. Avoidance: The DDAM and DDAMOUT subdmaps need to be replaced. The error is corrected in Version 2004.0.7 which is only available on the FEA 2004 R2 that is scheduled to be released by the end of May 2004. The error is also corrected in MSC.Nastran 2004.5 scheduled to be released June 15, 2004. 1-15795828 2004.5 SOL 600 - BCPARA - FTYPE default of coulumb friction is not translated If FTYPE is not specified on the BCPARA entry no Defaults are used even though the Quick Reference Guide mentions indicates that the default is Coulomb. Avoidance: Explicitly specify FTYPE on the BCPARA entry. 1-15831209 2005 Nonlinear Analysis - ESE - Wrong Answers with INTOUT SOL 106, nonlinear analysis, may create incorrect nonlinear ESE when the 9th field of NLPARM bulk data card, INTOUT, is not set to ALL in Version 2004 and earlier releases. Avoidance: Specify INTOUT=ALL. 1-15831507 2005 Frequency Response - SUPORT - SFM 6424 and 6144 Direct Frequency response with SUPORT entries may fail with the messages: SYSTEM FATAL MESSAGE 6424 (DFNSB) THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE INCOMPATIBLE LOAD VECTOR ROWS = 2536 FACTOR MATRIX ROWS = 2537 SYSTEM FATAL MESSAGE 6144 (MERGE1) THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY: The number of rows in DAY is not equal to the number of zeros in partitioning vector VAY User Information: Size of input matrices and partitioning vectors: DAY : Rows= 2537 by Cols= 1 VAY : Rows= 2537 no. of non-zeros= 1 no. of zeros= 2536 0 Avoidance: compile sedfreq alter 'call mmfind1','' type parm,nddl,char8,n,ltset,llset $ UPARTN USET,Kaa/KLL,,,/ltset/llset $ UPARTN USET,maa/mLL,,,/ltset/llset $ CALL MMFIND1, Kll,Mll,USET,SILS,EQEXINS,,bgpdts/ MECHA,phir,vspc,lll/ s,mmech/'l '/false $ endalter 1-15842401 2004.5 SOL 600 - Multiple NLSTRAT entries result in fatal message Even though multiple NLSTRAT entries are legal, SOL 600 gets a FATAL ERROR when more than one NLSTRAT is defined. Normally there needs to be one NLSTRAT per subcase with an additional one with ID=0 for Marc's phase zero if any at all are entered. 1-15848202 2004.5 SOL 600 - Memory request of ... words failed / RSSCON not supported In Version 2004 solution 600 may fail with the message: memory request of 83137782 words failed during the translation phase - no Marc input file gets created. Avoidance: Increasing the memory may not allow the problem to be solved. Running with a very large memory requested resulted in a marc input deck being created and the following message being written to the f06 file: TRANSL WARNING - RSSCON is not supported by the internal Marc translator. Marc will not be executed. 1-15848212 2004.5 Elements - STRESS, PSOLID, CHEXA - Stress at Gauss points not available for c IN=2 Writing out the stresses of CHEXA elements at the Gauss points for IN=2 is not possible. Stress at the grid points will be output. 1-15854501 2005 Submittal - node= - V2004 Windows missing nastran.rmt file The PC version of v2004 (both r1 and r2) does not include the nastran.rmt file (.../msc/msc2004/i386). This means that the "node=" option does not function. Workaround is to copy the one from v2001 (however there are issues with that file as well as you need to include a line that reads: jidtype=%jidtype% as a minimum - this is addressed in a separate CSR - see 1-15854504) 1-15854504 2005 Submittal - UFM, Input file does not exist While using "node=" command to submit from Windows to unix, the job will fail if the extension of the input file ( .bdf for example) does not match the "jidtype" setting on the remote machine. This error persists even if the "jidtype=bdf" keyword is used on the launching PC side. Avoidance: If the following line is added to the PC's nastran.rmt file, then the jidtype keyword is passed thru correctly and the job recognizes the keywords and will run correctly: jidtype=%jidtype% Note that the "nastran.rmt" file itself is missing completely from the 2004 (r1 or r2) installations. The jidtype command above is in the standard nastran.rmt file for Windows. When it is included in the delivery, this error will be eliminated. 1-15862001 2004.5 SOL 600 - SOL 600 incorrectly checks out a nastran nonlinear license A SOL 600 job may incorrectly check out a nastran nonlinear license as evidenced by the following message in the log file. Acquired 100 licenses for Group CAMPUS (MSC.Nastran Nonlinear) 1-15879701 2004.5 SOL 600 - TEMPP1 & TEMPRB may produce incorrect POINT TEMP Marc input leading to wrong answers SOL 600 TEMPP1 & TEMPRB may produce the wrong POINT TEMP in the Marc deck leading to wrong answers. 1-15895505 2005 Complex Eigenvalue Analysis - CLAN - Wrong Answers In Version 2004, complex Lanczos may produce bad answers if the block size is automatically augmented. The block size is only augmented when the number of repeated roots is greater than the block size or the solver is unable to converge and this rarely occurs in real world models. Avoidance: The problem can be avoided by setting system(108)=8. 1-15907201 2004.5 SOL 600 - Eigenvalue analysis after a nonlinear solution with contact gives wrong results SOL 600 eigenvalue analysis after a nonlinear solution with contact gives wrong results for the nonlinear portion of the job as well as the eigenvalue portion. Fixed using 1-15862001 1-15923905 2004.5 Documentation/SOL 600 - BCBODY - UFM 316 If the documented text of "3D" is entered into the "DIM" field (field 3) of the BCBODY entry, then MSC.Nastran 2004 and 2004r2 fatal out with a UFM 316 format error as it tries to read the "d" as part of an exponent instead of as a character as documented. Avoidance: Leave this blank (since 3 is the default) or specify just the number "3". BCBODY,1 $ Default is OK BCBODY,2,3 $ Using a number is OK BCBODY,3,3D $ Gives UFM on "3D" field Running even SOL 100 with the above as the bulk data file will demonstrate the problem 1-15925501 2004.5 External Superelements - EXTSEOUT - SFM 4276 (BLDPK) EC 211 Large external superelement jobs may fail in the MERGE1 module with the message: SYSTEM FATAL MESSAGE 4276 (BLDPK) ERROR CODE 211 PID= 0; f04: EXTOUT 166 UMERGE1 BEGN BLDPK TERM 1-15931801 2005 SOL 600 - out= leads to UFM 1019, SFM 6551, SFM 1004 If SOL 600 requests that marc results be output in the f06 (OUTR=f06) and out= is specified on the nastran submittal command, nastran will fail. *** USER FATAL MESSAGE 1019 (OPNPFL) or *** SYSTEM FATAL MESSAGE 6551 (INPTX2) AN END-OF-FILE WAS DETECTED ON UNIT 11 DURING BINARY INPUTT2 PROCESSING OR *** SYSTEM FATAL MESSAGE 1004 (INPTYP) UNABLE TO CREATE FORTRAN FILES ENTRY FOR UNIT 11 FOR LOGICAL NAME INPUTT2 USING DEFAULT FILE NAME. ERROR CODE = 1. 1-15944704 2004.5 Frequency Response - QSET, ASET1 - UIM 7588, SFM 6144 In SOL 108 with modal reduction (ASET1, QSET) the GKAM module issues USER INFORMATION MESSAGE 7588 indicating the number of modes that are retained. The number of modes indicated retained is actually the number of modes calculated and the then number of modes calculated is actually the number of q-set degrees of freedom. The residual vectors are subsequently thrown away and later in the solution MERGE1 fails because of incompatibility of datablocks DAY and VAY. 1-15950512 2004.0.7 SSSALTER - ddam - Wrong Answers The NRL summing convention may not be used due to an inconsistent parameter name used in the ddam* sssalter Avoidance: Download the latest v2001 alter (ddamall.v2001) from our website. This alter replaces the ddama and ddamba alters. 1-15950532 2005 Elements - CTRIAX6 - Incorrect Stress Label When using axisymmetric elements, vonmises stresses are labelled as octahedral stresses. Only the labels are incorrect, the values are correct. 1-15962101 2004.5 Elements - CWELD, CFAST, PFAST - Wrong mass when lumped mass specified in field MASS If the MASS field of the PFAST entry is populated with a value, the mass added is much larger than the lump mass specified. PARAM,GRDPNT,0 reports different masses in different directions and the eigenvalue analysis fails. 1-15994609 2004.5 P-elements - GMINTC and GMINTS - SFM 4276 EC 3021 If GMINTC and GMINTS Bulk Data entries are both present in the model then the run will terminate in the GP0 module with: *** SYSTEM FATAL MESSAGE 4276 (READ) ERROR CODE 3021 PID= 0 Avoidance: There is no avoidance. 1-16017810 Documntation/QRG - RCROSS - RCROSS Case Control Command In the QRG, there is an error in the description of the RCROSS case control command. It must read CORF instead of CROF. If CORF is mistyped, then the default PSDF is used, and no message is issued. 1-16026003 2004.5 SOL 600 - Gasket materials combined with other solid element materials generate error in Marc SOL 600 Gasket materials, MATG, combined with other solid element materials generate error in Marc. 1-16028004 2004.5 Optimization/Design Sensitivity - UFM 3001: Datablock CASEDM does not exist The fatal message USER FATAL MESSAGE 3001 DATABLOCK CASEDM DOES NOT EXIST can result when eigenvector senstivities are requested and the only RTYPE that is used is FORCE. Avoidance: An avoidance is to add other RTYPE's (DISP,STRAIN,ESE,STRESS or TOTSE) that invoke eigenvectors with an id that is equal to or greater than the highest ID appearing on a DRESP1 with RTYPE=FORCE 1-16028303 2005 Transient Analysis - SPCD - Wrong Answers with sparse data recovery. Sparse data recovery usage in transient analysis (both SOL 109 and SOL 112) employing SPCD enforced motion will give wrong answers if the base displacement or velocity is non-zero. This should not affect enforced acceleration scenarios, but may seriously affect enforced displacement or enforced velocity scenarios. Avoidance: Specify sparsedr=no. 1-16038804 2005 Documentation - DMAP Programmer's Guide Aerodynamic Module examples are obsolete In the DMAP Programmers Guide, the description of the aerodynamic modules is up to date. However, most of the examples still show the old argument lists, e.g. ADG, AMG, ... 1-16060036 2004.5 Frequency Response - METHOD - UFM 9056, METHOD Command required in all subcases In all previous versions of Nastran, under sol 111, the METHOD command was required only in the first subcase. In Version 2004 if multiple subcases are specified in frequency response but a METHOD command is not specified in all subcases the job will fail with the message: USER FATAL MESSAGE 9056 ( MODEFSRS) NO METHOD COMMAND WAS SPECIFIED IN THE CASE CONTROL SECTION. 1-16074001 2005 Dynamics/Enforced Motion/DMP/Acoustics - SFM 6144 (PARTN1) Acoustic models with enforced motion in DMP may fail with the message: SFM 6144 (PARTN1) Size of input matrices & partitioning vector incompatible Columns of PHSA0 not equal to rows of VR Avoidance: compile modefsrs alter 'if ( relmtn )'(2),'' if ( relmtn and not(procid>1 and (fdmodes or mdmodes)) ) then $ endalter 1-16090301 2004.5 DMAP - MATOFP module - no print control, ignores paging, uses CARDNO The MATOFP module has several deficiencies: 1. no print control. 2. ignores paging 3. uses old CARDNO processing Avoidance: There is no avoidance. 1-16096104 2005 Enforced Motion, SOL 109 - Unexpected Spikes in Acceleration Direct enforced motion with prescribed displacements (SOL 109) may result in unexpected acceleration spikes at the beginning and end of the enforced displacement. Enhancements to enforced motion have corrected this problem in version 2005. 1-16107905 2004.5 DMAP - MATMOD Option 40 - Poor message and wrong answers MATMOD Option 40 has several errors: 1. Incorrectly issues the following message in the f04: *24* Wrttrl Warning - Trailer type of terms for indexed matrix 201 is incorrect: 0. An automatic update has been made. *24* 2. Incorrectly issues SWM 7598 when doing parameter conversion from single to double precision. 3. Does not ouptut the matrix in machine precision if I1 is purged and TYPE parameter is not consistent with machine precision. 4. SFM 6918 and 6920 are fatal errors but do not terminate the run. 5. If output is purged then there is no fatal. 6. NZWDS and DENSITY in the trailer may be incorrect. Avoidance: There is no avoidance. 1-16109501 2004.5 Documentation/QRG - Nonlinear, PSOLID, TETRA - Nonlinear Supports 5-10 noded TETRA The PSOLID entry description in the V2001 and V2004 Quick Reference Guide incorrectly indicate that nonlinear is not supported for the 5-10 noded TETRA element. 1-16128001 2004.5 Performance - matmod option 16 on hpux Bad performance of matmod option 16 to punch DMIG has been reported for Nastran 2004 HPUX 2004 systems. 1-16132601 2004.5 Data Recovery - ESE ouput for DMIG missing with SETP When SETP case control is used to combine existing sets in a model with DMIG(s), the DMIG output maybe be missing in the ESE output. 1-16132609 2004.5 Data Recovery - ESE/EKE output printed twice when SETP used When the SETP case control command is used to combine existing SETs, and more than one type of output is requested among ESE, EKE and EDE, the output may be printed twice. 1-16143401 2004.5 Multilevel Superelements - Upstream generalized coordinates are discarded. If KOA is null, which can happen on collector superelements that have no physical boundary points, the coefficients for the generalized coordinates of the upstream superelements may be discarded. Avoidance: An alter that avoids this problem for non-inertia relief runs follows: $ remove line 72 in sekr $ 72 IF ( NOT(STATICS) AND $((XRESVECO='NO' AND XRESVIRO='NO' AND $ INRLM>-1)OR $ SEID=0 OR SEID=FLUIDSE) ) THEN $ alter 72,72 $ if (not statics or seid=0) then $ 1-16148301 2004.5 Optimization/Design Sensitivity - MFREQ/DFREQ, Superelements - Infinite Loop MFREQ/DFREQ SOL 200 optimization jobs may encounter an infinite loop condition if the number of records in FRQPRP is larger than NZ1. This scenario is most likely to happen when superelements are utilized and the number of subcases is high. Avoidance : Use the following DMAP alter only if the design model is in the residual (debug_dsad2.alter). compile descon $ alter 'dsad ','' $ DSAD RSP1CT,R1TAB,RESP12,OBJTAB,CONTAB,BLAMAX,LAMASX, CLAMAX,DIVTAB,AUXTAB,STBTAB,FLUTAB,OUGVS1,OESS1, ,OEF1AA, , , ,OQGS1,DSCREN,XINIT, tabdeq,COORDN,OLX, FRLSE, FRQRSP,CASEDS,CASEm, , OPTPRM,DVPTABF,PROPIF,BGPDTS,DNODEL,WGTM, , , ,resp3,rmstab,rmsval, UGXF, QGXF, QMPXF, UHXF, , , , ,MODRSP,CASEDMX,PHGX, , , ,upsdtx, RQATAB,RESP12X,RESP3X/ R1VAL,R2VAL,RSP2R,R2VALR,CVAL,CVALR,OBJTBR,CNTABR, R1TABR,R1VALR,DRSTBL,FRQRPR,UG1,AUG1,R1MAPR,R2MAPR, CASDSN,CASDSX,DRDUG,DRDUTB,CASADJ,LCDVECI,rr2idr, r3val,r3valr,resp3r,rmstbr,rmsvlr,FRLR,FOLR, UGM21, QGM21, QMPM21, UHM21,MODRPR,upsdt, RQATABR, RSP2XR,RSP3XR/ vols/vol/S,N,OBJVAL/S,N,NR1OFFST/S,N,NR2OFFST/ S,N,NCNOFFST/APP/ -1/SEID/DESITER/EIGNFREQ/ S,N,ADJFLG/PEXIST/MBCFLG/RGSENS/protyp/autoadjx/ fsdcyc/s,n,nr3offst/inrel/s,n,tadjc/PEID/s,n,ACTFREQ/ s,n,FREQ1/s,n,DLOADDS/FRQ345/DISCYC $ endalter $ 1-16149704 2005 Distributed Memory Parallel (DMP - ASET - SFM 7467, SFM 6144 This is now fixed. (Remember don't test MDMODES on tiny job for now.) DMP does not support the use of ASET/ASET1 entries. If ASET/ASET1 is used, SYSTEM FATAL MESSAGE 7467 is issued correctly in version 2001. In version 2004, SFM 6144--the sizes of the input matrices and partitioning vectors are incompatible--is issued. Since ASET is not supported in DMP, this also implies that DMP does not support ADAMSMNF. Avoidance: For models using DMP, remove the ASET/ASET1 entries. ASET/ASET1 entires are supported in MDACMS and MDMODES and Freq Domain Modes in V2005. GDACMS and GDMODES are not supported. 1-16163101 2005 Elements - QUAD4, TEMP, MAT2, MAT8 - Poor Answers In MSC.Nastran a single precision transformation is performed for non-isotropic 2D materials (MAT2 and MAT8). This may lead to poor answers and is especially noticable when zero stresses are expected for a free expansion under thermal loads. Avoidance: Use the QUADR element. 1-16181301 2004.5 Elements - CRAC2D, CRAC3D, MAT8, MAT9 - UFM TA1 If the crac2d or crac3d elements reference mat8 or mat9 orthotropic/anisotropic materials the job will fatal in Version 2004. 1-16230501 2004.5 Rotordynamics - ROTSEKE - Strain and kinetic energies are incorrect There are error in the ROTSEKE subDMAP that lead to 1) Rotor numbers on output do not change 2) Energies are not calculated correctly. 1-16267101 2004.5 Optimization/Design Sensitivity - DRESP3 - Unexpected failure in DSTAp2 for DRESP3 optimization job An external response optimization job (DRESP3) may fail in DSTAP2 without an error message. Avoidance: There is no avoidance. 1-16270201 2004.5 Distributed Memory Parallel (DMP) - LAM/MPI error - IA64 Distributed Memroy Parallel (DMP) will not work with MSC.Nastran on IA64 systems running RHEL 3.0 (Red Hat Enterprise). A message stating that the LAM Deamons will not boot will appear. Avoidance: Use MSC.Nastran V2004.5 (a.k.a. MSC.Nastran 2004 R3) or Install an OS that uses GLIBC 2.2. 1-16270204 2004.0.3 Memory - Unable to Allocate - IA64/Linux V2004.0.0 IA64/Linux systems cannot allocate more than 2.0 Gb on the "mem" parameter. V2001.0.9 allowed memory allocation over 2Gb. This error was corrected in V2004.0.3. 1-16306501 2004.5 Distributed Memory Parallel/ACMS - DMP - DISUTIL option 10 Bus Error DISUTIL option 10 may incur a Bus Error. This could affect distributed memory parallel ACMS, which is where DISUTIL option 10 is used most. 1-16323801 2004.5 SOL 600 - MATEP - MATEP workhardening slope, H, is not translated to Marc, Wrong Answers In SOL 600 the MATEP workhardening slope, H, is ignored and is not translated to Marc. 1-16323804 2005 SOL 600 - CORDi - Loads applied in cylinderical coords are sometimes incorrect SOL 600 loads applied in cylinderical coordinates are sometimes incorrect. This can happen even if the loads are in the basic coordinate system but the grids have specified a cylindrical output coordinate system in field 7 of the GRID entry. In most cases, the loads are correct. Only in unusual circumstances are the loads incorrect. 1-16326601 2005 Optimization/Design Sensitivity - DESVAR - UFM 7105 When an optimization job specifies DESVAR IDs > 1 million and the DESVAR command is used to select part of DESVAR entries, the job may fail with the message: USER FATAL MESSAGE 7105 (DOPR3F) The Fiedl DVID aaaa on DVPREL1 Entry ID = yyyy is not selected by the DESVAR Case Control command. Avoidance: Specify DESVAR IDs < 1 million. 1-16332103 2004.5 Static Analysis - PARAM,INREL,-2 - UFM 9050 In Version 2004, when param,inrel,-2, is specified to select inertia relief without the need to specify a SUPORT entry the analysis may fail with USER FATA MESSAGE 9050. Avoidance: Specify param,inrel,-1 and specify a suport entry. 1-16420502 2004.5 SOL 600 - Missing SPCs In SOL 600, an array in a is dimensioned 6 but values are set up to 8. This may cause Linux systems to fail to write SPCs resulting in an unconstrained model or wrong answers. 1-16442912 2004.5 Matrix Methods - DCMP - Fails to issue UFM leading to wrong answers. Version 2004 uses Lagrange multipliers in static analysis and hence negative factor diagonals can now be common and the stiffness well conditioned. Thus, in Version 2004 DECOMP may ignore negative maxratio values and fail to issue a fatal message when it should. 1-16443309 2005 External Superelements - EXTSEOUT, OUTPUT(PLOT), UFM 2025 (SDR2) If an external superelment, EXTSEOUT, superelement contains a displacement output request. and OUTPUT(PLOT) commands are used, the following FATAL message will occur: *** USER FATAL MESSAGE 2025 (SDR2) UNDEFINED COORDINATE SYSTEM ID = 268435455 Avoidance: Removing the OUTPUT(PLOT) section will eliminate the error. 1-16455901 2005 Optimization/Design Sensitivity- Eigenvector sensitivity with multiple boundary condtions broken Eigenvector sensitivity analysis based on DRESP1 entries was introduced in the 2004 release of MSC.Nastran. The original release supported multiple boundary conditions, but this capability was broken in the 2004.0.3 release (a.k.a 2004r2) when support for multiple boundary conditions in frequency response optimization was integrated. Avoidance: Go back to the earlier 2004 release or wait for the 2005 release. 1-16470701 2005 Optimization/Design Sensitivity - Multiple Boudary Conditions not robust with multipl analysis types Mutiple boundary conditions with frequency response analysis was introduced into SOL 200 in Version 2004.0.3 (a.k.a. 2004R2). Testing has shown problems when there are multiple disciplines as well as multiple boundary conditions. In particular, runs with ANALYSIS = MODES and ANALYSIS= MFREQ with different boundary condition can produce fatal messages. Quality report 1-1655901 is related. Avoidance: The dmap changes required to support analysis =MFREQ and analysis=MODES and multiple boundary conditions are extensive so this capability is not considered to be operational. It will be operational in Version 2005. 1-16470704 2005 Optimization/Design Sensitivity - Extra responses in formatted sensitivity prints Generalized mass and stiffness responses are "spawned" when the Rayleigh Quotient approach is applied to eigenvalue sensitivity analysis. These response are typically suppressed when formatted design senstivities are printed, but they appear if two different subcases share a DRES[1 id with type = eign or freq and the sensitivity is computed for both. In this case, the senstivities of the generalized matrices can appear following the eigenvalue sensitivities. Avoidance: An avoidance is to not share a DRESP1 ID for multiple subcases. 1-16474104 2004.5 Nonlinear Buckling Analysis - DCMP - Missing UIM 4698 to identify instabilities To identify instabilities and isolate buckling, the user should look for UWM 4698. However, in Version 2004 DCMP does not print the message making it impossible to identify buckling phenomena. The following is an example of the missing message: *** USER WARNING MESSAGE 4698 (DCMPD) STATISTICS FOR DECOMPOSITION OF MATRIX K(appropriate) . THE FOLLOWING DEGREES OF FREEDOM HAVE FACTOR DIAGONAL RATIOS GREATER THAN 1.00000E+07 OR HAVE NEGATIVE TERMS ON THE FACTOR DIAGONAL. GRID POINT ID DEGREE OF FREEDOM MATRIX/FACTOR DIAGONAL RATIO MATRIX DIAGONAL 102 R2 -1.93940E+03 2.14680E+04 1-16500402 2004.5 Superelements - Print Format error in TABPRT The Superelement Summary Output in the f06 filem may contain asterisks for large integer grid id's (******). 1-16503108 2005 Acoustics - FLSPOUT, STRUCTMP - Mislabeled Ouput Modal participation factors are calculated for each subcase but are mislabled as the first subcase. 1-16548801 2005 Heat Transfer - RMG2 - SFM 3008 (RMG2) Heat transfer jobs with large view computations may fail with the message: *** SYSTEM FATAL MESSAGE 3008 (RMG2) INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE RMG2 0FATAL ERROR 1-16603701 DMAP - NOT, AND, OR - SFM 223 poor diagnostic If the name of an expression like NOT or AND is used as a variable name, it is accepted in some statements but causes a message that is difficult to understand when it appears. An error report is attached to the back of the test problem, along with some suggested fixes. mag 1-16606402 2005 SSSALTER - spc101a alter missing In Nastran 2004 the spc101a alter was not included. Avoidance: SSSALTERs are posted to the web at: http://www.mscsoftware.com/support/prod_support/nastran/sssalters/v2004/toc.cfm 1-16630701 2005 Optimization - DRESP1 - Transient response types on the DRESP1 do not support multiple components. Rermark 7 for the DRESP1 entry in the QRG indicates that TDISP, TVELO, TACCL and TSPCF support multiple components. A code bug blocks this to a single component less than or equal to 6. Also for GPFORCP. the ATTA input is a grid id. therefore there are documentation errors in table 8-9 on the DRESP1 entry in the QRG and in Remark 7, GPFORCP should be omitted. Avoidance: Single components can be used for the transient responses with no loss of functionality. Mutiple components only simplify the input. 1-16658001 2005 Postprocessing - MSFRACTION - No output written to op2 file No MSFRACTION results are written to the op2 file. 1-16663924 2005 Differential Stiffness - CBAR - Missing UWM 6174 leads to wrong answers Solutions that use differential stiffness (105, 106 and any SOL with STATSUB) that have CBEAM elements with offsets will correctly issue the message below. However; this message may not be issued for similar models with CBAR elements. *** USER WARNING MESSAGE 6174 (EBEMD) BEAM ELEMENT (EID=110) WITH OFFSETS ARE NOT SUPPORTED IN DIFFERENTIAL STIFFNESS OR NONLINEAR ANALYSIS. REMODEL WITHOUT USING BEAMS WITH OFFSET. 0FATAL ERROR 1-16700702 2005 Postprocessing - POST - Missing Output in op2 file If POST NODISP is specified in one subcase then results may be missing from the op2 files in subsequent subcases. 1-16723804 2005 Frequency Response - MEFFMASS - signal 8 MEFFMASS command may lead to the following error on Nastran 2004 HPUX systems: ---------- SIGNAL CAUGHT: Signal number = 8 Signal code = 14 Signal tid = 1 Fault addr = 4000000001352823 FP inexact = 0x0 FP divide0 = 0x8000 FP underflow = 0x0 FP overflow = 0x10000 FP invalid = 0x0 Avoidance: Either remove the MEFFMASS command or run on another machine. 1-16761101 2005 Superelments - EXTSEOUT - Double Field Grids result in SFM 3002 in the BDRYINFO module. External superelements, EXTSEOUT, may fail with SYSTEM FATAL MESSAGE 3200 (LOGIC ERROR 28) in the BDRYINFO module if double field GRID entries are used. Avoidance: Use single field grid entries 1-16769901 2005 Documentation - V2004 DMAP Programmers Guide - UMERGE1 The Version 2004 DMAP programmers guide shows the following for the format of the UMERGE1 module: UMERGE1 USET,A11,A21,A12,A22/MAJOR/SET1/SET2/IOPT $ It should be: UMERGE1 USET,A11,A21,A12,A22/A/MAJOR/SET1/SET2/IOPT $ 1-16771901 2005 Composites - PCOMPG - Strength Ratio may cause composite stress & failure index output error When PCOMPG bulk data entries are used (with a blank FT field) and Strength Ratio output request is turned on (PARAM,SRCOMPS,YES), the composites stress, failure index and strength ratio output may be either missing or incorrect. 1-16815502 2005 Composites - PCOMP - Nastran fails with signal 11 if duplicate IDs for MAT entries exist If a PCOMP entry references a MAT8 entry that has the same ID as another MAT entry, i.e. MAT1, Nastran fails with signal 11 in the log file. No other error messages are given. 1-16821701 2004.5 Installation - HPUX 11 - ERROR: Unable to update RC file MSC.Nastran Version 2004.5 may have trouble installing on older versions of ksh on HPUX 11. If the following messages are encountered during installation then upgrade the ksh to at least 82.10.1.48 which was released in 2002. The error is considered fixed by this upgrade. Begin configuring MSC.Nastran 2004.5 Creating default version links... Configuring licensing... makercentry[4]: /tmp/./msc/conf/nast20045rc: cannot create ERROR: Unable to update RC file "/tmp/./msc/conf/nast20045rc" Setting user configuration items... makercentry[4]: /tmp/./msc/conf/nast20045rc: cannot create ERROR: Unable to update RC file "/tmp/./msc/conf/nast20045rc" makercentry[4]: /tmp/./msc/conf/nast20045rc: cannot create ERROR: Unable to update RC file "/tmp/./msc/conf/nast20045rc" 1-16855001 2005 Nonlinear Analysis - STRESS(PUNCH) - Bad Output in PUNCH File In SOL 106, nonlinear analysis, a request for nolinear stresses to be output to the punch file, STRESS(PUNCH), will lead to NanQ or ????? in the punch file. 1-16858013 2005 Documentation - V2004 DMAP Programmers Guide - MTRXIN description for NOMATi The Version 2004 DMAP Programmer's Guide MTRXIN description for the NOMATi flags indicates that the flags are set to a value of +1 whether the matrix is present or not. The description indicates: NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is generated; 1 otherwise. this should read: NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is generated; -1 otherwise. 1-16877703 2005 Miscellaneous - Disk full on Windows 2000 leads Access Violation A "DISK FULL" condition may lead to an access violation on Windows 2000. Avoidance: This error can be avoided by specifying "sysfield=mapio=no" in a .rcf file or on the command line when the MSC.Nastran job is submitted. 1-16903901 2005 External Superelements - EXTSEOUT - Missing Output An assembly run employing an external superelement created using the EXTSEOUT feature does not give any output for the external SE if the creation run has no DISP request. Avoidance: Apply the following dmap alter to the assembly run: compile extotmin alter 'dbstatus x_tug,x_rga',''(,1) $ dbstatus x_tug,x_tef,x_tes,x_tqg,x_rga// s,n,notug/s,n,notef/s,n,notes/s,n,notqg/s,n,norga $ if ( notug>0 or notef>0 or notes>0 or notqg>0 or norga>0 ) then $ endalter $ 1-16917806 2005 Optimization/Design Sensitivity - DRESP2, DRESP1 - UFM 3007 (dopr3) SOL 200 jobs may fail if DRESP2 entries that reference DRESP2 entires coexist with DRESP2 entries that reference DRESP1 entries. 1-16924801 2005 Miscellaneous - Include may not working on Windows 2000 if file attributes are chaned from default On Windows 2000, if a nastran include data file has the attributes (properties, Advanced, uncheck the "file is ready for archiving" and uncheck the "For fast searching") Then the job aborts. 1-16936701 2005 SOL 700 - SOL 700 in Natran 2004r3 (2004.5) does not work on Windows systems SOL 700 for Natran 2004r3 (2004.5) does not work on Windows systems because the latest Intel compilers provide full path names for the dytran-lsdyna input file and dytran-lsdyna is not able to accept full path names. 1-16937701 2005 Case Control - ESE THRESH does not work when there is no SUBCASE command The THRESH option of the ESE Case Control command does not work if a SUBCASE command is not present. Avoidance: Add a SUBCASE command. 1-16938101 2005 SOL 600 - PCOMP - Wrong Answers when Z0 is specified When translating the Nastran PCOMP enty into a Marc deck, if the Z0 field is specified, then the resulting Marc COMPOSITE entry will be wrong. The current action is to take whatever value is in the PCOMP Z0 field and map it directly into the Marc's COMPOSITE 3rd datablock 4th field. The 'meaning' of the Z0 on the PCOMP entry and this field in Marc are incompatible. In NASTRAN, Z0 on a PCOMP entry defines the distance from the reference plane to the bottom surface of the laminate. In Marc, the field it is mapped to represents the position of the user-defined reference plane. This is the value of the local z-coordinate of the user-defined plane with respect to the geometric midplane. 1-16959902 2005 Superelements - SEEEXCLD - UFM 6788 (SEPMFS) A model that has duplicate boundary grids in the residual structure may fail to exclude the duplicate grid and may fail with the message: *** USER FATAL MESSAGE 6788 (SEPMSF) SUPERELEMENT 1 GRID 3 AND SUPERELEMENT 0 GRID 13 HAVE CONFLICTING MANUAL DIRECTIVES. 1-16969464 Miscellaneous - SYSTEM(55)=0 - UFM 315 (IFPDRV) If SYSTEM(55) is set to 0, Nastran will likely fail in ifpdrv with the message: *** USER FATAL MESSAGE 315 (IFPDRV) FORMAT ERROR ON BULK DATA ENTRY GRID SYSTEM(55), a.k.a. IPREC, only expects a value of 1 for single precision or two for double precision. The user is never expected to set this system cell. 1-16989601 2004.0.7 Miscellaneous - IA32 Linux - Include files > 2Gb - UFM 398 Input files greater than 2Gb may not be included in a data file in Versions 2004.0.6 and prior on IA32 Linux systems. Version 2004.0.7 and later systems allow include files greater than 2Gb. Avoidance: If you must use version 2004.0.6 or earlier, then break the include file into separate files each less than 2Gb 1-17011701 2005 Optimization/Design Sensitivity - DRESP2 - Illegal Input to dopr3j When a DRESP2 response in a SOL 200 job intends to reference an existing DRESP1 entry but precedes with a DRESP2 flag, the job fails in DOPR3 with the fatal message "illegal input to subroutine DOPR3J". Avoidance: Specify the correct DRESP1 flag for the referenced entries. 1-17013601 2005 ADAMS/Flex - MNF grid point stress null for quadratic shell mid-side nodes The ADAMS/Flex modal neutral file's modal grid point stress/strain results are null for mid-side nodes of quadratic shell elements due to the fact that nastran does not compute grid point stress results for mid-side nodes of quad8 and tria6 elements. The ADAMS/Flex element face information for elements of these types should contain only the corner grid data and not the mid-side nodes. 1-17055508 2005 Superelements - PARAM,METHCMRS - UFM 3032 In solution 103 if param,methcmrs references an EIGR set id, the job may fail with the message: *** USER FATAL MESSAGE 3032 (READ) UNABLE TO FIND SELECTED SET ( 2000) IN TABLE (EED ) IN SUBROUTINE (REIG). Avoidance: Insert the following DMAP alter: compile phase0 alter 'SEP2.*nGEOM1,GEOM2,GEOM3,GEOM4'(2) if ( seid=0 ) equivx dynamic/dynamics/-1 $ endalter 1-17064430 2005 Distributed Memory Parallal - User must specify F2 on EIGR entry If a dmp job only specifies ND on the EIGR entry using method LAN and the DOMAINSOLVER entry specifies the partopt=freq option the job may attempt to solve all frequencies on all processors. Avoidance: The user must select F2 on the eigr entry. 1-17071801 2005 Miscellaneous - INPUTT2 - OP2 files with matrices and tables may lead to UFM in INPUTT2 OP2 files with intermixed tables and matrices that were correctly read in MSC.Nastran V2004.0.6 fail in V2004.5. The problem is caused because code handling end of matrix condition did not properly accept all valid conditions. corrected inputt2 per jas. 1-17081504 2005 Submittal - node=machine does not work on NT The node=machine nastran submit line option cannot be used from NT to a dissimilar machine. 1-17104601 2005 SOL 600, SOL 700 - Windows Version 2004.5 not useable The switch to Intel Version 8 compiler in MSC.Nastran Version 2004.5 for Windows caused many problems in SOL 600 and SOL 700. Thus, this release should not be used for SOL 600 and 700 on Windows. 1-17148302 2005 Optimization/Design Sensitivity - DOPR1, PCOMP - Poor Message, Illegal input to DOPR1I A composite optimization job fails in DOPR1 with "Illegal Input to Subroutine DOPR1I" if the following two conditions are met: 1. The integer input with FID option is used to sepcify a designed laminate thickness or ply angle on a DVPREL1/2 entry and 2. The laminate thickness or ply angle that the FID represents is Not defined on a PCOMP entry. For example, only two laminates are defined on a PCOMP entry but the FID field on a DVPREL1 entry references the thickness for the third laminate. Avoidance: Only design the laminate thickness or ply angle on a DVPRELi entry that is defined on a PCOMP entry. 1-17177340 2005 Aeroelastic Analysis - Direct Enforced Motion, wrong results Solution 146 produces wrong results showing when direct enforced motion is used. The call to subDMAP SUPER3 with AULF is missing data block RGY (penultimate input data block). This may cause some grids to deflect incorrectly. Avoidance: PARAM,DDRMM,-1 will also avoid the data recovery error. 1-17194201 2005 ESE - UWM 4506, UIM 4507, subcase, TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 0.0 If a job incorrectly specifies SUBCASE1 with no space instead of SUBCASE 1, the subcase number is read as zero. If ESE output is requested, UWM 4506 and UIM 4507 may be issued indicating the total strain energy is zero. No warning message is given that the SUBCASE entry is in error. The ESE output shows TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 0.000000E+00 and no list of strain energies by element is output Avoidance: Correct the SUBCASE entry to leave a space between the word SUBCASE and the 1 1-17202601 2005 Acoustics - DAREA entries not converted to static loads if they reference fluid points Currently, DAREA entries are not converted into equivalent static load entries if they reference fluid grid points. 1-17203001 2005 Distributed Memory Parallel - MDACMS with ESE fails if PARAM,POST specified Parallel MDACMS with ESE request and PARAM,POST will fail since slave processes are not prevented from attempting to write to the output2 file. Solution is to modify the DMAP to call OUTPUT2 only on the master. (Alter can be generated on request.) 1-17210346 2005 Lama table not output2 with post,-2 lama table not output2 with param,post,-2 avoidance is to also use param,postext,yes. However, this writes more files. Also PVT0 is missing from op2 file. 1-17242803 2005 Post Processing - Incomplete XDB File The DBC/XDB object in the dictionary does not contain the correct control information, it contains the original object template when the create function completes. This may lead to an incomplete xdb file which may cause post processers to fail. This error has only been observed for one test file that contained 55 subcases. Avoidance: A possible avoidance is to change the block size of the xdb in the FMS section. 1-17252901 2005 External Superelements - UFM 1126, Datablock GOA already exists In Version 2004.5 an external superelement reduction run with ACMS results in the following fatal message: *** USER FATAL MESSAGE 1126 (GNFIST) DMAP MODULE UMERGE1 IS ATTEMPTING TO OUTPUT DATABLOCK 201 NAME = GOA , WHICH ALREADY EXISTS. Avoidance: Insert following DMAP alter: compile phase1b alter 'call segoa'(9,-1) delete /goa,,,, $ endalter 1-17280829 2005 Documentation/QRG - Release Guide, ASSIGN - Output2 Example 4 under the ASSIGN FMS statement is incorrect. The current example is as follow: assign op2 bigendian' ... assign op2='test_op2.12' unit=12 assign op2='test_op2.35' unit=35 form=formatted The op2 logical name is assigned to unit 12 and this unit number should not be changed on the assign statement. This is usually used for param,post-1 and param,post,-2. The example should be modified as follow: assign op2 bigendian ... assign op2='test_op2.12' assign output2='test_op2.35' unit=35 form=formatted 1-17280840 Superelement - SELR, method - SFM 9104 In a static supelement analysis run, if case commands METHOD=n and secset1 entries are included in the model, the job may fail with the following unclear messages: ^^^ USER FATAL MESSAGE 9104 (SELR) ^^^ THERE IS NO COUPLING BETWEEN INTERIOR POINTS OF THIS SUPERELEMENT AND ITS BOUNDARY POINTS. ^^^ USER ACTION: ADD SOME ELEMENTS CONNECTING THE INTERIOR AND BOUNDARY POINTS. Avoidance: Removing either the method command or the secset1 entries will avoid the error. Note that neither one of these entities are used in sol 101 so the error is very unlikely. 1-17282301 2005 File Management Section - DBLOCATE - SFM 1013 Three successive DBLOCATE commands, the first 2 with NOCOPY and the last one with the COPY option, results in the following fatal message: *** SYSTEM FATAL MESSAGE 1013 (GBKMGX) CANNOT FIND CORRECT CLUSTER POINTER RECORD BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGX , FILE INDEX = 0. STATUS = 0 Avoidance: Do not mix COPY and NOCOPY options. 1-17297801 2005 Distributed Memory Parallel - EXTSEOUT - SFM 3008 UTMCOR In MSC.Nastran 2004r3(2004.5) a dmp run with external superlements may fail with the message: *** SYSTEM FATAL MESSAGE 3008 (UTMCOR) MODULE = MDENZO INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ENZO2 PROGRAMMER INFORMATION: LOCATION KEY = READ IN P Avoidance: Run without dmp or apply the following alter: compile cmpmode alter 'call mdacms ' (,-1) $ if( nproc>0 ) putsys(nproc,231) $ alter 'if ( fdcmrrs', '' $ if ( fdcmrrs OR mdacms ) then $ alter 'paraml cmphixz', '' $ paraml cmphixz//'trai'/1/s,n,nozset $ 1-17297961 2005 Installation - FLEXlm installation not handled correctly on hpia64 The current 'mscsetup' script correctly accounts for the hpuxia64 being distinct from hpux, as far as Patran and Nastran installs are concerned, however, when installing a FLEXlm server, the scripts in the .../msc/bin directory (flexlm, lm*) are based off an older mscsetup that does NOT account for the distinction as such, running those scripts on an IA64 will still search for the default 'hpux' location, when the install actually created an 'hpuxia64' folder, and the script will fail 1-17303819 2005 DMAP/Matrix Methods - SMPYAD method ABA wrong results for complex matrices The SMPYAD module ABA method produces wrong results for complex matrices under the following conditions: 1. Spill (multiple passes) used. 2. Triple loop kernels used. Avoidance: Set sys129=1 to bypass the ABA method. 1-17303823 2005 Acoustics - METHOD(FLUID) - Missing output and wrong answers For acoustics, if a METHOD(fluid) entry is not present in the Case Control, the fluid eigensolution is not performed. This conflicts with design intent and Remark 3 under the METHOD command in the QRG. Avoidance: Specify a METHOD(FLUID) entry in Case Control. 1-17322311 2005 Buckling Analysis - multiple buckling subcases - UWM 73, Wrong answers In buckling analysis UWM 73 will be issued if there are more than two buckling subcases in the following solution sequence: 1. SOL 105 with scr=no 2. SOL 200 with ANALYSIS=BUCK regardless of scr keyword Avoidance: Insert the following DMAP alter: compile super3 alter 'DBVIEW qGFs=qG' DBVIEW UGFb=UG WHERE (( (seid>0 and peid>0 and spc=* and mpc=* and suport=* and bmeth=* and mtemp=* and p2g=* and k2gg=* and m2gg=*) or (seid=0 and peid=0 and spc=cspc and mpc=cmpc and suport=csuport and bmeth=cmeth1 and p2g=cp2g and k2gg=ck2gg and m2gg=cm2gg and mtemp=cmtemp) )) $ DBVIEW qGFb=qG WHERE (( (seid>0 and peid>0 and spc=* and mpc=* and suport=* and bmeth=* and mtemp=* and p2g=* and k2gg=* and m2gg=*) or (seid=0 and peid=0 and spc=cspc and mpc=cmpc and suport=csuport and bmeth=cmeth1 and p2g=cp2g and k2gg=ck2gg and m2gg=cm2gg and mtemp=cmtemp) )) $ alter 'SEP4 CASESEP4' else if ( app1='bkl1' ) then $ SEP4 CASESEP4,PCDB,EMAP,XYCDB,UGFb,PUGF,QGFb,mmcdb/ DRLIST/ APP4/'SEID'/S,N,NODRALL/S,N,SEID0/S,N,NOUPL/CNTL $ alter 'DBVIEW UGs=UG ' DBVIEW UGb=UG WHERE (( (seid>0 and peid>0 and spc=* and mpc=* and suport=* and bmeth=* and mtemp=* and p2g=* and k2gg=* and m2gg=*) or (seid=0 and peid=0 and spc=cspc and mpc=cmpc and suport=csuport and bmeth=cmeth1 and p2g=cp2g and k2gg=ck2gg and m2gg=cm2gg and mtemp=cmtemp) )) $ alter 'NUGDWN=(NOGO=-1' else if ( app1='bkl1' ) then $ SEDR EMAPX,CASEX,PCDB,DRLIST,XYCDB,SLT,ETT, MAPSF,UGb,BGPDTSD,GDNTAB,,/ ULS,CASEDR,PCDBDR,XYCDBDR,,/ APP4/SEID/S,N,NOUP/S,N,NOSRT1//S,N,NOOUT/ S,N,NOPLOT/S,N,NOXYPLOT/'SEID'/NCUL $ NUGDWN=(NOGO=-1 AND SEID<>0) $ must appear right after sedr endalter 1-17370601 2005 Optimization/Design Sensitivity - MFREQ, DFREQ, scr=no - Wrong Answers Direct or modal frequency response optimization may produce different optimization results if scr=no is used. Avoidance : Use scr=yes A related problem has surfaced with a external se deck from GM. The client deck itself is not available. However, the problem can be reproduced with d200pe3 with resvec=no. Adding adelufx to the dbdelete fxied the problem. Or, scr=yes also does the trick. 1-17373002 2005 Enforced Motion - SPCD - Enforced motion in a subset of subcases results in SFM 5423. If a frequency response job with more than one subcase has an SPCD enforced motion specified in only a subset of the subcases, the job terminates with SYSTEM FATAL MESSAGE (SFM) 5423 in the MPYAD module. Avoidance: If a frequency response job with more than one subcase is to have SPCD enforced motion specified in only a subset of the subcases, define VERY SMALL enforced motion in those subcases where such enforced motion is not really needed. 1-17373523 2005 Elements - PBEAML, MAT8 - Poor Message, Missing UFM 2113 If a pbeaml entry incorrectly references a MAT8 entry a "Fatal Error" without any further information will be output in V2004.0.6. In V2001.0.9 the same job produces a better message- *** USER FATAL MESSAGE 2113 (EMG) ELEMENT 1 REFERENCED MATID 1 WHICH CANNOT BE USED TO OBTAIN REQUIRED PROPERTIES. Avoidance: Other than correcting the input there is no avoidance. 1-17378501 2005 Nonlinear Analysis - PCOMP, TEMP(MAT) - Wrong Answers Unsymmetric composite layups with temperature-dependent materials may produce wrong answers in nonlinear analysis. Avoidance: There is no avoidance. 1-17386627 2005 Miscellaneous - SWM 6498 UFM (1) - Unclear message Corrected usrmsg.F to increase dimension of array from 9 to 10. (cdp 8/24/04) If degrees of freedom are defined illegally in a set (e.g., constraining an dependent dof), the job should fail with a message similar to the following messages: USER FATAL MESSAGE 2101 (GP4) +165 GRID POINT 530 COMPONENT 1 ILLEGALLY DEFINED IN SETS UM US However, in v2004.5, the job may fail with the following unclear messages Windows machine. *** SYSTEM WARNING MESSAGE 6498 (MsgGen) Message number was not found. PROGRAMMER INFORMATION: Check call to MSGPOP from GP4 with message number 538976288.0. Severity is 'USER FATAL MESSAGE' (1) %1: ' 530' %2: ' 1' %3: ' UM' %4: ' US' %5: ' ' %6: ' ' %7: ' ' %8: ' ' %9: ' ' %10: '' Avoidance: Correct the offending entry 1-17395103 2005 DMAP - MPYAD - incorrect data in UFM 5423 If the MPYAD module issues SFM 5423, the message may contain an incorrect data block name specified in a prior execution of MPYAD. For example, in the following DMAP: MATGEN ,/A/4/4/3 $ MATGEN ,/B/4/3/4 $ MATGEN ,/C/4/3/3 $ MPYAD A,B,C/D $ MPYAD A,B, /E/1 $ the 1st multiply runs OK but the 2nd mpyad fails and references the C matrix in the first mpyad. SYSTEM FATAL MESSAGE 5423 (DMPYAD) ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES Avoidance: There is no avoidance. 1-17417801 2005 Complex Eigenvalue - CEAD - Eigenvector spill logic in complex Lanczos causes hard crash. The multishift logic in the complex branch of the complex Lanczos method suffers a hard crash when the eigenvectors spill. Avoidance: The avoidance is to increase memory or to use the old single vector complex Lanczos. 1-17432001 2005 Optimization/Design Sensitivity - DRSPAN, DOPR3 - SFM 4276 When an optimization job includes both DRSPAN subcases mixed with non-DRSPAN subcases, the job may fail with SFM 4276 with error code = 3001 in the DOPR3 module. Avoidance: Rearrange the subcases so that the non-DRSPAN subcases are put at the top of the DRSPAN subcases. 1-17446504 2005 Rotordynamics - TRD1 - Traceback in TRD1 Rotordynamcis may fail in trd1 with a traceback. Avoidance: There is no avoidance. 1-17446507 2005 Rotordynamics - ROTORG, NLTRD2, CDAMPi, CVISCi, UNBALNC - Wrong Answers, Damping Ignored The rotor damping (CDAMPi, CVISCi) should add instability to transient response but damping is effectively not included. 1-17464201 2005 Nonlinear (SOL 106) - SFM 1014 - Solution 106 may fail with the following message: *** SYSTEM FATAL MESSAGE 1014 (GBKMGX) ERROR IN LOOKING UP CLUSTER NUMBER BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGX , FILE INDEX = 0. STATUS = 0 1-17482902 2005 Submittal - libpath set incorrectly when exe= specified with no directory Fixed in round 16. When using nastran script with exe= keyword to override the default executable, if the pathname of the executable does not have any directory compoment specified, then the libpath will not include the correct directory path. 1-17557511 2004.5 Nonlinear Analysis - CTETRA, MATT - Temperature-dependent material , sdr2 - job aborts In version 2004, if a nonlinear model contains tetra elements and temperature-dependent material properties are used, then the job may abort in SDR2 with the following unclear messages: MAIN: The FPU has been reset after floating point exception. MAIN: For reference, A(MAINAL) = 73C3B0, This error is fixed in Version 2004.5. Avoidance: Removing either the temperature-dependent material or replacing the tetra elements with hexa elements avoids this error. 1-17575313 2004.0.7 File Management Section - ASSIGN, INPUTT2 - SFM 6551 An FMS ASSIGN statement to UNIT=300 may fail on linux with the message: *** SYSTEM FATAL MESSAGE 6551 (INPTX2) A READ ERROR WAS DETECTED ON UNIT 300 DURING BINARY INPUTT2 PROCESSING PROGRAMMER INFORMATION: 1. A KEY VALUE WAS NOT BEING READ 2. THE LAST KEY VALUE READ: 2 3. THE FORTRAN READ IOSTAT CODE IS 154 Avoidance: Use a different unit number 1-17584301 2005 Performance - Poor performance for unsymmetric FBS for uncoupled matrices The performance for unsymmetric FBS is poor when the matrices have very little coupling (i.e. very sparse RHS matrix). In this case, the code should select the special "MCE1-only" sparse FBS. 1-17604301 2005 Data Recovery - GPFORCE, SUBCOM - Missing output If GPFORCE is requested in a SUBCOM then "F-OF-SPC" may not be printed in the SUBCOM's grid point force balance output. Avoidance: Insert the following alter: COMPILE sedrcvr alter 'GPFDR CASEDR,UG,KELMX'(,-1) paraml qmg//'null'////s,n,nullqmg $ if ( nullqmg=-1 ) delete /qmg,,,, $ endalter 1-17620501 2005 Superelements/Frequency Response - DELAY, SPCD - SFM 4276 in DPD (in SEDLG subdmap) A SOL 111 superelement job employing DELAY data and SPCD enforced motion fails with SYSTEM FATAL MESSAGE 4276 (ERROR CODE 3021) on a call to the DPD module in the SEDLG subdmap during data recovery. 1-17647514 2005 Postprocessing - PARAM,POST,0 - GRIDX is not present in XDB for Collector Superelements THE GRIDX datablock is not present in the XDB when the superelement is a collector containing no elements. 1-17663601 2005 External Superelements - EXTSEOU, PSDF - Missing PSDF output in assembly run. When using the EXTSEOUT feature, the assembly run does not output the PSDF responses for velocities and accelerations for the external superelement. Avoidance: Insert the following DMAP alter in the assembly run: compile sedrcvr alter 'Multiply OTM' splitdva=-1 $ endalter 1-17664010 2005 Inertia Relief - param,inrel,-2 - Model with no mass does not issue UFM A model with no mass defined may only issue a max ratio warning message and continue when using param,inrel,-2. The job should issue a meaningful fatal message. 1-17670502 2005 Size Limitation - DCMP - Floating point exception error in DCMP for large models This should be fixed now. PJS 8/27/04 In MSC.Nastran Version 2004.5, large models may fail in decomp on 64 bit aix systems (AIX 5 and above). SIGTRAP - Trace trap Signal generated for floating-point exception: FP invalid operation. 1-17727701 2005 Dynamics - DELAY - SFM 3002 (DPD), Specifying DELAY for dof with no excitation Specifying DELAY data for DOFs without any excitation may lead to SYSTEM FATAL MESSAGE 3002 on a call to SKPREC in the DPD module. 1-17733738 Documentation/QRG - PBEND - Remark 3, FSI=1, Wrong Description Remark 3 under the PBEND description in the QRG incorrectly and incompletely describes the equation for FSI=1. It should read as follows: The flexibility factor is set to unity. The stress intensification factor in plane 2 using the general or alternate format is set to unity and for plane 1 it is set as follows: [equation] where r-elem is C1, D1, E1 or F1 of the stress points. If any of these values are exactly zero, then S1 is set to unity. 1-17766002 Documentation/Case Control - SET - Possible Traceback in sdr2c Depending on the use the SET Case Control command may contain a list of integers or a list of real numbers. However, there is no application where the list would contain both integers and real numbers. MSC.Nastran does not know the intent of the set until it is referenced. If a set contains integers when it should contain real numbers or vice versa, the nastran may issue a traceback. A traceback has been encountered in sdr2c but other routines are possible. 1-17776102 2005 Performance - Krylov performance may suffer due to DOF-based ordering The Krylov solver uses CFACTR to do the decomp for frequency response. This path to decomp uses degree-of-freedom based ordering. It should call CFACTR2 instead which uses grid based ordering. 1-17777901 2005 Performance - FASTFR check in GMA not correct If any structural matrices are missing, for example there are no fluid elements, the check in GMA to determine if FASTFR can be used is not correct. This may lead to slower run times. 1-17790001 2005 SOL 600 - Temperature Loading with offs gives wrong results For SOL 600 an option has been added to apply thermal loading at the original node, the offset node or both. This is activated by a new parameters in Nastran 2005 named marcofft and moffcore. The defaults for these new parameters cause the temperature loading to be applied at both nodes. Models now gets the same thermal strains using SOL 600 and 106. 1-17818401 2005 Elements - CBAR, CBEAM - UFM 2026 when BGG, BGE, or BEE is specified for OFFT UFM 2026 indicating illegal geometry is generated for CBAR/CBEAM elements when the orientation vector for the element is defined using the reference grid point (G0) option and the OFFT (field 9) value specifies BASIC (Bxx codes) for the orientation vector. Avoidance: Specify GLOBAL (Gxx) code for the orientation vector. 1-17835201 2005 Buckling - Multiple buckling subcase - SFM 3002 in GPSP Solution 105, buckling, may fail in MSC.Nastran 2004 with SYSTEM FATAL MESSAGE 3002 in the GPSP module if multiple buckling subcases exist. 1-17845802 2005 Rotordynamics - LOAD, RFORCE - Wrong Answers In a static analysis with rotors, the gyroscopic moments may be missing from the load vecotr if the LOAD Case Control Command references a LOAD Bulk Data Entry. Avoidance: The LOAD Case Control Command should reference the RFORCE Bulk Data Entry directly without using the LOAD Bulk Data Entry. 1-17867401 2005 Acoustics - param,panelmp - Panel grid Mode Participation Factor output incorrect Structure Mode Participation Factor output for panel grid points is incorrect if any fluid grid point id is less than the largest id of the structural grid points in the problem. All other MPF output is accurate. Avoidance: Make sure that all fluid points have IDs greater than the largest ID of the structure grid points. 1-17889001 2005 Rigid Elements - PARAM,AUTOMSET,YES fails with multiple boundary conditions or SOL105 Runs with PARAM,AUTOMSET,YES could fail in SOL 105 or with multiple BC with UFM 1126 (GNFIST) (matmod attempting to output GM which already exists). Avoidance: compile sekr0 alter 'xmce1',''(,1) TYPE PARM,NDDL,CHAR8,Y,automset $ IF ( NOGM=-1 or automset='yes' ) then $ if ( automset='yes' ) delete /gm,,,, $ call xmce1 USET1,RMG1,KGG/GM,nuset/rsonly $ dbstatus nuset//s,n,nonuset $ IF ( getsys(np,400)<>0 and nonuset>0 ) equivx nUSET/uset1/always $ endif $