MD Nastran/MSC.Nastran Current Error ListCurrent Update: February 12, 2009 --------------------------------------This section includes a description of all known errors and generallimitations in all releases of MSC.Nastran and MD NastranThe field next to the error number indicates the version that the error is corrected. The "versionis the version on the f06 title page". Recent versions are sometimes referred to by the CD id as follows:MSC.Nastran 2005R3 = 2005.5.0MSC.Nastran 2005R3b = 20005.5.2MD Nastran R1 = 2006.0.0MD Nastran R2 = 2007.0.0MSC.Nastran 2007r1 = 2007.0.0MD Nastran R2.1 = 2007.1.0MD Nastran R3 = 2008.0.0Note that intermediate patches (point releases) may be found at:http://www.mscsoftware.com/support/software_updates/"GL" in this field stands for a General Limitation which indicates a fix is not planned.Continuous updates to the error list are available to MSC.Nastran clients on the MSC web page at http://www.mscsoftware.com. The site may be located by clicking on "Services" and "Support".Major CapabilitiesA list of major capabilities is provided to assist the analyst in choosing key-words to search for to locate error that may impact their current project.Error DescriptionEach error has a heading with as many as three entries. The firstentry identifies the major capability affected and is also listed inthe major capabilities index. The second entry identifies either thename of the module in which an abnormal exit occurs or the card typeaffected if computed results are not satisfactory. (For abnormalexits, the last module name that appears in the Performance SummaryTable is usually the module where the exit occurs.) The third entrygives the symptoms of the error, such as, the MSC.Nastran system oruser message number printed just prior to termination or a descriptionof a "machine-dependent error". Other symptoms might be missingoutput or wrong answers. Error reports are updated when more facts orbetter avoidance techniques become known.Knowledge BaseThe error list may be queried through a relational database at:http://www.mscsoftware.com/products/nastran_support.cfmA list of the major categories follows:Accounting Acoustic Analysis Aeroelastic Analysis Authorization Axisymmetric Fluid Elements Beam LibraryBuckling Analysis Buckling & Differential StiffnessCase Control Complex Eigenvalues Component Mode SynthesisComposites Cyclic SymmetryDBC/TRANS/ACCESSDMAPDatabaseDesign SensitivityDocumentation Dynamic ReductionDynamic Response AnalysisEigenvalue AnalysisElement Strain EnergyElementsEstimate ExecutiveExecutive LimitsExterior AcousticsExternal SuperelementsFile Management SectionFrequency ResponseFrequency Response and Random AnalysisGap ConstraintsGeometric NonlinearityGrid Point ForceGrid Point StressGrid Point Stress DiscontinuitiesHeat Transfer AnalysisHydroelastic AnalysisHyperelastic Nonlinear AnalysisInertia ReliefInstallationInterface ElementsIterative SolverLimitation on Problem SizeLoadsMSC/ACCESSMSGMESH, MSGSTRESS, MSGVIEWMaterial Nonlinear AnalysisMaterialsMatrix MethodsMethod SelectionMiscellaneousModal AugmentationNonlinear AnalysisNonlinear Eigenvalue AnalysisNonlinear Slide-Line AnalysisNonlinear Static AnalysisNonlinear Superelement AnalysisNonlinear Transient AnalysisNonlinear Transient Heat TransferOld Design SensitivityOnline Documentation Optimization/Design SensitivityP-Elements Parallel PerformancePlottingPostprocessingResponse SpectraRestarts Rigid Elements SSSALTERSSecuritySequencerSingle Point ConstraintsSOL 400 (Advanced Nonlinear)SOL 600 (Implicit Nonlinear - marc solver)SOL 700 (Explicit Nonlinear)Static Aeroelastic Analysis Static AnalysisSubmittal Superelements Thermal Stress Analysis Timing Estimate TopologyTransient Nonlinear Analysis Transient Response Analysis UtilitiesVirtual Mass399 70.5 Eigenvalue Analysis - CEAD, QRG - Unexpected NormalizationComplex eigenvalue analysis with the inverse power method of eigenvalue extraction will always normalize to MAX. POINT normalization requests are ignored. The Version 70.5 Quick Reference Guide has been updated to indicate that point normalization is only available for the det method.785 69 MSGMESH, MSGSTRESS, MSGVIEW - MSGMESH, DIAG 29 - Infinite CPU LoopIf MSGMESH is used with the link specification update feature, an infinite loop occurs. An infinite loop no longer occurs; UFM 53 will be issued indicating an incorrect format for the mesh entries.868 70.7 Miscellaneous - PUNCH - Incorrect FormatSTRESS(PUNCH) will not properly output the HEXA, PENTA, BEND, BEAM, TRIA6, or QUAD8 elements. Element margins of safety (ROD, CONROD, TUBE, and BAR elements) will produce poor punched formats if stress allowables are not given on the referenced MATi entries.890 GL Grid Point Force - GPFDR - UFM 3008 The open core requirement for the GPFDR module can be as large as (6 X BUFFSIZE + 14 X number of grids) if the grids use a nonrectangular displacement coordinate system. For problems in basic coordinates, the grid requirement drops to 8 X number of grids.1103 GL Dynamic Response - TRD, TRD1, FRRD, FRR - UFM 3005 If the MGIV method of real eigenvalue extraction computes modes for massless DOF with uncoupled stiffnessterms, the eigenvalue is large (1.E+35) as it should be, but the generalized stiffness is 0.0 (it should also be1.E+35). Null eigenvectors may be produced. An avoidance is to use PARAM,HFREQ or PARAM,LMODES to discard these bad modes in dynamics.1357 70.5 Aeroelastic Analysis - GI - Poor AccuracyThe linear splines used to connect structural and aerodynamic degrees of freedom are sensitive to modeling techniques, particularly on short-word machines. This included all machines except CRAY, CDC and NEC. It is good practice to have the spline axis coincide with the structural grid points, and to avoid discontinuities in the lines joining structural grid points by using separate splines on each side of the discontinuity.1575 69 Dynamic Response - VDR - No Output If an OUTPUT(XYPLOT) command is in case control, but there are no other XYPLOT commands, all printed output requests are ignored. An avoidance is to put in XYPLOT requests or remove the OUTPUT(XYPLOT) command.1679 66 Elements - QUAD4,TRIA3 - Wrong Answers When the MID4 option of the PSHELL card is used to simulate offset of the element centerline from the gridpoint plane, the element is somewhat too stiff. The error increases with the ratio of offset to element width. An avoidance is to use RBAR elements to model the offsets .1712 GL Frequency Response Analysis - RANDOM - SWM 3002, UWM 979If a non-existent point is referenced in an output request when there are multiple subcases, the RANDOM module will cease processing at that point and issue SYSTEM WARNING MESSAGE 3002. The following user warning message is now issued: 0*** USER WARNING MESSAGE 979, AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID 2000 -ACCE- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA BLOCK 1021738 66 Grid Point Stress - Preface - UFM 603 If the SURFACE Case Control card has a continuation card, and the first words that appear on this card areOUTPUT SYSTEM, the error occurs. An avoidance is to start the continuation with another word.1739 66 DMAP - DIAG 4 - Addressing ERROR If DIAG 4 is used on restart, the program may exit abnormally at the start of the run. The DIAG 4 cross reference output for Label Names will be incorrect if no labels exist in the DMAP, and theparameter section of the cross reference will not contain any parameters although parameters are present. An avoidance is to put a label in the DMAP.1758 GL Cyclic Symmetry - Restarts - Various In superelement static cyclic symmetry (SOL 81), some restart paths do not function well. The followingrestart paths have been demonstrated to work, using the indicated input and DMAP Alters. Other types ofrestarts can be made, using these techniques.A. Conventional Superelement Restarts. Use the same techniques applicable to noncyclic symmetry superelement analysis. 1. Exit during Phase I. 2. Structural Changes in a Superelement. 3. Load Change RestartB. Time Limit in a Harmonic Loop SET N = 0, residual only SEMG = N PARAM,RESDUAL,-1 (bulk data) Input all bulk data, or use PARAM,NODATA,-1 and delete all the bulk data except PARAM entries.C. Loads Change in One Tip Superelement, Same Number of Loading Conditions, Sam1759 69 Plotting - RF24D20, Superelement - Wrong Labels If SPC labels at grid points are requested for plotting ("GSPC") and resequencing is requested, the SPC labels are attached to the wrong components. An avoidance is to make a separate run for these plots without resequencing, and insert an EXIT after the RFAlter, or not request the SEKR operation in superelements.1765 70.5 Cyclic Symmetry - CYCLIC2 - UFM 3005, UFM 4319, UWM 4359There are two errors related to the use of the CYSUP Bulk Data entry when rotational symmetry is applied to a model with three or more segments.1. If the rigid body rotations are to be supported, but there exists no stiffness at the components specified on the CYSUP entry, then UFM 3005 may be issued. But, if components 4 and 5 (out-of-plane rotations) are then constrained by an SPCi card or a GRID card, in order to avoid UFM 3005, then UFM 4319 will be issued. For components 4 and 5, an avoidance of UFM 4319 is to define rotational springs to ground (e.g., CELAS2).For component 6 (in-plane rotation), an avoidance of UFM 3005 is to apply a single-point constraint (e.g., SPCi), which is contrary to Remark 1 under the CYSUP Bulk Data entry description. b. The specif1801 66 Plotting - PLOT - SFM 4276 If modern plate elements are present, and SHRINK or DIAG 34 are requested, the error may occur.1802 66 Miscellaneous - Preface - CPU Loop If the THRU range on an input card is larger than 131,071 for CDC/7600 and CYBER computers, or 8,388,608 forCRAY computers, the error may occur. It has been observed on a PLOAD2 card with a larger range. (Cyber,CDC7600,CRAY only) An avoidance is to split the THRU range into smaller sets, so that none exceeds the limit.1803 66 Elements - PQUAD4 - UFM 2010 If both PQUAD4 and PSHELL (and/or PCOMP) cards exist in the same deck, the misleading message referencesPSHELL cards. The PQUAD4 card is obsolete, and is removed from current documentation. It should be replaced withthe PSHELL card. The PQUAD4 card will be deleted from the code on a future system. An avoidance is to replace PQUAD4 card with PSHELL cards wherever they exist as they cause various confusingerrors.1804 66 Superelements - SELA - Wrong Answers For large problems, if the first several upstream load vectors are null, the remaining upstream load vectorsmay be ignored. This can be detected with DIAG 20. An avoidance is to place a token load on all upstream superelements.1805 66 Elements - PCOMP - Wrong Answers For layered composite materials with an unsymmetric layup, the generated transverse shear matrix MID3 isincorrect.1806 66 Database - LOAD/UNLOAD - Wrong Answers If a database is unloaded to a sequential file using the DBMGR //3 command, then restored to a direct accessfile using the load command, any keywords stored in the database dictionary will be lost. Most keywords are onlyfor diagnostic use (i.e., "SEMGDONE"), and will cause no further errors. The one exception at present is thekeyword "NOSETRUE", which appears when all grid points are in the residual structure. This will cause the fatalmessage above on PARAM,NODATA or PARAM,DLOAD restarts. An avoidance is to use the following alter for this type of restart: ALTER 10 $ MSC/61B, AFTER DBMGR //11 SETVAL //V,N,NOSE/-1 $1807 66 Matrix Methods - FBS, Method 2 - Wrong Answers If a passive group appears within the first 20 columns of a matrix, some terms may be dropped. The error was first observed on a large static reduction. An avoidance is to block Method 2 by using the NASTRAN card entry FBSOPT=-1, when passive columns occur.1808 66 Database - DBSTORE - DBM 288 This error occurs when more than 32,768 GINO blocks are stored in a single database, and a store of anequivalenced file is attempted. (IBM only) An avoidance is to use several databases, none larger than 32,000 GINO blocks.1809 66 Heat Transfer - HBDY - Wrong Answers SOL 74 gives wrong answers for nonlinear HBDY types AREA3 and AREA4. An avoidance is to use the POINT option instead.1810 66 Elements - Midside Nodes - Wrong Answers The QUAD8, TRIA6, and HBDY elements use an incorrect average temperature for material properties when thenumber of active grid points is not the same for all elements of the same type. (Deleted midside grid points arenot active grid points; all connected grid points are active.) An avoidance is to delete the same number of nodes on all elements of the same type in the model.1811 69 Dynamic Response - SDR3 - UFM 4605 If DISP, VELO, or ACCE are requested for a set of grid points and the set is empty, USER FATAL MESSAGE 4605 occurs. An avoidance is to remove output requests for empty sets.1812 66 Miscellaneous - Multiple Runs - ITRENT 1111 If two or more MSC/NASTRAN executions are made in the same job, the error may occur. (Univac only) An avoidance is to submit each run as a separate job.1813 Response Spectra - PARAM,RSPECTRA,0 - Wrong AnswersThe response spectra option provided in transient analysis gives wrong answers for acceleration spectra at high frequencies. The peak accelerations for high frequency oscillators will not match the results of a transient analysis where a stiff spring and small mass have been attached to the structure to directly represent the oscillator. The displacement and velocity from the response spectra results will match those of the oscillator represented with spring and mass.Avoidance: The user should set the value of delta t on the TSTEP input such that 10 time steps occur during one cycle of oscillation for the highest frequency of interest.1814 66 Matrix Methods - MPYAD - Overflow If incompatible matrices are input to the MPYAD module, and one is of form 3, an unclear diagnostic results. A good practice is not to input form 3 matrices to MPYAD, as this capability will be removed in a futuresystem. The form 3 matrix [A] can be changed to form 6 by the following steps:ADD A, /A6 $ ADD WILL GENERATE PROPER MATRIXEQUIV A6,A/ALWAYS $ A6 REPLACES A1815 66 Dynamic Response - XYPUNCH - Missing Output The PCHRESP parameter described on p. 4.3-23 (2/15/82) of the MSC/NASTRAN User's Manual is not implemented.The function it was to perform (punch TABLED1 cards based on output data) can be performed with a DMAP Alter.Delete the XYTRAN module statements, and replace them with an identical statement except for the sixth parameter.Set it to S,Y,PCHRESP=0. (MSC/62 only)1816 66 Material Nonlinearity - SOL 66 - Wrong Answers If the large displacement option is used, and more than one rotation is enforced at a grid point with SPCDcards, the transformations are incorrect when increments are specified on the NLPARM card. An avoidance is to use separate subcases, each with a single increment, rather than many increments on asingle subcase. (MSC/62 only)1817 66 Transient Response - TRD1 - UFM 3050 If an IC card is selected in case control in SOL 31, which is illegal, the wrong fatal message ("insufficienttime") is printed. The correct text can be found under UFM 3051, listed in Section 6 of the U.M.1819 66 Elements - EMG - EMGPOM If HEX8 and HEX20 elements are used with other elements, and there is insufficient memory available, uncleardiagnostics may result. (IBM, Cyber, CDC/7600, CRAY, Univac only) An avoidance is to request more memory.1820 66 Database - DBSTORE - SFM 4167 The maximum number of database dictionary entries is influenced by the fourth input parameter for the DBMGRcommand when creating the database. The default value will almost always result in more than one GINO block beingused for the dictionary. If the dictionary has only one block, the database will be unusable. (Univac only) An avoidance is to insure that the dictionary is assigned more than one block. This can be determined fromSIM 4162, under the "WRITTEN" entry. This number should be greater than 1 when the database is created. If it isnot, increase the fourth input parameter to at least twice the value printed under the "NUMBER OF ENTRIES -MAXIMUM" for SIM 4162.1821 66 Superelements - Documentation - Wrong Answers The DMAP Alter described in the Application Note of January 1982 titled "Inertia Relief in SuperelementAnalysis" has a typographical error that causes inertia loads of the wrong sign. The second to last statement onpage 7 should be changed from SOLVE QRR,QR/CRX/ $ etc. to SOLVE QRR,QR/CRX//-1 $ Update pages for the application note will be delivered with the next newsletter.1822 66 Material Nonlinearity - MID3 - Wrong Answers In SOL 66, the values output for transverse shear forces for the QUAD4 and TRIA3 elements are incorrect ifMID3 (field 7 on the PSHELL card) is nonzero. An avoidance is to leave MID3 blank.1823 66 Miscellaneous - 1VARY - UFM, CARD TO VARY NOT FOUND Multiple 1VARY cards for the same type of data card may not sort correctly.1824 66 Matrix Routines - Method 3 - Various GINO Messages If Method 3 matrix multiplication is selected, and there is not sufficient memory available, various systemerrors may occur. The method selected can be determined by DIAG 19. Avoidances are to increase memory, or block Method 3.1825 66 Elements - Punched Output - Extra Output If output is requested in punched format, elements whose printed formats include more than one element perline will also print the last few elements, if they do not fill the line.1826 69 Cyclic Symmetry - SOL 77 - Parameter Print If illegal loads are requested in buckling analysis using cyclic symmetry, the program branches from theCYCLIC1 module to the PRTPARM module, then prints all parameters. This condition can be detected by noting that parameter GEOM3C has the value minus one. One such case was observed when GRAV entries were selected. This user error now results in a meaningful fatal message:0*** USER FATAL MESSAGE 4342, THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALYSIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE.An avoidance is to check the load entry types against the limitations described in Section 3.2 of theApplication Manual. 1827 66 Grid Point Stress - Branched Surface - Wrong Answers When requesting stresses for a surface with branches using geometric interpolation without a value fortolerance, some stresses at branch points may be incorrect. An avoidance is to use the BRANCH option.1828 66 Heat Transfer - CFTUBE - Wrong Answers If the CFTUBE is used in SOLs 24, 61, or 62, which is illegal, SOL 24 produces wrong answers, and the othersfatal error message GETSTB ERROR CODE 1604 or some equivalent message in the SSG3 module. CFTUBE elements are supported only in SOL 74.1829 66 Database - DBMGR, DBSTORE - IO6600 F.E. 1203 Any database file longer than 262, 143 PRUs may fail with this error on restart. An avoidance is to restrict all database files to be under this size. The size of a database is specified inGINO blocks. A good approximation of the maximum allowable number is one million/SYSBUF. (SYSBUF is the size ofthe GINO buffer, which has a default of 1792.) Thus with default buffer size, limit database files to about 8900blocks. (CDC/Cyber running under NOS only.)1830 66 Aeroelastic Analysis - FA1 - Wrong Answers The ATEIG subroutine for eigenvalue solution has a limit of 30 iterations. If convergence is not achieved,the subroutine continues with intermediate results without giving a warning message. This yields incorrecteigenvalues for that condition. This has been detected when implausible real eigenvalues were produced whencomplex eigenvalues were expected.1831 66 Superelements - UMERGE - SFM 3007 In SOL 62, if a data recovery restart is made while performing no Phase I operations, the error will occur. An avoidance is to add PARAM,NORSET,-1 above the subcase level.1832 66 Static Analysis - RF24D13B - SFM 4275 The error occurs when the RF Alter is used for restarts where only output requests are changed, but notloading conditions. The RF Alter should not be used for this condition. A standard restart may be used.1833 66 Material Nonlinearity - SOL 66 - UFM 1105 If CHKPNT YES appears in the Executive Deck, the error may occur at random places. If checkpointing is required, use the alter:ALTER 1 $PARAM //DIAGOFF//47 $ In general, it is more efficient to recover the input data from the database rather than use checkpointing.1834 66 Elements - ROD,HEXA - Wrong Answers In SOLS. 64, 66, and 99 the following errors occur: A. ROD elements give wrong answers if they have torsion properties (J>0.), and the element changes direction,even slightly, due to large deflection effects. B. HEXA elements give wrong answers when two of the axes X,Y, or Z (see U.M. p. 2.4-70) are of nearly equallength (that is, the element has almost square faces) and are not perpendicular. (Part B fixed in Version 62A)1835 66 Plotting - XYPLOT - Poor Efficiency If a plot is made of a constant function, such that the maximum and minimum y values are the same, theautomatic scaling algorithm may converge very slowly. This problem has been observed only on CYBER computers,where it appeared to be a CP loop. An avoidance is to set one of the scales manually with the plotting commands YMIN=0.0; YTMIN=0.0; YBMIN=0.0.1836 66 Restarts - Preface - IO66RD F.E. 314 For CYBER computers using the SCOPE 3.4 operating system, the error will occur if the buffer size is greaterthan 512 words, and the NPTP is sent directly to TAPE. An avoidance is to use the "L" parameter on the "REQUEST, NPTP..." card.1837 66 Executive - SOL 76 - SFM 14 All of the solution sequences will compile in the recommended default region of 200K octal except SOL 76. Itwill compile with an RFL of 205K octal. (CYBER only)1839 66 Heat Transfer - SPCD - Wrong Answers If an enforced temperature is input on SPC or SPCD cards in SOL 74, wrong answers result. An avoidance is to place the degree of freedom on a SPC1 card, and set its value with a TEMP Bulk Data card.1840 66 Dynamic Response - OLOADs - Missing Output If plots or print of OLOADs are requested in SOLs 70-72, 75, or 76, and there are no extra points, the erroroccurs. An avoidance is to place the following alter before the DMAP statement DBSTORE PGD, etc. For SOL 72, forexample, the alter is:ALTER 974 $ MSC/62EQUIV PP, PGD/NOUE $1841 66 Matrix Methods - DECOMP - LOGIC ERROR 582 For unsymmetric decomposition with spill, the error may occur. (CYBER only) Changes in region size sometime eliminates the problem.1842 66 Sequencing - SEQP - Various System Errors If the resequencing module spills in the SEQMR subroutine, various system errors occur. (CRAY, VAX, UNIVAConly). Avoidances are to: A. Increase the memory request, or B. Use PARAM, MPCX, -1.1843 66 Elements - BEND - Wrong Answers The BEND element produces incorrect element forces and stresses when thermal loads are applied to them.1844 66 Elements - PCOMP - Wrong Answers The interlaminate shear stresses are incorrect for laminae that have nonzero orientations.1845 69 Virtual Mass - XYPLOT - Missing Plot Output XYPLOT requests for MPRES output are ignored. An avoidance for SOL 31 is:ALTER 548 $ AFTER MDATA MSC/61, MSC/62SDR3 OEP,,,,,/OEP2,,,,,/ $XYTRAN XYCDB,,,,OEP2,/XYPPLOT/SOLTYPE/DSET/S,N,PFILE/ S,N,CARDNO/S,N,NOPLOT $ COND NOPPLOT,NOPLOT $XYPLOT XYPPLOT // $LABEL NOPPLOT $ Other solution sequences may also use this alter if appropriate changes are made to the alter line number. This error is fixed in the sss solution sequences; however the xyplot request is pres not mpres.1846 69 Transient Nonlinear Analysis - XYPLOT - Missing Plot OutputIn SOL 99, an XYPLOT requests may be ignored when there is no printed output requested.An avoidance is to request at least one grid point for printed output.1847 66 Material Nonlinearity - TABLES1 - Wrong Answers In solutions 66 and 99, if the stress-strain curve does not pass through the origin for FORM=1 the data isaccepted, producing unrealistic answers. On future systems, such input will cause a fatal error.1848 66 Superelements - SEP2 - UFM 4222 If SEUSETi cards reference interior points, the error occurs. They may be applied to exterior points. Infuture systems they may also be applied to interior points.1849 66 Superelements - SEUSET - UFM 315 The card description of this card in Section 2.4 of the User's Manual has fields 2 and 3 interchanged. Thecorrect format is:SEUSET, (SEID), (SNAME), ...1850 66 Cyclic Symmetry - GPFDR - UWM 2342,2354 In SOL's 81 through 83, the message results when GPF0RCE or ESE output is requested. An avoidance is to delete the DMAP line number for the GPFDR module, and change the APP parameter to APP1.For example,ALTER 822,822 $ SOL 81, MSC/62GPFDR CASEDR,UGVS,KELM,KDICT,ECTS,EQEXINS,GPECT,PG,QGS,BGPDTS,SILS,CSTMS,VELEM/ONRGY1,OGPFB1/APP1/V,Y, TINY $1851 66 Matrix Routines - MPYTIM - Integer divide by zero If large problems are run with small memory requests, the error may occur. An avoidance is to increase the memory request.1852 66 Restart - Dynamics - No Damping If a restart is made from SOL 24 to a dynamics solution sequence, any damping cards present in SOL 24 (i.e.CVISC) may be ignored. An avoidance is to delete one damping card on restart and reinsert it.1853 66 Executive - 3380 Disk Drives - Various System Errors (21OCT82) Users may not run any version of MSC/NASTRAN prior to MSC/62 on an IBM configuration that references 3380 diskdrives. A variety of I/O related fatal messages may result from the earlier version's inability to computeblocksize correctly on these drives. The most likely messages are one or more of the SFM 4212 codes. Some usershave had limited success by using half-track blocking with Version 61B. However, use of Version 62 is therecommended procedure. Furthermore, users may not copy (using IBM utilities) a MSC/NASTRAN database existing onnon 3380 disks to a file usable by MSC/NASTRAN on a 3380 disk. (IBM only) This procedure may be accomplished however, by using a short MSC/NASTRAN DMAP sequence to read the existingfile from the non 3380 disk and then write a1854 66 Material Nonlinearity - EMG - SFM 3007 If a SOL 66 run restarts from a prior run which had no updates of the stiffness matrix, the recoveredstiffness matrix may be incorrect. An avoidance is to restart the run from the beginning.1855 66 Material Nonlinearity - Contour Plots - SFM 4276 In SOL 66, when contour plots are requested for both linear and nonlinear elements, SFM 4276 will occur.Also, if all elements are linear, SFM 3002 might occur. An avoidance is to make linear elements into nonlinear elements by setting the yield stress very high.1856 66 Superelements - Multiple File databa - Purge of Upstream database If PARAM, DBSET1 is set to a value greater than zero, the entire upstream database will be purged during theSEKR operation. An avoidance is to repair two database purge statements that are in error. For SOLUTION 61, the fixes are:ALTER 440,440 $ MSC/62DBMGR //5/MODEL/SEID/0/DBSET1//GO$ALTER 452,452 $DBMGR //5/MODEL/SEID/0/DBSET1//KTT$ The change involves inserting a "0" parameter before DBSET1, and reducing the number of slashes after DBSET1from three to two. Two similar statements will be found in all the superelement solution sequences, at differentline numbers. They can be found by use of DIAG 14, followed by a search for statements of the form:DBMGR //5... GO $, andDBMGR //5..... KTT $ This error does not affect superelement run1857 66 Miscellaneous - RF24D40 - Various Fatal Messages or Wrong Answers If a user-supplied DMAP loop is provided around this alter, and the FBS module is within this loop it willresult in various fatal messages or wrong answer after the first pass. An avoidance is to copy and modify the alter by inserting the following two DMAP statements; After the first ALTER statement insert: PARAM //STSR/V,N,SAVE74/74 $ Just after the third occurrence of the SDR2 module insert: PARAM //STSR/V,N,SAVE74/-74 $1858 66 Miscellaneous - Demand Runs - FATAL MESSAGE 202 If two or more MSC/NASTRAN executions are made in the same demand session, the error may occur. (Univac only) An avoidance is to free all MSC/NASTRAN files (i.e. PRIXX, and SECXX's) between executions in demand mode.1859 66 Miscellaneous - IBM - Compilation Errors The UTIL data set which is the third data set on the IBM deliverable tape was incorrectly blocked at 13030bytes. This is acceptable except for installations having only DASD devices which support shorter maximumblocksizes (i.e. 3340 devices). At these sites the UTIL data set, as issued, cannot be restored. The mostheavily used programs in the UTIL data set are DECKEDIT, NASTPLOT and TECKPLT. Of these, DECKEDIT and NASTPLOT areavailable in the NASTRAN data set which is the second file on the deliverable tape. TECKPLT is identical with theprogram as issued in Version 61 and could be obtained from that source. If any other programs are required fromthe UTIL data set, or any of the above solutions are unacceptable, please contact MSC. (IBM only) An avoidance, i1860 66 Material Nonlinearity - TA1 - Wrong Answers or Overflow In SOL 66 and 99, Orthotropic Materials defined by MAT2 or MAT9 do not work in SOL 66 or SOL 99 for any typeof elements.1861 66 Geometric Nonlinearity - EMA - Overflow In SOL 64, 66, or 99, if the static displacement vector provided to the second subcase for differentialstiffness calculations is null, the results of the second subcase may be implausibly large, or the EMA module mayfirst terminate due to overflow. An avoidance is to request loads in the first subcase that will produce a nonnull displacement vector.1863 66 Superelements - Dynamics - No Damping The Application Note of May 1981 describes a method for obtaining differential stiffness effects in dynamicanalysis by performing a static analysis in SOL 64, followed by a special restart into SOL 63, or SOL's 67 through72. At present, damping is not computed in SOL 64, and may not be computed on the restart run without erasing thedifferential stiffness matrix. The following alter will provide damping: Alter for damping in SOL 64 /61B or /62 ALTER 62,62 $ MSC/61B/62, SOL 64 EMG EST1,GCSTMS,GMPT,GDIT,GGEOM2,,,/ KELM1,KDICT1,MELM,MDICT,BELM,BDICT/ S,N,NOKGG=1/S,N,NOMGG=1/S,N,NOBGG=1/// V,Y,COUPMASS=-1 $ ALTER 68 $ EMA GPECT,BDICT,BELM,GBGPDT,GSILS, GCSTMS/BJJ, / $ DBSTORE BJJ//MODEL/0 $1864 66 Superelements - Documentation - H/SEA The following errors have been found in the Handbook for Superelement Analysis, for Version 61. 1. Appendix J, page 3 Deck SEH616A Add after "DBSTORE EQEXINS..." DBMGR //7/////-2/UGVS/ULV $ This statement is needed to provide the presence of ULV for the next run, Deck SEH617. Its absence causes thedata recovery run for the external superelement to terminate without producing output. 2. Appendix J, pages 4 and 5 Several decks use the DBMGR //3 and DBMGR //4 commands. They use the default values for the third parameter,used for "search control". The default value allows several blocks with the same name to appear in the data base,which can lead to baffling fatal errors or wrong answers. It is good practice to set the third parameter1865 66 Geometric Nonlinearity - SOL 66,99 - Wrong Answers If SOL 66 or 99 is used with only LGDISP, the beam element has incorrect stress recovery output, if I1 doesnot equal I2. Output (recovered) stresses are only affected, and the solution is still correct. An avoidance is to either: 1. Make a "Dummy" material nonlinear group (w/yield stress set to a high value) 2. Run only with I1 equal to I2.1866 66 Material Nonlinearity - SOL 66, 99 - Wrong Answers In SOL 66 or 99, a beam element with thermal loads and nonbasic coordinates used by its end grid points givesincorrect results. An avoidance is to use the basic coordinate system to define the beam element grid points.1867 69 Cyclic Symmetry - Restarts - Missing Modal Deformation Plots In SOL 48 restarts, requests for modal deformation plots are ignored unless the requests were also made in the cold start. The following alter is an avoidance: ALTER 197 $ MODTRL FCASEBK1 /////1// $1868 66 Grid Point Stress - Subcases - Wrong Answers When there are multiple subcases in a run and in a particular subcase there is a stress request but not a gridpoint stress request then the subsequent subcase grid point stress results will be wrong. This is a stressrecovery error only and does not effect the solution. An avoidance is to put grid point stress requests (even if for only one element) in every subcase.1869 69 Geometric Nonlinearity - SSG1 - GINO Fatal Message 3029 In SOL 64, if only GRAV Loading is being used, GINO Fatal 3029 will occur in Subcase 2. An avoidance is to include a dummy load.1870 66 Miscellaneous - Composite Element wi - Incorrect Resutlsts Thermal loading at grid points (using TEMP or TEMPD) gives wrong temperature gradients and correspondingincorrect results in composite elements. An avoidance is to apply TEMP loads directly to elements.1871 66 Cyclic Symmetry - Thermal Loads - Wrong Answers or UFM 4587 Temperature load cases, i.e., TEMP(LOAD)=j in SOL 81, combined with other types of loads will provideincorrect force and stress output because the thermal strains are not correctly handled. If temperature loadingonly is requested, then UFM 4587 will occur. This situation arises because the identification number of thetemperature load "j" is not included in the CASEDR data block output by the SEDR module. An avoidance is to utilize the following alter:ALTER 642 $ MSC/63$ALTER 653 $ MSC/62TABEDIT CASEDR, CONT,,,/A1 $EQUIV A1, CASEDR/ALWAYS $in the Executive Control Deck, and to include the following DTI cards in the Bulk Data Deck:DTI, CONT, 1, CR, [1] , DW, 7, 7, 1, DTI1+TI1, "j" ENDRECDTI, CONT, 2, ER, ENDREC The number in brackets, i1872 66 Matrix Methods - MPYAD - Mode Error 1 This error condition may occur when multiplying large matrices. It is further characterized by aborting witha "P address" between 36000 and 37400. The P address is printed out in the dump on the line that starts "P =").This error was reported to be fixed in Version 62A, in a prior report. Field usage of Versions 62A shows that thefix was not fully effective. (CYBER, CDC/7600 only) Avoidances are to: 1. RFL up or down by about half of the largest dimension of any input matrix. 2. Set the REAL parameter on the NASTRAN card to core size minus the largest dimension of any input matrix.Core size may be determined from DIAG 13. 3. Deselect Method 1 and Method 1T. This should be done locally using a DMAP Alter statement, rather than onthe NASTRAN c1873 66 Miscellaneous - PARM Field - Incorrect PARMs The PARM option provided in the PROC delivered with NASTRAN allows up to 100 characters of input, based oninherent JCL limits. (See Section 7.6.2.1 of the A.M.) Submitting more data results in JCL fatal error messages.MSC/NASTRAN will process less data than this, however, with the remaining data set to unpredictable values. Theequation for the limit of data properly processed by MSC/NASTRAN is 4S*7+(OTHERS)*4 NGMAXwhere NGMAX = NCON + NDVand NAVC = # of active and violated constraints considered by the DOT algorithm NASIPE = # of active side constraints NCON = # of retained constraints passed to the optimizer NDV = # of design variables Generally, DOT selects a small set of NCON for NAVC. In the case that encountered the failure, there were a large number of properties an4469 68 Data Recovery - DTI,INDTA - Composite Stress Sorting Composite ply results processing does not support the DTI,INDTA Bulk Data entry. Avoidance: The following DMAP statement needs to be modified in each applicable Unstructured Solution Sequence and in the subDMAP SEDRCVR as follows:(old)STRSORT ES1C,/OES1C/V,Y,NUMOUT1=-2/V,Y,BIGER1=0.0 $STRSORT EFIT,/OEFIT/V,Y,NUMOUT2=-2/V,Y,BIGER2=0.0 $(corrected)STRSORT ES1C,INDTA/OES1C/V,Y,NUMOUT1=-2/V,Y,BIGER1=0.0 $STRSORT EFIT,INDTA/OEFIT/V,Y,NUMOUT2=-2/V,Y,BIGER2=0.0 $Alternatively, the analyst may use the default ply sorting with parameters NUMOUT1,NUMOUT2,BIGER1, and BIGER2. This gives sorting on the ply stresses and strains.4476 Elements - PSOLID - UWM 5460If the standard isoparametric integration (ISOP=FULL) is desired for the CHEXA or CPENTA element with midside nodes, and the IN field is blank on the PSOLID entry, then MSC/NASTRAN assumes that the user wants to use bubble functions. "USER WARNING MESSAGE 5460, ILLEGAL OPTION ON PSOLID ID = ***, FOR BUBBLE FUNCTION. ONLY REDUCED INTEGRATION IS ALLOWED" is issued, and the run will proceed using reduced integration. The same warning message is issued for CTETRA elements if the IN field is blank even though bubble functions and reduced integration are not supported by this element. The run will continue with the default integration options.Avoidance: To perform standard isoparametric integration on CHEXA and CPENTA elements with midside nodes, IN must be set to 3 or THREE. To avoid4482 68 Miscellaneous - CONVEX Only - Unacceptable Input FilenamesMSC/NASTRAN on the CONVEX will not accept the following filenames:t.datat.datdat.datAvoidance: Do not use the above names.4484 67.5 Cyclic Symmetry - GPFORCE, GPFDR -SFM 3001, FILE 108 NOT IN FISTGrid point force output is not available in upstream superelements in cyclic symmetry statics (SOLs 81 and 114). A GPFORCE request results in the message "SYSTEM FATAL MESSAGE 3001 FILE 108 NOT IN FIST" being issued from the GPFDR Module. Avoidance: A DMAP avoidance is under investigation.4486 Nonlinear Analysis - Hyperelastic, PLSOLID, FORM=MIXED - No Convergence When a displacement coordinate system (CD) is specified on any of the grid entries connecting a HEXA hyperelastic (PLSOLID) element, results may either converge slowly or no convergence occurs when FORM=MIXED is selected. Avoidance: Use the default FORM=ISOP.4491 70 DMAP - DRMS1 - SFM 4276, EC 7777The message "SYSTEM FATAL MESSAGE 4276 ERROR CODE 7777" may occur during data recovery of eigenvalues analysis in the DRMS1 module. This error is due to numerical underflow or overflow and is highly machine dependent. This error has only been observed on the DEC VAX(VMS) release of MSC/NASTRAN. Avoidance: Run the job on another machine.4494 GL Acoustic Analysis - Wrong Answers - SFM 5401When the surfaces of the fluid cavity are connected to a structural surface containing two or more distinct elements (i.e. the fluid is interfacing with HEXA elements on one surface and QUAD elements on the other surface ) then wrong answers may be produced for the FL./STR. INTERFACE CHECK and/or SFM 5401 may occur.Avoidance : This is a general limitation of MSC/NASTRAN. The acoustic cavity must be surrounded by plate or solid elements but not both.4496 GL Acoustic Analysis - CHACAB - UFM 4422, SFM 4276 EC 7777, Wrong AnswersIf the table input features of the PACABS Bulk Data entry (TIDi fields) are used to define the reactance for the CHACAB absorber element then, depending on the machine, the job may fail and issue either the message "USER FATAL MESSAGE 4422, NUMBER OF NULL ROWS IN THE DYNAMIC MATRICES IS NOT EQUAL TO THE NUMBER OF NULL COLUMNS" or "SYSTEM FATAL MESSAGE 4276 EC 7777". Incorrect DB pressure values may also be produced.Avoidance: Instead of using the TABLEDi features to calculate the stiffness and mass values for the absorber element, specify the k, m and b values explicitly on the PACABS Bulk Data entry.4498 70 Documentation - LINE, MAXLINES - SFM 3019The message "SYSTEM FATAL MESSAGE 3019 MAXIMUM LINE COUNT EXCEEDED IN SUBROUTINE PAGER LINE COUNT EQUALS ****" is misleading, because the code is actually counting the pages. If the user specifies LINE=X and MAXLINES=Y, then the max number of pages that will be output is Y/X, regardless of how many lines are actually on each page. When the code counts more pages than Y/X, it will issue the message above. If the user specifies a value for LINE that is greater than the actual number of lines per page, then the job fails at a lower line count than MAXLINES.Avoidance: Specify a correct value for LINE.4503 68 Case Control - SDR2, MODES - SFM 3002 In MSC/NASTRAN Version 67.5 if the MODES command references an eigenvector that does not exist, the run fails and the message "SYSTEM FATAL MESSAGE 3002 MODULE=SDR2 EOF ENCOUNTERED WHILE READING DATA SET PHG" is output from the SDR2 module. Prior versions of MSC/NASTRAN correctly ignore a MODES command that is beyond the number of eigenvectors calculated. Avoidance: Remove the additional subcase and MODES command.4506 67.5 Optimization/Design Sensitivity - UMERGE1 - SFM 4276, EC 1409.If an optimization or design sensitivity analysis contains EPOINTs as is required for the Lagrange multiplier large mass method, then the execution fails in the UMERGE1 module and the message "SYSTEM FATAL MESSAGE 4276 ERROR CODE 1409" is output. Avoidance: The UMERGE1 DMAP statements at lines 65, 66, and 67 of subDMAP DYNSEN must be ALTERed to set the IOPT parameter to 1 as follows:from: UMERGE USETD,EGMG,,,/EGMP/'P'/'G'/'E' $to: UMERGE USETD,EGMG,,,/EGMP/'P'/'G'/'E'/1 $4525 70.5 Documentation/Optimization - DEQATN - UFM 201, SFM 217, UFM 224, UFM 5199Input errors on the DEQATN Bulk Data entry often result in poor messages. The following messages have been encountered when invalid symbols such as a "[" are used or the restriction against large field format is violated on the DEQATN entry: "USER FATAL MESSAGE 215 (PRER2O) BINARY OPERATORS CANNOT BE THE FIRST SYMBOL FOUND IN AN ARITHMETIC LOGICAL EXPRESSION" or "SYSTEM FATAL MESSAGE 233 (PRSPOP) UNDERFLOW OCCURRED DURING PROCESSING OF OPERAND STACK" or "USER FATAL MESSAGE 5199. ON THE ABOVE BULK DATA FREE FIELD CARD AN INTEGER OR A BCD FIELD HAD MORE THAN EIGHT CHARACTERS". Avoidance: Review the requirements of the DEQATN entry documented in the MSC/NASTRAN User's Manual and modify the DEQATN entries as necessary.4528 68 Parallel Matrix Methods - SPARSE, PARALLEL - Segmentation Fault In Version 67.5 of MSC/NASTRAN on the CONVEX C3800 computer, if parallel sparse decomposition is selected, the job fails and no message is printed to the F06 output file. The log file indicates a "Segmentation Fault" error in the routine relcpuu. Avoidance: Presently the only avoidance is to run MSC/NASTRAN within csh and specify the csh command "limit concurrency 4" before execution. The error will be fixed for Version 68 by limiting the maximum number of CPUs to 4 when using parallel sparse decomposition.4529 67.7 Sequencer - SEQP, PARAM,NEWSEQ,6 - SFM 4276 FILPOS EC 1044An error exists in the nested dissection option of the sequencer module. This option is selected by setting PARAM,NEWSEQ,6 in Version 65E, 66, 66A, 66B, 67, or 67.5 of MSC/NASTRAN. The option is also available by setting PARAM,NEWSEQ,8 in Version 67.5 whenever sparse decomposition is also selected. This error causes the job to fail in the SEQP module and the message "SYSTEM FATAL MESSAGE 4276 FILPOS ERROR CODE 1044" to be output. The error occurs only when superelement groups exist in the model and when the number of grid points in any group is more than 1/4 or less than 1/3 of the total number of grids. Avoidance: Other than selecting another sequencer option, there is no avoidance.4536 68 DMAP - EQUIV, EQUIVX - UFM 1126 in CALL SELR for datablock FPS (output-twice) If the EQUIV or EQUIVX statement appears immediately after a CALL statement then the message "USER FATAL MESSAGE 1126" may be incorrectly issued in the subsequent loop. This is an error in the Last-Time-Used (LTU) logic. (Version 67, 67.5 and 67.7 only) Avoidance: An avoidance is to specify the PARAML module for the offending datablock after the EQUIV (or EQUIVX statement). For example, if UFM 1126 is issued for datablock PS then insert the PARAML DMAP statement as in the following example.CALL XXXX PG/PA,PS $EQUIVX PA/PA1/-1 $PARAML PS//'PRES' $4538 68.0.0 Nonlinear Analysis - ASETi, OMITi - Poor Message, SFM 2199, UWM 4698If ASETi or OMITi entries are specified in SOL 66 or 106 and there are no elements with linear material properties, then SFM 2199 and UWM 4698 are issued. This error has been corrected in MSC/NASTRAN Version 68by issuing the meaninful user fatal message 4423.Avoidance: This is a user error. The avoidance is to remove all ASETi and OMITi entries since nonlinear degrees of freedom can not be omitted. The correction to SOL 66 and SOL 106 DMAPs results in the meaningful message "USER FATAL MESSAGE 4423 A NONLINEAR ELEMENT IS ATTACHED TO AN OMITTED DEGREE OF FREEDOM" being output.4539 68 Plotting - NEUPS - Missing Plot Output, Stack ErrorIf a plot file generated by the NEUPS utility can be displayed using the SUN PageView utility or other utilities, but is not able to be printed, then the Postscript file contains too many data points in a single curve and the data overflows the printer's memory. Avoidance: Possible resolutions include:1. Increase the printer's memory (may not be feasible); or try on other printers,2. Break a single long curve into a number of curves,3. Modify the NEUPS utility with the following changes.In subroutine PLOT, change the following lines:After subroutine plot(x,y,i)Add save strklnAfter write (unit=ips,fmt=20) x, y,' lineto'Add strkln = strkln + 1if( strkln.gt.50) then write(unit=ips, fmt=10) 'stroke' write(unit=ips, fmt=10) 'newpath'4543 GL Elements - QUADR - Wrong Answers for Non-Uniform Thickness The corner stress output for the QUADR and TRIAR elements due to membrane forces are calculated and output for the average thickness. Thus the corner stress output for non-uniform thickness elements is wrong. Avoidance: In MSC/NASTRAN Version 67.5, the STRESS(CORNER) option for the QUAD4 element may be used.4545 68 File Management Section - INIT SCRATCH, SCR300- UFM 4275 Logical names and their reference to physical files must be unique across all INIT statements. Thus, if both SCRATCH and SCR300 are assigned to the same physical file, then the job may fail and the message "USER FATAL MESSAGE 4275" may be issued. Avoidance: ASSIGN SCRATCH and SCR300 to different files.4549 68 Documentation - CTRIAX6, GPWG - Missing DocumentationFor the axisymmetric TRIAX6 element, the Grid Point Weight Generator outputs the c.g. for the modeled structure only . The calculated mass is the mass for the entire structure of revolution. This is design intent. This error has been addressed by including a comment under the description of the PARAM,GRDPNT entry in the 2nd printing of the MSC/NASTRAN Version 68 Quick Reference Guide.4551 68 Documentation - Application Manual, Section 7.7 - Installation Errors The following documentation errors exist in the Version 67.5 Section 7.7 of the CRAY(UNICOS), CONVEX, and VAX(VMS) MSC/NASTRAN Application Manuals:1) CRAY(UNICOS)p. 7.7-5 n67ins should be n675ins.p. 7.7-7 %1f should be %1d.2) CONVEXp. 7.7-5 n67ins should be n675ins.p. 7.7-9 The documentation should say move the nastran.p file and the nastran.man file into the /usr/man/catp directory.p. 7.7-20 nast67 should be nast675.3) DEC VAX/VMSp. 7.7-14 The documentation on p. 7.7-14 should show "PRT=NO !" instead of "PRT=NO $". p. 7.7-36 5 should be 4 on the Step 5 line.p. 7.7-37 In the Step 7 section, "Steps 2 through 7" should read "Steps 2 through 6" and "Step 4" should be "Step 3"4555 68 Documentation - DTIIN - Incorrect User's Manual Documentation The MSC/NASTRAN User's Manual documentation for the DTIIN entry is incorrect. The documentation currently indicates:DTIIN DTI,DTINDX/DTI1,DTI2,DTI3,DTI4,DTI5,DTI6,DTI7,DTI8,DTI9,DTI10/ PARM1/PARM2/PARM3,PARM4,PARM5,PARM6,PARM7,PARM8,PARM9/PARM10 $This should be changed to:DTIIN DTI,DTINDX/DTI1,DTI2,DTI3,DTI4,DTI5,DTI6,DTI7,DTI8,DTI9,DTI10/ PARM1/PARM2/PARM3/PARM4/PARM5/PARM6/PARM7/PARM8/PARM9/PARM10 $This error has been corrected in the Version 68 DMAP Module Dictionary.4559 69 Miscellaneous - GPSTR1, MODAC2 - Missing Documentation, UWM 4605 The following two user messages have the same number:"USER WARNING MESSAGE 4605. MAXIMUM NUMBER OF MESSAGES HAVE BEEN ISSUED BY GPSTR1 MODULE.""USER FATAL MESSAGE 4605, INPUT MATRIX **** IS INCOMPATIBLE WITH ITS ASSOCIATED OUTPUT LIST (I.E., TOL, FOL, LAMA, CLAMA)."The latter message is correct since it is the one that is documented in the MSC/NASTRAN User's Manual.4561 68 Documentation - OFP - Missing OutputRemark 2 of the MSC/NASTRAN User's Manual description of the OFP DMAP statement states that data blocks can be output by OFP. However, parameter OP1 does not honor data blocks LAMA, OEIGS, LAMX, CLAMA, and OGPWG. This error has been corrected in the Version 68 DMAP Module Dictionary.Avoidance: There is no known avoidance.4563 68 Restarts - SUBCOM, CBEAM - Inefficient Restarts When the SUBCOM Case Control command is added to a Structured Solution Sequence (SOL 101 through 200) data recovery restart, and the model contains CBEAM elements, the SEKRRS subDMAP is unnecessarily re-executed in the restart. (V67+ only).Avoidance: The error may be avoided by using one of the following actions: 1) Use PARAM,SERST,SEDR in the restart run, 2) Replace the SUBCOM with a SUBCASE that references an equivalent load. 3) Use an Unstructured Solution Sequence and perform a manual restart.4566 Composites - GPSTRESS, PCOMP - Wrong Answers Grid point stress output is not supported for composite elements. If grid point stress output is requested for a SURFACE containing composite elements meaningless answers (i.e., 1.E+30) are output for the grid points attached to composite elements.4572 68 Miscellaneous - ACCT - Incorrect label in Accounting file The header of the last field of the MSC accounting file (created by the "acct" keyword) should indicate "Min" not "Sec". Avoidance: The MSC/NASTRAN Version 67.5 script should be changed as followsOriginal definition (line 521 on Sun): echo ' ACC3="Monthly-Total-CPU-Sec"'Change to: echo ' ACC3="Monthly-Total-CPU-Min"'4573 68 Aeroelastic Analysis - RESTART - Inefficient Restart If an M, K aero pair is added to a restart run in Solution 145 or 146, then the existing aerodynamic matrices are unnecessarily recomputed.4574 68 Nonlinear Analysis - DBC, ESE - Missing OutputOn the CONVEX Version 67.5 release of MSC/NASTRAN if a nonlinear analysis contains a request for element strain energy output, then no data recovery output is written to the .XDB file.Avoidance: Remove the ESE request.4575 70 Documentation - CQUAD4, PSHELL - Poor AnswersA remark should be added to the MSC/NASTRAN User's Manual description of the PSHELL entry. If transverse shear flexibility is specified for a model with curved shells where the loading is dominated by twist, the results for a coarse to medium mesh model may be inaccurate and the results will diverge as the mesh is refined. Avoidance: MSC/NASTRAN Version 68.2 and later releases include "Shell Normals" an enhancement which corrects this deficiency. This enhancement is documented in the Version 69 Release Guide. Note that by default shell normals are not activated they must be explicitly requested. The Quick Reference Guide description of the CQUAD4 and PSHELL entries should be updated to provide guidance for the above situation. Permanent documentation, not release guides, should4576 Material Nonlinear Analysis - NLPCI, RIKS, MRIKS - UWM 6195 When either the RIKS or MRIKS method is used in MSC/NASTRAN Version 67 and later systems, the message "USER WARNING MESSAGE 6195 SOLUTION HAS REGRESSED TO AN EARLIER LOAD STEP" may be issued and the solution will not adapt. Avoidance: Specify the CRIS method on the NLPCI entry.4582 Elements - CMASSi, SEQP- Poor Message, UFM 2012 If a CMASSi entry (and possibly other scalar elements) specify the "0" degree of freedom of a grid point, the job fails and the message "USER FATAL MESSAGE 2012 GRID POINT *** SAME AS SCALAR POINT" is issued. Avoidance: Specify a valid degree of freedom on the CMASSi entry.4584 67.5.0.1 Postprocessing - OUTPUT2, PARAM,POST - Segmentation Violation Depending on the machine and operating system level, an error may be encountered when writing very large unformatted OUTPUT2 and OUTPUT4 files. This error causes the message "Segmentation Violation = Signal 11 Code 3" to appear in the log file, with the result that the OUTPUTi files are incorrect. This error has been corrected in Version 67.5.01. Version 67.5.01 is delivered to all new Sun clients and is available on request to all existing clients. This error has been observed on the following hardware/software combinations:MSC/NASTRAN SunOSVersion Version Machine StatusV67.5 4.1.3 Ver. 3 SparcStation 2 Fails Sparcstation 10 Fails Sparc server4586 68 File Management Section - ASSIGN, INIT, - UFM 505If an FMS statement begins with any blank space, then the job fails and the message "USER FATAL MESSAGE 505 (XCSA) CONTROL CARD 'FMS STATEMENT' IS ILLEGAL" is output.Avoidance: Enter the FMS statement beginning in field 1.4606 Postprocessing - OUTPUT2 - SFM 1222 If an OUTPUT2 neutral file is created and the ITAPE=-9 option is not used to write an EOF, then the following messages appear in the RCOUT2 job print when converting the file back to binary form:*** SYSTEM FATAL MESSAGE 1222 (LDRTRN) AN UNEXPECTED END OF FILE WAS DETECTED ON A NEUTRAL FILE DURING A DBLOAD OPERATIONUSER INFORMATION: THIS ERROR TERMINATES PROGRAM EXECUTION AND GENERALLY OCCURS WHEN THE DBUNLOAD JOB FAILS DURING NEUTRAL FILE CREATIONUSER ACTION: REVIEW NEUTRAL FILE CREATION JOB FOR FATAL MESSAGES*** SYSTEM INFORMATION MESSAGE RC0008 (RCOUT2) THE END-OF-FILE FATAL MESSAGE WRITTEN ABOVE OCCURRED DURING DATA BLOCK NAME PROCESSING. PROGRAMMER INFORMATION: 1. THIS ERROR GENERALLY INDICATES THAT THE LAST OUTPUT2 OPTION USED WAS NOT -9 2. THE OUTPU4609 GL Superelements - TEMP(LOAD), TEMP(INIT), RESTARTS - Wrong Answers The following error with thermal loads may occur in restarts with the superelement unstructured Solution Sequences (61-99) or restarts with PARAM,SERST,SEMI (or SEDR) in Solutions 101-200. If the initial temperature is not specified (i.e., TEMP(INIT) is not present) in the initial run (cold start) loads are not generated (i.e., SELG and SELR are not requested), and in the restart run TEMP(LOAD), TEMP(BOTH) or TEMP is specified but no SEMG requests are made (for the superelements processed in the cold start), then the thermal loads are incorrect. This error occurs because the EST data block, which is used in generating thermal loads and depends on the TEMP(INIT), is not regenerated in the restart. It is only generated if SEMG is requested. Avoidance: Specify the same TEMP(INIT) in th4610 68 Static Analysis - PARAM,MPCF, PARAM,INREL - UFM 3055 If inertia relief is requested in SOL 101 (PARAM,INREL,-1) in conjunction with "PARAM,MPCF,YES" in MSC/NASTRAN Version 67.5, then the job fails and the message "USER FATAL MESSAGE 3055 AN ATTEMPT TO MULTIPLY OR MULTIPLY AND ADD NON-CONFORMABLE MATRICES TOGETHER WAS MADE IN MODULE MPYAD". This is a version 67.5+ error only.Avoidance: If the model does not contain superelements (i.e., residual only), the following DMAP Alter may be applied to avoid this error:COMPILE SEDRCVR SOUIN=MSCSOU LIST NOREFALTER 16,16 $ CHANGE PG TO PJ1UPARTN USET,PJ1/PM,,,/'G'/'M'/'N'/1 $ A DMAP avoidance is under investigation for models that contain superelements.4611 67.7 DMAP - OUTPUT2, INPUTT2 - Neutral Format, UWM 6444, SFM 1208, SFM 1214 Using the NEUTRAL FORMAT option of OUTPUT2 and INPUTT2 in DMAP may cause the run to fail and issue the following warning and fatal messages: "UWM 6444 (INPTYP) - THE FILE ASSIGNED TO UNIT = CONTAINS DATA THAT IS INCONSISTENT WITH FORM = FORMATTED", "SFM 1208 (LDSTR) - ERROR SETTING UP TRANSLATE TABLE AT LOC = " and "SFM 1214 (LDRTRN) - ERROR TRANSLATING DATA FROM NEUTRAL FILE READ FOR SUBROUTINE LDSTR". Avoidance: Encountering this error is very unlikely and there is no a priori avoidance. If the error is encountered, some possible ways to workaround this problem are as follows: 1. Use the RCOUT2 utility to convert the neutral file to a binary file. Then use the binary option of INPUTT2 to read the file. 2. Rerun the initial OUTPUT2 job with a different neutral record le4612 67.7 Postprocessing - OUTPUT2, INPUTT2 - UWM 6444, SFM 1208, SFM 1214, SFM 2190The INPUTT2 module may fail when attempting to read an input file formatted with the new neutral option in MSC/NASTRAN Version 67.5. Messages that are evidence of this error include "USER WARNING MESSAGE 6444", "SYSTEM FATAL MESSAGE 1208", "SYSTEM FATAL MESSAGE 1214", and "SYSTEM FATAL MESSAGE 2190 (INPTN2) ILLEGAL VALUE FOR KEY".Avoidance: Use the RCOUT2 utility to convert the neutral file to a binary file. Then use the binary option of the INPUTT2 module to read the file.4617 68 Miscellaneous - - Missing Completion Time and Date The date and time that MSC/NASTRAN finishes is not printed to the .log file on the DECstation ULTRIX Version 67R2 system. Avoidance: Line 331 in the ".shl" should be modified. Remove the "exec " command and replace as follows: echo "/bin/time ${LOC_EXE}/${EXE_NAME} ${asgf} {$mem}"4618 69 Acoustic Analysis - ACSRCE, CHACAB, PACABS - Wrong Answers, Missing OutputIf an ACSRCE Bulk Data entry has the same DAREA ID (field 3) for loads applied to structural grid points then wrong answers or missing output may result.Avoidance: Define a RLOADi or TLOADi Bulk Data entry with an SID (field 2) and DAREA ID (field 3) which is unique with respect to the ACSRCE entry. Then define a DLOAD Bulk Data entry which is referenced by the DLOAD Case Control command and combines the RLOADi (or TLOADi) and ACSRCE entries.4619 68 Matrix Methods - SPARSE DECOMP, FBS - Wrong AnswersIf the sparse solver and FBS are run more than once and 2 by 2 pivots are necessary for some of the FBS operations, there may be wrong answers. Positive definite matrices do not require pivoting operations. Thus, this error is unlikely in the delivered solution sequences. The DMAP alter RFLAG.V675 delivered with Version 67.5 does not encounter this problem if superelements are not present.Avoidance: Do not use sparse decomposition with alters such as the Lagrange multiplier method that may produce indefinite matrices.4620 67.7.0.1 Aeroelastic Analysis - AMG, UFBS, ZONA - Divide By Zero, Missing Data Blocks The supersonic aerodynamic code (ZONA) contained in the Aero II option can fail when the inverse Mach line emanating from a control point of one bax is almost perfectly aligned with the leading edge of another box. On some machines, the error is evidenced by a divide by zero check in the AMG module. On others, it produces missing datablocks in the UFBS module.Avoidance: Experience has shown that a slight change in the requested Mach number (e.g., from M=2.4 to M=2.41) causes the error to go away and good answers result.4621 Plotting - AERO1 - No Plottable Structural Elements ExistIf the user desires a plot of only the aerodynamic model and specifies SET 1=AERO1, the following message appears:NO PLOTTABLE STRUCTURAL ELEMENTS EXIST IN SET 1 Avoidance: Adding any other element to the SET, such as SET 1=AERO1,QUAD4, results in a plot of the aerodynamic model and the elements specified.4623 70.5.2 Dynamic Response Analysis - TRD1 - UWM 3045, Poor MessageIf a job fails in the TRD1 module due to insufficient time the message "USER WARNING MESSAGE 3045 INSUFFICIENT TIME TO COMPLETE THE REMAINING ** SOLUTION(S) IN MODULE TRD1" is output. This message gives no indication of the amount of time necessary to complete the module. This message is also output by modules AMP, CEAD, FA2, FRRD1, and TRD2. Avoidance: Increase the amount of time on the TIME command.4626 68 Documentation - LOAD - Limitation RemovedRemark 6 under the MSC/NASTRAN User's Manual and Quick Reference Guide description of the LOAD entry is no longer applicable. In MSC/NASTRAN Version 66 the limit of 300 Si, Li pairs was removed.4627 67.7 Eigenvalue Analysis - EIGRL, LANCZOS - UFM 5429 The time estimated to complete a LANCZOS iteration may be very conservative for large problems. Thus, a run where ample time is specified may inappropriately encounter the message "USER FATAL MESSAGE 5429, INSUFFICIENT TIME TO START LANCZOS ITERATION". Avoidance: Specify a very large value on the TIME entry.4629 68 Documentation - Application Manual, Section 7.7.2 - InstallationThe command "dd if=/dev/extape of=/tmp/MSC675 bs=8b" (documented on page 7.7-2 of the MSC/NASTRAN Application Manual, Version 67.5 for CRAY UNICOS computers) which is to load the file from the delivery tape when an expander tape drive is used, does not work. `Avoidance: Use the command "dd if=/dev/extape of=/tmp/MSC675 bs=32768" as documented on the same page.4631 68 Miscellaneous - Shell Script - Data File Not Found If the name of the .dat file happens to match the beginning of the directory name, and that directory is included in the 1st argument (jid), line 184 of the Convex script file will remove the file name portion from the directory path, and thus the data file will not be found: For example if you have a data file named "abc.dat" in directory /usr1/jones/abc_dir, then submitting a V675 job as: nast675 /usr1/jones/abc_dir/abc will yield: Data file /usr1/jones_dir/abc.dat not found.Avoidance:Change the the following (line 184) in the script:(add a "\$" sign after the "name")from jid_dir=`echo ${jid} | sed "s;\/$name;;"`to jid_dir=`echo ${jid} | sed "s;\/$name\$;;"`also change the name into nametmpold line: jid_dir=`echo ${jid} | se4634 69 Cyclic Symmetry - EIGRL, CYSUP - Wrong Answers In cyclic symmetry analysis, the Lanczos method of eigenvalue extraction may incorrectly apply "SUPORT" logic which is selected by the CYSUP Bulk Data entry. In one problem, the CYSUP entry resulted in the first eigenvalue of the second Harmonic (a flexible mode) being set to 0 incorrectly. The eigenvector for this mode is correct. Avoidance: Do not use the CYSUP entry with the Lanczos method of eigenvalue extraction.4637 70.7 DMAP - VECPLOT - Incorrect Matrix Trailer, Wrong AnswersWhen the VECPLOT module is used to generate a matrix containing the geometry of the model, the resulting matrix may have an incorrect trailer value for the number of rows. If this is the case, subsequent modules that use the matrix may fail or give incorrect results.Avoidance: The following DMAP Alter demonstrates the use of the VECPLOT module to generate a matrix called OUTGEOM with the model geometry and uses the MODTRL module to correct the trailer.VECPLOT ,,BGPDT,EQEXIN,CSTM,,/OUTGEOM/0/3 $MODTRL OUTGEOM///LUSET $4644 68.2 Acoustic Analysis - PARAM,FLUIDMP - Missing OutputThe panel participation factors output are missing when the modal participation factors are requested for panels in acoustics, the request is for a selected set of grids, and the model consists of only fluid elements. This error exists in Version 67.5 and 68. Version 67 users should refer to Error 3672 before proceeding. Avoidance: To avoid this error in Version 67.5, apply the DMAP Alter listed below.COMPILE SEMFREQ SOUIN=MSCSOU NOREFALTER 125,125EQUIVX OG/OA/NOA $IF (NOA>-1) UPARTN USET,OG/OA,,,/'G'/'A'/'S'/1 $ALTER 148IF ( FLUIDMP0) is selected on the TABPRT module.The formatted option of the OUTPUT2 module and migration is not affected by this.Avoidance: In the cnddls.dat file in the del directory replace the existing DATABLK CMLAMA statement and all subsequent statements up to but not including the next DATABLK statement with the following:DATABLK CMLAMA TYPE=TABLE PATH=MLAA1 LOCATION=DBUPX, SAMEAS,LAMA,EOF5402 69 Heat Transfer - VIEW3D, PARAM,VIEW3D,1 - SFE 4276, EC 7777On the HP 9000 Version 67 and later releases of MSC/NASTRAN, if the Gaussian integration method (PARAM,VIEW3D,1) is used to compute the geometric view factors, then the job may fail with the following message:SFE 4276 - EC 7777 - RECEIVED SIGNAL 10 - ABORTINGAvoidance: Use one of the following avoidances to compute the geometric view factors:1. Add a dummy HBDY element.2. Use the finite difference or contour integration method instead of the Gaussian integration.5409 69 Transient Response - OTIME - Wrong LabelsIf the OTIME case control command is used on a model with superelements in SOL 109, the correct output values are calculated, but they are labeled with incorrect time values for superelements outside the residual structure. Although the output is given for the correct time steps as specified on the OTIME command, the time labels appear in sequential order starting with the initial time, as they would without the OTIME request.Avoidance: Place all superelements in the residual structure or remove the OTIME request.5410 70 Nonlinear Analysis - MATS1, NLITER - SFM 4276, EC7777On the VAX, if the elastic-perfectly plastic option is used for the work hardening slope by letting H=0.0 (the default) on the MATS1 entry, then the job may fail in the NLITER module and issue the message "SYSTEM FATAL MESSAGE 4276 - ERROR CODE 7777". Avoidance: Specify a small number for the work hardening slope (e.g., 1.E-10).5414 70.6 Complex Eigenvalue Analysis - EIGC, CLAN - Wrong AnswersIn some cases, erroneous right eigenvectors have been produced by the Lanczos method of complex eigenvalue extraction. An unsymmetric mass matrix may be the cause of the error. In one known case results were found to be incorrect on the IBM RS/6000 system but correct on the DEC VAX/VMS release. Version 70.5 of MSC/NASTRAN introduces Block Complex Lanczos eigenvalue extraction method which will solve this problem. The new method is not yet the default and must be selected by setting system(108)=4.Avoidance: There is no avoidance. However, it is recommended that, if complex eigenvectors are anintegral part of an analysis, the results be checked using the DMAP alter contained in Section 7.5 of the MSC/NASTRAN User's Guide for Numerical Methods, Version 67 edition. 5416 68.2 Superelements - SEDRCVR - Extra Output for Upstream SuperelementsIf a solution 106 analysis contains superelements, and output (e.g., displacement) is requested for the residual structure, then an error in the DMAP results in the same type of output being printed for the upstream superelements even though no output is requested for these superelements.Avoidance: Insert the following DMAP avoidances:$$ for v67 and v67.5$compile sedrcvr souin=mscsou nolist noref $alter 199,199 $if (seid=0) then $OFP OUGV1,OPG1,OQG1,OEF1X,OSTR1//S,N,CARDNO $endif $$$ for v68$compile sedrcvr souin=mscsou nolist noref $alter 209,209 $if (seid=0) then $OFP OUGV1,OPG1,OQG1,OEF1X,OSTR1,, CSTMS,EPTS,GEOM1VU,ERROR1// S,N,CARDNO//PVALID $ endif $$5418 68.2 File Management Section - INIT - Unpredictable resultsIf more than one INIT statement is supplied per LOGICAL DBset, then unpredictable results occur. For example:INIT DBALL LOGICAL=(DB01(100),DB02(100),DB03(100),DB04(100))INIT DBALL LOGICAL=(DB05(100),DB06(100))creates DB05, DB06, DB03, and DB04 members of DBALL but DBO1 and DB02 are not created. No warning or fatal messages is issued.Avoidance: Specify only one INIT statement per LOGICAL DBset. A continuation of the INIT statement may be specified by ending a line with a comma as follows:INIT DBALL LOGICAL=(DB01(100),DB02(100),DB03(100),DB04(100) ,DB05(100),DB06(100))5422 68.2 Optimization/Sensitivity - DSCM2 - Wrong Sensitivities, UFM 5165MSC/NASTRAN Version 67.7 and 68 do not calculate sensitivities due to damping effects for modal transient response. Therefore, either the sensitivity results are not accurate or the message "USER FATAL MESSAGE 5165 (DSVG1D-1) UNDEFINED INPUT FILE = 106, NAME = (NONE) , ERROR CODE = -6, MODULE DSVG1 IS TERMINATED" is output.Avoidance: Use the following DMAP avoidance for version 68 only. compile pslgdv list noref souin=mscsou $ alter 199 $ IF ( DODFREQ>0 OR DOMFREQ>0 OR DOMTRAN>0 ) EMG, EST,CSTMS,MPTS,DIT,,,,,,/ ,,,,BELM,BDICT/0/0/S,N,NOBGG $5423 68.2 Optimization/Design Sensitivity - DRESP1, DRESP2 - Extra Column in DSCM2 MatrixIf a DRESP2 entry does not reference a DRESP1 entry and if there are multiple solution types (there are three: frequency response, modal transient, and everything else), the DRESP2 entry is included in each solution type. For this to be a problem, the DRESP2 entry must be invoked by a DESOBJ request. The error is benign in thatthe problem can only have one objective but it does manifest itself as a duplicate column in the DSCM2 matrix. 5425 69 Documentation - AUTOSPCR - UFM 6137, UFM 5225, UWM 3057, SFM 3002When performing nonlinear analysis, PARAM,AUTOSPC does not operate on the residual structure, PARAM,AUTOSPCR is provided for that function. However, PARAM,AUTOSPCR does not behave in the same way as AUTOSPC. It only operates on the o-set. Therefore, in nonlinear analysis using AUTOSPCR, many degrees of freedom may not be eliminated which would have been eliminated with AUTOSPC (e.g. DOFs 456 for solid models). This could result in various fatal messages such as "USER FATAL MESSAGE 6137 (DFMNRS/D) INPUT MATRIX IS RANK DEFICIENT, RANK = 99 USER ACTION: CHECK MODEL","USER FATAL MESSAGE 5225. ATTEMPT TO OPERATE ON THE SINGULAR MATRIX KLLRH IN SUBROUTINE DCMP.", "User Warning Message 3057 Module=nliter,matrix CNVTST not positive definite","System Fatal Message 3002 illegal input to subrouti5428 68.2 Acoustic Analysis - GIV, HOU, PARTN - UFM 2166If an acoustic analysis model contains massless degrees of freedom and any transformation method of eigenvalue extraction is chosen (i.e., GIV, MGIV, HOU, MHOU, AGIV, AHOU) on the EIGR entry, then the run fails in the PARTN module and issues the message "USER FATAL MESSAGE 2166". This error exists in MSC/NASTRAN Version 68.0.0 on the IBM RS/6000, SGI, HP 9000/700, SUN SUNOS and SUN SOLARIS systems only. It has been corrected in MSC/NASTRAN Version 68 on all DEC, CONVEX and CRAY systems.Avoidance: A DMAP avoidance will be made available, however the simplest avoidance is to choose the Lanczos method of eigenvalue extraction.5429 70.5 Acoustic Analysis - VELOCITY - Meaningless Answers for Complex Acoustic ResultsIn acoustic analysis if the user requests VELOCITY=ALL in the Case Control, then "COMPLEX ACOUSTIC RESULTS" are output for the fluid grid points only and the standard complex velocity is output for the structure point. This is by design intent. However, if the user requests VELOCITY=setid and the setid contains structural and fluid points, then the program attempts to output "COMPLEX ACOUSTIC RESULTS" for the structural points and meaningless data is output. Avoidance: The only avoidances are to request VELOCITY=ALL or define a set comprised entirely of fluid points. Data recovery for structural point may then be obtained in a subsequent restart.5431 68.2 Heat Transfer - Superelements, IFP - UFM 2011, Misleading MessageSuperelements are no longer allowed in heat transfer problems (SOl 74,89,153,159). However, if the user attempts to use superelements, a misleading fatal message such as "USER FATAL MESSAGE 2011 NO PHBDY ENTRIES FOR CHBDYP" is issued.Avoidance: Use Solution 101 with app heat or remove the superelements.DMAP avoidancecompile phase0, souin=mscsou, nolist, noref $alter 32 $type parm,nddl,logical,n, nlheat $if ((nose > -1) and nlheat) then $$ message //' ' $ message //'dmap fatal error: superelements are not allowed' $ message //' in nonlinear heat transfer analysis' $ message //' ' $ exit $$endif $5435 68.0.1 Optimization/Design Sensitivity - PARAM,POST, DBC - Missing OutputWhen PARAM,POST,0 is used in a SOL 200 design optimization analysis incomplete data is output to the .XDB file. The results for first design cycle are missing from the output. The result for only the last design cycle is output to the XDB file. Also, the qualifier corresponding to the last design cycle (DSN=) incorrectly identifies the data as the first design cycle. i.e. the DSN was set to 1 instead of 5. This error effects MSC/NASTRAN Version 68 on the IBM RS6000, SUN SUNOS, SUN SOLARIS, HP 9000/700 and SGI releases only. The error is corrected in Version 68 on the CRAY and all DEC releases.Avoidance: The following alter may be applied to avoid this error:compile super3 souin=mscsou noref nolistalter 88type parm,,i,n,descycl1 $descycl1=descycle $5437 68.0.1 Nonlinear Heat Transfer - SOL 153, RESTART, VIEW - Inefficient RestartIn a nonlinear heat transfer restart with SOL 153 that does not change view factors; e.g., changes in boundary conditions, MSC/NASTRAN Version 68.0.0 unnecessarily recalculates the view factors . This error exists in MSC/NASTRAN Version 68.0.0 on the IBM RS/6000, SGI, HP 9000/700, SUN SUNOS and SUN SOLARIS systems only. It has been corrected in MSC/NASTRAN Version 68 on all DEC, CONVEX and CRAY systems.Avoidance: Insert the following alter in the restart run(s):compile nlscsh souin=mscsou noref nolistalter 226putsys(0,109) $alter 227putsys(1,109) $5442 68.2 Transient Heat Transfer - PARTN, OTIME, DLOAD - UFM 2166In MSC/NASTRAN Version 68, if the OTIME case control option is used to reduce the output and the problem has constant boundary conditions, fixed with SPC entries, but does not have a DLOAD, then the run fails and issues the following message " USER FATAL MESSAGE 2166, MATRIX TO BE PARTITIONED IS OF SIZE *** ROWS BY *** COLUMNS."Avoidance: Define at least one time-varying load using DLOAD in conjuction with TLOAD1 or TLOAD2 entries to fix the temperatures instead of the SPC entry. DMAP avoidance:compile sedisp, souin=mscsou, nolist, noref $alter 194,195 $MODACC CASEDR,OL1R,YS,,,/OL1DUM,YS1,,,/APP1 $PARTN YS1,COLP,/YQ ,,,/1 $SDR1 USET,,UL1,,YS1,GOA,GM, , , ,/UG,, / 1/'STATICS'/-1 $endalter $5443 68.0.1 Documentation - NEWS - Incomplete NEWS FileThe MSC/NASTRAN news file delivered with MSC/NASTRAN Version 68.0.0 on the HP, RS6000, SunOS, Solaris, and SGI is incomplete. The correct news file is listed below with "***" next to the lines omitted in the delivered news file: Welcome to MSC/NASTRAN Version 68MSC/NASTRAN Version 68 adds the following major new capabilities: * Completely rewritten documentation, including online delivery * Shape optimization * Dynamic and acoustic optimization * Superelement optimization * Aeroelastic optimization * P-version elements and adaptivity * 3D slideline contact * Additional hyperelastic elements * Improved differential stiffness * Substantially enhanced heat transfer * Multiple boundary conditions in SOLs 101, 103, and 200 * Perform5444 68.0.2 Eigenvalue Analysis - ESE, MODES - Incorrect LabelingElement Strain Energy output is incorrectly labeled when the MODES command is used. If an ESE request is made for the first mode then all ESE output is labeled as mode 1. If no ESE request is made for the first mode, then all subsequent requests are labeled as mode 0. This error is a result of an attempt to fix error 3560. The correction to 3560 has been removed in Version 68.0.25446 70.7 P-Elements - GPFORCE - Meaningless AnswersIf a model is comprised entirely of P-elements, a request for GPFORCE is ignored. If the model contains P and H elements an attempt is made to process the GPFORCE request for the P-element internal grid points but the results are incorrect.Avoidance: Ignore GPFORCE output request for the P-element degrees of freedom. By default the IDs of the internal points are greater than 101000000. The ID of the first internal grid point may be adjusted by the user by setting SYSTEM(178) or its alias SYSTEM GNSTART.5447 Documentation/Reference Manual - P-Elements - Missing DocumentationThere are several undocumented SYSTEM cells that relate to P-element and the internal generation of IDs. These system cells, there defaults and their aliases are documented below:SYSTEM ALIAS DEFAULT DESCRIPTION178 GNSTRT 101000000 Adaptive Grid Start ID179 GNMAX 110000000 Adaptive Grid Maximum ID 180 VGSTRT 111001001 VU-Grid Start ID181 VGMAX 120000000 VU-Grid Maximum ID182 VESTRT 100001001 VU-Element Start ID183 VEMAX 200000000 VU-Element Maximum ID5448 2005.0.2 Buckling Analysis - Superelements - Mislabeled OutputUpstream eigenvector data recovery in buckling analysis incorrectly identifies the output as the first subcase. The eigenvalue label is correct.5454 Miscellaneous - SEMAP - Wrong Resource EstimatesIn Version 67+ systems, the disk space estimate printed in the "Estimation Data for Superelement x" generated by SEMAP is not accurate. In Version 68, for large problems, the time estimates may also be quite meaningless since these formulas are based on nonsparse methods and the default solver is the sparse solver.Avoidance: There is no complete avoidance. The time estimates from the DECOMP, FBS and MPYAD modules can be used instead. The DECOMP estimate is printed by default in the Execution Summary (f04 file). The MPYAD and FBS estimates can be obtained in the f04 file by requesting DIAG 19 in the executive control section.5455 68 Postprocessing - OUTPUT4, ASSIGN - UWM 6445, Incorrect FormatOn the MSC/NASTRAN Version 67.5 SCO Unix system, if FORM=FORMATTED output is requested with the OUTPUT4 ASSIGN statement, then the OUTPUT4 file generated may not be in an 80 column format. This is most likely to occur if a non-default number of significant digits is requested on the OUTPUT4 statement. The message "USER WARNING MESSAGE 6445, INTPTYP, INPUTT4 FAILS WITH FORTRAN IOSTAT=10006" may also appear in the OUTPUT4 file. The values generated in the OUTPUT4 file are correct. Only the format is different. Avoidance: Add RECL=80 to the ASSIGN statement.5458 68.1 Database - DBCRT - SFM 446If NASTRAN attempts to lock a database file that resides on a swap partition (memory), MSC/NASTRAN Version 68 on the SUN 4 issues the message "SYSTEM FATAL MESSAGE 446 (DBCRT) SFM 446 ERROR ATTEMPTING TO CREATE A FILE (LOGICAL= xxx ) FOR DBSET xxx WITH READ AND WRITE PRIVILEGES". The following message is also written to the log file: SYSTEM FATAL MESSAGE - bio_c.opnlck.fcntl A BIO operations on a GINO file has failed. File name: "filename" File descriptor: n. errno: 22 - Invalid argument Result: -1This error normally occurs when /tmp is defined as a swap partition and SDIR=/tmp is set in an RC file.Avoidance: There are two avoidances: 1) Direct the file to a non-swap partition. 2) Turn file-locking off by set5462 68.0.2 Eigenvalue Analysis - ESE, DBC, PARAM,POST - Missing Output from XDB, SWM 6065If a modes analysis contains subcases that are not numbered sequentially from 1, then element strain energy data is not output to the XDB. The warning message "SYSTEM WARNING MESSAGE 6065 (DBC) DBCMSG ERROR MESSAGE 8 FROM SUBROUTINE DBCESE INSUFFICIENT MEMORY TO PROCESS RELATIONAL REQUIREMENTS" is issued in the output file. This error was introduced by the correction to related errors 3560 and 3841.Avoidance: Other than numbering the subcases in sequential order there is no known avoidance.5463 68.2 Superelements - RESTART, CSUPER - Wrong AnswersIn MSC/NASTRAN, if a CSUPER entry is added to a restart run to define an image superelement, the system modes may not be recalculated which can lead to wrong answers (related to error 3514). This error is most likely to occur if there are no grid points added in the restart run.Avoidance: Add a dummy grid point to the restart run. This grid point may be constrained in all six degrees of freedom.5465 68.2 Miscellaneous - TABTST - System Fatal ErrorThe example program TABTST, delivered as a utility program for MSC/NASTRAN Verion 68 and MSC/EMAS Version 3, contains a statement that is out of order. As a result of this error, the program loops until the buffers overflow and a system error occurs.Lines 216 and 317 of the TABTST source file read:IF(IN .NE. 0) GO TO 70IUAP=0The order of these two lines should be reversed, i.e., the correct order is:IUAP=0IF(IN .NE. 0) GO TO 70This source file is found in:Unix: /msc68/util/tabtst.fVMS: [.UTIL]TABTST.FORMVS: UTILSOU(TABTST)This error is present in all MSC/NASTRAN V68.0.X and MSC/EMAS Version 3.0.X systems.5467 70.5 Buckling Analysis - EIGRL - UFM 5401, UFM 5407When using Lanczos for solution 105 with F1 and F2 blank on the EIGRL entry, the following messages may be issued:SYSTEM FATAL MESSAGE 5407.INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES ACTUALLY COMPUTED IN A (SUB-)INTERVALSYSTEM FATAL MESSAGE 5401 (REIGL). LANCZOS METHOD IS UNABLE TO FIND ALL EIGENVALUES IN RANGE.ACCEPTED EIGENVALUES AND ADDITIONAL ERROR MESSAGES MAY BE LISTED ABOVE.USER ACTION: RERUN WITH ANOTHER METHOD OR ANOTHER SETTING ON EIGRL ENTRY.Avoidance: Specify finite values for F1 and F2. Also, it is not recommended to use system cell 146=1 to reduce scratch space without the use of finite values for F1 and F2. Another avoidance is to set SHFSCL on the EIGRL entry near the absolute value of the lowest execpted root.Please se5468 68.0.2 Miscelleneous - util build - makefile.inc failsThe script file delivered with MSC/NASTRAN Version 68.0.0 for the util build command is incorrect. The following messages are issued:make ARCH=sunos EXE=../exe FFLAGS=-Bstatic buildmake: Warning: Can't find `../makefile.inc': No such file or directorymake: Fatal error in reader: makefile, line 44: Read of include file `../makefile.inc' failedThis error occurs for the following machines: Sun SunOS, Sun Solaris, IBM RS/6000, HP, and SGI.Avoidance: The corrected makefile follows:#!/bin/sh## This is a shar file that will replace the util shell script and makefile.## Change directory to install-dir/msc68/util and run this script using# sh, for example:## sh util.shar#echo "Creating util"sed 's/^X//' utilX#!/bin/shX# utilX#X#5469 68 Complex Eigenvalue Analysis - EIGC - Wrong answersFor the complex Lanczos method of eigenvalue extraction, an error exists that results in incorrect left eigenvectors. Avoidance: There is no avoidance. However, it is recommended that, if complex eigenvectors are an integral part of an analysis, the results be checked using the DMAP alter contained in Section 7.5 of the MSC/NASTRAN User's Guide for Numerical Methods, Version 67 edition. 5471 69 Miscellaneous - BUFFPOOL - Confusing MessagesThe minimum BUFFPOOL value allowed is 15. If this minimum is violated, then in addition to the appropriate USER FATAL MESSAGE 1287, the following misleading fatal message appears: *** USER FATAL MESSAGE 1286 (SEMINT) THE VALUE SPECIFIED FOR NASTRAN SYSTEM CELL 119 IS 0 USER INFORMATION: THE VALUE MUST BE EQUAL TO -3 WHICH IS THE DEFAULT.5475 68.0.0 File Management Section - INIT MASTER(NORAM), OUTPUT2 - UIM 1206The message, "USER INFORMATION MESSAGE 1206 (OUTPN2) THE DATABLOCK OQG1 /OQG IN AN OUTPUT2 REQUEST IS NOT DEFINED IN THE MSC/NASTRAN DATA DEFINITION LANGUAGE (NDDL) THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT", is improperly issued when writing to a formatted OUTPUT2 file if INIT MASTER(NORAM) is used in the FMS section in an Unstructured Solution Sequence run of MSC/NASTRAN Version 67.5. Avoidance: Do one of the following. 1. Remove the INIT MASTER(NORAM) request from the FMS Section. 2. Use a Structured Solution Sequence (e.g., sol 101) instead.5476 68.0.2 Installation - IBM RS/6000 - Unreadable 1/4" Tape, error 0511-193The IBM RS/6000 MSC/NASTRAN Version 68 1/4" tape may not be r