MSC Nastran Error Messages User’s Guide

MSC Nastran 2024.1

Error Messages Guide
Corporate Office
Hexagon Manufacturing Intelligence, Inc. UK
78 Portsmouth Road Cedar House
Cobham, Surrey KT11 1HY
Telephone: (+44) 02070686555

Worldwide Web
www.hexagon.com

Support
https://simcompanion.hexagon.com

Disclaimer
Hexagon reserves the right to make changes in specifications and other information contained in this document without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended
to be exhaustive or to apply to any particular engineering problem or design. Hexagon assumes no liability or responsibility to any
person or company for direct or indirect damages resulting from the use of any information contained herein.

User Documentation: Copyright  2024 Hexagon AB and/or its subsidiaries. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of Hexagon is prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from Hexagon suppliers. Additional
terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms and
conditions and/or notices may be set forth in documentation and/or at third-party software information (or successor website designated
by Hexagon from time to time).
PCGLSS 8.0, Copyright © 1992-2016, Computational Applications and System Integration Inc. All rights reserved. PCGLSS 8.0 is
licensed from Computational Applications and System Integration Inc.
The Hexagon logo, Hexagon, MSC Software logo, MSC, Dytran, Marc, MSC Nastran, Patran, e-Xstream, Digimat, and Simulating
Reality are trademarks or registered trademarks of Hexagon AB and/or its subsidiaries in the United States and/or other countries.
NASTRAN is a registered trademark of NASA. FLEXlm and FlexNet Publisher are trademarks or registered trademarks of Flexera
Software. All other trademarks are the property of their respective owners.
Use, duplicate, or disclosure by the U.S. Government is subjected to restrictions as set forth in FAR 12.212 (Commercial Computer
Software) and DFARS 227.7202 (Commercial Computer Software and Commercial Computer Software Documentation), as
applicable.
U.S. Patent 9,361,413
May 16, 2024
Documentation Feedback
At Hexagon Manufacturing Intelligence, we strive to produce the highest quality documentation and
welcome your feedback. If you have comments or suggestions about our documentation, write to us.
Please include the following information with your feedback:
 Document name
 Release/Version number
 Chapter/Section name
 Topic title (for Online Help)
 Brief description of the content (for example, incomplete/incorrect information, grammatical
errors, information that requires clarification or more details and so on).
 Your suggestions for correcting/improving documentation

Note: The above mentioned e-mail address is only for providing documentation specific
feedback. If you have any technical problems, issues, or queries, please contact Technical
Support.
 MSC Nastran Error Messages 1
Overview of Error Messages

Overview of Error Messages

MSC Nastran displays User Information, User Warning, and User Fatal messages in the printed output. The amount of
information reported in a message is controlled by The Nastran entry NASTRAN XMSG. When XMSG=0 is the default;
only message summaries are reported. When XMSG=1, the full messages are reported.

MSC Nastran is improving its messages, and for these improved messages, XMSG will have no effect. For example:

*** USER FATAL MESSAGE 4291 (EQD4S)

FOR ELEMENT WITH ID =1
THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-MATRIX FOR MATERIAL ID =1 WHICH
IS SINGULAR.
USER ACTION:
[1] MID3 FIELD ON A PSHELL POINTS TO A MAT8 ENTRY WITH G1Z OR G2Z HAVING
ZERO VALUES.
[2] ENSURE THAT APPROPRIATE NON-ZERO VALUES ARE ENTERED FOR THE SHEAR
MODULI.
[3] IF THE USER IS NOT INTERESTED IN MODELING TRANSVERSE SHEAR, REMOVE THE
MID FROM THE MID3 FIELD.
[4] IN THE CASE THAT THE USER WISHES TO HAVE TRANSVERSE SHEAR SPECIFIED AND
DOES NOT HAVE TEST DATA.

User messages typically indicate problems with the input file. Corrective action is often indicated in the message text.
Refer to the MSC Nastran Quick Reference Guide for proper input file formats.
Warning and information messages appear at various places in the output.
Fatal messages will cause the program to terminate. These messages will appear at the end of the output and will often give
corrective action.
Operating system specific messages can appear in the MSC Nastran output. The format of these messages will vary with
the operating system. You should refer to your operating system manuals for interpretation of these messages.

Main Index
 2 MSC Nastran Error Messages
MSC Nastran Error Message List

MSC Nastran Error Message List

Errors 0 - 999 Errors 1000 - 1999 Errors 2000 - 2999

Errors 3000 - 3999 Errors 4000 - 4999 Errors 5000 - 5999

Errors 6000 - 6999 Errors 7000 - 7999 Errors 8000 - 8999

Errors 9000 - 9999 Errors 10000 - 10999 Errors 11000 - 11999

Errors 12000 - 12999 Errors 15000 - 15999 Errors 20000 - 20999

Errors 21000 - 21999 Errors 22000 - 22999 Errors 23000 - 23999

Errors 25000 - 25999 Errors 26000 - 26999

Main Index
 MSC Nastran Error Messages 3
Errors 0 - 999

Errors 0 - 999
1.0 *** USER FATAL MESSAGE %1 (%2)

2.0 *** USER WARNING MESSAGE %1 (%2)

3.0 *** USER INFORMATION MESSAGE %1 (%2)

4.0 *** SYSTEM FATAL MESSAGE %1 (%2)

5.0 *** SYSTEM WARNING MESSAGE %1 (%2)

6.0 *** SYSTEM INFORMATION MESSAGE %1 (%2)

7.0 *** USER FATAL MESSAGE 7 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
PARAMETER NO. %3 NEEDS PARAMETER NAME

User information: The parameter is not in correct format.

7.1 *** USER WARNING MESSAGE 7 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
PARAMETER NO. %3 NEEDS PARAMETER NAME

8.0 *** USER FATAL/WARNING MESSAGE 8 (XGPIDG)

BULK DATA PARAM CARD ERROR - MUST NOT DEFINE PARAMETER NAMED %1.

User information: In DMAP, the "N" in V,N %1 or in TYPE PARM,A,B,N means user cannot set the
value of the parameter with name %1 on a PARAM entry. In DMAP, when defining a parameter, the "N"
in V,N %1 means user cannot set the value of the parameter with name %1 on a PARAM entry in Bulk
Data.

Main Index
 4 MSC Nastran Error Messages
Errors 0 - 999

9.0 *** USER FATAL MESSAGE 9 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
VALUE NEEDED FOR PARAMETER NO. %3

User information: The constant needs value in a DMAP instruction or on a PARAM entry. Here is a
parameter in the referenced DMAP instruction which must have a value assigned before the execution of
the module.

9.1 *** USER WARNING MESSAGE 9 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
VALUE NEEDED FOR PARAMETER NO. %3

10.0 *** USER FATAL MESSAGE 10 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL INPUT DATA BLOCK SPECIFICATION.

User information: Too many or too few inputs are specified in the input for the referenced module.

10.1 *** USER WARNING MESSAGE 10 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL INPUT DATA BLOCK SPECIFICATION.

11.0 *** USER FATAL MESSAGE 11 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL OUTPUT DATA BLOCK SPECIFICATION.

11.1 *** USER WARNING MESSAGE 11 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL OUTPUT DATA BLOCK SPECIFICATION.

12.0 *** USER FATAL/WARNING MESSAGE 12 (XGPIDG)

ERROR IN DMAP INSTRUCTION NO. %1, ILLEGAL CHARACTER IN DMAP INSTRUCTION
NAME.

User information: The name of a module must be alpha-numeric characters, the first character being
alphabetic. Special characters are not allowed.
For example DMAP names like "8MOD" or "SETI=2" are not allowed.

Main Index
 MSC Nastran Error Messages 5
Errors 0 - 999

13.0 *** USER FATAL/WARNING MESSAGE 13 (XGPIDG)

THE DMAP INSTRUCTION %1 AT LINE NUMBER %2 IS NOT IN A VALID MODULE NAME.

User action:
Check the following items:
1. Check the spelling of the module's name.
2. If the module's name is valid and a DMAP alter is present then ensure that an ENDALTER (or the
CEND) statement appears immediately after the final DMAP statement of the DMAP alter.

14.0 *** SYSTEM FATAL MESSAGE 14 (XGPIDG)

ARRAY NAMED %1 OVERFLOWED

System information: See XGPI module description in MFD section of MSC NASTRAN Programmer's
Manual. The usual cause is insufficient open core. In other cases, it may be necessary to divide the DMAP
sequence into subDMAPs.

14.1 *** SYSTEM FATAL MESSAGE 14 (XGPIDG)

ARRAY NAMED %1 OVERFLOWED
AT DMAP INSTRUCTION NO. %2.

14.2 *** SYSTEM FATAL MESSAGE 14 (CFLORD)

ATTEMPTED OVERFLOW OF DATABLOCK ORDINAL TABLE (ARRAY IORDNL)
AS MANY AS %1 DATABLOCK(S) COULD NOT BE ADDED TO THE ORDINAL TABLE.

User information: Non-Added datablocks may appear in UFM 22 messages above.

User action: Remove unnecessary datablocks/views from SUBDMAP or restructure into multiple
SUBDMAPS.

Programmer information: Increase length of IORDNL array by minimum of %2 words.

*** SYSTEM FATAL MESSAGE 14 (XGPI)

14.3

NUMBER OF DEFINED MODULES EXCEEDS MAXIMUM OF %1 BY %2.

Programmer information: Increase size of array IMPLT in common block CIMPL.

Main Index
 6 MSC Nastran Error Messages
Errors 0 - 999

15.0 *** USER FATAL MESSAGE 15 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
INCONSISTENT LENGTH USED FOR PARAMETER NAMED %3

User information: This parameter was used in a previous DMAP instruction which gave it a different type.
See the MSC NASTRAN DMAP Programmers Guide.

15.1 *** USER WARNING MESSAGE 15 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
INCONSISTENT LENGTH USED FOR PARAMETER NAMED %3

16.0 *** USER FATAL MESSAGE 16 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL FORMAT

User information: Usually caused by early termination such as a LABEL statement without a NAME.

16.1 *** USER WARNING MESSAGE 16 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL FORMAT

User information: Usually caused by early termination such as a LABEL statement without a NAME.

*** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 17 (EVLMSG)

17.0
SYMBOL "%1" IS UNDEFINED

18.0 *** USER FATAL MESSAGE 18 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
TOO MANY PARAMETERS IN DMAP PARAMETER LIST

User information: Incorrect calling sequence for DMAP instruction. Compare the DMAP statement to the
description in the MSC NASTRAN DMAP Programmer's Guide or the MSC NASTRAN Programmer's
Manual to find the error.

Main Index
 MSC Nastran Error Messages 7
Errors 0 - 999

18.1 *** USER WARNING MESSAGE 18 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
TOO MANY PARAMETERS IN DMAP PARAMETER LIST

User information: Incorrect calling sequence for DMAP instruction. Compare the DMAP statement to the
description in the MSC NASTRAN DMAP Programmer's Guide or the MSC NASTRAN Programmer's
Manual to find the error.

19.0 *** USER FATAL/WARNING MESSAGE 19 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
LABEL NAMED %3 IS MULTIPLY DEFINED.

User information: LABEL named appears in more than one place in DMAP program.

20.0 *** USER FATAL MESSAGE 20 (XGPIDG)

EXTRANEOUS 'ELSE' / 'ELSEIF' STATEMENT AT INSTRUCTION %1

21.0 *** USER FATAL MESSAGE 21 (CIPFL)

THE NAME OF THE DATA BLOCK AT %1 POSITION %2 HAS ILLEGAL SYNTAX.

22.0 *** USER FATAL MESSAGE 22 (CDBDP1)

DATABLOCK NAMED %1 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

User action: CHECK FOR CORRECT SPELLING, OR MISSING TYPE STATEMENT, AND
RERUN.

User information: A common mistake is to forget that DMAP statements DMIIN and DTIIN are required
to read DMI and DTI matrices, respectively. Note that RF24D41 requires a DTIIN command.

22.1 *** USER FATAL MESSAGE 22 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

22.2 *** USER WARNING MESSAGE 22 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

Main Index
 8 MSC Nastran Error Messages
Errors 0 - 999

23.0 *** USER FATAL MESSAGE 23 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 IS NOT REFERENCED IN SUBSEQUENT FUNCTIONAL MODULE

23.1 *** USER WARNING MESSAGE 23 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 IS NOT REFERENCED IN SUBSEQUENT FUNCTIONAL MODULE

24.0 *** SYSTEM FATAL/WARNING MESSAGE 24 (XGPIDG)

CANNOT FIND DATA BLOCK NAMED %1 ON DATA POOL TAPE

System information: The contents of /XDPL/ do not match contents of Pool Tape.

25.0 *** USER FATAL MESSAGE 25 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
PARAMETER NAMED %3 HAS AN INCONSISTENT USER AUTHORIZATION

User information: Parameter is referenced in nonfunctional module, but is nowhere defined. An example is
COND LBL,X where X is not a variable parameter in a module before this statement.

25.1 *** USER WARNING MESSAGE 25 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
PARAMETER NAMED %3 HAS AN INCONSISTENT USER AUTHORIZATION

26.0 *** USER FATAL MESSAGE 26 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
LABEL NAMED %3 NOT DEFINED

User information: LABEL name does not appear in LABEL instruction. For example a COND,XXX state-
ment appears without a LABEL,XXX statement.

26.1 *** USER WARNING MESSAGE 26 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
LABEL NAMED %3 NOT DEFINED

User information: LABEL name does not appear in LABEL instruction. For example a COND,XXX state-
ment appears without a LABEL,XXX statement.

Main Index
 MSC Nastran Error Messages 9
Errors 0 - 999

27.0 *** USER FATAL/WARNING MESSAGE 27 (XGPIDG)

LABEL NAMED %1 NOT REFERENCED

User information: LABEL name appears only in a LABEL instruction. It is not necessary to reference a
LABEL.

32.0 *** USER FATAL MESSAGE 32 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

32.1 *** USER WARNING MESSAGE 32 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 MUST BE DEFINED PRIOR TO THIS INSTRUCTION

34.0 *** SYSTEM FATAL/WARNING MESSAGE 34 (XGPIDG)

CANNOT TRANSLATE DMAP INSTRUCTION NO. %1

System information: Error in subroutine XSCNDM.

36.0 *** SYSTEM FATAL/WARNING MESSAGE 36 (XGPIDG)

CANNOT FIND DATA BLOCK NAMED %1 ON OLD PROBLEM TAPE

37.0 *** USER FATAL MESSAGE 37 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
WARNING ONLY - MAY NOT BE ENOUGH FILES AVAILABLE FOR MODULE
REQUIREMENTS
FILES NEEDED = %3 FILES AVAILABLE = %4

37.1 *** USER WARNING MESSAGE 37 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
WARNING ONLY - MAY NOT BE ENOUGH FILES AVAILABLE FOR MODULE
REQUIREMENTS
FILES NEEDED = %3 FILES AVAILABLE = %4

Main Index
 10 MSC Nastran Error Messages
Errors 0 - 999

38.0 *** SYSTEM FATAL MESSAGE 38 (XGPIDG)

NOT ENOUGH CORE FOR GPI TABLES.

System information: The user must break up DMAP program.

39.0 *** SYSTEM FATAL/WARNING MESSAGE 39 (XGPIDG)

RIGID FORMAT DMAP SEQUENCE DOES NOT CORRESPOND TO MED TABLE

System information: The MED Table must have the same number of entries as there are DMAP
instructions in DMAP sequence. Can be caused by having more than one END DMAP statement.

40.0 *** USER FATAL/WARNING MESSAGE 40 (XGPIDG)

ERROR IN ALTER DECK - CANNOT FIND END OF DMAP INSTRUCTION

User information: The user should check the ALTER part of the Executive Control Section.

41.0 *** SYSTEM FATAL/WARNING MESSAGE 41 (XGPIDG)

TABLES INCORRECT FOR REGENERATING DATA BLOCK %1

System information: File Name Table and MED Table used by routine XFLDEF are wrong. The user can
compensate by altering OUT and IN module(s) which regenerate the data block.

42.0 *** USER FATAL MESSAGE 42 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
PARAMETER NAMED %3 ALREADY HAD VALUE ASSIGNED PREVIOUSLY

42.1 *** USER WARNING MESSAGE 42 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
PARAMETER NAMED %3 ALREADY HAD VALUE ASSIGNED PREVIOUSLY

User information: A DMAP instruction is attempting to assign a default value to a parameter that appears
in a previous instruction which assigned it a value.

*** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 43 (EVLMSG)

43.0
"%1" IS INVALID

Main Index
 MSC Nastran Error Messages 11
Errors 0 - 999

45.0 *** USER FATAL MESSAGE 45 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 ALREADY APPEARED AS OUTPUT OR WAS USED AS INPUT
BEFORE BEING DEFINED

45.1 *** USER WARNING MESSAGE 45 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA BLOCK NAMED %3 ALREADY APPEARED AS OUTPUT OR WAS USED AS INPUT
BEFORE BEING DEFINED

46.0 *** USER FATAL/WARNING MESSAGE 46 (XGPIDG)

INCORRECT REENTRY POINT

47.0 *** USER FATAL MESSAGE 47 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
THIS INSTRUCTION CANNOT BE FIRST INSTRUCTION OF LOOP

47.1 *** USER WARNING MESSAGE 47 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
THIS INSTRUCTION CANNOT BE FIRST INSTRUCTION OF LOOP

48.0 *** USER FATAL MESSAGE 48 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA SET %3 IS ALWAYS REGENERATED, THEREFORE IT WILL NOT BE CHECKPOINTED

48.1 *** USER WARNING MESSAGE 48 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
DATA SET %3 IS ALWAYS REGENERATED, THEREFORE IT WILL NOT BE CHECKPOINTED

49.0 *** SYSTEM FATAL/WARNING MESSAGE 49 (XGPIDG)

MPL TABLE (MODULE PROPERTIES LIST) IS INCORRECT

System information: The error is in common block /XGP12/.

Main Index
 12 MSC Nastran Error Messages
Errors 0 - 999

49.1 *** SYSTEM FATAL/WARNING MESSAGE 49 (XGPIDG)

MPL TABLE (MODULE PROPERTIES LIST) IS INCORRECT
DECIMAL LOCATION RELATIVE TO MPL(1) = %1,MODULE NAME = %2

50.0 *** SYSTEM FATAL/WARNING MESSAGE 50 (XGPIDG)

CANNOT FIND JUMP OSCAR ENTRY NEEDED FOR THIS RESTART

51.0 *** SYSTEM FATAL MESSAGE 51 (XGPIBS)

NOT ENOUGH OPEN CORE FOR XGPIBS ROUTINE

System information: Additional core memory is required to compile DMAP or rigid format.

52.0 *** SYSTEM FATAL MESSAGE 52 (XGPIDG)

NAMED COMMON /XLINK/ IS TOO SMALL

System information: There must be one word in LINK table for every entry in MPL.

53.0 *** USER FATAL MESSAGE 53 (XGPIDG)

INCORRECT FORMAT IN ABOVE CARD

User information: The link specification updated data (DIAG 28, 29, 30) is incorrect.

55.0 *** USER FATAL MESSAGE 55 (XGPIDG)

THE "SUBDMAP" KEYWORD CAN BE USED ONLY ONCE PER SUBDMAP

User information: Check your DMAP to be sure that each subDMAP has only one "SUBDMAP"
statement and also that each one has an "END" statement.

57.0 *** SYSTEM FATAL MESSAGE 57 (XGPI)

DUPLICATE MPL NAME ENCOUNTERED. NAME = %1

58.0 *** SYSTEM FATAL MESSAGE 58 (CSPACE)

THE OSCAR REGION OF OPEN CORE IS INSUFFICIENT FOR DMAP CODE EXPANSION
PROGRAMMER INFORMATION: LOSCAR = %1

59.0 *** USER FATAL MESSAGE 59 (CIFTHN)

ENDIF AT DMAP STATEMENT # %1 IS MISSING AN IF THEN STATEMENT

60.0 *** USER FATAL MESSAGE 60 (CIFTHN)

Main Index
 MSC Nastran Error Messages 13
Errors 0 - 999

IF THEN AT DMAP STATEMENT # %1 IS MISSING AN ENDIF STATEMENT

61.0 *** USER FATAL MESSAGE 61 (CIFTHN)
AN EXTRA "ELSE" STATEMENT EXISTS AT DMAP STATEMENT %1

63.0 *** USER FATAL MESSAGE 63 (CBRNCH)

%1 AT DMAP NO. %2 IS ILLEGALLY BRANCHING INTO OR OVERLAPS AN "IF THEN", "DO
WHILE", OR "REPT"

64.0 *** USER FATAL MESSAGE 64 (CBRNCH)

ATTEMPT TO JUMP BACKWARDS AT DMAP STATEMENT %1

65.0 *** USER FATAL MESSAGE 65 (CDOWCH)

NO MATCHING DO WHILE FOR ENDDO AT DMAP STATEMENT %1

66.0 *** USER FATAL MESSAGE 66 (CDOWCH)

INSUFFICIENT CORE AVAILABLE FOR DO WHILE PROCESSING IN DMAP COMPILER

67.0 *** USER FATAL MESSAGE 67 (CSYNTX)

DMAP STRUCTURE HAS MISMATCHED NUMBER OF IF THEN AND ENDIF STATEMENTS

68.0 *** USER FATAL MESSAGE 68 (CSYNTX,CDOWHC)

THE NUMBER OF %1 STATEMENTS IS LESS THAN THE NUMBER OF %2 STATEMENTS.

69.0 *** USER FATAL MESSAGE 69 (CGPIB)

SUBDMAP STATEMENT PARAMETER %1 NOT DEFINED

70.0 *** USER WARNING MESSAGE 70 (CGPIB)

TYPE STATEMENT PARAMETER %1 NOT IN VPS TABLE
MUST BE A CODE LOGIC ERROR FOR THIS TO HAPPEN

71.0 *** USER FATAL MESSAGE 71 (CDOWHI)

SYNTAX ERROR IN ABOVE DO WHILE STATEMENT

Main Index
 14 MSC Nastran Error Messages
Errors 0 - 999

72.0 *** USER FATAL MESSAGE 72 (CCALL,CMESAG,CPARM2)

PARAMETER SYNTAX ERROR IN ABOVE STATEMENT. PARAMETER IS %1 --- ERROR CODE
= %2

User action: CHECK FOR MISSING QUOTES, SLASHES, EXTRA OR MISSING BLANK
FIELDS,ETC.

User information: If the value of a parameter is allowed to change in the called subDMAP, then it must be
specified as S,XXXXX, where XXXXX is the parameter name. If it is specified as S,N,XXXXX, then error
code 2 will occur pointing to a parameter named N. If a parameter field is left blank on a CALL subDMAP
statement, then error code 2 will be improperly issued pointing to the last parameter in the command pre-
ceding the blank field. The correction for this is to place either a parameter name or value in the blank field.

73.0 *** USER FATAL MESSAGE 73 (CCALL,CMESAG,CPARM2)

THE PARAMETER NAMED %1 IS UNDEFINED

73.1 *** USER WARNING MESSAGE 73 (PRGWHRX)

THE %1 NAMED %2 IS %3 %4

74.0 *** USER FATAL MESSAGE 74 (CPARM2)

PARAMETER SYNTAX ERROR IN ABOVE STATEMENT IN PARAMETER POSITION NUMBER
%1

75.0 *** USER FATAL MESSAGE 75 (CIFTHN)

ELSE AT DMAP STATEMENT # %1 APPEARS BEFORE AN ELSE IF THEN STATEMENT

76.0 *** SYSTEM FATAL MESSAGE 76 ( )

A PROGRAM INTERNAL LIMIT RELATING TO CALL STATEMENTS HAS BEEN EXCEEDED.

User information: THIS LIMIT DEPENDS ON THE TOTAL NUMBER OF ARGUMENTS SPECI-
FIED ON ALL THE CALL STATEMENTS BEEN COMPILED IN THIS RUN.

User action: REDUCE THE NUMBER OF CALL STATEMENTS OR THE NUMBER OF ARGU-
MENTS ON THE CALL STATEMENTS.

Programmer action: INCREASE THE SIZE OF VARIABLE MAXCAL AND ARRAY CALLS OF
COMMON BLOCK CCALL1.

Main Index
 MSC Nastran Error Messages 15
Errors 0 - 999

81.0 *** USER WARNING MESSAGE 81 (CFLORD)

DATABLOCK %1 IS DECLARED APPEND ON A FILE STATEMENT AND IS ALSO SPECIFIED
AS OUTPUT ON AN EQUIV OR EQUIVX STATEMENT AT STATEMENT NO.%2.

User information: This may lead to unpredictable and/or erroneous results. See the Equivx module
description in the MSC Nastran DMAP Programmers Guide.

100.0 *** USER FATAL MESSAGE 100 (NDDL)

THE ABOVE CARD HAS AN INCORRECT FORMAT.
ERROR CODE= %1

101.0 *** SYSTEM FATAL MESSAGE 101 (NDDL)

INCORE LIST OF DEPENDENCY CARDS HAS OVERFLOWED AVAILABLE OPEN CORE
SPACE
--AVAILABLE OPEN CORE WORDS IS %1
INCORE LIST OF DEPENDENCY CARDS HAS OVERFLOWED AVAILABLE OPEN CORE
SPACE
--AVAILABLE OPEN CORE WORDS IS %2
--12 WORDS ARE NEEDED FOR EACH DEPENDENCY CARD IN NDDL

102.0 *** SYTEM FATAL MESSAGE 102 (NDDL)

INSUFFICIENT STORAGE SPACE FOR NDDL DEFINED QUALIFIERS -- NUMBER OF
QUALIFIERS CURRENTLY LIMITED TO %1

103.0 *** USER FATAL MESSAGE 103 (NDDL)

INSUFFICIENT OPEN CORE TO HOLD NDDL DATA BLOCK DESCRIPTION FOR %1
--AVAILABLE OPEN CORE WORDS IS %2

104.0 *** USER FATAL MESSAGE 104 (NDDL)

INSUFFICIENT STORAGE SPACE FOR NDDL PATH CARDS
--STORAGE SPACE LIMITED TO %1 PATH CARDS

105.0 *** USER FATAL MESSAGE 105 (NDDL)

'PATH=' KEYWORD NOT FOUND ON NDDL DATA BLOCK STATEMENT FOR %1

Main Index
 16 MSC Nastran Error Messages
Errors 0 - 999

106.0 *** USER FATAL MESSAGE 106 (NDDL)

NDDL PATH NAME = %1 ON DATA BLOCK STATEMENT FOR %2 HAS NOT BEEN
DEFINED

107.0 *** USER FATAL MESSAGE 107 (NDDL)

INSUFFICIENT OPEN CORE SPACE FOR NDDL PARAMETER CARD TABLE
--AVAILABLE OPEN CORE IN WORDS IS %1
--EACH PARAMETER REQUIRES 9 WORDS OF THIS STORAGE SPACE

108.0 *** USER FATAL MESSAGE 108 (NDDL)

NDDL PATH NAME = %1 ON DATA BLOCK STATEMENT FOR %2 HAS NOT BEEN
DEFINED

109.0 *** USER FATAL MESSAGE 109 (NDDL)

NO NDDL DEPENDENCY CARDS FOUND

110.0 *** USER FATAL MESSAGE 110 (NDDL)

A QUALIFIER NAMED %1 USED ON A PATH CARD HAS NOT BEEN DEFINED

111.0 *** USER FATAL MESSAGE 111 (NDDL)

INSUFFICIENT STORAGE SPACE FOR NDDL PATH CARDS

Programmer action: INCREASE ARRAY PATHTB AND MAXDB

User action: DECREASE NUMBER OF PATHS AND/OR NUMBER OF QUALIFIERS ON PATH

CARDS. STORAGE SPACE LIMITED TO %1 WORDS. EACH PATH REQUIRES ((2 * #QUALIFI-
ERS) +1) WORDS.

112.0 *** SYSTEM FATAL MESSAGE 112 (NDDL)

THE PVA TABLE EXCEEDS THE MAXIMUM ALLOWABLE SIZE OF %1.
PROGRAMMER ACTION: INCREASE THE SIZE OF PVATB ARRAY.

113.0 *** USER FATAL MESSAGE 113 (NDDL)

INVALID LOGICAL ASSIGNMENT ATTEMPTED IN NDDL DESCRIPTION

114.0 *** USER FATAL MESSAGE 114 (NDDL)

INVALID ASSIGNMENT OF TRUE OR FALSE ATTEMPTED IN NDDL DESCRIPTION

Main Index
 MSC Nastran Error Messages 17
Errors 0 - 999

115.0 *** USER FATAL MESSAGE 115 (NDDL)

THE DATA BLOCK DESCRIPTION FOR %1 IS MISSING THE 'LOCATION= KEYWORD

116.0 *** USER FATAL MESSAGE 116 (NDDL)

LOCATION PARAMETER= %1 IS UNDEFINED FOR PARAMETER= %2

116.1 *** USER FATAL MESSAGE 116 (NDDL)

LOCATION PARAMETER= %1 IS UNDEFINED FOR DATA BLOCK= %2

117.0 *** SYSTEM FATAL MESSAGE 117 (NDDL)

THE PATH VALUE TABLE HAS OVERFLOWED.
THE NUMBER OF PATHS IN THIS NDDL EXCEEDS THE MAXIMUM ALLOWED

User information: MAXIMUM NUMBER OF PATHS ALLOWED = %1

Programmer action: INCREASE THE SIZE OF THE PVATB ARRAY

118.0 *** SYSTEM FATAL MESSAGE 118 (NDDL)

THE NDDL TABLES INITIALIZED BY SUBROUTINE XCSA ARE BAD.
CHECK THE RECORD AND OPTIONS OF OPENS (I.E. WRT, WRTREW)

119.0 *** USER FATAL MESSAGE 119 (NDDL)

THE LIMIT ON THE NUMBER OF NDDL PARAMETERS HAS BEEN EXCEEDED.

User information: THE CURRENT LIMIT IS = %1

120.0 *** USER INFORMATION MESSAGE 120 (NDDL)

*** ERROR IN DESCRIPTION OF DATA BLOCK %1

User information: UNRECOVERABLE SYNTAX ERROR ENCOUNTERED

121.0 *** USER INFORMATION MESSAGE 121 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: YOU MAY NOT SPECIFY TYPE=%3 FOR AN ARRAY

Main Index
 18 MSC Nastran Error Messages
Errors 0 - 999

121.1 *** USER INFORMATION MESSAGE 121 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: UNRECOVERABLE SYNTAX ERROR ENCOUNTERED

122.0 *** USER FATAL MESSAGE 122 (NDDL)

IN DATABLK %1 A RECORD DESCRIPTION WITH SAMEAS,%2 IS NOT SPECIFIED BELOW
THE DESCRIPTION OF RECORD=%3.

User action: SPECIFY THE DESCRIPTION OF RECORD=%4 ABOVE ALL OF ITS SAMEAS REF-
ERENCES.

123.0 *** USER FATAL MESSAGE 123 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "PC" VALUE NOT 1 TO 5 CHARACTERS LONG

124.0 *** USER FATAL MESSAGE 124 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "EITHER" DATA TYPE IS "I", "AHEAD" VARIABLE IS "PC4" OR "PC5"

124.1 *** USER FATAL MESSAGE 125 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "EITHER" DATA TYPE IS "PCx", "AHEAD" VARIABLE IS "I"

125.0 *** USER FATAL MESSAGE 126 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "AHEAD" VARIABLE DOES NOT HAVE DATA TYPE "I", "PC4" OR "PC5"

125.1 *** USER FATAL MESSAGE 129 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "ENDENTRY" COUNT VARIABLE IS NOT TYPE "I"

Main Index
 MSC Nastran Error Messages 19
Errors 0 - 999

126.0 *** USER FATAL MESSAGE 127 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: AN "AHEAD" IS NESTED INSIDE AN "EITHER"

127.0 *** USER FATAL MESSAGE 128 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "AHEAD" REFERENCE DOES NOT APPEAR IN "EITHER" COMPONENT,

BEFORE ANY OTHER "EITHER" OR "OR"

128.0 *** SYSTEM FATAL MESSAGE 130 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: INTERNAL LOGIC ERROR. "EITHER/OR" DATA TYPE NOT SET WHEN
"OR" ENCOUNTERED.

129.0 *** USER FATAL MESSAGE 131 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "EITHER/OR" DATA TYPE IS "%3", VALUE IS "%4"

130.0 *** USER FATAL MESSAGE 132 (NDDL)

*** ERROR IN THE DESCRIPTION OF DATA BLOCK %1 - RECORD %2

User information: "EITHER/OR" DATA TYPE IS "%3" WITH VALUE="%4", CANNOT BE

CONVERTED TO "%3"

131.0 *** USER WARNING MESSAGE 131 (NDDL)

QUALIFIER %1 IS DUPLICATED ON PATH %2

141.0 *** USER WARNING MESSAGE 141 (LINKND)

NDDL 'PARAMETER' DEFINITION TABLE NOT FOUND

User information: Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS.

Main Index
 20 MSC Nastran Error Messages
Errors 0 - 999

142.0 *** USER WARNING MESSAGE 142 (LINKND)

NDDL 'QUALIFIER' DEFINITION TABLE NOT FOUND

User information: Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS.

143.0 *** USER WARNING MESSAGE 143 (LINKND)

NDDL 'DATABLOCK' DEFINITION TABLE NOT FOUND

User information: Insert ACQUIRE NDDL or ACQUIRE NDDLOLD in FMS.

144.0 *** USER FATAL MESSAGE 144 (LINKSB)

SUBDMAP %1 (CALLED BY SUBDMAP %2) IS NOT IN THE DATA BASE

User information: A "CALL" statement refers to an undefined subDMAP. Check the format on the
offending "CALL" statement.

145.0 *** USER WARNING MESSAGE 145 (LINKSB)

SUBDMAP %1 (CALLED BY SUBDMAP - %2) DOES NOT HAVE CORRECT NUMBER OF
WORDS IN FIRST RECORD.
IT MUST NOT BE AN OSCAR FILE

User information: SEND RUN TO HEXAGON AB.

DUMP OF BAD FIRST RECORD:
%3
%4
%5

Main Index
 MSC Nastran Error Messages 21
Errors 0 - 999

146.0 *** USER WARNING MESSAGE 146 (LINKTP)

A 'TYPE' STATEMENT DEFINES A DATABLOCK %1 IN SUBDMAP %2 WHICH IS NOT
DEFINED IN THE 'NDDL'

User information:
THIS ERROR MAY BE ISSUED IN THE FOLLOWING CIRCUMSTANCES:
1. THE TYPE STATEMENT REFERENCES AN ITEM WHICH HAS NOT BEEN DEFINED IN
THE NDDL.
2. THE NDDL STORED IN THE USER'S MASTER DBSET IS INCONSISTENT WITH THE
NDDL AND DMAP STORED IN THE DELIVERY DATABASE; FOR EXAMPLE, A
DATABASE CREATED IN VERSION 66 OR 66A IS BEING USED IN A VERSION 67 RUN.
ANOTHER EXAMPLE OF WHEN THIS ERROR WILL OCCUR IS WHEN A USER IS
ACCIDENTALLY ATTACHING TO AN OLD DATABASE, BECAUSE HE HAS RUN
MULTIPLE JOBS WITH THE SAME INPUT FILENAME, AND HE HAS ALSO CHANGED
FROM A USS TO SSS SOLUTION SEQUENCE OR VICE-VERSA. (E.G., SOL 24 TO SOL
101).

147.0 *** USER WARNING MESSAGE 147 (LINKTP)

A 'TYPE' STATEMENT DEFINES A QUALIFIER/PARAMETER %1 IN SUBDMAP %2 WHICH IS
NOT DEFINED IN THE 'NDDL'

User Information:
THIS ERROR MAY BE ISSUED IN THE FOLLOWING CIRCUMSTANCES:
1. THE TYPE STATEMENT REFERENCES AN ITEM WHICH HAS NOT BEEN DEFINED IN
THE NDDL.
2. THE NDDL STORED IN THE USER'S MASTER DBSET IS INCONSISTENT WITH THE
NDDL AND DMAP STORED IN THE DELIVERY DATABASE; FOR EXAMPLE, A
DATABASE CREATED IN VERSION 66 OR 66A IS BEING USED IN A VERSION 67 RUN.
ANOTHER EXAMPLE OF WHEN THIS ERROR WILL OCCUR IS WHEN A USER IS
ACCIDENTALLY ATTACHING TO AN OLD DATABASE, BECAUSE HE HAS RUN
MULTIPLE JOBS WITH THE SAME INPUT FILENAME, AND HE HAS ALSO CHANGED
FROM A USS TO SSS SOLUTION SEQUENCE OR VICE-VERSA. (E.G., SOL 24 TO SOL
101).

Main Index
 22 MSC Nastran Error Messages
Errors 0 - 999

148.0 *** USER WARNING MESSAGE 148 (LINKTP)

A 'TYPE' STATEMENT DEFINES A QUALIFIER/PARAMETER %1 IN SUBDMAP %2 WHICH
DOES NOT MATCH THE VARIABLE TYPE IN THE 'NDDL'.

User information:
THIS ERROR MAY BE ISSUED IN THE FOLLOWING CIRCUMSTANCES:
1. The TYPE statement references an item which has not been defined in the NDDL.
2. The NDDL stored in the user's MASTER dbset is inconsistent with the NDDL and DMAP stored
in the delivery database; for example, a database created in Version 66 or 66A is being used in a
Version 67 run. Another example of when this error will occur is when a user is accidentally attaching
to an old database, because he has run multiple jobs with the same input filename, and he has also
changed from a USS to SSS solution sequence or vice-versa. (e.g., SOL 24 to SOL 101).

149.0 *** USER WARNING MESSAGE 149 (LINKAR)

In subDMAP %2, the number of %3 arguments on CALL %1 statement is different than the SUBDMAP
%1 statement.
The number of %3 arguments on the CALL statement is : %4
The number of %3 arguments on the SUBDMAP statement is: %5

User information:
The run can fail in an unpredictable manner. Make sure that the number of arguments in the subDMAP
CALL match the number of arguments in the subDMAP.

150.0 *** USER WARNING MESSAGE 150 (LINKAR)

SUBDMAP %1 CALLED BY SUBDMAP %2 CANNOT BE FOUND IN DATA BASE.

151.0 *** USER WARNING MESSAGE 151 (LINKAR)

CALL STATEMENT %1 IN SUBDMAP %2 HAS A PARAMETER THAT DOES NOT MATCH
CALLED SUBDMAP IN AUTHORIZATION CODE.

User information:
PARAMETER IS NUMBER %3
AUTHORIZATION CODE IS : %4
AUTHORIZATION CODE SHOULD BE: %5

Main Index
 MSC Nastran Error Messages 23
Errors 0 - 999

151.1 *** USER WARNING MESSAGE 151 (LINKAR)

CALL STATEMENT %1 IN SUBDMAP %2 HAS A PARAMETER THAT DOES NOT MATCH
CALLED SUBDMAP IN TYPE AND/OR LENGTH

User information:
PARAMETER IS NUMBER %3
TYPE IS : %4
TYPE SHOULD BE : %5
(0-UNDEFINED, 1-INTEGER, 2-REAL S.P., 3-BCD, 4-REAL D.P., 5-COMPLEX S.P., ,6-COM-
PLEX D.P., 7-LOGICAL)
LENGTH IS : %6
LENGTH SHOULD BE : %7

152.0 *** USER WARNING MESSAGE 152 (LWRTBK)

SUBDMAP %1 CANNOT BE FOUND IN DATA BASE, ---- MUST BE CODE LOGIC ERROR.

User Action: SEND RUN TO HEXAGON AB.

153.0 *** USER WARNING MESSAGE 153 (LWRTBK)

END-OF-FILE HIT WHILE READING SUBDMAP %1 ---MUST BE CODE LOGIC ERROR.

User Action: SEND RUN TO HEXAGON AB.

154.0 *** USER WARNING MESSAGE 154 (LINKTP)

A 'TYPE' STATEMENT DEFINES A VARIABLE %1 IN SUBDMAP %2 WHICH IS DEFINED AS
BOTH A QUALIFIER AND A PARAMETER IN THE 'NDDL'

155.0 *** USER WARNING MESSAGE 155 (LINKTP)

A 'TYPE' STATEMENT DEFINES A CHARACTER QUALIFIER/PARAMETER %1 IN SUBDMAP
%2 WHICH DOES NOT MATCH THE CHARACTER LENGTH IN THE 'NDDL'

156.0 *** USER WARNING MESSAGE 156 (LINKSB)

MAIN SUBDMAP (%1) IS NOT IN THE DATA BASE

User Action: CHECK SOL STATEMENT FOR CORRECT SOLUTION REQUEST

Main Index
 24 MSC Nastran Error Messages
Errors 0 - 999

157.0 *** SYSTEM FATAL MESSAGE 157 (LINKER)

TOTAL NUMBER OF SUBDMAPS REFERENCED BY THIS SOLUTION SEQUENCE HAS
EXCEEDED THE ALLOWABLE NUMBER.

User Action: REDUCE THE NUMBER OF SUBDMAPS.

Programmer’s Action: INCREASE THE SIZE OF LIST2 ARRAY

158.0 *** SYSTEM FATAL MESSAGE 158 (LINKER)

END OF RECORD OF FILE 315 IN LINKER. EACH RECORD IN THIS FILE SHOULD CONSIST
OF 10 WORDS.
THIS FILE CONTAINS THE LINK CARDS GENERATED IN XCSA/PRLINK

159.0 *** USER INFORMATION MESSAGE 159 (PRLINK)

THE EXTERNAL SUBDMAP CALLS FOR %1 (MAIN) SUBDMAP WILL BE SATISFIED BY
OBJECTS FROM MSCOBJ DBSET

160.0 *** USER FATAL MESSAGE 160 (LINKSB)

OBJECT FILE FOR SUBDMAP %1 IS EMPTY.

User Action: RECOMPILE THIS SUBDMAP.

161.0 *** USER FATAL MESSAGE 161 (CTYPE)

DATABLOCK %1 IS REFERENCED ON A TYPE DB STATEMENT AND THE SUBDMAP
STATEMENT.

User Action: REMOVE THE REFERENCE FROM THE SUBDMAP STATEMENT OR THE TYPE
DB STATEMENT.

User Information: If a datablock is on the SUBDMAP statement, the calling subDMAP will define
whether it is a TYPE DB or not. Therefore, having a "TYPE DB" statement in the called subDMAP is a
conflict.

200.0 *** SYSTEM INFORMATION MESSAGE 200 (XGPIMW)

NO ERROR MESSAGE EXISTS FOR XGPIMW INTERNAL CODE NUMBER %1

200.1 *** SYSTEM INFORMATION MESSAGE 200 (XGPIDG)

NO ERROR MESSAGE EXISTS FOR XGPIDG INTERNAL CODE NUMBER %1

Main Index
 MSC Nastran Error Messages 25
Errors 0 - 999

200.2 *** SYSTEM INFORMATION MESSAGE 200 (PRXMSG)

NO ERROR MESSAGE EXISTS FOR PRXMSG INTERNAL CODE NUMBER %1 CALLED FROM
%2 DURING %3 %4 PROCESSING

200.3 *** SYSTEM INFORMATION MESSAGE 200 (NDDMSG)

NO ERROR MESSAGE EXISTS FOR NDDMSG INTERNAL CODE NUMBER %1 CALLED
FROM %2

200.4 *** SYSTEM INFORMATION MESSAGE 200 (LNKMSG)

NO ERROR MESSAGE EXISTS FOR LNKMSG INTERNAL CODE NUMBER %1 CALLED FROM
%2

200.5 *** SYSTEM INFORMATION MESSAGE 200 (CEPMSG)

NO ERROR MESSAGE EXISTS FOR CEPMSG INTERNAL ERROR CODE %1 CALLED FROM
%2

202.0 *** SYSTEM FATAL MESSAGE 202 (A?)

UNABLE TO ADD %1 CONSTANT %2 TO %3 VPS TABLE

203.0 *** SYSTEM WARNING MESSAGE 203 (A?)

TYPE CODE %1 IS CURRENTLY NOT IMPLEMENTED IN THE %2 EXPRESSION PARSER

204.0 *** USER FATAL MESSAGE 204 (A?)

NULL CHARACTER %1 AT POSITION %2 OF %3 %4

205.0 *** USER FATAL MESSAGE 205 (A?)

SYNTAX ERROR IN STRING CONSTANT AT POSITION %1 OF %2 %3

206.0 *** USER FATAL MESSAGE 206 (A?)

SYNTAX ERROR DETECTED IN STRING AT POSITION %1 OF %2 %3 CHARACTER = %4

207.0 *** USER FATAL MESSAGE 207 (A?)

INVALID USE OF %1 CONSTRUCTING %2 CONSTANT AT POSITION %3 OF %4 %5

User information: This can occur if a complex number has a decimal point immediately following the
sign--make sure that there is a zero between the sign and the decimal point.

Main Index
 26 MSC Nastran Error Messages
Errors 0 - 999

208.0 *** USER FATAL MESSAGE 208 (A?)

INVALID %1 PRECISION CONSTANT AT POSITION %2 OF %3 %4

209.0 *** USER FATAL MESSAGE 209 (A?)

INVALID CHARACTER DETECTED IN COMPLEX CONSTANT AT POSITION %1 OF %2 %3

210.0 *** USER FATAL MESSAGE 210 (A?)

MULTIPLE SIGN DETECTED IN COMPLEX CONSTANT AT POSITION %1 OF %2 %3

211.0 *** USER FATAL MESSAGE 211 (A?)

EMBEDDED BLANKS DETECTED IN COMPLEX NUMBER AT POSITION %1 OF %2 %3

212.0 *** USER FATAL MESSAGE 212 (A?)

CHARACTER STRING EXCEEDS 80 CHARACTERS AT POSITION %1 OF %2 %3

213.0 *** USER FATAL MESSAGE 213 (A?)

%1 PRECEDED BY %2 AT POSITION %3 OF %4 %5

214.0 *** USER FATAL MESSAGE 214 (A?)

LOGICAL CONSTANTS MAY NOT APPEAR ON THE LEFT-SIDE OF AN ASSIGNMENT
STATEMENT. AN ATTEMPT WAS MADE TO REDEFINE %1 AT POSITION %2 OF %3 %4

215.0 *** USER FATAL MESSAGE 215 (A?)

BINARY OPERATORS CANNOT BE THE FIRST SYMBOL FOUND IN AN ARITHMETIC OR
LOGICAL EXPRESSION

216.0 *** USER WARNING MESSAGE 216 (A?)

VARIABLE NAME EXCEEDS 8 CHARACTERS AT POSITION %1 OF %2 %3.
VARIABLE NAME IS TRUNCATED TO %4.
RESULTANT PROCESSING MAY BE INCORRECT OR AMBIGUOUS

217.0 *** SYSTEM FATAL MESSAGE 217 (A?)

THE %1 OSCAR %2 ADDRESS POINTER (%3) IS INVALID

Main Index
 MSC Nastran Error Messages 27
Errors 0 - 999

218.0 *** USER FATAL MESSAGE 218 (A?)

NUMERIC MIXED MODE ASSIGNMENTS ARE NOT ALLOWED IN %1 %2S.
ASSIGNMENT ATTEMPTED: %3 DATA TO %4 VARIABLE.

User information: This indicates that an assignment statement has mixed-mode arithmetic. Check that all
variables in the expression are of the same type (example: real-single precision). If not, there are expressions
to convert from one type (example: integer) to another (example: real-single precision).

219.0 *** USER WARNING MESSAGE 219 (A?)

A NUMERIC MIXED MODE ASSIGNMENT WAS MADE IN THE PRECEDING %1 %2.
ASSIGNMENT MADE: %3 DATA TO %4 VARIABLE

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).

220.0 *** USER FATAL MESSAGE 220 (A?)

ASSIGNMENT OF %1 VALUE TO %2 VARIABLE IS ILLEGAL IN %3 %4S.

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).

221.0 *** USER FATAL MESSAGE 221 (A?) or USER WARNING MESSAGE 221 (A?)
MIXED MODE EXPONENTIATION OPERATION DETECTED DURING %1 %2 PROCESSING.
%3 BASE RAISED TO %4 POWER

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).

Main Index
 28 MSC Nastran Error Messages
Errors 0 - 999

222.0 *** USER FATAL MESSAGE 222 (A?)

NON-NUMERIC %1 USED IN EXPONENTIATION OPERATION DURING %2 %3
PROCESSING.

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).

223.0 *** USER FATAL MESSAGE 223 (A?)

THE %1 OPERATOR %2 CANNOT BE USED ON %3 OPERANDS DURING %4 %5
PROCESSING.

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).

224.0 *** USER FATAL MESSAGE 224 (A?) or USER WARNING MESSAGE 224 (A?)
MIXED MODE USAGE BY THE ARITHMETIC OPERATOR %1 DETECTED DURING %2 %3
PROCESSING.
USAGE IS BETWEEN %4 AND %5 OPERANDS

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).

225.0 *** USER FATAL MESSAGE 225 (A?) or USER WARNING MESSAGE 225 (A?)
THE %1 OPERATOR %2 DETECTED IN USE BETWEEN %3 AND %4 OPERANDS
DURING %5 %6 PROCESSING.
can you

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).

226.0 *** USER FATAL MESSAGE 226 (A?)

Main Index
 MSC Nastran Error Messages 29
Errors 0 - 999

THE %1 OPERATOR CANNOT BE USED ON %2 VALUES IN A %3 %4

User information: This indicates that an assignment statement has mixed-mode arithmetic.
Check that all variables in the expression are of the same type (example: real-single precision). If not, there
are expressions to convert from one type (example: integer) to another (example: real-single precision).
227.0 *** USER FATAL MESSAGE 227 (A?)
UNMATCHED %1 DETECTED IN %2 %3

User information: If the DMAP statement is followed by a "$" to denote a comment, and the comment
contains a single quote ( ' ), then this error will occur.

228.0 *** USER FATAL MESSAGE 228 (A?)

THE KEYWORD %1 WAS USED AS A VARIABLE AT POSITION %2 OF %3 %4

229.0 *** USER WARNING MESSAGE 229 (A?)

NO INFORMATION AVAILABLE TO PROCESS ON %1 %2

230.0 *** SYSTEM FATAL MESSAGE 230 (A?)

THE FUNCTION %1 WAS NOT FOUND IN LIBRARY FUNCTION TABLE DURING %2 %3
PROCESSING.

231.0 *** USER FATAL MESSAGE 231 (A?)

THE NUMBER OF ARGUMENTS IN THE ARGUMENT LIST FOR %1 IS %2 THAN THE %3 %4
ARGUMENTS %5
NUMBER OF ARGUMENTS SPECIFIED WAS %6

232.0 *** SYSTEM FATAL MESSAGE 232 (A?)

%1 ARGUMENT FORMAT FOR FUNCTION %2 NOT DEFINED IN LIBRARY FUNCTION
TABLE

233.0 *** SYSTEM FATAL MESSAGE 233 (A?)

Main Index
 30 MSC Nastran Error Messages
Errors 0 - 999

%1 OCCURRED DURING PROCESSING OF %2 STACK DURING %3 %4 PROCESSING.

User information: THIS ERROR OCCURS WHEN THE EXPRESSION BEING PARSED CON-
TAINS MORE UNIQUE VARIABLES AND CONSTANTS THAN ALLOWED OR IF KEYWORDS
(FOR EXAMPLE: OR) ARE USED AS VARIABLES

User action: SIMPLIFY EXPRESSION AND NOTIFY HEXAGON AB PROGRAMMER INFORMA-

TION: STACK POINTER = %5 WITH %6 = %7

233.1 *** SYSTEM FATAL MESSAGE 233 (A?)

%1 OCCURRED DURING PROCESSING OF %2 STACK DURING %3 %4 PROCESSING.

User action: CHECK THE EXPRESSION FOR VARIABLE NAMES WHICH ARE THE SAME AS
FUNCTION NAMES OR OPERAND NAMES AS LISTED IN THE DMAP PROGRAMMER'S
GUIDE

Programmer information: STACK POINTER = %5 WITH %6 = %7

234.0 *** USER FATAL MESSAGE 234 (A?)

SYNTAX ERROR DETECTED WHILE PROCESSING %1 PRECISION CONSTANT IN A %2 %3.

User action: CORRECT SYNTAX FOR %4 PRECISION CONSTANT AND RESUBMIT RUN.

235.0 *** USER FATAL MESSAGE 235 (A?)

THE MAXIMUM SPACE IN THE %1 ARRAY HAS BEEN EXCEEDED DURING %2 %3
PROCESSING.

User information:
1. THE MAXIMUM NUMBER OF AVAILABLE TOKENS IS %4
2. EACH OPERATOR, VARIABLE NAME, OR CONSTANT VALUE MAKE ONE TOKEN

User action: SIMPLIFY EXPRESSION AND RESUBMIT RUN.

300.0 *** USER FATAL MESSAGE 300 FROM XRCARD ABOVE.

300.1 *** USER FATAL MESSAGE 300 (RCARD)

DATA ERROR IN FIELD UNDERLINED.

Main Index
 MSC Nastran Error Messages 31
Errors 0 - 999

300.2 *** USER FATAL MESSAGE 300 FROM CRCARD ABOVE.

THE MESSAGES ABOVE ARE FROM CRCARD.

301.0 *** USER WARNING MESSAGE 301 (IFS4P)

BULK DATA ENTRY %1 CONTAINS INCONSISTENT DATA. SORTED ENTRY COUNT = %2

User information: One or more of the Poisson's ratios on a MAT3 entry is greater than 1.0.

302.0 *** USER INFORMATION MESSAGE 302 (IFS3P)

ONE OR MORE GRID ENTRIES HAVE DISPLACEMENT COORDINATE SYSTEM ID OF -1

User information: Coordinate system identification numbers of -1 indicate fluid grid point in coupled
fluid-structure analysis.

305.0 *** SYSTEM FATAL MESSAGE 305 (IFPDRV)

IFP MODULE CANNOT OPEN GINO FILE %1

System information: Unexpected nonstandard return from OPEN.

306.0 *** SYSTEM FATAL MESSAGE 306 (IFPDRV)

READ LOGICAL RECORD ERROR.

System information: Short record encountered. Bulk Data entries occupy 20 words.

307.0 *** SYSTEM FATAL MESSAGE 307 (IFPSIZ)

THE NAME OF BULK DATA ENTRY %1 IS INVALID.

Programmer Action: IF THE ABOVE NAME IS A VALID BULK ENTRY, THEN CHECK THE
HASHING FUNCTION TABLE(S), AND MAKE SURE THERE ARE NO "LOST" ITEMS.

307.1 *** USER FATAL MESSAGE 307 (IFPDRV)

ILLEGAL NAME FOR BULK DATA ENTRY %1

User information: See Chapter 5 of the MSC NASTRAN Quick Reference Guide.

Main Index
 32 MSC Nastran Error Messages
Errors 0 - 999

307.2 *** USER FATAL MESSAGE 307 (IFPDRV)

BULK DATA ENTRY %1 IS DETECTED.

User Action: Insert NASTRAN SYSTEM(444)=1 into the input file or specify sys444=1 on the nastran
command line or in an rcfile. If this is a deck with SESET and MATiF, you are advised to remove SESET
and rerun.

308.0 *** USER FATAL MESSAGE 308 (IFPDRV)

BULK DATA ENTRY %1 NOT ALLOWED IN %2 APPROACH.

User information: See chapter 5 of the MSC NASTRAN Quick Reference Guide.

308.1 *** USER FATAL MESSAGE 308 (IFS8P)

BULK DATA ENTRY TEMPBC NOT ALLOWED IN SOL 400.

User Information: Use SPC1 and SPCD Bulk Data entries to specify transient temperature boundary con-
ditions in SOL 400.

309.0 *** USER WARNING MESSAGE 309 (IFPDRV)

BULK DATA ENTRY %1 IMPROPER IN %2 APPROACH.

User information: See chapter 5 of the MSC NASTRAN Quick Reference Guide.

310.0 *** USER FATAL MESSAGE 310 (IFPDRV)

BULK DATA ENTRY %1 NOT ALLOWED IN SAME DECK WITH AXIC CARD.

User information: See chapter 5 of the MSC NASTRAN Quick Reference Guide.

311.0 *** USER FATAL MESSAGE 311 (IFPDRV)

NON-UNIQUE FIELD 2 ON BULK DATA ENTRY %1 %2 SORTED ENTRY COUNT = %3

User information: Sorted Bulk Data entry type indicated must have a unique integer in field 2. An error in
the input has been detected. Two or more grid points, elements, or properties have the same ID. (For
example, you may not use two GRID entries with the GID=2 in the same run.)

312.0 *** USER FATAL MESSAGE 312 (IFPDRV)

Main Index
 MSC Nastran Error Messages 33
Errors 0 - 999

TOO MANY CONTINUATIONS FOR BULK DATA ENTRY %1 %2 SORTED ENTRY COUNT =
%3

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

313.0 *** USER FATAL MESSAGE 313 (IFPDRV)

ILLEGAL NUMBER OF WORDS ON BULK DATA ENTRY %1 %2 SORTED ENTRY COUNT =
%3

User information: THIS MESSAGE IS USUALLY ISSUED WHEN THERE ARE ERRORS ON THE
CONTINUATIONS ENTRIES.
1- FIELD 1 IS NOT UNIQUE OR IS BLANK
2- FIELD 10 ON ONE OR MORE ENTRIES IS THE SAME AS FIELD 1 ON THIS ENTRY

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. One cause of this message is using a "D" before the exponent for a real number. Only "E" is
allowed, unless noted otherwise on the Bulk Data entry description in chapter 5 of the MSC NASTRAN
Quick Reference Guide. Another cause is placing a BCD variable in a real or integer field, such as using the
letter O when the number 0 is intended.

314.0 *** SYSTEM FATAL MESSAGE 314 (IFPDRV)

INVALID CALL FROM IFP : K = %1

System information: Code error, machine failure, or cell is being destroyed.

315.0 *** USER FATAL MESSAGE 315 (IFPDRV)

FORMAT ERROR ON BULK DATA ENTRY %1 %2 SORTED ENTRY COUNT = %3

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. If you are using the large field format make sure the number of entries is even.

Main Index
 34 MSC Nastran Error Messages
Errors 0 - 999

315.1 *** USER FATAL MESSAGE 315 (IFPDRV)

FORMAT ERROR ON BULK DATA ENTRY %1

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. If you are using the large field format make sure the number of entries is even.

315.2 *** USER FATAL MESSAGE 315 (IFPDRV)

POSSIBLE FORMAT ERROR ON BULK DATA ENTRY %1 ID=%2

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. If you are using the large field format make sure the number of entries is even.
316.0 *** USER FATAL MESSAGE 316 (IFS2P):
THE PRECONDITIONER OPTION %1 SPECIFIED ON THE ITER ENTRY IS INVALID.

User Action: CHECK BULK DATA CARD ITER.

316.1 *** USER FATAL MESSAGE 316 (IFPDRV)

ILLEGAL DATA ON BULK DATA ENTRY %1 %2 SORTED ENTRY COUNT = %3

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. If you are using the large field format make sure the number of entries is even.

316.2 *** USER FATAL MESSAGE 316 (IFPDRV)

ILLEGAL DATA ON BULK DATA ENTRY %1

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. If you are using the large field format make sure the number of entries is even.

316.3 *** USER FATAL MESSAGE 316 (IFPDRV)

ILLEGAL DATA ON BULK DATA ENTRY %1 ON SORTED ENTRY COUNT %2

User Information: %3 ID %4 EXCEEDS MAXIMUM VALUE ALLOWED %5.

User Action: IF THE ID VALUE GREATER THAN THE MAXIMUM VALUE MUST BE USED,
ADD NASTRAN STATEMENT (NASTRAN SYSTEM(175)= nnn) TO THE INPUT FILE.

316.4 *** USER FATAL MESSAGE 316 (IFPDRV)

Main Index
 MSC Nastran Error Messages 35
Errors 0 - 999

POSSIBLE ILLEGAL DATA ON BULK DATA ENTRY %1 ID=%2

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. If you are using the large field format make sure the number of entries is even.

316.5 *** USER FATAL MESSAGE 316 (IFPDRV)

ILLEGAL DATA ON BULK DATA ENTRY %1 ID=%2. A, I1, AND I2 ARE ZERO.

316.6 *** USER FATAL MESSAGE 316 (IFS2P):

ENTRY VIOLATION for BULK DATA ENTRY %1 with SID %2.
String %3 was found in a field that should be empty.

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

316.7 *** USER FATAL MESSAGE 316 (IFPDRV)

ILLEGAL DATA ON BULK DATA ENTRY %1, internal error=%2

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. If you are using the large field format make sure the number of entries is even.

316.8 *** USER FATAL MESSAGE 316,

Field %1 in %2 PID = %3 must be BLANK when ANAL = %4.

User information: Element behavior and Integration scheme must be consistent with analysis type.

317.0 *** USER FATAL MESSAGE 317,

BAD DATA OR FORMAT OR NON-UNIQUE NAME FOR DTI %1 SORTED CARD COUNT =
%2

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

317.1 *** USER FATAL MESSAGE 316 (IFS2P):

Main Index
 36 MSC Nastran Error Messages
Errors 0 - 999

Neither continuation is present nor ND0 is supplied in EIGC with SID=%1

User information: See Remark 3 of EIGC in Bulk Data entry description in the MSC NASTRAN Quick
Reference Guide.

318.0 *** SYSTEM FATAL MESSAGE 318,

NO ROOM IN /XDPL/ FOR DTI %1

System information: Overflow of Data Pool Table. See Chapter 2 of the MSC NASTRAN Programmer's
Manual.

318.1 *** USER FATAL MESSAGE 318,

Illegal character(s) found in name of DMIG %1

User action: Check and modify name field of this entry.

318.2 *** USER FATAL MESSAGE 318,

No header entry found for %2 %1.

User action: Check and add a %2 header entry with name %1.

318.3 *** USER FATAL MESSAGE 318 (IFS2P)

Incorrect precision in field %1 for %2

User action: Check and modify field %1 of %2

318.4 *** USER FATAL MESSAGE 318 (IFS2P)

Discontinuities or identical points at the starting or end point are not allowed in %1 %2

User action: Check and modify starting or end point of %1 %2

318.5 *** USER FATAL MESSAGE 318,

No matrix element entry (Gi, Ci, Ai) found for MDDMIG %1.

User action: Check and add a MDDMIG matrix element entry with name %1.

319.0 *** SYSTEM FATAL MESSAGE 319 (IFPDRV)

Main Index
 MSC Nastran Error Messages 37
Errors 0 - 999

IFP READING EOF ON NPTP.

System information: Unexpected EOF encountered while attempting to read a bulk data entry.

320.0 *** SYSTEM FATAL MESSAGE 320 (IFPTBL)

ERROR ENCOUNTERED PROCESSING BULK DATA.

Programmer Action: INCREASE THE NUMBER OF LIST(S) MXLIST BY %1 WORDS.

320.1 *** SYSTEM FATAL MESSAGE 320 (IFPTBL)

ERROR ENCOUNTERED PROCESSING BULK DATA.

Programmer Action: INCREASE THE DEPTH OF THE LIST(S) MXDEEP BY APPROXIMATELY

%1 WORDS.

320.2 *** SYSTEM FATAL MESSAGE 320 (IFPDRV)

IFP ERROR%1. LAST ENTRY PROCESSED IS %2.
SORTED ENTRY COUNT = %3

System information: Code error in IFP or XSORT.

320.3 *** SYSTEM FATAL MESSAGE 320 (IFPDRV)

CONTINUTATION ENTRIES WITH NO PARENT FOUND.
USE ECHO=SORT to print these continuation entries which show up at the top of the list.

321.0 *** USER FATAL MESSAGE 321 (IFPDRV)

NON-UNIQUE PARAM NAME -%1-

User information: All names of parameters must be unique.

322.0 *** SYSTEM FATAL MESSAGE 322 (IFS9P)

ILLEGAL ENTRY TO IFS1P.

322.1 *** SYSTEM FATAL MESSAGE 322 (IFS8P)

ILLEGAL ENTRY TO IFS8P.

Main Index
 38 MSC Nastran Error Messages
Errors 0 - 999

322.2 *** SYSTEM FATAL MESSAGE 322,

ILLEGAL ENTRY TO IFS7P.

322.3 *** SYSTEM FATAL MESSAGE 322 (IFS6P)

ILLEGAL ENTRY TO IFS6P.

322.4 *** SYSTEM FATAL MESSAGE 322 (IFS5P)

ILLEGAL ENTRY TO IFS5P.

322.5 *** SYSTEM FATAL MESSAGE 322 (IFS4P)

ILLEGAL ENTRY TO IFS4P.

322.6 *** SYSTEM FATAL MESSAGE 322 (IFS3P)

ILLEGAL ENTRY TO IFS3P.

322.7 *** SYSTEM FATAL MESSAGE 322,

ILLEGAL ENTRY TO IFS2P.

322.8 *** SYSTEM FATAL MESSAGE 322 (IFS1P)

ILLEGAL ENTRY TO IFS1P.

System information: IFP code error detected in IFS1P, IFS2P, IFS3P, IFS4P, IFS5P, IFS6P.

322.9 *** SYSTEM FATAL MESSAGE 322 (IFS11P)

INTERNAL ERROR IN IFS11P.

322.10 *** SYSTEM FATAL MESSAGE 322 (IFS11P)

ILLEGAL ENTRY TO IFS11P.

322.11 *** SYSTEM FATAL MESSAGE 322,

ILLEGAL ENTRY TO IFS10P.

322.12 *** USER WARNING MESSAGE 322 (IFS14P)

THE MATM/MATTM ENTRIES ARE NO LONGER SUPPORTED.

User information: USE A MATF OR MATDIGI IN PLACE OF THE MATM/MATTM ENTRIES.

323.0 *** USER FATAL MESSAGE 323 (IXCMDE12)

Main Index
 MSC Nastran Error Messages 39
Errors 0 - 999

Bulk data entry %1 is invalid for this solution sequence (SOL).

User information: %1 is only allowed in SOL %2

323.1 *** USER INFORMATION MESSAGE 395 (IFPS600)

%1 bulk data entry will be ignored.

User information: This entry is only recognized in SOL %2

324.0 *** USER WARNING MESSAGE 324 (XSORSO)

BLANK ENTRIES ENCOUNTERED WILL BE IGNORED.

User information: Blank Bulk Data entries are ignored by NASTRAN.

325.0 *** USER FATAL MESSAGE 325,

BAD DATA OR FORMAT OR NON-UNIQUE NAME. DMI %1 SORTED CARD COUNT = %2

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

326.0 *** SYSTEM FATAL MESSAGE 326,

NO ROOM IN /XDPL/ FOR DMI %1

System information: Overflow of Data Pool Table. See Chapter 2 of the MSC NASTRAN Programmer's
Manual.

327.0 *** USER FATAL MESSAGE 327,

BAD DATA OR FORMAT OR NON-UNIQUE NAME. DMIG %1 SORTED CARD COUNT = %2

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide. Often this is related to simply having the wrong type of input. For example, if the matrix type for
input is declared as double precision, then all values must be of the form x.xxxD+yy, or double precision.

328.0 *** USER WARNING MESSAGE 328 (IFS5P)

Main Index
 40 MSC Nastran Error Messages
Errors 0 - 999

THE ETOL, NCYCLE, AND AUGWEI FIELDS ON SPLINE6 BULK DATA ENTRY ID=%1 WILL
BE IGNORED.

User information: THESE FIELDS ARE IGNORED WHEN METHCON="NODEPROX" WHICH

IS THE DEFAULT.

329.0 *** USER FATAL MESSAGE 329 (IFS3P)

ONLY ONE(1) AXIC ENTRY ALLOWED.

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.
330.0 *** SYSTEM FATAL MESSAGE 330 (IFS3P)
NO ROOM IN MEMORY FOR PARAM ENTRIES.

System information: Change overlay or increase core size.

331.0 *** USER FATAL MESSAGE 331 (IFS3P)

IMPROPER PARAM ENTRY %1 SORTED ENTRY COUNT = %2

User information: See Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

331.1 *** USER FATAL MESSAGE 331 (IFS3P)

Improper %1 entry %2, sorted entry count = %3

User information: Continuation card is not allowed for this entry.

332.0 *** USER FATAL MESSAGE 332 (IFS3P)

AXIC BULK DATA ENTRY REQUIRED.

User information: The presence of any conical shell data entries requires the presence of an AXIC entry.
See the AXIC Bulk Data entry description in chapter 5 of the MSC NASTRAN Quick Reference Guide.

333.0 *** USER WARNING MESSAGE 333 (SEMTRN)

THE BEGIN BULK STATEMENT IS MISSING. A BEGIN BULK STATEMENT WILL BE
INSERTED BY THE PROGRAM

User information: No BEGIN BULK command was found in the input. Check input and add a BEGIN
BULK command.

Main Index
 MSC Nastran Error Messages 41
Errors 0 - 999

334.0 *** USER WARNING MESSAGE 334 (SEMTRN)

THE ENDDATA STATEMENT IS MISSING. AN ENDDATA STATEMENT WILL BE INSERTED
BY THE PROGRAM

User information: No ENDDATA entry was found in the input. Check input and add an ENDDATA
entry.

335.0 *** USER FATAL MESSAGE 335 (CNDRV2)

THE EXPRESSION IN A CONVERT CLAUSE EQUATION HAS INVALID SYNTAX

User Action:
1. REWRITE THE CONVERT CLAUSE EQUATION USING CORRECT SYNTAX
2. RESUBMIT RUN.

335.1 *** USER FATAL MESSAGE 335 (CNDRV2)

THE EXPRESSION IN A CONVERT CLAUSE EQUATION HAS INVALID SYNTAX

User Action:
1. REWRITE THE CONVERT CLAUSE EQUATION USING CORRECT SYNTAX
2. RESUBMIT RUN.

336.0 *** USER WARNING MESSAGE 336 (CNDRV2)

THE VARIABLE ON THE LEFT-SIDE OF A CONVERT CLAUSE EQUATION WAS NOT
FOUND IN THE PRIMARY DATABASE QUALIFIER TABLE

336.1 *** USER FATAL MESSAGE 336 (CNDRV2)

THE VARIABLE ON THE LEFT-SIDE OF A WHERE CLAUSE EQUATION WAS NOT FOUND
IN THE PRIMARY DATABASE QUALIFIER TABLE

337.0 *** USER FATAL MESSAGE 337 (IFS6P)

MORE THAN ONE %1 ENTRY EXISTS. ONLY ONE IS ALLOWED.

User information: Make sure only one such entry exists.

338.0 *** USER WARNING MESSAGE 338 (IFS2P)

Main Index
 42 MSC Nastran Error Messages
Errors 0 - 999

THE LAST X-VALUE ON %1 ENTRY ID = %2 IS MISSING A CORRESPONDING Y-VALUE.

THE LAST X-VALUE WILL BE IGNORED.

User information: There has to be an even number of entries. If there is an odd number, then this message
is issued and the last value ignored.

339.0 *** USER FATAL MESSAGE 339 (MDCASE)

SUBCASE %1 DOES NOT INCLUDE AN ANALYSIS CASE CONTROL COMMAND.

User information: AN ANALYSIS COMMAND MUST BE SPECIFIED FOR EACH SUBCASE.

339.1 *** USER FATAL MESSAGE 339 (MDCASE)

Linear perturbation analysis using an element-based iterative solver method (CASI) is not supported.

User action: Use a matrix-based solver.

339.2 *** USER FATAL MESSAGE 339 (MDCASE)

Frequency-based perturbation analysis using iterative solver method (SMETHOD) is not supported.

User action: Use direct solver.

339.3 *** USER FATAL MESSAGE 339 (MDCASE)

BUCKLING IS NOT SUPPORTED IN MULTISTEP ANALYSIS.

339.4 *** USER FATAL MESSAGE 339 (MDCASE)

NONLINEAR ANALYSIS AFTER PERTURBATION ANALYSIS IS NOT SUPPORTED FOR
ADVANCED ELEMENTS.

339.5 *** USER FATAL MESSAGE 339 (MDCASE)

LINEAR DYNAMIC ANALYSIS IS NOT SUPPORTED FOR ADVANCED ELEMENTS.

339.6 *** USER FATAL MESSAGE 339 (MDCASE)

There is no subcase specified for superelement %1.

User Action: Specify a subcase for this superelement with an ANALYSIS Case Control command.

340.0 *** USER FATAL MESSAGE 340 (MDCASE)

Main Index
 MSC Nastran Error Messages 43
Errors 0 - 999

BOTH MODAL (ANAL = MFREQ) AND DIRECT (ANAL = DFREQ) FREQUENCY ANALYSIS
HAVE BEEN SPECIFIED.

User action: SPECIFY EITHER MODAL OR DIRECT FREQUENCY RESPONSE BUT NOT
BOTH.

341.0 *** USER FATAL MESSAGE 341 (MDCASE)

SUBCASE %1 CONTAINS THE ANALYSIS = %2 COMMAND BUT LACKS THE REQUIRED
METHOD CASE CONTROL COMMAND.

User action: FOR MULTIDISCIPLINARY ANALYSIS THAT REQUIRE A NORMAL MODES OR

BUCKLING SOLUTION, THE METHOD COMMAND MUST BE SPECIFIED AT THE subcase
LEVEL OR ABOVE THE SUBCASE LEVEL.

342.0 *** USER FATAL MESSAGE 342 (MDCASE)

THERE ARE %1 MODAL TRANSIENT SUBCASES.

User information: ONLY ONE MODAL TRANSIENT SUBCASE IS PERMITTED WHEN PER-
FORMING MULTIDISCIPLINARY ANALYSIS.

343.0 *** USER FATAL MESSAGE 343 (MDCASE)

THERE ARE MULTIPLE DESGLB COMMANDS IN THE CASE CONTROL SECTION.

User information: ONLY ONE DESGLB COMMAND IS PERMITTED.

343.1 *** USER FATAL MESSAGE 343 (MDCASE)

THERE ARE MULTIPLE DESOBJ COMMANDS IN THE CASE CONTROL SECTION.

User information: ONLY ONE DESOBJ COMMAND IS PERMITTED.

344.0 *** USER FATAL MESSAGE 344 (MDCASE)

DESGLB COMMAND = %1 IN SUBCASE = %2 IS DIFFERENT THAN THE PREVIOUS SUB-
CASE

User information: SPECIFY THE DESGLB COMMAND ABOVE THE SUBCASE LEVEL.

Main Index
 44 MSC Nastran Error Messages
Errors 0 - 999

345.0 *** USER FATAL MESSAGE 345 (IFS1P)

FACE TYPE %1 IS INVALID ON THE QHBDY ENTRY.

346.0 *** USER FATAL MESSAGE 346 (IFS1P)

AN AREA FACTOR IS SPECIFIED FOR AN INAPPROPRIATE FACE TYPE = %1.

User information: AREA FACTOR IS PERMITTED FOR TYPE = POINT AND LINE ONLY.

347.0 *** USER FATAL MESSAGE 347 (IFS1P)

AN INVALID, OR NO, AREA FACTOR IS SPECIFIED FOR FACE TYPE = %1.

348.0 *** USER FATAL MESSAGE 348 (MDCASE)

THE ANALYSIS=MODES SUBCASE(S) DOES NOT INCLUDE A DESSUB COMMAND.

User information: SPECIFY THE DESSUB COMMAND IN ALL SUPERELEMENT AND RESID-
UAL SUBCASES WITH ANALYSIS=MODES.

349.0 *** USER FATAL MESSAGE 349 (MDCASE)

THERE ARE %1 COMPLEX EIGENVALUE SUBCASES.

User information: ONLY ONE COMPLEX EIGENVALUE SUBCASE, DCEIG OR MCEIG, IS PER-
MITTED.

350.0 *** USER FATAL MESSAGE 350 (IFS350)

THE FOLLOWING GRID OR SCALAR POINTS ARE SPECIFIED MORE THAN ONCE ON THE
BULK DATA ENTRY SHOWN BELOW:

350.1 *** USER FATAL MESSAGE 350 (IFS350)

THE FOLLOWING GRID/SCALAR POINT - COMPONENT IS SPECIFIED MORE THAN ONCE
ON THE BULK DATA ENTRY SHOWN BELOW:

351.0 *** USER FATAL MESSAGE 351 (MDCASE)

SUBCASE %1 CONTAINS A STATSUB = %2 COMMAND WITH ANALYSIS = %3.

User information: ONLY ANALYSIS = BUCKLING IS SUPPORTED WITH STATSUB.

User action: REMOVE THE STATSUB REQUEST WHEN ANALYSIS = %3 IS USED.

351.1 *** USER FATAL MESSAGE 351 (MDCASE)

Main Index
 MSC Nastran Error Messages 45
Errors 0 - 999

SUBCASE %1 CONTAINS A STATSUB = %2 COMMAND WITH A PRELOAD OPTION.

User information: STATSUB(PRELOAD) IS NOT SUPPORTED.

User action: REMOVE THE STATSUB(PRELOAD) REQUEST.

351.2 *** USER FATAL MESSAGE 351 (MDCASE)

SUBCASE %1 CONTAINS A MODTRAK = %2 COMMAND WITH ANALYSIS = %3.

User information: ONLY ANALYSIS = MODES IS SUPPORTED WITH MODTRAK.

User action: REMOVE THE MODTRAK REQUEST WHEN ANALYSIS = %3 IS USED.

352.0 *** USER FATAL MESSAGE 352 (MDCASE)

SUBCASE %1 CONTAINS A SUPER = %2 COMMAND WITH ANALYSIS TYPE FLUTTER AND
HAS A DESSUB = %3 REQUEST.

User information: FLUTTER CONSTRAINTS CANNOT BE APPLIED ON UPSTREAM

SUPERELEMENTS.

User action: REMOVE THE DESSUB REQUESTS FROM SUBCASES ASSOCIATED WITH
UPSTREAM SUPERELEMENTS.

353.0 *** USER FATAL MESSAGE 353 (IFPESO)

THE EXTID KEYWORD IS NOT SPECIFIED IN THE EXTSEOUT or EXTMDOUT CASE CON-
TROL COMMAND.

User information: THE EXTID KEYWORD MUST BE SPECIFIED IN THE EXTSEOUT or

EXTMDOUT CASE CONTROL COMMAND IF ONE OR MORE OF THE ASMBULK, EXT-
BULK, MATRIXOP4/MATOP4 OR DMIGPCH OPTIONS ARE SPECIFIED.

353.1 *** USER FATAL MESSAGE 353 (IFPESO)

On THE EXTSEOUT (or EXTMDOUT) CASE CONTROL COMMAND a SUPERELEMENT (or
Module) ID IS NOT SPECIFIED FOR THE EXTID KEYWORD.

353.2 *** USER FATAL MESSAGE 353 (IFPESO)

Main Index
 46 MSC Nastran Error Messages
Errors 0 - 999

ON THE EXTSEOUT (or EXTMDOUT) CASE CONTROL COMMAND A UNIT NUMBER IS

NOT SPECIFIED FOR THE DMIGOP2 OR MATRIXOP4/MATOP4 KEYWORD.

353.3 *** USER FATAL MESSAGE 353 (IFPFRF)

A COMPONENT ID IS NOT SPECIFIED FOR THE COMPID KEYWORD.

353.4 *** USER FATAL MESSAGE 353 (IFPFRF)

A COMPONENT NAME IS NOT SPECIFIED FOR THE COMPNAME KEYWORD.

353.5 *** USER FATAL MESSAGE 353 (IFPFRF)

A SET ID IS NOT SPECIFIED FOR THE CONNPTS KEYWORD.

353.6 *** USER FATAL MESSAGE 353 (IFPFRF)

A VALUE IS NOT SPECIFIED FOR THE %1 KEYWORD.

353.7 *** USER FATAL MESSAGE 353 (IFPFRF)

A UNIT NUMBER IS NOT SPECIFIED FOR THE %1 KEYWORD.

353.8 *** USER FATAL MESSAGE 353 (IFPFRF)

THE CONNPTS KEYWORD IS NOT SPECIFIED IN THE FRF CASE CONTROL COMMAND.

User information: THE CONNPTS KEYWORD MUST BE SPECIFIED IN THE FRF CASE
CONTROL COMMAND IF THE COMPID KEYWORD OR THE COMPNAME KEYWORD IS
SPECIFIED.

353.9 *** USER FATAL MESSAGE 353 (IFPFRF)

ONLY ONE OF THE %1, %2 OR %3 KEYWORDS MAY BE SPECIFIED IN THE FRF CASE CON-
TROL COMMAND

353.10 *** USER FATAL MESSAGE 353 (IFPFRF)

THE COMPNAME KEYWORD IS NOT SPECIFIED IN THE FRF CASE CONTROL COM-
MAND.

User information: THE COMPNAME KEYWORD MUST BE SPECIFIED IN THE FRF CASE CON-
TROL COMMAND IF THE COMPID KEYWORD IS SPECIFIED.

353.11 *** USER FATAL MESSAGE 353 (IFPFRF)

Main Index
 MSC Nastran Error Messages 47
Errors 0 - 999

THE COMPID KEYWORD IS NOT SPECIFIED IN THE FRF CASE CONTROL COMMAND.

User information: THE COMPID KEYWORD MUST BE SPECIFIED IN THE FRF CASE
CONTROL COMMAND IF THE COMPNAME KEYWORD IS SPECIFIED.

353.12 *** USER FATAL MESSAGE 353 (IFPFRF)

THE ICFAUTO KEYWORD MAY NOT BE SPECIFIED IN CONJUNCTION WITH THE
ICFGEN OR ICFUSE KEYWORD IN THE FRF CASE CONTROL COMMAND

354.0 System Fatal Message 354(IFP1D)

A DSAPRT COMMAND APPEARS IN A SUBCASE SUBSEQUENT TO THE FIRST SUBCASE.

User action: SPECIFY THE COMMAND IN EITHER THE FIRST SUBCASE OR ABOVE ALL
SUBCASES.

355.0 *** USER FATAL MESSAGE 355 (IFP1)

The number of PARAM Bulk Data entries allowed in a STEP case has been exceeded.

User information: The maximum number allowed is 100.

356.0 User Fatal Message 356(IFP1D)

AN SEALL, SEMG, SELG, SELR, SEKR, and/or SEMR COMMAND APPEARS IN A SUBCASE
SUBSEQUENT TO THE FIRST SUBCASE.

User information: SPECIFY THE COMMAND IN EITHER THE FIRST SUBCASE OR ABOVE ALL
SUBCASES.

356.1 User Fatal Message 356

The %1 command must appear in or above the first %2.

356.2 User Fatal Message 356

There is no %1 command in or above the first SUBSTEP.

356.3 User Fatal Message 356

The %1 command must appear above the first %2.

Main Index
 48 MSC Nastran Error Messages
Errors 0 - 999

356.4 User Fatal Message 356

There is no %1 command above the first SUBSTEP.

357.0 *** User Warning Message 357

ANALYSIS type %1 is not supported in SOL 400 Coupled Analysis.

358.0 *** USER FATAL MESSAGE 358 (MDCASE)

General contact (BCTABLE or BCONPRG entry with IGLUE=0) is being requested for a linear analysis
which is not supported.

User action: Use permanently glued contact by specifying a valid value for IGLUE on the BCTABLE or
BCONPRG entry.

359.0 *** user fatal message 359 (mdcasenl)

EXTSEOUT or EXTMDOUT is specified in a nonlinear SUBCASE or STEP. EXTSEOUT or
EXTMDOUT may only be specified in a linear perturbation STEP or linear analysis SUBCASE.

370.0 *** SYSTEM FATAL MESSAGE 370 (IFP3EM)

AXIC FILE RECORD FOR ENTRY(%1) NOT OF LENGTH = TO ENTRY MULTIPLES + 3.
RECORD HEADER =%2

371.0 *** USER FATAL MESSAGE 371 (IFP3EM)

%1 ID = %2 IS OUTSIDE THE PERMISSIBLE RANGE: 1 THROUGH 9999.

372.0 *** USER FATAL MESSAGE 372 (IFP3EM)

MINIMUM PROBLEM REQUIRES %1 ENTRY, NONE FOUND.

373.0 *** USER FATAL MESSAGE 373 (IFP3EM)

RING ID =%1 ON ENTRY TYPE (%2) IS OUTSIDE THE ALLOWABLE RANGE: 1 THROUGH
%3.

374.0 *** SYSTEM FATAL MESSAGE 374 (IFP3EM)

INCONSISTENCY, AXIC TRAILER BIT IS ON, BUT RECORD COULD NOT BE FOUND BY
LOCATE. RECORD HEADER =%1

375.0 *** USER FATAL MESSAGE 375 (IFP3EM)

HARMONIC NUMBER =%1 ON ENTRY TYPE (%2) IS OUTSIDE THE ALLOWABLE RANGE: 0
THROUGH %3.

Main Index
 MSC Nastran Error Messages 49
Errors 0 - 999

376.0 *** SYSTEM FATAL MESSAGE 376 (IFP3EM)

INCONSISTENT ERROR READING BALANCE OF %1%2 ENTRIES.

377.0 *** SYSTEM FATAL MESSAGE 377 (IFP3EM)

RECORD INCONSISTENCY FOR %1%2 ENTRIES

378.0 *** USER FATAL MESSAGE 378 (IFP3EM)

SPCAX OR MPCAX ENTRY HAS A SETID = 101 OR 102.

User information: 101 AND 102 ARE SPECIAL SETS RESERVED FOR SINE AND COSINE SETS.

379.0 *** USER FATAL MESSAGE 379 (IFP3EM)

RINGAX ENTRY WITH RING ID = %1 HAS A ZERO RADIUS SPECIFIED.

380.0 *** USER FATAL MESSAGE 380 (IFP3EM)

ENTRY TYPE %1 HAS BAD COMPONENT SPECIFICATION OF %2

381.0 *** SYSTEM FATAL MESSAGE 381 (IFP3EM)

AXIC TRAILER BIT ON BUT LOCATE CAN NOT FIND POINTAX OR SECTAX ENTRY.

382.0 *** USER FATAL MESSAGE 382 (IFP)

AN INVALID BULK DATA ENTRY HAS BEEN SPECIFIED FOR AXI-SYMMETRIC CONICAL
SHELL ANALYSIS

383.0 *** USER WARNING MESSAGE 383 (IFS8P)

NO ORIENTATION IS SPECIFIED FOR CHBDYP ELEMENT %1

384.0 *** USER FATAL MESSAGE 384 (IFS1P)

THE LOWER RANGE FREQUENCY ,F1, IS LESS THAN 0.0 HZ.

385.0 *** USER FATAL MESSAGE 385 (IFS1P)

THE UPPER RANGE FREQUENCY ,F2, IS LESS THAN THE LOWER RANGE FREQUENCY.

386.0 *** USER FATAL MESSAGE 386 (IFS3P)

Main Index
 50 MSC Nastran Error Messages
Errors 0 - 999

THE UD MATRIX INPUT ON THE GENEL ENTRY ID= %1 DOES NOT HAVE SIX AND ONLY
SIX DEGREES-OF-FREEDOM.

User information: IF THE S MATRIX IS NOT SPECIFIED THEN UD MUST HAVE SIX AND
ONLY SIX DEGREES-OF_FREEDOM.

387.0 *** USER FATAL MESSAGE 387 (IFS1P)

THE FREQUENCY SPREAD ,FSPD, ON FREQ4 ENTRY %1 IS LESS THAN OR EQUAL TO 0.0
OR GREATER THAN 1.0.

388.0 *** USER FATAL MESSAGE 388 (IFS1P)

THE NUMBER OF FREQUENCIES ,NFM, ON FREQ4 ENTRY %1 IS LESS THAN 1.

389.0 *** USER FATAL MESSAGE 389 (IFS1P)

ONE OR MORE FRACTIONS ,FRI, ON FREQ5 ENTRY %1 ARE LESS THAN 0.0

390.0 *** USER FATAL MESSAGE 390 (IFSEGL)

FIELD %1 ON EIGRL ENTRY, SID = %2 IS SPECIFIED MORE THAN ONCE.

390.1 *** USER FATAL MESSAGE 390 (IFSEGC)

FIELD %1 ON EIGC ENTRY, SID = %2 IS SPECIFIED MORE THAN ONCE.

391.0 *** USER FATAL MESSAGE 391 (XSDFF)

%1
THE COMMA-DELIMITED FREE-FIELD FORMAT IS NOT ALLOWED FOR THE ABOVE
ENTRY.

User information: REWRITE ENTRY WITH FIXED FORMAT IN FIELDS 1, 2, AND 10. FIELDS 3
THROUGH 9 ARE TREATED AS ONE CONTIGUOUS FIELD.

392.0 *** USER FATAL MESSAGE 392 (XSORSO)

THE AUXMID OR SEID ON THE FOLLOWING BEGIN BULK COMMAND IS NOT GREATER
THAN 0.
BULK ENTRY: %1

User information: THIS ERROR MAY OCCURE DUE TO BULK DATA ENTRIES BEING
DEFINED BEFORE THE "BEGIN BULK" STATEMENT.

393.0 *** USER FATAL MESSAGE 393 (IFS2P)

Main Index
 MSC Nastran Error Messages 51
Errors 0 - 999

ON MAT8 ID = %1, ONLY ONE OR TWO OF Xt, Yt AND S ARE SPECIFIED.

User action: SPECIFY VALUES FOR Xt, Yt AND S IF ANY OF Xt, Xc, Yt, Yc, AND S ARE SPECI-
FIED.

394.0 *** USER WARNING MESSAGE 394 (IFS5P)

INCONSISTENT OPTIONS FOR LOAD TYPE AND SCALE FACTOR ARE SPECIFIED ON
PLOAD1 BULK ENTRY = %1 .

User information: THE SCALE FACTOR = %2 IS IGNORED WHEN A LOAD TYPE = %3, BASED
ON ELEMENT COORDINATES IS USED.

396.0 *** USER WARNING MESSAGE 396 (GETLIN)

ENDDATA FOUND AT RECORD NUMBER %3 IN %1 FILE '%2'
ALL BULK DATA ENTRIES AFTER THIS ENTRY WILL BE IGNORED.

397.0 *** USER FATAL MESSAGE 397 (GETLIN)

THE INPUT FILE INCLUDE NEST DEPTH (= %1) HAS BEEN EXCEEDED.
FILE '%2' IS INCLUDED IN FILE '%3' AT RECORD NUMBER %4.
THE INCLUDE REQUEST IS SKIPPED.

398.0 *** USER FATAL MESSAGE 398 (GETLIN)

A REQUESTED %1 FILE WAS NOT FOUND.
FILE '%2' IS INCLUDED IN FILE '%3' AT RECORD NUMBER %4. THE INCLUDE REQUEST IS
SKIPPED.

398.1 *** USER FATAL MESSAGE 398 (GETLIN)

NO FILE NAME SPECIFIED ON %1 STATEMENT.
STATEMENT IS INCLUDED IN FILE '%3' AT RECORD NUMBER %4. THE INCLUDE
REQUEST IS SKIPPED.

398.2 *** USER FATAL MESSAGE 398 (GETLIN)

Main Index
 52 MSC Nastran Error Messages
Errors 0 - 999

FILE NAME SPECIFIED ON %1 STATEMENT EXCEEDS MAXIMUM ALLOWABLE LENGTH

OF %2
FILE '%3' IS INCLUDED IN FILE '%4' AT RECORD NUMBER %5. THE INCLUDE REQUEST IS
SKIPPED.

398.3 *** USER FATAL MESSAGE 398 (GETLIN)

END-OF-FILE ENCOUNTERED WHILE BUILDING %1 FILE NAME.
PARTIAL FILENAME '%2' IS INCLUDED IN FILE '%3' AT RECORD NUMBER %4. THE
INCLUDE REQUEST IS SKIPPED.

398.4 *** USER FATAL MESSAGE 398 (GETLIN)

SYNTAX ERROR FOUND AT COLUMN %2 IN SUBDIRECTORY SEARCH REQUEST IN %1
FILE NAME.
FILENAME '%3' IS SPECIFIED IN FILE '%4' AT RECORD NUMBER %5. THE INCLUDE
REQUEST IS SKIPPED.

399.0 *** USER FATAL MESSAGE 399 (GETLIN)

OPEN FOR %1 FILE FAILED. ERROR FLAG = %2, ERROR CODE = %3.
ERROR MESSAGE IS '%4'
FILE '%5' IS INCLUDED IN FILE '%6' AT RECORD NUMBER %7. THE INCLUDE REQUEST IS
SKIPPED.

400.0 *** SYSTEM FATAL MESSAGE 400 (CTYPE)

THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE TYPE CARD

User action: NOTIFY HEXAGON AB AS SOON AS POSSIBLE.

400.1 *** SYSTEM FATAL MESSAGE 400 (CSUBDM)

THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE SUBDMAP
CARD

User action: NOTIFY HEXAGON AB.

400.2 *** SYSTEM FATAL MESSAGE 400 (CEPMSG)

THE COMPILER HAS BECOME LOST, DURING PROCESSING OF THE ABOVE %1 CAR

** User action:
1. NOTIFY HEXAGON AB AS SOON AS POSSIBLE.
2. CHANGE %2 STATEMENT TO %3 STATEMENTS

Main Index
 MSC Nastran Error Messages 53
Errors 0 - 999

400.3 *** SYSTEM FATAL MESSAGE 400 (CEPMSG)

THE NUMBER OF DATA BLOCKS ON THE %1 CARD EXCEEDS THE MAXIMUM (%2 )
ALLOWED

401.0 *** SYSTEM FATAL MESSAGE 401 (CGVPST)

NUMBER OF NDDL PARAMETERS EXCEEDS THE MAXIMUM ALLOWED OF %1

401.1 *** SYSTEM FATAL MESSAGE 401 (CGVPST)

NUMBER OF PARAMETER ARGUMENTS EXCEEDS THE MAXIMUM ALLOWED OF %1

402.0 *** USER FATAL MESSAGE 402 (CTYPE)

%1 WAS DETECTED WHEN %2 WAS EXPECTED

User action: ADD CORRECT %3 AND RECOMPILE

402.1 *** USER FATAL MESSAGE 402 (CSUBDM)

%1 WAS DETECTED WHEN THE SUBDMAP NAME WAS EXPECTED

User action: ADD SUBDMAP NAME AND RECOMPILE

402.2 *** USER FATAL MESSAGE 402 (CTYPE)

%1 WAS DETECTED WHEN %2 WAS EXPECTED

User action: ADD CORRECT %3 AND RECOMPILE

User information: VALID SCOPE IDENTIFIERS ARE "NDDL" AND " "

402.3 *** USER FATAL MESSAGE 402 (CTYPE)

%1 WAS DETECTED WHEN %2 WAS EXPECTED

User action: ADD CORRECT %3 AND RECOMPILE

User information: VALID PARAMETER TYPE CODES ARE "I", "RS", "CHAR", "RD", "CS", "CD",
"LOGI", "RX", OR "CX"

Main Index
 54 MSC Nastran Error Messages
Errors 0 - 999

402.4 *** USER FATAL MESSAGE 402 (CTYPE)

%1 WAS DETECTED WHEN %2 WAS EXPECTED

User action: ADD CORRECT %3 AND RECOMPILE

User information: VALID AUTHORIZATION CODES ARE "Y", "N", OR " "

402.5 *** USER FATAL MESSAGE 402 (CTYPE)

%1 WAS DETECTED WHEN %2 WAS EXPECTED

User action: ADD CORRECT %3 AND RECOMPILE

User information: VALID IDENTIFIER KEYWORDS ARE "PARM" AND "DB"

403.0 *** USER FATAL MESSAGE 403 (CSUBDM)

A numeric value was detected at %1 position %2 in the SUBDMAP statement's argument list but a %3
dollar, or %4 name was expected.

User action: Remove the numeric value or replace with a valid %4 name.

404.0 *** USER FATAL MESSAGE 404 (CTYPE)

A NON-%1 DELIMITER WAS DETECTED WHERE A %2 DELIMITER IS REQUIRED

404.1 *** USER FATAL MESSAGE 404 (CSUBDM)

An invalid character was detected at %1 position %2 in the SUBDMAP statement's argument list but a %3
dollar, or %4 name was expected.

User action: Remove the invalid character or replace with a valid %4 name.

User information: This message can result when the default value of a real or complex parameter is speci-
fied to be a letter instead of a number. A common occurrence of this is using the letter "O" in place of the
number "0".

404.2 *** USER FATAL MESSAGE 404 (CTYPE)

AN INVALID DELIMITER IS DETECTED IN THE TYPE PARM STATEMENT.

404.3 *** USER FATAL MESSAGE 404 (CSUBDM)

The constant %1 is specified at position %2 in the subDMAP's statement's parameter list. This parameter
is a built-in constant and must not be specified in a subDMAP statement's parameter list.

Main Index
 MSC Nastran Error Messages 55
Errors 0 - 999

405.0 *** SYSTEM FATAL MESSAGE 405 (CSUBDM)

THE NUMBER OF WORDS ALLOCATED FOR PROCESSING THIS SUBDMAP'S %1 HAS
BEEN EXCEEDED. THE MAXIMUM IS %2 WORDS

User action: EACH NAME USES 2 WORDS. REDUCE THE NUMBER OF %3 AND
RESUBMIT

Programmer action: ENLARGE COUNTER %4 AND ARRAY DIMENSION FOR %5

406.0 *** USER FATAL MESSAGE 406 (NDDL)

INVALID DATA TYPE CODE %1.
VALID DATA TYPE CODES ARE "I", "RS", "CHAR", "RD", "CS", "CD", "LOGI", "RX", "CX",
"PC4" OR "PC5"

406.1 *** USER FATAL MESSAGE 406

INVALID PARAMETER TYPE CODE %1.
VALID PARAMETER TYPE CODES ARE "I", "RS", "CHAR", "RD", "CS", "CD", "LOGI", "RX", OR
"CX"

406.2 *** USER FATAL MESSAGE 406 (CTYPE)

INVALID IDENTIFIER KEYWORD %1.
VALID IDENTIFIER KEYWORDS ARE "PARM" AND "DB"

406.3 *** USER FATAL MESSAGE 406 (CTYPE)

INVALID USER AUTHORIZATION CODE %1.
VALID AUTHORIZATION CODES ARE "Y", "N", OR " "

406.5 *** USER FATAL MESSAGE 406 (CTYPE)

INVALID VARIABLE SCOPE IDENTIFIER %1.
VALID SCOPE IDENTIFIERS ARE "NDDL" AND " "

406.6 *** SYSTEM WARNING MESSAGE 406 (FORTIO)

INVALID PARAMETER CLOSE OPTION CODE %1.
VALID PARAMETER OPERATION CODES ARE 1 (REWIND), 2 (CLOSE/KEEP), AND 3
(CLOSE/DELETE)

Main Index
 56 MSC Nastran Error Messages
Errors 0 - 999

406.7 *** SYSTEM WARNING MESSAGE 406 (FORTIO)

INVALID PARAMETER OPERATION CODE %1.
VALID PARAMETER OPERATION CODES ARE "OPEN" OR "CLOSE"

406.8 *** SYSTEM FATAL MESSAGE 406 (ZRDBLK)

INVALID INTERNAL NDDL DATA CODE %1 PROCESSING RECORD %2 OF DATABLOCK
%3
VALID INTERNAL NDDL DATA CODES ARE 1 THROUGH 10

406.9 *** SYSTEM FATAL MESSAGE 406 (ZRDBLK)

INVALID INTERNAL NDDL DATA CODE %1 PROCESSING RECORD %2 OF DATABLOCK
%3
VALID INTERNAL NDDL DATA CODES ARE 1 THROUGH 10
INTERNAL NDDL DATA CODE 11 GENERALLY INDICATES AN NDDL COMPILATION
ERROR USING THE "SAMEAS" OPTION VERIFY RECORDS DESCRIBED AS "SAMEAS"
APPEAR AFTER THE REFERENCED "SAMEAS" RECORD

406.10 *** SYSTEM FATAL MESSAGE 406 (PRGWHRX)

INVALID INTERNAL OPERATION CODE %1 IN %2 %3 %4 PROCESSING.

407.0 *** USER FATAL MESSAGE 407 (CTYPE)

USER AUTHORIZATION FIELD IS MISSING ON ABOVE TYPE STATEMENT

User information: All "TYPE PARM" statements require a "Y" or "N" authorization code.

408.0 *** USER WARNING MESSAGE 408 (CTYPE)

PARAMETER %1 HAS BEEN PREVIOUSLY DEFINED TO THE VPS (PARAMETER) TABLE.
THIS DEFINITION IS IGNORED.

User information: THIS PARAMETER MAY BE EITHER A PERMANENT VPS TABLE ENTRY, OR
DEFINED BY A PREVIOUS TYPE STATEMENT.

User information: User is attempting to define a parameter twice.

409.0 *** USER WARNING MESSAGE 409 (CTYPE)

THE PARAMETER %1 IS IGNORED BECAUSE IT HAS BEEN PREVIOUSLY DEFINED IN A
TYPE DMAP STATEMENT

Main Index
 MSC Nastran Error Messages 57
Errors 0 - 999

410.0 *** USER WARNING MESSAGE 410 (CTYPE)

DEFAULT VALUE IGNORED FOR NDDL TYPED PARAMETER %1. DEFAULTS MUST BE SET
IN THE NDDL WITH THE NDDL PARAM STATEMENT.

411.0 *** USER FATAL MESSAGE 411 (CTYPE)

THE VALUE ASSIGNED TO ONE OF THE PARAMETERS ON THIS TYPE STATEMENT IS
INCONSISTENT WITH REQUESTED %1 TYPE CODE

411.1 *** USER FATAL MESSAGE 411 (CTYPE)

THE '%1' VALUE ASSIGNED TO THE PARAMETER %2 ON THIS TYPE STATEMENT IS
INCONSISTENT WITH REQUESTED '%3' TYPE CODE

412.0 *** SYSTEM FATAL MESSAGE 412 (CTYPE)

THE NUMBER OF WORDS ALLOCATED FOR PROCESSING TYPED PARAMETERS HAS
BEEN EXCEEDED. THE MAXIMUM IS %1 WORDS

User action: EACH PARAMETER USES 2 WORDS. REDUCE THE NUMBER OF PARAMETERS
AND RESUBMIT

Programmer action: ENLARGE COUNTER MAXPRM AND ARRAY DIMENSION FOR PARAMS

413.0 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND BCD VALUE WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1 CARD

413.1 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND NUMERIC VALUE WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1
CARD

413.2 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND END-OF-CARD WHEN EXPECTING DELIMITER, DURING PROCESSING OF %1
CARD

413.3 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND BCD VALUE WHEN EXPECTING DELIMITER OR END-OF-CARD, DURING PRO-
CESSING OF ABOVE %1 CARD

Main Index
 58 MSC Nastran Error Messages
Errors 0 - 999

413.4 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND NUMERIC VALUE WHEN EXPECTING DELIMITER OR END-OF-CARD, DURING
PROCESSING OF ABOVE %1 CARD

413.5 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND NUMERIC VALUE WHEN EXPECTING DATA BLOCK NAME, DURING PROCESS-
ING OF %1 CARD

413.6 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND END-OF-CARD WHEN EXPECTING DATA BLOCK NAME, DURING PROCESSING
OF %1 CARD

413.7 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND NUMERIC VALUE WHEN EXPECTING DATA BLOCK NAME OR DELIMITER,
DURING PROCESSING OF %1 CARD

413.8 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND END-OF-CARD WHEN EXPECTING DATA BLOCK NAME OR DELIMITER,
DURING PROCESSING OF ABOVE %1 CARD

413.9 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND NUMERIC VALUE WHEN EXPECTING PARAMETER NAME, DURING PROCESSING
OF %1 CARD

413.10 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND END-OF-CARD WHEN EXPECTING PARAMETER NAME, DURING PROCESSING
OF %1 CARD

413.11 *** USER FATAL MESSAGE 413 (CEPMSG)

FOUND NUMERIC VALUE WHEN EXPECTING PARAMETER NAME, DELIMITER, OR END-
OF-CARD, WHILE PROCESSING %1 CARD

414.0 *** SYSTEM FATAL MESSAGE 414 (CEPMSG)

DMAP INSTRUCTION %1 NOT FOUND IN DMAP LIBRARY

** User action: NOTIFY HEXAGON AB.

415.0 *** USER FATAL MESSAGE 415 (CEPMSG)

Main Index
 MSC Nastran Error Messages 59
Errors 0 - 999

%1 DMAP INSTRUCTION REQUIRES AT LEAST TWO DATA BLOCKS

416.0 *** USER FATAL MESSAGE 416 (CEPMSG)

NO DATA BLOCK NAME(S) SPECIFIED ON THIS %1 CARD

418.0 *** USER FATAL MESSAGE 418 (CEPMSG)

DATA BLOCK NAME(S) AND PARAMETER NAME NOT DELIMITED BY '/' ON %1 CARD

419.0 *** USER FATAL MESSAGE 419 (CEPMSG)

NO PARAMETER NAME SPECIFIED ON THIS %1 CARD

420.0 *** USER FATAL MESSAGE 420 (CEPMSG)

EXTRANEOUS DATA FOUND AFTER PARAMETER NAME, BUT BEFORE DELIMITER OR
END-OF-CARD. DATA IS IGNORED FOR THIS %1 STATEMENT

421.0 *** USER FATAL MESSAGE 421 (CEPMSG)

USE OF 'S,Y', 'S,N', 'V,N', OR 'V,Y' IS INVALID FOR PARAMETERS USED ON %1
STATEMENTS

** User action: REMOVE INVALID SYNTAX AND RERUN

421.1 *** USER FATAL MESSAGE 421 (CEPMSG)

USE OF 'S' OR 'V' IS INVALID FOR PARAMETERS USED ON %1 STATEMENTS

User action: REMOVE INVALID SYNTAX AND RERUN

422.0 *** SYSTEM INFORMATION MESSAGE 422 (CEPMSG)

FOR COMPILATION PURPOSES %1 WILL BE USED AS THE PARAMETER NAME FOR THIS
%2 STATEMENT

423.0 *** USER FATAL MESSAGE 423 (ATTDBS)

Main Index
 60 MSC Nastran Error Messages
Errors 0 - 999

THE FOLLOWING PHYSICAL FILE DOES NOT EXIST

%1
THIS FILE IS A PART OF THE M A S T E R DBSET OF THE DELIVERY DATABASE BEING
ATTACHED TO THIS RUN.

User information: The MASTER dbset is required for all runs which use an existing database. If the MAS-
TER has been allocated to several physical files, then all of these files must be available for all runs using the
database set. Also, see Error Reports 3652 in section 17.2 of MSC NASTRAN Reference Manual.

424.0 *** USER FATAL MESSAGE 424 (CEXPRS)

THE EXPRESSION FOUND IN AN IF, DO WHILE, OR WHERE STATEMENT IS NOT
ENCLOSED IN PARENTHESES.

User information: First check that the expression is enclosed in parentheses. If it is, then check the offend-
ing statement for syntax. It is possible that the expression has been improperly entered.

425.0 *** USER FATAL MESSAGE 425 (MODXTR) -

TOO MANY CONTINUATION CARDS DETECTED ON A %1 STATEMENT.
INVALID CONTINUATION CARD IMAGE IS: %2

User action: SIMPLIFY EXPRESSION.

User information: MAXIMUM ALLOWABLE NUMBER OF CONTINUATIONS IS %3 CARD

IMAGES, OR %4 CHARACTERS.

425.1 *** USER FATAL MESSAGE 425

TOO MANY CONTINUATION CARDS DETECTED ON AN IF OR A DO WHILE STATE-
MENT, OR ON A DBVIEW WHERE CLAUSE.
INVALID CONTINUATION CARD IMAGE IS: %1

User action: SIMPLIFY EXPRESSION.

User information: MAXIMUM ALLOWABLE NUMBER OF CONTINUATIONS IS 6 CARD

IMAGES, OR 432 CHARACTERS.

426.0 *** USER FATAL MESSAGE 426 (XTRLEF)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE %1 COMMAND
%2

Main Index
 MSC Nastran Error Messages 61
Errors 0 - 999

426.1 *** USER FATAL MESSAGE 426 (XCSOL2)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE SOL EXECUTIVE CONTROL
COMMAND
%1

426.2 *** USER FATAL MESSAGE 426 (XCSACM)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE COMPILE EXECUTIVE CONTROL
COMMAND
%1

426.3 *** USER FATAL MESSAGE 426 (RDUPDT)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBUPDATE EXECUTIVE
CONTROL COMMAND
%1

426.4 *** USER FATAL MESSAGE 426 (RDSECU)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE SECURITY COMMAND
%1

426.5 *** USER FATAL MESSAGE 426 (RDREST)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE RESTART COMMAND
%1

426.6 *** USER FATAL MESSAGE 426 (RDPROJ)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE PROJECT COMMAND
%1

426.7 *** USER FATAL MESSAGE 426 (RDINIT)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE INIT EXECUTIVE CONTROL
COMMAND
%1

426.8 *** USER FATAL MESSAGE 426 (RDFIX)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBFIX COMMAND
%1

Main Index
 62 MSC Nastran Error Messages
Errors 0 - 999

426.9 *** USER FATAL MESSAGE 426 (RDEXPN)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR EXPAND EXECUTIVE CONTROL
COMMAND
%1

426.10 *** USER FATAL MESSAGE 426 (RDDIRP)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR DBDIR EXECUTIVE CONTROL
COMMAND
%1

426.11 *** USER FATAL MESSAGE 426 (RDDBCL)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE DBCLEAN EXECUTIVE CONTROL
COMMAND.
%1

426.12 *** USER FATAL MESSAGE 426 (IFSLFT)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL OR REPEATED ON THE %1 BULK ENTRY
%2

426.13 *** USER FATAL MESSAGE 426 (CHKSTR)

THE FOLLOWING KEYWORD(S) ARE ILLEGAL FOR THE %1 COMMAND.
%2

427.0 *** SYSTEM FATAL MESSAGE 427 (CLOPBK)

THE LOPBLK TABLE HAS EXCEEDED ITS MAXIMUM %1 NUMBER OF ENTRIES

User information: THIS TABLE CONTAINS THE SCRATCH DATABLOCKS TO BE DELETED

AT THE TOP OF EACH LOOP)

User action: USE FILE=SAVE OPTION TO SAVE THE SCRATCH DATABLOCK OUTPUT
INSIDE LOOPS. NOTIFY HEXAGON AB OF THIS ERROR.

Programmer action: INCREASE TABLE SIZE OF LOPBLK AND LOPMAX.

428.0 *** USER FATAL MESSAGE 428 (COSGEN)

ALTER %1 IS OUT OF RANGE. LAST DMAP NUMBER IS %2

User information: When modifying a DMAP using Alter statements, the line numbers on the Alter
statement must be within the range of the line numbers of the DMAP being modified.

Main Index
 MSC Nastran Error Messages 63
Errors 0 - 999

428.1 *** USER FATAL MESSAGE 428 (CKALTR)

DMAP LINE NUMBER K1 IS OUT OF RANGE. LAST DMAP LINE NUMBER IS:%1

429.0 *** USER WARNING MESSAGE 429 (CPARAM)

THE CHARACTER CONSTANT USED AS PARAMETER NUMBER %1 HAS BEEN TRUN-
CATED TO '%2'.

User information: TRUNCATION MAY RESULT IN AMBIGUOUS OR INCORRECT

PROCESSING.

User information: This means that a character constant has been defined using more characters than are
allowed based on either the "TYPE PARM" statement or in the NDDL. Any characters beyond the defined
length will be truncated.

430.0 *** USER FATAL MESSAGE 430 (CPARAM)

THE "C,N," AND "C,Y," AND "S,Y," PARAMETER PREFIXES ARE NO LONGER SUPPORTED.

User information: "%1" PREFIX FOUND IN PARAMETER NUMBER %2

User actions:
1. FOR CHARACTER CONSTANTS REMOVE "C,N," AND "C,Y," PREFIXES AND
ENCLOSE THE CONSTANTS WITH SINGLE QUOTES.
2. FOR NUMERICAL OR LOGICAL CONSTANTS, REMOVE "C,N," AND "C,Y," PREFIXES.
3. ADD THE "V,N," OR "V,Y," PREFIXES TO VARIABLE PARAMETERS.
4. REMOVE THE "S,Y," PREFIX AND REPLACE IT WITH A TYPE STATEMENT.

431.0 *** USER WARNING MESSAGE 431 (CPARAM)

THE DEFAULT VALUE FOR AN NDDL TYPED PARAMETER IS IGNORED FOR PARAMETER
NUMBER %1

User information: NDDL DEFAULTS MUST BE SET IN NDDL DECK

Defaults may not be assigned on the TYPE PARM,NDDL statement.

432.0 *** SYSTEM FATAL MESSAGE 432 (LCFENT)

Main Index
 64 MSC Nastran Error Messages
Errors 0 - 999

INSUFFICIENT OPEN CORE AVAILABLE TO STORE DBENTRY OF THE LOCATED DATA

BASE

432.1 *** SYSTEM WARNING MESSAGE 432 (DIRPT2)

INSUFFICIENT OPEN CORE AVAILABLE TO STORE THE REMAINING TRAILER RECORDS.

User information: THE REMAINING RECORDS HAVE BEEN TRUNCATED.

432.2 *** SYSTEM FATAL MESSAGE 432 (CPYNDL)

INSUFFICIENT OPEN CORE AVAILABLE TO COPY NDDL TABLES TO THE PRIMARY DATA
BASE

434.0 *** SYSTEM WARNING MESSAGE 434 (CSCDMP)

UNABLE TO LOCATE PARAMETER NUMBER %1 IN VPS FOR INSTRUCTION %2

435.0 *** SYSTEM WARNING MESSAGE 435 (CSCXRF)

UNEXPECTED END-OF-FILE ON OSCAR TRAILERS DURING PROCESSING OF THE CROSS
REFERENCE

435.1 *** SYSTEM WARNING MESSAGE 435 (CSCDMP)

UNEXPECTED END-OF-FILE FOUND DURING PROCESSING OF CROSS REFERENCE.

436.0 *** SYSTEM WARNING MESSAGE 436 (CSCDMP)

OPEN CORE OVERFLOW IN CROSS REFERENCE. CROSS REFERENCE TERMINATED.

437.0 *** SYSTEM FATAL MESSAGE 437 (CSTORE)

LOGIC ERROR. TYPE VARIABLE %1 IS NOT VALID

438.0 *** USER WARNING MESSAGE 438 (CSTRNG)

THE CHARACTER STRING ABOVE HAS BEEN TRUNCATED FROM %1 CHARACTERS TO
THE CURRENT LIMIT OF 80 CHARACTERS

User information: There is a limit of 80 characters for any single character string. It would be best to use
two or more character parameters, rather than one.

439.0 *** USER WARNING/FATAL MESSAGE 439 (CPARAM)

Main Index
 MSC Nastran Error Messages 65
Errors 0 - 999

THE PARAMETER NAMED %1 (TYPE= %2) APPEARS TO BE AN INPUT PARAMETER BUT IS

NOT PREVIOUSLY INITIALIZED IN A TYPE STATEMENT OR SPECIFIED IN THE SUBDMAP
ARGUMENT LIST.

User Information: IF THIS IS A WARNING THEN A DEFAULT VALUE OF %3 WILL BE

ASSUMED.

User action: IF THE PARAMETER IS INTENDED TO BE AN OUTPUT PARAMETER, THEN

THE "S,N," PREFIX SHOULD BE SPECIFIED IN FRONT OF THE PARAMETER. IF THE
PARAMETER IS INTENDED TO BE AN INPUT PARAMETER THEN IT SHOULD BE
INITIALIZED ON A TYPE STATEMENT OR SPECIFIED IN THE SUBDMAP ARGUMENT LIST.

440.0 *** USER FATAL MESSAGE 440 (CVIEW)

ERROR IN PARSING DBVIEW DMAP STATEMENT.

441.0 *** SYSTEM FATAL MESSAGE 441 (CVIEW)

ERROR IN PROCESSING DBVIEW DMAP STATEMENT. OVERFLOW IN DBVIEW OSCAR
TRAILER RECORD.

User action: PLEASE NOTIFY HEXAGON AB.

443.0 *** USER FATAL MESSAGE 443 (DBALOC)

THE SUBDMAP %1 REFERENCED BY THE SOL, LINK OR COMPILE STATEMENT WAS NOT
FOUND ON THE %2 DBSET.

User information: See also Error Report 2992 in section 17.4 of MSC NASTRAN Reference Manual.

444.0 *** USER FATAL MESSAGE 444 (DBALOC)

LINKAGE OF THE SOLUTION SEQUENCE HAS FAILED BECAUSE THE OBJECT FILE FOR
SUBDMAP %1 WAS NOT FOUND ON THE %2 DBSET.

445.0 *** USER FATAL MESSAGE 445 (DBALOC)

THE EXECUTABLE (OSCAR) FILE FOR SUBDMAP %1WAS NOT FOUND ON THE %2 DBSET.

User information: THE EXECUTABLE WAS NEVER CREATED.

User action: SUBMIT RUN TO COMPILE AND LINK THIS SUBDMAP.

Main Index
 66 MSC Nastran Error Messages
Errors 0 - 999

446.0 *** SYSTEM FATAL MESSAGE 446 (XCL300)

ERROR ATTEMPTING TO %1 A FILE (LOGICAL= %2) FOR DBSET SCRATCH WITH READ
AND WRITE PRIVILEGES.

User action: CHECK THE AVAILABLE/ALLOCATED SPACE AND THE PRIVILEGES GRANTED
THIS ACCOUNT.

User information: This may occur if BUFFSIZE is too large. See the MSC NASTRAN Installation and
Operations Instructions for maximum allowable value. This error may occur if the corresponding ASSIGN
statement references an incorrect physical file specification. Another possible cause is two restart jobs trying
to access (read/write) the same database simultaneously. DBLOCATing (read only) the same database by
two jobs is acceptable. Another cause is if a restart is attempted from a database in which the MASTER is
split into multiple physical files. An avoidance is to explicitly point to the physical name associated with the
MASTER DBsets on ASSIGN statements. See Error Report 2953 in section 17.4 of MSC NASTRAN
Reference Manual.

446.1 *** SYSTEM FATAL MESSAGE 446

ERROR ATTEMPTING TO CREATE A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ
AND WRITE PRIVILEGES.

User action: CHECK THE AVAILABLE/ALLOCATED SPACE AND THE PRIVILEGES GRANTED
THIS ACCOUNT.

446.2 *** SYSTEM FATAL MESSAGE 446 (DBCRT)

ERROR ATTEMPTING TO OPEN A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ PRIVI-
LEGE.

User action: CHECK THE READ PRIVILEGE GRANTED THIS FILE.

446.4 *** SYSTEM FATAL MESSAGE 446 (DBCRT)

ERROR ATTEMPTING TO OPEN A FILE (LOGICAL= %1) FOR DBSET %2 WITH READ AND
WRITE PRIVILEGES.

User action: CHECK THE READ AND WRITE PRIVILEGES GRANTED THIS FILE.

447.0 *** SYSTEM FATAL MESSAGE 447 (DBCRT)

Main Index
 MSC Nastran Error Messages 67
Errors 0 - 999

ERROR ATTEMPTING TO CREATE A PHYSICAL FILE WITH READ_ONLY OPTION.

User information: LOGICAL FILE = %1 OF DBSET %2

447.1 *** SYSTEM FATAL MESSAGE 447 (MAKEsgp)
Error attempting to create a physical file with Fortran unit %1 in DMAP module %2.

User information: File name= %3

449.0 *** SYSTEM FATAL MESSAGE 449 (DBDEF2)

THE FILE ASSIGNMENT TABLE (DBSPACE) CONTAINS NO INFORMATION FOR THE %1
DBSET.

Programmer information: THE XFIST1 ARRAY HAS INFORMATION ABOUT THIS DBSET
EITHER BY DEFAULT OR AS STORED BY THE RDINIT SUBROUTINE AFTER PROCESSING
INIT CARDS. THIS INFORMATION DOES NOT MATCH THE DBSPACE TABLE CONTENTS.

450.0 *** SYSTEM FATAL MESSAGE 450 (DBMAP)

DBMAP FILE NOT IN FIST. UNABLE TO OPEN FOR DBSET = %1

450.1 *** SYSTEM FATAL MESSAGE 450 (DBDIR)

DBDIR FILE NOT IN FIST. UNABLE TO OPEN FOR DBSET = %1

452.0 *** SYSTEM FATAL MESSAGE 452 (DBNADD)

THE DATA BASE DIRECTORY FILE (DBNAME) IS FULL. NO ADDITIONAL SUBDMAPS CAN
BE ADDED TO THE DBSET %1

User action: MODIFY COMPILE CARD TO STORE SUBDMAP ON A PREVIOUSLY USED

DBSET

Programmer information: VARIABLES OF INTEREST ARE: DBNBOT = %2 DBNTOP = %3

LSTDBN = %4 DBSET = %5

453.0 *** USER FATAL MESSAGE 453 (LCXSIZ)

Main Index
 68 MSC Nastran Error Messages
Errors 0 - 999

THE DATABASE WITH DBSNO=%1 DOES NOT CONTAIN A COMPILED NDDL. THE
DBSNO NUMBERS ARE PRINTED NEAR THE TOP OF THE EXECUTION SUMMARY TABLE.

User action: RECREATE THE DATABASE AND SPECIFY THE

1. ACQUIRE FMS STATEMENT OR
2. COMPILE NDDL= EXECUTIVE STATEMENT OR
3. SOL EXECUTIVE STATEMENT. THE SOL STATEMENT MUST REFERENCE AN MSC
SOLUTION SEQUENCE.

453.1 *** USER FATAL MESSAGE 453 (LCXLOD)

THE DATABASE NUMBER (IDBSNO)=%1 BEING USED IN THIS RUN DOES NOT HAVE
ENOUGH INFORMATION TO START FROM.

453.2 *** USER FATAL MESSAGE 453 (DBOLD)

THE DATABASE WITH DBSNO=%1 DOES NOT CONTAIN A COMPILED NDDL.
THE DBSNO NUMBERS ARE PRINTED NEAR THE TOP OF THE EXECUTION SUMMARY
TABLE.

454.0 *** SYSTEM FATAL MESSAGE 454 (DBOL67)

DBSETS CANNOT BE ATTACHED WITH RWOPT = %1. THIS RWOPT IS NOT SUPPORTED.

455.0 *** USER WARNING MESSAGE 455 (DBOL67)

THE PHYSICAL FILE CORRESPONDING TO THE LOGICAL %1 NAME DOES NOT EXIST.
THIS FILE IS A PART OF THE DBSET %2 OF THE %3 DATA BASE.

User information: NO REFERENCES TO THIS DBSET SHOULD BE MADE BY THIS RUN

456.0 *** SYSTEM FATAL MESSAGE 456 (DBOL67)

ERROR ATTEMPTING TO DO BIOOPN ON LOGICAL FILE NAME %1 ON DBSET = %2

457.0 *** SYSTEM FATAL MESSAGE 457 (DBOLD)

Main Index
 MSC Nastran Error Messages 69
Errors 0 - 999

INSUFFICIENT CORE TO READ ONE RECORD FROM THE FILE ASSIGNMENT (DBSPACE)
TABLE

User action: INCREASE OPEN CORE SIZE

Programmer information: NWDS = %1

THE AMOUNT OF OPEN CORE REQUIRED IN DBOLD IS : %2 * ( MAXIMUM NUMBER OF
PHYSICAL FILES OF THE %3 DATABASE

457.1 *** SYSTEM FATAL MESSAGE 457 (DBOL67)

INSUFFICIENT CORE TO READ ONE RECORD FROM THE FILE ASSIGNMENT (DBSPACE)
TABLE

User action: INCREASE OPEN CORE SIZE

Programmer information: NWDS = %1

THE AMOUNT OF OPEN CORE REQUIRED IN DBOL67 IS %2 * ( MAXIMUM NUMBER OF
PHYSICAL FILES OF THE %3 DATABASE)

458.0 *** SYSTEM FATAL MESSAGE 458 (LCLDBS)

THE MASTER DBSET ON THE LOCATED DATABASE HAS A BUFFSIZE REQUIREMENT
EXCEEDING THE BUFFSIZE USED FOR THIS RUN.

User information: A SYSTEM BUFFER OF %1 HAS BEEN DEFINED FOR THIS RUN.

User action: ADD FOLLOWING KEYWORD TO DATA DECK:%2BUFFSIZE=%3

458.1 *** SYSTEM FATAL MESSAGE 458 (DBOLD)

A DBSET ON THE %1 DATABASE HAS A BUFFSIZE REQUIREMENT EXCEEDING THE BUFF-
SIZE USED FOR THIS RUN.

User information: A SYSTEM BUFFER OF %2 HAS BEEN DEFINED FOR THIS RUN.

User action: ADD THE FOLLOWING KEYWORD TO THE NASTRAN (EMAS) CARD: BUFF-
SIZE=%3

458.2 *** SYSTEM FATAL MESSAGE 458 (DBOL67)

Main Index
 70 MSC Nastran Error Messages
Errors 0 - 999

A DBSET ON THE %1 DATABASE HAS A BUFFSIZE REQUIREMENT EXCEEDING THE BUFF-

SIZE USED FOR THIS RUN.

User information: A SYSTEM BUFFER OF %2 HAS BEEN DEFINED FOR THIS RUN.

User action: ADD THE FOLLOWING KEYWORD TO THE NASTRAN CARD: BUFFSIZE=%3

458.3 *** SYSTEM FATAL MESSAGE 458 (DBDEF)

THE MASTER DBSET ON THE PRIMARY DATABASE HAS A BUFFSIZE REQUIREMENT
EXCEEDING THE BUFFSIZE USED FOR THIS RUN.

User information: A SYSTEM BUFFER OF %1 HAS BEEN DEFINED FOR THIS RUN.

User action: ADD THE FOLLOWING KEYWORD TO THE %2 CARD: BUFFSIZE=%3

458.4 *** SYSTEM FATAL MESSAGE 458 (ATTDBS)

THE MASTER DBSET ON THE DELIVERY DATABASE HAS A BUFFSIZE REQUIREMENT
EXCEEDING THE BUFFSIZE USED FOR THIS RUN.

User information: A SYSTEM BUFFER OF %1 HAS BEEN DEFINED FOR THIS RUN.

User action: ADD THE FOLLOWING KEYWORD TO THE NASTRAN CARD: BUFFSIZE=%2

459.0 *** USER FATAL MESSAGE 459 (DBPREQ)

SHORT RECORD ENCOUNTERED IN TRANSACTION FILE (%1).

User information: THIS INDICATES THAT THE DATABASE HAS BEEN DESTROYED AND IS
IRRECOVERABLE.

User action: DELETE AND RE-GENERATE THE DATABASE.

460.0 *** USER FATAL MESSAGE 460 (DBPREQ)

THE TRANSACTION TABLE HAS EXCEEDED AVAILABLE OPEN CORE.

User action: RE-SUBMIT THIS JOB WITH A LARGER HICORE AND WITH ALL DBSETS
ATTACHED TO CLEAN UP THE TRANSACTION FILE

User information: SEE THE EXECUTION SUMMARY FILE FOR THE LIST OF UNATTACHED
DBSETS.

Main Index
 MSC Nastran Error Messages 71
Errors 0 - 999

461.0 *** USER FATAL MESSAGE 461 (DBSCIN)

THE PHYSICAL FILE ASSIGNED TO THE %1 DBSET ALREADY EXISTS.

User actions: DELETE THE FOLLOWING FILE AND RESUBMIT THE JOB.
%2

462.0 *** USER FATAL MESSAGE 462 (DBSPC)

THE FOLLOWING PHYSICAL FILE NAME EXCEEDS THE MAXIMUM NUMBER OF CHAR-
ACTERS ALLOWED.
%1

User information: THE CURRENT LIMIT IS %2 CHARACTERS.

462.1 *** USER FATAL MESSAGE 462 (DBSEXP)

THE PHYSICAL FILE NAME FOLLOWING EXCEEDS THE MAXIMUM NUMBER OF CHAR-
ACTERS ALLOWED NAMES IN THE DBSPACE TABLE
%1

User information: THE CURRENT LIMIT IS %2 CHARACTERS.

463.0 *** USER FATAL MESSAGE 463 (DBSPC)

THE NUMBER OF ASSIGNED PHYSICAL FILE NAMES FOR THE %1 DBSET EXCEEDS %2

User information: There is a limit on the number of physical files which may exist in one DBSET. Check
Section 2 in the MSC NASTRAN Quick Reference Guide for the limits. If you need more files than are
allowed, there are several options: 1)Create a new DBSET; 2) Use DBUNLOAD and DBLOAD to unload
the DBSET and then to load it back using larger files.

465.0 *** USER FATAL MESSAGE 465

Main Index
 72 MSC Nastran Error Messages
Errors 0 - 999

THE LINK TABLE FOR SUBDMAP %1 DOES NOT EXIST.

User actions:
1. ENSURE THAT THE SUBDMAP IS THE APPROPRIATE MAIN SUBDMAP
2. ENSURE THAT THE SUBDMAP WAS LINKED PROPERLY.

User information: THE LINK TABLE IS DESCRIBED UNDER THE LINK STATEMENT.

465.1 *** USER FATAL MESSAGE 465 (OSCRIN)

THE OSCAR LIST FILE FOR SUBDMAP %1 IS EMPTY, OR IT WAS NEVER CREATED.

User actions:
1. MAKE SURE THAT THE SUBDMAP WAS CREATED AS A MAIN SUBDMAP
2. MAKE SURE THAT THE SUBDMAP WAS LINKED PROPERLY.

466.1 *** SYSTEM FATAL MESSAGE 466 (DBSWRT)

ATTEMPT TO WRITE FILE ASSIGNMENT (DBSPACE) TABLE TO MASTER DBSET FAILED.
THE CORE-RESIDENT FILE ASSIGNMENT (DBSPACE) TABLE IS EMPTY

User action: SEND RUN TO HEXAGON AB

Programmer information: VALUES OF INTEREST

DBSTOP = %1 DBSBOT = %2 LSTDBS = %3
IF THE ABOVE VALUES SEEM UNREASONABLE THEN /XSPACE/ COMMON BLOCK HAS
BEEN OVERWRITTEN

467.0 *** USER FATAL MESSAGE 467

THE MAXIMUM NUMBER OF CALLS WITHIN %1 MAIN SUBDMAP HAS BEEN EXCEEDED.

User information: THE MAXIMUM NUMBER OF CALLS IN THIS VERSION IS %2

User information: Combine subDMAPs in order to alleviate this problem.

467.1 *** USER FATAL MESSAGE 467 (OSCRIN)

THE MAXIMUM NUMBER OF CALLS WITHIN %1 MAIN SUBDMAP HAS BEEN EXCEEDED.

User information: THE MAXIMUM NUMBER OF CALLS IN THIS VERSION IS 50

Main Index
 MSC Nastran Error Messages 73
Errors 0 - 999

468.0 *** USER FATAL MESSAGE 468

THE DBSET %1 IS NOT PART OF ANY DATA BASE ATTACHED TO THIS RUN, INDICATING
IT WAS NOT ALLOCATED FOR THIS RUN.

469.0 *** SYSTEM FATAL MESSAGE 469 (DGETTS)

THE WRONG TIME STAMP BLOCK WAS READ FOR THE FOLLOWING PHYSICAL FILE
NAME:
%1

User information: Each database file created by MSC NASTRAN contains a "time stamp" indicating the
time the file was initially created. The MASTER dbset contains a record of these time stamps and MSC
NASTRAN compares these values. This message indicates that a file attached has a different time stamp
than expected. Check the files to verify they are correct. If you are sure they are, there is a System Cell (135
or TSTAMP) that turns off this checking.

470.0 *** USER FATAL MESSAGE 470 (LCLDBS)

THE LOGICAL NAME %1 WAS ASSIGNED TO THE FOLLOWING PHYSICAL FILE, WHICH
DOES NOT EXIST.
%2
%3

User action: CHECK FILE ASSIGNMENTS.

471.0 *** SYSTEM FATAL MESSAGE 471 (DGETTS)

ERROR ATTEMPTING TO CLOSE THE FOLLOWING PHYSICAL FILE NAME:
%1

471.1 *** SYSTEM FATAL MESSAGE 471 (DGETTS)

Main Index
 74 MSC Nastran Error Messages
Errors 0 - 999

ERROR ATTEMPTING TO OPEN THE FOLLOWING PHYSICAL FILE NAME (PFILEX=%1) :

%2

User action:
1. CHECK THE READ/WRITE PRIVILEGES GRANTED THIS FILE.
2. CHECK MAXIMUM NUMBER OF FILES THAT MAY BE OPENED SIMULTANEOUSLY.
3. CHECK THAT THIS DATABASE FILE IS COMPATIBLE WITH THIS PLATFORM.
4. ENSURE THAT NO OTHER JOB HAS OPENED THE DATABASE FOR UPDATING.

User information: MSC NASTRAN is attempting to read information from a file for which the system is
not allowing access.

472.0 *** USER FATAL MESSAGE 472 (DBSEXP)

THE PHYSICAL FILE FOLLOWING AND REFERENCED BY THE EXPAND COMMAND WITH
THE LOGICAL NAME OF %1 ALREADY EXISTS.
%2

User information: FILES BEING ASSIGNED BY EXPAND COMMANDS CANNOT EXIST PRIOR
TO THEIR ASSIGNMENTS.

474.0 *** USER INFORMATION MESSAGE 474 (GNADD)

THE %1 FOR SUBDMAP %2 HAS BEEN REPLACED BY THE CURRENT ONE ON %3 DBSET

475.0 *** SYSTEM FATAL MESSAGE 475 (GNADD)

LOGIC ERROR - THE %1 FOR SUBDMAP %2 HAS BEEN EQUIVALENCED TO ANOTHER
FILE (SUBDMAP) IN DBSET %3

User action: SET THE OBJOUT OR OSCAROUT OF THIS SUBDMAP TO SCRATCH DBSET.

476.0 *** USER FATAL MESSAGE 476 (GPFILX)

THE LOGICAL NAME %1 ASSIGNED TO A PHYSICAL FILE NAME OF THE %2 DATA BASE,
DOES NOT EXIST.

User information: PHYSICAL FILE NAME = %3

477.0 *** USER FATAL MESSAGE 477 (GPFILX)

Main Index
 MSC Nastran Error Messages 75
Errors 0 - 999

THE LOGICAL NAME %1 OF THE %2 DATABASE IS AUTO-ASSIGNED TO THE FOLLOW-

ING ASSOCIATED PHYSICAL FILE NAME:%3
THE TIME STAMP OF THIS PHYSICAL FILE DOES NOT MATCH THE ONE IN THE FILE
ASSIGNMENT (DBSPACE) TABLE.

User action: CHECK OR RE-CREATE THE %4 DATABASE TO RESOLVE THIS ERROR

478.0 *** SYSTEM FATAL MESSAGE 478 (GPFILX)

THERE WAS A PROBLEM ATTACHING THE PHYSICAL FILE ASSIGNED TO THE LOGICAL
NAME=%2 OF THE %1 DATABASE.

User information: CHECK THE SPELLING OF THE NAME AND LOCATION OF THE PHYSI-
CAL FILE.

Programmer information: THE PHYSICAL FILE MAY HAVE A NULL TIME STAMP OR THE FILE
ASSIGNMENT DOES NOT MATCH

479.0 *** USER FATAL MESSAGE 479 (LCLDBS)

THE REQUESTED LOGICAL NAME %1 WAS NOT ASSIGNED.

User action: CHECK FILE ASSIGNMENTS.

User information: This error may be issued if the LOGICAL keyword on DBLOCATE references a
reserved logical name such as DBC, PUNCH, etc.

480.0 *** SYSTEM INFORMATION MESSAGE 480

JOB TERMINATED DUE TO ABOVE ERROR(S)

480.1 *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN)

JOB TERMINATED DUE TO ENDJOB OPTION.

480.2 *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN)

JOB TERMINATED DUE TO NOEXE OPTION ON SOL CARD OR NOGO OPTION ON COM-
PILER CARD.

480.3 *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN)

Main Index
 76 MSC Nastran Error Messages
Errors 0 - 999

JOB TERMINATED DUE TO LACK OF SOL CARD IN EXECUTIVE CONTROL SECTION.

480.4 *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN)

JOB TERMINATED DUE TO ABOVE ERRORS IN THE DMAP/NDDL LINKAGE EDITOR
(LINKER)

480.5 *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN)

JOB TERMINATED DUE TO ABOVE ERRORS IN THE DMAP COMPILER (XGPI)

480.6 *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN)

JOB TERMINATED DUE TO ABOVE ERRORS IN THE NDDL COMPILER.

480.7 *** SYSTEM INFORMATION MESSAGE 480 (XSEMIN)

JOB TERMINATED DUE TO ABOVE ERRORS IN THE NDDL AND DMAP COMPILERS.

480.8 *** USER INFORMATION MESSAGE 480 (XSEMIN)

JOB TERMINATED DUE TO LACK OF SOL, COMPILE, OR LINK CARDS IN THE EXECUTIVE
CONTROL SECTION.

480.9 *** SYSTEM INFORMATION MESSAGE 480

JOB TERMINATED DUE TO ABOVE ERROR(S) IN THE FILE MANAGEMENT SECTION.

480.11 *** SYSTEM INFORMATION MESSAGE 480 (LCLDBS)

JOB TERMINATED DUE TO ABOVE ERRORS IN THE LCLDBS/DBLOCATE

480.12 *** SYSTEM INFORMATION MESSAGE 480 (DBINIT)

JOB TERMINATED DUE TO ENDJOB OPTION

480.16 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 480 (EVLMSG)

JOB TERMINATED DUE TO ABOVE ERROR(S) IN THE %1 STATEMENT PROCESSOR.

482.0 *** SYSTEM INFORMATION MESSAGE 482 (UNDRVR)

NO %1 DATA HAS BEEN UNLOADED FROM THE DATABASE TO UNIT %2.

482.1 *** SYSTEM INFORMATION MESSAGE 482 (UNDRVR)

%1 PARAMETER(S) HAVE BEEN UNLOADED FROM THE DATABASE TO UNIT %2 IN %3
FORMAT.

Main Index
 MSC Nastran Error Messages 77
Errors 0 - 999

482.2 *** SYSTEM INFORMATION MESSAGE 482 (UNDRVR)

%1 DATABLOCK(S) HAVE BEEN UNLOADED FROM THE DATABASE TO UNIT %2 IN %3
FORMAT.

482.3 *** SYSTEM INFORMATION MESSAGE 482 (LDDRVR)

NO %1 DATA HAS BEEN LOADED TO THE DATABASE FROM UNIT %2.

482.4 *** SYSTEM INFORMATION MESSAGE 482 (LDDRVR)

%1 PARAMETER(S) HAVE BEEN LOADED TO THE DATABASE FROM UNIT %2 IN %3 FOR-
MAT.

482.5 *** SYSTEM INFORMATION MESSAGE 482 (LDDRVR)

%1 DATABLOCK(S) HAVE BEEN LOADED TO THE DATABASE FROM UNIT %2 IN %3 FOR-
MAT.

482.6 *** SYSTEM INFORMATION MESSAGE 482 (LCDRVR)

NO DATA HAS BEEN LOCATED ON THE %1 DATABASE.

482.7 *** SYSTEM INFORMATION MESSAGE 482 (LCDRVR)

%1 PARAMETER(S) HAVE BEEN LOCATED ON THE %2 DATABASE.

System information: This is an information message which results when using DBLOCATE.

482.8 *** SYSTEM INFORMATION MESSAGE 482 (LCDRVR)

%1 DATABLOCK(S) HAVE BEEN LOCATED ON THE %2 DATABASE.

System information: This is an information message which results when using DBLOCATE.

482.9 SYSTEM INFORMATION MESSAGE 482 (DBEQIV)

NO DATA HAS BEEN LOCATED ON THE PRIMARY DATABASE.

482.10 SYSTEM INFORMATION MESSAGE 482 (DBEQIV)

%1 PARAMETER(S) HAVE BEEN LOCATED ON THE PRIMARY DATABASE.

482.11 SYSTEM INFORMATION MESSAGE 482 (DBEQIV)

%1 DATABLOCK(S) HAVE BEEN LOCATED ON THE PRIMARY DATABASE.

Main Index
 78 MSC Nastran Error Messages
Errors 0 - 999

482.12 SYSTEM INFORMATION MESSAGE 482 (DBDELE)

NO DATA HAS BEEN DELETED ON THE PRIMARY DATABASE.

482.13 SYSTEM INFORMATION MESSAGE 482 (DBDELE)

%1 PARAMETER(S) HAVE BEEN DELETED ON THE PRIMARY DATABASE.

482.14 SYSTEM INFORMATION MESSAGE 482 (DBDELE)

%1 DATABLOCK(S) HAVE BEEN DELETED ON THE PRIMARY DATABASE.

483.0 *** USER FATAL MESSAGE 483 (UNLDBP)

THE %1 NAME = %2 CANNOT BE FOUND IN THE NDDL OF THE PRIMARY DATA BASE.

User action: MAKE SURE THAT THE ABOVE %3 NAME EXISTS IN THE NDDL OF THIS
DATABASE.

483.1 *** USER FATAL MESSAGE 483 (LCDRVR)

THE DATABLOCK/PARAMETER NAME = %1 CANNOT BE FOUND IN THE NDDL OF %2
DATA BASE.

User action: MAKE SURE ABOVE DATABLOCK/PARAMETER NAME EXISTS IN THE NDDL OF
THIS DATA BASE.

483.2 *** USER FATAL MESSAGE 483

THE DATABLOCK/PARAMETER NAME = %1 CANNOT BE FOUND IN THE NDDL OF PRI-
MARY DATA BASE.

User action: MAKE SURE ABOVE DATABLOCK/PARAMETER NAME EXISTS IN THE NDDL OF
THIS DATA BASE.

485.0 *** SYSTEM FATAL MESSAGE 485 (TMALOC)

THE QUALIFIER NAME %1 CANNOT BE FOUND IN THE PATH TABLE

487.0 *** SYSTEM FATAL MESSAGE 487 (VWDRVR)

THE KEY USED IN CREATING THE DBVIEW DATA BLOCK WAS NOT FOUND.

User action: SEND RUN TO HEXAGON AB.

487.1 *** SYSTEM FATAL MESSAGE 487 (LCFENT)

Main Index
 MSC Nastran Error Messages 79
Errors 0 - 999

THE PATH USED IN CREATING THE LOCATE DATA BLOCK WAS NOT FOUND.

487.2 *** SYSTEM WARNING MESSAGE 487 (DIRPT3)

THE QUALIFIER USED IN SEARCHING FOR DATA BLOCKS WAS NOT FOUND.

User action: SEND RUN TO HEXAGON AB.

487.3 *** SYSTEM FATAL MESSAGE 487 (DBALO2)

THE PATH USED IN CREATING THE LOCATE DATA BLOCK WAS NOT FOUND.

User action: SEND RUN TO HEXAGON AB

493.0 *** SYSTEM FATAL MESSAGE 493 (VWDRVR)

THE LENGTH OF THE STRING WHICH HOLDS THE QUALIFIERS AND THEIR VALUES
FOR DATABLOCK %1 EXCEEDS THE LIMIT OF %2.

User action:
1) REDUCE NUMBER OF QUALIFIERS FOR THE DATABLOCK IN THE NDDL SEQUENCE.
2) CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information:
1) WLEN = %3
2) NWLEN = %4
3) STRING =

494.0 *** SYSTEM FATAL MESSAGE 494 (LTMVPS)

THE TEMPORARY VPS TABLE USED IN PROCESSING USER-SUPPLIED EQUATIONS HAS
OVERFLOWED.

User action: SIMPLIFY EQUATION AND NOTIFY HEXAGON AB.

495.0 *** USER WARNING MESSAGE 495 (DBSPC)

THE BUFFSIZE OF DBSET %1, ON DATABASE NUMBER %2 IS UNABLE TO BE PROCESSED.
A SYSTEM DEFAULT BUFFSIZE = %3 HAS BEEN SELECTED FOR THIS DBSET.

Main Index
 80 MSC Nastran Error Messages
Errors 0 - 999

496.0 *** USER FATAL MESSAGE 496 (XCSOL2)

THE DBSET NAME %1 IS NOT IN THE DBSPACE TABLE

User information: THE DBSET WAS NOT ASSIGNED TO THIS RUN

User action: CHECK SPELLING OF DBSET NAME AND ASSIGNMENT OF CORRECT MASTER
DBSET TO THIS RUN

497.0 *** USER FATAL MESSAGE 497 (OSCRIN)

THE DBSET %1 CONTAINING THE EXECUTABLES (OSCARS) HAS BEEN ATTACHED TO
THIS RUN.

User action: REMOVE SOLIN KEYWORD FROM THE SOL CARD TO LINK THIS SOLUTION
SEQUENCE.

498.0 *** USER WARNING MESSAGE 498 (DBSPC)

YOU HAVE SELECTED A BUFFER SIZE OF %1 FOR THE MASTER DBSET, WHICH IS DIF-
FERENT THAN SCRATCH BUFFER SIZE OF%2
THIS IS NOT ALLOWED WITH MASTER(RAM) OPTION.
THE SCRATCH BUFFER SIZE %3 HAS BEEN SELECTED.

498.1 *** USER WARNING MESSAGE 498 (DBSPC)

YOU HAVE SELECTED A BUFFER SIZE OF %1 FOR THE SCRATCH DBSET, WHICH IS DIF-
FERENT THAN MASTER BUFFER SIZE OF%2
THIS IS NOT ALLOWED WITH MASTER(RAM) OPTION.
THE SCRATCH BUFFER SIZE %3 HAS BEEN SELECTED.

499.0 *** USER INFORMATION MESSAGE 499 (PRLINK)

SUBDMAP %1 WILL BE LINKED.

500.0 *** USER FATAL MESSAGE 500 (GETLIN)

I/O ERROR ENCOUNTERED READING %2 FILE. IOSTAT = %1.

User action: CHECK STATUS OF FILE OR FILESYSTEM.

FILE IS '%3
ERROR MESSAGE IS '%4'

Main Index
 MSC Nastran Error Messages 81
Errors 0 - 999

501.0 *** SYSTEM FATAL MESSAGE 501 (GETLIN)

INTERNAL LOGIC ERROR ENCOUNTERED. INCLUDE PROCESSING FOUND INVALID
HANDLE.
HANDLE VALUE IS %1.

502.0 *** USER FATAL MESSAGE 502 (CVIEW1)

THE VIEW NAME AND DATABLOCK NAME ARE IDENTICAL ON THE DBVIEW %1 = %1
STATEMENT.

503.0
PARENT-CHILD RUN OPTION NOT SUPPORTED.

503.1 *** USER FATAL MESSAGE (GP4)

ADVANCED ELEMENTS ONLY SUPPORT SOL 400.

505.0 *** USER FATAL MESSAGE 505 (XCSA)

CONTROL CARD %1 IS ILLEGAL

User information: The statement preceding Message 505 cannot be processed correctly. This message may
also be issued if an invalid character; such as a control character appears on the statement. See Table 1 in
Section 3.1 for valid characters.

506.0 *** USER FATAL MESSAGE 506 (XCSA)

CONTROL CARD %1 DUPLICATED

User information: The statement preceding Message 506 cannot be input more than once.

507.0 *** USER FATAL MESSAGE 507 (XCSA)

ILLEGAL SPECIFICATION OR FORMAT ON PRECEDING CARD

User information: Executive control statements cannot have equal (=) signs.

508.0 *** USER FATAL MESSAGE 508 (XCSA)

PROBLEM TAPE MUST BE ON PHYSICAL TAPE FOR CHECK POINTING

510.0 *** SYSTEM FATAL MESSAGE 510 (XCSA)

Main Index
 82 MSC Nastran Error Messages
Errors 0 - 999

CHECKPOINT DICTIONARY EXCEEDS CORE SIZE - REMAINING RESTART CARDS

IGNORED

511.0 *** SYSTEM FATAL MESSAGE 511 (XCSA)

DMAP SEQUENCE EXCEEDS CPRE SIZE - REMAINING DMAP INSTRUCTIONS IGNORED

System information: There is no more open core. Split the DMAP sequence somewhere prior to where
Message 511 was printed out.

511.1 *** SYSTEM FATAL MESSAGE 511 (XCSA)

NDDL SEQUENCE EXCEEDS CORE SIZE - REMAINING NDDL INSTRUCTIONS IGNORED

512.0 *** USER FATAL MESSAGE 512 (XCSA)

OLD PROBLEM TAPE IS MISSING AND IS NEEDED FOR RESTART

515.0 *** USER FATAL MESSAGE 515 (XCSA)

END INSTRUCTION MISSING IN DMAP SEQUENCE

User information: DMAP sequence must end with END control card. (END must begin in column 1.)

519.0 *** USER FATAL MESSAGE 519 (XCSA)

ID CARD MUST PRECEDE ALL OTHER CONTROL CARDS

User information: ID statement must come before all other statements except the NASTRAN and FMS
statements. Although the ID statement is documented as being an optional comment statement, if it is
used, it must be before all other Executive Control statements.

520.0 *** USER FATAL MESSAGE 520 (XCSA)

CONTROL CARD %1 IS MISSING

521.0 *** USER FATAL MESSAGE 521 (XCSA)

SPECIFY A SOLUTION OR A DMAP SEQUENCE, BUT NOT BOTH

522.0 *** USER FATAL MESSAGE 522 (XCSA)

NEITHER A VALID SOL CARD NOR A DMAP SEQUENCE WAS INCLUDED

526.0 *** USER FATAL MESSAGE 526 (XCSA)

Main Index
 MSC Nastran Error Messages 83
Errors 0 - 999

CHECKPOINT DICTIONARY OUT OF SEQUENCE - REMAINING RESTART CARDS

IGNORED

527.0 *** USER FATAL MESSAGE 527 (DOMSOL)

THE VALUE ASSIGNED TO THE DOMAIN SOLVER OPTION %1 IS INVALID OR MIS-
SPELLED.

527.1 *** USER FATAL MESSAGE 527 (SPASOL)

THE VALUE ASSIGNED TO THE SPARSESOLVER KEYWORD %1 IS INVALID OR MIS-
SPELLED.

User information: VALID VALUES ARE GRID, SUPER, GRDSUPER OR NONE

527.2 *** USER FATAL MESSAGE 527 (SPASOL)

THE VALUE ASSIGNED TO THE SPARSESOLVER KEYWORD %1 IS INVALID OR MIS-
SPELLED.

User information: VALID VALUES ARE MD, MMD, NONE, BEND, AMF, METIS OR BEST.

527.3 *** USER FATAL MESSAGE 527 (SPASOL)

THE VALUE ASSIGNED TO THE SPARSESOLVER KEYWORD %1 IS INVALID OR MIS-
SPELLED.

User information: VALID VALUES ARE MSCLDL, MSCCHL, MSCLU, TAUCSLDL, TAUCSCHL
OR UMFLU.

528.0 *** USER FATAL MESSAGE 528 (DOMSOL)

THE %1 DOMAIN SOLVER METHOD IS INVALID OR MISSPELLED.

528.1 *** USER FATAL MESSAGE 528 (SPASOL)

Main Index
 84 MSC Nastran Error Messages
Errors 0 - 999

THE %1 SPARSESOLVER TARGET APPLICATION IS INVALID OR MISSPELLED.

User information: VALID TARGET APPLICATIONS ARE

SPARSESOLVER READ
SPARSESOLVER DCMP
SPARSESOLVER DECOMP
SPARSESOLVER SOLVE
SPARSESOLVER FRRD1
SPARSESOLVER TRD1
SPARSESOLVER CEAD
SPARSESOLVER NLSOLV
SPARSESOLVER MDSTAT

529.0 *** USER FATAL MESSAGE 529 (DOMSOL)

THE DOMAIN SOLVER OPTION %1 IS INVALID OR MISSPELLED.

529.1 *** USER FATAL MESSAGE 529 (SPASOL)

THE SPARSESOLVER KEYWORD %1 IS INVALID OR MISSPELLED.

User information: VALID KEYWORDS ARE COMPMETH (TO SELECT THE COMPRESSION
METHOD), ORDMETH (TO SELECT THE REORDERING METHOD), FACTMETH or
METHOD (TO SELECT THE FACTORIZATION METHOD).

530.0 *** USER FATAL MESSAGE 530 (DOMSOL)

THE DOMAIN SOLVER OPTION %1 IS NOT SUPPORTED FOR THE %2 METHOD.

530.1
PARENT-CHILD RUN OPTION NOT SUPPORTED FOR ELEMENT DOMAIN.
EXECUTION WILL CONTINUE IN MULTIPLE-MASTER MODE.

531.0 *** SYSTEM WARNING MESSAGE 531 (DOMSOL)

DOMAINSOLVER %1 (PARTOPT=%2) IS NOT SUPPORTED IN SOLUTION %3.

User information: THE DOMAIN SOLVER METHOD WILL NOT BE USED FOR THIS RUN.

Main Index
 MSC Nastran Error Messages 85
Errors 0 - 999

531.1 *** SYSTEM WARNING MESSAGE 531 (DOMSOL)

DOMAINSOLVER %1 (PARTOPT=MULTIMST) IS NOT SUPPORTED WITH INTEL MKL
PARDISO SOLVER.

User information: MULTI-MASTER MODE WILL NOT BE USED FOR THIS RUN.

532.0 *** USER FATAL MESSAGE 532 (DOMSOL)

THE SELECTED COMBINATION OF DOMAINSOLVER METHODS IS NOT SUPPORTED IN
THE %1 SOLUTION SEQUENCE.

533.0 *** SYSTEM WARNING MESSAGE 533 (DOMSOL)

THE NUMBER OF PROCESSORS SPECIFIED ON THE DMP KEYWORD OF THE NASTRAN
SUBMITTAL COMMAND--DMP=%3-- IS NOT EQUAL TO THE NUMBER OF DOMAINS
SPECIFIED FOR THE %1 DOMAIN SOLVER METHOD--NUMDOM=%2.

User information: NUMDOM WILL BE RESET TO %3.

534.0 *** USER FATAL MESSAGE 534 (DOMSOL)

DOMAINSOLVER %1 (PARTOPT=%2) IS NOT SUPPORTED IN A SERIAL RUN.

534.1 *** USER FATAL MESSAGE 534 (DOMSOL)

DOMAINSOLVER %1 (PARTOPT=%2) IS NOT SUPPORTED IN A PARALLEL RUN.

534.2 *** USER FATAL MESSAGE 534 (DOMSOL)

DOMAINSOLVER %1 IS NOT SUPPORTED IN A SERIAL RUN.

535.0 *** SYSTEM WARNING MESSAGE 535 (DOMSOL)

THE NUMBER OF DOMAINS SPECIFIED FOR THE 'DOMAINSOLVER MODES (PAR-
TOPT=FREQ)' METHOD--NUMDOM=%2--EXCEEDS
THE MAXIMUM LIMIT OF %1.

User information: NUMDOM WILL BE RESET TO %1.

536.0 *** USER FATAL MESSAGE 536 (DOMSOL)

Main Index
 86 MSC Nastran Error Messages
Errors 0 - 999

THE NUMBER OF DOMAINS HAS NOT BEEN SPECIFIED.

User information: FOR SERIAL EXECUTION OF DOMAINSOLVER %1 (PARTOPT=%2), NUM-

DOM MUST BE SPECIFIED.

537.0 *** USER WARNING MESSAGE 537 (DOMSOL)

PARTOPT = %1 IS NOT SUPPORTED WITH DOMAINSOLVER %2 IN SOLUTION %3.

User information: THE PARTITIONING REQUEST WILL BE IGNORED FOR THIS RUN.

537.1 *** USER WARNING MESSAGE 537 (SPASOL)

FACTMETH = %1 IS NOT SUPPORTED WITH SPARSESOLVER %2.

User information: THE DEFAULT FACTORIZATION METHOD WILL BE USED.

538.0 *** USER WARNING MESSAGE 538 (RMDUPGE)

THE IMPLEMENTED SAMENESS CRITERIA CANNOT DETERMINE IF THE FOLLOWING
%1 BULK DATA ENTRIES ARE EQUIVALENT.

User information: BOTH ENTRIES WILL BE ACCEPTED, BUT THE DUPLICATE ID FIELD
WILL RESULT IN A USER FATAL MESSAGE 311 BEING ISSUED LATER.

539.0 *** USER WARNING MESSAGE 539 (RMDUPGE)

A TRANSLATION ERROR HAS OCCURRED IN READING THE %1 FIELD OF %2 %3 BULK
DATA %5 FROM HOLLERITH TO %4.

User information: BOTH ENTRIES WILL BE ACCEPTED, BUT THE DUPLICATE ID FIELD
WILL RESULT IN A USER FATAL MESSAGE 311 BEING ISSUED LATER.

540.0 *** USER INFORMATION MESSAGE 540 (RMDUPGE)

THE IMPLEMENTED SAMENESS CRITERIA HAS DETERMINED THE FOLLOWING %1
BULK DATA ENTRIES ARE EQUIVALENT.

User information: THE %2 %1 ENTRY HAS BEEN REMOVED

540.1 *** User information MESSAGE 540 (RMDUPGE)

Main Index
 MSC Nastran Error Messages 87
Errors 0 - 999

THE IMPLEMENTED TOLERANCE CRITERIA HAS DETERMINED THE FOLLOWING %1

BULK DATA ENTRIES ARE EQUIVALENT WITHIN THE SPECIFIED
LIMIT OF %3.

User information: THE %2 %1 ENTRY HAS BEEN REMOVED

541.0 *** USER FATAL MESSAGE 541 (SPASOL)

EXECUTIVE ENTRY SPARSESOLVER %1 HAS BEEN SPECIFIED MORE THAN ONCE.

User information: PLEASE MAKE SURE THAT THERE IS ONLY 1 SPARSESOLVER ENTRY
WITH THIS TARGET APPLICATION.

600.0 *** USER WARNING MESSAGE 600 (IFP1D)

NO TEXT AVAILABLE FOR MESSAGE %1

601.0 *** USER WARNING/FATAL MESSAGE 601 (IFP1D)

THE KEYWORD ON THE ABOVE CARD TYPE IS ILLEGAL OR MISSPELLED.

User information: Case Control expects each command to begin with a keyword (usually 4 characters in
length). To remove the error, consult the Case Control command descriptions, Section 4 of the MSC
NASTRAN Quick Reference Guide, and spell your request correctly. This occurs for SURFACE and
VOLUME commands that are not in the OUTPUT(POST) section.

601.1 User Fatal Message 601

THE MAXMIN(DEF) COMMAND OUTPUT CLASS NAME %1 IS NOT RECOGNIZED.

User information: VALID CLASSES ARE DISPLACEMENT, VELOCITY, ACCELERATION, LOAD,

SPCF, MPCF, GPKE, STRESS, FORCE, STRAIN.

601.2 User Fatal Message 601.2

THE MAXMIN(DEF) COMMAND COMPONENT VERB % IS NOT RECOGNIZED.

User information: VALID VERBS ARE CENTER, ALL, GROUP, ENDS

601.3 User Fatal Message 601

Main Index
 88 MSC Nastran Error Messages
Errors 0 - 999

THE MAXMIN(DEF) COMMAND KEYWORD %1 IS NOT RECOGNIZED.

User information: VALID KEYWORDS ARE MAXALG, MINALG, ABSOLUTE, CID, ALL, RMS,
BRIEF, FULL.

601.4 *** User Fatal Message 601 (IFP1)

The %1 command keyword %2 is not recognized.

601.5 *** User Warning Message 601 (IFP1RULE)

%1 command is not supported for %2 and will be ignored.

601.6 *** User Warning Message 601 (IFP1RULE)

%1 command is only supported in %2. All other cases will be ignored.

601.7 *** User Warning Message 601 (IFP1RULE)

%1 command will be ignored due to the presence of %2 command.

601.8 *** User FATAL Message 601 (IFP1RULE)

%1 command is specified for %2.

User information: This is not supported.

601.9 *** User FATAL Message 601 (IFP1RULE)

%1 and %2 commands are specified for %3.

User information: This is not supported.

601.10 *** User Fatal Message 601 (IFP1NLOP)

The %1 command keyword %2 was specified more than once.

601.11 *** User FATAL Message 601 (IFP1RULE)

%1 command is supported for %2 only.

601.12 *** USER FATAL MESSAGE 601 (IFP1)

Both BCONTACT=%1 and BCONTACT=AUTO exist in case control. If BCONTACT=AUTO is
present, then BCONTACT=n(n>0) or BCONTACT=ALLBODY are not allowed.

601.13 *** USER FATAL MESSAGE 601 (IFP1)

Main Index
 MSC Nastran Error Messages 89
Errors 0 - 999

%1 is invalid on case control command %2

602.0 *** USER WARNING/FATAL MESSAGE 602 (IFP1D)

TWO OR MORE OF THE ABOVE CARD TYPES DETECTED WHERE ONLY ONE IS LEGAL.
THE LAST FOUND WILL BE USED.

User information: Remove the command with the duplicate meaning. Note that some commands have
alternate forms.

603.0 *** USER WARNING/FATAL MESSAGE 603 (IFP1D)

THE ABOVE CARD DOES NOT END PROPERLY. COMMENTS SHOULD BE PRECEDED BY A
DOLLAR SIGN.

User information: Case Control commands of the form, name - value, should not contain more than one
value. Consult the Case Control command descriptions, Section 4 of the MSC NASTRAN Quick
Reference Guide, for a complete description of the command or precede the comments with a dollar sign.

604.0 *** USER WARNING/FATAL MESSAGE 604 (IFP1D)

THE ABOVE CARD HAS A NON-INTEGER IN AN INTEGER FIELD.

User information: Consult the Case Control command descriptions, Section 4 of the MSC NASTRAN
Quick Reference Guide, for legal values.

604.1 User Fatal Message 604.1

ON THE MAXMIN(DEF) COMMAND, A NON-INTEGER VALUE IS SPECIFIED WHERE AN
INTEGER SHOULD BE SPECIFIED.

605.0 *** USER WARNING/FATAL MESSAGE 605 (IFP1D)

A SYMSEQ OR SUBSEQ CARD APPEARS WITHOUT A SYMCOM OR SUBCOM CARD.

User information: SYMSEQ or SUBSEQ commands must appear in a subcase defined by a SYMCOM or
SUBCOM command. Check the Case Control and relabel the combination subcase.

606.0 *** USER WARNING/FATAL MESSAGE 606 (IFP1D)

A REQUEST FOR TEMPERATURE DEPENDENT MATERIALS OCCURS AT THE SUBCASE
LEVEL. ONLY ONE ALLOWED PER PROBLEM.

Main Index
 90 MSC Nastran Error Messages
Errors 0 - 999

607.0 *** USER WARNING/FATAL MESSAGE 607 (IFP1D)

A REPCASE CARD MUST BE PRECEDED BY A SUBCASE CARD

User information: A REPCASE subcase is an attempt to reoutput the previously computed case; therefore,
it cannot be the first subcase.

608.0 *** USER WARNING/FATAL MESSAGE 608 (IFP1D)

THE SET ID SPECIFIED ON THE ABOVE CARD MUST BE DEFINED PRIOR TO THIS CARD.

User information: Set identification numbers must be specified prior to their use. Also sets specified within
a subcase are valid only within that subcase. Redefine the errant set (or define a required set) or move the set
out of the subcase it is in.

609.0 *** USER WARNING/FATAL MESSAGE 609 (IFP1D)

THE SUBCASE NUMBER SPECIFIED VIOLATES ONE OR MORE OF THE FOLLOWING
RULES :
A. EACH MUST BE A POSITIVE INTEGER.
B. EACH MUST BE GREATER THAN THE PREVIOUS.
C. EACH MUST BE LESS THAN 9999999.

610.0 *** USER WARNING/FATAL MESSAGE 610 (IFP1D)

THE VALUE FOLLOWING THE EQUAL SIGN ON THE ABOVE CARD IS ILLEGAL.

User information: Case control cannot identify the value after the equal sign. Consult the Case Control
command descriptions, Section 4 of the MSC NASTRAN Quick Reference Guide. For example, only real
data can follow SUBSEQ and SUBCOM commands--not integers.

610.1 *** USER WARNING/FATAL MESSAGE 610 (IFP1X)

THE VALUE, WHICH FOLLOWS THE EQUAL SIGN ON KEY WORD, %1%2, IN THE ABOVE
LINE OF CASE CONTROL COMMAND, IS NOT A LEGITIMATE ONE.

User information: Case control cannot identify the value after the equal sign. Consult the Case Control
command descriptions, Section 4 of the MSC NASTRAN Quick Reference Guide.

611.0 *** USER WARNING/FATAL MESSAGE 611 (IFP1D)

Main Index
 MSC Nastran Error Messages 91
Errors 0 - 999

TEN CARDS HAVE ILLEGAL KEY WORDS. THE PROGRAM ASSUMES BEGIN BULK CARD IS
MISSING. IT WILL NOW PROCESS YOUR BULK DATA.

User information: In Case Control, only ten key words may be misspelled. A common source of this error
may be the omission of the OUTPUT(PLOT) or OUTPUT(XYOUT) delimiter commands.

612.0 User Fatal Message 612

THE STARTING SYNTAX OF THE MAXMIN(DEF) COMMAND IS NOT CORRECT.

613.0 *** USER WARNING/FATAL MESSAGE 613 (IFP1D)

THE ABOVE SET CONTAINS -EXCEPT- WHICH IS NOT PRECEDED BY -THRU-.

User information: Only identification numbers included by the THRU keyword may be expected. Sim-
plify the SET request.

614.0 *** USER WARNING/FATAL MESSAGE 614 (IFP1D)

THE ABOVE SET IS BADLY SPECIFIED.

User information: Simplify the SET list.

615.0 *** USER WARNING/FATAL MESSAGE 615 (IFP1D)

AN IMPROPER OR NO NAME GIVEN TO THE ABOVE SET.

User information: SET lists must have integer names. This SET list does not have one. SET 10 = is an
example of the correct format. Give the SET a correct integer name.

616.0 *** USER WARNING/FATAL MESSAGE 616 (IFP1D)

-EXCEPT- CANNOT BE FOLLOWED BY -THRU-. LIST EXPLICITLY ALL EXCEPTIONS.

User information: EXCEPT in SET list can only be followed by integers. An integer larger than the THRU
pair terminates the THRU. Either list exceptions explicitly, use two THRUs or terminate the first THRU.

617.0 *** USER WARNING/FATAL MESSAGE 617 (IFP1D)

Main Index
 92 MSC Nastran Error Messages
Errors 0 - 999

A NON POSITIVE INTEGER APPEARS IN A POSITIVE POSITION

User information: Most integer values specified on Case Control command must be positive. The above
command either has a negative integer or a character value in a positive position. See Section 4 of the MSC
NASTRAN Quick Reference Guide.

618.0 *** USER FATAL MESSAGE 618 (IFP1D)

PLOTTER OUTPUT IS REQUESTED BUT THE PROPER PLOT TAPE IS NOT A PHYSICAL
TAPE.

619.0 User Fatal Message 619

ITEM CODE ON the MAXMIN(DEF) COMMAND IS OUT OF RANGE.

User action: CHECK THE DOCUMENTATION OR THE NDDL DESCRIPTION FOR ITEM
CODE OR NAME.

620.0 User Fatal Message 620

COMPONENT %1 ON THE MAXMIN(DEF) COMMAND DOES NOT REFERENCE A REAL-
VALUED COMPONENT.

User action: CHECK THE DOCUMENTATION OR THE NDDL DESCRIPTION FOR ITEM
CODE OR NAME.

621.0 User Fatal Message 621

NO ELEMENT TYPES WERE FOUND AFTER THE ELEMENT/GRID CLASSES ARE SPECIFIED
AND BEFORE THE COMPONENTS ARE SPECIFIED.

User information: AN EXAMPLE OF CORRECT SYNTAX: MAXMIN(DEF) STRESS (HEXA

PENTA) SX

622.0 User Fatal Message 622

ALL ELEMENTS SPECIFIED ON THE MAXMIN(DEF) COMMAND DO NOT SHARE THE
SAME COMPONENT CHARACTERISTICS.

623.0 User Fatal Message 623

THE MAXALG, MINALG, OR ABSOLUTE DEPTH VALUE IS OUT OF RANGE ON THE MAX-
MIN(DEF) COMMAND.

User information: THE VALID RANGE IS FROM 1 TO 25, INCLUSIVE.

Main Index
 MSC Nastran Error Messages 93
Errors 0 - 999

624.0 *** USER FATAL MESSAGE 624 (IFP1D)

MUTUALLY EXCLUSIVE KEYWORDS ARE FOUND IN ABOVE CASE CONTROL COMMAND.
PLEASE CHOOSE ONLY ONE OF THEM.

624.1 *** USER FATAL MESSAGE 624 (IFP1FTG)

Mutually exclusive keywords are found in the above %1 case control command. Please choose only one of
them.

User Information: Conflicting keywords are %2

625.0 *** USER WARNING/FATAL MESSAGE 625 (IFP1D)

TOO LARGE ID ON PRECEDING SUBCASE TYPE CARD. ALL ID-S MUST BE LESS THAN
9,999,999

User information: Reduce the size of the subcase identification number. Note also that character string
subcase identification numbers are not legal.

626.0 *** USER WARNING/FATAL MESSAGE 626 (IFP1D)

SUBCOM SUBCASE DOES NOT HAVE A SUBSEQ CARD.

User information: A SUBCOM SUBCASE must contain a SUBSEQ command to define the linear
combination coefficients.

627.0 *** USER WARNING/FATAL MESSAGE 627 (IFP1D)

THE ABOVE SUBCASE HAS BOTH A STATIC LOAD AND A REAL EIGENVALUE METHOD
SELECTION--REMOVE ONE.

User information: The buckling solution requires two subcases: one for statics and one for buckling. Both
a load and a method selection cannot appear in the same subcase.

628.0 *** USER WARNING/FATAL MESSAGE 628 (IFP1D)

Main Index
 94 MSC Nastran Error Messages
Errors 0 - 999

THERMAL, DEFORMATION, AND EXTERNAL LOADS CANNOT HAVE THE SAME SET
IDENTIFICATION NUMBER.

User information: Set IDs specified on the LOAD, TEMP(LOAD), and DEFRM Case Control com-
mands must be unique.

628.1 *** USER FATAL MESSAGE 628 (LCGEN)

THERMAL, DEFORMATION, AND EXTERNAL LOADS CANNOT HAVE THE SAME SET
IDENTIFICATION NUMBER IN BULK DATA DECK.
THE SET IDENTIFICATION MUMBER IS %1.

628.2 *** USER FATAL MESSAGE 628 (IFP1TRL)

FOR SUBCOM %1, SUBCASE ID %2 IS REPEATEDLY REFERENCED ON SUBSEQ1.

628.3 *** USER FATAL MESSAGE 628 (IFP1TRL)

FOR SUBCOM %1, SUBSEQ1 REFERENCES MISSING SUBCASE ID %2.

628.4 *** USER FATAL MESSAGE 628 (IFP1TRL)

FOR SUBCOM %1, SUBSEQ1 REFERENCES SUBCASE ID %2 OF DIFFERENT ANALYSIS TYPE.

628.5 *** USER FATAL MESSAGE 628 (IFP1TRL)

FOR SUBCOM %1, THERE IS NO PREVIOUSLY DEFINED SUBCASE OF SAME ANALYSIS
TYPE.

628.6 *** USER FATAL MESSAGE 628 (IFP1TRL)

FOR SUBCOM %1, SUBSEQ1 REFERENCES SUBCASE ID %2 OF DIFFERENT SUPERELE-
MENT GROUP.

628.7 *** USER FATAL MESSAGE 628 (IFP1TRL)

FOR SUBCOM %1, SUBCASE ID %2 REFERENCED ON SUBSEQ1 IS PREVIOUSLY UNDE-
FINED.

629.0 *** USER WARNING/FATAL MESSAGE 629 (IFP1D)

ECHO CARD HAS REPEATED OR UNRECOGNIZABLE SPECIFICATION DATA. REPEATED
SPECIFICATIONS WILL BE IGNORED.
UNRECOGNIZABLE SPECIFICATIONS WILL BE TREATED AS SORT.

User information: See Section 4 of the MSC NASTRAN Quick Reference Guide.

Main Index
 MSC Nastran Error Messages 95
Errors 0 - 999

629.1 *** USER WARNING/FATAL MESSAGE 629 (IFP1)

THE SORT DESCRIBER MUST APPEAR LAST ON THE ECHO CASE CONTROL COMMAND

630.0 *** USER WARNING/FATAL MESSAGE 630 (IFP1D)

ECHO CARD WITH -NONE- SPECIFICATION HAS ADDITIONAL SPECIFICATIONS WHICH
WILL BE IGNORED.

User information: See Section 4 of the MSC NASTRAN Quick Reference Guide.

631.0 *** USER WARNING/FATAL MESSAGE 631 (IFP1D)

TWO OR MORE TEMPERATURE(INIT) CARDS AND/OR TEMPERATURE(MATE) CARDS
DETECTED WHERE ONLY ONE IS ALLOWED.

User information: Only one TEMPERATURE(INIT) or TEMPERATURE(MATE) command is

required for temperature initialization. Remove the extra command(s).

632.0 *** USER WARNING/FATAL MESSAGE 632 (IFP1D)

USING THE MATERIAL OPTION IN THE TEMPERATURE CASE CONTROL CARD WILL
RESULT IN UPDATING OF MATERIAL PROPERTIES ONLY ONCE. USE THE INITIAL
OPTION IN THE TEMPERATURE CASE CONTROL CARD FOR UPDATING OF MATERIAL
PROPERTIES AT EVERY LOAD ITERATION IN MATERIAL NON-LINEAR ANALYSIS.

633.0 *** USER WARNING/FATAL MESSAGE 633 (IFP1D)

INCONSISTENT USE OF TEMPERATURE CASE CONTROL CARD. EITHER A TEMPERA-
TURE(INIT), TEMPERATURE(MATERIAL) OR A TEMPERATURE(BOTH) CASE CONTROL
CARD IS ALLOWED PER RUN.

User information: Use TEMP(LOAD) and TEMP(MATERIAL) together, or TEMP(BOTH) by itself.

634.0 *** USER WARNING/FATAL MESSAGE 634 (IFP1D)

SERST CASE CONTROL ENTRY SUPPORTS KEYWORDS SEMI OR SEDR ONLY

635.0 *** USER WARNING/FATAL MESSAGE 635 (IFP1D)

WRONG FORMAT OF DATA FOR THE EVEN FIELD ON CONTOUR CARD

Main Index
 96 MSC Nastran Error Messages
Errors 0 - 999

636.0 *** USER WARNING/FATAL MESSAGE 636 (IFP1D)

THE TRIM AND DIVERG COMMANDS MAY NOT BE SPECIFIED IN THE SAME SUBCASE.

637.0 *** USER WARNING/FATAL MESSAGE 637 (IFP1D)

THE TYPE USED ON AN ANALYSIS CASE CONTROL ENTRY IS INVALID.

638.0 *** USER WARNING/FATAL MESSAGE 638 (IFP1D)

A SPACE IS REQUIRED BETWEEN THE SET COMMAND AND THE SET ID.

639.0 *** USER WARNING/FATAL MESSAGE 639 (IFP1D)

YOU MAY NOT SPECIFY BOTH MAX AND MIN FOR OBJECTIVE THE DEFAULT VALUE OF
MIN WILL BE USED.

640.0 *** USER WARNING/FATAL MESSAGE 640 (IFP1D)

YOU MAY NOT SPECIFY THIS CASE CONTROL ENTRY AT THE SUBCASE LEVEL.

641.0 *** USER WARNING/FATAL MESSAGE 641 (IFP1D)

CSSCHD=ALL IS NOT ALLOWED.

User information: SPECIFY CSSCHD=NONE OR CSSCHD=n WHERE n IS A CONTROL SUR-

FACE SCHEDULE ID.

642.0 *** USER FATAL MESSAGE 642 (IFPERR)

THE ABOVE CASE CONTROL COMMAND OR KEYWORD, %1, IS AMBIGUOUS.

User action: SPECIFY EITHER %2 OR %3

643.0 *** USER FATAL MESSAGE 643 (IFPERR)

AERO SYMMETRY CASE CONTROL COMMAND: %1 SPECIFIES AN ILLEGAL VALUE: %2

User information: LEGAL VALUES ARE: ANTISYMMETRIC, ASYMMETRIC, AND SYMMETRIC.

644.0 *** USER FATAL MESSAGE 644 (IFP1)

THE NUMBER OF %1 COEFFICIENTS, %2 , HAS EXCEEDED THE MAXIMUM ALLOWABLE
%3 .

645.0 *** USER WARNING/FATAL MESSAGE 645 (IFP1D)

Main Index
 MSC Nastran Error Messages 97
Errors 0 - 999

THE OUTPUT(POST) AND SETS DEFINITION COMMANDS CANNOT BE SPECIFIED AT

THE SAME TIME.

646.0 *** USER FATAL MESSAGE 646 (IFP1D)

ILLEGAL OR UNRECOGNIZABLE OPTION SPECIFIED ON THE ABOVE MAXMIN
STATEMENT.

647.0 *** USER WARNING MESSAGE 647 (IFP1FC)

ERROR DETECTED IN ABOVE CASE CONTROL COMMAND %1.

Programmer information: DETECTED A NEGATIVE COUNT, WHEN EXPECTING A POSITIVE

GROUP COUNTER, A CONTINUATION INDICATOR, OR AN END OF ENTRY INDICATOR
WHILE PROCESSING ABOVE COMMAND.

User information: ATTEMPTING TO CONTINUE PROCESSING

648.0 *** USER FATAL MESSAGE 648 (IFP1FC)

INVALID CASE CONTROL COMMAND STRUCTURE DETECTED ON ABOVE %1 ENTRY.

User information: A DESCRIBER NAME WAS EXPECTED, BUT NOT FOUND.

648.1 *** USER FATAL MESSAGE 648 (IFP1FTG)

Invalid case control command structure detected on the above %1 entry.

User information: %2

648.2 *** USER FATAL MESSAGE 648 (IFP1FTG)

Invalid format code %1. Plus 10000 or 256 can be used only for sol 101, 103 or 112.

649.0 *** USER WARNING MESSAGE 649 (IFP1FC)

AN EQUAL SIGN WAS MISSING BETWEEN THE CASE CONTROL DESCRIBER %2 AND ITS
VALUE DURING ABOVE %1 ENTRY PROCESSING.

649.1 *** USER WARNING MESSAGE 649 (IFP1FC)

Main Index
 98 MSC Nastran Error Messages
Errors 0 - 999

AN OPEN PARENTHESIS WAS MISSING BETWEEN THE CASE CONTROL DESCRIBER %2

AND ITS COMPOUND VALUE DURING ABOVE %1 COMMAND PROCESSING.

User information: THE DATA FOLLOWING THE DESCRIBER IS HOLLERITH.

650.0 *** USER WARNING MESSAGE 650 (IFP1FC)

DETECTED A PREMATURE END OF THE CASE CONTROL COMMAND %1 PROCESSING
DESCRIBER %2.

User information: THE DESCRIBER IS IGNORED.

650.1 *** USER WARNING MESSAGE 650 (IFP1FC)
DETECTED A PREMATURE END OF THE CASE CONTROL COMMAND %1 PROCESSING
DESCRIBER %2.

User Information: THE DESCRIBER IS IGNORED.

651.0 *** USER FATAL MESSAGE 651 (IFP1FC)

INVALID HOLLERITH VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

652.0 *** USER FATAL MESSAGE 652 (IFP1FC)

BOTH HOLLERITH VALUES ( %3,%4 ) SPECIFIED FOR THE %1 CASE CONTROL
DESCRIBER %2 ARE INVALID.

652.1 *** USER FATAL MESSAGE 652 (IFP1FC)

ONE OF THE HOLLERITH VALUES ( %3,%4 ) SPECIFIED FOR %1 CASE CONTROL
DESCRIBER %2 IS INVALID.

653.0 *** USER FATAL MESSAGE 653 (IFP1FC)

INVALID CASE CONTROL DESCRIBER %2 SPECIFIED ON %1 COMMAND.

654.0 *** USER FATAL MESSAGE 654 (IFP1FC)

INVALID INTEGER VALUE %3 SPECIFIED FOR %1 CASE CONTROL DESCRIBER %2.

655.0 *** USER FATAL MESSAGE 655 (IFP1FC)

INVALID DATA TYPE ON SPECIFIED %1 CASE CONTROL DESCRIBER %2.

656.0 *** USER FATAL MESSAGE 656 (IFP1FC)

Main Index
 MSC Nastran Error Messages 99
Errors 0 - 999

INVALID NUMERIC DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2.

User information: REQUIRED DATA TYPE IS %3.

656.1 *** USER FATAL MESSAGE 656 (IFP1FC)

INVALID DATA TYPE SPECIFIED ON %1 CASE CONTROL DESCRIBER %2.

User information: REQUIRED DATA TYPE IS %3.

657.0 *** USER WARNING/FATAL MESSAGE 657 (IFP1D)

THE STEP NUMBERS MUST BE IN ASCENDING ORDER AND LESS THAN 9999999.

657.1 *** USER WARNING/FATAL MESSAGE 657 (IFP1SSTP)

The SUBSTEP numbers are not in ascending order or are not less than 9999999.

658.0 *** USER WARNING/FATAL MESSAGE 658 (IFP1)

THE %1 COMMAND IS ALLOWED ONLY FOR NLMARC OR SOL 400.

658.1 *** USER FATAL MESSAGE 658 (IFP1)

THE CLOAD CASE CONTROL COMMAND HAS BEEN SPECIFIED.

User information: THE CLOAD COMMAND IS NOT ALLOWED IN SOL 400.

User action: PLEASE USE THE LOAD COMMAND FOR STATIC ANALYSIS (NLSTAT) OR
DLOAD COMMAND FOR TRANSIENT ANALYSIS (NLTRAN) TO SPECIFY LOADS.

659.0 *** USER FATAL MESSAGE 659 (IFP1PO)

THE ASSIGN STATEMENT IS MISSING FOR THE LOGICAL FILE ASSOCIATED WITH UNIT
%1 ON THE ABOVE COMMAND.

659.1 *** USER FATAL MESSAGE 659 (IFP1PO)

THE FORTRAN LOGICAL UNIT REFERENCE NUMBER %1 ON THE ABOVE POST COM-
MAND REFERENCES A FILE THAT HAS A FORM=FORMATTED ATTRIBUTE. A PREVIOUS
POST COMMAND SPECIFIES FILE UNIT %2 FOR FORMATTED OUTPUT. THE POST COM-
MAND DOES NOT ALLOW A FILE UNIT CHANGE FOR FORM=FORMATTED FILES.

Main Index
 100 MSC Nastran Error Messages
Errors 0 - 999

659.2 *** USER FATAL MESSAGE 659 (IFP1PO)

A POST COMMAND IS REQUIRED ABOVE ALL SUBCASES BUT HAS NOT BEEN SPECIFIED.

659.3 *** USER FATAL MESSAGE 659 (IFP1PO)

THE VALUE FOLLOWING THE POST COMMAND DESCRIBER %1 IS INVALID.

660.0 *** USER WARNING MESSAGE 660 (IFP1PO)

THE POST-PROCESSOR PROGRAM SELECTION IS DIFFERENT THAN IN THE PREVIOUS
POST COMMAND.

User information: FIRST SELECTION SPECIFIED WILL BE USED.

661.0 *** USER FATAL MESSAGE 661 (IFP1PO)

%1 SPECIFIED ON THE ABOVE POST COMMAND.

662.0 *** USER FATAL MESSAGE 662 (IFP1PO)

%1 SPECIFIED ON THE ABOVE POST COMMAND.

663.0 User Fatal Message 663

A NUMERICAL ITEM (COMPONENT) CODE IS SPECIFIED WITH A COMPONENT VERB
AND/OR GROUPED WITH LITERAL COMPONENT NAMES.

User information: NUMERICAL ITEM CODES MAY BE GROUPED WITH OTHER NUMERICAL
CODES BUT MAY NOT BE ASSOCIATED WITH COMPONENT VERBS.

User information: VALID VERBS ARE CENTER, ALL, GROUP, ENDS

664.0 System Fatal Message 664

THE ELEMENT ENCRIPTIONAL ALGORITHM HAS FAILED.

665.0 User Fatal Message 665

ON THE MAXMIN(DEF) COMMAND, THE CID SPECIFICATION IS MISSPELLED OR OUT
OF RANGE

User information: VALID SPECIFICATIONS ARE BASIC OR GLOBAL CHARACTER STRINGS

OR POSITIVE OR ZERO INTEGER VALUES.

667.0 System Fatal Message 667

Main Index
 MSC Nastran Error Messages 101
Errors 0 - 999

DETECTED A PREMATURE END OF THE ECHO CASE CONTROL COMMAND

User information: ATTEMPTING TO CONTINUE PROCESSING

668.0 System Fatal Message 668

THE SET SPECIFIED ON THE ABOVE COMMAND DOES NOT CONTAIN THE TYPE OF
LIST ITEMS REQUIRED BY THIS COMMAND.

User information: CERTAIN CASE CONTROL COMMANDS REQUIRE SETS

CONTAINING LISTS OF INTEGERS, OTHERS REQUIRE LISTS OF REAL NUMBERS,
OTHERS CHARACTER LISTS.

User information: THE MCFRACTION, PFMODE(STRUCTURE) AND PFPANEL (STRUCTURE)

COMMANDS REQUIRE SPECIAL LISTS OF GRIDID/COMPONENT CODES.

669.0 System Fatal Message 669

THE %1 COMMAND IS MISSING THE KEYWORD "%2".

670.0 User Warning Message

The ENHOP2 keyword on the POST Case Control command is not honored for %1 and will be ignored.

User information: ENHOP2 is only honored for PATRAN.

675.0 *** USER FATAL MESSAGE 675,

ABOVE CARD DOES NOT BEGIN WITH A NON-NUMERIC WORD.

User information: XYPLOT commands must begin with character data.

676.0 *** USER FATAL MESSAGE 676,

%1 IS NOT RECOGNIZED ON ABOVE CARD.

User information: Unrecognized XYPLOT command.

677.0 *** USER FATAL MESSAGE 677,

Main Index
 102 MSC Nastran Error Messages
Errors 0 - 999

ILLEGAL VALUE SPECIFIED.

User information: See Section 13.3 of MSC NASTRAN Reference Manual.

678.0 *** USER FATAL MESSAGE 678,

%1 CONTRADICTS PREVIOUS DEFINITION.

User information: Conflicting requests on an XYPLOT command.

679.0 *** USER FATAL MESSAGE 679,

%1 DELIMITER ILLEGALLY USED.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

680.0 *** USER FATAL MESSAGE 680,

%1 IS ILLEGAL IN STATEMENT.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

681.0 *** USER FATAL MESSAGE 681,

%1 IS ILLEGAL IN STATEMENT.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

682.0 *** USER FATAL MESSAGE 682,

%1 IS ILLEGAL IN STATEMENT.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

683.0 *** USER FATAL MESSAGE 683,

TOO MANY SUBCASES. MAXIMUM = 200 ON ANY ONE XY-OUTPUT COMMAND CARD.

User information: No more than 200 subcases are allowed on an XYPLOT request command.

684.0 *** USER FATAL MESSAGE 684,

SUBCASE-ID IS LESS THAN 1 OR IS NOT IN ASCENDING ORDER.

User information: Subcases must be positioned in ascending order.

Main Index
 MSC Nastran Error Messages 103
Errors 0 - 999

685.0 *** USER FATAL MESSAGE 685,

%1 = POINT OR ELEMENT ID IS ILLEGAL (LESS THAN 1).

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

686.0 *** USER FATAL MESSAGE 686,

NEGATIVE OR ZERO COMPONENTS ARE ILLEGAL.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

687.0 *** USER FATAL MESSAGE 687,

ALPHA-COMPONENTS ARE NOT PERMITTED FOR STRESS OR FORCE XY-OUTPUT
REQUESTS.

688.0 *** USER FATAL MESSAGE 688,

%1 COMPONENT NAME NOT RECOGNIZED.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

689.0 *** USER FATAL MESSAGE 689,

LAST CARD ENDED WITH A DELIMITER BUT NO CONTINUATION CARD WAS PRESENT.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual. If an
XYPLOT command ends in a delimiter (i.e., comma or slash) then the next entry is assumed to be a
continuation for that entry. This error often occurs when a command is longer than 72 characters. Any
characters in columns 73 and on are ignored in the XYPLOT section.

689.1 *** USER FATAL MESSAGE 689,

LOGICAL CARD ENDED WITH A DELIMITER SUCH AS COMMA.

User action: review above case control command and make required change.

User information: Case control command error; see Section 13.3 of MSC NASTRAN Reference Manual.
If a case control command ends in a delimiter (i.e., comma or slash) then the next entry is assumed to be a
continuation for that entry. This error often occurs when a command is longer than 72 characters. Any
characters in columns 73 and on are ignored.

Main Index
 104 MSC Nastran Error Messages
Errors 0 - 999

690.0 *** USER FATAL MESSAGE 690,

TYPE OF CURVE WAS NOT SPECIFIED. (E.G. DISPLACEMENT, STRESS, ETC.).

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

691.0 *** USER FATAL MESSAGE 691,

MORE THAN 2 OR UNEQUAL NUMBER OF COMPONENTS FOR ID-S WITHIN A SINGLE
FRAME.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

692.0 *** USER FATAL MESSAGE 692,

XY-OUTPUT COMMAND IS INCOMPLETE.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual. This may
simply be a command that is too long (that is, a command that extends into column 73 or beyond). Those
columns are not used in the XYPLOT section.

692.1 *** USER WARNING MESSAGE 692,

THE FOLLWING XY-OUTPUT REQUESTS WERE REJECTED DUE TO UNDEFINED SUB-
CASE ID(S) IN CASE CONTROL %1:

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual. Make sure the
Subcase statement was defined for each XY-OUTPUT request.

693.0 *** USER FATAL MESSAGE 693,

INSUFFICIENT CORE FOR SET TABLE.

User information: Reduce the number of requests or increase memory. Six words are used for each frame.

694.0 *** USER FATAL MESSAGE 694,

AUTO OR PSDF REQUESTS MAY NOT USE SPLIT FRAME, THUS ONLY ONE COMPONENT
PER ID IS PERMITTED.

User information: AUTO or PSDF requests may only be specified for full frames.

695.0 *** USER FATAL MESSAGE 695,

Main Index
 MSC Nastran Error Messages 105
Errors 0 - 999

COMPONENT VALUE = %1 IS ILLEGAL FOR AUTO OR PSDF VECTOR REQUESTS.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

696.0 *** USER FATAL MESSAGE 696,

COMPONENT VALUE = %1 IS ILLEGAL FOR VECTOR TYPE SPECIFIED.

User information: XYPLOT error; see Section 13.3 of MSC NASTRAN Reference Manual.

697.0 *** USER FATAL MESSAGE 697 (IFP1XY).

THE ABOVE COMMAND MUST END WITH ONE INTEGER VALUE.

698.0 *** USER FATAL MESSAGE 698 (IFP1IC).

THE ABOVE TRANSIENT INITIAL CONDITION SET CANNOT BE PROCESSED AS IT CON-
FLICTS WITH PREVIOUS IC() SET.

User information: IC(STATSUB) and IC (STATSUB, DIFFK) cannot be specified together in same run.

701.0 *** USER FATAL MESSAGE 701

THE NUMBER OF SUBDMAPS BEING COMPILED EXCEEDS THE MAXIMUM ALLOWED
NUMBER OF %1 FOR THIS VERSION.

702.0 *** USER INFORMATION MESSAGE 702 (PRCMPL)

THE NDDL WILL NOT BE COMPILED BECAUSE THE DATA BASE ALREADY EXISTS

User information: If a run is using an existing database, the valid NDDL for the database is stored in the
MASTER. If a new version were to be created, the information on the database would no longer be consid-
ered valid, since it would not match the current NDDL.

703.0 *** USER FATAL MESSAGE 703 (XCSA)

DMAP COMPILATION IS NOT ALLOWED WHEN "SOL" STATEMENT REQUESTS "SOLIN="

User action: REMOVE DMAP COMPILES FROM INPUT AND RESUBMIT

User information: You can also remove the SOLIN = from the SOL statement and provide the correct
information for compiling and linking the solution.

Main Index
 106 MSC Nastran Error Messages
Errors 0 - 999

706.0 *** USER FATAL MESSAGE 706

THE SUBDMAP STATEMENT IS MISSING OR THE SUBDMAP NAME IS INCORRECT.

User action: ASSURE THAT THE SUBDMAP NAME SPECIFIED ON THE SUBDMAP STATE-
MENT IS THE SAME ON THE COMPILE STATEMENT

User information: When compiling a user-supplied SUBDMAP, the SUBDMAP must always begin with a
SUBDMAP statement.

707.0 *** USER FATAL MESSAGE 707

THE "SOUIN=" COMPILE OPTION AND INLINE DMAP CANNOT BOTH BE SPECIFIED

708.0 *** USER FATAL MESSAGE 708 (PRCMPL)

THE "SOUIN=" DBSET CANNOT BE A "SCRATCH" DBSET

709.0 *** USER FATAL MESSAGE 709 (PRCMPL)

THE COMPILE COMMAND CANNOT RESTORE SOURCE FROM %1 DBSET, SINCE THIS IS
A DATA BASE INITIALIZATION RUN

User action: CHECK SPELLING OF THE ABOVE SPECIFIED DBSET FOR THE "SOUIN" KEY-
WORD, OR SUPPLY THE DMAP FOR %2 SUBDMAP

User information: When creating a database, use the ACQUIRE NDDL FMS statement or SOL xxx,
NOEXE to attach the data paths.

710.0 *** USER FATAL MESSAGE 710 (XTRAC4)

NO INFORMATION TO PROCESS ON THE PROJECT KEYWORD

710.1 *** USER FATAL MESSAGE 710 (XCSOL2)

NO INFORMATION TO PROCESS ON SOL STATEMENT

710.2 *** USER FATAL MESSAGE 710 (XCSACM)

NO INFORMATION TO PROCESS ON THE COMPILE EXECUTIVE COMMAND

710.3 *** USER FATAL MESSAGE 710

EXTRANEOUS DATA FOUND ON %1 STATEMENT.

710.4 *** USER FATAL MESSAGE 710 (RDSECU)

Main Index
 MSC Nastran Error Messages 107
Errors 0 - 999

NO INFORMATION TO PROCESS ON SECURITY COMMAND

710.5 *** USER FATAL MESSAGE 710 (RDPROJ)

PROJECT ID MUST BE ENCLOSED IN SINGLE QUOTES

710.6 *** USER FATAL MESSAGE 710 (RDPROJ)

MISSING PROJECT ID ON PROJECT COMMAND

710.7 *** USER FATAL MESSAGE 710 (RDLINK)

NO INFORMATION TO PROCESS ON LINK CARD

710.8 *** USER FATAL MESSAGE 710 (RDINIT)

NO INFORMATION TO PROCESS ON INIT STATEMENT

710.9 *** USER FATAL MESSAGE 710 (RDEXPN)

NO INFORMATION TO PROCESS ON EXPAND STATEMENT

710.10 *** USER FATAL MESSAGE 710 (RDASGN)

NO INFORMATION TO PROCESS ON ASSIGN COMMAND.

710.11 *** USER FATAL MESSAGE 710 (RDACQU)

NO INFORMATION TO PROCESS ON ACQUIRE STATEMENT.

713.0 *** SYSTEM FATAL MESSAGE 713 (PRTNDL)

END-OF-FILE ENCOUNTERED WHILE READING NDDL.

714.0 *** SYSTEM WARNING MESSAGE 714 (PVAPRT)

A DATA BASE PATH WITH KEY NUMBER %1 WAS NOT FOUND IN THE PVA (PATH VALUE
TABLE) WHILE PROCESSING DIRECTORY PRINT
INFORMATION FOR THE DATA BLOCK %2

User information: THIS INDICATES A PROBLEM WITH THE POINTERS IN YOUR DATA-
BASE'S MASTER DIRECTORIES

User action: DELETE THE OFFENDING DATA BLOCK WITH THE FMS SECTION COM-
MAND --> DBFIX

Main Index
 108 MSC Nastran Error Messages
Errors 0 - 999

715.0 *** SYSTEM INFORMATION MESSAGE 715 (RCARD)

THE ALTERNATE SECOND FIELD FORMAT FOR VPS TYPE %1 IS NOT CURRENTLY SUP-
PORTED.

User information: THIS FIELD WILL BE ASSUMED CHARACTER ( VPS TYPE 3 ) DATA

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

716.0 *** USER FATAL MESSAGE 716 (RDACQU)

AN UNRECOGNIZABLE NDDL NAME APPEARS ON THE ACQUIRE STATEMENT

User information: THE VALID NAMES ARE NDDLOLD AND NDDL FOR THE OLD AND THE
NEW SOLUTION SEQUENCES, RESPECTIVELY.

717.0 *** USER WARNING MESSAGE 717 (RDASGN)

RECL SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME.

User information: ASSIGNED RECL OF %2 WORDS IS REPLACED BY SYSTEM DEFAULT RECL

OF 1024 WORDS.

717.1 *** USER WARNING MESSAGE 717 (RDASGN)

RECL SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME.

User information: RECL IS IGNORED.

717.2 *** USER WARNING MESSAGE 717 (RDASGN)

RECL SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES.

User information: RECL IS IGNORED.

717.3 *** USER WARNING MESSAGE 717 (RDASGN)

FORM SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES.

User information: FORM IS IGNORED.

717.4 *** USER WARNING MESSAGE 717 (RDASGN)

Main Index
 MSC Nastran Error Messages 109
Errors 0 - 999

UNIT SPECIFICATION IS NOT REQUIRED FOR %1 LOGICAL NAME.

User information: UNIT IS IGNORED.

717.5 *** USER WARNING MESSAGE 717 (RDASGN)

UNIT SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES.

User information: UNIT IS IGNORED.

717.6 *** USER WARNING MESSAGE 717 (RDASGN)

SIZE SPECIFICATION IS NOT REQUIRED FOR WRITING DATA BASE FILES.

User information: SIZE IS IGNORED.

718.0 *** USER FATAL MESSAGE 718 (RDASGN)

FORM SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

718.1 *** USER FATAL MESSAGE 718 (RDASGN)

STATUS SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

718.2 *** USER FATAL MESSAGE 718 (RDASGN)

RECL SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

718.3 *** USER FATAL MESSAGE 718 (RDASGN)

UNIT SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

718.4 *** USER FATAL MESSAGE 718 (RDASGN)

SIZE SPECIFICATION IS MISSING ON THIS ASSIGN CARD.

719.0 *** USER FATAL MESSAGE 719 (RDREST)

THE SECURITY KEYWORD IS MISSING ON THE RESTART COMMAND.

User action: REMOVE THE PARENTHESES, IF NO SECURITY IS DEFINED IN THIS DATA

BASE.

719.1 *** USER FATAL MESSAGE 719 (RDDIRP)

Main Index
 110 MSC Nastran Error Messages
Errors 0 - 999

THE SECURITY KEYWORD IS MISSING ON THE DBDIR COMMAND.

REMOVE PARENTHESES IF NO SECURITY CODE DEFINED IN THIS DATA BASE

719.2 *** USER FATAL MESSAGE 719 (RDDBCL)

THE SECURITY KEYWORD IS MISSING ON THE DBCLEAN COMMAND.

User action: REMOVE THE PARENTHESES, IF NO SECURITY CODE DEFINED IN THIS DATA
BASE

720.0 *** USER FATAL MESSAGE 720 (RDEXPN)

THE EXPAND STATEMENT IS MISSING THE KEYWORD "LOGICAL="

720.1 *** USER FATAL MESSAGE 720 (RDDIRP)

THE DBDIR COMMAND IS MISSING KEYWORD "VERSION=" ID

720.2 *** USER FATAL MESSAGE 720 (RDDBCL)

THE DBCLEAN COMMAND IS MISSING THE KEYWORD "VERSION=" ID

721.0 *** USER FATAL MESSAGE 721 (RDASGN)

ILLEGAL FORM KEYWORD.

User information: THE VALID FORM KEYWORDS ARE: FORMATTED, UNFORMATTED,

BIGENDIAN, LITTLEENDIAN AND SYNONYMS.

721.1 *** USER FATAL MESSAGE 721 (RDASGN)

INVALID STATUS KEYWORD.

User information: THE VALID STATUS KEYWORDS ARE: OLD OR NEW.

722.0 *** USER FATAL MESSAGE 722 (RDASGN)

LOGICAL NAME EXCEEDS MAXIMUM NUMBER OF CHARACTERS ALLOWED.

User information: MAXIMUM CHARACTER LENGTH IS 8.

723.0 *** USER FATAL MESSAGE 723 (XTRDPO)

Main Index
 MSC Nastran Error Messages 111
Errors 0 - 999

DMAP EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJ-
ECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJ-
ECT=*" VERSION=LAST" will be conflicting.

723.1 *** USER FATAL MESSAGE 723 (XTRDAP)

%1 EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as
WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification
of "PROJECT=*" VERSION=LAST" will be conflicting.

723.2 *** USER FATAL MESSAGE 723 (XTRCLO)

THE ABOVE DMAP MODULE EXPRESSION HAS AN UNBALANCED NUMBER OF PAREN-
THESES.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJ-
ECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJ-
ECT=*" VERSION=LAST" will be conflicting.

723.3 *** USER FATAL MESSAGE 723 (XTRCLA)

THE ABOVE %1 EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJ-
ECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJ-
ECT=*" VERSION=LAST" will be conflicting.

723.4 *** USER FATAL MESSAGE 723 (XTRACI)

Main Index
 112 MSC Nastran Error Messages
Errors 0 - 999

THE ABOVE FILE NAME CONTAINS AN UNBALANCED NUMBER OF DELIMITERS.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as
WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification
of "PROJECT=*" VERSION=LAST" will be conflicting.

723.5 *** USER FATAL MESSAGE 723 (XTRAC4)

PROJECT ID EXPRESSION HAS AN UNBALANCED NUMBER OF SINGLE QUOTES

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as
WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification
of "PROJECT=*" VERSION=LAST" will be conflicting.

723.6 *** USER FATAL MESSAGE 723 (XTRAC2)

THE ABOVE COMMAND CONTAINS AN UNBALANCED NUMBER OF SINGLE QUOTES.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as
WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification
of "PROJECT=*" VERSION=LAST" will be conflicting.

723.7 *** USER FATAL MESSAGE 723

%1 STATEMENT HAS AN UNBALANCED NUMBER OF PARENTHESES.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as
WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification
of "PROJECT=*" VERSION=LAST" will be conflicting.

723.8 *** USER FATAL MESSAGE 723

%1 STATEMENT HAS AN UNBALANCED NUMBER OF SINGLE QUOTES.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as
WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification
of "PROJECT=*" VERSION=LAST" will be conflicting.

Main Index
 MSC Nastran Error Messages 113
Errors 0 - 999

723.9 *** USER FATAL MESSAGE 723 (RDREST)

VERSION EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as
WHERE(PROJECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification
of "PROJECT=*" VERSION=LAST" will be conflicting.

723.10 *** USER FATAL MESSAGE 723 (RDPROJ)

PROJECT ID HAS UNBALANCED NUMBER OF SINGLE QUOTES

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification suchas WHERE(PROJ-
ECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJ-
ECT=*" VERSION=LAST" will be conflicting.

723.11 *** USER FATAL MESSAGE 723

LOGICAL= EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJ-
ECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJ-
ECT=*" VERSION=LAST" will be conflicting.

723.13 *** USER FATAL MESSAGE 723

VERSION EXPRESSION HAS AN UNBALANCED NUMBER OF PARENTHESES

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJ-
ECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJ-
ECT=*" VERSION=LAST" will be conflicting.

723.15 *** USER FATAL MESSAGE 723 (PARSYS)

Main Index
 114 MSC Nastran Error Messages
Errors 0 - 999

THE ABOVE COMMAND CONTAINS AN UNBALANCED NUMBER OF SINGLE QUOTES.

User information: This can occur when the DBLOCATE feature is used with the WHERE(PROJECT=*)
clause. Modify the WHERE clause to include VERSION specification such as WHERE(PROJ-
ECT=*,VERSION=*); otherwise, the default for VERSION is "last" and the specification of "PROJ-
ECT=*" VERSION=LAST" will be conflicting.

723.16 User Fatal Message 723

UNBALANCED PARENTHESIS HAS BEEN DETECTED ON THE MAXMIN(DEF) COMMAND.

User information: EXAMPLE OF CORRECT SYNTAX IS MAXA(5).

724.0 *** USER WARNING MESSAGE 724 (RDASGN)

SIZE SPECIFICATION IS NOT NECESSARY FOR THIS MACHINE.

User information: SIZE IS IGNORED.

725.0 *** USER FATAL MESSAGE 725

THE EQUAL SIGN IS MISSING AFTER THE LOGICAL KEYWORD

725.2 *** USER FATAL MESSAGE 725 (RDASGN)

THE EQUAL SIGN IS MISSING AFTER THE LOGICAL KEYWORD

725.3 *** USER FATAL MESSAGE 725 (PARSYS)

THE EQUAL SIGN IS MISSING AFTER THE SYS KEYWORD.

726.0 *** USER FATAL MESSAGE 726 (RDINIT)

THE LIST OF LOGICAL NAMES MUST BE IN ENCLOSED PARENTHESES

727.0 *** USER WARNING MESSAGE 727 (RDINIT)

NO SPACE WAS REQUESTED FOR LOGICAL NAME %1

User information: A DEFAULT OF %2 IS USED

User information: Assign the desired disk space by using the ASSIGN statement or by JCL.

727.1 *** User information MESSAGE 727 (RDEXPN)

Main Index
 MSC Nastran Error Messages 115
Errors 0 - 999

NO SPACE WAS REQUESTED FOR LOGICAL NAME %1

User information: A DEFAULT OF %2 IS USED

User information: Assign the desired disk space by using the ASSIGN statement or by JCL.

728.0 *** USER FATAL MESSAGE 728 (RDINIT)

THE LOGICAL NAME SPACE OR MEM REQUEST IS MISSING A CLOSING PARENTHESIS.

User action: VERIFY THAT THE STATEMENT DOES NOT EXTEND BEYOND COLUMN 72.

728.1 *** USER FATAL MESSAGE 728 (RDEXPN)

THE LOGICAL NAME SPACE REQUEST IS MISSING A CLOSING PARENTHESIS

729.0 *** USER WARNING MESSAGE 729 (RDINIT)

THE BUFFSIZE FOR USROBJ CANNOT BE CHANGED FROM THE MACHINE DEFAULT.

User information: BUFFSIZE PARAMETER IGNORED.

730.0 *** USER FATAL MESSAGE 730 (XCSACM)

SYNTAX ERROR IN COMPILE EXECUTIVE COMMAND

User information: CHECK SYNTAX AND FORMAT OF COMPILE CARD

730.1 *** USER FATAL MESSAGE 730 (RDLINK)

SYNTAX ERROR IN LINK EXECUTIVE COMMAND

User information: CHECK SYNTAX AND FORMAT OF LINK CARD

731.0 *** USER WARNING MESSAGE 717 (RDASGN)

THE FORM=%1 SPECIFICATION IS NOT VALID FOR THIS FILE.

User information: FORM=%1 WILL BE IGNORED.

732.0 *** USER FATAL MESSAGE 717 (OPFUNT)

Main Index
 116 MSC Nastran Error Messages
Errors 0 - 999

LOGICAL NAMES '%1' AND '%2' ARE ASSIGNED TO THE SAME PHYSICAL FILE.

User information: PHYSICAL FILE NAME 1: %3

PHYSICAL FILE NAME 2: %4

User information: CHANGE FILE NAME ON ONE OF THE ASSOCIATED ASSIGN

STATEMENTS.

735.0 *** USER WARNING MESSAGE 735 (RDREST)

THE MODIFIED AND UNMODIFIED KEYWORDS ARE NO LONGER VALID ON THE
RESTART COMMAND.

736.0 *** USER INFORMATION MESSAGE 736 (RDREST)

THE RESTART VERSION ID IS NOT DEFINED ON THE RESTART COMMAND.
A RESTART OF LAST VERSION ID IS ASSUMED.

User information: Whenever performing a restart, the program assumes that the restart will use the most
recent version in the database unless a version number is specified.

737.0 *** USER FATAL MESSAGE 737 (XTRUNI)

THE FORTRAN UNIT NUMBER SPECIFIED ON FMS COMMAND MUST BE AN INTEGER
UNIT=%1

737.1 *** USER FATAL MESSAGE 737 (XTRKIV)

THE VALUE SPECIFIED FOR %1 MUST BE AN INTEGER
%2=%3

737.2 *** USER FATAL MESSAGE 737 (RDUPDT)

THE VALUE SPECIFIED FOR DBUPDATE CARD HAS A BAD INTEGER FORMAT %1

737.3 *** USER FATAL MESSAGE 737 (RDREST)

THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER.
THE VALUE IS %1

737.4 *** USER FATAL MESSAGE 737 (RDINIT)

THE SPACE SPECIFIED FOR LOGICAL NAME %1 IS NOT A VALID NUMBER
SPACE DEFINED IS %2

737.5 *** USER FATAL MESSAGE 737 (RDINIT)

Main Index
 MSC Nastran Error Messages 117
Errors 0 - 999

THE VALUE OF THE SPECIFIED CLUSTER SIZE IS NOT AN INTEGER

THE VALUE IS %1

737.6 *** USER FATAL MESSAGE 737 (RDINIT)

THE VALUE SPECIFIED FOR BUFFSIZE IS NOT AN INTEGER
THE VALUE IS %1

737.7 *** USER FATAL MESSAGE 737 (RDINIT)

THE BUFFSIZE SPECIFIED FOR "MEM" IS NOT A VALID NUMBER
MEM=%1

737.8 *** USER FATAL MESSAGE 737 (RDINIT)

THE VALUE SPECIFIED FOR RAM SIZE MUST BE AN INTEGER
%1=%2

737.9 *** USER FATAL MESSAGE 737 (RDEXPN)

SPACE SPECIFIED FOR LOGICAL NAME %1 IS NOT A VALID NUMBER
SPACE DEFINED IS %2

737.10 *** USER FATAL MESSAGE 737 (RDDIRP)

THE VALUE SPECIFIED FOR FORMAT IS NOT AN INTEGER
THE VALUE IS %1

737.11 *** USER FATAL MESSAGE 737 (RDDIRP)

THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER
THE VALUE IS %1

737.12 *** USER FATAL MESSAGE 737 (RDDBCL)

THE VALUE SPECIFIED FOR VERSION IS NOT AN INTEGER
THE VALUE IS %1

737.13 *** USER FATAL MESSAGE 737 (RDASGN)

THE VALUE SPECIFIED FOR RECL IS NOT AN INTEGER.
THE VALUE IS %1

737.14 *** USER FATAL MESSAGE 737 (RDASGN)

Main Index
 118 MSC Nastran Error Messages
Errors 0 - 999

THE VALUE SPECIFIED FOR UNIT IS NOT AN INTEGER.

THE VALUE IS %1

737.15 *** USER FATAL MESSAGE 737 (RDASGN)

THE VALUE SPECIFIED FOR SIZE IS NOT AN INTEGER.
THE VALUE IS %1

737.16 *** USER FATAL MESSAGE 737 (INPTT4)

THE FORTRAN UNIT NUMBER SPECIFIED ON AN INPUTT4 STATEMENT MUST BE AN
INTEGER GREATER THAN 0.
UNIT SPECIFIED=%1

738.0 *** USER FATAL MESSAGE 738 (RDASGN)

THE FILE NAME MUST BE DEFINED FOR LOGICAL %1

739.0 *** USER FATAL MESSAGE 739 (RDASGN)

THE LOGICAL NAME %1 IS NOT USER ASSIGNABLE.

740.0 *** USER FATAL MESSAGE 740 (RDASGN)

UNIT NUMBER %1 HAS ALREADY BEEN ASSIGNED TO THE LOGICAL NAME %2

User action: CHANGE THE UNIT NUMBER ON THE ASSIGN STATEMENT AND IF THE UNIT
IS USED FOR PARAM,POST,<0 THEN SPECIFY PARAM,OUNIT2 WITH THE NEW UNIT
NUMBER. AVOID USING THE FOLLOWING UNIT NUMBERS THAT ARE ASSIGNED TO
SPECIAL FILES IN MSC NASTRAN: 1 THRU 12, 14 THRU 22, 40, 50, 51, 91, 92, 1133, 1234, 1235,
1236, AND 2269. SEE THE MSC NASTRAN INSTALLATIONS/OPERATIONS GUIDE SECTION
ON MAKING FILE ASSIGNMENTS OR MSC NASTRAN QUICK REFERENCE GUIDE ON
ASSIGN PHYSICAL FILE FOR REFERENCE.

740.1 *** USER FATAL MESSAGE 740 (RDASGN)

Main Index
 MSC Nastran Error Messages 119
Errors 0 - 999

UNIT NUMBER %1 HAS ALREADY BEEN ASSIGNED TO THE LOGICAL NAME %2

User action: MAKE ONE OF THE FOLLOWING MODIFICATIONS:

1. IF INPUTT2 AND OUTPUT2 ARE SPECIFIED FOR THE SAME UNIT,THEN REMOVE
ONE AND KEEP THE OTHER ASSIGN STATEMENT.
OR
2. CHANGE THE UNIT NUMBER ON THE ASSIGN STATEMENT AND IF THE UNIT IS
USED FOR PARAM,POST,<0 THEN SPECIFY PARAM,OUNIT2 WITH THE NEW UNIT
NUMBER. AVOID USING THE FOLLOWING UNIT NUMBERS THAT ARE ASSIGNED
TO SPECIAL FILES IN MSC NASTRAN: 1 THRU 12, 14 THRU 22, 40, 50, 51, 91, 92. SEE
THE MSC NASTRAN INSTALLATIONS/OPERATIONS GUIDE SECTION ON MAKING
FILE ASSIGNMENTS OR MSC NASTRAN QUICK REFERENCE GUIDE ON ASSIGN
PHYSICAL FILE FOR REFERENCE.

740.2 *** USER FATAL MESSAGE 740 (RDASGN)

UNIT NUMBER %1 HAS ALREADY BEEN ASSIGNED TO THE LOGICAL NAME %2

User action: MAKE ONE OF THE FOLLOWING MODIFICATIONS:

1. IF INPUTT4 AND OUTPUT4 ARE SPECIFIED FOR THE SAME UNIT, THEN REMOVE
ONE AND KEEP THE OTHER ASSIGN STATEMENT.
OR
2. CHANGE THE UNIT NUMBER ON THE ASSIGN STATEMENT AND IF THE UNIT IS
USED FOR PARAM,POST,<0 THEN SPECIFY PARAM,OUNIT2 WITH THE NEW UNIT
NUMBER. AVOID USING THE FOLLOWING UNIT NUMBERS THAT ARE ASSIGNED
TO SPECIAL FILES IN MSC NASTRAN: 1 THRU 12, 14 THRU 22, 40, 50, 51, 91, 92. SEE
THE MSC NASTRAN INSTALLATIONS/OPERATIONS GUIDE SECTION ON MAKING
FILE ASSIGNMENTS OR MSC NASTRAN QUICK REFERENCE GUIDE ON ASSIGN
PHYSICAL FILE FOR REFERENCE.

741.0 *** USER FATAL MESSAGE 741 (RDASGN)

THE LOGICAL NAME %1 HAS ALREADY BEEN ASSIGNED TO THE FOLLOWING PHYSICAL
FILE:
%2

742.0 *** USER FATAL MESSAGE 742

ILLEGAL USAGE OF DBSET KEYWORD %1

Main Index
 120 MSC Nastran Error Messages
Errors 0 - 999

742.1 *** USER FATAL MESSAGE 742 (RDINIT)

ILLEGAL USAGE OF SCRATCH KEYWORD %1

743.0 *** USER FATAL MESSAGE 743 (RDEXPN)

A LOGICAL KEYWORD HAS NOT BEEN DEFINED.

User action: SPECIFY LOGICAL NAME(S) TO EXPAND THIS DBSET.

User information: LOGICAL NAMES ENABLE US TO OBTAIN THE PHYSICAL FILES WHICH
YOU INTEND TO ADD TO A PARTICULAR DBSET.

744.0 *** USER FATAL MESSAGE 744 (RDEXPN)

%1 IS AN INVALID EXPAND CARD KEYWORD

User information: THE VALID KEYWORDS FOR THE EXPAND STATEMENT ARE: "MASTER",
"DBALL", "USROBJ", "USRSOU", "OBJSCR", "DBSET_NAME", AND "SCRATCH"

745.0 *** USER FATAL MESSAGE 745

THE MAXIMUM NUMBER OF DBSETS ASSIGNABLE TO THIS RUN HAS BEEN EXCEEDED

User information: THE MAXIMUM NUMBER ALLOWED IS %1

746.0 *** USER FATAL MESSAGE 746 (RDEXPN)

THE MAXIMUM NUMBER OF LOGICALS THAT CAN BE ASSIGNED WITH THE EXPAND
COMMAND HAS BEEN EXCEEDED.

User information: THE MAXIMUM NUMBER ALLOWED IS %1

746.1 *** USER FATAL MESSAGE 746 (FNDUNT)

THE MAXIMUM NUMBER OF LOGICALS THAT CAN BE ASSIGNED WITH THE ASSIGN
COMMAND HAS BEEN EXCEEDED.

User information: THE MAXIMUM NUMBER ALLOWED IS %1

747.0 *** USER FATAL MESSAGE 747 (XDFNAM)

Main Index
 MSC Nastran Error Messages 121
Errors 0 - 999

THE MAXIMUM NUMBER OF MEMBERS FOR THE ABOVE DBSET HAS BEEN EXCEEDED.

User information: THE MAXIMUM NUMBER ALLOWED IS %1.

NOTES FOR DBSET SCRATCH:
1. IF NO MEMBERS ARE EXPLICITLY DEFINED FOR THE NON-SCR300 PARTITION, A
DEFAULT MEMBER SCRATCH IS PROVIDED.
2. IF NO MEMBERS ARE EXPLICITLY DEFINED FOR THE SCR300 PARTITION, A
DEFAULT MEMBER SCR300 IS PROVIDED IF SYSTEM(142)=2.

748.0 *** USER FATAL MESSAGE 748 (DBINIT)

NO MORE THAN TEN DBCLEAN COMMANDS ARE ALLOWED.

748.1 *** USER FATAL MESSAGE 748 (DBINIT)

NO MORE THAN ONE %1 COMMAND IS ALLOWED.

749.0 *** USER WARNING MESSAGE 749 (DBINIT)

WHEN THE PROJECT ID ON THE DBCLEAN CARD HAS NOT BEEN DEFINED, A DELE-
TION WITH "BLANK" PROJECT ID WILL BE ASSUMED.
THE PROJECT CARD HAS TO BE DEFINED PRIOR TO THE DBCLEAN CARD, WHEN DELE-
TIONS OF THE CURRENT PROJECT ID ARE DESIRED.

749.1 *** USER WARNING MESSAGE 749 (DBINIT)

WHEN THE PROJECT ID ON THE RESTART CARD HAS NOT BEEN DEFINED, A RESTART
WITH "BLANK" PROJECT ID WILL BE ASSUMED.
THE PROJECT CARD HAS TO BE DEFINED PRIOR TO THE RESTART CARD, WHEN
RESTARTS OF THE CURRENT PROJECT ID ARE DESIRED.

750.0 *** USER WARNING MESSAGE 750 (DBINIT)

ONLY ONE %1 COMMAND IS FUNCTIONAL. THE OTHERS ARE IGNORED

750.1 ***USER WARNING MESSAGE 750 (DBINIT)

DIRECTORY OUTPUT FORMAT OF FIRST DBDIR COMMAND WILL OVERWRITE THE
CURRENT DBDIR COMMAND

751.0 *** USER FATAL MESSAGE 751 (DBINIT)

Main Index
 122 MSC Nastran Error Messages
Errors 0 - 999

THE PRIMARY DATA BASE CONTAINS BAD OR NULL MASTER DIRECTORIES.

User actions:
1. CORRECT THE CAUSE OF THIS PROBLEM
2. RESUBMIT THE DATA BASE INITIALIZATION RUN.

752.0 *** USER WARNING MESSAGE 752 (DBINIT)

%1 CARDS IN DATA BASE INITIALIZATION RUNS ARE IGNORED.

753.0 *** USER FATAL MESSAGE 753 (XSEMIN)

THE SOLUTION SEQUENCE %1 DOES NOT EXIST IN THE FIST.

User information: IT HAS EITHER NOT BEEN ALLOCATED OR NOT BEEN LINKED.

User actions: SUPPLY THE NECESSARY LINK CARD, IF THIS SOLUTION SEQUENCE IS
BEING COMPILED IN THIS RUN.

755.0 *** USER FATAL MESSAGE 755 (XCSA)

THE ABOVE STATEMENT IS NOT SUPPORTED IN THE EXECUTIVE CONTROL SECTION,
BUT IN THE FILE MANAGEMENT SECTION (FMS).

User information: THE FMS IS DELIMITED BY ANY EXECUTIVE CONTROL STATEMENT.

User actions: MOVE THE STATEMENT ABOVE THE EXECUTIVE CONTROL SECTION.

756.0 *** USER FATAL MESSAGE 756

THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION.

756.1 *** USER FATAL MESSAGE 756 (XCSA)

THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION.

User information: THE RESTART STATEMENT IN THE EXECUTIVE CONTROL SECTION

HAS BEEN REPLACED BY THE RESTART FILE MANAGEMENT STATEMENT. SEE USER
MANUAL SECTION 2.2.

User information: This can occur if the RESTART statement of the File Management Section does not
begin in column one.

756.2 *** USER FATAL MESSAGE 756 (XCSA)

Main Index
 MSC Nastran Error Messages 123
Errors 0 - 999

THE %1 CARD IS NO LONGER SUPPORTED IN THE EXECUTIVE CONTROL SECTION.

User information: THE BEGIN STATEMENT IN THE EXECUTIVE CONTROL SECTION HAS
BEEN REPLACED BY THE SUBDMAP DMAP STATEMENT. SEE USER MANUAL chapter 5.

757.0 *** USER FATAL MESSAGE 757 (XCSA)

THE FIRST ALTER CARD OF A SUBDMAP MUST BE PRECEDED BY A COMPILE CARD THAT
SPECIFIES THE SUBDMAP NAME AND LOCATION.

User information: The ALTER Executive Control statement must immediately follow a COMPILE
statement.

758.0 *** USER FATAL MESSAGE 758 (XCSA)

THE READ EXECUTIVE COMMAND IS NO LONGER A VALID COMMAND, OR IT IS NOT
SUPPORTED IN THIS VERSION

760.0 *** USER FATAL MESSAGE 760 (XCSOL2)

THE ABOVE SOL CARD CONTAINS A DBSET VALUE EXCEEDING 8 CHARACTERS
VALUE = %1

761.0 *** USER FATAL MESSAGE 761 (XCSSUB)

INVALID SOLUTION SEQUENCE REQUESTED.

User information: VALID SOL NUMBERS ARE:

762.0 *** SYSTEM FATAL MESSAGE 762 (XGPI)

UNEXPECTED END-OF-RECORD DETECTED ON SCRATCH FILE %1

User information: THE SCRATCH FILE CONTAINING THE COMPILE STATEMENTS HAS
PROBABLY BEEN DESTROYED.

763.0 *** SYSTEM FATAL MESSAGE 763 (XXLOAD)

Main Index
 124 MSC Nastran Error Messages
Errors 0 - 999

INSUFFICIENT OPEN CORE AVAILABLE TO STORE DATA BASE DIRECTORY TABLES

User action: INCREASE MEMORY REQUEST AND RERUN.

Programmer information: THE AMOUNT OF MAIN MEMORY AVAILABLE BEFORE STORAGE

OF DIRECTORY TABLES = %1
FOLLOWING IS A DUMP OF VALUES IN THE COMMON BLOCK /XDIR/, WHICH TRACKS
THE POSITION OF DIRECTORY TABLES IN OPEN CORE AS THEY ARE READ FROM DISK.
NOTE: THE FIRST WORD OF EACH 3 WORD ENTRY IS UNUSED, THE SECOND WORD IS
THE TOP POINTER, AND THE 3RD WORD IS THE END POINTER+1 TO A DIRECTORY
TABLE THE DIFFERENCE BETWEEN THE SECOND WORD OF THE LAST NON-ZERO
ENTRY AND THE AVAILABLE OPEN CORE WILL INDICATE HOW MUCH SPACE THE LAST
TABLE TOOK UP BEFORE RUNNING OUT OF OPEN CORE THE DUMP OF THE COMMON
BLOCK /XDIR/ IS: %2

763.1 *** SYSTEM FATAL MESSAGE 763

Main Index
 MSC Nastran Error Messages 125
Errors 0 - 999

INSUFFICIENT OPEN CORE AVAILABLE TO STORE DATA BASE DIRECTORY TABLES

User action: INCREASE MEMORY REQUEST AND RERUN.

Programmer information: THE AMOUNT OF MAIN MEMORY AVAILABLE BEFORE STORAGE

OF DIRECTORY TABLES = %1
FOLLOWING IS A DUMP OF VALUES IN THE COMMON BLOCK /XDIR/, WHICH TRACKS
THE POSITION OF DIRECTORY TABLES IN OPEN CORE AS THEY ARE READ FROM DISK.
NOTE: THE FIRST WORD OF EACH 3 WORD ENTRY IS UNUSED, THE SECOND WORD IS
THE TOP POINTER, AND THE 3RD WORD IS THE END POINTER+1 TO A DIRECTORY
TABLE THE DIFFERENCE BETWEEN THE SECOND WORD OF THE LAST NON-ZERO
ENTRY AND THE AVAILABLE OPEN CORE WILL INDICATE HOW MUCH SPACE THE LAST
TABLE TOOK UP BEFORE RUNNING OUT OF OPEN CORE THE DUMP OF THE COMMON
BLOCK /XDIR/ IS:
%2
%3
%4
%5
%6
%7
%8
%9

Main Index
 126 MSC Nastran Error Messages
Errors 0 - 999

763.2 *** SYSTEM FATAL MESSAGE 763 (XDIRLD)

INSUFFICIENT OPEN CORE AVAILABLE TO STORE DATA BASE DIRECTORY TABLES

User action: INCREASE MEMORY REQUEST AND RERUN.

Programmer information: THE AMOUNT OF MAIN MEMORY AVAILABLE BEFORE STORAGE

OF DIRECTORY TABLES = %1
FOLLOWING IS A DUMP OF VALUES IN THE COMMON BLOCK /XDIR/, WHICH TRACKS
THE POSITION OF DIRECTORY TABLES IN OPEN CORE AS THEY ARE READ FROM DISK.
NOTE: THE FIRST WORD OF EACH 3 WORD ENTRY IS UNUSED, THE SECOND WORD IS
THE TOP POINTER, AND THE 3RD WORD IS THE END POINTER+1 TO A DIRECTORY
TABLE THE DIFFERENCE BETWEEN THE SECOND WORD OF THE LAST NON-ZERO
ENTRY AND THE AVAILABLE OPEN CORE WILL INDICATE HOW MUCH SPACE THE LAST
TABLE TOOK UP BEFORE RUNNING OUT OF OPEN CORE
THE DUMP OF THE COMMON BLOCK /XDIR/ IS:
%2
%3
%4
%5
%6
%7
%8
%9
%10
%11
%12

764.0 *** SYSTEM FATAL MESSAGE 764 (XSCNDM)

END-OF-FILE ENCOUNTERED WHILE READING SUBDMAP SOURCE

User information: SUBDMAP FILE MUST BE EMPTY

765.0 *** USER FATAL MESSAGE 765 (XREAD)

Main Index
 MSC Nastran Error Messages 127
Errors 0 - 999

END-OF-FILE ENCOUNTERED ON UNIT %1. THE INPUT FILE IS INCOMPLETE.

User information: THE FOLLOWING GUIDE LINES SHOULD BE FOLLOWED FOR PREPARA-
TION OF AN INPUT DECK. FILE MANAGEMENT SECTION (FMS) CAN BE ENDED BY
EITHER AN "ENDJOB" OR A NON-FMS CARD. EXECUTIVE CONTROL SECTION CAN
ONLY BE TERMINATED BY A "CEND" CARD.

User information: This error can also occur when there is a missing right or left parenthesis in an IF-
THEN DMAP statement.

767.0 *** USER FATAL MESSAGE 767 (XSCNDM)

END-OF-RECORD ENCOUNTERED WHILE READING SUBDMAP SOURCE

User information: SUBDMAP SOURCE IS MISSING AN "END" STATEMENT

769.0 *** USER FATAL MESSAGE 769 (XTRACT)

COMPILE CARD SYNTAX ERROR. MISSING "=" OR NAME FOLLOWING EQUAL SIGN

770.0 *** USER FATAL MESSAGE 770 (XCSSUB)

A VALUE IS NOT GIVEN FOR THE ID KEYWORD(SECONDARY SOLUTION SEQUENCE
NUMBER) ON THE SOL 600 EXECUTIVE CONTROL STATMENT.

773.0 *** USER FATAL MESSAGE 773 (DBDEF)

THE FOLLOWING PHYSICAL FILE ALREADY EXISTS.
LOGICAL NAME = %1
PHYSICAL FILE = %2

User information: NO ASSOCIATED DEFAULT FILES OR ASSIGNED DBSETS CAN EXIST

PRIOR TO THE DATA BASE INITIALIZATION RUN.

User action: DELETE THIS FILE AND RESUBMIT THE JOB.

774.0 *** USER FATAL MESSAGE 774 (XDMAP)

THE "END" STATEMENT IS MISSING FROM THE SUBDMAP SOURCE.

User information: THE "END" STATEMENT MARKS THE END OF EACH SUBDMAP.

Main Index
 128 MSC Nastran Error Messages
Errors 0 - 999

775.0 *** USER FATAL MESSAGE 775 (DBFASG)

NUMBER OF ASSIGNED PHYSICAL UNITS HAS BEEN EXCEEDED THE LIMIT =%1

776.0 *** USER WARNING MESSAGE 776 (DGETTS)

THERE IS NO REQUEST FOR PROCESSING OF THE TIME STAMP BLOCK.
IT IS ASSUMED FOR ANY EXISTING MASTER DBSET THAT:
1. THE DEFAULT BUFFER SIZE =%1
2. THE DEFAULT CLUSTER SIZE = 1

777.0 *** USER FATAL MESSAGE 777 (XTRLGN)

THE MAXIMUM NUMBER OF DBLOCATE DATABASES HAS BEEN EXCEEDED. MAXIMUM
NUMBER NUMBER ALLOWED =%1

778.0 *** SYSTEM FATAL MESSAGE 778 (GALLOX)

LOGIC ERROR.

User action: SEND RUN TO HEXAGON AB.

781.0 *** SYSTEM INFORMATION MESSAGE 781 (CGPIB)

SUBDMAP %1 HAS GENERATED ONE OR MORE FATAL ERROR(S) (SEE ABOVE MESSAGES)-
-NOGO = %2

782.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 782 (EVLMSG)

THE %1 BUFFSIZE PARAMETER CANNOT BE SMALLER THAN MACHINE DEFAULT =%2

User information: %3 BUFFSIZE PARAMETER IGNORED.

User action: USE THE INIT FMS STATEMENT TO SET THE DESIRED BUFFSIZE FOR EACH
INDIVIDUAL DBSET.

784.0 *** USER WARNING MESSAGE 784 (XCLNUP)

VERSION = %1 PROJECT = %2 OF THIS DATA BASE IS NOT VALID FOR RESTART
PURPOSES.

User information: This can occur in a run when a user's DMAP sequence and SYTEM cell 125 has not
been set to 1. If this is the case, insert PUTSYS(1,125) into the DMAP sequence.

Main Index
 MSC Nastran Error Messages 129
Errors 0 - 999

786.0 *** USER FATAL MESSAGE 786 (NDDL)

A CIRCULAR DEPENDENCY CONDITION WAS FOUND WHILE PROCESSING %1

User information: Examine the DEPEN statements and make the appropriate modifications.

787.0 *** USER FATAL MESSAGE 787 (XSEM)

ILLEGAL ALTER OR DMAP SEQUENCE DETECTED

User information: NO DMAP MODULES MAY BE EXECUTED BEFORE THE XSORT AND IFP1
MODULES.

User information: In Multi-Link (2 or more) Systems, Link 1 cannot be reentered. The only modules cur-
rently found exclusively in Link 1 are IFP1 and XSORT. Some statements may be executed before these
modules (arithmetic assignments/expressions). Put misplaced module after IFP1 module.

789.0 *** USER WARNING MESSAGE 789 (RDSDEL)

THE DBSET NAME "%1" SPECIFIED ON A DBSETDEL STATEMENT DOES NOT EXIST.

790.0 *** USER FATAL MESSAGE 790 (RDSDEL)

THE DBSETDEL STATEMENT HAS A SYNTAX ERROR NEAR COLUMN %1

User action: CHECK FOR ILLEGAL CHARACTERS, UNMATCHED PARENTHESES, OR DBSET

NAMES LONGER THAN 8 CHARACTERS.

791.0 *** USER FATAL MESSAGE 791 (RDSDEL)

THE DBSETDEL STATEMENTS HAVE MORE THAN %1 DBSET NAMES.

792.0 *** USER FATAL MESSAGE 792 (RDSDEL)

A DBSETDEL STATEMENT SPECIFIES "%1" DBSET WHICH SHOULD NOT BE DELETED.

793.0 *** USER FATAL MESSAGE 793 (CFLORD)

THE SIZE OF THE OSCAR FOR A SINGLE SUBDMAP HAS A LIMIT OF %1 WORDS WHICH
HAS BEEN EXCEEDED FOR THIS SUBDMAP (%2 WORDS REQUIRED).

User action: PARTITION THIS SUBDMAP INTO SMALLER SUBDMAPS.

Main Index
 130 MSC Nastran Error Messages
Errors 0 - 999

794.0 *** USER FATAL MESSAGE 794 (XSTORE)

THE OBJECT FOR THIS SUBDMAP IS NOT COMPATIBLE WITH THIS VERSION OF
NASTRAN.

User action: RECOMPILE THIS SUBDMAP.

795.0 *** USER FATAL MESSAGE 795 (CTYPE)

NUMBER OF CHARACTERS SPECIFIED FOR PARAMETER %1 EXCEEDS THE ALLOWABLE
LIMIT OF 80.

796.0 *** USER FATAL MESSAGE 796 (CCALL)

DATA BLOCK "%1" IS A DBVIEW NAME AND IS SPECIFIED AS INPUT OR OUTPUT IN A
CALL STATEMENT. THIS IS NOT ALLOWED.

797.0 *** USER FATAL MESSAGE 797 (CVIEW)

THE VIEWNAME %1 IS REFERENCED ON MORE THAN ONE DBVIEW STATEMENTS.

798.0 *** SYSTEM WARNING MESSAGE 798 (NDDL)

THE ITEM NAMES WITH (C) OPTION OF DATA BLOCK=%1, RECORD=%2,HAVE
EXCEEDED THE MAXIMUM NUMBER OF %3

Programmer action: REDUCE THE NUMBER OF (C) ITEM NAMES, OR, CHANGE THE INTER-
NAL LIMIT TO A GREATER NUMBER

799.0 *** USER FATAL MESSAGE 799 (SELCHK)

A SYNTAX ERROR WAS DETECTED WHILE PROCESSING A %1 CLAUSE ON A %2 STATE-
MENT.

User information: ITEM BEING PROCESSED IS %3

800.0 *** USER FATAL MESSAGE 800 (CVIEW1)

THE VIEW NAME = %1 SPECIFIED ON A DBVIEW STATEMENT IS ALSO SPECIFIED
AS A DATA BLOCK NAME ON A TYPE STATEMENT OR THE SUBDMAP STATEMENT.

801.0 *** USER FATAL MESSAGE 801 (CKALTR)

THE OFFSET ON ALTER/MALTER STRING%1 RESULTS IN A NEGATIVE LINE NUMBER.

Main Index
 MSC Nastran Error Messages 131
Errors 0 - 999

802.0 *** USER FATAL MESSAGE 802 (CKALTR)

NO MATCH WAS FOUND FOR STRING%1.

803.0 *** USER FATAL MESSAGE 803 (CKALTR)

DMAP LINE NUMBER K1 IS GREATER THAN DMAP LINE NUMBER K2.

804.0 *** USER FATAL MESSAGE 804 (CKALTR)

DMAP LINE NUMBER K1 OVERLAPS PREVIOUS ALTER.
PREVIOUS LINE NUMBER: %1 PREVIOUS K1:%2 PREVIOUS K2:%3
ALTER: %4

805.0 *** USER FATAL MESSAGE 805 (PRALTR)

THE INLINE SUBDMAP %1 CANNOT BE SEARCHED FOR ALTER/MALTER STRINGS.

User action: COMPILE THE SUBDMAP AND APPLY THE ALTERS IN SEPARATE RUNS.

806.0 *** USER FATAL MESSAGE 806 (RLALTR)

THE MALTER STATEMENTS LISTED BELOW AFTER THE USER ACTION, WERE NOT
FOUND IN THE DMAP SOURCE FILES.

User action: Check the following items:

1. Check the spelling of the MALTER string.
2. Ensure that an ENDALTER (or the CEND) statement appears immediately after the final statement
of the DMAP alter.

807.0 *** USER FATAL MESSAGE 807

THERE IS A SYNTAX ERROR IN %1 OF %2 STATEMENT.

809.0 *** USER FATAL MESSAGE 809

STRING1 IS NOT SPECIFIED ON THE MALTER STATEMENT ABOVE.

810.0 *** USER FATAL MESSAGE 810

COMPILATION OF REGULAR EXPRESSION FAILED WITH RETURN CODE:%1

Main Index
 132 MSC Nastran Error Messages
Errors 0 - 999

811.0 *** USER FATAL MESSAGE 811

SUBDMAP %1 IS SPECIFIED ON MORE THAN ONE COMPILE STATEMENT WITH DIFFER-
ENT SOUIN REQUESTS.

User action: SPECIFY SAME SOUIN ON THE COMPILE STATEMENTS.

812.0 *** USER FATAL MESSAGE 812

THE VALUE SPECIFIED FOR OCCURRENCE ON THE %1 STATEMENT IS LESS THAN
ZERO.

User information: THE VALUE FOR OCCURRENCE MUST BE AN INTEGER GREATER THAN
ZERO.

813.0 *** USER FATAL MESSAGE 813 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE A VERSION OF MSC NASTRAN PRIOR TO VERSION 69.

813.1 *** USER FATAL MESSAGE 813 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

SPECIFY PARAM, CHECKOUT, YES IN THE BULK DATA.

813.2 *** USER FATAL MESSAGE 813 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

SPECIFY PARAM, ALTRED, YES IN THE BULK DATA.
SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC
RESTART PROCESSING.

813.3 *** USER FATAL MESSAGE 813 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

813.4 *** USER FATAL MESSAGE 813 (XCSSUB)

Main Index
 MSC Nastran Error Messages 133
Errors 0 - 999

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC
RESTART PROCESSING.

813.5 *** USER FATAL MESSAGE 813 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User information: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED.

813.6 *** USER FATAL MESSAGE 813 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User information: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED.

SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC
RESTART PROCESSING.

814.0 *** USER WARNING MESSAGE 814 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE A VERSION OF MSC NASTRAN PRIOR TO VERSION 69.

814.1 *** USER WARNING MESSAGE 814 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

SPECIFY PARAM, CHECKOUT, YES IN THE BULK DATA.

814.2 *** USER WARNING MESSAGE 814 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

SPECIFY PARAM, ALTRED, YES IN THE BULK DATA.
SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC
RESTART PROCESSING.

Main Index
 134 MSC Nastran Error Messages
Errors 0 - 999

814.3 *** USER WARNING MESSAGE 814 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

814.4 *** USER WARNING MESSAGE 814 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User action: USE SOL %3.

SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC
RESTART PROCESSING.

814.5 *** USER WARNING MESSAGE 814 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User information: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED.

814.6 *** USER WARNING MESSAGE 814 (XCSSUB)

SOLUTION SEQUENCE%1 HAS BEEN %2

User information: ALTERNATE SOLUTION SEQUENCE%3 WILL BE EXECUTED.

SPECIFY PARAM, SERST, SEMI IN THE BULK DATA IF YOU WISH TO AVOID AUTOMATIC
RESTART PROCESSING.

815.0 *** USER FATAL MESSAGE 815 (RDINIT)

DBSET %1 IS ALREADY SPECIFIED ON AN INIT STATEMENT.

User information: ONLY ONE INIT STATEMENT MAY BE SPECIFIED PER DBSET.

816.0 *** USER WARNING MESSAGE 816 (RDACQU)

"NDDLOLD" IS NO LONGER AVAILABLE.

User information: "NDDL" WILL BE USED INSTEAD.

817.0 *** USER FATAL MESSAGE 817 (CKALTR)

THE FOLLOWING ALTER STATEMENT INSERTS AFTER THE END STATEMENT.
818.0 *** USER FATAL MESSAGE 818 (CHKFM)

Main Index
 MSC Nastran Error Messages 135
Errors 0 - 999

THE FMS STATEMENT %1 IS NOT UNIQUE.

User action: SPECIFY EITHER %2 OR %3

819.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 819 (EVLMSG)

INVALID CHARACTER "%1"

820.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 820 (EVLMSG)

OPERAND IS MISSING BEFORE "%1"

821.0 *** USER FATAL MESSAGE 821 (A?)

THE EQUAL SIGN IS MISSING IN A %1 %2

821.1 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 821 (EVLMSG)

THE EQUAL SIGN IS MISSING BEFORE "%1"

822.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 822 (EVLMSG)

EXTRA CHARACTERS ARE SPECIFIED ON DEFINE STATEMENT "%1"

823.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 823 (EVLMSG)

OPERATOR IS MISSING BEFORE "%1"

824.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 824 (EVLMSG)

RIGHT PARENTHESIS IS UNBALANCED AT "%1"

825.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 825 (EVLMSG)

RIGHT PARENTHESIS IS MISSING AFTER "%1"

826.0 *** USER WARNING MESSAGE 826 (SSWTOF)

THE DIAG%1 EXECUTIVE CONTROL STATEMENT IS INVALID.

User information: THE DIAG NUMBER MUST BE GREATER THAN ZERO AND LESS THAN 65.

827.0 *** SYSTEM FATAL MESSAGE 827 (SOPEN)

Main Index
 136 MSC Nastran Error Messages
Errors 0 - 999

UNABLE TO LOCATE FORUNIT INFORMATION FOR "%1" LOGICAL NAME.

User action: CONTACT HEXAGON AB REGARDING THIS ERROR.

828.0 *** USER FATAL MESSAGE 828 (SOPEN)
'FORM=FORMATTED' NOT SUPPORTED FOR "%1" LOGICAL NAME FOR 'SC' PLOTTER.

User action: ONLY USE 'FORM=FORMATTED' FOR 'NAST' PLOTTER.

829.0 *** USER FATAL MESSAGE 829 (SOPEN)

BINARY FORMAT CODE OTHER THAN 'UNFORMATTED' NOT SUPPORTED FOR "%1"
LOGICAL NAME

User action: ONLY USE 'FORM=UNFORMATTED' FOR BINARY FORMAT PLOT GENERA-
TION.

830.0 *** USER WARNING MESSAGE 830 (SOPEN)

INVALID POSTSCRIPT OPTION SPECIFIED IN 'SYSFIELD' FIELD FOR '%1' LOGICAL NAME
DATA.
OPTION IN ERROR IS '%2'

User action: CORRECT THIS OPTION.

831.0 *** USER WARNING MESSAGE 831 (SOPEN)

INVALID POSTSCRIPT OPTION SPECIFIED IN 'SYS' FIELD FOR '%1' LOGICAL NAME.
OPTION IN ERROR IS '%2'

User action: CORRECT THIS OPTION.

832.0 *** SYSTEM FATAL MESSAGE 832 (POSTSCRERROR)

INVALID PLOTTER COMMAND/DATA ENCOUNTERED IN POSTSCRIPT MODE.
EXPECTED %1, ACTUAL VALUE = %2

User action: IF THERE ARE PRIOR ERRORS IN POSTSCRIPT INITIALIZATION, CORRECT

THEM AND RERUN. OTHERWISE, CONTACT HEXAGON AB REGARDING THIS ERROR.

Main Index
 MSC Nastran Error Messages 137
Errors 0 - 999

975.0 *** USER WARNING MESSAGE 975,

XYTRAN DOES NOT RECOGNIZE %1 AND IS IGNORING

User information: Keyword XYPLOT package is not correct; see Section 13.3 of MSC NASTRAN Refer-
ence Manual.

976.0 *** USER WARNING MESSAGE 976,

OUTPUT DATA BLOCK%1 IS PURGED. XYTRAN WILL PROCESS ALL REQUESTS OTHER
THAN PLOT

User information: The data block output from XYTRAN has been purged; thus no XYPLOTs are possible.

977.0 *** USER WARNING MESSAGE 977,

FOLLOWING NAMED DATA-BLOCK IS NOT IN SORT-II FORMAT

User information: Probably a DMAP calling sequence error to XYTRAN. Only SORT2 data blocks can be
purged.

979.0 *** USER WARNING MESSAGE 979,

AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID%1
-%2- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA BLOCK%3
SUBCASE%4

979.1 *** USER WARNING MESSAGE 979,

AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID%1
-%2- CURVE IS BEING PASSED OVER. THE ID COULD NOT BE FOUND IN DATA BLOCK%3

User information: Curve request could not be found. Point, element or subcase requested was not on input
data block.

979.2 *** SYSTEM WARNING MESSAGE 979 (XYTRAN)

AN XY-OUTPUT REQUEST FOR POINT OR ELEMENT ID%1 - %2- CURVE IS BEING
IGNORED BECAUSE A LOCAL MEMORY AREA HAS BEEN EXCEEDED, REQUEST= %3 CUR-
RENT SIZE=%4.

User action: CONTACT HEXAGON AB DEVELOPMENT WITH INFORMATION.

Main Index
 138 MSC Nastran Error Messages
Errors 0 - 999

979.3 *** USER WARNING MESSAGE 979 (XYTRN2)

AN XY-OUTPUT REQUEST FOR FLUID POINT ID%1 -%2- CURVE IS BEING PASSED OVER.
THE ID COULD NOT BE FOUND IN DATA BLOCK%3%4

User information: Curve request could not be found. Point, frequency, mode number, panel name or
panel grid id was not on input data block.

979.4 *** SYSTEM WARNING MESSAGE 979 (XYTRAN)

AN XY-OUTPUT REQUEST FOR BEAM3 ELEMENT ID %1 IS IGNORED BECAUSE NASTRAN
CURRENTLY DOES NOT SUPPORT XY-OUTPUT REQUEST FOR STRESS, STRAIN AND
FORCE OF BEAM3 ELEMENT.

980.0 *** USER WARNING MESSAGE 980,

INSUFFICIENT CORE TO HANDLE ALL DATA FOR ALL CURVES OF THIS FRAME
ID =%1 COMPONENT =%2 COMPONENT =%3 DELETED FROM OUTPUT

User information: Increase memory request.

981.0 *** USER WARNING MESSAGE 981,

COMPONENT =%1 FOR ID=%2 IS TOO LARGE. THIS COMPONENTS CURVE NOT
OUTPUT

User information: Component request was larger than the data item available; see Section 13.3 of MSC
NASTRAN Reference Manual.

981.1 *** USER WARNING MESSAGE 981,

COMPONENT =COMPONENT =%1 FOR ID=%2 IS NULL. THIS COMPONENTS CURVE
NOT OUTPUT.

982.0 *** USER WARNING MESSAGE 982.

FORMAT OF %1 INCOMPATIBLE WITH SDR3 DESIGN. CODE =%2

Main Index
 MSC Nastran Error Messages 139
Errors 0 - 999

User information: This message appears when the SDR3 module encounters trouble. he exact nature of the
problem can be detected from the "code" number. The file type causing the problem can be determined
from its name (for example, OESi is the stress output file, and OUGVi the displacement, velocity, and
acceleration output file). The function of this module is to convert SORT1 output tables to SORT2 tables.
It operates on one output type per pass (for example, displacements, then velocities, then stresses in BAR
elements, then ROD elements, etc.). Since the user controls the content and size of the output tables with
case control and plot requests, it is often possible to avoid these errors, as described below.

Codes Cause and User Action

110 Insufficient memory. Increase memory request, or decrease the number 140 of variables
output on one run by using restarts for additional output.
150
The following codes should not occur on standard solution sequences. Please send any such runs to
Hexagon. If they occur on user written DMAPs, it is likely that an illegal input block is used, or that the
input block is not correctly formatted.

Codes Cause and User Action

100 The ID record is missing on the input file.
120
101 Missing data record.
102 Wrong number of words in input block.
122
112 The number of words per record is not an integer multiple of the number 142 of words
per entry.
152
165 Logic error or ID record indicates zero words.

984.0 *** USER WARNING MESSAGE 984.

OUTPUT DATA BLOCK NO.%1 IS PURGED. SDR3 CANNOT PROCESS INPUT DATA BLOCK
%2

User information: Probably DMAP calling sequence error. Needed output is purged.

Main Index
 140 MSC Nastran Error Messages
Errors 0 - 999

985.0 *** USER WARNING MESSAGE 985 (USRMSG)

If SORT2 output is requested, then all subcases must have the same output requests.

User action: An easy way to do this is to place all output requests above the first subcase

992.0 *** USER WARNING MESSAGE 992,

XYPLOT INPUT DATA FILE I.D. RECORDS TOO SHORT. XYPLOT ABANDONED.

User information: The input data file records have invalid word counts and further plotting is not feasible.

993.0 *** USER WARNING MESSAGE 993,

XYPLOT FOUND ODD NR. OF VALUES FOR DATA PAIRS IN FRAME%1, CURVE NR.%2.
LAST VALUE IGNORED.

User information: May indicate a bad input file, but plotting continues.

994.0 *** USER WARNING MESSAGE 994,

XYPLOT OUTPUT FILE NAME %1 NOT FOUND. XYPLOT ABANDONED.

User information: PLT2 is missing.

997.0 *** USER WARNING MESSAGE 997,

NR.%1. FRAME NR.%2 INPUT DATA INCOMPATIBLE. ASSUMPTIONS MAY PRODUCE
INVALID PLOT.

User information: Nr. %1 may take any value from 1 to 4 with the following meaning:
1 - Specified X maximum equal X minimum. If this value is zero, then X maximum is set to 5.0 and X min-
imum to -5.0, otherwise 5 times the absolute value of X maximum is added to X maximum and
subtracted from X minimum.
2 - Specified X maximum is smaller than X minimum. The values are reversed.
3 - Same meaning as number 1 except for Y maximum and Y minimum.
4 - Same meaning as number 2 except for Y maximum and Y minimum.

Main Index
 MSC Nastran Error Messages 141
Errors 1000 - 1999

Errors 1000 - 1999

1001.0 *** SYSTEM FATAL MESSAGE 1001 (BGNSYS)
ERROR IN READING FORTRAN UNIT 2 FILE

1002.0 *** SYSTEM FATAL MESSAGE 1002 (BGNSYS)

PREMATURE END-OF-FILE IN READING FORTRAN UNIT 2 FILE

1003.0 *** SYSTEM FATAL MESSAGE 1003 (OPNPFL)

1003.1 *** SYSTEM FATAL MESSAGE 1003 (CLSPFL)

1003.2 *** SYSTEM WARNING MESSAGE 1003 (FORTIO)

UNIT %1 DOES NOT HAVE A CORRESPONDING VALUE IN FORUNT ARRAY.

User information: UNITS MUST BE ASSIGNED A PHYSICAL FILE NAME USING AN ASSIGN
STATEMENT.

User information: As an example, for punch files unit 7 must be one of the units on the ASSIGN
statement.

1003.3 *** SYSTEM FATAL MESSAGE 1003 (ISHELL)

UNIT %1 DOES NOT HAVE A CORRESPONDING VALUE IN FORUNT ARRAY.

User information: UNITS MUST BE ASSIGNED A PHYSICAL FILE NAME USING AN ASSIGN
STATEMENT.

User information: As an example, for punch files unit 7 must be one of the units on the ASSIGN state-
ment.

1004.0 *** SYSTEM FATAL MESSAGE 1004 (XSEM)

FORTRAN UNIT OPEN/CREATE ERROR.

User information: UNIT=%1, IOSTAT=%2

Main Index
 142 MSC Nastran Error Messages
Errors 1000 - 1999

1004.1 *** SYSTEM FATAL MESSAGE 1004 (XSEM)

FORTRAN UNIT CLOSE/DELETE ERROR.

User information: UNIT=%1, IOSTAT=%2

User information: A possible cause is that you ran out of disk space.

1004.2 *** USER FATAL MESSAGE 1004 (CLSPFL)

1004.3 *** SYSTEM FATAL MESSAGE 9910 (various)

UNABLE TO CREATE FORTRAN FILES ENTRY FOR UNIT %1 FOR LOGICAL NAME %2
USING DEFAULT FILE NAME. ERROR CODE = %3.

1005.0 *** SYSTEM FATAL MESSAGE 1005 (ENDSYS)

ERROR IN WRITING FORTRAN UNIT 2 FILE

1006.0 *** SYSTEM WARNING MESSAGE 1006 (F04SUM)

CANNOT FIND END FOR %1%2 BEGIN AT LINE NUMBER %3

1007.0 *** SYSTEM WARNING MESSAGE 1007 (F04SUM)

LOGIC ERROR %1 WITH FOLLOWING RECORD(S):
%2
%3

System information:
Possible cause: If DIAG 49 is turned on and the time spent in some of the modules are too small to cause
the END statement to be printed, then the message may be issued without summing the time spent in an
individual module. This can occur even when there are other modules that substantial time.

User action: Add the following NASTRAN System Cell to your run:
NASTRAN SYSTEM(20) = 0

1008.0 *** SYSTEM WARNING MESSAGE 1008 (F04SUM)

CANNOT FIND END FOR %1 AT LINE NUMBER%2

1009.0 *** USER INFORMATION MESSAGE 1009 (F04SUM)

STATISTICAL SUMMARY OF ABOVE LOG FILE FOLLOWS.

Main Index
 MSC Nastran Error Messages 143
Errors 1000 - 1999

1010.0 *** USER INFORMATION MESSAGE 1010 (F04SUM)

LOG FILE DOES NOT CONTAIN ANY PERTINENT STATISTICAL INFORMATION

1011.0 *** USER FATAL MESSAGE 9911 (INPTxx)

UNABLE TO PROCESS INPUT FILE CONNECTED TO UNIT %1 FOR LOGICAL NAME %2
BECAUSE IT HAS INVALID BINARY FORMAT.
FILE HAS %3 FORMAT, THIS PLATFORM REQUIRES %4 FORMAT.

1012.0 *** USER FATAL MESSAGE 1012 (GALLOX)

DBSET %1 IS FULL AND NEEDS TO BE EXPANDED.

User action: SEE THE MSC NASTRAN CONFIGURATION AND OPERATIONS GUIDE OR
KB8012329 ON THE MSC WEB SITE FOR METHODS TO MAKE LARGER DATABASES.

User information: See Chapter 12. Also, see Error Report 3652 in 17.2 of MSC NASTRAN Reference
Manual.

1013.0 *** SYSTEM FATAL MESSAGE 1013

CANNOT FIND CORRECT CLUSTER POINTER RECORD

1014.0 *** SYSTEM FATAL MESSAGE 1014 (GBKZ67)

ERROR IN LOOKING UP CLUSTER NUMBER

System information: This has been observed when the maximum number of superelements or modules has
been exceeded.

1015.0 *** SYSTEM FATAL MESSAGE 1015 (GBKZ67)

PHYSICAL FILE NOT FOUND IN FILE ASSIGNMENT TABLE

System information: This may be on restart issued if scratch files were not deleted in previous run. It may
also be issued if there is insufficient memory.

Main Index
 144 MSC Nastran Error Messages
Errors 1000 - 1999

1016.0 *** SYSTEM FATAL MESSAGE 9913 (OUTPX2)

** INTERNAL LOGIC ERROR ** UNABLE TO GET FILE HANDLE FOR UNIT %1, ERROR
CODE = %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

1017.0 *** SYSTEM FATAL MESSAGE 1017 (GBKZ67)

NO CLUSTER RECORD INCORE FOR DATA BASE DIRECTORY
*** USER FATAL MESSAGE 1019 (OPNPFL)

1020.0 *** SYSTEM FATAL MESSAGE 1020 (ZIO)

UNABLE TO PERFORM LOGICAL TO PHYSICAL FILE ASSIGNMENT

1021.0 *** SYSTEM FATAL MESSAGE 1021 (ZIO)

ERROR OCCURRED IN BIORD

1022.0 *** SYSTEM FATAL MESSAGE 1022 (ZIO)

ERROR OCCURRED IN BIOWRT

1023.0 *** SYSTEM FATAL MESSAGE 1023 (ZIO)

ATTEMPT TO OPEN A FILE WHICH WAS PREVIOUSLY OPENED (%1)

1026.0 *** SYSTEM FATAL MESSAGE 1026 (ZIO)

ATTEMPT TO ACCESS A FILE WHICH IS NOT OPENED

1027.0 *** SYSTEM FATAL MESSAGE 1027 (ZIO)

SAVPOS ATTEMPTED ON A FILE WHICH WAS OPENED TO UPDATE

1028.0 *** SYSTEM FATAL MESSAGE 1028 (ZIO)

FILPOS ATTEMPTED ON A FILE WHICH WAS OPENED TO APPEND

1029.0 *** SYSTEM FATAL MESSAGE 1029 (ZIO)

ATTEMPT TO READ FROM AN EMPTY FILE

1030.0 *** SYSTEM FATAL MESSAGE 1030 (ZIO)

BLOCK NUMBER MISMATCH IN READ

Main Index
 MSC Nastran Error Messages 145
Errors 1000 - 1999

1031.0 *** SYSTEM FATAL MESSAGE 1031 (ZIO)

FIELD 3 OF CONTROL WORD NOT EQUAL TO RECORD LENGTH.
FIELD3 =%1 REC LENGTH =%2

System information: One cause of this may be an illegal BUFFSIZE (e.g., larger than allowed).

1032.0 *** SYSTEM FATAL MESSAGE 1032 (ZIO)

ATTEMPT TO READ PAST END OF DATA

1033.0 *** SYSTEM FATAL MESSAGE 1033 (ZIO)

FILE %1 NOT FOUND IN FIST

1034.0 *** SYSTEM FATAL MESSAGE 1034 (ZIO)

UNRECOGNIZED CONTROL WORD ENCOUNTERED AFTER FILPOS OPERATION

1035.0 *** SYSTEM FATAL MESSAGE 1035 (ZIO)

ATTEMPT TO BCKREC PAST BEGINNING OF BLOCK

1036.0 *** SYSTEM FATAL MESSAGE 1036 (ZIO)

UNRECOGNIZED CONTROL WORD ENCOUNTERED AFTER BCKREC OPERATION

1037.0 *** SYSTEM FATAL MESSAGE 1037 (ZIO)

ATTEMPT TO BCKREC ON A FILE OPENED FOR APPEND

1038.0 *** SYSTEM FATAL MESSAGE 1038 (ZIO)

ILLEGAL OPCODE =%1

1041.0 *** SYSTEM FATAL MESSAGE 1041 (GALLEX)

THE DB-DIRECTORY FOR %1 HAS BEEN FILLED UP AND IS NOT EXPANDABLE.

User action:
1. DELETE UNWANTED FILES FROM THE DBSET IF PERMANENT.
2. INCREASE BUFFSIZE AND/OR CLUSTER SIZE FOR THIS DBSET, IF TEMPORARY.

Main Index
 146 MSC Nastran Error Messages
Errors 1000 - 1999

1042.0 *** SYSTEM FATAL MESSAGE 1042 (GALLEX)

FILE %1 NOT FOUND IN FIST
1046.0 *** USER FATAL MESSAGE 1046, (INQPFL)
FORTRAN INQUIRE ERROR
IOSTAT = %1, %2
LOGICAL = %3 FILE = %4

1047.0 *** USER FATAL MESSAGE 1047

ILLEGAL INPUT FOR SUBDMAP %1. THE ABOVE COMMAND IS AN NDDL COMMAND.

User action: CORRECT OR REMOVE THE SUBDMAP COMPILE CARD.

User information: This error occurs when compiling a SUBDMAP which contains NDDL statements.
Correct your COMPILE statement to specify that you are compiling NDDL, using the NDDL keyword
on the COMPILE statement.

1048.0 *** USER FATAL MESSAGE 1048

ILLEGAL INPUT FOR NDDL %1. THE ABOVE COMMAND IS NOT AN NDDL COMMAND.

User action: CORRECT OR REMOVE THE NDDL COMPILE CARD.

User information: This error occurs when compiling an NDDL which contains DMAP statements. Cor-
rect your COMPILE card to specify that you are compiling SUBDMAP, using the SUBDMAP keyword
on the COMPILE card.

1049.0 *** USER FATAL MESSAGE 1049 (XSPAC)

AMOUNT OF USER OPENCORE(HICORE), MASTER(RAM)
SCRATCH(MEM) AND BUFFER POOL SIZE HAVE EXCEEDED THE MSC NASTRAN
MEMORY LIMIT:
MSC NASTRAN MEMORY LIMIT =%1 WORDS
USER OPENCORE(HICORE) =%2
MASTER(RAM) SIZE =%3
SCRATCH(MEM) SIZE =%4 (%5 BUFFERS)
BUFFER POOL SIZE =%6 (%7 BUFFERS)

User action: DECREASE THE SUM OF HICORE, MASTER(RAM), SCRATCH(MEM) AND BUF-
FER POOL SIZE TO FIT WITHIN THE MSC NASTRAN MEMORY LIMIT.

Main Index
 MSC Nastran Error Messages 147
Errors 1000 - 1999

1049.1 *** USER FATAL MESSAGE 1049 (XSPAC)

Amount of MASTER(RAM), SCRATCH(MEM) and BUFFER POOL size have exceeded the
NASTRAN MEMORY limit:
MASTER(RAM) SIZE =%2
SCRATCH(MEM) SIZE =%3 (%4 BUFFERS)
BUFFER POOL SIZE =%5 (%6 BUFFERS)
(SUM OF THE ABOVE) =%7 words
NASTRAN MEMORY LIMIT =%1 words

User action: Increase the MEMORY or decrease one or more of MASTER(RAM), SCRATCH(MEM) and
BUFFER POOL.

1050.0 *** USER WARNING MESSAGE 1050 (DBPRVR)

THE PROJECT ID = '%1' SPECIFIED ON THE DBDIR CARD IS NOT DEFINED IN THIS DATA
BASE

1051.0 *** USER WARNING MESSAGE 1051 (DBPRVR)

THE VERSION ID = %1 OF PROJECT '%2' ON THE DBDIR CARD HAS ALREADY BEEN
DELETED.

User information: THIS DBDIR CARD IS IGNORED.

1052.0 *** USER WARNING MESSAGE 1052 (DBPRVR)

THE VERSION ID = %1 OF PROJECT '%2' ON THE DBDIR CARD HAS NEVER BEEN CRE-
ATED.

User information: THIS DBDIR CARD IS IGNORED.

1053.0 *** USER FATAL MESSAGE 1053 (GPVTSH)

PARAMETER INPUT DATA ERROR, ILLEGAL VALUE FOR PARAMETER NAMED %1.

1102.0 *** SYSTEM WARNING MESSAGE 1102 (BPOPEN)

Main Index
 148 MSC Nastran Error Messages
Errors 1000 - 1999

BUFFER FOUND IS ALREADY AN ACTIVE BUFFER

1103.0 *** SYSTEM FATAL MESSAGE 1103 (BPOPEN)

LOGIC ERROR IN BUFFER POOL MANAGEMENT LINK LIST. BUFFER IN LINK LIST OF %1
EXCEEDS DEFAULT SIZE OF %2

User action: PLEASE SEND RUN TO HEXAGON AB.

System information: This has been observed for very dense complex unsymmetric matrices. An avoidance
is to increase WSL or decrease HICORE and REAL. See Error Report 3670 in section 17.4 of MSC NAS-
TRAN Reference Manual.

1104.0 *** SYSTEM FATAL MESSAGE 1104 (XCHK)

FDICT TABLE IS INCORRECT

1105.0 *** SYSTEM WARNING MESSAGE 1105 (BPSIZE)

NO MEMORY AVAILABLE FOR BUFFER POOLING.

Programmer information: BPOOL = %1 MAXBUF = %2 NEEDBF = %3 LIMIT = %4

1105.1 *** USER FATAL MESSAGE 1105 (XCHK)

CANNOT FIND DATA BLOCK NAMED %1 HEADER RECORD = %2

1106.0 *** SYSTEM FATAL MESSAGE 1106

ATTEMPT TO CLOSE FILE %1 WHICH IS NOT CURRENTLY OPENED.

User information: THE ABOVE FILE CONTAINS THE DATA BASE DIRECTORY

1106.1 *** SYSTEM FATAL MESSAGE 1106 (CLSDBS)

ATTEMPT TO CLOSE FILE %1 WHICH IS NOT CURRENTLY OPENED.

User information: THE ABOVE FILE CONTAINS THE DATA BASE DIRECTORY

1106.2 *** SYSTEM FATAL MESSAGE 1106 (CLSDBM)

Main Index
 MSC Nastran Error Messages 149
Errors 1000 - 1999

ATTEMPT TO CLOSE FILE %1 WHICH IS NOT CURRENTLY OPENED.

User information: THE ABOVE FILE CONTAINS THE DATA BASE BIT MAP

1107.0 *** USER FATAL MESSAGE 1107 (OPNENT)

A NON-400 FIST NUMBER OF %1 USED, WHEN ATTEMPTING TO OPEN THE DBENTRY
FILE
1107.1 *** SYSTEM FATAL MESSAGE 1107 (CLSENT)
A NON-400 FIST NUMBER OF %1 USED, WHEN ATTEMPTING TO CLOSE THE DBENTRY
FILE

1108.0 *** SYSTEM FATAL MESSAGE 1108 (XCHK)

PURGE TABLE OVERFLOWED

1108.1 *** SYSTEM FATAL MESSAGE 1108 (ZRDBLK)

TEMPORARY NDDL BULK ENTRY NAME TABLE OVERFLOWED

1112.0 **** SYSTEM FATAL MESSAGE 1112 (LCLEAD)

ATTEMPT TO ADD A DBENTRY IN A LOCATION WHERE ANOTHER DBENTRY ALREADY
EXISTS.

User action: CONTACT HEXAGON AB.

Programmer information: DBENTRY POINTER, /FREEX/ AND CONTENTS OF DBENTRY ARE:

%1
%2
%3

1112.1 **** SYSTEM FATAL MESSAGE 1112 (DBEADD)

ATTEMPT TO ADD A DBENTRY IN A LOCATION WHERE ANOTHER DBENTRY ALREADY
EXISTS.

User action: CONTACT HEXAGON AB.

1113.1 *** SYSTEM WARNING MESSAGE 1113 (DBEDEL)

Main Index
 150 MSC Nastran Error Messages
Errors 1000 - 1999

WHILE ATTEMPTING TO DECREMENT THE PVA TABLE COUNTER, NO ENTRIES WERE

FOUND FOR THIS PATH.

User action: MAKE RUN USING FMS COMMAND DBFIX

1114.0 *** SYSTEM FATAL MESSAGE 1114 (XREMOV)

POTENTIAL INFINITE-LOOP PROBLEM EXISTS IN DBENTRY TABLE FOR DATA BLOCK =
%1

User action: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX

1114.1 *** SYSTEM FATAL MESSAGE 1114 (XECHRD)

POTENTIAL INFINITE-LOOP PROBLEM EXISTS IN DBENTRY TABLE

User action: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX

Programmer information: ENTPTR=%1

CNTBLK=%2

1114.2 *** SYSTEM FATAL MESSAGE 1114 (XECHAD)

POTENTIAL INFINITE-LOOP PROBLEM EXISTS IN DBENTRY TABLE

User action: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX

Programmer information: ENTPTR=%1 ENTPT2=%2

CNTBLK=%3 %4%5%6

1114.3 *** SYSTEM FATAL MESSAGE 1114 (PRJVFN)

POTENTIAL INFINITE-LOOP PROBLEM EXISTS IN DBENTRY TABLE FOR %1 = %2

User action: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX.

1114.4 *** SYSTEM FATAL MESSAGE 1114 (DBXREM)

Main Index
 MSC Nastran Error Messages 151
Errors 1000 - 1999

POTENTIAL INFINITE-LOOP PROBLEM EXISTS IN DBENTRY TABLE FOR DATA BLOCK =

%1

User action: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX.

1115.0 *** SYSTEM FATAL MESSAGE 1115 (XEQDIN)

ERROR OPENING THE DATABASE TRANSACTION FILE (DBRQUE). GINO FILE NAME = %1

User action: SEND THIS RUN TO HEXAGON AB.

System information: This has been observed when using the SOLVE module and the B matrix in A x = B
is null. Explicitly define an identity matrix for the B matrix input. If the SOLVE module is not used, then
contact Hexagon.

1117.0 *** SYSTEM FATAL MESSAGE 1117 (DBESEA)

DBENTRY TABLE POINTER TO DB DIRECTORY EQUALS 0.

1119.0 *57* SYSTEM WARNING MESSAGE 1119 (DIRCLN)

ATTEMPTING TO DELETE AN EMPTY DB-DIRECTORY

User information: THIS MAY INDICATE A PROBLEM.

NAME=%1 ON DBSET %2

User information: This message will be issued if a data block name appears twice as input to a module and
its LTU (last-time-used) is also at that module. For example, in the following module, SMPYAD
PHI,MAA,PHI,,,/X/3////1 $ this error would occur if this were the last time PHI were used.
This does not indicate a problem.

1120.0 *** SYSTEM FATAL MESSAGE 1120 (DIRPT3)

Main Index
 152 MSC Nastran Error Messages
Errors 1000 - 1999

THE DATA BASE DBENTRY TABLE HAS NO DBSET/FILPOS OFFSET

User information: THIS MAY INDICATE THAT THE DATABASE DIRECTORY HAS BEEN
DESTROYED

User action: TURN ON DIAG 2 AND SEND RUN TO HEXAGON AB

Programmer action: VARIABLES OF INTEREST:

NAME = %1 DBEPTR,DBDPTR,DBSPTR = %2

1121.0 *** USER WARNING MESSAGE 1121 (DIRPT2)

ROUTINE DIRPT2 WAS CALLED WITH AN ILLEGAL OPCODE = %1.

User information: NO ***DIAG 2*** PRINT HAS BEEN PRODUCED.

1122.0 *** USER FATAL MESSAGE 1122 (DIRPT3)

THE FILE ASSIGNMENT (DBSPACE) TABLE DOES NOT CONTAIN AN ENTRY FOR THE
SCRATCH DBSET, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN.

1123.0 *** SYSTEM FATAL MESSAGE 1123 (GDBSNO)

DATABASE NUMBER:%1 IS OUT OF RANGE. DBSPTR =%2

User action: MAKE SURE ALL ATTACHED DATABASE(S), INCLUDING THE DELIVERY DATA-
BASE, ARE VERSION (e.g. 69) COMPATIBLE.

1124.0 *** USER FATAL MESSAGE 1124 (GNFIST)

AN APPENDABLE OUTPUT FILE %1 CANNOT BE APPENDED ON A DBLOCATE DATABASE.

User action: REMOVE THIS DATABLOCK NAME FROM THE DBLOCATE COMMAND AND
RERUN JOB OR COPY THE DATABLOCK TO THIS DATABASE.

1125.0 ****SYSTEM FATAL MESSAGE 1125 (GNFIST)

Main Index
 MSC Nastran Error Messages 153
Errors 1000 - 1999

PROGRAM LOGIC ERROR -- UNGENERATED OUTPUT DATA BLOCK %1(%2) DETECTED

AT CONCLUSION OF FILE ALLOCATION ROUTINE.

User action: CONTACT HEXAGON AB.

1126.0 *** USER FATAL MESSAGE 1126 (GNFIST)

DMAP MODULE %1 IS ATTEMPTING TO OUTPUT DATABLOCK %2 NAME = %3, WHICH
ALREADY EXISTS.

User action: DELETE THE DATABLOCK, OR USE FILE %4=OVRWRT. IF THIS IS NONLINEAR
ANALYSIS, THIS ERROR CAN OCCUR WHEN ITERATIONS FOR THE CURRENT SUBCASE
HAVE BEEN TERMINATED WITHOUT CONVERGENCE.

1127.0 *** USER FATAL MESSAGE 1127 (SALLOC)

DBUNLOAD IS ATTEMPTING TO ACCESS DATA BLOCK NAME = %1 WHICH IS ON AN
UNAVAILABLE DBSET =%2

1127.1 *** USER FATAL MESSAGE 1127 (GNFIST)

DMAP MODULE %1 IS ATTEMPTING TO ACCESS DATA BLOCK %2 NAME = %3 WHICH IS
ON AN UNAVAILABLE DBSET

1128.0 *** SYSTEM FATAL MESSAGE 1128 (GNLOC)

Main Index
 154 MSC Nastran Error Messages
Errors 1000 - 1999

A LOCATION PARAMETER HAS AN INCORRECT TYPE AND/OR LENGTH.

User information:
1. GNLOC PERFORMS MODULE FILE ALLOCATIONS
2. LOCATION PARAMETER MUST BE TYPE 3 (BCD) AND LENGTH 2

User action: SEND RUN TO HEXAGON AB

Programmer information:
1. THE DBDIR RECORD INDICATES TYPE = %1 AND LENGTH = %2
2. THE FULL DBDIR RECORD IS:
%3%4%5
VALUE = %6
%7
%8
Programmer action: THE NDDL COMPILER SHOULD HAVE CAUGHT THIS DISCREPANCY.
THE DATA BASE MAY HAVE BEEN DESTROYED

1129.0 *** USER FATAL MESSAGE 1129 (GNLOC)

THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR LOCATION
PARAMETER %1 = %2

User information:
1. GNLOC PERFORMS MODULE FILE ALLOCATIONS
2. THE DBSET %3 WAS NOT ALLOCATED FOR THIS RUN
Programmer information: THE FULL DBDIR RECORD CONTAINING THIS LOCATION
PARAMETER IS: %4%5%6%7

1130.0 *** SYSTEM FATAL MESSAGE 1130 (GNLOC)

Main Index
 MSC Nastran Error Messages 155
Errors 1000 - 1999

PARAMETERS USED AS "LOCATION" PARAMETERS MUST BE OF TYPE=3 (BCD) AND

LENGTH=2.

User information: THE PARAMETER DBNAME TABLE ENTRY FOR THIS PARAMETER IS :
%1%2

User action: SEND RUN TO HEXAGON AB.

Programmer information:
1. THE NDDL COMPILER SHOULD HAVE CAUGHT THIS ERROR.
2. IF THE PARAMETER ENTRY DUMP IS CORRECT, THEN OPEN CORE MAY HAVE
BEEN OVERWRITTEN, OR
3. THE DATA BASE MAY HAVE BEEN DESTROYED/DAMAGED.

1131.0 *** SYSTEM FATAL MESSAGE 1131 (GNPARM)

THE POINTER INTO THE VPS TABLE FROM THE OSCAR IS ZERO

User action: SEND RUN TO HEXAGON AB.

Programmer information: THIS ERROR MAY MEAN THAT OPEN CORE HAS BEEN OVER-
WRITTEN

1133.0 *** USER FATAL MESSAGE 1133 (GNXFST)

INVALID INPUT FIST NUMBER = %1
JOB TERMINATED DUE TO ABOVE ERROR

1135.0 *** USER FATAL MESSAGE 1135 (XTVPS2)

DMAP MODULE %1 IS ATTEMPTING TO ACCESS PARAMETER NAME = %2
WHICH IS ON AN UNAVAILABLE DBSET = %3 IN DATABASE NUMBER (DBSNO) = %4

1135.1 *** USER FATAL MESSAGE 1135

THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE %1 DBSET,
INDICATING IT WAS NOT ALLOCATED FOR THIS RUN.

User information: Check ASSIGN FMS statements and DBS keyword for misspelled or improper physical
file specification.

Main Index
 156 MSC Nastran Error Messages
Errors 1000 - 1999

1135.3 *** USER FATAL MESSAGE 1135 (GNPREP)

THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE SCRATCH
DBSET, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN.

User information: Check ASSIGN FMS statements and DBS keyword for misspelled or improper physical
file specification.

1135.4 *** USER FATAL MESSAGE 1135 (GNPARM)

DMAP MODULE %1 IS ATTEMPTING TO ACCESS PARAMETER NAME = %2
WHICH IS ON AN UNAVAILABLE DBSET = %3 IN DATABASE NUMBER (DBSNO) =%4

1135.5 *** USER FATAL MESSAGE 1135 (GNLOC)

THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE MASTER
DBSET, INDICATING IT WAS NOT ALLOCATED FOR THIS RUN.

User information: Check ASSIGN FMS statements and DBS keyword for misspelled or improper physical
file specification.

1135.6 *** USER FATAL MESSAGE 1135 (GNALOC)

THE FILE ASSIGNMENT (DBSPACE) TABLE CONTAINS NO ENTRY FOR THE SCRATCH OR
OBJSCR DBSETS, INDICATING THEY WERE NOT ALLOCATED FOR THIS RUN.

User information: Check ASSIGN FMS statements and DBS keyword for misspelled or improper physical
file specification.

1139.0 *** SYSTEM FATAL MESSAGE 1139 (QVAGEN)

THE MAXIMUM QUALIFIER TABLE LENGTH HAS BEEN EXCEEDED

User action: CONTACT HEXAGON AB REGARDING THIS ERROR.

Programmer information: THE MAXIMUM LENGTH IS %1

Programmer action: INCREASE MAXIMUM TABLE LENGTH IN CALLING ROUTINE.

Main Index
 MSC Nastran Error Messages 157
Errors 1000 - 1999

1139.1 *** SYSTEM FATAL MESSAGE 1139 (QUASEA)

THE MAXIMUM QUALIFIER TABLE LENGTH HAS BEEN EXCEEDED

User action: CONTACT HEXAGON AB REGARDING THIS ERROR.

Programmer information: THE MAXIMUM TABLE LENGTH IS %1

THE REQUESTED NUMBER OF QUALIFIER IS %2

Programmer action: INCREASE MAXIMUM TABLE LENGTH IN CALLING ROUTINE.

1139.2 *** SYSTEM FATAL MESSAGE 1139

THE MAXIMUM QUALIFIER TABLE LENGTH HAS BEEN EXCEEDED

1140.0 *** USER FATAL MESSAGE 1140 (RESENT)

AN ERROR HAS BEEN DETECTED IN THE DATABASE POINTERS

User action: SUBMIT A RUN WITH FMS COMMAND DBFIX.

Programmer action: THIS ERROR OCCURRED WHILE SEARCHING FOR THE BEGINNING OF
THE DBENTRY FREE-CHAIN. THE FREE-CHAIN APPEARS TO BE CONNECTED IN A CIR-
CULAR LOOP.

1141.0 *** USER INFORMATION MESSAGE 1141 (RESENT)

A DB-DIRECTORY NOT PROPERLY CLOSED IN THE PREVIOUS RUN IS BEING RESTORED
BY THIS RUN.

1142.0 *** USER FATAL MESSAGE 1142 (RSPRVR)

THE RESTART PROJECT ID = '%1' IS NOT DEFINED IN THIS DATA BASE

1142.1 *** USER FATAL MESSAGE 1142 (DBCLPR)

THE PROJECT ID ='%1' SPECIFIED ON THE DBCLEAN CARD IS NOT DEFINED IN THIS
DATA BASE

1143.0 *** USER FATAL MESSAGE 1143 (RSPRVR)

Main Index
 158 MSC Nastran Error Messages
Errors 1000 - 1999

THE RESTART STATEMENT REFERENCES RESTART VERSION ID = %1,WHICH DOES NOT

EXIST.

1144.0 *** USER INFORMATION MESSAGE 1144 (RSPRVR)

LAST VERSION CREATED IS BEING USED FOR THIS RESTART JOB.
LAST VERSION = %1 PROJECT = %2

1145.0 *** USER FATAL MESSAGE 1145 (RSPRVR)

THE VERSION ID = %1 OF PROJECT '%2' SPECIFIED ON RESTART CARD HAS BEEN
DELETED PRIOR TO THIS RUN. A RESTART IS IMPOSSIBLE.

1146.0 *** SYSTEM FATAL MESSAGE 1146 (RESENT)

ATTEMPTING TO READ BEYOND THE END OF DATA ON THE DATABASE DBENTRY
TABLE.

User action: RESUBMIT THIS RUN WITH FMS COMMAND DBFIX.

Programmer information: ATTEMPT TO READ DBENTRY BLOCK NUMBER %1. THE LAST
DBENTRY BLOCK NUMBER SPECIFIED IN DBDIR TABLE IS %2.

1147.0 *** SYSTEM WARNING MESSAGE 1147 (WRTTRL)

BAD TRAILER FOR FILE %1

System information: This message will be issued when one of the trailer values (see the MSC NASTRAN
DMAP Programmers Guide) is outside an accepted range. For example, if the density of a matrix exceeds
1.0, the message is issued. Usually, these messages will not have an adverse affect on the
job, but should be reported to Hexagon as a precaution.

1147.1 *** SYSTEM WARNING MESSAGE 1147 (SSMHFD)

BAD TRAILER FOR FILE %1

System information: This message will be issued when one of the trailer values (see the MSC NASTRAN
DMAP Programmers Guide) is outside an accepted range. For example, if the density of a matrix exceeds
1.0, the message is issued. Usually, these messages will not have an adverse affect on the job, but should be
reported to Hexagon as a precaution.

Main Index
 MSC Nastran Error Messages 159
Errors 1000 - 1999

1148.0 *** SYSTEM WARNING MESSAGE 1148 (WRTTRL)

UNABLE TO WRITE TRAILER FOR FILE %1

1148.1 *** SYSTEM WARNING MESSAGE 1148 (PTNZTM)

UNABLE TO WRITE EXTENDED TRAILER FOR FILE %1

1149.0 *** SYSTEM FATAL MESSAGE 1149 (SETTRL)

TRAILER BIT POSITION VALUE %1 EXCEEDS THE MAXIMUM ALLOWED VALUE OF 176.

User action: CONTACT MSC CLIENT SUPPORT.

1150.0 *** SYSTEM FATAL MESSAGE 1150 (XRSLTU)

END OF FILE ENCOUNTERED WHILE DOING CONDITIONAL JUMP FROM COND, DMAP
STATEMENT NUMBER IS %1

User action: CONTACT HEXAGON AB.

1151.0 *** SYSTEM FATAL MESSAGE 1151 (XCEI)

ERROR DELETING SCRATCH FILE %1 AT TOP OF DMAP LOOP

1152.0 *** USER WARNING MESSAGE 1152 (XCLNUP)

SOME DBSETS IN THIS DATA BASE WERE NOT INITIALIZED COMPLETELY.

User information: THE DATA BASE CREATED IN THIS RUN IS TOO IMMATURE TO BE
RESTARTED.

User action: DELETE THIS DATA BASE BEFORE STARTING YOUR NEXT RUN.

1153.0 *** USER WARNING MESSAGE 1153 (XCLNUP)

Main Index
 160 MSC Nastran Error Messages
Errors 1000 - 1999

THE NDDL FOR THIS DATA BASE HAS NEITHER BEEN CREATED NOR OBTAINED FROM
THE DELIVERY DATA BASE.

User information: THE DATA BASE CREATED IN THIS RUN IS TOO IMMATURE TO BE
RESTARTED.

User action: DELETE THIS DATA BASE BEFORE STARTING YOUR NEXT RUN.

1155.0 *** SYSTEM FATAL MESSAGE 1155 (XCLOAD)

FILPOS POINTER TO DBDIR (DBENTRY) TABLE = 0

User action: SEND RUN TO HEXAGON AB, WITH DATA BASE DIRECTORY PRINT

Programmer action: EXAMINE DBENTRY ENTRY -- DBEPTR = %1

1156.0 *** SYSTEM INFORMATION MESSAGE 1156 (XCLNUP)

GINO FILE %1 WAS LEFT OPEN AT PROGRAM TERMINATION.

1157.0 *** USER FATAL MESSAGE 1157 (XDRMGR)

THE %1 DATA BASE CONTAINS INVALID OR NULL MASTER DIRECTORIES(NDDL).

User information: THE NDDL FOR THIS DATA BASE HAS NEITHER BEEN CREATED NOR
OBTAINED FROM THE DELIVERY DATA BASE. THE DATA BASE ATTACHED TO THIS RUN
IS TOO IMMATURE TO BE RESTARTED.

User action: DELETE THIS DATA BASE AND RESUBMIT ITS DATA BASE INITIALIZATION
RUN.

1158.0 *** SYSTEM FATAL MESSAGE 1158 (XRETUR)

UNEXPECTED END OF FILE ENCOUNTERED WHILE POSITIONING BACK TO CALLING
SUBDMAP %1

Main Index
 MSC Nastran Error Messages 161
Errors 1000 - 1999

1159.0 *** SYSTEM FATAL MESSAGE 1159 (XRETUR)

THE "MAIN" SUBDMAP %1 CANNOT HAVE A "RETURN" STATEMENT

1160.0 *** SYSTEM FATAL MESSAGE 1160 (XSTORE)

OSCAR FILE MUST BE INCORRECTLY POSITIONED SINCE END-OF-FILE ENCOUNTERED

User action: SEND RUN TO HEXAGON AB.

Programmer action: CHECK LOGIC IN ROUTINE XSEM.

1160.1 *** SYSTEM FATAL MESSAGE 1160 (XRSLTU)

OSCAR FILE MUST BE INCORRECTLY POSITIONED SINCE END-OF-FILE ENCOUNTERED

User action: SEND RUN TO HEXAGON AB.

Programmer action: CHECK LOGIC IN ROUTINE XRSLTU.

1160.2 *** SYSTEM FATAL MESSAGE 1160 (XCEI)

OSCAR FILE MUST BE INCORRECTLY POSITIONED SINCE END-OF-FILE ENCOUNTERED

User action: SEND RUN TO HEXAGON AB

Programmer action: CHECK LOGIC IN ROUTINE XCEI.

1161.0 *** SYSTEM FATAL MESSAGE 1161 (XSTORE)

THE PREALLOCATED SPACE FOR DBDIR RECORDS IS INSUFFICIENT

User action: SEND THIS RUN TO HEXAGON AB

Programmer action: INCREASE THE APPROPRIATE FIXED BUFFER SIZE

1162.0 *** SYSTEM FATAL MESSAGE 1162 (XSTORE)

CODING LOGIC ERROR ,TYPE VARIABLE = %1 IS INVALID IN CALLS TO XSTORE

Main Index
 162 MSC Nastran Error Messages
Errors 1000 - 1999

1163.0 *** SYSTEM INFORMATIONAL MESSAGE 1163 (XSTVPS)

AN ATTEMPT WAS MADE TO UPDATE AN UNKNOWN LOCAL VPS ENTRY %1

1164.0 *** SYSTEM INFORMATIONAL MESSAGE 1164 (XSTVPS)

AN ATTEMPT WAS MADE TO UPDATE THE LOCAL VPS ENTRY %1, WHOSE VALUE IS
STORED ON THE DATA BASE

1165.0 *** SYSTEM FATAL MESSAGE 1165 (XSTVPS)

AN ATTEMPT WAS MADE TO UPDATE THE TYPE OF THE LOCAL VPS ENTRY %1 FROM
TYPE %2 TO TYPE %3

1166.0 *** SYSTEM INFORMATIONAL MESSAGE 1166 (XSTVPS)

AN UPDATE TO THE CHARACTER ENTRY %1 IN THE LOCAL VPS WAS TRUNCATED
FROM %2 WORDS TO %3 WORDS

1167.0 *** SYSTEM FATAL MESSAGE 1167 (XSUBLD)

THE DUMMY RECORD IS MISSING FROM THE OSCAR FILE %1

1167.1 *** SYSTEM WARNING MESSAGE 1167 (NSMEPT)

The property record for %1 elements is missing from the %2 table.

1168.0 *** SYSTEM FATAL MESSAGE 1168 (DBOLD)

THE NUMBER OF ENTRIES IN THE EXECUTIVE TABLE HAS BEEN EXCEEDED.

User action:
1. ADD THE FOLLOWING KEYWORD TO THE %1 STATEMENT: SYSTEM(162)=%2
2. OR REDUCE NUMBER OF SUBDMAPS IN THIS RUN.

1169.0 *** SYSTEM FATAL MESSAGE 1169 (XSTVPS)

AN ATTEMPT WAS MADE TO UPDATE THE LENGTH OF THE LOCAL VPS ENTRY %1 OF
TYPE %2 FROM %3 TO %4 WORDS

1170.0 *** SYSTEM INFORMATIONAL MESSAGE 1170 (XSTVPS)

AN UPDATE TO THE CHARACTER ENTRY %1 IN THE LOCAL VPS WAS BLANK-FILLED
FROM WORD %2 FOR %3 WORDS

1171.0 *** SYSTEM FATAL MESSAGE 1171 (XSUBLD)

Main Index
 MSC Nastran Error Messages 163
Errors 1000 - 1999

UNEXPECTED END OF RECORD FOUND ON THE FIRST RECORD OF THE OSCAR FILE =
%1

User information: THIS IS PROBABLY NOT AN OSCAR DATA BLOCK

User action: SEND RUN TO HEXAGON AB

Programmer action: EXAMINE THE FOLLOWING DUMP OF THE OSCAR FILE

1173.0 *** USER INFORMATION MESSAGE 1173 (DBCLPR)

VERSION %1 OF PROJECT '%2' HAS BEEN DELETED FROM THE PRIMARY DATA BASE.
THE CREATION DATE OF THIS VERSION IS %3/%4/%5 %6:%7.%8

1174.0 *** USER WARNING MESSAGE 1174 (DBCLPR)

THE VERSION ID = %1 OF PROJECT '%2' ON THE DBCLEAN CARD HAS NEVER BEEN CRE-
ATED.

User information: THIS DBCLEAN CARD IS IGNORED.

1174.1 *** USER WARNING MESSAGE 1174 (DBCLPR)

THE VERSION ID = %1 OF PROJECT '%2' ON THE DBCLEAN CARD HAS ALREADY BEEN
DELETED.

User information: THIS DBCLEAN CARD IS IGNORED.

1175.0 *** USER FATAL MESSAGE 1175 (COPY1)

THE DBSET OF THE OUTPUT DATABLOCK HAS A BUFFSIZE LESS THEN THE DBSET OF
THE INPUT DATABLOCK

User information:
THE DBSET OF THE INPUT DATABLOCK HAS BUFFSIZE OF %1
THE DBSET OF THE OUTPUT DATABLOCK HAS BUFFSIZE OF %2

1175.1 *** SYSTEM FATAL MESSAGE 1175 (COPY1)

Main Index
 164 MSC Nastran Error Messages
Errors 1000 - 1999

THE DBSET OF THE OUTPUT DATABLOCK %1 (%2) HAS A NBUFF2 NOT EQUAL TO THE
DBSET OF THE INPUT DATABLOCK
%3 (%4).

System information:
THE DBSET OF THE INPUT DATABLOCK HAS AN NBUFF2 OF %5
THE DBSET OF THE OUTPUT DATABLOCK HAS AN NBUFF2 OF %6

1175.2 *** SYSTEM FATAL MESSAGE 1175 (COPY1)

THE DBSET OF THE OUTPUT DATABLOCK %1 (%2) HAS A NBUFF2 LESS THAN THE
DBSET OF THE INPUT DATABLOCK
%3 (%4).

System information:
THE DBSET OF THE INPUT DATABLOCK HAS AN NBUFF2 OF %5
THE DBSET OF THE OUTPUT DATABLOCK HAS AN NBUFF2 OF %6

1176.0 *** SYSTEM WARNING MESSAGE 1176 (DIRPT3)

NOT ENOUGH SPACE AVAILABLE TO PRINT ENTIRE PATH VALUE TABLE. PRINT WILL
NOT INCLUDE PATH VALUES.

1177.0 *** SYSTEM WARNING (TEMPORARY) MESSAGE 1177 (DIRPT3)

SPILL LOGIC NOT YET INCORPORATED INTO THIS MODULE, AND DATA WILL NOT FIT
IN OPEN CORE. DBDIR ABORTED.

1178.0 *** SYSTEM FATAL (TEMPORARY) MESSAGE 1178 (GNDIR)

DURING A DATABLOCK ALLOCATION THE DATA BASE DIRECTORY (DBDIR) HAS OVER-
FLOWED.

User actions:
1. DELETE ANY UNWANTED FILES FROM THE DBSET THIS DATABLOCK IS ON (VIA
DBCLEAN FMS COMMAND) AND RE-RUN.
2. CONTACT HEXAGON AB.
Programmer information:
1. DATA BLOCK BEING ALLOCATED IS %1
2. XFIST # OF DBDIR IS %2

Main Index
 MSC Nastran Error Messages 165
Errors 1000 - 1999

1179.0 *** USER INFORMATION MESSAGE 1179 (RESDBS)

A DB-DIRECTORY IMPROPERLY CLOSED IN THE PREVIOUS RUN IS BEING RESTORED BY
THIS RUN.

1180.0 *** SYSTEM FATAL MESSAGE 1180 (DBCLN)

LOGIC ERROR IN DATA BASE CLEANUP ROUTINE

Programmer information: VARIABLE DBUPTR (THE 10TH ENTRY OF THE DBTEMP ARRAY)
INDICATES NO NEW OUTPUT
DBDIR ENTRY WAS GENERATED FOR DATA BLOCK %1
ALL OUTPUT OR SCRATCH (300 SERIES) DATA BLOCKS MUST HAVE A NON-ZERO
DBUPTR VALUE--

User action: RERUN WITH DIAG 44 AND THEN SEND RUN TO HEXAGON AB

1181.0 *** SYSTEM FATAL MESSAGE 1181 (GPUTTS)

ERROR WRITING THE TIME STAMP TO THE DBSET %1

User information: THE CORRESPONDING PHYSICAL FILE IS:

%2

1181.1 *** SYSTEM FATAL MESSAGE 1181 (GGETTS)

ERROR READING THE TIME STAMP FROM THE DBSET %1

User information: THE CORRESPONDING PHYSICAL FILE IS:

%2

1182.0 *** SYSTEM FATAL MESSAGE 1182 (GPUTTS)

THE BIT MAP SHOWS CLUSTER FOR TIME STAMP IS ALREADY IN USE.

1183.0 *** SYSTEM WARNING MESSAGE 1183 (BPRITE)

FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED

Programmer information: REFNUM = %1 FILEX = %2 BPUNRF=%3

Main Index
 166 MSC Nastran Error Messages
Errors 1000 - 1999

1183.1 *** SYSTEM WARNING MESSAGE 1183 (BPREWI)

FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED

Programmer information: REFNUM = %1

1183.2 *** SYSTEM FATAL MESSAGE 1183 (BPREAD)

FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED

Programmer information: REFNUM = %1 FILEX = %2 BPUNRF=%3

1183.3 *** SYSTEM WARNING MESSAGE 1183 (BPCLOS)

FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED

Programmer information: REFNUM = %1. FILEX = %2.

NAM=%3 TOP=%4 BOT=%5 CUR=%6

1183.4 *** SYSTEM WARNING MESSAGE 1183 (BPBACK)

FILE REQUESTED HAS NOT BEEN PREVIOUSLY OPENED

Programmer information: REFNUM = %1

1184.0 *** SYSTEM WARNING MESSAGE 1184 (BPREWI)

REWIND FILE WAS OPENED FOR WRITE

Programmer information: REFNUM = %1 NAM = %2 TOP = %3 BOT = %4 CUR = %5

1184.1 *** SYSTEM WARNING MESSAGE 1184 (BPBACK)

BACKSPACE FILE WAS OPENED FOR WRITE

Programmer information: REFNUM = %1 NAM = %2 TOP = %3 BOT = %4 CUR = %5

1185.0 *** SYSTEM FATAL MESSAGE 1185 (ADDPAT)

Main Index
 MSC Nastran Error Messages 167
Errors 1000 - 1999

THE PATH VALUE TABLE HAS GROWN TOO LARGE FOR ITS CURRENT LIMITS.

User action: INCREASE MASTER(RAM) SIZE ON THE INIT MASTER COMMAND TO

INCREASE THE SIZE OF THE TABLE.

1186.0 *** SYSTEM FATAL MESSAGE 1186

THE DBDIR CLUSTER PONTER RECORD LENGTH HAS BEEN EXCEEDED AND IS NOT
EXPANDABLE.

User action: DELETE DATA BLOCKS WHICH ARE NOT NEEDED ON THE DATABASE WITH
THE DELETE DMAP MODULE, OR DELETE ENTIRE VERSIONS WITH THE DBCLEAN FILE
MANAGEMENT COMMAND.

System information: Currently, a DB Directories cluster pointer record is un-expandable. If it has filled up,
the user must delete data blocks for the cluster pointer record in order to proceed writing to his database.
This has been observed when the maximum number of superelements or modules has been exceeded.

1187.0 *** USER INFORMATION MESSAGE 1187 (XRETUR)

RETURNING TO SUBDMAP %1 WHICH WAS RECURSIVELY CALLED
1188.0 *** USER FATAL MESSAGE 1188 (GALLEX)
DBSET %1 DOES NOT HAVE %2 CONTIGUOUS BLOCKS TO EXPAND THIS DBSET
DIRECTORY

User action:
1. USE FILE MANAGEMENT COMMAND "INIT" FOR A TEMPORARY (SCRATCH) DBSET.
2. USE FILE MANAGEMENT COMMAND "EXPAND" FOR A PERMANENT DBSET.

User information: A number of contiguous blocks need to be allocated for an expansion of a DBSET direc-
tory. The BIT-MAP is searched for available bits and it cannot find the requested bits.

1189.0 *** SYSTEM FATAL MESSAGE 1189 (GALLOC)

Main Index
 168 MSC Nastran Error Messages
Errors 1000 - 1999

THE SIZE DATA BLOCK %1 ON DBSET %2 HAS EXCEEDED THE MSC NASTRAN LIMIT OF
65535 GINO BLOCKS.

User action:
1. REDUCE THE SIZE OF THE MODEL OR DIVIDE THE MODEL INTO (MORE)
SUPERELEMENTS
OR
2. CREATE A NEW DATA BASE WITH A LARGER BUFFSIZE FOR THE DBSET,
OR
3. CONTACT HEXAGON AB FOR OTHER POSSIBLE AVOIDANCES.

1190.0 *** SYSTEM INFORMATION MESSAGE 1190 (NUMCPU)

NUMBER OF PROCESSORS REQUESTED=%1, NUMBER OF PROCESSORS AVAILABLE=%2

System information: This is issued if the number of parallel processors specified on the NASTRAN PAR-
ALLEL statement exceeds the number available.

1191.0 *32* SYSTEM INFORMATION MESSAGE 1191 (XSTORE)

THE EXECUTIVE SYSTEM WORK AREA WILL BE INCREASED BY %1 WORDS DUE TO AN
OVERFLOW OF TABLE TYPE = %2 *32*

1192.0 *** SYSTEM FATAL MESSAGE 1192 (LDUSAV)

THE SAVENT TABLE SIZE HAS BEEN EXCEEDED FOR %1 %2.

*** User information:

THE TABLE SIZE IS EQUAL TO %3 WORDS PARTITIONED FROM THE AVAILABLE OPEN-
CORE SPACE.

*** User action:

INCREASE HICORE SIZE AND RERUN JOB.

1192.1 *** SYSTEM FATAL MESSAGE 1192 (LCXSIZ)

Main Index
 MSC Nastran Error Messages 169
Errors 1000 - 1999

THE DIRECTORY TABLES SIZE HAS BEEN EXCEEDED.

User information: INCREASE HICORE SIZE AND RERUN JOB.

Programmer information:
IDBSNO %1 NZ %2 DIRSIZ %3

1192.2 *** SYSTEM FATAL MESSAGE 1192 (LCXLOD)

THE DIRECTORY TABLES SIZE HAS BEEN EXCEEDED.

User information: INCREASE HICORE SIZE AND RERUN JOB.

Programmer information:
IDBSNO%1 MXDLEN%2 STARTZ%3 LENDIR%4 NZ%5
XPTRS%6
%7
%8
%9

1192.3 *** SYSTEM FATAL MESSAGE 1192 (CKEQUV)

THE EQUIVALENCE CORRESPONDENCE TABLE SIZE HAS BEEN EXCEEDED.

*** User information:

THE TABLE SIZE IS EQUAL TO %1 WORDS PARTITIONED FROM THE AVAILABLE OPEN-
CORE SPACE.

*** User action:

INCREASE HICORE SIZE AND RERUN JOB.

1192.4 *** SYSTEM FATAL MESSAGE 1192 (XINSBL)

Main Index
 170 MSC Nastran Error Messages
Errors 1000 - 1999

THE NDDL RECORDS LENGTH TABLE SIZE HAS BEEN EXCEEDED.

Programmer information: THE TABLE SIZE IS EQUAL TO %1 WORDS PARTITIONED FROM

THE AVAILABLE OPENCORE SPACE.

1193.0 *** USER WARNING MESSAGE 1193 (UNLDRF)

THE FORMAT ON THE ASSIGN,DBUNLOAD STATEMENT IS INCOMPATIBLE WITH THE
FORM ON THE DBUNLOAD STATEMENT FOR UNIT %1

*** User information:

1. FORMAT ON ASSIGN IS %2
2. FORM ON DBUNLOAD IS %3
3. DBUNLOAD FORM DEFAULTS ARE SET FOR THIS UNIT
RECL = %4 FORMAT = %5

1193.1 *** USER WARNING MESSAGE 1193 (LDLDRF)

THE FORMAT ON THE ASSIGN,DBLOAD STATEMENT IS INCOMPATIBLE WITH THE
FORM ON THE DBLOAD STATEMENT FOR UNIT %1

*** User information:

1. FORMAT ON ASSIGN IS %2
2. FORM ON DBLOAD IS %3
3. DBLOAD FORM DEFAULTS ARE SET FOR THIS UNIT
RECL = %4 FORMAT = %5

1194.0 *** SYSTEM FATAL MESSAGE 1194 (UNLIFU)

OVERFLOW OF DBUNLOAD FORTRAN UNIT ARRAY

*** User action: REDUCE THE NUMBER OF FORTRAN UNITS SPECIFIED IN DBUNLOAD
STATEMENTS

*** User information: THE MAXIMUM NUMBER OF FORTRAN UNITS THAT CAN BE SPECI-
FIED ON DBUNLOAD STATEMENTS IS %1

Main Index
 MSC Nastran Error Messages 171
Errors 1000 - 1999

1195.0 *** USER FATAL MESSAGE 1195 (UNLODR)

INVALID VALUE SPECIFIED FOR FORM KEYWORD ON DBUNLOAD STATEMENT

1200.0 *** SYSTEM FATAL MESSAGE 1200 (UNDRVR)

AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ A DBUNLOAD HEADER
RECORD FROM THE FMS CONTROL FILE.

*** Programmer information:

ERROR FLAG FROM FMSGEH = %1.

1200.1 *** SYSTEM FATAL MESSAGE 1200 (LDDRVR)

AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ A DBLOAD HEADER
RECORD FROM THE FMS CONTROL FILE.

*** Programmer information:

ERROR FLAG FROM FMSGEH = %1.

1200.2 *** SYSTEM FATAL MESSAGE 1200 (DBDICT)

AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ A DBDICT HEADER RECORD
FROM THE FMS CONTROL FILE.

*** Programmer information:

ERROR FLAG FROM FMSGEH = %1.

1201.0 *** SYSTEM FATAL MESSAGE 1201 (UNDRVR)

Main Index
 172 MSC Nastran Error Messages
Errors 1000 - 1999

AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ ONE OR MORE DBUNLOAD

DATA RECORDS FROM THE FMS CONTROL FILE.

*** Programmer information:

1. ERROR FLAG 1 FROM FMSGEI = %1.
2. ERROR FLAG 2 FROM FMSGEI = %2.
3. ERROR FLAG 3 FROM FMSGEI = %3.
4. RROR FLAG 4 FROM FMSGEC = %4.
5. ERROR FLAG 5 FROM FMSGEC = %5.

1201.1 *** SYSTEM FATAL MESSAGE 1201 (LDDRVR)

AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ ONE OR MORE DBLOAD
DATA RECORDS FROM THE FMS CONTROL FILE.

*** Programmer information:

1. ERROR FLAG 1 FROM FMSGEI = %1.
2. ERROR FLAG 2 FROM FMSGEI = %2.
3. ERROR FLAG 3 FROM FMSGEI = %3.
4. ERROR FLAG 4 FROM FMSGEC = %4.
5. ERROR FLAG 5 FROM FMSGEC = %5.

1201.2 *** SYSTEM FATAL MESSAGE 1201 (LCDRVR)

AN ERROR HAS OCCURRED WHILE ATTEMPTING TO READ ONE OR MORE DBLOCATE
DATA RECORDS FROM THE FMS CONTROL FILE.

*** Programmer information:

1. HEDTYP FROM FMSGEH = %1.
2. ERROR FLAG 0 FROM FMSREW = %2.
3. ERROR FLAG 1 FROM FMSGEH = %3.
4. ERROR FLAG 2 FROM FMSGEI = %4.
5. ERROR FLAG 3 FROM FMSGEI = %5.
6. ERROR FLAG 4 FROM FMSGEI = %6.
7. ERROR FLAG 5 FROM FMSGEC = %7.
8. ERROR FLAG 6 FROM FMSGEC = %8.

Main Index
 MSC Nastran Error Messages 173
Errors 1000 - 1999

1202.0 *** SYSTEM FATAL MESSAGE 1202 (UNDRVR)

AN ERROR HAS OCCURRED WHILE ATTEMPTING TO REWIND THE FMS CONTROL FILE.

*** Programmer information:

ERROR FLAG FROM FMSREW = %1.

1203.0 *** USER WARNING MESSAGE 1203 (UNDRVR)

THE CONVERT CLAUSE IS NOT SUPPORTED BY THE DBUNLOAD STATEMENT.
THE CONVERT CLAUSE SPECIFIED WILL BE IGNORED.
SPECIFIED CONVERT CLAUSE WAS:

1204.0 *** SYSTEM WARNING MESSAGE 1204 (UNRTN)

ABSOLUTE VALUE OF SINGLE PRECISION VALUE IS %1 THAN THE %2 FILTER OF %3,
AND WILL BE RESET TO THE CORRECTLY SIGNED FILTER VALUE

1204.1 *** SYSTEM WARNING MESSAGE 1204 (UNMTND)

ABSOLUTE VALUE OF DOUBLE PRECISION VALUE IS %1 THAN THE %2 FILTER OF %3,
AND WILL BE RESET TO THE CORRECTLY SIGNED FILTER VALUE

1204.2 *** SYSTEM WARNING MESSAGE 1204 (UNxxx)

%3 %2 VALUE ENCOUNTERED.

User information: VALUE IN HEXADECIMAL FORMAT IS %1 AND WILL BE REPLACED BY %4.

1205.0 **** SYSTEM INFORMATION MESSAGE 1205 (UNEND)

%1 ERRORS OCCURRED DURING TRANSMISSION PROCESS

1206.0 *** SYSTEM INFORMATION MESSAGE 1206

THE DATABLOCK %1 IN A DBUNLOAD REQUEST IS NOT DEFINED IN THE MSC NAS-
TRAN DATA DEFINITION LANGUAGE (NDDL)
THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT

1206.1 *** SYSTEM INFORMATION MESSAGE 1206 (OUTPX2)

THE DATABLOCK %1%2 IN AN OUTPUT2 REQUEST IS NOT DEFINED IN THE MSC NAS-
TRAN DATA DEFINITION LANGUAGE (NDDL)
THIS DATABLOCK WILL NOT BE TRANSLATED TO %3 FORMAT ON UNIT %4

Main Index
 174 MSC Nastran Error Messages
Errors 1000 - 1999

1206.2 *** SYSTEM INFORMATION MESSAGE 1206 (INPTX2)

THE DATABLOCK %1%2 IN AN INPUTT2 REQUEST IS NOT DEFINED IN THE MSC NAS-
TRAN DATA DEFINITION LANGUAGE (NDDL)
THIS DATABLOCK WILL NOT BE TRANSLATED FROM %3 FORMAT ON UNIT %4

1206.4 *** USER INFORMATION MESSAGE 1206 (OUTPN2)

THE DATABLOCK %1%2 IN AN OUTPUT2 REQUEST IS NOT DEFINED IN THE MSC NAS-
TRAN DATA DEFINITION LANGUAGE (NDDL)
THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT

1207.0 *** SYSTEM INFORMATION MESSAGE 1207 (UNLNEU)

THE DATABLOCK %1 DEFINED AS NDDL TYPE %2 IS NOT SUPPORTED BY NEUTRAL FILE
TRANSLATION.
THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT.

1207.1 *** USER INFORMATION MESSAGE 1207 (OUTPN2)

THE DATABLOCK %1%2 DEFINED AS NDDL TYPE %3 IS NOT SUPPORTED BY NEUTRAL
FILE TRANSLATION.
THIS DATABLOCK WILL NOT BE TRANSLATED TO NEUTRAL FORMAT

1207.2 *** USER INFORMATION MESSAGE 1207 (OUTPN2)

THE DATABLOCK %1%2 DEFINED AS NDDL TYPE %3 IS NOT SUPPORTED FOR WORD
LENGTH OR ENDIAN CONVERSION.
THIS DATABLOCK WILL NOT BE CONVERTED ON UNIT %5

User action: Specify the appropiate FORM option on the ASSIGN FMS statement. For example,
to override 32-bit conversion on a 64-bit machine, specify "FORM=64" keyword on the ASSIGN state-
ment

1208.0 *** SYSTEM FATAL MESSAGE 1208 (UNSTR)

ERROR SETTING UP TRANSLATE TABLE AT LOC = %1

Main Index
 MSC Nastran Error Messages 175
Errors 1000 - 1999

1209.0 *** SYSTEM FATAL MESSAGE 1209 (LDPARM)

INSUFFICIENT OPENCORE SPACE AVAILABLE TO LOAD SAVENT ARRAY FOR PARAME-
TER %1.

User action: INCREASE OPENCORE

User information:
1. THE SAVENT ARRAY USES 15 PERCENT OF AVAILABLE OPENCORE, OR %2 WORDS
IN THIS RUN.
2. THIS SAVENT ARRAY CONTAINS %3 WORDS.

1209.1 *** SYSTEM FATAL MESSAGE 1209 (LDDBLK)

INSUFFICIENT OPENCORE SPACE AVAILABLE TO LOAD SAVENT ARRAY FOR DATA-
BLOCK %1.

User action: INCREASE OPENCORE

User information:
1. THE SAVENT ARRAY USES 15 PERCENT OF AVAILABLE OPENCORE, OR %2 WORDS
IN THIS RUN
2. THIS SAVENT ARRAY CONTAINS %3 WORDS.

1210.0 *** SYSTEM FATAL MESSAGE 1210 (LDPARM)

THE PRIMARY QUALIFIER TABLE SIZE HAS BEEN EXCEEDED FOR PARAMETER %1

User information: THE MAXIMUM PRIMARY QUALIFIER TABLE SIZE IS %2 WORDS.

User action:
1. DECREASE NUMBER OF QUALIFIERS FOR PARAMETER AND RERUN JOB
2. NOTIFY HEXAGON AB

Main Index
 176 MSC Nastran Error Messages
Errors 1000 - 1999

1210.1 *** SYSTEM FATAL MESSAGE 1210 (LDDBLK)

THE PRIMARY QUALIFIER TABLE SIZE HAS BEEN EXCEEDED FOR DATABLOCK %1

User information: THE MAXIMUM PRIMARY QUALIFIER TABLE SIZE IS %2 WORDS.

User action:
1. DECREASE NUMBER OF QUALIFIERS FOR DATABLOCK AND RERUN JOB
2. NOTIFY HEXAGON AB

1211.0 *** SYSTEM FATAL MESSAGE 1211 (LDDRVR)

AN ERROR WAS DETECTED IN THE SUBROUTINE LDLENT WHEN ATTEMPTING TO
LOAD A DATABLOCK OR PARAMETER TO THE DATABASE

*** User information:

THE REMAINING INPUT FILE WILL NOT BE PROCESSED

1212.0 *** SYSTEM FATAL MESSAGE 1212 (LDINPT)

INVALID DATABLOCK TRAILER DETECTED FOR %1 DURING DBLOAD NEUTRAL FILE
PROCESSING.

*** User information:

1. DATABLOCK TRAILERS CONSIST OF%2 WORDS.
2. THIS TRAILER CONTAINS %3 WORDS.

1213.0 *** SYSTEM FATAL MESSAGE 1213 (LDPHDR)

HEADER RECORD MISSING ON NEUTRAL FILE ATTACHED TO UNIT%1

1214.0 *** SYSTEM INFORMATION MESSAGE 1214 (LDRTRN)

ERROR TRANSLATING DATA FROM NEUTRAL FILE READ FOR SUBROUTINE %1.
CHARACTER = A POSITION IS LINE %2 CHARACTER %3

Main Index
 MSC Nastran Error Messages 177
Errors 1000 - 1999

1215.0 *** USER FATAL MESSAGE 1215 (CKRVER)

THE PRIMARY DATABASE IS INCOMPATIBLE WITH THIS VERSION OF THE PROGRAM.

User information:
PRIMARY DATABASE VERSION IS %1
PROGRAM VERSION IS %2

User actions:
1. CONVERT THE PRIMARY DATABASE USING THE HEXAGON AB MIGRATION
TOOLS.
2. OR, SET SYSTEM CELL 148 ON %3 STATEMENT TO IGNORE THIS
INCOMPATIBILITY, E.G.,
"%4 SYSTEM(148)=1". HOWEVER, IGNORING THIS INCOMPATIBILITY MAY LEAD TO
UNPREDICTABLE RESULTS.

1216.0 *** SYSTEM INFORMATION MESSAGE 1216 (LDDBLK)

THE DATABLOCK %1 CLASSIFIED AS NDDL-TYPE %2 CANNOT BE LOADED TO THIS
DATABASE BECAUSE THE PROGRAM BUFFER SIZES ARE INCOMPATIBLE
UNLOAD BUFFER SIZE: %3
LOAD BUFFER SIZE: %4

1216.1 *** SYSTEM INFORMATION MESSAGE 1216 (LDDBLK)

THE DATABLOCK %1 CLASSIFIED AS NDDL-TYPE %2 CANNOT BE LOADED TO THIS
DATABASE BECAUSE THE MACHINE TYPES ARE INCOMPATIBLE
UNLOAD MACHINE TYPE: %3
LOAD MACHINE TYPE: %4

1217.0 *** USER FATAL MESSAGE 1217 (LCDEFC)

Main Index
 178 MSC Nastran Error Messages
Errors 1000 - 1999

VERSION IS NOT SPECIFIED IN CONVERT CLAUSE. CONTENTS OF CONVERT CLAUSE:

%1

User action: SPECIFY PROJECT AND VERSION.

User information:
If either PROJECT or VERSION is specified then both must be specified.

1218.0 *** USER FATAL MESSAGE 1218 (VWDRVR)

RUN IS TERMINATED DUE TO ABOVE ERROR(S) IN DBVIEW STATEMENT.

1218.1 *** USER FATAL MESSAGE 1218 (LCDRVR)

RUN IS TERMINATED DUE TO ABOVE ERRORS IN DBLOCATE.

1219.0 *** USER FATAL MESSAGE 1219 (LCLENT)

AN ATTEMPT TO OVERWRITE THE EXISTING DATABLOCK/PARAMETER %1 WITH %2
WAS MADE BUT THE NOOVRWRT KEYWORD IS SPECIFIED.

Programmer information: PATH-POINTER%3 DBENTRY POINTER%4

1220.0 *** USER INFORMATION MESSAGE 1220 (LCLPJV)

%1 IS CREATING
V E R S I O N - ID=%2 OF
P R O J E C T - ID="%3" (PROJECT-NO=%4) IN THE PRIMARY DATABASE.

1220.1 *** USER INFORMATION MESSAGE 1220 (LCLPJV)

%1 IS CREATING
P R O J E C T - ID="%2" (PROJECT-NO=%3) IN THE PRIMARY DATABASE.

1220.2 *** USER INFORMATION MESSAGE 1220 (LCLPJV)

%1 IS RECREATING
V E R S I O N - ID=%2 OF
P R O J E C T - ID="%3" (PROJECT-NO=%4) IN THE PRIMARY DATABASE.

1221.0 *** USER INFORMATION MESSAGE 1221

Main Index
 MSC Nastran Error Messages 179
Errors 1000 - 1999

THE PARTITION OF THE SCRATCH DBSET USED FOR DMAP-SCRATCH DATABLOCKS IS

FULL.

User information: THE DMAP-SCRATCH PARTITION WILL NOW SPILL INTO THE 300-
SCRATCH PARTITION BECAUSE NASTRAN SYSTEM(151)=1.

1221.1 *** USER FATAL MESSAGE 1221 (GALLOX)

THE PARTITION OF THE SCRATCH DBSET USED FOR DMAP-SCRATCH DATABLOCKS IS
FULL.

User information: THE DMAP SCRATCH PARTITION WILL NOT SPILL INTO THE 300-
SCRATCH PARTITION.

User action:
1. SET NASTRAN SYSTEM(151)=1, OR
2. INCREASE THE NUMBER OF MEMBERS, AND/OR THEIR MAXIMUM SIZE, FOR THE
SCRATCH DBSET ON THE "INIT" STATEMENT.

1221.2 *** USER INFORMATION MESSAGE 1221 (GALLOC)

THE PARTITION OF THE SCRATCH DBSET USED FOR 300-SCRATCH FILES IS FULL.

User information: THE 300-SCRATCH PARTITION WILL NOW SPILL INTO THE DMAP-
SCRATCH PARTITION.

1222.0 *** SYSTEM FATAL MESSAGE 1222 (LDRTRN)

Main Index
 180 MSC Nastran Error Messages
Errors 1000 - 1999

AN UNEXPECTED END OF FILE WAS DETECTED ON A NEUTRAL FILE DURING %1 OPER-

ATION

User information:
THIS ERROR TERMINATES PROGRAM EXECUTION AND GENERALLY OCCURS WHEN
THE %2 JOB FAILS DURING NEUTRAL FILE CREATION

User action:
REVIEW NEUTRAL FILE CREATION JOB FOR FATAL MESSAGES

1222.1 *** SYSTEM FATAL MESSAGE 1222 (INPTT4)

AN UNEXPECTED END OF FILE WAS DETECTED ON %1 INPUTT4 FILE ON UNIT %2

User information:
THIS ERROR TERMINATES PROGRAM EXECUTION AND GENERALLY OCCURS WHEN
RECORD 2 INDICATES MORE DATA THEN ACTUALLY EXISTS ON RECORD 3

User action:
REVIEW DATA FILE FOR POSSIBLE DATA DISCREPANCIES.
One possible reason for error may be that the OP4 file has been generated by a previous version of MSC
Nastran - then it should be re-generated using the current version in order to remove compatibility issues
that might be present. If the file has been generated by an external program, it is possible that the file format
may be incorrect.

1222.2 *** SYSTEM WARNING MESSAGE 1222 (IO2WFM)

Main Index
 MSC Nastran Error Messages 181
Errors 1000 - 1999

AN UNEXPECTED END OF FILE WAS DETECTED ON A NEUTRAL OP2 FILE DURING %1

OPERATION

User information:
THE END OF FILE OCCURRED WHILE ATTEMPTING TO BEGIN READING A NEW DATA-
BLOCK.
THIS GENERALLY OCCURS WHEN THE JOB CREATING THE NEUTRAL OP2 FILE FAILS
BETWEEN SUCCESSIVE %2 CALLS, OR THE -9 ITAPE OPTION OF %2 WAS NOT THE LAST
I/O PERFORMED ON THE OP2 FILE.OP2 FILE CONTENT MAY BE INCOMPLETE.

User action:
REVIEW NEUTRAL FILE CREATION JOB FOR FATAL MESSAGES AND/OR NO EOF WRIT-
TEN TO OP2 FILE

1222.3 *** SYSTEM FATAL MESSAGE 1222 (IO2WFM)

AN UNEXPECTED END OF FILE WAS DETECTED ON A NEUTRAL OP2 FILE DURING %1
OPERATION

User information: THIS ERROR TERMINATES PROGRAM EXECUTION. THIS GENERALLY

OCCURS WHEN THE JOB CREATING THE NEUTRAL OP2 FILE FAILS WHILE PROCESSING
%2 MODULE. OP2 FILE CONTENT IS INCOMPLETE AND LIKELY CORRUPTED.

User action: REVIEW NEUTRAL FILE CREATION JOB FOR FATAL MESSAGES

1223.0 *** USER WARNING MESSAGE 1223 (UNLDRF)

THE RECL SPECIFIED ON THE ASSIGN STATEMENT IS %1 THAN THE %2 VALUE
ALLOWED FOR NEUTRAL FILES

User information:
1. THE SPECIFIED RECL OF %3 HAS BEEN RESET TO THE %4 ALLOWED RECL OF %5
2. UNIT NUMBER = %6 LOGICAL NAME = %7 FILE NAME = %8

1223.1 *** USER WARNING MESSAGE 1223 (RDASGN)

Main Index
 182 MSC Nastran Error Messages
Errors 1000 - 1999

THE %1 SPECIFIED ON THE %2 STATEMENT IS %3 THAN THE %4 VALUE ALLOWED FOR

NEUTRAL FILES

User information:
1. THE SPECIFIED RECL OF %5 HAS BEEN RESET TO THE %6 ALLOWED RECL OF %7
2. UNIT NUMBER = %8 LOGICAL NAME = %9 FILE NAME = %10

1223.2 *** USER WARNING MESSAGE 1223 (OUTPN2)

THE %1 SPECIFIED ON THE OUTPUT2 STATEMENT IS %2 THAN THE %3 VALUE
ALLOWED FOR NEUTRAL FILES

User information:
1. THE SPECIFIED RECL OF %4 HAS BEEN RESET TO THE %5 ALLOWED RECL OF %6
2. UNIT NUMBER = %7 LOGICAL NAME = %8 FILE NAME = %9

1223.3 *** USER WARNING MESSAGE 1223 (LDLDRF)

THE RECL SPECIFIED ON THE ASSIGN STATEMENT IS %1 THAN THE %2 VALUE
ALLOWED FOR NEUTRAL FILES

User information:
1. THE SPECIFIED RECL OF %3 HAS BEEN RESET TO THE %4 ALLOWED RECL OF %5
2. UNIT NUMBER = %6 LOGICAL NAME = %7 FILE NAME = %8

1224.0 *** USER WARNING MESSAGE 1224 (LDLDRF)

NO RECL WAS SPECIFIED ON THE ASSIGN,DBLOAD STATEMENT FOR UNIT %1.

User information: THE RECL HAS BEEN SET TO THE DEFAULT VALUE OF %2 CHARACTERS
1224.1 *** USER WARNING MESSAGE 1224 (LDLDRF)
NO RECL WAS SPECIFIED ON THE ASSIGN,DBLOAD STATEMENT FOR UNIT %1.

User information: THE RECL HAS BEEN SET TO THE VALUE OF %2 CHARACTERS
DETECTED ON THE NEUTRAL FILE

1225.0 *** USER WARNING MESSAGE 1225 (LDLDRF)

Main Index
 MSC Nastran Error Messages 183
Errors 1000 - 1999

THE RECL ON THE ASSIGN,DBUNLOAD STATEMENT DIFFERS FROM THE INTERNAL

RECL OF THE NEUTRAL FILE OF UNIT %1.

User information:
1. THE INTERNAL RECL FROM THE NEUTRAL FILE WILL BE USED.
2. THE INTERNAL NEUTRAL FILE RECL IS %2.
3. THE ASSIGN,DBUNLOAD STATEMENT RECL IS %3.

1226.0 *** SYSTEM FATAL MESSAGE 1226 (DBINIT).

THE LENGTH OF THE %1 STATEMENT HAS EXCEEDED THE MAXIMUM OF %2 CHARAC-
TERS.

User information: THE NUMBER OF CHARACTERS DOES NOT INCLUDE COMMENTS OR

LEADING AND TRAILING BLANKS.

User action: REMOVE REDUNDANT EMBEDDED BLANKS OR USE MULTIPLE %3 STATE-

MENTS.

1227.0 *** USER FATAL MESSAGE 1227 (LCDRVR)

THE DATABLOCK/PARAMETER NAME %1 CANNOT BE PROCESSED DUE TO ABOVE POS-
SIBLE SYNTAX ERROR IN THE ABOVE DBLOCATE STATEMENT.

1227.1 *** USER FATAL MESSAGE 1227 (DBEQIV)

THE DATABLOCK/PARAMETER NAME %1 CANNOT BE PROCESSED DUE TO POSSIBLE
SYNTAX ERROR IN THE DBEQUIV STATEMENT ABOVE.

1227.2 *** USER FATAL MESSAGE 1227 (DBDELE)

THE DATABLOCK/PARAMETER NAME %1 CANNOT BE PROCESSED DUE TO POSSIBLE
SYNTAX ERROR IN THE DBDELETE STATEMENT ABOVE.

1243.0 *** USER WARNING MESSAGE 1243, (NASLOG)

Main Index
 184 MSC Nastran Error Messages
Errors 1000 - 1999

AN ERROR OCCURRED PROCESSING SYMBOL NAMES IN THE CONTROL FILE.

SYMBOL SPECIFICATION IGNORED
RECORD = %1, NLOG = %2
LOG = %3 ALIAS = %4

User action: CHECK SYMBOL NAME SPECIFICATION. THE SYMBOL NAME MUST BE PRES-
ENT. THE SYMBOL NAME CAN BE NO MORE THAN 16 CHARACTERS IN LENGTH. THE
SYMBOL VALUE CAN BE NO MORE THAN %5 CHARACTERS IN LENGTH.

1245.0 *** USER FATAL MESSAGE 1245, (BIO)

AN ALLOCATION ERROR HAS OCCURRED FOR A DATABASE FILE, FILX = %1.
WRITE ATTEMPTED ON FILX WHICH WAS OPENED FOR READONLY.
LOGICAL = %2 FILE = %3

User action: CHECK FILE ASSIGN STATEMENTS AND FILE ACCESS PRIVILEGES.
This error can also occur in a restart run if BPOOL is too low and the cold start run INIT'ed a new
dbset other than MASTER and DBALL; so increasing BPOOL may avoid the error.

1246.0 *** CONTINUATION MESSAGE (SEVERITY = MCONT (-1))

BIOMSG: ERROR %1 HAS OCCURRED IN ROUTINE %2, FILE INDEX = %3.

1246.1 *** CONTINUATION MESSAGE (SEVERITY = MCONT (-1))

LOGICAL NAME IS %1
FILENAME IS %2

1246.2 *** CONTINUATION MESSAGE (SEVERITY = MCONT (-1))

STATUS = %1

1247.0 *** USER FATAL MESSAGE 1247, (BIO...)

UNABLE TO VALIDATE DATABASE FILE FORMAT. DATABASE MAY NOT HAVE BEEN
BUILT ON A COMPATIBLE PLATFORM.
TIMESTAMP/RECL VALIDATION FAILED. FILX = %1, LOGNAME = %2, NSBUF3 = %3
FILE IS %4

1247.1 *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT (-1))

TIMESTAMP OFFSET INVALID.

Main Index
 MSC Nastran Error Messages 185
Errors 1000 - 1999

1247.2 *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT (-1))

TIMESTAMP SIGNATURE VALIDATION FAILED.

1247.3 *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT (-1))

RECL VALUE NOT POSITIVE.

1247.4 *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT (-1))

WORK AREA ALLOCATION (FMALLC) FAILED.

1247.5 *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT (-1))

FILE IS EMPTY.

1247.6 *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT (-1))

NUMERIC FORMAT NOT COMPATIBLE WITH THIS PLATFORM.

1247.7 *** CONTINUATION MESSAGE FOR 1247.0 (SEVERITY = MCONT (-1))

RECL SHOULD BE %1, ACTUAL VALUE IS %2.

1248.0 *** SYSTEM INFORMATION MESSAGE 1248, (BIO)

SYSTEM(207).NE.0 - File locking suppressed.

1249.0 *** USER WARNING MESSAGE 1249, (BIO)

STATUS = %1, FILX = %2, LOGNAME = %3, NSBUF3 = %4
FILE = %5

1249.1 *** CONTINUATION MESSAGE FOR 1249.0 (SEVERITY = MCONT (-1))

BLKNBR = %1

1249.2 *** CONTINUATION MESSAGE FOR 1249.0 (SEVERITY = MCONT (-1))

WARNING MESSAGE IS --

1249.3 *** CONTINUATION MESSAGE FOR 1249.0 (SEVERITY = MCONT (-1))

%1

Main Index
 186 MSC Nastran Error Messages
Errors 1000 - 1999

1250.0 *** USER FATAL MESSAGE 1250, (BIO)

STATUS = %1, FILX = %2, LOGNAME = %3, NSBUF3 = %4
FILE = %5

1250.1 *** CONTINUATION MESSAGE FOR 1250.0 (SEVERITY = MCONT (-1))

BLKNBR = %1

1250.2 *** CONTINUATION MESSAGE FOR 1250.0 (SEVERITY = MCONT (-1))

ERROR MESSAGE IS --

1250.3 *** CONTINUATION MESSAGE FOR 1250.0 (SEVERITY = MCONT (-1))

%1

1251.0 *** SYSTEM FATAL MESSAGE 1251, (BIO)

FILX = %1 (%2 HEX) OUT OF RANGE

1254.0 *** SYSTEM FATAL MESSAGE 1254 (RPLPAT)

CANNOT REPLACE THE EXISTING PATH.
REPTR=%1 KEYNO=%2 PATCNT=%3

1254.1 *** SYSTEM FATAL MESSAGE 1254 (RPLPAT)

CANNOT REPLACE MIS-MATCHED NUMBER OF QUALIFIERS.
LENGTH=%1 QUALS(1)=%2

1254.2 *** SYSTEM FATAL MESSAGE 1254 (RPLPAT)

CANNOT REPLACE THE NONEXISTENT PATH.
REPTR=%1 KEYNO=%2

1255.0 *** USER WARNING MESSAGE 1255 (LCLDBS)

Main Index
 MSC Nastran Error Messages 187
Errors 1000 - 1999

THE DATABASE ASSIGNED TO LOGICAL NAME %1 IS INCOMPATIBLE WITH THIS VER-

SION OF THE PROGRAM.

User information:
DATABASE VERSION IS %2
PROGRAM VERSION IS %3

User actions: IF RUN TERMINATES DUE TO THE INCOMPATIBILITY, CONVERT THE DATA-
BASE USING THE HEXAGON AB MIGRATION TOOLS.

1255.1 *** USER WARNING MESSAGE 1255 (LCLDBS)

THE DATABASE ASSIGNED TO LOGICAL NAME %1 IS INCOMPATIBLE WITH THIS VER-
SION OF THE PROGRAM.

User information:
DATABASE VERSION IS %2
PROGRAM VERSION IS %3

1256.0 *** USER FATAL MESSAGE 1256 (ATTDBS)

THE DELIVERY DATABASE ASSIGNED TO LOGICAL NAME %1 IS INCOMPATIBLE WITH
THIS VERSION OF THE PROGRAM.

User information:
DELIVERY DATABASE VERSION IS %2
PROGRAM VERSION IS %3

User actions:
REBUILD THE DELIVERY DATABASE UNDER THE PROGRAM VERSION.

1257.0 *** USER FATAL MESSAGE 1257

THE MAX-SIZE SPECIFIED ON THE INIT FMS STATEMENT FOR THE FIRST MEMBER OF
DBSET %1 IS %2 BLOCKS AND IS LESS THAN THE RECOMMENDED MINIMUM OF %3
BLOCKS.

User action: SPECIFY A MAX-SIZE VALUE AT OR ABOVE THE RECOMMENDED VALUE.

Main Index
 188 MSC Nastran Error Messages
Errors 1000 - 1999

1257.1 *** USER FATAL MESSAGE 1257

THE MAX-SIZE SPECIFIED ON THE INIT FMS STATEMENT OR SMEM VALUE IN THE RC
FILE OR SMEM KEYWORD IN THE COMMAND PROCEDURE FOR THE MEMFILE OF
DBSET %1 IS %2 BLOCKS AND IS LESS THAN THE RECOMMENDED MINIMUM OF %3
BLOCKS.

User action: SPECIFY A MAX-SIZE OR SMEM VALUE AT OR ABOVE THE RECOMMENDED

VALUE.

1259.0 *** USER FATAL MESSAGE 1259 (SEMTRN)

PREPROCESSOR CONTROL VALIDATION FAILED.%1

*** User information: THE BULK DATA SECTION OF THE INPUT DATA HAS BEEN
CHANGED OR WAS CREATED ON A DIFFERENT COMPUTER.

1259.1 *** USER FATAL MESSAGE 1259 (SEMTRN)

PREPROCESSOR CONTROL VALIDATION FAILED.%1

*** User information: THE BULK DATA SECTION OF THE INPUT DATA HAS BEEN
CHANGED

1260.0 *** SYSTEM FATAL MESSAGE 1260 (SLCDRV)

UNABLE TO OPEN DBDIR DBSET FOR DATABLOCK %1.

1261.0 *** SYSTEM FATAL MESSAGE 1261 (UNLNXT)

INSUFFICIENT LOCAL WORKING ARRAY.

Programmer action: INCREASE LOCAL ARRAY FIST IN UNLNXT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

1261.1 *** SYSTEM FATAL MESSAGE 1261 (OUTPX2)

INSUFFICIENT LOCAL WORKING ARRAY.

Programmer action: INCREASE LOCAL ARRAY FIST IN OUTPX2.

Main Index
 MSC Nastran Error Messages 189
Errors 1000 - 1999

1261.2 *** SYSTEM FATAL MESSAGE 1261 (CPYFIL)

INSUFFICIENT LOCAL WORKING ARRAY.

Programmer action: INCREASE LOCAL ARRAY FIST IN CPYFIL.

1261.3 *** SYSTEM FATAL MESSAGE 1261 (COPY1)

INSUFFICIENT LOCAL WORKING ARRAY.

Programmer action: INCREASE LOCAL ARRAY FIST IN COPY1.

1262.0 *** SYSTEM FATAL MESSAGE 1262 (UNLNXT)

DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED BY UNL-
NXT.

1262.1 *** SYSTEM FATAL MESSAGE 1262 (OUTPX2)

DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED BY OUT-
PX2.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

1262.2 *** SYSTEM FATAL MESSAGE 1262 (LDINPT)

DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED FROM THE
NEUTRAL FILE.

Programmer information: %3 NAMES SHOULD BE RETRIEVED. %4 WORDS ARE STORED IN

THE 2ND RECORD OF THE CURRENT DATABLOCK.

1262.3 *** SYSTEM FATAL MESSAGE 1262 (CPYFIL)

DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED BY CPYFIL.

1262.4 *** SYSTEM FATAL MESSAGE 1262 (COPY1)

DATABLOCK %1 (%2) HAS ASSOCIATED FILES THAT CANNOT BE RETRIEVED BY COPY1.

1265.0 *** SYSTEM WARNING MESSAGE 1265 (GTASCT)

THE DATABLOCK %1 (%2) HAS NO ASSOCIATED FILES.

Main Index
 190 MSC Nastran Error Messages
Errors 1000 - 1999

1266.0 *** SYSTEM FATAL MESSAGE 1266 (SLCDRV)

THE FILE %1 IS NOT A MAIN FILE.

Programmer information: THE FIRST ARGUMENT OF XOPEN, XGOPEN OR XMOPEN HAS TO

BE THE FIST NUMBER OF A MAIN FILE.

1266.1 *** SYSTEM FATAL MESSAGE 1266 (GTASCT)

THE FILE %1 IS NOT A MAIN FILE.

Programmer information: THE FIRST ARGUMENT OF GTASCT HAS TO BE THE FIST NUM-
BER OF A MAIN FILE.

1267.0 *** SYSTEM FATAL MESSAGE 1267 (GTFREE)

NO MORE MEMORY SPACE AVAILABLE FOR EXECUTIVE TABLES.

User action: INCREASE DEFAULT NUMBER OF EXECUTIVE TABLES ENTRIES VIA SYSTEM
CELL 162. SYSTEM(162) IS CURRENTLY SET TO %1.

1268.0 *** SYSTEM FATAL MESSAGE 1268 (SLCDRV)

SUBROUTINE SALLOC RETURNED A NULL FIST NUMBER.

Programmer action: CHECK SALLOC ARGUMENTS.

1269.0 *** SYSTEM FATAL MESSAGE 1269 (SLCDRV)

THE ASSOCIATED FILE %1 OF DATABLOCK %2 IS ALREADY OPEN.

1270.0 *** SYSTEM FATAL MESSAGE 1270 (SLCDRV)

THE ASSOCIATED FILE %1 CANNOT BE ATTACHED TO DATABLOCK %2.

Programmer information: NO MORE THAN %3 ASSOCIATED FILES CAN BE ATTACHED TO

ONE DATABLOCK.

Main Index
 MSC Nastran Error Messages 191
Errors 1000 - 1999

1273.0 *** USER FATAL MESSAGE 1273 (WRTTRL)

ATTEMPT TO OPEN DATABLOCK %1 (%2). INVALID DATABLOCK FORMAT, ITS
NUMERIC OR/AND INDICES FILES WERE NOT FOUND.

User information: THE DATABLOCK WAS PROBABLY CREATED IN A PRIOR VERSION OF

THE PROGRAM.

User action: MAKE SURE THAT THE DATABLOCK IS COMPATIBLE WITH THE CURRENT
VERSION OF THE PROGRAM.

1273.1 *** USER FATAL MESSAGE 1273 (OPNFCU)

ATTEMPT TO OPEN DATABLOCK %1 (%2). INVALID DATABLOCK FORMAT, ITS
NUMERIC OR/AND INDICES FILES WERE NOT FOUND.

User information: THE DATABLOCK WAS PROBABLY CREATED IN A PRIOR VERSION OF

THE PROGRAM.

User action: MAKE SURE THAT THE DATABLOCK IS COMPATIBLE WITH THE CURRENT
VERSION OF THE PROGRAM.

1273.2 *** USER FATAL MESSAGE 1273 (OPNFAC)

ATTEMPT TO OPEN DATABLOCK %1 (%2). INVALID DATABLOCK FORMAT, ITS
NUMERIC FILE WAS NOT FOUND.

User information: THE DATABLOCK WAS PROBABLY CREATED IN A PRIOR VERSION OF

THE PROGRAM.

User action: MAKE SURE THAT THE DATABLOCK IS COMPATIBLE WITH THE CURRENT
VERSION OF THE PROGRAM.

1274.0 *** SYSTEM WARNING MESSAGE 1274 (GTASCT)

THERE ARE MORE THAN %1 ASSOCIATED FILES ATTACHED TO DATABLOCK %2 (%3).

Programmer information: ONLY THE FIRST %4 ASSOCIATED FILES ARE RETURNED.

Main Index
 192 MSC Nastran Error Messages
Errors 1000 - 1999

1275.0 *** SYSTEM FATAL MESSAGE 1275 (BPGETB)

THE SIZE OF THE BUFFER POOL AREA IS INSUFFICIENT TO CONTINUE PROCESSING.

User action: INCREASE THE SIZE WITH THE BUFFPOOL KEYWORD ON THE NASTRAN
STATEMENT.

User information: THE NUMBER OF BLOCKS CURRENTLY ALLOCATED FOR BUFFER POOL-
ING IS%1.

1275.1 *** SYSTEM FATAL MESSAGE 1275 (BP_ERROR)

BUFFER POOL ERROR %1

Programmer information: POSSIBLE LOGIC ERROR

1276.0 *** SYSTEM FATAL MESSAGE 1276 (LDINPT)

SPARSE FACTOR MATRIX %1 (%2) HAS AN INCORRECT NUMBER OF ASSOCIATED FILES
STORED IN THE NEUTRAL FILE.

Programmer information: THE SPARSE FACTOR MATRIX TYPE IS %3 AND SHOULD HAVE %4
FILES. THE NEUTRAL FILE FOR THE MATRIX HAS %5 FILES.

1277.0 *** USER FATAL MESSAGE 1277 (LCLDBS)

THE FILE ASSIGNED TO LOGICAL NAME = %1 IS NOT A VALID MASTER DBSET FOR A
DBLOCATED DATABASE.

User action: VERIFY THE FILE NAME SPECIFIED ON THE ASSIGN %2 STATEMENT.

1277.1 *** USER FATAL MESSAGE 1277 (DBDEF)

THE FILE ASSIGNED TO LOGICAL NAME = %1 IS NOT A VALID MASTER DBSET FOR A PRI-
MARY DATABASE.

User action: VERIFY THE FILE NAME SPECIFIED ON THE ASSIGN %2 STATEMENT.

Main Index
 MSC Nastran Error Messages 193
Errors 1000 - 1999

1277.2 *** USER FATAL MESSAGE 1277 (ATTDBS)

THE FILE ASSIGNED TO LOGICAL NAME = %1 IS NOT A VALID MASTER DBSET FOR A
DELIVERY DATABASE.
1279.0 *** SYSTEM WARNING MESSAGE 1279 (RDINIT)
THE BUFFSIZE IS LARGER THAN THE MAXIMUM ALLOWABLE BUFFSIZE FOR THIS
MACHINE.

User information: THE SPECIFIED VALUE WILL BE RESET TO THE MAXIMUM ALLOWED
WHICH IS %1

1280.0 *** USER FATAL MESSAGE 1280 (RDINIT)

THE LOGICAL NAME %1 IS ALREADY SPECIFIED FOR A MEMBER OF THE %2 DBSET.

1281.0 *** SYSTEM FATAL MESSAGE 1281 (SLCDRV)

AN ATTEMPT WAS MADE TO ATTACH AN ASSOCIATED FILE TO EXECUTIVE FILE %1.

Programmer information: ASSOCIATED FILES ARE NOT ALLOWED TO BE ATTACHED TO

EXECUTIVE FILES.

1282.0 *** SYSTEM FATAL MESSAGE 1282 (SLCDRV)

AN ATTEMPT WAS MADE TO OPEN A NON EXISTENT ASSOCIATED FILE %1,%2, TO
READ.

Programmer information: CHECK THE NAME OF THE ASSOCIATED FILE TO OPEN.

1283.0 *** SYSTEM FATAL MESSAGE 1283 (XOPEN)

AN ATTEMPT WAS MADE TO ATTACH AN ASSOCIATED FILE TO DATABLOCK %1 WITH-
OUT BUFFER POOLING.

User action: BUFFERPOOLING IS ACTIVATED WITH NASTRAN SYSTEM(119) AND NASTRAN

BUFFPOOL STATEMENTS.

1283.1 *** SYSTEM FATAL MESSAGE 1283 (XGOPEN)

Main Index
 194 MSC Nastran Error Messages
Errors 1000 - 1999

AN INVALID ATTEMPT WAS MADE TO ATTACH AN ASSOCIATED FILE TO DATABLOCK

%1 WITHOUT BUFFER POOLING.

User action: BUFFERPOOLING IS ACTIVATED WITH NASTRAN SYSTEM(119) AND NASTRAN

BUFFPOOL STATEMENTS.

1284.0 *** USER FATAL MESSAGE 1284 (REIGL)

THE REQUESTED NUMBER OF SEGMENTS (NUMS OR SYSTEM(197)=%1) IS NOT VALID.
LIMITS ARE 1 TO %2.

1284.1 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 1284 (EVLMSG)

THE REQUESTED NUMBER OF SEGMENTS ( SYSTEM(197)=%1 ) IS TOO LARGE. THE LIMIT
IS %2.

1285.0 *** USER FATAL MESSAGE 1285 (RDINIT)

SCR300 IS SPECIFIED AS A DBSET-NAME ON THE INIT FILE MANAGEMENT STATEMENT.

User information: SCR300 IS A RESERVED NAME AND CANNOT BE INITIALIZED AS A DBSET

NAME.
THE SCR300 PARTITION IS INITIALIZED ON THE INIT SCRATCH STATEMENT.
FOR EXAMPLE, INIT SCRATCH SCR300=(SCRA(50000)).

1286.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 1286 (EVLMSG)

THE VALUE SPECIFIED FOR %1 SYSTEM CELL 119 IS %2

User information: THE VALUE MUST BE EQUAL TO %3 WHICH IS THE DEFAULT.

1287.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 1287 (EVLMSG)

THE VALUE SPECIFIED FOR %1 SYSTEM CELL 114 (OR 'BUFFPOOL KEYWORD) IS %2
User information: THE VALUE MUST BE GREATER THAN %3

1288.0 *** USER INFORMATION MESSAGE 9100 (BIOCRT)

MAXIMUM SIZE REQUESTED FOR FILE EXCEEDS FILE SYSTEM CAPACITY
LOGICAL NAME IS '%4', BLOCK SIZE = %3 WORDS
FILE NAME IS '%5'
REQUESTED BLOCKS COUNT = %1, BLOCKS COUNT RESET TO %2.

Main Index
 MSC Nastran Error Messages 195
Errors 1000 - 1999

Main Index
 196 MSC Nastran Error Messages
Errors 1000 - 1999

Main Index
 MSC Nastran Error Messeges 197
Errors 2000 - 2999

Errors 2000 - 2999

2001.0 *** USER FATAL MESSAGE 2001 (USRMSG)
SEQGP ENTRY REFERENCES UNDEFINED GRID POINT %1

User information: SEQGP references a point which is not a grid or scalar point.

2002.0 *** SYSTEM FATAL MESSAGE 2002 (USRMSG)

GRID POINT %1 NOT IN EQEXIN.

User information: This message indicates a program design error in GP1.

2003.0 *** USER FATAL MESSAGE 2003 (GP1C)

COORDINATE SYSTEM %1 REFERENCES UNDEFINED GRID POINT %2 IN SUPEREL
MENT OR MODULE %3

User information: Applies to CORD1j definitions.

2003.1 *** USER FATAL MESSAGE 2003 (USRMSG)

COORDINATE SYSTEM %1 REFERENCES UNDEFINED GRID POINT %2

User information: Applies to CORD1j definitions.

2004.0 *** USER FATAL MESSAGE 2004 (GP1C)

COORDINATE SYSTEM %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2 IN
SUPERELEMENT OR MODULE %3

User information: Applies to CORD2j definitions.

2004.1 *** USER FATAL MESSAGE 2004 (USRMSG)

COORDINATE SYSTEM %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2

User information: Applies to CORD2j definitions.

Main Index
 198 MSC Nastran Error Messeges
Errors 2000 - 2999

2004.2 *** USER FATAL MESSAGE 2004 (GP1C)

COORDINATE SYSTEM %1 REFERENCES A NON-BASIC COORDINATE SYSTEM %2 IN
CORD2i DEFINITIONS, WHICH IS NOT SUPPORTED IN SOL 600.

User information: A CORD2i can only reference the basic coordinate system in SOL 600.

2005.0 *** SYSTEM FATAL MESSAGE 2005 (GP1C)

INCONSISTENT COORDINATE SYSTEM DEFINITIONS DETECTED IN SUPERELEMENT
OR MODULE %1

System information: At least one coordinate system cannot be tied to the basic system.

2005.1 *** SYSTEM FATAL MESSAGE 2005 (USRMSG)

INCONSISTENT COORDINATE SYSTEM DEFINITION.

System information: At least one coordinate system cannot be tied to the basic system.

2006.1 *** USER FATAL MESSAGE 2006

GRID POINT %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2 IN
SUPERELEMENT OR MODULE %3

2006.2 *** USER FATAL MESSAGE 2006 (USRMSG)

GRID POINT %1 REFERENCES UNDEFINED COORDINATE SYSTEM %2 IN FIELD 3 OR IN
FIELD 7

2007.0 *** USER FATAL MESSAGE 2007 (USRMSG)

ELEMENT %1 REFERENCES UNDEFINED GRID POINT %2

User information: The element specified points to a non-existent grid or scalar point.
This message may occur in superelement or module analysis when the reference grid point GO is neither
exterior nor interior to the superelement or module. An avoidance is to instead use the vector component
method to define the element coordinate system.

2007.1 *** USER FATAL MESSAGE 2007 (MODGM2)

ELEMENT %1 ID = %2 REFERENCES UNDEFINED GRID POINT %3

Main Index
 MSC Nastran Error Messeges 199
Errors 2000 - 2999

2007.2 *** USER FATAL MESSAGE 2007 (MODGM2)

THE NUMBER OF DEFINED %7 ELEMENTS IS REDUCED BY %1% ACCORDING TO THE
USER PARAMETER %6=%2
NUMBER OF %7 ELEMENTS DEFINED IN BULK DATA SECTION %3
NUMBER OF %7 ELEMENTS RANDOMLY DELETED %4
NUMBER OF %7 ELEMENTS RETAINED FOR THE ANALYSIS %5

2007.3 *** USER WARNING MESSAGE 2007 (MODGM2)

%1=%2 IS SPECIFIED. ALL %3S ARE DELETED.

2007.4 *** USER FATAL MESSAGE 2007 (MODGM2)

CFAST ELEMENT %1 ORIENTATION VECTOR YIELDS BAD PROJECTION

2007.5 *** USER FATAL MESSAGE 2007 (MDG2EL1)

THE NUMBER OF DEFINED CELASi ELEMENTS IS REDUCED BY %1%
NUMBER OF %5 ELEMENTS DEFINED IN BULK DATA SECTION %2
NUMBER OF %5 ELEMENTS RANDOMLY DELETED %3
NUMBER OF %5 ELEMENTS RETAINED FOR THE ANALYSIS %4

2007.6 *** USER WARNING MESSAGE 2007 (MDG2EL1)

%1=%2 IS SPECIFIED. ALL %3S ARE DELETED.

2007.7 *** USER FATAL MESSAGE 2007 (USRMSG)

ELEMENT %1 REFERENCES UNDEFINED GRID POINT %2 IN MODULE 0

2007.8 *** USER FATAL MESSAGE 2007 (USRMSG)

INTERNALLY GENERATED ELEMENT %1 REFERENCES UNDEFINED GRID POINT %2

2008.0 *** USER FATAL MESSAGE 2008 (USRMSG)

LOAD SET %1 REFERENCES UNDEFINED GRID POINT %2

User information: The LOAD set specified points to a non-existent grid or scalar point

2008.1 *** USER FATAL MESSAGE 2008 (MKAEF1)

Main Index
 200 MSC Nastran Error Messeges
Errors 2000 - 2999

UNDEFINED GRID POINT ID = %1 IS REFERENCED BY FORCEI OR MOMENTI BULK DATA

ENTRY.
2008.2 *** USER FATAL MESSAGE 2008 (USRMSG)
LOAD SET %1 REFERENCES UNDEFINED GRID POINT %2 IN MODULE 0

User information: The LOAD set specified points to a non-existent grid or scalar point.

2008.3 *** USER FATAL MESSAGE 2008 (NLC3DC)

Duplicate element IDs across different element types is not supported in 3D contact analysis stress
recovery.
Correct duplicate Element ID %1 encountered for %2 and %3 Element.

2009.0 *** USER FATAL MESSAGE 2009 (USRMSG)

TEMPERATURE SET %1 REFERENCES UNDEFINED GRID POINT %2

User information: The TEMP set specified points to a non-existent grid or scalar point.

2009.1 *** USER WARNING MESSAGE 2009 (NLCTMA)

TMPSET Bulk Data entry ID=%1 REFERENCES UNDEFINED GRID POINT %2

2009.2 *** USER FATAL MESSAGE 2009 (USRMSG)

TEMPERATURE SET %1 REFERENCES UNDEFINED GRID POINT %2 IN MODULE 0

User information: The TEMP set specified points to a non-existent grid or scalar point.

2010.0 *** USER FATAL MESSAGE 2010 (USRMSG)

ELEMENT %1 REFERENCES UNDEFINED PROPERTY %2

User information: The element specified points to a non-existent property entry.

2010.1 *** USER FATAL MESSAGE 2010

PROPERTY ID %1 FOR ELEMENT TYPE %2 IS DUPLICATED

2010.2 *** USER WARNING MESSAGE 2010

NSMADD ENTRY %1 CONTAINS UNDEFINED SET ID %2

2010.3 *** USER WARNING MESSAGE 2010

Main Index
 MSC Nastran Error Messeges 201
Errors 2000 - 2999

ELEMENT TYPE %1 IS NOT SUPPORTED BY NSML/NSML1 ENTRY

2010.4 *** USER WARNING MESSAGE 2010

%1 ENTRY WITH SET ID %2 AND PROPERTY TYPE "ELEMENT" HAS 1-D AND 2-D ELE-
MENTS DEFINED

2010.5 *** USER WARNING MESSAGE 2010 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE HAS ENCOUNTERED AN UNSUP-
PORTED ELEMENT TYPE (%1) DURING DISPLAY GEOMETRY PROCESSING. THE ELE-
MENT TYPE IS IGNORED AND NO FACE INFORMATION IS OUTPUT.

User information: The model contains an element type that cannot currently be interpreted by the
ADAMS/FLEX toolkit. It is being ignored.
There will be no element face entries for the geometry of elements of this type stored to the modal neutral
file.

2010.6 *** USER FATAL MESSAGE 2010 (MODGM2)

PLSOLID ID = %1 REFERENCES MATHP ID = %2 WHICH DOES NOT EXIST.

User action: SPECIFY MATHP ENTRY WITH ID = %3.

2010.7 *** USER WARNING MESSAGE 2010 (MODGM2)

PLSOLID ID = %1 REFERENCES MATHP ID = %2.
IF USING A LINEAR SOLUTION SEQUENCE, NONLINEAR ELEMENTS REFERENCING A
PLSOLID ENTRY WILL NOT PROVIDE STRESS RESULTS.
THE ELEMENTS WILL GENERATE THE CORRECT STIFFNESS MATRICES FOR THE LINEAR
SOLUTION. IN CONTACT ANALYSIS, THE SEPARATION.
CRITERIA IBSEP=2 OR 4 WON'T WORK AND CONTACT STRESS WON'T BE CALCULATED.

User action: IF YOU WISH TO SEE THE ABOVE MENTIONED OUTPUT, USE SOL 400.

2010.8 *** USER WARNING MESSAGE 2010 (MODGM2)

Main Index
 202 MSC Nastran Error Messeges
Errors 2000 - 2999

IN GENERAL, PLSOLID ID = %1 SHOULD REFERENCE MATERIAL ENTRY MATHP WHICH

DOES NOT EXIST HERE.
IF THIS FILE IS RUN UNMODIFIED IN NOLINEAR SOLUTION SOL 400, A FATAL MESSAGE
WILL RESULT.
IF USING A LINEAR SOLUTION SEQUENCE, IT IS ALLOWED TO USE NONLINEAR ELE-
MENTS REFERENCING A PLSOLID ENTRY BUT WITHOUT MATHP ENTRY FOR MODEL
CHECK. THE ELEMENTS WILL GENERATE THE CORRECT STIFFNESS MATRICES FOR
THE LINEAR SOLUTION, BUT STRESS RESULTS ARE NOT PROVIDED. IN CONTACT
ANALYSIS, SEPARATION CRITERIA IBSEP=2 OR 4 WON'T WORK AND CONTACT STRESS
WON'T BE CALCUATED.

User action: IF YOU WISH TO SEE THE ABOVE MENTIONED OUTPUT, USE SOL 400.

2011.0 *** USER FATAL MESSAGE 2011 (TA1A)

NO PHBDY ENTRIES FOR CHBDYP

2011.1 *** USER FATAL MESSAGE 2011 (USRMSG)

NO PROPERTY ENTRY FOR ELEMENT TYPE %1

2011.2 *** USER FATAL MESSAGE 2011 (MDG2E6)

NO MATERIAL ENTRY FOR PROPERTY TYPE %1

2011.3 *** USER FATAL MESSAGE 2011 (TA1A)

No %1 entries for %2

2012.0 *** USER FATAL MESSAGE 2012 (GP1GSM)

IDENTIFICATION %1 SAME BETWEEN GRID, SCALAR OR POINT OR AUTOMATICALLY
GENERATED Q-SET SPOINT ID IN SUPERELEMENT OR MODULE %2

2012.1 *** USER FATAL MESSAGE 2012 (USRMSG)

GRID POINT %1 SAME AS SCALAR POINT.

User information: Identification of grid and scalar points must be unique.

2012.2 *** USER FATAL MESSAGE 2012 (GP1GSM)

IDENTIFICATION %1 SAME BETWEEN GRID, SCALAR OR POINT OR AUTOMATICALLY
GENERATED Q-SET SPOINT ID

Main Index
 MSC Nastran Error Messeges 203
Errors 2000 - 2999

2013.0 *** USER WARNING MESSAGE 2013 (USRMSG)

NO STRUCTURAL ELEMENTS EXIST.

User information: Model check for structural elements.

2014.0 *** SYSTEM FATAL MESSAGE 2014 (USRMSG)

LOGIC ERROR IN ECPT CONSTRUCTION.

System information: Internal logic error in connection table construction.

Send run to Hexagon for analysis.

2015.0 *** USER WARNINT MESSAGE 2015 (USRMSG)

EITHER NO ELEMENTS CONNECT INTERNAL GRID POINT %1
OR IT IS CONNECTED TO A RIGID ELEMENT OR A GENERAL ELEMENT.

2016.0 *** USER FATAL MESSAGE 2016 (USRMSG)

NO MATERIAL PROPERTIES EXIST AND THESE ARE REQUIRED FOR MATRIX GENERA-
TION.

User action: ADD MATERIAL PROPERTIES TO YOUR BULK DATA FILE.

User information: Material properties are required for matrix generation and none are present in the Bulk
Data Section.

2017.0 *** USER FATAL MESSAGE 2017 (USRMSG)

MATERIAL PROPERTY IDENTIFICATION %1 WAS DUPLICATED.

User action: CHECK ALL MATI ENTRIES FOR UNIQUE MATERIAL IDENTIFICATION NUM-
BERS.

2018.0 *** USER FATAL MESSAGE 2018 (USRMSG)

Main Index
 204 MSC Nastran Error Messeges
Errors 2000 - 2999

MATT%1 ENTRY %2 DID NOT MATCH PARENT TYPE.

User action: ENSURE THAT REFERENCED TEMPERATURE AND MATERIAL ENTRIES ARE
IDENTIFIED AS THE SAME TYPE.

User information: A temperature-dependent material entry does not match the correct type of parent
entry.

2019.0 *** USER FATAL MESSAGE 2019,

AN INCONSISTENT VALUE FOR -NU.21- HAS BEEN COMPUTED FOR MAT8 ID %1.

User action: REVIEW VALUES FOR E1 and E2 TO ENSURE THAT EVALUATION OF GAMMA =
1 - NU12*(NU12*E12/E1) RESULTS IN NON-NEGATIVE VALUE.

User information: The evaluation of gamma = 1 - nu12*(nu12*E12/E1) resulted in a negative value that
will not cause mathematical failure, but could cause strange behavior on elements which reference this
MAT ID.

2019.1 *** USER WARNING MESSAGE 2019 (USRMSG)

AN INCONSISTENT VALUE FOR -NU.21- HAS BEEN COMPUTED FOR MAT8 ID %1.

User action: REVIEW VALUES FOR E1 and E2 TO ENSURE THAT EVALUATION OF GAMMA =
1 - NU12*(NU12*E12/E1) RESULTS IN NON-NEGATIVE VALUE.

User information: The evaluation of gamma = 1 - nu12*(nu12*E12/E1) resulted in a negative value that
will not cause mathematical failure, but could cause strange behavior on elements which reference this
MAT ID.

2020.0 *** USER WARNING MESSAGE 2020 (USRMSG)

ONE OR MORE OF THE ALLOWABLE STRESS CONSTANTS WERE INCORRECT FOR ELE-
MENT %1 PLY %2

User information: Failure theory calculations were requested, but Sb on the PCOMP entry or Xt, Xc, Yt,
Yc, S or HF1-HF6 or HT1-HT12 or HFB1-HFB12 on the MAT8 were less than or equal to zero.
See the element/PLY for which PCOMP or MAT8 entry is in error. The failure index calculations were not
made. Either drop request for Failure theory calculations or be sure that Sb,Xt, Xc, Yt, Yc and S or HF1-
HF6 or HT1-HT12 or HFB1-HFB12 are positive.

Main Index
 MSC Nastran Error Messeges 205
Errors 2000 - 2999

2021.0 *** SYSTEM FATAL MESSAGE 2021 (USRMSG)

BAD GMMAT- CALLING SEQUENCE.

System information: The calling sequence of the subroutine which calls either subroutine GMMATD or
GMMATS defined a non-conformable matrix product. The subroutine examines the transpose flags in
combination with the orders of the matrices to make sure that a conformable matrix product is defined by
this input data. This test clearly is made for purposes of calling routine checkout only. No tests are made,
nor can they be made, to insure that the calling routine has provided sufficient storage for arrays.

2022.0 *** USER FATAL MESSAGE 2022 (USRMSG)

PROBLEM SIZE OF %1 DOF HAS EXCEEDED THE LIMIT OF 65535 FOR AN INDIVIDUAL
PROBLEM OR SUPERELEMENT.

2024.0 *** USER FATAL MESSAGE 2024,

OPERATION CODE %1 NOT DEFINED FOR MODULE PARAM.

User action: MAKE SURE OPERATION CODE PARAMETER IS ENCLOSED WITHIN SINGLE
QUOTES ("'")

User information: The operation code "SUB" was not chosen from the legal list or was misspelled.

2024.1 *** SYSTEM FATAL MESSAGE 2024 (USRMSG)

UNDEFINED MESSAGE.

2025.0 *** USER FATAL MESSAGE 2025 (SEPOMT)

COORDINATE SYSTEM %1 REFERENCED BY GRID %2 IS UNDEFINED IN SUPERELEMENT
OR MODULE %3.

2025.1 *** USER FATAL MESSAGE 2025 (MODULE)

Main Index
 206 MSC Nastran Error Messeges
Errors 2000 - 2999

UNDEFINED COORDINATE SYSTEM ID = %1

User information: Check coordinate system numbers used on Bulk Data entries against those defined on
CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems.
This message can occur in superelement analysis when the CORD1x entry is in the Bulk Data entry. The
cause is that grid points referenced on the CORD1x entry are not connected by elements in the
superelement or module.
An avoidance is to use the CORD2x formats, which reference points in space rather than grid points.
This message also occurs frequently when using a non-Hexagon model generation program that places grid
point identification numbers in the field used for material identification numbers by modern plate ele-
ments. See especially the CTRIA3 entry, field 7.

2025.2 *** USER FATAL MESSAGE 2025 (EBSH4D)

UNDEFINED COORDINATE SYSTEM ID = %1 IS REFERRED IN OCID FIELD OF CBUSH
ENTRY ID = %2.

User information: Check coordinate system numbers used on Bulk Data entries against those defined on
CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems.
This message can occur in superelement or module analysis when the CORD1x entry is in the Bulk Data
entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the
superelement or module.
An avoidance is to use the CORD2x formats, which reference points in space rather than grid points.
This message also occurs frequently when using a non-Hexagon model generation program that places grid
point identification numbers in the field used for material identification numbers by modern plate ele-
ments. See especially the CTRIA3 entry, field 7.

2025.3 *** USER FATAL MESSAGE 2025 (EBSH3D)

UNDEFINED COORDINATE SYSTEM ID = %1 IS REFERRED IN CBUSH ENTRY ID = %2.

User information: Check coordinate system numbers used on Bulk Data entries against those defined on
CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems.
This message can occur in superelement or module analysis when the CORD1x entry is in the Bulk Data
entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the
superelement or module. An avoidance is to use the CORD2x formats, which reference points in space
rather than grid points.
This message also occurs frequently when using a non-Hexagon model generation program that places grid
point identification numbers in the field used for material identification numbers by modern plate ele-
ments. See especially the CTRIA3 entry, field 7.

Main Index
 MSC Nastran Error Messeges 207
Errors 2000 - 2999

2025.4 *** USER FATAL MESSAGE 2025 (APD0)

%1 COORDINATE SYSTEM ID = %2 REFERENCED BY %3 ENTRY IS NOT DEFINED.

User information: Check coordinate system numbers used on Bulk Data entries against those defined on
CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems.
This message can occur in superelement or module analysis when the CORD1x entry is in the Bulk Data
entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the
superelement or module.
An avoidance is to use the CORD2x formats, which reference points in space rather than grid points.
This message also occurs frequently when using a non-Hexagon model generation program that places grid
point identification numbers in the field used for material identification numbers by modern plate ele-
ments. See especially the CTRIA3 entry, field 7.

2025.5 *** USER FATAL MESSAGE 2025

COORDINATE SYSTEM ID = %1 REFERENCED BY PLPLANE ENTRY FOR ELEMENT ID = %2
IS NOT DEFINED.

User information: Check coordinate system numbers used on Bulk Data entries against those defined on
CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems.
This message can occur in superelement or module analysis when the CORD1x entry is in the Bulk Data
entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the
superelement or module. An avoidance is to use the CORD2x formats, which reference points in space
rather than grid points.
This message also occurs frequently when using a non-Hexagon model generation program that places grid
point identification numbers in the field used for material identification numbers by modern plate ele-
ments. See especially the CTRIA3 entry, field 7.

2025.7 *** SYSTEM FATAL MESSAGE 2025 (APDST2,APDCST)

Main Index
 208 MSC Nastran Error Messeges
Errors 2000 - 2999

COORDINATE SYSTEM ID = %1 REFERENCED BY CAERO%2 ENTRY ID = %3 IS NOT

FOUND.

User information: Check coordinate system numbers used on Bulk Data entries against those defined on
CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems.
This message can occur in superelement or module analysis when the CORD1x entry is in the Bulk Data
entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the
superelement or module.
An avoidance is to use the CORD2x formats, which reference points in space rather than grid points.
This message also occurs frequently when using a non-Hexagon model generation program that places grid
point identification numbers in the field used for material identification numbers by modern plate ele-
ments. See especially the CTRIA3 entry, field 7.

2025.8 *** USER FATAL MESSAGE 2025 (BGSLPD)

UNDEFINED COORDINATE SYSTEM ID = %1 IS REFERRED IN %2 ENTRY ID = %3.

User information: Check coordinate system numbers used on Bulk Data entries against those defined on
CORD1C, CORD1R, etc., Bulk Data entries to insure that there are no undefined coordinate systems.
This message can occur in superelement or module analysis when the CORD1x entry is in the Bulk Data
entry. The cause is that grid points referenced on the CORD1x entry are not connected by elements in the
superelement or module.
An avoidance is to use the CORD2x formats, which reference points in space rather than grid points.
This message also occurs frequently when using a non-Hexagon model generation program that places grid
point identification numbers in the field used for material identification numbers by modern plate ele-
ments. See especially the CTRIA3 entry, field 7.

2025.9 *** USER WARNING MESSAGE 2025 (SDR2MM)

COORDINATE SYSTEM ID=%1 SPECIFIED ON THE MAXMIN COMMAND IS UNDEFINED.

User information: THE %2 COORDINATE SYSTEM WILL BE USED.

2025.10 *** USER WARNING MESSAGE 2025 (ILMPGLB)

COORDINATE SYSTEM ID=%1 SPECIFIED ON MONPNT3 ENTRY %2 IS UNDEFINED.

User information: ALL TERMS FOR THIS MONPNT3 ARE OUTPUT AS ZERO AND PROCESS-
ING CONTINUES TO THE NEXT MONPNT3.

Main Index
 MSC Nastran Error Messeges 209
Errors 2000 - 2999

2025.11 *** USER FATAL MESSAGE 2025

UNDEFINED RECTANGULAR COORDINATE SYSTEM ID = %1 IS REFERRED IN TOPVAR
ENTRY ID = %2.

User information: CHECK COORDINATE SYSTEM NUMBERS USED ON BULK DATA ENTRIES
AGAINST THOSE DEFINED ON CORD1R AND CORD2R BULK DATA ENTRIES TO INSURE.

2025.12 *** USER FATAL MESSAGE 2025

INCONSISTENT COORDINATE SYSTEM ID = %1 and %2 DETECTED IN TOPVAR ENTRY
ID = %3.

User information: ONE COORDINATE SYSTEM DEFINED ON CORD1R AND CORD2R BULK
DATA ENTRIES IS ALLOWED IN EACH TOPVAR ENTRY.

2025.13 *** USER FATAL MESSAGE 2025

INVALID USE OF MANUFACTURABILITY CONSTRAINTS DETECTED IN TOPVAR ENTRY
ID = %1.

User information: CHECK CASTING/EXTRUSION CONSTRAINTS AGAINST SYMMETRIC

CONSTRAINTS DEFINED ON TOPVAR BULK DATA ENTRIES TO INSURE VALID COMBI-
NATIONS.

2025.14 *** USER FATAL MESSAGE 2025

INVALID USE OF CASTING AND EXTRUSION CONSTRAINTS DETECTED IN TOPVAR
ENTRY ID = %1.

User information: CASTING, EXTRUSION, AND OVERHANG CONSTRAINTS CANNOT BE

PRESENT IN THE SAME TOPVAR BULK DATA ENTRY.

2025.15 *** USER FATAL MESSAGE 2025 (USRMSG)

UNDEFINED COORDINATE SYSTEM %1 IS REFERENCED BY ELEMENT %2 ID=%3.

Main Index
 210 MSC Nastran Error Messeges
Errors 2000 - 2999

2025.16 *** USER FATAL MESSAGE 2025

INVALID USE OF CASTING or EXTRUSION or OVERHANG CONSTRAINTS DETECTED IN
TOPVAR ENTRY ID = %1.

User information: CASTING, EXTRUSION, or OVERHANG CONSTRAINTS CAN BE USED FOR

SOLID PROPERTY ONLY

2025.17 *** USER FATAL MESSAGE 2025

INVALID USE OF OVERHANG CONSTRAINTS DETECTED IN TOPVAR ENTRY ID = %1.

User information: OVERHANG CONSTRAINTS CANNOT BE USED FOR MORE THAN ONE
TOPVAR BULK DATA ENTRY

2025.18 *** USER FATAL MESSAGE 2025

INVALID USE OF OVERHANG CONSTRAINTS DETECTED IN TOPVAR ENTRY ID = %1.

User information: OVERHANG CONSTRAINTS CANNOT BE USED WITH SYMMETRY

CONSTRAINTS

2026.0 *** USER FATAL MESSAGE 2026 (USRMSG)

ELEMENT %1 GEOMETRY YIELDS UNREASONABLE MATRIX.

User information: Referenced element geometry and/or properties yield a numerical

result which causes an element stiffness or mass matrix to be undefined.
Possible causes include, but are not limited to,
1. The length of a rod or bar is zero because the end points have the same coordinates,
2. The sides of a triangle or quadrilateral are collinear which leads to a zero cross product in defining an
element coordinate system,
3. The bar/bend orientation vector is parallel to the bar/bend axis, or
4. A shear panel has zero thickness or modulus. Check GRID Bulk Data entries defining element end
points for bad data.

2027.0 *** USER FATAL MESSAGE 2027 (USRMSG)

Main Index
 MSC Nastran Error Messeges 211
Errors 2000 - 2999

ELEMENT %1 HAS INTERIOR ANGLE GREATER THAN 180 DEGREES AT GRID POINT %2

User information: SHEAR panel element with the referenced element number has been defined with the
four grid points out of the proper cyclical order.
See Bulk Data entry definition for CSHEAR entry.

2027.1 *** USER FATAL MESSAGE 2027 (USRMSG)

ELEMENT %1 IN MODULE 0 HAS INTERIOR ANGLE GREATER THAN 180 DEGREES AT
GRID POINT %2 IN MODULE 0

User information: SHEAR panel element with the referenced element number has been defined with the
four grid points out of the proper cyclical order.
See Bulk Data entry definition for CSHEAR entry.

2028.0 *** SYSTEM FATAL MESSAGE 2028 (USRMSG)

SMA3A ERROR NUMBER %1

System information: Internal logic error in Subroutine SMA3A of Module SMA3. Possibly an error exists
in the generation of the GEI data block. Use the TABPT module to print GEI.

2029.0 *** USER FATAL MESSAGE 2029 (USRMSG)

UNDEFINED TEMPERATURE SET %1

User information: The referenced temperature set had no default temperature defined.
Define a temperature or default temperature for each grid point in the model.

2029.1 *** USER FATAL MESSAGE 2029 (NLCTMA)

TTEMP Bulk Data entry ID=%1 references an undefined TMPSET %2 entry.

2030.0 *** SYSTEM FATAL MESSAGE 2030 (USRMSG)

BAD GPTT DATABLOCK DETECTED.

2031.0 *** USER FATAL MESSAGE 2031 (USRMSG)

ELEMENT %1 UNACCEPTABLE GEOMETRY.

User information: Possible error on GRID entry or connection entry.

Main Index
 212 MSC Nastran Error Messeges
Errors 2000 - 2999

2031.1 *** USER WARNING MESSAGE 2031 (GEOB3D)

FOR CBEAM3 ELEMENT %1, CHECK GRID POINT LOCATIONS

User information: Results for this element should be checked since the mid-node point GC is either
- not between the two end points, GA and GB, or
- it is too far from both of them. This results in a highly curved element.

2033.0 *** USER FATAL MESSAGE 2033 (USRMSG)

SINGULAR H-MATRIX FOR ELEMENT %1

User information: Possible error on GRID entry or connection entry.

2034.0 *** SYSTEM FATAL MESSAGE 2034 (USRMSG)

ELEMENT %1 SIL-S DO NOT MATCH PIVOT.

2035.0 *** USER FATAL MESSAGE 2035 (USRMSG)

QUADRILATERAL %1 INTERIOR ANGLE GREATER THAN 180 DEGREES.

User information: Possible error on connection entry for element.

2036.0 *** USER FATAL MESSAGE 2036 (USRMSG)

SINGULAR MATRIX FOR ELEMENT %1

User information: Possible error on GRID entry or connection entry.

2037.0 *** USER FATAL MESSAGE 2037.

ILLEGAL GEOMETRY FOR TRIAR ELEMENT WITH ID =%1

2037.1 *** USER FATAL MESSAGE 2037 (USRMSG)

BAD ELEMENT %1 GEOMETRY.

User information: Possible error on GRID entry or connection entry.

2038.0 *** SYSTEM FATAL MESSAGE 2038,

Main Index
 MSC Nastran Error Messeges 213
Errors 2000 - 2999

SINGULAR MATRIX FOR ELEMENT %1

System information: Possible error on GRID entry, connection entry, or rigid element.
Rigid elements must have 6 n-set degrees of freedom that define all six rigid body motions of the element.

2038.1 *** USER FATAL MESSAGE 2038,

RBE3 ELEMENT %1 IS SINGULAR.

User action: ADD MORE DOFS TO THE CONNECTED POINTS TO INSURE THAT THEY CAN
CONSTRAIN ALL 6 RIGID BODY MODES OF THE ELEMENT.

2038.2 *** USER FATAL MESSAGE 2038,

MONDSP1 ENTRY %1 IS SINGULAR.

User action: ADD MORE DOFS TO THE CONNECTED POINTS TO INSURE THAT THEY CAN
CONSTRAIN ALL 6 RIGID BODY MODES OF THE ELEMENT.

2039.0 *** USER FATAL MESSAGE 2039 (USRMSG)

ZERO SLANT LENGTH FOR HARMONIC %1 OF CCONEAX %2

User information: Possible error on GRID entry or connection entry.

2040.0 *** USER FATAL MESSAGE 2040 (USRMSG)

SINGULAR MATRIX FOR ELEMENT %1

User information: Possible error on GRID entry or connection entry or a zero value of G was specified on
a MAT1 entry for a Beam element. A zero value of G may be used if K1 and K2 are explicitly set to zero
also. Their default value is nonzero.

2041.0 *** USER FATAL MESSAGE 2041 (USRMSG)

A MATT1, MATT2, MATT3 OR MATS1 ENTRY REFERENCES TABLE NUMBER %1 WHICH IS
NOT DEFINED ON A TABLEM1,TABLEM2,TABLEM3,TABLEM4 OR TABLES1 ENTRY.

User information: The user must insure that all table identification numbers on MATT1, MATT2,
MATT3, or MATS1 entries reference tables which exist in the Bulk Data Deck.

Main Index
 214 MSC Nastran Error Messeges
Errors 2000 - 2999

2042.0 *** USER FATAL MESSAGE 2042 (USRMSG)

MISSING MATERIAL INPUT %1 FOR ELEMENT %2

User information: The referenced material identification number is missing, or the corresponding
property does not refer proper material definition ID.
The user should check to see that all element property Bulk Data entries (e.g., PBAR, PROD) reference
material identification number for material property entries that exist in the Bulk Data Section.

2042.1 *** USER FATAL MESSAGE 2042 (TA1MCK)

%1 PROPERTY ID %2 REFERENCES UNDEFINED MATERIAL PROPERTY ID %3 %4

User information: No material property Bulk Data entry (e.g. MAT1, MAT2) could be found for the ref-
erenced material table identification number. The user should check the specified element property Bulk
Data entry (e.g., PBAR, PROD) for reference to the identification number of the missing material Bulk
Data entry. Either replace the ID of the missing material entry on the property entry with one that exists, or
add a new material Bulk Data entry with the missing identification number.

2042.2 *** USER FATAL MESSAGE 2042 (MDG2E7)

MISSING MATERIAL TABLE %1 FOR PROPERTY ID = %2.

User information: The referenced material identification number is missing, or the corresponding property
does not refer proper material definition ID.
The user should check to see that all element property Bulk Data entries (e.g., PBAR, PROD) reference
material identification number for material property entries that exist in the Bulk Data Section.

2042.3 *** USER FATAL MESSAGE 2042 (IFP10E)

Designed %1 property id %2 references MAT1/MAT9 ID %3 which does not exist

User action: Make sure the designed property refers to a MAT1(or MAT9) and that MAT1 (or MAT9) ID
%3 Exists.

Main Index
 MSC Nastran Error Messeges 215
Errors 2000 - 2999

2042.4 *** USER FATAL MESSAGE 2042 (TA1MCK)

PAXSYMH PROPERTY ID %1 CANNOT FIND MATERIAL ID %2 AMONG MAT1 OR MAT9
ENTRIES.

User information: PAXSYMH ENTRIES MAY REFERENCE ONLY MAT1 OR MAT9 ENTRIES

2042.5 *** USER FATAL MESSAGE 2042 (IFP10I)

%1 PROPERTY ID %2 REFERENCES UNDEFINED MAT1 ID %3 %4
TOMVAR ENTRY SUPPORTS MAT1 ONLY

2042.6 *** USER FATAL MESSAGE 2042 (IFP10E)

TOPOLOGY OPTIMIZATION SUPPORTS ONLY %1 UNIQUE ANISOTROPIC MATERIAL
PROPERTIES. THIS NUMBER HAS BEEN EXCEEDED.

User action: Reduce The Number of MAT9 PIDS Referenced by selected TOPVAR Entries

2042.7 *** USER FATAL MESSAGE 2042 (IFP10E)

PROPERTY ID %1 DEFINED ON TOPVAR ID %2 REFERENCES MAT9 ID %3

User action: TOPOLOGY OPTIMIZATION CAN SUPPORT ANISOTROPIC MATERIAL PROP-

ERTIES FOR PSOLID ONLY

2042.8 *** USER FATAL MESSAGE 2042 (IFP10E)

TOPOLOGY OPTIMIZATION CANNOT SUPPORT STRESS CONSTRAINTS FOR ANISOTRO-
PIC MATERIAL PROPERTIES

2042.9 *** USER FATAL MESSAGE 2042 (MAT)

MISSING MATERIAL ID %1 FOR PROPERTY ID %2

User information: The referenced material identification number is missing, or the corresponding property
ID does not refer to a proper material ID.
The user should check to see that all element property Bulk Data entries (e.g., PBAR, PROD) reference
material identification numbers for material entries that exist in the Bulk Data Section.

Main Index
 216 MSC Nastran Error Messeges
Errors 2000 - 2999

2043.0 *** USER FATAL MESSAGE 2043 (USRMSG)

MISSING MATERIAL TABLE %1

2044.0 *** USER FATAL MESSAGE 2044 (USRMSG)

UNDEFINED TEMPERATURE SET %1

User information: The referenced temperature set was selected in the Case Control but not defined in the
Bulk Data.
2045.0 *** USER FATAL MESSAGE 2045 (USRMSG)
TEMPERATURE UNDEFINED AT GRID POINT WITH INTERNAL INDEX %1

2046.0 *** USER FATAL MESSAGE 2046 (USRMSG)

UNDEFINED ELEMENT DEFORMATION SET %1

User information: The referenced element deformation set was selected in the Case Control but not
defined in the Bulk Data.

2047.0 *** USER WARNING MESSAGE 2047 (USRMSG)

UNDEFINED MULTI-POINT CONSTRAINT SET %1

User information: A multipoint constraint set selected in the Case Control could not be found in either an
MPC or MPCADD entry or a set referenced on an MPCADD entry could not be found on an MPC entry.

2048.0 *** USER FATAL MESSAGE 2048 (USRMSG)

UNDEFINED GRID POINT %1 IN MULTI-POINT CONSTRAINT SET %2

User information: An MPC entry references a grid point which has not been defined.
This message can be output in superelement or module analysis if:
1. All grids referenced on the MPC are not interior to the same superelement or module, or
2. The dependent DOF are downstream of the independent DOF. As a minimum requirement, when
an MPC (or RBE) definition includes grid points interior to more than one superelement or module,
then the independent DOF must be downstream of the dependent DOF.

2049.0 *** USER WARNING MESSAGE 2049 (SEPSEQ)

GRID POINT %1 SPECIFIED ON %2 IS NOT DEFINED FOR SUPERELEMENT OR MODULE
%3

Main Index
 MSC Nastran Error Messeges 217
Errors 2000 - 2999

2049.1 *** USER FATAL MESSAGE 2049,

UNDEFINED GRID POINT %1 HAS A COORDINATE REFERENCED ON A %2 CARD.

2049.2 *** USER WARNING MESSAGE 2049,

THE %1 BULK DATA ENTRY SPECIFIES ILLEGAL DEGREE(S) OF FREEDOM %2 FOR %3
POINT %4.

User information: The illegal degrees-of-freedom will be ignored but the single DOF at this %3 point
will be included in the requested set.
Fluid GRID points have only one degree of freedom. The allowable DOF code is 1. All other codes (2-6)
are ignored.
SCALAR points have only one degree of freedom. The allowable DOF code is blank or 0. All other codes
(1-6) are ignored.

2049.4 *** USER FATAL MESSAGE 2049 (USRMSG)

UNDEFINED GRID POINT %1 HAS A COORDINATE REFERENCED ON A CONSTRAINT
CARD.

User information: An ASET, BSET, CSET, QSET, MPC, SPC, OMIT, or SUPORT entry references an
undefined grid or scalar point. In superelement or module analysis, the equivalent entries SEBSET,
SECSET, or SEQSET must refer to exterior points of the superelement or module being processed. This
message has been observed when the superelement or module has no exterior points, due to
modeling errors.
This message has also been observed to reference grid point 0 when scalar points have any of the
components 1 through 6 referenced in the C field. Zero or blank should be used instead.

2049.5 *** USER FATAL MESSAGE 2049

Main Index
 218 MSC Nastran Error Messeges
Errors 2000 - 2999

UNDEFINED GRID POINT %1 ON A %2 CARD.

IF MDLPRM BDF ENTRY UDEFGRID PARAMETER IS NOT SET OR IS 0,
THIS FATAL MESSAGE BECOMES A WARNING MESSAGE AND THE JOB CONTINUES.

2049.6 *** USER WARNING MESSAGE 2049

UNDEFINED GRID POINT %1 ON A %2 CARD IGNORED. ANY OTHERS ALSO IGNORED.
THE SEVERITY OF THIS MESSAGE CAN BE CONTROLLED BY MDLPRM UDEFGRID
PARAMETER.

2049.7 *** USER WARNING MESSAGE 2049

UNDEFINED GRID POINT %1 ON A %2 CARD IGNORED.

2049.8 *** USER FATAL MESSAGE 2049

GRID POINT %1 ON A BNDGRID ENTRY IS A FLUID GRID POINT.
THE SPECIFICATION OF FLUID GRID POINTS ON A BNDGRID ENTRY IS NOT SUP-
PORTED.

2050.0 *** USER FATAL MESSAGE 2050 (USRMSG)

UNDEFINED GRID POINT %1 HAS A SUPPORT COORDINATE.

User information: A SUPORT entry references a grid point which has not been defined.

2051.0 *** USER FATAL MESSAGE 2051 (USRMSG)

UNDEFINED GRID POINT %1 IN SINGLE-POINT CONSTRAINT SET %2

User information: In superelement or module analysis this message may not be issued. It is recommended
that all superelement or module definitions (e.g., SESET and SEID field on GRID entries) be removed
temporarily so that PARAM,CHECKOUT may be used to check for this type of error.

2051.1 *** USER WARNING MESSAGE 2051 (GP4)

UNDEFINED GRID POINT %1 IN SPC SET %2 IGNORED. (ANY OTHERS ALSO IGNORED)

2051.2 *** USER WARNING MESSAGE 2051 (DPD)

THE FOLLOWING SPC ENTRIES ARE BEING IGNORED:
SPC ID GRID/SPOINT ID COMPONENT # VALUE

Main Index
 MSC Nastran Error Messeges 219
Errors 2000 - 2999

2051.3 *** USER INFORMATION MESSAGE 2051 (GP4)

RIGID ELEMENTS INCLUDED VIA MPC %1 IN CASE CONTROL AND SET3 %2 IN BULK
DATA.

2052.0 *** USER FATAL MESSAGE 2052 (GP4)

UNDEFINED GRID POINT %2 ON AN %1 ENTRY WITH %1 SET ID %3

2052.1 *** USER FATAL MESSAGE 2052 (USRMSG)

UNDEFINED GRID POINT %1 IN SINGLE-POINT CONSTRAINT SET %2

User information: An SPC entry in the selected SPC set references a grid point which has not been defined.

2052.2 *** USER FATAL MESSAGE 2052 (GP4)

UNDEFINED GRID POINT %1 ON AN MPCD ENTRY WITH MPCD SET ID %2

2052.3 *** USER WARNING MESSAGE 2052 (G4MPCYM)

MPCY AND/OR MPCD EQUATION CONSTANT COEFFICIENTS EXIST BUT THE ASSOCI-
ATED OUTPUT DATA BLOCK COULD NOT BE OPENED.
THE CONSTANT COEFFICIENTS WILL BE IGNORED.

2052.4 *** USER FATAL MESSAGE 2052 (USRMSG)

UNDEFINED GRID POINT %1 IN MODULE 0 IN SINGLE-POINT CONSTRAINT SET %2

User information: An SPC entry in the selected SPC set references a grid point which has not been defined.

2053.0 *** USER WARNING MESSAGE 2053 (USRMSG)

UNDEFINED SINGLE-POINT CONSTRAINT SET %1

User information: A single point constraint set selected in the Case Control could not be found on either
an SPCADD, SPC or SPC1 entry, or a set referenced on an SPCADD entry could not be found on either
an SPC or SPC1 entry.

2054.0 *** USER FATAL MESSAGE 2054 (USRMSG)

SUPER ELEMENT %1 REFERENCES UNDEFINED SIMPLE ELEMENT %2

2056.0 *** USER FATAL MESSAGE 2056 (USRMSG)

Main Index
 220 MSC Nastran Error Messeges
Errors 2000 - 2999

UNDEFINED SUPER ELEMENT %1 PROPERTIES

2057.0 *** USER FATAL MESSAGE 2057 (USRMSG)

IRRATIONAL SUPER ELEMENT %1 TOPOLOGY

2058.0 *** USER WARNING MESSAGE 2058 (USRMSG)

ELEMENT %1 CONTRIBUTES TO THE DAMPING MATRIX WHICH IS PURGED. IT WILL BE
IGNORED.

2059.0 *** USER FATAL MESSAGE 2059 (USRMSG)

UNDEFINED GRID POINT %1 ON SE--BFE ENTRY FOR SUPER ELEMENT %2

2060.0 *** USER FATAL MESSAGE 2060 (USRMSG)

UNDEFINED GRID POINT %1 ON QDSEP ENTRY FOR SUPER ELEMENT %2

2061.0 *** USER FATAL MESSAGE 2061 (USRMSG)

UNDEFINED GRID POINT %1 ON GENERAL ELEMENT %2

User information: A general element references an undefined grid point.

2062.0 *** USER FATAL MESSAGE 2062 (USRMSG)

UNDEFINED SUPER ELEMENT PROPERTY %1 FOR SUPER ELEMENT %2

2063.0 *** SYSTEM FATAL MESSAGE 2063 (USRMSG)

TA1C LOGIC ERROR

2064.0 *** USER FATAL MESSAGE 2064 (USRMSG)

UNDEFINED EXTRA POINT %1 REFERENCED ON SEQEP ENTRY.

User information: An attempt has been made to resequence an undefined extra point.

2064.1 *** USER WARNING MESSAGE 2064 (ROTOR2)

UNDEFINED EXTRA POINT %1 REFERENCED ON RSPINT ENTRY WITH ROTORID OF %2
AND ROTRSEID OF %3.
SPIN RATE WILL NOT BE OUTPUT FOR THIS ROTOR.

2064.2 *** USER WARNING MESSAGE 2064 (ROTOR2)

Main Index
 MSC Nastran Error Messeges 221
Errors 2000 - 2999

UNDEFINED EXTRA POINT %1 REFERENCED ON UNBALNC ENTRY WITH ID %2.

UNBALNC FORCE CORRESPONDING TO THIS EXTRA POINT WILL NOT BE OUTPUT.

2064.3 *** USER INFORMATION MESSAGE 2064 (ROTOR2)

FOR ROTOR WITH ID %1 AND SEID %2, SPIN DIRECTION IS SAME AS THE ASSUMED
DIRECTION

2064.4 *** USER INFORMATION MESSAGE 2064 (ROTOR2)

FOR ROTOR WITH ID %1 AND SEID %2, SPIN DIRECTION IS REVERSE OF THE ASSUMED
DIRECTION

2064.5 *** USER INFORMATION MESSAGE 2064 (ROTOR2)

FOR ROTOR WITH ID %1 AND SEID %2, GRID %3 DEFINED ON RSPINR/T IS NOT
FOUND.

2064.6 *** USER INFORMATION MESSAGE 2064 (ROTOR2)

FREQUENCIES FOR NON-REFERENCE ROTOR WITH ID %1 AND SEID %2 ARE NOT
CRITICAL SPEEDS.

User action: TO GET CRITICAL SPEEDS FOR A PARTICULAR ROTOR, DEFINE

IT AS THE REFERENCE ROTOR.

2064.7 *** USER FATAL MESSAGE 2064 (IFPecREF)

FOR FREQUENCY RESPONSE SYNC ANALYSIS, UNBALANCE LOAD WITH ID %1 DEFINED
ON ROTOR WITH ID %2 AND SEID %3 HAS SPEED RATIO NOT EQUAL TO 1.0 WITH
RESPECT TO REFERENCE ROTOR ID %4

2064.8 *** USER FATAL MESSAGE 2064 (ROTOR2)

FOR ROTOR WITH ID %1 AND SEID %2, GRID %3
AND GRID %4 DEFINED ON RSPINR/RSPINT HAVE THE SAME LOCATION
ALONG THE ROTOR AXIS

2064.9 *** USER INFORMATION MESSAGE 2064 (ROTPRD)

GRID %1 DEFINED ON THE AXIS FOR ROTOR WITH ID %2 IS NOT FOUND IN THE
MODEL

Main Index
 222 MSC Nastran Error Messeges
Errors 2000 - 2999

2064.10 *** USER FATAL MESSAGE 2064 (ROTOR2)

FOR FREQUENCY RESPONSE SYNC ANALYSIS, UNBALANCE LOAD WITH ID %1 DEFINED
ON ROTOR WITH ID %2 AND SEID %3 DOES NOT HAVE THE SAME SPEED TABLE AS
THAT OF THE REFERENCE ROTOR ID %4

2064.11 *** USER INFORMATION MESSAGE 2064 (ROTOR2)

FOR FREQUENCY RESPONSE SYNC ANALYSIS, UNBALANCE LOAD WITH ID %1 DEFINED
ON NON-REFERENCE ROTOR WITH ID %2 AND SEID %3

2064.12 *** USER INFORMATION MESSAGE 2064 (ROTOR2)

FOR FREQUENCY RESPONSE SYNC ANALYSIS, UNBALANCE LOAD WITH ID %1 DEFINED
ON REFERENCE ROTOR WITH ID %2 AND SEID %3

2065.0 *** USER FATAL MESSAGE 2065 (USRMSG)

UNDEFINED GRID POINT %1 ON DMIG ENTRY.

User information: Direct matrix input references an undefined grid point.

2066.0 *** USER FATAL MESSAGE 2066 (USRMSG)

UNDEFINED GRID/SCALAR POINT %1 ON DAREA, DELAY, DPHASE, FRFXIT OR FRFXIT1
ENTRY.

User information: A DAREA, DELAY or DPHASE entry or an FRF excitation entry references an unde-
fined grid/scalar point.

2066.1 *** USER FATAL MESSAGE 2066 (GP1D and GP1F)

%1 BULK DATA ENTRY %2 REFERENCES UNDEFINED %3 POINT %4

2066.2 *** USER FATAL MESSAGE 2066 (GP1M3DC)

The following list of grid points are missing. This is possibly caused by an error in contact body definition.

User information: All contact bodies must be in the residual.

2067.0 *** USER FATAL MESSAGE 2067 (USRMSG)

Main Index
 MSC Nastran Error Messeges 223
Errors 2000 - 2999

UNDEFINED GRID/SCALAR/EXTRA POINT %1 IN BULK DATA ENTRY: %2%3.

User information: A nonlinear dynamic load references an undefined grid/scalar/extra point.

2068.0 *** USER FATAL MESSAGE 2068 (USRMSG)

UNDEFINED GRID POINT %1 IN TRANSFER FUNCTION SET %2

User information: A dynamic loading entry references an undefined grid point.

2069.0 *** USER FATAL MESSAGE 2069 (USRMSG)

UNDEFINED GRID POINT %1 IN TRANSIENT INITIAL CONDITION SET %2

User information: An attempt has been made to specify initial conditions for an undefined grid point.

2070.0 *** USER FATAL MESSAGE 2070 (USRMSG)

REQUESTED DMIG MATRIX %1 IS UNDEFINED.

User information: A DMIG matrix was selected in the Case Control but was not present in the Bulk Data.
2070.1 *** USER FATAL MESSAGE 2070 (MTRXIN)
AN AEDW, AEFORCE OR AEPRESS BULK DATA ENTRY REFERENCES A DIRECT MATRIX
INPUT MATRIX NAME %1 WHICH DOES NOT EXIST.

2071.0 *** USER FATAL MESSAGE 2071 (DPD2)

DYNAMIC LOAD %1 ENTRY %2 REFERENCES UNDEFINED %3 SET %4

User information: A referenced dynamic load table was not present in the Bulk Data.

2071.1 *** USER WARNING MESSAGE 2071 (DPD2)

EXCITATION SET %1 REFERENCED IN DYNAMIC LOAD %2 ENTRY %3 DEFINES A NULL
LOAD

User information:
1. Check for proper excitation ID references on RLOADi, TLOADi and/or ACSRCE entries and the
associated DAREA and/or static load entries. (FORCEi, MOMENTi, etc.).
2. Check for null magnitudes on the above-mentioned entries.

Main Index
 224 MSC Nastran Error Messeges
Errors 2000 - 2999

2071.2 *** USER WARNING MESSAGE 2071 (DPD2)

EXCITATION SET %1 REFERENCED IN DYNAMIC LOAD %2 ENTRY %3 DEFINES NULL
ENFORCED MOTION

User information:
1. Check for proper excitation ID references on RLOADi, TLOADi and/or ACSRCE entries and the
associated enforced motion entries (SPC, SPCD, etc.)
2. Check for null magnitudes on the above-mentioned entries.
3. If enforced motion is defined via SPCD entries, make sure that the referenced components also
appear on SPC, SPC1 or the PS field of GRID entries.
If the above condition exists, USER WARNING MESSAGE 2108 is also issued.

2071.3 *** USER WARNING MESSAGE 2071 (DPD2)

EXCITATION SET %1 REFERENCED IN DYNAMIC LOAD %2 ENTRY %3 DEFINES A NULL
LOAD OR NULL ENFORCED MOTION

User information:
1. Check for proper excitation ID references on RLOADi, TLOADi and/or ACSRCE entries and the
associated DAREA and/or static load and enforced motion entries (FORCEi, MOMENTi, SPC,
SPCD, etc.).
2. Check for null magnitudes on the above-mentioned entries.
3. If enforced motion is defined via SPCD entries, make sure that the referenced components also
appear on SPC, SPC1 or the PS field of GRID entries.
If the above condition exists, USER WARNING MESSAGE 2108 is also issued.

2071.4 *** USER FATAL MESSAGE 2071 (DPDBB)

Main Index
 MSC Nastran Error Messeges 225
Errors 2000 - 2999

THE INPUT EXCITATION MATRICES FOR THE DPD MODULE DO NOT ALL HAVE THE
SAME NUMBER OF COLUMNS.

User action: CHECK THE INPUT TO THE DPD MODULE TO ENSURE THAT ALL OF THE
INPUT EXCITATION MATRICES HAVE THE SAME NUMBER OF COLUMNS.

2072.0 *** SYSTEM WARNING MESSAGE 2072 (USRMSG)

CARD TYPE %1 NOT FOUND ON DATA BLOCK.

System information: This warning message is issued when the trailer bit for the card type= 1 but the corre-
sponding record is not on the data block.

2073.0 *** USER INFORMATION MESSAGE 2073 (USRMSG)

MPYAD METHOD %1,NO. PASSES = %2

2073.1 *** USER INFORMATION MESSAGE 2073.1 (MPYSC2)

SPARSE MPYAD--DETAILS ON COLUMN PACKING
MPYS10 CALLED %1 TIMES, PACKZ CALLED %2 TIMES
MRGOK WAS FALSE %2 TIMES, BIN WAS FULL %4 TIMES

2074.0 *** USER FATAL MESSAGE 2074 (USRMSG)

UNDEFINED TRANSFER FUNCTION SET %1

User action: CHECK CASE CONTROL TFL COMMAND SET SELECTION AS WELL AS
CORRESPONDING TRANSFER FUNCTION (IF IT EXISTS) IN BULK DATA FILE.

2075.0 *** SYSTEM FATAL MESSAGE 2075 (USRMSG)

IMPROPER VALUE -%1- FOR FIRST PARAMETER IN DMAP INSTRUCTION SDR2.

System information: Data recovery was requested for a problem type which was not defined.

2075.1 *** SYSTEM FATAL MESSAGE 2075.

Main Index
 226 MSC Nastran Error Messeges
Errors 2000 - 2999

IMPROPER VALUE - %1 - FOR FIRST PARAMETER IN DMAP INSTRUCTION CASE.

2075.2 *** SYSTEM FATAL MESSAGE 2075 (DPD).

EIGR ENTRY SET ID = %1 HAS UNDEFINED GRID OR SCALAR POINT %2

2076.0 *** USER FATAL MESSAGE 2076 (USRMSG)

TABLES1 BULK DATA ENTRY ID %1, WHICH IS REFERENCED BY MATS1 ENTRY ID %2, IS
INCORRECTLY DEFINED FOR NONLINEAR ANALYSIS, AN EXAMPLE WOULD BE A PLAS-
TIC MATERIAL SHOWING ELASTIC BEHAVIOR AFTER PLASTIC YIELD POINT.

User action: ENTER THE CORRECT TABLE FORM OR CHANGE THE MATS1 ANALYSIS TYPE.

User information: The user has referenced a TABLES1 entry of FORM=1 which is plastic strains and
slopes of the curve in the plastic region rather than FORM=0 which is a list of stress-strain data points. For
FORM=0 tables, the second point was not at the yield location.

2077.0 *** SYSTEM FATAL MESSAGE 2077 (USRMSG)

INVALID NONLINEAR EST APPENDAGE ENCOUNTERED FOR ELEMENT %1 AT LOCA-
TION %2.

System information: While processing the nonlinear EST data block, an appendage was located which did
not conform to the bit specifications on the trailer, thus it could not be processed n the routine's open-core
area. This is a possible user error. Regenerate the ESTNL data block from TA1. If this does not work, then
the code must be reexamined for error.

2078.0 *** USER FATAL MESSAGE 2078 (USRMSG)

TABLES1 ID.%1 HAS INSUFFICIENT NUMBER OF ENTRIES.

User action: UPDATE TABLES1 TO HAVE A MINIMUM OF THREE ENTRIES WHICH WILL
ALLOW THE PLASTIC STRAIN VERSUS STRESS-STRAIN SLOPE APENDAGE TO BE COM-
PUTTED.

2079.0 *** USER FATAL MESSAGE 2079 (USRMSG)

GRID OR SCALAR POINT %1 HAS AN ILLEGAL COMPONENT REFERENCED ON A %2
ENTRY.

2079.1 *** USER FATAL MESSAGE 2079 (GP1D and GP1F)

Main Index
 MSC Nastran Error Messeges 227
Errors 2000 - 2999

%1 BULK DATA ENTRY %2 REFERENCES ILLEGAL COMPONENT %3 FOR %4 POINT ID %5

2079.2 *** USER FATAL MESSAGE 2079 (DPD)

EIGR ENTRY SET ID = %1 HAS AN ILLEGAL COMPONENT %2 REFERENCED ON A GRID
OR SCALAR POINT %3

2079.3 *** USER FATAL MESSAGE 2079 (G4SPC/G4SPC1)

%1 POINT %2 HAS AN ILLEGAL COMPONENT %3 REFERENCED ON %4 ENTRY WITH ID
OF %5

2079.4 *** USER FATAL MESSAGE 2079 (GP1F)

%1 BULK DATA ENTRY %2 REFERENCES %3 POINT ID %4

User information: NLRGAP, NLRSFD AND NLBSH3D BULK DATA ENTRIES MAY REFERENCE
ONLY GRID POINTS

2079.5 *** USER FATAL MESSAGE 2079 (GP1F)

GRID POINTS %1 AND %2 REFERENCED ON %3 BULK DATA ENTRY %4 ARE NOT COIN-
CIDENT

User information: NLRGAP, NLRSFD AND NLBSH3D BULK DATA ENTRIES MUST REFER-
ENCE COINCIDENT GRID POINTS

2079.6 *** USER FATAL MESSAGE 2079 (GP1F)

GRID POINTS %1 AND %2 REFERENCED ON %3 BULK DATA ENTRY %4 DO NOT HAVE
PARALLEL DISPLACEMENT COORDINATE SYSTEMS

2080.0 *** USER WARNING MESSAGE 2080 (USRMSG)

Main Index
 228 MSC Nastran Error Messeges
Errors 2000 - 2999

AN OBSOLETE CAPABILITY FOR %1 PROCESSING IS BEING USED.

THIS CAPABILITY MAY BE DELETED IN THE NEXT SYSTEM.

User information:
As capabilities are replaced by newer technology, the old version is removed. Usually a system or two is
allowed for removal.
Currently the following capabilities are being considered for removal.
PLOTTING The SC 4020 plotter
ELEMENT The element entries CHEXA1, CHEXA2, CHEX8, CHEX20, CQDPLT, CQDMEM,
CQUAD1, CQUAD2,
CQDMEM1, CQDMEM2, CTRIA1, CTRIA2, CTRBSC, CTRPLT, CTRMEM and CWEDGE
CNGRNT The CNGRNT Bulk Data entry.
Before the next system release of MSC NASTRAN, change your input to use the newer capabilities.

2081.0 *** USER FATAL MESSAGE 2081 (USRMSG)

NULL DIFFERENTIAL STIFFNESS MATRIX.

2082.0 *** USER FATAL MESSAGE 2082 (USRMSG)

PROJECTED OR CONCENTRATED LOAD USED ON BEND ELEMENT %1

User information: The PLOAD1 options for projected or concentrated loads are not supported for bend
elements.

2083.0 *** USER FATAL MESSAGE 2083 (TA1NLE).

FOR NONLINEAR MATERIAL PROPERTIES REFERENCED ON THE PSHELL ENTRY, 12I/T3
FIELD MUST BE 1.0 (OR BLANK).

2083.1 *** USER FATAL MESSAGE 2083 (TA1NLE).

FOR NONLINEAR MATERIAL PROPERTIES REFERENCED ON THE PSHELL ENTRY,
MID4 MUST BE BLANK AND MID1 AND MID2 MUST REFERENCE THE SAME MAT1/MATS1
ENTRY COMBINATION.

User information: For nonlinear material properties referenced on the PSHELL entry, MID4 must be
blank and MID1 and MID2 must reference the same MAT1/MATS1 entry combination.

2083.2 *** USER FATAL MESSAGE 2083 (USRMSG)

MATERIAL INPUT INCONSISTENT WITH NONLINEAR FORMULATION FOR ELEMENT %1

Main Index
 MSC Nastran Error Messeges 229
Errors 2000 - 2999

2083.3 *** USER WARNING MESSAGE 2083 (TA1NLE)

FOR ELEMENT %1 MID3 REFERENCE TO A MATS1 IS IGNORED BECAUSE MSC NASTRAN
SHELL THEORY IS A 2-D REPRESENATION OF PLASTICITY.

2083.4 *** USER WARNING MESSAGE 2083 (TA1NLE)

FOR ELEMENT %1 MIDi REFERENCE TO A MATS1 IS IGNORED BECAUSE THE TEMPERA-
TURE DEPENDENT COMPOSITE ELELEMTS DO NOT HAVE MATERIAL NONLINEAR
CAPABILITIES.

2083.5 *** USER FATAL MESSAGE 2083 (TA1NLE)

R-ELEMENTS RBAR, RBAR1, RBE1, RBE2, RBE3, RJOINT, RROR, RTRPLT, AND RTRPLT1
ARE NOT SUPPORTED IN THERMAL ANALYSIS.

User action: REMOVE ALL R-ELEMENTS FROM THE THERMAL MODEL.

2084.0 *** USER FATAL MESSAGE 2084 (USRMSG)

GAP ELEMENT WITH ID. = %1 HAS ILLEGAL GEOMETRY OR CONNECTIONS.

User action: REVIEW CGAP ELEMENT DEFINITION.

2085.0 *** SYSTEM FATAL MESSAGE 2085 (USRMSG)

ELEMENT TYPE %1 NOT SUPPORTED FOR NONLINEAR ANALYSIS.

System information: An element type not currently implemented was encountered on the data block
ESTNL. This should be impossible unless the user inputs an EST data block with its trailer altered.

2086.0 *** USER WARNING MESSAGE 2086 (MODGM2).

THE QUADR/TRIAR ELEMENTS ARE NOT AVAILABLE YET FOR THE NONLINEAR ANALY-
SIS. THEY ARE USED AS LINEAR ELEMENTS.

2086.1 *** USER FATAL MESSAGE 2086.

Main Index
 230 MSC Nastran Error Messeges
Errors 2000 - 2999

THE NONLINEAR FORMULATION IS REQUESTED FOR CQUADR/CTRIAR ELEMENTS

WHICH ARE NOT SUPPORTED IN THIS SOLUTION SEQUENCE.

User action: PLEASE SET NASTRAN QRMETH=1 TO OBTAIN A LINEAR FORMATION IN THIS
SOLUTION SEQUENCE OR RUN SOL 400 TO OBTAIN A NONLINEAR FORMULATION.

2086.2 *** USER FATAL MESSAGE 2086.

THE LAGRANGIAN RIGID ELEMENTS ARE NOT SUPPORTED IN THIS SOLUTION
SEQUENCE.

User action: PLEASE USE SOL 400.

2087.0 *** USER WARNING MESSAGE 2087 (MODGM2).

SINCE QRMETH (OR SYSTEM(370)) IS SET TO 4 OR 5 ON THE NASTRAN STATEMENT,
THEN THE QUAD4/TRIA3 OUTPUT REQUESTS FOR FORCE/STRESS/STRAIN WILL BE
IGNORED AND THE OUTPUT FORMATS FOR QUADR/TRIAR WILL BE USED INSTEAD.

2088.0 *** USER FATAL MESSAGE 2088 (USRMSG)

DUPLICATE TABLE ID %1

User action: ENSURE THAT TABLE IDs ARE UNIQUE ACROSS ALL TABLES TYPES PRESENT
IN BULK DATA.

2089.0 *** USER FATAL MESSAGE 2089 (USRMSG)

TABLE %1 IS UNDEFINED.

User information: The table number in the list of table numbers input to subroutine PRETAB with argu-
ment 7 was not found after reading the DIT data block. Check list of tables in the Bulk Data.

2089.1 *** USER FATAL MESSAGE 2089 (USRMSG)

TABLE %1 WITH ID=%2 IS UNDEFINED.

User information: The table number in the list of table numbers input to subroutine PRETAB with argu-
ment 7 was not found after reading the DIT data block. Check list of tables in the Bulk Data.

2090.0 *** SYSTEM FATAL MESSAGE 2090 (USRMSG)

Main Index
 MSC Nastran Error Messeges 231
Errors 2000 - 2999

TABLE DICTIONARY ENTRY %1 IS MISSING.

System information: Logic error in subroutine PRETAB, or open core used by PRETAB has been
destroyed.

2092.0 *** SYSTEM WARNING MESSAGE 2092 (USRMSG)

SDR2 FINDS A SYMMETRY SEQUENCE LENGTH =%1
AND AN INSUFFICIENT NUMBER OF VECTORS AVAILABLE =%2 WHILE ATTEMPTING TO
COMPUTE STRESSES AND FORCES.
ALL FURTHER STRESS AND FORCE COMPUTATION TERMINATED.

System information: The number of SUBSEQ command coefficients must be less than or equal to the
number of SUBCASES that precede the SUBCOM which contains the SUBSEQ command. Either
increase the number of SUBCASEs or reduce the number of SUBSEQ coefficients.

2093.0 *** USER FATAL MESSAGE 2093 (DPD4)

%5 Bulk Data entry with SID=%1 REFERENCES GRID %2 COMPONENT %3 WHICH IS NOT IN
the D-SET.

User Information: Nonlinear %6 can only be applied to points in the dynamic analysis set (d-set).

User action: Ensure that these components are not being left out of the d-set because they are:
1. Defined as dependent degrees-of-freedom on multipoint constraints or rigid elements and this
cannot be fixed with PARAM,AUTOMSET,YES.
2. Constrained by SPC, SPC1, AUTOSPC, etc.
3. Omitted by OMITi or unspecified on existing ASETi, etc.
Programmer Information: SIL=%4

2093.1 *** USER FATAL MESSAGE 2093 (DPD4)

NLRSFD OR NLRSFDA USER-DEFINED SUBROUTINE IS SUPPORTED IN SOL128 AND
SOL400 (WITH ANALYSIS = NLTRAN OPTION ONLY)

User action: USE ONLY ANALYSIS = NLRTRAN SUBCASE IN SOL400, REMOVE ALL OTHER
LINEAR ANALYSIS SUBCASES

2094.0 *** USER WARNING MESSAGE 2094 (TABFMT)

Main Index
 232 MSC Nastran Error Messeges
Errors 2000 - 2999

KEYNAME %1 NOT IN LIST OF AVAILABLE KEYNAMES.

SET OPT3=2 TO GET OUTPUT FROM NDDL DATA BLOCKS.

User information: Formatted table print is requested for a data block which is not coded in the module.

2099.0 *** USER WARNING MESSAGE 2099 (TABFMT)

NUMWDS =%1

2101.0 *** USER FATAL MESSAGE 2101 (USRMSG)

GRID POINT %1 COMPONENT %2 ILLEGALLY DEFINED IN SETS %3 %4 %5 %6 %7 %8 %9

User information: The above grid point and component are defined in each of the above dependent sub-
sets. A point may belong to a maximum of one dependent subset. This error occurs when a DOF is defined
as belonging to two mutually exclusive sets. A common example of this occurs when a DOF is defined as
dependent an MPC (M-set) as well as being constrained (s-set) on an SPC entry. The message for this states
that the component is illegally defined in the um (user-defined m-set) and us (user-defined s-set) sets. These
two sets are mutually exclusive because all MPC equations are processed before the SPCs are applied
(exception is SOL 24) and the m-set DOFs are removed from the matrix. When the program attempts pply
the SPC, the DOF is no longer available, and the FATAL message is issued. The normal correction for this
is to modify the MPC so that the DOF in question is independent (N-set). Then there is no conflict.

2101.1 *** USER FATAL MESSAGE 2101 (USRMSG)

SCALAR POINT %1 ILLEGALLY DEFINED IN SETS %2 %3 %4 %5 %6 %7 %8

User information: The above scalar point has been defined in each of the above dependent subsets. A point
may belong to at most one dependent subset.

2101.2 *** SYSTEM FATAL MESSAGE 2101 (GP4)

GRID OR SCALAR POINT ID= %1 COMPONENT = %2 FOUND ON THE MPC ENTRY IS
ILLEGAL.

User action: CHECK MPC ENTRIES.

2102.0 *** USER WARNING MESSAGE 2102 (USRMSG)

LEFT HAND MATRIX ROW POSITION %1 OUT OF RANGE - IGNORED.
LEFT HAND MATRIX ROW POSITION %2 OUT OF RANGE - IGNORED.

Main Index
 MSC Nastran Error Messeges 233
Errors 2000 - 2999

2103.0 *** SYSTEM FATAL MESSAGE 2103 (USRMSG)

SUBROUTINE MAT WAS CALLED WITH INFLAG=2, THE SINE OF THE ANGLE X MATERIAL
ORIENTATION ANGLE, NON-ZERO, BUT, SIN(X)**2+COS(X)**2 DIFFERED FROM 1 IN
ABSOLUTE VALUE BY MORE THAN .0001.

2104.0 *** USER FATAL MESSAGE 2104 (USRMSG)

UNDEFINED COORDINATE SYSTEM %1

2105.0 *** USER FATAL MESSAGE 2105 (USRMSG)

PLOAD2 CARD FROM LOAD SET %1 REFERENCES MISSING OR NON-2-D ELEMENT OR
HYPERELASTIC PLANE ELEMENT %2

User information: PLOAD2 entries must reference two-dimensional elements and not reference hyperelas-
tic elements.

2106.0 *** USER FATAL MESSAGE 2106 (USRMSG)

LOAD ENTRY DEFINES NON-UNIQUE LOAD SET %1

User information: All load sets must have unique identification numbers.

2106.1 *** USER FATAL MESSAGE 2106

LOAD BULK DATA ENTRY ID = %1 CONTAINS ILLEGAL MULIPLE REFERENCES TO LOAD
SET ID = %2.

User information: The LOAD bulk data entry may not reference a load set ID more than once in the Si,Li
list.

2107.0 *** USER FATAL MESSAGE 2107 (USRMSG)

EIG- ENTRY FROM SET %1 REFERENCES DEPENDENT COORDINATE OF GRID POINT %2

User information: When the point option is used on an EIGR entry, the referenced point and component
must be in the analysis set (a-set) for use in normalization.

2107.1 *** USER FATAL MESSAGE 2107 (USRMSG)

Main Index
 234 MSC Nastran Error Messeges
Errors 2000 - 2999

EIG- ENTRY FROM SET %1 REFERENCES DEPENDENT COORDINATE OF GRID POINT %2

IN MODULE 0

User information: When the point option is used on an EIGR entry, the referenced point and component
must be in the analysis set (a-set) for use in normalization.

2108.0 *** USER WARNING MESSAGE 2108 (USRMSG)

SPCD ON A POINT NOT IN S SET. GRID %1 COMP. %2

User action: SPECIFY A CORRESPONDING SPC FOR THE ABOVE SPCD ENTRY OR THE DOF
WILL BE IGNORED FOR ENFORCED MOTION

2108.1 *** USER WARNING MESSAGE 2108 (USRMSG)

MPCD ON A POINT NOT IN M SET. GRID %1 COMP. %2

2109.0 *** USER FATAL MESSAGE 2109 (USRMSG)

NO GRID, SCALAR, OR EXTRA POINTS DEFINED.

User information: Dynamics problems must have at least one grid, scalar, or extra point.

2111.0 *** USER WARNING MESSAGE 2111 (USRMSG)

BAR %1 COUPLED BENDING INERTIA SET TO 0.0 IN DIFFERENTIAL STIFFNESS.

2112.0 *** SYSTEM FATAL MESSAGE 2112 (USRMSG)

ATTEMPT TO USE TABLE PROCESSING FOR MATERIAL %1 WHEN NO TABLE SUPPLIED.

System information: This error occurs in nonlinear analysis when, for a given value of strain, a table lookup
was requested but the user did not supply a table. Make sure that tables referenced by MATS1 or CREEP
entries are supplied.

2113.0 *** USER FATAL MESSAGE 2113 (USRMSG)

Main Index
 MSC Nastran Error Messeges 235
Errors 2000 - 2999

ELEMENT %1 REFERENCED MATID %2 WHICH CANNOT BE USED TO OBTAIN

REQUIRED PROPERTIES.

User information: A search procedure in MAT allows any possible MATi entry to be referenced under any
INFLAG. However, only certain material formats can be used to construct the required output in /
MATOUT/.
Make certain the element can reference the material entry type.

2113.1 *** USER FATAL MESSAGE 2113 (TA1MCK)

%1 PROPERTY ID %2 REFERENCES MATID %3 %4 WHICH DOES NOT EXIST.

User information: No material property Bulk Data entry (e.g. MAT1, MAT2) could be found for the ref-
erenced material table identification number. The user should check the specified element property Bulk
Data entry (e.g., PBAR, PROD) for reference to the identification number of the missing material Bulk
Data entry. Either replace the ID of the missing material entry on the property entry with one that exists, or
add a new material Bulk Data entry with the missing identification number.

2114.0 *** USER WARNING MESSAGE 2114 (USRMSG)

THE VALUE OF PARAMETER F12 DOES NOT SATISFY THE STABILITY CRITERION FOR
ELEMENT %1 PLY %2

User information: Failure theory calculations for the noted element/ply were not calculated. The value of
the parameter F12 did not satisfy the following equations for Tsai-Wu failure theory:
(1/(Xt * Xc)) * (1/(Yt * Yc)) - F12 ** 2 > 0
Change the value of the parameter F12.

2115.0 *** USER FATAL MESSAGE 2115 (USRMSG)

TABLE %1 (TYPE%2) ILLEGAL WITH STRESS-DEPENDENT MATERIAL.

User information: Only TABLES1 entries may be used to define stress-strain curves for use in piecewise
linear analysis.

2116.0 *** USER FATAL MESSAGE 2116 (USRMSG)

ALL TABLES MUST BE SUPPLIED FOR CREEP ENTRY %1.

User information: When the table option is selected for CREEP analysis, all possible table fields must be
supplied.

Main Index
 236 MSC Nastran Error Messeges
Errors 2000 - 2999

2117.0 *** SYSTEM FATAL MESSAGE 2117 (USRMSG)

LOGIC ERROR, ELEMENT %1 MATERIAL %2 REQUIRES A MATS1 OR CREEP ENTRY
WHICH WAS NOT LOADED.

System information: Normally, module TA1 determines which types of analysis are possible for an element
based upon which material is referenced. The processing routine has requested processing other than that
for which the element was flagged. Review references to MATS1 or CREEP entries by MATi entries.

2117.1 *** SYSTEM FATAL MESSAGE 2117 (USRMSG)

LOGIC ERROR, %1 PROPERTY ID %2 REFERENCES MATID %3 %4 THAT REQUIRES A
MATS1 OR CREEP ENTRY WHICH WAS NOT LOADED.

System information: Normally, module TA1 determines which types of analysis are possible for an element
based upon which material is referenced. The processing routine has requested processing other than that
for which the element was flagged. Review references to MATS1 or CREEP entries by MATi entries.

2117.2 *** USER FATAL MESSAGE 2117 (TA1M)

SOL 400 DOES NOT ALLOW BLANK MID3 IN PSHELL ENTRY %1 WHEN ITS CORRE-
SPONDING SECONDARY PROPERTY ENTRY PSHLN1 HAS DIFFERENT MID1 AND MID2
WITH BEH4=DEFAULT OR DCT.

User action:
1. IF MID3 IS NOT SPECIFIED ON THE PSHELL, BEH4=DCTN with INT4=LDK SHOULD
BE SPECIFIED; OR
2. PROVIDE MID3 ID in PSHELL ENTRY %1

2120.0 *** USER FATAL MESSAGE 2120,

MODULE VEC - BOTH SUBSET BITS ARE NON-ZERO. I = %1

User information: Possible error in partitioning set definition.

2121.0 *** USER FATAL MESSAGE 2121,

MODULE VEC - BOTH SUBSET BITS ARE ZERO. I = %1

User information: Possible error in partitioning set definition.

Main Index
 MSC Nastran Error Messeges 237
Errors 2000 - 2999

2122.0 *** USER FATAL MESSAGE 2122,

MODULE VEC - SET X BIT IS ZERO BUT SUBSET X0 BIT IS NOT. I = %1

User information: Possible error in partitioning set definition.

2123.0 *** USER FATAL MESSAGE 2123,

MODULE VEC - SET X BIT IS ZERO BUT SUBSET X1 BIT IS NOT. I = %1

User information: Possible error in partitioning set definition.

2124.0 *** USER WARNING MESSAGE 2124,

MODULE VEC - NR=0, OUTPUT WILL BE PURGED.

User information: Requested partitioning vector is null.

2125.0 *** USER WARNING MESSAGE 2125,

MODULE VEC - NZ=0, ONE OR MORE COLUMNS OF OUTPUT MATRIX WILL BE NULL.

User information: Requested partitioning vector is full.

2126.0 *** USER FATAL MESSAGE 2126 (USRMSG)

UNDEFINED MATERIAL FOR ELEMENT %1

2131.0 *** USER FATAL MESSAGE 2131 (USRMSG)

NON-SCALAR ELEMENT %1 REFERENCES A SCALAR POINT.

User information: An element which must be attached to a geometric grid point has been attached to a sca-
lar point. No geometry data can be inferred.

2132.0 *** USER FATAL MESSAGE 2132 (USRMSG)

NON-ZERO SINGLE POINT CONSTRAINT VALUE SPECIFIED BUT DATA BLOCK YS IS
PURGED.

2133.0 *** USER FATAL MESSAGE 2133 (USRMSG)

Main Index
 238 MSC Nastran Error Messeges
Errors 2000 - 2999

INITIAL CONDITION IN SET %1 SPECIFIED FOR POINT NOT IN ANALYSIS SET.

User information: Initial conditions can only be specified for analysis set points. Therefore the point/com-
ponent mentioned on TIC entries must belong to the d- or h- sets.

2133.1 *** USER FATAL MESSAGE 2133 (DPD4)

%4 Bulk Data entry with SID=%1 REFERENCES GRID %2 COMPONENT %3 WHICH IS NOT IN
the D-SET.

User Information: Initial conditions can only be applied to points in the dynamic analysis set (d-set).

User action: Ensure that these components are not being left out of the d-set because they are:
1. Defined as dependent degrees-of-freedom on multipoint constraints or rigid elements and this
cannot be fixed by placing them in the U5 set with PARAM,AUTOMSET,YES.
2. Cnstrained by SPC, SPC1, AUTOSPC, etc.
3. Omitted by OMITi or unspecified on existing ASETi, etc.

2134.0 *** USER FATAL MESSAGE 2134 (USRMSG)

LOAD OR DEFORM SET %1 DEFINED FOR BOTH GRAVITY AND NON-GRAVITY LOADS.

User information: The same load set identification number cannot appear on both a GRAV entry and
another loading entry such as FORCE or MOMENT.
To apply both a gravity load and a concentrated load simultaneously, the LOAD entry must be used.

2134.1 *** USER FATAL MESSAGE 2134 (GP1D)

DAREA BULK DATA ENTRY %1 IS THE SAME AS A LOAD OR GRAV BULK DATA ENTRY

2135.0 *** USER FATAL MESSAGE 2135 (USRMSG)

DLOAD CARD %1 HAS A DUPLICATE SET ID FOR SET ID %2.

User information: The Li Set IDs on a DLOAD entry are not unique. See the DLOAD Bulk Data descrip-
tion.

2136.0 *** USER FATAL MESSAGE 2136---

Main Index
 MSC Nastran Error Messeges 239
Errors 2000 - 2999

DUPLICATE %1 SET ID NUMBER =%2 HAS BEEN ENCOUNTERED FOR %3 SET =%4

User information: Dynamic loads may not be combined by giving multiple data entries with the same ID.
Use unique IDs.

2136.1 *** USER FATAL MESSAGE 2136 (DPD2)

%1 SET ID %2 HAS BEEN DUPLICATED ON A %3 CARD.

2137.0 *** USER FATAL MESSAGE 2137 (USRMSG)

PROGRAM RESTRICTION FOR MODULE %1. ONLY 300 LOAD SET ID'S ALLOWED. DATA
CONTAINS %2 LOAD SET ID'S.

2138.0 *** USER FATAL MESSAGE 2138 (USRMSG)

ELEMENT IDENTIFICATION NUMBER %1 IS TOO LARGE.

2139.0 *** USER WARNING MESSAGE 2139 (USRMSG)

ELEMENT %1 IN DEFORM SET %2 IS UNDEFINED.

User information: A selected element deformation set includes an element twice, includes a non-existent
element, or includes a non includes a non-one-dimensional element.

2140.0 *** USER FATAL MESSAGE 2140 (USRMSG)

GRID POINT OR SCALAR POINT ID %1 IS TOO LARGE.

User information: This is a program restriction on the size of integer numbers. An entry defining a grid
point or scalar point has a number larger than the maximum of 2,000,000.

2141.0 *** USER INFORMATION MESSAGE 2141,

HOUSEHOLDER TIME ESTIMATE IS %1 SECONDS.
PROBLEM SIZE IS %2 .

2141.1 *** USER INFORMATION MESSAGE 2141,

Main Index
 240 MSC Nastran Error Messeges
Errors 2000 - 2999

GIVENS TIME ESTIMATE IS %1 SECONDS.

PROBLEM SIZE IS %2, SPILL WILL OCCUR FOR THIS CORE AT A PROBLEM SIZE OF %3 .

User information: The time estimate includes the time of the tridiagonalization and eigenvalue calculation
when the GIV or HOU methods are used. If ND is given on the EIGR entry, it also includes the time of
the eigenvector generation. If F1 and F2 are used instead, the eigenvector times

2142.0 *** USER FATAL MESSAGE 2142,

INSUFFICIENT CORE FOR MODULE VEC. AVAILABLE CORE = %1 WORDS.
ADDITIONAL CORE NEEDED = %2 WORDS.

User information: Additional main memory is needed to execute module VEC.

2143.0 *** USER FATAL MESSAGE 2143,

MODULE VEC UNABLE TO IDENTIFY SET OR SUBSET DESCRIPTOR %1

User information: Illegal set name for partitioning vector definition.

2145.0 *** USER FATAL MESSAGE 2145,

%1 FATAL MESSAGES HAVE BEEN GENERATED IN SUBROUTINE VEC.
ONLY THE FIRST %2 HAVE BEEN PRINTED.

User information: Only a limited number of error messages are printed.

2146.0 *** USER FATAL MESSAGE 2146,

BOTH OF THE SECOND AND THIRD VEC PARAMETERS REQUEST COMPLEMENT.

User information: Illegal definition of partitioning vector.

2150.0 *** USER FATAL MESSAGE 2150,

ILLEGAL VALUE FOR FOURTH PARAMETER = %1

2154.0 *** USER WARNING MESSAGE 2154,

ZERO AREA OR ILLEGAL CONNECTION FOR %1 ELEMENT NUMBER %2

User information: Possible error on connection entry or property entry.

Main Index
 MSC Nastran Error Messeges 241
Errors 2000 - 2999

2154.1 *** USER WARNING MESSAGE 2154,

ZERO AREA OR ILLEGAL CONNECTION FOR ELEMENT NUMBER %1

User information: Possible error on connection entry or property entry.

2155.0 *** USER WARNING MESSAGE 2155,

MAT4 AND MAT5 MATERIAL DATA CARDS HAVE SAME ID =%1
MAT4 DATA WILL BE SUPPLIED WHEN CALLED FOR THIS ID.

User information: The same identification number has been used for an isotropic and an anisotropic
material.

2157.0 *** USER FATAL MESSAGE 2157,

MATERIAL ID =%1 FOR ELEMENT ID = %2
DOES NOT APPEAR ON ANY RADM RADIATION MATERIAL DATA CARD

User information: Material properties required for thermal matrix generation are not present in the Bulk
Data.

2157.1 *** USER FATAL MESSAGE 2157,

MATERIAL ID =%1 FOR ELEMENT ID = %2
DOES NOT APPEAR ON ANY MAT4 OR MAT5 MATERIAL DATA CARD.

User information: Material properties required for thermal matrix generation are not present in the Bulk
Data.

2157.2 *** USER FATAL MESSAGE 2157,

Material ID = %1 referenced by %2 property ID = %3 does not appear on any %4 material data entry.

User information: Required material property entry is not present in the Bulk Data.

2157.3 *** USER FATAL MESSAGE 2157,

MATERIAL ENTRY WITH ID = %1 REFERENCED BY %2 PROPERTY ID = %3 IS NOT
SUPPORTED.

User information: ONLY %4 is valid material when ANAL = %5.

Main Index
 242 MSC Nastran Error Messeges
Errors 2000 - 2999

2158.0 *** USER FATAL MESSAGE 2158 (IFP6NLM):

%1 ID = %2 has a positive value in the DIRECT field but the sum of the ply thicknesses is %3

User information: For positive values of DIRECT, the sum of ply thicknesses must be 1.0

2160.0 *** USER FATAL MESSAGE 2160 (ESLTD)

BAD GEOMETRY OR ZERO COEFFICIENT FOR SLOT ELEMENT NUMBER %1

User information: Possible error on GRID entry or connection entry.

2161.0 *** USER FATAL MESSAGE 2161,

PARTITION FILE %1 IS OF SIZE %2 ROWS BY %3 COLS.
PARTITIONING VECTORS INDICATE THAT THIS PARTITION SHOULD BE OF SIZE %4
ROWS BY %5 COLUMNS FOR A SUCCESSFUL MERGE.

User information: Check RP and CP sizes for MERGE.

2162.0 *** USER WARNING MESSAGE 2162,

THE FORM PARAMETER AS GIVEN TO THE MERGE MODULE IS INCONSISTENT WITH
THE SIZE OF THE MERGED MATRIX, HOWEVER IT HAS BEEN USED. FORM = %1 SIZE =
%2 ROWS BY %3 COLUMNS.

User information: Use square forms for square matrices, etc, or use FORM=0.

2163.0 *** USER WARNING MESSAGE 2163,

REQUESTED VALUE OF %1 %2 %3USED BY %4. LOGICAL CHOICE IS %5

User information: The type of the output matrix is not consistent with the precision of the computer.

2166.0 *** USER FATAL MESSAGE 2166,

Main Index
 MSC Nastran Error Messeges 243
Errors 2000 - 2999

MATRIX TO BE PARTITIONED IS OF SIZE %1 ROWS BY %2 COLUMNS.

ROW PARTITION SIZE IS %3 COLUMN PARTITION SIZE IS %4 (INCOMPATIBLE).

User information: The RP or CP matrices do not match the incoming matrix size. Check the DMAP and
DIAG 8 output. Note that in versions prior to V65C, the size of the partitioning vector did not have to be
compatible with the matrix being partitioned. This was changed starting with V65C, when a warning mes-
sage was issued. Starting with V67.5, this was changed to a fatal message.

2168.0 *** USER WARNING MESSAGE 2168,

THE FORM PARAMETER AS GIVEN TO THE PARTITIONING MODULE FOR SUB-PARTI-
TION %1 IS INCONSISTENT WITH ITS SIZE. FORM = %2 SIZE = %3 ROWS BY %4 COL-
UMNS.

User information: Either use FORM=0, or label square results square, etc.

2170.0 *** USER FATAL MESSAGE 2170,

BOTH THE ROW AND COLUMN PARTITIONING VECTORS ARE PURGED AND ONLY ONE
MAY BE.

User information: Check your DMAP PARTN or MERGE for loss of both RP and CP.

2171.0 *** USER WARNING MESSAGE 2171,

SYM FLAG INDICATES TO THE PARTN OR MERGE MODULE THAT A SYMMETRIC
MATRIX IS TO BE OUTPUT. THE PARTITIONING VECTORS%1 HOWEVER DO NOT CON-
TAIN AN IDENTICAL NUMBER OF ZEROS AND NON-ZEROS.

User information: Do not specify both RP and CP if a symmetric partition is desired.

2172.0 *** USER WARNING MESSAGE 2172,

ROW AND COLUMN PARTITIONING VECTORS DO NOT HAVE IDENTICAL ORDERING
OF ZERO AND NON-ZERO ELEMENTS, AND SYM FLAG INDICATES THAT A SYMMETRIC
PARTITION OR MERGE IS TO BE PERFORMED.

User information: Do not specify both RP and CP if a symmetric partition is desired.

2173.0 *** USER WARNING MESSAGE 2173,

Main Index
 244 MSC Nastran Error Messeges
Errors 2000 - 2999

PARTITIONING VECTOR FILE%1 CONTAINS %2 COLUMNS.

THE FIRST COLUMN WILL BE USED, NOT THE REQUESTED COLUMN %3

User information: The COLNO parameter has been set longer than the number of columns in RP or CP
in the PARTN or MERGE modules.

2174.0 *** USER WARNING MESSAGE 2174,

PARTITIONING VECTOR ON FILE %1 IS NOT REAL-SINGLE OR REAL-DOUBLE PRECI-
SION.

User information: Partitioning vectors may not be complex for the PARTN or MERGE modules.

2184.0 *** SYSTEM WARNING MESSAGE 2184,

STRESS OR FORCE REQUESTS FOR ELEMENT TYPE =%1
WILL NOT BE HONORED AS THIS ELEMENT IS UNDEFINED TO SDR2.

2187.0 *** USER FATAL MESSAGE 2187 (OUTPX2)

INSUFFICIENT WORKING CORE TO HOLD FORTRAN LOGICAL RECORD IN MODULE
%1.
LENGTH OF WORKING CORE = %2, LENGTH OF FORTRAN LOGICAL RECORD = %3.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

2187.1 *** USER FATAL MESSAGE 2187 (OUTPN2)

INSUFFICIENT WORKING CORE TO HOLD FORTRAN LOGICAL RECORD IN MODULE
%1.
LENGTH OF WORKING CORE = %2, LENGTH OF FORTRAN LOGICAL RECORD = %3.

2187.2 *** USER FATAL MESSAGE 2187

INSUFFICIENT WORKING CORE TO HOLD FORTRAN LOGICAL RECORD.
LENGTH OF WORKING CORE = %1, LENGTH OF FORTRAN LOGICAL RECORD = %2.

2187.3 *** USER FATAL MESSAGE 2187

INSUFFICIENT WORKING CORE TO HOLD FORTRAN LOGICAL RECORD.
LENGTH OF WORKING CORE = %1, LENGTH OF FORTRAN LOGICAL RECORD = %2.

User action: INCREASE WORKING CORE BY %3 WORDS

Main Index
 MSC Nastran Error Messeges 245
Errors 2000 - 2999

2190.0 *** SYSTEM FATAL MESSAGE 2190 (OUTPX2)

ILLEGAL VALUE FOR KEY =%1.
FORTRAN UNIT = %2 (GENERATED IN %3 FORMAT)

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

2190.1 *** SYSTEM FATAL MESSAGE 2190 (OUTPX2)

ILLEGAL VALUE FOR KEY =%1, EXPECTED VALUE = %2.
FORTRAN UNIT = %3 (GENERATED IN %4 FORMAT)

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

2190.2 *** SYSTEM FATAL MESSAGE 2190

ILLEGAL VALUE FOR KEY =%1.
FORTRAN UNIT = %2 (GENERATED IN %3 FORMAT)

2190.3 *** SYSTEM FATAL MESSAGE 2190

ILLEGAL VALUE FOR KEY =%1, EXPECTED VALUE = %2.
FORTRAN UNIT = %3 (GENERATED IN %4 FORMAT)

2190.7 *** SYSTEM FATAL MESSAGE 2190 (INPTN2)

ILLEGAL VALUE FOR KEY = %1.

2190.12 *** SYSTEM FATAL MESSAGE 2190

ILLEGAL VALUE FOR KEY =%1.
PROCESSING DATA BLOCK %2 ON FORTRAN UNIT %3 (GENERATED IN %4 FORMAT) IN
%5 FORMAT

2190.13 *** SYSTEM FATAL MESSAGE 2190

ILLEGAL VALUE FOR KEY =%1, EXPECTED VALUE = %2.
PROCESSING DATA BLOCK %3 ON FORTRAN UNIT %4 (GENERATED IN %5 FORMAT) IN
%6 FORMAT

2190.14 *** SYSTEM FATAL MESSAGE 2190

Main Index
 246 MSC Nastran Error Messeges
Errors 2000 - 2999

ILLEGAL VALUE FOR KEY =%1.

PROCESSING DATA BLOCK %2 ON FORTRAN UNIT %3 (GENERATED IN %4 FORMAT)
USING NDDL DESCRIPTION FOR %5

2190.15 *** SYSTEM FATAL MESSAGE 2190

ILLEGAL VALUE FOR KEY =%1, EXPECTED VALUE = %2.
PROCESSING DATA BLOCK %3 ON FORTRAN UNIT %4 (GENERATED IN %5 FORMAT)
USING NDDL DESCRIPTION FOR %6

2192.0 *** USER FATAL MESSAGE 2192 (USRMSG)

UNDEFINED GRID POINT %1 IN RIGID ELEMENT %2

2193.0 *** USER FATAL MESSAGE 2193 (USRMSG)

A REDUNDANT SET OF RIGID BODY MODES WAS SPECIFIED FOR THE GENERAL ELE-
MENT.

User information: Only a non-redundant list of rigid body modes is allowed to appear in the ud set when
the S matrix is to be internally calculated in subroutine TA1CA.

2194.0 *** USER FATAL MESSAGE 2194 (USRMSG)

A MATRIX D IS SINGULAR IN SUBROUTINE TA1CA.

User information: While attempting to calculate the [S] matrix for a general element in TA1CA, it was dis-
covered that the matrix Dd which relates ub to ud was singular and could not be inverted.

2195.0 *** USER FATAL MESSAGE 2195 (TIMTST)

ILLEGAL VALUE FOR P4 =%1

2197.0 *** SYSTEM FATAL MESSAGE 2197,

ABORT CALLED DURING TEST TEST OF %1

2198.0 *** SYTEM FATAL MESSAGE 2198 (USRMSG)

INPUT DATA BLOCK %1 HAS BEEN PURGED.

2199.0 *** SYTEM FATAL MESSAGE 2199 (USRMSG)

SUMMARY, ONE OR MORE OF THE ABOVE FATAL ERRORS WAS ENCOUNTERED IN SUB-
ROUTINE %1.

Main Index
 MSC Nastran Error Messeges 247
Errors 2000 - 2999

2200.0 *** USER FATAL MESSAGE 2200,

INCONSISTENT RIGID BODY SYSTEM.

User information: The rigid-body mass matrix is not positive definite. Possible causes are unconstrained
mechanisms or input of negative mass terms. A diagnostic method is to remove all SUPORT entries and
inspect the resulting eigenvectors for implausible behavior.

2201.0 *** USER FATAL MESSAGE 2201 (IFPLC)

LOAD BULK DATA ENTRY ID = %1 CONTAINS AN ILLEGAL REFERENCE TO ITSELF.

2202.0 *** USER INFORMATION MESSAGE 2202 (IFPLC)

LOAD BULK DATA ENTRY ID = %1 CONTAINS SID REFERENCES TO OTHER LOAD BULK
DATA ENTRIES.
THESE REFERENCES HAVE BEEN RESOLVED BY REPLACING THEM WITH THE Si,Li LISTS
OF THE REFERENCED LOAD ENTRIES.

2202.1 *** USER INFORMATION MESSAGE 2202 (IFPLC)

THERE ARE AN ADDITIONAL %1 LOAD BULK DATA ENTRY SID REFERENCES TO OTHER
LOAD BULK DATA ENTRIES.
THESE REFERENCES HAVE ALSO BEEN RESOLVED BY REPLACING THEM WITH THE Si,Li
LISTS OF THE REFERENCED LOAD ENTRIES
.
2230.0 *** USER FATAL MESSAGE 2230 (PFAERO)
DETECTED CHANGE IN USER INPUT FOR WKK
THIS IS NOT SUPPORTED ON RESTART

User action: PERFORM A COLDSTART WITH DESIRED WKK

2231.0 *** USER FATAL MESSAGE 2231 (PFAERO)

DETECTED CHANGE IN USER INPUT FOR WTFACT
THIS IS NOT SUPPORTED ON RESTART

User action: PERFORM A COLDSTART WITH DESIRED WTFACT

2251.0 *** USER WARNING MESSAGE 2251 (IFS1P)

Main Index
 248 MSC Nastran Error Messeges
Errors 2000 - 2999

ONE OR MORE MAT1 ENTRIES HAVE UNREASONABLE OR INCONSISTENT VALUES OF

E,G OR NU. ID OF FIRST ONE = %1

User information: Potentially bad elastic constants have been defined on one or more MAT1 entries.
Checks are made for (a) any of E << 0.0, G << 0.0, (unless two of the three data fields are blank). Verify
that the values defined are meaningful for the designated application.

2251.1 *** USER WARNING MESSAGE 2251 (IFS1P)

THE NUMBER OF MAT1 ENTRIES HAVING UNREASONABLE OR INCONSISTENT VALUES
FOR E,G AND/OR NU IS %1 ID OF LAST ONE = %2

User information: See Message 2251.0. Check all MAT1 entries in the range indicated for the ones with
potentially bad elastic constants. These values should be verified for application suitability.

2251.2 *** USER FATAL MESSAGE 2251 (IFS1P)

MAT1 ID = %1 HAS INVALID VALUE IN %2 FIELD.

User information: Set NASTRAN SYSTEM(430)=1 to proceed with a warning.

2257.0 ***USER WARNING MESSAGE 2257

SET %1 IS EMPTY.

User information: While processing the SET1 or SET2 entry referenced on the SPLINEi entry, no
included grid points were found. If SET1 was used, either no points were included or they were all scalar
points. If SET2 was used, the volume of space referenced did not include any structural grid points. This
may occur if a tapered element is extended too far. The spline is omitted from the problem and processing
continues.

2258.0 ***USER FATAL MESSAGE 2258

SET %1 REFERENCED ON SPLINE CARD %2 NOT FOUND.

User information: The necessary SET1 or SET2 entry was not found. Include the proper SET entry.

2258.1 *** USER FATAL MESSAGE 2258 (APD0)

SET ENTRY ID = %1 THAT IS REFERENCED ON SPLINE ENTRY ID = %2 WAS NOT FOUND.

2258.2 *** USER FATAL MESSAGE 2258 (GISPL)

Main Index
 MSC Nastran Error Messeges 249
Errors 2000 - 2999

%1 %2 REFERENCED ON SPLINE CARD %3 NOT FOUND.

2258.3 *** USER FATAL MESSAGE 2258 (ILMPGPF)

SET1 ENTRY ID = %1 THAT IS REFERENCED ON MONPNT3 ENTRY ID = %2 WAS NOT
FOUND.

User information: THIS MONPNT3 IS IGNORED.

2258.4 *** USER FATAL MESSAGE 2258 (FBODYFLT)

THE SET1 ENTRY ID = %1 REFERENCED ON THE FBODYSB ENTRY NAME="%2" WAS NOT
FOUND.

2258.5 ***USER FATAL MESSAGE 2258 (DTOG2F)

SET1 ENTRY ID = %1 THAT IS REFERENCED ON BEADVAR ENTRY ID = %2 WAS NOT
FOUND.

User action: Provide the necessary SET1 entry or check the IDs on the SET1 and BEADVAR entries.

2258.6 ***USER FATAL MESSAGE 2258 (DTOG2G)

THERE ARE NO FREE GRIDS IN TOPOGRAPHY OPTIMIZATION DEFINED BY BEADVAR
ENTRIES.

User action: CHECK THE INPUT TO ENSURE THAT THE JOB HAS FREE DESIGNED GRIDS
(GRIDS CONNECTING TO NON-DESIGNED ELEMENTS ARE FIXED IN OPTIMIZATION)

2259.0 ***SYSTEM FATAL MESSAGE 2259

POINT ASSIGNED TO BOX %1 FOR CAERO1 %2 NOT IN ECTA.

System information: No internal k point could be found for external box. If box number is correct, module
APD is in error; if box number is incorrect, module GI is in error.

2260.0 *** USER FATAL MESSAGE 2260

SINGULAR MATRIX DEVELOPED WHILE PROCESSING SPLINE%1

User information: Matrix developed by SSPLIN or LSPLIN (depending on type of spline) could not be
inverted; possibly for the surface spline all points lie in a straight line, or not enough points are included.

Main Index
 250 MSC Nastran Error Messeges
Errors 2000 - 2999

2261.0 *** USER FATAL MESSAGE 2261 (L1SPLD)

PLANE OF LINEAR SPLINE %1 PERPENDICULAR TO PLANE OF AERO ELEMENT %2

User information: Y-axis of linear spline was perpendicular to connected element and could not be
projected onto element.

2262.0 *** USER FATAL MESSAGE 2262 (GIPUSG)

SPLINE %1 REFERENCES AN AERO BOX MULTIPLE TIMES OR AN AERO BOX REFER-
ENCED ON ANOTHER SPLINE.

User information: The same aero box is splined more than once. Splines may be connected to the same
structural grid point but not the same aerodynamic grid point. This type of error checking will stop with
one error, so check this spline and subsequent splines (sorted) for overlaps before resubmitting.

2263.0 *** USER FATAL MESSAGE 2263

INSUFFICIENT CORE TO PROCESS SPLINE%1

User information: Depending on type of spline and input options, subroutine SSPLIN, or LSPLIN would
not have had enough core for this spline. Either allow more core or break this spline into smaller splines.

2264.0 *** SYSTEM FATAL MESSAGE 2264,

NUMBER OF ROWS COMPUTED (%1) WAS GREATER THAN SIZE REQUESTED FOR
OUTPUT MATRIX (%2).

System information: Module ADD determines size of output matrices (j set size). Sum of number of rows
added by different method total more than maximum allowed.

2264.1 *** SYSTEM FATAL MESSAGE 2264,

INPUT OF M=1.0 IS NOT ALLOWED IN AN AERODYNAMIC ANALYSIS USING CAERO1
TYPE AERODYNAMICS

User information: MACH=1.0 RESULTS IN SINGULARITIES IN THE AERODYNAMIC

ANALYSIS AND IS NOT SUPPORTED

2265.0 *** USER FATAL MESSAGE 2265 (dopr3i)

Main Index
 MSC Nastran Error Messeges 251
Errors 2000 - 2999

SUBCASE %1 PLACES A CONSTRAINT ON DRESP1 ID %2 WITH RTYPE %3 AND

THIS RESPONSE REFERENCES RANDPS ENTRY %4 WHICH INVOKES SUBCASE %5.

User information: CONSTRAINTS PLACED ON RMS/PSD RESPONSES MUST BE PLACED IN

THE FIRST SUBCASE REFERENCED ON THE ASSOCIATED RANDPS.

User avoidance: PLACE THE DESSUB REQUEST IN, AND ONLY IN, THE FIRST
SUBCASE REFERENCED ON THE ASSOCIATED RANDPS ENTRY.

2266.0 *** USER FATAL MESSAGE 2266 (FA1)

ONE OR MORE OF THE FOLLOWING FLFACT SETS WERE NOT FOUND - %1

User information: One or more of the FLFACT IDs on the FLUTTER entry could not be found.
Include all sets mentioned.

2266.1 *** USER FATAL MESSAGE 2266 (DOPR3I)

FLUTTER ENTRY ID = %1 REFERENCES A FLFACT BULK DATA ENTRY ID = %2 WHICH
CANNOT BE FOUND.

2267.0 *** USER FATAL MESSAGE 2267 (FA1)

INTERPOLATION METHOD %1 UNKNOWN.

User information: Matrix interpolation method on FLUTTER entry is not implemented.

2268.0 *** USER FATAL MESSAGE 2268 (FA1)

FMETHOD SET %1 NOT FOUND.

User information: FLUTTER entry for FMETHOD = %1 in case control could not be found.

2269.0 *** USER FATAL MESSAGE 2269 (FA1)

FLUTTER METHOD %1 NOT IMPLEMENTED.

2269.1 *** USER WARNING MESSAGE 2269 (FA1)

Main Index
 252 MSC Nastran Error Messeges
Errors 2000 - 2999

THE KE FLUTTER METHOD DOES NOT SUPPORT A BHH MATRIX AND THESE DATA ARE
IGNORED.

User action: DELETE THE INPUT DATA WHICH GENERATES THE BHH MATRIX OR USE AN
ALTERNATIVE FLUTTER METHOD (PK OR K ).

2269.2 *** USER FATAL MESSAGE 2269 (FA1)

A NEGATIVE K VALUE HAS BEEN ENTERED ON AN FLFACT ENTRY. THIS IS NOT
PERMITTED.

User action: ENSURE THAT ALL K VALUES ON THE FLFACT ENTRY ARE POSITIVE.

2270.0 ***USER FATAL MESSAGE 2270

LINEAR INTERPOLATION WITHOUT ENOUGH IND. MACH NUMBERS EQUAL TO DEP.
MACH %1

User information: Linear interpolation is for points with the same Mach number, and fewer than two more
found from QHHL list which matched the requested Mach on an FLFACT entry.

2271.0 *** USER FATAL MESSAGE 2271,

INTERPOLATION MATRIX IS SINGULAR

User information: Possibly for the surface spline, all the Mach numbers were the same, or for either
method, not enough points were included. The range of Mach numbers and reduced frequencies must be
larger on the MKAEROi entry than on the FLFACT entry.

2272.0 *** USER FATAL MESSAGE 2272 (MKCKBL)

SPLINE ID= %1 BULK DATA ENTRY IS REFERENCED BY BLENDING ENTRY ID= %2 AND
BLENDING ENTRY ID= %3

User information: A SPLINE ENTRY CAN BE REFERENCED BY ONLY ONE BLENDING ENTRY

User action: CHECK SPBLND1 AND SPBLND2 ENTRIES

2273.0 *** USER WARNING MESSAGE 2273 (APD0)

%1 BULK DATA ENTRIES ARE IGNORED IF AN EXTERNAL AERODYNAMIC MESH IS
DEFINED

Main Index
 MSC Nastran Error Messeges 253
Errors 2000 - 2999

2274.0 *** USER FATAL MESSAGE 2274 (LRSPLD)

STRUCTURAL GRID POINTS OF SPLINE %1 ARE NOT ON THE SPLINE AXIS.

User information: THIS IS REQUIRED IF METHOD=RIS IS SELECTED.

User action: ASSIGN STRUCTURAL GRID POINTS ON THE SPLINE AXIS. USE RBE3 TO CON-
NECT TO STRUCTURAL GRID POINTS NOT ON THE SPLINE AXIS.

2275.0 *** USER FATAL MESSAGE 2275 (RISPLD)

SPLINE ID = %1 USES METHOD=RIS.

User information: THE REFERENCED COMPONENT ID = %2 MUST BE DOUBLET LATTICE

OR EXTERNAL AERODYNAMICS.

2276.0 *** USER FATAL MESSAGE 2276 (GIB2A)

SPLINES INVOLVED IN BLENDED SPLINE %1 HAVE A DIFFERENT USAGE

User information: SPLINES TO BE BLENDED MUST HAVE THE SAME USAGE

2277.0 *** USER FATAL MESSAGE 2277 (GIB31D)

ORIENTATION VECTOR ON %1 ENTRY ID = %2 HAS ZERO LENGTH

2278.0 *** USER FATAL MESSAGE 2278 (GIB5AD)

INTERSECTION OF AELIST ID = %1 WITH GRID POINTS IN SPLINE ID = %2 IS EMPTY

User information: THE POINTS CONTROLLING RELAXATION MUST BE PART OF THE

SPLINE REFERENCED IN FIELD 3 OF THE SPRELAX ENTRY

2279.0 *** USER FATAL MESSAGE 2279 (GIB5AD)

THE LIST OF POINTS TO BE RELAXED IS EMPTY FOR RELAXATION OF SPLINE ID = %1
WITH SPLINE ID = %2

User information: THE POINTS IN AELIST ID = %3 DO NOT BELONG TO SPLINE ID = %4

2280.0 *** USER FATAL MESSAGE 2280 (GIB5AD)

Main Index
 254 MSC Nastran Error Messeges
Errors 2000 - 2999

SPLINE ID = %1 TO BE RELAXED WITH SPLINE ID = %2 HAS DIFFERENT USAGE

User information: SPLINES TO BE RELAXED MUST HAVE THE SAME USAGE

2281.0 *** USER FATAL MESSAGE 2281 (MKCKBL)

SPLINE ID = %1 IS NOT UNIQUE

User information: WITH BLENDING AND RELAXATION, SPLINE IDENTIFIERS MUST BE

UNIQUE

2282.0 *** USER FATAL MESSAGE (AMG)

SYMXY = %1 IS INCORRECTLY SPECIFIED FOR THE %2 AERODYNAMIC METHOD

User information: NON-ZERO SYMXY VALUES ARE ONLY SUPPORTED FOR THE DOUBLET
LATTICE AERODYNAMICS METHOD

2286.0 *** USER FATAL MESSAGE 2286. (SSGSLB)

ELEMENT %1 REFERENCED ON PLOAD1 %2 NOT FOUND

User information: An element identification number is referenced on a PLOAD1 entry which does not
exist on either a CBAR or CBEAM Bulk Data entry.

2286.1 *** USER FATAL MESSAGE 2286. (PL1BMD)

THERE IS A MISSING CBEAM3 ELEMENT REFERENCED BY PLOADB3 %1.

User information: A PLOADB3 must have its corresponding CBEAM3 element.

2286.2 *** USER FATAL MESSAGE 2286. (PL1BMD)

CBEAM3 ELEMENT %1, REFERENCED BY PLOADB3 %2, IS MISSING.

User information: A PLOADB3 must have its corresponding CBEAM3 element.

2287.0 *** USER FATAL MESSAGE 2287 (PKFRQD)

Main Index
 MSC Nastran Error Messeges 255
Errors 2000 - 2999

FRQVAR ID %1 REFERENCES MODE NUMBER %2 WHICH HAS A NON-ZERO OFF-DIAGO-

NAL TERM AT %3 %4.

User information: THE FRQVAR ENTRY CAN ONLY BE APPLIED TO GENERALIZED STIFF-
NESS TERMS THAT HAVE NO OFF-DIAGONAL TERMS.

2288.0 *** USER FATAL MESSAGE 2288 (PKFRQD)

FRQVAR ID=%1 REFERENCES MODE NUMBER %2 BUT THE DIMENSION OF THE GENER-
ALIZED STIFFNESS MATRIX IS ONLY %3

User action: ENSURE THAT THE MODE SPECIFIED ON THE FRQVAR ENTRY IS INCLUDED
IN THE GENERALIZED STIFFNESS USED IN THE FLUTTER ANALYSIS

2289.0 *** USER FATAL MESSAGE 2289 (PKFRQD)

FRQVAR ID=%1 REFERENCES MODE NUMBER %2 BUT THIS MODE HAS ALREADY BEEN
PERTURBED FOR THIS SUBCASE

User information: THE MODES CALLED OUT ON FRQVAR ENTRIES WITH THE SAME ID
MUST BE UNIQUE.

2290.0 *** USER FATAL MESSAGE 2290 (PKFRQD)

FRQVAR ID=%1 REFERENCES A MODE LABELED %2 BUT THIS MODE IS NOT INCLUDED
IN THE FLUTTER ANALYSIS FOR THIS SUBCASE

User action: CHECK THE SPELLING OF THE REFERENCE LABEL, INCLUDING BLANKS.

2317.0 *** USER WARNING MESSAGE 2317,

PARAM HAS STORED OUTSIDE DEFINED RANGE OF COMMON BLOCK /SYSTEM/.
INDEX VALUE = %1

2318.0 *** USER FATAL MESSAGE 2318 (APD0)

NO %1 ENTRY FOUND FOR %2 AEROELASTIC ANALYSIS.

User information: AN %3 ENTRY IS REQUIRED FOR %4 AEROELASTIC ANALYSIS.

2319.0 *** USER FATAL MESSAGE 2319 (APD0)

Main Index
 256 MSC Nastran Error Messeges
Errors 2000 - 2999

NO CAERO ENTRIES FOUND.

User information: At least one CAERO MESSAGE entry is required for module APD.

2322.0 *** USER FATAL MESSAGE 2322 (APD0)

NEITHER MKAERO1 OR MKAERO2 ENTRIES FOUND.

User information: Either MKAERO1 or MKAERO2 entries are required.

2323.0 *** USER FATAL MESSAGE 2323 (APD12)

PAERO %1 ENTRY ID = %2 THAT IS REFERENCED BY CAERO %3 ENTRY ID = %4 DOES
NOT EXIST.

2324.0 *** USER FATAL MESSAGE 2324 (MKSPL)

CAERO ENTRY ID = %1 THAT IS REFERENCED ON SPLINE %2 ENTRY ID = %3 DOES NOT
EXIST.

User information: Either a SPLINE1 or a SPLINE2 entry references a CAERO1 entry which is missing.

2324.1 *** USER FATAL MESSAGE 2324.1 (MKSPL)

SPLINE6 %1 IS USED FOR A 3D AERODYNAMIC MESH, BUT VSLIST IS NOT DEFINED.

User action: Define VSLIST.

2325.0 *** USER FATAL MESSAGE 2325 (MKSPLN)

CAERO ENTRY ID = %1 THAT IS REFERENCED ON SET2 ENTRY ID = %2 DOES NOT EXIST.

User information: A SET2 entry points to a CAERO1 which was not included.

2326.0 *** USER FATAL MESSAGE 2326 (APD12)

AEFACT ENTRY ID = %2 THAT IS REFERENCED ON CAERO1 ENTRY ID = %1 DOES NOT
EXIST.

2326.1 *** USER FATAL MESSAGE 2326,

DUPLICATE %1 DIVISIONS FOUND ON AEFACT ID = %2.

2327.0 *** SYSTEM FATAL MESSAGE 2327 (MKSPL)

Main Index
 MSC Nastran Error Messeges 257
Errors 2000 - 2999

MISSMATCH RECORD SIZE IN EDTSPL.PRM AND NDDL DEFINITION FOR %1.

2328.0 *** USER FATAL MESSAGE 2328 (MKSPL)

NO SPLINES ENTRIES HAVE BEEN FOUND.

User information: SPLINE ENTRIES ARE REQUIRED FOR AEROELASTIC ANALYSIS.

THIS WARNING CAN BE IGNORED IF THE JOB CONTAINS SUPERELEMENTS AND ONE
OR MORE OF THE SUPERELEMENTS OR THE RESIDUAL CONTAIN(S) SPLINE ENTRIES.

2329.0 *** USER FATAL MESSAGE 2329 (APD0)

DUPLICATE EXTERNAL MESHING POINT GRID ID = %1 GENERATED.

User information: The external ID's assigned to each generated box must be unique, and different from
any grid or scalar point ID.

2329.1 *** USER FATAL MESSAGE 2329 (APD0)

DUPLICATE EXTERNAL AERO GRID (BOX) ID = %1 GENERATED.

User information: The external ID's assigned to each generated box must be unique, and different from
any grid or scalar point ID.

2329.2 *** USER FATAL MESSAGE 2329 (APD0)

DUPLICATE EXTERNAL INTERFERENCE ELEMENT CENTER POINT ID = %1 GENERATED.

2330.0 *** USER FATAL MESSAGE 2330 (APD0)

USER INFORMATION: SET1 OR SPLINE3 ENTRY NO. %1 REFERENCES EXTERNAL ID NO.
%2 WHICH DOES NOT EXIST.

User information: External ID on SET1 or SPLINE3 entry does not exist as structural grid point.

2330.1 *** USER FATAL MESSAGE 2330 (GIMAPX)

USER INFORMATION: %1 ENTRY NO. %2 REFERENCES EXTERNAL ID NO. %3 WHICH
DOES NOT EXIST.

User information: External ID on SET1, SPLINE3, or AELIST entry does not exist. Note that if the id is
defined on a SPLINE1 or SPLINE2, then the set id will be internally generated.

Main Index
 258 MSC Nastran Error Messeges
Errors 2000 - 2999

2331.0 *** USER FATAL MESSAGE 2331 (MKSPL)

BOXES PICKED ON SPLINE%1 ENTRY ID = %2 HAVE NOT BEEN GENERATED BY CAERO
ENTRY ID = %3.

User information: CAERO ENTRY ID = %4 GENERATES BOXES %5 to %6.

2333.0 *** SYSTEM INFORMATION MESSAGE 2333 (DDRMM)

MODULE DDRMM TERMINATED WITH VARIABLE IERROR = %1

System information:
IERROR CODE CAUSE
----------- -----
2 Frequency list is empty probably due to DMAP error

2334.0 *** USER WARNING MESSAGE 2334. (DDRMM-3)

ILLEGAL MAJOR OR MINOR OFP-ID IDENTIFICATIONS = %1
DETECTED IN DATA BLOCK%2. PROCESSING OF SAID DATA BLOCK DISCONTINUED.

2335.0 *** USER WARNING MESSAGE 2335. (DDRMM1-1)

THE AMOUNT OF DATA IS NOT CONSISTENT FOR EACH EIGENVALUE IN DATA BLOCK
%1 PROCESSING OF THIS DATA BLOCK TERMINATED.

2336.0 *** USER WARNING MESSAGE 2336. (DDRMM1-2)

A CHANGE IN WORD 2 OF THE OFP-ID RECORDS OF DATA BLOCK %1 HAS BEEN
DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED.

2337.0 *** USER WARNING MESSAGE 2337. (DDRMM2-2)

DATA BLOCK%1 CAN NOT BE PROCESSED DUE TO A MEMORY INSUFFICIENCY OF
APPROXIMATELY%2 DECIMAL WORDS.

2338.0 *** USER WARNING MESSAGE 2338. (DDRMM2-3)

DATA BLOCK%1 MAY NOT BE FULLY COMPLETED DUE TO A MEMORY INSUFFICIENCY
OF APPROXIMATELY%2 DECIMAL WORDS.

2339.0 *** USER WARNING MESSAGE 2339. (DDRMM2-1)

Main Index
 MSC Nastran Error Messeges 259
Errors 2000 - 2999

A CHANGE IN WORD 2 OF THE OFP-ID RECORDS OF DATA BLOCK %1 HAS BEEN

DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED.

2340.0 *** USER INFORMATION MESSAGE 2340

MODULE %1 HAS BEEN REQUESTED TO DO UNSYMMETRIC DECOMPOSITION OF A
SYMMETRIC MATRIX.

User information: The matrix to be solved has a matrix trailer that indicates that it is symmetric
("FORM=6"). The DMAP call requests that the unsymmetric decomposition algorithm be used. The
symmetric algorithm is more economical that the unsymmetric algorithm, and unconditionally stable for
positive-definite matrices.
Change the DMAP call to request symmetric decomposition, unless it is known that the unsymmetric
algorithm is required.

2341.0 *** USER INFORMATION MESSAGE 2341

MODULE %1 HAS BEEN FURNISHED A SQUARE MATRIX MARKED UNSYMMETRIC FOR
SYMMETRIC DECOMPOSITION.

User information: The module has been instructed to perform the symmetric decomposition algorithm in
the DMAP call, but the trailer of the input matrix indicates that it is not of Form 6. If the matrix should be
symmetric, a MODTRL module call can be scheduled before the module to convert the matrix trailer to
Form 6. If this message is encountered in a solution sequence,it is a signal that a solution is being requested
for a system (unsymmetric matrices) for which it was not designed. Wrong answers may result if the
solution is forced through with the MODTRL technique.

2341.1 *** USER INFORMATION MESSAGE 2341

ONE OF THE INPUTS (%1) TO THE REAL EIGENVALUE EXTRACTION MODULE (READ) IS
A SQUARE UNSYMMETRIC MATRIX.

Programmer information: The trailer of the matrix indicates that it is not Form=6 and the READ module
is not intended to process unsymmetric matrices.

Programmer action: If the matrix is intended to be symmetric, then the MODTRL module may be used to
convert the matrix trailer to Form 6 but wrong answers may result. Alternatively, the CEAD module may
be used for perform an eigenvalue analysis with unsymmetric matrices.

2342.0 *** SYSTEM WARNING MESSAGE 2342. (GPFDCC)

Main Index
 260 MSC Nastran Error Messeges
Errors 2000 - 2999

UNRECOGNIZED DMAP APPROACH PARAMETER = %1

User information: NO GPFORCE, ESE, EKE OR EDE RESULTS WILL BE PRINTED.

2342.1 *** SYSTEM FATAL MESSAGE 2342 (APCODE)

UNRECOGNIZED DMAP APPROACH PARAMETER = %1

User information: AVAILABLE NAMES ARE %2 %3 %4 %5 %6 %7 %8 %9 %10 %11

2342.2 *** SYSTEM WARNING MESSAGE 2342. (GPFDCC)

UNSUPPORTED DMAP APPROACH PARAMETER = %1

User information: NO GPFORCE, ESE, EKE OR EDE RESULTS WILL BE PRINTED.

2342.3 *** SYSTEM WARNING MESSAGE 2342 (PFCALC)

APPROACH TYPE (%1) IS NOT VALID.

Programmer information: PFCALC MODULE OPERATIONS ARE BEING BYPASSED.

THE VALID APPROACH TYPES ARE "FREQ", "TRAN" AND "CEIG".

User information: NO PARTICIPATION FACTOR OUTPUT WILL BE GENERATED.

2342.4 *** SYSTEM WARNING MESSAGE 2342 (MCFRAC)

APPROACH TYPE (%1) IS NOT VALID.

Programmer information: MCFRACTION MODULE OPERATIONS ARE BEING BYPASSED.

THE VALID APPROACH TYPES ARE "FREQ", "TRAN" AND "CEIG".

User information: NO MODAL CONTRIBUTION FRACTION OUTPUT WILL BE GENERATED.

2342.5 *** SYSTEM FATAL MESSAGE 2342 (APCODE)

UNRECOGNIZED DMAP APPROACH PARAMETER = %1

User information: AVAILABLE NAMES ARE %2

2343.0 *** SYSTEM WARNING MESSAGE 2343. (GPFDR)

DATA BLOCK %1 IS EITHER NOT -EQEXIN- OR POSSIBLY INCORRECT.

Main Index
 MSC Nastran Error Messeges 261
Errors 2000 - 2999

2344.0 *** SYSTEM WARNING MESSAGE 2344. (GPFDR)

GPFDR FINDS A SYMMETRY SEQUENCE LENGTH %1 WHILE ATTEMPTING TO COM-
PUTE GRID POINT FORCES AND ENERGIES.
THERE IS AN INSUFFICIENT NUMBER OF VECTORS AVAILABLE %2.

2345.0 *** SYSTEM WARNING MESSAGE 2345. (GPFDR)

GPFDR FINDS AND IS IGNORING UNDEFINED ECT DATA WITH LOCATE NUMBERS = %1

2346.0 *** SYSTEM WARNING MESSAGE 2346. (GPFDR)

DATA FOR ELEMENT TYPE = %1 IN DATA BLOCK %2
IS NOT IN AGREEMENT WITH THAT WHICH IS EXPECTED.

2347.0 *** SYSTEM WARNING MESSAGE 2347. (GPFDR)

TOO MANY ACTIVE CONNECTING GRID POINTS FOR ELEMENT ID = %1

2348.0 *** USER INFORMATION MESSAGE 2348. (GPFTDL)

THERMAL (TEMPij) AND ELEMENT DEFORMATION (DEFORM) LOADS ARE NOT
EXPLICITLY DISPLAYED IN GRID POINT FORCES AND ELEMENT ENERGIES IN
FREQUENCY AND TRANSIENT RESPONSE ANALYSIS. THEY ARE IMPLICITLY INCLUDED
IN THE RESULTS.

2349.0 *** SYSTEM WARNING MESSAGE 2349. (GPFDR)

FINDS AN ELEMENT ENTRY CONNECTING PIVOT SIL =%1 ON DATA BLOCK%2
TOO LARGE FOR A LOCAL ARRAY. ENTRY IS BEING IGNORED.

2350.0 *** USER INFORMATION MESSAGE 2350. (GPFDCC)

INERTIAL AND DAMPING EFFECTS ARE IGNORED IN THE CALCULATION OF GRID
POINT FORCES.

2351.0 *** USER INFORMATION MESSAGE 2351. (GPFDR)

A FORCE CONTRIBUTION DUE TO ELEMENT TYPE = %1, ON POINT ID =%2
WILL NOT APPEAR IN THE GRID-POINT-FORCE-BALANCE SUMMARY.

2352.0 *** SYSTEM WARNING MESSAGE 2352. (GPFDR)

Main Index
 262 MSC Nastran Error Messeges
Errors 2000 - 2999

IS NOT ABLE TO FIND PIVOT SIL =%1 AS READ FROM DATA BLOCK %2
IN TABLE OF SILS.

2352.1 *** SYSTEM WARNING MESSAGE 2352 (GPFDFA)

UNABLE TO FIND PIVOT SIL =%1 AS READ FROM DATA BLOCK %2 (GPECT) IN TABLE OF
SILS.

2353.0 *** USER WARNING MESSAGE 2353. (GPFDR)

INSUFFICIENT CORE TO HOLD ALL NON-ZERO APP-LOAD AND F-OF-SPC OUTPUT LINE
ENTRIES OF GRID-POINT-FORCE-BALANCE REQUESTS. SOME POINTS REQUESTED FOR
OUTPUT WILL BE MISSING THEIR APP-LOAD OR F-OF-SPC CONTRIBUTION IN THE
PRINTED BALANCE.

2354.0 *** USER WARNING MESSAGE 2354. (GPFDR)

MODULE IS UNABLE TO CONTINUE AND HAS BEEN TERMINATED DUE TO ERROR MES-
SAGE PRINTED ABOVE OR BELOW THIS MESSAGE.
THIS ERROR OCCURRED IN CODE WHERE THE VARIABLE -NERROR- WAS SET = %1

User information: This can occur in nonlinear solutions which invoke GPFDR via user-written DMAP.

2355.0 *** USER WARNING MESSAGE 2355. (GPFDR)

NULL DISPLACEMENT VECTOR ENCOUNTERED IN CROSS STRAIN ENERGY CALCULA-
TIONS.

2356.0 *** USER WARNING MESSAGE 2356. (GPFEV2)

THE SET %1 REFERENCED BY SETP %2 STARTING IN SUBCASE %3 PRODUCES A NULL
SET.

User information: THE SET WILL BE IGNORED.

2357.0 *** USER WARNING MESSAGE 2357. (GPFSET)

SETP %1 REFERENCES ANOTHER SETP %2.

User information: SETP %3 WILL BE IGNORED.

2358.0 *** USER WARNING MESSAGE 2358. (GPFSET)

Main Index
 MSC Nastran Error Messeges 263
Errors 2000 - 2999

ONE OR MORE SETS ARE UNDEFINED FOR SETP %1.

User action: CHECK CASE CONTROL REFERENCES FOR SETP %2.

2359.0 *** SYSTEM WARNING MESSAGE 2359. (GPFSET)

SETP %1 IN SUBCASE %2 IS UNDEFINED.

2360.0 *** USER FATAL MESSAGE 2360 (ADG)

CAERO 3, 4, OR 5 ENTRIES HAVE BEEN FOUND IN THE AERO MODEL BUT ARE NOT
ALLOWED IN STATIC AERO PROBLEMS.

User information: Static aeroelasticity only supports the doublet-lattice method of aerodynamics. Remove
these entry types from the Bulk Data.

2361.0 *** USER FATAL MESSAGE 2361. (IFP1A4)

SETP %1 IS NOT SUPPORTED FOR THE ABOVE DATA RECORVERY REQUEST.

2362.0 *** SYSTEM FATAL MESSAGE 2362. (SETA2L)

SET Spill AREA HAS BEEN EXCEEDED.

User action: CALL MSC CLIENT SUPPORT.

2364.0 *** USER FATAL MESSAGE 2364 (MKSTRP)

CAERO1 ENTRY ID = %1 THAT IS REFERENCED ON MONCNCM ENTRY ID LABELED = %2
DOES NOT EXIST.

User information: THE MISSING CAERO1 ID WILL BE IGNORED

2365.0 *** USER INFORMATION MESSAGE 2365. (GPFLNE)

GRID POINT FORCE OUTPUTS FOR LAGRANGE MULTIPLIER DEGREE-OF-FREEDOM ARE
ERRORS IN DISPLACEMENT CONSTRAINTS FOR RIGID ELEMENTS (WHICH ARE USU-
ALLY SMALL).

2365.1 *** USER INFORMATION MESSAGE 2365. (GPFNLE)

Main Index
 264 MSC Nastran Error Messeges
Errors 2000 - 2999

GRID POINT FORCE OUTPUTS FOR LAGRANGE MULTIPLIER DEGREE-OF-FREEDOM ARE

ERRORS IN DISPLACEMENT CONSTRAINTS FOR RIGID ELEMENTS (WHICH ARE USU-
ALLY SMALL).

2401.0 *** USER FATAL MESSAGE xxxx (P_UPDTSP)

IN %1 Part = %2 - DOES NOT EXIST IN THE TREE

User action: VERIFY THAT THE COMMANDS ARE CORRECT AND CHECK THE SPELLING
OF THE PARTNAME

2402.0 *** SYSTEM FATAL MESSAGE xxxx (P_UPDTSP)

IN %1 DATABLOCK %2 DOES NOT EXIST FOR PARTNAME = %3

User action: IF THE PART IS AN EXISTING PART, CHECK THE GENERATE OR COMBINE
RUN THAT CREATED THE PART TO VERIFY THAT IT WORKED PROPERLY. IF IT IS A NEW
PART, VERIFY THAT THE DMAP HAS THE CORRECT OUTPUT DATABLOCKS

2403.0 *** SYSTEM FATAL MESSAGE xxxx (P_UPDTSP)

ERROR READING INPUT DATABLOCK %1 NAME = %2
THERE ARE MORE THAN TWO WORDS IN RECORD 1

Programmer information: THIS DATABLOCK SHOULD BE THE TREE AND HAVE TWO
WORDS IN THIS RECORD

Programmer action: CHECK THE DMAP TO VERIFY THAT YOU HAVE THE PROPER DATA-
BLOCK NAMES IN THE CORRECT LOCATIONS

2404.0 *** SYSTEM FATAL MESSAGE xxxx (P_UPDTSP)

ERROR IN %1 - %2 DOES NOT EXIST FOR %3
BUT %4 DOES exist.

User action: VERIFY THAT PROCESSING COMPLETED PROPERLY IN THE GENERATE STEP
FOR THIS PART

2405.0 *** USER FATAL MESSAGE 2405 (P_UPDTSP)

Main Index
 MSC Nastran Error Messeges 265
Errors 2000 - 2999

ERROR IN %1 CHECKING BOUNDARIES:

GRID %2 FOR THE OLD PART HAS COORDINATE SYSTEM TYPE CODE %3 AND DOF
CODE %4
GRID %5 FOR THE NEW PART HAS COORDINATE SYTSEM TYPE CODE %6 AND DOF
CODE %7

User action: THE COINCIDENT GRID POINT TESTS CHECK TO VERIFY THAT THE NEW
GRID POINTS HAVE THE SAME DISPLACEMENT COORDINATE SYSTEM TYPE AND
ALIGNMENT - MAKE SURE THAT THE GRIDS HAVE THE SAME TYPE OF COORDINATE
SYTSEM AND THE DOF ALIGN PROPERLY

2406.0 *** USER FATAL MESSAGE 2406 (P_UPDTSP)

ERROR IN %1 CHECKING BOUNDARIES: MISMATCH ON %2 LOCATION
GRID %3 IN OLD PART IS AT %4
GRID %5 IN NEW PART IS AT %6

User information: THEY SHOULD BE COINCIDENT

2407.0 *** USER FATAL MESSAGE 2407 (P_UPDTSP)

ERROR IN %1 CHECKING BOUNDARIES: GRID/SPOINT %2 DOES NOT EXIST IN Part = %3

User action: THE GRID/SPOINT IS IN THE EQSP TABLE FOR THIS PART, VERIFY THAT THE
PART WAS PROPERLY PROCESSED WHEN IT WAS CREATED

2408.0 *** USER FATAL MESSAGE 2408 (P_UPDTSP)

ERROR IN %1 CHECKING BOUNDARIES: DISPLACEMENT COORDINATE SYSTEMS FOR
GRIDS ARE NOT ALIGNED -
COORDINATE SYSTEM MAP FOR GRID %2 IN OLD PART;
%3 %4 %5
%6 %7 %8
%9 %10 %11
COORDINATE SYSTEM MAP FOR GRID %12 IN NEW PART;
%13 %14 %15
%16 %17 %18
%19 %20 %21

User action: THE COORDINATE SYSTEMS MUST ALIGN

Main Index
 266 MSC Nastran Error Messeges
Errors 2000 - 2999

2409.0 *** USER FATAL MESSAGE 2409 (P_UPDTSP)

ERROR IN %1 CHECKING BOUNDARIES: UNABLE TO FIND COORDINATE SYSTEM %2 IN
%3

User information: A BOUNDARY GRID POINT REFERENCES THE ABOVE COORDINATE

SYSTEM. AN ERROR PROBABLY OCCURRED IN THE GENERATE OR COMBINE RUN THAT
CREATED THE PART

Programmer information: THE COORDINATE SYSTEM IS NOT FOUND IN THE PART'S

CSTMP TABLE.

2410.0 *** USER FATAL MESSAGE 2410 (P_UPDTSP)

PROBLEM ENCOUNTERED DURING RAPID SIMULATION PROTOTYPING.

User action: CHECK THAT THE RUN THAT CREATED THIS PART RAN SUCCESSFULLY IT IS
NOT POSSIBLE TO PERFORM RAPID SIMULATION PROTOTYPING

Programmer information: IN %1 DATABLOCK %2 DOES NOT EXIST OR AN UNEXPECTED

EOF HAS BEEN ENCOUNTERED READING IT FOR Part = %3

2411.0 *** USER FATAL MESSAGE 2411 (P_UPDTSP)

IN %1 NEW AND OLD PARTS HAVE A DIFFERENT NUMBER OF BOUNDARY POINTS
NEWPart = %2 - HAS %3 BOUNDARY POINTS AND
OLDPart = %4 - HAS %5 BOUNDARY POINTS

User action: CHECK TO MAKE SURE THAT THE OLDPART AND NEWPART HAVE IDENTI-
CAL BOUNDARIES

2412.0 *** USER FATAL MESSAGE 2412 (P_UPDTSP)

Main Index
 MSC Nastran Error Messeges 267
Errors 2000 - 2999

NON-IDENTICAL BOUNDARIES ENCOUNTERED BETWEEN OLDPART AND NEWPART

User information: THE TWO PARTS MUST HAVE IDENTICAL BOUNDARIES FOR RAPID
SIMULATION PROTOTYPING.

Programmer information: IN %1 RECORD 3 OF THE EQSP FILE FOR THE OLDPART HAS %2
WORDS AND THE EQSP OF THE NEWPART HAS %3 WORDS

2413.0 *** USER FATAL MESSAGE 2413 (P_UPDTSP)

THE LOADINGS FOR THE NEWPART ARE INCONSISTENT WITH THE LOADINGS FOR
THE SOLUTION PART.

User action: CHECK TO MAKE SURE THAT THE OLDPART WAS PROPERLY PROCESSED
AND INCLUDED IN ALL ASSEMBLIES

Programmer information: IN %1 AFTER TRANSFORMATION, THE LOADINGS FOR

NEWPart = %2 - HAVE %3 ROWS, BUT THE
LOADINGS FOR THE SOLUTION Part = %4 - HAVE %5 ROWS

2414.0 USER INFORMATION message xxxx (P_STORE)

The current PART has dynamic DOFs (q-set) but no physical DOFs defined in the a-set

User information: The resulting PART will be a modal representation with no physical DOFs.

2415.0 user fatal message yyyy (P_RCVR_RCOVA)

Solution type %1 could not be processed

2416.0 system fatal message zzzz (P_RCVR_RCOVMS)

Failed to get GINO FIST number for data block %1 using DBKSTRING = ',%2)

2416.1 user fatal message bbbb (P_RCVR_RCOVSS)

Failed to get GINO FIST number for %1 using DBKSTRING %2

2416.2 system fatal message oooo (P_RCVR)

Failed to get GINO FIST number for UAPART in Part = %1

Main Index
 268 MSC Nastran Error Messeges
Errors 2000 - 2999

2416.3 system fatal message oooo (P_RCVR)

Failed to get GINO FIST number for %1 in Part = %2

2417.0 user fatal message aaaa (P_RCVR_RCOVSS)

SOLN table for SOLUTION Part = %1 - does not exist

2418.0 user warning message cccc (P_RCVR_RCOVSS)

SOLN table could not be created for PARTNAME = %1

2419.0 user warning message dddd (P_GETPRT)

COMMAND Option %1 is not valid.

User action: Resubmit with OUTPUT,SUMMARY.

2420.0 system fatal message eeee (P_RCVR_TREE)

There is insufficient memory to hold table in p_process_order.

2421.0 user information message gggg (P_EXPORT)

For PART - %1,
data block %2 cannot be exported due to security = %3

2422.0 user warning message hhhh (P_EXPORT)

Requested option %1 is not valid for EXPORT

2423.0 system warning message llll (P_IMPORT)

Qualifier string not found for data block %1

2424.0 system warning message nnnn (P_IMPORT)

Output data block %1 could not be created for Part = %2

2425.0 system fatal message pppp (P_RCVR_BOUNDARY)

Error in processing TREE Data block

User information: Length of PARTNAME is inconsistent

2426.0 system information message qqqq (P_RCVR_BOUNDARY)

Main Index
 MSC Nastran Error Messeges 269
Errors 2000 - 2999

In PART = %3 non-conforming matrices encountered during recovery of boundary displacements.

Programmer information: NUMCOLSA = %1 NUMROWSB = %2

2427.0 user fatal message ssss (P_RCVR_BOUNDARY)

The root part name - %1 is not the same as the Solution part name - %2

2428.0 user information message tttt (P_RCVR_BOUNDARY)

In the NOTDONE Table, parts which do not have a boundary solution are indicated by a positive record
index

2429.0 user information message xxxx (P_RCVR3M)

Beginning data recovery for Part = %1

2430.0 system fatal message y1y1 (P_RCVR3M)

For PART = %1,
the number of solutions in SOLN %2 does not agree with the number of columns of the displacement
matrix %3

2431.0 system fatal message xxxx (P_IFSPAA)

Process error in P_IFSPAA

2432.0 system fatal message d1d1 (PAA_EQSP)

EQSP grid id does not match GEOM1 grid id %1 %2

2433.0 system fatal message e1e1 (PAA_EQSP)

Unrecoverable error encountered while processing EQEXIN and EQSP.

2433.1 system fatal message f1f1 (PAA_COMBINE)

Unrecoverable error encountered while processing LODS record %1 for PART %2

2433.2 system fatal message g1g1 (PAA_COMBINE)

Unrecoverable error encountered while processing LODS header record
for PART = %1

2433.3 system fatal message l1l1 (PAA_GEOM1)

Main Index
 270 MSC Nastran Error Messeges
Errors 2000 - 2999

Unrecoverable error encountered while processing %1 coordinate systems

2433.4 system fatal message m1m1 (PAA_GEOM1)

Unrecoverable error encountered while processing %1 for PART = %2

2433.5 system fatal message o1o1 (PAA_GEOM1)

Unrecoverable error encountered while processing GEOM1

2433.6 system fatal message p1p1 (P_COMB1A)

Unrecoverable error encountered in P_COMB1A_DRIVER

2433.7 system fatal message q1q1 (P_COMB1B)

Unrecoverable error encountered in P_COMB1B_DRIVER

2433.8 user fatal message a2a2 (P_COMB1A_DRIVER)

User information: see messages above issued by the command processor

2433.9 user fatal message b2b2 (P_COMB1A_DRIVER)

Unrecoverable error (code = %1) encountered processing the COMBINE command

User information: see messages above issued by the command processor

2433.10 system fatal message c2c2 (P_COMB1A_DRIVER)

Unrecoverable error encountered while updating the GEOM1 table for the assembly

2433.11 system fatal message e2e2 (P_COMB1A_DRIVER)

Unrecoverable error encountered while creating the EQSP for the assembly

2433.12 system fatal message f2f2 (P_COMB1A_DRIVER)

Unrecoverable error encountered updating %1 for the assembly

2433.13 system fatal message j2j2 (P_COMB1B_DRIVER)

Unrecoverable error encountered while creating the assembly matrices, error code = %1

2433.14 system fatal message p2p2 (PAA_GEOM4)

Unrecoverable error encountered while inserting RBAR into grid set

Main Index
 MSC Nastran Error Messeges 271
Errors 2000 - 2999

2434.0 system fatal message k1k1 (PAA_GEOM1)

For PART = %1
Could not insert from TREE %2 into set %3

2435.0 system fatal message n1n1 (PAA_GEOM1)

For part = %1
Error on GRIDA with GRIDA-ID = %2 - GRID-ID = %3 not found for

2436.0 system fatal message k2k2 (PAA_GEOM4)

Could not locate RBAR record in the GEOM4 NDDL

2437.0 user information message m2m2 (PAA_GEOM4)

There are no GRID points to connect in any of the parts.

2438.0 system fatal message n2n2 (PAA_GEOM4)

Could not create %1 set

2439.0 system fatal message p2p2 (PAA_GEOM4)

Could not open RGPDT header in GEOM4_UPDATE

2440.0 user fatal message s2s2 (P_UPDTSP)

There are insufficient partnames defined for the update of the Solution Part

User information: See output above issued by the command processor.

2441.0 system fatal message t2t2 (P_UPDTSP)

The transformation matrix does not exist for PART = %1 and Solution PART = %2

2442.0 user fatal message u2u2 (P_UPDTSP)

Update failed.

User information: See above output for more information.

2443.0 user fatal message a3a3 (COMMANDS)

There are no command records.

Main Index
 272 MSC Nastran Error Messeges
Errors 2000 - 2999

2444.0 user fatal message b3b3 (COMMANDS)

THE CURRENT PARTNAME INDEX %1 HAS ALREADY BEEN USED FOR PARTNAME %2

2445.0 user fatal message c3c3 (COMMANDS)

COMPONENT INDEX %1 EXCEEDS %2 IN COMBINE.

2446.0 system fatal message d3d3 (COMMANDS)

PART INDEX %1 EXCEEDS the maximum value allowed of %2 IN RECOVER PROCESSIN

2447.0 system warning message e3e3 (COMMANDS)

PSID %1 IS GREATER THAN maximum value allowed.

2448.0 user warning message f3f3 (COMMANDS)

ID %1 IS GREATER THE the maximum value allowed of %2 IN PROCESSING CURRENT COM-
MAND

2449.0 user warning message g3g3 (COMMANDS)

TRANSLATE is an invalid option.

2450.0 user warning message h3h3 (COMMANDS)

OUTPUT KEYWORD %1 is an invalid COMMAND option.

2451.0 user warning message i3i3 (COMMANDS)

THE NUMBER OF DATA BLOCKS TO BE DELETED EXCEEDS THE MAXIMUM NUMBER
%1.

User information: THE LAST %2 DATA BLOCKS will be IGNORED.

2452.0 user warning message j3j3 (COMMANDS)

IN %1 PROCESSIN
PART INDEX %2 EXCEEDS the maximum value allowed of %3

2453.0 user warning message k3k3 (COMMANDS)

SUBCOMMAND %1 is invalid FOR COMMAND %2.

2454.0 system fatal message l3l3 (COMMANDS)

UNKNOWN OBJECT %1 COULD NOT BE PROCESSED IN GET_NUMBERO.

Main Index
 MSC Nastran Error Messeges 273
Errors 2000 - 2999

2455.0 user fatal message ffff (P_RCVR_TREE)

Upstream and Downstream PARTNAME are not the same for a single record tree.

2456.0 user warning message jjjj (P_EXPORT)

EXPORT failed for data block %1 for PART = %2

User information: Although requested, the data block does not exist on database.

2457.0 user fatal message kkkk (P_IMPORT)

COMMAND file could not be processed.

User information: See messages above for details.

2458.0 user information message rrrr (P_RCVR_BOUNDARY)

Process tree printout, length = %1 for PART = %2
Index Rec No. Num Connections Lower Rec

2459.0 system fatal message mmmm (P_IMPORT)

Length of string %1 exceeds limit of %2

2462.0 user fatal message mmmm (MECHCASE)

%1 does not exist on DMAP statement, module terminated

2470.0 *** USER WARNING MESSAGE 2470 (MODGM2)

THE VALUE OF PARAMETER OSWPPT=%1 IS LESS THAN THE MAXIMUM GRID ID=%2,
WHICH MAY INTRODUCE CONFLICTS OF GRID ID NUMBERS AND MAY CAUSE FATAL
ERRORS LATER.

User action: REDEFINE OSWPPT TO AVOID CONFLICTING GRID ID NUMBERS.

2470.1
THE VALUE OF PARAMETER OSWPPT=%1 IS LESS THAN SQSETID=%2.
OSWPPT MUST BE GREATER THAN (SQSETID + NUMBER OF QSET POINTS).

User action: REDEFINE OSWPPT.

Main Index
 274 MSC Nastran Error Messeges
Errors 2000 - 2999

Main Index
 MSC Nastran Error Messeges 275
Errors 3000 - 3999

Errors 3000 - 3999

3001.0 FORMAT 1001:

THE %1 FILE %2 DOES NOT EXIST.

Programmer information: SUBROUTINE %3

3001.1 FORMAT 1011 and 1021:

THE %1 DATA BLOCK NAMED %2 AT POSITION %3 DOES NOT EXIST.

User information: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING:

1. THE DATA BLOCK WAS NEVER CREATED.
2. THE DATA BLOCK WAS DELETED.
3. THE DATA BLOCK IS SPECIFIED ON A TYPE STATEMENT IN THE CURRENT
SUBDMAP OR A HIGHER SUBDMAP BUT THE CURRENT QUALIFIER VALUES DO
NOT MATCH THE QUALIFIER VALUES OF THE DATA BLOCK(S) ON THE DATABASE.

User action:
1. IF YOU ARE EXECUTING AN HEXAGON AB SUPPLIED SOLUTION SEQUENCE AND
NOT USING THE ALTER EXECUTIVE CONTROL STATEMENT, THEN CHECK FOR
BULK DATA AND/OR CASE CONTROL INPUT ERRORS. IF NO ERRORS CAN BE
FOUND, THEN CONTACT HEXAGON AB CLIENT SUPPORT.
2. IF YOU ARE EXECUTING A DMAP PROGRAM NOT SUPPLIED BY HEXAGON AB,
THEN FOR DEBUGGING PURPOSES INSERT STATEMENT DIAGON(20) BEFORE THE
MODULE SHOWN ABOVE.
Programmer information: THE FIST NUMBER IS %4 AND SUBROUTINE IS %5

User information:
This message should not occur for HEXAGON AB SOLs, but it has been observed when there is a mis-
match between Case Control commands and Bulk Data entries (for example, a missing FREQi entry in
modal frequency response analysis). Because this kind of missing data should be caught by MSC NAS-
TRAN in a better manner, please inform Hexagon so we better trap the error.

3001.2 FORMAT 1010 and 1020:

THE %1 DATA BLOCK IN POSITION %2 DOES NOT EXIST.

Main Index
 276 MSC Nastran Error Messages
Errors 3000 - 3999

User information: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING:

1. THE DATA BLOCK IS UNSPECIFIED ON THE DMAP MODULE.
2. THE DATA BLOCK IS SPECIFIED ON THE DMAP MODULE AND ON THE SUBDMAP
STATEMENT BUT NOT ON THE CORRESPONDING CALL STATEMENT.

User action:
1. IF YOU ARE EXECUTING AN HEXAGON AB SUPPLIED SOLUTION SEQUENCE AND
NOT USING THE ALTER EXECUTIVE CONTROL STATEMENT, THEN CHECK FOR
BULK DATA AND/OR CASE CONTROL INPUT ERRORS. IF NO ERRORS CAN BE
FOUND, THEN CONTACT HEXAGON AB CLIENT SUPPORT.
2. IF YOU ARE EXECUTING A DMAP PROGRAM NOT SUPPLIED BY HEXAGON AB,
THEN FOR DEBUGGING PURPOSES INSERT STATEMENT DIAGON(20) BEFORE THE
MODULE SHOWN ABOVE.
Programmer information: THE FIST NUMBER IS %3 AND SUBROUTINE IS %4

3001.3 FORMAT 9965:

** SYSTEM FATAL MESSAGE 3001 (PGTHD), PTELM IS PURGED

3001.4 *** USER WARNING MESSAGE 3001. (DRMH3)

OUTPUT DATA BLOCK %1 IS PURGED, NO OUTPUT WILL BE GENERATED

3001.5 *** USER WARNING MESSAGE 3001. (DRMH3)

INPUT DATA BLOCK %1 IS PURGED, OUTPUT DATA BLOCK %2 WILL NOT BE GENER-
ATED

3001.6 *** USER WARNING MESSAGE 3001. (DRMH3)

THE CASE CONTROL DATA BLOCK IS PURGED, OUTPUT DATA BLOCKS WILL BE GENER-
ATED; SOME OUTPUT LABELS MAY BE MISSING

3001.7 *** USER WARNING MESSAGE 3001. (DRMH1)

INPUT DATA BLOCK %1 IS NOT SORT 1 FORMAT. INPUT DATA BLOCK IGNORED.

3001.9 *** USER FATAL MESSAGE 3001. (MATMOD-26)

UNABLE TO OPEN DATA BLOCK %1 BECAUSE IT IS PURGED.

3001.10 *** SYSTEM INFORMATION MESSAGE 3001

ATTEMPT TO OPEN THE DATA SET %1 WHICH WAS NOT DEFINED IN FIST.

Main Index
 MSC Nastran Error Messeges 277
Errors 3000 - 3999

3001.11 *** SYSTEM FATAL MESSAGE 3001

ATTEMPT TO OPEN THE DATA SET %1 WHICH WAS NOT DEFINED IN FIST.

3001.12 *** SYSTEM WARNING MESSAGE 3001 (PFCHKI)

%2 INPUT DATA BLOCK IS PURGED.

User information: %1 CASE CONTROL OUTPUT REQUEST WILL BE IGNORED.

3001.13 *** SYSTEM WARNING MESSAGE 3001 (PFCALC)

%2 OUTPUT DATA BLOCK IS PURGED.

User information: %1 PARTICIPATION FACTOR OUTPUT REQUEST WILL BE IGNORED.

3002.0 FORMAT 102:

EOF ENCOUNTERED WHILE READING DATA BLOCK %1 (FILE %2) IN SUBROUTINE %3

3002.1 *** SYSTEM FATAL MESSAGE 3002 (SK11RD)

END OF FILE WAS ENCOUNTERED WHILE READING K11 MATRIX FOR ITERATIVE
SOLVER INSIDE STATICS MODULE.

3002.2 *** SYSTEM FATAL MESSAGE 3002 (SCALRD):

END OF FILE WAS ENCOUNTERED WHILE READING K11 MATRIX FOR ITERATIVE
SOLVER INSIDE STATICS SUPERMODULE.

3002.3 *** SYSTEM INFORMATION MESSAGE 3002

EOF ENCOUNTERED WHILE READING DATA SET %1.

3002.4 *** SYSTEM FATAL MESSAGE 3002

EOF ENCOUNTERED WHILE READING DATA SET %1.

System information: This message is issued when an END-OF-FILE occurs while trying to skip the header
record. The data block is not in the proper format. This generally occurs when data that the subroutine
expects is missing.

Main Index
 278 MSC Nastran Error Messages
Errors 3000 - 3999

3002.5 *** SYSTEM FATAL MESSAGE 3002 (DISOFM)

UNEXPECTED END OF FILE WAS ENCOUNTERED WHILE READING %1 FROM PARALLEL
NODE %2

3002.6 *** SYSTEM FATAL MESSAGE 3002

ERROR ENCOUNTERED DURING READ OF EQMAP
User action: CONTACT HEXAGON AB CLIENT SUPPORT.

3002.7 *** USER FATAL MESSAGE 3002 (PARAML)

RECORD NO. %1 SPECIFIED BY THE %2 PARAMETER EXCEEDS THE NUMBER OF
RECORDS (%3) IN THE INPUT DATA BLOCK

*** ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK %1 (FILE
3003.0
%2) IN SUBROUTINE %3
System information: The data block is not in proper format.

3003.1 *** SYSTEM FATAL MESSAGE 3003 (NSL1SD)

ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA SET %1.

3003.2 *** system fatal message 3003 (disofm)

UNEXPECTED END OF RECORD WAS ENCOUNTERED WHILE READING %1 FROM PAR-
ALLEL NODE %2

3003.3 *** USER FATAL MESSAGE 3003 (PARAML)

WORD NO. %1 IMPLIED BY THE %2 PARAMETER EXCEEDS THE NUMBER OF WORDS
(%3) IN RECORD %4 OF THE INPUT DATA BLOCK

3004.0 *** INCONSISTENT TYPE FLAGS ENCOUNTERED WHILE PACKING DATA BLOCK %1

3005.0 *** ATTEMPT TO OPERATE ON THE SINGULAR MATRIX %1 IN SUBROUTINE %2

User information: Subroutine SDCOMP or subroutine UDCOMP has detected a singular matrix and the
calling routine does not support this case. A User Information Message defining the singularity has already
been printed.

3006.0 ***SYSTEM FATAL MESSAGE 3006,

Main Index
 MSC Nastran Error Messeges 279
Errors 3000 - 3999

CONFLICTS WITH BUFFERS CURRENTLY OPEN.

3007.0 ILLEGAL INPUT TO SUBROUTINE %1

BUFFER ASSIGNED WHEN OPENING DATA BLOCK %1,FILE %2,

System information:
Subroutine %1 has encountered data which it cannot process. This error should not be caused by user
input data, except as described in the next paragraphs. A system or programming error is indicated. Go
directly to the subroutine listing or description to determine the exact cause of the problems.
This message occurs in superelement or module analysis when restarting improperly. The illegal input
message is usually caused by a purged input file.
One example is if the subroutine is CALCV. A common cause of this error is when attempting to perform
a PARTN (or MERGE) on matrices with null partitioning vectors, or attempting to perform UPARTN (or
UMERGE) on a matrix for which the original set is the same size as the final set. In this case, the
partitioning vector generated by the program is null and this error is generated. In CALCV, if the DMAP
partition "hard-coded" and the set does not exist, you'll get this error. For example, if a UPARTN module
is using the Q-set, but the user hasn't used any Q set entries, this error will be issued. One remedy is to
conditionally jump over the problem DMAP based on parameters such as NOQSET, NORSET, etc.

3007.1 *** SYSTEM FATAL MESSAGE 3007

MODULE = GEOMSRVR
ILLEGAL INPUT TO SUBROUTINE GEOMSR

3007.2 *** SYSTEM FATAL MESSAGE 3007

ILLEGAL INPUT TO SUBROUTINE %1
INPUT MATRIX %2 IS COMPLEX,
THE CURRENT SOLUTION SEQUENCE DOES NOT SUPPORT COMPLEX ARITHMETIC

3007.3 *** SYSTEM FATAL MESSAGE 3007

LOGIC ERROR IN SUBROUTINE %1.

Programmer information: LOCATION/INFO = %2.

3007.4 *** SYSTEM FATAL MESSAGE 3007

INPUT MATRIX IS REAL
THIS ROUTINE DOES NOT SUPPORT REAL ARITHMETIC

Main Index
 280 MSC Nastran Error Messages
Errors 3000 - 3999

3008.0 INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE %1

3008.1 *** SYSTEM FATAL MESSAGE 3008 (UTMCOR),

MODULE = %1
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE %2

Programmer information: LOCATION KEY = %3

System information:
This message implies that the particular subroutine does not have sufficient memory to meet its demands.
The subroutine or module description should be consulted to determine the memory requirements.
If an increase in memory is desired for only the module producing the error, an alter must be included in
the Executive section of the input file. An example of the alter is included below.
COMPILE DMAP=dmap,SOUIN=source $ source=MSCSOU or USRSOU ALTER #
$ before module TYPE PARM,,I,N,MVAL $
MVAL = GETSYS(MVAL,57) PUTSYS(value1,57) $
value1=increased memory value
ALTER #
$ after module PUTSYS(MVAL,57) $
ENDALTER $
One cause observed for this in the Bulk Data SORT module is too many continuation entries. An
avoidance is to have the Bulk Data already sorted and to increase available memory. Also, large THRU
ranges can cause excessive memory to be used.

3008.2 *** SYSTEM FATAL MESSAGE 3008 (UTMCOR),

MODULE = %1
INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE %2

User action: INCREASE OPEN CORE BY AT LEAST %3 WORDS

Programmer information: LOCATION KEY = %4

3008.3 *** USER WARNING MESSAGE 3008 (UDSFB)

INSUFFICIENT MEMORY TO PERFORM FBS METHOD S3. THIS MAY LEAD TO POOR PER-
FORMANCE IN THE MCE1 MODULE FOR BETTER PERFORMANCE INCREASE MEMORY
BY%1 WORDS

Main Index
 MSC Nastran Error Messeges 281
Errors 3000 - 3999

3008.4 *** USER INFORMATION MESSAGE 3008 (SSM10D)

INSUFFICIENT MEMORY TO COMPUTE ERROR RATIOS.

User action: SUPPLY AN ADDITIONAL %1 WORDS OF MEMORY IF EPSILON CHECKING IS

DESIRED.

3008.5 *** SYSTEM FATAL MESSAGE 3008 (SK11RD)

ITERATIVE SOLVER IN STATICS MODULE: ONLY %1 COLUMNS OF THE MATRIX FIT IN
MEMORY.
CURRENTLY THERE IS NO SPILL LOGIC FOR THE ITERATIVE SOLVER INSIDE THE STAT-
ICS MODULE.

User action: INCREASE MEMORY OR USE THE DIRECT METHOD.

3008.6 *** SYSTEM FATAL MESSAGE 3008 (SEPCAG)

INSUFFICIENT MEMORY FOR MAIN BULK BASIC GEOMETRY.

3008.7 *** SYSTEM FATAL MESSAGE 3008 (SEPCAG)

INSUFFICIENT MEMORY FOR SUPERELEMENT OR MODULE %1 BASIC GEOMETRY.

3008.9 *** SYSTEM FATAL MESSAGE 3008

INSUFFICIENT MEMORY FOR UNROLLED DESCRIPTOR.

3008.10 *** SYSTEM FATAL MESSAGE 3008

INSUFFICIENT DYNAMIC MEMORY.

3008.13 *** SYSTEM FATAL MESSAGE 3008

INSUFFICIENT MEMORY AT ROW %1.

3008.20 *** SYSTEM FATAL MESSAGE 3008 (IFPDRV)

NO OPEN CORE FOR IFP MODULE.
3008.21 *** SYSTEM FATAL MESSAGE 3008 (IFP4)
INSUFFICIENT MEMORY TO PERFORM OPERATIONS REQUIRED AS A RESULT OF
FREEPT OR PRESPT ENTRIES.

Main Index
 282 MSC Nastran Error Messages
Errors 3000 - 3999

3008.22 *** SYSTEM FATAL MESSAGE 3008 (IFP4)

INSUFFICIENT MEMORY TO BUILD FREE SURFACE LIST TABLE.

3008.23 *** SYSTEM FATAL MESSAGE 3008 (IFP4)

INSUFFICIENT MEMORY TO HOLD RINGFL ENTRIES.

3008.24 *** SYSTEM FATAL MESSAGE 3008 (IFP4)

INSUFFICIENT MEMORY TO BUILD BOUNDARY LIST TABLE.

3008.25 *** SYSTEM FATAL MESSAGE 3008 (IFP4)

INSUFFICIENT MEMORY = %1 TO HOLD GRIDB ENTRIES.

3008.26 *** SYSTEM FATAL MESSAGE 3008 (IFP4)

INSUFFICIENT MEMORY = %1 TO READ DATA ON AXIF ENTRY.

3008.27 *** USER FATAL MESSAGE 3008. (DRMH3E)

INSUFFICIENT MEMORY FOR TIME POINT LABELS, %1 WORDS ADDITIONAL MEMORY
NEEDED.

3008.28 *** USER FATAL MESSAGE 3008.

INSUFFICIENT MEMORY FOR FREQUENCIES, %1 WORDS ADDITIONAL MEMORY
NEEDED.

3008.30 *** USER INFORMATION MESSAGE 3008. (DRMH3A)

INSUFFICIENT MEMORY FOR TIME POINTS, %1 READ UNKNOWN AMOUNT OF ADDI-
TIONAL MEMORY NEEDED DRMH3 ABORTING.

3008.31 *** USER INFORMATION MESSAGE 3008. (DRMH3A)

INSUFFICIENT MEMORY FOR FREQUENCIES, %1 READ UNKNOWN AMOUNT OF ADDI-
TIONAL MEMORY NEEDED DRMH3 ABORTING.

3008.32 *** USER INFORMATION MESSAGE 3008. (DRMH3A)

INSUFFICIENT MEMORY TO STORE COLUMN LABELS ADDITIONAL %1 WORDS
NEEDED.
3008.33 *** USER INFORMATION MESSAGE 3008. (DRMH3A)
INSUFFICIENT MEMORY FOR LAMA, %1 MODES READ; %2 * (REMAINING MODES)
WORDS OF ADDITIONAL MEMORY NEEDED; DRMH3 ABORTING

Main Index
 MSC Nastran Error Messeges 283
Errors 3000 - 3999

3008.34 *** USER INFORMATION MESSAGE 3008. (DRMH3)

INSUFFICIENT MEMORY FOR CASE CONTROL RECORD, ADDITIONAL %1 WORDS
NEEDED; DRMH3 ABORTED

3008.35 *** USER INFORMATION MESSAGE 3008. (DRMH3)

INSUFFICIENT MEMORY, ADDITIONAL %1 WORDS ARE NEEDED.

3008.36 *** SYSTEM FATAL MESSAGE 3008 (AELOOP)

INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE AELOOP.

3008.37 *** USER FATAL MESSAGE 3008 (HOUSE)

INSUFFICIENT MEMORY TO HOLD ONE COLUMN OF THE MATRIX IN HOUSEHOLDER
TRIDIAGONALIZATION.

3008.38 ***SYSTEM FATAL MESSAGE 3008 (PXMLOC)

PID%1 UNABLE TO ACQUIRE SPACE OF %2 WORDS.

User information: INCREASE MEMORY AVAILABLE TO JOB.

3008.39 *** SYSTEM INFORMATION MESSAGE 3008 (SDRVP)

NOT ENOUGH MEMORY FOR COMPUTING OPTIMIZED COMMUNICATION PATTERN.
SWITCHED TO REGULAR PATTERN.

User action: ADD A MINIMUM OF %1 ADDITIONAL WORDS IF AN OPTIMIZED PATTERN IS

DESIRED.

3008.40 *** SYSTEM INFORMATION MESSAGE 3008 (SITDRV)

INSUFFICIENT CORE TO COMPUTE RIC PRECONDITIONER.

User action: INCREASE MEMORY BY AT LEAST %1 WORDS.

3008.41 *** SYSTEM INFORMATION MESSAGE 3008 (SITDRV)

INSUFFICIENT CORE TO KEEP RIC PRECONDITIONER IN MEMORY.

User action: INCREASE MEMORY BY AT LEAST %1 WORDS.

Main Index
 284 MSC Nastran Error Messages
Errors 3000 - 3999

3008.42 *** SYSTEM INFORMATION MESSAGE 3008

INSUFFICIENT CORE FOR CHOLESKY FACTORIZATION.

User action: INCREASE CORE BY %1 WORDS.

SWITCHED TO JACOBI PRECONDITIONER.

3008.43 *** SYSTEM INFORMATION MESSAGE 3008 (BGCASO)

INSUFFICIENT CORE IS AVAILABLE FOR BUILDING CONTACT PRIMARY SET.

3008.44 *** SYSTEM INFORMATION MESSAGE 3008 (BGCAU1)

INSUFFICIENT CORE IS AVAILABLE TO PROCESS CONTACT REGION OUTPUT REQUEST.

3008.45 *** SYSTEM FATAL MESSAGE 3008 (BGCONR)

INSUFFICIENT CORE IS AVAILABLE FOR READING %1 RECORD.

3008.46 *** SYSTEM WARNING MESSAGE 3008 (GPFGED)

*** SWM 3008.46
GENEL ELEMENT %1 WILL BE SKIPPED DUE TO INSUFFICIENT MEMORY.

User action: INCREASE MEMORY BY %2 WORDS OR USE DMIG ENTRIES.

3008.47 *** SYSTEM FATAL MESSAGE 3008 (BGLSCW)

INSUFFICIENT CORE IS AVAILABLE FOR READING BLSEG SECONDARY AND PRIMARY
RECORDS.

3008.48 *** SYSTEM FATAL MESSAGE 3008 (BGPECT)

INSUFFICIENT CORE TO ACCOMMODATE BGPECT RECORD.

3008.50 *** SYSTEM FATAL MESSAGE 3008 (BGTPEN)

INSUFFICIENT CORE TO BUILD BTOPO AND ESTNL RECORDS.

3008.51 *** USER FATAL MESSAGE 3008 (IFP5)

INSUFFICIENT MEMORY TO HOLD ALL GRIDS ENTRIES.

3008.52 *** USER FATAL MESSAGE 3008 (IFP5)

INSUFFICIENT MEMORY TO HOLD ALL GRIDF ENTRIES.

Main Index
 MSC Nastran Error Messeges 285
Errors 3000 - 3999

3008.53 *** USER FATAL MESSAGE 3008 (IFP5)

INSUFFICIENT MEMORY TO HOLD ALL GRIDF ENTRIES BEING CREATED INTERNALLY
DUE TO GRIDS ENTRIES SPECIFYING AN IDF.

3008.54 *** USER FATAL MESSAGE 3008 (IFP5)

INSUFFICIENT MEMORY TO CONSTRUCT ENTIRE BOUNDARY TABLE FOR SLBDY
ENTRIES PRESENT.

3008.55 *** USER FATAL MESSAGE 3008 (BGUPEN)

INSUFFICIENT CORE IS AVAILABLE.

3008.56 *** USER FATAL MESSAGE 3008 (SEQMRP)

INSUFFICIENT SPACE IN MEMORY TO CREATE %1 RECORD IN SCRATCH FILE RBESCR.

Programmer information: NUMBER OF WORDS TO BE STORED IN THIS RECORD OF RBE-

SCR: %2. NUMBER OF WORDS AVAILABLE IN SCRATCH ARRAY: %3.

User information: THIS MODEL CANNOT BE ANALYSED USING THE DOMAIN DECOMPOSI-
TION METHOD.

User action: PLEASE SUBMIT THE JOB IN SERIAL MODE (DO NOT SET DMP ON THE SUB-
MITTAL LINE).

3008.57 *** USER INFORMATION MESSAGE 3008 (OUTPRT)

INSUFFICIENT MEMORY WAS AVAILABLE TO PROCESS THE OUTPUT REQUESTS.

User information: MORE ECONOMICAL DATA RECOVERY MAY BE POSSIBLE IF ADDI-

TIONAL MEMORY IS PROVIDED.

3008.58 *** SYSTEM WARNING MESSAGE 3008.58 (LDNSSEL)

Main Index
 286 MSC Nastran Error Messages
Errors 3000 - 3999

NOT ENOUGH MEMORY AVAILABLE TO LOAD NSERVER_SELECT CLAUSE(S).

REQUESTED I= %1 WORDS

User information: CLAUSE(S) WILL BE IGNORED.

User action: INCREASE MEMORY OR REDUCE NUMBER OF NSERVER_SELECT CLAUSE(S)

3008.59 *** SYSTEM WARNING MESSAGE 3008.59 (NSSELWH)

INSUFFICIENT MEMORY WHILE WORKING ON NSERVER_SELECT WHERE CLAUSE
STARTING WITH %1 MEMORY USED = %2.

User information: WHERE CLAUSE IS IGNORED.

User action: INCREASE MEMORY SIZE OR REDUCE NSERVER_SELECT STATEMENT.

3008.60 *** SYSTEM WARNING/FATAL MESSAGE 3008 (PREBRD)

INSUFFICIENT MEMORY %1.

User action: INCREASE MEMORY BY AT LEAST %2 K WORDS.

3008.61 *** SYSTEM WARNING MESSAGE 3008 (IFPINDX)

INSUFFICIENT MEMORY TO BUILD INDEX
ADDITIONAL MEMORY REQUIRED: %1 MW.

User information: %2 NOT INDEXED

User action: INCREASE MEMORY IF THIS FILE NEEDS TO BE INDEXED

3008.62 *** SYSTEM FATAL MESSAGE 9102 (GUSTLDW)

THE FOLLOWING MEMORY MANAGEMENT ERROR CODE = %1 OCCURRED IN %2:
%3

3008.63 *** SYSTEM FATAL MESSAGE 9102 (GUSTLDW)

A NON DOCUMENTED MEMORY MANAGEMENT ERROR CODE = %1 OCCURRED IN %2.

3008.64 *** USER INFORMATION MESSAGE

Main Index
 MSC Nastran Error Messeges 287
Errors 3000 - 3999

INSUFFICIENT CORE FOR SPECIAL ACMS FACTORIZATION ROUTINE.

User action: FOR IMPROVED PERFORMANCE, INCREASE MEMORY BY AT LEAST %1

WORDS.

User information: THE STANDARD SPARSE FACTORIZATION WILL BE USED INSTEAD. THE
SPECIAL ACMS FACTORIZATION IMPROVES THE PERFORMANCE OF ACMS JOBS WITH A
VERY LARGE FREQUENCY RANGE.

3008.65 *** SYSTEM INFORMATION MESSAGE 3008 (CAPMEM):

SOLVIT MEMORY ESTIMATE FOR CASI SOLVER INDICATES THAT NASTRAN MEMORY IS
INSUFFICIENT TO ATTEMPT SOLUTION.

Programmer information: SWITCHING TO SYSTEM HEAP MEMORY.

NASTRAN MEMORY AVAILABLE = %1MB,
MINIMUM ESTIMATED MEMORY NEEDED FOR CASI ITERATIVE SOLVER = %2MB,
MAXIMUM ESTIMATED MEMORY NEEDED FOR CASI ITERATIVE SOLVER = %3MB

3008.66 *** USER FATAL MESSAGE 3008 (UMFDRV):

INSUFFICIENT MEMORY FOR UMFPACK FACTORIZATION
UMFPACK PEAK MEMORY ESTIMATE = %1 MB
UMFPACK REALISTIC MEMORY EST. = %2 MB
MEMORY AVAILABLE = %3 MB

3008.67 *** USER FATAL MESSAGE 3008 (UMFDRV):

MEMORY REQUIREMENTS FOR SPARSE UNSYMMETRIC DECOMPOSITION
MINIMUM MEMORY REQUIREMENT = %1 WORDS (%2 MB)
MEMORY AVAILABLE = %3 WORDS (%4 MB)

3008.68 *** system FATAL MESSAGE 3008 (CMPDRV):

THE OUT-OF-CORE SUPERNODAL COMPRESSION METHOD FAILED TO COMPRESS THE
ADJACENCY STRUCTURE. THERE IS INSUFFICIENT MEMORY AVAILABLE TO STORE
FULL ADJACENCY STRUCTURE IN MEMORY.

User action: INCREASE MEMORY BY AT LEAST %1 WORDS.

Main Index
 288 MSC Nastran Error Messages
Errors 3000 - 3999

3008.69 *** system FATAL MESSAGE 3008 (DDMBND):

There is INSUFFICIENT MEMORY TO FIND THE BOUNDARY for METIS DOMAIN DECOM-
POSITION POST PROCESSING.

3008.70 *** system fatal message 3008 (PAA_BULK_READER)

There is insufficient memory to read in Bulk Data section

3008.71 *** system fatal message d2d2 (P_COMB1A_DRIVER)

There is insufficient memory for GEOM1 grid sort

3008.72 *** system fatal message l2l2 (PAA_GEOM4)

There is insufficient memory in PAA_GEOM4_UPDATE_PARTS

3008.73 system fatal message r2r2 (MEMMGR)

There is insufficient memory from MEMMGR_MALLOC

3008.74 *** system FATAL MESSAGE 3008 (CMPDRV):

There is INSUFFICIENT MEMORY AVAILABLE TO STORE ADJACENCY STRUCTURE.

User action:
- INCREASE MEMORY BY AT LEAST %1 WORDS
OR
- USE THE DEFAULT COMPRESSION METHOD (OUT-OF-CORE SUPERNODAL COMPRES-
SION) FOR YOUR RUN.

3008.75 *** USER WARNING MESSAGE 3008 (ELIM2I):

THERE IS INSUFFICIENT MEMORY AVAILABLE TO COMPLETE ELIM2 IN-CORE MATRIX
OPERATIONS. SWITCHING TO OUT-OF-CORE MPYAD TO COMPLETE THE PROCESS.
THIS ACTION OCCURED AT INTERNAL LOCATION ILOC = %1.

User action: INCREASE MEMORY BY AT LEAST %2M WORDS.

3008.76 *** USER FATAL MESSAGE 3008 (XSPAC):

Main Index
 MSC Nastran Error Messeges 289
Errors 3000 - 3999

Insufficient MEMORY to proceed %1

User information: %2

User action: %3

3008.77 *** USER WARNING MESSAGE 3008 (ELIM2I):

THERE IS INSUFFICIENT MEMORY AVAILABLE TO COMPLETE ELIM2 IN-CORE MATRIX
OPERATIONS. SWITCHING TO OUT-OF-CORE MPYAD TO COMPLETE THE PROCESS.
THIS ACTION OCCURED AT INTERNAL LOCATION ILOC = %1.

User information: SUBMITTING THE JOB WITH MORE MEMORY MAY PREVENT THE JOB
FROM SWITCHING TO OUT-OF-CORE MPYAD. HOWEVER, THE AMOUNT OF MEMORY
NEEDED FOR INCORE OPERATION EXCEEDS THE LARGEST INTEGER THAT CAN BE
STORED, WHICH IS %2 IN I4 MODE.

User action: RUN THE JOB WITH MORE MEMORY ALLOCATED AND MODE=I8.

3008.78 *** USER FATAL MESSAGE 3008 (ACMS1PR):

MEMORY ALLOCATION FAILURE FOR THREAD ID = %1, DOMAIN = %2,
REQUEST AMOUNT = %3, RETURN CODE = %4, LOCATE CODE = %5

3008.79 *** USER FATAL MESSAGE 3008 (ACMS1PR):

MEMORY RELEASE FAILURE FOR THREAD ID = %1, DOMAIN = %2,
RETURN CODE = %3, LOCATE CODE = %4

3008.80 *** USER FATAL MESSAGE 3008 (ACMS1PR):

INSUFFICIENT STACK MEMORY FOR THREAD ID = %1, DOMAIN = %2,
REQUEST AMOUNT = %3, LOCATE CODE = %4

3008.81 *** SYSTEM INFORMATION MESSAGE 3008 (CAPMEM):

MEMORY AVAILABLE TO NASTRAN IS SUFFICIENT FOR CASI ITERATIVE SOLVER. TOTAL
HIWATER MARK FOR NASTRAN WITH CASI CAN BE CALCULATED BY ADDING THE
BELOW MAXIMUM ESTIMATED MEMORY NEEDED TO NASTRAN HIWATER
NASTRAN MEMORY AVAILABLE = %1MB,
MINIMUM ESTIMATED MEMORY NEEDED FOR CASI ITERATIVE SOLVER = %2MB,
MAXIMUM ESTIMATED MEMORY NEEDED FOR CASI ITERATIVE SOLVER = %3MB

Main Index
 290 MSC Nastran Error Messages
Errors 3000 - 3999

3008.82 *** SYSTEM WARNING/FATAL MESSAGE 3008 (LUSOLDRV)

INSUFFICIENT MEMORY %1.

User action: INCREASE MEMORY BY AT LEAST %2 MB.

3008.83 *** USER INFORMATION MESSAGE 3008 (MODGM2):
THERE IS INSUFFICIENT MEMORY AVAILABLE TO COMPLETE MODGM2 IN-CORE TABLE
OPERATIONS. SWITCHING TO OUT-OF-CORE PROCESSING TO COMPLETE THE PRO-
CESS.

User action: INCREASE MEMORY BY AT LEAST %1 MB.

3009.0 *** FORMAT 109: DATA TRANSMISSION ERROR ON DATA BLOCK %1(FILE %2)

*** FORMAT 110: ATTEMPT TO MANIPULATE DATA BLOCK %1(FILE %2) BEFORE OPEN-
3010.0
ING THE FILE

3011.0 FORMAT 111:

ATTEMPT TO WRITE A TRAILER ON FILE %1 WHEN IT HAS BEEN PURGED

System information: The file did not exist in the FIST when WRTTRL was called.

3012.0 ATTEMPT TO OPEN DATA BLOCK %1(FILE %2) WHICH HAS ALREADY BEEN OPENED

3013.0 ATTEMPT TO READ DATA BLOCK %1(FILE %2) WHEN IT WAS OPENED FOR OUTPUT

3014.0 ATTEMPT TO WRITE DATA BLOCK %1(FILE %2) WHEN IT WAS OPENED FOR INPUT

ATTEMPT TO FWDREC ON DATA BLOCK %1(FILE %2) WHEN IT WAS OPENED FOR
3015.0
OUTPUT

3016.0 %1 MATRIX IS NOT IN PROPER FORM IN SUBROUTINE %2

System information:
This implies that the input matrix is not in the proper form of type acceptable to the subroutine. Check the
trailer information on the matrix and the subroutine description for the discrepancy.

3017.0 NO MESSAGE FOR MESSAGE NO. = %1

Main Index
 MSC Nastran Error Messeges 291
Errors 3000 - 3999

PARAMETERS =%2

3018.0 MODULE %1, SEQUENCE NO.%2, REQUIREMENTS EXCEED AVAILABLE FILES

System information:
Segment File Allocator (SFA) did not have sufficient logical files available to fill the request of the module.
Reduce module requirements or increase the logical files within the computer system. See chapter 5
of the MSC NASTRAN DMAP Programmer's Manual.

3019.0 MAXIMUM LINE COUNT EXCEEDED IN SUBROUTINE %1 LINE COUNT EQUALS %2

User information:
The total number of lines written on the system output file has exceeded the set limit. To increase this
value, specify the MAXLINES=n command in the Case Control Section.

3020.0 GNFIST OVERFLOWED FIST TABLE AT SEQUENCE NO.%1DATASET %2

3021.0 FILE%1 NOT DEFINED IN FIST

3023.0 *** USER INFORMATION MESSAGE 3023 (originally 3028??)

B =%1 C =%2 R =%3

THE BANDWIDTH OF MATRIX %1 EXCEEDS THE MAXIMUM BANDWIDTH. A MAXIMUM

3024.0
BANDWIDTH OF %2 WILL BE USED

3025.0 ILLEGAL INDEX IN ACTIVE ROW OR COLUMN CALCULATION IN %1

MATRIX %1 EXCEEDS MAXIMUM ALLOWABLE SIZE FOR BAND WIDTH PLUS ACTIVE
3026.0
COLUMNS. BMAX = %2 CMAX = %3

3028.0 *** USER INFORMATION MESSAGE 3028,

BBAR =%1 CBAR =%2 R = %3

3028.1 *** USER INFORMATION MESSAGE 3028,

B =%1 C =%2 R =%3

3029.0 *** SYSTEM FATAL MESSAGE 3029,

PHYSICAL EOF ENCOUNTERED ON DATA BLOCK %1 (FILE %2 ).

Main Index
 292 MSC Nastran Error Messages
Errors 3000 - 3999

3030.0 *** SYSTEM WARNING MESSAGE 3030 (OFP)

THE OFP MODULE CANNOT PRINT THE DATABLOCK %1

User action: USE THE MATPRN OR TABPT MODULE.

Programmer information: OFP LOC CODE = %2 FILE =%3

3030.1 *** USER WARNING MESSAGE 3030,

MACOFP UNABLE TO PROCESS DATA BLOCK, ALTER IN A TABLE PRINT TO SEE DATA
MACOFP LOC CODE = %1
User information:
The format of the file is unrecognized. This may be caused by an output request for an element for which
formats are not defined.

3030.2 *** USER FATAL MESSAGE 3030,

MATGPR: If the first parameter is OFP, the second may not be blank.

3031.0 *** USER FATAL MESSAGE 3031 (FRRD1A)

THE %1 COMMAND IS NOT SPECIFIED IN CASE CONTROL.

3032.0 UNABLE TO FIND SELECTED SET (%1) IN TABLE (%2) IN SUBROUTINE (%3).
User information:
A particular set used in the problem was not included in the data. Good examples are loads, initial
conditions, or frequency sets. Include the required data or change the Case Control commands to select
data already in the problem. Set zero (0) has a special meaning. A set selection was required, but none was
made. For example, no METHOD was selected for an eigenvalue extraction problem, or no FREQ was
selected for frequency response. This message can also indicate that a LOAD entry references another
LOAD entry, which is not permitted. This message can also occur if a DLOAD entry references a non-
existing LOAD entry, e.g., RLOAD1.

3032.1 *** USER WARNING MESSAGE 3032 (LCGEN)

SELECTED LSEQ ENTRY %1 REFERENCES UNDEFINED %2 SET ID %3

3032.2 *** USER WARNING MESSAGE 3032 (LCGEN)

Main Index
 MSC Nastran Error Messeges 293
Errors 3000 - 3999

SELECTED LSEQ ENTRY %1 DOES NOT REFERENCE EXCITATION SET ID %2

SPECIFIED ON A RLOAD1/RLOAD2/TLOAD1/TLOAD2/ACSRCE ENTRY

3032.3 *** USER WARNING MESSAGE 3032 (LCGEN)

UNABLE TO FIND SET (%1) FOR %2.

3033.0 *** USER FATAL MESSAGE 3033,

SUBCASE ID%1 IS REFERENCED ON ONE OR MORE RANDPS CARDS
BUT IS NOT A CURRENT SUBCASE ID.

User information:
The RANDPS set selected can only reference subcase identification numbers included in the current loop.
All subcases in which the direct input matrices or transfer functions do not change are run together.
Either add a subcase with referenced identification number, change your RANDPS entries, or change the
identification numbers on your current subcases.

3034.0 ORTHOGONALITY CHECK FAILED, LARGEST TERM = %1, EPSILON = %2

3034.1 *** USER WARNING MESSAGE 3034,

ORTHOGONALITY TEST FAILED. LARGEST TERM = %1 ,NUMBER FAILED = %2
PAIR = %3,%4 , EPSILON = %5

User information:
This indicates that eigenvector accuracy is in doubt. This message is printed only when the off-diagonal
terms of the modal mass matrix are larger than 1.0E-10. The eigenvectors are not orthogonal to this
extent. This nonorthogonality is especially important if a modal formulation is used. The pair of eigenvec-
tors listed exhibit the worst behavior. The number failed is the number of pairs above the criteria. You can
improve the numerical conditioning of the problem by reducing the range of mass ratios, stiffness ratios,
and eigenvalue range.

3034.2 *** SYSTEM FATAL MESSAGE 3034 (LNNHERR)

INTERNAL FAILURE IN THE LANCZOS PROCEDURE:
M-ORTHOGONAL QR PROCEDURE FAILED TO CONVERGE. PROBABLE CAUSE: MASS
MATRIX IS INDEFINITE (MODES) OR STIFFNESS MATRIX IS INDEFINITE (BUCKLING).

User action: CONTACT MSC CLIENT SUPPORT.

Main Index
 294 MSC Nastran Error Messages
Errors 3000 - 3999

3035.0 FOR SUBCASE NUMBER %1 EPSILON SUB E =%2

3035.1 *** USER INFORMATION MESSAGE 3035

FOR DATA BLOCK %1
SUPPORT PT.NO. EPSILON STRAIN ENERGY EPSILONS LARGER THAN %2 ARE FLAGGED
WITH ASTERISKS

User information:
One line of output is printed for each component referenced on the SUPORT and SUPORT1 entries.
Large values of either EPSILON or STRAIN ENERGY indicate errors in the constraints.

3036.0 DATA BLOCK %1 IS REQUIRED AS INPUT BUT HAS NOT BEEN GENERATED OR PURGED

3037.0 JOB TERMINATED IN SUBROUTINE %1

System information: This message designates the subroutine in which the program terminated. It should
be preceded by a user message which explains the cause of the termination. The module in which the pro-
gram terminated can be found by examining the log messages.

3038.0 DATA BLOCK %1 DOES NOT HAVE MULTI-REEL CAPABILITY

3039.0 *** SYSTEM FATAL MESSAGE 3039,

ENDSYS CANNOT FIND SAVE FILE.

3040.0 ATTEMPT TO WRITE DATA BLOCK %1(FILE %2) WHEN IT IS AN INPUT FILE
System information:
Input data blocks for a module (FILE NO. 101-199) may be read only.

3041.0 EXTERNAL GRID POINT %1 DOES NOT EXIST OR IS NOT A GEOMETRIC GRID POINT.

Main Index
 MSC Nastran Error Messeges 295
Errors 3000 - 3999

THE BASIC ORIGIN WILL BE USED.

User information:
The reference grid point specified on the PARAM, GRDPNT entry for weight and balance calculations in
GPWG cannot be used.
GPWG cannot be used.
Possible causes include:
1. The referenced grid point does not exist.
2. In superelement analysis, if the referenced grid point is not either interior or exterior to the current
superelement, this message is issued. If it is desired to use the listed grid point as a reference, then a CSU-
PEXT entry should be used to make it exterior to the superelement.
3042.0 INCONSISTENT SCALAR MASSES HAVE BEEN USED. EPSILON/DELTA = %1
User information:
The GPWG has detected inconsistent scalar masses. Direct masses
have been used. Skew inertia's will result. Examine the scalar
masses and CONM1 entry.

3043.0 Unconnected extra point (modal coordinate =%1 ) has been detected by subroutine %2
User information:
Extra points must be connected via Direct Matrix Input (or Transfer
Functions) in modal transient or frequency response.

3044.0 A POINT ON NON-LINEAR LOAD SET %1 NOLIN%2 IS NOT AN EXTRA POINT.

ONLY EXTRA POINTS MAY HAVE NON-LINEAR LOADS IN A MODAL FORMULATION.

User information:
Modal transient analysis will support nonlinear loads only on extra
points. Pick another nonlinear load Set.

3045.0 *** USER WARNING MESSAGE 3045,

Main Index
 296 MSC Nastran Error Messages
Errors 3000 - 3999

INSUFFICIENT TIME TO COMPLETE THE REMAINING %1 SOLUTION(S) IN MODULE %4

User information: TIME ESTIMATE TO COMPLETE: %2 SECONDS

TIME REMAINING %3 SECONDS

User information:
The estimated time for completion of the module is less than the time remaining, as specified on the Exec-
utive Control TIME statement. The module and computes one solution (for example, one excitation
frequency in frequency response analysis) and then processes all output requests. The remaining frequencies
can be obtained on restart by adding or changing a FREQ command.

3046.0 *** USER FATAL MESSAGE 3046 (TRD1)

THIS TRANSIENT RESPONSE ANALYSIS HAS NO EXCITATION SPECIFIED FOR IT.
APPLIED LOADS, ENFORCED MOTION, INITIAL CONDITION AND NON-LINEAR FORCES
ARE ALL NULL.
THE RESULT WILL THEREFORE BE A ZERO SOLUTION.

User information:
Transient response solutions must have one of the above nonzero. Also, make
sure that LOADSET is spelled correctly, in its entirety.

3046.1 *** USER FATAL MESSAGE 3046 (SQFREQ/DPFREQ/CYCL4A)

THIS FREQUENCY RESPONSE ANALYSIS HAS NO EXCITATION SPECIFIED FOR IT.
APPLIED LOADS AND ENFORCED MOTION ARE BOTH NULL.
THE RESULT WILL THEREFORE BE A ZERO SOLUTION.

User information:
Frequency response solutions must have one of the above nonzero. Also, make sure that LOADSET is
spelled correctly, in its entirety.

3046.2 *** USER FATAL MESSAGE 3046 (TRD2)

THIS TRANSIENT RESPONSE ANALYSIS in SOL 200 or 400 HAS NO EXCITATION SPECIFIED
FOR IT.
THE APPLIED LOADS ARE NULL. THE RESULT WILL THEREFORE BE A ZERO SOLUTION.

User information:
Transient response analysis with ANALYSIS=MTRAN in SOL 200 or 400 must have nonzero applied
loads. Also, make sure that LOADSET is spelled correctly, in its entirety.

Main Index
 MSC Nastran Error Messeges 297
Errors 3000 - 3999

3047.0 *** USER FATAL MESSAGE 3047,

NO MODES HAVE BEEN SELECTED FOR USE IN THE ANALYSIS. THEREFORE A MODAL
FORMULATION CANNOT BE MADE.

User information:
The modes used for a modal formulation must be selected either via a MODESELECT Case Control com-
mand or via the LMODES/LMODESFL, LFREQ/LFREQFL or HFREQ/HFREQFL parameters.

3048.0 *** SYSTEM FATAL MESSAGE 3048,

BUFFER CONTROL WORD INCORRECT FOR GINO %1 OPERATION ON DATA BLOCK %2

3049.0 *** SYSTEM FATAL MESSAGE 3049,

GINO UNABLE TO POSITION DATA BLOCK %1 CORRECTLY DURING %2 OPERATION.

3050.0 *** USER FATAL MESSAGE 3050,

INSUFFICIENT TIME REMAINING FOR %1. TIME ESTIMATE IS %2 SECONDS.

User information:
The time estimate for execution of the named subroutine exceeds the time remaining as specified on the
TIME statement.

3050.1 *** USER FATAL MESSAGE 3050 (DFMSA)

INSUFFICIENT TIME REMAINING FOR SPARSE MATRIX DECOMPOSITION

3052.0 *** USER WARNING MESSAGE 3052,

A RANDOM REQUEST FOR CURVE TYPE - %1 -, POINT - %2
COMPONENT - %3 -, SPECIFIES TOO LARGE A COMPONENT ID. THE LAST COMPONENT
WILL BE USED.

User information:
Check Chapter 13 for component order.

3053.0 *** USER WARNING MESSAGE 3053,

Main Index
 298 MSC Nastran Error Messages
Errors 3000 - 3999

THE ACCURACY OF EIGENVALUE %1 IS IN DOUBT. GIV/HOU QR FAILED TO CONVERGE

IN %2 ITER.

User information:
Each eigenvalue is computed to the precision limits of each machine consistent with the maximum number
of iterations allowed.

AN ATTEMPT TO MULTIPLY OR MULTIPLY AND ADD NON-CONFORMABLE MATRICES

3055.0
TOGETHER WAS MADE IN MODULE %1
User information:
The multiply/add subroutine requires conformable matrices. There are two possible equations
1. X = A * B + C The number of columns of [A] must be equal to the number of rows of [B] the number of
columns of [C] be equal to the number of columns of [B] and the number of rows of [C] must be equal to
the number of rows of [A]. 2. X = A(T) *B + C The number of rows of [A] must be equal to the number of
rows of [B] the number of columns of [C] must be equal to the number of columns of [B] and the number
of rows of [C] must be equal to the number of columns of [A]. One cause of this is if the model in a cyclic
symmetry analysis contains MPCs and only the zero harmonic is requested. This can be avoided by
requesting an additional harmonic.

3056.0 NO MASS MATRIX IS PRESENT BUT MASS DATA IS REQUIRED

3057.0 MATRIX %1 IS NOT POSITIVE DEFINITE.

User information:
A Cholesky decomposition was attempted on the above matrix, but a diagonal term of the factor was imag-
inary or equal to zero such that the decomposition failed. This message is from the regular (as opposed to
sparse) decomposition method. This message may be produced because of constraint problems. Check
the output for UWM 4698 for large factor diagonal ratios and constrain appropriately.

3058.0 EPSILON IS LARGER THAN %1 FOR SUBCASE %2

3059.0 SET IDENTIFIER %1 DOES NOT EXIST. ERROR DETECTED IN SUBROUTINE %2

User information:
When describing displacement matrices only those set identifiers (such as M or G) listed in DMAP module
MATGPR are legal set names. Choose a set name which is legal (and describes the matrices to be operated
on).

NEW SET IDENTIFIER %1 IN DEFUSET IS NOT UNIQUE. ERROR DETECTED IN SUBROU-

3059.1
TINE %2

Main Index
 MSC Nastran Error Messeges 299
Errors 3000 - 3999

User information:
When Using new set names, these must be unique with respect to all other set names.

3060.0 *** USER FATAL MESSAGE 3060,

SUBROUTINE %1 - OPTION %2 NOT IN APPROVED LIST.
SYSTEM DATE (MM/DD/YY): %3/%4/%5
SYSTEM MSCID: %6 (DECIMAL) %7 (HEXADECIMAL) SYSTEM MODEL NUMBER: %8
SYSTEM OS CODE: %9
REFER TO THE MSC NASTRAN LOG FILE FOR DETAILED INFORMATION

User information:
This option is not authorized for your authorization code. Contact your Hexagon Remote Office Manager
for the list of options available at your site. This option can be easily enabled with a contractual change on
your present system and a new authorization code. There may be a problem with the file that contains the
authorization code. Refer to the MSC NASTRAN Installation and Operation Instructions
for a description and use of the file.

3060.1 *** USER FATAL MESSAGE 3060

Main Index
 300 MSC Nastran Error Messages
Errors 3000 - 3999

SUBROUTINE %1 - OPTION %2 NOT IN APPROVED LIST.

SYSTEM DATE (MM/DD/YY): %3/%4/%5
SYSTEM MSCID: %6 (DECIMAL) %7 (HEXADECIMAL) SYSTEM MODEL NUMBER: %8 SYS-
TEM OS CODE: %9
SYSTEM MSCID: %10 (DECIMAL) %11 (HEXADECIMAL) SYSTEM MODEL NUMBER: %12
SYSTEM OS CODE: %13
SYSTEM MSCID: %14 (DECIMAL) %15 (HEXADECIMAL) SYSTEM MODEL NUMBER: %16
SYSTEM OS CODE: %17
SYSTEM MSCID: %18 (DECIMAL) %19 (HEXADECIMAL) SYSTEM MODEL NUMBER: %20
SYSTEM OS CODE: %21
SYSTEM MSCID: %22 (DECIMAL) %23 (HEXADECIMAL) SYSTEM MODEL NUMBER: %24
SYSTEM OS CODE: %25
SYSTEM MSCID: %26 (DECIMAL) %27 (HEXADECIMAL) SYSTEM MODEL NUMBER: %28
SYSTEM OS CODE: %29
SYSTEM MSCID: %30 (DECIMAL) %31 (HEXADECIMAL) SYSTEM MODEL NUMBER: %32
SYSTEM OS CODE: %33
SYSTEM MSCID: %34 (DECIMAL) %35 (HEXADECIMAL) SYSTEM MODEL NUMBER: %36
SYSTEM OS CODE: %37
REFER TO THE MSC NASTRAN LOG FILE FOR DETAILED INFORMATION

User information:
This option is not authorized for your authorization code. Contact your Hexagon Remote Office Manager
for the list of options available at your site. This option can be easily enabled with a contractual change on
your present system and a new authorization code. There may be a problem with the file that contains the
authorization code. Refer to the MSC NASTRAN Installation and Operation Instructions
for a description and use of the file.

3060.2 *** USER FATAL MESSAGE 3060 (MSGWRT)

- AUTHORIZATION ERROR ***
UNABLE TO OBTAIN LICENSES FOR %1
PLEASE REFER TO THE LOG FILE FOR ADDITIONAL DETAILS

3060.3 *** USER FATAL MESSAGE 3060,

Main Index
 MSC Nastran Error Messeges 301
Errors 3000 - 3999

SUBROUTINE %1 - OPTION %2 NOT IN APPROVED LIST.

SYSTEM DATE (MM/DD/YY): %3/%4/%5
MSC NASTRAN NO LONGER SUPPORTS AUTH=ESP, AS OF VERSION 2004. YOU CAN
EITHER USE A V2001 INSTALLATION OF MSC NASTRAN WITH N4W, OR CONTACT YOUR
MSC REPRESENTATIVE TO OBTAIN AN ALTERNATE LICENSE (IF ALLOWED UNDER
YOUR CONTRACT).

User information:
As of MSC NASTRAN v2004, AUTH=ESP is no longer supported.

3061.0 *** USER INFORMATION MESSAGE 3061 (DMK9NS)

THE MEASURE OF NON-PLANARITY IS %1 FOR ELEMENT NUMBER %2

User information:
THE MEASURE OF NON-PLANARITY FOR ISOPARAMETRIC QUADRILATERAL MEMBRANE
ELEMENTS IS THE DISTANCE FROM ACTUAL GRID POINTS TO MEAN PLANE DIVIDED
BY THE AVERAGE LENGTH OF THE DIAGONALS. THIS MESSAGE IS ISSUED
ONLY WHEN THE ABSOLUTE VALUE OF THIS MEASURE IS GREATER THAN .01.

3071.0 *** SYSTEM WARNING MESSAGE 3071,

EXTRA DATA IN RADLST RECORD OF MATPOOL DATA BLOCK IGNORED.

3072.0 *** USER WARNING MESSAGE 3072,

TOO MANY MATRIX VALUES INPUT VIA RADMTX BULK DATA FOR COLUMN %1.
EXTRA VALUES IGNORED AS MATRIX SIZE IS DETERMINED TO BE OF SIZE %2 FROM
RADLST COUNT OF ELEMENT ID-S.

3073.0 *** USER FATAL MESSAGE 3073,

NO -HBDY- ELEMENT SUMMARY DATA IS PRESENT FOR ELEMENT ID = %1
WHICH APPEARS ON A -RADLST- BULK DATA CARD.

3074.0 *** USER FATAL MESSAGE 3074 (SDRMG)

COLUMN %1 OF THE YSYM MATRIX IS NULL.

3079.0 *** USER FATAL MESSAGE 3079,

THERE ARE NO -HBDY- ELEMENTS PRESENT.

Main Index
 302 MSC Nastran Error Messages
Errors 3000 - 3999

3080.0 *** USER FATAL MESSAGE 3080 (QLOADL)

QVECT TABLE INPUT NOT ALLOWED FOR STEADY STATE.
3081.0 *** SYSTEM WARNING MESSAGE 3081 (DFMSYA)
The size of the matrix to be decomposed is not equal to the size of the degree-of-freedom set.
Size of %1 set = %2
Size of %3 matrix = %4

User information: Decomposition PERFORMANCE MAY BE DEGRADED AND/OR MORE MEM-

ORY MAY Be REQUIRED.

3081.1 *** SYSTEM FATAL MESSAGE 3081

INCONSISTENT USET DATA DETECTED.

System information:
Input matrices whose dimensions are inconsistent with the matrix sizes stored in the USET table have been
detected. The usual cause is a restart that does not select the proper SE-type Case Control commands.
Try an SEALL=ALL restart

3081.2 *** SYSTEM WARNING MESSAGE 3081 (DFMSYA)

The size of the degree-of-freedom set is not equal to the size of the partitioning vector.
Size of %1 set = %2
Size of %3 vector = %4

User information: Decomposition PERFORMANCE MAY BE DEGRADED AND/OR MORE MEM-

ORY MAY Be REQUIRED.

3081.3 *** SYSTEM WARNING MESSAGE 3081 (DFMSYA)

The size of the matrix to be decomposed is not equal to the number of zeros in the partitioning vector.
Size of %1 matrix = %2
Number of zeros in %3 vector = %4

User information: Decomposition PERFORMANCE MAY BE DEGRADED AND/OR MORE MEM-

ORY MAY Be REQUIRED.

3094.0 *** SYSTEM FATAL MESSAGE 3094

Main Index
 MSC Nastran Error Messeges 303
Errors 3000 - 3999

SLT LOAD TYPE %1 IS NOT RECOGNIZED.

System information: A new load type was added to SLT but not to subroutine SSGSLT.
3095.0 *** USER WARNING MESSAGE 3095 (SSGSLT)
ALL ELEMENT TYPE %1, REFERENCED BY A QVOL CARD IN LOAD SET %2,
ARE NOT BEING USED FOR INTERNAL HEAT GENERATION IN THIS LOAD SET AS THIS
ELEMENT TYPE IS CURRENTLY NOT SUPPORTED IN THIS AREA.

3095.1 *** USER WARNING MESSAGE 3095 (SSGSLT)

ELEMENT TYPE %1 WITH ID =%2, REFERENCED BY A QVOL CARD IN LOAD SET %3,
IS NOT BEING USED FOR INTERNAL HEAT GENERATION IN THIS LOAD SET BECAUSE
ANOTHER ELEMENT TYPE WITH THE SAME ID HAS ALREADY BEEN PROCESSED.

3096.0 *** USER FATAL MESSAGE 3096 (SSGSLT)

ELEMENT ID =%1 AS REFERENCED ON A QVOL, QBDY1, QBDY2, QBDY3, OR QVECT
ENTRY COULD NOT BE FOUND AMONG ACCEPTABLE ELEMENTS FOR THAT LOAD
TYPE.

User information: QBDY1, QBDY2 or QVECT entries can only point to CHBDY elements. QVOL can
only point to legal heat transfer elements. See the MSC NASTRAN Thermal Analysis User's Guide for the
list.

3097.0 *** USER WARNING MESSAGE 3097.

SYMMETRIC DECOMPOSITION OF DATA BLOCK %1 ABORTED DUE TO ABOVE MES-
SAGES AND USER OPTION.

3097.1 *** USER WARNING MESSAGE 3097.

SYMMETRIC DECOMPOSITION OF DATA BLOCK %1 ABORTED BECAUSE THE FOLLOW-
ING COLUMN IS NULL--%2

User information: The user can avoid this message by using the DECOMP=16 statement to continue with
the zero column. (This is set by setting SYSTEM(69)=16 or via DMAP.) This puts 1.0 on the diagonal of
the null column.
See the MSC NASTRAN Numerical Methods User's Guide.

3097.2 *** USER WARNING MESSAGE 3097.

Main Index
 304 MSC Nastran Error Messages
Errors 3000 - 3999

SYMMETRIC DECOMPOSITION OF DATA BLOCK %1 HAS ZERO ON THE DIAGONAL AT

COLUMN %2.
DECOMPOSITION ABORTED.

3097.3 *** USER WARNING MESSAGE 3097.

SYMMETRIC DECOMPOSITION LEADING MINOR OF DATA BLOCK %1 IS SINGULAR AT
COLUMN %2.
DECOMPOSITION ABORTED.

3097.4 *** SYSTEM FATAL MESSAGE 3097.

PARALLEL DECOMPOSITION OF DATA BLOCK %1 ABORTED
BECAUSE THE FOLLOWING COLUMN IS NULL %2

3097.5 *** SYSTEM FATAL MESSAGE 3097

PARALLEL DECOMPOSITION OF DATA BLOCK %1 HAS ZERO ON THE DIAGONAL AT
COLUMN %2
DECOMPOSITION ABORTED

3097.6 *** USER WARNING MESSAGE 3097 (DFMSA)

COLUMN %1 HAS ZERO DIAGONAL TERM, DECOMPOSITION ABORTED ON USER
REQUEST.

3097.7 *** USER WARNING MESSAGE 3097 (DFMSA)

COLUMN %1 IS NULL, DECOMPOSITION ABORTED ON USER REQUEST.

3097.8 *** USER WARNING MESSAGE 3097 (DFMSAP)

ZERO DIAGONAL TERMS ENCOUNTERED, DECOMPOSITION ABORTED ON USER
REQUEST.

3097.9 *** SYSTEM FATAL MESSAGE 3097

PARALLEL DECOMPOSITION OF LEADING MINOR OF DATA BLOCK %1 IS SINGULAR AT
COLUMN %2
DECOMPOSITION ABORTED

3097.10 *** SYSTEM INFORMATION MESSAGE 3097

PARALEL DECOMPOSITION OF DATA BLOCK %1 HAS ZERO DIAGONAL AT COLUMN %2

Main Index
 MSC Nastran Error Messeges 305
Errors 3000 - 3999

3097.11 *** SYSTEM FATAL MESSAGE 3097

PARALLEL DECOMPOSITION OF DATA BLOCK %1 ABORTED DUE TO ABOVE MESSAGES
AND USER OPTION

3097.12 *** SYSTEM INFORMATION MESSAGE 3097

COLUMN %1 of DATA BLOCK %2 IS NULL.

3097.13 *** SYSTEM INFORMATION MESSAGE 3097

DATA BLOCK %1 HAS ZERO DIAGONAL TERM AT COLUMN%2

3097.14 *** SYSTEM INFORMATION MESSAGE 3097

PARTIAL DECOMPOSITION FAILED

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

3097.15 *** SYSTEM INFORMATION MESSAGE 3097

BOUNDARY DECOMPOSITION FAILED

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

3097.16 *** USER WARNING MESSAGE 3097

INTEL MKL PARDISO SPARSE DECOMPOSITION OF MATRIX NAMED %1 ON UNIT %2
HAS ZERO DIAGONAL AT COLUMN %3

3103.0 *** USER WARNING MESSAGE 3103,

EMGCOR OF EMG MODULE FINDS EITHER OF DATA BLOCKS%1 OR %2 ABSENT AND
THUS
%3. MATRIX WILL NOT BE FORMED.

3104.0 *** SYSTEM FATAL MESSAGE 3104,

EMGCOR FINDS EST (ASSUMED DATA BLOCK%1) MISSING. EMG MODULE
COMPUTATIONS THUSLY LIMITED.

3112.0 *** USER INFORMATION MESSAGE 3112,

Main Index
 306 MSC Nastran Error Messages
Errors 3000 - 3999

ELEMENTS CONGRUENT TO ELEMENT ID =%1

WILL BE RE-COMPUTED AS THERE IS INSUFFICIENT CORE AT THIS MOMENT TO HOLD
DICTIONARY DATA.

3113.0 *** SYSTEM FATAL MESSAGE 3113,

NO DISPLACEMENT DATA FOR ELEMENT %1 FOR DIFFERENTIAL STIFFNESS
GENERATION.

3114.0 *** USER FATAL MESSAGE 2036 (AIEGOR)

BASE POINT CONNECTION ORDER FOR CACINF%1 ELEMENT ID %2 IS BEING
REVERSED.

3115.0 *** SYSTEM FATAL MESSAGE 6935. (EMGPOM)

ILLEGAL COMBINATION OF INPUT PARAMETERS SUPPLIED FOR ELEMENT TYPE %1
INPUT PRECISION = %2, INPUT MATRIX FORM = %3, OUTPUT MATRIX FORM = %4

3116.0 *** USER FATAL MESSAGE 3116 (AIEMGD/S)

ELEMENT %1 MATRIX GENERATION FAILED FOR CACINF%2 ELEMENT ID %3
ELEMENT MATRIX GENERATION ERROR CODE = %4

3116.1 *** USER FATAL MESSAGE 3116 (AIEMGD/S)

ELEMENT %1 MATRIX GENERATION FAILED FOR CACINF%2 ELEMENT ID %3
INCORRECT NUMBER OF NODES (%4) FOR ELEMENT TYPE.

3116.2 *** USER FATAL MESSAGE 3116 (AIEMGD/S)

ELEMENT %1 MATRIX GENERATION FAILED FOR CACINF%2 ELEMENT ID %3
INVALID RADIAL INTERPOLATION ORDER (%4) DEFINED ON PACINF ENTRY (ID = %5).
RIO MUST BE BETWEEN 1 AND 50.

3116.3 *** USER FATAL MESSAGE 3116 (AIEMGD/S)

ELEMENT %1 MATRIX GENERATION FAILED FOR CACINF%2 ELEMENT ID %3
INVALID POLE LOCATION DEFINED ON PACINF ENTRY (ID = %4).

3116.4 *** USER FATAL MESSAGE 3116 (AIEMGD/S)

Main Index
 MSC Nastran Error Messeges 307
Errors 3000 - 3999

ELEMENT %1 MATRIX GENERATION FAILED FOR CACINF%2 ELEMENT ID %3 DUE TO A

FACTORIZATION ERROR

User action: CHECK ELEMENT GEOMETRY.

3117.0 *** SYSTEM WARNING MESSAGE 3117 (AFPIFFD)

ERROR CODE %1 REPORTED FROM FFT ROUTINE %2

User action: CONTACT MSC CLIENT SUPPORT

3117.1 *** USER WARNING MESSAGE 3117 (AFPIFFD)

FIELD POINT ID %1 COULD NOT BE LOCATED WITHIN INFINITE ELEMENT.
RESULTS WILL BE ZERO.

User action: CHECK LOCATION OR ADJUST GEOMETRIC TOLERANCE.

3117.2 *** USER WARNING MESSAGE 3117 (AFPIPTD)

ACOUSTIC FPM COMPUTATIONS REQUIRING NORMAL VECTORS ABORTED FOR
ACOUSTIC FIELD POINT MESH ID = %1.

User information: ELEMENT NORMAL DIRECTIONS POINTING AWAY FROM THE POLE
CANNOT BE VERFIED DUE TO THE PRESENCE OF MULTIPLE PACINF ENTRIES CON-
TAINING DIFFERENT POLE LOCATIONS.

User action: ADD A PARAM,PACINFID,PID ENTRY TO THE AFPM BULK DATA SECTION
WHERE PID IS THE ID OF THE PACINF ENTRY THAT SHOULD BE USED TO OBTAIN THE
POLE LOCATION FOR THIS AFPM SECTION.

3117.3 *** USER WARNING MESSAGE 3117 (AFPIPTD)

Main Index
 308 MSC Nastran Error Messages
Errors 3000 - 3999

ACOUSTIC FPM COMPUTATIONS REQUIRING NORMAL VECTORS ABORTED FOR

ACOUSTIC FIELD POINT MESH ID = %1.

User information: ELEMENT NORMAL DIRECTIONS POINTING AWAY FROM THE POLE
CANNOT BE VERFIED SINCE PACINFID = %2 CANNOT
BE LOCATED AMONG THE EXISTING PACINF ENTRIES.

User action: VERIFY THAT THE PID SPECIFIED ON THE PARAM,PACINFID,PID ENTRY FOR
THIS AFPM BULK DATA SECTION IS PRESENT
AMONG THE PACINF ENTRIES.

3117.4 *** USER INFORMATION MESSAGE 3117 (AFPINVD)

REVERSING NORMAL VECTORS THAT POINT TOWARD THE AIE POLE FOR %1 %2 ELE-
MENTS IN AFP MESH ID %3.

User information: AFPM ELEMENT NORMAL DIRECTIONS MUST POINT AWAY FROM THE
POLE LOCATION SPECIFIED FOR THE ACOUSTIC
INFINITE ELEMENTS.

3118.0 *** USER FATAL MESSAGE 3118.

ROD ELEMENT WITH ID =%1 HAS ILLEGAL GEOMETRY OR CONNECTIONS.
LOC CODE =%2

3119.0 *** USER INFORMATION MESSAGE 3117 (AFPINI)

DATA RECOVERY OF ACOUSTIC FIELD POINT MESH %1 INITIATED

3120.0 *** SYSTEM FATAL MESSAGE 3120 (EMGPOM)

EMGPOM PROCESS LOGIC ERROR. MULTIPLE PARTITIONS RECEIVED BY EMGPOM FOR
ELEMENT TYPE %1 DURING EMG
SQUARE (INFORM=1) MATRIX PROCESSING FOR CASI SOLVER.

User information: INFORM=1 MATRICES MUST BE RECIEVED IN A SINGLE CALL TO EMG-

POM.

3121.1 %1 ELEMENT %2, CANNOT FIND ELEMENT COORDINATE SYSTEM %3.

Main Index
 MSC Nastran Error Messeges 309
Errors 3000 - 3999

3121.2 %1 ELEMENT %2, THE %3-TH GRID POINT IS NOT IN ELEMENT PLANE.

3121.3 %1 ELEMENT %2, THE %3-TH GRID POINT HAS NEGATIVE RADIUS.

3121.4 %1 ELEMENT %2, MATERIAL %3 IS NOT AXISYMMETRIC.

MAT9 ENTRIES MUST HAVE ZERO VALUES FOR G15, G16, G25, G26,
G35, G36, G45, AND G46 TO BE AXISYMMETRIC.

3121.5 %1 ELEMENT %2, HAS BAD GEOMETRY.

CHECK GRID POINT LOCATIONS.

3121.6 %1 ELEMENT %2, HAS NON POSITIVE AREA.

3121.7 %1 ELEMENT %2, %3-TH CORNER NOT SUPPLIED.

THE VERTEX GRID POINTS ARE NOT OPTIONAL

3121.8 %1 ELEMENT %2, HAS UNKNOWN GEOMETRY TYPE.

3121.9 %1 ELEMENT %2, HAS UNKNOWN INTEGRATION RULE.

ALLOWED VALUES ARE 0, 1, 2, AND 3
3121.10 %1 ELEMENT %2, HAS UNSUPPORTED 9-TH POINT.

3122.1 *** SYSTEM FATAL MESSAGE 3122 (RBAX3DD)

CANNOT FIND 3-D (INDEPENDENT) GRID POINT %1 REFERENCED IN RBAX3D ENTRY
%2

3122.2 *** SYSTEM FATAL MESSAGE 3122 (RBAX3DD)

CANNOT FIND AXISYMMETRIC HARMONIC (DEPENDENT) GRID POINT %1 REFER-
ENCED IN RBAX3D ENTRY %2

3122.3 *** USER FATAL MESSAGE 3122 (RBAX3DD)

CANNOT FIND COORDINATE SYSTEM %1 ASSOCIATED WITH AXISYMMETRIC HAR-
MONIC (DEPENDENT) GRID POINT %2
REFERENCED IN RBAX3D ENTRY %3

3122.4 *** USER FATAL MESSAGE 3122 (RBAX3DD)

Main Index
 310 MSC Nastran Error Messages
Errors 3000 - 3999

3-D (INDEPENDENT) GRID POINT %1 REFERENCED IN RBAX3D ENTRY %2 IS NOT IN

THE PLANE OF THE AXISYMMETRIC HARMONIC ROTOR

3122.5 *** USER FATAL MESSAGE 3122 (RBAX3DD)

AXISYMMETRIC HARMONIC (DEPENDENT) GRID POINT %1 REFERENCED IN RBAX3D
ENTRY %2 IS NOT IN THE PLANE OF THE AXISYMMETRIC HARMONIC ROTOR

3122.6 *** USER FATAL MESSAGE 3122 (RBAX3DD)

3-D (INDEPENDENT) GRID POINT %1 REFERENCED IN RBAX3D ENTRY %2 HAS NEGA-
TIVE RADIUS

3122.7 *** USER FATAL MESSAGE 3122 (RBAX3DD)

AXISYMMETRIC HARMONIC (DEPENDENT) GRID POINT %1 REFERENCED IN RBAX3D
ENTRY %2 HAS NEGATIVE RADIUS

3122.8 *** USER FATAL MESSAGE 3122 (RBAX3DD)

3-D (INDEPENDENT) GRID POINT %1 REFERENCED IN RBAX3D ENTRY %2 IS NOT ON
THE AXIS SYMMETRY

3122.9 *** USER FATAL MESSAGE 3122 (RBAX3DD)

3-D (INDEPENDENT) GRID POINT %1 AND AXISYMMETRIC HARMONIC (DEPENDENT)
GRID POINT %2
REFERENCED IN RBAX3D ENTRY %3 DO NOT HAVE THE SAME AXIAL COORDINATE
ALONG THE AXIS OF SYMMETRY

3122.10 *** SYSTEM FATAL MESSAGE 3122 (RBAX3DD)

CANNOT FIND DEPENDENT DOF ASSOCIATED WITH RBAX3D ENTRY %1

3199.0 FORMAT 199,2001,5100:

*** USER WARNING MESSAGE 3199,
INFORMATION AND WARNING MESSAGES MAY HAVE BEEN LOST BY ATTEMPTING TO
QUEUE MORE THAN %1 MESSAGES.

FORMAT 400: LOGIC ERROR DETECTED BY SUBROUTINE%1%2 = LOCATE CODE OR

3200.0
VALUE.

Main Index
 MSC Nastran Error Messeges 311
Errors 3000 - 3999

3200.1 *** USER WARNING MESSAGE 3200

IFLAG = %1

3200.2 *** SYSTEM FATAL MESSAGE 3200

LOGIC ERROR %1 ENCOUNTERED IN SUBROUTINE %2 -- JFLAG = %3

User action: REPORT THIS PROBLEM TO MSC CLIENT SUPPORT

*** SYSTEM FATAL MESSAGE 3200 (SECNV1/SECNV2/SECNV3, BDYINF/BDYINA/BDYINP

3200.3
and SEEFMB/SEEFMC/SEEFMD/SEEFML/SEEFMN)
*** SYSTEM FATAL MESSAGE 3200 (GKAM1C)
LOGIC ERROR %1 ENCOUNTERED IN SUBROUTINE %2

User action: REPORT THIS PROBLEM TO MSC CLIENT SUPPORT

3201.0 FORMAT 410: FIAT OVERFLOW IN SUBROUTINE %1

3201.1 *** SYSTEM FATAL MESSAGE 3201 (ELFDR)

Programmer information: JSUB = %1 IMSG = %2 LOC= %3 FILE = %4

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

3201.2 *** SYSTEM WARNING MESSAGE 3201 (COMPRS)

Programmer information:%1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

3201.3 *** SYSTEM FATAL MESSAGE 3201 (ILMPGPF)

Programmer information: LOCATION = %1

3202.0
DATA POOL DICTIONARY (DPD) OVERFLOW IN SUBROUTINE %1

3202.1 *** SYSTEM FATAL MESSAGE 3202 (DBSPC)

Main Index
 312 MSC Nastran Error Messages
Errors 3000 - 3999

Programmer information: THE LOGICAL FILE NAME %1 CAN NOT BE FOUND.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

3203.0 FORMAT 430: AN ILLEGAL VALUE OF -NU- HAS BEEN

SPECIFIED UNDER MATERIAL ID%1 FOR ELEMENT ID%2

User information:
Plate elements must not have Poisson's ratio equal to + 1.0 or -1.0.
Solid elements must not have Poisson's ratio equal to +0.5 or -1.0.

3204.0 FORMAT 132: UNABLE TO FIND SELECTED SET (%1) IN TABLE (%2) IN SUBROUTINE (%3).
User information:
A load set ID referenced either in Case Control or on a LOAD Bulk Data entry does not exist for the struc-
ture or for the current superelement or module. This message can also indicate that a LOAD Bulk Data
entry has referenced another LOAD Bulk Data entry, which is not permitted. Remove the ID of
the non-existent LOAD from the Bulk Data entry.

3300.0 *** SYSTEM FATAL MESSAGE 3300 (DSVG1P)

INVALID VALUE = %1 SUPPLIED TO 6TH PARAMETER.

3300.1 *** SYSTEM WARNING MESSAGE 3300

INVALID PARAMETER %1 SUPPLIED TO MODULE DIAGONAL, COLUMN SUBSTITUTED

3300.2 *** SYSTEM WARNING MESSAGE 3300 (DVSKMD)

INVALID ELEMENT TYPE = %1

3300.3 ***SYSTEM FATAL MESSAGE 3300 (MACOFP)

IMPROPER OP CODE P1 %1

3300.4 *** SYSTEM FATAL MESSAGE 3300 (MTMD32)

ILLEGAL VALUE FOR PARAMETER P2 = %1 - MODULE ABORTING

3300.5 *** SYSTEM FATAL MESSAGE 3300 (LNNRIGL)

Main Index
 MSC Nastran Error Messeges 313
Errors 3000 - 3999

ILLEGAL VALUE SPECIFIED FOR PARAMETER POSITION NUMBER 3 OF THE READ MOU-
DLE.

User information: THE VALUE MUST BE NON-NEGATIVE.

Main Index
 314 MSC Nastran Error Messages
Errors 3000 - 3999

Main Index
 MSC Nastran Error Messages 315
Errors 4000 - 4999

Errors 4000 - 4999

4010.0 *** USER FATAL MESSAGE 4010,
TEMPP3 BULK DATA CARD WITH SET ID = %1 AND ELEMENT ID = %2
DOES NOT HAVE ASCENDING VALUES SPECIFIED FOR Z.

User information: See TEMPP3 entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

4011.0 *** USER FATAL MESSAGE 4011,

ELEMENT TEMPERATURE SET%1
CONTAINS MULTIPLE TEMPERATURE DATA SPECIFIED FOR ELEMENT ID =%2

User information: Temperature for element is specified on more than one bulk data card.

4012.0 *** USER WARNING MESSAGE 4012,

THERE IS NO ELEMENT, GRID POINT, OR DEFAULT TEMPERATURE DATA FOR TEM-
PERATURE SET %1, WITH RESPECT TO ELEMENT ID = %2

User information: Required temperature data is probably missing from the Bulk Data. Check for TEMPD
or for TREF on the MAT1 entry.

4012.1 *** USER WARNING MESSAGE 4012,

THERE IS NO DEFAULT TEMPERATURE DATA FOR GRID POINT %1 IN ELEMENT ID = %2
WITH RESPECT TO THE TEMPERATURE SET %3

User information: Required temperature data is probably missing from the Bulk Data. Check for TEMPD
or for TREF on the MAT1 entry.

4013.0 *** USER FATAL MESSAGE 4013 (EDTL)

INSUFFICIENT MEMORY FOR TEMPERATURE SETS.

4015.0
TABLE NAMED %1 PUNCHED ONTO %2 CARDS.

Main Index
 316 MSC Nastran Error Messages
Errors 4000 - 4999

4016.0 *** USER FATAL MESSAGE 4016,

THERE IS NO TEMPERATURE DATA FOR ELEMENT %1 IN SET %2

User information: Required temperature data is probably missing from Bulk Data.

4016.1 *** USER FATAL MESSAGE 4016, (GETEMP)

THERE ARE NO TEMPERATURES FOR %1 ELEMENT %2 IN SET %3

User information: Required temperature data is probably missing from Bulk Data.

4017.1 *** USER FATAL MESSAGE 4017

ESTNL AND FILE (%1) ARE NOT PROPERLY ALIGNED

4020.0 *** SYSTEM FATAL MESSAGE 4020

TA1A HAS PICKED UP TEMPERATURE SET %1 AND NOT THE REQUESTED SET %2.

System information: The requested temperature set ID for temperature dependent material properties can-
not be found in data block GPTT.

4020.1 *** USER FATAL MESSAGE 4020 (CECORF)

CORE IS INSUFFICIENT BY AMOUNT= %1 WORDS TO PROCESS ELEMENT WITH ID = %2

4023.0 *** USER FATAL MESSAGE 4023 (TA1A)

FINDS NO ELEMENT, GRID POINT, OR DEFAULT TEMPERATURE DATA FOR ELEMENT
ID =%1

User information: Required temperature data is probably missing from Bulk Data.

4024.0 *** USER FATAL MESSAGE 4024.

NO CYJOIN CARDS WERE SUPPLIED.

User information: CYJOIN entries are required in cyclic symmetry problems to define the boundary
points.

4025.0 *** USER WARNING MESSAGE 4025.

NO SIDE 2 DATA FOUND.

Main Index
 MSC Nastran Error Messages 317
Errors 4000 - 4999

4025.1 *** USER WARNING MESSAGE 4025.

NO SIDE 1 DATA FOUND.

User information: See CYJOIN entry description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

4025.2 *** USER WARNING MESSAGE 4025.

NO SIDE 2 DATA FOUND.

4025.3 *** USER WARNING MESSAGE 4025.

NO SIDE 1 DATA FOUND.

4026.0 *** USER FATAL MESSAGE 4026.

TOO MANY SIDE 1 CYJOIN BULK DATA CARDS.

User information: Only one Side 1 entry is permitted.

4027.0 *** USER FATAL MESSAGE 4027.

NUMBER OF ENTRIES IN SIDE 1(%1) NOT EQUAL TO NUMBEER IN SIDE 2(%2) (MINI-
MUM VALUE WILL BE PROCESSED)

User information: Number of boundary points on Side 1 must be the same as on Side 2.

4028.0 *** USER FATAL MESSAGE 4028.

THE CODE FOR GRID POINT %1 DOES NOT MATCH THE CODE FOR GRID POINT %2

4029.0 *** USER FATAL MESSAGE 4029.

GRID POINT %1 APPEARS IN BOTH SIDE LISTS.

User information: A grid point cannot be on both Side 1 and Side 2.

4030.0 *** USER WARNING MESSAGE 4030.

COMPONENT %1 OF GRID POINTS %2,%3 CANNOT BE CONNECTED. (GRID POINT %4 IS
AT FAULT)

Main Index
 318 MSC Nastran Error Messages
Errors 4000 - 4999

4032.0 *** USER WARNING MESSAGE 4032.

NO COMPONENTS OF GRID POINTS %1 AND %2 WERE CONNECTED.

4032.1 *** USER WARNING MESSAGE 4032.

NO COMPONENTS OF GRID POINT %1 WERE IN THE A-SET.

4033.0 *** USER FATAL MESSAGE 4033 (IFP4)

COORDINATE SYSTEM ID = %1 AS SPECIFIED ON AXIF ENTRY IS NOT PRESENT AMONG
ANY OF CORD1C, CORD1S, CORD2C, OR CORD2S ENTRY TYPES.
CYLINDRICAL TYPE ASSUMED FOR CONTINUING DATA CHECK.

4035.0 *** USER FATAL MESSAGE 4035 (IFP4)

THE FLUID DENSITY HAS NOT BEEN SPECIFIED ON A BDYLIST ENTRY AND THERE IS
NO DEFAULT FLUID DENSITY SPECIFIED ON THE AXIF ENTRY.

User information: Required information missing from Bulk Data.

4037.0 *** USER FATAL MESSAGE 4037.

GRID POINT %1 IS LISTED MORE THAN ONCE ON CYJOIN CARDS.

4038.0 *** USER FATAL MESSAGE 4038 (IFP4)

RINGFL ENTRY HAS ID = %1 WHICH HAS BEEN USED.

User information: An identification number of a RINGFL entry is not unique.

4040.0 *** USER FATAL MESSAGE 4040 (IFP4)

ID =%1 APPEARS ON A BDYLIST ENTRY, BUT NO RINGFL ENTRY IS PRESENT WITH THE
SAME ID.

User information: All entries on BDYLIST card must be defined on a RINGFL entry.

4041.0 *** USER FATAL MESSAGE 4041,

ID = %1 IS OUT OF PERMISSIBLE RANGE OF 1 TO 499999.

User information: The identification number of a RINGFL is too large to be processed.

Main Index
 MSC Nastran Error Messages 319
Errors 4000 - 4999

4042.0 *** USER FATAL MESSAGE 4042 (IFP4)

COORDINATE SYSTEM IS CYLINDRICAL BUT RINGFL ENTRY ID = %1 HAS A NON-ZERO
X2 VALUE.

User information: The azimuthal angle of a RINGFL point must be zero.

4043.0 *** USER FATAL MESSAGE 4043 (IFP4)

COORDINATE SYSTEM IS SPHERICAL BUT RINGFL ENTRY ID = %1 HAS A NON-ZERO X3
VALUE.

4044.0 *** USER FATAL MESSAGE 4044 (IFP4AD)

RINGFL ENTRY ID = %1 HAS SPECIFIED A ZERO RADIAL LOCATION.

User information: Fluid points cannot be located on the axis of symmetry.

4045.0 *** USER FATAL MESSAGE 4045 (IFP4AD)

THE BOUNDARY LIST ENTRY FOR ID = %1 HAS A ZERO CROSS-SECTION LENGTH.

User information: A hydroelastic boundary can not be defined between two RINGFL points having the
same location. Check BDYLIST and RINGFL entries.

4048.0 *** USER FATAL MESSAGE 4048 (IFP4)

THE FLUID DENSITY HAS NOT BEEN SPECIFIED ON AN FSLIST ENTRY AND THERE IS NO
DEFAULT FLUID DENSITY SPECIFIED ON THE AXIF ENTRY.

User information: Required information missing from Bulk Data.

4050.0 *** USER FATAL MESSAGE 4050 (IFP4)

FSLIST ENTRY HAS INSUFFICIENT IDF DATA, OR FSLIST DATA MISSING.

User information: A referenced RINGFL point doesn't exist or the FSLIST entry is in error. At least two
points must be defined.

Main Index
 320 MSC Nastran Error Messages
Errors 4000 - 4999

4051.0 *** USER FATAL MESSAGE 4051 (IFP4)

AN MPC ENTRY HAS A SET ID SPECIFIED = 102. SET 102 IS ILLEGAL WHEN FLUID DATA IS
PRESENT.

User information: This set identification number is reserved for internal use in hydroelastic problems.

4052.0 *** USER FATAL MESSAGE 4052 (IFP4)

IDF = %1 ON A FREEPT ENTRY DOES NOT APPEAR ON ANY FSLIST ENTRY.

User information: A referenced RINGFL point must also appear on a FSLIST entry.

4055.0 *** USER FATAL MESSAGE 4055 (IFP4)

SET ID = 102 MAY NOT BE USED FOR SPC ENTRIES WHEN USING THE HYDROELASTIC-
FLUID ELEMENTS.

User information: This set identification number is reserved for internal use in hydroelastic problems.

4056.0 *** USER FATAL MESSAGE 4056,

RECORD ID = %1 IS OUT OF SYNC ON DATA BLOCK NUMBER %2
AN IFP4 SYSTEM ERROR.

User information: The record identification numbers are the values of LOCATE record ID. The data
block numbers are the GINO file numbers. Error implies that IFP4 is possibly operating on the wrong data
block. This system error should not occur. Message comes from IFP4B.

4057.0 *** USER FATAL MESSAGE 4057 (IFP4)

GRIDB ENTRY WITH ID = %1 HAS A REFERENCE IDF =%2 WHICH DOES NOT APPEAR IN A
BOUNDARY LIST.

User information: GRIDB points must be in the fluid boundary.

4058.0 *** USER FATAL MESSAGE 4058 (IFP4)

THE FLUID DENSITY HAS NOT BEEN SPECIFIED ON A CFLUID ENTRY WITH ID = %1 AND
THERE IS NO DEFAULT ON THE AXIF ENTRY.

User information: Required data missing from the Bulk Data Section.

Main Index
 MSC Nastran Error Messages 321
Errors 4000 - 4999

4059.0 *** USER FATAL MESSAGE 4059 (IFP4)

THE FLUID BULK MODULUS HAS NOT BEEN SPECIFIED ON A CFLUID ENTRY WITH ID =
%1 AND THERE IS NO DEFAULT ON THE AXIF ENTRY.

User information: Required data missing from the Bulk Data Section.

4060.0 *** SYSTEM FATAL MESSAGE 4060 (BMG)

COORDINATE SYSTEM = %1 CAN NOT BE FOUND IN CSTM DATA

System information: Data blocks MATPOOL or CSTM have been changed illegally.

4062.0 *** USER FATAL MESSAGE 4062 (IFP4)

DMIG BULK DATA ENTRY SPECIFIES DATA BLOCK %1 WHICH ALSO APPEARS ON A
DMIAX ENTRY.

User information: One direct input matrix may not be specified by both types of bulk data entries.

4081.0 *** USER FATAL MESSAGE 4081 (IFP5)

AXSLOT ENTRY IS NOT PRESENT OR IS INCORRECT.

User information: Acoustic analysis data is present and this entry is necessary.

4086.0 *** USER FATAL MESSAGE 4086 (IFP5)

CELAS2 BULK DATA ENTRY HAS ID =%1 WHICH IS GREATER THAN 10000000 AND
10000000 IS THE LIMIT FOR CELAS2 ID WITH ACOUSTIC ANALYSIS ENTRIES PRESENT.

User information: The program is generating CELAS2 entries and a possible conflict of ID numbers exists.

4087.0 *** USER FATAL MESSAGE 4087 (IFP5)

SLBDY ID =%1 DOES NOT APPEAR ON ANY GRIDS ENTRIES.

User information: The SLBDY entry has a point listed which does not exist in the data.

4088.0 *** USER FATAL MESSAGE 4088 (IFP5)

Main Index
 322 MSC Nastran Error Messages
Errors 4000 - 4999

ONE OR MORE OF THE FOLLOWING ID-S NOT EQUAL TO -1 HAVE INCORRECT OR NO

GEOMETRY DATA
ID = %1 ID = %2 ID = %3

User information: The listed GRIDS points may have a bad radius or a slot width greater than geometri-
cally possible.

4089.0 *** USER FATAL MESSAGE 4089 (IFP5)

RHO AS SPECIFIED ON SLBDY OR AXSLOT ENTRY IS 0.0 FOR ID =%1

User information: A value of density is required to formulate the slot boundary matrix terms.

4090.0 *** USER FATAL MESSAGE 4090 (IFP5)

ONE OF THE FOLLOWING NON-ZERO IDENTIFICATION NUMBERS APPEARS ON SOME
COMBINATION OF GRID, GRIDS, OR GRIDF BULK DATA ENTRIES. ID=%1 ID=%2 ID=%3

User information: All GRID, SPOINT, EPOINT, GRIDS, and GRIDF data entries should have unique
identification numbers.

4101.0 *** SYSTEM FATAL MESSAGE 4101

PMTPCH UNABLE TO FIND NAME FOR DATA BLOCK %1

4101.1 *** SYSTEM FATAL MESSAGE 4101

MATPCH UNABLE TO FIND NAME FOR DATA BLOCK %1

4103.0 *** USER INFORMATION MESSAGE 4103

PMTPCH HAS PUNCHED MATRIX DATA BLOCK %1 ONTO %2 DMI CARDS.

4103.1 *** USER INFORMATION MESSAGE 4103

MATPCH HAS PUNCHED MATRIX DATA BLOCK %1 ONTO %2 DMI CARDS.

4104.0 *** USER FATAL MESSAGE 4104

ATTEMPT TO PUNCH MORE THAN 99999 DMI CARDS FOR A SINGLE MATRIX.

4105.0 *** USER INFORMATION MESSAGE 4105 (LDINPT)

Main Index
 MSC Nastran Error Messages 323
Errors 4000 - 4999

DATA BLOCK %1 RETRIEVED FROM FORTRAN UNIT %2

NAME OF DATA BLOCK WHEN PLACED ON FORTRAN UNIT WAS %3.

User information: As each block is retrieved, its new and old names are printed. Check to be sure your
unit/DMAP are together.

4105.1 *** USER INFORMATION MESSAGE 4105 (LDINPT)

DATA BLOCK %1 RETRIEVED FROM FORTRAN UNIT %2 (GENERATED IN %4 FORMAT)
NAME OF DATA BLOCK WHEN PLACED ON FORTRAN UNIT WAS %3.

User information: As each block is retrieved, its new and old names are printed. Check to be sure your
unit/DMAP are together.

4105.2 *** USER INFORMATION MESSAGE 4105 (INPTX2)

DATA BLOCK %1 RETRIEVED FROM FORTRAN UNIT %2 (GENERATED IN %4 FORMAT)
USING NDDL DESCRIPTION FOR %5 NAME OF DATA BLOCK WHEN PLACED ON FOR-
TRAN UNIT WAS %3.

User information: As each block is retrieved, its new and old names are printed. Check to be sure your
unit/DMAP are together.

4105.3 *** USER INFORMATION MESSAGE 4105 (INPTX2)

DATA BLOCK %1 RETRIEVED FROM FORTRAN UNIT %2 (GENERATED IN %4 FORMAT)
IN %5 FORMAT NAME OF DATA BLOCK WHEN PLACED ON FORTRAN UNIT WAS %3.

User information: As each block is retrieved, its new and old names are printed. Check to be sure your
unit/DMAP are together.

4106.0 *** USER INFORMATION MESSAGE 4106 (OUTPT4)

DATA BLOCK %1 WRITTEN ON FORTRAN UNIT %2 FROM DMAP MODULE OUTPUT4 IN
%3 FORMAT %4
TRAILER= %5 %6 %7 %8 %9 %10 %11
NAME OF DATA BLOCK WRITTEN ON FORTRAN UNIT IS %12

4108.0 *** SYSTEM FATAL MESSAGE 4108 (LDINPT)

MODULE DBLOAD UNABLE TO OPEN OUTPUT DATA BLOCK %1

Main Index
 324 MSC Nastran Error Messages
Errors 4000 - 4999

4108.1 *** SYSTEM FATAL MESSAGE 4108

MODULE %1 UNABLE TO OPEN OUTPUT DATA BLOCK %2

4109.0 *** USER INFORMATION MESSAGE 4109 (UNPHDR)

THE LABEL IS %1 FOR NEUTRAL FILE FORTRAN UNIT %2

4109.2 *** USER INFORMATION MESSAGE 4109

THE LABEL IS %1 FOR FORTRAN UNIT %2
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%3 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%4 RECORDS.)
(TOTAL DATA WRITTEN FOR LABEL =%5 WORDS.)

4109.3 *** USER INFORMATION MESSAGE 4109

THE LABEL IS %1 FOR FORTRAN UNIT %2, WITH SUFFIX FILE NAME, %3
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%4 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%5 RECORDS.)
(TOTAL DATA WRITTEN FOR LABEL =%6 WORDS.)

4110.0 *** USER INFORMATION MESSAGE 4110 (UNDRVR)

END-OF-DATA SIMULATION ON NEUTRAL FILE FORTRAN UNIT %1

4110.1 *** USER INFORMATION MESSAGE 4110 (OUTPX2)

END-OF-DATA SIMULATION ON FORTRAN UNIT %1
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%2 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%3 RECORDS.)
(TOTAL DATA WRITTEN FOR EOF MARKER =%4 WORDS.)

4110.2 *** USER INFORMATION MESSAGE 4110 (OUTPN2)

END-OF-DATA SIMULATION ON FORTRAN UNIT %1
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%2 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%3 RECORDS.)
(TOTAL DATA WRITTEN FOR EOF MARKER =%4 WORDS.)

4110.3 *** USER INFORMATION MESSAGE 4110 (OUTPN2)

Main Index
 MSC Nastran Error Messages 325
Errors 4000 - 4999

END-OF-DATA SIMULATION ON FORTRAN UNIT %1, CONNECTED TO FILE WITH SUF-

FIX NAME: %2
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%3 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%4 RECORDS.)
(TOTAL DATA WRITTEN FOR EOF MARKER =%5 WORDS.)

4113.0 *** USER FATAL MESSAGE 4113

MODULE %1 - ILLEGAL VALUE FOR FIRST PARAMETER = %2

User information: See the MSC NASTRAN DMAP Programmers Guide.

4114.0 *** USER INFORMATION MESSAGE 4114

DATA BLOCK %1 WRITTEN TO NEUTRAL FILE FORTRAN UNIT %2 TRL = %3

User information: This message is issued for each non-purged data block as it is written.

4114.1 *** USER INFORMATION MESSAGE 4114

DATA BLOCK %1 WRITTEN TO NEUTRAL FILE FORTRAN UNIT %2

4114.11 *** USER INFORMATION MESSAGE 4114

DATA BLOCK %1 WRITTEN ON FORTRAN UNIT %2, TRL = %3
NAME OF DATA BLOCK WRITTEN ON FORTRAN UNIT IS %8.
(MAXIMUM POSSIBLE FORTRAN RECORD SIZE =%4 WORDS.)
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%5 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%6 RECORDS.)
(TOTAL DATA WRITTEN FOR DATA BLOCK =%7 WORDS.)

4114.12 *** USER INFORMATION MESSAGE 4114

DATA BLOCK %1 WRITTEN ON FORTRAN UNIT %2, CONNECTED TO FILE WITH SUFFIX
NAME %3, TRL = %4
(MAXIMUM POSSIBLE FORTRAN RECORD SIZE =%5 WORDS.)
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%6 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%7 RECORDS.)
(TOTAL DATA WRITTEN FOR DATA BLOCK =%8 WORDS.)

4114.13 *** USER INFORMATION MESSAGE 4114

Main Index
 326 MSC Nastran Error Messages
Errors 4000 - 4999

DATA BLOCK %1 WRITTEN ON FORTRAN UNIT %2 IN %9 FORMAT USING NDDL

DESCRIPTION FOR %10, TRL = %3
NAME OF DATA BLOCK WRITTEN ON FORTRAN UNIT IS %8
(MAXIMUM POSSIBLE FORTRAN RECORD SIZE =%4 WORDS.)
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%5 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%6 RECORDS.)
(TOTAL DATA WRITTEN FOR DATA BLOCK =%7 WORDS.)

4114.14 *** USER INFORMATION MESSAGE 4114

DATA BLOCK %1 WRITTEN ON FORTRAN UNIT %2 IN %9 FORMAT AND IN %10 FOR-
MAT, TRL = %3
NAME OF DATA BLOCK WRITTEN ON FORTRAN UNIT IS %8
(MAXIMUM POSSIBLE FORTRAN RECORD SIZE =%4 WORDS.)
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%5 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%6 RECORDS.)
(TOTAL DATA WRITTEN FOR DATA BLOCK =%7 WORDS.)

4114.15 *** USER INFORMATION MESSAGE 4114

DATA BLOCK %1 WRITTEN ON FORTRAN UNIT %2 IN %9 FORMAT (NDDL DESCRIP-
TION FOR %10 NOT FOUND), TRL = %3
NAME OF DATA BLOCK WRITTEN ON FORTRAN UNIT IS %8
(MAXIMUM POSSIBLE FORTRAN RECORD SIZE =%4 WORDS.)
(MAXIMUM SIZE OF FORTRAN RECORDS WRITTEN =%5 WORDS.)
(NUMBER OF FORTRAN RECORDS WRITTEN =%6 RECORDS.)
(TOTAL DATA WRITTEN FOR DATA BLOCK =%7 WORDS.)

4115.0 *** SYSTEM FATAL MESSAGE 4115 (OUTPX2)

MODULE %1 - SHORT REC.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

4116.0 *** SYSTEM FATAL MESSAGE 4116

MODULE DBUNLOAD UNABLE TO OPEN INPUT DATABLOCK %1

4116.4 *** SYSTEM FATAL MESSAGE 4116 (OUTPX2)

Main Index
 MSC Nastran Error Messages 327
Errors 4000 - 4999

MODULE %1 UNABLE TO OPEN INPUT DATA BLOCK %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

4116.5 *** SYSTEM FATAL MESSAGE 4116 (OUTPN2)

MODULE OUTPUT2 UNABLE TO OPEN INPUT DATABLOCK %1

4117.0 *** SYSTEM WARNING MESSAGE 4117 (OUTPN2)

THE LABEL WAS NOT DETECTED ON FORTRAN UNIT= %1

4120.0 *** USER FATAL MESSAGE 4120 (OUTPX2)

MODULE %1 - ILLEGAL VALUE FOR FIRST PARAMETER =%2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

User information: See the MSC NASTRAN DMAP Programmers Guide.

4121.0 *** USER FATAL MESSAGE 4121 (IFS4P)

ONLY ONE (1) AXIF ENTRY ALLOWED IN BULK DATA.

User information: See Bulk Data Description in chapter 5 of the MSC NASTRAN Quick Reference.

4122.0 *** USER FATAL MESSAGE 4122 (IFS4P)

AXIF BULK DATA ENTRY NOT FOUND.

4123.0 *** USER FATAL MESSAGE 4123 (IFS4P)

ONLY ONE (1) FLSYM ENTRY ALLOWED IN BULK DATA.

User information: See Bulk Data Description in chapter 5 of the MSC NASTRAN Quick
Reference Guide.

4124.0 *** USER WARNING MESSAGE 4124 (IFS3P)

Main Index
 328 MSC Nastran Error Messages
Errors 4000 - 4999

THE SPCADD OR MPCADD UNION CONSISTS OF A SINGLE SET.

User information: Only one SET was on an SPCADD or MPCADD entry. There are no sets
to add together.

4125.0 *** USER FATAL MESSAGE 4125 (IFS4P)

MAXIMUM ALLOWABLE HARMONIC ID IS 99. ENTRY CONTAINS MAXIMUM = %1

User information: See Bulk Data Description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

4126.0 *** USER FATAL MESSAGE 4126 (IFS4P)

BAD DATA OR FORMAT OR NON-UNIQUE NAME, DMIAX %1

User information: See Bulk Data Description in chapter 5 of the MSC NASTRAN Quick Reference
Guide.

4130.0 *** USER FATAL MESSAGE 4130 (OUTPX2)

MODULE %1 - ILLEGAL LABEL HEADER = %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

4131.0 *** USER WARNING MESSAGE 4131 (OUTPX2)

FORTRAN DATABLOCK NAME -%1- DOES NOT MATCH THIRD %2 DMAP PARAMETER -
%3-.

4134.0 *** USER FATAL MESSAGE 4134 (INPTX2)

MODULE %1 - ILLEGAL LABEL HEADER = %2

4135.0 *** USER WARNING MESSAGE 4135 (INPTX2)

USER DATABLOCK NAME -%1- DOES NOT MATCH THIRD %2 DMAP PARAMETER -%3-.

4136.0 *** USER FATAL MESSAGE 4136 (INPTX2)

USER DATABLOCK NAME -%1- DOES NOT MATCH THIRD %2 DMAP PARAMETER -%3-.

4137.0 *** USER WARNING MESSAGE 4137 (INPTX2)

ALL OUTPUT DATA BLOCKS FOR INPUTT2 ARE PURGED.

Main Index
 MSC Nastran Error Messages 329
Errors 4000 - 4999

4138.0 *** USER WARNING MESSAGE 4138 (INPTX2)

DATA BLOCK %1 (DATA BLOCK COUNT = %2) HAS PREVIOUSLY BEEN RETRIEVED FROM
FORTRAN UNIT %3 AND WILL BE IGNORED.

4139.0 *** USER INFORMATION MESSAGE 4139 (INPTX2)

DATA BLOCK %1 RETRIEVED FROM FORTRAN UNIT %2 (DATA BLOCK COUNT = %3)

4140.0 *** USER WARNING MESSAGE 4140 (INPTX2)

SECONDARY VERSION OF DATA BLOCK HAS REPLACED EARLIER ONE.

4141.0 *** USER WARNING MESSAGE 4141 (INPTX2)

ONE OR MORE DATA BLOCKS NOT FOUND ON FORTRAN UNIT.

4142.0 *** USER FATAL MESSAGE 4142 (INPTX2)

ONE OR MORE DATA BLOCKS NOT FOUND ON FORTRAN UNIT.

4143.0 *** SYSTEM FATAL MESSAGE 4143.

SEMAP WAS GENERATED ON A PRIOR RELEASE. IT MUST BE REGENERATED ON THIS
RELEASE.

System information: Format of SEMAP was changed between releases (Versions of MSC NASTRAN).
Execute SEP1 in order to generate a new SEMAP.

4144.0 *** SYSTEM WARNING MESSAGE 4144 (TABFM6)

TABPRT module is unable to print %1 with NDDL labels because there is no NDDL description for %2.
TABPT module's format will be used to print the table.

4148.0 *** USER INFORMATION MESSAGE 4148---

CSUPER%1 HAS BEEN WRITTEN ON UNIT%2, NUMBER OF CARD IMAGES=%3

User information: This message indicates the number of CSUPER entries punched by the TABPRT mod-
ule.

4149.0 *** USER WARNING MESSAGE 4149---

Main Index
 330 MSC Nastran Error Messages
Errors 4000 - 4999

MORE THAN 1000 CARD IMAGES ENCOUNTED IN PUNCHING CSUPER%1 ON UNIT%2

ONLY 1000 WERE PUNCHED.

User information: An attempt has been made to punch more than 1000 CSUPER entries
(8000 grid points on the boundary).

4150.0 *** USER INFORMATION MESSAGE 4150 (CGTEMS)

INSUFFICIENT MEMORY AVAILABLE FOR STORAGE OF ALL ELEMENT MATRICES AND
SPILL OCCURS AT ELEMENT %1 OF %2

User information: ELEMENT MATRICES WILL BE PROCESSED FROM BOTH MEMORY AND
DATABASE FILES.

4152.0 *** USER FATAL MESSAGE 4152 (G4COLT)

DIFFERENT VALUES OF ENFORCED MOTION ARE PRESCRIBED ON MORE THAN ONE
%1 ENTRY FOR THE SAME GRID ID = %2 AND COMPONENT = %3.

User information: THE VALUES SPECIFIED ARE %4 (OLD) AND %5 (NEW).

4152.1 *** USER WARNING MESSAGE 4152 (G4COLT)

DUPLICATE VALUES OF ENFORCED MOTION ARE PRESCRIBED ON MORE THAN ONE
%1 ENTRY FOR THE SAME GRID ID = %2 AND COMPONENT = %3.

User information: THE REDUNDANT SPECIFICATION OF %4 WILL BE IGNORED.

4153.0 *** USER INFORMATION MESSAGE 4153.

LEFT HANDED FBS TIME ESTIMATE TO FORM %1 CPU=%2, I/O=%3, TOTAL=%4,
PASSES=%5

4153.1 *** USER INFORMATION MESSAGE 4153.

FBS METHOD %1 TIME ESTIMATE TO FORM %2 - CPU=%3, I/O=%4, TOTAL=%5,
PASSES=%6

User information: I/O seconds are equivalent to CPU seconds based on the estimated number of blocks to
be transferred between main and secondary storage and the blocks per second rate. Seconds printed is the
sum of CPU and I/O. This message is printed when the time estimate is greater than the contents of SYS-
TEM(20).

Main Index
 MSC Nastran Error Messages 331
Errors 4000 - 4999

4154.0 *** USER WARNING MESSAGE 4154 (SEP1C)

SEELT ENTRY REFERENCES UNDEFINED SUPERELEMENT %1. ELEMENT ASSIGNMENTS
ARE IGNORED.

User information: Element reassignment specified by SEELT entry not possible because
superelement specified does not exist.

4155.0
CONFORMITY CHECKS NOT MADE.

4155.1 *** USER WARNING MESSAGE 4155.

GRID POINTS FOR PRIMARY SUPER ELEMENT%1 WHICH IS REFERENCED BY SECOND-
ARY%2 ARE COLLINEAR. CONFORMITY CHECKS NOT MADE.

4156.0 *** USER FATAL MESSAGE 4156.

DIMENSIONS OR TYPE OF DATA BLOCK %1, SUPERELEMENT %2 TRAILER=(%3) ARE
INCONSISTENT WITH SUPERELEMENT MAP.

User information: The referenced superelement matrix is not consistent with the new
superelement map. Request SEALL for the superelement.

4157.1 *** USER INFORMATION MESSAGE 4157 (DFMSA) ---

PARAMETERS FOR SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2) FOLLOW
MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS
NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6

4157.2 *** SYSTEM INFORMATION MESSAGE 4157 (SITDRV)

Main Index
 332 MSC Nastran Error Messages
Errors 4000 - 4999

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA
BLOCK %1(TYPE = %2) FOLLOW
MATRIX SIZE =%3 ROWS DENSITY =%4
STRING LENGTH =%5 AVG NUMBER OF STRINGS =%6 K
NONZERO TERMS =%7 K FULL BAND WIDTH =%8 AVG
MEMORY AVAILABLE =%9 K WORDS MIN MEMORY NEEDED =%10 K WORDS
NUMBER OF RHS =%11 NUMBER OF PASSES =%12
OPTIMAL MEMORY =%13 K WORDS PREFACE CPU TIME =%14 SECONDS

System information: This information is useful in optimizing the performance of your run. When spill is
indicated, the model is too large to fit into memory. The job may run faster by increasing the available
memory (this will decrease the number of spill group). See the MSC NASTRAN Installation and Opera-
tion Instructions for a description of these terms. See also the MSC NASTRAN Numerical
Methods User's Guide.

4157.3 *** SYSTEM INFORMATION MESSAGE 4157 (SITDRV)

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA
BLOCK %1(TYPE = %2) FOLLOW
MATRIX SIZE =%3 ROWS DENSITY =%4
GEOMETRIC DOFS =%5 HIERARCHIC DOFS =%6
STRING LENGTH =%7 AVG NUMBER OF STRINGS =%8 K
NONZERO TERMS =%9 K FULL BAND WIDTH =%10 AVG
MEMORY AVAILABLE =%11 K WORDS MIN MEMORY NEEDED =%12 K WORDS
NUMBER OF RHS =%13 NUMBER OF PASSES =%14
OPTIMAL MEMORY =%15 K WORDS PREFACE CPU TIME =%16 SECONDS

System information: This information is useful in optimizing the performance of your run.
When spill is indicated, the model is too large to fit into memory. The job may run faster by increasing the
available memory (this will decrease the number of spill groups). See the MSC NASTRAN Installation and
Operation Instructions for a description of these terms. See also the MSC NASTRAN Numerical Methods
User's Guide.

4157.4 *** USER INFORMATION MESSAGE 4157---

Main Index
 MSC Nastran Error Messages 333
Errors 4000 - 4999

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA

BLOCK %1(TYPE = %2) FOLLOW
MATRIX SIZE =%3 ROWS DENSITY =%4
NONZERO TERMS =%5 K NUMBER OF RHS =%6
MEMORY AVAILABLE =%7 K WORDS MIN MEMORY NEEDED =%8 K WORDS

User information: This information is useful in optimizing the performance of your run. When spill is
indicated, the model is too large to fit into memory. The job may run faster by increasing the available
memory (this will decrease the number of spill groups). See the MSC NASTRAN Installation and Opera-
tion Instructions for a description of these terms. See also the MSC NASTRAN Numerical Methods User's
Guide.

4157.5 *** SYSTEM INFORMATION MESSAGE 4157 (SITDR3)

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA BLOCK %1(TYPE = %2) FOL-
LOW
MATRIX SIZE =%3 ROWS DENSITY =%4
STRING LENGTH =%5 AVG NUMBER OF STRINGS =%6 K
NONZERO TERMS =%7 K FULL BAND WIDTH =%8 AVG
MEMORY AVAILABLE =%9 K WORDS IPAD =%10
NUMBER OF RHS =%11

System information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical Methods User's Guide.

4157.6 *** USER INFORMATION MESSAGE 4157---

Main Index
 334 MSC Nastran Error Messages
Errors 4000 - 4999

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA

BLOCK %1(TYPE = %2) FOLLOW
MATRIX SIZE =%3 ROWS DENSITY =%4
NONZERO TERMS =%5 K FULL BAND WIDTH =%6 AVG
MEMORY AVAILABLE =%7 K WORDS PREFACE CPU TIME =%8 SECONDS
NUMBER OF RHS =%9 NUMBER OF PASSES =%10

User information:
When spill is indicated, the model is too large to fit into memory. The job may run faster by increasing the
available memory (this will decrease the number of spill groups). See the MSC NASTRAN Installation and
Operation Instructions for a description of these terms. See also the MSC NASTRAN Numerical Methods
User's Guide.

4157.7 *** USER INFORMATION MESSAGE 4157---

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA
BLOCK %1(TYPE = %2) FOLLOW
MATRIX SIZE =%3 ROWS DENSITY =%4
NONZERO TERMS =%5 K FULL BAND WIDTH =%6 AVG
MEMORY AVAILABLE =%7 K WORDS IPAD =%8
NUMBER OF RHS =%9

User information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical
Methods User's Guide.

4157.8 *** USER INFORMATION MESSAGE 4157

PARAMETERS FOR THE DISTRIBUTED ITERATIVE SOLUTION WITH DATA BLOCK
%1(TYPE = %2) FOLLOW:

4157.9 *** USER INFORMATION MESSAGE 4157---

Main Index
 MSC Nastran Error Messages 335
Errors 4000 - 4999

PARAMETERS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3( TYPE=%4) FOLLOW

MATRIX SIZE =%5 ROWS CPU TIME ESTIMATE =%6 SECONDS
ADDITIONAL MEMORY =%7 K WORDS PASSIVE COLUMNS =%8 GROUPS
ACTIVE COLUMNS =%9 MAX PASSIVE COLUMNS =%10 MAX
ACTIVE COLUMNS =%11 RMS PASSIVE COLUMNS =%12 AVG
SPILL =%13 GROUPS I/O TIME ESTIMATE =%14 SECONDS
SPILL ROWS =%15 AVG NZ NBR IN FACTOR =%16 K TERMS
FACTOR STRNG LGTH =%17 AVG FACTOR STRNG SUM =%18 STRINGS

User information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical Methods User's Guide.

4157.10 *** USER INFORMATION MESSAGE 4157---

PARAMETERS FOR PARALLEL %1DECOMPOSITION OF DATA BLOCK %2( TYPE=%3) FOL-
LOW
MATRIX SIZE =%4 ROWS CPU TIME ESTIMATE =%5 SEC
MAX.HALFBANDWIDTH =%6 TERMS I/O TIME ESTIMATE =%7 SEC
AVG.HALFBANDWIDTH =%8 TERMS ROLLING (0=N/1=Y) =%9
iN-SKYLINE ELE. =%10 K TERMS REQUESTED PROC. =%11 CPUS
REQUI. WORK MEMORY =%12 K WORDS AVAIL. WORK MEMORY =%13 K WORDS

User information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical Methods User's Guide.

4157.11 *** USER INFORMATION MESSAGE 4157---

Main Index
 336 MSC Nastran Error Messages
Errors 4000 - 4999

PARAMETERS FOR PARALLEL %1DECOMPOSITION OF DATA BLOCK %2( TYPE=%3) FOL-

LOW
MATRIX SIZE =%4 ROWS CPU TIME ESTIMATE =%5 SEC
MAX.HALFBANDWIDTH =%6 TERMS I/O TIME ESTIMATE =%7 SEC
AVG.HALFBANDWIDTH =%8 TERMS ROLLING (0=N/1=Y) =%9
IN-SKYLINE ELE. =%10 TERMS REQUESTED PROC. =%11 CPUS
REQUI. WORK MEMORY =%12 K WORDS AVAIL. WORK MEMORY =%13 K WORDS

User information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical Methods User's Guide.

4157.12 *** USER INFORMATION MESSAGE 4157 (DFMSA) ---

PARAMETERS FOR PARALLEL SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2)
FOLLOW
MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS
NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6
SYSTEM (107) =%7 REQUESTED PROC. =%8 CPUS

User information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical Methods User's Guide.

4157.13 *** USER INFORMATION MESSAGE 4157 ---

PARAMETERS FOR SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2) FOLLOW
MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS
NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6

User information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical Methods User's Guide.

4157.16 *** SYSTEM INFORMATION MESSAGE 4157 (PDDRV)

Main Index
 MSC Nastran Error Messages 337
Errors 4000 - 4999

LOCAL PARAMETERS AND TIMINGS FOR THE DISTRIBUTED PARALLEL SPARSE DECOM-
POSITION

4157.17 *** SYSTEM INFORMATION MESSAGE 4157 (DFMSAP)

PARAMETERS FOR PARALLEL SPARSE DECOMPOSITION OF DATA BLOCK %1( TYPE=%2)
FOLLOW
MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS
NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6
SYSTEM (231) =%7 REQUESTED PROC. =%8 CPUS

4157.18 *** SYSTEM INFORMATION MESSAGE 4157 (SITDRV)

PARAMETERS FOR THE ITERATIVE SOLUTION WITH DATA
BLOCK %1(TYPE = %2) FOLLOW
MATRIX SIZE =%3 ROWS DENSITY =%4
STRING LENGTH =%5 AVG NUMBER OF STRINGS =%6 K
NONZERO TERMS =%7 K FULL BAND WIDTH =%8 AVG
MEMORY AVAILABLE =%9 K WORDS MIN MEMORY NEEDED =%10 K WORDS
NUMBER OF RHS =%11 NUMBER OF PASSES =%12
OPTIMAL MEMORY =%13 K WORDS PREFACE CPU TIME =%14 SECONDS
IPAD =%15 IEXT =%16

System information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory (this will decrease the number of spill groups). See the MSC
NASTRAN Installation and Operation Instructions for a description of these terms. See also the MSC
NASTRAN Numerical Methods User's Guide.

4157.19 *** SYSTEM INFORMATION MESSAGE 4157 (FBSTIM)

TIMING DETAILS FOR FBS METHOD 2
COLSB=%1, TERMSL=%2, FWDFAC=%3, TEMP1=%4, TEMP2=%5, ARITH=%6

4157.20 ***SYSTEM INFORMATION MESSAGE 4157

P/C GROUPS FOLLOW..

4157.21 *** SYSTEM INFORMATION MESSAGE 4157

SPILL GROUPS FOLLOW..

Main Index
 338 MSC Nastran Error Messages
Errors 4000 - 4999

4157.22
ARITH=%1 IOA =%2
SPILL=%3 IOSPL=%4 NBR SPILL ROWS=%5
P/C =%6 IOP/C=%7
IOCPU=%8 IOL =%9

4157.23
ELAPSED CPU I/O (MB)
LMT Phase 1: %1 %2 %3
LMT Phase 2: %4 %5 %6
LMT TOTALS: %7 %8 %9

4157.24 *** USER WARNING MESSAGE 4157---

MEMORY PARAMETERS FOR INTEL MKL PARDISO PARALLEL DECOMPOSITION FOLLOW
AVAIL. WORK MEMORY =%1 MB
REQUI. IN-CORE MEMORY =%2 MB REQUI. OUT-OF-CORE MEMORY =%3 MB

User information: When spill is indicated, the model is too large to fit into memory. The job may run
faster by increasing the available memory. See the MSC NASTRAN Installation and Operation Instruc-
tions for a
description of these terms. See also the MSC NASTRAN Numerical Methods User's Guide.

4157.25 *** USER WARNING MESSAGE 4157---

INSUFFICIENT MEMORY FOR INTEL MKL PARDISO, SWITCHING TO MSCLDL SPARSE
SOLVER.

User information: Use the Pardiso minimum memory requirement values to increase memory
using 'mem=' on the submittal line.

4157.26 *** USER WARNING MESSAGE 4157---

INSUFFICIENT MEMORY FOR INTEL MKL PARDISO, SWITCHING TO MSCLDL/MSCLU
SPARSE SOLVER.

User information: Use the Pardiso minimum memory requirement values to increase memory using
'mem=' on the submittal line.

4158.0 *** USER INFORMATION MESSAGE 4158---

Main Index
 MSC Nastran Error Messages 339
Errors 4000 - 4999

STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW

NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL =%4

4158.1 *** USER INFORMATION MESSAGE 4158---

STATISTICS FOR PARALLEL %1 DECOMPOSITION OF DATA BLOCK %2

4158.2 *** USER INFORMATION MESSAGE 4158 (DFMSA)

---- STATISTICS FOR SPARSE DECOMPOSITION OF DATA BLOCK %1 FOLLOW
NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL = %2
MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL = %3 AT ROW NUM-
BER %4

User information: One, two or three of the statistics will be printed as follows:
1. negative terms on factor diagonal only if they exist;
2. maximum ratio only if it exceeds a threshold defined by the parameter MAXRATIO (default 1.0E7);
3. spill rows only if the problem spills.
Depending on the context, these messages may indicate modeling problems. The threshold may be changed
with the parameter MAXRATIO, however, the user is cautioned against arbitrarily increasing the
MAXRATIO value just to get the model to run. The cause of large MAXRATIOs should be investigated.
This message is also generated (though the text is slightly different) when a Sturm check is performed
during eigenvalue extraction. For this case, the message does not generally indicate a modeling problem. See
the MSC NASTRAN Installation and Operation Instructions for a discussion of these statistics. See also
the MSC NASTRAN Numerical Methods User's Guide.

4158.3 *** SYSTEN INFORMATION MESSAGE 4158.

SPILL I/O =%1 SEC

4158.4 *** USER INFORMATION MESSAGE 4158 (SDCBOD)

STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW

Main Index
 340 MSC Nastran Error Messages
Errors 4000 - 4999

MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL =%4 AT ROW NUM-

BER %5

User information: One, two or three of the statistics will be printed as follows:
1. negative terms on factor diagonal only if they exist;
2. maximum ratio only if it exceeds a threshold defined by the parameter MAXRATIO (default 1.0E7);
3. spill rows only if the problem spills.
Depending on the context, these messages may indicate modeling problems. The threshold may be changed
with the parameter MAXRATIO, however, the user is cautioned against arbitrarily increasing the MAXRA-
TIO value just to get the model to run. The cause of large MAXRATIOs should be investigated. This mes-
sage is also generated (though the text is slightly different) when a Sturm check is performed during
eigenvalue extraction. For this case, the message does not generally indicate a modeling problem. See the
MSC NASTRAN Installation and Operation Instructions for a discussion of these statistics. See also the
MSC NASTRAN Numerical Methods User's Guide.

4158.5 *** USER INFORMATION MESSAGE 4158 (SDCBOD)

STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW
NUMBER OF ROWS WRITTEN TO SPILL FILE =%4, RATIO =%5

4158.6 *** USER INFORMATION MESSAGE 4158 (SDCBOD)

STATISTICS FOR %1E%2 DECOMPOSITION OF DATA BLOCK %3 FOLLOW
NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL =%4
MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL =%5 AT ROW NUM-
BER %6

User information: One, two or three of the statistics will be printed as follows:
1. negative terms on factor diagonal only if they exist;
2. maximum ratio only if it exceeds a threshold defined by the parameter MAXRATIO (default 1.0E7);
3. spill rows only if the problem spills.
Depending on the context, these messages may indicate modeling problems. The threshold may be changed
with the parameter MAXRATIO, however, the user is cautioned against arbitrarily increasing the
MAXRATIO value just to get the model to run. The cause of large MAXRATIOs should be investigated.
This message is also generated (though the text is slightly different) when a Sturm check is performed
during eigenvalue extraction. For this case, the message does not generally indicate a modeling problem. See
the MSC NASTRAN Installation and Operation Instructions for a discussion of these statistics. See also
the MSC NASTRAN Numerical Methods User's Guide.

Main Index
 MSC Nastran Error Messages 341
Errors 4000 - 4999

4159.0 *** SYSTEM INFORMATION MESSAGE 4159 (dfmsa)

THE DECOMPOSITION OF %1 YIELDS A MAXIMUM MATRIX-TO-FACTOR-DIAGONAL
RATIO OF %2

4160.0 *** SYSTEM WARNING MESSAGE 4160 (PNCHGRPDRV):

MPI GROUP WITH LABEL %1 DOES NOT EXIST.

User information: THE MPI GROUP DEFINES THE PARALLEL MESSAGE PASSING CONTEXT.
THE DEFAULT GROUP CONTAINING ALL PROCESSORS HAS THE LABEL "WORLD". ADDI-
TIONAL GROUPS MAY BE CREATED USING THE PNMKGRP MODULE.

User action : IF YOU ARE USING THE PNCHGRP MODULE IN A DMAP ALTER, VERIFY THAT
ANY GROUPS ASSOCIATED WITH THE GROUP LABELS WERE SUCCESSFULLY CREATED
USING THE PNMKGRP MODULE.
SET SYSTEM(294)=1 FOR MORE INFORMATION.
IF YOU WERE NOT USING THE PNCHGRP MODULE IN A DMAP ALTER, CONTACT HEXA-
GON AB CLIENT SUPPORT.

4161.0 *** SYSTEM WARNING MESSAGE 4161 (PNCHGRPDRV):

ATTEMPT TO CHANGE FROM MPI GROUP LABEL %1, WHEN THE PRESENT GROUP
LABEL IS %2.

User information: THE MPI GROUP DEFINES THE PARALLEL MESSAGE PASSING CONTEXT.
THE DEFAULT GROUP CONTAINING ALL PROCESSORS HAS THE LABEL "WORLD". ADDI-
TIONAL GROUPS MAY BE CREATED USING THE PNMKGRP MODULE.

User action : IF YOU ARE USING THE PNCHGRP MODULE IN A DMAP ALTER, VERIFY THAT
ANY GROUPS ASSOCIATED WITH THE GROUP LABELS WERE SUCCESSFULLY CREATED
USING THE PNMKGRP MODULE.
SET SYSTEM(294)=1 FOR MORE INFORMATION.
IF YOU WERE NOT USING THE PNCHGRP MODULE IN A DMAP ALTER, CONTACT HEXA-
GON AB CLIENT SUPPORT.

4162.0 *** SYSTEM FATAL MESSAGE 9100 (PNCHGRP)

Main Index
 342 MSC Nastran Error Messages
Errors 4000 - 4999

ATTEMPT TO CHANGE MPI GROUP FAILED - GROUP WITH GIVEN LABEL, "%1", DOES
NOT EXIST.

User information: THE MPI GROUP DEFINES THE PARALLEL MESSAGE PASSING CONTEXT.
THE DEFAULT GROUP CONTAINING ALL PROCESSORS HAS THE LABEL "WORLD". ADDI-
TIONAL GROUPS MAY BE CREATED USING THE PNMKGRP MODULE.

User action : IF YOU ARE USING THE PNCHGRP MODULE IN A DMAP ALTER, VERIFY THAT
ANY GROUPS ASSOCIATED WITH THE GROUP LABEL "%1" WERE SUCCESSFULLY CRE-
ATED USING THE PNMKGRP MODULE.
SET SYSTEM(294)=1 FOR MORE INFORMATION.
IF YOU WERE NOT USING THE PNCHGRP MODULE IN A DMAP ALTER, CONTACT HEXA-
GON AB CLIENT SUPPORT.

4163.0 *** SYSTEM FATAL MESSAGE 9101 (PNMKGRP)

NOT ENOUGH PROCESSORS TO CREATED REQUESTED MPI GROUP SET WITH LABEL
%1.

User information: THE MPI GROUP DEFINES THE PARALLEL MESSAGE PASSING CONTEXT.
THE DEFAULT GROUP CONTAINING ALL PROCESSORS HAS THE LABEL "WORLD". ADDI-
TIONAL GROUPS MAY BE CREATED USING THE PNMKGRP MODULE.

User action : IF YOU ARE USING THE PNMKGRP MODULE IN A DMAP ALTER, VERIFY THAT
THE PRODUCT OF THE NUMBER OF SUBGROUPS AND THE GROUP SIZE IS NO MORE
THAN THE NUMBER OF PROCESSORS AVAILABLE IN THE PARENT GROUP. SET SYS-
TEM(294)=1 FOR MORE INFORMATION. IF YOU WERE NOT USING THE PNCHGRP MOD-
ULE IN A DMAP ALTER, CONTACT HEXAGON AB CLIENT SUPPORT.

4164.0 *** SYSTEM FATAL MESSAGE 9102 (PNMKGRP)

MAXIMUM NUMBER OF MPI GROUP SETS (%1) EXCEEDED.

User information: THE MPI GROUP DEFINES THE PARALLEL MESSAGE PASSING CONTEXT.
THE DEFAULT GROUP CONTAINING ALL PROCESSORS
HAS THE LABEL "WORLD". ADDITIONAL GROUPS MAY BE CREATED USING THE PNMK-
GRP MODULE.

User action : CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 MSC Nastran Error Messages 343
Errors 4000 - 4999

4165.0 *** SYSTEM FATAL MESSAGE 9103 (PNMKGRP)

ATTEMPT TO MAKE A NEW MPI GROUP USING A PARENT GROUP WHICH IS NOT THE
ACTIVE GROUP.

THE LABEL OF THE NEW GROUP IS "%1",

THE LABEL OF THE PARENT GROUP IS "%2", AND
THE LABEL OF THE ACTIVE GROUP IS "%3".

User information: THE MPI GROUP DEFINES THE PARALLEL MESSAGE PASSING CONTEXT.
THE DEFAULT GROUP CONTAINING ALL PROCESSORS
HAS THE LABEL "WORLD". ADDITIONAL GROUPS MAY BE CREATED USING THE PNMK-
GRP MODULE.

User action : IF YOU ARE USING THE PNMKGRP MODULE IN A DMAP ALTER, USE THE
PNCHGRP MODULE TO MAKE THE PARENT GROUP THE ACTIVE GROUP AND ALSO
VERIFY THAT THIS PROCESSOR BELONGS TO THE PARENT GROUP. IF YOU WERE NOT
USING THE PNMKGRP MODULE IN A DMAP ALTER, CONTACT HEXAGON AB CLIENT
SUPPORT.

4166.0 *** SYSTEM FATAL MESSAGE 9104 (PNMKGRP)

ATTEMPT TO MAKE A NEW MPI GROUP USING A PARENT GROUP WHICH DOES NOT
EXIST.
THE LABEL OF THE NEW GROUP IS "%1", AND
THE LABEL OF THE PARENT GROUP IS "%2".

User information: THE MPI GROUP DEFINES THE PARALLEL MESSAGE PASSING CONTEXT.
THE DEFAULT GROUP CONTAINING ALL PROCESSORS HAS THE LABEL "WORLD". ADDI-
TIONAL GROUPS MAY BE CREATED USING THE PNMKGRP MODULE.

User action : IF YOU ARE USING THE PNMKGRP MODULE IN A DMAP ALTER, VERIFY THAT
THE PARENT GROUP LABEL IS SPELLED CORRECTLY. IF SO, VERIFY THAT THE PNMK-
GRP MODULE SUCCESSFULLY CREATED THE PARENT GROUP (LABEL "%2"). IF YOU
WERE NOT USING THE PNMKGRP MODULE IN A DMAP ALTER, CONTACT HEXAGON AB
CLIENT SUPPORT.

4167.0 *** SYSTEM FATAL MESSAGE 4167 (LNNRIGL)

Main Index
 344 MSC Nastran Error Messages
Errors 4000 - 4999

ERROR RETURN FROM SPECIAL ACMS SYMBOLIC FACTORIZATION WITH ERROR FLAG =
%1.

User information: THE STANDARD SPARSE FACTORIZATION WILL BE USED INSTEAD. THE
SPECIAL ACMS FACTORIZATION IMPROVES THE PERFORMANCE OF ACMS JOBS WITH A
VERY LARGE FREQUENCY RANGE.

4167.1 *** SYSTEM FATAL MESSAGE 4167 (LNCIxD)

ERROR RETURN FROM SPECIAL ACMS %2 WITH ERROR FLAG = %1.

User action: USE THE STANDARD SPARSE FACTORIZATION AND FBS BY SPECIFYING
PARAM, MDLGDEF, 99999999

User information: THE SPECIAL ACMS FACTORIZATION IMPROVES THE PERFORMANCE

OF ACMS JOBS WITH A VERY LARGE FREQUENCY RANGE.

4168.0 *** SYSTEM FATAL MESSAGE 4168 (ELEINF/ELEMAT):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: SYNCHRONIZING ELEMENTS WHILE PROCESSING KDICT TABLE

DATA FOR INTERNAL ELEMENT NUMBER %1, PHASE = %2

Uer action: Contact MSC Technical Support.

4168.1 *** SYSTEM FATAL MESSAGE 4168 (CASMAT):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: SYNCHRONIZING MATERIALS WHILE PROCESSING MATERIAL

PROPERTY DATA FOR INTERNAL MATERIAL NUMBER %1, PHASE = %2

User action: Contact MSC Technical Support.

4168.2 *** SYSTEM FATAL MESSAGE 4168 (CASPIE):

Main Index
 MSC Nastran Error Messages 345
Errors 4000 - 4999

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: ELEMENT ID %1 (EST TABLE ELTYPE %2) COULD NOT BE FOUND
IN IMPLICIT ELEMENT ID EQUIVALENCE TABLE STORED IN MEMORY.

User action: Contact MSC Technical Support.

4168.3 *** SYSTEM FATAL MESSAGE 4168 (CASGMT):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: SYNCHRONIZING ELEMENTS WHILE PROCESSING MATERIAL

PROPERTY ID FOR IMPLICIT INTERNAL ELEMENT NUMBER %1, PHASE = %2

User action: Contact MSC Technical Support.

4168.4 *** SYSTEM FATAL MESSAGE 4168 (ELEINF,SOLVIT):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: SOLVER DOES NOT SUPPORT EST TABLE ELEMENT TYPE %1 (%2)

User action: Contact MSC Technical Support.

4168.5 *** SYSTEM FATAL MESSAGE 4168 (ELEINF):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: CANNOT LOCATE IMPLICIT ELEMENT ID %1 IN ELEMENT ID /

MATERIAL PROPERTY ID ASSOCIATION TABLES.

User action: Contact MSC Technical Support.

4168.6 *** SYSTEM FATAL MESSAGE 4168 (ELEINF):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: CANNOT LOCATE MATERIAL PROPERTY ID %1 IN ELEMENT ID /

MATERIAL PROPERTY ID ASSOCIATION TABLES FOR IMPLICIT ELEMENT ID %2

User action: Contact MSC Technical Support.

Main Index
 346 MSC Nastran Error Messages
Errors 4000 - 4999

4168.7 *** SYSTEM FATAL MESSAGE 4168 (EMTFRI):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: ERROR IN ELEMENT MATRIX TRANSFORMATION UTILITY

ENCOUNTERED FOR ELEMENT ID %1 THAT EXCEEDS THE LIMIT OF 20 ACTIVE CON-
NECTION POINTS. COUNT IS %2

User action: Contact MSC Technical Support.

4168.8 *** SYSTEM FATAL MESSAGE 4168 (EMTFRI):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: ERROR IN ELEMENT MATRIX TRANSFORMATION UTILITY

ENCOUNTERED AT LOC = %1 FOR ELEMENT ID %2

User action: Contact MSC Technical Support.

4168.9 *** SYSTEM FATAL MESSAGE 4168 (EMTFRI):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: ERROR IN ELEMENT MATRIX MATRIX TRANSFORMATION UTIL-

ITY ENCOUNTERED. MATRIX OUTPUT FORM %1 FOUND IN ELEMENT STIFFNESS
MATRIX DICTIONARY HEADER FOR ELEMENT ID %2 IS NOT ACCEPTABLE.

User action: Contact MSC Technical Support.

4168.10 *** SYSTEM FATAL MESSAGE 4168 (EMTFRM):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: ERROR IN ELEMENT MATRIX MATRIX TRANSFORMATION UTIL-

ITY ENCOUNTERED. MATRIX INPUT FORM %1 FOR ELEMENT ID %2 IS NOT ACCEPT-
ABLE. MATRIX TRANSFORMATION IS NOT POSSIBLE.

User action: Contact MSC Technical Support.

4168.11 *** SYSTEM FATAL MESSAGE 4168 (ITSCAS):

Main Index
 MSC Nastran Error Messages 347
Errors 4000 - 4999

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: CASI ERROR STATUS IS %2 SO SOLUTION IS NOT POSSIBLE.

User information: ATTEMPTING TO RECOVER.

4168.12 *** SYSTEM FATAL MESSAGE 4168 (SOLVIT):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: SOLVER DOES NOT SUPPORT %1 AND SOLUTION IS NOT POSSI-
BLE.

4168.13 *** SYSTEM FATAL MESSAGE 4168 (SOLVIT):

CASI ELEMENT-BASED ITERATIVE SOLVER LOGIC ERROR.

Programmer information: REQUESTED ELEMENT-BASED ITERATIVE SOLVER TECHNOLOGY

IS NOT SUPPORTED. PARAMETER 2 = %1, PARAMETER 13 = %2, SYSTEM(216) = %3 and
SOLUTION IS NOT POSSIBLE.

4168.14 *** SYSTEM WARNING MESSAGE 4168 (SOLVIT)

CASI ELEMENT-BASED ITERATIVE SOLVER HAS FAILED DUE TO A LOGIC ERROR.

User information: DIFFERENTIAL STIFFNESS WILL BE IGNORED AND THE ELEMENT-

BASED ITERATIVE SOLVER WILL BE ATTEMPTED.

4168.15 *** SYSTEM warning MESSAGE 4168 (SOLVIT)

CASI ELEMENT-BASED ITERATIVE SOLVER HAS FAILED DUE TO A LOGIC ERROR.

User information: THE DIRECT SOLVER WILL BE ATTEMPTED.

4168.16 *** SYSTEM warning MESSAGE 4168 (NL2QNV)

MATRIX-BASED ITERATIVE SOLVER HAS FAILED TO CONVERGE.

User information: THE DIRECT SOLVER WILL BE ATTEMPTED.

4168.17 *** SYSTEM warning MESSAGE 4168 (CEMSAD)

Main Index
 348 MSC Nastran Error Messages
Errors 4000 - 4999

CASI ITERATIVE SOLVER ELEMENT MATRIX COMBINE OPERATION HAS FAILED.

MATRIX FORM %1 HAS BEEN DETECTED AT MATRIX %2 FOR ELEMENT ID %3.

User information: ONLY MATRIX FORM=3 IS SUPPORTED. ELEMENT MATRIX COMBINE

ABORTED.

4168.18 *** SYSTEM warning MESSAGE 4168 (CEMSAD)

CASI ITERATIVE SOLVER ELEMENT MATRIX COMBINE OPERATION HAS FAILED DUE TO
ACTIVE NODE NUMBER MIS-MATCH.
NUMBER OF ACTIVE NODES (%1) AT MATRIX %2 FOR ELEMENT ID %3 DIFFERS FROM
PREVIOUS NUMBER (%4)

User information: ELEMENT MATRIX COMBINE ABORTED.

4168.19 *** SYSTEM FATAL MESSAGE 4168 (NL2QNV)

ERROR ENCOUNTERED DURING ITERATIVE SOLUTION AND RECOVERY IS NOT POSSI-
BLE.

User action: RE-RUN ANALYSIS WITH MDLPRM,USEOLD,1

4168.20 *** SYSTEM FATAL MESSAGE 4168 (NL2QNV)

UNABLE TO CONVERGE WITH ITERATIVE METHOD AND RECOVERY IS NOT POSSIBLE.

User action: INCREASE MAXIMUM NUMBER OF ITERATIONS OR USE DIRECT METHOD.

4169.0 *** USER FATAL MESSAGE 4169 (RDITER):

A CHANGE IN ITERATIVE SOLUTION METHODS HAS BEEN DETECTED ACROSS SUB-
CASES.

User information: THIS IS NOT CURRENTLY ALLOWED.

User action: MAKE SURE THAT THE SMETHOD CASE CONTROL COMMAND SELECTS ITER
BULK DATA ENTRIES THAT SPECIFY THE SAME PRE-CONDITIONER.

4170.0 *** SYSTEM INFORMATION MESSAGE 4170 (ITSCAS):

Main Index
 MSC Nastran Error Messages 349
Errors 4000 - 4999

CASI ITERATIVE SOLVER PRE-SOLUTION STATISTICS FOLLOW:

NUMBER OF NON-ZEROES IN UPPER TRIANGLE OF GLOBAL MATRIX = %1
NUMBER OF NON-ZEROES IN PRE-CONDITIONER = %2
TIME IN SECONDS REQUIRED TO ASSEMBLE GLOBAL MATRIX = %3
TIME IN SECONDS NEEDED TO CONSTRUCT PRECONDITIONER = %4
TIME IN SECONDS NEEDED TO FACTOR PRECONDITIONER = %5

4171.0 *** SYSTEM INFORMATION MESSAGE 4171 (ITSCAS):

CASI ITERATIVE SOLVER SOLUTION PROCESS STATISTICS FOLLOW FOR LOAD CASE
NUMBER: %1
TOTAL OPERATION COUNT = %2
NUMBER OF PCG ITERATIONS = %3
TIME IN SECONDS FOR CONJUGATE GRADIENT = %4
TIME IN SECONDS FOR TOTAL PCG SOLVER = %5
MEMORY REQUIRED IN MB = %6
DISK SPACE REQUIRED IN MB = %7
MATRIX-VECTOR MULTIPLY MEGAFLOP RATE = %8
PC SOLVE MEGAFLOP RATE = %9

4172.0 *** SYSTEM INFORMATION MESSAGE 4172 (ITSCAS):

CASI ITERATIVE SOLVER SOLUTION ERROR ESTIMATION STATISTICS FOLLOW FOR
LOAD CASE NUMBER: %1
INPUT ERROR CONVERGENCE EPSILON VALUE = %2
REDUCTION IN 2-NORM OF THE RESIDUAL = %3
REDUCTION IN INFINITY NORM OF THE RESIDUAL = %4
REDUCTION IN PRECONDITIONED NORM OF RESIDUAL = %5
ESTIMATE OF NORMALIZED ENERGY NORM OF ERROR = %6

4173.0 *** SYSTEM WARNING MESSAGE 4172 (FACDRVI),

ERROR IN MEMORY MANAGEMENT ROUTINES WHILE ATTEMPTING IN-CORE SPARSE
DECOMPOSITION.

User information: AN ALTERNATVE SPARSE DECOMPOSITION METHOD WILL BE

ATTEMPTED.

4174.0 *** SYSTEM WARNING MESSAGE 4174 (FACDRVI)

Main Index
 350 MSC Nastran Error Messages
Errors 4000 - 4999

ERROR IN REORDERING PHASE OF SPARSE DECOMPOSITION

User information: AN ALTERNATVE SPARSE DECOMPOSITION METHOD WILL BE

ATTEMPTED.

4174.1 *** SYSTEM WARNING MESSAGE 4174 (FACDRVI)

ERROR IN SYMBOLIC PHASE OF IN-CORE SPARSE DECOMPOSITION

User information: AN ALTERNATVE SPARSE DECOMPOSITION METHOD WILL BE

ATTEMPTED.

4174.2 *** SYSTEM WARNING MESSAGE 4174 (FACDRVI)

ERROR IN NUMERIC PHASE OF IN-CORE SPARSE DECOMPOSITION

User information: AN ALTERNATVE SPARSE DECOMPOSITION METHOD WILL BE

ATTEMPTED.

4174.3 *** SYSTEM WARNING MESSAGE 4174 (FACDRVI)

ERROR IN POST-NUMERIC PHASE OF IN-CORE SPARSE DECOMPOSITION

User information: AN ALTERNATVE SPARSE DECOMPOSITION METHOD WILL BE

ATTEMPTED.

4175.0 *** USER WARNING MESSAGE 4175 (FACDRVI)

WHILE ATTEMPTING IN-CORE SPARSE DECOMPOSITION, MATRIX IS NOT POSITIVE
DEFINITE AT ROW %1

User action: CHECK MODEL

User information: AN ALTERNATVE SPARSE DECOMPOSITION METHOD WILL BE

ATTEMPTED.

4176.0 ***USER WARNING MESSAGE 4176

BOTH the ELEMENT-based AND MATRIX-BASED ITERATIVE SOLVERS have been SELECTED.

User information: The program will switch to the MATRIX-BASED iterative SOLVER.

Main Index
 MSC Nastran Error Messages 351
Errors 4000 - 4999

4177.0 ***USER WARNING MESSAGE 4177

Lagrange multiplier TRANSFORMATION (LMT) IS being requested but ANALYSIS is not equal to
NLSTAT (nonlinear statics).

User information: LMT may only be requested with ANALYSIS=NLSTAT. Program will SWITCH TO
DEFAULT METHODS.

4178.0 ***USER WARNING MESSAGE 4178

ELEMENT-BASED ITERATIVE SOLUTION IS being requested but with ANALYSIS not equal to
NLSTAT (nonlinear statics).

User information: ELEMENT-BASED ITERATIVE SOLUTION may only be requested with ANALY-
SIS=NLSTAT.

4178.1 ***USER WARNING MESSAGE 4178

MATRIX-BASED ITERATIVE SOLUTION IS being requested but with ANALYSIS not equal to
NLSTAT (nonlinear statics).

User information: MATRIX-BASED ITERATIVE SOLUTION may only be requested with ANALY-
SIS=NLSTAT. Program will SWITCH TO THE DIRECT SOLVER.

4179.0 *** USER FATAL MESSAGE 4179 (SEPTRE)

SETREE CONTAINS NON-UNIQUE DOWNSTREAM ID-S %1 AND %2 FOR SUPERELEMENT
%3.

4179.1 *** USER FATAL MESSAGE 4179 (SEP1A)

TABLE %1 CONTAINS NON-UNIQUE DOWNSTREAM ID-S %2 AND %3 FOR SUPERELE-
MENT %4

4180.0 *** USER FATAL MESSAGE 4180---

NUMBER OF GENERALIZED COORDINATES REQUIRED IS %1
ONLY%2 GENERALIZED COORDINATES AVAILABLE

User information: An insufficient number of generalized coordinates has been specified by the user on the
DYNRED Bulk Data entry. Bulk Data entry.

Main Index
 352 MSC Nastran Error Messages
Errors 4000 - 4999

4181.0 *** USER INFORMATION MESSAGE 4181---

NUMBER OF ROOTS BELOW %1 CYCLES IS %2
NUMBER OF GENERALIZED COORDINATES SET TO %3

User information: The message specifies the number of generalized coordinates as determined by the pro-
gram. The number of generalized coordinates chosen (if autoselection is used) is the minimum of the fol-
lowing quantities:
1. 1.5 times the number of natural frequencies below FMAX, rounded up to the next integer multiple
of the number of initial random vectors.
2. The number of non-zero columns of the matrix.
If there are any natural frequencies below FMAX, a minimum of NIRV (from the DYNRED entry) gener-
alized coordinates is always provided. If FMAX is below all natural frequencies and there are no physical
degrees of freedom in the a set, User Fatal Message 4683 will result.

4182.0 *** USER FATAL MESSAGE 4182 (SEPTRE)

SETREE REFERENCES UNDEFINED SUPERELEMENT %1.

4182.1 *** USER FATAL MESSAGE 4182 (SEP1A)

TABLE %1 REFERENCES UNDEFINED SUPERELEMENT %2

4183.0 *** USER WARNING MESSAGE 4183 (SEP1A)

TABLE %1 DID NOT SPECIFY DOWNSTREAM CONNECTION FOR THE FOLLOWING
SUPERELEMENTS.

User information: A RESIDUAL-ONLY MODEL IS ASSUMED.

4184.0 *** USER WARNING MESSAGE 4184

Lagrange multiplier (LM) TO MPC TRANSFORMATION is being REQUESTED BUT THERE ARE
NO LM degrees-of-freedom IN THE MODEL.

User information: LM degrees-of-freedom are created via contact or RIGID Case Control command. This
REQUEST will be IGNORED.

4185.0 *** USER FATAL MESSAGE 4185 (SEPTRE)

SETREE SPECIFIES CLOSED SUPERELEMENT CONNECTIVITY LOOP BEGINNING WITH
SUPERELEMENT %1
SE ID DOWNSTREAM ID

Main Index
 MSC Nastran Error Messages 353
Errors 4000 - 4999

4185.1 *** USER FATAL MESSAGE 4185 (SEP1A)

TABLE %1 SPECIFIES CLOSED SUPERELEMENT CONNECTIVITY LOOP BEGINNING WITH
SUPERELEMENT %2
SE ID DOWNSTREAM ID

4186.0 *** USER FATAL MESSAGE 4186,

%1 element ID of %2 connects superelements %3 and %4, but they are not in the same path.

4187.0 *** USER FATAL MESSAGE 4187,

%1 element ID of %2 connects superelements %3, %4, and %5. Only two connections allowed.

4188.0 *** USER FATAL MESSAGE 4188,

%1 element ID of %2 references undefined grid point %3.

4189.0 *** SYSYTEM WARNING MESSAGE 4189 (CASINI)

IMPLICIT MODE ELEMENTS ARE BEING USED IN COMBINATION WITH TEMPERATURE
LOADS.

User information: INCORRECT RESULTS ARE PROBABLE AND THIS IS NOT ADVISED DUE
TO THE DIFFERENT ELEMENT FORMULATION USED IN CASI COMPARED TO NASTRAN.

DMAP programmer action: MAKE SURE THAT THE DMAP PARAMETER SOLVER OPTION
BITS SPECFIED ARE SET CORRECTLY.

4189.1 *** SYSTEM WARNING MESSAGE 4189 (CASINI)

IMPLICIT MODE ELEMENTS ARE BEING USED DURING NON-LINEAR SOLVER ITERA-
TIONS.

User information: INCORRECT RESULTS ARE PROBABLE AND THIS IS NOT ADVISED DUE
TO THE DIFFERENT ELEMENT FORMULATION USED IN CASI COMPARED TO NASTRAN.

DMAP programmer action: MAKE SURE THAT THE DMAP PARAMETER SOLVER OPTION
BITS SPECFIED ARE SET CORRECTLY.

Main Index
 354 MSC Nastran Error Messages
Errors 4000 - 4999

4190.0 *** SYSTEM FATAL MESSAGE 4168 (ITSCAS)

ILLEGAL INPUT TO SUBROUTINE ITSCAS. PROBLEM SIZE SET SELECTION SPECIFICA-
TION (=%1) IS NOT RECOGNIZED.

4190.1 *** SYSTEM FATAL MESSAGE 4168 (ITSCAS)

ILLEGAL INPUT TO SUBROUTINE ITSCAS. SOLUTION TYPE SPECIFICATION (=%1) IS NOT
RECOGNIZED.

4190.2 *** SYSTEM FATAL MESSAGE 4168 (ITSCAS)

ITSCAS LOGIC ERROR. MATRIX PROBLEM SIZE OF %1 DOES NOT MATCH USET TABLE
DOF COUNT OF %2.

4190.3 *** SYSTEM FATAL MESSAGE 4168 (ITSCAS)

ITSCAS LOGIC ERROR. NORMAL AND TANGENTIAL S2S ELEMENTAL MATRICES PRES-
ENT AND EFRIC = %1.

4191.0 *** USER FATAL MESSAGE 4191 (SEP1A1)

BOLT element ID=%1 connects to one or more grids that are interior to a superelement.

User information: BOLT elements can only connect to grids in the residual structure.

4192.0 *** SYSTEM FATAL MESSAGE 4192 (SEDR)

GRID POINT %1 IN SUPERELEMENT %2 IS NOT DEFINED IN GDNTAB FOR DOWN-
STREAM SUPERELEMENT %3.

System information: There are two probable causes for the failure: (1) User has made some changes to the
geometry for the superelement and has not regenerated the SEMAP data block (or has fetched an incorrect
version of SEMAP from the database); or (2) a programming logic error exists in SEP2 in preparing the
data block subsets.

4192.1 *** SYSTEM FATAL MESSAGE 4192 (SEMA)

Main Index
 MSC Nastran Error Messages 355
Errors 4000 - 4999

GRID POINT %1 IN SUPERELEMENT %2 IS NOT DEFINED IN BGPDT FOR DOWNSTREAM

SUPERELEMENT %3

System information: There are two probable causes for the failure:
1. User has made some changes to the geometry for the superelement and has not regenerated the
SEMAP data block (or has fetched an incorrect version of SEMAP from the database);
2. a programming logic error exists in SEP2 in preparing the data block subsets.

4192.2 *** SYSTEM FATAL MESSAGE 4192 (SEMA)

BOUNDARY POINT%1B IN SUPERELEMENT %2 IS NOT DEFINED IN BGPDT FOR DOWN-
STREAM SUPERELEMENT %3

4193.0 *** USER WARNING MESSAGE 4193---

NO EXCITATION HAS BEEN SPECIFIED FOR ONE OR MORE COMPONENTS SPECIFIED
ON %1 SET %2 REFERENCED ON %3 ENTRY %4

User information: No excitation (applied loads or enforced motion) has been specified for some compo-
nents specified on DELAY/DPHASE entries

4193.1 *** USER WARNING MESSAGE 4193---

NO EXCITATION HAS BEEN SPECIFIED FOR ANY OF THE COMPONENTS SPECIFIED ON
%1 SET %2 REFERENCED ON %3 ENTRY %4

User information: No excitation (applied loads or enforced motion) has been specified for the above com-
ponents

4193.2 *** USER FATAL MESSAGE 4193---

DELAY IS NOT SUPPORTED IN SOL 400 WITH FOLLOWER FORCE. TO IGNORE %1 SET %2
REFERENCED ON %3 ENTRY %4 AND CONTINUE TO RUN THIS JOB, PLEASE USING SYS-
TEM(798)=1.

4193.3 *** USER WARNING MESSAGE 4193---

DELAY IS NOT SUPPORTED IN SOL 400 WITH FOLLOWER FORCE. %1 SET %2 REFER-
ENCED ON %3 ENTRY %4 IS IGNORED.

4194.0 *** USER FATAL MESSAGE 4194.

Main Index
 356 MSC Nastran Error Messages
Errors 4000 - 4999

ROD ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4194.1 *** USER FATAL MESSAGE 4194.

PENTA ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4194.2 *** USER FATAL MESSAGE 4194.

HEXA ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4194.3 *** USER FATAL MESSAGE 4194.

BEAM ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4194.4 *** USER FATAL MESSAGE 4194 (GTR3D)

TRIA3 ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4194.6 *** USER FATAL MESSAGE 4194.

QUAD4 ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4194.10 *** USER FATAL MESSAGE 4194.

QUADR ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4194.11 *** USER FATAL MESSAGE 4194.

TRIAR ELEMENT %1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4196.0 *** USER WARNING MESSAGE 4196,

POINT ID =%1 .GE. %2 (MESSAGE NOT REPEATED FOR ANY OTHER SUCH POINTS)

User information: The indicated point ID is greater than the maximum allowed. Only one such message is
printed.

4197.0 *** USER WARNING MESSAGE 4197,

MORE THAN %1 UNIQUE ENTRYS WILL NOT BE LISTED IN FULL.

User information: Word size insufficient to hold the indicated number of unique entries. Additional
unique entries will not be processed. Only one such message printed.

4198.0 *** USER WARNING MESSAGE 4198,

Main Index
 MSC Nastran Error Messages 357
Errors 4000 - 4999

UNABLE TO PRINT UNIQUE CONNECTIVITY LIST SORTED BY SUPERELEMENT ID DUE

TO INSUFFICIENT CORE.
ADDITIONAL CORE NEEDED =%1 WORDS.

User information: The indicated additional memory is required to process the unique connectivity list
sorted by superelement ID.

4199.0
%1 FRONTAL MATRICES OUT OF A TOTAL OF %2 ARE STORED IN MEMORY.
MEMORY AVAILABLE: %3 MB
ESTIMATED ADDITIONAL MEMORY NEEDED TO STORE THE ENTIRE FACTOR: %4 MB

4199.1
ALL %1 FRONTAL MATRICES ARE STORED IN MEMORY.
MEMORY AVAILABLE: %2 MB
MEMORY USED TO STORE THE ENTIRE FACTOR: %3 MB

4200.0 *** USER WARNING MESSAGE 4200,

KEYWORD %1 NOT RECOGNIZED. IT WILL BE IGNORED.

User information: DIT keyword for superelement or module time estimation not in recognized list and is
ignored. List of acceptable keywords is printed after first unrecognized keyword is encountered.

4201.0 *** SYSTEM FATAL MESSAGE 4201 (GNFMID)

THE DICTIONARY DESCRIPTION OF THE STIFFNESS MATRIX IS UNACCEPTABLE AT
LOC= %1
EITHER IN FORM= %2 OR BAD SIL = %3 FOR ELEMENT ID = %4

System information: Programming error in processing stiffness matrix in nonlinear analysis.

4201.1 *** SYSTEM FATAL MESSAGE 4201 (NKUPTD)

THE DICTIONARY DESCRIPTION OF THE STIFFNESS MARTIX IS UNACCEPTABLE TO %1
EITHER IN FORM=%2 OR BAD SIL =%3 FOR ELEMENT ID =%4

System information: Programming error in processing stiffness matrix in nonlinear analysis.

Main Index
 358 MSC Nastran Error Messages
Errors 4000 - 4999

4202.0 *** SYSTEM FATAL MESSAGE 4202 (GNFM)

CANNOT FIND CORRELATED ENTRIES IN THE EST, STIFFNESS, AND DIFFERENTIAL
STIFFNESS MATRICES.
LOC=%1 ELTYPE= %2 ELID=%3,%4,%5,

System information: Programming error in processing stiffness matrix in nonlinear analysis.

4203.0 *** USER WARNING MESSAGE 4203 ,

THE SEMAP DATA BLOCK HAS BEEN MARKED NON-EXECUTABLE BY MODULE SEP1.

User information: Warning message is issued by SEP1 during generation of the superelement map. Fatal
message is issued by SEP3 if further execution is attempted without regenerating the superelement map.

4203.1 *** SYSTEM WARNING MESSAGE 4203 (SEP1)

THE SEMAP DATA BLOCK HAS BEEN MARKED NON-EXECUTABLE. ( SEE ERRORS NOTED
ABOVE )

System information: Warning message is issued by SEP1 during generation of the superelement map. Fatal
message is issued by SEP3 if further execution is attempted without regenerating the superelement map.

4203.2 *** SYSTEM FATAL MESSAGE 4203.

THE SEMAP DATA BLOCK HAS BEEN MARKED NON-EXECUTABLE BY SEP1.( SEE ERRORS
NOTED IN CREATION RUN)

System information: Warning message is issued by SEP1 during generation of the superelement map. Fatal
message is issued by SEP3 if further execution is attempted without regenerating the superelement map.

4204.0 *** USER WARNING MESSAGE 4204,

RSPLINE %1 SEGMENT %2 HAS NO DEPENDENT DEGREES OF FREEDOM.

User information: The RSPLINE has a segment with two independent grid points with no dependent grid
points between them.

4205.0 *** USER WARNING MESSAGE 4205

Main Index
 MSC Nastran Error Messages 359
Errors 4000 - 4999

ELEMENT-BASED ITERATIVE SOLUTION IS being requested in the presence of LAGRANGE multi-

plier (LM) degrees-of-freedom.

User information: LM degrees-of-freedom are created via contact or RIGID Case Control command. Pro-
gram will perform a Lagrange Multiplier TRANSFORMATION.

4206.0 *** USER WARNING MESSAGE 4206

ELEMENT-BASED ITERATIVE SOLUTION IS being requested without request for Lagrange multi-
plier (LM) TO MPC TRANSFORMATION.

User information: Program will perform a Lagrange Multiplier TRANSFORMATION.

4207.0 *** SYSTEM FATAL MESSAGE 4206

LOGIC ERROR encountered in Lagrange Multiplier transformation.
Programmer information: NO M-SET FOUND IN LMT TO MPC PHASE 2.

4208.0 *** system FATAL MESSAGE 4208 (DDMDRV)

An ERROR was encountered while UN-COMPRESSING PERMUTATION ARRAY AFTER GRID
COMPRESSION.

User action: SELECT A DIFFERENT COMPRESSION METHOD VIA NASTRAN SYSTEM CELL
317.

4209.0 *** User Warning Message 4209 (sep1c)

Due to Case Control command RIGID=LAGRAN (default in SOL 400) or LGELIM and MDL-
PRM,REUPSE,0 (default) and ALPHA (thermal expansion coefficient) being non-zero on one or more
rigid elements assigned to a superelement, all rigid elements assigned to any superelement will be moved to
the residual structure.

4210.0 *** User Information Message 4210 (sep1c)

Due to Case Control command RIGID=LAGRAN (default in SOL 400) or LGELIM and MDL-
PRM,REUPSE,1, all rigid elements belonging to superelements have been moved to the residual structure.

4211.0 *** User Warning Message 4211 (sep1c)

Main Index
 360 MSC Nastran Error Messages
Errors 4000 - 4999

Non-zero ALPHA (thermal expansion coefficient), on rigid elements assigned to any up-stream superele-
ments, is ignored, due to
1. Case Control command: RIGID=LAGRAN (default in SOL 400) or LGELIM; and
2. Bulk Data Entry: MDLPRM,REUPSE,777.

4214.0 *** USER INFORMATION MESSAGE 4214.

ROW AND COLUMN%1 OF DATA BLOCK %2 ARE NULL. DIAGONAL TERM REPLACED
WITH 1.0

User information: This message is printed (depending on the option selected) by the unsymmetric decom-
position routine. If the default option is selected, this message will be treated as an error condition and the
execution aborted at the completion of the preface of the decomposition. Schedule matrix partitioning or
other technique to remove singularities.

4214.1 *** SYSTEM INFORMATION MESSAGE 4214 (SDCBOD)

%1 SUBSTITUTED FOR DIAG. TERM OF LOWER TRIANGULAR FACTOR AT ROW %2

4215.0 *** USER WARNING MESSAGE 4215.

%1%2%3 OF DATA BLOCK %4 IS NULL BUT %5%6%7 IS NOT.

User information: The matrix is singular and cannot be decomposed by the unsymmetric decomposition
routine. Examine and correct data which caused singular matrix to be generated.

4216.0 *** USER INFORMATION MESSAGE 4216 ---

PARAMETERS FOR PARALLEL SPARSE UNSYM. DECOMP OF DATA BLOCK %1( TYPE=%2)
FOLLOW
MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS
NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6
SYSTEM (107) =%7 REQUESTED PROC. =%8 CPUS

4216.1 *** USER INFORMATION MESSAGE 4216 ---

PARAMETERS FOR SPARSE UNSYM. DECOMP OF DATA BLOCK %1( TYPE=%2) FOLLOW
MATRIX SIZE =%3 ROWS NUMBER OF NONZEROES =%4 TERMS
NUMBER OF ZERO COLUMNS =%5 NUMBER OF ZERO DIAGONAL TERMS =%6

4216.2 *** USER INFORMATION MESSAGE 4216.

Main Index
 MSC Nastran Error Messages 361
Errors 4000 - 4999

PARAMETERS FOR UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1( TYPE=%2)

FOLLOW
MATRIX SIZE =%3 ROWS CPU TIME ESTIMATE =%4 SECS I/O TIME ESTIMATE =%5 SECS
ACTIVE COLS =%6 AVG ACTIVE COLS =%7 MAX ACTIVE COLS*ROWS =%8 AVG
ACTIVE ROWS =%9 AVG ACTIVE ROWS =%10 MAX ACTIVE COLS*ROWS =%11
MAX
SPILL =%12 GROUPS SPILL GROUP AVG =%13 ROWS SPILL TOTAL =%14 BLOCKS
PASSIVE COLS/ROWS PASSIVE COLS*ROWS =%16 AVG PASSIVE COLS*ROWS =%17
=%15 GROUP MAX
ADDITIONAL MEMORY NZ NBR IN LOWER =%19 TERMS NZ NBR IN UPPER =%20
=%18 WORDS TERMS

4216.3 *** USER INFORMATION MESSAGE 4216 ---

PARAMETERS FOR IN-CORE SPARSE UNSYM. DECOMP ( MATRIX TYPE=%1) FOLLOW
MATRIX SIZE =%2 ROWS NUMBER OF NONZEROES =%3 TERMS
NUMBER OF ZERO COLUMNS =%4 NUMBER OF ZERO DIAGONAL TERMS =%5

4217.0 *** USER INFORMATION MESSAGE 4217.

DECOMPOSITION OF DATA BLOCK %1 TERMINATED ACCORDING TO USER REQUEST.

User information: The bit corresponding to 26 has been set in SYSTEM(69) indicating that the execution
is to be terminated after execution of the preface of symmetric or unsymmetric decomposition. This occurs
when a zero diagonal occurs and SYSTEM(69) is not set to continue (SYSTEM(69)=16). This message is
often preceded by a message that indicates the offending column.

4217.3 *** USER INFORMATION MESSAGE 4217

ITERATIVE SOLVER TERMINATED ACCORDING TO USER REQUEST (PREFONLY<0 ON
ITER BULK DATA ENTRY).

4217.9 *** USER INFORMATION MESSAGE 4217.

DECOMPOSITION OF DATA BLOCK %1 TERMINATED ACCORDING TO USER REQUEST.

4218.0 *** SYSTEM FATAL MESSAGE 4218.

Main Index
 362 MSC Nastran Error Messages
Errors 4000 - 4999

UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1 IS ABORTED DUE TO INSUFFI-

CIENT MEMORY. REASON =%2

System information:
The preface of the unsymmetric decomposition has insufficient memory to execute.
Reasons are:
100 minimum core= * MATRIX SIZE + 7 * BUFFSIZE not available.
190 nonzero terms in longest column do not fit.
218 active row vector does not fit.
222 nonzero terms in longest row do not fit.
302 active column vector does not fit.
320 spill definition table does not fit.
335 spill definition table does not fit.

4219.0 *** SYSTEM FATAL MESSAGE 4219.

UDCOMP LOGIC ERROR %1. CONTENTS OF /UDCOMX/ FOLLOW...

System information: A situation which the program is not prepared to handle has occurred. Contact MSC
client support.

4220.0 *** USER INFORMATION MESSAGE 4220 (UMFDRV):

PARAMETERS FOR SPARSE UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1
(TYPE=%2) FOLLOW
MATRIX SIZE = %3 ROWS NUMBER OF NONZEROS = %4 TERMS
INITIAL MEMORY REQUIREMENT = %5 MB
MEMORY AVAILABLE FOR UMFPACK = %6 MB
TOTAL MEMORY AVAILABLE = %7 MB

4221.0 *** USER WARNING MESSAGE 4221 (SEP2SE)

%1 ENTRY REFERENCES SECONDARY SUPERELEMENT %2 WHICH IS NOT ALLOWED.

User information: The referenced entries define interior constraints of superelements. Secondary superele-
ments automatically have the same interior constraints as their primary superelement, hence no other con-
straints may be specified. Remove the entries listed.

4222.0 *** USER FATAL MESSAGE 4222 (SEP2SE)

Main Index
 MSC Nastran Error Messages 363
Errors 4000 - 4999

%1 ENTRY FOR SUPERELEMENT %2 REFERENCES INTERIOR POINT %3.

User information: The referenced entries are used to place exterior points in special boundary sets. Either
change grid from interior to exterior, or remove offending SE-type bulk data entry.

4223.0 *** USER FATAL MESSAGE 4223

%1 ENTRY FOR SUPERELEMENT %2 REFERENCES UNDEFINED POINT %3.

User information: These entries must reference exterior grid or scalar points for the superelement they ref-
erence. Inspect the SEMAP for the list of exterior degrees of freedom of the superelement.

4224.0 ***USER WARNING MESSAGE 4224 (SEPSEQ)

%1 ENTRY REFERENCES UNDEFINED SUPERELEMENT %2

User information: THE %3 ENTRY WILL BE IGNORED. These entries define generalized coordinates
of superelements. Inspect the SEMAP table for the list of superelement identification numbers in the
model.

4224.1 *** USER FATAL MESSAGE 4224 (SEPMC1)

SECONCT ENTRY REFERENCES UNDEFINED SUPERELEMENT %1

4224.2 *** USER WARNING MESSAGE 4224 (SEPMA1)

%2 ENTRY REFERENCES AN UNDEFINED %3 %1.

User information: These entries define generalized coordinates of superelements. Inspect the SEMAP table
for the list of superelement identification numbers in the model.

4224.3 *** USER WARNING MESSAGE 4224 (SEPAQN)

SENQSET ENTRY REFERENCES UNDEFINED SUPERELEMENT %1

User information: THE SENQSET ENTRY WILL BE IGNORED.

4224.4 *** USER FATAL MESSAGE 4224 (SEP1C)

Main Index
 364 MSC Nastran Error Messages
Errors 4000 - 4999

%1 ENTRY REFERENCES UNDEFINED SUPERELEMENT %2

User information: These entries define generalized coordinates of superelements. Inspect the SEMAP table
for the list of superelement identification numbers in the model.

4224.5 *** USER WARNING MESSAGE 4224 (SEPMA1)

%2 ENTRY ID=%4 REFERENCES UNDEFINED %3 %1.

User information: These entries reference superelement or module IDs. Inspect the SEMAP table for the
list of superelement or module identification numbers in the model.

4225.0 *** USER FATAL MESSAGE 4225---,

THE NUMBER OF GENERALIZED COORDINATES IS%1, WHICH IS GREATER THAN THE
ASET SIZE%2

User information: For generalized dynamic reduction, the user must define at least as many ASET points as
there are generalized coordinates. The user may either reduce the number of generalized coordinates or
increase the number of ASET points.

4226.0 *** USER INFORMATION MESSAGE 4226 (UMFDRV):

ACTUAL MEMORY AND DISK SPACE REQUIREMENTS FOR SPARSE UNSYMMETRIC
DECOMPOSITION
NUMBER OF NONZERO TERMS IN UPPER FACTOR = %1
NUMBER OF NONZERO TERMS IN LOWER FACTOR = %2
MINIMUM MEMORY REQUIREMENT = %3 MB

4227.0 *** USER FATAL MESSAGE 4227

ILLEGAL VALUE SPECIFIED FOR CTYPE PARAMETER

User information: CTYPE can only take on the values DIH, AXI or ROT.

4228.0 *** USER FATAL MESSAGE 4228,

TEMPERATURE SET %1 CONTAINS DUPLICATE GRID ID (%2 ).

User information: A grid point has been referenced more than once within the temperature set indicated.

Main Index
 MSC Nastran Error Messages 365
Errors 4000 - 4999

4228.1 *** USER FATAL MESSAGE 4228 (NLCTMA)

TTEMP Bulk Data entry id=%1 CONTAINS DUPLICATE GRID ID (%2 ) in different TMPSET
groups.

4234.0 *** USER INFORMATION MESSAGE 4234.

UFBS TIME ESTIMATE TO FORM %1( TYPE=%2 ) CPU=%3, I/O=%4,TOTAL=%5,PASSES=%6

4234.1 *** USER INFORMATION MESSAGE 4234.

UFBS METHOD %1 TIME ESTIMATE TO FORM %2 - CPU=%3, I/O=%4, TOTAL=%5,
PASSES=%6

4234.3 *** USER INFORMATION MESSAGE 4234.

LEFT HANDED UFBS TIME ESTIMATE TO FORM %1CPU=%2, I/
O=%3,TOTAL=%4,PASSES=%5

4235.0 *** USER FATAL MESSAGE 4235 (SEP1C)

CSUPER ENTRY %1 REFERENCES INTERIOR POINT %2 OF ITS PRIMARY SUPERELEMENT.

4236.0 *** USER FATAL MESSAGE 4236 (SEP1C)

NUMBER OF EXTERIOR GRID POINTS FOR SECONDARY SUPERELEMENT %1 IS NOT
EQUAL TO NUMBER FOR PRIMARY SUPERELEMENT %2

User information: Probably an error on the CSUPER Bulk Data entry for the secondary superelement.

4237.0 *** USER FATAL MESSAGE 4237 (SEP1C)

SEQSEP ENTRY REFERENCES SECONDARY SUPERELEMENT %1 WHICH WAS NOT
DEFINED ON A CSUPER ENTRY.

4238.0 *** USER FATAL MESSAGE 4238 (SEP1C)

NUMBER OF GRID POINTS ON SEQSEP %1 DOES NOT MATCH NUMBER ON REFER-
ENCED CSUPER ENTRY.

4239.0 *** USER FATAL MESSAGE 4239 (SEP1C)

SEQSEP %1 REFERENCES PRIMARY SUPERELEMENT %2 WHICH IS DEFINED AS A SEC-
ONDARY.

Main Index
 366 MSC Nastran Error Messages
Errors 4000 - 4999

4240.0 *** USER FATAL MESSAGE 4240 (TA1BND)

BEND ELEMENT %1 BEND RADIUS OR ARC ANGLE INCONSISTENT WITH GEOM
OPTION

User information: RB is nonzero on PBEND entry when GEOM option on CBEND entry is 1, 2, or 4 or
RB is zero when GEOM option is 3 or AB is nonzero when when GEOM option is 1, 2, or 3 or B is .LE.
zero or .GT. 180, when GEOM option is 4. Fix inconsistency and resubmit run.

4241.0 *** SYSTEM INFORMATION MESSAGE 4241 (COMIFP)

---, COMIFP ABORTED, %1%2 FILE COMPARISON OF CARD TYPE %3
ESTIMATED INCREASED CORE REQUIREMENT = %4 WORDS.

System information: Increase core available by at least suggested amount.

4242.0 *** SYSTEM INFORMATION MESSAGE 4242 (COMIFP)

--- %1 -- CARD IMAGE(S) CANNOT BE RECONSTRUCTED PRESENTLY, ( ICS=%2 ).
THE CARD(S) REPRESENTED BY THIS %3 RECORD ARE %4

System information: Either insufficient information in the IFP file to reconstruct the entry type or the
entry is currently not implemented in module.

4243.0 ***USER FATAL MESSAGE 4243 (IFPDRV)

ELEMENT TYPE %1 IS OUT OF SORT STARTING WITH ID %2

User information: Elements which were allowed to be input two per entry, must now be input in sort.
Make two physical entries for the out-of-sort elements and resubmit.

4244.0 *** USER FATAL MESSAGE 4244 (SEP1C)

SEQSEP %1 REFERENCES PRIMARY SUPERELEMENT %2 WHICH IS UNDEFINED.

User information: The PSID field should reference the same primary superelement that the CSUPER entry
does. Change the PSID field on the CSUPER and SEQSEP entries to reference a primary superelement.

4245.0 *** USER FATAL MESSAGE 4245 (SEP1C)

Main Index
 MSC Nastran Error Messages 367
Errors 4000 - 4999

SEQSEP %1 REFERENCES GRID POINT %2 WHICH IS NOT IN SUPERELEMENT %3

User information: SEMAP table to find the exterior grid points of the primary superelement. Inspect the
SEMAP table to find the exterior grid points of the primary superelement.

4246.0 *** USER FATAL MESSAGE 4246 (SEP1C)

SEQSEP %1 REFERENCES UNDEFINED GRID POINT %2

User information: Same comments as Message 4245.

4247.0 *** USER FATAL MESSAGE 4247.

SECONDARY SUPERELEMENT %1 AND PRIMARY SUPERELEMENT %2 HAVE SCALAR
POINTS IN DIFFERENT SEQUENCE.

User information: Scalar points are included in the same sequence as grid points when establishing exterior
grid and scalar point sequencing.

4248.0 *** USER INFORMATION MESSAGE 4248.

NUMBER OF EXTERIOR GRID POINTS .LT. 3 FOR SECONDARY SUPERELEMENT %1
CONGRUENCE TEST WITH PRIMARY SUPERELEMENT %2 CANNOT BE PERFORMED.

User information: The first three non-colinear exterior grid points of the secondary superelement and its
primary superelement are used to establish local coordinate systems for grid point location and global coor-
dinate congruence test. These tests will not be performed if there are less than three exterior grid points. A
third point may be attached to the primary superelement by use of a CSUPEXT entry, if congruence tests
are desired. It will not change the load paths of the structure.

4249.0 *** USER FATAL MESSAGE 4249.

SUPERELEMENT PROCESSING REQUESTED BUT SEMAP DATA BLOCK IS MISSING.

User information: One cause is improper use of PARAM,DLOAD or PARAM,NODATA. Another cause
might be lack of a RESTART FMS statement on restart. Use PARAM,DBDICT,2 to print the contents of
database.

4250.0 *** USER FATAL MESSAGE 4250

The SUPER=%1 Case Control command references neither a valid superelement or SET command ID.

Main Index
 368 MSC Nastran Error Messages
Errors 4000 - 4999

4251.0 *** USER FATAL MESSAGE 4251 (SEPSET)

CONFLICTING DEFINITIONS FOR GRID POINT %1 ON SESET ENTRIES FOR SUPERELE-
MENTS %2 AND %3

User information: SESET entries are used to describe the interior grid point membership of superelements.
A grid point may be interior to only one superelement. Remove one of the offending SESET entries.

4252.0 *** SYSTEM FATAL MESSAGE 4252 (SEMA)

MATRIX %1 FOR UPSTREAM SUPERELEMENT %2 DOES NOT EXIST.

User information: THE CURRENT SUPERELEMENT REQUIRES ALL OF ITS UPSTREAM

SUPERELEMENT MATRICES FOR ASSEMBLY INTO THE CURRENT SUPERELEMENT. THE
PROBABLE CAUSES ARE:
1. THE UPSTREAM SUPERELEMENT'S DBSET OR DATABASE IS NOT ATTACHED.
2. THE UPSTREAM SUPERELEMENT DID NOT COMPLETE REDUCTION IN A
PREVIOUS RUN.
User action: RERUN THE REDUCTION OF THE UPSTREAM SUPERELEMENT AND/OR
ENSURE THAT THE DBSET AND/OR DBLOCATE'D DATABASE WHICH CONTAINS THE
UPSTREAM SUPERELEMENT MATRIX IS ATTACHED.

4253.0 *** SYSTEM FATAL MESSAGE 4253,

GRID POINTS LISTED FOR DOWNSTREAM SUPERELEMENT IN BGPDT TABLE DO NOT
MATCH CURRENT SEMAP.

System information: If the downstream database is assembled, and then its bulk data is changed, its stored
matrices and tables will not match the current SEMAP. This can also happen using multiple databases if an
obsolete database is mounted. Perform the SEALL operation on the downstream superelement, or attach
the correct downstream database.

4254.0 *** USER FATAL MESSAGE 4254 (SEP1A)

CSUPER ENTRY DEFINES SECONDARY SUPERELEMENT %1 WHICH IS ALREADY DEFINED
AS A PRIMARY.

User information: Image, mirror and external superelements are defined on CSUPER entries. They may
not have the same identification number as existing primary superelements.
Change the SSID field on the CSUPER entry.

Main Index
 MSC Nastran Error Messages 369
Errors 4000 - 4999

4255.0 *** SYSTEM FATAL MESSAGE 4255.

UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1 FAILS AT ROW %2. UNABLE TO
PIVOT.
UII/MAXUIJ =%3

System information: The matrix is undoubtedly singular. No terms which exceed the user specified thresh-
old (or its default) were available to allow pivoting to take place. Use SOL 60 or PARAM,CHECKOUT to
determine where the problems exist, and look for large MAXRATIOs. See Chapter 9 or the MSC NAS-
TRAN Numerical Methods User's Guide for further discussion. it can be because the DOF defined on the
dependent set on an RBE3 entry are indeterminate and form a redundant set. See Section 9.4.1 and
Remark 3 under RBE3 in the MSC NASTRAN Quick Reference Guide, chapter 5. See also Error Report
3486 in Chapter 17.

4255.1 *** SYSTEM FATAL MESSAGE 4255.

INCORE UNSYMMETRIC DECOMPOSITION FAILS AT COLUMN %1 UNABLE TO PIVOT.

4256.0 *** SYSTEM INFORMATION MESSAGE 4256---,

MPC SEQUENCE PROCESSING HAS COMPLETED.

System information: Message appears if NOGO flag set information message to indicate that MPC pro-
cessing has completed. Under condition where NEWSEQ=-1 and MPC 0 on input, the NOGO flag is set
at start of SEQP module processing. If MPC processing is successful, no error messages or other informa-
tion messages would appear prior to termination of run. Some doubt may otherwise be left in the user's
mind that anything had been done.

4257.0 *** USER FATAL MESSAGE 4257.

FLUID MATRIX CALCULATION STOPPING BECAUSE ELEMENTS%1 AND%2 HAVE ZERO
DISTANCE.

User information: Elements noted have zero separation. Element centers are coincidental, not allowed for
fluid interaction calculation.

4258.0 *** USER FATAL MESSAGE 4258.

Main Index
 370 MSC Nastran Error Messages
Errors 4000 - 4999

ELEMENT %1, WHICH IS ON FLUID STRUCTURE BOUNDARY, CROSSES A PLANE OF SYM-

METRY.

User information: None of the elements included in an MFLUID group may span a symmetry plane.

4259.0 *** USER FATAL MESSAGE 4259. (FMPH1D)

ELIST VALUES ON MFLUID CARDS MAY NOT BOTH BE ZERO.

User information: MFLUID entry parameters ELIST1 and ELIST2 may not both be zero. This constitutes
a fluid group containing no element surfaces.

4260.0
%1 CHARACTERISTIC PARAMETER EXCEEDS RANGE OF APPLICABILITY FOR ELEMENT
%2

User information: Stress output for the CBEND element may exceed the range of applicability for the fol-
lowing stress intensification options. For CBEND elements with the FSI option of 3; the bending parame-
ter should be within
0.05 < = T*RB/(r**2*SQRT(1-nu**2)) < = 1.0
the pressure should be within
0. < = P*RB**2/(E*r*t) < = 0.1
For the CBEND elements with the FSI option of 2 the bending parameter should be
t*RB/(r**2*SQRT(1-nu**2)) > = 0.2
Change parameter so equations are within range.

4261.0 *** USER FATAL MESSAGE 4261---,

THE INPUT MAXIMUM NUMBER OF GENERALIZED COORDINATES IS ZERO.

User information: NCMAX field on DYNRED entry is 0 or blank. Must be nonzero if QSETi or
SEQSETi entries are not used.

4262.0 *** USER FATAL MESSAGE 4262---,

MASS MATRIX IS NOT PRESENT OR IS PURGED.

User information: Dynamic reduction computes approximate eigenvectors and therefore requires nonzero
mass terms. Determine why no mass terms are present and rectify. Common causes are no mass density
input on material cards, or dynamic reduction not appropriate for massless superelement.

Main Index
 MSC Nastran Error Messages 371
Errors 4000 - 4999

4263.0 *** USER WARNING MESSAGE 4263 (RBE3D):

THE UM SET SELECTED FOR RBE3 ELEMENT %1 IS POOR.

User action: MODIFY THE UM SELECTION OR USE PARAM,AUTOMSET

4265.0 *** USER WARNING MESSAGE 4265---,

RBE3 RECORD HAS ERRONEOUS GRID %1 AND COMPONENTS %2 SPECIFIED.

User information: All grid and components specified in the m-set on the RBE3 entry must also be specified
either in the REFGRID and component or in the independent grid and components.

4266.0 *** SYSTEM FATAL MESSAGE 4266---,

UNABLE TO FIND EXTERNAL GRID %1 IN THE EXTERNAL V. INTERNAL CONVERSION
TABLE.

System information: Either an internal logic error has occurred or erroneous data has been detected incom-
ing to subroutine SEQMR for use in its MPC relations processing.

4267.0 *** USER FATAL MESSAGE 4267---,

THE NUMBER OF PHYSICAL DEGREES OF FREEDOM PLUS GENERALIZED CO-ORDI-
NATES %1 IS LESS THAN NCMAX %2

User information: The number of generalized coordinates specified by SPOINT and ASETi entries must
match the NCMAX field.

4268.0 *** SYSTEM FATAL MESSAGE 4268---,

MINIMUM CONNECTIVITY SEARCH FAILED AFTER %1 GRIDS SEQUENCED.

System information: Subroutine SEQMAC was unable to choose the next grid for sequencing before all
grids had been sequenced. Possible cause believed to be machine failure or logic error.

4269.0 *** USER FATAL MESSAGE 4269. (FMPH1D)

ONE OR MORE ELIST BULK DATA CARDS IS MISSING.

User information: MFLUID entry selects an ELIST entry which cannot be located.

Main Index
 372 MSC Nastran Error Messages
Errors 4000 - 4999

4270.0 *** USER FATAL MESSAGE 4270. (FMPH1D)

SELECTED MFLUID BULK DATA CARD WITH ID %1 CANNOT BE FOUND.

User information: MFLUID set selected in Case Control Section cannot be found.

4271.0 *** USER WARNING MESSAGE 4271. (FMPH1D)

MFLUID SET %1 CONTAINS NO ELEMENTS BELOW THE FLUID FREE SURFACE.

User information: Possible error in defining fluid free surface. No elements are wetted.

4272.0 *** USER FATAL MESSAGE 4272. (FMPH1D)

COORDINATE SYSTEM %1 USED FOR FLUID-STRUCTURE INTERACTION NOT DEFINED
OR IS NOT A RECTANGULAR SYSTEM.

User information: The coordinate system used to identify the orientations of the free surface (normal to
X3) and the planes of symmetry (if any) must be rectangular. Review CID value on MFLUID entry.

4273.0 *** USER WARNING MESSAGE 4273. (FMPH1D)

ELEMENT %1 HAS BEEN LISTED MORE THAN ONCE FOR FLUID STRUCTURE BOUND-
ARY.

User information: ELIST entries have referenced a given element ID more than once in an MFLUID
group.

4274.0 *** USER WARNING MESSAGE 4274. (FMPH1D)

%1 ELEMENTS SELECTED FOR FLUID STRUCTURE BOUNDARY CANNOT BE FOUND
AMONG ALLOWED ELEMENT TYPES.

User information: One or more element IDs referenced on ELIST entries were not present.

4275.0 *** SYSTEM FATAL MESSAGE 4275.

Main Index
 MSC Nastran Error Messages 373
Errors 4000 - 4999

DURING A %1 OPERATION, UNIT = %2, DATA BLOCK=%3, A %4 CONDITION OCCURRED.

( %5CODE=%6)

System information: Fatal error in subroutine IOVAX while processing I/O request. I/O ERROR is either
program logic or possible machine error condition. If run is a restart and data block is from previous run,
END-OF-DATA may be caused by improper job setup. Otherwise, END-OF-DATA is probably caused
by a program logic error. If error is in job setup, correct DCL and resubmit. Otherwise, examine the RMS
codes for a possible I/O error or other type of machine error. If it does not appear to be caused by local
hardware problems, forward the run to the Hexagon programming staff. Another possible cause is that the
disk is full. See Error Report 3161 in section 17.4 of MSC NASTRAN Reference Manual. Another possi-
ble cause is that the BUFFSIZE needs to be increased. See Error Report 3484. If this corrects the error,
please notify Hexagon so it can be better documented.

4276.0 *** SYSTEM FATAL MESSAGE 4276 (%1).

ERROR CODE %1 PID=%2

User information: THIS ERROR MAY BE CAUSED BY EXCEEDING THE CAPACITY OF A SYS-
TEM RESOURCE.
(E.G., ALLOCATED DISK IS FULL, OR MAXIMUM FILE SIZE HAS BEEN REACHED)

4276.1 *** USER INFORMATION MESSAGE 4276 (%1).

THE DIAG 44 RELATED %1 DUMP IS SENT TO LOG FILE.

User action: THIS INFORMATION MAY BE USEFUL TO MSC FOR DEBUGGING YOUR PROB-
LEM.
PLEASE CONTACT MSC CLIENT SUPPORT.

4276.2 *** SYSTEM FATAL MESSAGE 4276 (%1).

ERROR CODE %1 PID=%2

4277.0 *** USER FATAL MESSAGE 4277.

Main Index
 374 MSC Nastran Error Messages
Errors 4000 - 4999

GRID POINT%1 OF SECONDARY SUPERELEMENT %2 IS NOT IN SAME RELATIVE LOCA-

TION AS GRID POINT%3 OF PRIMARY SUPERELEMENT %4 DELTA ALLOWED =%5 DELTA
CALCULATED =%6

User information: All grid points for secondary superelement must be in the same location as for primary
superelement. See PARAMeter CONFAC described in Section 6 of the MSC NASTRAN Quick Reference
Guide.

4278.0 *** USER FATAL MESSAGE 4278.

GRID POINT %1 OF SECONDARY SUPERELEMENT %2 DOES NOT HAVE SAME GLOBAL
ORIENTATION AS GRID POINT %3 OF PRIMARY SUPERELEMENT %4

User information: All grid points for a secondary superelement must have the same global coordinate sys-
tem as the primary superelement. See PARAMeter CONFAC described in Section 6 of the MSC/NAS-
TRAN Quick Reference Guide.

4281.0 *** USER FATAL MESSAGE 4281,

POOR CHOICE OF DEPENDENT DEGREE OF FREEDOM ON RIGID ROD %1

User information: The dependent degree of freedom should not be perpendicular (or nearly so) to the
RROD.

4282.0 *** USER FATAL MESSAGE 4282, (RBSRHD)

UNDEFINED GRID POINT %1 RIGID ELEMENT %2

User information: The rigid element references a grid point that does not exist in the model, or is disjoint
from the superelement or module being processed. Check the Bulk Data Section and the superelement or
module SEMAP table for the existence of the grid point referenced.

4283.0 *** USER FATAL MESSAGE 4283

ILL-CONDITIONED CONSTRAINT MATRIX FOR RIGID ELEMENT %1

User information: The independent degrees of freedom of a rigid element must form a non-redundant and
sufficient set of freedoms to define rigid motions.

4284.0 *** USER FATAL MESSAGE 4284. (RBE3D)

Main Index
 MSC Nastran Error Messages 375
Errors 4000 - 4999

RIGID ELEMENT %1 HAS ILLEGAL UM SET SPECIFICATION

User information: One or more unique dependent degrees of freedom must be selected for a rigid element.

4286.0 *** USER FATAL MESSAGE 4286,

RSPLINE %1 HAS MORE THAN 100 GRID POINTS

User information: The number of grid points for an RSPLINE is limited.

4287.0 *** USER FATAL MESSAGE 4287 ,

ILLEGAL THICKNESS FOR PLATE ELEMENT ID = %1

User information: The user can supply thickness either on the connection entry or the PSHELL property
entry. No corner thickness may be negative and at least one corner thickness must be positive.

4287.1 *** USER FATAL MESSAGE 4287 ,

ILLEGAL THICKNESS FOR CRAC2D ELEMENT ID = %1

4288.0 *** USER FATAL MESSAGE 4288 (EPTTRD)

ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = %2

User information: The code paths refer to the reason. Reasons 1 through 5 mean that the program was
unable to find an element coordinate system. Reasons 6 through 12 imply the program cannot find a local
coordinate system at a Gauss point. Reason 13 may be due to a negative 12I/T3 (PSHELL). Reason 14 is
due to zero transverse shear thickness (PSHELL). Reason 21 occurs if the isoparametric mapping is unrea-
sonable, which can occur if the midside nodes are too close to the corners.

4288.1 *** USER FATAL MESSAGE 4288. (NTR6D)

ILLEGAL GEOMETRY FOR TRIA6 ELEMENT WITH ID =%1. CODE PATH =%2

4288.2 *** USER FATAL MESSAGE 4288. (GPJAC)

ILLEGAL GEOMETRY FOR %1 ELEMENT WITH ID =%2. CODE PATH =%3

4288.11

Main Index
 376 MSC Nastran Error Messages
Errors 4000 - 4999

ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 1

User information: CONNECTION GRIDS 1 AND 3 ARE COINCIDENT.

4288.12
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 2

User information: CONNECTION GRIDS 2 AND 4 ARE COINCIDENT.

4288.13
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 3

User information: ELEMENT LOCAL COORDINATE SYSTEM I_VECTOR LENGTH IS ZERO.

4288.14
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 4

User information: ELEMENT LOCAL COORDINATE SYSTEM J_VECTOR LENGTH IS ZERO.

4288.15
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 5

User information: ELEMENT LOCAL COORDINATE SYSTEM K_VECTOR LENGTH IS ZERO.

4288.16
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 6

User information: POOR GEOMETRY RESULTING IN BAD JACOBIAN. THE MIDSIDE GRID
POINT IS LOCATED AT THE QUARTER POINT. IT IS RECOMMENDED THAT THE
MIDSIDE GRID POINTS BE LOCATED WITHIN THE MIDDLE THIRD OF THE EDGE.

4288.17
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 7

User information: CURVILINEAR X-AXIS CANNOT BE COMPUTED.

4288.18

Main Index
 MSC Nastran Error Messages 377
Errors 4000 - 4999

ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 8

User information: CURVILINEAR Y-AXIS CANNOT BE COMPUTED.

4288.19
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 9

User information: CURVILINEAR X-AXIS HAS ZERO LENGTH.

4288.20
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 10

User information: CURVILINEAR Y-AXIS HAS ZERO LENGTH.

4288.21
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 11

User information: CURVILINEAR X-AXIS Y-AXIS HAVE POOR GEOMETRY.

4288.22
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 12

User information: JACOBIAN MATRIX IS ZERO.

4288.23
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 13

User information: BAD GEOMETRY, IOVER12 TIMES AVETHICK OVER GAUSS POINTS COM-
PUTE TO ZERO.

4288.24

Main Index
 378 MSC Nastran Error Messages
Errors 4000 - 4999

ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 14

User information: BAD GEOMETRY, ZERO VOLUME AT A GAUSS POINT FOR TRANSVERSE
SHEAR COUPLING COMPUTATION.

4288.25
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 15

User information: BAD SURFACE JACOBIAN FOR RESIDUAL BENDING FLEXIBILITY, CHECK
SURFACE GEOMETRY.

4288.26
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 16

User information: BAD GEOMETRY FOR RESIDUAL BENDING FLEXIBILITY, CHECK X OF

CORNER GRID LOCATIONS.

4288.27
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 17

User information: BAD GEOMETRY FOR RESIDUAL BENDING FLEXIBILITY, CHECK Y OF

CORNER GRID LOCATIONS.

4288.28
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 18

User information: BAD GEOMETRY FOR RESIDUAL BENDING FLEXIBILITY, CHECK G11.

4288.29
ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 19

User information: ZERO EDGE LENGTH WHEN COMPUTING LOCATION OF MISSING

MIDSIDE GRID POINT.

4288.31

Main Index
 MSC Nastran Error Messages 379
Errors 4000 - 4999

ILLEGAL GEOMETRY FOR QUAD8 ELEMENT WITH ID =%1. CODE PATH = 21

User information: IT IS RECOMMENDED THAT THE MIDSIDE GRID POINTS BE LOCATED

WITHIN THE MIDDLE THIRD OF THE EDGE.

4289.0 *** SYSTEM FATAL MESSAGE 4289.

CORE IS INSUFFICIENT BY A BASE10
AMOUNT =%1 WORDS TO PROCESS PENTA ELEMENT WITH ID =%2

4289.1 *** SYSTEM FATAL MESSAGE 4289.

CORE IS INSUFFICIENT BY A BASE10
AMOUNT =%1 WORDS TO PROCESS QUAD8 ELEMENT WITH ID =%2

4289.2 *** SYSTEM FATAL MESSAGE 4289 (STR61D)

CORE IS INSUFFICIENT BY A BASE10 AMOUNT =%1 WORDS TO PROCESS TRIA6 ELE-
MENT WITH ID =%2

4290.0 *** USER FATAL MESSAGE 4290.

FOR QUAD ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 3X3
MATERIAL MATRIX WITH EITHER OR BOTH OF TERMS G11 ANDG22 EQUAL TO ZERO.
MATERIAL ID CONCERNED EQUALS%2

4290.1 *** USER FATAL MESSAGE 4290.

FOR QUAD8 ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 3X3
MATERIAL MATRIX WITH EITHER OR BOTH OF TERMS G11 ANDG22 EQUAL TO ZERO.
MATERIAL ID CONCERNED EQUALS%2

User information: Nonzero values of bending stiffness are required if MID2 data is supplied.

4290.2 *** USER FATAL MESSAGE 4290.

PRE 2008 %1 DIFFSTIF BECAUSE SYSTEM(448) =%2

4291.0 *** USER FATAL MESSAGE 4291.

FOR TRIA3 ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-
MATRIX FOR MATERIAL ID =%2 WHICH IS SINGULAR.

Main Index
 380 MSC Nastran Error Messages
Errors 4000 - 4999

4291.2 *** USER FATAL MESSAGE 4291. (SQD41D)

FOR QUAD4 ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-
MATRIX FOR MATERIAL ID =%2 WHICH IS SINGULAR.

4291.3 *** USER FATAL MESSAGE 4291.

FOR QUAD8 ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-
MATRIX FOR MATERIAL ID =%2 WHICH IS SINGULAR.

4291.5 *** USER FATAL MESSAGE 4291.

FOR TRIA6 ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-
MATRIX FOR MATERIAL ID =%2 WHICH IS SINGULAR.

4291.6 *** USER FATAL MESSAGE 4291 (EQDRD)

FOR QUADR ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-
MATRIX FOR MATERIAL ID =%2 WHICH IS SINGULAR.

4291.7 *** USER FATAL MESSAGE 4291. (EQD4D)

FOR ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-MATRIX
FOR MATERIAL ID =%2 WHICH IS SINGULAR.

User action:
1. MID3 FIELD ON A PSHELL POINTS TO A MAT8 ENTRY WITH G1Z OR G2Z HAVING
ZERO VALUES.
2. ENSURE THAT APPROPRIATE NON-ZERO VALUES ARE ENTERED FOR THE SHEAR
MODULI.
3. IF THE USER IS NOT INTERESTED IN MODELING TRANSVERSE SHEAR, REMOVE
THE MID FROM THE MID3 FIELD.
4. IN THE CASE THAT THE USER WISHES TO HAVE TRANSVERSE SHEAR SPECIFIED
AND DOES NOT HAVE TEST DATA TO DETERMINE G1Z AND G2Z, THEN THE
VALUE OF G12 SHOULD BE USED FOR G1Z AND G2Z.

4291.8 *** USER FATAL MESSAGE 4291.

FOR TRIAR ELEMENT WITH ID =%1
THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-MATRIX FOR MATERIAL ID =%2
WHICH IS SINGULAR.

Main Index
 MSC Nastran Error Messages 381
Errors 4000 - 4999

4291.9 *** USER FATAL MESSAGE 4291 (STR61D)

TRIA6 ELEMENT WITH ID =%1
THE MATERIAL ROUTINE -MAT- RETURNS A 2X2 J-MATRIX FOR MATERIAL ID =%2
WHICH IS SINGULAR.

4292.0 *** USER FATAL MESSAGE 4292 (EQD81D).

FOR QUAD8 ELEMENT WITH ID =%1 THE FLEXIBILITY MATRIX Z(4X4) IS SINGULAR.

4293.0 *** USER INFORMATION MESSAGE 4293.

MATERIAL -ID- 1 NOT SPECIFIED FOR %1 ELEMENT WITH ID =%2

4294.0 *** USER FATAL MESSAGE 4294.

QUAD8 ELEMENT%1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

User information: For geometric nonlinear calculation, the deformations are so large that the geometry
tests fail.

4294.1 *** USER FATAL MESSAGE 4294.

TRIA6 ELEMENT%1 HAS ILLEGAL GEOMETRY DUE TO DEFORMATIONS.

4295.0 *** USER FATAL MESSAGE 4295.

NON-LINEAR FOR ELEMENT WITH ID =%1 IS INVALID WITH MATID-1, MATID-2, MATID-
4, RESPECTIVELY =%2 NLFLAG NLTYPE =%3

User information: For a material nonlinear element an incorrect set of material identifications were
selected. Review material limitations for material nonlinear elements.

4295.2 *** USER FATAL MESSAGE 4295 (EQDRD)

NON-LINEAR FOR ELEMENT WITH ID =%1IS INVALID WITH MATID-1, MATID-2, MATID-
4, RESPECTIVELY =%2

User information: For a material nonlinear element an incorrect set of material identifications were
selected. Review material limitations for material nonlinear elements.

4295.3 *** USER FATAL MESSAGE 4295. (EQD4D)

Main Index
 382 MSC Nastran Error Messages
Errors 4000 - 4999

NON-LINEAR FOR ELEMENT WITH ID =%1 IS INVALID WITH MATID-1, MATID-2, MATID-
4, RESPECTIVELY =%2

4295.4 *** USER FATAL MESSAGE

NON-LINEAR FOR ELEMENT WITH ID =%1 IS INVALID WITH MATID-1, MATID-2, MATID-
4 RESPECTIVELY =%2 %3 %4

4295.5 *** USER FATAL MESSAGE 4295. (EQD4D)

QUAD4 ELEMENT WITH ID = %1 HAS A SINGULAR MEMBRANE MATERIAL MATRIX.
IF MAT2 IS USED, BE SURE G33 IS POSITIVE OR
IF MAT8 IS USED, BE SURE G12 IS POSITIVE.

4295.6 *** USER WARNING MESSAGE 4295 (TA1M)

HASHIN FAILURE THEORY DATA PROVIDED ON MAT8 IS NOT USED FOR ELEMENTS
WITH PSHLN1 EXTENSION USE MATF INSTEAD

4296.0 *** USER WARNING MESSAGE 4296. (SQD41D)

ILLEGAL GEOMETRY FOR QUAD4 ELEMENT WITH ID =%1

User information: This may be caused by improper specification of geometry and/or connectivity. Make
sure that the QUAD4 connectivity goes completely around the element clockwise or counter-clockwise.

4296.2 *** USER FATAL MESSAGE 4296 (EQDRD)

ILLEGAL GEOMETRY FOR QUADR ELEMENT WITH ID=%1

4296.3 *** USER FATAL MESSAGE 4296. (EQD4D)

ILLEGAL GEOMETRY FOR QUAD4 ELEMENT WITH ID = %1

User information: This may be caused by improper specification of geometry and/or connectivity. Make
sure that the QUAD4 connectivity goes completely around the element clockwise or counter-clockwise.

4296.4 *** USER FATAL MESSAGE 4296 (EQDGED)

IMPROPER GEOMETRY FOR ELEMENT WITH ID = %1

4296.5 *** USER FATAL MESSAGE 4296. (SECNSD)

ILLEGAL GEOMETRY FOR %1 ELEMENT WITH ID = %2

Main Index
 MSC Nastran Error Messages 383
Errors 4000 - 4999

4297.0 *** USER WARNING MESSAGE 4297.

QUAD4 ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR
EQUAL 180 DEGREES.

User action:
1. LOCATE THE ELEMENT WITHIN THE MODEL USING THE ELEMENT ID SPECIFIED.
2. IN THE LINEAR AND NON-LINEAR SOLUTION SEQUENCES, ALL INTERIOR ANGLES
MUST BE LESS THAN 180 DEGREES.
3. IN NON-LINEAR SOLUTION SEQUENCES, THE ELEMENT GEOMETRY MAY GET
WORSE BECAUSE OF THE DEFORMATION. CHECK THE ELEMENT GEOMETRY AT
THE INCREMENT BEFORE THE JOB STOPPED.

User information: This may be caused by improper specification of geometry and/or connectivity. Make
sure that the CQUAD4 connectivity goes completely around the element clockwise or counter-clockwise.

4297.1 *** USER FATAL MESSAGE 4297.

QUAD4 ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR
EQUAL 180 DEGREES.

User action:
1. LOCATE THE ELEMENT WITHIN THE MODEL USING THE ELEMENT ID SPECIFIED.
2. IN THE LINEAR AND NON-LINEAR SOLUTION SEQUENCES, ALL INTERIOR ANGLES
MUST BE LESS THAN 180 DEGREES.
3. IN NON-LINEAR SOLUTION SEQUENCES, THE ELEMENT GEOMETRY MAY GET
WORSE BECAUSE OF THE DEFORMATION. CHECK THE ELEMENT GEOMETRY AT
THE INCREMENT BEFORE THE JOB STOPPED.

User information: This may be caused by improper specification of geometry and/or connectivity. Make
sure that the CQUAD4 connectivity goes completely around the element clockwise or counter-clockwise.

4297.2 *** USER FATAL MESSAGE 4297 (EQDRD)

QUADR ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR
EQUAL 180 DEGREES.

4297.3 *** USER FATAL MESSAGE 4297.

Main Index
 384 MSC Nastran Error Messages
Errors 4000 - 4999

QUAD4 ELEMENT WITH ID =%1 HAS AN INTERIOR ANGLE POSSIBLY GREATER THAN OR
EQUAL 180 DEGREES.

User information: THIS ERROR MAY BE CAUSED BY SPECIFYING "MDLPRM,OFFDEF,LROFF"

WITH OFFSETS WHICH CAUSE BAD ELEMENT GEOMETRY.

4298.0 *** USER FATAL MESSAGE 4298.

A CORNER POINT MEMBRANE THICKNESS HAS NOT BEEN SPECIFIED FOR ELEMENT
WITH ID =%1 AND THERE IS NO DEFAULT VALUE ON THE ASSOCIATED PROPERTY
CARD.

4299.0 *** USER FATAL MESSAGE 4299. (SQD41D)

FOR ELEMENT WITH ID =%1 THE JACOBIAN FOR INTEGRATION POINT NUMBER %2 IS
ZERO.

User information: This may be caused by improper specification of geometry and/or connectivity. As an
example, connecting the CRACi in the wrong direction (counterclockwise) can cause this.

4299.1 *** USER FATAL MESSAGE 5479.

FOR ELEMENT WITH ID =%1
*** THE INTERNAL STRAIN MODES ARE SINGULAR.

4299.2 *** USER FATAL MESSAGE 4299.

FOR ELEMENT WITH ID =%1
*** THE JACOBIAN MATRIX IS SINGULAR.

4299.3 *** USER INFORMATION MESSAGE 4299.

FOR %1 ELEMENT WITH ID =%2 TRANSVERSE SHEAR OFFSET CORRECTION TURNED
OFF, SYSTEM(%4)= %3.

4300.0 *** USER FATAL MESSAGE 4300. (SQD41D)

FOR ELEMENT WITH ID =%1 THE THICKNESS FOR INTEGRATION POINT NUMBER %2 IS
ZERO.

4301.0 *** USER FATAL MESSAGE 4301.

Main Index
 MSC Nastran Error Messages 385
Errors 4000 - 4999

FOR ELEMENT WITH ID =%1 THE MATERIAL ROUTINE -MAT- RETURNS A 3X3 G-MATRIX
WITH EITHER OR BOTH OF TERMS G11 AND G22 EQUAL ZERO.
MATERIAL ID CONCERNED EQUALS %2

User information: The material data (Gxx and Gyy) is not supplied for the QUAD4 element. In material
nonlinear analysis this message will be issued if PARAM,NLAYERS is greater than or equal to 12 and a
stiffness update is performed during the nonlinear iterations. The avoidance is to set PARAM,NLAYERS
less than 12. If the MID2 field on the PSHELL entry is greater than 0, PARAM,NLAYERS should be set to
a value greater than 1 or bending stiffness will be ignored.

4303.0 *** USER FATAL MESSAGE 4303. (SQD41D)

FOR ELEMENT WITH ID =%1 THE FLEXIBILITY MATRIX Z(4X4) IS SINGULAR.

User information: Logic error. To avoid problem, add transverse shear flexibility.

4304.0 *** SYSTEM FATAL MESSAGE 4304.

LOGIC ERROR IN ROUTINE SQD41D FOR ELEMENT WITH ID =%1
LOC CODE =%2

4304.1 *** SYSTEM FATAL MESSAGE 4304.

LOGIC ERROR IN ROUTINE SQDR1D OR SQDR1S FOR ELEMENT WITH ID =%1
LOC CODE =%2

4305.0 *** USER INFORMATION MESSAGE 4305. (SQD41D)

MATERIAL -ID- NOT SPECIFIED FOR ELEMENT =%1

4306.0 *** USER FATAL MESSAGE 4306.

DEGENERATE GEOMETRY OR INADEQUATE MATERIAL DATA SPECIFIED FOR TRIA6
ELEMENT WITH ID =%1 REASON NUMBER =%2

User information: REASONS 1 THROUGH 5 MEAN THAT THE PROGRAM WAS UNABLE TO
FIND AN ELEMENT COORDINATE SYSTEM. REASONS 6 THROUGH 12 IMPLY THE PRO-
GRAM CANNOT FIND A LOCAL COORDINATE SYSTEM AT A GAUSS POINT. REASON 13
MAY BE DUE TO A NEGATIVE 12I/T**3 (PSHELL). REASON 14 IS DUE TO ZERO TRANS-
VERSE SHEAR THICKNESS (PSHELL). REASON 28 OCCURS IF THE ISOPARAMETRIC MAP-
PING IS UNREASONABLE, WHICH CAN OCCUR IF THE MIDSIDE NODES ARE TOO CLOSE
TO THE CORNERS.

Main Index
 386 MSC Nastran Error Messages
Errors 4000 - 4999

4311.0 *** USER FATAL MESSAGE 4311 (XSEM)

TIME EXPIRED PRIOR TO LINK %1, CALLING MODULE - %2

User information: The time specified on the TIME statement in the Executive Control Section has been
exceeded.

4312.0 *** USER WARNING MESSAGE 4312. (MCONMD)

CONM2 %1 HAS NON POSITIVE-DEFINITE INERTIA MATRIX.

User information: Most dynamic analysis methods require positive-definite mass matrices. Inserting inertia
data into the wrong fields can result in non-positive definite systems, which are not physically realistic for
normal modeling practices. Reduce the size of the off-diagonal terms to provide a positive-definite determi-
nant.

4313.0 *** USER WARNING MESSAGE 4313 (GPSP)

GRID POINT %1, REFERENCED BY CYAX, CYSUP, OR CYJOIN BULK DATA ENTRY DOES
NOT EXIST.

4313.1 *** USER FATAL MESSAGE 4313.

GRID POINT %1 REFERENCED BY CYSUP BULK DATA CARD IS UNDEFINED.

4313.2 *** USER FATAL MESSAGE 4313.

GRID POINT %1 REFERENCED BY %2 BULK DATA CARD IS UNDEFINED.

4313.4 *** USER FATAL MESSAGE 4313.

GRID POINT %1 REFERENCED BY A CYJOIN BULK DATA CARD IS UNDEFINED.

4314.0 *** USER FATAL MESSAGE 4314,

HARMONICS CARD IS REQUIRED IN CASE CONTROL DECKFOR CYCLIC SYMMETRY
ANALYSIS BUT IS NOT SUPPLIED BY USER.

4315.0 *** USER FATAL MESSAGE 4315,

OVERALL SYMMETRY OPTION IS NOT ALLOWED UNDER ROTOR AXI CYCLIC SYMME-
TRY ANALYSIS.

4316.0 *** USER FATAL MESSAGE 4316.

Main Index
 MSC Nastran Error Messages 387
Errors 4000 - 4999

GRID POINT %1 REFERENCED BY A CYAX CARD WAS ALSO DEFINED AS A SIDE%2 POINT
BY A CYJOIN CARD.

4317.0 *** USER FATAL MESSAGE 4317.

GRID POINT%1, DOF =%2. AXIS POINTS MAY NOT BE CONSTRAINED BY MULTI POINT
CONSTRAINTS.

4318.0 *** USER FATAL MESSAGE 4318.

GRID POINT ID %1 WHICH LIES ON THE AXIS OF SYMMETRY HAS ILLEGALLY DEFINED
SPC CONSTRAINTS.

4319.0 *** USER INFORMATION MESSAGE 4319.

SUPPORT POINT ID %1 HAD COMPONENT %2 DEFINED ON SPC, SPC1, OMIT,
OMIT1,CARDS OR IN RIGID ELEMENTS OR MULTIPOINT CONSTRAINTS AS DEPENDENT
COORDINATES.

4320.0 *** USER FATAL MESSAGE 4320.

SUPPORT POINT %1 WAS LOCATED ON THE %2 NSEG = %3

4321.0 *** USER WARNING MESSAGE 4321,

SOME VALUES OF THE HARMONICS SPECIFIED FOR ANALYSIS IN THE HARMONICS
CARD ARE GREATER THAN THE MAXIMUM VALUE PERMISSIBLE. VALUES OF HARMON-
ICS GREATER THAN NSEG/2 WILL NOT BE USED IN THE ANALYSIS.

4321.1 *** USER WARNING MESSAGE 4312. (MCONMD)

CONM2 %1 HAS NON POSITIVE-DEFINITE INERTIA MATRIX.

4326.0 *** USER INFORMATION MESSAGE 4326,

USER SUPPLIED LOADCYH AND GRAV CARDS ARE REPLACED AS FOLLOWS-

4327.0 *** USER INFORMATION MESSAGE 4327,

USER SUPPLIED LOADCYH AND RFORCE CARDS ARE REPLACED AS FOLLOWS-

4328.0 *** USER WARNING MESSAGE 4328, (ECONED)

THE ANISOTROPIC MATERIAL PROPERTY FOR MEMBRANE ACTION DEFINED BY MAT2
ID %1 IS INCONSISTENT WITH CONICAL SHELL THEORY. G13 AND G23 WILL BE SET TO
ZERO

Main Index
 388 MSC Nastran Error Messages
Errors 4000 - 4999

4329.0 *** USER WARNING MESSAGE 4329, (ECONED)

THE ANISOTROPIC MATERIAL PROPERTY FOR BENDING ACTION DEFINED BY MAT2 ID
%1 IS INCONSISTENT WITH CONICAL SHELL THEORY. G13 AND G23 WILL BE SET TO
ZERO

4330.0 *** USER WARNING MESSAGE 4330,

THE ANISOTROPIC MATERIAL PROPERTY FOR TRANSVERSE SHEAR ACTION DEFINED
BY MAT2 ID %1 IS INCONSISTENT WITH CONICAL SHELL THEORY. G13 AND G23 WILL
BE SET TO ZERO

4330.2 *** USER WARNING MESSAGE 4330,

THE ANISOTROPIC MATERIAL PROPERTY FOR TRANSVERSE SHEAR ACTION DEFINED
BY MAT2 ID %1 IS INCONSISTENT WITH CONICAL SHELL THEORY. G12 WILL BE SET TO
ZERO

4334.0 *** USER FATAL MESSAGE 4334 ***,

NON - POSITIVE DEFINITE MASS MATRIX FOUND IN DYNAMIC REDUCTION.

User information: Generalized dynamic reduction assumes a non-negative definite mass matrix. This pre-
vents computation of modes with negative generalized mass. User input of negative mass, large off-diagonal
mass terms, or requesting more modes than there are independent degrees of freedom with mass can lead to
this condition. Inspect the input mass data for the conditions described above, or reduce FMAX if the
number of degrees of freedom with mass is not adequate.

4335.0 *** USER FATAL MESSAGE 4335.

THERE MAY ONLY BE ONE SUPPORT POINT. ALL OF THE FOLLOWING WERE ENCOUN-
TERED ON CYSUP BULK DATA CARDS.

4336.0 *** USER FATAL MESSAGE 4336,

CYSYM BULK DATA CARD MUST BE PRESENT IN CYCLIC SYMMETRY ANALYSIS, BUT IS
NOT SPECIFIED IN THE DECK.

Main Index
 MSC Nastran Error Messages 389
Errors 4000 - 4999

4337.0 *** USER FATAL MESSAGE 4337,

HARMONICS SET SPECIFIED ON HOUTPUT CASE CONTROL CARD IS UNDEFINED.

User information: The HOUTPUT Case Control command defines the values of harmonics for which
output will be produced. The set ID specified by this command is not defined in Case Control.

4338.0 *** USER FATAL MESSAGE 4338,

SEGMENTS SET SPECIFIED ON NOUTPUT CASE CONTROL CARD IS UNDEFINED.

User information: The NOUTPUT Case Control command defines the values of segments for which out-
put will be produced. The set ID specified by this command is not defined in Case Control Section.

4339.0 *** USER FATAL MESSAGE 4339,

HARMONICS SET SPECIFIED ON NOUTPUT CASE CONTROL CARD IS UNDEFINED.

User information: In the solution of vibration problems, the segment output can be selected for a specified
set of harmonics. The set of harmonics specified in the NOUTPUT Case Control command is not defined
in the Case Control.

4340.0 *** USER FATAL MESSAGE 4340,

LINEAR COMBINATION OF SUBCASES NOT ALLOWED IN CYCLIC SYMMETRY ANALYSIS.

User information: SUBCOMS and/or SYMCOMS are not allowed in cyclic symmetry analysis. Delete
requests of SUBCOMS and/or SYMCOMS.

4340.1 *** USER FATAL MESSAGE 4340,

SUBCOM, SYMCOM OR REPCASE MAY NOT BE EMPLOYED WHEN THE EXTSEOUT or
EXTMDOUT CASE CONTROL COMMAND IS SPECIFIED

User information: SUBCOM, SYMCOM AND REPCASE ARE NOT MEANINGFUL WHEN THE
EXTSEOUT or EXTMDOUT CASE CONTROL COMMAND IS SPECIFIED

4340.2 *** USER FATAL MESSAGE 4340,

Main Index
 390 MSC Nastran Error Messages
Errors 4000 - 4999

%1 CASE CONTROL COMMAND FOUND FOR THE FIRST TIME IN SUBCASE OTHER
THAN FIRST SUBCASE.

User information: INSERT %1 COMMAND IN THE FIRST SUBCASE OR MOVE THE SUBCASE
WITH ERP AS THE FIRST SUBCASE.

4341.0 *** USER FATAL MESSAGE 4341,

HARMONICS SET SPECIFIED FOR ANALYSIS IS UNDEFINED.

User information: The values of harmonics for which analysis will be performed is given by the set specified
in the HARMONICS Case Control Section. This set is not defined. Define the set of integer values of har-
monics for analysis.

4342.0 *** USER FATAL MESSAGE 4342,

THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALY-
SIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE.

User information: The load specified by LOADCYH Bulk Data entry should specify loading for harmon-
ics that are valid for the problem. For example, the integer value of the harmonics that are loaded should be
contained in the analysis harmonics set and furthermore the harmonic type should also be contained in
analysis harmonics type. If not, this fatal message will result. Similarly, the load specified by LOADCYN
Bulk Data entry should specify loading for segments that are in the model. In addition, if symmetry option
is used in DIHEDRAL type problems, the load should be applied in segments in the first half-plane (or
quadrant) of the model. Specify valid harmonic loading or segment loading. In buckling problems, the
static preload must be the same for all segments, which is ensured by providing a zero (cosine) harmonic
loading. For such problems, this fatal message will result if the loading is specified any other way than via
LOADCYH entry. See also Error Report 3502 in Chapter 17.

4342.1 *** USER FATAL MESSAGE 4342,

THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALY-
SIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE.

LOADCYN %1 %2%3 %4
4342.2 *** USER FATAL MESSAGE 4342,
THE LOAD BULK DATA CARD GIVEN BELOW IS INCONSISTENT WITH SPECIFIED ANALY-
SIS HARMONICS OR SEGMENTS OR SYMMETRY TYPE.
LOADCYH %1 %2%3 %4

Main Index
 MSC Nastran Error Messages 391
Errors 4000 - 4999

4343.0 *** USER FATAL MESSAGE 4343,

LOAD ID = %1 WAS ILLEGALLY REFERENCED BY BOTH LOADCYH AND LOADCYN
CARDS.

User information: The same load set ID has been referenced by both LOADCYH and LOADCYN Bulk
Data entries. This is illegal. Define separate load IDs for loads referenced by LOADCYH and LOADCYN
entries.

4344.0 *** USER FATAL MESSAGE 4344,

SELECTED LOAD SET, ID =%1 WAS NOT DEFINED ONA LOADCYH, LOADCYN OR LOAD-
CYT CARD.

User information: The load set ID selected in case control is not defined by a LOADCYH, LOADCYN
and/or LOADCYT Bulk Data entry. Define the load set ID selected in case control by means of LOAD-
CYH, LOADCYN, and/or LOADCYT Bulk Data entry.

4345.0 *** USER FATAL MESSAGE 4345,

USER SPECIFIED CASE CONTROL LOAD ID =%1 WHICH SPECIFIES A %2 LOAD ID =%3
WHICH WAS USED ELSEWHERE.

4346.0 *** USER FATAL MESSAGE 4346 (CY1NFR FRRD1A and dopr3)
THE FREQUENCY SET %1 SELECTED IN CASE CONTROL IS NOT DEFINED IN THE BULK
DATA BY FREQi ENTRIES.

User information: Define the set of frequencies to be used for analysis.

4346.1 *** USER FATAL MESSAGE 4346 (FRRD1A)

THE DYNAMIC LOAD SET %1 SELECTED BY THE DLOAD CASE CONTROL COMMAND IS
NOT DEFINED IN THE BULK DATA BY RLOADi, TLOADi OR ACSRCE ENTRIES.

User information: Define the excitations to be used for the analysis.

4346.2 *** USER FATAL MESSAGE 4346 (FRRD1A)

Main Index
 392 MSC Nastran Error Messages
Errors 4000 - 4999

THE DYNAMIC LOAD SET %1 SELECTED BY THE DLOAD BULK DATA ENTRY %2 IS NOT
DEFINED IN THE BULK DATA BY RLOADi, TLOADi OR ACSRCE ENTRIES.

User information: Define all of the excitations specified on the DLOAD Bulk Data entry.

4346.3 *** USER FATAL MESSAGE 4346 (TRLGA)

THE DYNAMIC LOAD SET %1 SELECTED BY THE DLOAD CASE CONTROL COMMAND IS
NOT DEFINED IN THE BULK DATA BY TLOADi ENTRIES.

User information: Define the excitations to be used for the analysis.

4346.4 *** USER FATAL MESSAGE 4346 (TRLGA)

THE DYNAMIC LOAD SET %1 SELECTED BY THE DLOAD BULK DATA ENTRY %2 IS NOT
DEFINED IN THE BULK DATA BY TLOADi ENTRIES.

User information: Define all of the excitations specified on the DLOAD Bulk Data entry.

4346.5 *** USER FATAL MESSAGE 4346 (FRRD1A)

TABLEDi %1 REFERENCED BY AN RLOADi, TLOAD1 OR ACSRCE ENTRY IS NOT DEFINED
IN THE BULK DATA

User information: Define the tables to be used for the analysis.

4346.6 *** USER FATAL MESSAGE 4346 (TRLGCD/S)

TABLEDi %1 REFERENCED BY A TLOAD1 ENTRY IS NOT DEFINED IN THE BULK DATA

User information: Define the tables to be used for the analysis.

4346.7 *** USER WARNING MESSAGE 4346 (NL3INT)

A TTEMP Bulk Data entry references a TABLEDi ID=%1 entry which IS NOT DEFINED.

4346.8 *** USER FATAL MESSAGE 4346 (FmChkDYN)

The dynamic load set %1 selected by the DLOAD Case Control command is not defined in the bulk data
by DLOAD, RLOADi, TLOADi, ACLOAD or ACSRCE entries.

Main Index
 MSC Nastran Error Messages 393
Errors 4000 - 4999

4346.9 *** USER FATAL MESSAGE 4346 (FmChkDYN)

The ID %1 selected by %2 case control in SUBCASE %3 is not defined in the bulk data by %4 entries.

4346.10 *** USER WARNING MESSAGE 4346 (ROTUTL)

There are no TABLEDi entries with TID=%1.

4347.0 *** USER FATAL MESSAGE 4347,

RFORCE OPTION SPECIFIED ON LOADCYH CARD, BUT NO RFORCE CARD FOUND.

User information: Define RFORCE Bulk Data entry selected by LOADCYH Bulk Data entry.

4348.0 *** USER FATAL MESSAGE 4348,

GRAV OPTION SPECIFIED ON LOADCYH CARD, BUT NO GRAV CARD FOUND.

User information: Define GRAV loading via GRAV Bulk Data entry.

4349.0 *** USER FATAL MESSAGE 4349 (GP4)

THERE ARE LAGRANGE RIGID ELEMENTS IN THE MODEL (RBAR, RBE1, RBE2, RBE3,
RJOINT, RROD, RPRPLT) AND AN EXTERNAL SUPERELEMENT GENERATION REQUEST
(EXTSEOUT or EXTMDOUT OR PARAM,EXTOUT).

User information: AN EXTERNAL SUPERELEMENT (CREATED WITH THE EXTSEOUT or

EXTMDOUT CASE CONTROL COMMAND OR THE EXTOUT PARAMETER) CANNOT
CONTAIN LAGRANGE RIGID ELEMENTS.

4350.0 *** USER FATAL MESSAGE 4350,

LOADCYT CARD WITH SID= %1, SPECIFIES NON-EXISTENT TABLE ID=%2

4351.0 *** USER WARNING MESSAGE 4351,

TEMPERATURE/DEFORMATION SET ID = %1 SPECIFIES INPUT IN HARMONIC VARI-
ABLES. PHYSICAL ELEMENT STRESS OUTPUT WILL BE IN ERROR, USE ONLY STRESS
OUTPUT IN HARMONIC VARIABLES.

4352.0 *** USER WARNING MESSAGE 4352,

Main Index
 394 MSC Nastran Error Messages
Errors 4000 - 4999

TEMPERATURE/DEFORMATION SET ID = %1 SPECIFIES INPUT IN PHYSICAL VARIABLES.

HARMONIC ELEMENT STRESS OUTPUT WILL BE IN ERROR, USE ONLY STRESS OUTPUT
IN PHYSICAL VARIABLES.

4353.0 *** USER FATAL MESSAGE 4353

DMIG MATRICES SELECTED BY K2GG, M2GG, B2GG OR K42GG DO NOT HAVE
SYMMETRIC FORM (IFO=6).

User information: DMIG matrices added before constraints are applied must be symmetric in form. The
form is specified in the IFO field (Field 4) of the DMIG entry. Set IFO to 6.

4354.0 *** USER FATAL MESSAGE 4354 (MTRXIN)

POINT %2 DOES NOT HAVE A COMPONENT %3 AS HAS BEEN SPECIFIED ON DMIG %1

User information: This can happen if point %2 is an EPOINT or SPOINT and COMPONENT %3 is
not zero or one.

Programmer information: This can happen if MATPOOL is created with Option 16 of the MATMOD
but this point and component is inconsistent with the EQEXIN table input to the MTRXIN module.

4356.0 *** USER WARNING MESSAGE 4356,

MATMOD MODULE OPTION 16 WILL NOT PROCESS MATRIX %1 BECAUSE IT IS NOT OF
FORM 1, 2 OR 6.

User information: This option converts MSC NASTRAN matrices to DMIG entry formats. The other
forms of matrices are not suitable for DMIG formats. Convert the matrix to the proper form using the
MODTRL and ADD modules.

4357.0 *** USER WARNING MESSAGE 4357,

MATRIX %1 INPUT TO MATMOD OPTION 16 HAS %2 ROWS AND %3 COLUMNS. G-SIZE
IS %4. NO OUTPUT PRODUCED.

User information: All matrices input for Option 16 with third parameter = 0 must have g-size rows. If they
are Form 1 or 6, they must also have g-size columns. Merge the matrices to g-size.

4357.1 *** USER WARNING MESSAGE 4357,

Main Index
 MSC Nastran Error Messages 395
Errors 4000 - 4999

MATRIX %1 INPUT TO MATMOD OPTION 16 IS SYMMETRIC OR SQUARE, BUT ROW SET

IS "%2" AND COLUMN SET IS "%3". NO OUTPUT PRODUCED.

User information: Matrices of Form 1 or 6 input for Option 16 must have the same set for both rows and
columns. Check the data to ensure this condition is satisfied.

4357.2 *** USER WARNING MESSAGE 4357,

MATRIX %1 INPUT TO MATMOD OPTION 16 HAS %2 ROWS AND %3 COLUMNS, BUT
ROW SET "%4" SIZE IS %5 AND COLUMN SET "%6" SIZE IS %7. NO OUTPUT PRODUCED.

User information: The number of rows and columns of matrices input for Option 16 must match the size
corresponding to the sets specified. Check the data to ensure this condition is satisfied.
4357.3 *** USER WARNING MESSAGE 4357,
MATRIX %1 INPUT TO MATMOD OPTION 16 HAS %2 ROWS, BUT ROW SET "%3" SIZE IS
%4. NO OUTPUT PRODUCED.

User information: The number of rows and columns of matrices input for Option 16 must match the size
corresponding to the sets specified. Check the data to ensure this condition is satisfied.

4358.0 *** USER FATAL MESSAGE 4358.

SUPPORT POINT IS ILLEGALLY SPECIFIED AS A SCALAR POINT.

User information: The support point should be a grid point in cyclic symmetry analysis. Redefine the sup-
port point such that it is a grid point and not a scalar point.

4359.0 *** USER WARNING MESSAGE 4359.

COMPONENT%1 REFERENCED ON CYSUP BULK DATA CARD FORCES COMPONENT%2
TO ALSO BE SUPPORTED.

User information: See CYSUP Bulk Data entry for explanatory remarks.

4360.0 *** USER WARNING MESSAGE 4360.

COMPONENT 2 WILL BE SUPPORTED INSTEAD OF COMPONENT 6, AS REFERENCED ON
THE CYSUP BULK DATA CARD.

User information: See CYSUP Bulk Data entry for explanatory remarks.

Main Index
 396 MSC Nastran Error Messages
Errors 4000 - 4999

4361.0 *** USER INFORMATION MESSAGE 4361 (SEQRS).

SINCE THE ORIGINAL PERFORMANCE IS BETTER THAN THE RESEQUENCED PERFOR-
MANCE DATA, THE NEW SEQGP ENTRIES WILL NOT BE GENERATED.

4362.0 *** USER FATAL MESSAGE 4362.

INTERIOR POINTS ILLEGALLY DEFINED IN THE AXI OPTION OF THE CYCLIC SYMME-
TRY PROBLEM.

User information: In the AXI option of cyclic symmetry, all degrees of freedom must be on Side 1, Side 2,
or on the axis. Define all grid points to be on Side 1, Side 2, or on the axis.

4363.0 *** USER FATAL MESSAGE 4363,

SYMMETRY ON TWO PLANES OF THE MODEL ILLEGALLY SPECIFIED WITH ODD NUM-
BER OF SEGMENTS.

User information: Symmetry on the planes of the model is allowed only when the total number of seg-
ments is even. Use only symmetry with respect to Side 1 of Segment 1 of the model.

4364.0 *** USER FATAL MESSAGE 4364.

COMPONENT %1 OF GRID POINTS %2,%3 CANNOT BE CONNECTED. (GRID POINT %4 IS
AT FAULT)

User information: In the AXI option of CYCLIC symmetry, all degrees of freedom in the analysis set must
be on SIDE 1, SIDE 2, or on the AXIS. If a SIDE 2, or on the AXIS. If a degree of freedom is on either
SIDE 1 or SIDE 2, then its connected d.o.f. must not be constrained out in any way. (This same condition
is only a warning error for the ROT option.) Make all SIDE 1 and SIDE 2 points meet the above stated
restrictions.

4365.0 *** USER INFORMATION MESSAGE 4365

USER SUPPLIED LOADCYT BULK DATA CARD (SID = %1) IS USED AS EQUIVALENT TO
THE FOLLOWING LOADCYH CARD(S).

User information: When Method = 0 (or blank) option is used with the LOADCYT Bulk Data entry, the
magnitude of the load (specified by the loadset ID) will be multiplied by the following harmonic coeffi-
cients.

4366.0 *** USER INFORMATION MESSAGE 4366

Main Index
 MSC Nastran Error Messages 397
Errors 4000 - 4999

USER SUPPLIED LOADCYT BULK DATA CARD (SID = %1) IS USED AS EQUIVALENT TO
THE FOLLOWING LOADCYN CARD(S).

User information: When Method = 1 option is used with the LOADCYT Bulk Data entry, the magnitude
of the load (specified by the LOADSET ID) at corresponding points in the various segments of the model
will be multiplied by the following scale factors.

4367.0 *** USER INFORMATION MESSAGE 4367.

STATISTICS FOR UNSYMMETRIC DECOMPOSITION OF DATA BLOCK %1 FOLLOW NUM-
BER OF PIVOT OPERATIONS = %2

User information: Pivot operations only occur when the ratio of the diagonal term of the pivot row to the
largest term in the pivot column is less than the threshold. (Default = 1.E-6) See the MSC NASTRAN
Numerical Methods User's Guide.

4368.0 *** USER WARNING MESSAGE 4368---,

THERE MAY BE INSUFFICIENT TIME TO COMPLETE GENERALIZED DYNAMIC REDUC-
TION. TIME REQUIRED IS%1 SECONDS.

User information: THE RUN WILL BE ALLOWED TO PROCEED BECAUSE CPU TIME ESTI-
MATES, IN SOME CASE, ARE POOR. An interval time estimate made using parameters reflecting the
users model, indicates that DYNAMIC reduction module will consume more than the user allowed for
when the time estimate was set for the entire job.

4368.1 *** USER FATAL MESSAGE 4368---,

INSUFFICIENT TIME TO COMPLETE GENERALIZED DYNAMIC REDUCTION. TIME
REQUIRED IS%1 SECONDS.

User information: An interval time estimate made using parameters reflecting the users model, indicates
that DYNAMIC reduction module will consume more than the user allowed for when the time estimate
was set for the entire job.

4369.0 *** USER FATAL MESSAGE 4369.

Main Index
 398 MSC Nastran Error Messages
Errors 4000 - 4999

FOR THE DIH OR AXI OPTION OF CYCLIC SYMMETRY (EXCEPT FOR HEAT TRANSFER)
THE DEGREE OF FREEDOM NORMAL TO SIDE 1 (AND/OR SIDE 2) - FIELD 3 CYJOIN BULK
DATA CARD - MUST BE DEFINED.

User information: Field 3 of the CYJOIN entry for Side 1 must be filled in for non-heat transfer problems.
Supply degree of freedom perpendicular to Side 1 (and/or Side 2) in Field 3 of CYJOIN Bulk Data entry.

4370.0 *** SYSTEM FATAL MESSAGE 4370.

DECOMPOSITION REQUIRES THAT PRECISION OF DATA BLOCK %1 EQUAL SYSTEM
PRECISION.

System information: The symmetric and unsymmetric decomposition routines require that the input
matrix be single precision for CDC and CRAY machines, and double precision for all other machines.

4372.0 *** USER WARNING MESSAGE 4372 (NLTINT)

*** NO NONLINEAR ELEMENTS HAVE BEEN FOUND FOR NONLINEAR ANALYSIS SOLU-
TION. USE ADAPT METHOD FOR LINEAR PROBLEMS.

User information: Material nonlinear analysis solution sequences must have at least one nonlinear element.

4375.0 *** USER FATAL MESSAGE 4375,

SUBCASE LISTS ARE ILLEGAL FOR AUTO OR PSDF REQUESTS

4376.0 *** USER FATAL MESSAGE 4376.

ILLEGAL NUMBER OF SUPPORT POINTS ARE GIVEN FOR AUTOMATIC RIGID BODY
MATRIX CALCULATION. SIX ARE REQUIRED.

User information: Module VECPLOT provides an option to compute a rigid-body transformation matrix
based on grid point coordinates. To use this option, there must be six, and only six, r-set degrees of freedom
specified on SUPORT entries. This option is commonly used in component modal synthesis using external
superelements. The user must provide six degrees-of-freedom on SUPORT entries or input the rigid-body
transformation on DMIG entries.

4377.0 *** USER FATAL MESSAGE 4377 (IFS3P)

Main Index
 MSC Nastran Error Messages 399
Errors 4000 - 4999

PCOMP ID. %1 HAS NO PLY DATA.

User action: VERIFY EXISTENCE AND/OR UNIQUENESS OF CONTINUATION FIELD(S)

User information: User supplied no ply information for the specified PCOMP bulk data entry. Supply
some ply data.

4377.1 *** USER FATAL MESSAGE 4377

PCOMP ID.%1 HAS NO PLY DATA

User information: User supplied no ply information for the specified PCOMP bulk data entry. Supply
some ply data.

4377.2 *** USER FATAL MESSAGE 4377 (IFS3P)

PCOMP ID. %1 HAS NO PLY DATA.

User action: VERIFY EXISTENCE AND/OR UNIQUENESS OF CONTINUATION FIELD(S)

4377.3 *** USER FATAL MESSAGE 4377

PCOMP ID.%1 HAS NO PLY DATA

4378.0 *** USER WARNING MESSAGE 6279 (IFS6P)

REPEATED STATIONS (X/XB) ARE SPECIFIED ON PBEAM %1

User action: ADJUST THE VALUE (X/XB) SLIGHTLY FOR ONE OF THE REPEATED
STATIONS.

4379.0 *** USER INFORMATION MESSAGE 4379,

THE USER SUPPLIED PCOMP BULK DATA CARDS ARE REPLACED BY THE FOLLOWING
PSHELL AND MAT2 CARDS. WARNING, MAT2 RECORDS WITH MID GREATER THAN
400000000 USE A SPECIAL FORMAT FOR PCOMPS. REFER TO REMARK 13 OF THE MAT2
DESCRIPTION IN THE MSC NASTRAN QUICK REFERENCE GUIDE.

User information: Output is only produced when PCOMP Bulk Data entries are present and sorted
ECHO output is requested.

Main Index
 400 MSC Nastran Error Messages
Errors 4000 - 4999

4379.1 *** USER INFORMATION MESSAGE 4379 (IFP9A)

THE USER SUPPLIED %1 BULK DATA ENTRIES ARE REPLACED BY THE FOLLOWING %2
ENTRIES. CONVERSION METHOD FOR PBARL/PBEAML - %3.

4379.2 *** USER INFORMATION MESSAGE 4379

PCOMP BULK DATA ENTRIES HAVE BEEN CONVERTED TO EQUIVALENT PSHELL AND
MAT2 ENTRIES. TO VIEW THE PSHELL AND MAT2 ENTRIES, SPECIFY NASTRAN PRTP-
COMP OR NASTRAN SYSTEM(361)=1.

4379.3 *** USER INFORMATION MESSAGE 4379 (MDG2E6)

THE BULK DATA ENTRIES CBAR AND PBAR HAVE BEEN CONVERTED TO EQUIVALENT
CBEAM AND PBEAM ENTRIES. TO VIEW THE CBEAM AND PBEAM ENTRIES, SPECIFY NAS-
TRAN BRTOBM=-1 OR NASTRAN SYSTEM(416)=-1.

4379.4 *** USER INFORMATION MESSAGE 4379 (MDG2E6)

THE BULK DATA ENTRIES CBAR AND PBAR HAVE BEEN CONVERTED TO THE FOLLOW-
ING EQUIVALENT CBEAM AND PBEAM ENTRIES.

4379.5 *** USER INFORMATION MESSAGE 4379 (MDG2E7)

THE BULK DATA ENTRIES CSHEAR, PSHEAR, AND ITS RELATED MAT1 HAVE BEEN CON-
VERTED TO EQUIVALENT CQUAD4/PSHELL/MAT2 AND CROD/PROD. TO VIEW THE
CONVERTED ENTRIES, SPECIFY NASTRAN SHRTOQ4=2 OR NASTRAN SYSTEM(417)=2.

4379.6 *** USER INFORMATION MESSAGE 4379 (MDG2E7)

THE BULK DATA ENTRIES CSHEAR, PSHEAR, AND ITS RELATED MAT1 HAVE BEEN CON-
VERTED TO THE FOLLOWING EQUIVALENT CQUAD4/PSHELL/MAT2 AND CROD/PROD.

4379.7 *** USER INFORMATION MESSAGE 4379 (MDG2E6)

THE BULK DATA ENTRIES CBAR AND PBAR HAVE BEEN CONVERTED TO EQUIVALENT
CBEAM AND PBEAM ENTRIES. EQUIVALENT CBEAM AND PBEAM HAVE BEEN GENER-
ATED FOR OFFSETS, IF ANY. TO VIEW THE CBEAM AND PBEAM ENTRIES, SPECIFY NAS-
TRAN BRTOBM=-2 OR NASTRAN SYSTEM(416)=-2.

4379.8 *** USER INFORMATION MESSAGE 4379 (MDG2E6)

THE BULK DATA ENTRIES CBAR, PBAR AND ITS OFFSETS, IF ANY, HAVE BEEN CON-
VERTED TO THE FOLLOWING EQUIVALENT CBEAM AND PBEAM ENTRIES.

Main Index
 MSC Nastran Error Messages 401
Errors 4000 - 4999

4380.0 *** SYSTEM FATAL MESSAGE 4380

RECORD ID =%1 %2 IS OUT OF SYNC ON DATA BLOCK NUMBER %3 AN %4 SYSTEM
ERROR.

System information: IFP output files of either EPT or MPT were not properly formed.

4381.0 *** SYSTEM FATAL MESSAGE 4381 (IFP6)

ABNORMAL END OF PCOMP RECORD ENCOUNTED ON DATA BLOCK%1

System information: An unexpected end of record mark was encountered while processing the PCOMP
record as output by IFP. Check PCOMP Bulk Data entries for proper format.

4381.1 *** SYSTEM FATAL MESSAGE 4381 (IFP6)

PCOMPLS ENTRY IS ONLY SUPPORTED IN SOL 400, SOL 600 and SOL 700

4382.0 *** USER FATAL MESSAGE 4382 (IFP9)

THERE ARE PBEAML/PBMSECT AND PBEAM BULK DATA ENTRIES WITH DUPLICATE ID =
%1.

4382.1 *** USER FATAL MESSAGE 4382 (IFP9)

THERE ARE PBARL/PBRSECT AND PBAR BULK DATA ENTRIES WITH DUPLICATE ID = %1.

4382.2
PCOMP AND PSHELL IDENTIFICATION %1 WAS DUPLICATED THERE ARE PCOMP AND
PSHELL BULK DATA ENTRIES WITH DUPLICATE ID = %1.

User information: While merging the new PSHELL bulk data entries generated from the presence of the
PCOMP bulk data entries a duplicate identification number (PID) was encountered within the user sup-
plied PSHELL data. The user record is temporarily copied to the EPT data block to continue preface pro-
cessing. Remove duplicate identification.

PCOMP AND PCOMPG IDENTIFICATION %1 WAS DUPLICATED THERE ARE PCOMP AND
4382.3
PCOMPG BULK DATA ENTRIES WITH DUPLICATE ID = %1.

4382.4 *** USER FATAL MESSAGE 4382 (IFP9)

THERE ARE PBRSECT AND PBARL BULK DATA ENTRIES WITH DUPLICATE ID = %1.

Main Index
 402 MSC Nastran Error Messages
Errors 4000 - 4999

4382.5 *** USER FATAL MESSAGE 4382 (IFP9)

THERE ARE PBMSECT AND PBEAML BULK DATA ENTRIES WITH DUPLICATE ID = %1.

4382.6 *** USER FATAL MESSAGE 4382 (IFP9)

SET3 ID %1 HAS BEEN USED ON SET1 ALREADY.

4382.7 *** USER FATAL MESSAGE 4382 (IFP9)

BOTH SET1 AND SET3 ENTRIES ARE MISSING, A REQUIRED INPUT FOR PBRSECT/PBM-
SECT.

4382.8 *** USER FATAL MESSAGE 4382 (IFP10)

SPAWNED PCOMP/PCOMPG AND PSHELL IDENTIFICATION %1 WAS DUPLICATED

User information: While merging the new PCOMP/PCOMPG bulk data entries generated from the pres-
ence of the TOMVAR bulk data entries a duplicate identification number (PID) was encountered within
the user supplied PSHELL/PCOMP/PCOMPG data.

User action: RESET PSHELL OR PCOMP/PCOMPG ID = %1 OUTSIDE THE RANGE: %2

THROUGH %3

4382.9 *** USER FATAL MESSAGE 4382 (IFP10)

TOPVAR CANNOT BE USED WITH DVMREL1 or DVMREL2

4382.10 *** USER FATAL MESSAGE 4382 (IFP10)

TOMVAR WITH STRESS CONSTRAINTS CANNOT BE USED WITH TOPVAR or BEADVAR or
DESVAR

4382.11 *** USER FATAL MESSAGE 4382 (IFP10)

TOPVAR WITH STRESS CONSTRAINTS CANNOT BE USED WITH TOMVAR or BEADVAR or
DESVAR

4382.12 *** USER WARNING MESSAGE 4382 (IFP9)

NOW USING BEAM LIBRARY EQUATIONS TO COMPUTE PROPERTIES FOR PBARL/
PBEAML %1.
(AUTO MESH ERROR CODE:%2)

Main Index
 MSC Nastran Error Messages 403
Errors 4000 - 4999

4383.0 *** USER FATAL MESSAGE 4383

TRANSVERSE SHEAR MATERIAL MATRIX IS SINGULAR FOR PCOMP %1

User information: Review properties given for MAT2 and MAT8 bulk data entries for specified PCOMP
record causing error.

4384.0 *** USER FATAL MESSAGE 4384

THERMAL MATRIX INVERSION FAILURE FOR PCOMP %1 MID %2

User information: Review properties given for MAT2 and MAT8 bulk data entries for specified PCOMP
record causing error.

4385.0 *** USER WARNING MESSAGE 4385,

STRESS PROCESSING FOR %1 ELEMENTS IN SUBCASE %2 NOT COMPLETE BECAUSE OF
INSUFFICIENT DATA IN DATA BLOCK %3

User information: The composite stress was not calculated for the noted element type in a particular sub-
case because the data needed could not be found. If the data block is the force data block, then perhaps
forces were not requested in this subcase. If the data block is any other, the problem is a programming bug.

4386.0 *** USER WARNING MESSAGE 4386,

COMPOSITE STRESSES FOR ELEMENT %1 NOT CALCULATED. FORCE RECORD WAS NOT
FOUND

User information: For composite stress calculations there must be a force element record for each requested
stress. Match up the stress and force requests or make the stress request a subset of the force request.

4386.1 *** USER WARNING MESSAGE 4386 (SDRCMoc)

Composite stresses for %1 is not calculated. Force record was not found.

User information: For composite stress calculations there must be a force record for each requested stress.
Match up the stress and force requests or make the stress request a subset of the force request.

4387.0 *** USER INFORMATION MESSAGE 4387.

THE FOLLOWING TABLE SUMMARIZES THE SIZE IN BLOCKS OF INTERNAL PERMANENT
UNITS NAME SIZE

Main Index
 404 MSC Nastran Error Messages
Errors 4000 - 4999

4388.0 *** USER FATAL MESSAGE 4388.

AXIS POINT %1 DEFINED BY THE CYAX BULK DATA CARD HAS COMPONENTS OF
MOTION IN THE O-SET.

User information: If there are ASET, ASET1 and/or OMIT, OMIT1 bulk data entries present the compo-
nents of axis points must be in the analysis set. Include degrees of freedom of axis points in the a-set.

4390.0 *** USER FATAL MESSAGE 4390,

LSEQ ENTRY %1 REQUESTED VIA LOADSET FOR SUPERELEMENT OR MODULE %2 DOES
NOT EXIST IN THE BULK DATA

User information: A LOADSET entry has selected a set of LSEQ bulk data entries which do not exist in
the static load table. Check bulk data LSEQ entries for proper set ID.

4390.1 *** USER FATAL MESSAGE 4390,

LSEQ ENTRY %1 REQUESTED VIA LOADSET DOES NOT EXIST IN THE BULK DATA

User information: A LOADSET entry has selected a set of LSEQ bulk data entries which do not exist in
the static load table. Check bulk data LSEQ entries for proper set ID.

4391.0 *** USER FATAL MESSAGE 4391,

NON-UNIQUE EXCITATION SET %1 HAS BEEN SPECIFIED FOR LSEQ DEFINED VECTOR
%2.

User information: Each vector number defined on an LSEQ Bulk Data entry must have a unique exci-
tation set specification, i.e., the combination of vector number and excitation set number must be main-
tained throughout all LSEQ sets. Make sure that each vector number "X" always specifies the same
excitation "Y", regardless of which LSEQ set the vector is in.

4392.0 *** USER FATAL MESSAGE 4392 (ST2DN0)

THE LOADSET CASE CONTROL COMMAND (LOADSET= %1 ) is specified in static subcase %2
STEP %3.

User information: LOADSET IS only SUPPORTED WHEN ANALYSIS=NLTRAN .

User action: USE the LOAD CASE CONTROL COMMAND.

Main Index
 MSC Nastran Error Messages 405
Errors 4000 - 4999

4392.1 *** USER FATAL MESSAGE 4392 (ST2DN0)

The LOADSET case control command (LOADSET=%1) is specified in static SUBCASE %2 STEP %3
SUBSTEP %4.

User information: LOADSET is only supported when ANALYSIS=NLTRAN.

User action: Use the LOAD case control command.

4393.0 *** USER FATAL MESSAGE 4393.

ILLEGAL DELETE CARD.

User information: A delete card contains a / in Field 1, a positive integer in Field 2 and a positive integer or
blank in Field 3. If Field 3 is non-blank, its contents must be greater than or equal to Field 2. Failing to
meet any of these conditions results in the error message. It may be best to use free-field format (i.e., /,a,b).

4394.0 *** USER WARNING MESSAGE 4394 (MODB)

SOLUTION SIZE REDUCTION PARAMETER %1 IS NOT APPROPRIATE FOR THIS PROB-
LEM.

User information: The MODB module has been asked to retain more vectors than exist. The module will
retain all that have been found.

4395.0 *** USER WARNING MESSAGE 4395 (MODB)

PROBLEM SIZE (VECTORS RETAINED) HAS BEEN REDUCED TO %1 VECTORS.

User information: The number of vectors retained has been reduced by user request.

4396.0 *** USER INFORMATION MESSAGE 4396 (MODB)

MASS CONVERGENCE OF %1 ACHIEVED AFTER %2 CYCLES.

User information: The generalized masses have all passed the test (M(new) - N(old)) / M(new) < = MVAR

4397.0 *** USER INFORMATION MESSAGE 4397 (MODB)

Main Index
 406 MSC Nastran Error Messages
Errors 4000 - 4999

FREQUENCY CONVERGENCE OF %1 ACHIEVED AFTER %2 CYCLES.

User information: The frequencies (f) have all (not including f < .01) passed the test.

4398.0 *** USER WARNING MESSAGE 4398 (GPSP)

GRID POINT %1 FOR %2DEGREES OF FREEDOM DOES NOT PASS SYMMETRY CHECK.
NO SINGULARITY TESTS MADE ON THESE TERMS.
%3
%4
%5

User information: The stiffness matrix is inspected for singularities before any user-supplied unsymmetric
terms are allowed. The solution technique makes it unlikely that correct answers will result if unsymmetric
terms exist. When these tests are made, the three-by-three stiffness matrix terms printed are the terms about
the diagonal of the listed grid point, normalized to the largest term in the three-by-three submatrix. Likely
causes are unsymmetric terms from user-supplied matrices, downstream superelements whose upstream
members have mechanisms suppressed due to use of PARAM,MAXRATIO or PARAM,BAILOUT, or
errors in MSC NASTRAN code. If the stiffness terms were generated from MSC NASTRAN elements
rather than matrices from outside MSC NASTRAN, and no large factor-to-diagonal messages are present,
please send runs to Hexagon.

4401.0 *** USER FATAL MESSAGE 4401 (PRTPRN)

A Q-SET EXISTS, BUT AN O-SET DOES NOT EXIST.

User information: This error is detected by the GPSP module and issued by the PRTPARM DMAP state-
ment. The q-set is used for Generalized Dynamic Reduction and Component Mode Synthesis. It requires
the presence of an o-set. An o-set is formed only if ASETi or OMITi entries are present. Put degrees of free-
dom listed on QSETi entries on ASETi entries.

4402.0 *** USER FATAL MESSAGE 4402 (PRTPRN)

NO L-SET REMAINS AFTER CONSTRAINTS AND O-SET REMOVED.

User information: No degrees of freedom remain in the L-set after multipoint and single point constraints
and omitted coordinates are removed. Although this may be a well-defined engineering problem, all solu-
tion sequences require at least one L-set degree of freedom. Either remove some constraints or omitted
coordinates or add unconstrained degrees of freedom.

Main Index
 MSC Nastran Error Messages 407
Errors 4000 - 4999

4402.1 *** USER FATAL MESSAGE 4402 (NLITER)

NO L-SET IS PRESENT.

4403.0 *** USER FATAL MESSAGE 4403 (PRTPRN)

STIFFNESS MATRIX FOR Q-SET NOT NULL.

User information: The q-set is reserved for generalized coordinates. In superelement analysis, each
superelement must have a unique set of variables specified for its q-set. Remove any elements connected to
q-set points and provide a unique set of degrees of freedom for each superelement that has generalized coor-
dinates.

4404.0 *** USER FATAL MESSAGE 4404 (PRTPRN)

MASS MATRIX FOR Q-SET NOT NULL.

User information: The q-set is reserved for generalized coordinates. In superelement analysis, each
superelement must have a unique set of variables specified for its q-set. Remove any elements connected to
q-set points and provide a unique set of degrees of freedom for each superelement that has generalized coor-
dinates.

4405.0 *** USER FATAL MESSAGE 4405 (PRTPRN)

NO EIGENVECTORS COMPUTED FOR COMPONENT MODE SYNTHESIS OR SYSTEM
SOLUTION.

User information: The eigenvectors computed in component mode synthesis (CMS) are used to approxi-
mate the motion of the component. Some vectors must be present to perform this reduction. For the sys-
tem solution, an exit is taken if eigenvalues are requested but not eigenvectors. Reset the "range of
frequency" and/or the "number desired" on the EIGR EIGR or EIGRL entry. If the superelement does not
have any eigenvalues in the range of interest, remove the CMS request for that particular
superelement. This message is also issued when the eigenvectors calculated with a transformation method
such as GIV do not pass internal orthogonality checks. This is indicative of a modeling error.
This message can also be issued if insufficient memory is available for the Lanczos method with sparse
decomposition. This could occur with UFM 5401 and be related to UWM 5411.

4406.0 *** USER FATAL MESSAGE 4406 (PRTPRN)

Main Index
 408 MSC Nastran Error Messages
Errors 4000 - 4999

THE SEMG OPERATION HAS NOT BEEN COMPLETED FOR THIS SUPERELEMENT.

User information: The SEMG operation must be completed before the SEKR, SEMR, SELR, and SELG
operation is requested. If these other operations are requested and the SEMG operation was not completed
on a prior run, certain data blocks such as the SIL will not be in the Database. Request the SEMG opera-
tion for the superelement that fails.

4407.0 *** USER FATAL MESSAGE 4407 (PRTPRN)

MR MATRIX HAS NULL DIAGONAL TERM.

User information: The MR matrix contains the rigid-body mass matrix of the structure as measured at the
degrees of freedom listed on the SUPORT entry. If any of these degrees of freedom have null mass, they
result in invalid eigenvectors. Put in enough masses to define all rigid-body modes.

4408.0 *** USER FATAL MESSAGE 4408 (PRTPRN)

Q-SET NOT IMPLEMENTED FOR SOL 62.

User information: The q-set is used for generalized coordinates and has no function in this solution
sequence. Load reduction errors will occur if it is present. Remove QSETi entries.

4409.0 *** USER WARNING MESSAGE 4409 (PRTPRN)

PARAM, FIXEDB USED IN SOLUTION SEQUENCE WHERE NOT SUPPORTED.

User information: This capability is intended for the data recovery in the statics and normal modes solu-
tion sequences only. If requested in other solution sequences it will cause an exit from the data recovery
loop for
the present superelement and continuation to the next superelement.

4410.0 *** USER WARNING MESSAGE 4410 (PRTPRN)

DATA RECOVERY REQUESTED WHEN USET TABLE NOT PRESENT.

User information: This is caused by improper restarts or improper use of the multiple file database con-
cept. The program will terminate processing the superelement listed at the top of the page, and attempt
data recovery on the next superelement. Attach the database that has the superelement data on it or rerun
the superelement and all downstream superelements through the SEALL process.

4411.0 *** USER FATAL MESSAGE 4411 (PRTPRN)

Main Index
 MSC Nastran Error Messages 409
Errors 4000 - 4999

GEOMETRIC NONLINEAR MODEL WITH NO STRUCTURAL ELEMENTS AND/OR GENELS.

User information: Solution 64 requires "simple" (conventional) elements and does not process GENEL
entries.

4412.0 *** USER FATAL MESSAGE 4412 (PRTPRN)

GEOMETRIC NONLINEARITY DOES NOT SUPPORT O-SET OR R-SETS.

User information: SOL 64 does not process any sets that are subsets of the f-set. Remove OMITi,
SUPORT, ASETi, BSETi, CSETi entries from the Bulk Data Section.

4413.0 *** USER FATAL MESSAGE 4413 (PRTPRN)

Negative terms are encountered on the factor diagonal of the combined stiffness matrix. Negative terms
indicate that the differential stiffness has introduced a structural instability or post-buckled state.

User action: PARAM,TESTNEG may be used to override this fatal termination. Check the boundary con-
ditions in the dynamic or buckling subcase.

User information: Negative terms on the diagonal terms of the factor of the decomposed stiffness matrix
indicates that portions of the structure are in a post-buckled state. If allowed to iterate, the solution may not
converge. PARAM, TESTNEG may be used to force iteration to continue.

4413.1 *** USER INFORMATION MESSAGE 4413 (subDMAP SEKDR)

Negative terms are encountered on the factor diagonal of the combined stiffness matrix. Negative terms
indicate that the differential stiffness has introduced a structural instability or post-buckled state. Since
PARAM,TESTNEG,-2 is specified the analysis will proceed without the differential stiffness.

4413.2 *** USER INFORMATION MESSAGE 4413 (subDMAP SEKDR)

Negative terms are encountered on the factor diagonal of the combined stiffness matrix. Negative terms
indicate that the differential stiffness has introduced a structural instability or post-buckled state. Since
PARAM,TESTNEG,0 or 1 is specified the analysis will proceed with the differential stiffness but the run
may terminate during dynamic analysis.

4413.3 *** USER FATAL MESSAGE 4413 (PRTPRN)

Main Index
 410 MSC Nastran Error Messages
Errors 4000 - 4999

If fatal or warning messages 7340, 3034, and 5411 were issued above then this may indicate modeling
errors or the differential stiffness has introduced a structural instability or post-buckled state.

User action: Check constraint conditions, reduce static loading and/or adjust the eigenvalue range of inter-
est. If the preload subcase contains ANALYSIS=STATIC then change it to ANALYSIS=NLSTATIC.

4414.0 *** USER FATAL MESSAGE 4414 (PRTPRN)

SIL TABLE NOT AVAILABLE FOR COMPRESSIBLE VIRTUAL FLUID MASS.

User information: The SEALL operation must be completed on the residual structure before this capability
may be used.

4415.0 *** USER INFORMATION MESSAGE 4415 (PRTPRN)

THE FOLLOWING A-SET DEGREES OF FREEDOM HAVE EITHER NULL MASSES OR NULL
MASSES AND STIFFNESS.

User information: If the listed degrees of freedom have null mass for the GIV, HOU, MHOU, or MGIV
methods, they are automatically omitted. For the INV method, or for direct frequency or direct transient
response, they are given the auto-elimination operation. Inspect the listed degrees of freedom to ensure that
masses or stiffnesses are not left out inadvertently.

4415.1 *** USER WARNING MESSAGE 4415 (FRRD1F)

ONE OR MORE OF THE FORCING FREQUENCIES FOR THIS UNDAMPED STRUCTURE
(USING THE UNCOUPLED SOLUTION ALGORITHM) ARE EXACT MATCHES OF THE NAT-
URAL FREQUENCIES. THE THEORETICAL RESPONSE FOR THESE CASES IS INFINITE. THE
PROGRAM HAS SET THE RESPONSE TO 1.0+36.

User information:
The user can change the above behavior by making any one of the following modifications to the data:
1. Add some damping to the model.
2. Specify PARAM,NONCUP,1 to force the program to employ the coupled solution algorithm.
3. Replace the FREQ3/FREQ4/FREQ5/entries by equivalent FREQ1/FREQ2 entries.

4415.2 *** USER WARNING MESSAGE 4415 (RAND8)

Main Index
 MSC Nastran Error Messages 411
Errors 4000 - 4999

FLOATING POINT OVERFLOW IN RANDOM ANALYSIS. CALCULATED PSDF ELEMENT

(COMPUTE SJ-S) WOULD EXCEED MACHINE INFINITY. IN CORE ELEMENT: FREQ = %1,
PSD Factor = %2, PSD Value = %3. THE PROGRAM HAS SET THE RESPONSE TO TWO
ORDERS LESS THAN MACHINE INFINITY: %4

User information: Check for previous warning messages. Check for large response from frequency response
analysis.

4416.0 *** USER FATAL MESSAGE 4416 (PRTPRN)

NO DYNAMIC LOAD TABLE AVAILABLE.

User information: A frequency response or transient response analysis was requested, but no dynamic load
data is available. Include dynamic load data in model.

4417.0 *** USER FATAL MESSAGE 4417 (PRTPRN)

NO TRANSIENT RESPONSE LIST AVAILABLE.

User information: A transient response dynamic analysis was requested, but no transient response list is
available. Include TSTEP entry in Bulk Data.

4418.0 *** USER FATAL MESSAGE 4418 (PRTPRN)

NO EIGENVALUE EXTRACTION DATA IS AVAILABLE.

User information: A dynamic analysis was requested, but no eigenvalue extraction data was available.
Include eigenvalue extraction data EIGR or EIGRL in the Bulk Data. Possible causes are METHOD com-
mand in Case Control, no EIGR or EIGRL in Bulk Data. METHOD command in Case Control, EIGRL
entry in Bulk Data, or no RF3D83 (SOL 3 only). No correspondence between set IDs on METHOD and
EIGR/EIGRL entries.

4419.0 *** USER FATAL MESSAGE 4419 (PRTPRN)

NO QSET, THOUGH REQUIRED FOR DYNAMIC REDUCTION.

User information: Dynamic reduction was requested for dynamic analysis but no QSET was specified.
Define QSET in bulk data.

4420.0 *** USER WARNING MESSAGE 4420 (PRTPRN)

Main Index
 412 MSC Nastran Error Messages
Errors 4000 - 4999

THE FOLLOWING DEGREES OF FREEDOM ARE POTENTIALLY SINGULAR.

User information: During decomposition, the degrees of freedom listed had pivot ratios greater than MAX-
RATIO. Verify that the degrees of freedom are not part of a mechanism and that elements do not have
excessive stiffness. In superelement analysis, this condition causes run termination. PARAM,BAILOUT
may be used to continue the run. See the MSC NASTRAN Numerical MethodsUser's Guide.

4421.0 *** USER FATAL MESSAGE 4421 (PRTPRN)

NO FREQUENCY RESPONSE LIST AVAILABLE.

User information: A frequency response dynamic analysis was requested, but no frequencydata is available.
Include frequency data (FREQ, FREQ1, FREQ2) in the Bulk Data.

4422.0 *** USER FATAL MESSAGE 4422 (PRTPRN)

NUMBER OF NULL ROWS IN THE DYNAMIC MATRICES IS NOT EQUAL TO THE NUMBER
OF NULL COLUMNS. AUTOMATIC CONSTRAINTS CANNOT BE PERFORMED.

User information: This problem may be caused by improper direct inputs for K2PP, M2PP and B2PP.
Check all DMIGs and TFs defining K2PP, M2PP and B2PP It can also occur when all input matrices are
null. This problem may also be caused by singularities in the model. Check the constraints in the model.

4423.0 *** USER FATAL MESSAGE 4423 (PRTPRN)

A NONLINEAR ELEMENT IS ATTACHED TO AN OMITTED DEGREE OF FREEDOM.

User information: In material and geometric nonlinear analysis all nonlinear elements must not be attached
to o-set degrees of freedom. Move the degree of freedom to the a-set. This error will occur if there are
QSETi entries present but no ASETi or OMITi entries.

4424.0 *** USER WARNING MESSAGE 4424 (PRTPRN)

ESTNL IS PURGED. CHECK YOUR DATABASE OR PARAM, LOOPID.

4425.0 *** USER INFORMATION MESSAGE 4425 (PRTPRN)

Main Index
 MSC Nastran Error Messages 413
Errors 4000 - 4999

ONE OR MORE FATAL ERRORS HAVE OCCURRED. THERE MAY BE MORE ERROR MES-
SAGES IN THE PRECEDING OUTPUT

User information: One or more modules has found a fatal error condition. A message is printed for each
fatal error condition. They have set a flag, which causes this message to be printed at the end of the run.
Error messages may occur anywhere in the output, so you should search your output for these errors (search
for FATAL). This message is most likely when PARAM,ERROR,0 is used. However, this error will be
issued in superelement analysis if User Warning Message 4698 is also issued. In cyclic symmetry analysis, if
no eigenvalues are found in the prescribed frequency range on the EIGR or EIGRL entry for the current
harmonic, the run will not continue to the next harmonic and the message will result. Instead of selecting a
frequency range, input the desired number of modes.

4427.0 *** USER FATAL MESSAGE 4427 (PRTPRN)

ONE OR MORE FREQUENCY-DEPENDENT ELEMENTS ARE ATTACHED TO OMITTED
DEGREES OF FREEDOM (O-SET).

User information: FREQUENCY-DEPENDENT ELEMENTS MUST BE ATTACHED TO ANALY-

SIS DEGREES OF FREEDOM (A-SET).

User action: REASSIGN THE DEGREE OF FREEDOM TO THE A-SET.

4427.1 *** USER FATAL MESSAGE 4427 (GENGYRO)

ONE OR MORE FREQUENCY-DEPENDENT ELEMENTS ARE ATTACHED TO OMITTED
DEGREES OF FREEDOM (O-SET).

User information: THIS IS CAUSED BY THE FACT THAT THE GYROSCOPIC MATRIX AND/OR
THE CIRCULATION MATRICES, WHICH ARE FREQUENCY DEPENDENT, HAVE ONE OR
MORE TERMS ASSOCIATED WITH OMITTED DEGREES OF FREEDOM (O-SET)

User action: DO EITHER ONE OF THE FOLLOWING TO GET AROUND THE PROBLEM:
1. DO NOT PERFORM ANY STATIC CONDENSATION (GUYAN REDUCTION) OR
MODAL REDUCTION
2. EMPLOY PARAM,GYROAVG,-1 IN THE DATA (SEE QRG FOR FURTHER DETAILS)

4500.0 *** USER WARNING MESSAGE 4500 (GPSP)

Main Index
 414 MSC Nastran Error Messages
Errors 4000 - 4999

STIFFNESS MATRIX PURGED, GRID POINT SINGULARITY NOT TESTED.

User information: The stiffness matrix (KGG) input to module GPSP was purged. No singularity testing
was possible. This can occur normally during checkout of downstream superelements before their upstream
components are reduced. Assemble and reduce the upstream superelements.

4500.1 *** USER WARNING MESSAGE 4500 (subDMAP SEKRRS)

The stiffness matrix was not generated.
User action: Check earlier diagnostic messages and model completeness.

4501.0 *** USER FATAL MESSAGE 4501 (TRLGA)

RLOADI CARD SELECTED IN TRANSIENT ANALYSIS. USE TLOADI .

User information: RLOADi entries are used in frequency response analysis. These entries have no meaning
in transient analysis. Replace RLOADi with TLOADi entries.

4502.0 *** USER WARNING MESSAGE 4502.

ALL PLOT VECTORS FOR SEUPPLOT%1 DO NOT HAVE THE SAME NUMBER OF COL-
UMNS.

User information: The SEUPPLOT command causes plot vectors that were generated for each superele-
ment to be combined. There must be an equal number of vectors for all superelements. Common causes of
this error include not using the same SUBCASE - SUBCOM - REPCASE structure for all superelements
and restart errors. Print the database dictionary, and inspect the number of columns in all PUGV matrices.
Rerun any superelement with an incorrect number through data recovery.

4503.0 *** USER FATAL MESSAGE 4503. (FMPH1D)

SELECTED ELIST BULK DATA CARD WITH ID %1 CANNOT BE FOUND.

User information: An ELIST entry selected on an MFLUID Bulk Data entry could not be found in the
MATPOOL.

4504.0 *** USER FATAL MESSAGE 4504. (FMPH1D)

Main Index
 MSC Nastran Error Messages 415
Errors 4000 - 4999

COMPRESSIBLE FLUID (MFLUID SET = %1) NOT ALLOWED FOR SUPERELEMENT OR

MODULE ID = %2 ONLY ALLOWED ON THE RESIDUAL STRUCTURE.

User information: Compressible fluid may only be placed on the elements of the residual structure--not on
upstream superelements.

4505.0 *** USER INFORMATION MESSAGE 4505

AUXILIARY ANGLE CONCEPT IS BEING USED FOR INTERNAL GRID NO. =%1 AT DOF = %2
AND = %3 IN RADIANS

4506.0 *** USER WARNING MESSAGE 4506. (GPFDR)

TOTAL STRAIN ENERGY IS ZERO. THE PERCENT OF TOTAL STRAIN ENERGY IS ALSO SET
TO ZERO.

4507.0 *** USER INFORMATION MESSAGE 4507. (GPFDEV)

IN SUBCASE %1 %2 %3 THERE ARE %4 %5 ELEMENTS HAVING STRAIN ENERGY WHICH
IS LESS THAN %6 PERCENT OF THE TOTAL STRAIN ENERGY OF ALL ELEMENTS.

4507.1 *** USER INFORMATION MESSAGE 4507. (GPFDEV)

IN SUBCASE %1 %2 %3 THERE ARE %4 %5 ELEMENTS HAVING KINETIC ENERGY WHICH
IS LESS THAN %6 PERCENT OF THE TOTAL STRAIN ENERGY OF ALL ELEMENTS.

4507.2 *** USER INFORMATION MESSAGE 4507. (GPFDEV)

IN SUBCASE %1 %2 %3 THERE ARE %4 %5 ELEMENTS HAVING ENERGY LOSS WHICH IS
LESS THAN %6 PERCENT OF THE TOTAL STRAIN ENERGY OF ALL ELEMENTS.

4507.3 *** USER INFORMATION MESSAGE 4507. (GPFDEV)

IN SUBCASE %1 %2 %3 THERE ARE %4 %5 ELEMENTS HAVING STRAIN ENERGY THAT
WERE NUMERICALLY ZERO.

4508.0 *** USER FATAL MESSAGE 4508

A GRID %1 AND COMPONENT %3 HAS BEEN SPECIFIED TWICE ON DMIG %2

User information: The referenced DMIG matrix has an element input more than once. This is not
allowed, even if both entries are of the same value. Delete all multiple entries.

Main Index
 416 MSC Nastran Error Messages
Errors 4000 - 4999

4508.1 *** USER FATAL MESSAGE 4508

A GRID %1 AND COMPONENT %3 HAS BEEN SPECIFIED TWICE ON DMIK %2

4508.2 *** USER FATAL MESSAGE 4508

A GRID %1 AND COMPONENT %3 HAS BEEN SPECIFIED TWICE ON DMIJ %2

4508.3 *** USER FATAL MESSAGE 4508

A GRID %1 AND COMPONENT %3 HAS BEEN SPECIFIED TWICE ON DMIJI %2

4509.0 *** USER FATAL MESSAGE 4509

A GRID AND COMPONENT HAS BEEN SPECIFIED TWICE ON TF FUNCTION %1

User information: The referenced TF entry has an element input more than once. Delete all multiple
entries.

4510.0 *** USER FATAL MESSAGE 4510.

NLSTAT SUBCASE %1 HAS NLTRAN CASE BETWEEN ITS STEPS.

User information: In SOL400, NLSTAT case can have several TSTEPs, but they can not be interrupted by
any NLTRAN case.

4510.1 *** USER FATAL MESSAGE 4510.

SUBCASE %1 REFERENCES UNSUPPORTED %2 CARD WITH ID =%3 IN NONLINEAR ANAL-
YSIS.

User information: In SOL400, DEFORM CASE CONTROL COMMAND IS NOT SUPPORTED.

4511.0 *** USER FATAL MESSAGE 4511.

SUBCASE %1 DOES NOT REFERENCE ANY %2 BULK DATA CARD. (REQUIRED BY NON-
LINEAR ANALYSIS.)

User information: Each subcase in a nonlinear analysis must contain an NLPARM Bulk Data entry selec-
tion. The subcase indicated does not contain this selection.

4511.1 *** USER FATAL MESSAGE 4511.

Main Index
 MSC Nastran Error Messages 417
Errors 4000 - 4999

%1 %2 does not reference any %3 Bulk Data entry.

User information: This is required for nonlinear analysis.

4511.2 *** USER FATAL MESSAGE 4511 (RCNcPCV1)

%1 references %2 Bulk Data entry.

User information: This is %3 supported for %4.

4512.0 *** USER FATAL MESSAGE 4512.

SUBCASE %1 REFERENCES UNDEFINED %2 CARD WITH ID =%3.

User information: The %2 Bulk Data entry referenced in the subcase indicated does not exist in the MPT.

4512.1 *** USER FATAL MESSAGE 4512.

%1 %2 references undefined %3 Bulk Data entry with ID = %4.

4513.0 *** USER FATAL MESSAGE 4513.

A IC AND NLIC CASE CONTROL COMMAND ARE BOTH SPECIFIED IN THE FIRST STEP
(STEP %2) OF SUBCASE %1.

User information: For nonlinear analysis, either IC or NLIC, but not both, can be specified in the first
STEP of each SUBCASE when ANALYSIS=NLTRAN.

4514.0 *** USER WARNING MESSAGE 4514.

A IC CASE CONTROL COMMAND IS SPECIFIED IN SUBCASE %1 STEP %2 WHICH IS NOT
THE FIRST STEP.

User information: For nonlinear analysis, the IC command can only be specified in the first STEP of each
SUBCASE when ANALYSIS=NLTRAN. The command will be ignored.

4515.0 *** USER WARNING MESSAGE 4515.

Main Index
 418 MSC Nastran Error Messages
Errors 4000 - 4999

A IC CASE CONTROL COMMAND IS SPECIFIED IN SUBCASE %1 STEP %2 WHICH IS

STATIC, NORMAL MODES OR BUCKLING ANALYSIS.

User information: The IC command can only be specified in transient analysis. The command will be
ignored.

4515.1 *** USER WARNING MESSAGE 4515.

A IC case control command is specified in SUBCASE %1 STEP %2 SUBSTEP %3 with ANALYSIS =
%4.

User information: The IC command can only be specified in transient analysis. The command will be
ignored.

4515.2 *** USER FATAL MESSAGE 4515.

In the multi-step subcase %1, FLUTTER analysis can't be implemented with NLSTATIC or NLTRAN
analysis

4516.0 *** USER WARNING MESSAGE 4516.

A NLIC case control command is specified in SUBCASE %1 STEP %2 which is STATIC analysis.

User information: The NLIC command can only be specified in transient, normal modes or buckling anal-
ysis. The command will be ignored.

4516.1 *** USER WARNING MESSAGE 4516.

A NLIC case control command is specified in SUBCASE %1 STEP %2 SUBSTEP %3 which is STATIC
analysis.

User information: The NLIC command can only be specified in transient, normal modes or buckling anal-
ysis. The command will be ignored.

4517.0 *** USER WARNING MESSAGE 4517.

A NLIC CASE CONTROL COMMAND IS SPECIFIED IN SUBCASE %1 STEP %2 WHICH IS
NOT THE FIRST TRANSIENT STEP.

User information: The NLIC command can only be specified in the first transient STEP of each SUB-
CASE. The command will be ignored.

Main Index
 MSC Nastran Error Messages 419
Errors 4000 - 4999

4518.0 *** USER WARNING MESSAGE 4518.

A NLIC AND STATSUB CASE CONTROL COMMAND ARE BOTH SPECIFIED IN SUBCASE
%1 STEP %2.

User information: The NLIC command takes precedence over the STATSUB command.

4519.0 *** USER FATAL MESSAGE 4519.

A STATSUB CASE CONTROL COMMAND IS SPECIFIED IN THE FIRST STEP OF SUBCASE
%1.

User information: The STATSUB command cannot be specified in the first STEP of a SUBCASE.

4519.1 *** USER FATAL MESSAGE 4519.

User information: MODEL PARAMETER(MDLPRM) RDBOTH = %1
RDBOTH=4(BIT3=1) OR RDBOTH=8(BIT4=1) CAN NOT BE SPECIFIED IN SOL 400.

User action: TO INCLUDE EFFECT OF STRESS STIFFENING, ADD A LINEAR/NONLINEAR

STATIC STEP VIA RFORCE.

4520.0 *** USER INFORMATION MESSAGE 4520 (MC2THETA)

THE USER SUPPLIED COORDINATE SYSTEM ID %1 IS ORIENTED AT AN ANGLE OF %2 TO
SIDE 1-2 OF THE ELEMENT ID %3

4521.0 *** USER FATAL MESSAGE 4521 (MC2THETA)

THE X-AXIS OF COORDINATE SYSTEM %1 IS PERPENDICULAR TO ELEMENT %2

User action: WHEN USING THE MCID OPTION TO DEFINE A SHELL ELEMENT MATERIAL
COORDINATE SYSTEM, THE MCID T1 AXIS IS PROJECTED ONTO THE SHELL SURFACE
AND THEREFORE CANNOT BE PERPENDICULAR TO THE SURFACE.

User information: The user supplied material orientation coordinate system x-axis is normal to the plane of
the element and, hence, the material orientation angle with lines = constant of the element is indeterminate.
Choose a new coordinate system ID whose x-axis is not normal to the plane of the element.

4522.0 *** USER FATAL MESSAGE 4522

Main Index
 420 MSC Nastran Error Messages
Errors 4000 - 4999

THE NON-RECTANGULAR AREA4 ELEMENTS ARE DIVIDED INTO TWO AREA3 ELE-
MENTS BY THE PROGRAM. THIS HAS CREATED TOO MANY ELEMENTS FOR THE PRO-
GRAM TO HANDLE. INCREASE YOUR MEMORY REQUEST OR DECREASE THE NUMBER
OF ELEMENTS.

User information: Increase memory.

4523.0 *** USER FATAL MESSAGE 4523

ERROR IN CHBDY CARD%1 THE GRID POINTS OF A LINE ELEMENT MUST BE DISTINCT.
VECTOR (V1,V2,V3) MUST NOT BE THE ZERO VECTOR NOR MAY IT COINCIDE WITH
THE LINE CONNECTING THE TWO GRID POINTS.

User information: CHBDY entry defines an illegal line element.

4524.0 *** USER FATAL MESSAGE 4524

ERROR IN CHBDY CARD%1 THIS CARD REFERENCES AN UNDEFINED VIEW CARD.

User information: Either the VIEW entry number in field 9 of the CHBDY entry is incorrect, or the
VIEW entry is incorrect (field 1 or 2).

4525.0 *** USER WARNING MESSAGE 4525

THE USER HAS SPECIFIED A ZERO SUB-ELEMENT MESH SIZE FOR CHBDY CARD%1
THE PROGRAM DEFAULTS TO A 1 X 1 MESH SIZE AND CONTINUES PROCESSING.

User information: The results are quite sensitive to subelement mesh size.

4526.0 *** USER FATAL MESSAGE 4526

ERROR IN PHBDY CARD%1 THE AREA SPECIFIED MUST BE POSITIVE.

User information: Element must be given positive areas.

4527.0 *** USER FATAL MESSAGE 4527

ERROR IN CHBDY CARD %1 GRID POINTS %2 AND %3 ARE COINCIDENT.

User information: Coincident grid points will not properly define the element shape specified in field 4 of
the CHBDY entry.

Main Index
 MSC Nastran Error Messages 421
Errors 4000 - 4999

4528.0 *** USER FATAL MESSAGE 4528

ERROR IN CHBDY CARD%1 AN AREA4 ELEMENT MUST BE A QUADRILATERAL CON-
TAINING NO ANGLE GREATER THAN OR EQUAL TO 180 DEGREES. THE GRID POINTS
MUST BE SPECIFIED SEQUENTIALLY AROUND THE QUADRILATERAL.

4529.0 *** USER FATAL MESSAGE 4529

ERROR IN CHBDY CARD%1 VECTOR (V1,V2,V3) MUST NOT BE THE ZERO VECTOR.
FIELDS 6,7, AND 8 OF THE CONTINUATION CARD OF THE CHBDY CARD WERE ALL
FOUND TO BE ZERO.

User information: Thus, a vector V = (0, 0, 0) was defined. The element type (either POINT or LINE)
defined in field 4 of the CHBDY entry requires V to be nonzero.

4530.0 *** USER FATAL MESSAGE 4530

ERROR IN CHBDY CARD%1 THE FOUR GRID POINTS MUST ALL BE IN ONE PLANE

User information: All four grid points of AREA4 element must be coplanar.

4531.0 *** USER WARNING MESSAGE 4531

EITHER NB OR NG HAS BEEN CALCULATED AS ZERO FOR THE SECOND TRIANGLE
COMPOSING CHBDY CARD%1 . REPLACE THE ZERO WITH A ONE.

User information: The AREA4 element was split into two triangles as it is non-rectangular. The MESH
distribution for NB and NG yielded a zero MESH. It was changed to one. The user should consider replac-
ing AREA4 with two AREA3 elements to assume control of the MESH.

4532.0 *** USER FATAL MESSAGE 4532.

FOR LOAD SET =%1, A %2 CARD REFERENCES UNDEFINED GRID ID =%3.

User information: The referenced entry refers to a grid point ID that is not in the Bulk Data deck.

4533.0 *** USER FATAL MESSAGE 4533.

THE SPECIFIED INITIAL CONDITION CANNOT BE FOUND IN SUBCASE %1 STEP %2.

User information: PLEASE CHECK THE FORMAT OF NLIC OR STATSUB in nonlinear transient
analysis.

Main Index
 422 MSC Nastran Error Messages
Errors 4000 - 4999

4534.0 *** USER INFORMATION MESSAGE 4534,

%1 ELEMENTS HAVE A TOTAL VIEW FACTOR (FA/A) LESS THAN 0.99, ENERGY MAY BE
LOST TO SPACE.

User information: Some radiation HBDY elements have a column sum in the RADMTX matrix which is
less than the element area. If you intended to allow energy loss, no action is required. If you do not want the
loss, adjust the values on the RADMTX input data entries.

4535.0 *** USER WARNING MESSAGE 4535 (PTHBDY)

CHBDY ELEMENT %1 HAS NO NORMAL OR BAD GEOMETRY WHICH MAKES IT UNPLOT-
TABLE.

User information: CHBDY types "POINT" and "LINE" must have an orientation vector. For type LINE
the two grid points must be specially distinct and not define a line collinear with the orientation vector (V1,
V2, V3 on CHBDY entry). Check V1, V2 and V3 on CHBDY entry.

4536.0 *** USER WARNING MESSAGE 4536,

COL %1, ROW %2 OF RADMTX IS NEGATIVE (%3).

User information: A negative RADMTX value is not valid for a real structure, since it corresponds to a neg-
ative view factor. Correct RADMTX entries.

4536.1 *** USER FATAL MESSAGE 4536.

FREE FIELD BULK DATA CARD HAS GENERATED AN INTEGER THAT OVERFLOWS THE
ALLOWED 8 COLUMNS.

User information: The free field Bulk Data entry generator only works with 8 column fields, but input to it
generated an integer less than -9999999 or greater than 99999999. Redesignate the numbering scheme or
switch to double field entries. NOTE: Double field entries CANNOT be generated using free field entries.

4537.0 *** USER INFORMATION MESSAGE 4537,

TOTAL VIEW FACTOR (FA/A), FOR ELEMENT %1 IS %2, ELEMENT AREA IS %3.

User information: This information is requested by SYSTEM(88) = 1. Correct RADMTX data, unless it is
intended to radiate to space (lost to zero absolute temperature surroundings).

Main Index
 MSC Nastran Error Messages 423
Errors 4000 - 4999

4538.0 *** USER FATAL MESSAGE 4538 (NL2INT)

UNABLE TO FIND SELECTED TSTEPNL SET (%1) IN %2 DATA IN SUBROUTINE %3

4538.1 *** USER FATAL MESSAGE 4538 (NLCINT)

UNABLE TO FIND SELECTED %1 SET (%2) IN %3 DATA IN SUBROUTINE %4

User information: The set identification was either not selected within case control or the Bulk Data entry
for the set was not supplied. Check both the case control and bulk data for the requested NLPARM set.

4539.0 *** USER FATAL MESSAGE 4539 (NL2INT)

THE TSTEPNL DATA CARDS HAVE NOT BEEN ENTERED.

4539.1 *** USER FATAL MESSAGE 4539 (NLCINT)

THE %1 DATA CARDS HAVE NOT BEEN ENTERED.

User information: The user requested nonlinear analysis and supplied the correct Case Control commands
but did not supply the corresponding NLPARM OR TSTEPNL Bulk Data entries. Enter the correspond-
ing NLPARM or TSTEPNL Bulk Data entries.

4540.0 *** SYSTEM FATAL MESSAGE 4540 (NL2INT)

INPUT ESTNL DATA BLOCK IS NOT IN NON-LINEAR FORMAT.

System information: The EST data block which was submitted to the nonlinear iteration module was not
in the correct format. This implies that the nonlinear appendages were nonexistent and no computations
can be performed. (This is detected by the fact that the second trailer word for linear EST data blocks is a
zero, and it is non-zero for nonlinear appendage format.) Make sure that the DMAP has the correct EST
data block as the input to the NLITER module.

4541.0 *** USER FATAL MESSAGE 4541

IC=%1 and TEMP(INIT)=%2 do not have same ID in SUBSTEP %3 where ANALYSIS = HTRAN.

4542.0 *** USER FATAL MESSAGE 4542 (NLINIT)

Main Index
 424 MSC Nastran Error Messages
Errors 4000 - 4999

NO LOAD INCREMENT EXISTS FOR NONLINEAR SUBCASE.

User information: The DELPLV data block, which is the incremental load vector for the subcase, was null.
This implies that no change in the nonlinear occurred. Review the LOAD requests and make sure a valid
SUBCASE was selected.

4543.0 *** USER WARNING MESSAGE 4543 (NL2IML)

NO RESTART DISPLACEMENTS EXIST FOR NON-LINEAR SUBCASE.

User information: On a NLITER restart condition the nonlinear incremental displacement vector was
zero. Review the SUBCASE and LOAD options for correctness.

4544.0 *** USER FATAL MESSAGE 4544

The IC commands are identical for SUBSTEP %1 (where ANALYSIS = %2) and SUBSTEP %3 (where
ANALYSIS = %4).

4545.0 *** USER INFORMATION MESSAGE 4545 (NLICLP)

THE initial condition OR PRELOAD will START from the PREVIOUS STEP

4545.1 *** USER INFORMATION MESSAGE 4545 (NLICLP)

THE Initial condition OR PRELOAD will START FROM SUBCASE=%1 STEP=%2 TIME(LOAD
FACTOR)=%3

4546.0 *** SYSTEM FATAL MESSAGE 4546 (NLEMG)

ESTNL AND FILE (%1) ARE NOT PROPERLY ALIGNED

System information: The nonlinear EST file has become misaligned with the associated file number.
Check that no elements have been inadvertently eliminated. Review element and set definitions.

4547.0 *** SYSTEM FATAL MESSAGE 4547 (RMG2)

THE TEMPERATURE VECTOR DOES NOT EXIST.

User information: This error may be caused by missing initial temperatures. The initial temperatures are
specified by the TEMPERATURE(INIT) Case Control command and TEMP/TEMPD Bulk Data entries.

4548.0 *** SYSTEM FATAL MESSAGE 4548 (NBEM1D)

Main Index
 MSC Nastran Error Messages 425
Errors 4000 - 4999

SINGULAR (C-KRR) MATRIX ENCOUNTERED FOR BEAM ELEMENT %1

System information: A singular CBEAM plastic hinge matrix was detected. Review definition of CBEAM
element.

4549.0 *** SYSTEM FATAL MESSAGE 4549 (NBEM2D)

SINGULAR (C+KBRR) MATRIX ENCOUNTERED FOR BEAM ELEMENT %1

System information: A singular CBEAM plastic hinge update matrix was encountered. Review definition
for CBEAM element.

4550.0 *** USER INFORMATION MESSAGE 4550

*** NEW STIFFNESS MATRIX IS REQUIRED ***
User information: This is issued based on the stiffness matrix update strategy specified on the NLPARM or
TSTEPNL entry, or when the adaptive gap element stiffens or its penalty value is adjusted after conver-
gence.

4550.1 *** USER INFORMATION MESSAGE 4550 (NL2CON)

*** %1 IS ACTIVATED BY %2.

4550.2 *** USER INFORMATION MESSAGE 4550 (NCONVG)

*** NEW STIFFNESS MATRIX IS REQUIRED BY GAP ***

4550.3 *** USER INFORMATION MESSAGE 4550 (NCONVG)

*** NEW STIFFNESS MATRIX IS REQUIRED BY LINE CONTACT.

4550.4 *** USER INFORMATION MESSAGE 4550 (NLITER)

*** NEW STIFFNESS MATRIX IS REQUIRED BY GAP FOR PENALTY VALUE ADJUSTMENT ***

4550.5 *** USER INFORMATION MESSAGE 4550 (NL3ITR)

*** NEW STIFFNESS MATRIX IS REQUIRED BY 3D CONTACT ***

4550.6 *** USER INFORMATION MESSAGE 4550 (NL3CON)

*** THE STIFFNESS MATRIX IS UPDATING TO THE PREVIOUS CONVERGED SOLUTION
***

Main Index
 426 MSC Nastran Error Messages
Errors 4000 - 4999

4550.7 *** USER INFORMATION MESSAGE 4550 (NL3CON)

*** THE STIFFNESS MATRIX IS UPDATING TO THE CURRENT SOLUTION ***

4550.8 *** USER INFORMATION MESSAGE 4550 (NL3CON)

*** THE STIFFNESS MATRIX IS UPDATING TO THE PREVIOUS ITERATION ***

4550.9 *** USER INFORMATION MESSAGE 4550 (NL3CON)

*** THE STIFFNESS MATRIX IS UPDATING TO THE PREVIOUS CONVERGED SOLUTION
FOR BISECTION ***

4550.10 *** USER INFORMATION MESSAGE 4550 (NL3CON)

*** THE STIFFNESS MATRIX IS UPDATING TO THE INITIAL STATE FOR NEW LMFACT=%1,
PENFN=%2 ***

4550.11 *** USER FATAL MESSAGE 4550 (NL3CON)

*** THE ITERATION TERMINATED DUE TO A STOP SIGNAL RECEIVED FROM DIGIMAT
***
PLEASE REFER TO DIGIMAT LOG FILE FOR DETAILED ERROR MESSAGE.

4550.12 *** USER FATAL MESSAGE 4550 (NL3CON)

*** ITERATION STOPPED DUE TO PENETRATION CANNOT BE RESOLVED (N3DFF2) ***

4550.13 *** USER FATAL MESSAGE 4550 (NL3CON)

SOL 101 CAN'T UPDATE STIFFNESS MATRIX REQUESTED BY RIGID=LAGA WITH CON-
TACT, TRY RE-SUBMITTING THE JOB WITH THE FOLLOWING PARAMETER VALUES:
PARAM, LMFACT, %1
PARAM, PENFN, %2

4550.14 *** system FATAL MESSAGE 4550 (NL3CON)

SOLUTION IS DIVERGING, SEARCH PREVIOUS OUTPUT FOR ADDITIONAL MESSAGES.

4551.0 *** USER FATAL MESSAGE 4551 (NL2CON)

STOPPED PROBLEM DUE TO FIVE CONSECUTIVE DIVERGING TIME STEPS.

User information: A solution is not possible. Review NLPARM requests and modify to select a better solu-
tion approach.

Main Index
 MSC Nastran Error Messages 427
Errors 4000 - 4999

4551.1 *** USER FATAL MESSAGE 4551 (NL2CON)

STOPPED PROBLEM DUE TO TWO DIVERGENCES IN THE SAME TIME STEP.

User information: A solution is not possible. Review NLPARM requests and modify to select a better solu-
tion approach.

4551.2 *** USER FATAL MESSAGE 4551 (NL2CON)

*** PREVIOUS MESSAGE HAS OCCURRED ON FIVE CONSECUTIVE TIME STEPS.

User information: A solution is not possible. Review NLPARM requests and modify to select a better solu-
tion approach.

4551.3 *** USER FATAL MESSAGE 4551 (NCONVG)

*** STOPPED PROBLEM DUE TO FAILED CONVERGENCE.
User action:
1. MAKE APPROPRIATE CHANGES TO THE TIME-STEP AND LOADING SPECIFIED IN
THE ANALYSIS.
2. FOR SOL 400, PLEASE USE NLSTEP AND ADAPTIVE LOAD STEPPING TO ALLOW THE
SOLVER TO ADJUST LOAD INCREMENTS BASED ON PREVIOUS INCREMENT
CONVERGENCE RATE. IF THE ERROR OCCURS IN THE FIRST INCREMENT, TRY
REDUCING INITIAL LOAD STEP.

User information: A solution is not possible. Review NLPARM requests and modify to select a better solu-
tion approach.

4551.4 *** SYSTEM FATAL MESSAGE 4551 (NLTCON)

STOPPED PROBLEM DUE TO FIVE CONSECUTIVE DIVERGING TIME STEPS.

System information: A solution is not possible. Review NLPARM requests and modify to select a better
solution approach.

4551.5 *** SYSTEM FATAL MESSAGE 4551 (NLTCON)

STOPPED PROBLEM DUE TO TWO DIVERGENCES IN THE SAME TIME STEP.

System information: A solution is not possible. Review NLPARM requests and modify to select a better
solution approach.

Main Index
 428 MSC Nastran Error Messages
Errors 4000 - 4999

4551.6 *** USER INFORMATION MESSAGE 4551 (NLTRD)

*** DIVERGENCE HAS OCCURRED ON THE EXTRA TIME STEP %1 AND CONVERGENCE
HAS BEEN FORCED.

User information: A solution is not possible. Review NLPARM requests and modify to select a better solu-
tion approach.

4551.7 *** USER FATAL MESSAGE 4551 (NL3CON)

*** UNABLE TO ACHIEVE CONVERGENCE FOR %1 CONSECUTIVE INCREMENTS OR
TIME STEPS ***
User action:
1. MAKE APPROPRIATE CHANGES TO THE TIME-STEP AND LOADING SPECIFIED IN
THE ANALYSIS.
2. FOR SOL 400, PLEASE USE NLSTEP AND ADAPTIVE LOAD STEPPING TO ALLOW THE
SOLVER TO ADJUST LOAD INCREMENTS BASED ON PREVIOUS INCREMENT
CONVERGENCE RATE. IF THE ERROR OCCURS IN THE FIRST INCREMENT, TRY
REDUCING INITIAL LOAD STEP.

4551.8 *** USER FATAL MESSAGE 4551 (MDCONVD)

*** UNBOUNDED RESIDUAL FORCE. UNABLE TO ACHIEVE CONVERGENCE.

User information: Module MDCONVD, nonlinear iterations have failed to converge due to unbounded
residual force. Solution will be stopped prematurely.

User action: Adjust the parameters of NLSTEP/NLPARM/TSTEPNL to allow for the selection of a
smaller time/load increment.

4552.0 *** USER FATAL MESSAGE 4552 (NLSOLV)

THE SOLUTION SET IS EMPTY. NO FE-SET IS PRESENT.

4553.0 *** USER WARNING MESSAGE 4553 (NL3MAP)

THE CURRENT SIZE OF %1-SET DOES NOT EQUAL THE PREVIOUS ONE.
THE PREVIOUS SIZE = %2
THE CURRENT SIZE = %3

4554.0 *** USER WARNING MESSAGE 4554 (NL3INT)

The ANALYSIS command has changed in the same subcase BETWEEN DIFFERENT STEP cases.

Main Index
 MSC Nastran Error Messages 429
Errors 4000 - 4999

4554.1 *** USER FATAL MESSAGE 4554 (NL3INT)

NLSTEP ID %1 SPECIFIES BOTH FIXED AND ADAPTIVE STEPPING. ONLY ONE IS
ALLOWED.

4554.2 *** USER WARNING MESSAGE 4554 (NL3INT)

MAXIMUM NUMBER OF ITERATIONS FOR NLSTEP ID %1 RESET FROM %2 TO %3.

4554.3 *** USER WARNING MESSAGE 4554 (NL3INT)

THE SPECIFIED INITIAL TIME STEP %1 HAS BEEN REDUCED TO %2 SINCE IT IS LARGER
THAN THE SPECIFIED POST OUTPUT TIME INTERVAL

4554.4 *** USER WARNING MESSAGE 4554 (NL3INT)

THE SPECIFIED INITIAL TIME STEP %1 HAS BEEN SET TO %2 SINCE IT IS SMALLER THAN
THE MINIMUM TIME STEP

4554.5 *** USER WARNING MESSAGE 4554 (NL3INT)

THE SPECIFIED INITIAL TIME STEP %1 HAS BEEN REDUCED TO %2 SINCE IT IS GREATER
THAN THE MAXIMUM TIME STEP

4554.6 *** USER FATAL MESSAGE 4554 (NL3INT)

NLSTEP ID %1 SPECIFIES BOTH FIXED AND ARC-LENGTH STEPPING. ONLY ONE IS
ALLOWED.

4554.7 *** USER FATAL MESSAGE 4554 (NL3INT)

NLSTEP ID %1 SPECIFIES BOTH ADAPTIVE AND ARC-LENGTH STEPPING. ONLY ONE IS
ALLOWED.

4554.8 *** USER FATAL MESSAGE 4554 (NL3INT)

NLSTEP ID %1 WITH ARC LENGTH STEPPING PROCEDURE DOES NOT SUPPORT CON-
TACT

4554.9 *** USER FATAL MESSAGE 4554 (NL3INT)

FOR NLSTEP ID %1, ONLY KMETHOD=PFNT AND KMETHOD=ITER ARE CURRENTLY
SUPPORTED

Main Index
 430 MSC Nastran Error Messages
Errors 4000 - 4999

4554.10 *** USER FATAL MESSAGE 4554 (NL3INT)

FOR NLSTEP ID %1, ONLY KMETHOD=PFNT, KMETHOD=ITER AND KMETHOD=AUTO
ARE CURRENTLY SUPPORTED

4554.11 *** USER FATAL MESSAGE 4554 (NL3INT)

FOR NLSTEP ID %1, ONLY ELEMENTS WITH NON-LINEAR PROPERTY ENHANCEMENTS
AND USING MATVP MATERIAL CAN BE USED WITH THE CREEP FLAG

4554.12 *** USER WARNING MESSAGE 4554 (SPASOL)

NLSTEP with arc length stepping procedure does not support Intel MKL Pardiso sparse solver option.
Switching to MSCLDL sparse solver.

4554.13 *** USER WARNING MESSAGE 4554 (NL3INT)

FOR NLSTEP ID %1, ONLY CONV=A IS NOT ENOUGH FOR CONVERGENCE CRITERIA
SELECTION, CONV=PAV WILL BE ENFORCED.

4554.14 *** USER WARNING MESSAGE 4554 (NL3INT)

FOR NLSTEP ID %1, DTINITF has been adjusted from %2 to %3 beause INTOUT is %4, which is
greater than 1.0/DTINITF(=%5).

4555.0 *** USER WARNING MESSAGE 4555 (NLCTMA)

TTEMP Bulk Data entry ID=%1 specifies GRPID=-1.

User information: ALL THE OTHER TTEMP entries with the same SID will be IGNORED.

4557.0 *** USER WARNING MESSAGE 4557 (XSBFF)

THE BELOW FREE FIELD BULK DATA ENTRY IS INCORRECTLY FORMATTED. THIS
ENTRY WILL MOST LIKELY BE FLAGGED AS A FATAL ERROR LATER ON.
%1

User information: There was an error in the free field format. Most likely an "=(n)" was coded outside of
field 1, there was a parenthesis mismatch, or an alphabetic character incorrectly included in a numeric field
(e.g., "*(1.2F7)" instead of "*(1.2E7)." Correct the entry.

4558.0

Main Index
 MSC Nastran Error Messages 431
Errors 4000 - 4999

INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA

SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2.

User action:
1. USE THE ELEMENT ID SPECIFIED ABOVE TO IDENTIFY THE ELEMENT AND ITS
LOCATION WITHIN THE F.E. MODEL AND CHECK THE ELEMENT GEOMETRY TO
INSURE IT FORMS A REASONABLE TRIANGLE.
2. MAKE NECESSARY CORRECTIONS TO THE MATERIAL PROPERTIES DEFINED FOR
THE SPECIFIC ELEMENT(S) IN THE MATERIAL PROPERTIES SECTION.

4558.1
INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA
SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2.
INAPPROPRIATE -TRIAR- GEOMETRY.

User action:
1. USE THE ELEMENT ID SPECIFIED ABOVE TO IDENTIFY THE ELEMENT AND ITS
LOCATION WITHIN THE F.E. MODEL AND CHECK THE ELEMENT GEOMETRY TO
INSURE IT FORMS A REASONABLE TRIANGLE.
2. MAKE NECESSARY CORRECTIONS TO THE MATERIAL PROPERTIES DEFINED FOR
THE SPECIFIC ELEMENT(S) IN THE MATERIAL PROPERTIES SECTION

4558.2
INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA
SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2.
MID2 MATERIAL -G- 3X3 MATRIX INSUFFICIENT, MATERIAL ID =%3

User action:
1. USE THE ELEMENT ID SPECIFIED ABOVE TO IDENTIFY THE ELEMENT AND ITS
LOCATION WITHIN THE F.E. MODEL AND CHECK THE ELEMENT GEOMETRY TO
INSURE IT FORMS A REASONABLE TRIANGLE.
2. MAKE NECESSARY CORRECTIONS TO THE MATERIAL PROPERTIES DEFINED FOR
THE SPECIFIC ELEMENT(S) IN THE MATERIAL PROPERTIES SECTION.

4558.3

Main Index
 432 MSC Nastran Error Messages
Errors 4000 - 4999

INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA

SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2. ZERO
MOMENT OF INERTIA HAS BEEN COMPUTED.

User action:
1. USE THE ELEMENT ID SPECIFIED ABOVE TO IDENTIFY THE ELEMENT AND ITS
LOCATION WITHIN THE F.E. MODEL AND CHECK THE ELEMENT GEOMETRY TO
INSURE IT FORMS A REASONABLE TRIANGLE.
2. MAKE NECESSARY CORRECTIONS TO THE MATERIAL PROPERTIES DEFINED FOR
THE SPECIFIC ELEMENT(S) IN THE MATERIAL PROPERTIES SECTION.

4558.4
INAPPROPRIATE GEOMETRY OR INCORRECT MATERIAL DATA
SPECIFIED FOR ELEMENT WITH ID =%1. SUBROUTINE REASON IS NUMBER %2.
MID3 MATERIAL -G- 2X2 MATRIX INSUFFICIENT, MATERIAL ID =%3

User action:
1. USE THE ELEMENT ID SPECIFIED ABOVE TO IDENTIFY THE ELEMENT AND ITS
LOCATION WITHIN THE F.E. MODEL AND CHECK THE ELEMENT GEOMETRY TO
INSURE IT FORMS REASONABLE TRIANGLE.
2. MAKE NECESSARY CORRECTIONS TO THE MATERIAL PROPERTIES DEFINED FOR
THE SPECIFIC ELEMENT(S) IN THE MATERIAL PROPERTIES SECTION.

4559.0 *** USER FATAL MESSAGE 4559.

ILLEGAL GEOMETRY FOR TRIA3 ELEMENT WITH ID =%1

User information: An illegal geometry was determined while calculating the local element reference system.
Check the element grid locations and properties for acceptable values.

4561.0 *** USER WARNING MESSAGE 4561.

INSUFFICIENT MEMORY INWHICH TO PERFORM ORTHOGONALITY CHECKS. ADDI-
TIONAL MEMORY REQUIRED = %1 .

User information: The amount of memory needed for eigenvector orthogonalization is 1/2 [number of
eigenvectors * (number of eigenvectors +1)] + 2 * BUFFSIZE + number of eigenvalues. If this equation is
not met, the modes are orthogonalized, but the checking function is not performed. However, all outputs
from the module are provided. If the check is desired, you should either increase memory or decrease the
number of eigenvectors to satisfy the above equation.

Main Index
 MSC Nastran Error Messages 433
Errors 4000 - 4999

4562.0 *** USER FATAL MESSAGE 4562

TSTEP (TIME STEP) DATA IS MISSING

User information: Transient analysis requires the time step data. Add a TSTEP Bulk Data entry, and select
it with a Case Control command.

4563.0 *** USER FATAL MESSAGE 4563 (TA0SP)

GPFORCE RESULTS ARE NOT AVAILABLE WITH PARAM,BUSHNM,NO.

User information: SPECIFY PARAM,BUSHNM,YES IN THE BULK DATA IF GPFORCE RESULTS

ARE DESIRABLE.

4564.0 *** USER FATAL MESSAGE 4564 (TA0SP)

GPFORCE RESULTS ARE NOT AVAILABLE FOR FREQUENCY-DEPENDENT PROPERTIES
WITH NON-UNIQUE FREQUENCY SET ID %1.

User information: EACH SUBCASE MUST HAVE A UNIQUE FREQUENCY SET ID FOR
GPFORCE OUTPUT REQUEST WITH FREQUENCY-DEPENDENT PROPERTIES.

4565.0 *** USER FATAL MESSAGE 4565 (TA0N2M)

Element ID=%1 with %2 grids references %3 property entry ID=%4

User action: Correct the connectivity or the property entry reference. Programmer information: %5

4565.1 *** USER FATAL MESSAGE 4565 (TA0N2M)

Element ID=%1 with %2 grids references %3 property entry ID=%4

User information: The %5 (ANAL=%6) Behavior and Integration Scheme on the property entry are %7
and %8, respectively.

User action: Correct the connectivity or the property entry reference.

Programmer information: %9

4566.0 *** USER FATAL MESSAGE 4566

Main Index
 434 MSC Nastran Error Messages
Errors 4000 - 4999

SEALED RESPONSE SPECTRA REQUESTED BUT, SPECSEL FILE NOT IN DATA BASE.

User information: The Bulk Data entry used to control scaled response spectra is named DTI,SPSEL. It is
described in chapter 5 of the MSC NASTRAN Quick Reference Guide under that name. It must be stored
in the database using a DMAP alter, as described on the referenced entry description. Print the database
directory to see if the SPSEL block is present. See also Error Report 3042 in Chapter 17.

4567.0 *** USER WARNING MESSAGE 4567,

HESSENBERG METHOD FAILED TO CONVERGE.
ALTERNATE METHOD RECOMMENDED.

User information: For certain pathological problems, the transformation method may fail. In MSC testing,
this has occurred only for problems with multiple only for problems with multiple real roots or complex
conjugate roots with zero-real components. Avoidances are to add a small damping or stiffness term, to add
degrees of freedom, or otherwise perturb the problem to separate the roots on the real axis or move them
into the complex plane.

4567.1 *** USER WARNING MESSAGE 4567,

NEW HESSENBERG METHOD FAILED TO CONVERGE.

4567.2 *** USER WARNING MESSAGE 4567,

NEW HESSENBERG METHOD STOPPED TO CONVERGE.

4568.0 *** USER WARNING MESSAGE 4568

THE NUMBER OF SPECTRUMS SELECTED ON THE, DLOAD CARD DOES NOT MATCH
THE NUMBER OF SUPPORT POINTS., CALCULATIONS FOR THIS SUBCASE TERMINATED.

User information: The DLOAD Bulk Data entry is used for an unconventional purpose in response spec-
trum analysis. It is required, and is used to place a scaling factor on each coordinate with enforced motion.
Each of these coordinates must also be on SUPORT Bulk Data entries. (See Section 15.10.) Change the
number of pairs of Si, Li entries to match the number of coordinates where enforced motion occurs.

4569.0 *** USER FATAL MESSAGE 4569

Main Index
 MSC Nastran Error Messages 435
Errors 4000 - 4999

ERROR ON RECORD %1 of %2 - WRONG TYPE, NO TABLES OR INCOMPLETE PAIRS.

User information: An error has been found in the DTI Bulk Data entries used for response spectra input.
Check your input against the examples given in the Handbook for Dynamic Analysis. In particular, check
for the presence of "D", "U", or "A" on each record.

4570.0 ***USER INFORMATION MESSAGE 4570 (SELA)

NO LOADS WERE FOUND FOR UPSTREAM SUPERELEMENT %1.

User information: One of the matrices needed for load assembly was not found on the database. It is
assumed that no loads exist for this superelement.

4571.0 *** USER FATAL MESSAGE 4571 ---,

THE PARAMETER OLDSEQ FOR THE SEQUENCER MODULE HAS A VALUE%1 WHICH IS
NOT AN ACCEPTABLE VALUE. VALID SETTINGS ARE -1 THRU 8 FOR SERIAL RUNS AND 9
OR 11 FOR PARALLEL RUNS.

User information: The referenced parameter is set to an illegal value. See the MSC NASTRAN Quick Ref-
erence Guide, Section 6 for proper values for the parameter, and their action.

4571.1 *** USER WARNING MESSAGE 4571 ---,

THE PARAMETER NEWSEQ FOR THE SEQUENCER MODULE HAS A VALUE OF ZERO THIS
WILL BE CHANGED TO NEWSEQ=3

User information: The referenced parameter is set to an illegal value. See the MSC NASTRAN Quick Ref-
erence Guide, Section 6 for proper values for the parameter, and their action.

4572.0 *** USER FATAL MESSAGE 4572---,

RESEQUENCING PROCESSING CANNOT BE COMPLETED.

User information: The resequencing algorithm has failed to converge. Avoidances are:
1. request more memory;
2. divide the structure into groups, using the SESET Bulk Data entry;
3. avoid the resequencing operation by use of PARAM,NEWSEQ,-1.

4573.0 *** SYSTEM FATAL MESSAGE 4573---,

Main Index
 436 MSC Nastran Error Messages
Errors 4000 - 4999

UNABLE TO COMPUTE EIGENVALUE SOLUTION WITH THE QZ HESSENBERG METHOD

BECAUSE THE MAXIMUM INTEGER VALUE HAS BEEN EXCEEDED.

User information: THE MAXIMUM INTEGER NUMBER ALLOWED ON THIS MACHINE IS %1.
HOWEVER, THE SIZE OF THE PROBLEM, N=%2, IS SO LARGE THAT IT CAUSES MAXIMUM
INTEGER OVERFLOW.

User action: USE THE COMPLEX LANCZOS METHOD OR USE MODE=I8

4574.0 *** USER FATAL MESSAGE 4574 (SDR1)

DATA RECOVERY STARTED BUT NO DISPLACEMENT VECTORS AVAILABLE

User information: The SDR1 module has begun to expand the displacement vector from solution set size
to g-set size, but no solution set vector is available. Usual causes are a null load vector. Check the loading
input. If only enforced displacements are desired, add a very small load to produce a load vector. This mes-
sage may also occur in a non-superelement or non-module unstructured solution sequence if SEALL,
SEMG, SELG, SEKR, SELR, or SEMP are used in the Case Control.

4575.0 *** USER WARNING MESSAGE 4575 (ST2DN1DT)

The NDT and/or DT values on TSTEPNL Bulk Data entry %1 (for SUBSTEP %2) are different from
that of TSTEPNL %3 (for SUBSTEP %4).

User information: The NDT and DT values from TSTEPNL %3 will be used. SUBCASE ID = %5, STEP
ID = %6. TSTEPNL entries must have identical NDT and DT values for all SUBSTEPs under the same
STEP.

4576.0 *** USER WARNING MESSAGE 4576.

DISPLACEMENT OR VELOCITY OUTPUT REQUEST FOR GRID POINT %1 REFERENCED
IN DTI, SPSEL NOT PRESENT IN CASE CONTROL. NO SCALED RESPONSE SPECTRA WILL
BE CALCULATED FOR IT.

User information: Response spectra of the form requested by XYPLOT SPECTRAL etc. requires the pres-
ence of the DTI Bulk Data entries named SPECSEL. See Section 15.10. Scaled response spectra of the
form requested by XYPLOT SPECTRAL etc. has been listed on the required Bulk Data entry DTI,SPEC-
SEL, but not in DISP and VELO Case Control requests. Add Case Control requests for DISP and VELO.

4577.0 *** USER FATAL MESSAGE 4577. (GP3C)

Main Index
 MSC Nastran Error Messages 437
Errors 4000 - 4999

PLOAD4 LOAD SET =%1 REFERENCES ELEMENT ID =%2 WHICH WAS NOT FOUND
AMONG TRIA3, TRIAR, TRIA6, QUAD4, QUADR, QUAD8, HEXA, PENTA, TETRA OR HYPER-
ELASTIC SOLID ELEMENTS IN THE PROBLEM.

4578.0 *** USER FATAL MESSAGE 4578. (GP3C)

PLOAD4 LOAD SET =%1 WITH DIAGONAL CONNECTING GRIDS %2 AND %3 IS INCOR-
RECT FOR ELEMENT WITH ID =%4

User information: The two grids must be at opposite corners of a quadrilateral face.

4578.1 *** USER FATAL MESSAGE 4578. (GP0P4B)

PLOAD4 LOAD SET =%1 ELEMENT WITH ID =%2
GRIDS %3 AND %4 ARE NOT CONNECTING DIAGONALLY OPPOSITE.
PROGRAMMERS NOTE ( CORNER GRIDS ARE:%5 )

4578.2 *** USER FATAL MESSAGE 4578. (GP0P4A)

PLOAD4 LOAD SET =%1 HEXA ELEMENT WITH ID =%2
GRIDS %3 AND %4 ARE NOT CONNECTING DIAGONALLY OPPOSITE.

4579.0 *** USER FATAL MESSAGE 4579. (GP3C)

PLOAD4 LOAD SET =%1. TETRA ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A COR-
NER NODE FOR ANY TRIANGULAR FACE.

4579.1 *** USER FATAL MESSAGE 4579. (GP3C)

PLOAD4 LOAD SET =%1. PENTA ELEMENT%2 DOES NOT CONTAIN GRID%3 AS A COR-
NER NODE FOR EITHER TRIANGULAR FACE.

4579.2 *** USER FATAL MESSAGE 4579. (GP0P4A)

PLOAD4 LOAD SET =%1 TETRA ELEMENT WITH ID =%2
%3 IS NOT A CORNER NODE FOR THE TRIANGULAR FACE WHICH DOES NOT CONTAIN
"G4" = %4

4579.3 *** USER FATAL MESSAGE 4579. (GP0P4A)

PLOAD4 LOAD SET =%1 TETRA ELEMENT WITH ID =%2
GRID POINT %3 IS A INVALID FOR "G4".

Main Index
 438 MSC Nastran Error Messages
Errors 4000 - 4999

4579.4 *** USER FATAL MESSAGE 4579. (GP0P4A)

PLOAD4 LOAD SET =%1 PENTA ELEMENT WITH ID =%2 DOES NOT CONTAIN GRID %3
AS ACORNER NODE FOR EITHER TRIANGULAR FACE.

4580.0 *** USER WARNING MESSAGE 4580.

DET METHOD HAS CONVERGED TO A MULTIPLE POLE AT %1 INCREASE M.

User information: The EIGP Bulk Data entry is used to input known roots "poles"), and the number of
roots at the pole (the multiplicity, "M"). If M is underestimated, the method will not converge. If this con-
dition is detected, the iteration process is halted. Increase M.

4581.0 *** USER WARNING MESSAGE 4581 (FA1PKE)

PK FLUTTER ANALYSIS FAILED TO CONVERGE FOR LOOP %1, ROOT %2

User information: When using the PK-method for flutter analysis, the FA1 module may not always con-
verge to a solution. The last estimate has been kept for output. If DIAG 39 is used, the iteration data can be
printed for examination.

4582.0 *** USER WARNING MESSAGE 4582 (DPDBB),

EXCITATION ID=%1 SPECIFIED IN DYNAMIC LOAD DATA REFERS TO A NON-EXISTENT
STATIC LOADS MATRIX COLUMN %2 (NCOLS=%3)

User information: The most likely cause occurs when changing an LSEQ entry on a restart without regen-
erating and assembling the static load matrix. This error is detected in subroutine DPD2.

4583.0 *** SYSTEM FATAL MESSAGE 4583.0 (fasort):

THE FLUTTER ROOT SORTING ALGORITHM HAS ENCOUNTERED TWO DYNAMIC PRES-
SURES THAT ARE IDENTICAL AND THIS VIOLATES AN ASSUMPTION OF THE SORTING
ALGORITHM. THE TWO POINTS HAVE THE FOLLOWING INPUT:
POINT 1: DENSITY = %1, VELOCITY = %2
POINT 2: DENSITY = %3, VELOCITY = %4

User action: MODIFY THE FLFACT INPUT TO AVOID DUPLICATE DYNAMIC PRESSURES

4584.0 *** SYSTEM WARNING MESSAGE 4584---,

Main Index
 MSC Nastran Error Messages 439
Errors 4000 - 4999

UNABLE TO EXECUTE THE SEQUENCER PROCESSOR DUE TO THE LACK OF CONNEC-

TION DATA.

System information: No connection data could be found probably due to missing or incomplete Bulk Data
entries.0

4585.0 *** USER WARNING MESSAGE 4585. (PLOD1D)

PLOAD1 WITH SID %1 HAS AN APPLIED LOAD BEYOND THE END OF ELID %2

User information: The load specified or the element specified is being applied outside the end points of the
CBAR, CBEAM or CBEND element. The load will be applied correctly, but it is probably not what was
desired. The effective values for X1 and X2 on the PLOAD1 entry should be less than or equal to 1.0.

4587.0 *** USER FATAL MESSAGE 4587,

NO LOAD DATA AVAILABLE FOR CYCLIC SYMMETRY ANALYSIS.

User information: A cyclic symmetry analysis was requested but no load data is available. Include load data
in model (i.e., LOADCYN, LOADCYH, or LOADCYT and other appropriate load data). For superele-
ment analysis the user must include loads in all superelements.

4588.0 *** USER WARNING MESSAGE 4588 (SELA)

Main Index
 440 MSC Nastran Error Messages
Errors 4000 - 4999

The number of static load cases (%1) in the external superelement (%2) is not the same as the number of
static load cases (%3) in the downstream superelement (%4).

User information: Firstly, the external superelement load cases will be assembled in the same sequence as
the downstream superelement load cases. For example, the first external load case will be assembled into the
first downstream superelement load case, the second external load case will be assembled into the second
downstream superelement load case, etc.
Secondly,
1. If the number of external superelement load cases is less than the number of downstream
superelement load cases then the undefined external load cases are assumed to be null. For example,
if there is one external case and four downstream cases then the 2nd through 4th external cases are
assumed to be null in the downstream cases.
2. If the number of external superelement load cases is greater than the number of downstream
superelement load cases then the extra external superelement load cases will be ignored. For example,
if there are four external load cases and one downstream superelement case then the 2nd through 4th
external cases will be ignored in the downstream cases.

User action: Consider using the SELOAD Bulk Data entry to select and/or scale the external superele-
ment's loads. If not then:
1. If this is a static analysis then add or reduce the number of subcases in the external superelement's
creation run to match the number of subcases and align with the subcases in the downstream
superelement.
2. If this is a frequency or transient response analysis then add or reduce the number of subcases in the
external superelement's creation run to match the number of EXCITEIDs and aligned according to
ascending EXCITEIDs in the downstream superelement.

4588.1 *** USER WARNING MESSAGE 4588 (SubDMAP SELG)

Main Index
 MSC Nastran Error Messages 441
Errors 4000 - 4999

The number of columns (%1) in the P2G matrix is not the same as the number of columns (%2) in the
applied load matrix.

User information: Firstly, the P2G columns will be assembled in the same sequence as the applied load
matrix's columns. For example, P2G's first column will be assembled into the first column of applied load
matrix, P2G's second column will be assembled into the second column of the applied load matrix,
Secondly,
1. If the number of columns in P2G is less than the number of columns in the applied load matrix then
the missing columns in P2G are assumed to be null. For example, if there is one column in P2G and
four columns in the applied load matrix then the 2nd through 4th columns in P2G are assumed to
be null when added to the applied load matrix.
2. If the number of columns in P2G is greater than the number of columns in the applied load matrix
then the extra columns in P2G will be ignored. For example, if there are four columns in P2G and
one column in the applied load matrix then the 2nd through 4th columns in P2G will be ignored
when added to the applied load matrix.
User action: If this is an external superelement created with EXTSEOUT(DMIGPCH) then consider
using the SELOAD Bulk Data entry to select and/or scale the external superelement's loads. If not then:
1. If this is a static analysis then add or reduce the number of columns in P2G to match the number of
subcases and align with the subcases.
2. If this is a frequency or transient response analysis then add or reduce the number of columns in P2G
to match the number of EXCITEIDs and aligned according to ascending EXCITEIDs.

4589.0 *** USER INFORMATION MESSAGE 4589 ---,

THE SEQUENCER RIGID BODY PROCESSING REQUIRES AN ESTIMATED%1 WORDS OF
ADDITIONAL MEMORY.

4589.1 *** USER INFORMATION MESSAGE 4589 ---,

NO SPILL WILL OCCUR IN THE SEQUENCER (MPC & RIGIDS) WITH %1 WORDS OF ADDI-
TIONAL MEMORY.

4589.2 *** USER INFORMATION MESSAGE 4589 ---,

NO SEQUENCING COULD OCCUR WITH %1 WORDS LESS MEMORY.
*** SPILL FACTOR =%2 ***

4589.3 *** USER INFORMATION MESSAGE 4589 ---,

NO SPILL WILL OCCUR IN THE SEQUENCER WITH %1 WORDS OF ADDITIONAL MEM-
ORY.

Main Index
 442 MSC Nastran Error Messages
Errors 4000 - 4999

4590.0 *** USER WARNING MESSAGE 4590.

A SURFACE OR VOLUME CARD HAS BEEN IMPROPERLY DEFINED - IGNORED.

User information: The SURFACE or VOLUME command does not have a valid ID. Check all SURFACE
or VOLUME commands for proper integer IDs.

4591.0 *** USER WARNING MESSAGE 4591.

ILLEGAL PARAMETER SPECIFICATION ON A SURFACE OR VOLUME CARD. ID= %1

User information: The SURFACE or VOLUME command indicated contains data which cannot be prop-
erly interpreted or which is not a legal value for a given parameter. Check indicated SURFACE or VOL-
UME commands for illegal data.

4592.0 *** USER WARNING MESSAGE 4592.

THE SURFACE OR VOLUME CARD WITH ID =%1 HAS NO SET SPECIFICATION -
IGNORED.

User information: The SURFACE or VOLUME command indicated does not select a set of elements.
Check indicated SURFACE or VOLUME command for missing set ID specification.

4593.0 *** USER WARNING MESSAGE 4593.

THE SURFACE OR VOLUME CARD WITH ID =%1 HAS COLLINEAR AXIS AND NORMAL
SPECIFICATION. NOT ALLOWED - SURFACE OR VOLUME WILL BE IGNORED

User information: The SURFACE or VOLUME command indicated fails to select different axis and nor-
mal specifications. Check indicated SURFACE or VOLUME command for improper AXIS/NORMAL
specification combination. They must be different.

4594.0 *** USER WARNING MESSAGE 4594.

THE POSTCDB CONTAINS NO LEGITIMATE SURFACE OR VOLUME DEFINITIONS.

User information: SINCE NO LEGITIMATE SURFACE OR VOLUME COMMANDS EXIST, PRO-

CESSING STOPPED. CHECK OUTPUT(POST) AND CASE CONTROL GRID POINT STRESS
REQUESTS FOR CONSISTENCY. ALSO, MAKE SURE THAT SURFACE IS SPELLED COR-
RECTLY (SEE ERROR REPORT 3576 IN CHAPTER 17).

Main Index
 MSC Nastran Error Messages 443
Errors 4000 - 4999

4595.0 *** USER WARNING MESSAGE 4595.

UNABLE TO OPEN INTERNAL DATA BLOCK %1 IN GPSTR1 MODULE - PROCESS
STOPPED.

User information: An essential data block to module GPSTR1 is purged. A programming logic error exists
in GPSTR1 which failed to supply the indicated data block.

4596.0 *** USER WARNING MESSAGE 4596.

A SURFACE OR VOLUME CARD WITH ID= %1 REFERENCES A NON-EXISTENT SET ID =
%2.

User information: The set referenced on the surface card has not been defined within the post control sec-
tion of the CASE CONTROL, i.e. OUTPUT(POST). Check OUTPUT(POST) and Case Control grid
point stress requests for consistency of SURFACE definitions.

4597.0 *** USER WARNING MESSAGE 4597.

A SURFACE OR VOLUME CARD WITH ID = %1 REFERENCES A SET ID =%2 WHICH CON-
TAINS NOELEMENTS OF PERMISSIBLE TYPE.

User information: The set referenced contains no CQUAD4, CQUAD8, CQUADR, CTRIA3, CTRIA6
or CTRIAR elements. Grid point stresses are not calculated which contain no elements of permissible
types.

4598.0 *** USER WARNING MESSAGE 4598.

REFERENCE COORDINATE SYSTEM %1 SPECIFIED ON %2 CARD %3 IS NOT DEFINED IN
CSTM.
%4 IGNORED.

User information: The surface card references a nonexistent coordinate system. Reference coordinate sys-
tem on indicated SURFACE is not defined in (superelement or module) model. Surface ignored.

4599.0 *** USER WARNING MESSAGE 4599.

Main Index
 444 MSC Nastran Error Messages
Errors 4000 - 4999

THE REFERENCE STRESS OUTPUT X-AXIS IS PERPENDICULAR TO STRESS SURFACE %1

AT ELEMENT %2, GRID ID = %3. STRESSES ARE ILL-DEFINED AT THIS GRID POINT.

User information: The reference stress output X-AXIS does not project on the localaverage surface for indi-
cated element. The element to output stress rotation angle and fibre consistency cannot be determined.
Keys are assumed to be the same. Stresses are ill-defined at the indicated grid point number. Check refer-
ence output system and AXIS specification for consistency with indicated element.

4600.0 *** USER WARNING MESSAGE 4600.

THE REFERENCE STRESS OUTPUT NORMAL IS NEARLY PARALLEL TO ELEMENT, SUR-
FACE %1 AT ELEMENT %2, GRID ID = %3.

User information: The reference stress output NORMAL nearly lies in the element surface. Element fibre
to output fibre consistency may be incorrect. Stress must indicate internal grid point number may not be
valid. Check reference output system and NORMAL specification for consistency with indicated element.

4601.0 *** USER WARNING MESSAGE 4601.

THE REFERENCE STRESS OUTPUT X-AXIS IS NEARLY PERPENDICULAR TO ELEMENT,
SURFACE %1 AT ELEMENT %2, GRID ID = %3.

User information: The reference stress output X-AXIS does not project on the element surface. Element to
output stress rotation angle cannot be determined. Rotation angle set to 0. Stresses at indicated internal grid
point number may not be valid. Check reference output system and AXIS specification for consistency with
indicated element.

4602.0 *** USER WARNING MESSAGE 4602.

BREAK WARNING MESSAGE- GRID%1 IN SURFACE%2 CONNECTS TO A LINE SEGMENT
SHARED BY MORE THAN TWO ELEMENTS.

User information: Indicated grid point connects to a line segment shared by more than two elements
(GEOMETRIC interpolation only). Stress at indicated internal grid point may not be valid.

4603.0 *** USER FATAL MESSAGE 4603.

THE LSEQ SET ID %1 IS NOT UNIQUE WITH RESPECT TO OTHER STATIC LOAD IDS.

User information: LSEQ set IDs must be unique with respect to all other static load set IDs.

Main Index
 MSC Nastran Error Messages 445
Errors 4000 - 4999

4604.0 *** USER FATAL MESSAGE 4604.

FLUID MASS INTEGRATION ROUTINE HAS DETECTED ILLEGAL GEOMETRY.
SENDER ELEMENT ID =%1. RECEIVER ELEMENT ID =%2

User information: Surface elements used for virtual mass must not overlap. This message occurs when the
center of a receiver element lies at an edge of a sender element. Correct geometry or selection of elements.

4605.0 *** USER FATAL MESSAGE 4605.

INPUT MATRIX %1 IS INCOMPATIBLE WITH ITS ASSOCIATED OUTPUT LIST (I.E.,
TOL,FOL,LAMA,CLAMA).

User information: Input matrix to module MODACC has fewer columns than its output list indicates.
Probable DMAP error.

4606.0 *** USER WARNING MESSAGE 4606.

SURFACE OR VOLUME ID %1 HAS BEEN MULTIPLY DEFINED. LAST DEFINITION USED.

4607.0 *** USER WARNING MESSAGE 4607.

%1 %2 CONTAINS ELEMENTS OF QUESTIONABLE STRESS/STRAIN RECOVERY FORMULA-
TIONS, REASONS: %3 %4 %5 %6
1. MIX OF ELEMENTS WITH PLANE STRESS AND PLANE STRAIN RECOVERY.
2. MIX OF H-ELEMENTS AND HYPERELASTIC ELEMENTS DETECTED.
3. GAUSS DATA RECOVERY DETECTED ON SOME ELEMENTS.
4. AXISYMMETRIC AND NON-AXISYMMETRIC HYPERELASTIC ELEMENTS PRESENT.

User action: REASSIGN THE %1 WITH ELEMENTS THAT HAVE CONSISTENT STRESS/
STRAIN RECOVERY FORMULATIONS.

4608.0 *** USER WARNING MESSAGE 4608 FROM GPSTR1

COORDINATE SYSTEM SPECIFIED ON PSOLID BULK DATA ENTRY BUT NO CSTM DATA
BLOCK PRESENT.

4609.0 *** USER WARNING MESSAGE 4609 .

FOR ELEMENT ID=%1, THE CORNER POINTS HAVE NOT BEEN SUPPLIED CORRECTLY.
GPSTR1 TERMINATED.

Main Index
 446 MSC Nastran Error Messages
Errors 4000 - 4999

4610.0 *** USER WARNING/FATAL MESSAGE 4610 (TA0NLPRP)

Material combination has been specified for nonlinear property type %1 with ID= %2

4610.1 *** USER WARNING/FATAL MESSAGE 4610 (TA0NLPRP)

Material combination has been specified for ply ID %3 with nonlinear property type %1 with ID= %2

4611.0 *** USER INFORMATION MESSAGE 4611 (TA0NLEPT)

For property type %1 with ID= %2, the secondary property type %3 has been created automatically.

4612.0 *** USER INFORMATION/FATAL MESSAGE 4612 (TA0NLEPT)

For property type %1 with ID= %2, the secondary property type is not specified.

User action: Add the secondary property type %3.

4613.0 *** USER WARNING/FATAL MESSAGE 4613 (TA0NLEPT)

For property type %1 with ID= %2, the secondary property type is %4.

User action: Change the secondary property type to suggested type %3.

4614.0 *** USER FATAL MESSAGE 4614 (IFP1RUL2)

The first %1 ID = %2 is a linear perturbation with ANALYSIS = %3.

4615.0 *** USER INFORMATION MESSAGE 4615 (IFP1RUL2)

The linear perturbation analysis at %1 does not contain an NLIC command.

User information: By default, the immediately previous %2 = %3 in the same %4 will be assumed.

4616.0 *** USER FATAL MESSAGE 4616 (IFP1RUL2)

The NLIC command in linear perturbation analysis at %1 references %2 = %3 which is not a static analy-
sis.

4617.0 *** USER FATAL MESSAGE 4617 (IFP1RUL2)

NLIC command in linear perturbation analysis at %1 references SUBCASE = %2 which is not the current
SUBCASE.

User action: IF YOU WISH TO CONTINUE, SET SYSTEM(779)=0, OR REMOVE SYSTEM(779)=1.

Main Index
 MSC Nastran Error Messages 447
Errors 4000 - 4999

4617.1 *** USER WARNING MESSAGE 4617 (IFP1RUL2)

NLIC command in linear perturbation analysis at %1 references SUBCASE = %2 which is not the current
SUBCASE. This usage is not recommended.

User action: IF YOU WISH TO STOP, PLEASE SET SYSTEM(779)=1.

4618.0 *** USER FATAL MESSAGE 4618 (IFP1RUL2)

The NLIC command in linear perturbation analysis at %1 references a non-existent or later %2 = %3.

4619.0 *** USER WARNING MESSAGE 4619

PLOAD, PLOAD2 AND PLOAD4 WITH FOLLOWER FORCE ARE UNSUPPORTED IN MULTI-
STEP ANALYSIS EXCEPT WHEN THEY ARE REFERENCED IN THE LAST STEP ONLY

4620.0 *** USER WARNING MESSAGE 4620,

GPSTRESS REQUEST IN SUBCASES IGNORED SINCE NO BGPDT INPUT.

4621.0 *** USER WARNING MESSAGE 4621 (STDCON),

NO STRESS DATA IS AVAILABLE FOR ELEMENT %1 SUBCASE %2 SURFACE/VOLUME %3.

User information: Stress output for the specified element was not requested. This stress output is required
to calculate the grid stresses for the specified surface.

User action: REQUEST ELEMENT STRESS OUTPUT FOR ALL ELEMENTS IN THE SURFACE/
VOLUME.

4623.0 *** USER WARNING MESSAGE 4623

OES1 MISSING GPSTR2 PROCESSING ERMINATED.

4625.0 *** USER FATAL MESSAGE 4625

INSUFFICIENT MEMORY FOR GPSTR2 MODULE GINO BUFFER ALLOCATION.

4626.0 *** USER FATAL MESSAGE 4626

INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO PROCESS GPL.

4627.0 *** USER FATAL MESSAGE 4627

Main Index
 448 MSC Nastran Error Messages
Errors 4000 - 4999

INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO PROCESS CASECC.

4628.0 *** USER FATAL MESSAGE 4628

INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE STRFIELD SET.

4629.0 *** USER FATAL MESSAGE 4629

INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE GPSTRESS SET.

4630.0 *** USER FATAL MESSAGE 4630

INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE ELEMENT LIST.

4631.0 *** USER WARNING MESSAGE 4631,

STRFIELD SET %1 NOT FOUND IN CASECC SUBCASE%2

4632.0 *** USER WARNING MESSAGE 4632,

GPSTRESS SET %1 NOT FOUND IN CASECC SUBCASE%2

4633.0 *** USER WARNING MESSAGE 4633,

NO OUTPUT STRESS REQUEST FOR SUBCASE %1 SO NO GRID STRESSES CALCULATED

4634.0 *** USER WARNING MESSAGE 4634,

NO STRESSES FOR SUPPORTED ELEMENT TYPES ON OES1 FOR SUBCASE %1 SO NO GRID
STRESSES CALCULATED

4635.0 *** USER WARNING MESSAGE 4635,

GPSTRESS REQUEST IN SUBCASE %1 IGNORED SINCE OGS1 PURGED

4636.0 *** USER WARNING MESSAGE 4636,

STRFIELD REQUEST IN SUBCASE %1 IGNORED SINCE EGPST PURGED

4637.0 *** USER FATAL MESSAGE 4637

INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO STORE ELEMENT POINTER LIST

User information: GPSTR2 requires at least enough working space to hold in memory an element pointer
list consisting of two computer words for each element of a supported type (CQUAD4, CQUAD8,
CTRIA3, or CTRIA6) selected for output.

Main Index
 MSC Nastran Error Messages 449
Errors 4000 - 4999

4638.0 *** SYSTEM FATAL MESSAGE 4638,

LOGIC ERROR SUBROUTINE GPS2GS-SCR1 FILE INCONSISTENT WITH POINTER TABLE.
SEARCHING FOR EID %1 FOUND EID %2

4639.0 *** USER WARNING MESSAGE 4639,

GPSTRESS REQUEST IN SUBCASE %1 BUT NO MATCHING SURFACE OR VOLUME ID ON
EGPSF

4639.1 *** SYSTEM FATAL MESSAGE 4639, (GPS2GD)

LOGIC ERROR SUBROUTINE GPS2GS-SCR1 FILE ENTRY FOR EID %1 DOES NOT HAVE
GRID PT. %2

4640.0 *** USER WARNING MESSAGE 4640,

STRFIELD REQUEST IN SUBCASE %1 BUT NO MATCHING SURFACE OR VOLUME ID ON
EGPSF

User information: STRFIELD must reference set xx, which in turn references SURFACE or VOLUME yy.
For example,
SET 21 = 91
GPSTRESS = 21
STRFIELD = 21
...
OUTPUT(POST)
...
SURFACE 91 ---

4642.0 *** USER WARNING MESSAGE 4642 (NLINIT)

NLPARM SET%1 DISPLACEMENT CONVERGENCE OPTION IS INVALID FOR MATRIX
UPDATE INTERVAL OF ONE WHEN METHOD IS EITHER ITER OR LSQN. THE WORK(W)
CONVERGENCE OPTION HAS BEEN SUBSTITUTED IF NONE SUPPLIED.

4642.1 *** USER WARNING MESSAGE 4642 (NLTINT)

TSTEPNL SET%1 CONVERGENCE OPTION IS INVALID FOR MATRIX UPDATE INTERVAL
OF ONE HWHEN METHOD IS TSTEP. THE LOAD(P) CONVERGENCE OPTION HAS BEEN
SUBSTITUTED.

Main Index
 450 MSC Nastran Error Messages
Errors 4000 - 4999

4643.0 *** USER FATAL MESSAGE 4643 (GP1C)

DUPLICATE COORDINATE SYSTEM ID %1 FOUND IN SUPERELEMENT OR MODULE %2

User information: Message indicates user has defined a coordinate system twice. Check for duplicate coor-
dinate system IDs on CORD ij entries.

4645.0
THE SHIFTED STIFFNESS MATRIX IS NOT POSITIVE DEFINITE IN MHOUSEHOLDER
METHOD.

User information: The matrix sum K + LAMBDA * M is decomposed by the Cholesky method at the start
of the MGIV method of eigensolution. This decomposition requires that the matrix be positive-definite. A
condition that prevents this is a massless mechanism (for example, a point mass on an offset with no rota-
tional stiffness).

4645.1 ***USER WARNING MESSAGE 4645 (REIG)

THE SHIFTED STIFFNESS MATRIX IS NOT POSITIVE DEFINITE IN MGIVENS METHOD.

4646.0 ***USER FATAL MESSAGE 4646----

THE MASS MATRIX IS NOT POSITIVE DEFINITE, USING THE HOUSEHOLDER METHOD.
USE MGIV INSTEAD.

4646.1 ***USER FATAL MESSAGE 4646----

THE MASS MATRIX IS NOT POSITIVE DEFINITE, USING THE GIVENS METHOD. USE
MGIV INSTEAD.

User information: The reduced mass matrix has columns that are not linearly independent. Common
causes are rotation degrees of freedom whose only inertia terms result from point masses on offsets. Use the
MGIV or MHOU method instead since it does not require a positive definite mass matrix.

4646.4 *** USER FATAL MESSAGE 4646.

Main Index
 MSC Nastran Error Messages 451
Errors 4000 - 4999

THE MASS MATRIX INPUT TO THE REAL EIGENSOLVER IS INDEFINITE.

User action: INSPECT THE ELEMENTS CONNECTED TO THIS POINT. IF ALL ARE VALID, A
VALUE OF 1.E-6 OR MORE TIMES THE MASS DIAGONAL TERM PRINTED ABOVE ADDED
TO THIS DOF MAY MAKE THE MASS MATRIX ACCEPTABLE, IF THIS IS AN ACCEPTABLE
CHANGE TO YOUR MODEL. YOU MAY ALSO PERTURB THE MASS MATRIX DIAGONALS
BY SPECIFYING SYSTEM(304)=0 ON THE NASTRAN CARD. IF SUCH CHANGES ARE NOT
VALID, CONTACT YOUR HEXAGON AB SALES REPRESENTATIVE. YOU MAY HAVE DIS-
COVERED AN ERROR IN THE ELEMENT CODE.

4647.0 *** USER FATAL MESSAGE 4647.

INSUFFICIENT TIME TO COMPLETE %1
CPU ESTIMATE =%2 SEC. CPU REMAINING =%3 SEC.
I/O ESTIMATE =%4 SEC. I/O REMAINING =%5 SEC.

User information: CPU and I/O limits are supplied on the Executive Control statement TIME (in min-
utes). The module where the terminated program is listed. If the time to completion appears reasonable,
you should increase the estimates on the TIME statement and resubmit the run. For large models, an
increase in the system memory request should also be considered.

4648.0 ***USER WARNING MESSAGE 4648----

THE MODAL MASS MATRIX IS NOT POSITIVE DEFINITE.

User information: The modal mass matrix cannot be decomposed by the Cholesky algorithm after merging
elastic and free-body modes. (Cholesky decomposition is used to orthogonalize the eigenvectors with
respect to the mass matrix.) Causes include the input of negative masses and the calculation of eigenvectors
for eigenvalues approaching machine infinity. Inspect the model or ask for fewer eigenvectors using of the
F2 option. When this condition occurs, the eigenvectors are not orthogonalized r normalized. The second
parameter of the READ or REIGL module is given a negative sign. This parameter is used in the solution
sequences to branch to an error exit after printing the real eigenvalue table. You may use a DMAP Alter to
print these eigenvectors if the cause of the problem is not apparent in the eigenvalues. The solution can be
forced to completion by changing the sign of this parameter. You should be aware that a poor quality of
solution is provided for this case. This poor solution may be useful for diagnosing the problem but
should not be used for other purposes. The error can occur when large offsets (large relative to the element
length) are used for the BEAM element and coupled mass is selected.

4652.0 *** SYSTEM INFORMATION MESSAGE 4652 (NL2INT)

Main Index
 452 MSC Nastran Error Messages
Errors 4000 - 4999

THE ADDITIONAL MEMORY ESTIMATE IS %1 WORDS.

REDUCE P-SET BY APPROXIMATELY %2 DEGREES OF FREEDOM.

System information: For nonlinear problems (either statics or transient) there was insufficient open core
space to process the problem. This attempts to estimate the additional memory requirements in machine
words and supply an alternative approach to allow the user to reduce his problem size. Either supply more
machine memory or reduce the problem size by the indicated amount. This is similar to the UFM 6136.

4653.0 *** SYSTEM FATAL MESSAGE 4653. (TTX6D)

CORE IS INSUFFICIENT BY A BASE10 AMOUNT =%1 WORDS TO PROCESS ELEMENT
WITH ID =%2

System information: Reduce problem size or increase memory.

4654.0 *** USER FATAL MESSAGE 4654 .

ELEMENT WITH ID =%1
CONNECTS TWO POINTS HAVING THE SAME COORDINATES.
CONNECTION ORDER OF GRID POINTS IN QUESTION =%2 AND %3

User information: Two grid points which should be unique are defined as coincident. Check connectivity.

4654.1 *** USER FATAL MESSAGE 4654

ELEMENT WITH ID =%1 CONNECTS TWO GRID POINTS=%2 AND %3 HAVING SAME
COORDINATES.

4654.2 *** USER FATAL MESSAGE 4654 (SECNV3)

GRID POINTS %1 AND %2 REFERENCED ON THE FOLLOWING %3 BULK DATA ENTRY %4
ARE COINCIDENT

4654.3 *** USER FATAL MESSAGE 4654 (SECNV3)

THE VECTORS DEFINED BY THE GRID POINT PAIRS %1 / %2 AND %3 / %4 REFERENCED
ON THE FOLLOWING %5 BULK DATA ENTRY %6 ARE COINCIDENT

4655.0 *** USER INFORMATION/FATAL MESSAGE 4655

Main Index
 MSC Nastran Error Messages 453
Errors 4000 - 4999

RATIO OF LONGEST EDGE TO SHORTEST EDGE EXCEEDS 100 FOR ELEMENT WITH ID
=%1

User information: Aspect ratio too large. Try to idealize the structure in such a way that all the edges are
nearly the same size.

4655.1 *** USER WARNING MESSAGE 4655

IN CRAC2D ELEMENT%1 ,THE ASPECT RATIO EXCEEDS 2 TO 1 CAUSES RESULTS IN
WRONG ANSWERS

4655.2 *** USER WARNING MESSAGE 4655

IN CRAC3D ELEMENT%1 ,THE ASPECT RATIO EXCEEDS 2 TO 1 CAUSES RESULTS IN
WRONG ANSWERS

4655.3 *** USER INFORMATION MESSAGE 4655

THE RATIO OF LONGEST EDGE TO SHORTEST EDGE EXCEEDS %1 FOR %2 ELEMENT ID
=%3

User information: Aspect ratio too large. Try to idealize the element in such a way that all the edges are
nearly the same length.

4656.0 *** USER INFORMATION MESSAGE 4656

ELEMENT WITH ID =%1 HAS A SIDE WHICH IS CONSIDERABLY OUT OF PLANE.

User information: One of grid points for the element may be defined wrong. Check connectivity.

4656.1 *** USER INFORMATION MESSAGE 4656

PRE VERSION 2006 THERMAL EXPANSION METHOD USED.
SYSTEM(428) REQUESTS OLD METHOD FOR HEXA, PENTA AND TETRA ELEMENTS.

4657.0 *** USER INFORMATION MESSAGE 4657 .

CONNECTION ORDER GRID NUMBER %1 DOES NOT LIE APPROXIMATELY BETWEEN
CONNECTION ORDER GRID NUMBERS %2 AND %3 FOR ELEMENT ID = %4

User information: Midside node for the element node may be defined wrong. Check connectivity of all
nodes for the element.

Main Index
 454 MSC Nastran Error Messages
Errors 4000 - 4999

4658.0 *** USER FATAL MESSAGE 4658 .

DIFFICULT GEOMETRY PREVENTS FURTHER COMPUTATIONS FOR ELEMENT WITH ID
=%1

User action:
1. LOCATE THE ELEMENT WITHIN THE MODEL USING THE ELEMENT ID SPECIFIED.
2. IN THE LINEAR AND NON-LINEAR SOLUTION SEQUENCES, REVIEW THE
GEOMETRY CHECK INFORMATION SHOWN ABOVE, AND IMPROVE THE
ELEMENT GEOMETRY.
3. IN NON-LINEAR SOLUTION SEQUENCES, THE ELEMENT GEOMETRY MAY GET
WORSE BECAUSE OF THE DEFORMATION. CHECK THE ELEMENT GEOMETRY AT
THE INCREMENT BEFORE THE JOB STOPPED.

User information: Difficult geometry for solid elements occurs when faces have zero areas, or when Jacobi-
ans at integration points do not all have the same sign, which signifies that the edges are crossed. In geomet-
ric nonlinear analysis, tests are made for initial and deformed geometry. Elements should be modeled such
that their faces are as nearly equilateral as possible and midside nodes should be positioned close to the cen-
ter of their edges.

4658.5 *** USER FATAL MESSAGE 4658 .

DIFFICULT GEOMETRY PREVENTS FURTHER COMPUTATIONS FOR QHBDY WITH GRID
POINTS
%1

4659.0 *** USER FATAL MESSAGE 4659.

DURING INTEGRATION FOR ELEMENT WITH ID =%1 BAD GEOMETRY HAS BEEN
DETECTED.

User information: The element may be folding on itself. Check the grid points which connect all the edges
of the element.

4659.6 *** USER WARNING MESSAGE 4659 (PSNORD)

DURING COMPUTING NORMALS AT EDGE FOR ELEMENT WITH ID =%1 BAD GEOME-
TRY HAS BEEN DETECTED.

4659.7 *** USER WARNING MESSAGE 4659 (PSNORD)

Main Index
 MSC Nastran Error Messages 455
Errors 4000 - 4999

DURING COMPUTING NORMALS AT VERTEX FOR ELEMENT WITH ID =%1 BAD GEOME-
TRY HAS BEEN DETECTED.

4659.10 *** USER FATAL MESSAGE 4659 (ETETD)

DURING INTEGRATION FOR ELEMENT WITH ID =%1 BAD GEOMETRY HAS BEEN
DETECTED.

User action: IF YOU WISH TO CONTINUE, THEN SET SYSTEM(213)=1, HOWEVER, THE
RESULTS MAY BE POOR.

4659.11 *** USER INFORMATION MESSAGE 4659 (ETETD)

PRE VERSION 2007 TETRA FLUID MASS METHOD SELECTED BY SYSTEM(446)

4659.20 *** USER WARNING MESSAGE 4659

BAD GEOMETRY IGNORED FOR ELEMENT WITH ID =%1 BASED ON SYSTEM(213)=3.
HOWEVER, RESULTS MAY BE POOR.

User action: REMOVE SMALL GEOMETRIC FEATURES AND/OR REDUCE ELEMENT SIZE IN
THE IMMEDIATE NEIGHBORHOOD OF THIS ELEMENT BEFORE REMESHING. SEE
BELOW FOR ELEMENT CORNER GRID LOCATIONS. ELEMENT CORNER GRID INFORMA-
TION (X,Y,Z):
GRID 1: %2
GRID 2: %3
GRID 3: %4
GRID 4: %5

4659.21 *** USER WARNING MESSAGE 4659

Main Index
 456 MSC Nastran Error Messages
Errors 4000 - 4999

BAD GEOMETRY IGNORED FOR ELEMENT WITH ID =%1 BASED ON SYSTEM(213)=3.

HOWEVER, RESULTS MAY BE POOR.

User action: REMOVE SMALL GEOMETRIC FEATURES AND/OR REDUCE ELEMENT SIZE IN
THE IMMEDIATE NEIGHBORHOOD OF THIS ELEMENT BEFORE REMESHING. SEE
BELOW FOR ELEMENT CORNER GRID LOCATIONS. ELEMENT CORNER GRID INFORMA-
TION (X,Y,Z):
GRID 1: %2
GRID 2: %3
GRID 3: %4
GRID 4: %5
GRID 5: %6
GRID 6: %7

4659.22 *** USER WARNING MESSAGE 4659

BAD GEOMETRY IGNORED FOR ELEMENT WITH ID =%1 BASED ON SYSTEM(213)=3.
HOWEVER, RESULTS MAY BE POOR.

User action: REMOVE SMALL GEOMETRIC FEATURES AND/OR REDUCE ELEMENT SIZE IN
THE IMMEDIATE NEIGHBORHOOD OF THIS ELEMENT BEFORE REMESHING. SEE
BELOW FOR ELEMENT CORNER GRID LOCATIONS. ELEMENT CORNER GRID INFORMA-
TION (X,Y,Z):
GRID 1: %2
GRID 2: %3
GRID 3: %4
GRID 4: %5
GRID 5: %6
GRID 6: %7
GRID 7: %8
GRID 8: %9

4659.23 *** USER WARNING MESSAGE 4659 (EMBPMD)

BAD GEOMETRY IGNORED FOR ELEMENT WITH ID =%1
BASED ON SYSTEM(213)=1, HOWEVER RESULTS MAY BE POOR

4659.25 *** USER FATAL MESSAGE 4659 (TA0ECT)

Main Index
 MSC Nastran Error Messages 457
Errors 4000 - 4999

Bad geometry detected for CQUAD element ID = %1

User information: Ensure that the element is connected via G1, G2, G3, G4, and G9 only.

4659.26 *** USER FATAL MESSAGE 4659 (TA0ECT)

BAD INT CODE FOR CBEAM ELEMENT ID = %1

User information: ENSURE THAT INT2 IS LCO IN PBEMN1 FOR BEAM WITH WARPING.

4659.27 *** USER FATAL MESSAGE 4659 (TA0ECT)

THERE ARE ADDITIONAL %1 CBEAM ELEMENTS THAT HAVE BAD INT CODE

User information: ENSURE THAT INT2 IS LCO IN PBEMN1 FOR BEAM WITH WARPING.

4660.0 *** USER FATAL MESSAGE 4660 .

FOR ELEMENT WITH ID =%1
THE CORNER POINTS HAVE NOT BEEN SUPPLIED CORRECTLY.

4660.5 *** USER FATAL MESSAGE 4660 .

FOR ELEMENT WITH ID =%1
THE GEOMETRY HAS NOT BEEN DEFINED PROPERLY .

4660.11 *** USER FATAL MESSAGE 4660 (EGRACT)

FOR ELEMENT WITH ID =%1 ALL THE CORNER POINTS HAVE NOT BEEN SUPPLIED.

User action: SPECIFY ALL REQUIRED CORNER POINTS.

User information: Elements like CHEXA and CPENTA require, at a minimum, 8 or 6 corner points,
respectively. Minimum number of corner points are mandatory for certain elements. Check connectivity.

4661.0 *** USER FATAL MESSAGE 4661 .

ELEMENT %1 HAS SINGULAR STRAIN FUNCTIONS . CHECK MATERIAL PROPERTIES.

User information: Because of 0 in a diagonal element of strain function stiffness matrix, inversion is not
possible. Check to make sure tangent matrix is nonsingular.

Main Index
 458 MSC Nastran Error Messages
Errors 4000 - 4999

4661.1 *** USER FATAL MESSAGE 4661 .

THE MATERIAL PROPERTIES WILL NOT ROTATE WITH THE SOLID ELEMENTS FOR GEO-
METRIC NONLINEAR ANALYSIS DUE TO SYSTEM(%1)=%2

4662.0 *** USER WARNING MESSAGE 4662 .

SOME VARIABLES ARE RESET TO AVOID OVERFLOW OR UNDERFLOW CONDITIONS IN
ELEMENT ID = %1

User information: Creep laws are unit dependent. Creep parameters could get into overflow condition if
inconsistent units are used (e.g., lb and ksi). The program resets the value to 1.0E38 and continues. Check
structural units (length, force, stress, time, etc.). Reduce the time step (t).

4664.0 *** USER WARNING MESSAGE 4664 .

UNREALISTIC VALUE OF STRESSES FOR PLASTIC DEFORMATION IN ELEMENT-ID =%1

User information: This message is issued if the second invariant of the deviatoric stress is nearly zero during
plastic deformation. This condition should not occur under the normal deformation process. It may be a
program error if it happens. Use smaller steps. If this does not work, contact Hexagon.

4665.0 *** USER WARNING MESSAGE 4665 .

THE NUMBER OF LAYERS MUST BE GREATER THAN 0 AND LESS THAN 13 . FOR THIS
PROBLEM , NLAYER = %1

User information: NLAYER must be greater than zero and less than thirteen. NLAYER is the number of
layers for integration through the thickness. For bending, it is advisable to have NLAYER greater than 1.

4666.0 *** USER WARNING MESSAGE 4666 ,

PROBABLE ERROR . NEED MORE LAYERS THAN ONE IF BENDING .

User information: If bending is present, then wrong results are likely if only one layer is specified for inte-
gration through the thickness. Either use the default (5) or specify NLAYERS greater than 1.

4667.0 *** USER WARNING MESSAGE 4667 .

Main Index
 MSC Nastran Error Messages 459
Errors 4000 - 4999

INCREMENTAL TIME INTERVAL FOR CREEP ANALYSIS IS EXCESSIVE IN ELEMENT ID=%1

User information: This message is issued if the incremental creep strain (primary and/or total creep) is
greater than 10**-3 or if the incremental stress and/or strain is too large compared to the total stress/strain.
This message is issued only when the solution is converging. Reduce the creep time interval. This message
may also be issued when the initial static subcase is missing. Include a static subcase before the creep sub-
cases.

4669.0 *** USER FATAL MESSAGE 4669 .

NO LOAD DATA EXISTS FOR VECTOR =%1

User information: Check the CLOAD entry.

4670.0 *** USER FATAL MESSAGE 4670 .

SELECTED CLOAD BULK DATA CARD DOES NOT EXIST FOR SID = %1

4671.0 *** USER FATAL MESSAGE 4671 .

LOAD COMBINATION REQUESTED BUT LSEQ CARDS DO NOT EXIST FOR SID = %1

User information: Check the LSEQ entries.

4672.0 *** USER FATAL MESSAGE 4672 (TA1NLE).

PIN FLAG(S) IS(ARE) SPECIFIED FOR ONE OR MORE NONLINEAR CBEAM ELEMENT
ENTRIES.

User information: IN NONLINEAR ANALYSIS, THE USE OF PIN FLAGS ON NONLINEAR

BEAM ELEMENTS IS NOT SUPPORTED. Either remove the pin flags for nonlinear elements or make
the problem linear.

4672.1 *** USER WARNING MESSAGE 4672 (TA1A)

PIN FLAG(S) IS(ARE) SPECIFIED FOR ONE OR MORE CBEAM P-ELEMENT ENTRIES.

User information: IN P-ELEMENT ANALYSIS, THE USE OF PIN FLAGS ON BEAM P-ELEMENTS
IS NOT SUPPORTED.

4673.0 *** USER WARNING MESSAGE 4673 .

Main Index
 460 MSC Nastran Error Messages
Errors 4000 - 4999

AT LEAST ONE SOLID ELEMENT IGNORES NONLINEAR MATERIAL DATA BECAUSE

SELECTED OPTION IS NOT AVAILABLE.

User information: For nonlinear analysis, solid elements with nonlinear material properties may not have
midside nodes and their integration network may not be 3 or THREE. See the PSOLID entry description
in chapter 5 of the MSC NASTRAN Quick Reference Guide. Otherwise only a linear solution is possible.

4674.0 *** USER FATAL MESSAGE 4674 .

E IS TOO LARGE FOR ELEMENT =%1

4675.0 *** USER WARNING MESSAGE 4675 .

EXCESSIVE INCREMENTAL LOAD IS APPLIED IN ELEMENT ID = %1 REDUCE THE LOAD
INCREMENT BY A FACTOR OF %2 FOR BETTER SOLUTION .

User information: This message is issued if the number of sub-increments (m) in the plasticity routine is
required to be greater than 25. The number of sub-increments is determined by m = lnt ( F / FSTRESS * Y
+ 1 ) Where F is the value of yield function, Y is the yield stress, FSTRESS is the user input, on NLPARM
entry. Use smaller load increments.

4676.0 *** USER FATAL MESSAGE 4676 .

ERROR EXCEEDS %1 PERCENT OF YIELD STRESS IN ELEMENT ID=%2

User information: The error in the yield function will be corrected if it is within (FSTRESS*100) %. This
message will be issued if the error is greater than this. Take smaller load increments or specify a larger error
tolerance in the FSTRESS field on the NLPARM entry. All output requests are honored for subcases pro-
cessed prior to this message; then execution is terminated.

4676.1 *** USER WARNING MESSAGE 4676 (NLITER)

THE RESULTS JUST DECLARED CONVERGED HAVE NOT BEEN OUTPUT DUE TO EXCES-
SIVE INCREMENT DURING ELEMENT STRESS REVOVERY.

4678.0 *** USER WARNING MESSAGE 4678 .

TABLE LOOK-UP RESULTS IN NEGATIVE VALUE OF CREEP MODEL PARAMETER IN ELE-
MENT ID = %1

4678.1 *** USER WARNING MESSAGE 4678 (HMAT1)

Main Index
 MSC Nastran Error Messages 461
Errors 4000 - 4999

TABLE LOOK-UP ON TABLE ID %1 FOR MATERIAL ID %2 RESULTS IN A NEGATIVE VALUE

OF A MATERIAL PROPERTY FOR ELEMENT ID =%3 . THIS MATERIAL PROPERTY WILL BE
SET TO 0.0 .

User action: MAKE SURE THE TABLE CANNOT RETURN NEGATIVE VALUES BY INTERPO-
LATION OR BY EXTRAPOLATION.

User information: Creep parameters must be positive for table supplied data. The program sets the value to
zero and continues. Check the table values of creep parameters.

4679.0 *** USER WARNING MESSAGE 4679

ZERO DERIVATIVE ENCOUNTERED IN CREEP LAW TYPE 300 FOR ELEMENT ID = %1

User information: Unsolvable nonlinear equation in creep law type 300. The program sets the value to 10-
6 and continues. Check the creep data. Reduce t for creep.

4680.0 *** USER WARNING MESSAGE 4680

SEMAP DATA BLOCK DOES NOT EXIST.

4680.1 *** USER WARNING MESSAGE 4680

INPUT FILES TO TABPT ARE PURGED.

User information: "PURGED" means "does not exist".

4680.2 *** USER WARNING MESSAGE 4680

LISTFL DATA BLOCK DOES NOT EXIST.

4680.3 *** USER INFORMATION MESSAGE 4680

NO RIGID BODY VECTOR HAS EFFECTIVE MASS IN ITS DIRECTION OF MOTION.

4681.0 *** USER FATAL MESSAGE 4681

Main Index
 462 MSC Nastran Error Messages
Errors 4000 - 4999

INSUFFICIENT MEMORY FOR GPSTR2 MODULE TO SORT OGS1 DATA ON EXT GRID ID.

User information: In order to sort OGS1 data on external grid ID, GPSTR2 must store a table of size 2 x
(no. of grids in surface) in open core. The above message is issued if amount of open core will not accom-
modate this table. Increase memory request for the job.

4682.0 *** USER FATAL MESSAGE 4682,

HARMONICS SET SPECIFIED FOR ANALYSIS INCONSISTENT WITH SPECIFIED SYMME-
TRY OPTION.

User information: All of the harmonics specified by the user with the HARMONICS command are
excluded from the analysis by the symmetry option specified on the DSYM command. Note that the AA
and SS options omit all odd harmonics. The AS and SA options omit all even harmonics.

4683.0 *** USER FATAL MESSAGE 4683

Main Index
 MSC Nastran Error Messages 463
Errors 4000 - 4999

%1 MATRIX NEEDED FOR EIGENVALUE ANALYSIS

User action: CHECK YOUR MODEL AND ADD MASS DEFINITIONS. THE MATRIX CAN BE
GENERATED BASED ON THE FOLLOWING USER INPUTS:

1. RHO (MASS DENSITY) OF MATi ENTRIES (DEFINE DENSITY IN THE MATERIAL

PROPERTIES SECTION).
2. CONCENTRATED MASS OF CONM1 OR CONM2 ENTRIES.
3. NONSTRUCTURAL MASS OF CONROD, PBAR, PBARL, PBCOMP, PBEAM, PBEAM3,
PBEAML, PCOMP, PCOMPG, PCONEAX, PROD,PSHEAR, PSHELL, PTUBE, NSM, NSM1,
NSML, AND NSML1 ENTRIES.
4. DIRECT MATRIX INPUT, DMI OR DMIG.

User information: There is no mass found at the solution set degrees-of-freedom. Set PARAM,GRD-
PNT,0 to see if the model has mass. If it does, then use WEIGHTCHECK to see if there is any mass in a-
set for system modes (or o-set for component modes). If there is no mass reported in WEIGHTCHECK
then check for the following:
RHO field on MATi Bulk Data entries is zero or unspecified
All of the mass is eliminated by MPC, SPCi, or rigid elements
Non-structural mass (NSM) on element properties (i.e., PSHELL, PBAR)
Concentrated mass (CONMi or CMASSi Bulk Data entries)
The program requires at least one of the above to compute the mass matrix. Incorrect cross-sectional prop-
erties may also lead to this error but typically show up as another error.

4683.1 *** USER FATAL MESSAGE 4683,

DIFFERENTIAL STIFFNESS MATRIX NEEDED FOR EIGENVALUE ANALYSIS

User information: The eigensolution module was given a purged (that is, nonexistent) differential stiffness
matrix. Check for the following:
Missing static analysis (STATSUB)
Elements in the model do not have a differential stiffness formulation
Static analysis results in zero displacements

4684.0 *** SYSTEM FATAL MESSAGE 4684 (SNHEXD)

NUMERIC OVERFLOW ENCOUNTERED FOR THE VALUE OF CREEP STRAIN IN ELEMENT
ID=%1.

Main Index
 464 MSC Nastran Error Messages
Errors 4000 - 4999

4685.0 *** SYSTEM WARNING MESSAGE 4685 (EFFMAS)

The mass matrix is null and therefore modal effective mass calculations will be skipped.

4691.0 *** USER FATAL MESSAGE 4691

ERROR IN CHBDY CARD%1 THE FIRST TWO GRID POINTS MUST DETERMINE A LINE IN
THE X-Z PLANE WHICH IS NOT PARALLEL TO THE X AXIS. THE X COORDINATES MUST
BOTH BE POSITIVE.

User information: This error may also occur if the REV option is used for TYPE on the CHBDY Bulk
Data entry, and the IVIEW field is not blank. Set IVIEW (Field 9).

4696.0 **USER FATAL MESSAGE 4696,

MODE ACCELERATION RECOVERY REQUESTED BUT LLL MATRIX NOT AVAILABLE.

4697.0 *** USER FATAL MESSAGE 4697 (XSBFF)

THE BELOW BULK DATA FREE FIELD ENTRY HAS MORE THAN TEN FIELDS SPECIFIED.
(ENTRY IGNORED).
%1

User information: A free field Bulk Data entry had more than ten fields specified. Only ten fields are
allowed on a free field Bulk Data entry.

4698.0 *** USER WARNING MESSAGE 4698.

STATISTICS FOR DECOMPOSITION OF MATRIX %1.
THE FOLLOWING DEGREES OF FREEDOM HAVE FACTOR DIAGONAL RATIOS GREATER
THAN %2 OR HAVE NEGATIVE TERMS ON THE FACTOR DIAGONAL.

User information: THIS MESSAGE MAY BE IGNORED IF NO GRID POINT IDS OR HIGH
RATIO MESSAGES APPEAR IN THE TABLE ON THE NEXT PAGE.

User information: During decomposition, the degrees of freedom listed have pivot ratios that are that are
greater than maxratio or are negative. Verify that the degrees of freedom are not part of a mechanism and
that elements do not have excessive stiffness. In superelement analysis this condition causes run termina-
tion. PARAM,BAILOUT may be used to continue the run. See the MSC NASTRAN Numerical Methods
User's Guide.

Main Index
 MSC Nastran Error Messages 465
Errors 4000 - 4999

4699.0 *** USER WARNING MESSAGE 4699 (XSBFF)

THE FREE FIELD BULK DATA ENTRY BELOW HAS A REAL FIELD WITH MORE THAN 8
CHARACTERS. SOME PRECISION MAY BE LOST.
%1

User information: The Bulk Data entry replicator reads the first eight fields of an entry, then discards any
that may remain. This may lead to unintended results. Check all entries generated by the replicator if this
message appears.

4699.1 *** USER WARNING MESSAGE 4699 (XSBFF)

THE CONTROL FILE ENTRY BELOW HAS A REAL FIELD WITH MORE THAN 8 CHARAC-
TERS. SOME PRECISION MAY BE LOST.
%1

4700.0 *** USER ERROR MESSAGE 4700

TABLE %1 used in MATEP %2 must be stress vs plastic strain since Y0 is zero

4700.1 *** USER ERROR MESSAGE 4700

MATEP %2 uses "TABLE" option, but TABLE %1 is not defined. Please define TABLE %1 or refer to an
available TABLE ID.

4700.2 *** USER ERROR MESSAGE 4700

TABLE %1 used in MATTEP %2 for T(Y0) is of the wrong format

4700.3 *** USER ERROR MESSAGE 4700

TABLE %1 used in MATTEP %2 for T(FID) is of the wrong format

4700.4 *** USER ERROR MESSAGE 4700

TABLE %1 used in MATTEP %2 for T(H) is of the wrong format

4999.0 *** USER ERROR MESSAGE 4999

IRLOAD is not allowed if superelements present or LGDISP is not -1

Main Index
 466 MSC Nastran Error Messages
Errors 4000 - 4999

Main Index
 MSC Nastran Error Messages 467
Errors 5000 - 5999

Errors 5000 - 5999

5000.0 *** USER FATAL MESSAGE 5000 (EFD2D)
NEGATIVE OR ZERO RADIUS DETECTED FOR CFLUID2 ELEMENT %1

5001.0 *** USER FATAL MESSAGE 5001 (EFD3D)

NEGATIVE OR ZERO RADIUS DETECTED FOR CFLUID3 OR CFLUID4 ELEMENT %1

5002.0 *** USER FATAL MESSAGE 5002 (EFD4D)

INTERIOR ANGLE GREATER THAN OR EQUAL TO 180 DEGREES FOR ELEMENT %1

5003.0 *** USER FATAL MESSAGE 5003 (TA1BND)

THE BEND RADIUS RB IS A NEGATIVE NUMBER CREATING ILLEGAL GEOMETRY FOR
ELEMENT = %1

User information: The orientation of the CBEND element has been improperly specified (see the remarks
on the CBEND entry). Correct the CBEND element geometric or orientation vector data.

5004.0 *** USER FATAL MESSAGE 5004 (TA1BND)

THE ARC SUBTENDED BY THE BEND ELEMENT = %1 HAS EXCEEDED AN ARC OF 180
DEGREES.

User information: The orientation of the CBEND element has been improperly specified (see the remarks
on the CBEND entry). Correct the CBEND element geometric or orientation vector data.

5005.0 *** USER FATAL MESSAGE 5005 (APPEND)

INVALID VALUE OF OPTION PARAMETER DETECTED %1

User information: The user, in calling a module, has specified an option that does not
exist. Change the option parameter in the DMAP statement.

5005.1 *** USER WARNING MESSAGE 5005 (AFERRM)

Main Index
 468 MSC Nastran Error Messages
Errors 5000 - 5999

THE ADAMS/FLEX MNF GENERATION MODULE DETECTED AN ILLEGAL VALUE SPECI-

FIED FOR DMAP PARAMETER NUMBER %1. VALUE = %2 MNF GENERATION ABORTED.

User Information: The ADAMSMNF Case Control Command describers require values for the various
options. These values are assigned to the DMAP parameters input to the ADAMSMNF module. Other
information such as problem size, superelement ID and number of superelements are all input as parame-
ters. These DMAP parameters are checked to ensure that they are in acceptable ranges.
For example, the superelement ID must be positive. The acceptance rules are shown in the following table.
ADAMS/FLEX MNF GENERATION MODULE DMAP PARAMETER DESCRIPTION TABLE
Position Type Description Acceptance Rules
1 CHAR Path Qualifier Value for Superelement ID Any valid character string
2 INT Superelement ID Must not be negative.
3 INT Number of Superelements in the problem Must not be negative.
4 INT Number of g-set DOF Must be positive.
5 INT Number of a-set DOF Must be positive.
6 CHAR Output File generation request Must be one of "MNF ", "BOTH" or "MASS"
7 CHAR Output grid point stress request Must be one of "YES " or "NO "
8 CHAR Output grid point strain request Must be one of "YES " or "NO "
9 CHAR Mass invariant processing option Must be one of "FULL", "PART", "CONS" or
"NONE"
10 INT Plot set ID Any valid integer.

User Action: Ensure that the ADAMSMNF Case Control Command specifies valid input options. If
PARAM bulk data entries are used, ensure that none of them accidentally update the ADAMSMNF Case
Control Command options.

5006.0 *** USER FATAL MESSAGE 5006 (APPEND)

INPUT FILES HAVE DIFFERENT RECORD TYPES

User information: One of the input files was a matrix and the other was not.

5007.0 *** USER FATAL MESSAGE 5007

INPUT MATRICES ARE OF DIFFERENT DATA TYPES

User information: The matrices involved are of different data types, e.g., one contains real data and another
contains integer data.

Main Index
 MSC Nastran Error Messages 469
Errors 5000 - 5999

5007.1 *** USER FATAL MESSAGE 5007

INPUT MATRICES ARE OF DIFFERENT DATA TYPES. THIS MAY BE CAUSED BY USING THE
AUTOMATIC MODEL PARTITIONER FOR A VERY SMALL MODEL.

User action: IF THE MODEL HAS LESS THAN 100 GRID POINTS, PLEASE REMOVE DMP
FROM THE SUBMITTAL LINE.

User information: The matrices involved are of different data types, e.g., one contains real data and another
contains integer data.

5008.0 *** USER FATAL MESSAGE 5008

THE INPUT MATRICES HAVE DIFFERENT NUMBERS OF ROWS

User information: One of the input matrices has a larger number of rows than the other(s), thereby pre-
venting the requested matrix calculation.

5009.0 *** USER FATAL MESSAGE 5009

IN CALL TO %1, UGX MATRIX OF WRONG SIZE

User information: The number of columns in the UGX matrix is not evenly divisible by the number of col-
umns in the UG matrix. As a result, the UGX matrix cannot be divided into submatrices for the DSVG3
routine. Check the generation sequence for the UGX matrix.

5010.0 *** USER INFORMATION MESSAGE 5010

STURM SEQUENCE DATA FOR EIGENVALUE EXTRACTION.
TRIAL EIGENVALUE = %1, CYCLES = %2 THE STURM COUNT = %3

User information: This message is automatic output during eigenvalue extraction. This can be used, along
with the list of eigenvalues, to identify the modes found. See the MSC NASTRAN Numerical Methods
User's Guide.

5146.0 *** USER FATAL MESSAGE 5146

IN GPSPEN OF GPSTR1. MUST BE A CODING ERROR,
SINCE EMG SHOULD HAVE FOUND GEOMETRY ERROR
ELEMENT ID= %1

5147.0 ***SYSTEM FATAL MESSAGE 5147

Main Index
 470 MSC Nastran Error Messages
Errors 5000 - 5999

LOGIC ERROR, READ COUNTER IF1 = 0 --UTILITY MERGER TERMINATED

5148.0 ***SYSTEM FATAL MESSAGE 5148

LOGIC ERROR, READ COUNTER IF2 = 0 --UTILITY MERGER TERMINATED

5149.1 ***USER WARNING MESSAGE 5149 (DSAB5A)

NO PROPERTY IDS REFERENCED ON DVSET CARDS WERE FOUND IN ELEMENT PROP-
ERTY TABLE EPT.

5151.0 ***USER FATAL MESSAGE 5151

IN GPSHEX ROUTINE OF GPSTR1 ,MUST BE A CODING ERROR SINCE GEOMETRY
SHOULD HAVE BEEN CHECKED IN EMG ROUTINES FOR HEXA ELEMENT %1

5164.0 *** SYSTEM FATAL MESSAGE 5164 (DSVG1D)

DATA BLOCKS %1 AND %2 ARE INCONSISTENT.

5165.0 *** USER FATAL MESSAGE 5165 (DSVGPD)

ELEMENT TYPE = %1 (%2) ELEMENT ID = %3 DOES NOT EXIST IN ESTDVF DATA BLOCK

5165.1 *** USER FATAL MESSAGE 5165 (DVSGPD)

ELEMENT TYPE = %1 (%2), DOES NOT EXIST IN ESTDVF/ESTDVB DATA BLOCK

5165.2 *** USER FATAL MESSAGE 5165 (DVSGPD)

ELEMENT TYPE = %1 (%2) HAS MISS MATCH INFORMATION IN ESTDVF AND ESTDVB
DATA BLOCK

5172.0 *** USER FATAL MESSAGE 5172 (DSDJ1D)

THE VARIATIONAL ELEMENT ID IN %1 INCONSISTENT WITH THE VARIATIONAL ELE-
MENT ID IN %2, MODULE DSVG1 IS TERMINATED.

User information: Inconsistent variational element ID between XKDICT and DSPT1 data sets. Check
XKDICT and DSPT1 data blocks. Send run to Hexagon.

5174.0 *** USER WARNING MESSAGE 5174 (DSVG1D)

FOR MODE NUMBER %1 GENERALIZED MASS IS EQUAL TO ZERO. THE CORRESPOND-
ING DESIGN SENSITIVITY GRADIENTS SET TO ZERO.

Main Index
 MSC Nastran Error Messages 471
Errors 5000 - 5999

5181.0 *** USER FATAL MESSAGE 5181. (NLSL3D)

ELEMENT WITH ID = %1 HAS A GRID POINT OPPOSITE TO THOSE OF A FACE RECEIV-
ING A PRESSURE LOAD WHICH IS EVIDENTLY IN THE SAME PLANE AS THIS FACE.

User information: The solid element is so distorted that it is impossible to find the inward direction for
pressure loads. This can happen with incorrect grid geometry, or excessive deflections with geometric non-
linear option. Fix model or reduce load increments.

5182.0 *** USER FATAL MESSAGE 5182. (NLSL3D)

ELEMENT ID = %1 CID =%2, N1, N2, N3 =%3
LOAD DIRECTION VECTOR WHEN TRANSFORMED TO BASIC CO-ORDINATES AT A
GAUSS POINT HAS A ZERO LENGTH.

User information: The user supplied N vector or the PLOAD4 Bulk Data entry was nonzero but became
zero when transformed to basic. This is a program error or underflow.

5183.0 *** USER WARNING MESSAGE 5183. (DRMS2-2)

OUTPUT DATA BLOCK CORRESPONDING TO INPUT MODAL SOLUTION DATA BLOCK
%1 IS NOT PRESENT. INPUT DATA BLOCK THUSLY IGNORED.

User information: Since the output data block was purged, the data in the corresponding input data block
was not used.

5184.0 *** USER WARNING MESSAGE 5184.

INVALID INPUT DATA DETECTED IN DATA BLOCK %1. PROCESSING STOPPED FOR THIS
DATA BLOCK.

5185.0 *** USER WARNING MESSAGE 5185. (DRMS2B-1)

THE AMOUNT OF DATA IS NOT CONSISTENT FOR EACH EIGENVALUE IN DATA BLOCK
%1 PROCESSING OF THIS DATA BLOCK TERMINATED.

User information: Send run to Hexagon.

5186.0 *** USER WARNING MESSAGE 5186. (DRMS2A-2)

A CHANGE IN WORD 2 OF THE OFP-ID RECORDS OF DATA BLOCK %1
HAS BEEN DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED.

Main Index
 472 MSC Nastran Error Messages
Errors 5000 - 5999

5187.0 *** USER INFORMATION MESSAGE 5187. (DRMS1-3)

INSUFFICIENT MEMORY, ADDITIONAL %1 WORDS ARE NEEDED.

5188.0 *** USER INFORMATION MESSAGE 5188. (DRMS2-1)

MODULE DRMS2 TERMINATED WITH VARIABLE IERROR = %1

5189.0 *** USER WARNING MESSAGE 5189. (DRMS2A-3)

ILLEGAL MAJOR OR MINOR OFP-ID IDENTIFICATIONS = %1 %2
DETECTED IN DATA BLOCK%2. PROCESSING OF SAID DATA BLOCK DISCONTINUED.

5190.0 *** USER WARNING MESSAGE 5190. (DRMS2B-3)

DATA BLOCK%1 MAY NOT BE FULLY COMPLETED DUE TO A MEMORY INSUFFICIENCY
OF APPROXIMATELY%2 DECIMAL WORDS.

5191.0 *** USER WARNING MESSAGE 5191. (DRMS2B-2)

A CHANGE IN WORD 2 OF THE OFP-ID RECORDS OF DATA BLOCK %1
HAS BEEN DETECTED. PROCESSING OF THIS DATA BLOCK HAS BEEN TERMINATED.

5192.0 *** user warning message (drmh3c)

There is a request for strain curvatures but the element strain output transformation matrix (OTM) con-
tains only fiber strains. The STRCUR keyword (default) will be ignored.

5192.1 *** user warning message (drmh3c)

There is a request for fiber strains but the element strain output transformation matrix (OTM) contains
only strain curvatures. The FIBER keyword will be ignored.

5193.0 *** USER WARNING MESSAGE 5193,

PARTITION FILE %1 IS OF SIZE %2 ROWS BY %3 COLS.
PARTITIONING VECTORS INDICATE THAT THIS PARTITION SHOULD BE OF SIZE %4
ROWS BY %5 COLUMNS FOR A SUCCESSFUL MERGE.

5194.0 *** USER WARNING MESSAGE 5194,

THE FORM PARAMETER AS GIVEN TO THE MERGE MODULE IS INCONSISTENT WITH
THE SIZE OF THE MERGED MATRIX, HOWEVER IT HAS BEEN USED. FORM = %1 SIZE =
%2 ROWS BY %3 COLUMNS.

Main Index
 MSC Nastran Error Messages 473
Errors 5000 - 5999

5195.0 *** USER WARNING MESSAGE 5195,

REQUESTED VALUE OF %1%2 %3USED BY %4. LOGICAL CHOICE IS %5

5196.0 *** SYSTEM FATAL MESSAGE 5196,

ATTEMPT TO RECOVER PLASTIC-STRAIN VS SLOPE FOR ELEMENT %1 MATERIAL %2
WHEN NONE FORMULATED.

System information: This message is issued if MATS1 refers to TABLES1 which does not exist.
This error is also issued if PLASTIC is specified with TID and the first data point is not at the origin.
Check MATS1 and TABLES1 entries to ensure that proper tables exist.

5196.1 *** USER FATAL MESSAGE 5196,

TID of MATS1 MID=%1 is zero or not provided. TID is required when TYPE is NLELAST.

5197.0 ****USER FATAL MESSAGE 5197 (MPRO)

MATRIX MCHI3 IS SINGULAR.

User information: Module MPRO attempted to decompose matrix MCHI3 which was singular.
The location of the fluid coordinate system must not touch any element.
It should be at the center of fluid.

5199.0 *** USER FATAL MESSAGE 5199 (XSBFF)

THE BULK DATA FREE FIELD ENTRY BELOW HAS AN INTEGER OR A CHARACTER FIELD
WITH MORE THAN EIGHT CHARACTERS.
%1

User information: The bulk data free field formatter will not accept integer or character fields with more
than eight characters, since it only generates single field entries.
This can also occur when the line length exceeds 72 characters (note that commas count as characters).

5199.1 *** USER FATAL MESSAGE 5199 (XSBFF)

THE CONTROL FILE ENTRY BELOW HAS AN INTEGER OR A CHARACTER FIELD WITH
MORE THAN EIGHT CHARACTERS.
%1

5202.0 *** USER WARNING MESSAGE 5202 .

Main Index
 474 MSC Nastran Error Messages
Errors 5000 - 5999

NOT POSSIBLE TO PERFORM TEMPERATURE CORRECTION FOR ELEMENT ID = %1

AS TEMPERATURE IS ZERO.

User information: The value of the absolute temperature must be greater than zero for temperature correc-
tions in the creep process. The program ignores temperature corrections and continues. Check the "RT"
field on the CREEP entry and the PARAM,TABS Bulk Data entry. To reduce the amount of output gener-
ated, this message is printed for the first element only while the error may exist for others.

5203.0 *** USER WARNING MESSAGE 5203

THE SEMAP DATA BLOCK HAS BEEN MARKED NON-EXECUTABLE BY MODULE SEP1.

5203.1 *** USER FATAL MESSAGE 5203 .

IMPLAUSIBLE CREEP LAW OF TYPE 300 IS USED.

User information: The value of d must be less than 2 on the CREEP entry.

5214.0 *** USER FATAL MESSAGE 5214,

GRAV OPTION ON LOADCYH ENTRY ILLEGAL FOR BUCKLING

5215.0 *** USER FATAL MESSAGE 5215,

RFORCE OPTION ON LOADCYH ENTRY ILLEGAL FOR BUCKLING

5217.0 *** USER FATAL MESSAGE 5217 (DPD1)

POINT ID %1 DUPLICATES A GRID OR SCALAR POINT ID

User action: Check above to see if User Warning Message 2470 is issued above.

User information: While processing the external grids in Module DPD, duplicate grid numbers were
found.

5217.1 *** USER FATAL MESSAGE 5217 (GP1A, GP1GSM)

Main Index
 MSC Nastran Error Messages 475
Errors 5000 - 5999

THE GRID OR SCALER POINT ID, %1, IS IN CONFLICT WITH THE LAGRANGE MULTI-
PLIER ID FOR RIGID ELEMENTS.

User action: CHANGE THE GRID OR SCALER POINT ID, OR CHANGE THE LAGRANGE
MULTIPLER ID BY USING THE BULK DATA ENTRY: 'PARAM,ORIGID,rigid0', WHERE rigid0
IS THE OFFSET FOR LAGRANGE MULTIPLIER ID. rigid0 MUST BE LARGER THEN ALL GRID
AND SCALER POINT ID. THE CURRENT LAGRANGE MULTIPLIER ID'S ARE FROM %2
TO %3.

5218.1 *** USER INFORMATION MESSAGE 5218 (WILVCD)

EIGENVALUE APPROACHING INFINITY AT %1TH MODE. EIGENVECTORS WILL NOT BE
COMPUTED BEYOND THIS POINT.

User information: The MGIV, MHOU, AGIV, and AHOU methods substitute a very large number for
eigenvalues that approach machine infinity. If eigenvectors are computed for these artificial values, they
may be numerical noise, or they may cause overflows. Eigenvector computation is halted at the first
machine infinity instead even if you requested eigenvectors in this range.

5218.2 *** USER INFORMATION MESSAGE 5218 (CLASDD)

%1 INFINITE ROOTS AND %2 INDETERMINATE ROOTS HAVE BEEN FOUND, FOR A
PROBLEM SIZE OF %3.
EIGENSOLUTIONS ARE NOT PROVIDED FOR INFINITE OR INDETERMINATE ROOTS.

5219.0 *** USER FATAL MESSAGE 5219

FORM 3 MATRIX INPUT TO SMPYAD MODULE. USE MATMOD OPTION 27 FIRST.

User information: Prior to Version 63, a special diagonal matrix could be input via DMI entries. It could
be used properly only by the ADD, MPYAD, and MATPRN modules. This capability has been removed
from the first two modules.
Use MATMOD Option 27 to convert the matrix to Form 6.

5219.1 *** USER FATAL MESSAGE 5219

Main Index
 476 MSC Nastran Error Messages
Errors 5000 - 5999

FORM 3 MATRIX INPUT TO DMPYAD MODULE. USE MATMOD OPTION 27 FIRST.

User information: Prior to Version 63, a special diagonal matrix could be input via DMI entries. It could
be used properly only by the ADD, MPYAD, and MATPRN modules. This capability has been removed
from the first two modules.
Use MATMOD Option 27 to convert the matrix to Form 6.

5219.2 *** USER FATAL MESSAGE 5219 (ADD)

FORM 3 MATRIX INPUT TO ADD MODULE. USE MATMOD OPTION 27 FIRST.

User information: Prior to Version 63, a special diagonal matrix could be input via DMI entries. It could
be used properly only by the ADD, MPYAD, and MATPRN modules. This capability has been removed
from the first two modules.
Use MATMOD Option 27 to convert the matrix to Form 6.

5220.0 *** USER FATAL MESSAGE 5220 (SEP1A)

GRID NO. %1 APPEARS MORE THAN ONCE ON CSUPER ENTRY WITH SSID = %2

5220.1 *** USER FATAL MESSAGE 5220 (SEPEXT)

GRID OR SCALAR ID=%1 APPEARS MORE THAN ONCE ON EXTRN BULK DATA ENTRY
WITH SUPERELEMENT=%2.

5221.0 *** USER WARNING MESSAGE 5221.

STATISTICS FOR DECOMPOSITION OF MATRIX %1.
THE FOLLOWING DEGREES OF FREEDOM HAVE NULL COLUMNS.

User information: Module DCMP tried to decompose a matrix which was singular. That matrix had null
columns and the associated grid point numbers and degrees of freedom are printed out.

5221.1 *** USER FATAL MESSAGE 5221.

STATISTICS FOR ITERATIVE SOLUTION/DECOMPOSITION OF MATRIX %1.
THE COLUMNS ASSOCIATED WITH THE FOLLOWING DEGREES OF FREEDOM ARE
NULL.

User information: Module SOLVIT iterative solver tried to operate on a matrix that contains null
columns.
The null column numbers and the associated grid point numbers and degrees of freedom are printed out.

Main Index
 MSC Nastran Error Messages 477
Errors 5000 - 5999

5222.0 *** USER INFORMATION MESSAGE 5222 ,

%1 COUPLED SOLUTION ALGORITHM USED.

User information: The modal methods use uncoupled solution algorithms, if possible. The uncoupled
algorithms are considerably more economical than the coupled algorithms. Coupled algorithms are
required when any of thefollowing effects are present: transfer functions, DMIG requests of the p-type, ele-
ment damping, and PARAM,G. Consider the use of modal damping (TABDMP1 entry) to reduce the cost
of your analysis.

5222.1 *** USER WARNING MESSAGE 5222 ,

ERROR: SINGLE FORCING FREQUENCY USED WITH KRYLOV METHOD.
DIRECT METHOD IS USED INSTEAD.

User information: Krylov does not work with single forcing frequency. Direct method is used instead.

5222.2 *** USER INFORMATION MESSAGE 5222,

%1 FAST FREQUENCY RESPONSE SOLUTION ALGORITHM USED FOR %2.

User information: For modal frequency response where the dynamic problem size is Significant, an alter-
nate solution method is employed. These methods are automatically selected based on a set of heuristics.
Fast frequency response options are controlled by PARAM,FASTFR.

5223.0 *** USER WARNING MESSAGE 5221.

Main Index
 478 MSC Nastran Error Messages
Errors 5000 - 5999

GENERATION OF MATRIX DIAGONAL TERM RATIO STATISTICS FOR DECOMPOSITION

OF MATRIX %1 FAILED IN ROUTINE %2. ERROR CODE = %3.

User information:
Error codes and their causes follow.
Code 1 : Compute or use Aii/Lii input control option is not 0 or 1.
Code 7 : Logic error trying to find USET g-set dof in Scalar Index List data.
Code 8 : Insufficient memory.
Code 11 : Data block containing input matrix to decomposition process is not defined.
Code 12 : Data block containing the Aii diagonal terms is missing.
Code 13 : Data block containing the Lii diagonal terms is missing.
Code 21 : All diagonal terms in Aii are null.
Code 22 : All diagonal terms in Lii are null.
Code 30 : No SPARSESOLVER Executive Section statement controls could be found.

5224.0 *** SYSTEM FATAL MESSAGE 5224 (XSEM)

THE LINK SPECIFICATION TABLE HAS DIRECTED EXECUTION TO LINK %1
HOWEVER, THIS LINK DOES NOT CALL MODULE %2

System information: The "new" module has been incorrectly installed in the specified link or the problem
is being run on a mismatched set of LINKS of MSC NASTRAN.
Report the problem to the programmer responsible for the generation of the failing link.

5225.0 *** SYSTEM FATAL MESSAGE 5225 (XSEM)

THIS MODULE %1 CANNOT BE FOUND IN THIS LINK %2 OR ANY OTHER LINK.

5225.1 *** USER FATAL MESSAGE 5225 (SB46RD)

ATTEMPT TO OPERATE ON THE SINGULAR MATRIX IN SUBROUTINE SB46RD.

User information: This message is preceded by the listing of the grid point ID and degrees of freedom for
any null columns.

5225.2 *** USER WARNING MESSAGE 5225.

ATTEMPT TO OPERATE ON THE SINGULAR MATRIX %1 IN SUBROUTINE DCMP.

User information: This message is preceded by the listing of the grid point ID and degrees of freedom for
any null columns.

Main Index
 MSC Nastran Error Messages 479
Errors 5000 - 5999

5226.0 *** USER FATAL MESSAGE 5226 (IFS5P)

ILLEGAL INDEPENDENT DEGREES OF FREEDOM FOR RIGID ELEMENT %1 SORTED
COUNT %2

User information: Rigid elements (excluding the RROD) must have six n-set degrees-of-freedom.

5226.1 *** USER WARNING MESSAGE 5226 (IFS5P)

Alpha(Thermal Expansion Coefficient) in RBE elements will be ignored in current analysis, due to
RIGID=LINEAR defined by user or by default in current solution. To compute thermal expansion effects,
Alpha should be used with RIGID=LAGRAN in SOL101, SOL103, SOL105 and SOL400.

5227.0 *** USER FATAL MESSAGE 5227 (IFS5P)

ILLEGAL DEPENDENT DEGREES OF FREEDOM FOR RIGID ELEMENT %1 SORTED
COUNT %2

User information: The rigid element listed has picked an illegal component for a dependent degree of free-
dom. See chapter 5 of the MSC NASTRAN Quick Reference Guide.

5227.1 *** USER FATAL MESSAGE 5227 (MDG2RG)

ILLEGAL DEPENDENT DEGREES OF FREEDOM,%1, FOUND FOR RIGID ELEMENT, ID=%2.

5228.0 *** USER fatal message (frrd2)

A DYNAMIC AEROELASTIC RESPONSE ANALYSIS IS BEING EXECUTED WITH A NON-
ZERO Q VALUE BUT THE VELOCITY FIELD ON THE AERO BULK DATA ENTRY IS BLANK

User action: SPECIFY A POSITIVE VELOCITY VALUE ON THE AERO BULK DATA ENTRY

5229.0 *** USER WARNING MESSAGE 5229

INPUT FILE TO MODULE %1 PURGED. MODULE RETURNS WITH PURGED OUTPUT.

User information: The matrix to be decomposed is not present. Any module that depends on the output of
this module will also have purged input.

5230.0 *** SYSTEM FATAL MESSAGE 5230,

Main Index
 480 MSC Nastran Error Messages
Errors 5000 - 5999

ELEMENT NUMBER OUTSIDE RANGE OF POSSIBLE NONLINEAR ELEMENTS.

System information: The index passed to the new element type subroutine which unpacks the Block Data
information determined that no data exists.

5231.0 *** SYSTEM FATAL MESSAGE 5231,

INCONSISTENT LENGTH ON NONLINEAR APPENDAGE DETECTED FOR ELEMENT %1

System information: The length encode with the EST file for the length of an element appendage did not
match that decode from the Block Data.

5232.0 *** USER FATAL MESSAGE 5232 (XSBFF)

THE BELOW REPLICATOR ENTRY HAS AN ILLEGAL VALUE. THE VALUE MUST BE AN
INTEGER GREATER THAN 0.
%1

User information: The replicator count on the replicator entry must be an integer, greater than zero.

5236.0 *** USER INFORMATION MESSAGE 5236,

THE FREQUENCY RANGE HAS BEEN SPLIT INTO %1 SUBREGIONS.

User information: The overall frequency range for eigenanalysis is split into several smaller ranges when
using the SINV option to calculate modes and frequencies.

5237.0 *** USER INFORMATION MESSAGE 5237,

THE NEGATIVE FREQUENCY RANGE HAS BEEN SPLIT INTO %1 SUBREGIONS.

User information: The overall frequency range for eigenanalysis has been split into several smaller ranges.
This message occurs only for buckling analysis.

5238.0 *** USER INFORMATION MESSAGE 5238,

NUMBER OF ROOTS IN THE DEFINED FREQUENCY RANGE IS GREATER THAN 600.

User information: More than 600 roots are in the desired frequency range, which is greater than the maxi-
mum allowed using SINV. Decrease the size of the frequency range.

5239.0 *** USER INFORMATION MESSAGE 5239,

Main Index
 MSC Nastran Error Messages 481
Errors 5000 - 5999

BISECTING IN THE %1 - %2 INTERVAL ON LAMBDA.

User information: The frequency subregion encompassing eigenvalues xx-yy is cut in half in order to find
the remaining roots.

5240.0 *** USER INFORMATION MESSAGE 5240,

THE BISECTION VALUE IS : %1 FREQUENCY:%2

User information: The selected value is midway between the lowest and highest frequencies in the fre-
quency subregion.

5241.0 *** USER INFORMATION MESSAGE 5241,

MISSING ROOT(S) IN THE %1 - %2 INTERVAL ON LAMBDA.

User information: The Sturm sequence check has indicated that roots are missing in the frequency range,
and they cannot be found by further bisectioning. If the run terminates with missing roots, decrease the fre-
quency range.

5242.0 *** USER INFORMATION MESSAGE 5242,

THE ROOT FOUND IS NOT THE LOWEST ONE ABOVE FMIN.

User information: The Sturm sequence check indicates that at least one unfounded root exists between
FMIN and the lowest frequency root found. Set FMAX close to the lowest frequency found, so that the
lower roots can be found.

5243.0 *** SYSTEM FATAL MESSAGE 5243 (SEQGP)

NO GRID POINT (GEOM1) OR SCALAR POINT (GEOM2) GEOMETRY DATA AVAILABLE.

System information: Both the GEOM1 (the first input file) for gridpoint geometry and the GEOM2 (the
second input file) for scalar point geometry are either purged or contain no geometry data as input to the
sequencer module SEQP.

5244.0 *** USER WARNING MESSAGE 5244. (GPFDR)

Main Index
 482 MSC Nastran Error Messages
Errors 5000 - 5999

HAS IGNORED DATA FROM THE %1 MATRIX (%2 X %3 )

DUE TO INCOMPATIBILITY WITH THE UGV MATRIX (%4 X %5 )

User information: The UG, PG, QG matrices are processed in synchronization. Incompatible sizes for
these matrices which happens for some solution sequences causes obscure terminations. An incompatible
QG may be caused by grounded CELASi elements in a model with no constraints.
Check whether GPFDR is supported for the solution sequence being used.

5245.0 *** USER INFORMATION MESSAGE 5245 (GPFLNE):

FREQUENCY DEPENDENT ELEMENTS %1 WERE DETECTED BECAUSE OF THE PRES-
ENCE OF %2 BULK ENTRIES.
THEREFORE, ALL %1 ELEMENTS HAVE BEEN EXCLUDED FROM THE ELEMENT ENERGY
CALCULATIONS.

5246.0 *** USER WARNING MESSAGE 5246---,

SUBCASE %1, LOAD CASE %2
ELEMENT TYPE %3, HAS AN IDENTICAL ELEMENT ID %4 IN EACH INPUT FILE.

5247.0 *** SYSTEM WARNING MESSAGE 5247---,

THE NUMBER OF WORDS %1 IN %2 FILE RECORD %3 IS INCORRECT.

System information: Files being read do not agree with expected format. Check that correct files are being
input to MERGEOFP.

5248.0 *** SYSTEM WARNING MESSAGE 5248---,

ELEMENT NAMES NOT FOUND IN ALPHABETICAL SORT WITHIN SUBCASE/LOADCASE
IN%1 DATA BLOCK.

System information: Check that the correct input files are being supplied to MERGEOFP.
This error has also been observed when restart parameters LOOPID and SUBID are not set properly.

5249.0 *** SYSTEM WARNING MESSAGE 5249---,

ELEMENT WITH ELEMENT TYPE %1 NOT FOUND IN TABLE OF ELEMENTS /GPTA1 /.

5250.0 *** USER FATAL MESSAGE 5250,

Main Index
 MSC Nastran Error Messages 483
Errors 5000 - 5999

A negative term in matrix %1 is being raised to an exponent that is not a whole number.

User information: The DIAGONAL module allows raising terms in matrices to non-integer exponents
with the WHOLE option. Whenever the matrix terms are negative, the exponentiation fails if the term is
greater than the 3rd parameter of the DIAGONAL module. The 3rd parameter's default is 0.0.
The PARAMR module performs a similar function with real parameters and the POWER option.
These special applications may be performed by alternate DMAP modules depending upon the exponenti-
ation the user wishes.
This can also be issued if the time increment is too large in transient response-specify a smaller time incre-
ment.

5251.0 *** SYSTEM FATAL MESSAGE 5251 (ADG)

INSUFFICIENT OPEN CORE FOR DOWNWASH MATRIX GENERATION.

5252.0 *** SYSTEM FATAL MESSAGE 5252 (ADG)

INCORRECT FORM OF INPUT DATA BLOCK %1 (FILE %2) FOR DOWNWASH MATRIX
GENERATION IN ADG MODULE.

System information: Check AESURF entries for references to undefined coordinate systems.
Check AELIST entries for references to nonexistent boxes. Also, box identification numbers on the
AELIST entry should be greater than all grid identification numbers.

5253.1 *** SYSTEM FATAL MESSAGE 5253 (ADG)

INCORRECT FORM OF AESTAT ,AESURF, AEROS OR AELIST CARD IN EDT.

System information: Check the aforementioned Bulk Data entries for correctness.

5254.0 *** SYSTEM FATAL MESSAGE 5254 (OPTGPH)

UNABLE TO OPEN GEOM1.

5254.1 *** SYSTEM FATAL MESSAGE 5254 (ADG)

UNABLE TO OPEN THE INPUT DATABLOCK EDT.

5255.0 *** USER FATAL MESSAGE 5255 (ADG)

THE REQUIRED INPUT DATA BLOCK %1 (FILE %2) DOES NOT EXIST (IS PURGED).

Main Index
 484 MSC Nastran Error Messages
Errors 5000 - 5999

5256.0 *** USER FATAL MESSAGE 5256 (ADG)

NO AESTAT ENTRIES WERE FOUND IN THE EDT.

User information: AESTAT ENTRIES ARE REQUIRED TO DEFINE RIGID BODY MOTIONS.

5257.0 *** USER FATAL MESSAGE 5257

DIVERG BULK DATA ENTRY WITH ID %1 DOES NOT EXIST.

5257.1 *** USER FATAL MESSAGE 5257 (ASGPRD)

TRIM BULK DATA ENTRY WITH ID %1 DOES NOT EXIST.

5257.2 *** USER FATAL MESSAGE 5257 (ASGTRD)

Trim set ID %1 is not unique among all TRIM and TRIM2 entries.

5257.3 *** USER FATAL MESSAGE 5257 (AELOOP)

TRIM BULK DATA ENTRY WITH ID %1 DOES NOT EXIST.

5258.0 *** USER WARNING MESSAGE 5258,

UNSUPPORTED NOLINI CARD ENCOUNTERED FOR SET%1 IN NON-LINEAR TRAN-
SIENT.

User information: The Nonlinear Transient Module NLTRD does not support the NFTUBE and
NOLIN5 entries.

5259.0 *** USER FATAL MESSAGE 5259,

UXVEC BULK DATA ENTRY WITH ID %1 INVOKED BY A %2 BULK DATA ENTRY DOES
NOT EXIST

5260.0 *** USER WARNING MESSAGE 5260 (SDP)

DIVISION BY ZERO, USING MACH NUMBER, REFERENCE SPAN, CHORD, OR AREA

User information: The AEROS entry or the TRIM entry includes a zero value for one of the above
parameters.
Check input parameters.

5261.0 *** USER FATAL MESSAGE 5261 (DOPR1C)

Main Index
 MSC Nastran Error Messages 485
Errors 5000 - 5999

DVPREL1 ID %1 WITH GPLY ID %2 references a PCOMPG %3 with the MICRO option.

User Information: This is not supported in SOL 200.

User action: Provide equivalent PCOMPG without the MICRO option.

5262.0 *** USER FATAL MESSAGE (DOPR1b)

THE INITIAL COMPUTED VALUE FOR DEPENDENT DESIGN VARIABLE NO. %1 IS %2
WHICH IS OUTSIDE THE BOUNDS SPECIFIED ON THE DESVAR ENTRY OF
%3 < %2 < %4

User action: CORRECT THE DESIGN MODEL SO THAT THE BOUNDS

SPECIFIED ON THE DEPENDENT DESIGN VARIABLE BRACKET THE
COMPUTED INITIAL VALUE

5263.0 *** USER FATAL MESSAGE 5263 (CLUXVD)

INTERCPT = 1.0 MUST APPEAR FOR ONE OF THE AERODYNAMIC STATES

User information: TYPICALLY, THIS ERROR OCCURS WHEN EXTERNAL AERODYNAMICS

ARE BEING INPUT AND ALL THE UXVEC INPUTS HAVE INTERCPT=0.0

5263.1 *** USER FATAL MESSAGE 5263 (CLUXVD)

A UXVEC ENTRY CONTAINS A LABEL = INTERCPT WITH A VALUE OF %1

User information: ONLY VALUES OF 0.0 OR 1.0 ARE VALID FOR INTERCPT

5264.0 *** USER FATAL MESSAGE 5264 (ASGLAB)

%1 BULK DATA ENTRY REFERENCES LABEL %2 WHICH IS UNDEFINED ON AN AESTAT,
AESURF OR AEPARM ENTRY.

5264.1 *** USER FATAL MESSAGE 5264 (UXVGEN)

UXVEC BULK DATA ENTRY REFERENCES LABEL %1 WHICH IS UNDEFINED ON AN AES-
TAT, AESURF OR AEPARM ENTRY.

5264.2 *** USER FATAL MESSAGE 5264 (DOPR1IC)

Main Index
 486 MSC Nastran Error Messages
Errors 5000 - 5999

A DVPSURF BULK DATA ENTRY REFERENCES LABEL %1 WHICH IS UNDEFINED ON TRIM

ENTRY %2.

5264.3 *** USER FATAL MESSAGE 5264 (UXVGEN)

UXVEC ID %1 REFERENCES LABEL %2 WITH A UXI VALUE OF %3.
%2 IS AN AESTAT THAT CAN ONLY BE USED ON A UXVEC ENTRY WHEN THE UXI VALUE
IS 1.0

User information: WHEN THE UXI IS 1.0, THE USER SUPPLIED AERODYNAMICS ARE ADDED
TO THE AERODYNAMICS GENERATED BY THE INTERNAL AERODYNAMICS FROM AES-
TAT/CAERO1/CAERO2 INPUTS.
AN APPLICATION WOULD BE TO ADD AERODYNAMICS FOR A FUSELAGE THAT HAVE
NOT BEEN INCLUDED IN THE INTERNAL MODEL.

5265.0 *** USER FATAL MESSAGE 5265 (ASG)

TOO LITTLE DATA ON TRIM OR AELINK BULK DATA ENTRIES.

5266.0 *** USER FATAL MESSAGE 5266 (ASGPRD)

TOO MUCH DATA ON TRIM OR AELINK BULK DATA ENTRIES.

5267.0 *** USER FATAL MESSAGE 5267 (ASGLD)

ZXX MATRIX IS SINGULAR. TRIM AND AELINK ENTRIES SPECIFY AN INADEQUATE CON-
STRAINT SET.

5268.0 *** USER FATAL MESSAGE (AELOOP)

A STATIC AEROELASTIC ANALYSIS IS BEING PERFORMED BUT THERE IS NO TRIM OR
DIVERG COMMAND IN ANY OF THE SUBCASES.

User avoidance: INSERT A TRIM OR DIVERG COMMAND IN EACH SUBCASE REQUESTING A

STATIC AEROELASTIC ANALYSIS.

5269.0 *** USER WARNING MESSAGE 5269 (ASDR)

REQUESTED ASDR OUTPUT SET%1 IS NOT PRESENT

User information: The output set identified on the APRES or AEROF entry is not present.
Modify the ID requested on the AEROF or APRES entry, or supply an output set with an ID matching the
on the AEROF or APRES entry.

Main Index
 MSC Nastran Error Messages 487
Errors 5000 - 5999

5269.1 *** USER WARNING MESSAGE 5269 (ASDR)

REQUESTED ASDR OUTPUT APRESS IS NOT PRESENT.

User information: THE OUTPUT INVOKED BY THE APRES CASE CONTROL COMMAND IS
NOT PRESENT.
IT IS LIKELY THIS IS A NON-STANDARD AERO MODEL THAT DOES NOT INCLUDE AERO-
DYNAMIC PRESSURES.

5269.2 *** USER WARNING MESSAGE 5269 (ASDR)

REQUESTED ASDR OUTPUT APRESS IS NOT SUPPORTED

User information: OUTPUT OF AERODYNAMIC PRESSURES IS NOT SUPPORTED FOR NON

DLM MODELS.

5270.0 *** USER FATAL MESSAGE 5270 (ETETD)

ZERO ELEMENT VOLUME DETECTED FOR ELEMENT WITH ID = %1

User information: This message occurs when a zero volume is calculated for the TETRA element using the
four corner points. Probably the TETRA has all four points lying on a plane.
Geometry must be corrected.

5271.0 *** USER FATAL MESSAGE 5271 (ETETD)

FOR TETRA ELEMENT ID = %1, THE RATIO OF LONGEST EDGE TO SHORTEST ALTITUDE
EXCEEDS %2

User action: THE TOLERANCE MAY BE ADJUSTED WITH TETRAAR KEYWORD ON THE
NASTRAN STATEMENT.

User information: This occurs as a warning when there is a folded or shallow CTETRA element. Results
are suspect because the aspect ratio is not favorable.
If region being modeled is important, remeshing may be needed.

5272.0 *** USER FATAL MESSAGE 5272

Main Index
 488 MSC Nastran Error Messages
Errors 5000 - 5999

PLASTICITY MODULUS MUST BE LESS THAN THE ELASTICITY MODULUS FOR TABLE ID
%1.

User information: Ensure that the slope of the stress-strain curve in the plastic region does not exceed the
elasticity modulus.
Check the stress strain curve for the specific Table-ID.

5274.0 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF EIGENVECTOR GENERATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

5274.1 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF EIGENVALUE ITERATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

5274.2 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF PARALLEL MHOUSEHOLDER TRIDIAGONALIZATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

5274.3 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF MHOUSEHOLDER TRIDIAGONALIZATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

5274.4 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF PARALLEL HOUSEHOLDER TRIDIAGONALIZATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

Main Index
 MSC Nastran Error Messages 489
Errors 5000 - 5999

5274.5 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF HOUSEHOLDER TRIDIAGONALIZATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

5274.6 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF MGIVENS TRIDIAGONALIZATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

5274.7 *** USER INFORMATION MESSAGE 5274,

THE ACTUAL TIME OF GIVENS TRIDIAGONALIZATION IS:%1

User information: The time spent in the major operations of the real eigensolution module are output.
Note that the number of eigenvectors requested has a large effect on solution cost.

5274.8 *** USER INFORMATION MESSAGE 5274.

SPILL OCCURRED FOR THIS PROBLEM AT COLUMN NUMBER :%1 .

5274.9 *** USER INFORMATION MESSAGE 5274.

%1. SWITCHING METHODS.

5275.0 *** SYSTEM WARNING MESSAGE 5275---

***** MRGOFP NEEDS MAXTYP INCREASED ABOVE%1 *****

5276.0 *** USER WARNING MESSAGE 5276 (EQD8D)

ELEMENT %1 HAS TOO MUCH CURVATURE AND MAY YIELD POOR ANSWERS.

User information: The element listed has an angle greater than 30 degrees between normals to some corner
grid points. This can lead to excessively low stiffness.
Use a finer mesh size to reduce the angles between the normals.

5278.0 ***USER FATAL MESSAGE 5278,

Main Index
 490 MSC Nastran Error Messages
Errors 5000 - 5999

INPUT FILE,%1 NOT PROPER OR TAPE BIT NOT SET. FBS CHKPT OPTION CANNOT EXE-
CUTE.

5279.0 ***USER INFORMATION MESSAGE 5279,

FBS RESTARTED AT COLUMN NUMBER %1

5280.0 *** USER INFORMATION MESSAGE 5280,

FBS CHECKPOINT ON %1,PASS %2 COMPLETE, LAST COL NBR =%3

5281.0 *** USER WARNING MESSAGE 5281 (FA1PKE)

THE PK METHOD OF FLUTTER ANALYSIS HAS FOUND REDUCED FREQUENCY VALUES
OUTSIDE THE RANGE OF REDUCED FREQUENCIES USED FOR INTERPOLATION.

User information: The MKAEROi entry has reduced frequency values specified for interpolation.
If complex eigenvalues are found that have an associated reduced frequency outside the range on the
MKAEROi entries then convergence may not be obtained. If it fails to converge and the k is outside the
range the remaining eigenvalue will be skipped. Increase the range of reduced frequency on the MKAEROi
entries.

5282.0 *** USER information message (faipkv/dsfltv)

SYSTEM(108) HAS A NONZERO VALUE, IMPLYING THERE IS A PREFERENCE TO USE THE
UPPER HESSENBERG METHOD FOR FLUTTER ANALYSIS.

User information: THIS IS NO LONGER SUPPORTED AND THE DEFAULT QZ ALGORITHM

WILL BE USED INSTEAD.

5288.0 *** USER FATAL MESSAGE 5288,

NO ROOT EXISTS ABOVE FMIN.

User information: This message occurs when the eigenproblem of finding any number of roots above
FMIN is expected, but the Sturm number indicates that there is no root above FMIN. Reduce FMIN in
order to attempt to find
a root.

5289.0 *** USER FATAL MESSAGE 5289

Main Index
 MSC Nastran Error Messages 491
Errors 5000 - 5999

DEPENDENT DEGREE-OF-FREEDOM GRID ID =%1 AND COMPONENT =%2 APPEARS ON

MORE THAN ONE MPC OR RIGID ELEMENT ENTRY.

User information: An MPC entry or rigid element entry lists the same dependent grid point more than
once.

5289.1 *** USER FATAL MESSAGE 5289 (WRGMTD)

AN MPC OR RIGID ELEMENT BULK DATA ENTRY WITH DEPENDENT DEGREE-OF-FREE-
DOM GRID ID =%1 AND COMPONENT =%2 CONTAINS AN INDEPENDENT DEGREE-OF-
FREEDOM --GRID ID =%3 AND COMPONENT =%4-- THAT IS SPECIFIED MORE THAN
ONCE.

User information: No DEGREE-OF-FREEDOM may be specified more than once on the same entry.
List each independent grid point once per entry.

5289.2 *** USER FATAL MESSAGE 5289 (WRGMTD)

AN MPC OR RIGID ELEMENT BULK DATA ENTRY WITH DEPENDENT DEGREE-OF-FREE-
DOM GRID ID =%1 AND COMPONENT =%2 IS ALSO SPECIFIED AS AN INDEPENDENT
DEGREE-OF-FREEDOM.

User information: No DEGREE-OF-FREEDOM may be specified more than once on the same entry.

5289.3 *** USER FATAL MESSAGE 5289

GRID ID =%1 AND COMPONENT =%2 APPEARS MORE THAN ONCE IN AN EQUATION
GENERATED BY MPC OR RIGID ELEMENT ENTRY.

User information: No DEGREE-OF-FREEDOM may be specified more than once on the same entry. List
each independent DEGREE-OF-FREEDOM only once per entry making sure to not duplicate the depen-
dent grid point.

5290.0 *** USER FATAL MESSAGE 5290 (GPSP)

Main Index
 492 MSC Nastran Error Messages
Errors 5000 - 5999

EXTERNAL ID =%1 DOF =%2 IS IN THE Q-SET, BUT HAS A STIFFNESS TERM BEFORE
REDUCTION.

User action: THE DOFS SPECIFIED FORM MEMBERS OF THE MUTUALLY EXCLUSIVE Q
SET. ENSURE THAT THEY ARE NOT ALSO DEFINED AS MEMBERS OF OTHER MUTUALLY
EXCLUSIVE SETS.

User information: The q-set is reserved for generalized coordinates. In superelement analysis, each
superelement must have a unique set of variables specified for its q-set. Remove any elements connected to
q-set points and provide a unique set of degrees of freedom for each superelement that has generalized coor-
dinates. See also the description of parameter ERROR in Section 6 of the MSC NASTRAN Quick Refer-
ence Guide.

5291.0 *** USER WARNING MESSAGE 5291 (GPSP)

EXTERNAL ID %1, REFERENCED ON AN SPCOFFI ENTRY, DOES NOT EXIST.

5293.1 *** USER INFORMATION MESSAGE 5293

FOR DATA BLOCK %1
LOAD SEQ. NO. EPSILON EXTERNAL WORK EPSILONS LARGER THAN %2 ARE FLAGGED
WITH ASTERISKS

User information: One line of output is printed for each static loading condition. Small values of EPSI-
LON are due to accumulated round-off error. Large values of EPSILON indicate possible singularities in
the stiffness matrix. See Section 9.5.1.

5293.3 *** USER INFORMATION MESSAGE 5293 (SSM10D)

ERROR RATIO FOR LARGEST EPSILON VALUE IN FIRST TEN SOLUTIONS:
LOAD SEQ. NO. EPSILON EXTERNAL WORK EPSILONS LARGER THAN %1 ARE FLAGGED
WITH ASTERISKS

5293.4 *** USER INFORMATION MESSAGE 5293 (SSM10D)

LOAD SEQ. NO. EPSILON EXTERNAL WORK EPSILONS LARGER THAN %1 ARE FLAGGED
WITH ASTERISKS

User information: One line of output is printed for each static loading condition. Small values of EPSI-
LON are due to accumulated round-off error. Large values of EPSILON indicate possible singularities in
the stiffness matrix. See Section 9.5.1.

Main Index
 MSC Nastran Error Messages 493
Errors 5000 - 5999

5293.5 *** USER INFORMATION MESSAGE 5293 (SSM10D)

ERROR RATIO(S) FOR FIRST %1 SOLUTIONS:
LOAD SEQ. NO. EPSILON EXTERNAL WORK EPSILONS LARGER THAN %2 ARE FLAGGED
WITH ASTERISKS

5293.11 *** USER INFORMATION MESSAGE 5293

FOR DATA BLOCK %1
LOAD SEQ. NO. EPSILON EXTERNAL WORK

User information: One line of output is printed for each static loading condition. Small values of EPSI-
LON are due to accumulated round-off error. Large values of EPSILON indicate possible singularities in
the stiffness matrix. See Section 9.5.1.

5293.13 *** USER INFORMATION MESSAGE 5293

FOR DATA BLOCK %1
LOAD SEQ. NO. EPSILON EXTERNAL WORK

User information: One line of output is printed for each static loading condition. Small values of EPSI-
LON are due to accumulated round-off error. Large values of EPSILON indicate possible singularities in
the stiffness matrix. See Section 9.5.1.

5298.1 *** USER WARNING MESSAGE 5298 (EDTL)

UNDEFINED THERMAL OR DEFORM LOAD SET %1

5298.2 *** USER FATAL MESSAGE 5298,

ILLEGAL KSYM OPTION ENCOUNTERED IN MODULE %1.

5299.0 *** SYSTEM FATAL MESSAGE 5299.

I/O ERROR WHEN WRITING FINAL STARTING BLOCK

5299.1 *** SYSTEM FATAL MESSAGE 5299.

UNRECOVERABLE TERMINATION FROM LANCZOS ITERATION
INTERNAL ERROR CODE = %1 USER ERROR RETURN = %2

5299.2 *** SYSTEM FATAL MESSAGE 5299.

Main Index
 494 MSC Nastran Error Messages
Errors 5000 - 5999

IMPROPER PARAMETER SPECIFICATION FOR LANCZOS

5299.3 *** SYSTEM FATAL MESSAGE 5299.

TRUST REGION OVERFLOW IN BLOCK SHIFTED LANCZOS.

5299.4 *** SYSTEM FATAL MESSAGE 5299.

RESTORATION OF FACTORIZATION ERROR

5299.5 *** SYSTEM FATAL MESSAGE 5299.

FACTORIZATION ERROR ON THREE CONSECUTIVE SHIFTS

5299.6 *** SYSTEM FATAL MESSAGE 5299.

INSUFFICIENT STORAGE FOR BLOCK SHIFTED LANCZOS.
WORKSPACE AVAILABLE = %1 WORKSPACE REQUIRED = %2

5299.7 *** SYSTEM FATAL MESSAGE 5299.

STARTING BLOCK COMPUTATION ERROR

5299.8 *** SYSTEM FATAL MESSAGE 5299.

FACTORIZATION ERROR AT A BOUNDARY SHIFT.
POTENTIAL FIXES:
IF LOWER BOUND IS ZERO USE A SMALL NEGATIVE VALUE.
IF LOWER BOUND IS A SMALL NEGATIVE VALUE DECREASE IT.
ELIMINATE MASSLESS MECHANISMS THE MODEL MAY CONTAIN.

5299.9 *** SYSTEM FATAL MESSAGE 5299 (LANCZ).

INSUFFICIENT STORAGE FOR BLOCK SHIFTED LANCZOS.
WORKSPACE AVAILABLE = %1 WORKSPACE REQUIRED = %2

5400.0 *** USER FATAL MESSAGE 5400 (REIGL)

INCORRECT RELATIONSHIP BETWEEN FREQUENCY LIMITS.

5401.0 *** SYSTEM FATAL MESSAGE 5401 (REIGL)

Main Index
 MSC Nastran Error Messages 495
Errors 5000 - 5999

LANCZOS METHOD IS UNABLE TO FIND ALL EIGENVALUES IN RANGE.

ACCEPTED EIGENVALUES AND ADDITIONAL ERROR MESSAGES MAY BE LISTED ABOVE.
A POSSIBLE CAUSE IS THE OCCURENCE OF HIGH MAXRATIOS ABOVE.

User action: RERUN WITH ANOTHER METHOD OR ANOTHER SETTING ON EIGRL ENTRY
OR CHECK MODEL FOR MECHANISMS IF HIGH MAXRATIOS EXIST.

System information: This message can be issued if insufficient memory is available for Lanczos with sparse
decomposition. It can also be issued if UFM 5299 occurs. See the MSC NASTRAN Numerical Methods
User's Guide. This condition can be related to the occurrence of UWM 5411.

5401.1 *** SYSTEM WARNING MESSAGE 5401 (LANCZ).

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 DIFFERENT SETTINGS FOR F1, F2,
AND/OR NDES.

System information: This message can be issued if insufficient memory is available for Lanczos with sparse
decomposition. It can also be issued if UFM 5299 occurs. See the MSC NASTRAN Numerical Methods
User's Guide. This condition can be related to the occurrence of UWM 5411.

5402.0 ***USER WARNING MESSAGE 5402----

THE PROBLEM HAS AN EMPTY STIFFNESS MATRIX.

User information: The problem requires a stiffness matrix. Verify that property entries are specified cor-
rectly.

5403.0 *** USER INFORMATION MESSAGE 5403,

CPU TIME AT START OF LANCZOS ITERATION%1

User information: Since several Lanczos iterations may be executed during one application of the Lanczos
method (each shift is followed by at least one iteration), this information is given to measure the time
required for the individual iterations.

5403.1 *** USER INFORMATION MESSAGE 5403 (LNNRIGL)

Main Index
 496 MSC Nastran Error Messages
Errors 5000 - 5999

BREAKDOWN OF CPU USAGE DURING LANCZOS ITERATIONS:

OPERATION REPETITIONS TIMES (SEC): MAXIMUM MINIMUM AVERAGE TOTAL
FBS (BLOCK SIZE=%1) %2 %3 %4 %5 %6
MATRIX-VECTOR MULTIPLY %7 %8 %9 %10 %11
SHIFT AND FACTOR %12 %13 %14 %15 %16
LANCZOS RUN %17 %18 %19 %20 %21

5403.2 *** USER INFORMATION MESSAGE 5403 (CLASDD)

BREAKDOWN OF CPU USAGE DURING COMPLEX LANCZOS ITERATIONS:
OPERATION REPETITIONS TIMES (SEC): AVERAGE TOTAL
SHIFT AND FACTOR %1 %2 %3
MATRIX-VECTOR MULTIPLY & FBS %4 %5 %6
REORTHOGONALIZATION %7 %8 %9
SOLVE BLOCK TRIDIAGONAL PROBLEM %10 %11 %12
EIGENVECTORS AND RESIDUALS %13 %14 %15

5404.0 *** USER WARNING MESSAGE 5404,

NEGATIVE MODAL MASS TERM IS ENCOUNTERED DURING INVERSE ITERATION PRO-
CESS ABORTED.

User information: The modal mass matrix should have unit diagonal terms (for mass normalization). Neg-
ative terms may indicate negative eigenvalues. If these negative terms are computational zeroes (rigid-body
modes, for example), then the negative terms are acceptable. If the negative terms are finite values, there
may be a modeling problem.

5405.0

Main Index
 MSC Nastran Error Messages 497
Errors 5000 - 5999

Termination message: ERROR %1 OCCURRED DURING ITERATION.

User information: This message marks the breakdown of the inverse iteration process.
See the MSC NASTRAN Numerical Methods User's Guide for additional
values and actions.
Y Value User Action
-11 File open error in interface; This error should not occur;
see GINO error message. report error to Hexagon.
-12 File open error in post pro- This error should not occur;
processing; see GINO error report error to Hexagon.
message.
-13 File read error; see GINO This error should not occur;
error message. report error to Hexagon.
-21 Insufficient space for block- Increase memory
size = 1.
-22 Three consecutive factorizations Possible ill-conditioning;
failed at a shift. check model.
-23 Lanczos internal table overflow Specify smaller internal;
due to enormous number of shifts. may be necessary to have
several runs.
-31 Internal error in Lanczos (REIGL) This error should not occur;
module. report error to Hexagon.
-32 No convergence in solving the Possible ill-conditioning;
tridiagonal problem. check model.
-33 Too many eigenvalues found; Check the orthogonality of the
inconsistency between roots eigenvectors; if it is good,
found and sturm number. then ignoring this warning.

5406.0 *** USER WARNING MESSAGE 5406 (LNCR8D)

NO CONVERGENCE IN SOLVING THE TRIDIAGONAL PROBLEM.

User information: This message signals eigensolution problems in the Lanczos method. There is possible
ill-conditioning; check your model.

5406.1 *** SYSTEM FATAL MESSAGE 5406 (LNNHERR)

Main Index
 498 MSC Nastran Error Messages
Errors 5000 - 5999

INTERNAL FAILURE IN THE LANCZOS PROCEDURE:

TRIDIAGONAL QL PROCEDURE FAILED TO CONVERGE.

User action: CONTACT MSC CLIENT SUPPORT.

5407.0 *** SYSTEM FATAL MESSAGE 5407 (LNCS1D)

INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES
ACTUALLY COMPUTED IN A (PARTIAL) INTERVAL

User action: THE FOLLOWING CHANGES TO THE EIGRL CARD MAY HELP TO SOLVE THIS
PROBLEM
1. INCREASE MAXSET.
2. IF F1 IS GIVEN AS ZERO, LEAVE IT BLANK.
3. IF F1 AND F2 ARE BOTH GIVEN, LEAVE F2 BLANK AND SPECIFY A VALUE FOR ND.

5407.1 *** SYSTEM WARNING MESSAGE 5407 (LNCCKD)

INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES
ACTUALLY COMPUTED IN A (PARTIAL) INTERVAL

System information: This message shows a serious problem. Spurious modes were found in the Lanczos
method. Check the multiplicity of the roots given in the interval. See the MSC NASTRAN Numerical
Methods User's Guide.

5407.2 *** SYSTEM WARNING MESSAGE 5407 (MDACMS)

INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES
ACTUALLY COMPUTED IN A (PARTIAL) INTERVAL DURING THE DMP ACMS SYSTEM
SOLUTION.

User actions:
1. Rerun with different number of DMP processes.
2. Change EIGRL F2 (F-max) by a small amount.

5408.0 *** SYSTEM WARNING MESSAGE 5408.

FACTORIZATION FAILED. SHIFT CHANGED TO %1

System information: No user action to be taken. This message occurs only for the Lanczos method.

Main Index
 MSC Nastran Error Messages 499
Errors 5000 - 5999

5409.0 *** USER INFORMATION MESSAGE 5409 (NL2CON)

*** INTERNAL DEGREES OF FREEDOM FOR %1 ELEMENT(S) FAILED TO CONVERGE

User information: Reduce the load increment.

5410.0 *** USER FATAL MESSAGE 5410 (IFP7)

PBCOMP AND PBEAM IDENTIFICATION %1 WAS DUPLICATED

User information: Property identification numbers for the PBCOMP and PBEAM entries must be unique.
Check bulk data and ensure that PIDS for PBCOMP and PBEAM entries are not duplicated.

5410.1 *** USER FATAL MESSAGE 5410

DUPLICATE PROPERTY ID NUMBERS = %1 FOR PSOLID AND PLSOLID OR PSHELL AND
PLPLANE ARE NOT PERMITTED.

5410.2 *** USER FATAL MESSAGE 5410

Duplicate property ID numbers = %1 for PSHELL, PLPLANE and PLCOMP are not permitted.

5410.3 *** USER FATAL MESSAGE 5410

Duplicate property ID Numbers = %1 for PSOLID, PLSOLID and PCOMPLS are not permitted.

5410.4 *** USER FATAL MESSAGE 5410

Duplicate entity ID Numbers = %1 for GMBNDC BID=%2 are not permitted.

5410.5 *** USER FATAL MESSAGE 5410

Duplicate ID numbers = %1 for %2 and %3 are not permitted.

5411.0 *** USER WARNING MESSAGE 5411

Main Index
 500 MSC Nastran Error Messages
Errors 5000 - 5999

NEGATIVE TERM ON DIAGONAL OF MASS(VIBRATION) OR STIFFNESS(BUCKLING)

MATRIX DETECTED.
ROW NUMBER = %1 VALUE = %2

User information: The message is given from the REIGL module which performs a necessary (but not suf-
ficient) check on the positive semi-definiteness of the indicated matrix. Look for evidence of negative mass,
such as minus signs on input. Negative terms on the factor of the indicated matrix
must be removed for correct answers.
Something has caused a negative term on the diagonal of the mass or stiffness matrix. Look for explicitly
defined negative mass and/or stiffness terms. Also, check the continuation entries on the PBEAM entry. An
incorrect entry for the SO field may lead to improper mass definition. For example, if SO is set to NO at a
particular X/XB location, the continuation entry for defining four stress locations on the cross section (C,
D, E, F) is not used. If SO is NO but the C, D, E, and F points are entered in error, negative mass terms
can result if either E1 or E2 entries are entered. The offending DOF can be traced using the USET tables.
The Lanczos method gives wrong answers for indefinite matrices. The existence of negative diagonal terms
indicates a subclass of indefinite matrix.
See the MSC NASTRAN Numerical Methods User's Guide for more information.

5412.0 *** USER FATAL MESSAGE 5412

IMPLAUSIBLE NONLINEAR ELASTIC MATERIAL USED
STRESS = %1 STRAIN = %2 STRESS = %3 STRAIN = %4

User information: If the product of the stress and the strain is negative, this fatal message will result.

5413.0 *** USER FATAL MESSAGE 5413 (IFP7)

PRODUCT OF MOMENTS OF INERTIA I1 AND I2 SHOULD EXCEED THE SQUARE OF I12
FOR PBCOMP ENTRY WITH PID %1

User information: This limitation is consistent with the existing beam. If the condition is not enforced the
stiffness matrix for the generated beam element will be ill-defined.
Check values of l1, l2, and l12 on the PBCOMP entry.

5414.0 *** SYSTEM FATAL MESSAGE 5414 (IFP9)

ABNORMAL END OF PBEAML RECORD ENCOUNTERED ON DATA BLOCK %1

5414.1 *** SYSTEM FATAL MESSAGE 5414 (IFP9)

Main Index
 MSC Nastran Error Messages 501
Errors 5000 - 5999

ABNORMAL END OF PBARL RECORD ENCOUNTERED ON DATA BLOCK %1

System information: End of record encountered where there should not be any. Could be hardware or
computer system problem. Print the data block to see if it is plausible.
If no hardware error suspected, send run to Hexagon.

5414.2 *** USER INFORMATION MESSAGE 5414 (IFP7)

NO ELEMENTS REFERENCE PBCOMP BULK DATA ENTRIES.

5415.0 *** SYSTEM FATAL MESSAGE 5415 (IFP7)

ABNORMAL END OF PBCOMP RECORD ENCOUNTERED ON DATA BLOCK %1

5416.0 *** USER FATAL MESSAGE 5416 (EQDRD)

CONGRUENCY IS NOT PERMITTED FOR NONLINEAR ANALYSIS. CHECK QUADR ELE-
MENT WITH ID=%1

5416.1 *** USER FATAL MESSAGE 5416. (EQD4D)

CONGRUENCY IS NOT PERMITTED FOR NONLINEAR ANALYSIS. CHECK QUAD4 ELE-
MENT WITH ID =%1

5417.1 *** USER FATAL MESSAGE 5417 (EQDRD)

THICKNESS SPECIFIED FOR QUADR ELEMENT WITH ID=%1 RESULTS IN COMPUTED
ZEROS.

User information: Moment of inertia is a function of thickness cubed. If thickness specified is too small,
moment of interior terms are computed to be zeros. This error is computer dependent because computed
zeros are a function
of machine precision. Increase the thickness.

5417.2 *** USER FATAL MESSAGE 5417. (EQD4D)

THICKNESS SPECIFIED FOR QUAD4 ELEMENT WITH ID=%1RESULTS IN COMPUTED
ZEROS.

5418.0 *** USER FATAL MESSAGE 5418 (IFS4P)

Main Index
 502 MSC Nastran Error Messages
Errors 5000 - 5999

ILLEGAL DUPLICATION ON RANDPS ENTRIES.

User information: This message is issued if J, K, and X are all duplicated on the next RANDPS entry.
This can also occur if there are additional RANDPS entries in the Bulk Data that are not referenced in Case
Control. Remove the extra RANDPS entries from the Bulk Data.

5419.0 *** USER FATAL MESSAGE 5419 (TA1C)

GENEL CARD %1 CONTAINS DUPLICATE GRID AND COMPONENT ID NUMBERS

5419.1 *** USER FATAL MESSAGE 5419 (GP2)

GENEL CARD ID=%1 MISSING DATA

5419.2 *** USER FATAL MESSAGE 5419 (MODGM2)

STRUCTURAL ELEMENT %1, ID = %2, REFERENCES FLUID GRID POINT ID = %3

5419.3 *** USER FATAL MESSAGE 5419 (MODGM2)

FLUID ELEMENT %1, ID = %2, REFERENCES STRUCTURAL GRID POINT ID = %3

User action:
1. MODIFY THE ELEMENT TYPES USED TO SIMULATE THE INTERACTION.
2. PROBLEMATIC REGIONS CAN BE IDENTIFIED BY USING THE ELEMENT IDS
MENTIONED ABOVE.
3. CHECK TO SEE THAT FLUID ELEMENT IS ONLY CONNECTED TO FLUID GRIDS;
IDENTIFIED BY A -1 IN THE CD FIELD OF THE GRID ENTRY.

User information: This element type may only connect to grid points that specify -1 for an output coordi-
nate system ID.
The element type mentioned is associated with a corresponding CHEXA, CPENTA or CTETRA element
type.

5419.4 *** USER FATAL MESSAGE 5419 (CHKRGD)

%1 ELEMENT ID = %2, REFERENCES FLUID GRID POINT ID = %3.

User action: Replace the rigid element Bulk Data entry with one or more MPC entries.

5419.5 *** USER FATAL MESSAGE 5419 (GP2)

Main Index
 MSC Nastran Error Messages 503
Errors 5000 - 5999

%1 with id %2 refers to scalar point %3, but the corresponding component is %4, not 0, 1 nor blank.
The component number must be 0, 1 or blank.

User action: Review and modify the input file.

5420.0 *** SYSTEM WARNING MESSAGE 5420 (SEP2)

SUPERELEMENT %1 HAS NO EXTERIOR POINTS.

5421.0 *** USER FATAL MESSAGE 5421

THE VALUES FOR M2GG, B2GG, K2GG, P2G, K42GG, AND A2GG MUST BE REAL

User information: When K2GG, B2GG, M2GG, or P2G is used, no complex DMIG entries may exist in
the Bulk Data, even if they are not used. The only avoidance is to enter the complex matrix as two real
matrices, one containing the real terms and the other containing the imaginary terms, and then adding
them via DMAP.

5422.0 *** USER WARNING MESSAGE 5422 .

PLATE ELEMENTS WITH ALL MIDSIDE NODES DELETED GIVE POOR RESULTS.

5423.0 *** USER/SYSTEM FATAL MESSAGE 5423

ATTEMPT TO %1 INCOMPATIBLE MATRICES
FILE# COLS ROWS FORM TYPE NZWD DENS

5423.1 *** USER/SYSTEM FATAL/WARNING MESSAGE 5423

ATTEMPT TO %1 INCOMPATIBLE MATRICES
ID COLS ROWS FORM TYPE NZWD DENS

5423.2 *** USER/SYSTEM FATAL MESSAGE 5423

ATTEMPT TO %1 INCOMPATIBLE MATRICES
FILE# COLS ROWS FORM TYPE NZWD DENS T

5423.7 *** SYSTEM FATAL MESSAGE 5423 (SDR4BA)

Main Index
 504 MSC Nastran Error Messages
Errors 5000 - 5999

ATTEMPT TO MERGE INCOMPATIBLE MATRICES

ID COLS ROWS FORM TYPE NZWD DENS
TRAILER FOR %1 IS%2
TRAILER FOR %3 IS%4
TRAILER FOR %5 IS%6
TRAILER FOR %7 IS%8

5423.8 *** SYSTEM FATAL MESSAGE 5423 (UNPACKCB)

Matrix unpack routines cannot retrieve terms from the factor matrix %1 on file %2

5424.0 *** USER FATAL MESSAGE 5424. (GP3C)

PLOADX1 LOAD SET %1 REFERENCES ELEMENT %2
WHICH WAS NOT FOUND AMONG THE TRIAX6, TRIAX OR QUADX ELEMENTS

5425.0 *** USER FATAL MESSAGE 5425. (GP3C)

PLOADX1 LOAD SET =%1. TRIAXFD ELEMENT%2
DOES NOT CONTAIN GRID%3 AS A CORNER GRID

5425.1 *** USER FATAL MESSAGE 5425. (GP3C)

PLOADX1 LOAD SET =%1. TRIAX6 ELEMENT%2
DOES NOT CONTAIN GRID%3 AS A CORNER GRID

5425.2 *** USER FATAL MESSAGE 5425. (GP3C)

PLOADX1 LOAD SET =%1. QUADXFD ELEMENT%2
DOES NOT CONTAIN GRID%3 AS A CORNER GRID

5426.0 *** USER WARNING MESSAGE 5426,

DEFORM BULK DATA CARDS REFERENCED BY DEFORM CASE CONTROL COMMAND
ARE NOT DEFINED.
THE REQUEST FOR STRESSES AND/OR FORCES IS IGNORED.

5427.0 *** USER INFORMATION MESSAGE 5427 --

ENTERING LINK 16 DUMMY MODULE #1 ***

5428.0 *** USER INFORMATION MESSAGE 5428 --

ENTERING LINK 16 DUMMY MODULE #2 ***

Main Index
 MSC Nastran Error Messages 505
Errors 5000 - 5999

5429.0 *** USER FATAL MESSAGE 5429 (REIGL)

INSUFFICIENT TIME TO FINISH LANCZOS ITERATION.
ESTIMATED TIME TO COMPLETE LANCZOS RUN IS %1 SECOND(S).

User information: There is not enough time remaining to complete the analysis based on an estimate of
how long the Lanczos iteration will take. Increase the value on the TIME statement in the Executive Con-
trol Section and rerun. In order to ensure that the run can be competed, overestimate the TIME value and
do not rely on estimates or on actual times from a similar model.

5430.0 *** USER FATAL MESSAGE 5430 (APD2)

CAERO2 ENTRY ID = %1 THAT REFERENCES THE PAERO2 ENTRY ID = %2,
HAS EITHER AN INCONSISTENT USE FOR THIi OR THNi OR,
THE LTH2 FIELD IS REQUIRED.

5431.0 *** USER FATAL MESSAGE 5431 (APD2)

THI1 AND THN1 REQUIRED FOR CAERO2 %1

5432.0 *** USER FATAL MESSAGE 5432 (APD2)

CAERO2 BODY ENTRY ID = %1 THAT REFERENCES THE PAERO2 ENTRY ID = %2,
THAT REFERENCES THE AEFACT ENTRY ID = %3, DOES NOT HAVE ENOUGH SLENDER
ELEMENTS.

User information: AT LEAST 2 SLENDER ELEMENTS ARE REQUIRED.

5438.0 *** USER FATAL MESSAGE 5438 ***

FOLLOWER FORCES ARE NOT ALLOWED WITH ENFORCED MOTIONS.

User information: The direction vector of an enforced motion is constant within a subcase.
Hence, a TLOADi entry which selects an enforced motion cannot refer to a follower force load. Modify the
offending TLOADi entry.

5440.0 *** USER WARNING MESSAGE 5440 (EXPMSG)

AUTHORIZATION EXPIRES WITHIN%1 MONTHS

5443.0 *** USER WARNING MESSAGE 5443 (ULANDD):

Main Index
 506 MSC Nastran Error Messages
Errors 5000 - 5999

DYNAMIC MATRIX IS SINGULAR AT THE SHIFT OF %1.

User information: This is a diagnostic message issued when performing a complex eigenvalue analysis with
Lanczos. See the MSC NASTRAN Numerical Analysis User's Guide.

5443.1 *** USER WARNING MESSAGE 5443 (PTNLSP):

E1 MATRIX IS SINGULAR.

5443.2 *** USER WARNING MESSAGE 5443

DYNAMIC MATRIX IS SINGULAR AT THE SHIFT OF %1

5444.0 *** USER INFORMATION MESSAGE 5444

REQUIRED NUMBER OF ROOTS HAVE BEEN FOUND.

User information: This is a diagnostic message issued when performing a complex eigenvalue analysis with
Lanczos.

5445.0 *** USER INFORMATION MESSAGE 5445 (ULANCZ):

MORE ROOTS THAN REQUIRED HAVE BEEN FOUND AT THIS SHIFT.

User information: This is a diagnostic message issued when performing a complex eigenvalue analysis with
Lanczos.

5445.1 *** USER INFORMATION MESSAGE 5445

NO ROOTS FOUND AT ALL.

5446.0 **** USER FATAL MESSAGE 5446

COMPLEX LANCZOS NEEDS %1 K MORE CORE WORDS

User information: You need to supply more memory.

5447.0 *** USER INFORMATION MESSAGE 5447 (ULANRD):

LANCZOS PROCESS FINISHED AT STEP %1 OF THE SHIFT OF %2.

5447.1 *** USER WARNING MESSAGE 5447:

Main Index
 MSC Nastran Error Messages 507
Errors 5000 - 5999

LANCZOS PROCESS ABORTED AT STEP %1 OF THE SHIFT OF %2.

User information: This indicates a breakdown in the Lanczos method. See Chapter 7 in the MSC NAS-
TRAN Numerical Methods User's Guide.

5448.0 *** USER WARNING MESSAGE 5448 (ULANRD):

CANNOT FIND START VECTORS ORTHOGONAL TO PREVIOUSLY CALCULATED SUB-
SPACE AT THE SHIFT OF %1.

User information: When a new shift is started, the starting vectors are orthogonalized with respect to the
already accepted eigenvectors of the earlier shifts (other orthogonalization). The message occurs if this pro-
cess fails.

5449.0 **** USER FATAL MESSAGE 5449

UNEXPECTED EOF ENCOUNTERED %1

5450.0 **** USER FATAL MESSAGE 5450

UNEXPECTED WORD COUNT%1 %2

User information: This should not normally occur. This is associated with input/output operations. You
should clean your disk (remove unnecessary files), verify database allocations, and perform similar functions
related
to disk I/O.

5451.0 **** USER WARNING MESSAGE 5451

NO ROOTS FOUND AT THIS SHIFT.

User information: See the MSC NASTRAN Numerical Methods User's Guide.

5452.0 **** USER WARNING MESSAGE 5452

NO ROOTS ACCEPTED AT THIS SHIFT.

User information: See the MSC NASTRAN Numerical Methods User's Guide.

5453.0 *** USER INFORMATION MESSAGE 5453 (ULANCZ):

Main Index
 508 MSC Nastran Error Messages
Errors 5000 - 5999

FEWER ROOTS THAN REQUIRED HAVE BEEN FOUND AT THIS SHIFT.

User information: This is a diagnostic message issued when performing a complex eigenvalue analysis with
Lanczos. See the MSC NASTRAN Numerical Methods User's Guide.

5453.1 *** USER INFORMATION MESSAGE 5453

FEWER ROOTS THAN REQUIRED HAVE BEEN FOUND.

5454.0 *** SYSTEM FATAL MESSAGE 5454 (FRD2C)

INCOMPATIBLE MATRICES

User information: PROBABLE CAUSE IS DATA BLOCK QHHL IS NOT THE SAME ORDER AS
KHH.

User information: If a restart is performed where MHH, BHH, and KHH are redetermined with a change
in the number of eigenvalues, the H-set will change and QHH must be reformed in the AMP module.
Re-execute the AMP module by deleting the PARAM, SKPAMP entry.

5455.0 *** USER INFORMATION MESSAGE 5455 ***

INITIAL EQUILIBRIUM IS NOT SATISFIED.

User information: In a nonlinear transient run using the adaptive time increment with the "STATIC"
option, the initial equilibrium condition (F(u) = P is not satisfied.
Examine TLOADi Bulk Data entries for an inadvertent specification of Po 0, or TIC entries for an inadver-
tent specification of uo 0.

5456.0 *** USER FATAL MESSAGE 5456 (NMEVD)

VALUE OF YOUNG'S MODULUS (E) IS LESS THAN OR EQUAL TO ZERO.

User information: The effective strain is undefined unless E > 0. The computation cannot proceed without
the effective strain.
The error may be in the default value on a MAT1 entry or in the tabular data on a TABLEM1 entry. An
extrapolated value obtained from the tabular data may be out of bounds.

5457.0 *** USER FATAL MESSAGE 5457 (EQDRD)

Main Index
 MSC Nastran Error Messages 509
Errors 5000 - 5999

NONLINEAR ANALYSIS IS NOT SUPPORTED FOR QUADR ELEMENT.

User information: The PSHELL entry referenced by a CQUADR element may not contain references to
MATS1 entries in the MIDi fields. Replace this element with the CQUAD4 element.

5457.1 *** USER FATAL MESSAGE 5457 (DSAH6E)

SUBSPACE ITERATION METHOD IN OPTIMIZATION IS NOT SUPPORTED FOR SUPERELE-
MENT.

User information: SELECT NELSON'S METHOD.

5458.0 *** USER INFORMATION MESSAGE 5458,

MODIFIED GIVENS METHOD IS FORCED BY USER.

User information: The exact text of this message depends on the METHOD field on the selected EIGR
Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.).

5458.1 *** USER INFORMATION MESSAGE 5458,

MODIFIED HOUSEHOLDER METHOD IS FORCED BY USER.

User information: The exact text of this message depends on the METHOD field on the selected EIGR
Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.).

5458.2 *** USER INFORMATION MESSAGE 5458,

MODIFIED GIVENS METHOD IS AUTOMATICALLY SELECTED.

User information: The exact text of this message depends on the METHOD field on the selected EIGR
Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.).

5458.3 *** USER INFORMATION MESSAGE 5458,

MODIFIED HOUSEHOLDER METHOD IS AUTOMATICALLY SELECTED.

User information: The exact text of this message depends on the METHOD field on the selected EIGR
Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.).

5458.4 *** USER INFORMATION MESSAGE 5458,

Main Index
 510 MSC Nastran Error Messages
Errors 5000 - 5999

REGULAR GIVENS METHOD IS SELECTED.

User information: The exact text of this message depends on the METHOD field on the selected EIGR
Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.).

5458.5 *** USER INFORMATION MESSAGE 5458,

REGULAR HOUSEHOLDER METHOD IS SELECTED.

User information: The exact text of this message depends on the METHOD field on the selected EIGR
Bulk Data entry. This message indicates the eigensolution status (all eigenvalues found, not all found, etc.).

5458.6 *** USER INFORMATION MESSAGE 5458,

QL HOUSEHOLDER METHOD IS AUTOMATICALLY SELECTED.

User information: Based upon automatic selection criteria the eigensolution was changed to this method.
To turn off this automatic selection, please set system cell 359 to 0. In the case of an original Lanczos
method selection, setting the NE field to zero on the READ DMAP line will also turn off this automatic
option.

5459.0 *** USER FATAL MESSAGE 5459 (ELTPRT)

NON-UNIQUE ELEMENT ID NUMBER DETECTED. %1 ELEMENT ID = %2 DUPLICATES A
%3 ELEMENT.

5459.1 *** USER FATAL MESSAGE 5459 (MDG2RG)

DUPLICATE ELEMENT ID =%1 FOUND FOR RIGID ELEMENTS.

User information: The element ID for rigid elements RBAR, RBAR1, RBE1, RBE2, RBE3, RJOINT,
RROD, RTRPLT, and RTRPLT1 must be unique.

5459.2 *** USER INFORMATION MESSAGE 5459 (ELTPRT)

NONUNIQUE ELEMENT ID NUMBERS DETECTED %1 TIMES FOR HEAT TRANSFER ELE-
MENT TYPES.

5459.3 *** USER INFORMATION MESSAGE 5459 (ERPECT)

ERPPNL %1 PROCESSING FOUND AND REMOVED %2 DUPLICATES FROM THE SET3 (ID =
%3) LIST OF ELEMENT IDS.

Main Index
 MSC Nastran Error Messages 511
Errors 5000 - 5999

5459.4 *** SYSTEM WARNING MESSAGE 5459 (ERPLCC)

THE SET STORAGE AREA OF THE SUBCASE CASE CONTROL RECORD ENDED PREMA-
TURELY AFTER PARAM %1%2 DATA.

User information: MODULE PROCESSING IS ABORTED. NO ERP OUTPUT IS GENERATED.

5459.5
DEPENDENT GRID ID =%1 IS DEFINED ON MULTIPLE RIGID ELEMENTS.

User information: The dependent grids on Lagrange rigid elements (RBAR, RBAR1, RBE1, RBE2,
RBE3,RJOINT, RROD, RTRPLT, and RTRPLT1 with RIGID=LAGR) cannot be defined in multiple
element entries.

5460.0 *** USER WARNING MESSAGE 5460 (IFS5P)

ON PSOLID ENTRY PID=%1 FULL OR 1 IS SPECIFIED IN THE "ISOP" FIELD AND BLANK, 0,
OR BUBBLE IS SPECIFIED IN THE "IN" FIELD.

User information:
1. IF THIS ENTRY IS REFERENCED BY CHEXA OR CPENTA ELEMENTS WITH NO
MIDSIDE NODES, THEN THE "IN" FIELD WILL BE RESET TO 2.
2. IF THIS ENTRY IS REFERENCED BY CHEXA OR CPENTA ELEMENTS WITH MIDSIDE
NODES, THEN THE "IN" FIELD WILL BE RESET TO 3.

User information: For CPENTA and CHEXA elements, when bubble function option is requested, only
reduced integration scheme is allowed.

5461.0 *** USER FATAL MESSAGE 5461 .

ELEMENT ID =%1 HAS SINGULAR INTERPOLATION FUNCTION, SCHEME TO REDUCE
THE RANK OF THE SHEAR STRAINS FAILED.

User information: Least square technique used in weight reduced integration method fails if the elements
has singular interpolation function.

5461.1 *** USER FATAL MESSAGE 5461 .

Main Index
 512 MSC Nastran Error Messages
Errors 5000 - 5999

LEAST SQUARE LINEAR TEMPERATURE MATRIX IS SINGULAR

User information: Least square technique used for thermal load in 3-D element has singular interpolation
function.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

5462.0 *** USER WARNING MESSAGE 5462 (IFS5P)

OPTIONS IN PSOLID ID = %1 FOR FLUID ELEMENT ARE NOT ALLOWED. DEFAULT VAL-
UES WILL BE TAKEN.

5463.0 *** USER FATAL MESSAGE 5463 (TA1BND)

RADIUS SPECIFIED FOR THE BEND ELEMENT =%1 IS LESS THAN HALF THE DISTANCE
BETWEEN ITS TWO END POINTS.

User information: Only a physically plausible radius should be used for the CBEND element.

5464.0 *** USER FATAL MESSAGE 5464 .

ELEMENT %1 HAS ZERO MASS DENSITY OR BULK MODULUS. CHECK MATERIAL PROP-
ERTIES.

5465.0 *** USER WARNING MESSAGE 5465 (DDRMM)

SOLUTION FOR SUBCASE %1 IS MISSING, THEREFORE IT WILL NOT BE PROCESSED.

User information: IF MORE THAN ONE RESIDUAL STRUCTURE SUBCASE IS SPECIFIED, THE
RESULT OF THE FIRST SUBCASE WILL BE CALCULATED IN THIS SOLUTION SEQUENCE.

User information: Only one residual structure subcase is allowed in the superelement solution sequences
which perform transient analysis. See Section 3.6.

5466.0 *** USER FATAL MESSAGE 5466 (SDP)

UNDEFINED COORDINATE SYSTEM ID = %1 IS REFERENCED BY THE AEROS BULK DATA
ENTRY

User information: Define referenced coordinate system ID in Bulk Data.

5467.0 *** USER FATAL MESSAGE 5467

Main Index
 MSC Nastran Error Messages 513
Errors 5000 - 5999

CONNECTION POINT G%1 OF CRAC3D ELEMENT %2 IS REQUIRED BUT NOT DEFINED

User information: At least one of the required connection points has not been specified on the element
entry. See chapter 5 of the MSC NASTRAN Quick Reference Guide.

5467.2 *** USER FATAL MESSAGE 5467

CONNECTION POINT G%1 OF CRAC2D ELEMENT %2 IS REQUIRED BUT NOT DEFINED

User information: At least one of the required connection points has not been specified on the element
entry. See chapter 5 of the MSC NASTRAN Quick Reference Guide.

5468.0 *** USER FATAL MESSAGE 5468 (DUM9D)

ILLEGAL GEOMETRY IN CRAC3D ELEMENT%1

User information: Only some of the connection points between G37 and G46 inclusive are defined.
Supply missing grids on CRAC3D entry or do not specify any. See chapter 5 of the MSC NASTRAN
Quick Reference Guide.

5469.0 *** USER FATAL MESSAGE 5469 (DUM9D)

IN CRAC3D ELEMENT%1 CONNECTION POINT G%2 IS REQUIRED IF CONNECTION
POINT G%3 IS SPECIFIED

User information: On the element card, only one of a pair of connection points is specified. This rule
applies to connection points G11 through G18 and G29 through G36. For example, if G11 is specified,
then G29 must also be specified. See chapter 5 of the MSC NASTRAN Quick Reference Guide.

5470.0 *** USER FATAL MESSAGE 5470

THE SPECIFIED CONNECTIVITY ON THE CRAC3D ELEMENT %1 IS NOT CONSISTENT
WITH THE SYMMETRIC HALF CRACK OPTION

User information: See chapter 5 of the MSC NASTRAN Quick Reference Guide.

5470.2 *** USER FATAL MESSAGE 5470

THE SPECIFIED CONNECTIVITY ON THE CRAC2D ELEMENT%1 IS NOT CONSISTENT
WITH THE SYMMETRIC HALF CRACK OPTION

User information: See chapter 5 of the MSC NASTRAN Quick Reference Guide.

Main Index
 514 MSC Nastran Error Messages
Errors 5000 - 5999

5470.4 *** USER FATAL MESSAGE 5470 (DM9NS)

THE SPECIFIED CONNECTIVITY ON THE CRAC3D ELEMENT%1 IS NOT CONSISTENT
WITH THE SYMMETRIC HALF CRACK OPTION

User information: See chapter 5 of the MSC NASTRAN Quick Reference Guide.

5470.6 *** USER FATAL MESSAGE 5470 (DM8NS)

THE SPECIFIED CONNECTIVITY ON THE CRAC2D ELEMENT%1 IS NOT CONSISTENT
WITH THE SYMMETRIC HALF CRACK OPTION

User information: See chapter 5 of the MSC NASTRAN Quick Reference Guide.

5471.0 *** USER FATAL MESSAGE 5471

IN CRAC3D ELEMENT %1, TWO OR MORE CONNECTION POINTS ARE EITHER COINCI-
DENT OR COLLINEAR

5471.2 *** USER FATAL MESSAGE 5471

IN CRAC2D ELEMENT %1, TWO OR MORE CONNECTION POINTS ARE EITHER COINCI-
DENT OR COLLINEAR

5472.0 *** USER WARNING MESSAGE 5472

IN CRAC3D ELEMENT%1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE%2, IS TOO
LARGE

5472.2 *** USER WARNING MESSAGE 5472

IN CRAC2D ELEMENT %1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE %2, IS TOO
LARGE

5472.4 *** USER WARNING MESSAGE 5472 (DM9NS)

IN CRAC3D ELEMENT %1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE %2, IS TOO
LARGE

5472.6 *** USER WARNING MESSAGE 5472 (DM8NS)

Main Index
 MSC Nastran Error Messages 515
Errors 5000 - 5999

IN CRAC2D ELEMENT%1, THE CRACK ANGLE, WHICH IS COMPUTED TO BE%2, IS TOO

LARGE

5473.0 *** USER WARNING MESSAGE 5473

IN CRAC3D ELEMENT %1, THE LOCATION OF MIDSIDE NODES CAUSES EXTREME DIS-
TORTION IN THE BASIC PENTAHEDRONS OF THE ELEMENT

5473.2 *** USER WARNING MESSAGE 5473

IN CRAC2D ELEMENT %1, THE LOCATION OF MIDSIDE NODES CAUSES EXTREME DIS-
TORTION IN THE BASIC TRIANGLES OF THE ELEMENT

5474.0 *** USER WARNING MESSAGE 5474

IN CRAC3D ELEMENT %1, AN INTERIOR ANGLE OF THE BASIC PENTAHEDRONS IS
EXTREMELY OBTUSE OR ACUTE

User information: This may also be caused by poorly located midside nodes.

5474.2 *** USER WARNING MESSAGE 5474

IN CRAC2D ELEMENT %1, AN INTERIOR ANGLE OF THE BASIC TRIANGLES IS
EXTREMELY OBTUSE OR ACUTE

User information: This may also be caused by poorly located midside nodes.

5477.0 *** USER WARNING MESSAGE 5477 (EQDRD)

COUPLING BETWEEN BENDING AND MEMBRANE IS NOT SUPPORTED FOR QUADR ELE-
MENT.

User information: The MID4 field on the PSHELL bulk data entry and the ZOFFS field on the QUADR
bulk data entry must be blank.

5477.1 *** USER WARNING MESSAGE 5477.

COUPLING BETWEEN BENDING AND MEMBRANE IS NOT SUPPORTED FOR TRIAR ELE-
MENT.

Main Index
 516 MSC Nastran Error Messages
Errors 5000 - 5999

5478.0 *** USER FATAL MESSAGE 5478. (TQDRD)

FOR ELEMENT WITH ID =%1
THE JACOBIAN MATRIX IS SINGULAR.

5479.0 *** USER FATAL MESSAGE 5479.

FOR ELEMENT WITH ID =%1
THE INTERNAL STRAIN MODES ARE SINGULAR.

User information: Check material property entries referenced by this element for correctness.

5480.0 *** SYSTEM FATAL MESSAGE 5480.

FOR ELEMENT WITH ID =%1
*** THE EXTRAPOLATION MATRIX IS SINGULAR.

User information: This indicates a logic error in the program. Contact Hexagon Client Support.

5480.1 *** SYSTEM FATAL MESSAGE 5480.

LOGIC ERROR IE=%1
THE AREA MATRIX IS SINGULAR.

User information: This indicates a logic error in the program. Contact Hexagon Client Support.

5481.0 *** USER WARNING MESSAGE 5481 (EQDRD)

BUCKLING ANALYSIS IS NOT SUPPORTED FOR QUADR ELEMENT.

User information: Differential stiffness, which is computed in a geometric nonlinear or buckling analysis, is
not available for this element. Replace this element with the CQUAD4 or CTRIA3 element.

5481.1 *** USER WARNING MESSAGE 5481.

BUCKLING ANALYSIS IS NOT SUPPORTED FOR TRIAR ELEMENT.

User information: Differential stiffness, which is computed in a geometric nonlinear or buckling analysis, is
not available for this element. Replace this element with the CQUAD4 or CTRIA3 element.

5481.2 *** USER FATAL MESSAGE 5481.

NONLINEAR ANALYSIS IS NOT SUPPORTED FOR QUADR ELEMENT.

Main Index
 MSC Nastran Error Messages 517
Errors 5000 - 5999

5481.3 *** USER WARNING MESSAGE 5481.

DIFFERENTIAL STIFFNESS IS NOT AVAILABLE FOR %1 ELEMENT.

5482.0 *** USER FATAL MESSAGE 5482 (EQDRD)

HEAT TRANSFER ANALYSIS IS NOT SUPPORTED FOR QUADR ELEMENT.

User information: The solution sequence requested on the Executive Control statement SOL is a heat
transfer sequence or the HEAT keyword is specified on the NASTRAN or APP statements.

5482.1 *** USER FATAL MESSAGE 5482

HEAT TRANSFER ANALYSIS IS NOT SUPPORTED BY %1 ELEMENT.

User information: The solution sequence requested on the Executive Control statement SOL is a heat
transfer sequence or the HEAT keyword is specified on the NASTRAN or APP statements.

5482.2 *** USER WARNING MESSAGE 5482 (GPFDR)

ELEMENT TYPE %1 IS NOT CURRENTLY SUPPORTED FOR FREQUENCY ANALYSIS. AS A
RESULT, THE GPFORCE RESULTS ARE NOT COMPLETE.

5482.3 *** USER WARNING MESSAGE 5482 (GPFDR)

THE FOLLOWING %1 ELEMENT TYPES ARE NOT CURRENTLY SUPPORTED FOR FRE-
QUENCY ANALYSIS. AS A RESULT, THE GPFORCE RESULTS ARE NOT COMPLETE.
%2

5483.0 *** SYSTEM FATAL MESSAGE 5483, (TA1H)

ROUTINE NEEDS TO BE UPDATED, IT DOES NOT SUPPORT ELEMENTS WITH GRIDS
MORE THAN =%1

5483.1 *** SYSTEM FATAL MESSAGE 5483,

*** ELEMENT TIMING TABLE IN
*** SEQCT ROUTINE NEEDS TO BE UPDATED, IT DOES NOT SUPPORT ELEMENT TYPE
GREATER THAN =%1

System information: Contact Hexagon Client Support.

5483.2 *** SYSTEM FATAL MESSAGE 5483, (BLDECT),

Main Index
 518 MSC Nastran Error Messages
Errors 5000 - 5999

ROUTINE NEEDS TO BE UPDATED, IT DOES NOT SUPPORT ELEMENTS WITH GRIDS

MORE THAN =%1

5484.0 *** USER WARNING MESSAGE 5484,

TABRND1 CARD, ID = %1, DEFINED (OR EXTRAPOLATED TO) NEGATIVE AUTO SPEC-
TRAL DENSITIES. THEY WERE RESET TO ZERO.

5485.0 *** USER FATAL MESSAGE 5485,

NO SOLUTION IS AVAILABLE TO PERFORM A RESTART.

5486.0 *** USER FATAL MESSAGE 5486 (SSG1A)

NO STATIC LOAD SUBCASE IS SPECIFIED FOR A BUCKLING SOLUTION

5487.0 *** USER WARNING/FATAL MESSAGE 5487

ORIENTATION VECTOR DEFINED FOR THE ELEMENT ID =%1 IS NEARLY PARALLEL, IT
MAY GIVE POOR RESULTS.

5488.0 *** USER FATAL MESSAGE 5488 (NLINIT)

THE CONTROLLED INCREMENTS METHOD MAY NOT BE USED WITHOUT LOAD
INCREMENTS.

5489.0 *** USER WARNING MESSAGE 5489 (CASE)

THE CONTROLLED INCREMENTS METHOD MAY NOT BE USED WITH CREEP.
THE STANDARD ITERATION METHOD HAS BEEN SUBSTITUTED.

5490.0 *** USER FATAL MESSAGE 5490 (INRELF)

THE NUMBER OF SUPERELEMENT EIGENVECTORS %1 IS LESS THAN OR EQUAL TO THE
NUMBER OF DEGREES OF FREEDOM, %2, ON THE SESUP BULK DATA ENTRY.

User action: INCREASE THE NUMBER OF EIGENVECTORS DESIRED ON THE EIGR OR

EIGRL BULK DATA ENTRY, OR DECREASE THE NUMBER OF DEGREES OF FREEDOM ON
THE SESUP BULK DATA ENTRY.

5491.0 *** USER WARNING MESSAGE 5491 (EQD4D)

Main Index
 MSC Nastran Error Messages 519
Errors 5000 - 5999

BAD GEOMETRY FOR QUAD4 ELEMENT ID =%1 THE TAPER OF %2 EXCEEDS THE MAXI-
MUM VALUE OF %3

User action: THE TOLERANCE MAY BE ADJUSTED WITH Q4TAPER KEYWORD ON THE
NASTRAN STATEMENT.

User information: Bad geometry can cause incorrect answers for CQUAD4 elements. The bad geometry
warning may be neglected if the element is in a non- critical part of the model, or if the element stress is
constant. If the element is in a critical part of the model, you are advised to refine your model so these bad
geometries do not occur. Skew and taper are representative of the amount that a CQUAD4 deviates
from being rectangular. Skew is the angle between the lines that join opposite midsides. When this angle is
less than 30 degrees the message is issued. For no skew this angle is 90 degrees. Taper is computed as fol-
lows: Connect opposite grid points and compute the area of the enclosed triangles. Ji is 1/2 of the area asso-
ciated with grid i and the adjacent grids of the enclosed triangle. Ja is 1/4 of J1+J2+J3+J4. If ABS((Ji-Ja)/Ja)
exceeds 0.5 then the message is issued. (The equation equals 0.0 if there is no taper.) Another way to think
of taper is the ratio of the areas on the two sides of a diagonal; if the ratio is greater than 3, then the taper
test fails. Note that these tests concern only geometry, and are made prior to the analysis. Another useful
test, made after the analysis, is the stress discontinuity calculation.

5491.1 *** USER WARNING MESSAGE 5491 (EQD4D)

BAD GEOMETRY FOR QUAD4 ELEMENT ID =%1 THE SKEW ANGLE %2 IS LESS THAN THE
MINIMUM VALUE OF %3 DEGREES.

User action: THE TOLERANCE MAY BE ADJUSTED WITH Q4SKEW KEYWORD ON THE NAS-
TRAN STATEMENT.

5491.2 *** USER WARNING MESSAGE 5491 (ETR3D)

BAD GEOMETRY FOR TRIA3 ELEMENT ID =%1 THE SMALLEST ANGLE,%2 IS LESS THAN
THE MINIMUM VALUE OF %3 DEGREES.

User action: THE TOLERANCE MAY BE ADJUSTED WITH T3SKEW KEYWORD ON THE NAS-
TRAN STATEMENT.

5491.3 *** USER INFORMATION MESSAGE 5491 (EQDGED)

BAD GEOMETRY FOR QUAD ELEMENT WITH ID =%1
THE SKEW ANGLE%2 IS LESS THAN THE RECOMMENDED MINIMUM VALUE OF 30
DEGREES.

Main Index
 520 MSC Nastran Error Messages
Errors 5000 - 5999

5491.4 *** USER INFORMATION MESSAGE 5491 (EQDGED)

BAD GEOMETRY FOR QUAD ELEMENT WITH ID =%1
THE TAPER OF%2 EXCEEDS THE RECOMMENDED MAXIMUM VALUE OF 0.5 .

5492.0 *** USER FATAL MESSAGE 5492 (OPTGPE)

AN UNDEFINED DVID ID =%1 HAS BEEN REFERENCED BY A DVGRID BULK DATA CARD
WITH A DVID =%2

User action: CHECK THE DVGRID AND GRID BULK DATA CARDS

5492.1 *** USER FATAL MESSAGE 5492 (DSAJ1)

AN UNDEFINED GRID ID =%1 HAS BEEN REFERENCED BY A DVGRID BULK DATA CARD
WITH A DVID =%2

User action: CHECK THE DVGRID AND GRID BULK DATA CARDS

5494.0 *** USER WARNING MESSAGE 5494,

ONLY THE FIRST 50 MESSAGES HAVE BEEN PRINTED.

5495.0 *** USER WARNING MESSAGE 5495,

REQUESTED RESPONSE DATA OF ( %1 %2 ) BY RCROSS ENTRY IS MISSING. RCROSS
ENTRY IS:
RCROSS = %3
RTYPE1 = %4 ,ID1 = %5 ,COMP1 = %6 ,RTYPE2 = %7 ,ID2 = %8 ,COMP2 = %9 ,CURID = %10
IT IS NEITHER COMPUTED NOR BELONGS TO CURRENT SUPERELEMENT OR MODULE.
RCROSS REQUEST FOR THIS ENTRY IS IGNORED.

5495.1 *** USER WARNING MESSAGE 5495,

REQUESTED RESPONSE DATA OF ( %1 ) BY RCROSS CARD IS MISSING.
IT IS NEITHER COMPUTED NOR BELONGS TO CURRENT SUPERELEMENT OR MODULE.

5495.2 *** USER WARNING MESSAGE 5495,

Main Index
 MSC Nastran Error Messages 521
Errors 5000 - 5999

REQUESTED RESPONSE DATA OF ( %1 %2 ) BY BOTH RCROSS AND RANDPS CARDS IS

MISSING IN SOME SUBCASE(S).
RCROSS CARD IS:
RCROSS = %3
RTYPE1 = %4 ,ID1 = %5 ,COMP1 = %6 ,RTYPE2 = %7 ,ID2 = %8 ,COMP2 = %9 ,CURIV = %10
THE MISSING DATA IS RELATED TO THE FOLLOWING SUBCASE(S) ( ONLY UP TO TEN
OF THEM ARE PRINTED ):
SUBCASE(S): %11, %12, %13, %14, %15, %16, %17, %18, %19, %20
RCROSS REQUEST FOR THIS CARD IS IGNORED.

5495.3 *** USER WARNING MESSAGE 5495,

REQUESTED COMPONENT CODE %1 OF RESPONSE DATA ( %2 %3 ) BY RCROSS CARD IS
INCORRECT.
RCROSS CARD IS:
RCROSS = %4
RTYPE1 = %5 ,ID1 = %6 ,COMP1 = %7 ,RTYPE2 = %8 ,ID2 = %9 ,COMP2 = %10 ,CURIV = %11
RCROSS REQUEST FOR THIS CARD IS IGNORED.

5495.4 *** USER WARNING MESSAGE 5495,

REQUESTED RESPONSE DATA OF ( %1 %2 ) BY RANDPS CARDS IS MISSING IN SUBCASE
%3.
RCROSS CARD IS:
RCROSS = %4
RTYPE1 = %5 ,ID1 = %6 ,COMP1 = %7 ,RTYPE2 = %8 ,ID2 = %9 ,COMP2 = %10 ,CURIV = %11
RCROSS REQUEST FOR THIS CARD IS IGNORED.

5496.0 *** USER INFORMATION MESSAGE 5496 (NL3EMA)

THE TOTAL STIFFNESS MATRIX is negative definite and hence THE DIFFERENTAIL STIFFNESS
will not be included in THE TOTAL STIFFNESS MATRIX.

5497.0 *** USER FATAL MESSAGE 5497 (APD3)

PLANFORM GEOMETRY FOR CAERO3 ID = %1 IS IN ERROR.

User action: CHECK LEADING EDGE SWEEP ANGLE OR CONTROL SURFACE HINGE LINE.

5498.0 *** USER FATAL MESSAGE 5498 (APD2)

CAERO2 ENTRY ID = %1 NOT INPUT IN Z,ZY,Y SEQUENCE

Main Index
 522 MSC Nastran Error Messages
Errors 5000 - 5999

5499.0 *** USER FATAL MESSAGE 5499 (APD2)

ASSOCIATED BODY ID = %1 REFERENCED ON PAERO1 ENTRY %2 COULD NOT BE
FOUND.

5500.0 *** SYSTEM FATAL MESSAGE 5500 (DSAB3)

NO MATCH FOUND IN GPTA1 FOR ECT LOCATE IDS%1

5501.0 *** SYSTEM FATAL MESSAGE 5501 (DSAB3)

ECT ENTRY LENGTH FOR ELEMENT TYPE %1 IS %2---PROGRAM LIMIT IS 350

5502.0 *** USER WARNING MESSAGE 5502 (DSAL1)

GRID ID = %1 REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND.

User information: THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT
ERROR.
RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.

5502.1 *** USER FATAL MESSAGE 5502 (DSAD15)

GRID ID = %1 REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND.

User information: THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT
ERROR.
RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.

5502.2 *** USER FATAL MESSAGE 5502 (DOPR3I)

IN SUBCASE = %1 GRID ID = %2 REFERENCED ON DRESP1 ENTRY = %3 COULD NOT BE
FOUND.

User action: CHECK THE GRID ID OR FOR THE EXISTENCE OF THE REFERENCED GRID
ENTRY

User information: SUBSEQUENT SUBCASES HAVE NOT BEEN CHECKED

5502.3 *** USER FATAL MESSAGE 5502 (DSAD58)

Main Index
 MSC Nastran Error Messages 523
Errors 5000 - 5999

SET3 ID = %1 REFERENCED ON A DRESP1 ENTRY WITH RTYPE=ERP COULD NOT BE

FOUND.

User information: THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT
ERROR.
RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.

5503.0 *** USER FATAL MESSAGE 5503 (DSAD13)

ELEM NO. %1 PLY NO. %2 REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND.

User action: CHECK THE ELEMENT IDS REQUESTED ON THE DRESP1 ENTRY.
IF A CFAILURE RESPONSE TYPE IS REQUESTED, CHECK THAT THE CORRESPONDING
PCOMP AND MAT1 BULK DATA ENTRIES HAVE BEEN CORRECTLY SPECIFIED.

User information: USE OF UNREFERENCED ELEMENTS IS NOT RECOMMENDED AND MAY

INDICATE A USER INPUT ERROR.
RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.

5503.1 *** USER FATAL MESSAGE 5503 (DSAB5D)

RECORD ID = %1 %2 IS OUT OF SYNC ON DATA BLOCK NUMBR %3
AN DSAB5D SYSTEM ERROR USER ACTION: PLEASE SEND THIS RUN TO HEXAGON AB.

5504.0 *** USER FATAL MESSAGE 5504 (DSAD25)

GRID ID = %1 ELEMENT ID = %2 REFERENCED ON A DRESP1 ENTRY COULD NOT BE
FOUND.

User information: THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT
ERROR.
MAKE SURE THE ELEMENT ID IS ASSOCIATED WITH THE GRID ID ON DRE-
SP1=GPFORCE DATA ENTRY

5504.1 *** USER FATAL MESSAGE 5504 (DSAD26)

Main Index
 524 MSC Nastran Error Messages
Errors 5000 - 5999

GRID ID = %1 ORIENT ID = %2 REFERENCED ON A DRESP1 ENTRY COULD NOT BE

FOUND.

User information: THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT
ERROR.
RTYPE=GPFORCP IS FOR ONE AND TWO DIMENSIONAL ELEMENTS ONLY.

5504.2 *** USER WARNING MESSAGE 5504 (DSAL8)

GRID ID = %1 ELEMENT ID = %2 REFERENCED ON A DRESP1 ENTRY COULD NOT BE
FOUND.

User information: THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT
ERROR.
RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.

5504.3 *** USER WARNING MESSAGE 5504 (DSAL9)

GRID ID = %1 ORIENT ID = %2 REFERENCED ON A DRESP1 ENTRY COULD NOT BE
FOUND.

User information: THIS IS NOT RECOMMENDED AND MAY INDICATE A USER INPUT
ERROR.
RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.

5504.4 *** USER FATAL MESSAGE 5504 (dsab1f)

The design task cannot proceed because the designed properties referenced on the DVxRELy entries are not
used by the finite element model.

User information: Ensure that at least one finite element references the
designed properties.

5505.0 *** USER FATAL MESSAGE 5505 (DSAD14)

A RESULT COULD NOT BE FOUND FOR A FLUTTER ROOT WITH DENSITY = %1,
MACH = %2, VELOCITY = %3 FOR MODE NO. %4

User action: CHECK THE FLUTTER SUMMARY TO SEE IF THE REQUESTED ROOT
WAS EXTRACTED

Main Index
 MSC Nastran Error Messages 525
Errors 5000 - 5999

5506.0 *** USER FATAL MESSAGE 5506

TRANSVERSE SHEAR MATERIAL MATRIX IS SINGULAR FOR PCOMP %1

5507.0 *** SYSTEM FATAL MESSAGE 5507 (DSABET)

TEMPERATURE SET ID. IN DATA RECORD NOT FOUND IN HEADER RECORD
TEMP(1)=%1
TLIST(I)= %2
%3
%4
%5
%6
%7
%8
%9
%10
%11
%12
%13
%14
%15
%16
%17
%18
%19
%20
%21

5508.0 **** USER WARNING MESSAGE 5508

THERE ARE DRESP1 ENTRIES WITH RTYPE = PSDxxxx AND/OR RMSxxxx BUT ALL OF THE
CORRESPONDING RESPONSES ARE ZERO.

User information: THIS MAY CAUSE THE JOB TO FAIL LATER ON WTIH UFM 3046 - THIS
FREQUENCY ANALYSIS HAS NO EXCITATION.

User action: REVIEW THE SPECIFICATION OF THE DRESP1 ENTRIES WITH RTYPE =
PSDxxxx AND/OR RMSxxxx TO MAKE SURE THAT THE REQUESTED QUANTITIES ARE
NON-ZERO.

Main Index
 526 MSC Nastran Error Messages
Errors 5000 - 5999

5509.0 *** USER INFORMATION MESSAGE 5509

A NULL COLUMN OF RESPONSES HAS BEEN ENCOUNTERED .
THESE ZERO RESULTS WILL NOT BE PRINTED.

5510.0 *** USER FATAL MESSAGE 5510 (MDLPRM)

Argument %1 for DMAP function %2 is not supported.

5511.0 *** USER FATAL MESSAGE 5511 (DSACTC)

PROBLEM LIMITATION OF 66 TEMPERATURE SETS AS BEEN EXCEEDED.

5512.0 *** SYSTEM FATAL MESSAGE 5512 (DSACTC)

TEMPERATURE SET ID. IN DATA RECORD NOT FOUND IN HEADER RECORD
TEMP(1)= %1TLIST(I)=%2
%3
%4
%5
%6
%7
%8
%9
%10
%11
%12
%13
%14
%15
%16
%17
%18
%19
%20
%21

5513.0 *** USER FATAL MESSAGE 5513 (TA0VCCTX)

Main Index
 MSC Nastran Error Messages 527
Errors 5000 - 5999

Grid ID = %1 connected to element ID = %2 is referenced by VCCT entry = %3

User information: VCCT entry can only refer to grids connected to Nonlinear Material elements that refer
to property entries such as %4.

5514.0 *** SYSTEM FATAL MESSAGE 5514 (DSAE)

ELEMENT TYPE DOES NOT MATCH

5515.0 *** USER FATAL MESSAGE 5515 (TA1MTFx)

%1 element ID %2, which does not currently support Frequency Dependent Materials, is referring to
%3 %4 that is associated with %5 %6.

User information: Please do not refer to Frequency Dependent Material entries for %1 elements pointing
to %3.

5516.0 *** SYSTEM FATAL MESSAGE 5516 (DSAE)

TABLE DIBIDG IS PURGED

User action: VERIFY THAT THIS TABLE IS NOT PURGED

5532.0 *** USER WARNING MESSAGE 5532 (WEIGHT)

RHO OF MAT CARD IS LESS THAN OR EQUAL TO ZERO

User information: See Error Report 3557 in Chapter 17.

5535.0 *** USER FATAL MESSAGE 5535 (DSAW)

THIS IS A NONSUPPORTED ELEMENT TYPE

User information: ELEMENT TYPE = %1 , PLEASE SEE PROGRAM MANUAL VOL.1 EST DATA-
BLOCK FOR ELEMENT TYPE

5535.1 *** SYSTEM WARNING MESSAGE 5535 (HBDY2)

ELEMENT TYPE = %1 IS NOT SUPPORTED BY THIS MODULE.

5536.0 *** SYSTEM FATAL MESSAGE 5536 (DSMRG9)

THE OBJECTIVE FUNCTION HAS NOT BEEN DEFINED FOR THIS RUN

Main Index
 528 MSC Nastran Error Messages
Errors 5000 - 5999

5537.0 *** USER WARNING MESSAGE 5537 (DOPR3L)

ELEMENT DEFORMATION SETS ARE NOT ACCOUNTED FOR PROPERLY IN SENSITIVITY
CALCULATIONS.
WRONG ANSWERS MAY RESULT FOR CALCULATED RESPONSES.

5538.0 *** USER FATAL MESSAGE 5538 (DOPR3)

The TABLEDi entries ID's (TID) specified FOR LALLOW/LID AND/OR UALLOW/UID on the
DCONSTR entry are missing.

User action: EITHER REPLACE INTEGER INPUT for TID WITH REAL VALUE FOR UPPER/
LOWER BOUNDS OR PROVIDE CORRESPONDING TABLEDi FOR FREQUENCY DEPEN-
DENT BOUNDS.

5554.0 *** USER FATAL MESSAGE 5554 (DSABET)

PROBLEM LIMITATION OF 66 TEMPERATURE SETS HAS BEEN EXCEEDED.

5555.0 *** USER FATAL MESSAGE 5555 (DSAH2)

THE EIGENVECTOR OF MODE NUMBER %1 IS REQUIRED FOR THE SENSITIVITY OF THE
ASSOCIATED EIGENVALUE/EIGENFREQUENCY BUT ONLY %2 EIGENVECTORS WERE
EXTRACTED

User action: EITHER INCREASE THE NUMBER OF EXTRACTED EIGENVECTORS OR

REMOVE THE REQUEST FOR THE DESIGNATED EIGENVALUE/EIGENFREQUENCY FROM
A DRESP1 ENTRY

5555.1 *** USER FATAL MESSAGE 5555 (DSAH2)

THE EIGENVECTOR OF MODE NUMBER %1 IS REQUIRED FOR THE SENSITIVITY OF THE
ASSOCIATED BUCKLING EIGENVALUE BUT ONLY %2 EIGENVECTORS WERE
EXTRACTED

User action: EITHER INCREASE THE NUMBER OF EXTRACTED EIGENVECTORS OR

REMOVE THE REQUEST FOR THE DESIGNATED EIGENVALUE FROM A DRESP1 ENTRY

5556.0

Main Index
 MSC Nastran Error Messages 529
Errors 5000 - 5999

SPARSE DATA RECOVERY IS NOT SUPPORTED FOR EIGENVECTOR SENSITIVITY ANALY-

SIS.

User action: SPECIFY PARAM,SPARSEDR,NO WHEN EIGENVECTOR SENSITIVITIES ARE

REQUIRED

5556.1
SPARSE DATA RECOVERY IS NOT AVAILABLE IF DATA IS OFFLINE.

5601.0 *** USER FATAL MESSAGE 5601 (SDSA)

A DESOBJ ENTRY CANNOT BE FOUND. ONE MUST BE DEFINED FOR THE DESIGN
MODEL.

5602.0 *** USER FATAL MESSAGE 5602. (SDSA)

DESOBJ ENTRY ID=%1 REFERENCES EXTERNAL SUPERELEMENT ID=%2

User information: DESOBJ ENTRY MAY ONLY REFERENCE A PRIMARY OR AN IMAGE

SUPERELEMENT

5603.0 *** USER FATAL MESSAGE 5603. (SDSA)

DESOBJ ENTRY ID=%1 REFERENCES AN UNDEFINED SUPERELEMENT OR MODULE

5605.0 *** USER FATAL MESSAGE 5605. (SDSAA)

SUPERELEMENT OR MODULE MAP DOES NOT CONTAIN ELEMENT IDS FOR SEID OR
MID =%1

5606.0 *** USER FATAL MESSAGE 5606. (SDSAB)

NO DRESP1 ENTRIES CAN BE FOUND IN DATABLOCK EDOM.

User action: SPECIFY AT LEAST ONE DRESP1 ENTRY.

5607.0 *** USER FATAL MESSAGE 5607. (SDSAB)

Main Index
 530 MSC Nastran Error Messages
Errors 5000 - 5999

NO DRESP1 ENTRIES CAN BE FOUND FOR SUPERELEMENT OR MODULE ID=%1 WITH

DRESP2 - SYNTHETIC RESPONSES

User action: SPECIFY AT LEAST A SINGLE DRESP1 - DIRECT RESPONSE FOR THIS
SUPERELEMENT OR MODULE

5608.0 *** USER FATAL MESSAGE 5608 (SDSAC)

%1 ENTRY ID=%2 REFERENCES AN UNDEFINED DRESP1 ENTRY ID=%3

5608.1 *** USER FATAL MESSAGE 5608 (SDSAE)

%1 ENTRY ID=%2 REFERENCES AN UNDEFINED DRESP2 ENTRY ID=%3

5608.2 *** USER FATAL MESSAGE 5608 (SDSAC)

%1 ENTRY ID=%2 REFERENCES AN UNDEFINED DRESP2 ENTRY ID=%3

5608.3 *** USER FATAL MESSAGE 5608 (SDSAE)

MORE THAN 10 LEVELS OF NESTED DRESP2 FOUND.

User information: THERE IS A CURRENT LIMIT OF 10 NESTED DRESP2 LEVELS.

User action: REDUCE NESTED DRESP2 LEVELS TO 10 OR LESS.

5609.0 *** USER FATAL MESSAGE 5609 (SDSAC)

DRESP2 ENTRY ID=%1 REFERENCES DRESP1 IDS THAT BELONG TO DIFFERENT
SUPERELEMENTS OR MODULES.

User action: MAKE SURE ALL DRESP1 IDS REFERENCED ON A DRESP2 REFER TO GID/EID
OF A SINGLE SE.

5609.1 *** USER FATAL MESSAGE 5609 (SDSAE)

DRESP2 ENTRY ID=%1 REFERENCES DRESP1/2 IDS THAT BELONG TO DIFFERENT
SUPERELEMENTS OR MODULES.

User action: MAKE SURE ALL DRESP1 IDS REFERENCED ON A DRESP2 REFER TO GID/EID
OF A SINGLE SE.

5609.2 *** USER FATAL MESSAGE 5609 (SDSAC)

Main Index
 MSC Nastran Error Messages 531
Errors 5000 - 5999

DRESP3 ENTRY ID=%1 REFERENCES DRESP1/2 IDS THAT BELONG TO DIFFERENT

SUPERELEMENTS OR MODULES.

User action: MAKE SURE ALL DRESP1 IDS REFERENCED ON A DRESP2 REFER TO GID/EID
OF A SINGLE SE.

5610.0 *** USER WARNING MESSAGE 5610 (DSAW)

THE MASS DEFINED ON CMASSI BULK DATA ENTRIES DOES NOT CONTRIBUTE TO THE
WEIGHT RESPONSE AND WILL BE IGNORED IN THE DESIGN SENSITIVITY AND OPTIMI-
ZATION ANALYSIS.

User action: DRESP2 SYNTHETIC RESPONSES CAN BE USED TO INCLUDE THE EFFECTS OF
MASS CHANGES ON THE WEIGHT.

5611.0 *** USER FATAL MESSAGE 5611 (DPR1A2 )

DRESP2 %1 USES FUNC=BETA BUT THERE ARE NO DRESP1 RESPONSES IDENTIFIED.
ONLY DRESP1 ENTRIES CAN BE INVOKED WHEN FUNC=BETA IS USED ON THE DRESP2
ENTRY.

5611.1 *** USER FATAL MESSAGE 5611 (DPR1A2 )

DRESP2 %1 USES FUNC=MATCH CONTAINS %2 DTABLE ENTRIES AND %3 DRESP1
ENTRIES. THESE TWO NUMBERS MUST BE THE SAME WHEN FUNC=MATCH IS
USED ON THE DRESP2 ENTRY.

5612.0 *** USER FATAL MESSAGE 5612 (DOPR2B)

ZERO GRID PERTURBATION IS PRESCRIBED BY ALL DESIGN VARIABLES.

User action: CHECK DVGRID BULK DATA ENTRIES FOR ZERO GRID PERTURBATION.
PROGRAMMER INFORMATION: INPUT MATRIX DESVEC IS NULL.

5613.0 *** USER FATAL MESSAGE 5613 (DMPR)

A DRESPI ENTRY DOES NOT EXIST IN THE BULK DATA.

User information: AT LEAST ONE DRESP1 OR DRESP2 MUST BE PRESENT IN THE DESIGN
MODEL.

Main Index
 532 MSC Nastran Error Messages
Errors 5000 - 5999

5615.0 *** USER FATAL MESSAGE 5615 (DMPRB)

A DRESP2 ENTRY ID=%1 REFERENCES AN UNDEFINED DRESP1 ENTRY ID =%2

5616.0 *** USER FATAL MESSAGE 5616 (DMPRB)

DRESP2 ENTRY ID =%1 REFERENCES DRESP1 ENTRIES WHICH HAVE INCONSISTENT
RESPONSE TYPES.

User information: When referencing DRESP1 entries, each referenced entry must have the same RTYPE
and PTYPE.

5617.0 *** USER FATAL MESSAGE 5617. (SDSAB)

THE SUPERELEMENT OR MODULE ID SPECIFIED ON THE DESOBJ BULK DATA ENTRY
DOES NOT EXIST ON THE REFERENCED DRESP1 BULK DATA ENTRY.

User action: VERIFY THE DESOBJ AND DRESP1 ENTRIES.

5619.0 *** USER FATAL MESSAGE 5619. (SDSAB)

A WEIGHT OR VOLUME RESPONSE IS REQUESTED FOR COLLECTOR SUPERELEMENT
OR MODULE =%1 IN DRESP1 BULK DATA ENTRY =%2

User action: ENSURE THE SUPERELEMENT OR MODULE CONTAINS AT LEAST ONE ELE-
MENT WITH VOLUME.

5619.1 *** USER FATAL MESSAGE 5619. (SDSAP)

PART SE %1 MUST HAVE DRESP2 REFERENCING DRESP1 of GLOBAL RESPONSE, SUCH AS
LAMA, FREQ and etc, UNDER BEGIN SUPER.

User action: COPY FOLLOWING ITEMS FROM MAIN BULK to BEGIN SUPER of each PART SE
with DESVAR
1. DRESP2 REFERENCING DRESP1 of GLOBAL RESPONSE; INCLUDING NESTED
DRESP2
2. DTABLE REFERENCED ON DRESP2
3. DEQATN REFERENCED ON DRESP2

5620.0 *** USER FATAL MESSAGE 5620 (DSAJ1)

Main Index
 MSC Nastran Error Messages 533
Errors 5000 - 5999

AN UNDEFINED DESIGN VARIABLE ID =%1 HAS BEEN REFERENCED BY A DVGRID BULK

DATA ENTRY WHICH HAS A GRID ID =%2

5621.0 *** USER FATAL MESSAGE 5621 (DOM11K)

THREE POINTS REFERENCED BY CORD2I ENTRY ID =%1 HAVE BECOME COLLINEAR

User action: REEXAMINE DESIGN TASK SPECIFICATION

User information:
X Y Z

5621.1 *** USER FATAL MESSAGE 5621 (DOM11J)

THREE POINTS REFERENCED BY CORD1I ENTRY ID =%1 HAVE BECOME COLLINEAR.

User action: REEXAMINE DESIGN TASK SPECIFICATION

User information:
GRID ID X Y Z

5622.0 *** USER FATAL MESSAGE 5622 (DSAJ)

FOR AN EXTERNAL AUXILIARY MODEL:
THE AUXILIARY DISPLACEMENT MATRIX OR THE DVSHAP BULK DATA ENTRY IS MISS-
ING.

User action: CHECK FOR THE EXISTENCE OF DVSHAP ENTRIES AND YOUR DATABASE
FILE REFERENCED ON THE DBLOCATE STATEMENT.

5623.0 *** USER FATAL MESSAGE 5623 (DSAJ)

AN UNDEFINED DESIGN VARIABLE ID =%1 HAS BEEN REFERENCED BY A DVSHAP/DVB-
SHAP BULK DATA ENTRY.

5624.0 *** USER FATAL MESSAGE 5624 (DSAJ2)

THE %1TH COLUMN OF THE DIRECT INPUT BASIS VECTOR MATRIX IS NULL.

5625.0 *** USER FATAL MESSAGE 5625 (DSAJ)

Main Index
 534 MSC Nastran Error Messages
Errors 5000 - 5999

AN UNDEFINED BASVEC COLUMN ID =%1 HAS BEEN REFERENCED BY A DVSHAP/DVB-

SHAP BULK DATA ENTRY.

5265.1 *** USER FATAL MESSAGE 5265 (UXVPRD)

MULTIPLE POINTS OF AEFORCE/UXVEC DATA ARE SPECIFIED IN A SINGLE
DIMENSION, AND INTERPOLATION BASED ON SUCH FORCES REQUIRES AT LEAST
TWO DIMENSIONS (NOT INCLUDING INTERCPT).

User action: SPECIFY A DUMMY AEPARM DIMENSION IN THE CORRESPONDING

UXVEC ENTRIES FOR TWO-DIMENSIONAL INTERPOLATION.

5265.2 *** USER FATAL MESSAGE 5265 (UXVPRD)

ERROR IN ALLOCATING MEMORY FOR MATRIX %1 IN UXVPRD

5626.0 *** USER FATAL MESSAGE 5626 (DSAD13)

ITEM CODE %1 REFERENCED ON DRESP1 ENTRY %2 WITH RTYPE = %3 IS INVALID FOR
ELEMENT TYPE %4 (%5).

User action: CHECK THE SPECIFIED ITEM CODE WITH THOSE LISTED IN
CHAPTER 6 OF THE MSC NASTRAN QUICK REFERENCE GUIDE.

5626.1 *** USER FATAL MESSAGE 5626 (DSAD58)

ITEM CODE %1 REFERENCED ON DRESP1 ENTRY %2 IS INVALID FOR ERP

User action: CHECK THE SPECIFIED ITEM CODE WITH THOSE LISTED IN
CHAPTER 6 OF THE MSC NASTRAN QUICK REFERENCE GUIDE.

5627.0 *** USER FATAL MESSAGE 5627 (DSAD17)

MORE THAN FIFTY INVALID ITEM CODES HAVE BEEN DETECTED

5628.0 *** USER FATAL MESSAGE 5628 (DSAD17)

DRESP1 ID = %1 IS FOR RTYPE = %2 AND ELEMENT ID = %3.
THE RESPONSE COULD NOT BE FOUND, EITHER BECAUSE THE ELEMENT DOES NOT
EXIST OR BECAUSE THE RESPONSE TYPE IS NOT AVAILABLE FOR THE ASSOCIATED ELE-
MENT TYPE.

5629.0 *** USER FATAL MESSAGE 5629 (DSAD1C)

Main Index
 MSC Nastran Error Messages 535
Errors 5000 - 5999

THERE ARE DRESP1 ENTRIES FOR RESPONSE TYPE = %1 BUT THERE ARE NO CORRE-
SPONDING OUTPUT RESPONSES.

User action: CHECK THAT THE %2 ID'S LISTED ON THE DRESP1 ENTRIES EXIST.

5629.1 *** USER FATAL MESSAGE 5629 (DSAD1C)

THERE ARE DRESP1 ENTRIES FOR RESPONSE TYPE = %1 BUT THERE ARE NO CORRE-
SPONDING OUTPUT RESPONSES.

5630.0 *** USER INFORMATION MESSAGE 5630 (STOCHAST)

Randomization of real values on all %1 is performed with CDF=%2, CoV=%3 and M=%4.

5631.0 *** USER FATAL MESSAGE 7056 (STOCHAS0)

STOCHAS ENTRY %1 SPECIFIES A CDF NAME = %2 THAT IS NOT VALID.

5902.0 *** USER FATAL MESSAGE 5902. (DSAR)

ZERO OR NEGATIVE TIME STEP ENCOUNTERED.

5903.0 *** USER FATAL MESSAGE 5903. (DSAR)

INCONSISTENT DATA DETECTED FOR UG AND TOLA

User action: VERIFY NUMBER OF SOLUTION VECTORS IN UG ARE THREE TIMES THE
NUMBER OF TIME STEPS IN TOLA.

5903.1 *** USER WARNING MESSAGE 5903. (ERPCALC)

Main Index
 536 MSC Nastran Error Messages
Errors 5000 - 5999

INCONSISTENT COMBINATION OF INPUT FOR CASE CONTROL, DISPLACEMENTS AND

OUTPUT FREQUENCIES/TIMESTEPS.
NUMBER OF SUBCASES = %1, NUMBER OF DISPLACEMENT COLUMNS = %2, NUMBER OF
FREQ/TIMES = %3

User action: POSSIBLE DMAP ERROR

LET NSUBC = NUMBER OF SUBCASES INPUT ON CASECC DATABLOCK,
NUG = NUMBER OF COLUMNS FOR THE UG MATRIX,
NOUT = NUMBER OF OUTPUT FREQUENCIES OR TIMES STORED IN OUTPUT LIST DATA
BLOCK
FOR FREQUENCY RESPONSE, VERIFY THAT NUG = NSUBC * NOUT
FOR TRANSIENT RESPONSE, VERIFY THAT NUG = NSUBC * NOUT * 3

5904.0 *** SYSTEM WARNING MESSAGE 5904. (VNORM)

EMPTY SET, UNION OF VNORM SET, ERP SET AND UNIT NORMAL SET, FOR OUTPUT.
VNORM MODULE TERMINATED.

User action: USE ALL FOR VNORM, INCREASE PARAM,SNORM VALUE AND/OR REMOVE
ERP, IF ANY, ON VNORM.

Main Index
 MSC Nastran Error Messeges 537
Errors 6000 - 6999

Errors 6000 - 6999

6001.0 *** SYSTEM FATAL MESSAGE 6001 (RSTART)

ERROR IN OPENING THE DATABASE TRANSACTION FILE (DBRQUE). GINO FILE NAME =
%1

User action: SEND THIS RUN TO HEXAGON AB.

6002.0 *** SYSTEM WARNING MESSAGE 6002 (ZREAD)

FOR DATA BLOCK=%1, TYPE = UNSTRUCTURED, MATRIX, OR VECTOR IS NOT SUP-
PORTED.

Programmer action: USE PROPER ROUTINES.

6002.1 *** USER FATAL MESSAGE 6002 (RSTART)

RESTART DOES NOT SUPPORT TYPE = UNSTRUCTURED, FOUND ON DATA BLOCK %1

6003.0 *** USER FATAL MESSAGE 6003 (RSTART)

TOO MANY INPUT DATA BLOCKS STARTING WITH BLOCK %1

User information: There are two possible input modes into the RESTART module. In neither of them are
all three of the input data block slots to be filled.

6004.0 *** SYSTEM WARNING MESSAGE 6004 (TMALOC)

DATA BLOCK %1 IS NOT DEFINED IN THE NDDL

6006.0 *** USER FATAL MESSAGE 6006 (DTIIN)

INPUT DATA BLOCK %1 - GINO FILE NUMBER %2 NOT FOUND

6007.0 *** USER WARNING MESSAGE 6007 (DTIIN) -

OUTPUT DATA BLOCK %1 - GINO FILE NUMBER %2 ALREADY APPEARS AS A DTIIN OUT-
PUT BLOCK ON THIS CARD

6007.1 *** USER WARNING MESSAGE 6007 (DMIIN) -

Main Index
 538 MSC Nastran Error Messeges
Errors 6000 - 6999

OUTPUT DATA BLOCK %1 - GINO FILE NUMBER %2 ALREADY APPEARS AS A DMIIN OUT-
PUT BLOCK ON THIS CARD
6009.0 *** SYSTEM FATAL MESSAGE 6009 (IFP1CP)
THE NUMBER OF UNIQUE CASE CONTROL PARAMETERS EXCEEDS THE CURRENT
LIMIT OF %1.

User action: REDUCE THE NUMBER OF CASE CONTROL PARAMETERS

6010.0 *** SYSTEM FATAL MESSAGE 6010 (PVTCCP)

THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE TABLE (PVT) HAS BEEN
EXCEEDED.

User information: THE PARAMETER VALUE DEFAULT TABLE (PVTS)WAS BEING MERGED
INTO THE PARAMETER VALUE TABLE (PVT).
THE MAXIMUM SIZE OF THE PVT TABLE IS %1 WORDS.

User action: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL
PARAMETERS

6010.1 *** SYSTEM FATAL MESSAGE 6010 (IFPCCP)

THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE DEFAULT TABLE (PVTS)
HAS BEEN EXCEEDED.

User information: THE NDDL PARAMETER DEFAULT VALUES WERE BEING %1 INTO THE
PARAMETER VALUE DEFAULT TABLE (PVTS).
THE MAXIMUM SIZE OF THE PVTS TABLE IS %2 WORDS.

User action: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL
PARAMETERS

6010.2 *** SYSTEM FATAL MESSAGE 6010 (IFPCCP)

THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE DEFAULT TABLE (PVTS)
HAS BEEN EXCEEDED.

User information: THE CASE CONTROL PARAMETERS WERE BEING %1 INTO THE PARAME-
TER VALUE DEFAULT TABLE (PVTS).

Main Index
 MSC Nastran Error Messeges 539
Errors 6000 - 6999

THE MAXIMUM SIZE OF THE PVTS TABLE IS %2 WORDS.

User action: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL
PARAMETERS

6010.3 *** SYSTEM FATAL MESSAGE 6010 (IFPCCP)

THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE DEFAULT TABLE (PVTS)
HAS BEEN EXCEEDED.

User information: THE BULK DATA PARAMETERS WERE BEING LOADED INTO THE PARAM-
ETER VALUE DEFAULT TABLE (PVTS).
THE MAXIMUM SIZE OF THE PARAMETER VALUE DEFAULT TABLE IS %1 WORDS.

User action: REDUCE THE NUMBER OF UNIQUE BULK DATA, CASE CONTROL, AND NDDL
PARAMETERS

6011.0 *** USER FATAL MESSAGE 6011 (IPVDFT)

THE TYPE OF DMAP PARAMETER %1 DEFINED IN THE MAIN SUBDMAP DIFFERS FROM
THE TYPE DETERMINED FROM THE TYPE OF THE VALUE SPECIFIED ON THE PARAM
ENTRY.

User information: MAIN SUBDMAP TYPE IS %2 AND THE PARAMS VALUE TYPE IS %3.

User action: CHECK THE TYPE OF THE VALUE ON THE PARAM ENTRY.

6011.1 *** USER FATAL MESSAGE 6011 (IFPCCP)

THE TYPE OF DMAP PARAMETER %1 DEFINED IN THE NDDL DIFFERS FROM THE TYPE
DETERMINED FROM THE TYPE OF THE VALUE SPECIFIED ON THE PARAM ENTRY.

User information: The NDDL TYPE IS %2 AND THE PARAMS VALUE TYPE IS %3.

User action: CHECK THE TYPE OF THE VALUE ON THE PARAM ENTRY.

6012.0 *** SYSTEM FATAL MESSAGE 6012 (IFPDRV)

Main Index
 540 MSC Nastran Error Messeges
Errors 6000 - 6999

THE MAXIMUM ALLOWABLE SIZE OF THE PARAMETER VALUE TABLE (PVT) HAS BEEN
EXCEEDED.

User information: THE PVT TABLE WAS BEING CREATED FROM BULK DATA PARAM
ENTRIES.
THE MAXIMUM SIZE OF THE PVT TABLE IS %1 WORDS.

User action: REDUCE THE NUMBER OF UNIQUE BULK DATA PARAMETERS.

6013.0 *** SYSTEM FATAL MESSAGE 6013 (IFSEQU)
THE EQUATION INDEX TABLE HAS EXCEEDED THE MAXIMUM NUMBER OF EQUA-
TIONS ALLOWED FOR THE %1 BLOCK.

User information: THE MAXIMUM NUMBER OF EQUATIONS IS: 0.5 * SYSBUF - 1 EQUA-
TIONS, OR %2 IN THIS RUN

6014.0 *** SYSTEM WARNING MESSAGE 6014 (MODTRL)

UNABLE TO WRITE TRAILER FOR FILE %1

6015.0 *** SYSTEM FATAL MESSAGE 6015,

TABLE ID %1 NOT FOUND. PREMAT TABLE LOGIC ERROR ...

6016.0 *** USER INFORMATION MESSAGE 6016 (PRTPRM)

NO PARAMETERS EXIST IN THE VPS OF REQUESTED SUBDMAP

6017.0 *** USER INFORMATION MESSAGE 6017 (PRTPRM)

SUBDMAP %1 IS NOT IN CURRENT SUBDMAP CALLING CHAIN.

6018.0 *** USER INFORMATION MESSAGE 6018 (PRTPRM)

PARAMETER NAMED %1 IS NOT IN THE VPS OF SUBDMAP %2.

6019.0 *** USER INFORMATION MESSAGE 6019 (PRTPRM)

THE SECOND PRTPARM PARAMETER VALUE - %1 - IS IMPROPER.

6020.0 *** USER INFORMATION MESSAGE 6020 (PRTPRM)

THE PRTPARM DIAGNOSTIC %1 IS NOT IN TABLE.

6021.0 *** USER INFORMATION MESSAGE 6021 (PVT)

Main Index
 MSC Nastran Error Messeges 541
Errors 6000 - 6999

NULL INPUT DATA BLOCKS ARE BEING USED FOR PVT.

6022.0 *** USER WARNING MESSAGE 6022 (PVT)

AN UNEXPECTED END-OF-FILE ENCOUNTERED PROCESSING INPUT DATA BLOCK 102.

User information: IT WILL BE PROCESSED AS IF PURGED.

6023.0 *** USER WARNING MESSAGE 6023 (PVT)

AN ATTEMPT WAS MADE TO REDEFINE THE TYPE OF THE BULK DATA OR CASE CON-
TROL PARAMETER %1.

User information: THE ATTEMPT AT REDEFINITION IS IGNORED.

6024.0 *** SYSTEM FATAL MESSAGE 6024 (PVT)

THE PARAMETER VARIABLE TABLE - PVT - HAS OVERFLOWED

User action: REDUCE NUMBER OF BULK DATA AND/OR CASE CONTROL PARAM CARDS.

6025.0 *** SYSTEM FATAL MESSAGE 6025 (PVT)

INSUFFICIENT OPEN CORE TO READ CASE CONTROL DATA

6027.0 *** USER WARNING MESSAGE 6027 (XEQUIV)

ATTEMPT TO EQUIVALENCE PRIMARY DATABLOCK %1, WHICH DOES NOT EXIST.

User information: This warning message can occur for many reasons. It has been seen in user DMAPs or
DMAP alters where datablocks are being stored permanently on the database. If an EQUIV is done on one
of these stored datablocks, and the qualifiers for that datablock are not set, then this message can occur. A
more confusing case occurs when all qualifiers for a permanent datablock are not TYPEd as NDDL param-
eters, or are not passed into the current subDMAP. When an EQUIV is attempted, the UWM 6027 can
occur. Be sure that ALL qualifiers that were set when the primary was stored are still set when the equiva-
lence is attempted.

6028.0 *** SYSTEM WARNING MESSAGE 6028 (XMESAG)

PARAMETER NUMBER %1 WAS NOT FOUND IN THE VPS

6029.0 *** SYSTEM FATAL MESSAGE 6029 (XQALVL)

Main Index
 542 MSC Nastran Error Messeges
Errors 6000 - 6999

ATTEMPT TO LOAD FUNCTION NAME FROM INVALID ADDRESS

Programmer information: ADDRESS POINTER = %1

6029.1 *** SYSTEM FATAL MESSAGE 6029 (XQALVL)

ATTEMPT TO LOAD VALUE FROM NON-EXISTENT VPS VARIABLE

Programmer information: VPS ADDRESS POINTER = %1

6030.0 *** SYSTEM FATAL MESSAGE 6030 (XQASVL)
ATTEMPT TO STORE (STOR) NON-TEMPORARY VALUE IN TEMPORARY STORAGE ARRAY

Programmer information: TEMPORARY ADDRESS POINTER = %1

6031.0 *** SYSTEM FATAL MESSAGE 6031 (XQASVL)

UNABLE TO STORE (STOR) TEMPORARY VALUE IN TEMPORARY STORAGE ARRAY

Programmer information: TEMPORARY ADDRESS POINTER = %1

6032.0 *** SYSTEM FATAL MESSAGE 6032 (XQALVL)

UNDEFINED OPERAND DETECTED IN INSTRUCTION %1

Programmer information: OPERAND POINTER = %2

6033.0 *** SYSTEM FATAL MESSAGE 6033 (XQALVL)

ATTEMPT BY INSTRUCTION %1 TO OPERATE ON NON-EXISTENT VPS VARIABLE

6033.1 *** SYSTEM FATAL MESSAGE 6033 (XQALVL)

ATTEMPT BY INSTRUCTION %1 TO OPERATE ON NON-EXISTENT TEMPORARY VARI-
ABLE

6034.0 *** SYSTEM FATAL MESSAGE 6034 (XQAROS)

ATTEMPT BY INSTRUCTION %1 TO PERFORM LOGICAL OPERATION ON NON-LOGICAL
VALUE

6034.1 *** SYSTEM FATAL MESSAGE 6034 (XQAROS)

Main Index
 MSC Nastran Error Messeges 543
Errors 6000 - 6999

ATTEMPT BY INSTRUCTION %1 TO PERFORM RELATIONAL OPERATION ON LOGICAL

VALUE

6034.2 *** SYSTEM FATAL MESSAGE 6034 (XQAROS)

ATTEMPT BY INSTRUCTION %1 TO PERFORM CHARACTER OPERATION ON NON-
CHARACTER VALUE

6034.3 *** SYSTEM FATAL MESSAGE 6034 (XQAROS)

ATTEMPT BY INSTRUCTION %1 TO PERFORM ARITHMETIC OPERATION ON NON-
NUMERIC VALUE
6035.0 *** SYSTEM FATAL MESSAGE 6035 (XQAROS)
ATTEMPT TO RAISE NEGATIVE %1 BASE TO A FRACTIONAL EXPONENT

6036.0 *** SYSTEM FATAL MESSAGE 6036 (XQAROS)

ATTEMPT TO DIVIDE BY %1 ZERO

6036.1 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 6036 (EVLMSG)

DIVIDE BY ZERO WAS DETECTED

6037.0 *** SYSTEM FATAL MESSAGE 6037 (XQAROS)

ATTEMPT BY INSTRUCTION %1 TO COMPARE COMPLEX EXPRESSIONS WITH RELA-
TIONAL OPERATOR

6038.0 *** SYSTEM FATAL MESSAGE 6038 (XQAROS)

INVALID BLANK COMMON POINTER.

Programmer information: BLANK COMMON POINTER VALUE = %1

6039.0 *** SYSTEM FATAL MESSAGE 6039 (XQALVL)

ATTEMPT BY INSTRUCTION %1 TO ASSIGN VALUE TO NON-VPS VARIABLE

6040.0 *** SYSTEM FATAL MESSAGE 6040 (XQAROS)

UNABLE TO ASSIGN (==) VALUE TO SPECIFIED VPS/DATABASE VARIABLE

6041.0 *** SYSTEM FATAL MESSAGE 6041 (XQALVL)

Main Index
 544 MSC Nastran Error Messeges
Errors 6000 - 6999

ATTEMPT BY INSTRUCTION %1 TO LOAD VALUE OF A NON-EXISTENT VPS OR DATA-

BASE VARIABLE INTO THE ARGUMENT STORAGE ARRAY

Programmer information: VPS/DATABASE POINTER = %2

6041.1 *** SYSTEM FATAL MESSAGE 6041 (XQALVL)
ATTEMPT BY INSTRUCTION %1 TO LOAD VALUE OF A NON-EXISTENT TEMPORARY
VARIABLE INTO THE ARGUMENT STORAGE ARRAY

Programmer information: TEMPORARY POINTER VALUE = %2

6041.2 *** SYSTEM FATAL MESSAGE 6041 (XQALVL)

ATTEMPT BY INSTRUCTION %1 TO LOAD VALUE FROM AN INVALID ADDRESS INTO
THE ARGUMENT STORAGE ARRAY

Programmer information: ADDRESS VALUE = %2

6042.0 *** SYSTEM FATAL MESSAGE 6042 (XQAROS)

ATTEMPT TO PERFORM %1 OPERATION %2 BETWEEN %3 AND %4 DATA

6043.0 *** SYSTEM FATAL MESSAGE 6043 (XQAROS)

UNABLE TO EVALUATE EXPRESSIONS OF OSCAR TYPE %1

6044.0 *** SYSTEM FATAL MESSAGE 6044 (XQASVL)

ATTEMPT BY INSTRUCTION %1 TO STORE A NON-ARGUMENT VALUE IN THE ARGU-
MENT STORAGE ARRAY

Programmer information: ARGUMENT POINTER VALUE = %2

6045.0 *** SYSTEM FATAL MESSAGE 6045 (XQASVL)

UNABLE TO STORE ARGUMENT VALUE IN ARGUMENT STORAGE ARRAY DURING %1
INSTRUCTION

6046.0 *** SYSTEM FATAL MESSAGE 6046 (XQFUNC)

ATTEMPT TO OPERATE ON NON-EXISTENT FUNCTION ARGUMENT

6047.0 *** USER FATAL MESSAGE 6047 (XQFNC2)

ILLEGAL %1 ARGUMENT GIVEN FOR %2 FUNCTION.

Main Index
 MSC Nastran Error Messeges 545
Errors 6000 - 6999

6048.0 *** SYSTEM FATAL MESSAGE 6048 (XQFNC7)

SQRT FUNCTION ATTEMPTED ON NEGATIVE %1 VALUE.

6048.1 *** SYSTEM FATAL MESSAGE 6048 (XQFNC5)

MOD FUNCTION ATTEMPTED ON ZERO %1 VALUE

6048.2 *** SYSTEM FATAL MESSAGE 6048 (XQFNC5)

COMMON LOGARITHM FUNCTION ATTEMPTED ON INVALID %1 VALUE.

6048.3 *** SYSTEM FATAL MESSAGE 6048 (XQFNC5)

USER-DEFINED BASE LOGARITHM FUNCTION ATTEMPTED ON INVALID %1 VALUE.

6048.4 *** SYSTEM FATAL MESSAGE 6048 (XQFNC5)

NATURAL LOGARITHM FUNCTION ATTEMPTED ON INVALID %1 VALUE.

6048.5 *** SYSTEM FATAL MESSAGE 6048 (XQFNC2)

ARC HYPERBOLIC SINE FUNCTION ATTEMPTED ON INVALID %1 VALUE.

6048.6 *** SYSTEM FATAL MESSAGE 6048 (XQFNC2)

ARC HYPERBOLIC COSINE FUNCTION ATTEMPTED ON INVALID %1 VALUE.

6048.7 *** SYSTEM FATAL MESSAGE 6048 (XQFNC1)

ARC SINE FUNCTION ATTEMPTED ON INVALID %1 VALUE.

6048.8 *** SYSTEM FATAL MESSAGE 6048 (XQFNC1)

ARC COSINE FUNCTION ATTEMPTED ON INVALID %1 VALUE.

6049.0 *** SYSTEM FATAL MESSAGE 6049 (XQFNC4)

NON-CHARACTER CONSTANT/VARIABLE FOUND, WHERE CHARACTER CONSTANT/
VARIABLE EXPECTED IN FUNCTION INDEXSTR.

6050.0 *** USER WARNING MESSAGE 6050

Main Index
 546 MSC Nastran Error Messeges
Errors 6000 - 6999

THE ATTEMPT TO WRITE VALUE INTO /SYSTEM/ CELL %1 HAS FAILED

User information: THE SYSTEM CELL NUMBER IS OUTSIDE THE VALID RANGE. THE %2
ATTEMPT IS IGNORED.

6050.1 *** USER WARNING MESSAGE 6050

THE ATTEMPT TO READ VALUE FROM /SYSTEM/ CELL %1 HAS FAILED

User information: THE SYSTEM CELL NUMBER IS OUTSIDE THE VALID RANGE. THE %2
ATTEMPT IS IGNORED.

6051.0 *** USER WARNING MESSAGE 6051

THE ATTEMPT TO TURN ON DIAG %1 HAS FAILED

User information: THE DIAG REQUESTED IS OUTSIDE THE VALID RANGE OF DIAGS. THE
%2 ATTEMPT IS IGNORED.

6051.1 *** USER WARNING MESSAGE 6051 (XQFNC3)

THE ATTEMPT TO TURN OFF DIAG %1 HAS FAILED

User information: THE DIAG REQUESTED IS OUTSIDE THE VALID RANGE OF DIAGS. THE
%2 ATTEMPT IS IGNORED.

6052.0 *** USER WARNING MESSAGE 6052

INVALID DIAG WORD WRITE REQUEST FOR DIAG WORD %1

User information: ONLY 2 DIAG WORDS EXIST IN THE PROGRAM

WORD 1 - DIAGS 1 THROUGH 32 (ASSUMED WHEN ERROR OCCURS)
WORD 2 - DIAGS 33 THROUGH 64

6052.1 *** USER WARNING MESSAGE 6052 (XQFNC4)

INVALID DIAG WORD READ REQUEST FOR DIAG WORD %1

User information: ONLY 2 DIAG WORDS EXIST IN THE PROGRAM

WORD 1 - DIAGS 1 THROUGH 32 (ASSUMED WHEN ERROR OCCURS)
WORD 2 - DIAGS 33 THROUGH 64

Main Index
 MSC Nastran Error Messeges 547
Errors 6000 - 6999

6059.0 *** SYSTEM FATAL MESSAGE 6059 (DIOMSG)

NO ERROR MESSAGE EXISTS FOR DIOMSG INTERNAL CODE NUMBER %1 CALLED FROM
%2

6060.0 *** USER FATAL MESSAGE 6060 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
DATA BASE UNIT %3 IS OUT OF RANGE.

6061.0 *** USER WARNING MESSAGE 6061 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
DATA BASE %3 NOT OPENED, NO ACTION TAKEN.

6061.1 *** USER WARNING MESSAGE 6061 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
DATA BASE %3 OPENED FOR READONLY, NO ACTION TAKEN.

6061.2 *** USER WARNING MESSAGE 6061 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
THE FOLLOWING LOGICAL FILE WAS LEFT OPEN AT DATABASE CLOSE, FORCE CLOS-
ING %3

6061.3 *** USER WARNING MESSAGE 6061 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
THE FOLLOWING LOGICAL FILE WAS OPEN AT THE TIME A PURGE WAS REQUESTED
NO PURGE ACTION WAS TAKEN FOR LOGICAL FILE %3

6062.0 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
BLOCK REQUEST FROM DATA BASE UNIT %3, WHICH IS CLOSED.

6062.1 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
BLOCK %3 REQUESTED FROM DATA BASE UNIT %4, WHICH IS OPEN FOR READONLY.

6062.2 *** SYSTEM FATAL ERROR 6062 (DBC)

Main Index
 548 MSC Nastran Error Messeges
Errors 6000 - 6999

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2

INSUFFICIENT SPACE ALLOCATED FOR DATA BASE UNIT %3.

6062.3 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
OVERFLOW OF DICTIONARY PRIMARY INDEX FOR DATABASE UNIT %3.

User information: THE NUMBER OF ENTRIES FOR AN OBJECT EXCEEDED ITS CAPACITY
WITH THE DEFAULT STORAGE METHOD.

User action: FOR MARGINAL OVERFLOW, INCREASE RECL ON THE FMS ASSIGN DBC
STATEMENT OR IF LARGE CAPACITY IS REQUIRED, USE THE NASTRAN STATEMENT
WITH EITHER DBCFACT=2 OR DBCFACT=4 TO CHANGE THE STORAGE ALGORITHM.

6062.4 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
BUFFER LOCKING PROBLEMS ON POOL FOR DATA BASE UNIT %3, BLOCK %4
POSSIBLE MULTIPLE LOGICAL FILES ASSIGNED TO THE SAME DATA RELATION.

6062.5 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
FREE BUFFER POOL SPACE EXHAUSTED, REDUCE NUMBER OF LOGICAL FILES OR
INCREASE SPACE.

6062.6 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
LOGIC ERROR, DICTIONARY PRIMARY BLOCK ON DEAD CHAIN FOR DATA BASE %3.

6062.7 *** SYSTEM FATAL ERROR 6062 (DBC)

Main Index
 MSC Nastran Error Messeges 549
Errors 6000 - 6999

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2

UNABLE TO FIND ENTRY %3 ON SI BLOCK %4, WHICH HAD BEEN PREVIOUSLY FOUND
DISK ERROR OR MEMORY OVER WRITE ASSUMED.

6062.8 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
UNABLE TO FIND ENTRY %3 ON PI BLOCK %4, WHICH HAD BEEN PREVIOUSLY FOUND
DISK ERROR OR MEMORY OVER WRITE ASSUMED.

6062.9 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
PROGRAMMING ERROR. LENGTH OF DICTIONARY ENTRIES CHANGED, BUT CLOSGR
NOT INFORMED.

6062.10 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
DICTIONARY OR DICTIONARY NAME FOR FILE %3 CORRUPTED. UNABLE TO CLOSE
DATA BLOCK.

6062.11 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
LOGICAL DATA BASE %3 IS MISSING DDL WITH SWAP CONDITION %4.

6062.12 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
LOGICAL DATA BASE %3 IS MISSING THE BLOCK NUMBER FOR DDL VERSION %4.

6062.13 *** SYSTEM FATAL ERROR 6062 (DBC)

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
OBJECT %3 ENTRY LENGTH AND DATA DEFINITION IS INCONSISTENT FOR HETEROG-
ENOUS OPERATIONS. TRANSMIT AND RECEIVE MUST BE USED TO MIGRATE XDB
BETWEEN PLATFORMS.

6062.14 *** SYSTEM FATAL ERROR 6062 (DBC)

Main Index
 550 MSC Nastran Error Messeges
Errors 6000 - 6999

*** DIOMSG ERROR MESSAGE %1 FROM SUBROUTINE %2

LOGICAL DATA BASE %3 DDL LENGTH LESS THAN ENTRY LENGTH.
DDL LENGTH = %4, ENTRY LENGTH = %5

6063.0 *** SYSTEM WARNING MESSAGE 6063 (DBCMSG)

NO ERROR MESSAGE EXISTS FOR DBCMSG INTERNAL CODE NUMBER %1 CALLED
FROM %2.

6064.0 *** USER WARNING MESSAGE 6064 (DBC)

*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 %3 ELEMENT %4 HAS BEEN
UPDATED.

6064.1 *** SYSTEM WARNING MESSAGE 6064 (DBC)

*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 %3 IS AN INVALID OPTION
OR KEYWORD.
6064.2 *** SYSTEM WARNING MESSAGE 6064 (DBC)
*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2
FORTRAN LOGICAL UNIT %3 HAS NOT BEEN ASSIGNED.

6064.3 *** SYSTEM WARNING MESSAGE 6064 (DBC)

*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2
FORTRAN LOGICAL UNIT %3 IS NOT DEFINED AS A DBC MODULE DATA BASE UNIT.

6064.4 *** SYSTEM WARNING MESSAGE 6064 (DBC)

*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2
%3 PROPERTY %4 HAS BEEN UPDATED.

6064.5 *** SYSTEM WARNING MESSAGE 6064 (DBC)

*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2
COORDINATE SYSTEM TRANSFORMATION %3 HAS BEEN UPDATED.

6064.6 *** SYSTEM WARNING MESSAGE 6064 (DBC)

*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2
COORDINATE SYSTEM TRANSFORMATION %3 HAS BEEN UPDATED FOR FIELD %4, THE
ORIGINAL VALUE %5 IS CONVERTED TO %6, ERROR IS %7.
TO SUPPRESS THIS MESSAGE, SET DBCTOLE of MDLPRM TO A VALUE LARGER THAN %7.

Main Index
 MSC Nastran Error Messeges 551
Errors 6000 - 6999

6064.7 *** SYSTEM WARNING MESSAGE 6064 (DBC)

*** DBCMSG WARNING MESSAGE %1 FROM SUBROUTINE %2 %3 ELEMENT %4 HAS BEEN
UPDATED FOR FIELD %5, THE ORIGINAL VALUE %6 IS CONVERTED TO %7, ERROR IS
%8.
TO SUPPRESS THIS MESSAGE, SET DBCTOLE of MDLPRM TO A VALUE LARGER THAN %8.

6065.0 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
UNABLE TO OPEN OUTPUT RELATION %3 RETURN CODE =%4.

6065.1 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
PREMATURE END OF FILE ENCOUNTERED READING ECT.

6065.2 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
ELEMENT %3 GRID POSITION %4 CONTAINS AN INVALID INTERNAL INDEX.
6065.3 *** SYSTEM WARNING MESSAGE 6065 (DBC)
*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
MISSING %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6.

6065.4 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
BAD TRAILER FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6.

6065.5 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
INCONSISTENT GEOMETRY TRAILERS DETECTED FOR SEID %3, DBSET %4.

6065.6 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
INSUFFICIENT MEMORY TO PROCESS RELATIONAL REQUIREMENTS.

6065.7 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
OPEN FAILURE FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6.

Main Index
 552 MSC Nastran Error Messeges
Errors 6000 - 6999

6065.8 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
PREMATURE EOF FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6.

6065.9 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
PREMATURE EOR FOR %3 LOGICAL FILE %4 FOR SEID %5, DBSET %6.

6065.10 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
DATA BASE PURGE PROBLEM FOR RELATION %3 RETURN CODE = %4.

6065.11 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
DATA BASE WRITE RELATION PROBLEM FOR %3 RETURN CODE = %4.

6065.12 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
UNABLE TO OPEN INPUT RELATION %3 RETURN CODE = %4.

6065.13 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
SEQUENTIAL READ PROBLEMS FOR RELATION %3 RETURN FLAGS = %4.

6065.14 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
ELEMENT %3 WAS A %4 AND IS CURRENTLY A %5
UPDATE MODE DOES NOT ALLOW FOR ELEMENTS TO CHANGE TYPES.

User action: IF YOU DO NOT WANT TO APPEND THE CURRENT RESULTS TO THE PREVI-
OUS RESULTS THEN DELETE THE OLD .XDB FILE.

6065.15 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
MEMORY LOAD PROBLEM FOR %3 FOR SEID %4, DBSET %5.

Main Index
 MSC Nastran Error Messeges 553
Errors 6000 - 6999

6065.16 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
LIST ALIGNMENT PROBLEMS PROCESSING %3 FOR SEID %4, DBSET %5.

6065.17 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
EXTERNAL GRID ID %3 DOES NOT MEET UPDATE ASSUMPTIONS, CHECK MODEL
BEFORE PROCEEDING.

6065.18 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
INVALID OFP FILE FORMAT CODE DETECTED, WANTED %3, ENCOUNTERED %4.

6065.19 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
SOLUTION APPROACH CODE %3 IS NOT SUPPORTED.

6065.20 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
DATA BASE READ RELATION PROBLEM FOR %3 RETURN CODE = %4.

6065.21 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
OUTPUT LIST SYNCHRONIZATION PROBLEM FOR %3 VALUE = %4, POSITION = %5.

6065.22 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
SORT-2 STATIC SOLUTION RECOVERY IS NOT SUPPORTED.

6065.23 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
FORM UPDATE FOR RELATION %3 INVALID, OLD FORM %4 NEW FORM %5.

6065.24 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
INVALID MODE DETECTED FOR OPTION %3, MODE = %4.

Main Index
 554 MSC Nastran Error Messeges
Errors 6000 - 6999

6065.25 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
LIST AREA EXCEEDED, CURRENT SIZE IS 500 TERMS.

6065.26 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
CONFLICT DETECTED WITH SEID AS PARAMETER AND PATH QUALIFIER PARAMETER IS
%3, PATH QUALIFIER IS %4.

6065.27 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
RELATION %3 HAS LENGTHENED FROM ASSUMED DEFINITION.

6065.28 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
EXTERNAL ELEMENT IDENTIFICATION %3 CAN NOT BE LOCATED IN EQEXIN TABLE.

6065.29 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
P-ELEMENT TYPE %3 IS UNKNOWN.

6065.30 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
P-ELEMENT TYPE %3 LENGTH HAS CHANGED ASSUMED VALUE.

6065.31 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
CONVECTIVE COORDINATE SYSTEMS ARE NOT SUPPORTED.

6065.32 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
AN UNKNOWN ELEMENT TYPE HAS BEEN ENCOUNTERED.

6065.33 *** SYSTEM WARNING MESSAGE 6065 (DBC)

Main Index
 MSC Nastran Error Messeges 555
Errors 6000 - 6999

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2

ELEMENT %3 WAS PREVIOUSLY %4 AND IS CURRENTLY A %5
THE DBC MODULES ASSUMPTIONS ARE UNIQUE ELEMENT IDENTIFICATIONS WITHIN
A SUPERELEMENT OR RESIDUAL STRUCTURE.

6065.34 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
OUTPUT LIST PROCESSING IS NOT SUPPORTED FOR ACCESS APPROACH %3.

6065.35 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
31 BIT ACCESS KEY WILL BE EXCEEDED, GRID/ELEMENT INDEX %3 QUALIFIER FACTOR
%4.

User action: SUPPLY PARAM,DBCDIAG,4 TO DETERMINE DBC TRANSLATIONAL FAILURE

POINT.
THEN CONTACT MSC NASTRAN REPRESENTATIVE FOR POSSIBLE AVOIDANCE.

6065.36 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
OUTPUT LIST DOES NOT MATCH EXISTING IN THE DATABASE, MERGE/RESTART OPER-
ATION IMPOSSIBLE.
6065.37 *** SYSTEM WARNING MESSAGE 6065 (DBC)
*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
THE CURRENT OUTPUT LIST LENGTH =%3 EXCEEDS PRESET LIST FACTOR OF %4.

User action: CHECK RC FILE FOR DBCFACT (SYSTEM(274)=1) USING PRE V70.5 TRANSLA-
TION CONVENTIONS.

6065.38 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
ELEMENT %3, SIL %4, CAN NOT BE LOCATED IN CONNECTION LIST, ELEMENT
IGNORED.

6065.39 *** SYSTEM WARNING MESSAGE 6065 (DBC)

Main Index
 556 MSC Nastran Error Messeges
Errors 6000 - 6999

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2

THE AEROELASTIC CONFIGURATION NAME %3 CAN NOT BE RESOLVED.

6065.40 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
THE AEROELASTIC CONFIGURATION NAME %3 DID NOT MATCH PREVIOUSLY STORED
AT PATH %4.

6065.41 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
THE MATRICES SUPPLIED DO NOT HAVE CONFORMABLE SIZES; ROWS COLUMNS OR
PRECISION.

6065.42 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
MATRIX ROW CONSISTENCY CHECK FALUIRE; MATRIX %3 TABLE %4.

6065.43 *** SYSTEM WARNING MESSAGE 6065 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
MATRIX COLUMN CONSISTENCY CHECK FALUIRE; MATRIX %3 TABLE %4.

6066.0 *** SYSTEM WARNING MESSAGE 6066 (DBC)

*** DBCMSG ERROR MESSAGE %1 FROM SUBROUTINE %2
THE DBC MODULE HAS BEEN TERMINATED BECAUSE OF THE ABOVE FATAL DBC
ERROR.

User information: SUBSEQUENT DBC CALLS WILL NOT BE EXECUTED, AND THE DATA-
BASE CONVERSION IS INCOMPLETE.

6067.0 *** USER FATAL MESSAGE 6067 (IFS3P)

MAXIMUM LIMIT OF 40 PLIES EXCEEDED ON THE PSOLIDL BULK DATA ENTRY PID = %1

User action: CHECK AND MODIFY THE PSOLIDL BULK DATA ENTRY

6069.0 *** SYSTEM FATAL MESSAGE 6069 (LFBSS)

Main Index
 MSC Nastran Error Messeges 557
Errors 6000 - 6999

SYMMETRIC LEFT HANDED FBS IS CALLED TO SOLVE A COMPLEX SINGLE OR DOUBLE

PRECISION SYSTEM WITH CHOLESKY FACTOR

System information: This option is not supported.

6070.0 *** SYSTEM FATAL MESSAGE 6070 (LFBSS)

ERROR IN READING THE FACTOR IN SYMMETRIC LEFT-HANDED FBS

6072.0 *** SYSTEM FATAL MESSAGE 6072 (LFBSU)

INCORRECT PIVOTING INSTRUCTIONS IN UNSYMMETRIC FACTOR DURING A LEFT-
HANDED FBS

System information: See the MSC NASTRAN Numerical Methods User's Guide.

6073.0 *** SYSTEM FATAL MESSAGE 6073 (LFBSU)

ERROR IN READING THE FACTOR IN UNSYMMETRIC LEFT-HANDED FBS

6074.0 *** SYSTEM FATAL MESSAGE 6074 (LFBTIM)

ERROR IN READING THE FACTOR IN LEFT-HANDED FBS

System information: See the MSC NASTRAN Numerical Methods User's Guide.

6080.0 *** USER WARNING MESSAGE 6080 (TMALOC)

Main Index
 558 MSC Nastran Error Messeges
Errors 6000 - 6999

THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY
DATABASE FOR:
MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL= %5
LOADING DEFAULT TIMING CONSTANTS DATA BLOCK FOR:
MACHINE = %6 CONFIG = %7 OPERASYS = %8 OPERALEV = %9 SUBMODEL= %10
MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECU-
TION

User action: ADD TIMEBLK TO DELIVERY FILE OR USE NASTRAN STATEMENT TO SPECIFY
THE MACHINE
(SEE CONFIGURATION AND OPERATION GUIDE FOR THE MACHINE ).
6080.1 *** USER WARNING MESSAGE 6080 (TMALOC)
THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY
DATABASE FOR:
MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL= %5
LOADING DEFAULT TIMING CONSTANTS DATA BLOCK FOR:
MACHINE = %6 CONFIG = %7 OPERASYS = %8 OPERALEV = %9 SUBMODEL= %10
MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECU-
TION

User action: ADD TIMEBLK TO DELIVERY FILE OR USE THE EMAS STATEMENT TO SPECIFY
THE MACHINE

(SEE MSC.EMAS INSTALLATION PROCEDURE).

*** USER WARNING MESSAGE 6080 (SETKRN)
THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY
DATABASE FOR:
ZERO TIMING CONSTANTS BEING USED MODULE TIMING ESTIMATES INACCURATE
6080.2 AND MAY CAUSE INEFFICIENT JOB EXECUTION

User action: ADD TIMEBLK TO DELIVERY FILE OR USE NASTRAN STATEMENT TO SPECIFY
THE MACHINE
(SEE CONFIGURATION AND OPERATION GUIDE FOR THE MACHINE).

6080.3 *** USER WARNING MESSAGE 6080 (SETKRN)

Main Index
 MSC Nastran Error Messeges 559
Errors 6000 - 6999

THE TIMING CONSTANTS DATA BLOCK TIMEBLK NOT FOUND ON THE DELIVERY
DATABASE FOR:
MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL = %5
MODULE TIMING ESTIMATES INACCURATE AND MAY CAUSE INEFFICIENT JOB EXECU-
TION

User action: ADD TIMEBLK TO DELIVERY FILE OR USE THE EMAS STATEMENT TO SPECIFY
THE MACHINE
(SEE MSC.EMAS INSTALLATION PROCEDURE).

6081.0 *** USER FATAL MESSAGE 6081 (TIMTS3)

VALUE OF P2 CANNOT BE LESS THAN 64

6082.0 *** USER FATAL MESSAGE 6082 (TIMTS7)

THE RETURNED TIME NEEDED TO DO THE TASK CANNOT BE EQUAL TO THE VALUE
ZERO.

User action: INCREASE THE VALUE OF P1 FOR TIMTS7

6082.1 *** USER FATAL MESSAGE 6082 (TIMTS3)

THE RETURNED TIME NEEDED TO DO THE TASK CANNOT BE EQUAL TO THE VALUE
ZERO.

User action: INCREASE THE VALUE OF P1 FOR TIMTS3

6083.0 *** USER FATAL MESSAGE 6083 (TIMTS4)

THE RETURNED TIME NEEDED TO DO THE TASK CANNOT BE EQUAL TO THE VALUE
ZERO.

User action: INCREASE THE VALUE OF P1 FOR TIMTS4

6084.0 *** SYSTEM FATAL MESSAGE 6084 (TIMTS5)

ERROR IN MPYAD METHOD SELECTION, MPYAD CALLED FORM WITHIN TIMTS5

User action: EXECUTION OF TIMTS5 IS OPTIONAL AND CAN BE DELETED FROM THE
TIMETEST RUN

Main Index
 560 MSC Nastran Error Messeges
Errors 6000 - 6999

6085.0 *** USER WARNING MESSAGE 6085 (SETKRN)

THE TIMING CONSTANTS DATA BLOCK TIMEBLK DOES NOT CONTAIN DATA FOR
DOT3 KERNELS FOR:
MACHINE = %1 CONFIG = %2 OPERASYS = %3 OPERALEV = %4 SUBMODEL =%5
NUMERICAL METHODS WHICH USE THESE KERNELS WILL NOT BE AVAILABLE

User action: ADD NEW TIMEBLK CONTAINING DOT3 DATA TO DELIVERY FILE
(SEE MSC NASTRAN MACHINE DEPENDENT DOCUMENTATION).

6127.0 *** USER FATAL MESSAGE 6127

*** MAT2 OR MAT9 CARD MAY NOT BE COMBINED WITH NLELAST TYPE ON MATS1.

6133.0 *** USER FATAL MESSAGE 6133 (DFMNRS/D)

SINGULAR MATRIX IN SPARSE DECOMPOSITION AT ROW = %1

User action: CHECK MODEL

User information:
This message is often followed by UFM 4645, UWM 4646, or UWM 4648.

6133.1 *** USER FATAL MESSAGE 6133

SINGULAR MATRIX IN SPARSE DECOMPOSITION

User action: CHECK MODEL

User information:
This message is often followed by UFM 4645, UWM 4646, or UWM 4648.

6134.0 *** USER FATAL MESSAGE 6134 (DFMNRS/D)

MATRIX IS NOT POSITIVE DEFINITE IN SPARSE DECOMPOSITION AT ROW = %1

User action: CHECK MODEL

User information:
This message is often followed by UFM 4645, UWM 4646, or UWM 4648.

Main Index
 MSC Nastran Error Messeges 561
Errors 6000 - 6999

6134.1 *** USER FATAL MESSAGE 6134

MATRIX IS NOT POSITIVE DEFINITE IN SPARSE DECOMPOSITION

User action: CHECK MODEL

User information:
This message may be issued if the FBS module is using a sparse method to solve factors which are not
decomposed by the sparse method. This message can also be caused by a compatibility or database integrity
problem.

6134.2 *** USER WARMING MESSAGE 6134

MAT2 MID=%1 MATRIX IS NOT POSITIVE DEFINITE

User action: IF MID4 MATRIX FOR A PSHELL, MATRIX DOES NOT NEED TO BE POSITIVE
DEFINITE.
OTHERWISE, CHECK MODEL

6134.3 *** USER FATAL MESSAGE 6134

MATRIX IS NOT POSITIVE DEFINITE IN ACMS METHOD AND CANNOT BE HANDLED
WITH NEW ACMS METHOD.

User action: TEST MODEL WITH LANCZOS TO SEE IF NEGATIVE EIGENVALUES EXIST.
THIS CAN OCCUR WITH BRAKE SQUEAL IN SOL 400 OR IF AUTOSPC IS NOT CORRECTLY
APPLIED IN SOL 400 LINEAR PERTURBATION.

6134.4 *** USER warning MESSAGE 6134

NUMERIC SINGULARITY ENCOUNTERED DURING COMPONENT SOLUTION.

Programmer information: LOCATION = %1 AND INFO = %2

6135.0 *** USER WARNING MESSAGE 6134 (DFMFRS/D)

Main Index
 562 MSC Nastran Error Messeges
Errors 6000 - 6999

MATRIX HAS NEGATIVE DIAGONAL OR 2 BY 2 PIVOT IN SPARSE CHOLESKY DECOMPOSI-

TION AT ROW = %1

User action: CHECK MODEL

User information:
This message is often followed by UFM 4645, UWM 4646, or UWM 4648.

6136.0 *** USER WARNING/FATAL MESSAGE 6136 (DFMNRS/D)

INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE CORE BY %1 WORDS

6136.1 *** USER WARNING/FATAL MESSAGE 6136 (DFMNRS/D)

INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE CORE BY AN ESTIMATED %1 K WORDS.

Warning: THE ABOVE NUMBER IS ONLY AN ESTIMATE, THE ACTUAL CORE SIZE NEEDED
MAY BE HIGHER.

6136.3 *** USER WARNING/FATAL MESSAGE 6136 (DFMSAP)

INSUFFICIENT CORE FOR SYMBOLIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE CORE BY %1 K WORDS.

User information:
If this message is issued in the symbolic phase, the memory estimate is not necessarily conservative and even
more memory may be required (although this estimate is fairly accurate for Version 68). Also, the memory
increase required is only for the symbolic phase. It is not unusual for the decomposition phase to require
more memory than the symbolic phase. To increase the chances for a successful run, increase the memory
even more than the amount indicated in this message. After the run is complete, determine the amount of
memory actually used and use this as a guideline for similar runs in the future. The user information mes-
sage is written if SYSTEM(166) = 1 (that is, if there is not enough memory for sparse decomposition, then
switch to regular decomposition).

6136.4 *** USER WARNING/FATAL MESSAGE 6136

Main Index
 MSC Nastran Error Messeges 563
Errors 6000 - 6999

INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE CORE BY %1 K WORDS

6136.5 *** USER WARNING/FATAL MESSAGE 6136

INSUFFICIENT CORE FOR NUMERIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE CORE BY AN ESTIMATED %1 K WORDS BUT NOTE THAT IT IS

ONLY AN ESTIMATE AND THE ACTUAL CORE SIZE NEEDED MAY BE HIGHER.

6136.6 *** USER WARNING MESSAGE 6136 (FACDRVI)

INSUFFICIENT CORE FOR IN-CORE SPARSE DECOMPOSITION.

User action: INCREASE CORE BY AN ESTIMATED %1 K WORDS.

Warning: THE ABOVE NUMBER IS ONLY AN ESTIMATE, THE ACTUAL CORE SIZE NEEDED
MAY BE HIGHER.

User information: AN ALTERNATVE SPARSE DECOMPOSITION METHOD WILL BE

ATTEMPTED.

6137.0 *** USER INFORMATION MESSAGE 6137 (DFMN)

INPUT MATRIX TO DECOMPOSITION HAS %1 SINGULARITIES.
SEE FOLLOWING MESSAGES FOR DETAILS.

6137.1 *** USER WARNING MESSAGE 6137

INPUT MATRIX IS RANK DEFICIENT, RANK = %1

User action: CHECK MODEL

User information:
One of your matrices is singular. See the MSC NASTRAN Numerical Methods User's Guide. for a discus-
sion of singularity.

Main Index
 564 MSC Nastran Error Messeges
Errors 6000 - 6999

6138.0 *** USER FATAL MESSAGE 6138 (DFMSB)

INSUFFICIENT CORE FOR SPARSE FBS

User action: INCREASE CORE BY %1 WORDS

User information:
See UFM 6136.

6138.1 *** USER FATAL MESSAGE 6138 (UFBSS)

INSUFFICIENT CORE FOR SPARSE UNSYMMETRIC FBS

User action: INCREASE CORE BY %1 WORDS

6138.2 *** USER FATAL MESSAGE 6138 (FBSDRVI)

INSUFFICIENT CORE FOR IN-CORE SPARSE SYMMETRIC FBS

User action: INCREASE CORE BY %1 WORDS

6139.0 *** SYSTEM FATAL MESSAGE 6140

Invalid degree-of-freedom set name(s) for IOPT=3. Review warning messages above.

6140.0 *** SYSTEM FATAL MESSAGE 6140

One or more of the degree-of-freedom subsets is COMP or blank--SET1=%1 and SET2=%2--and this is
not allowed when IOPT=3.

6141.0 *** SYSTEM FATAL MESSAGE 6141

The %1-set is not a degree-of-freedom subset of the %2-set.

6142.0 *** USER INFORMATION MESSAGE 6142 (FA2)

THE K OR KE METHOD OF FLUTTER ANALYSIS HAS FOUND A ROOT THAT HAS NO
PHYSICAL INTERPRETATION.
NOTE THAT TO OBTAIN PHYSICALLY MEANINGFUL V-G AND V-F PLOTS,
XMIN,XMAX,YMIN,YMAX VALUES MUST BE EXPLICITLY SET IN THIS CASE.

6143.0 *** SYSTEM FATAL MESSAGE 6143 (DUPART)

Main Index
 MSC Nastran Error Messeges 565
Errors 6000 - 6999

THE SIZES OF THE INPUT MATRICES AND THE DOF SETS ARE INCOMPATIBLE.
SPECIFICALLY:

6144.0 *** SYSTEM FATAL MESSAGE 6144 (PARTN1)

THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE
INCOMPATIBLE. SPECIFICALLY:

6146.0 *** SYSTEM FATAL MESSAGE 6146

ELEMENT TYPE =%1 IS NOT SUPPORTED IN ACOUSTIC ANALYSIS.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: GP5 MODULE FAILED TO RECOGNIZE THIS ELEMENT TYPE

CHECK GPTABD ROUTINE.

6146.15 *** SYSTEM FATAL MESSAGE 6146, (GP0B),

ELEMENT TYPE =%1 IS NOT SUPPORTED IN P-ELEMENT ANALYSIS.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: GP0 MODULE FAILED TO RECOGNIZE THIS ELEMENT TYPE

CHECK GPTABD ROUTINE.

6146.16 *** SYSTEM FATAL MESSAGE 6146, (GP5H/GP5HND),

ATTEMPT TO OBTAIN ELEMENT FACE(S) NORMAL FAILED. CHECK GEOMETRY and/or
CONNECTION OF ELEMENT ID %1.

6147.0 *** SYSTEM FATAL MESSAGE 6147 (GP5I),

AN INCORRECT ELEMENT FACE CONNECTION TABLE HAS BEEN CREATED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: ELEMENT FACE CONNECTION TABLE BUILDING PROCEDURE

FAILED IN GP5I ROUTINE.

Main Index
 566 MSC Nastran Error Messeges
Errors 6000 - 6999

6147.1 *** SYSTEM FATAL MESSAGE 6147

AN INCORRECT ELEMENT FACE CONNECTION TABLE HAS BEEN CREATED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: ELEMENT FACE CONNECTION TABLE BUILDING PROCEDURE

FAILED IN GP5A ROUTINE.

6148.0 *** USER FATAL MESSAGE 6148,

NO ACOUSTIC ELEMENTS FOUND IN THE BULK DATA FOR FLUID-STRUCTURE COU-
PLING.

User action: CHECK PSOLID DATA, MAKE SURE FIELD 8 CONTAINS BCD WORD (PFLUID)
FOR SELECTED
ACOUSTIC ELEMENTS. ALTERNATIVELY, TO AVOID FLUID-STRUCTURE COUPLING USE
PARAM,ASCOUP,NO.

6148.1 *** USER FATAL MESSAGE 6148

NO STRUCTURAL ELEMENTS FOUND IN THE BULK DATA FOR FLUID-STRUCTURE COU-
PLING.

User action: INCLUDE STRUCTURE OR USE PARAM,ASCOUP,NO TO AVOID FLUID-STRUC-

TURE COUPLING.

6149.0 *** USER FATAL MESSAGE 6149,

THREE OR MORE FLUID GRID POINTS HAVE IDENTICAL COORDINATES.

User action: CHECK GRIDS AND/OR SET1 BULK DATA ENTRIES WHICH ARE REFERENCED
ON PANEL OR ACMODL ENTRIES.

6150.0 *** USER FATAL MESSAGE 6150,

Main Index
 MSC Nastran Error Messeges 567
Errors 6000 - 6999

FOUND GRID POINTS WITH IDENTICAL COORDINATES, WHICH ARE NOT CLASSIFIED
AS FLUID OR STRUCTURAL GRIDS.

User action: CHECK GRIDS AND/OR SET1 BULK DATA ENTRIES WHICH ARE REFERENCED
ON PANEL OR ACMODL ENTRIES.

6151.0 *** USER WARNING MESSAGE 6151,

ACOUSTIC COUPLING MATRIX WILL NOT BE CREATED FOR FACE =%1 OF ELEMENT ID
=%2 ,BECAUSE ITS FLUID GRID POINTS DO NOT HAVE CORRESPONDING STRUCTURAL
GRID POINTS.

User action: IF COUPLING IS DESIRED, THEN CHECK GRID POINT DATA.

6151.1 *** USER WARNING MESSAGE 6151,

ACOUSTIC COUPLING MATRIX WILL NOT BE CREATED FOR FACE =%1 OF ELEMENT ID
=%2 ,BECAUSE ALL ITS STRUCTURAL GRID POINTS DO NOT LIE INSIDE THE FLUID
BOUNDARY POINTS.

User action: IF COUPLING IS DESIRED, THEN CHECK GRID POINT DATA.

6151.2 *** USER WARNING MESSAGE 6151,

ACOUSTIC COUPLING MATRIX WILL NOT BE CREATED FOR FACE =%1 %2 %3 %4 %5 %6
%7 %8 OF ELEMENT ID =%9 ,BECAUSE ITS FLUID GRID POINTS DO NOT HAVE CORRE-
SPONDING STRUCTURAL GRID POINTS.

User action: IF COUPLING IS DESIRED, THEN CHECK GRID POINT DATA.

6151.3 *** USER WARNING MESSAGE 6151,

ACOUSTIC COUPLING MATRIX WILL NOT BE CREATED FOR FACE =%1 %2 %3 %4 %5 %6
%7 %8 OF ELEMENT ID =%9 ,BECAUSE ITS FLUID GRID POINTS DO NOT HAVE CORRE-
SPONDING STRUCTURAL GRID POINTS.

User action: IF COUPLING IS DESIRED, THEN CHECK GRID POINT DATA.

6152.0 *** USER WARNING MESSAGE 6152,

Main Index
 568 MSC Nastran Error Messeges
Errors 6000 - 6999

ACOUSTIC COUPLING MATRIX IS NOT CREATED FOR THIS MODEL.

User action: IF COUPLING IS DESIRED, THEN CHECK INPUT DATA.

6153.0 *** USER FATAL MESSAGE 6153.

NO FLUID OR STRUCTURAL GRIDS ARE REFERENCED ON SET1 ENTRIES.

User action: CHECK SET1 ENTRIES REFERENCED BY ACMODL ENTRIES.

6154.0 *** SYSTEM FATAL MESSAGE 6154.

GRID ID = %1 DOES NOT EXIST IN THE BGPDT TABLE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK INTERNAL GRID ID TO EXTERNAL GRID ID CONVERSION

LOGIC IN %2 ROUTINE.

6154.2 *** SYSTEM FATAL MESSAGE 6154.

GRID ID =%1 DOES NOT EXIST IN THE EQEXIN TABLE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK INTERNAL GRID ID TO EXTERNAL GRID ID CONVERSION

LOGIC IN GP5B ROUTINE.

6155.0 *** USER FATAL MESSAGE 6155.

SET1 ID =%1 DOES NOT EXIST.

User action: CHECK ALL SET1 DATA REFERENCED BY PANEL ENTRIES.

6155.1 *** USER FATAL MESSAGE 6155.

SET1 ID =%1 DOES NOT EXIST.

User action: CHECK ALL SET1 DATA REFERENCED BY PANEL/ACMODL ENTRIES.

6155.2 *** USER FATAL MESSAGE 6155.

Main Index
 MSC Nastran Error Messeges 569
Errors 6000 - 6999

PANEL Bulk Data entry id= %2 references entry id= %1 which is undefined.

6155.3 *** USER FATAL MESSAGE 6155.

SET1 ID =%1 REFERENCED BY DOPTPRM PARAMETER P2RSET DOES NOT EXIST

User action: REMOVE THE PR2SET REQUEST OR SUPPLY THE MISSING SET1 DATA

6155.4 *** USER FATAL MESSAGE 6155 (DOPR1A)

UNABLE TO LOAD THE SERVICE THAT CORRESPONDS TO OPTCOD=%1 ON DOPTPRM
BULK DATA ENTRY.

User action: CHECK THE CONNECT SERVICE ENTRY IN THE FMS THAT IS CALLED BY
THEDOPTPRM BULK DATA ENTRY OPTCOD= %1. EITHER THE CONNECT SERVICE
ENTRY DOES NOT EXIST OR ITS SERVICE IDENTIFIER DOES NOT MATCH OPTCOD ON
DOPTPRM BULK DATA ENTRY.

6155.5 *** USER FATAL MESSAGE 6155 (DOPR1A)

UNABLE TO LOAD THE SERVICE THAT CORRESPONDS TO OPTCOD=%1 ON DOPTPRM
BULK DATA ENTRY.

User action: CHECK THE CONNECT SERVICE ENTRY IN THE FMS THAT IS CALLED BY THE
DOPTPRM BULK DATA ENTRY OPTCOD=%1. EITHER THE SERVICE NAME IS INCORRECT
OR THERE IS A PROBLEM WITH THE SCA KERNEL. PLEASE SEE ABOVE FOR ADDITIONAL
INFORMATION.

6156.0 *** USER FATAL MESSAGE 6156,

THERE ARE NO FLUID ELEMENTS IN CONTACT WITH STRUCTURAL ELEMENTS.

User action: CHECK INPUT DATA.

6156.1 *** USER WARNING MESSAGE

THERE ARE %1 UNDEFINED GRID IDS IN THE SETS ON ACMODL. THESE UNDEFINED
GRIDS WILL NOT PARTICIPATE IN FSI COUPLING ALGORITHM.

User action: CHECK INPUT DATA.

Main Index
 570 MSC Nastran Error Messeges
Errors 6000 - 6999

6157.0 *** SYSTEM FATAL MESSAGE 6157,

THE THIRD OUTPUT DATA BLOCK OF GP5 CANNOT NOT BE PURGED WHEN MULTIPLE
PANEL CAPABILITY IS REQUESTED.

6158.0 *** USER FATAL MESSAGE 6158.

A SET1 BULK DATA ENTRY WAS NOT SUPPLIED.

6159.0 *** SYSTEM FATAL MESSAGE 6159 (GP5DA),

INTERMEDIATE FACE SORTING PROCESS FAILED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6160.0 *** SYSTEM FATAL MESSAGE 6160 (GP5ED),

ELEMENT ID =%1 HAS A FACE ON THE FLUID/STRUCTURE BOUNDARY WHICH
IS NOT WELL DEFINED. THE GEOMETRY SUGGESTS THAT GRID9 LIES ON THE SAME
PLANE AS THE FACE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK THE PROCEDURE OBTAINING GRID9.

6161.0 *** USER FATAL MESSAGE 6161,

PANEL DATA DOES NOT EXIST.

User action: CHECK INPUT DATA.

6162.0 *** USER FATAL MESSAGE 6162,

GRID ID =%1 REFERENCED THROUGH (ALL) OPTION ON AN ACMODL ENTRY DOES
NOT LIE ON THE FLUID/STRUCTURE BOUNDARY.

6163.0 *** USER WARNING MESSAGE 6163,

THERE ARE NO ELEMENT FACES CORRESPONDING TO THE PANEL NAME =%1

User action: CHECK GRID IDS DEFINED FOR THIS PANEL.

6163.1 *** USER WARNING MESSAGE 6163,

Main Index
 MSC Nastran Error Messeges 571
Errors 6000 - 6999

THERE ARE NO ELEMENTS PRESENT IN THE SET3 LIST CORRESPONDING TO THE

PANEL NAME =%1

User action: CHECK THAT QUADx/TRIAx/HEXA/PENTA/TETRA ELEMENT IDS DEFINE THIS

PANEL AND ARE IN RESIDUAL STRUCTURE.

6163.2 *** USER FATAL MESSAGE 6163

ERPPNL %1 IS EMPTY. IT REFERENCES SET3 ID %2 THAT SPECIFIES %3 ID LIST BUT NO
ASSOCIATION TO STRUCTURAL ELEMENTS COULD BE FOUND FOR THE IDS IN THIS
LIST.

User action: ENSURE THAT THERE IS AT LEAST ONE QUADx, TRIAx, HEXA, PENTA OR
TETRA ELEMENT THAT HAS %4 ID IN THE LIST.

6164.0 *** USER FATAL MESSAGE 6164,

THERE ARE NO FLUID ELEMENTS IN CONTACT WITH STRUCTURAL ELEMENTS.
FOR PANEL ID = %1

User action: CHECK PANEL BULK DATA ENTRY.

6165.0 *** USER FATAL MESSAGE 6165 (MODEPT)

THERE EXISTS A DIFFERENT NUMBERS OF TERMS IN RESISTANCE REACTANCE AND
WEIGHTING FUNCTION TABLES IDS = %1 RESPECTIVELY.

6166.0 *** USER WARNING MESSAGE 6166,

PANEL BULK DATA ENTRY NAME "%1" REFERENCES NO RELEVANT STRUCTURAL
GRIDS.

User information: No output will be produced for this panel.

When a panel is defined by SET3 with DES='ELEM' or 'PROP', it supports grids associated only with
structural shell elements of CQUAD4, CQUADR, CTRIA3, CTRIAR, CQUAD8 and CTRIA6. The
grids connected to any other elements are considered irrelevant to the panel.

6167.0 *** USER FATAL MESSAGE 6167 (MODEPT)

Main Index
 572 MSC Nastran Error Messeges
Errors 6000 - 6999

THE TABLEDI ID = %1 ENTRY REFERENCED BY A PACABS ENTRY IS NOT A TABLED1

ENTRY.

User information: THE PACABS ENTRY SHOULD ONLY REFERENCE A TABLED1 ENTRY.

6168.0 *** USER FATAL MESSAGE 6168 (MODEPT)

THE BULK DATA TABLED1 ENTRIES, ID =%1 HAS NO ACCEPTABLE VALUES BELOW CUT-
OFF FREQUENCY.

6168.1 *** USER FATAL MESSAGE 6168 (MODEPT)

THE BULK DATA TABLED1 ENTRIES, ID =%1 HAS NO ACCEPTABLE VALUES BELOW CUT-
OFF FREQUENCY.

6169.0 *** USER FATAL MESSAGE 6169,

FOUND TWO OR MORE STRUCTURAL GRID POINTS WITH IDENTICAL COORDINATES
WHICH LIE ON THE FLUID/STRUCTURE BOUNDARY.

User action: CHECK GRID AND/OR SET1 entries referenced by PANEL OR ACMODL entries.
6169.1 *** USER FATAL MESSAGE 6169,
FOUND TWO OR MORE STRUCTURAL GRID POINTS WITH IDENTICAL COORDINATES
WHICH LIE ON THE FLUID/STRUCTURE BOUNDARY. This can occur also when the fluid/struc-
ture boundary touches Module boundaries.

User action: CHECK GRID AND/OR SET1 entries referenced by PANEL OR ACMODL entries. Also
avoid contact between the fluid/structure boundary and Module boundaries.

6170.0 *** USER WARNING MESSAGE 6170 (MODEPT)

LEAST SQUARE FIT PROCESS HAS RESULTED IN A NEGATIVE MASS VALUE =%1 NO MASS
MATRIX WILL BE GENERATED.

6170.1 *** USER WARNING MESSAGE 6170 (MODEPT)

LEAST SQUARE FIT PROCESS HAS RESULTED IN A NEGATIVE DAMPING VALUE =%1 NO
DAMPING MATRIX WILL BE GENERATED.

6170.2 *** USER WARNING MESSAGE 6170 (MODEPT)

Main Index
 MSC Nastran Error Messeges 573
Errors 6000 - 6999

LEAST SQUARE FIT PROCESS HAS RESULTED IN A NEGATIVE STIFFNESS VALUE =%1 NO
STIFFNESS MATRIX WILL BE GENERATED.

6171.0 *** USER FATAL MESSAGE 6171 (APD5)

WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR AEFACT ID = %1 ASSOCI-
ATED WITH CAERO5 ID = %2

6171.1 *** USER FATAL MESSAGE 6171 (APD4)

WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR %3 ID = %1 ASSOCIATED
WITH CAERO4 ID = %2

6171.2 *** USER FATAL MESSAGE 6171 (APD3)

WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR AEFACT ID = %1 ASSOCI-
ATED WITH CAERO3 ID = %2

6171.3 *** USER FATAL MESSAGE 6171 (APD2)

WRONG NUMBER OF WORDS OR ENTRY NOT FOUND FOR AEFACT ID = %1 ASSOCI-
ATED WITH THE PAERO2 ENTRY THAT IS REFERENCED BY CAERO2 ENTRY ID = %2

6172.0 *** USER FATAL MESSAGE 6172 (APD5)

THE NUMBER OF CAOCI ENTRIES ON PAERO5 ENTRY ID = %1 MUST EQUAL THE NUM-
BER OF STRIPS SPECIFIED ON CAERO5 ENTRY ID = %2

6173.0 *** USER FATAL MESSAGE 6173. (EQD4D)

If offsets are applied to plate elements, the corresponding property entry (PSHELL) must have materials
defined in both the MID1 and MID2 fields. If the modeling intent is to ignore either the membrane
(MID1) or bending (MID2) behavior, try defining a very small E value for the associated property.

User information: Offsets were specified on the shell connection Bulk Data entry, CQUAD4, CTRIA3,
CQUAD8, or CTRIA6, in field ZOFFS. Since offsets produce coupling between membrane and bending
stiffness, then the PSHELL entry must include a specification of membrane and bending stiffness in fields
MID1 and MID2, respectively.

6173.1 *** USER FATAL MESSAGE 6173. (EQD4D)

Main Index
 574 MSC Nastran Error Messeges
Errors 6000 - 6999

TEMPERATURE DEPENDENT COMPOSITE %1 ELEMENT ID=%2 WITH OFFSETS

REQUIRES LARGE ROTATION OFFSET METHOD.

User action: USE "MDLPRM,OFFDEF,LROFF" IN SOL 400 TO ENABLE THE LARGE ROTA-
TION OFFSET METHOD.

6174.0 *** USER FATAL MESSAGE 6174.

THE OFFSET IN %1 ELEMENT (EID=%2) REQUIRES DIFFERENTIAL STIFFNESS UPDATES.

User information: FOR SOL 400, BULK DATA ENTRY "MDLPRM,OFFDEF,LROFF" ENABLES
THIS OPTION. PLEASE NOTE THAT "LROFF" OPTION IS NOT AVAILABLE IN NONLINEAR
SOLUTION SEQUENCE 106 AND 129. FOR LINEAR SOLUTION SEQUENCES, USE MDL-
PRM,OFFDEF,ELMOFF (THE DEFAULT).

User action: TO PROVIDE FOR DIFFERENTIAL STIFFNESS OF THE OFFSET, IT IS RECOM-

MENDED THAT THE USER ADD THE BULK DATA ENTRY "MDLPRM, OFFDEF, LROFF" OR
"MDLPRM, OFFDEF, NODIF". THE LATTER PROVIDES THE REQUIRED DIFFERENTIAL
STIFFNESS TO THE ELEMENTS BUT TURNS OFF THE LARGE ROTATION EFFECT OF OFF-
SET, WHICH IN LINEAR BUCKLING OFTEN CAUSES SPURIOUS MODES.

6174.1 *** USER FATAL MESSAGE 6174,

CBEAM ELEMENT (EID=%1), WITH NON-GLOBAL OFFSET VECTORS, IS NOT SUPPORTED
IN P-ELEMENT ANALYSIS.

User action: SPECIFY OFFSET VECTORS IN GRID POINT OUTPUT COORDINATE SYSTEM
DIRECTIONS.

6175.0 *** USER FATAL MESSAGE 6175 (ASGPRD)

A TRIM VARIABLE WITH TRIM ID = %1, LABEL = %2 IS DEFINED MORE THAN ONCE.

User action: CHECK TRIM AND AELINK BULK DATA ENTRIES.

6176.0 *** USER FATAL MESSAGE 6176 (EQDRD)

ZOFFS FOR QUADR ELEMENT ARE NOT SUPPORTED

6176.1 *** USER FATAL MESSAGE 6176 (ETRRD)

ZOFFS FOR TRIAR ELEMENT ARE NOT SUPPORTED

Main Index
 MSC Nastran Error Messeges 575
Errors 6000 - 6999

6176.2 *** USER FATAL MESSAGE 6176. (TTRRD)

ZOFFS IS NOT SUPPORTED FOR TRIAR ELEMENT.

6177.0 *** USER FATAL MESSAGE 6177 (APD0)

THE AEROS BULK DATA ENTRY, IN FIELD 3, ILLEGALLY REFERENCES A SPHERICAL OR
CYLINDRICAL COORDINATE SYSTEM.

6177.1 *** USER FATAL MESSAGE 6177 (APD0)

THE AERO AND AEROS BULK DATA ENTRIES, IN FIELD 2, ILLEGALLY REFERENCE A
SPHERICAL OR CYLINDRICAL COORDINATE SYSTEM.

6177.2 *** USER FATAL MESSAGE 6177 (APD0)

THE AERO BULK DATA ENTRY, IN FIELD 2, ILLEGALLY REFERENCES A SPHERICAL OR
CYLINDRICAL COORDINATE SYSTEM.

6177.3 *** USER FATAL MESSAGE 6177 (APD0)

THE AEROS BULK DATA ENTRY, IN FIELD 2, ILLEGALLY REFERENCES A SPHERICAL OR
CYLINDRICAL COORDINATE SYSTEM.

6178.0 *** USER FATAL MESSAGE 6178 (APD0)

AERO AND AEROS BULK DATA ENTRIES MUST REFER TO THE SAME COORDINATE SYS-
TEM ID FOR THE AERODYNAMIC COORDINATE SYSTEM.

6179.0 *** USER FATAL MESSAGE 6179 (APD0)

AERO AND AEROS BULK DATA ENTRIES MUST HAVE SAME SYMMETRY CONDITIONS.

6180.0 *** USER FATAL MESSAGE 6180 (APDCST)

CAERO 1, 3, 4 OR 5 BULK DATA ENTRY %1 HAS A ZERO PANEL SURFACE AREA.

User information: X12 AND X43 ARE MEASURED ALONG THE X AXIS OF THE AERODY-
NAMIC COORDINATE SYSTEM.

User action: CHECK THE COORDINATE DATA IN THIS ENTRY TOGETHER WITH THE
AERODYNAMIC COORDINATE SYSTEM.

Main Index
 576 MSC Nastran Error Messeges
Errors 6000 - 6999

6181.0 *** USER FATAL MESSAGE 6181 (SMPYAD)

THE LAST INPUT MATRIX MUST BE UNTRANSPOSED

User information: THE TRANSPOSE FLAG PARAMETER CORRESPONDING TO THE LAST

INPUT MATRIX IN THE SMPYAD MODULE SPECIFICATION IS NOT ZERO

User action: ASSURE THAT THIS FLAG IS ZERO, WHICH IS THE DEFAULT

6182.0 *** USER FATAL MESSAGE 6182 (ADG)

6183.0 *** USER FATAL MESSAGE 6183 (MBAMG)

IMPROPER MACH BOX CONTROL POINTS, SINGULAR MATRIX RESULTED

6184.0 *** USER FATAL MESSAGE 6184 (MBAMG)

GENERATION OF BOXES FAILED WITH MACH BOX

6185.0 *** USER FATAL MESSAGE 6185 (PSTAMG)

MACH NUMBER %1 WAS NOT FOUND IN THE PISTON THEORY ALPHA ARRAY

6186.0 *** USER INFORMATION MESSAGE 6186 (NCONVG)

*** SOLUTION HAS CONVERGED ***

6187.0 *** USER INFORMATION MESSAGE 6187 (NCONVG)

*** BISECTION IS ACTIVATED DUE TO LARGE INCREMENTAL ROTATIONS AT ITERA-
TION NO. %1 ***

6187.1 *** USER INFORMATION MESSAGE 6187 (NCONVG)

*** BISECTION METHOD IS NOW ACTIVATED ***

6187.2 *** USER INFORMATION MESSAGE 6187 (NCONVG)

*** BISECTION METHOD IS ACTIVATED BY LINE CONTACT ***

6187.3 *** USER INFORMATION MESSAGE 6187 (NL3CON)

*** BISECTION IS ACTIVATED DUE TO LARGE INCREMENTAL ROTATION %1 DEGREE AT
GRID=%2, DOF=%3 ***

6187.4 *** USER INFORMATION MESSAGE 6187 (NL3CON)

Main Index
 MSC Nastran Error Messeges 577
Errors 6000 - 6999

*** BISECTION IS ACTIVATED DUE TO LARGE AVERAGE INCREMENTAL ROTATION %1

DEGREE ***

6188.0 *** USER INFORMATION MESSAGE 6188

*** INITIAL ARC LENGTH IS %1

User information: The initial arc-length is printed when the NLITER module is first executed and the
arc<#0106>length method is used. A new arc-length is printed when the arc length changes due to bisec-
tion. It is also printed after a converged solution, when the arc length may change due to restoration after
bisection, or due to the DESITER field on the NLPCI entry.

6188.1 *** USER INFORMATION MESSAGE 6188 (NLITER)

*** ARC LENGTH RATIO IS %1

6189.0 *** USER INFORMATION MESSAGE 6189 (NL2CON)

*** REPEAT ITERATION, STOPPING AT LOWEST ERROR ***

User information: This is issued when the time/load/arc-length increment has already reached its mini-
mum limit and the solution has not converged, though the maximum number of iterations has been per-
formed. If the best iteration is not the last iteration, a reiteration is done to obtain the best solution.

6189.1 *** USER INFORMATION MESSAGE 6189 (NCONVG)

*** BEST ATTAINABLE SOLUTION HAS BEEN FOUND ***

6189.2 *** USER INFORMATION MESSAGE 6189 (NL3CON)

*** LINEAR SOLUTION IS REQUESTED ***

6189.3 *** USER INFORMATION MESSAGE 6189 (NL3CON)

*** REPEAT ITERATION TO FIND THE BEST SOLUTION FOR STIFFNESS UPDATE ****
6189.4 *** USER INFORMATION MESSAGE 6189 (NL3CON)
*** BEST SOLUTION FOR STIFFNESS UPDATE HAS BEEN FOUND ***

6190.0 *** USER FATAL MESSAGE 6190 (NLITER)

Main Index
 578 MSC Nastran Error Messeges
Errors 6000 - 6999

*** MAXIMUM NUMBER OF CONTROLLED INCREMENTS (MXINC) HAS BEEN EXCEEDED

***

User information: In the arc-length control methods, the number of solution steps actually completed in a
subcase is usually different from that specified by the user. Therefore, its limit is controlled by MXINC. No
action is necessary if the solutions exceed the desired extent. Otherwise, increase the value of MXINC on
the NLPCI entry.

6190.1 *** USER INFORMATION MESSAGE 6190 (NL3CON)

*** MAXIMUM NUMBER OF INCREMENTS (NSMAX) HAS BEEN REACHED FOR NLSTEP ***

6191.0 *** USER INFORMATION MESSAGE 6191 (NL2CON)

*** EXIT FROM NLTRD2 DUE TO DIVERGING SOLUTION LIMIT ***

User information: The solution has diverged twice consecutively during the iteration. Change the stiffness
matrix update strategy (Method) or increase the divergence criterion value of MAXDIV on the NLPARM
or TSTEPNL entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on the
TSTEPNL entry.

6191.1 *** USER INFORMATION MESSAGE 6191 (NCONVG)

*** FIRST DIVERGING SOLUTION ***

6191.2 *** USER INFORMATION MESSAGE 6191 (NCONVG)

*** SECOND DIVERGING SOLUTION ***

6191.3 *** SYSTEM INFORMATION MESSAGE 6191 (NLTCON)

*** EXIT FROM NLTRD DUE TO DIVERGING SOLUTION LIMIT ***

System information: The solution has diverged twice consecutively during the iteration. Change the stiff-
ness matrix update strategy (Method) or increase the divergence criterion value of MAXDIV on the
NLPARM or TSTEPNL entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on
the TSTEPNL entry.

6191.4 *** USER FATAL MESSAGE 6191 (NLTCON)

*** EXIT FROM NLTRD DUE TO DIVERGING SOLUTION LIMIT ON FIRST TIME STEP ***
6191.5 *** USER INFORMATION MESSAGE 6191 (NCONVG)
*** DIVERGING SOLUTION SEQUENCE INITIATED ***

Main Index
 MSC Nastran Error Messeges 579
Errors 6000 - 6999

6191.6 *** USER INFORMATION MESSAGE 6191 (NCONVG)

*** SOLUTION CONVERGED, DIVERGING SOLUTION SEQUENCE ENDS ***

6191.7 *** USER INFORMATION MESSAGE 6191 (NCONVG)

*** %1 INCREMENTS OR TIME STEPS HAVE BEEN ACCEPTED WITHOUT CONVERGENCE
***

6191.8 *** USER INFORMATION MESSAGE 6191 (NCONVG)

*** UNABLE TO ACHIEVE CONVERGENCE FOR THE CURRENT INCREMENT OR TIME
STEP, TRY TO FIND THE BEST SOLUTION ***

6192.0 *** USER INFORMATION MESSAGE 6192

*** NO ROOT CASE HAS BEEN ENCOUNTERED ***

User information: The quadratic equation which contains the load factor increment as the unknown vari-
able does not have any real roots. A special algorithm specifically developed for this case will be automati-
cally activated.

6193.0 *** USER INFORMATION MESSAGE 6193 (NL2CON)

*** MAXIMUM NUMBER OF BISECTIONS OR MINIMUM TIME STEP HAS BEEN REACHED
***

User information: In nonlinear transient analysis, the minimum allowable time step has been reached. In
nonlinear static analysis, with Newton's method, the minimum allowable load step has been reached or,
with the arc-length method, the minimum allowable arc length has been reached. Change the stiffness
matrix update strategy (METHOD) or increase the value of MAXBIS on the NLPARM or TSTEPNL
entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on the TSTEPNL entry.

6193.1 *** USER INFORMATION MESSAGE 6193 (NCONVG)

*** MAXIMUM NUMBER OF BISECTIONS OR MINIMUM LOAD STEP HAS BEEN REACHED.

User information: In nonlinear transient analysis, the minimum allowable time step has been reached. In
nonlinear static analysis, with Newton's method, the minimum allowable load step has been reached or,
with the arc-length method, the minimum allowable arc length has been reached. Change the stiffness
matrix update strategy (METHOD) or increase the value of MAXBIS on the NLPARM or TSTEPNL
entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on the TSTEPNL entry.

Main Index
 580 MSC Nastran Error Messeges
Errors 6000 - 6999

6193.2 *** USER INFORMATION MESSAGE 6193

*** MAXIMUM NUMBER OF BISECTIONS OR MINIMUM ARC LENGTH HAS BEEN
REACHED.

User information: In nonlinear transient analysis, the minimum allowable time step has been reached. In
nonlinear static analysis, with Newton's method, the minimum allowable load step has been reached or,
with the arc-length method, the minimum allowable arc length has been reached. Change the stiffness
matrix update strategy (METHOD) or increase the value of MAXBIS on the NLPARM or TSTEPNL
entry. Alternatively, increase NINC on the NLPARM entry or decrease DT on the TSTEPNL entry.

6194.0 *** USER INFORMATION MESSAGE 6194 (NL2CON)

*** STOPPED ITERATIONS DUE TO REACHING MAXIMUM ITERATION LIMIT WITHOUT
CONVERGENCE ***

User information: For insufficient time, increase the value on the TIME Executive Control statement. For
maximum iterations, change the stiffness matrix update strategy (METHOD) or increase the value of
MAXITER on the NLPARM or TSTEPNL entry.

6194.1 *** USER INFORMATION MESSAGE 6194

*** STOPPED ITERATIONS DUE TO INSUFFICIENT TIME REMAINING ***

User information: For insufficient time, increase the value on the TIME Executive Control statement. For
maximum iterations, change the stiffness matrix update strategy (METHOD) or increase the value of
MAXITER on the NLPARM or TSTEPNL entry.

6194.2 *** USER WARNING MESSAGE 6194 (NLTCON)

*** STOPPED ITERATIONS DUE TO REACHING MAXIMUM ITERATION LIMIT WITHOUT
CONVERGENCE ***

User information: For insufficient time, increase the value on the TIME Executive Control statement. For
maximum iterations, change the stiffness matrix update strategy (METHOD) or increase the value of
MAXITER on the NLPARM or TSTEPNL entry.

6195.0 *** USER WARNING MESSAGE 6195 (NLITER)

Main Index
 MSC Nastran Error Messeges 581
Errors 6000 - 6999

SOLUTION HAS REGRESSED TO AN EARLIER LOAD STEP. (BACK-UP COEFFICIENT =%1)

User information: This message is issued for the Arc-Length method (See NLPARM entry) only. Change
the iteration strategy for the RIKS and MRIKS method. The program will automatically activate a different
root selection procedure for the Crisfield method.

6196.0 *** USER FATAL MESSAGE 6196 (NLITER)

REGRESSION HAS OCCURRED WITH BOTH ROOT-SELECTION ALGORITHMS IN CRIS-
FIELD'S METHOD

User information: The program has returned to a converged solution in a prior loop using both available
algorithms. The bisection algorithm will automatically be activated if the absolute value of MAXBIS is
greater than 0.

6197.0 *** USER INFORMATION MESSAGE 6197 (NLITER)

SOLUTION AT THIS STEP IS DISCARDED. SOLUTION WILL BE ATTEMPTED WITH A DIF-
FERENT ROOT-SELECTION PROCEDURE.

User information: This message is issued for the Crisfield method (See NLPARM entry) only.

6198.0 *** USER FATAL MESSAGE 6198.0 (MPYAD)

ALL MPYAD METHODS HAVE BEEN DESELECTED.

User information: METHODS MAY BE DESELECTED INTERNALLY BY THE MODULE AND/

OR BY THE USER VIA SYSTEM CELL 66.

User action: CHECK THE VALUE OF SYSTEM CELL 66, OR DO NOT SET THE CELL.

6198.1
User action: INCREASE MEMORY REQUESTED FOR OPEN CORE BY AT LEAST %1 MB.
6199.0 *** SYSTEM FATAL MESSAGE 6199 (MPYSC2)

Main Index
 582 MSC Nastran Error Messeges
Errors 6000 - 6999

INSUFFICIENT CORE AVAILABLE FOR MATRIX MULTIPLY.

Programmer information: ERROR CODE=%1

User action: INCREASE MEMORY BY %2 WORDS.

User information: This message comes from the sparse multiply method when the memory estimate based
on the trailer information is exceeded during the actual execution of the operation.

6200.0 *** USER FATAL MESSAGE 6200.

TEMPERATURE(INITIAL) COMMAND IS NOT SPECIFIED IN CASE CONTROL. BOTH TEM-
PERATURE(LOAD) AND TEMPERATURE(INITIAL) MUST BE SPECIFIED IN NONLINEAR
STATIC SOLUTION FOR THERMAL LOADS.

User information: Insert a TEMPERATURE(INITIAL) command above the subcase level in the case con-
trol and the corresponding temperature values on TEMPij entries in the bulk data. TEMPERA-
TURE(MATERIAL) or TEMPERATURE(BOTH) will cause this error.

6201.0 *** USER FATAL MESSAGE 6201, (UFBSS)

SPARSE UNSYMMETRIC FBS CANNOT BE PERFORMED WHEN THE FACTOR TYPE AND
THE RIGHT HAND SIDE TYPE ARE NOT THE SAME

User action: DO NOT SELECT THE SPARSE DECOMPOSITION AND FBS METHODS UNDER
THESE CIRCUMSTANCES.

6202.0 *** USER FATAL MESSAGE 6202 (MCE1)

THE SELECTED MULTIPOINT CONSTRAINT SET AND/OR RIGID ELEMENTS PRODUCE A
SINGULAR RMM MATRIX. THIS MAY BE CAUSED BY A CIRCULAR DEPENDENCY IN
WHICH A DEGREE OF FREEDOM IS INDIRECTLY DEPENDENT UPON ITSELF.

User action:
[1] ENSURE THE CORRECTNESS OF DATA ENTERED IN THE RESPECTIVE FIELDS OF MPC
CREATION.
[2] CASE CONTROL COMMAND "FEMCHECK" CAN BE USED TO FIND RBE2/3 ELEMENTS
WITH UNCONNECTED NODES.
[3] SETTING "PARAM,AUTOMSET,YES" WILL ALLOW THE PROGRAM TO TRY TO
RESOLVE THIS CONFLICT BY REMOVING REDUNDANT CONSTRAINT EQUATIONS.

Main Index
 MSC Nastran Error Messeges 583
Errors 6000 - 6999

6203.0 *** SYSTEM FATAL MESSAGE 6203 (CEAD)

INCOMPATIBLE MATRICES ARE DETECTED IN COMPLEX EIGENVALUE ANALYSIS

User information: CHECK THE SIZES OF THE MATRIX INPUTS TO THIS MODULE. ALSO
CHECK FOR THE PRESENCE OF NON-ZERO K (ALWAYS REQUIRED), M OR B FOR EIGEN-
VALUE ANALYSIS (AT LEAST ONE REQUIRED), OR M AND B MATRICES WITH THE SVD
METHOD (NOT ALLOWED).

6204.0 *** USER INFORMATION MESSAGE 6204 ***

%1 SECONDS REQUIRED TO DECOMPOSE MATRIX.

User information: A matrix decomposition has been performed within the NLTRD2 module. The time
required for this decomposition is provided for the user's information.

6204.1 *** USER FATAL MESSAGE 6204 ***

AJUST=0 AND MAXBIS=0 MUST BE USED ON BULK DATA ENTRY TSTEPNL IF
'PARAM,NODCMP,1' IS SPECFIED.

User information: IF NODCMP=1, THE SOLUTION MATRIX WILL NOT BE DECOMPOSED,

WHICH MEANS THAT THE AUTOMATIC TIME ADJUSTMENT AND BISECTION MUST BE
DEACTIVATED.

6205.0 *** USER FATAL MESSAGE 6205

BEAM ELEMENT %1 IS USING WARPING WITHOUT TORSIONAL STIFFNESS

User information: If warping degrees of freedom (SA,SB) are supplied on the CBEAM data card, then
warping is used. Torsional stiffness (JA on PBEAM data card) must be greater than zero if warping is used.

6206.0 *** USER WARNING MESSAGE 6206 (GP5),

MORE THAN ONE ACMODL ENTRY HAS BEEN FOUND, ONLY THE FIRST ENTRY WILL BE
USED.

User action: CHECK INPUT DATA.

6207.0 *** USER INFORMATION MESSAGE 6207 (GP5),

Main Index
 584 MSC Nastran Error Messeges
Errors 6000 - 6999

AN ACMODL ENTRY WAS NOT FOUND. A NONMATCHING MESH IS ASSUMED.

METHOD: %1

6208.0 *** USER FATAL MESSAGE 6208 (GP5K),

IN THE NONMATCHING ALGORITHM NO STRUCTURAL GRIDS HAVE BEEN FOUND ON
THE FLUID SURFACE.

User action: CHECK GRID POINT ENTRIES.

6209.0 *** USER WARNING MESSAGE 6209 (ACMG),

THERE ARE NO ELEMENT FACES CORRESPONDING TO THE PANEL NAME =%1 CHECK
GRID IDS. DEFINED FOR THIS PANEL.

6210.0 *** SYSTEM FATAL MESSAGE 6210 (ACMG),

AN INTERNAL TABLE HAS BEEN INCORRECTLY CREATED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: MODULE FAILED TO CONVERT INTERNAL GRID ID TO SIL NO.

(TABLE2)%1

6210.1 *** SYSTEM FATAL MESSAGE 6210 (ACMG),

AN INTERNAL TABLE HAS BEEN INCORRECTLY CREATED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: MODULE FAILED TO CONVERT INTERNAL GRID ID TO SIL NO.

(EQACST)%1

6210.2 *** SYSTEM FATAL MESSAGE 6210 (ACMG),

AN INTERNAL TABLE HAS BEEN INCORRECTLY CREATED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: MODULE FAILED TO CONVERT INTERNAL GRID ID TO SIL NO.

(TABLE1)%1

Main Index
 MSC Nastran Error Messeges 585
Errors 6000 - 6999

6211.0 *** SYSTEM FATAL MESSAGE 6211 (ACMG),

A NORMAL TABLE HAS BEEN INCORRECTLY CREATED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6212.0 *** SYSTEM WARNING MESSAGE 6212 (GPFRBI),

THE CASE CONTROL DATA BLOCK HAS THE WRONG RECORD COUNT FOR BLK1
APPROACH.

6213.0 *** SYSTEM WARNING MESSAGE 6213 (GPFRBI),

%1 CASE CONTROL RECORDS DETECTED FOR BRANCH %2 WHERE ONE WAS
EXPECTED.

6214.1 *** USER INFORMATION MESSAGE 6214 (WILVCD)

FEWER THAN REQUESTED VECTORS CALCULATED DUE TO INSUFFICIENT TIME

User information: This information message occurs in the READ module when there is insufficient time to
compute eigenvectors. Resubmit the job with an increased time limit (TIME).

6215.0 *** USER FATAL MESSAGE 6215 (PRETBH)

THE INDEPENDENT VARIABLES ON THE %1 BULK DATA ENTRY ID=%2 ARE NOT SPECI-
FIED IN ASCENDING ORDER.

6216.0 *** USER WARNING MESSAGE 6216 (GPSP)

THE PENALTY FUNCTION SCALE FACTOR FOR LAGRANGE RIGID ELEMENTS
('PARAM,PENFN') IS TOO SMALL FOR AUTOSPC PROCESSING.

User information:
If PENFN is too small, the dependent degrees-of-freedom of rigid element may be incorrectly constrained
by AUTOSPC.

User action: For linear or material nonlinear analysis a value of %1 or larger is suggested. However, this
suggested value may be incorrect for geometric nonlinear analysis.

6217.0 *** USER FATAL MESSAGE 6217

Main Index
 586 MSC Nastran Error Messeges
Errors 6000 - 6999

WARPING DOF(s) ARE SPECIFIED on CBEAM ELEMENT ID=%1 in geometric nonlinear analysis.

User information: Warping degrees of freedoms may not be specified in geometric nonlinear analysis.

6226.0 *** USER WARNING MESSAGE 6226 (RECTND),

NATURAL COORDINATE CONVERGENCE FAILED AFTER FIVE ITERATIONS.

User information: NATURAL COORDINATES (XI,ETA,ZETA) OF THE GRID POINT (X,Y,Z)=

%1%2%3 ARE SET TO (0,0,0).

6227.0 *** USER FATAL MESSAGE 6227 (MBAMG)

REQUESTED MACH NUMBER = %1 IS LESS THAN THE MACH BOX REQUIREMENT OF
MACH > 1.0

6228.0 *** USER FATAL MESSAGE 6228 (DLAMBY)

REQUESTED MACH NUMBER = %1 IS GREATER THAN THE DOUBLET LATTICE WITH
BODIES REQUIREMENT OF MACH < 1.0

6229.0 *** USER FATAL MESSAGE 6229 (CY1CCT)

THE LOADSET CASE CONTROL COMMAND AND LSEQ BULK DATA ENTRY MAY NOT BE
SPECIFIED IN STATIC ANALYSIS WITH CYCLIC SYMMETRY.

User action: REPLACE LOADSET/LSEQ COMBINATIONS WITH THE EQUIVALENT LOAD/

LOADCYI COMBINATIONS.

6230.0 *** USER FATAL MESSAGE 6230 (CYCL1)

6231.0 *** USER WARNING MESSAGE 6231 (CY1CCT)

BOUNDARY CONDITIONS IN SUBCASE%1 ARE DIFFERENT THAN THOSE IN THE FIRST
SUBCASE.
SUBCASE 1 SPC=%2 AND MPC=%3
SUBCASE%4 SPC=%5 AND MPC=%6

User information: ONLY ONE BOUNDARY CONDITION IS PERMITTED FOR ALL SUBCASES
IN CYCLIC SYMMETRY ANALYSIS. THEREFORE, THE CONDITIONS IN THE FIRST SUB-
CASE WILL BE USED FOR ALL SUBCASES.

Main Index
 MSC Nastran Error Messeges 587
Errors 6000 - 6999

6232.0 *** USER INFORMATION MESSAGE 6232 (MODEPT)

THE PROPERTIES BELOW WILL BE USED FOR THE FOLLOWING ACOUSTIC ABSORBER
PROPERTY ENTRIES (PACABS) PID DAMPING(B) STIFFNESS(K) MASS(M)

6233.0 *** USER INFORMATION MESSAGE 6233 (MODEPT)

THE PROPERTIES BELOW WILL BE USED FOR THE FOLLOWING ACOUSTIC BARRIER
PROPERTY ENTRIES (PACBAR) PID RESONANT STIFFNESS(K) RESONANT FREQUENCY(F)

6234.0 *** USER WARNING MESSAGE 6234 (MAT)

G13, G23 AND/OR G33 ARE NONZERO ON MAT2 ENTRY ID= %1 WHICH IS REFERENCED
IN THE MID3 FIELD OF A PSHELL ENTRY. THEY WILL BE IGNORED, SHEAR FLEXIBILITY
IS SET TO ZERO.

User information: This can occur when the PSHELL entry references a MAT2 entry in the MID3 field
and either G13, G23, or G33 is nonzero. See Error Report 3664.

6235.0 *** USER WARNING MESSAGE 6235 (IFP7)

PROBLEM WITH PBCOMP ENTRY=%1.

User information: THERE MUST BE AT LEAST 3 LUMPED AREAS NOT ON A STRAIGHT LINE.

User information: One cause is that fewer than four stress output points are specified.

6236.0 *** USER FATAL MESSAGE 6236 (EBEMD)

FOR BEAM ELEMENT =%1 THE MOMENT OF INERTIA IS NEGATIVE OR VERY SMALL
ABOUT SOME AXIS.

6237.0 *** USER WARNING MESSAGE 6237 (PLOT)

*** CONTOUR PLOTS ARE REQUESTED FOR COMPLEX RESULTS. THIS IS NOT SUP-
PORTED.

6238.0 *** USER WARNING MESSAGE 6238 (IFSEQU)

THE FIRST %1 EQUATION OF ID NUMBER = %2 HAS BEEN DEFINED WITH NO PARAME-
TERS IN ITS ARGUMENT LIST.

6239.0 *** USER FATAL MESSAGE 6239 (IFSEQU)

Main Index
 588 MSC Nastran Error Messeges
Errors 6000 - 6999

THE FIRST %1 EQUATION OF ID NUMBER = %2 HAS BEEN DEFINED WITH NO ARGU-

MENT LIST.

6240.0 *** USER FATAL MESSAGE 6240 (IFSEQU)

ARGUMENT NUMBER %1 (%2) OF THE %3 EQUATION WITH ID NUMBER = %4 HAS BEEN
PREVIOUSLY USED AS AN ARGUMENT IN THIS EQUATION

6241.0 *** USER FATAL MESSAGE 6241 (IFSEQU)

FUNCTION %1 DEFINED IN THE %2 EQUATION WITH ID NUMBER = %3 HAS BEEN PRE-
VIOUSLY USED AS AN ARGUMENT IN THIS EQUATION

User information: THIS ERROR MAY BE CAUSED WHEN THE FUNCTION NAME BEGINS IN
FIELD 2 INSTEAD OF FIELD 3

6242.0 *** USER FATAL MESSAGE 6242 (NLINIT)

ENFORCED DISPLACEMENTS CAN NOT BE USED WITH ARC-LENGTH METHODS.

User action: REMOVE NLPCI BULK DATA ENTRY OR ENFORCED DISPLACEMENTS.

6243.1 *** USER WARNING MESSAGE 6243 (REIG).

THE DEGREE OF FREEDOM (D.O.F) REQUESTED FOR POINT NORMALIZATION HAS NOT
BEEN SPECIFIED ON THE EIGR OR EIGB ENTRY

User information: THE D.O.F PRECEDING THE REQUESTED D.O.F. IN THE INTERNAL
SEQUENCE LIST WILL BE USED

6244.0 *** USER WARNING MESSAGE 6244 (STDCON),

THERE IS STRFIELD DISCONTINUITY REQUEST IN SUBCASE %1 BUT NO MATCHING
SURFACE OR VOLUME ID ON GPSTRESS COMMAND.

User action: CHECK STRFIELD COMMAND.

6244.1 *** USER WARNING MESSAGE 6244 (STDCON),

THERE IS STRESS DISCONTINUITY REQUEST IN SUBCASE %1 BUT NO MATCHING SUR-
FACE OR VOLUME ID ON GPSTRESS COMMAND.

User action: CHECK STRFIELD COMMAND.

Main Index
 MSC Nastran Error Messeges 589
Errors 6000 - 6999

6245.0 *** SYSTEM WARNING MESSAGE 6245 (STDCON),

ANALYSIS TYPE %1 IS NOT SUPPORTED IN ERROR ANALYSIS.

User action: USE STATIC ANALYSIS WITH STRESS REQUEST.

6246.0 *** USER WARNING MESSAGE 6246 (STDCON),

ELSDCON SET %1 NOT FOUND IN CASECC SUBCASE %2.

User action: CHECK ELSDCON REQUEST.

6246.1 *** USER WARNING MESSAGE 6246 (STDCON),
GPSDCON SET %1 NOT FOUND IN CASECC SUBCASE %2.

User action: CHECK GPSDCON REQUEST.

6246.2 *** USER WARNING MESSAGE 6246 (STDCON),

NO OUTPUT STRESS REQUEST FOR SUBCASE %1 SO NO STRESS DISCONTINUITY CAL-
CULATED.

User action: CHECK ELSTRESS REQUEST.

6246.3 *** USER WARNING MESSAGE 6246 (STDCON),

STRFIELD SET %1 NOT FOUND IN CASECC SUBCASE %2.

User action: CHECK STRFIELD REQUEST.

6247.0 *** SYSTEM WARNING MESSAGE 6247 (STDCON),

THERE IS AN INCONSISTENT POINTER TABLE FOR SCR4 FILE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK POINTER TABLE 4 FOR SCR3 FILE.

6247.1 *** SYSTEM WARNING MESSAGE 6247 (STDCON),

Main Index
 590 MSC Nastran Error Messeges
Errors 6000 - 6999

THERE IS AN INCONSISTENT POINTER TABLE FOR SCR3 FILE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK POINTER TABLE 3 FOR SCR3 FILE.

6247.2 *** SYSTEM WARNING MESSAGE 6247

THERE IS AN INCONSISTENT POINTER TABLE FOR SCR3 FILE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK POINTER TABLE 2 FOR SCR3 FILE.

6247.5 *** SYSTEM WARNING MESSAGE 6247 (STD2GD/S),

THERE IS AN INCONSISTENT POINTER TABLE FOR SCR5 FILE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK POINTER TABLE 5 FOR SCR5 FILE.

6247.6 *** SYSTEM WARNING MESSAGE 6247 (STD2HD/S),

THERE IS AN INCONSISTENT POINTER TABLE FOR SCR4 FILE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK POINTER TABLE 5 FOR SCR4 FILE.

6247.7 *** SYSTEM WARNING MESSAGE 6247 (STD2HD/S),

ELEMENT %1 NOT FOUND IN SURFACE/VOLUME DISCONTINUITY LIST.

6248.0 *** SYSTEM WARNING MESSAGE 6248 (STDCON),

EXTERNAL GRID ID %1 COULD NOT BE FOUND IN THE EQEXIN FILE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK EQEXIN DATA FILE.

Main Index
 MSC Nastran Error Messeges 591
Errors 6000 - 6999

6249.0 *** SYSTEM WARNING MESSAGE 6249 (STD2EX)

ERROR ANALYSIS OUTPUT CAPABILITY IS NOT SUPPORTED FOR ELEMENT TYPE %1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: THIS ROUTINE HAS FAILED TO RECOGNIZE ABOVE ELEMENT

TYPE.

6250.0 *** SYSTEM WARNING MESSAGE 6250 (STD2HD/S),

GRID POINT STRESS DATA FOR THE SURFACE/VOLUME ID %1 COULD NOT BE FOUND
IN THE EGPST FILE.

User action: CHECK STRFIELD REQUEST FOR THIS ID.

6251.0 *** SYSTEM WARNING MESSAGE 6251 (STD2EX),

IMPROPER OES1 FILE FOUND.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK OES1 FILE INPUT.

6251.1 *** SYSTEM WARNING MESSAGE 6251 (STD2EX),

IMPROPER ECT FILE FOUND.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK ECT FILE INPUT.

6252.0 *** USER WARNING MESSAGE 6252 (STD2HD/S),

THERE IS NO STRESS OUTPUT FOR THE ELEMENT ID. %1.

User action: REQUEST ELEMENT STRESS OUTPUT.

6253.0 *** SYSTEM WARNING MESSAGE 6253 (STDCON),

Main Index
 592 MSC Nastran Error Messeges
Errors 6000 - 6999

STRFIELD REQUEST IN SUBCASE %1 IGNORED SINCE GPDCT IS PURGED.

Programmer information: CHECK GPDCT FILE INPUT.

6253.1 *** SYSTEM WARNING MESSAGE 6253 (STDCON),

STRFIELD REQUEST IN SUBCASE %1 IGNORED SINCE ELDCT IS PURGED.

Programmer information: CHECK ELDCT FILE INPUT.

6253.2 *** SYSTEM WARNING MESSAGE 6253 (STDCON),

GRID POINT STRESS DISCONTINUITY REQUEST IN SUBCASE %1 IGNORED SINCE
OGDS1 IS PURGED.

Programmer information: CHECK OGDS1 FILE INPUT.

6253.3 *** SYSTEM WARNING MESSAGE 6253 (STDCON),

ELEMENT STRESS DISCONTINUITY REQUEST IN SUBCASE %1 IGNORED SINCE OEDS1IS
PURGED.

Programmer information: CHECK OEDS1 FILE INPUT.

6254.0 ***USER FATAL MESSAGE 6254 (TIMTS9)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: NUMBER OF SPECIFIED BREAK POINTS FOR KERNEL %1 EXCEEDS

%2

6255.0 ***USER FATAL MESSAGE 6255 (TIMTS9)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: SEE ENTRY NUMBER %1

6256.0 ***USER FATAL MESSAGE 6256 (TIMTS9)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: SEE ENTRY FOR KERNEL %1

Main Index
 MSC Nastran Error Messeges 593
Errors 6000 - 6999

6257.0 ***USER FATAL MESSAGE 6257 (TIMTS9)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: KERNEL NAME %1 NOT FOUND ON THE LIST

6258.0 ***USER FATAL MESSAGE 6258 (TIMTS9)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: KERNEL NAME %1 HAS USER SPECIFIED BREAK POINTS THAT ARE
LESS THAN OR EQUAL TO 1

6259.0 ***USER FATAL MESSAGE 6259 (TIMTS9)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: KERNEL %1 HAS USER SPECIFIED BREAK POINTS THAT ARE NOT
IN ASCENDING ORDER BY AT LEAST AN INCREMENT OF TWO

6260.0 ***SYSTEM FATAL MESSAGE 6260 (TIMT9F)

LOGIC ERROR IN TIMETEST 9 PLEASE CONTACT HEXAGON AB CLIENT SUPPORT

6261.0 ***USER FATAL MESSAGE 6261 (TIMTS6)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: NOT ALL KERNELS TESTED IN TIMTS9, THEREFORE RESULTS ARE
NOT WRITTEN TO THE OUTPUT DATA BLOCK

6262.0 ***SYSTEM FATAL MESSAGE 6262 (TIMTS6)

ERROR WHILE READING FILE1=%1

6263.0 ***USER FATAL MESSAGE 6263 (TIMTS9)

ILLEGAL DTI ENTRY INPUT FOR TIMETEST MODULE

Programmer information: BREAK POINTS ABOVE %1 CANNOT BE CONSIDERED FOR KER-

NEL %2

6264.0 *** USER FATAL MESSAGE 6264 (TABFM4).

Main Index
 594 MSC Nastran Error Messeges
Errors 6000 - 6999

ILLEGAL INPUT SPECIFIED ON DTI,ESTDATA BULK DATA ENTRY: %1%2

TIMING ESTIMATES WILL BE WRONG.

User action: ASSURE PROPER TYPE IS SPECIFIED IN ALL FIELDS.

6265.0 ***USER FATAL MESSAGE 6265 (DYNAM0)

THE FACTOR FILE IN THIS RUN HAS BEEN CREATED USING AN OLDER VERSION OF
THE PROGRAM IN WHICH SPARSE SOLUTION IS NOT SUPPORTED FOR THIS SOLUTION
SEQUENCE

User action: DO NOT USE THE RESTART CAPABILITY IN THIS RUN

6267.0 *** USER FATAL MESSAGE 6267,

CONTROL POINT NO.%1ON PANEL NO.%2 ALIGNS WITH THE EDGE OF BOX NO.%3ON
PANEL NO.%4

6269.0 USER INFORMATION MESSAGE 6269 (MPYABT)

THERE EXISTS INSUFFICIENT MEMORY FOR TRIPLE MULTIPLY. THEREFORE, TWO
EQUIVALENT MPYAD OPERATIONS WILL BE PERFORMED

User action: IF TRIPLE MULTIPLY METHOD IS DESIRED, THEN INCREASE MEMORY SIZE
BY=%1 WORDS

6270.0 *** USER FATAL MESSAGE 6270 (RCARD)

FIELD 2 OF THE FOLLOWING %1 ENTRY CONTAINS AN INVALID CHARACTER.

User information:
1. ENTRY: %2
2. FIELD 2: %3

6270.1 *** USER FATAL MESSAGE 6270 (RCARD)

FIELD 2 OF THE FOLLOWING %1 ENTRY CONTAINS EMBEDDED BLANKS.

User information:
1. ENTRY: %2
2. FIELD 2: %3

Main Index
 MSC Nastran Error Messeges 595
Errors 6000 - 6999

6271.0 *** USER FATAL MESSAGE 6271 (PRJVER)

PARAMETER NO. %1 OF "PROJVER" DMAP MODULE IS ILLEGAL.

6273.0 *** USER FATAL MESSAGE 6273 (PRJVER)

THE "SET" OPTION IS BEING REQUESTED IN THE "PRJVER" SUBROUTINE FOR A
DELETED OR NON-EXISTENT PROJECT/VERSION.

User information: PROJECT ID=%1, VERSION ID=%2, STATUS="%3"

6274.1 *** USER FATAL MESSAGE 6274 (PRJVER)

PROJECT ID OF %1 CANNOT BE FOUND IN THE "PROVER" TABLE.

6274.2 *** USER FATAL MESSAGE 6274

PROJECT-NO %1 OF DBSNO %2 CANNOT BE FOUND IN THE "PROVER" TABLE.

6274.4 *** USER FATAL MESSAGE 6274 (VWHCPJ)

PROJECT-ID %1 OF DBSNO%2 CANNOT BE FOUND IN THE "PROVER" TABLE.

6275.0 *** SYSTEM FATAL MESSAGE 6275 (PRJVER)

ERROR DETECTED IN THE "PROVER" TABLE.
6276.0 *** SYSTEM FATAL MESSAGE 6276 (PRJVER)
CURRENT PROJECT ID OF %1 AND VERSION ID OF %2 COULD NOT BE FOUND IN THE
2ND RECORD OF "PROVER" TABLE.

6277.0 *** USER WARNING MESSAGE 6277 (KSHERD),

THE EFFECTIVENESS FACTOR F%1=%2 FOR SHEAR ELEMENT ID. =%3 GIVES THE EFFEC-
TIVE AREA GREATER THAN THE ACTUAL AREA.

User action: CHECK EFFECTIVENESS FACTOR F%4 ON PSHEAR ENTRY.

6277.1 *** USER FATAL MESSAGE 6277 (KSHERD),

PSHEAR ID = %1 HAS BAD MATERIAL PROPERTY INFORMATION. POISSONS RATIO IS
TOO CLOSE TO -1.

User action: CHECK MATERIAL PROPERTY INFORMATION ON MATID = %2.

Main Index
 596 MSC Nastran Error Messeges
Errors 6000 - 6999

6278.0 *** USER FATAL MESSAGE 6278 (MTMD23)

THE %1 BULK DATA ENTRY SELECTED BY THE CASE CONTROL COMMAND %2 = %3
WAS NOT FOUND

6278.1 *** USER FATAL MESSAGE 6278

THE %1 BULK DATA ENTRY SELECTED BY SID = %3 WAS NOT FOUND

6279.0 *** USER WARNING MESSAGE 6279 (IFS6P)

THE DOPTPRM ENTRY SPECIFIES A DELP = %1.

User information: DELP > 1.0 MAY NOT BE USED

6280.0 *** USER INFORMATION MESSAGE 6280 (NCONVG)

AN EXCESSIVE NUMBER OF STIFFNESS MATRIX UPDATES HAS ACTIVATED DIVERGENCE
CONDITIONS.

6281.0 *** USER FATAL MESSAGE 6281 (SEP2D)

NO SUBCASES ARE SPECIFIED FOR THE RESIDUAL STRUCTURE.
IN A STATIC ANALYSIS, AT LEAST ONE SUBCASE MUST BE SPECIFIED FOR THE RESIDUAL
STRUCTURE.

6282.0 *** USER FATAL MESSAGE 6282 (SEP2D)

There are monitor points and some but not all subcases contain SUPER=ALL.

User information: This combination is not allowed.

User action: This fatal may be avoided by removing SUPER=ALL and specifying a fully expanded Case
Control structure or removing SUPER>0 and specifying SUPER=ALL above all subcases. Also, this fatal
may be bypassed by specifying SYSTEM(711)=1 but this may result in wrong answers for monitor point
data recovery.

6283.0 *** USER INFORMATION MESSAGE 6283 (MNPNTDR)

INTERNAL LOAD MONITOR POINTS (MONPNT2) ARE NOT SUPPORTED FOR STATIC
ANALYSIS WITH THERMAL LOADS. NO OUTPUT IS GENERATED FOR THEM.

6284.0 *** USER FATAL MESSAGE 6284 (APD0)

Main Index
 MSC Nastran Error Messeges 597
Errors 6000 - 6999

User information: GRID ID = %1 IS LISTED MORE THAN ONCE ON SET1 BULK DATA ENTRY
ID = %2.

User action: REMOVE THE DUPLICATE GRID FROM THE SET1 ENTRY.

6285.0 *** USER FATAL MESSAGE 6285 (VNASIN)

CHBDY%1 DOES NOT REFERENCE A PHBDY ENTRY.

6286.0 *** USER WARNING MESSAGE 6286 (ZREAD)

THE NDDL DESCRIPTION OF DATA BLOCK=%1, RECORD=%2,DOES NOT HAVE AN
EITHER/OR TO MATCH OPT=%3. ITEMS ARE ASSUMED TO BE UNDEFINED.

User information: PROBABLE CAUSE IS WRONG NDDL DESCRIPTION CODED, OR , WRONG

GENERIC DATABLOCK USED (E.G. OES INSTEAD OF OEF).

6287.0 *** SYSTEM WARNING MESSAGE 6287 (F04SUM)

FORTRAN UNIT=%1 CANNOT BE REWOUND BECAUSE IT IS LOCATED ON A NON-
REWINDABLE DEVICE.

User information: DIAG 49 PROCESSING IS TERMINATED.

User action: ASSIGN THE UNIT TO A REWINDABLE (TAPE/DISK) FILE AND RERUN JOB.

6288.0 *** USER FATAL MESSAGE 6288

UNABLE TO CONVERGE WITH ITERATIVE METHOD.

6288.1 *** USER FATAL MESSAGE 6288 (SITDRD)

UNABLE TO CONVERGE WITH ITERATIVE METHOD.

User action: INCREASE MAXIMUM NUMBER OF ITERATIONS OR USE DIRECT METHOD.

6288.4 *** SYSTEM WARNING MESSAGE 6288 (SDRVP)

UNABLE TO CONVERGE WITH ITERATIVE METHOD.

6290.0 *** USER WARNING MESSAGE 6290

Main Index
 598 MSC Nastran Error Messeges
Errors 6000 - 6999

TABFM6 SUPPORTS ONLY TYPES TABLE AND CASECC. ANOTHER TYPE WAS FOUND ON
DATA BLOCK %1.

6291.0 *** SYSTEM WARNING MESSAGE 6291 (DDRMM)

OUTPUT DATA BLOCK CORRESPONDING TO INPUT MODAL SOLUTION DATA BLOCK
%1 IS NOT PRESENT. INPUT DATA BLOCK THUSLY IGNORED.

6292.0 *** SYSTEM WARNING MESSAGE 6292 (DDRMM)

INVALID INPUT DATA DETECTED IN DATA BLOCK %1. PROCESSING STOPPED FOR THIS
DATA BLOCK.

6293.0 *** USER FATAL MESSAGE 6293 (DSAD16)

GRID NO. %1 REFERENCED ON A DRESP1 ENTRY COULD NOT BE FOUND.

User action: USE OF UNREFERENCED GRIDS IS NOT RECOMMENDED AND MAY INDI-
CATE A USER INPUT ERROR, RESULTS FOR OTHER RESPONSES ARE NOT AFFECTED.

6293.1 *** USER WARNING MESSAGE 6293 (DSD82A)

COMPONENT %2 OF GRID NO. %1 USED IN RESPONSE SET OF ELSENS COMMAND
EXCEEDS MAX DOFS ALLOWED. SYSTEM ACTION : RESET TO COMPONENT T1 AND EXE-
CUTION CONTINUED.

6293.2 *** USER FATAL MESSAGE 6293 (DSD82A)

COMPONENT %2 OF GRID NO. %1 USED ON DRESP1 ENTRIES EXCEEDS MAX DOFS
ALLOWED.

User action: CHECK IF GRID IS FOR FLUID/ACOUSTIC FIELD. IF YES, USE 1 FOR COMPO-
NENT.

6293.3 *** USER FATAL MESSAGE 6293 (CASELS)

RESPONSE SET %1 ON ELSENS/WETSENS CASE CONTROL COMMAND NOT DEFINED.

User action: DEFINE THE SET PRIOR TO ELSENS/WETSENS CASE CONTROL COMMAND.
FOR COMPONENT.

6293.4 *** USER FATAL MESSAGE 6293 (DSD82C)

Main Index
 MSC Nastran Error Messeges 599
Errors 6000 - 6999

DRESP1 ID %1 WITH RTYPE = DYSTIFF HAS A RESPONSE VALUE OF ZERO.

User information: THIS INDICATES THE LOAD AT THE POINT IS ZERO AND NOT A VALID
DYNAMIC STIFFNESS RESPONSE.

6294.0 *** SYSTEM FATAL MESSAGE 6294 (ACMG),

COUPLING CONTRIBUTION FOR THIS FLUID ELEMENT ID =%1 CAN NOT BE COM-
PUTED.

User action: CHECK THE GEOMETRY OF THE STRUCTURAL ELEMENT IN THE VICINITY
OF THIS ELEMENT.

6295.0 *** USER FATAL MESSAGE 6295 (GIGTKG)

User information: SPLINE3 %1 FOR CAERO %2 HAS ILLEGAL COMPONENT %3

6296.0 *** SYSTEM FATAL MESSAGE 6296 (qmatr)

UNABLE TO LOCATE A MEMBER OF DATABLOCK %1 (FILE %2) WITH ATTRIBUTES:

6296.1 *** SYSTEM FATAL MESSAGE 6296

UNABLE TO LOCATE %1 IN DATA BLOCK %2 (FILE %3).

6296.2 *** SYSTEM FATAL MESSAGE 6296

UNABLE TO LOCATE TRIM ID %1 ON A TRIM OR TRIM2 BULK DATA ENTRY.

6297.0 FORMAT 3000: # *** SYSTEM FATAL MESSAGE 6297 (EMG)

INCORRECT VALUE %1 HAS BEEN SPECIFIED FOR THE 22ND PARAMETER.

6297.1 *** SYSTEM FATAL MESSAGE 6297 (DSAH)

INCORRECT VALUE %1 HAS BEEN SPECIFIED FOR THE FIRST PARAMETER.

6298.0 *** USER FATAL MESSAGE 6298 (PSTA)

Main Index
 600 MSC Nastran Error Messeges
Errors 6000 - 6999

THE LEADING EDGE IS NOT SUPERSONIC: M=%1 AND SECANT LAMBDA=%2.

User information: WHEN USING PISTON THEORY WITH A SWEEP CORRECTION

(NTHRY=2), THE LEADING EDGE MUST BE SUPERSONIC; THAT IS, THE MACH NUMBER
MUST BE GREATER THAN THE SECANT OF THE SWEEP ANGLE.

User action: INCREASE THE MACH NUMBER OR USE AN ALTERNATIVE AERODYNAMIC

THEORY ( MACH BOX OR ZONA ).

6300.0 *** USER FATAL MESSAGE 6300 (FA1PKI)

SINGULAR MATRIX FOR INTERPOLATION IN %1

User information: THE USER INPUT VALUES OF K PRODUCED AN INTERPOLATION

MATRIX THAT IS ILL-CONDITIONED.

User action: ADJUST THE K VALUES INPUT ON THE MKAEROi ENTRIES.

6300.1 *** USER FATAL MESSAGE 6300 (FA1PKB)

COLUMN %1 OF THE FLUTTER SYSTEM MATRIX IS NULL. THIS CAN RESULT IN MEAN-
INGLESS FLUTTER RESULTS

User information: THE LIKELY CAUSE OF THIS MESSAGE IS THAT THERE ARE UNUSED
EPOINTS IN THE BULK DATA FILE.

User action: REMOVE UNUSED EPOINTS IN THE BULK DATA FILE.

6300.2 *** USER FATAL MESSAGE 6300 (FA1PKB)

COLUMN %1 OF THE FLUTTER SYSTEM MATRIX HAS NO STRUCTURAL OR AERODY-
NAMIC STIFFNESS.

User information: THE LIKELY CAUSE OF THIS MESSAGE IS THAT THERE IS A RIGID BODY
MODE THAT DOES PRODUCE AERODYNAMIC FORCES (E.G., A FORE-AFT MODE). FLUT-
TER RESULTS MAY BE CLEARER IF THIS MODE IS REMOVED FROM THE ANALYSIS.

6301.0 *** USER FATAL MESSAGE 6301 (DSAD14)

Main Index
 MSC Nastran Error Messeges 601
Errors 6000 - 6999

DIVERGENCE ROOT NO.%1 REQUESTED FOR MACH %2 EXCEEDS %3, THE NUMBER OF
ROOTS EXTRACTED AT THIS MACH NUMBER.

User action: DELETE THE DRESP1 ENTRY WITH DIVERGENCE SINCE IT DOES NOT
AFFECT THE DESIGN.

6302.0 *** SYSTEM FATAL MESSAGE 6302 (DSASRT)

INSUFFICIENT SPACE TO PROCESS GPTABD INFORMATION.

Programmer information: THE DSASRT PLACES A LIMIT OF %1 ON THE NUMBER OF ELE-

MENT TYPES. NASTRAN CURRENTLY SUPPORTS %2 TYPES.

6303.0 *** USER INFORMATION MESSAGE 6303 (BGICA)

NO BCONP BULK DATA ENTRIES ARE SPECIFIED.

6303.1 *** USER FATAL MESSAGE 6303 (BGICA)

NO BLSEG AND BSURF BULK DATA ENTRIES ARE SPECIFIED.

6304.0 *** SYSTEM FATAL MESSAGE 6304

%1 RECORD CANNOT BE LOCATED.

6305.0 *** USER INFORMATION MESSAGE 6305 (BGCAU1)

GRID ID = %1 DEFINED IN BOUTPUT ENTRY ID = %2 IS NOT A SECONDARY NODE

6305.1 *** USER FATAL MESSAGE 6305 (BGFRCR)

%1 ENTRY ID = %2 WHICH IS REFERRED IN BCONP ENTRY ID =%3 IS UNDEFINED.

6306.0 *** USER INFORMATION MESSAGE 6306 (BGCORA)

NO BWIDTH BULK DATA ENTRIES ARE SPECIFIED, DEFAULT WIDTH VALUE OF UNITY
WILL BE USED.

6306.1 *** USER INFORMATION MESSAGE 6306 (BGFRCR)

NO BFRIC BULK DATA ENTRIES ARE SPECIFIED, DEFAULT VALUES WILL BE USED.

6306.2 *** USER INFORMATION MESSAGE 6306 (BGWIDR)

Main Index
 602 MSC Nastran Error Messeges
Errors 6000 - 6999

WIDTHS ARE NOT SPECIFIED FOR SECONDARY ID = %1 DEFAULT VALUES OF UNITY

ARE ASSUMED FOR ALL THE SECONDARY SEGMENTS.

6307.0 *** USER INFORMATION MESSAGE 6307 (BGPENR)

THE MAGNITUDE OF F0 IS CHANGED TO ZERO FOR BNPEN ENTRY ID = %1.

6307.1 *** USER INFORMATION MESSAGE 6307 (BGPENR)

THE MAGNITUDE OF C0 IS CHANGED TO ZERO FOR BNPEN ENTRY ID = %1.

6308.0 *** USER FATAL MESSAGE 6308 (BGCOCL)

SECONDARY REGION ID = %1 SPECIFIED IN BCONP ENTRY ID = %2 IS NOT DEFINED.

6308.1 *** USER FATAL MESSAGE 6308 (BGCOCL)

PRIMARY REGION ID = %1 SPECIFIED IN BCONP ENTRY ID = %2 IS NOT DEFINED.

6309.0 *** USER FATAL MESSAGE 6309 (BGCOCL)

SECONDARY REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 IS NOT UNIQUE.

6309.1 *** USER FATAL MESSAGE 6309 (BGCOCL)

PRIMARY REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 IS NOT UNIQUE.

6309.2 *** USER FATAL MESSAGE 6309 (BGLSCW)

BOTH SECONDARY AND PRIMARY CAN NOT BE CLOSED FOR A SYMMETRIC CONTACT
REGION - BCONP ENTRY ID = %1

6309.3 *** USER FATAL MESSAGE 6309 (BGLSCW)

LINE REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 DOES NOT HAVE UNIQUE
GRID POINTS.

6309.4 *** USER FATAL MESSAGE 6309 (BGLSCW)

LINE REGION ID = %1 REFERRED IN BCONP ENTRY ID = %2 CAN NOT HAVE SAME FIRST
AND SECOND GRID POINTS.
6309.5 *** USER FATAL MESSAGE 6309 (BGLSCW)
GRID POINT ID = %1 REFERRED IN BOTH SECONDARY AND PRIMARY REGIONS FOR
BCONP ENTRY ID = %2

User action: DO NOT INCLUDE A GRID POINT IN SECONDARY AND PRIMARY REGIONS.

Main Index
 MSC Nastran Error Messeges 603
Errors 6000 - 6999

6310.0 *** USER FATAL MESSAGE 6310 (BGCOCL)

SECONDARY BLSEG ENTRY ID = %1 REFERRED IN BCONP ENTRY ID = %2 HAS ONLY ONE
GRID POINT FOR THE SYMMETRIC CASE.

User action: SECONDARY BLSEG ENTRY SHOULD HAVE AT LEAST TWO GRID POINTS FOR
THE SYMMETRIC CASE.

6310.1 *** USER FATAL MESSAGE 6310 (BGCOCL)

PRIMARY BLSEG ENTRY ID = %1 REFERRED IN BCONP ENTRY ID = %2 HAS ONLY ONE
GRID POINT.

User action: PRIMARY BLSEG ENTRY SHOULD HAVE AT LEAST TWO GRID POINTS.

6311.0 *** USER FATAL MESSAGE 6311 (BGCOCL)

INCONSISTENT BCONP ENTRY ID = %1 HAS SECONDARY BLSEG ENTRY ID = %2 AND
PRIMARY BSURF ENTRY ID = %3.

6311.1 *** USER FATAL MESSAGE 6311 (BGCOCL)

INCONSISTENT BCONP ENTRY ID = %1 HAS SECONDARY BSURF ENTRY ID = %2 AND
PRIMARY BLSEG ENTRY ID = %3.

6312.0 *** USER FATAL MESSAGE 6312 (BGCOCL)

SECONDARY GRID POINT =%1 AND THE CORRESPONDING PRIMARY GRID POINTS =
%2%3 OF BCONP ENTRY ID = %4 DO NOT LIE IN THE SPECIFIED SLIDE LINE PLANE.

6313.0 *** USER WARNING MESSAGE 6313 (BGSRCD)

SECONDARY GRID POINT =%1 HAS ZERO LENGTH PRIMARY SEGMENT WITH GRID
POINTS =%2%3.

6314.0 *** USER FATAL MESSAGE 6314 (BGSRCD)

INITIAL PENETRATION = %1 OF SECONDARY GRID POINT = %2 INTO PRIMARY SEG-
MENT = %3 - %4 IS NOT ALLOWED.

6315.0 *** USER WARNING MESSAGE 6315 (BGSRCD)

Main Index
 604 MSC Nastran Error Messeges
Errors 6000 - 6999

COORDINATES OF SECONDARY GRID POINT =%1 ARE CHANGED TO %2 %3 %4 FROM

%5 %6 %7 TO PRECLUDE PENETRATION.

6316.0 *** SYSTEM FATAL MESSAGE 3200 (BGTPEN)

SURFACE CONTACT FOR THE BCONP ENTRY ID = %1 IS NOT SUPPORTED.

6319.0 *** USER FATAL MESSAGE 6319 (STPDA)

MACH NUMBER %1 WAS NOT SPECIFIED ON AN AEFACT BULK DATA ENTRY %2

User information: A MACH NUMBER LISTED ON A MKAEROI ENTRY CANNOT BE FOUND

ON AN AEFACT ENTRY REFERENCED BY A PAERO4 ( STRIP THEORY ) BULK DATA ENTRY.

6320.0 *** USER INFORMATION MESSAGE 6320 (SITDRV)

SOLUTION WAS CONTINUED BECAUSE EXTERNAL CONVERGENCE CRITERION WAS
PASSED.

6321.0 *** USER FATAL MESSAGE 6321 (DOPR1B)

THE INDEPENDENT DESIGN VARIABLE ID %1 APPEARS MORE THAN ONCE ON THE
DLINK ENTRY ASSOCIATED WITH DEPENDENT DESIGN VARIABLE ID %2

User action: REMOVE THE DUPLICATE REFERENCE TO THE INDEPENDENT DESIGN VARI-
ABLE.

6321.1 *** USER FATAL MESSAGE 6321 (DOPR1B)

THE DESVAR ENTRY ID %1 REFERENCES A DDVAL ENTRY ID %2
THAT IS NOT SPECIFIED IN THE BULK DATA.

User action: REMOVE THE DDVAL ENTRY FROM DESVAR ENTRY OR ADD A DDVAL
ENTRY.

6324.0 *** SYSTEM FATAL MESSAGE 6324 (PEDGED)

THE TWO SILS FOR EDGE ID=%1 ARE BOTH ZERO.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6328.0 *** SYSTEM FATAL MESSAGE 6328 (EMGSIL)

Main Index
 MSC Nastran Error Messeges 605
Errors 6000 - 6999

THE SIL FOR GRID ID=%1 IS %2 WHICH IS NOT POSITIVE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6329.0 *** USER FATAL MESSAGE 6329

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2

User action: CHECK GEOMETRY OF ELEMENT ID=%3 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.2 *** USER FATAL MESSAGE 6329 (SHTRPD)

BAD GEOMETRY CONDITION AT GAUSS POINT :%1

User action: CHECK GEOMETRY OF ELEMENT ID=%2 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.3 *** SYSTEM FATAL MESSAGE 6329 (SHPSHD)

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1, Y=%2 FOR ELE-
MENT ID=%3.

User action: CHECK GEOMETRY OF THIS FACE. OTHERWISE, CONTACT HEXAGON AB

CLIENT SUPPORT.

6329.4 *** USER FATAL MESSAGE 6329 (SDPS1D)

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2

User action: CHECK GEOMETRY OF ELEMENT ID=%3 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.5 *** USER FATAL MESSAGE 6329 (PTERMD)

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 Z=%3

User action: CHECK GEOMETRY OF ELEMENT ID=%4 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.6 *** SYSTEM FATAL MESSAGE 6329 (PFACED)

Main Index
 606 MSC Nastran Error Messeges
Errors 6000 - 6999

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 FOR FACE ID=%2.

User action: CHECK GEOMETRY OF THIS FACE. OTHERWISE, CONTACT HEXAGON AB

CLIENT SUPPORT.

6329.7 *** SYSTEM FATAL MESSAGE 6329 (PEDGED)

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 FOR EDGE ID=%2.

User action: CHECK GEOMETRY OF THIS EDGE. OTHERWISE, CONTACT HEXAGON AB

CLIENT SUPPORT.

6329.8 *** USER FATAL MESSAGE 6329 (JACTD)

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 Z=%3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6329.12 *** USER FATAL MESSAGE 6329

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2

User action: CHECK GEOMETRY OF ELEMENT ID=%3 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.15 *** USER FATAL MESSAGE 6329

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2 Z=%3

User action: CHECK GEOMETRY OF ELEMENT ID=%4 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.16 *** USER FATAL MESSAGE 6329

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: =%1

User action: CHECK GEOMETRY OF ELEMENT ID=%2 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.18 *** USER FATAL MESSAGE 6329 (EBMVLD)

Main Index
 MSC Nastran Error Messeges 607
Errors 6000 - 6999

THE DETERMINANT OF JACOBIAN IS ZERO AT GAUSS POINT: X=%1 Y=%2

User action: CHECK GEOMETRY OF ELEMENT ID=%3 OTHERWISE, CONTACT HEXAGON

AB CLIENT SUPPORT.

6329.19 *** USER FATAL MESSAGE 6329 (BMPPMD)

THE CURVATURE OF ARC AT GAUSS POINT %1 FOR THE BEAM ELEMENT %2 IS ZERO.

User action: CHECK GEOMETRY OF ELEMENT OTHERWISE, CONTACT HEXAGON AB CLI-

ENT SUPPORT.

6329.20 *** USER FATAL MESSAGE 6329 (BMPPMD)

THE SLOPE OF ARC AT GAUSS POINT %1 FOR THE BEAM ELEMENT %2 IS ZERO.

User action: CHECK GEOMETRY OF ELEMENT OTHERWISE, CONTACT HEXAGON AB CLI-

ENT SUPPORT.

6331.0 *** SYSTEM FATAL MESSAGE 6331 (PSHBUT)

INADMISSIBLE CASE NUMBER=%1 FOR BUBBLE FUNCTIONS TRIAP SHELL ELEMENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.1 *** SYSTEM FATAL MESSAGE 6331 (PSHBUB)

INADMISSIBLE CASE NUMBER=%1 FOR BUBBLE FUNCTIONS QUADP SHELL ELEMENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.2 *** SYSTEM FATAL MESSAGE 6331 (PFAC4L)

LOGIC ERROR: LOOP =%1, IERROR=%2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.3 *** SYSTEM FATAL MESSAGE 6331 (ETREPL)

LOGIC ERROR: LOOP =%1 IS GREATER THAN 21 FOR THE TRIA ELEMENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 608 MSC Nastran Error Messeges
Errors 6000 - 6999

6331.4 *** SYSTEM FATAL MESSAGE 6331 (ETREPL)

LOGIC ERROR: NUMBER OF FUNCTIONS USED =%1 IS GREATER THAN THE MAX FUNC-
TIONS =%2.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.5 *** SYSTEM FATAL MESSAGE 6331 (ETREPL)

LOGIC ERROR: MAX FUNCTIONS =%1 FOR WHICH SPACE IS RESERVED IS LESS THAN 1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.6 *** SYSTEM FATAL MESSAGE 6331 (ETEPL)

LOGIC ERROR: LOOP =%1 IS GREATER THAN 21 FOR THE PENTA ELEMENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.7 *** SYSTEM FATAL MESSAGE 6331 (EPEPL)

LOGIC ERROR: GRID SIL VALUES FOR QUADRILATERAL FACE ARE NOT UNIQUE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.8 *** SYSTEM FATAL MESSAGE 6331 (AAAAAAAA)

LOGIC ERROR: ELEMENT TYPE = %1 (ELEMENT ID =%2) IS NOT A SUPPORTED P-ELE-
MENT TYPE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.9 *** SYSTEM FATAL MESSAGE 6331 (BUBITT)

INADMISSIBLE CASE NUMBER=%1 FOR BUBBLE FUNCTIONS QUADP/TRIAP SHELL ELE-
MENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.10 *** SYSTEM FATAL MESSAGE 6331 (EMGMID)

Main Index
 MSC Nastran Error Messeges 609
Errors 6000 - 6999

LOGIC ERROR: L1 =%1, L2=%2, L3=%3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6331.11 *** SYSTEM FATAL MESSAGE 6331 (JACPD)

LOGIC ERROR: ZERO POLYNOMIAL COEFFICIENT

6333.0 *** SYSTEM FATAL MESSAGE 6333 (EQNINC)

DEQIND DATA BLOCK HAS A LENGTH OF %1 WHICH IS NOT A MULTIPLE OF %2.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6334.0 *** SYSTEM FATAL MESSAGE 6334 (EQNINC)

THE DEQATN ENTRY ID=%1 CAN NOT BE FOUND IN THE DEQIND DATA BLOCK.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6334.1 *** SYSTEM FATAL MESSAGE 6334

THE DEQATN ENTRY ID=%1 CANNOT BE FOUND IN THE EQUATION POOL.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6334.2 *** USER FATAL MESSAGE 6334 (EMGPTD)

THE DEQATN ENTRY ID=%1 CAN NOT BE FOUND IN THE DEQIND DATA BLOCK.

User action: CHECK TEMPF ENTRY SPECIFICATION.

6335.0 *** SYSTEM FATAL MESSAGE 6335 (EQNINC)

ERROR DETECTED IN DEQATN TABLE.

Programmer information: LENGTH OF RECORD=%1, LENGTH OF HEADER=%2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6336.0 *** USER WARNING MESSAGE 6336 (EQNINC)

Main Index
 610 MSC Nastran Error Messeges
Errors 6000 - 6999

THE NUMBER OF ARGUMENTS IN THE DEQATN ENTRY ID=%1 IS %2.

User information: IT IS SUPPOSED TO BE %3.

User action: CHECK MSC NASTRAN USERS MANUAL FOR THE BULK DATA ENTRY THAT
REFERS TO THIS DEQATN ENTRY.

6338.0 *** SYSTEM FATAL MESSAGE 6338 (GIFACD)

LOGIC ERROR: IERR=%1, N=%2, J=%3, X=%4

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6341.0 *** SYSTEM FATAL MESSAGE 6341 (PEDGED)

NFUN=%1 OBTAINED FROM PEDGEL SUBROUTINE IS INCONSISTENT WITH (PEDGE-
1)=%2 FROM SLT RECORD.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6341.1 *** SYSTEM FATAL MESSAGE 6341 (EMSPPD)

NFUN=%1 FOR KEDGE=%2 OBTAINED FROM EQEPL SUBROUTINE IS INCONSISTENT
WITH (PEDGE-1)=%3 FROM EHT RECORD.

6341.2 *** SYSTEM FATAL MESSAGE 6341 (EMBPPD)

NFUN=%1 FOR KEDGE=%2 OBTAINED FROM EBEPL SUBROUTINE IS INCONSISTENT
WITH (PEDGE-1)=%3 FROM EHT RECORD.

6341.3 *** SYSTEM FATAL MESSAGE 6341

NFUN=%1 FOR KDOFTP=%2 OBTAINED FROM %3 SUBROUTINE IS INCONSISTENT
WITH (PEDGE-1)=%4 FROM SLT RECORD.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6342.0 *** USER FATAL MESSAGE 6342 (PFACED)

FOR FACE ID=%1 ONLY ONE OF THE FIELDS: FEQNID, FTABID, AND F1 THROUGH F9
CAN BE USED TO SPECIFY THE PFACE LOAD.

User action: CHECK PFACE ENTRY FOR THIS FACE.

Main Index
 MSC Nastran Error Messeges 611
Errors 6000 - 6999

6342.1 *** USER FATAL MESSAGE 6342 (PEDGED)

FOR EDGE ID=%1 ONLY ONE OF THE FIELDS: FEQNID, FTABID, AND F1 THROUGH F4
CAN BE USED TO SPECIFY THE PEDGE LOAD.

User action: CHECK PEDGE ENTRY FOR THIS EDGE.

6342.2 *** USER FATAL MESSAGE 6342 (FCEN3D)

FOR FACE ID=%1 ON GMBC LOAD ID=%2 SPC ID=%3 ONLY ONE OF THE FIELDS: IDEQN,
IDTAB, AND D1 THROUGH D6 CAN BE USED TO SPECIFY THE ENFORCED DISPLACE-
MENT.

User action: CHECK THE BCFACE OR BCSURF ENTRIES

6342.3 *** USER FATAL MESSAGE 6342 (EMGPTD)

FOR ELEMENT ID=%1 ONLY ONE OF THE FIELDS: FEQNID, FTABID, AND F1 THROUGH
F4 CAN BE USED TO SPECIFY THE TEMPERATURE.

User action: CHECK TEMPF ENTRY SPECIFICATION.

6342.4 *** USER FATAL MESSAGE 6342 (EGENDD)

FOR EDGE ID=%1 ON GMBC LOAD ID=%2 SPC ID=%3, ONLY ONE OF THE FIELDS:
IDEQN, IDTAB, AND D1 THROUGH D4 CAN BE USED TO SPECIFY THE ENFORCED DIS-
PLACEMENT.

User action: CHECK THE BCEDGE, BCCURVE, BCFACE OR BCSURF ENTRIES

6342.5 *** USER FATAL MESSAGE 6342 (FCEN4D)

FOR FACE ID=%1 ON GMBC LOAD ID=%2 SPC ID=%3 ONLY ONE OF THE FIELDS: IDEQN,
IDTAB, AND D1 THROUGH D9 CAN BE USED TO SPECIFY THE ENFORCED DISPLACE-
MENT.

User action: CHECK THE BCFACE OR BCSURF ENTRIES.

6343.0 *** USER FATAL MESSAGE 6343 (PFACED)

Main Index
 612 MSC Nastran Error Messeges
Errors 6000 - 6999

NO METHOD CAN BE FOUND ON THE PFACE ENTRY ID=%1 TO DEFINE THE LOAD.

User action: CHECK PFACE ENTRY FOR THIS FACE.

6343.1 *** USER FATAL MESSAGE 6343 (PEDGED)

NO METHOD CAN BE FOUND ON THE PEDGE ENTRY ID=%1 TO DEFINE THE LOAD.

User action: CHECK PEDGE ENTRY FOR THIS EDGE.

6345.0 *** SYSTEM FATAL MESSAGE 6345

MDOFS OF KDOFTP=%1 IS EQUAL TO %2 WHICH IS LESS THAN THE MINIMUM ALLOW-
ABLE VALUE OF 3.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6349.0 *** USER FATAL MESSAGE 6349 (PFTBLS)

TABLE3D ID=%1 REQUIRES THE SPECIFICATION OF AT LEAST 4 POINTS.

6350.0 *** USER FATAL MESSAGE 6350 (PFTBLI)

THE TABLE3D ENTRY ID=%1 DOES NOT EXIST.

6352.0 *** SYSTEM FATAL MESSAGE 6352 (%1)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6352.1 *** SYSTEM FATAL MESSAGE 6352 (AAAAAA)

LOGIC ERROR: KERROR=%1, IAPP=%2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6352.2 *** SYSTEM FATAL MESSAGE 6352 (PFUNSD)

LOGIC ERROR: ILLEGAL VALUE FOR IOPT OR NMAX.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: IOPT=%1 NMAX=%2

Main Index
 MSC Nastran Error Messeges 613
Errors 6000 - 6999

6352.3 *** SYSTEM FATAL MESSAGE 6352 (AAAAAAAA)

LOGIC ERROR: KERROR=%1, GID=%2

Programmer information: THE PARENT SUBROUTINE IS %3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6352.4 *** SYSTEM FATAL MESSAGE 6352 (REMENT)

LOGIC ERROR: KERROR=%1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: RECORD NAME = %2

6352.5 *** SYSTEM FATAL MESSAGE 6352 (BMPEED)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KDOFTP=%2 DOFSIL=%3

6352.6 *** SYSTEM FATAL MESSAGE 6352 (ADPVAL)

LOGIC ERROR: KERROR=%1

Programmer information: OPTION=%2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6352.7 *** SYSTEM FATAL MESSAGE 6352

LOGIC ERROR: KERROR=%1, ADAPT ID=%2.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6352.8 *** USER INFORMATION MESSAGE 6352

Main Index
 614 MSC Nastran Error Messeges
Errors 6000 - 6999

SYSTEM(228)=%1 HAS BEEN SPECIFIED TO USE %2 METHOD FOR ADAPTIVITY ERROR-

ESTIMATE.

6352.9 *** SYSTEM FATAL MESSAGE 6352 (ELPOLY)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KPTYPE=%2, NPTYPE=%3.

6352.10 *** SYSTEM FATAL MESSAGE 6352 (ELPOLY)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KGEFB=%2, NGEFB=%3.

6352.11 *** SYSTEM FATAL MESSAGE 6352 (ELVOLD)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: LTAB=%2, NELEM=%3, NWD=%4, KPTYPE=%5

.
6352.12 *** SYSTEM FATAL MESSAGE 6352 (ELVOLD)
LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KPTYPE=%2 IS NOT SUPPORTED.

6352.13 *** SYSTEM FATAL MESSAGE 6352 (ELVOLW)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KPTYPE=%2, IVOLX=%3

Main Index
 MSC Nastran Error Messeges 615
Errors 6000 - 6999

6352.14 *** SYSTEM FATAL MESSAGE 6352 (ELVOLW)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KPTYPE=%2, LVOLX=%3, NWD=%4, NELEM=%5

6352.15 *** SYSTEM FATAL MESSAGE 6352 (ELVOLW)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KPTYPE=%2

6352.16 *** SYSTEM FATAL MESSAGE 6352 (%1)

LOGIC ERROR: KERROR=%2.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: KCOL=%3 IS NOT SUPPORTED. THE PARENT SUBROUTINE IS %4

6352.17 *** SYSTEM FATAL MESSAGE 6352 (EMGPGD)

LOGIC ERROR : JXGAUS(1..3) = %1 JW = %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6352.18 *** SYSTEM FATAL MESSAGE 6352 (ADPOLY)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: III=%2%3%4, IP123=%5, GEFB=%6, KORDER=%7, EID=%8

6352.19 *** SYSTEM FATAL MESSAGE 6352 (ADPSAV)

Main Index
 616 MSC Nastran Error Messeges
Errors 6000 - 6999

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: IERRN=%2, LERRN=%3, NWERRN=%4 SHOULD ALL BE POSITIVE.

6352.20 *** SYSTEM FATAL MESSAGE 6352 (ADPSAV)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: IPVALN=%2, LPVALN=%3, NWPVALN=%4 SHOULD ALL BE POSI-

TIVE.

6352.21 *** SYSTEM FATAL MESSAGE 6352 (ADPSAV)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: LERRN=%2 IS NOT A MULTIPLE OF NWERRN=%3

6352.22 *** SYSTEM FATAL MESSAGE 6352 (ADPSAV)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: NVIEWX=%2, NWVIEW=%3, LVIEWX=%4, KPTYPE=%5

6352.23 *** SYSTEM FATAL MESSAGE 6352 (ADPVLN)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: NPMRG=%2, NWPMRG=%3, LPMRT=%4

6352.24 *** SYSTEM FATAL MESSAGE 6352 (ADPVLN)

Main Index
 MSC Nastran Error Messeges 617
Errors 6000 - 6999

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: NPVAL)=%2, NWPVAL=%3, LPVALO=%4

6352.25 *** SYSTEM FATAL MESSAGE 6352 (ADPVLN)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: EID=%2 CAN NOT BE FOUND IN THE PVALN TABLE.

6352.26 *** SYSTEM FATAL MESSAGE 6352 (ADPWHY)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: THE PARENT SUBROUTINE IS %2

6352.27 *** SYSTEM FATAL MESSAGE 6352 (ADPWHY)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: EID=%2 IS MISSING FROM THE ERRNEW TABLE.

Programmer information: THE PARENT SUBROUTINE IS A8

6352.28 *** SYSTEM FATAL MESSAGE 6352 (ESTBLD)

LOGIC ERROR: KERROR=%1.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: MAXLST=%2 IS SMALLER THAN %3=%4

6352.29 *** SYSTEM FATAL MESSAGE 6352 (TETIND)

Main Index
 618 MSC Nastran Error Messeges
Errors 6000 - 6999

LOGIC ERROR: 1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: GROUP NO = %1, REF. TO INTEGRATION POINT = %2 DOES NOT

EXIST

6352.30 *** SYSTEM FATAL MESSAGE 6352 (TETIND)

LOGIC ERROR: 2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: IC = %1 IS NOT EQUAL TO NC = %2

6352.31 *** SYSTEM FATAL MESSAGE 6352 (TETIND)

LOGIC ERROR: 3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: IN = %1 IS NOT EQUAL TO N = %2

6352.32 *** SYSTEM FATAL MESSAGE 6352 (GETPVD)

LOGIC ERROR: 4

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: RULE %1 IS NOT INSTALLED.

6352.33 *** SYSTEM WARNING MESSAGE 6352 (MSGDRV)

LOGIC ERROR: 1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: MESSAGE UTILITY IS CALLED WITH WRONG POSION VALUE = %1

THE CORRESPONDING POSITION VARIABLE IS IGNORED. CHECK MESSAGE NO = %2,
VER = %3

Main Index
 MSC Nastran Error Messeges 619
Errors 6000 - 6999

6352.34 *** SYSTEM WARNING MESSAGE 6352 (MSGDRV)

LOGIC ERROR: %1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: %2

6352.35 *** SYSTEM WARNING MESSAGE 6352 (MSGDRV)

LOGIC ERROR: %1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

User information: %2

6352.36 *** USER FATAL MESSAGE 6352 (TOLSCASE)

CANNOT FIND NLPARM %1

User action: SUPPLY NLPARM RECORDS FOR ALL SUBCASES

6353.0 *** USER INFORMATION MESSAGE 6353 (EGENDD)

ENFORCED DISPLACEMENT VECTOR IS NULL FOR COMPONENT=I OF EDGE GENER-
ATED BY GRID %1 AND %2
IN FACE ID=%3 ON GMBC LOAD ID=%4 AND SPC ID=%5.

6353.1 *** USER INFORMATION MESSAGE 6353 (EGENDD)

ENFORCED DISPLACEMENT VECTOR IS NULL FOR COMPONENT=I OF EDGE ID=%1 ON
GMBC LOAD ID=%2 AND SPC ID=%3.

6353.2 *** USER WARNING MESSAGE 6353 (FCUCND)

ENFORCED DISPLACEMENT VECTOR FOR COMPONENT=%1 OF FACE ID=%2 ON GMBC
LOAD ID=%3 AND SPC ID=%4 IS NULL.

6354.0 *** SYSTEM FATAL MESSAGE 6354 (FCEN3D)

Main Index
 620 MSC Nastran Error Messeges
Errors 6000 - 6999

ALL COMPONENTS FOR FACE ID=%1 IN FCEND RECORD ARE ZERO.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6354.1 *** SYSTEM FATAL MESSAGE 6354 (EGENDD)

ALL COMPONENTS OF EDGE ID=%1 IN EGEND RECORD ARE ZERO.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6355.0 *** SYSTEM FATAL MESSAGE 6355 (FCEN3D)

GRID ID(S) IN GPSIL ARRAY AND FCEND TABLE ARE NOT CONSISTENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: GP IN FCEND:%1

%2
GP IN GPSIL:%3
%4

6355.1 *** SYSTEM FATAL MESSAGE 6355 (EGENDD)

GRID ID(S) IN GPSIL ARRAY AND EGEND TABLE ARE NOT CONSISTENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: GP IN EGEND:%1

GP IN GPSIL:%2

6355.2 *** SYSTEM FATAL MESSAGE 6355 (FCEN4D)

GRID ID(S) IN GPSIL ARRAY AND FCEND TABLE ARE NOT CONSISTENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information:
FCEND:%1
%2
GPSIL:%3
%4

Main Index
 MSC Nastran Error Messeges 621
Errors 6000 - 6999

6357.0 *** USER FATAL MESSAGE 6357

NO GRID POINTS FOUND

6357.1 *** USER WARNING MESSAGE 6357 (AFGMNF)

THE ADAMS/FLEX MNF GENERATION MODULE FOUND NO GRID POINTS IN THE
MODEL FOR SUPERELEMENT ID %1.
MNF GENERATION ABORTED.

User information:
No grid pints have been assigned to the specified superelement. The ADAMS/FLEX modal neutral file gen-
eration requires that GRID points be present and that at least one mode shape be available.

User action:
Review superelement definitions and ensure that each superelement is assigned at least one GRID point.

6359.0 *** USER WARNING MESSAGE 6359 (PREMAT)

MAT2 OR MAT9 ENTRY COMBINED WITH ISOTROPIC CREEP FORMULATION MAY PRO-
DUCE INCORRECT RESULTS.

6361.0 *** USER INFORMATION MESSAGE 6361 (ULANCZ)

UNSYMMETRIC REAL LANCZOS DIAGNOSTICS.

6361.1 *** SYSTEM INFORMATION MESSAGE 6361 --

REIGL MODULE DIAGNOSTICS
THESE DIAGNOSTICS ARE REQUESTED BY MSGLVL = %1 ON THE EIGRL ENTRY.
INITIAL PROBLEM SPECIFICATION
DEGREES OF FREEDOM = %2 MESSAGE LEVEL = %3
LEFT END POINT = %4
NUMBER OF MODES = %5 OUTPUT UNIT = %6
RIGHT END POINT = %7
MODE FLAG = %8 SIZE OF WORKSPACE = %9
CENTER FREQUENCY = %10
PROBLEM TYPE = %11 MAXIMUM BLOCK SIZE = %12
ACCURACY REQUIRED = %13
SHIFTING SCALE = %14

Main Index
 622 MSC Nastran Error Messeges
Errors 6000 - 6999

6361.2 *** USER INFORMATION MESSAGE 6361 (CLASDD)

COMPLEX LANCZOS DIAGNOSTICS.
THIS DIAGNOSTICS IS REQUESTED BY DIAG12.
INITIAL PROBLEM SPECIFICATION
DEGREES OF FREEDOM = %1 ACCURACY REQUIRED = %2
REQUESTED MODES = %3 NUMBER OF SHIFTS = %4
DAMPING MODE FLAG = %5 SIZE OF WORKSPACE = %6

6362.0 *** SYSTEM FATAL MESSAGE 6362, (EVLFCE),

THE ENFORCED DISPLACEMENT VALUE OF THE GRIP POINT WHICH BELONGS
TO THE FACE ID = %1 DOES NOT EXIST.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE.

6363.0 *** SYSTEM FATAL MESSAGE 6363, (EVLFCE),

THE ENFORCED DISPLACEMENT VECTOR COLUMN DOES NOT EXIST
FOR FACE ID = %1 FOR COMPONENT = %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE (IERROR=%3).

6363.1 *** SYSTEM FATAL MESSAGE 6363, (EVLEDG),

THE ENFORCED DISPLACEMENT VECTOR COLUMN DOES NOT EXIST
FOR EDGE ID = %1 FOR COMPONENT = %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE (IERROR=%3).

6364.0 *** SYSTEM FATAL MESSAGE 6364, (EVLFCE),

Main Index
 MSC Nastran Error Messeges 623
Errors 6000 - 6999

THE ENFORCED DISPLACEMENT VECTOR LENGTH DOES NOT MATCH

WITH THE CALCULATED VALUE FOR THE FACE ID = %1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE.

6364.1 *** SYSTEM FATAL MESSAGE 6364, (EVLEDG),
THE ENFORCED DISPLACEMENT VECTOR LENGTH DOES NOT MATCH
WITH THE CALCULATED VALUE FOR THE EDGE ID = %1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE.

6365.0 *** SYSTEM FATAL MESSAGE 6365, (EVLFCE),

THE COMPONENT: %1 IS INVALID FOR FACE ID = %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK SPCDE/SPCDF RECORDS.

6367.0 *** USER FATAL MESSAGE 6367, (POLYD),

GRID IDS =%1%2 ARE VERY CLOSE TO EACH OTHER

User action: CHECK GRID ENTRIES.

6367.1 *** USER FATAL MESSAGE 6367, (POLYD),

GRID OR POINT ID =%1 FOR ELEMENT ID =%2 IS UNDEFINED.

6367.2 *** USER FATAL MESSAGE 6367, (OPTGPC)

GRID OR POINT ID =%1 FOR FEEDGE/FEFACE ID = %2 IS UNDEFINED.

6367.3 *** USER FATAL MESSAGE 6367, (EVLPND),

GRID OR POINT ID =%1 FOR FEEDGE ID =%2 IS UNDEFINED.

6369.0 *** USER FATAL MESSAGE 6369, (GP0DA),

Main Index
 624 MSC Nastran Error Messeges
Errors 6000 - 6999

THE SELECTED ADAPT SET ID =%1 CANNOT BE FOUND.

User action: CHECK ADAPT AND PSET BULK DATA ENTRIES.

6370.0 *** USER FATAL MESSAGE 6370, (POLYD),

FINAL EDGE OR FACE TABLE IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6370.1 *** USER FATAL MESSAGE 6370, (GP0P4)

INVALID DATA

6370.2 *** USER FATAL MESSAGE 6370, (GP0P4),

FINAL ELEMENT PROPERTY TABLE CREATED IN GP0D IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6370.9 *** USER FATAL MESSAGE 6370,

FINAL EDGE OR FACE TABLE CREATED IN GP0DA IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6371.0 *** USER FATAL MESSAGE 6371, (GP0DA),

BOTH THE ADAPT AND PSET ENTRIES ARE PRESENT.

User information: EITHER THE ADAPT OR PSET ENTRY MAY BE SPECIFIED BUT NOT BOTH.

6374.0 *** SYSTEM FATAL MESSAGE 6374,

ELEMENT TYPE =%1 IS NOT SUPPORTED IN P-ELEMENT ANALYSIS.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: GP0 MODULE FAILED TO RECOGNIZE THIS ELEMENT TYPE

CHECK GPTABD ROUTINE.

6375.0 *** SYSTEM FATAL MESSAGE 6375, (GP0E),

Main Index
 MSC Nastran Error Messeges 625
Errors 6000 - 6999

THE FINAL EDGE OR FACE TABLE CREATED IN GP0D IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6376.0 *** SYSTEM FATAL MESSAGE 6376, (GP0E),

THE FINAL EDGE TABLE CREATED IN GP0H IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6376.1 *** SYSTEM FATAL MESSAGE 6376, (GP0E),

THE FINAL TABLE 2 CREATED IN GP0E IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6376.2 *** SYSTEM FATAL MESSAGE 6376, (GP0DE),
TABLE 2 CREATED IN GP0DA IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6376.3 *** USER FATAL MESSAGE 6376 (CIFGRI)

THE GMBNDC BOUNDARY ID = %1 REFERENCED BY GMINTC ELEMENT ID = %2 HAS AN
UNDEFINED
P-ELEMENT EDGE BETWEEN GRID ID = %3 AND GRID ID = %4.

6376.4 *** SYSTEM FATAL MESSAGE 6376, (CIECHT),

THE FINAL TABLES CREATED IN THE %1 ROUTINE IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6376.5 *** SYSTEM FATAL MESSAGE 6376, (CSFFAC),

THE EDGE TABLE CREATED IN THE %1 ROUTINE IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6377.0 *** USER FATAL MESSAGE 6377, (GP0H),

Main Index
 626 MSC Nastran Error Messeges
Errors 6000 - 6999

THE GRID POINTS SPECIFIED ON FEFACE BULK DATA ENTRY ID = %1 DO NOT DEFINE A
VALID THREE OR
FOUR SIDED FACE OF ANY P-ELEMENT.

User action: CHECK FEFACE AND/OR SET ENTRIES.

6379.0 *** USER FATAL MESSAGE 6379,

THE FEEDGE ID = %1 REFERENCED BY %2 IS UNDEFINED.

6379.1 *** USER WARNING MESSAGE 6379, (GP0F),

THE %1 ID=%2 ASSOCIATED WITH GMSURF ID=%3 HAS NO ASSOCIATED FEFACE,
THUS LOAD WILL BE IGNORED.

6379.2 *** USER WARNING MESSAGE 6379, (GP0F),

THE %1 ID=%2 ASSOCIATED WITH GMCURV ID=%3 HAS NO ASSOCIATED FEEDGE,
THUS LOAD WILL BE IGNORED.

6379.3 *** USER WARNING MESSAGE 6379, (CSFFAC),

THE FACE ID =%1 SPECIFIED ON GMBNDS BULK DATA ENTRY ID = %2 DOES NOT
DEFINE A VALID FACE OF ANY
P-ELEMENT.

User action: CHECK FEFACE AND/OR SET ENTRIES.

6379.4 *** USER WARNING MESSAGE 6379, (CSFSRF),

THE SURFACE ID =%1 SPECIFIED ON GMBNDS BULK DATA ENTRY ID =%2 DOES NOT
DEFINE A VALID FACE OF
ANY P-ELEMENT.

6379.5 *** USER WARNING MESSAGE 6379, (CSFGRI),

THE GRID ID =%1 SPECIFIED ON GMBNDS BULK DATA ENTRY ID =%2 DOES NOT
BELONG TO THE P-ELEMENT BOUNDARY.

User action: CHECK GMBNDS AND/OR FEFACE ENTRIES.

User action: CHECK FEFACE AND/OR SET ENTRIES.

Main Index
 MSC Nastran Error Messeges 627
Errors 6000 - 6999

6380.0 *** USER FATAL MESSAGE 6380, (GP0F),

THE FEFACE ID = %1 REFERENCED BY %2 IS UNDEFINED.

6381.0 *** USER FATAL MESSAGE 6381,

THE FEFACE CORRESPONDING TO GMSURF ID = %1 REFERENCED BY %2 IS UNDE-
FINED.

6381.1 *** USER FATAL MESSAGE 6381,

THE FEEDGE CORRESPONDING TO GMCURV ID = %1 REFERENCED BY %2 IS UNDE-
FINED.

6381.2 *** USER FATAL MESSAGE 6381, (GP0F),

INVALID THE GMCURV OR GMSURF ID =%1 REFERENCED BY GMLOAD ID =%2 IS UNDE-
FINED.

6381.4 *** USER FATAL MESSAGE 6381, (GBCSF),

THE GMSURF ID = %1 REFERENCED BY %2 IS UNDEFINED.

6381.6 *** USER FATAL MESSAGE 6381, (GBCCE),

THE GMCURV ID = %1 REFERENCED BY %2 IS UNDEFINED.

6382.0 *** SYSTEM FATAL MESSAGE 6382, (GP0F),

THE FINAL GRIDN TABLE CREATED IN GP0D IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6385.0 *** USER FATAL MESSAGE 6385, (GSPCCE),

THE FEEDGE ID = %1 REFERENCED BY %2 IS UNDEFINED.

6386.0 *** USER FATAL MESSAGE 6386, (GSPCSF),

THE FEFACE ID = %1 REFERENCED BY %2 IS UNDEFINED.

6387.0 *** SYSTEM FATAL MESSAGE 6387, (GSPCSF),

FINAL GRIDN TABLE CREATED IN GP0DA IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 628 MSC Nastran Error Messeges
Errors 6000 - 6999

6388.0 *** USER INFORMATION MESSAGE 6388, (GP0),

ADAPT CASE CONTROL ENTRY EXIST, HOWEVER THERE ARE NO P-ELEMENTS IN THE
DECK.

6388.1 *** USER INFORMATION MESSAGE 6388, (GP0),

ADAPT CASE CONTROL ENTRY EXIST, HOWEVER PVAL AND/OR PSET ENTRY DOES NOT
EXIST

6389.0 *** USER FATAL MESSAGE 6389, (GP0H),

THERE ARE DUPLICATE FACE ENTRIES WITH ID =%1.

6390.0 *** USER FATAL MESSAGE 6390, (GP0I),

ELEMENT ID =%1 TYPE HEXA20 OR PENTA15 AND/OR TETRA10 ARE NOT SUPPORTED IN
P-ELEMENT ANALYSIS.

User action: CHECK ELEMENT CONNECTION ENTRY OR SET ENTRY.

6391.0 *** USER FATAL MESSAGE 6391, (GP0H),

THE GMSURF ID = %1 REFERENCED BY %2 ID =%3 IS UNDEFINED.

6392.0 *** USER FATAL MESSAGE 6392 , (EVLPND),

POINT ID =%1 FOR FEEDGE ID =%2 HAS AN ILLEGAL LOCATION.

6392.1 *** USER FATAL MESSAGE 6392 , (EVLPND),

POINT IDS =%1 FOR FEEDGE ID =%2 HAVE ILLEGAL LOCATIONS.

6394.0 *** USER FATAL MESSAGE 6394, (GP0I),

FEFACE/FEEDGE ID = %1 REFERENCED BY ELEMENT TYPE %2 ID = %3

User information: THIS ELEMENT TYPE CANNOT REFERENCE AN FEEDGE OR FEFACE

ENTRY.

6395.0 *** USER FATAL MESSAGE 6395, (MRGCOR),

THE GRID POINTS SPECIFIED ON FEFACE ENTRY ID =%1 DO NOT DEFINE A VALID
EDGE OF ANY P-ELEMENT.

Main Index
 MSC Nastran Error Messeges 629
Errors 6000 - 6999

6395.1 *** USER FATAL MESSAGE 6395, (GP0I),

THE GRID POINTS SPECIFIED ON FEEDGE BULK DATA ENTRY ID = %1 DO NOT DEFINE
A VALID EDGE OF ANY P-ELEMENT.

User action: CHECK FEEDGE AND/OR SET ENTRIES.

6397.0 *** USER FATAL MESSAGE 6397, (GP0I),

THE GMCURV ID = %1REFERENCED BY FEEDGE ID = %2 IS UNDEFINED.

6398.0 *** SYSTEM FATAL MESSAGE 6398, (MRGCOR),

PRELIMINARY EDGE TABLE CREATED IN GP0B IS INVALID.

User action: CONTACT CLIENT SUPPORT AT HEXAGON AB.

6399.0 *** USER FATAL MESSAGE 6399, (MRGCOR),

FOR EDGE ID%1 CIDS PROVIDED BY FEFACE ID =%2 ARE DIFFERENT.

User action: CHECK FEFACE ENTRIES

6399.1 *** USER FATAL MESSAGE 6399, (MRGCOR),

FOR THE EDGE (G1-G2) =%1-%2 CIDS%3,%4 PROVIDED BY FEFACE ENTRIES ARE DIFFER-
ENT.

User action: FOR SUCH CASE EITHER PROVIDED FEEDGE ENTRY FOR THAT EDGE, OR
CHECK CIDS IN FEFACE ENTRIES.

6399.2 *** USER FATAL MESSAGE 6399, (MRGCOR),

FOR THE EDGE (G1-G2) =%1,%2 THERE ARE TWO INTERSECTING SURFACES.%3,%4

User action: FOR SUCH CASE PROVIDE FEEDGE ENTRY FOR THAT EDGE.

6400.0 *** USER FATAL MESSAGE 6400, (GP0I),

THERE ARE DUPLICATE FEEDGE ENTRIES WITH ID = %1.

6402.0 *** SYSTEM FATAL MESSAGE 6402, (BCEDG),

Main Index
 630 MSC Nastran Error Messeges
Errors 6000 - 6999

THE FINAL EDGE OR FACE TABLE CREATED IN GP0F IS INVALID.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6403.0 *** USER FATAL MESSAGE 6403 (GECINT)

THE GMBNDC BOUNDARY ID = %1 REFERENCED BY %2 ID = %3 IS UNDEFINED.

6403.1 *** USER FATAL MESSAGE 6403 (CIFEDG)

THE BOUNDARY GMBNDC ID = %1 REFERENCED BY GMINTC ID = %2 HAS AN UNDE-
FINED FEEDGE ID = %3.

6403.2 *** USER FATAL MESSAGE 6403 (CIFEDG)

THE GMBNDC BOUNDARY ID = %1 REFERENCED BY GMINTC ELEMENT ID = %2 IS NOT
CONTINUOUS
AT GRID ID = %3.

6403.3 *** USER FATAL MESSAGE 6403, (CIFCRV),

THE GMBNDC ID = %1 REFERENCED BY %2 ID =%3 IS NOT CONTINUOUS AT GRID
ID=%4.

6403.4 *** USER FATAL MESSAGE 6403, (BCEDG),

THE FEEDGE ID = %1 REFERENCED BY %2 ID =%3 IS UNDEFINED.

6403.5 *** USER FATAL MESSAGE 6403, (CSFSRF),

THE GMBNDS ID = %1 REFERENCED BY %2 ID =%3 DOES NOT DEFINE A VALID FACE OF
ANY P-ELEMENT.

User action: CHECK GMBNDS ENTRIES.

6403.6 *** USER FATAL MESSAGE 6403 (GESINT)

THE GMBNDS BOUNDARY ID = %1 REFERENCED BY %2 ID = %3 IS UNDEFINED.

6404.0 *** USER FATAL MESSAGE 6404, (BCFAC),

THE FEFACE ID = %1 REFERENCED BY %2 ID =%3 IS UNDEFINED.

6405.0 *** SYSTEM FATAL MESSAGE 6405, (GP3D),

Main Index
 MSC Nastran Error Messeges 631
Errors 6000 - 6999

THE GEOM3 TABLE CONTAINS AN INVALID TEMPF RECORD SET ID = %1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6406.0 *** SYSTEM FATAL MESSAGE 6406 (GP4)

GRID POINT ID= %1 ON AN SPCP/SPCDP ENTRY HAS COMPONENT= %2 GREATER THAN
MAX. NDOF= %3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK SPCP/SPCDP ENTRIES CREATED IN GP0 MODULE.

6407.0 *** SYSTEM FATAL MESSAGE 6407, (MDGM4F),

ENFORCED DISPLACEMENT VECTOR LENGTH DOES NOT MATCH
WITH THE CALCULATED VALUE FOR THE FEEDGE/FEFACE ID = %1

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: CHECK ENFORCED DISPLACEMENT VECTOR ROUTINE.

6408.0 *** SYSTEM FATAL MESSAGE 6408 (TA1A)

NO ELEMENT HIERARCHICAL DATA FOR THE ELEMENT ID =%1 WAS FOUND.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer action: CHECK EHT TABLE.

6409.0 *** SYSTEM WARNING MESSAGE 6409, (TPUSET)

FOR P-ELEMENT OR LAGRANGE MULTIPLIER USET PRINT, SIL TABLE MUST EXIST AS A
THIRD INPUT TO TABPRT MODULE.

6410.0 *** SYSTEM INFORMATION MESSAGE 6410 (IFP8HP).

BEGIN PROCESSING OF MATHP ENTRY ID =%1

System information: This message is issued when the curve-fitting algorithm is activated to produce the
material constants for hyperelastic materials based on experimental data. An image of the produced
MATHP Bulk Data entry is printed after this message.

Main Index
 632 MSC Nastran Error Messeges
Errors 6000 - 6999

6410.1 *** SYSTEM INFORMATION MESSAGE 6410 (IFP8HE).

BEGIN PROCESSING OF %1 ENTRY ID = %2

System information: This message is issued when the curve-fitting algorithm is activated to produce the
material constants for hyperelastic materials based on experimental data. An image of the produced Bulk-
Data entry is printed after this message.

6411.0 *** SYSTEM FATAL MESSAGE 6411 (LSQRS).

SINGULAR VALUE DECOMPOSITION DID NOT CONVERGE.

System information:
This message is issued by the Singular Value Decomposition (SVD) method which is used by the curve-fit-
ting algorithm for the hyperelastic material constants. The message occurs when the SVD fails to converge,
which may be caused by an error in the experimental data. Check the input in the TABLES1 Bulk Data
entries for errors.

6411.1 *** SYSTEM FATAL MESSAGE 6411 (LNNHERR)

INTERNAL FAILURE IN THE LANCZOS PROCEDURE:
SVD QL PROCEDURE FAILED TO CONVERGE.

User action: CONTACT MSC CLIENT SUPPORT.

6412.0 *** SYSTEM INFORMATION MESSAGE 6412

RANK DEFICIENCY HAS BEEN DETECTED IN DATA BLOCK %1

6412.1 *** SYSTEM INFORMATION MESSAGE 6412

RANK DEFICIENCY HAS BEEN DETECTED IN DATA BLOCK P
THAT IS THE PRODUCT OF THE MATRIX %1 BY %2

6412.6 *** SYSTEM WARNING MESSAGE 6412

Main Index
 MSC Nastran Error Messeges 633
Errors 6000 - 6999

RANK DEFICIENCY HAS BEEN DETECTED. RANK =%1. FULL RANK =%2

User information:
This message is issued by the Singular Value Decomposition (SVD) method which is used by the curve-fit-
ting algorithm for the hyperelastic material constants. The message occurs when the least squares problem
for estimation of the material parameters is rank deficient, i.e., the rank is less than the number of material
parameters (full rank). This message may be issued for either distortional (Aij) or volumetric (Di) parameter
fitting. The program will proceed to find a non-unique solution. However, it is best to try to avoid rank
deficiency by providing more experimental data for curve fitting or lowering the order of the strain energy
polynomial, NA or ND in the MATHP Bulk Data entry.

6413.0 *** USER WARNING/FATAL MESSAGE 6413

INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE MEMORY BY AN ESTIMATED %1 WORDS.

THE EXACT MEMORY REQUIREMENT FOR THE SYMBOLIC PHASE
MAY BE OBTAINED BY INCREASING MEMORY BY AT LEAST %2 WORDS.

6413.1 *** USER WARNING/FATAL MESSAGE 6413

INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE MEMORY BY AN ESTIMATED %1 WORDS.

6413.2 *** USER WARNING/FATAL MESSAGE 6413 (DFMSYN)

INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION
(BEND).

User action: INCREASE MEMORY BY AN ESTIMATED %1 WORDS.

6413.3 *** USER WARNING/FATAL MESSAGE 6413 (DFMSYN)

INSUFFICIENT MEMORY FOR THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION
(METIS).

User action: INCREASE MEMORY BY AN ESTIMATED %1 WORDS.

6414.0 *** SYSTEM FATAL MESSAGE 6414

Main Index
 634 MSC Nastran Error Messeges
Errors 6000 - 6999

THE FACTOR MATRIX (FIST=%1) CANNOT BE USED WITH THE SPARSE METHOD.

User information: THE FACTOR MATRIX WAS PROBABLY OBTAINED VIA THE RESTART OR
DBLOCATE FMS STATEMENT
OF A DATABASE CREATED IN A PRIOR VERSION OF THE PROGRAM.

User action: RECOMPUTE THE FACTOR MATRIX IN THIS VERSION OF THE PROGRAM.

6415.0 *** SYSTEM INFORMATION MESSAGE 6415 (DFNSB)

MORE EFFICIENT PROCESSING IN FBS MAY BE POSSIBLE BY SETTING SYSTEM(146) TO 2,
3 OR 4
WHICH WILL RESPECTIVELY MULTIPLY THE FBS MEMORY ALLOCATION FOR THE FAC-
TOR BY 2, 3 OR 4

6417.0 *** USER WARNING MESSAGE 6417 (SQD41D)

THE (%1) OPTION FOR STRESSES IS NOT AVAILABLE FOR NONLINEAR MATERIAL OR
COMPOSITE ELEMENTS.

User information: STRESS (CENTER) WILL BE APPLIED TO THOSE ELEMENTS.

User information:
CUBIC refers to corner output for element STRESS, STRAIN, and FORCE.
Corner output is not available for nonlinear analysis, so only center
stresses are computed for nonlinear CQUAD4 elements.

6418.0 *** USER WARNING MESSAGE 6418 (SDR2A)

Main Index
 MSC Nastran Error Messeges 635
Errors 6000 - 6999

THE %1 OPTION FOR STRAINS OVERRIDES ALL OTHER OPTIONS IN THE FORCE COM-
MANDS.

User information:
CUBIC refers to corner output for element STRESS, STRAIN, and FORCE.
When corner output is selected for CQUAD4 elements, only one output
type--CORNER or CENTER-- is available in the entire run, regardless
of output request (STRESS, STRAIN, and FORCE) and subcase. The
hierarchy is as follows:
1. STRESS in the first subcase determines the request type (CENTER
or CORNER).
2. STRESS above the subcase level determines the type.
3. STRAIN in the first subcase determines the type.
4. STRAIN above the subcase level determines the type.
5. FORCE in the first subcase determines the type.
6. FORCE above the subcase level determines the type.
The second (and successive) subcases are not used to determined
output type (CENTER or CORNER).

6418.1 *** USER WARNING MESSAGE 6418 (SDR2A)

Main Index
 636 MSC Nastran Error Messeges
Errors 6000 - 6999

THE %1 OPTION FOR STRESSES OVERRIDES ALL OTHER OPTIONS IN STRAIN AND
FORCE COMMANDS.

User information:
CUBIC refers to corner output for element STRESS, STRAIN, and FORCE.
When corner output is selected for CQUAD4 elements, only one output
type--CORNER or CENTER-- is available in the entire run, regardless
of output request (STRESS, STRAIN, and FORCE) and subcase. The
hierarchy is as follows:
1. STRESS in the first subcase determines the request type (CENTER
or CORNER).
2. STRESS above the subcase level determines the type.
3. STRAIN in the first subcase determines the type.
4. STRAIN above the subcase level determines the type.
5. FORCE in the first subcase determines the type.
6. FORCE above the subcase level determines the type.
The second (and successive) subcases are not used to determined
output type (CENTER or CORNER).

6418.2 *** USER WARNING MESSAGE 6418 (SDR2A)

THE DEFAULT OPTION (CENTER FOR QUAD4, CORNER FOR QUADR/TRIAR) FOR
STRAINS OVERRIDES ALL OTHER OPTIONS
IN THE FORCE COMMANDS.

6418.3 *** USER WARNING MESSAGE 6418 (SDR2A)

THE DEFAULT OPTION (CENTER FOR QUAD4, CORNER FOR QUADR/TRIAR) FOR
STRESSES OVERRIDES ALL OTHER OPTIONS
IN STRAIN AND FORCE COMMANDS.

6419.0 *** USER FATAL MESSAGE 6419

THE NUMBER OF GAUSS POINTS IN %1 DIRECTION IS GREATER THAN THE MAXIMUM
ALLOWED (%2).

User action: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %3.

6419.2 *** USER FATAL MESSAGE 6419 (TBEMPD)

Main Index
 MSC Nastran Error Messeges 637
Errors 6000 - 6999

THE NUMBER OF GAUSS POINTS %1 GREATER THAN THE MAXIMUM ALLOWED (%2).

User action: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %3.

6419.3 *** USER FATAL MESSAGE 6419 (PGAUSS)

THE NUMBER OF GAUSS POINTS IN %1-DIRECTION = %2 IS GREATER THAN THE MAXI-
MUM ALLOWED (%3).

User action: CHECK THE "IN" FIELD OF THE %4 ENTRY FOR ELEMENT ID = %5.

6419.4 *** USER FATAL MESSAGE 6419

THE NUMBER OF GAUSS POINTS IN %1 DIRECTION IS GREATER THAN THE MAXIMUM
ALLOWED (%2).

User action: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %3.

6419.5 *** USER FATAL MESSAGE 6419

THE NUMBER OF GAUSS POINTS IN %1-DIRECTION = %2 IS GREATER THAN THE MAXI-
MUM ALLOWED (%3).

User action: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %4.

6419.6 *** USER FATAL MESSAGE 6419 (EBEMPD)

THE NUMBER OF GAUSS POINTS %1 GREATER THAN THE MAXIMUM ALLOWED (%2).

User action: CHECK THE "IN" FIELD OF THE PSOLID ENTRY FOR ELEMENT ID = %3.

6419.7 *** USER WARNING MESSAGE 6419 (TA1)

IN=2 OPTION ON TETRAS WITH MID-SIDE NODES IS NOT ALLOWED. IN=3 WILL BE
USED
INSTEAD.

6420.0 *** USER FATAL MESSAGE 6420 (GONCED)

ELEMENT ID = %1 REFERENCES A MATERIAL ID = %2 WHICH DOES NOT IDENTIFY A
MAT1 OR MAT9 ENTRY.

Main Index
 638 MSC Nastran Error Messeges
Errors 6000 - 6999

6422.0 *** USER WARNING MESSAGE 6422 (FA2)

THE EIGENVECTOR CORRESPONDING TO THE EIGENVALUE %1,%2 IS NOT AVAILABLE.

User action: REQUEST ADDITIONAL ROOTS ON THE NDJ FIELD OF THE EIGC BULK DATA
ENTRY.

6423.0 *** USER FATAL MESSAGE 6423 (DIAGON)

THE "WHOLE" OPTION OF THE DIAGONAL MODULE CANNOT BE PERFORMED ON A
SPARSE FACTOR MATRIX

6424.0 *** SYSTEM FATAL MESSAGE 6424 (UFBSS)

THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE INCOM-
PATIBLE
LOAD VECTOR ROWS = %1
FACTOR MATRIX ROWS = %2

6425.0 *** SYSTEM FATAL MESSAGE 6425 (EMA).

THE KDICTP TABLE AND KDICTP TRAILER ARE INCONSISTENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT

6425.1 *** SYSTEM FATAL MESSAGE 6425 (MIRROD).

THE KDICTP AND SILS TABLES ARE INCONSISTENT.

User action: CONTACT HEXAGON AB CLIENT SUPPORT

6426.0 *** USER FATAL MESSAGE 6426 (RMG2)

THE CAVITY ID=%1 REFERENCES UNDEFINED RADIATION MATRIX.

User information: THE RADIATION MATRIX MUST BE DEFINED ON EITHER RADCAV OR

RADLST/RADMTX BULK DATA ENTRIES.

6427.0 *** USER WARNING MESSAGE 6427 (VIEW)

Main Index
 MSC Nastran Error Messeges 639
Errors 6000 - 6999

VIEW FACTORS WILL NOT BE COMPUTED FOR RADIATION CAVITY ID=%1 BECAUSE A
RADIATION MATRIX IS ALREADY DEFINED.

User information: THE RADIATION MATRIX IS DEFINED ON RADLST OR RADMTX BULK

DATA ENTRIES.

6428.0 *** SYSTEM WARNING MESSAGE 6428 (ZREAD)

LOGIC ERROR -- CALLING SUBROUTINE SPECIFIED NEGATIVE ARRAY LENGTH.
PROGRAMMER ACTION : CHECK OPEN CORE METHOD.

6430.0 *** USER WARNING MESSAGE 6430 (ZREAD)

MULTIPLE READ PROBLEM IN DATA BLOCK=%1, RECORD=%2 : ARRAY OR UNDEF ITEM
IS MORE THAN 100 WORDS.

User action: SPLIT ARRAY OR UNDEF INTO GROUPS SMALLER THAN 100 WORDS.

6431.0 *** USER WARNING MESSAGE 6431 (ZREAD)

A COUNT ITEM AT OFFSET=%1,IN DATA BLOCK=%2, RECORD=%3, WITH AN NDDL
NAME=%4,CONFLICTS WITH THE ACTUAL NAME=%5.

User information: PROBABLE CAUSE IS TOO LITTLE/MUCH DATA ON RECORD=%6.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6432.0 *** SYSTEM WARNING MESSAGE 6432 (ZREAD)

THE ITEM NAMES WITH (C) OPTION OF DATA BLOCK=%1, RECORD=%2,HAVE
EXCEEDED THE MAXIMUM NUMBER OF %3

Programmer information: PROBABLE CAUSE IS MISMATCH OF NDDL AND ZREAD LIMIT.

Programmer action: INTRODUCE A BLOCK DATA FOR BOTH ROUTINES.

6433.0 *** SYSTEM WARNING MESSAGE 6433 (ZREAD)

Main Index
 640 MSC Nastran Error Messeges
Errors 6000 - 6999

THE DECODED C-ITEM "TCODE" OF DATA BLOCK=%1, RECORD=%2,

EXCEEDS NORMAL LIMITS "J"=%3 "I"=%4.

Programmer information: PROBABLE CAUSE IS WRONG POSITION OF TABLE CODE, OR

EARLIER RESET OF (C) ITEMS.

6434.0 *** USER WARNING MESSAGE 6434 (ZREAD)

THE LENGTH OF THE DATA IN DATA BLOCK=%1, RECORD=%2,
IS LONGER THAN DESCRIBED IN THE NDDL.

User information: IF YOU USED INPUT2, CHECK FOR A NAME MISMATCH.

IF YOU MODIFIED THE NDDL CHECK YOUR MODIFICATIONS.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6435.0 *** SYSTEM WARNING MESSAGE 6435 (ZREAD)

DURING A SECOND READ OF DATA BLOCK=%1, RECORD=%2, AN ERROR OCCURRED.

Programmer information: PROBABLE CAUSE IS "EMARK" VARIABLE OVERWRITTEN, OR

A REQUEST TO READ THE 3 WORD HEADER OF IFP BLOCK OCCURRED.

6437.0 *** USER FATAL MESSAGE 6437, (MAT)

MATHP ENTRY ID = %1 IS SPECIFIED FOR ELEMENT ID = %2, WHICH IS NOT A FINITE
DEFORMATION ELEMENT.

User information:
This message is issued when a hyperelastic material (MATHP) is referenced
by an element which is not a finite deformation element. Finite deformation
elements must have a PLSOLID or PLPLANE property entry reference or have
SOL 400 advanced nonlinear property extensions such as PSLDN1, PSHLN1, etc.
Please refer to QRG for the detailed description of MATHP.

6437.1 *** USER FATAL MESSAGE 6437, (MAT)

Main Index
 MSC Nastran Error Messeges 641
Errors 6000 - 6999

MATHP ENTRY ID = %1 IS SPECIFIED FOR PROPERTY ID = %2, WHICH IS NOT A FINITE

DEFORMATION PROPERTY.

User information:
This message is issued when a hyperelastic material (MATHP) is referenced by an element which is not a
finite deformation element. Finite deformation elements must have a PLSOLID or PLPLANE property
entry reference or have SOL 400 advanced nonlinear property extensions such as PSLDN1, PSHLN1, etc.
Please refer to QRG for the detailed description of MATHP.

6438.0 *** USER FATAL MESSAGE 6438, (MAT)

MATHP ENTRY ID = %1 CAN NOT BE FOUND FOR FINITE DEFORMATION (HYPERELAS-
TIC) ELEMENT ID = %2.

User action: SPECIFY MATHP ENTRY WITH ID = %3.

User information:
This message is issued if a PLSOLID or PLPLANE property entry, for a hyperelastic element, does not ref-
erence a MATHP entry.

6438.1 *** USER FATAL MESSAGE 6438, (MAT)

MATHP ENTRY ID = %1 CAN NOT BE FOUND FOR FINITE DEFORMATION (HYPERELAS-
TIC) PROPERTY ID = %2.

User action: SPECIFY MATHP ENTRY WITH ID = %3.

User information:
This message is issued if a PLSOLID or PLPLANE property entry, for a hyperelastic element, does not ref-
erence a MATHP entry.

6439.0 *** USER INFORMATION MESSAGE 6439 (UDSFA) ---

ACTUAL MEMORY AND DISK SPACE REQUIREMENTS FOR SPARSE UNSYM. DECOMPOSI-
TION

User information:
This message is issued in the .F04 file after decomposition. It tells how much memory and disk space were
actually required.

Main Index
 642 MSC Nastran Error Messeges
Errors 6000 - 6999

6439.2 *** USER INFORMATION MESSAGE 6439 (DFMSA) ---

ACTUAL MEMORY AND DISK SPACE REQUIREMENTS FOR SPARSE SYM.
DECOMPOSITION

User information:
This message is issued in the .F04 file after decomposition. It tells how much memory and disk space were
actually required.

6439.3 *** USER INFORMATION MESSAGE 6439 (DISDCM1)

ACTUAL MEMORY AND DISK SPACE REQUIREMENTS FOR DISTRIBUTED SPARSE SYM.
DECOMPOSITION

6440.0 *** USER FATAL MESSAGE 6440

ELEMENT %1 REFERS TO AN INVALID PROPERTY ENTRY.

User action: SPECIFY APPROPRIATE PROPERTY ENTRY.

6441.0 *** USER FATAL MESSAGE 6441 (DOPR1Z)

DEQATN ENTRY ID = %1, HAS TOO MANY OR TOO FEW ARGUMENTS.

User information: THE DEQATN ENTRY HAS %2 ARGUMENTS BUT THE

REFERENCING DVPREL2 ENTRY ID = %3 SPECIFIES %4 DESIGN VARIABLES AND %5 DTA-
BLE CONSTANTS.

User action: MODIFY THE INPUT SO THAT THE NUMBER OF DESIGN VARIABLES PLUS
THE
NUMBER OF DTABLE CONSTANTS IS EQUAL TO THE NUMBER OF DEQATN ARGU-
MENTS.

6442.0 *** USER FATAL MESSAGE 6442 (DOPR3J)

Main Index
 MSC Nastran Error Messeges 643
Errors 6000 - 6999

DEQATN %1, WHICH HAS %2 ARGUMENTS, IS REFERENCED BY A DRESP2 ENTRY %3

WHICH HAS %4 ARGUMENTS.

User action: MODIFY THE INPUT SO THAT THE NUMBER OF ARGUMENTS ON THE
DEQATN BULK DATA ENTRY
EQUALS THE SUM OF THE NUMBER OF DESIGN VARIABLES, DTABLE CONSTANTS,
RESPONSES AND NODES ON THE
CORRESPONDING DRESP2 BULK DATA ENTRY.

6443.0 *** USER WARNING MESSAGE 6443 (SQD41D)

NO CORNER STRESSES, FORCES, OR STRAINS WILL BE COMPUTED FOR QUAD4 ELE-
MENT ID = %1 BECAUSE ONE OR MORE
OF ITS CORNER THICKNESSES IS ZERO.

User information: ALSO, GRID POINT STRESSES WILL BE INCORRECT AT THOSE CORNERS.

User information:
When requesting corner output for CQUAD4 elements, all membrane
thicknesses at the four grid points must be greater than zero.
If any thickness is zero, then stresses, forces, and strains are not computed for that element. Subsequent ele-
ment computations--
such as gridpoint stresses and stress discontinuities-- will not
have results from the offending elements.

6444.0 *** USER WARNING MESSAGE 6444 (INPTYP)

THE FILE ASSIGNED TO UNIT =%1 CONTAINS DATA THAT IS INCONSISTENT WITH
FORM = %2

User information:
1. THIS MAY BE CAUSED BY:
A. THE FILE IS ACTUALLY A FORTRAN %3 FILE.
B. THE FILE MAY NOT BE A VALID %4 FILE
C. THE FILE HAS BEEN MISPOSITIONED BY A PREVIOUS FORTRAN I/O STATEMENT
2. AN ASSIGN FILE MANAGEMENT STATEMENT WAS %5 TO ASSIGN THE FILE

Programmer information:
THE FILE DOES NOT CONTAIN A %6

Main Index
 644 MSC Nastran Error Messeges
Errors 6000 - 6999

6445.0 *** USER WARNING MESSAGE 6445 (INPTYP)

A FORTRAN %1 READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = %2

User information: THE FILE %3 SPECIFIED IN AN ASSIGN FILE MANAGEMENT STATEMENT

User action: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT HEXAGON AB
CLIENT SUPPORT.

Programmer information: FORTRAN IOSTAT CODE = %4

6445.1 *** USER WARNING MESSAGE 6445 (INPTT4)

A FORTRAN %1 READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = %2

User information: THE FILE WAS SPECIFIED IN AN ASSIGN FILE MANAGEMENT STATE-
MENT

User action: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT HEXAGON AB
CLIENT SUPPORT.
VERIFY DATA AND FORTRAN FORMAT SPECIFICATION.

Programmer information: FORTRAN IOSTAT CODE = %3

6445.2 *** USER WARNING MESSAGE 6445 (INPUT2/4)

READ ERROR HAS OCCURRED WHILE PROCESSING UNIT = %1, LOGICAL NAME = %2
IOSTAT CODE = %3, ERROR MESSAGE IS --
%4

User information: FILE WAS SPECIFIED IN AN ASSIGN FILE MANAGEMENT STATEMENT

User action: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT HEXAGON AB
CLIENT SUPPORT.

6445.3 *** USER WARNING MESSAGE 6445 (INPUT2/4)

Main Index
 MSC Nastran Error Messeges 645
Errors 6000 - 6999

READ REQUESTED RETURNED INCORECT DATA LENGTH WHILE PROCESSING UNIT =

%1 FOR LOGICAL NAME %2
EXPECTED %3 WORDS, ACTUALLY READ %4 WORDS

User action: VERIFY THE FILE ASSIGNMENT AND CONTENTS OR CONTACT HEXAGON AB
CLIENT SUPPORT.

6445.4 *** USER WARNING MESSAGE 6445 (OUTPT2/4)

WRITE ERROR HAS OCCURRED WHILE PROCESSING UNIT = %1, LOGICAL NAME = %2
IOSTAT CODE = %3, ERROR MESSAGE IS --
%4

6445.5 *** USER WARNING MESSAGE 6445 (OUTPT2/4)

UNEXPECTED END-OF-FILE ENCOUNTERED WHILE READING UNIT %1, LOGICAL NAME
= %2

6445.6 *** USER WARNING MESSAGE 6445 (INPUT4)

READ REQUEST RETURNED EXCESS DATA WHILE PROCESSING UNIT = %1 FOR LOGICAL
NAME %2
EXPECTED %3 WORDS, ACTUALLY READ %4 WORDS. EXCESS DATA HAS BEEN
IGNORED.

6446.0 *** SYSTEM WARNING MESSAGE 6446 (INPTYP)

A FORTRAN %1 READ ERROR HAS OCCURRED PROCESSING STRING VARIABLE %2

User information: FORTRAN IOSTAT CODE = %3

STRING IS = %4

6447.0 *** USER INFORMATION MESSAGE 6447 (SITDRV)

ITERATIVE SOLVER DIAGNOSTIC OUTPUT

6447.2 *** USER INFORMATION MESSAGE 6447 (SITDR3)

ITERATIVE SOLVER DIAGNOSTIC OUTPUT

6447.4 *** SYSTEM INFORMATION MESSAGE 6447 (SDRVP)

DISTRIBUTED PARALLEL ITERATIVE SOLVER DIAGNOSTIC OUTPUT

Main Index
 646 MSC Nastran Error Messeges
Errors 6000 - 6999

6448.0 *** USER INFORMATION MESSAGE 6448

SOLUTION CONVERGED WITH ITERATIVE METHOD.

6448.4 *** SYSTEM INFORMATION MESSAGE 6448 (SDRVP)

SOLUTION CONVERGED WITH ITERATIVE METHOD.

6449.0 *** USER INFORMATION MESSAGE 6449:

INTERNAL CONVERGENCE CRITERION WAS NOT PASSED FOR LOAD NUMBER %1

6449.2 *** SYSTEM INFORMATION MESSAGE 6449

INTERNAL CONVERGENCE CRITERION WAS NOT PASSED FOR %1 RHS(S) OUT OF %2.
(PLEASE SEE FIRST %3 LOAD(S) FOLLOWING USER INFORMATION MESSAGE 5293
BELOW)

6449.7 *** SYSTEM INFORMATION MESSAGE 6449 (SDRVP)

PROBLEM TOO SMALL FOR COMPUTING OPTIMAL COMMUNICATION PATTERN.
SWITCHED TO REGULAR PATTERN.

6449.8 *** USER INFORMATION MESSAGE 6449 (SUCGRD):

INTERNAL CONVERGENCE CRITERION WAS NOT PASSED FOR %1 RHS(S) OUT OF %2.
(PLEASE SEE FIRST %3 LOAD(S) FOLLOWING USER INFORMATION MESSAGE 5293 BELOW

6450.0 *** USER WARNING MESSAGE 6450 (OUTPT4)

Main Index
 MSC Nastran Error Messeges 647
Errors 6000 - 6999

THE SELECTION OF THE ASCII FORMAT OPTION IN THE OUTPUT4 MODULE FOR DAT-
ABLOCK %1 MAY RESULT IN NUMERIC TRUNCATION.

User information:
1. THE FORTRAN FORMAT BEING USED IS %2
2. THE DEFAULT FORTRAN FORMAT IS (1P,5E16.9)
3. THE FIFTH PARAMETER OF THE OUTPUT4 MODULE CAN BE USED TO INCREASE THE
NUMBER OF SIGNIFICANT DIGITS.

User action:
1. IF THE NUMBER OF SIGNIFICANT DIGITS IS ACCEPTABLE, THEN NO ACTION IS
REQUIRED.
2. IF ADDITIONAL SIGNIFICANT DIGITS ARE REQUIRED, THEN INCREASE THE VALUE
OF THE FIFTH PARAMETER, AND
RERUN THE JOB.

User information:
This message is issued if the internal precision is greater than
the requested output precision for OUTPUT4. If you want more
precision, increase the value of the fifth parameter in the
OUTPUT4 module and rerun the job.

6451.0 *** SYSTEM FATAL MESSAGE 6451 (SITDRV)

ITERATIVE SOLVER HAS BEEN REQUESTED TO SOLVE A SYSTEM WITH PURGED
MATRIX.

6452.0 *** SYSTEM FATAL MESSAGE 6452 (SITDRV)

THE INPUT MATRICES TO THE ITERATIVE SOLVER ARE INCOMPATIBLE IN THE NUM-
BER OF ROWS.

6453.0 *** SYSTEM FATAL MESSAGE 6453 (SITDRV)

THE INPUT MATRICES TO THE ITERATIVE SOLVER ARE DIFFERENT TYPES.

User action: USE DIRECT SOLUTION METHOD AS IN SOLVE, SSG3 OR FBS MODULES.

6454.0 *** USER FATAL MESSAGE 6454 (IFP8).

Main Index
 648 MSC Nastran Error Messeges
Errors 6000 - 6999

NEGATIVE GROUND SHEAR MODULUS HAS BEEN OBTAINED.

User action: REVISE EXPERIMENTAL DATA AND/OR ORDER OF POLYNOMIAL.

User information:
This message is issued if A10+A01 obtained from the curve-fitting the strain energy polynomial should be
modified.

6455.0 *** USER FATAL MESSAGE 6455 (BGCAU2)

CONTACT REGION ID = %1 SELECTED BY THE BOUTPUT CASE CONTROL COMMAND
IN SUBCASE NUMBER %2
OR THE BOUTPUT BULK DATA ENTRY IS UNDEFINED.

6456.0 *** USER FATAL MESSAGE 6456 (BGCOCL)

SAME ID IS SPECIFIED FOR SECONDARY = %1 AND PRIMARY = %2 REGIONS IN BCONP
ENTRY ID = %3.

6457.0 *** USER WARNING MESSAGE 6457

NO BOUTPUT CASE CONTROL REQUESTS WERE FOUND AND THEREFORE ANY X-Y
PLOT REQUESTS FOR BOUT CANNOT BE PROCESSED.

User action: SPECIFY THE BOUTPUT CASE CONTROL FOR THE DESIRED SECONDARY
NODES.

6458.0 *** USER FATAL MESSAGE 6458 (DSAD11)

THE REQUESTED EIGENVALUE OR BUCKLING LOAD FACTOR ID %1 IS GREATER THAN
THE NUMBER OF MODES
THAT WERE COMPUTED

User action: CHECK THE MODE ID SPECIFIED ON THE DRESP1 ENTRY AND THE FRE-
QUENCY RANGE AND/OR NUMBER OF
DESIRED EIGENVECTORS SPECIFIED ON THE EIGR/EIGB/EIGRL ENTRY

6459.0 *** USER FATAL MESSAGE 6459 (TA1BSH)

Main Index
 MSC Nastran Error Messeges 649
Errors 6000 - 6999

BUSH ELEMENT ID = %1 WITH NONCOINCIDENT CONNECTING NODES REQUIRES THE

SPECIFICATION OF ORIENTATION VECTOR OR CID FIELDS
ON THE CBUSH ENTRY, UNLESS ONLY AXIAL PROPERTIES ARE SPECIFICED IN PBUSH
ENTRY.

6459.1 *** USER FATAL MESSAGE 6459, (EGAPD)

GAP ELEMENT ID = %1 WITH COINCIDENT CONNECTING NODES REQUIRES THE SPEC-
IFICATION OF CID FIELD ON
THE CGAP ENTRY.

6459.2 *** USER FATAL MESSAGE 6459 (IFS1P)

BUSH ELEMENT ID = %1 WITH COINCIDENT CONNECTING NODES REQUIRES THE
SPECIFICATION OF CID FIELD ON THE CBUSH ENTRY.

6459.3 *** USER FATAL MESSAGE 6459 (EBS1D)

BUSH1D ELEMENT ID = %1 WITH COINCIDENT CONNECTING GRIDS REQUIRES THE
SPECIFICATION OF CID FIELD ON THE CBUSH1D ENTRY.
EITHER NO COORDINATE SYSTEM IS SPECIFIED ON THE CBUSH1D ENTRY, OR THE
COORDINATE SYSTEM SPECIFIED DOES NOT EXIST.

6459.4 *** USER FATAL MESSAGE 6459 (SBS11D)

FORCE CALCULATION ON BUSH1D ELEMENT ID = %1 WAS NOT PERFORMED. USE
STRESS OPTION INSTEAD.

6459.5 *** USER FATAL MESSAGE 6459 (SBS21D)

FORCE/STRESS REQUEST ON BUSH2D ELEMENT ID = %1 IS IS NOT CURRENTLY SUP-
PORTED AND WILL BE IGNORED.

6460.0 *** SYSTEM FATAL MESSAGE 6460 (UDSFRD)

ERROR IN OUT OF FRONT PIVOT LOGIC

User action: PLEASE SEND THIS RUN TO HEXAGON AB.

6461.0 *** USER WARNING MESSAGE 6461 (NLINIT)

Main Index
 650 MSC Nastran Error Messeges
Errors 6000 - 6999

NLPARM SET%1 LOAD(P) CONVERGENCE OPTION IS REMOVED WHEN NO LOAD

INCREMENT EXISTS.
THE WORK(W) CONVERGENCE OPTION HAS BEEN SUBSTITUTED IF NONE SUPPLIED.

6462.0 *** USER WARNING MESSAGE 6462 (RMG2)

STEFAN-BOLTZMANN CONSTANT IS ZERO --- RADIATIVE COUPLINGS NULLIFIED.

6463.0 *** USER WARNING MESSAGE 6463 (RMG2)

%1SYMMETRIC SCRIPT-AF MATRIX (HREE) ASSUMED IN RADMTX.

6464.0 *** USER INFORMATION MESSAGE 6464 (DOM12E)

RUN TERMINATED DUE TO MAXIMUM NUMBER OF DESIGN CYCLES = %1.

6464.1 *** USER INFORMATION MESSAGE 6464 (DOM12E)

RUN TERMINATED DUE TO PARAMETER OPTEXIT = %1.

6464.2 *** USER INFORMATION MESSAGE 6464 (DOM12E)

RUN TERMINATED DUE TO SOFT CONVERGENCE AT CYCLE NUMBER = %1.

6464.3 *** USER INFORMATION MESSAGE 6464 (DOM12E)

RUN TERMINATED DUE TO HARD CONVERGENCE TO AN OPTIMUM AT CYCLE NUM-
BER = %1.

6464.4 *** USER INFORMATION MESSAGE 6464 (DOM12E)

RUN TERMINATED DUE TO HARD CONVERGENCE TO A BEST COMPROMISE INFEASI-
BLE DESIGN AT CYCLE NUMBER = %1.

6464.5 *** USER INFORMATION MESSAGE 6464 (DOM12E)

RUN TERMINATED DUE TO CASE CONTROL COMMAND DSAPRT(END=SENSITIVITY).

6464.6 *** USER INFORMATION MESSAGE 6464 (DOM12E)

RUN TERMINATED DUE TO POOR GEOMETRY OR POOR PROPERTIES. SEE FATAL MES-
SAGES PRINTED ABOVE FOR INFORMATION.

6464.7 *** USER INFORMATION MESSAGE 6464 (DELSOPT)

RUN TERMINATED DUE TO NONLINEAR ANALYSIS JOB UNEXPECTED FAILURE AT
DESIGN CYCLE = %1.

Main Index
 MSC Nastran Error Messeges 651
Errors 6000 - 6999

6464.8 *** USER INFORMATION MESSAGE 6464 (DELSOPT)

RUN TERMINATED DUE TO NONLINEAR ANALYSIS JOB UNABLE TO CONVERGE AT
DESIGN CYCLE = %1.

6464.9 *** USER INFORMATION MESSAGE 6464 (DELSOPT)

RUN TERMINATED DUE TO LINEAR OPTIMIZATION JOB UNEXPECTED FAILURE AT
DESIGN CYCLE = %1.

6464.10 *** USER INFORMATION MESSAGE 6464 (DELSOPT)

RUN TERMINATED AFTER %1 CONSECUTIVE NONLINEAR ANALYSIS JOBS ARE UNABLE
TO CONVERGE AT
DESIGN CYCLE = %2.

6464.11 *** USER INFORMATION MESSAGE 6464 (DELSOPT)

RUN TERMINATED DUE TO PARAMETER ESLOPTEX = %1.

6464.12 *** USER INFORMATION MESSAGE 6464 (DOM12J)

PENALTY FACTOR WILL AUTOMATICALLY BE INCREASED BY 1.0 FOR TOPVAR %1.

6464.13 *** USER INFORMATION MESSAGE 6464 (DMKESL)

THE ESLNRO DESIGN TASK HAS A RESPONSE TYPE OTHER THAN SUPPORTED TYPES
WEIGHT,
VOLUME, DISP, STRESS, SPCFORCE, FRMASS AND COMP. UNSUPPORTED RESPONSE
TYPES ARE
IGNORED.

6464.14 *** USER FATAL MESSAGE 6464 (DMKESL)

THE ESLNRO DESIGN TASK DOES NOT CONTAIN ANY SUPPORTED GRID OR ELEMENT
DESIGN RESPONSES.
THE DESIGN TASK IS ABANDONED.

6465.0 *** SYSTEM FATAL MESSAGE 6465

DIVISION BY ZERO WAS ENCOUNTERED BY THE ITERATIVE SOLVER.

6466.0 *** SYSTEM FATAL MESSAGE 6466 (SBUT5)

Main Index
 652 MSC Nastran Error Messeges
Errors 6000 - 6999

FOR THE %1 INPUT ALL TERMS IN COLUMN NUMBER = %2 ARE NULL.

6466.1 *** SYSTEM FATAL MESSAGE 6466 (SBUT2)

FOR THE %1 INPUT ALL TERMS IN COLUMN NUMBER = %2 ARE NULL.

6466.3 *** SYSTEM FATAL MESSAGE 6466 (SBDCD)

ALL TERMS IN ROW NUMBER = %1 ARE NULL.

6467.0 *** SYSTEM FATAL MESSAGE 6467:

A NULL COLUMN WAS ENCOUNTERED AT COLUMN NUMBER = %1 IN THE PRECONDI-
TIONER MATRIX.

6467.4 *** SYSTEM WARNING MESSAGE 6467

A NULL COLUMN WAS ENCOUNTERED AT COLUMN NUMBER = %1 DURING ORTHOG-
ONALIZATION

6468.0 *** USER FATAL MESSAGE 6468 (GETCOL)

CASE CONTROL SPECIFIED A STATSUB ENTRY ID= %1. NO SUBCASE ENTRIES WITH
THAT ID WERE FOUND

User information: PROBABLE CAUSE IS MISMATCH IN CASE CONTROL.

User action: SPECIFY A MATCHING SUBCASE/STATSUB

6469.0 *** USER WARNING MESSAGE 6469 (GP4)

CASE CONTROL COMMAND SUPORT1 ID= %1 REFERENCES UNDEFINED SUPORT1
ENTRIES.

User information: PROBABLE CAUSE IS SUPERELEMENT OR MODULE SUBCASES CONTAIN-

ING THE SUPORT1 COMMAND.
ONLY THE RESIDUAL STRUCTURE SUBCASES SHOULD CONTAIN THE SUPORT1 COM-
MAND.
ANOTHER CAUSE MAY BE NO VALID SUPORT1 ENTRIES IN THE BULK DATA.

6469.1 *** USER FATAL MESSAGE 6469 (GP4)

Main Index
 MSC Nastran Error Messeges 653
Errors 6000 - 6999

CASE CONTROL COMMAND MPC ID= %1 SELECTED SET3 WITH BOTH RBEIN and RBEEX.

User information: RBEIN AND RBEEX ON SET3 ARE MUTUALLY EXCLUSIVE.

6469.2 *** USER FATAL MESSAGE 6469 (GP4)

CASE CONTROL COMMAND MPC ID= %1 SELECTED MULTIPLE SET3 entries WITH RBEIN
or RBEEX.

User information: ALL RIGID ELEMENTS IDS MUST BE COLLECTED ON A SET3 ENTRY.

6470.0 *** SYSTEM INFORMATION MESSAGE 6470 (REIGL0)

MORE EFFICIENT PROCESSING IN LANCZOS EIGENSOLUTION MAY BE POSSIBLE BY
INCREASING THE BUFFER SIZE
OR BY INCREASING THE VALUE OF SYSTEM CELL 199. THE PRODUCT OF THESE TWO
VALUES SHOULD BE
AT LEAST %1 WORDS. IF SYSTEM CELL 199 IS ALREADY ZERO INCREASE MEMORY

6470.1 *** SYSTEM FATAL MESSAGE 6470 (SSMR0D)

THE MASS MATRIX HAS MORE TERMS PER COLUMN THAN CAN FIT IN A BUFFER.
INCREASE THE BUFFER SIZE OR THE VALUE OF SYSTEM CELL 199 SUCH THAT THE
PRODUCT OF THESE TWO VALUES IS AT LEAST %1 WORDS.

6471.0 *** SYSTEM FATAL MESSAGE 6471 (NLITER)

THE BOUNDARY CONDITION SPECIFIED BY THE SPC AND/OR MPC CASE CONTROL
COMMAND IN THE CURRENT SUBCASE
IS DIFFERENT FROM THE PREVIOUS SUBCASE. THIS IS NOT ALLOWED IF THE CURRENT
SUBCASE REQUESTS THE ARC-LENGTH METHOD.

User action: REMOVE THE NLPCI BULK DATA ENTRY.

6472.0 *** USER INFORMATION MESSAGE 6472

NASTRAN SYSTEM(173)>0 IS SPECIFIED. A VALUE OF 1 BLOCKS BOTH THE OFFSET AND
SKEW
FIXES (GIVING PRE VERSION 68 STIFFNESS) AND A VALUE 2 BLOCKS THE SKEW FIX
(GIVING VERSION 68-70.5 STIFFNESS).

Main Index
 654 MSC Nastran Error Messeges
Errors 6000 - 6999

6472.1 *** USER INFORMATION MESSAGE 6472. (EQD4D)

NASTRAN SYSTEM(170)=1 IS SPECIFIED. THEREFORE, THE DIFFERENTIAL STIFFNESS
FOR QUAD4 AND TRIA3 ELEMENTS IS COMPUTED USING THE PRE-VERSION 68
METHOD.

6473.0 *** USER FATAL MESSAGE 6473 (DOM9P2)

THERE IS INSUFFICIENT DATA TO PERFORM OPTIMIZATION.

User information: THE PROBABLE CAUSE IS NO DESOBJ COMMAND IS SPECIFIED IN CASE

CONTROL.

6474.0 *** USER FATAL MESSAGE 6474 (IFS6P)

THE DOPTPRM ENTRY HAS ALREADY SPECIFIED PARAMETER NAME = %1.

User information: YOU MAY SPECIFY A PARAMETER ONLY ONCE.

6474.1 *** USER FATAL MESSAGE 6474 (IFS6P)

THE DOPTPRM ENTRY SPECIFIES AN INVALID PARAMETER NAME = %1.

User information: CHECK FOR THE PROPER SPELLING OF THE PARAMETER NAME.

6474.2 *** USER FATAL MESSAGE 6474 (IFS10P)

THE %1 ENTRY HAS ALREADY SPECIFIED PARAMETER NAME = %2.

User information: YOU MAY SPECIFY A PARAMETER ONLY ONCE.

6474.3 *** USER FATAL MESSAGE 6474 (IFS10P)

THE %1 ENTRY SPECIFIES AN INVALID PARAMETER NAME = %2.

User information: CHECK FOR THE PROPER SPELLING OF THE PARAMETER NAME.

6474.4 *** USER FATAL MESSAGE 6474 (IFS10P)

In BCPARA, FGCNST, FGCNSTR, AND FGCNSTI MUST BE UNIQUE

User information: CHECK FOR THE UNIQUENESS OF THE PARAMETER NAME.

6474.5 *** USER FATAL MESSAGE 6474 (IFS10P)

Main Index
 MSC Nastran Error Messeges 655
Errors 6000 - 6999

In BCPARA, FGCTST, FGCTSTR, AND FGCTSTI MUST BE UNIQUE

User information: CHECK FOR THE UNIQUENESS OF THE PARAMETER NAME.

6474.6 *** USER WARNING MESSAGE 6474 (IFS6P)

IN MDLPRM, PARAM NAME IS BLANK BUT ASSIGNED VALUE, PLEASE CHECK IT.

User information: CHECK FOR BLANK PARAM NAME IN MDLPRM

6474.7 *** USER WARNING MESSAGE 6474 (IFS6P)

LABEL required field of DRESP1 with ID=%1 is not supplied.

6474.8 *** USER FATAL MESSAGE 6474 (ixMDLPRM)

A positive number is required for %1 in %2 entry.

6474.9 *** USER FATAL MESSAGE 6474 (ixMDLPRM)

The MDLPRM entry has an illegal parameter %1 at position %2.

6474.10 *** USER FATAL MESSAGE 6474 (ixMDLPRM)

The MDLPRM entry has illegal value %1 for paramter %2 at position %3.

6474.11 *** USER FATAL MESSAGE 6474 (ixMATTVE)

Initial fictive temperature (IFICT) for Narayanswamy model can not be %1.

6475.0 *** USER WARNING MESSAGE 6475 (OUTPT4)

DATABLOCK %1 IS A SPARSE FACTOR MATRIX AND WILL NOT BE WRITTEN TO THE
OUTPUT4 FILE.

User information: THE SPARSE FACTOR MATRIX FORMAT IS NOT SUPPORTED BY THE
OUTPUT4 MODULE.

6475.1 *** USER WARNING MESSAGE 6475 (OUTPN2)

Main Index
 656 MSC Nastran Error Messeges
Errors 6000 - 6999

DATABLOCK %1 IS A SPARSE FACTOR MATRIX AND WILL NOT BE WRITTEN TO THE

OUTPUT2 FILE IN NEUTRAL FORMAT.

User information: THE SPARSE FACTOR MATRIX FORMAT IS NOT SUPPORTED BY THE
OUTPUT2 MODULE IN NEUTRAL FORMAT.

6475.2 *** USER WARNING MESSAGE 6475 (MATPRT)

DATABLOCK %1 IS A SPARSE FACTOR MATRIX AND WILL NOT BE OUTPUT BY THE MAT-
PRT MODULE.

User information: THE SPARSE FACTOR MATRIX FORMAT IS NOW SUPPORTED BY THE
MATPRN MODULE.

6476.0 *** USER FATAL MESSAGE 6476 (DOPR4)

DESVAR ENTRY ID = %1
IS REFERENCED BY SHAPE VARIABLES (DVGRID/DVSHAP/DVBSHAP) AND PROPERTY
VARIABLES (DVPREL1/DVPREL2)

User information: THE CAPABILITY FOR A DESIGN VARIABLE TO MODIFY BOTH SHAPE
AND PROPERTY VARIABLES
IS NOT SUPPORTED.

6476.1 USER FATAL MESSAGE 6476 (DOP1A4)

User information: This is an SOL200 shape optimization limitation. DVGRID or BNDGRID cannot
design contact grids (i.e., contact grids may not be moved during optimization)

6477.0 *** USER FATAL MESSAGE 6477 (GIGGKG)

FOR SPLINE ENTRY %1 THE FIRST CHORDWISE INTERPOLATED AERODYNAMIC BOX IS
AFT OF THE LAST BOX.

User information: THE INTERPOLATED SET OF AERODYNAMIC BOXES MUST FORM A

TRAPEZOID.
THE VALUES IN FIELDS 4 AND 5 ON THE SPLINE ENTRY DO NOT SPECIFY A SET OF
BOXES.

6478.0 ***USER FATAL MESSAGE 6478. (AXMPR1)

Main Index
 MSC Nastran Error Messeges 657
Errors 6000 - 6999

KEYWORD AUXMODEL=%2

6480.0 *** USER INFORMATION MESSAGE 6480 (REIGLA)

EXTERNAL IDENTIFICATION TABLE FOR DECOMPOSITION MESSAGES FOR MATRIX %1
ROW NUMBER = GRID ID + COMPONENT
%2%3%4

User information:
This message is output from the REIGL module when using sparse decomposition
to convert the internal (row number oriented) diagnostic messages to
external (grid and component) form.

6480.1 EXTERNAL IDENTIFICATION TABLE FOR DECOMPOSITION MESSAGES FOR MATRIX %1

ROW NUMBER = GRID ID + COMPONENT

User information:
This message is output from the REIGL module when using sparse decomposition
to convert the internal (row number oriented) diagnostic messages to
external (grid and component) form.

6481.0 *** SYSTEM INFORMATION MESSAGE 6481 (SOLVIT)

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS

AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO JACOBI PRECONDITION-
ING.

6481.1 *** USER INFORMATION MESSAGE 6481 (SITDRV)

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: USER GIVEN PRECONDITIONING IS AVAILABLE FOR SYMMETRIC

MATRICES ONLY,
SWITCHED TO JACOBI PRECONDITIONING.

6481.2 *** USER INFORMATION MESSAGE 6481 (SITDRV)

Main Index
 658 MSC Nastran Error Messeges
Errors 6000 - 6999

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: REDUCED INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE

FOR SYMMETRIC MATRICES ONLY,
SWITCHED TO JACOBI PRECONDITIONING.

6481.3 *** USER INFORMATION MESSAGE 6481 (SITDRV)

DATA BLOCK %1 IS A COMPLEX MATRIX.

User information: REDUCED INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE

FOR REAL ARITHMETIC ONLY,
SWITCHED TO JACOBI PRECONDITIONING.

6481.4 *** SYSTEM FATAL MESSAGE 6481 (SITDRD)

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: INSIDE THE MODULE, THE ITERATIVE SOLVER IS AVAILABLE FOR SYM-
METRIC MATRICES ONLY.

6481.5 *** SYSTEM FATAL MESSAGE 6481 (ORTHOG)

%1 IS UNSYMMETRIC

User information: ORTHOGONALIZATION IS AVAILABLE FOR SYMMETRIC M MATRICES

ONLY

6481.6 *** USER INFORMATION MESSAGE 6481 (FRRD2)

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE FOR

SYMMETRIC MATRICES ONLY,
SWITCHED TO CHOLESKY PRECONDITIONING.

6481.7 *** USER INFORMATION MESSAGE 6481 (FRRD1D)

Main Index
 MSC Nastran Error Messeges 659
Errors 6000 - 6999

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS

AVAILABLE FOR SYMMETRIC MATRICES ONLY, SWITCHED TO CHOLESKY PRECONDI-
TIONING.

6481.8 *** USER INFORMATION MESSAGE 6481 (FREQ)

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: USER GIVEN PRECONDITIONING IS AVAILABLE FOR SYMMETRIC

MATRICES ONLY,
SWITCHED TO CHOLESKY PRECONDITIONING.

6481.9 *** USER INFORMATION MESSAGE 6481 (FREQ)

DATA BLOCK %1 IS AN UNSYMMETRIC MATRIX.

User information: BLOCK INCOMPLETE CHOLESKY PRECONDITIONING IS AVAILABLE FOR

SYMMETRIC MATRICES ONLY,
SWITCHED TO CHOLESKY PRECONDITIONING.

6481.10 *** SYSTEM FATAL MESSAGE 6481 (SITDRV)

DISTRIBUTED ITERATIVE SOLUTION IS AVAILABLE FOR SYMMETRIC MATRICES ONLY.

User action: SWITCH TO SERIAL EXECUTION.

6481.11 *** SYSTEM INFORMATION MESSAGE 6481 (SITDRV)

DISTRIBUTED ITERATIVE SOLUTION IS AVAILABLE FOR JACOBI PRECONDITIONING
ONLY.
SWITCHED TO JACOBI PRECONDITIONING.

6481.12 *** SYSTEM FATAL MESSAGE 6481 (ORTHOG)

%1 IS A COMPLEX MATRIX

User information: ORTHOGONALIZATION IS AVAILABLE FOR REAL MATRICES ONLY.

6482.0 *** USER FATAL MESSAGE 6482 (DOPR3R)

Main Index
 660 MSC Nastran Error Messeges
Errors 6000 - 6999

FOR SUBCASE %1, THE ANALYSIS TYPE IS %2 BUT THE %3 COMMAND REFERENCES AN
INCOMPATIBLE DRESP1 ENTRY WITH RID =%4 AND RTYPE =%5

6482.1 *** USER FATAL MESSAGE 6482 (DOPR3R)

THE DESGLB COMMAND REFERENCES AN INCOMPATIBLE DRESP1 ENTRY WITH RID =
%1 AND RTYPE = %2.

User information: THE DESGLB COMMAND CAN ONLY REFERENCE TO GLOBAL QUANTI-
TIES WHICH ARE NOT ASSOCIATED
WITH A SUBCASE, SUCH AS WEIGHT OR VOLUME.

User action: REPLACE DESGLB WITH DESSUB.

6482.2 *** USER FATAL MESSAGE 6482 (DOPR3R)

FOR SUBCASE %1, THE ANALYSIS TYPE IS %2 BUT THE %3 COMMAND REFERENCES A
DRESP1 ENTRY WITH RID = %4 AND RTYPE = %5 WITH A NON-ZERO ATTB VALUE = %6

User action: REMOVE THE NON-ZERO ATTB VALUE

6482.3 *** USER FATAL MESSAGE 6482 (DOPR3R)

FOR SUBCASE %1, THE ANALYSIS TYPE IS %2 BUT THE %3 COMMAND REFERENCES A
DRESP1 ENTRY WITH RID = %4 AND RTYPE = %5 WITH A BLANK ATTB VALUE

User action: ADD THE MODE NUMBER IN THE ATTB FIELD OF THE DRESP1 ENTRY

6482.4 *** USER FATAL MESSAGE 6482 (DOPR3A)

DRESP1 ENTRY ID = %1 WITH RTYPE=FRMASS CANNOT BE USED FOR SIZING OR SHAPE
OPTIMIZATION

User action: REPLACE RTYPE=FRMASS WITH RTYPE=WEIGHT or VOLUME.

6482.5 *** USER FATAL MESSAGE 6482 (DOPR3I)

Main Index
 MSC Nastran Error Messeges 661
Errors 6000 - 6999

DRESP1 ENTRY ID = %1 INVOKES A RESPONSE TYPE THAT IS NOT SUPPORTED USING

THE ITERATIVE SOLVER METHOD.

User information: ONLY RTYPE = COMP, FRMASS, WEIGHT OR VOLUME IS SUPPORTED

WHEN SMETHOD IS SPECIFIED IN CASE CONTROL.

User action: REMOVE THE SMETHOD COMMAND TO USE THE DIRECT SOLVER.

6482.6 *** USER FATAL MESSAGE 6482 (DOPR3A)

RTYPE OF BOTH FATIGUE AND FRFTG ARE FOUND ON DRESP1.

User action: SOL 200 SUPPORTS STATICS FATIGUE OR VIBRATION FATIGUE. REMOVE ONE
AND RESUBMIT.

6482.7 *** USER FATAL MESSAGE 6482 (DOPR3A)

FOR TOPOLOGY OPTIMIZATION (TOPVAR or TOMVAR ENTRY) WITH STRESS CONTINU-
ATION LINE

User action: REMOVE ALL RTYPE=STRESS/STRAIN/FORCE/SPCFORCE/CSTRESS/CSTRAIN/

CFAILURE ENTRIES.

6482.8 *** USER FATAL MESSAGE 6482 (DSAF2)

THIS IS NOT SUPPORTED. THE GLOBAL STRESS OPTION ON THE TOPVAR ENTRY
SHOULD BE USED IN ITS STEAD.

User action: REMOVE ALL RTYPE=STRESS/STRAIN/FORCE/CSTRESS/CSTRAIN/CFAILURE

ENTRIES.

6483.0 *** USER FATAL MESSAGE 6483 (EQDGED)

ELEMENT ID = %1 HAS CONNECTING GRIDS THAT MAY NOT FORM A PLANE PARALLEL
TO
THE X-Y PLANE OF THE CID COORDINATE SYSTEM ON THE PLPLANE ENTRY.

6485.0 ***SYSTEM FATAL MESSAGE 6485 (DFBS)

Main Index
 662 MSC Nastran Error Messeges
Errors 6000 - 6999

User action: DO NOT USE THE SPARSE DECOMPOSITION IN THIS PROBLEM OR MODIFY
THE DMAP TO
REPLACE THE LEFT HANDED FBS BY A TRANSPOSE OPERATION FOLLOWED BY A REGU-
LAR FBS.

6486.0 *** SYSTEM FATAL MESSAGE 6486 (CSEDGD)

MAXIMUM NDOF IS NOT EQUAL TO 3 OR 6 FOR EDGE ID=%1

Programmer information: ELEMENT TYPE=%2 AND ELEMENT ID=%3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6487.0 *** SYSTEM FATAL MESSAGE 6487 (CSFCTD)

EDGE DOES NOT EXIST FOR GRID1 = %1 AND GRID2 = %2 IN MEDGE TABLE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6488.0 *** USER FATAL MESSAGE 6488 (NL3NON)

UNABLE TO LOAD THE SERVICE THAT CORRESPONDS TO GROUP NAME %1 ON THE %2
BULK DATA ENTRY.

User action: CHECK THE CONNECT SERVICE ENTRY IN THE FMS THAT IS CALLED BY THE
%2 BULK DATA ENTRY ID %3 AND GROUP NAME %1. EITHER THE CONNECT SERVICE
ENTRY DOES NOT
EXIST OR ITS GROUP NAME DOES NOT MATCH THE GROUP NAME ON THE %2 BULK
DATA ENTRY.

6488.1 *** USER FATAL MESSAGE 6488 (NL3NON)

UNABLE TO LOAD THE SERVICE THAT CORRESPONDS TO GROUP NAME %1 ON THE %2
BULK DATA ENTRY.

User action: CHECK THE CONNECT SERVICE ENTRY IN THE FMS THAT IS CALLED BY THE
%2 BULK DATA ENTRY ID %3 AND GROUP NAME %1. EITHER THE SERVICE NAME IS
INCORRECT OR
THERE IS A PROBLEM WITH THE SCA KERNEL. PLEASE SEE ABOVE FOR ADDITIONAL
INFORMATION.

Main Index
 MSC Nastran Error Messeges 663
Errors 6000 - 6999

6489.0 *** SYSTEM INFORMATION MESSAGE 6489 (NLSOLV)

UNABLE TO UNLOAD SERVICE %1

6490.0 *** USER FATAL MESSAGE 6490 (WRGMTD)

FATAL ERRORS HAVE OCCURRED WHILE PROCESSING MPC AND RIGID ELEMENT
ENTRIES.

Programmer information: SIL NUMBER %1 DOES NOT EXIST IN THE DEPENDENT SIL TABLE.

6491.0 *** USER FATAL MESSAGE 6491, (CIDTRD)

THE INPUT COORDINATE SYSTEM=%1 SPECIFIED ON THE GM%2=%3 BULK DATA
ENTRY IS NOT A RECTANGULAR SYSTEM.

User information: FOR THIS GROUP, THE COORDINATE SYSTEM MUST BE RECTANGULAR.

6492.0 *** USER FATAL MESSAGE 6492 (GP1CCV)

COORDINATE SYSTEM ID=%1 IS DEFINED MORE THAN ONCE.

User information: ALL GMCORD, CORD3G AND CORDIJ ENTRIES MUST HAVE UNIQUE
IDENTIFICATION NUMBERS.

6493.0 *** USER FATAL MESSAGE 6493 (GP1CVG)

THE FEFACE %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT DEFINED.

6493.1 *** USER FATAL MESSAGE 6493 (GP1CVG)

THE FEEDGE %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT DEFINED.

6493.2 *** USER FATAL MESSAGE 6493 (CONVGM)

THE GMSURF %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT DEFINED.

6493.3 *** USER FATAL MESSAGE 6493 (CONVGM)

THE GMCURV %1 SPECIFIED ON THE GMCORD %2 BULK DATA ENTRY IS NOT
DEFINED.

6494.0 *** USER FATAL MESSAGE 6494 (DBINIT)

Main Index
 664 MSC Nastran Error Messeges
Errors 6000 - 6999

THE CONNECT STATEMENT IN THE FMS SECTION REFERS TO AN INVALID NAME.

User information: ONLY THE FOLLOWING NAMES MAY BE SPECIFIED ON THE CONNECT
STATEMENT:
GEOMEVAL BEAMEVAL DRESP3 SPLINEX SERVICE

6495.0 *** SYSTEM FATAL MESSAGE 6495 (DBINIT)

UNABLE TO CONNECT TO GEOMETRY EVALUATOR SPECIFIED ON THE CONNECT FMS
STATEMENT.

6496.0 *** SYSTEM WARNING MESSAGE 6496, (ERGAPI)

THE LIST OF DIAGNOSTIC MESSAGES PRINTED ABOVE IS NOT COMPLETE.

User action: CHECK THE ENTIRE MODEL FOR SIMILAR ERRORS.

6497.0 *** USER FATAL MESSAGE 6497 (TRNJFD)

THE POINT AT: X=%1 Y=%2 Z=%3, IN THE BASIC COORDINATE SYSTEM
COULD NOT BE LOCATED ON FEFACE ID=%4.

6497.1 *** USER FATAL MESSAGE 6497 (TRNJED)

THE POINT AT: X=%1 Y=%2 Z=%3, IN THE BASIC COORDINATE SYSTEM
COULD NOT BE LOCATED ON FEEDGE ID=%4.

6499.0 *** USER FATAL MESSAGE 6499

THE %1 OPTIMIZATION ALGORITHM HAS ENCOUNTERED AN ERROR THAT MAKES
FURTHER PROGRESS IMPOSSIBLE. SEE MESSAGES ABOVE.

6499.1 *** USER FATAL MESSAGE 6499

THE %1 OPTIMIZATION CANNOT MAKE FURTHER PROGRESS DUE TO VIOLATED CON-
STRAINTS HAVING ZERO GRADIENTS.

User action: MODIFY DESIGN OPTIMIZATION MODEL (FOR EXAMPLE CHANGE DESIGN
VARIABLES TO AVOID ZERO GRADIENTS)

6500.0 *** USER FATAL MESSAGE 6500 (%1)

Main Index
 MSC Nastran Error Messeges 665
Errors 6000 - 6999

MULTIPLE SUBCASES WITH DIFFERENT METHOD COMMANDS AND/OR SPC/MPC/

SUPORT COMMANDS HAVE BEEN SPECIFIED
WITH P-ELEMENTS IN NORMAL MODES ANALYSIS.

User information: ONLY ONE BOUNDARY CONDITION AND ONE METHOD COMMAND
PER RUN IS ALLOWED.

6501.0 *** USER WARNING MESSAGE 6501

THE ADAPT=%1 COMMAND IN SUBCASE %2 IS DIFFERENT FROM THAT OF THE FIRST
SUBCASE.

User information: ONLY ONE ADAPT COMMAND SHOULD BE SPECIFIED.

ADAPT=%3 OF THE FIRST SUBCASE WILL BE USED.

6502.0 *** USER INFORMATION MESSAGE 6502 (ADAPT)

THE CURRENT SUPERELEMENT (ID =%1) REQUIRES NO FURTHER P-ADAPTIVE ANALY-
SIS BECAUSE
%2.

6502.1 *** USER INFORMATION MESSAGE 6502 (ADAPT)

P-ADAPTIVE ANALYSIS TERMINATED BECAUSE %1.

6502.2 *** USER INFORMATION MESSAGE 6502 (ADAPT)

THE CURRENT SUPERELEMENT (ID =%1) REQUIRES NO FURTHER P-ADAPTIVE ANALY-
SIS BECAUSE
%2.

User information: MAXIMUM ITERATION IS %3 WHICH IS SPECIFIED ON ADAPT BULK

DATA ENTRY ID = %4

6503.0 *** USER INFORMATION MESSAGE 6503 (%1)

AN ADAPT BULK DATA ENTRY IS NOT SPECIFIED. P-ADAPTIVE ANALYSIS WILL NOT BE
PERFORMED.

6504.0 *** USER INFORMATION MESSAGE 6504 (%1)

Main Index
 666 MSC Nastran Error Messeges
Errors 6000 - 6999

THE ADAPT = %1 CASE CONTROL COMMAND REFERENCES AN UNDEFINED ADAPT

BULK DATA ENTRY.
P-ADAPTIVE ANALYSIS WILL NOT BE PERFORMED.

6505.0 *** USER WARNING MESSAGE 6505 (%1)

PART %1 ON ADAPT BULK DATA ENTRY ID = %2 SPECIFIES ERRTOL=%3 WHICH IS NOT
SUPPORTED.

User information: ERRTOL=0.1 WILL BE USED.

6505.1 *** USER WARNING MESSAGE 6505 (AAAAAAAA)

PART %1 ON ADAPT BULK DATA ENTRY ID = %2 SPECIFIES ERREST=%3 WHICH IS NOT
SUPPORTED.

User information: ERREST=1 WILL BE USED.

6506.0 *** USER WARNING MESSAGE 6506 (%1)

PART %1 ON ADAPT BULK DATA ENTRY ID = %2 SPECIFIES ERREST=0 AND TYPE=%3

User information: NO ERROR ESTIMATE IS PERFORMED AND P-VALUES ARE NOT

CHANGED FOR THIS PART.

6507.0 *** USER WARNING MESSAGE 6507 (ADPMRG)

THE MAXIMUM P VALUE=%1 SPECIFIED FOR DIRECTION #%2 AND ELEMENT ID=%3 IS
LESS THAN THE
STARTING P VALUE=%4. THE MAXIMUM VALUE WILL BE USED FOR THE STARTING
VALUE.

User information: THE MAXIMUM P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY
ID=%5
THE STARTING P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY ID=%6

6507.1 *** USER WARNING MESSAGE 6507 (ADPMRG)

Main Index
 MSC Nastran Error Messeges 667
Errors 6000 - 6999

THE MINIMUM P VALUE=%1 SPECIFIED FOR DIRECTION #%2 AND ELEMENT ID=%3 IS
GREATER THAN THE
STARTING P VALUE=%4. THE MINIMUM VALUE WILL BE USED FOR THE STARTING
VALUE.

User information: THE MINIMUM P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY
ID=%5
THE STARTING P VALUE IS SPECIFIED ON PVAL BULK DATA ENTRY ID=%6

6508.0 *** USER WARNING MESSAGE 6508 (ADPVAL)

TWO PVAL BULK DATA ENTRIES WITH ID=%1 REFERENCE THE ELEMENT ID=%2 BUT
SPECIFY A DIFFERENT COORDINATE
SYSTEM. (CID=%3 AND %4).

6509.0 *** USER FATAL MESSAGE 6509 (ADPVAL)

THE SETTYP FIELD (%1) ON PVAL ENTRY ID = %2 IS NOT VALID.

User information: ONLY %3 AND %4 ARE ALLOWED.

6510.0 *** USER INFORMATION MESSAGE 6510 (ADPVAL)

NO VALID ELEMENTS CAN BE FOUND IN SET %1 WHICH IS REFERENCED BY A PVAL
BULK DATA ENTRY ID=%2.

6511.0 *** USER FATAL MESSAGE 6511 (%1)

ADAPT BULK DATA ENTRY ID = %1 REFERENCED BY AN ADAPT CASE CONTROL DOES
NOT EXIST.

User action: CHECK ADAPT CASE CONTROL AND ADAPT OR PSET BULK DATA ENTRIES.

6512.0 *** SYSTEM FATAL MESSAGE 6512 (GETREC)

RECORD %1 CAN NOT BE FOUND IN THE %2 DATA BLOCK (GINO ID=%3).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6513.0 *** USER FATAL MESSAGE 6513 (GETSDF)

Main Index
 668 MSC Nastran Error Messeges
Errors 6000 - 6999

%1 BULK DATA ENTRY ID=%2 REFERENCES SET %3 WHICH IS NOT SPECIFIED, OR THE
SET CONTAINS IDENTIFICATION
NUMBERS WHICH ARE NOT VALID.

User information: THE SET STATEMENT(S) MUST BE PROCEEDED BY A "SETS DEFINITION"

OR "OUTPUT(POST)" STATEMENT.

6514.0 *** USER WARNING MESSAGE 6514 (SDRPOP)

THE DATAREC=%1 CASE CONTROL COMMAND REFERENCES UNDEFINED OUTPUT
BULK DATA ENTRY.

User information: THE DATAREC COMMAND WILL BE IGNORED.

6517.0 *** SYSTEM FATAL MESSAGE 6517

THE %1-P ELEMENT ID ON VIEWTB RECORD IS %2 IS DIFFERENT FROM THAT OF THE
EST RECORD

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6517.2 *** SYSTEM FATAL MESSAGE 6517 (AAAAAAAA)

THE %1 ELEMENT ID ON VIEWTB RECORD IS %2 IS DIFFERENT FROM THAT OF THE
EST RECORD (%3)

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6517.3 *** SYSTEM FATAL MESSAGE 6517 (SBEMPD)

THE %1-P ELEMENT ID ON VIEWTB RECORD IS %2 IS DIFFERENT FROM THAT OF THE
EST RECORD

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6518.0 *** SYSTEM FATAL MESSAGE 6518 (%1)

FOR %1 ELEMENT ID OF %2, THE NUMBER OF DEGREES-OF-FREEDOM = %3 IS GREATER
THAN THE LENGTH
OF THE DISPLACEMENT VECTOR = %4.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 MSC Nastran Error Messeges 669
Errors 6000 - 6999

6519.0 *** SYSTEM FATAL MESSAGE 6519 (VIEWP)

LENGTH OF %1 RECORD IN %2 DATA BLOCK IS INCORRECT.

Programmer information: LENGTH%3 = %4 WHICH IS NOT MULTIPLES OF %5

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6520.0 *** USER WARNING MESSAGE 6520 (VIEWP)

THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS LESS THAN OR EQUAL TO
GNMAX=SYSTEM(179)=%3.

User information: THE VALUE OF %4 WILL BE USED FOR THE STARTING ID NUMBER.

6520.1 *** USER WARNING MESSAGE 6520

THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS GREATER THAN ITS MAXIMUM
NUMBER=%3.

User information: THE MAXIMUM NUMBER IS IGNORED.

User action: ADJUST THE STARTING AND MAXIMUM NUMBERS WITH THE NASTRAN
STATEMENT SYSTEM CELLS %4 AND %5.

6520.2 *** USER WARNING MESSAGE 6520 (DVIEWP)

THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS LESS THAN OR EQUAL TO
GNMAX=SYSTEM(179)=%3.

User information: THE VALUE OF %4 WILL BE USED FOR THE STARTING ID NUMBER.

6521.0 *** USER WARNING MESSAGE 6521 (VIEWP)

PARAMETER NUMBER %1 (%2=%3) OF VIEWP MODULE IS TOO SMALL WHEN PROCESS-
ING %4 ELEMENT %5.

User information: A JUMP VALUE OF %6 IS USED TO AVOID DUPLICATE VIEW %7 ID'S.

6521.1 *** USER WARNING MESSAGE 6521 (DVIEWP)

Main Index
 670 MSC Nastran Error Messeges
Errors 6000 - 6999

PARAMETER NUMBER %1 (%2=%3) OF DVIEWP MODULE IS TOO SMALL WHEN PROCESS-

ING %4 ELEMENT %5.

User information: A JUMP VALUE OF %6 IS USED TO AVOID DUPLICATE VIEW %7 ID'S.

6522.0 *** USER FATAL MESSAGE 6522 (VIEWP)

THE NEXT VU%1 IDENTIFICATION NUMBER=%2 IS TOO SMALL.

User action: SPECIFY A DIFFERENT STARTING VALUE WITH THE NASTRAN SYSTEM(%3)
STATEMENT.

User information: ITS VALUE SHOULD BE GREATER THAN %4

6523.0 *** USER FATAL MESSAGE 6523 (%1)

THE OUTRCV=%1 CASE CONTROL REFERENCES AN UNDEFINED OUTRCV BULK DATA
ENTRY.

6524.0 *** USER WARNING MESSAGE 6524 (%1)

ELEMENT ID=%1 IS REFERENCED BY MORE THAN ONE OUTRCV BULK DATA ENTRY
WITH ID=%2
THE OUTRCV ENTRY WHICH REFERENCES SET %3 WILL BE USED FOR THE ELEMENT.

6525.0 *** USER WARNING MESSAGE 6525 (%1)

OUTRCV BULK DATA ENTRY ID=%1 SPECIFIES A METHOD (%2) WHICH IS NOT SUP-
PORTED.

User information: METHOD=DIRECT WILL BE USED.

6526.0 *** USER FATAL MESSAGE 6526 (ADPVAL)

THE ADAPT=%1 CASE CONTROL COMMAND REFERENCES UNDEFINED PVAL ENTRY
ID=%2.

6526.1 *** USER FATAL MESSAGE 6526 (ADPVAL)

THE ADAPT=%1 CASE CONTROL COMMAND REFERENCES AN UNDEFINED PSET BULK
DATA ENTRY.

6526.2 *** USER FATAL MESSAGE 6526 (AAAAAAAA)

Main Index
 MSC Nastran Error Messeges 671
Errors 6000 - 6999

THE ADAPT=%1 CASE CONTROL COMMAND REFERENCES UNDEFINED PVAL ENTRY

ID=%2.

6527.0 *** SYSTEM WARNING MESSAGE 6527. (DRMH3)

TABLE %1 INDICATES THAT MATRIX%2 SHOULD HAVE %3 ROWS THE MATRIX TRAILER
INDICATES %4 ROWS;
THE MATRIX AND TABLE ARE INCOMPATIBLE - DATA BLOCKS SKIPPED

6527.1 *** SYSTEM FATAL MESSAGE 6527 (EXTLDD)

THE %1 TABLE INDICATES THAT MATRIX %2 SHOULD HAVE %3 ROWS BUT THE
MATRIX TRAILER INDICATES %4 ROWS.

6528.0 *** SYSTEM WARNING MESSAGE 6528. (DRMH3)

MATRIX %1 SHOULD BE REAL FOR SOLUTION TYPE %2

6528.1 *** SYSTEM WARNING MESSAGE 6528. (DRMH3)

MATRIX %1 SHOULD BE COMPLEX FOR SOLUTION TYPE %2

6529.0 *** USER INFORMATION MESSAGE 6529. (DRMH3A)

COLUMN LABEL DATA BLOCK (109) IS WRONG TYPE,
A COMPLEX LAMA TABLE SHOULD HAVE BEEN SUPPLIED FOR SLTYPE %1; DRMH3
ABORTING.

6529.1 *** SYSTEM WARNING MESSAGE 6529. (DRMH3A)

COLUMN LABEL DATA BLOCK (109) IS WRONG TYPE.
A LAMA TABLE SHOULD HAVE BEEN SUPPLIED FOR SLTYPE %1

6530.0 *** USER WARNING MESSAGE 6530. (DRMH3E)

DRMH3 DATA BLOCK %1 IS AN UNKNOWN TYPE (%2) DATA BLOCK IS SKIPPED.

6530.4 *** SYSTEM INFORMATION MESSAGE 6530. (DRMH3A)

%1 IS AN UNKNOWN SOLUTION TYPE (PARAMETER 1) DEFAULT TYPE (STATICS) SUBSTI-
TUTED

6531.0 *** SYSTEM INFORMATION MESSAGE 6531. (DRMH3C)

Main Index
 672 MSC Nastran Error Messeges
Errors 6000 - 6999

MATRIX %1 HAS MORE MODES (%2) THAN CASE CONTROL RECORDS (%3)
THE LAST CASE CONTROL RECORD WILL BE USED FOR REMAINING MODES

6531.1 *** USER INFORMATION MESSAGE 6531. (DRMH3B)

MATRIX %1 HAS MORE COLUMNS (%2) THAN CASE CONTROL RECORDS (%3)
THE LAST CASE CONTROL RECORD WILL BE USED FOR REMAINING COLUMNS.

6532.0 *** SYSTEM WARNING MESSAGE 6532. (DRMH3E)

THE CASE CONTROL RECORD DOES NOT FIT IN OPEN CORE.
PROBABLY WRONG CASECC TRAILER INFO DRMH3 PROCESSING TERMINATED.

6533.0 *** USER WARNING MESSAGE 6533. (DRMH3E)

COMPLEX FORMAT REQUEST MADE FOR REAL DATA - THE FORMAT REQUEST IS
IGNORED

6533.1 *** USER WARNING MESSAGE 6533. (DRMH3D)

REAL FORMAT REQUEST MADE FOR COMPLEX DATA - THE FORMAT REQUEST IS
IGNORED

6533.2 *** USER WARNING MESSAGE 6533.

REAL/IMAG OR MAG/PHASE FORMAT REQUEST MADE FOR REAL DATA - THE FORMAT
REQUEST IS IGNORED

6534.0 *** USER INFORMATION MESSAGE 6534. (DRMH3C)

MATRIX %1 HAS MORE MODES (%2) THAN LAMA TABLE (%3) FREQ = 0.0 WILL BE USED
FOR REMAINING MODES

6536.0 *** SYSTEM WARNING MESSAGE 6536. (DRMH3E)

MATRIX %1 COLUMNS (%2) DOES NOT MATCH PRODUCT OF CASE CONTROL
RECORDS (%3)
AND TERMS IN TIME POINT LIST (%4). EXTRA RECORDS WILL BE IGNORED.

6536.1 *** USER WARNING MESSAGE 6536. (DRMH3E)

NUMBER OF COLUMNS FOR MATRIX %1= (%2) AND IS NOT AN EVEN MULTIPLE OF 3.
DATA BLOCK IGNORED

6536.2 *** SYSTEM WARNING MESSAGE 6536. (DRMH3D)

Main Index
 MSC Nastran Error Messeges 673
Errors 6000 - 6999

MATRIX %1 COLUMNS (%2) DOES NOT MATCH PRODUCT

OF CASE CONTROL RECORDS (%3) AND TERMS IN FREQUENCY LIST (%4)

6536.3 *** SYSTEM WARNING MESSAGE 6536. (DRMH3D)

NUMBER OF MATRIX COLUMNS FOR MATRIX %1(%2)
IS NOT AN EVEN MULTIPLE OF THE NUMBER OF SUBCASES (%3), DATA BLOCK IS NOT
PROCESSED

6536.4 *** SYSTEM WARNING MESSAGE 6536. (DRMH3D)

NUMBER OF MATRIX COLUMNS FOR MATRIX %1(%2)
IS NOT AN EVEN MULTIPLE OF THE FREQUENCY LIST (%3)

6537.0 *** USER INFORMATION MESSAGE 6537 (%1)

ERRSEC=%1 (SYSTEM CELL 200) IS NOT WITHIN THE RANGE OF %2 THROUGH %3. THE
DEFAULT VALUE OF %4 WILL BE USED.
USER INFORMATION MESSAGE: ERRSEC IS USED AS NUMBER OF DIVIDING SECTION
FOR INCREASING P-VALUES.

6538.0 *** USER WARNING MESSAGE 6538 (SDRPOI)

%1=%2 IN SUBCASE ID=%3 IS NOT ALLOWED IN P-ELEMENT OUTPUT REQUESTS. THE
ALL OPTION IS ASSUMED.

User information: THE DATAREC CASE CONTROL COMMAND AND OUTPUT BULK DATA
ENTRY CAN BE USED TO SPECIFY SETS OF ELEMENTS
FOR SPECIFIC PRINT/PUNCH/PLOT REQUESTS.

6539.0 *** USER WARNING MESSAGE 6539 (IFS6P)

THE VALUES SPECIFIED ON MAT10 ENTRY ID= %1 DO NOT OBEY THE EQUATION: BULK
= RHO*(C**2).

User information: ONLY TWO OF THE THREE VALUES HAVE TO BE SPECIFIED AND THE
UNSPECIFIED VALUE WILL THEN COMPUTED
FROM THE EQUATION ABOVE.

6540.0 *** SYSTEM WARNING MESSAGE 6540(REIGLC)

Main Index
 674 MSC Nastran Error Messeges
Errors 6000 - 6999

THE GRID POINT IDENTIFICATION NUMBER AND THE COMPONENT NUMBER CAN-
NOT BE DETERMINED FOR THE DECOMPOSITION MESSAGES ABOVE.

User action: SPECIFY THE EQEXINS, SILS AND USET TABLE AS INPUT TO THE REIGL MOD-
ULE.

6541.0 *** SYSTEM FATAL MESSAGE 6541 (%1)

VUELEM ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN SYSTEM CELL
(183).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6541.1 *** SYSTEM FATAL MESSAGE 6541 (AAAAAAAA)

VUGRID ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN SYSTEM CELL
(181).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6541.2 *** USER FATAL MESSAGE 6541 (VIEWP)

VUELEM ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN THE SYSTEM
CELL (183).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6541.3 *** USER FATAL MESSAGE 6541 (VIEWP)

VUGRID ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN THE SYSTEM
CELL (181).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6541.4 *** SYSTEM FATAL MESSAGE 6541,

ADAPTIVE GRID ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN SYS-
TEM CELL (179).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6541.7 *** USER FATAL MESSAGE 6541 (DVIEWP)

Main Index
 MSC Nastran Error Messeges 675
Errors 6000 - 6999

VUELEM ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN THE SYSTEM
CELL (183).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6541.8 *** USER FATAL MESSAGE 6541 (DVIEWP)

VUELEM ID =%1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID =%2 IN THE SYSTEM
CELL (181).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6541.9 *** USER FATAL MESSAGE 6541 (APD0)

User information: AERO GRID ID %1 EXCEEDS THE MAXIMUM ALLOWED INTEGER ID %2

IN SYSTEM CELL (%3).

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6543.0 *** USER FATAL MESSAGE 6543, (GP0I),

THERE ARE NO VALID P-ELEMENTS IN THE UNION OF ALL SET ENTRIES REFERENCED
BY ADAPT ID =%1.

6544.0 *** USER FATAL MESSAGE 6544, (GP0I),

THE EDGE WITH GRIDS ID =%1,%2 ON P-ELEMENT ID =%3 IS SHARED BY
AN H-ELEMENT WITH MID SIDE GRID.

User action: REMOVE MID SIDE GRID FROM H-ELEMENT AND VERIFY GEOMETRY.

6545.0 *** USER FATAL MESSAGE 6545 (DOPR3)

A DESGLB = %1 COMMAND APPEARS AT THE SUBCASE LEVEL.

User action: EITHER REPLACE THE DESGLB COMMAND WITH A DESSUB COMMAND OR
PLACE THE DESGLB REQUEST ABOVE THE FIRST SUBCASE.

6546.0 *** USER FATAL MESSAGE 6546 (EQUDFD)

Main Index
 676 MSC Nastran Error Messeges
Errors 6000 - 6999

THE CID FIELD ON PLPLANE ENTRY IS SPECIFIED FOR CQUADX ELEMENT ID = %1.

User action: SET CID TO ZERO OR LEAVE BLANK.

6546.1 *** USER FATAL MESSAGE 6546 (ETRIFD)

THE CID FIELD ON PLPLANE ENTRY IS SPECIFIED FOR CTRIAX ELEMENT ID = %1.

User action: SET CID TO ZERO OR LEAVE BLANK.

6547.0 *** USER WARNING MESSAGE 6547 (RCARD)

THE SEQGP/SEQEP ENTRY HAS MORE THAN ONE DECIMAL POINT IN THE SEQID FIELD.

User information: SEQID WILL BE TRUNCATED AT THE SECOND DECIMAL POINT FROM
THE LEFT.
FOR EXAMPLE, 1.9.2.6 BECOMES 1.9

6548.0 *** SYSTEM FATAL MESSAGE 6548 (SFUPFC)

INSUFFICIENT LOCAL WORKING ARRAY FOR SPARSE MATRIX FORWARD-BACKWARD
SUBSTITUTION.

Programmer information: CHECK THE SECOND ORDER EQUATION ON IC2 IN SPUPFC.

6548.1 *** SYSTEM FATAL MESSAGE 6548 (SFUPBC)

INSUFFICIENT LOCAL WORKING ARRAY FOR SPARSE MATRIX FORWARD-BACKWARD
SUBSTITUTION.

Programmer information: CHECK THE SECOND ORDER EQUATION ON IC2 IN SFUPBC.

6549.0 *** SYSTEM WARNING MESSAGE 6549 (SFMG68)

FOR THE VERSION %1 SPARSE FACTOR MATRIX CALLED %2, RECORD 0 IS INCOMPLETE.

6550.0 *** SYSTEM WARNING MESSAGE 6550 (SFMG68)

FOR THE VERSION %1 SPARSE FACTOR MATRIX CALLED %2, THE MATRIX SIZE IN THE
TRAILER IS INCONSISTENT WITH RECORD 1.

6551.0 *** SYSTEM FATAL MESSAGE 6551 (INPTX2)

%1 WAS DETECTED ON UNIT %2 DURING BINARY %3 PROCESSING

Main Index
 MSC Nastran Error Messeges 677
Errors 6000 - 6999

6552.0 *** USER FATAL MESSAGE 6552 (IFS6P)

THE DOPTPRM ENTRY DOES NOT SPECIFY A PARAMETER NAME.

User information: THIS ENTRY HAS CHANGED FOR VERSION 68. YOU MUST SPECIFY A
PARAMETER NAME AND A VALUE.

6552.1 *** USER FATAL MESSAGE 6552 (IFS10P)

THE %1 ENTRY DOES NOT SPECIFY A PARAMETER NAME.

User information: YOU MUST SPECIFY A PARAMETER NAME AND A VALUE.

6553.0 *** USER FATAL MESSAGE 6553 (DOPR3R)

A %1 RESPONSE HAS BEEN INVOKED BY THE DESSUB COMMAND IN SUBCASE %2,
WHICH IS NOT THE FIRST SUBCASE.

User information: %3 RESPONSES MUST BE INVOKED EITHER ABOVE THE SUBCASE LEVEL
WITH DESGLB OR IN THE FIRST SUBCASE.

6553.1 *** USER FATAL MESSAGE 6553 (DOPR3R)

A %1 RESPONSE HAS BEEN INVOKED BY THE DESSUB COMMAND.

User information: CONSTRAINED %2 RESPONSES MUST BE INVOKED WITH A DESGLB

REQUEST.

6554.0 *** USER FATAL MESSAGE 6554 (DOPR2A)

FOR AN INTERNAL AUXILIARY MODEL:
THE INTERNAL AUXILIARY MODEL, THE AUXILIARY DISPLACEMENT MATRIX, OR A
DVBSHAP BULK DATA ENTRY IS MISSING.

User action: CHECK FOR THE EXISTENCE OF THE AUXILIARY CASE CONTROL SECTION,
AUXILIARY MODEL BULK DATA
SECTION AND DVBSHAP ENTRIES.

6555.0 *** USER FATAL MESSAGE 6555 (DOPR2A)

Main Index
 678 MSC Nastran Error Messeges
Errors 6000 - 6999

BOTH DVBSHAP AND DVSHAP ENTRIES ARE SPECIFIED, WHICH IS NOT ALLOWED.

User action: USE DVBSHAP ENTRIES FOR AN INTERNAL AUXILIARY MODEL OR DVSHAP
ENTRIES FOR AN EXTERNAL AUXILIARY MODEL.

6556.0 *** USER FATAL MESSAGE 6556 (DOPR3K)

DCONSTR ASSOCIATED WITH DRESP1 %1, AN IMPLIED DRESP2, CAN NOT REFERENCE
TABLEDx ID IN LALLOW AND/OR UALLOW FIELDS.

User action: SPECIFIC ALLOWABLES IN REAL NUMBER MUST BE PROVIDED ON DCONSTR

FOR AN IMPLIED DRESP2.

6556.1 *** USER FATAL MESSAGE 6556 (DOPR3K)

DCONSTR ASSOCIATED WITH DRESP2 %1 CAN NOT REFERENCE TABLEDx ID IN LAL-
LOW AND/OR UALLOW FIELDS.

User action: SPECIFIC ALLOWABLES IN REAL NUMBER MUST BE PROVIDED ON DCONSTR

FOR A DRESP2.

6556.2 *** USER FATAL MESSAGE 6556 (DOPR3K)

DCONSTR ASSOCIATED WITH DRESP3 %1 CAN NOT REFERENCE TABLEDx ID IN LAL-
LOW AND/OR UALLOW FIELDS.

User action: SPECIFIC ALLOWABLES IN REAL NUMBER MUST BE PROVIDED ON DCONSTR

FOR A DRESP3.

6556.3 *** USER FATAL MESSAGE 6556 (DOPR3K)

DCONSTR ASSOCIATED WITH DRESP1 %1 WITH RTYPE OTHER THAN FRxxx OR PSDxxx
CAN NOT REFERENCE TABLEDx ID
IN LALLOW AND/OR UALLOW FIELDS.

User action: SPECIFIC ALLOWABLES IN REAL NUMBER MUST BE PROVIDED ON DCONSTR

FOR A DRESP1 WITH RTYPE
HAVING PREFIX OTHER THAN FR OR PSD.

6556.4 *** USER FATAL MESSAGE 6556 (DOPR3K)

Main Index
 MSC Nastran Error Messeges 679
Errors 6000 - 6999

INTERPOLATED LALLOW %1(WITH TABLE %2) IS LARGER THAN OR EQUAL TO UALLOW

%3
(WITH TABLE %4) FOR DRESP1 %5 AT FREQUENCY %6

User action: REVIEW TABLE INPUT DATA AND MAKE SURE TABLE FOR UALLOW WILL
PRODUCE ALLOWABLE HIGHER THAN
LALLOW ACORSS THE FREQUENCY RANGE OF INTEREST

6557.0 *** USER FATAL MESSAGE 6557 (AXCDFD)

STRAIN SINGULARITY WAS ENCOUNTERED IN HYPERELASTIC ELEMENT %1 IN THE
SOLUTION PHASE.

6558.0 *** USER WARNING MESSAGE 6558 (DSADMS)

A DRESP1 ENTRY DEFINES A MARGIN OF SAFETY AS A RESPONSE FOR ELEMENT TYPE
%1, ELEMENT ID = %2,
AND COMPONENT = %3. THE REQUESTED RESPONSE IS NOT AVAILABLE.

User information: THIS PROBABLY INDICATES THAT THE ELEMENT STRESS IS ZERO OR
HAS THE OPPOSITE SIGN OF THE LIMIT STRESS.
HOWEVER, IT COULD INDICATE THAT THE REQUIRED STRESS LIMITS HAVE NOT BEEN
SPECIFIED ON THE MATERIAL
PROPERTY BULK DATA ENTRY.

6559.0 *** USER FATAL MESSAGE 6559 (MODEPT)

THE TABLEDI ID = %1 ENTRY REFERENCED BY A PACABS ENTRY CONTAINS ZERO OR
NEGATIVE VALUES FOR FREQUENCY (XI).

User information: FREQUENCY VALUES SPECIFIED ON THE TABLEDI ENTRY MUST BE

GREATER THAN ZERO.

6560.0 *** USER WARNING MESSAGE 6560 (GPST1T)

THE MAXIMUM NUMBER OF MESSAGES HAVE BEEN ISSUED BY THE GRID POINT STRESS
PROCESSOR (%1 MODULE).

6561.0 *** SYSTEM FATAL MESSAGE 6561 (ULANDD):

DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, A READ ERROR
WAS ENCOUNTERED IN READING THE TRIDIAGONAL FILE %1.

Main Index
 680 MSC Nastran Error Messeges
Errors 6000 - 6999

6562.0 *** SYSTEM FATAL MESSAGE 6562 (ULANDD):

DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, CONVERGENCE
FAILED FOR ONE OR MORE EIGENVALUES.
ERROR IN QL ITERATION, STEP %1

6563.0 *** SYSTEM FATAL MESSAGE 6563 (ULANFD):

DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, A FACTOR ERROR
WAS ENCOUNTERED, ERROR TYPE = %1

6564.0 *** SYSTEM FATAL MESSAGE 6564 (ULANXD):

DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION, A NULL COLUMN
WAS ENCOUNTERED WHILE READING
THE MATRIX FROM FILE %1.

6565.0 *** USER FATAL MESSAGE 6565 (UEIGL):

THE SIXTH OUTPUT DATA BLOCK WHICH IS REQUIRED IS PURGED.

User action: CHECK UEIGL DMAP CALL.

6566.0 *** SYSTEM FATAL MESSAGE 6566 (UEIGL):

THE MASS AND THE DIVERGENCE MATRICES DO NOT EXIST FOR REAL UNSYMMETRIC
LANCZOS.

User action: EITHER THE MASS OR THE DIVERGENCE MATRIX IS REQUIRED.

6567.0 *** SYSTEM FATAL MESSAGE 6567 (UEIGL):

THE INPUT MATRICES TO THE REAL UNSYMMETRIC LANCZOS EIGENVALUE
EXTRACTION MODULE REQUIRE A COMPLEX
EIGENVALUE SOLUTION.

User action: USE THE COMPLEX LANCZOS (CEAD) MODULE.

6568.0 *** SYSTEM WARNING MESSAGE 6568 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, MORE ROOTS THAN EXIST
HAVE BEEN FOUND.

Main Index
 MSC Nastran Error Messeges 681
Errors 6000 - 6999

6569.0 *** USER WARNING MESSAGE 6569 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, NO ROOTS HAVE BEEN
FOUND.

6570.0 *** USER INFORMATION MESSAGE 6570 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, ALL ROOTS REQUIRED
HAVE BEEN FOUND.

6570.1 *** USER INFORMATION MESSAGE 6570 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, ALL ROOTS REQUIRED AT
THIS SHIFT HAVE BEEN FOUND.

6571.0 *** USER FATAL MESSAGE 6571 (DOPR1B)

DESVAR ENTRY %1 IS LISTED AS THE DEPENDENT DESIGN VARIABLE ID ON MORE
THAN ONE DLINK ENTRY

User action: REMOVE THE DUPLICATE REFERENCE TO THE DESVAR ENTRY.

6571.1 *** SYSTEM FATAL MESSAGE 6571 (%1)

A MISSING OR DUMMY SUBROUTINE HAS BEEN CALLED.

6571.2 *** USER FATAL MESSAGE 6571 (DR1XPA)

DESVAR ENTRY %1 OF PART SE %2 IS LISTED AS THE DEPENDENT DESIGN VARIABLE ID
ON MORE THAN ONE SEDLINK ENTRY

User action: REMOVE THE DUPLICATE REFERENCE TO THE DESVAR ENTRY.

6571.3 *** USER FATAL MESSAGE 6571 (ISHELL)

PEM is supported only on Linux and Windows platforms.

6572.0 *** USER WARNING MESSAGE 6572 (TASNP2)

Main Index
 682 MSC Nastran Error Messeges
Errors 6000 - 6999

A TOTAL OF%1 SNORM BULK DATA ENTRIES ARE IGNORED,

BECAUSE THE REFERENCED GRID POINT(S) DO NOT CONNECT TO A SHELL ELEMENT.

User information: THE FOLLOWING IS THE LIST OF THE SNORM ENTRY IDs THAT ARE
IGNORED. (If Modules are present then the
following is the list of SNORM ID/Module ID pairs).

6572.1 *** USER WARNING MESSAGE 6572 (TASN)

A TOTAL OF%1 SNORM BULK DATA ENTRIES ARE IGNORED,
BECAUSE THE REFERENCED GRID POINT(S) DO NOT CONNECT TO A SHELL ELEMENT.

User information: THE FOLLOWING IS THE LIST OF THE FIRST %2 ENTRIES THAT ARE
IGNORED.
%3
%4
%5
%6
%7

6572.2 *** USER FATAL MESSAGE 6572 (TASNP2)

SNORM BULK DATA PROCESSING FAILED DUE TO DETECTION OF %1 BOUNDARY GRID
POINTS ON BGPDT BUT NO SUPERELEMENTS
ARE PRESENT.
PROBABLE CAUSE IS SEQUENCED GRID IDS LARGER THAN THE BASE BGID VALUE (%2)
STORED IN SYSTEM(223).
SEQUENCED GRID IDS ARE ORIGINAL GRID IDS MULTIPLIED BY %3.

6573.0 *** SYSTEM INFORMATION MESSAGE 6573 (EMA).

BECAUSE OF INSUFFICIENT CORE MEMORY AVAILABLE, PARALLEL EMA HAS BEEN
ABORTED SEQUENTIAL EMA WILL BE USED

6573.1 *** SYSTEM INFORMATION MESSAGE 6573 (EMA).

BECAUSE P-VERSION ELEMENTS ARE PRESENT, PARALLEL EMA HAS BEEN DESELECTED
SEQUENTIAL EMA WILL BE USED

6573.2 *** SYSTEM INFORMATION MESSAGE 6573 (EMA).

Main Index
 MSC Nastran Error Messeges 683
Errors 6000 - 6999

BECAUSE HALF MATRIX WAS REQUESTED WITH SYSTEM(215)=1, PARALLEL EMA HAS
BEEN DESELECTED
SEQUENTIAL EMA WILL BE USED

6573.3 *** SYSTEM INFORMATION MESSAGE 6573 (EMA).

BECAUSE OF AVAILABLE CPU AND/OR SYSTEM(107) VALUE CHOSEN, PARALLEL EMA HAS
BEEN DESELECTED
SEQUENTIAL EMA WILL BE USED

6575.0 *** SYSTEM INFORMATION MESSAGE 6575 (EMA).

REVERTING TO FULL MATRIX FORM BECAUSE ASYMMETRY OF ELEMENT MATRICES

6576.0 *** SYSTEM INFORMATION MESSAGE 6576 (EMA).

P-VERSION ELEMENT LEVEL SPILL HAS BEEN ACTIVATED

6577.0 *** SYSTEM FATAL MESSAGE 6577 (REIGL)

FOURTH INPUT DATA BLOCK (CASE CONTROL) IS PURGED AND FIFTH PARAMETER
VALUE (SET ID) IS ZERO IN REIGL MODULE.

User information: SET ID MUST BE GREATER THAN ZERO IF CASE CONTROL IS NOT PRO-
VIDED AS INPUT TO MODULE.

6577.1 *** SYSTEM FATAL MESSAGE 6577 (LANCZOS)

THE FIFTH INPUT DATA BLOCK (CASE CONTROL) IS PURGED AND THE SIXTH
PARAMETER'S VALUE (SET ID) IS LESS THAN ZERO IN THE LANCZOS MODULE.

User information: THE SET ID MUST BE GREATER THAN ZERO IF CASE CONTROL
IS NOT PROVIDED AS INPUT TO THE MODULE.

6577.2 *** SYSTEM FATAL MESSAGE 6577 (LNNRIGL)

FOURTH INPUT DATA BLOCK (CASE CONTROL) IS PURGED AND FIFTH PARAMETER
VALUE (SET ID) IS ZERO IN READ MO
DULE.

User information: SET ID MUST BE GREATER THAN ZERO IF CASE CONTROL IS NOT PRO-
VIDED AS INPUT TO MODULE.

Main Index
 684 MSC Nastran Error Messeges
Errors 6000 - 6999

6578.0 *** SYSTEM FATAL MESSAGE 6578 (REIGL)

REIGL MODULE PARAMETER NUMBER %1 IS OUT OF BOUNDS

6578.1 *** SYSTEM FATAL MESSAGE 6578 (LANCZOS)

LANCZOS MODULE PARAMETER NUMBER %1 IS OUT OF BOUNDS

6578.2 *** SYSTEM FATAL MESSAGE 6578 (LANCZOS)

THE FIRST PARAMETER (IPROB) MUST BE 'MODES

6578.3 *** SYSTEM FATAL MESSAGE 6578 (LNNRIGL)

LNNRIGL MODULE PARAMETER NUMBER ii IS OUT OF BOUNDS

6579.0 *** SYSTEM WARNING MESSAGE 6579 (ORTHRD)

ALL COLUMNS OF MATRIX %1 ARE NULL

6580.0 *** SYSTEM FATAL MESSAGE 6580 (ORSMRD)

MATRIX %1 IS NOT POSITIVE SEMIDEFINITE

6580.1 *** SYSTEM WARNING MESSAGE 6580 (ORSMRD)

MATRIX %1 IS NOT POSITIVE SEMIDEFINITE

6581.0 *** SYSTEM INFORMATION MESSAGE 6581 (ORTHOG)

PERFORMING M-ORTHOGONALIZATION: MATRIX MODIFIED GRAM-SCHMIDT ALGO-
RITHM

6581.1 *** SYSTEM INFORMATION MESSAGE 6581 (ORTHOG)

PERFORMING HOUSEHOLDER ORTHOGONALIZATION

6582.0 *** SYSTEM FATAL MESSAGE 6582 (ORTHOG)

THE NUMBER OF ROWS OF THE INPUT MATRIX %1 ARE LESS THAN THE NUMBER OF
COLUMNS

6583.0 *** SYSTEM INFORMATION MESSAGE 6583 (ORTHOG)

Main Index
 MSC Nastran Error Messeges 685
Errors 6000 - 6999

The MATRIX MODIFIED GRAM-SCHMIDT ORTHOGONALIZATION IS BEING PERFORMED

WITH RESPECT TO AN IDENTITY MATRIX.

User information: THE HOUSEHOLDER METHOD OF ORTHOGONALIZATION MAY BE BET-

TER.

6584.0 *** USER FATAL MESSAGE 6584 (RFORCD)

RFORCE ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED FOR
THIS SUPERELEMENT OR MODULE.

6584.1 *** USER FATAL MESSAGE 6584 (RFORCD)

RFORCE ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED IN
THE MAIN BULK DATA SECTION.

6584.2 *** USER WARNING MESSAGE 6584 (RFORCD)

METHOD = 1 IS SPECIFIED ON THE RFORCE ENTRY IN COMBINATION WITH P-ELE-
MENTS.

User information: METHOD = 1 DOES NOT YIELD CORRECT RESULTS WITH P-ELEMENTS
AND/OR CONSISTENT(NON-LUMPED) MASS.

6584.3 *** USER FATAL MESSAGE 6584 (GRAVD)

GRAV ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED FOR
THIS SUPERELEMENT OR MODULE.

6584.4 *** USER FATAL MESSAGE 6584 (GRAVD)

GRAV ENTRY REFERENCES COORDINATE SYSTEM %1 WHICH IS NOT DEFINED IN THE
MAIN BULK DATA SECTION.

6585.0 *** USER WARNING MESSAGE 6585 (MDSPC7)

CONSTRAINTS (SPC ENTRIES) HAVE BEEN CREATED FOR THE RADIAL DEGREES OF
FREEDOM WHICH ARE LOCATED ON
THE AXIS OF AXISYMMETRY AND ALSO CONNECTED TO A CQUADX OR CTRIAX ELE-
MENT.

6586.0 *** USER FATAL MESSAGE 6586 (NQUDFD)

Main Index
 686 MSC Nastran Error Messeges
Errors 6000 - 6999

NONZERO RADIAL DISPLACEMENTS WERE COMPUTED AT GRID POINT %1 LOCATED

ON THE AXIS OF AXISYMMETRY.

User action: SPECIFY CONSTRAINTS (I.E., SPC/SPC1 ENTRIES) FOR THOSE RADIAL
DEGREES OF FREEDOM.

6587.0 *** SYSTEM FATAL MESSAGE 6587 (SEP1A)

GRID ID = %1 FOR PRESSURE ELEMENT IS MISSING IN EQEXIN TABLE.

6588.0 *** USER FATAL MESSAGE 6588 (SEP1A)

CSUPER %1 REFERENCES PRIMARY SUPERELEMENT %2 WHICH IS UNDEFINED.

6589.0 *** SYSTEM FATAL MESSAGE 6589

LOGIC ERROR

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6589.2 *** SYSTEM FATAL MESSAGE 6589

LOGIC ERROR %1

User action: CONTACT HEXAGON AB CLIENT SUPPORT

6589.3 *** SYSTEM FATAL MESSAGE 6589

LOGIC ERROR %1

User information: CONTACT HEXAGON AB CLIENT SUPPORT.

6589.4 *** SYSTEM FATAL MESSAGE 6589 (SEP1A)

LOGIC ERROR 19713

User information: CONTACT HEXAGON AB CLIENT SUPPORT.

SE ID DOWNSTREAM ID PROCESS ORDER LEVEL TABLE SECON TABLE

6590.0 *** USER FATAL MESSAGE 6590 (SEP2R)

RIGID ELEMENT %1 REFERENCES UNDEFINED GRID POINT %2.

6590.1 *** USER FATAL MESSAGE 6590 (SEPRBE)

Main Index
 MSC Nastran Error Messeges 687
Errors 6000 - 6999

RBE2GS ELEMENT %1 REFERENCE GS GRID %2 IS UNDEFINED.

6590.2 *** SYSTEM FATAL MESSAGE 6590 (SEPRBE)

RBE2GS ELEMENT %1 REFERENCE GS GRID %2 WAS MISSING FROM SEMAP.

6591.0 *** USER FATAL MESSAGE 6591 (SEP2RP)

%1 ELEMENT %2, SUPERELEMENT %3, DEFINES DEPENDENT EXTERIOR POINTS.

User information: The dependent points must be interior to the superelement.

6593.0 *** USER FATAL MESSAGE 6593 (SEP1C)

CSUPEXT ENTRY REFERENCES UNDEFINED SUPERELEMENT %1

6594.0 *** USER FATAL MESSAGE 6594 (SEP1C)

CSUPER %1 REFERENCES GRID POINTS IN SUPERELEMENTS %2 AND %3.

6595.0 *** USER FATAL MESSAGE 6595 (SEP1C)

FIELD 2 ON CSUPER %1 IS ILLEGAL.

6596.0 *** USER WARNING MESSAGE 6596 (SEP1C)

SUPERELEMENT %1 SPECIFIED ON SEFINAL COMMAND DOES NOT EXIST AND IS
IGNORED.

6597.0 *** USER FATAL MESSAGE 6597 (SEP1C)

SUPERELEMENT CONNECTIVITY DOES NOT OBEY SPECIFIED RULES. ORIGINAL
SUPERELEMENT
CONNECTION TABLE FOLLOWS

6598.0 *** USER FATAL MESSAGE 6598 (SEP1C)

SECONDARY SUPERELEMENT %1 CANNOT BE PROCESSED AFTER PRIMARY SUPERELE-
MENT %2

6599.0 *** USER FATAL MESSAGE 6599 (SEP1C)

DUPLICATE ELEMENT IDS %1 %2 AND %3 %4

6599.1 *** USER FATAL MESSAGE 6599 (SEPUEC)

Main Index
 688 MSC Nastran Error Messeges
Errors 6000 - 6999

DUPLICATE ELEMENT IDS %1 %2 AND %3 %4 IN SUPERELEMENT OR

MODULE %5

6600.0 *** USER FATAL MESSAGE 6600 (ebard)

ON CBAR=%1 THE AREA IS ZERO WHILE K1 AND/OR K2 ARE NONZERO

User information: DURING OPTIMIZATION, THE AREA MAY BE OPTIMIZED TO A ZERO

VALUE.

User action: INCREASE PMIN OR DVPREL1 OR DVPREL2 ENTRY OR LEAVE K1 AND K2

UNSPECIFIED.

6600.1 *** USER FATAL MESSAGE 6600 (IFS1P)

ON PBAR ENTRY=%1 THE AREA IS ZERO WHILE K1 AND/OR K2 ARE NONZERO

User action: SPECIFY A NONZERO AREA OR LEAVE K1 AND K2 UNSPECIFIED.

6601.0 *** USER FATAL MESSAGE 6601 (TA1A)

A %1 ELEMENT REFERENCES UNDEFINED ELEMENT %2.

6602.0 *** USER FATAL MESSAGE 6602 (TA1A)

ON CHBDYE ELEMENT %1 THE SIDE %2 IS INCONSISTENT WITH %3 ELEMENT %4.

6603.0 *** SYSTEM WARNING MESSAGE 6603 (MAKMSG)

%1 TABLE CONVERSION REQUESTED BUT NO INPUT TABLE SUPPLIED BY PARAMETER
LIST SPECIFICATIONS.

6604.0 *** SYSTEM WARNING MESSAGE 6604 (MAKMSG)

%1 TABLE CONVERSION REQUESTED BUT NO INPUT TABLE SUPPLIED AS INPUT DATA-
BLOCK, CHECK FILES VERSUS PARAMETER ORDER.

6605.0 *** SYSTEM WARNING MESSAGE 6605 (MAKMSG)

CSTM CONVERSION WITH CONVECTIVE COORDINATE SYSTEMS ALSO REQUIRES THE
BGPDT TABLE FOR COMPLETENESS.

6606.0 *** SYSTEM WARNING MESSAGE 6606 (MAKMSG)

A SIMULATION OF GPL RECORD 2 IS BEING CONSTRUCTED.

Main Index
 MSC Nastran Error Messeges 689
Errors 6000 - 6999

6607.0 *** SYSTEM WARNING MESSAGE 6607 (MAKMSG)

%1 TABLE GENERATION REQUIRES ROOT DATA BLOCKS OF EQEXIN OR SIL AND GPL.

6608.0 *** SYSTEM WARNING MESSAGE 6608 (MAKMSG)

CONVERSION OF CONVECTIVE COORDINATE SYSTEM %1 HAS DETECTED A MISSING
EXTERNAL GRID IDENTIFICATION.

6609.0 *** SYSTEM WARNING MESSAGE 6609 (MAKMSG)

CONVERSION OF EST SIL VALUES FOR ELEMENT %1 ENCOUNTERED A MISSING INDEX
OF %2

6610.0 *** SYSTEM WARNING MESSAGE 6610 (MAKMSG)

CONVERSION OF MSC NASTRAN V68 EST CONTAINING P-ELEMENTS CAN NOT BE DIS-
TINTLY PERFORMED.

6611.0 *** SYSTEM WARNING MESSAGE 6611 (MAKMSG)

CONVERSION OF EST CONTAINING HEAT TRANSFER ELEMENTS IS NOT SUPPORTED.

6612.0 **** SYSTEM WARNING MESSAGE 6612 (MAKRPL)

THE ROOT DATA BLOCK TYPE %1 IS NOT KNOWN, THE DATA BLOCK INFORMATION
WILL BE IGNORED.

6613.0 **** SYSTEM WARNING MESSAGE 6613 (MAKRPL)

THE CONTENT OF ROOT DATA BLOCK TYPE %1 APPEARS TO BE NULL, NO CONVER-
SION WILL BE PERFORMED.

6614.0 *** %1 FATAL MESSAGE 6614 (DOMCB)

THE DESIGNED DIMENSIONS FOR PBARL ENTRY = %1 ARE INCONSISTENT AND PRO-
DUCE BAR
SECTION PROPERTIES THAT ARE UNATTAINABLE.

6614.1 *** SYSTEM FATAL MESSAGE 6614 (DOMCB)

Main Index
 690 MSC Nastran Error Messeges
Errors 6000 - 6999

User action: THE INCONSISTENT DIMENSIONS HAVE MOST LIKELY BEEN PRODUCED
WHEN THE OPTIMIZER
WAS ATTEMPTING TO OVERCOME A VIOLATED CONSTRAINT. IF AN INITIALLY FEASI-
BLE DESIGN CAN
BE PRODUCED, THE FATAL MESSAGE SHOULD NOT OCCUR.

6615.0 *** SYSTEM FATAL MESSAGE 6615 (BLEMSG)

LOGIC ERROR ENCOUNTERED IN BEAM LIBRARY SUBROUTINE.

Programmer information:
SUBNAM = %1 ERROR NUMBER = %2 SECTION TYPE = %3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6616.0 *** USER FATAL MESSAGE 6616 (DOPR1Z)

DVPREL2 ENTRY ID = %1, REFERENCES A A PBARL/PBEAML/PBRSECT/PBMSECT PROP-
ERTY TYPE, WHICH IS NOT ALLOWED.

User information: THE BEAM LIBRARY DIMENSIONS CAN ONLY BE DESIGNED USING THE
DVPREL1 ENTRY.

6617.0 *** USER WARNING MESSAGE 6617 (MAKEOLD)

THERE ARE FIELD(S), WITH NON-DEFAULT VALUES, ON THE FOLLOWING %1 BULK
DATA ENTRY WITH IDS:
%2
( ONLY THE FIRST TEN ARE PRINTED ).

User information: THESE FIELDS WILL NOT BE CONVERTED BY THE MAKEOLD MODULE.

6618.0 *** USER INFORMATION MESSAGE 6618 (SEPRBE)

THE RADIUS DEFINED BY RBE2GS ELEMENT ID %1 CONTAINS THE FOLLOWING
GRID(S) WHICH WERE UNUSED.

User information: THE LIST IS PRESENTED IN ASCENDING RADIAL DISTANCE FROM THE
GS LOCATION.

Main Index
 MSC Nastran Error Messeges 691
Errors 6000 - 6999

6619.0 *** USER WARNING MESSAGE 6619 (SEPRBE)

TWO GRID POINTS COULD NOT BE LOCATED WITHIN THE RADIUS DEFINED BY
RBE2GS ELEMENT ID %1.

User information: THIS ELEMENT WILL BE IGNORED UNLESS THE ELEMENT APPEARS
ABOVE IN "RBE2GS - RBE2 GENERATION INFORMATION".

6621.0 *** SYSTEM INFORMATION MESSAGE 6621

FOR LANCZOS EIGENVALUE ANALYSIS, METHOD WILL BE USED

6621.1 *** SYSTEM INFORMATION MESSAGE 6621 (REIGL)

THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS
METHOD WILL BE USED
BECAUSE OF AVAILABLE NUMBER OF CPUS AND/OR USER DESELECTION. (SEE PARAL-
LEL KEYWORD ON NASTRAN STATEMENT).

6621.2 *** SYSTEM INFORMATION MESSAGE 6621 (REIGL)

THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS
METHOD WILL BE USED
BECAUSE NON-SPARSE DECOMPOSITION IS SELECTED. (SEE SPARSE KEYWORD ON NAS-
TRAN STATEMENT).

6621.3 *** SYSTEM INFORMATION MESSAGE 6621 (REIGL)

THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS
METHOD WILL BE USED
BECAUSE NUMBER OF SEGMENTS=1. (SEE SYSTEM CELL 197 ON NASTRAN STATEMENT
OR NUMS FIELD ON EIGRL ENTRY).

6621.4 *** SYSTEM INFORMATION MESSAGE 6621 (REIGL)

THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS
METHOD WILL BE USED
WITH ONE SEGMENT BECAUSE UPPER FREQUENCY LIMIT IS NOT SPECIFIED ON EIGRL
ENTRY.

6621.5 *** SYSTEM INFORMATION MESSAGE 6621 (REIGL)

Main Index
 692 MSC Nastran Error Messeges
Errors 6000 - 6999

THE PARALLEL LANCZOS METHOD IS DESELECTED AND SEQUENTIAL LANCZOS

METHOD WILL BE USED
BECAUSE THE NUMBER OF DESIRED EIGENVALUES IS SPECIFIED ON EIGRL ENTRY.

6621.6 *** SYSTEM INFORMATION MESSAGE 6621 (REIGL)

FOR LANCZOS EIGENVALUE ANALYSIS METHOD WILL BE USED
WITH ONE SEGMENT BECAUSE UPPER FREQUENCY LIMIT IS NOT SPECIFIED ON EIGRL
ENTRY.

6621.7 *** SYSTEM INFORMATION MESSAGE 6621 (XREAD)

FREQUENCY RANGE MUST BE SPECIFIED IN ORDER TO USE
DMP-PARALLEL LANCZOS METHOD FOR FLUID EIGENMODE ANALYSIS.
SERIAL SOLVER IS USED. DMP IS DISABLED.

6622.0 *** SYSTEM INFORMATION MESSAGE 6622 (REIGL0)

SYSTEM CELL 199 = %1 FORCES MASS MATRIX TO BE LOADED IN MEMORY.

6624.0 *** USER FATAL MESSAGE 6624 (IFP9)

SEE INFORMATION MESSAGES ABOVE

6625.0 *** USER WARNING MESSAGE 6625 (VIEW)

MORE THAN 30 PAIRS OF GLOBAL VIEW FACTORS ARE SPECIFIED FOR RADIATION CAV-
ITY ID=%1.

User information: THE EXTRA PAIRS OF GLOBAL VIEW FACTORS ARE IGNORED.

6626.0 *** USER INFORMATION MESSAGE 6626, (MODGM1),

THE DISPLACEMENT COORDINATE SYSTEM OF THE GRID ID = %1 IS MODIFIED TO CID
=%2 TO MATCH THE
CORRESPONDING %3 ID =%4 CONSTRAINT COORDINATE SYSTEM.

User action: IF THIS IS NOT DESIRE, SPECIFY A COORDINATE SYSTEM ID IN THE CD FIELD
OF GRID ENTRY.

6627.0 *** SYSTEM WARNING MESSAGE 6627 (LANCZ)

%1

Main Index
 MSC Nastran Error Messeges 693
Errors 6000 - 6999

6628.0 *** USER INFORMATION MESSAGE 6628 (SCALED)

%1
SCALER ELEMENT ID =%1 SPECIFIES A CONNECTION TO ITSELF.

6629.0 *** USER FATAL MESSAGE 6629 (TA1BSH)

BUSH ELEMENT ID = %1 HAS INFINITESIMAL LENGTH

User action: SPECIFY CID FIELD ON THE CBUSH ENTRY.

6629.1 *** USER FATAL MESSAGE 6629 (EBSH3D)

BUSH ELEMENT ID = %1 IS SPECIFIED WITH A ORIENTATION VECTOR WHICH IS INFIN-
ITESIMAL OR PARALLEL TO AXIS AB.

6629.2 *** USER FATAL MESSAGE 6629 (ROTOR2)

UNBALNC ID = %1 IS SPECIFIED WITH AN ORIENTATION VECTOR WHICH IS INFINITES-
IMAL OR PARALLEL TO ROTOR AXIS AB.

6629.3 *** USER FATAL MESSAGE 6629 (ROTOR2)

GRID %1 SPECIFIED ON UNBALNC ID = %2 ENTRY WITH CD = %3
GRIDA %4 SPECIFIED ON RSPINR/T ENTRY WITH CD = %5

User action: GRID SPECFIED ON UNBALNC AND GRIDA FROM RSPINR/RSPINT MUST USE
THE SAME CD.

6630.0 *** USER FATAL MESSAGE 6630 (ROTDR1)

ROTOR %1 HAS NO ASSOCIATED MASS WHICH WILL RESULT IN NO GYROSCOPIC
TERMS BEING CALCULATED.

User action: IF THERE IS A PHYSICAL MODEL OF THE ROTOR ATTACHED TO THE GRIDS
LISTED ON THE ROTORG ENTRY VIA
R-ELEMENTS OR MPC EQUATIONS THEN DEFINE THE MODEL AS A SUPERELEMENT
AND PERFORM A STATIC
REDUCTION TO THE ROTORG GRIDS. OTHERWISE, ENSURE THAT THE ROTOR MODEL
HAS ASSOCIATED MASS.

6630.1 *** USER FATAL MESSAGE 6630 (ROTDR1)

Main Index
 694 MSC Nastran Error Messeges
Errors 6000 - 6999

MASS MATRIX IS NOT DEFINED FOR ROTOR %1

6631.0 *** USER FATAL MESSAGE 6631 (EASFD)

TWO GRID POINTS ARE COINCIDENT OR THREE GRID POINTS ARE COLLINEAR FOR
ELEMENT ID = %1

6632.0 *** USER FATAL MESSAGE 6632 (EASFD)

THE NORM OF IMPEDANCE IS TOO SMALL FOR ELEMENT ID = %1 IN FREQUENCY = %2

6633.0 *** USER FATAL MESSAGE 6633, (MODGM1),

FOR GRID ID = %1 CONSTRAINT COORDINATE SYSTEMS SPECIFIED ON THE CIDBC
FIELD OF THE
%2 ENTRY ID =%3 AND %4 ENTRY ID =%5 ARE NOT THE SAME.

User action: EXPLICITLY DEFINE COORDINATE SYSTEM ID IN THE CD FIELD OF THE

GRID ENTRY,
WHICH OVERRIDES THE CIDBC FIELD.

6634.0 *** SYSTEM FATAL MESSAGE 6634 (SSM7D)

INSUFFICIENT MEMORY AS DESCRIBED IN THE FATAL MESSAGE BELOW.

User action: INCREASE MEMORY OR SPECIFY A BLOCK SIZE OF 1 ON THE EIGRL ENTRY
OR THE LANCZOS DMAP MODULE SPECIFICATION.

6635.0 *** SYSTEM FATAL MESSAGE 6635 (TABLD)

INVALID INPUT FOR TABLE INTERPOLATION. TABLE ID = %1
FOR LOGARITHMIC X-AXIS, VALUE = %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6636.0 *** SYSTEM WARNING MESSAGE 6636

THE FOLLOWING DIAGNOSTIC(S) ARE ISSUED BY THE LANCZOS MODULE.

6636.4 *** SYSTEM WARNING MESSAGE 6636 (LNCTRD)

NO MODES EXIST IN THE INTERVAL SPECIFIED (0.0 TO %1 HZ).

6636.5 *** SYSTEM WARNING MESSAGE 6636 (LNCTRD)

Main Index
 MSC Nastran Error Messeges 695
Errors 6000 - 6999

EITHER NO MODES EXIST BETWEEN %1 HZ AND %2 HZ

OR THE EIGENSOLVER WAS UNABLE TO FIND ALL MODES IN THAT RANGE.

6636.6 *** SYSTEM WARNING MESSAGE 6636 (LNCTRD)

THERE ARE ONLY %1 MODES BELOW %2 HZ.

6637.0 *** USER WARNING MESSAGE 6637 (TASNP2)

THE SPECIFIED VALUE FOR PARAM SNORM IS %1 DEGREES

User information: THE PROGRAM WILL USE A VALUE OF %2 DEGREES.

6638.0 *** SYSTEM FATAL MESSAGE 6638 (DOP1c1)

THE %1 SECTION TYPES IN GROUP %2 EXCEED THE LIMIT OF %3 FOR USER DEFINED
BEAM LIBRARIES.

User action: REDUCE THE NUMBER OF SECTION TYPES.

6639.0 *** USER INFORMATION MESSAGE 6639 (ROTDR1)

THE MASS TERMS LISTED ABOVE WILL BE USED TO CALCULATE THE ROTORDYNAMIC
TERMS.

User action: REVIEW THE ABOVE SUMMARY(S) TO ENSURE THAT THE ALL MASS ASSOCI-
ATED WITH THE ROTOR(S)
IS INCLUDED.

6640.0 *** SYSTEM FATAL MESSAGE 6640 (SSM5D):

ITERATIVE SOLVER IS NOT AVAILABLE FOR LANCZOS SUPERMODULE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: IOPTI = %1

6641.0 *** SYSTEM FATAL MESSAGE 6641 (SK11RD)

Main Index
 696 MSC Nastran Error Messeges
Errors 6000 - 6999

ERROR IN READING K11 MATRIX FOR ITERATIVE SOLVER INSIDE STATICS MODULE.
NUMBER OF INDICES AND
NUMBER OF NZ TERMS ARE INCOMPATIBLE IN COLUMN %1
NUMBER OF INDICES: %2 NUMBER OF NZ TERMS: %3

6641.1 *** SYSTEM FATAL MESSAGE 6641 (SCALRD):

ERROR IN READING K11 MATRIX FOR ITERATIVE SOLVER INSIDE STATICS SUPERMOD-
ULE. NUMBER OF INDICES AND
NUMBER OF NZ TERMS ARE INCOMPATIBLE IN COLUMN %1
NUMBER OF INDICES: %2 NUMBER OF NZ TERMS: %3

6642.0 *** USER INFORMATION MESSAGE 6642 (SSM9D)

ERROR RATIO(S) FOR FIRST %1 MODES:

6643.0 *** USER INFORMATION MESSAGE 6643 (SSM9D)

ERROR RATIO FOR LARGEST EPSILON VALUE IN FIRST TEN MODES MODES:

6644.0 *** SYSTEM FATAL MESSAGE 6644 (DOM10)

DESCYCLE, THE FIRST PARAMETER IN THE DOM10 MODULE HAS AN INVALID VALUE
OF %1.

Programmer information: VALID VALUES OF DESCYCLE ARE A POSITIVE INTEGER, -1 OR -2.

6644.1 *** USER WARNING MESSAGE 6644 (FRPROD)

SOME OR ALL COMPUTED EXCITATION FREQUENCIES ARE OUTSIDE THE RANGE F1
AND F2 FOR %1 BULK DATA ENTRY WITH ID =%2
THESE COMPUTED EXCITATION FREQUENCIES ARE IGNORED.

6645.0 *** USER WARNING MESSAGE 6645 (FRSRTD)

FREQ3,FREQ4, AND FREQ5 ENTRIES ARE PRESENT IN A DIRECT FREQUENCY RESPONSE
ANALYSIS.

6647.0 *** USER FATAL MESSAGE 6647 (FRSRTD)

EXCITATION FREQUENCIES CAN NOT BE COMPUTED.
BECAUSE FREQUENCIES ARE NOT AVAILABLE.

6647.1 *** USER FATAL MESSAGE 6647 (FRSRTD)

Main Index
 MSC Nastran Error Messeges 697
Errors 6000 - 6999

EXCITATION FREQUENCIES CAN NOT BE COMPUTED.

BECAUSE FREQUENCIES ARE NOT AVAILABLE.

User action: PROVIDE FREQ, FREQ1 OR FREQ2 CARDS

6648.0 *** USER WARNING MESSAGE 6648 (FRPROD)

THE NUMBER OF FREQUENCIES SPECIFIED ON THE FREQ4 ENTRY ID = %1 IS NOT AN
ODD NUMBER.

User information: AN EXTRA FREQUENCY WILL BE INCLUDED.

6649.1 *** SYSTEM INFORMATION MESSAGE 6649 (DOM9)

MSCADS METHOD = 1 (MMFD) HAS BEEN SELECTED FOR DESIGN CYCLE = %1.

6649.2 *** SYSTEM INFORMATION MESSAGE 6649 (DOM9)

MSCADS METHOD = 2 (SLP) HAS BEEN SELECTED FOR DESIGN CYCLE = %1.

6649.3 *** SYSTEM INFORMATION MESSAGE 6649 (DOM9)

MSCADS METHOD = 3 (SQP) HAS BEEN SELECTED FOR DESIGN CYCLE = %1.

6649.4 *** SYSTEM INFORMATION MESSAGE 6649 (DOM9)

MSCADS METHOD = 4 (SUMT) HAS BEEN SELECTED FOR DESIGN CYCLE = %1.

6649.5 *** SYSTEM INFORMATION MESSAGE 6649 (DOM9)

IPOPT HAS BEEN SELECTED FOR DESIGN CYCLE = %1.

6650.0 *** SYSTEM WARNING MESSAGE 6650 (SSM2)

IMPROPER SET SPECIAL DEFINITION.

6651.0 *** SYSTEM WARNING MESSAGE 6651 (SSM2)

IMPROPER USET TABLE READING.

6652.0 *** USER FATAL MESSAGE 6652 (SSM3D)

Main Index
 698 MSC Nastran Error Messeges
Errors 6000 - 6999

DIFFERENT NUMBER OF LOAD VECTORS AND ENFORCED DISPLACEMENT VECTORS IN

STATICS MODULE
NUMBER OF LOAD VECTORS = %1
NUMBER OF ENFORCED DISPLACEMENT VECTORS = %2

6653.0 *** USER WARNING MESSAGE 6653

ONLY ONE LOAD VECTOR IS ALLOWED WITH THE ITERATIVE SOLVER
THE FIRST ONE WILL BE USED AND THE OTHERS IGNORED

6653.1 *** SYSTEM FATAL MESSAGE 6653 (SITDRD)

INSIDE THE MODULE, THE ITERATIVE SOLVER IS NOT AVAILABLE FOR MULTIPLE LOAD
CASES.

6654.0 *** USER WARNING MESSAGE 6654 (DOM9PR)

APRCOD HAS BEEN RESET TO 1 (DIRECT) BECAUSE THE DESIGN VARIABLES ARE
POTENTIALLY ZERO.

User information: APRCOD IS SET ON THE DOPTPRM BULK DATA ENTRY. APRCOD VALUES
OF 2 OR 3
CAUSE A DIVIDE BY ZERO ERROR WHEN THE DESIGN VARIABLE VALUE IS ZERO.

6654.1 *** USER WARNING MESSAGE 6654 (DISPR)

APRCOD HAS BEEN RESET TO 1 (DIRECT) BECAUSE THE DESIGN VARIABLES ARE
POTENTIALLY ZERO.

User information: APRCOD IS SET ON THE DOPTPRM BULK DATA ENTRY. APRCOD VALUES
OF 2 OR 3
CAUSE A DIVIDE BY ZERO ERROR WHEN THE DESIGN VARIABLE VALUE IS ZERO.

6655.0 *** USER FATAL MESSAGE 6655 (LANCZ)

Main Index
 MSC Nastran Error Messeges 699
Errors 6000 - 6999

THE CASE CONTROL COMMAND METHOD=%1 REFERENCES AN UNSPECIFIED EIGRL

BULK DATA ENTRY.

User action: SUPPLY AN EIGRL ENTRY.

Programmer action: ALTERNATIVELY, SET THE SIXTH PARAMETER TO THE LANCZOS

MODULE (SET ID)
TO A NEGATIVE INTEGER AND SUPPLY EIGRL VALUES TO THE LANCZOS MODULE
DIRECTLY AS PARAMETERS SEVEN THROUGH THIRTEEN.

6655.1 *** USER WARNING MESSAGE 6655 (GETEIGR)

NO EIGR/EIGRL HAS BEEN FOUND CORRESPONDING TO METHOD=%1

User action: SUPPLY AN EIGR OR EIGRL ENTRY WITH THE CORRECT SET ID.

6656.0 *** USER FATAL MESSAGE 6656 (MODTRK)

THE TRACKED SUBSET %1 OF MODES FROM A PREVIOUS DESIGN CYCLE CAN NOT BE
FOUND.

User action: CALL HEXAGON AB CLIENT SUPPORT.

6657.0 *** USER FATAL MESSAGE 6657 (MTD0RD)

NO DRESP1 BULK DATA ENTRIES WERE SPECIFIED FOR PURPOSES OF MODE TRACKING.

6658.0 *** USER WARNING MESSAGE 6658 (MTD0RD)

THERE ARE NO DRESP1 RESPONSES MATCHING THE MODES SPECIFIED FOR MODE
TRACKING.

6659.1 *** SYSTEM WARNING MESSAGE 6659 (DOM9)

OPTCOD HAS BEEN RESET TO MSCADS

User information:
THE DOT OPTIMIZER IS NOT SUPPORTED BY HEXAGON AB IN THIS RELEASE
The program has automatically switched to MSC enhanced ADS optimizer

6659.2 *** SYSTEM WARNING MESSAGE 6659 (DOM9)

Main Index
 700 MSC Nastran Error Messeges
Errors 6000 - 6999

OPTCOD HAS BEEN RESET TO IPOPT

User information:
THE BIGDOT OPTIMIZER IS NOT SUPPORTED BY HEXAGON AB IN THIS RELEASE
The program has automatically switched to optimizer IPOPT.

6659.3 *** SYSTEM WARNING MESSAGE 6659 (DOM9)

User information:
THE DOT OPTIMIZER IS NOT SUPPORTED BY HEXAGON AB IN THIS RELEASE
The program has automatically switched to MSC enhanced ADS optimizer

6659.4 *** SYSTEM WARNING MESSAGE 6659 (DOPR1)

OPTCOD HAS BEEN RESET TO IPOPT DUE TO TOPOLOGY OPTIMIZATION SYMMETRY
OR
CASTING OR EXTRUSION MANUFACTURING CONSTRAINTS.

6659.5 *** SYSTEM WARNING MESSAGE 6659 (DOM9)

OPTCOD HAS BEEN RESET TO MSCADS

User information:
THE BIGDOT OPTIMIZER IS NOT SUPPORTED BY HEXAGON AB IN THIS RELEASE
The program has automatically switched to MSC enhanced ADS optimizer

6659.6 *** SYSTEM WARNING MESSAGE 6659 (DOM9)

OPTCOD HAS BEEN RESET TO IPOPT

User information:
THE DOT OPTIMIZER IS NOT SUPPORTED BY HEXAGON AB IN THIS RELEASE
The program has automatically switched to optimizer IPOPT.

6659.7 *** SYSTEM WARNING MESSAGE 6659 (DOM9)

OPTCOD HAS BEEN RESET TO MSCADS SUMT

User information:
THE BIGDOT OPTIMIZER IS NOT SUPPORTED BY HEXAGON AB IN THIS RELEASE
The program has automatically switched to MSC enhanced ADS optimizer

Main Index
 MSC Nastran Error Messeges 701
Errors 6000 - 6999

6659.8 *** SYSTEM WARNING MESSAGE 6659 (DOPR1)

OPTCOD HAS BEEN RESET TO IPOPT

6659.9 *** SYSTEM WARNING MESSAGE 6659 (DOPR1)

DVPREL1/2 REFERENCES UNDEFINED PROPERTY

User action: SPECIFY APPROPRIATE PROPERTY ENTRY.

6659.10 *** SYSTEM WARNING MESSAGE 6659 (DOPR1)

DVMREL1/2 REFERENCES UNDEFINED PROPERTY

User action: SPECIFY APPROPRIATE PROPERTY ENTRY.

6660.0 *** USER FATAL MESSAGE 6660 (VIEW)

THE RADIATION MATRIX FOR RADIATION CAVITY ID=%1 DEFINED ON RADLST OR
RADMTX BULK DATA ENTRIES HAS WRONG FORMAT OR DATA.

User information: THE RADIATION MATRIX MUST BE SPECIFIED COMPLETELY.

6660.1 *** USER FATAL MESSAGE 6660 (VIEW)

Hemicube method does not support axisymmetric view factor calculations.

User action: Use Gaussian integration method.

6661.0 *** USER INFORMATION MESSAGE 6661 (VIEWP)

THE CURRENT SUPERELEMENT DOES NOT CONTAIN ANY P-ELEMENTS.

6661.1 *** USER INFORMATION MESSAGE 6661 (SDR2AA)

THE CURRENT MODEL DOES NOT CONTAIN ANY P-ELEMENTS.

6662.0 *** USER FATAL MESSAGE 6662 (IFP6CD)

ONE OR MORE MAT1 ENTRIES SPECIFY ZERO FOR YOUNG'S MODULUS , E.

User information: MAT1 ENTRIES REFERENCED BY PCOMP ENTRIES MUST HAVE A

YOUNG'S MODULUS GREATER THAN ZERO.

Main Index
 702 MSC Nastran Error Messeges
Errors 6000 - 6999

6663.0 *** SYSTEM WARNING MESSAGE 6663 (FRRD1D)

THE SOLUTION FOR FREQUENCY %1 (HZ) DID NOT CONVERGE USING THE ITERATIVE
SOLVER.

User information: THE RESULTS FOR THIS FREQUENCY SHOULD BE INSPECTED FOR
VALIDITY.

User action: RERUN THE JOB ONLY FOR THIS FREQUENCY WITH A HIGHER MAXIMUM
NUMBER OF
ITERATIONS (INCREASE ITSMAX ON ITER BULK DATA ENTRY) OR USING THE
DIRECT METHOD (SET ITER=0 ON THE %2 STATEMENT).

6664.0 *** SYSTEM INFORMATION MESSAGE 6664. (DRMH1C)

The following element IDs are of element type %1 (%2) which is not supported in the Output Transfor-
mation Matrix (OTM).
Only the first 1000 elements are shown below and so there may be more elements which are not supported.
If the element type
above is QUAD4C, QUADRC, TRIARC, or TRIA3C then this means that one of the CORNER, BILIN,
SGAGE, or CUBIC keywords is
specified on the STRESS, STRAIN, or FORCE Case Control command. Only the CENTER keyword is
supported in the OTM.

6665.0 *** SYSTEM WARNING MESSAGE 6665 (GP4)

NOT ENOUGH BUFFER SPACE WAS RESERVED TO READ THE SUPORT1 BULK DATA
ENTRIES. %1 WORDS ALLOCATED

Programmer information: PROBABLE CAUSE IS TOO SMALL A SPACE ALLOCATED.

Programmer action: SPECIFY MAXX TO BE GREATER THAN TWO SYSBUFS.

6666.0 *** USER WARNING MESSAGE 6666

The %1 output transformation matrix (OTM) is empty. This may be due to the presence of unsupported
elements as
indicated by User Warning Message 6664 above.

6667.0 USER FATAL MESSAGE 6667 (AXMPR2)

Main Index
 MSC Nastran Error Messeges 703
Errors 6000 - 6999

AUXILIARY MODEL ID=%1 HAS A %2 BULK DATA ENTRY WITH A DUPLICATE ID=%3.

User information: THE IDENTIFICATION NUMBER FOR THIS ENTRY MUST BE UNIQUE
WITH RESPECT TO ANY SIMILAR ENTRY TYPE IN THE PRIMARY MODEL BULK DATA.

6670.0 *** SYSTEM WARNING MESSAGE 6670 (SEQPRT)

SUFFICIENT MEMORY IS NOT AVAILABLE TO RESEQUENCE P-ELEMENT HIERARCHICAL
GRID POINTS IN ORDER TO
OBTAIN MAXIMUM EFFICIENCY DURING MATRIX DECOMPOSITION.

User action: INCREASE MEMORY USING THE MEM KEYWORD ON THE NASTRAN COM-
MAND OR
THE HICORE KEYWORD ON THE NASTRAN STATEMENT.

6671.0 *** USER INFORMATION MESSAGE 6671 (MATMOD):

FOR MATMOD OPTION 10 (COMPLEX CONJUGATE) THE INPUT DATA BLOCK %1 IS
REAL (TYPE = %2).

User information: THE INPUT DATA BLOCK WILL BE COPIED TO THE OUTPUT DATA
BLOCK.

6672.0 *** USER INFORMATION MESSAGE 6672 (MTD1RD)

THE NUMBER OF DEGREES OF FREEDOM IN THE ANALYSIS SET (A-SET) HAVE
CHANGED
FROM THE PREVIOUS DESIGN CYCLE.

User information: ALL DEGREES OF FREEDOM WILL BE USED.

6673.0 *** USER FATAL MESSAGE 6673 (MTD1RD)

THE NUMBER OF DEGREES OF FREEDOM (G-SET) HAS CHANGED FROM THE PREVIOUS
DESIGN CYCLE.

6674.0 *** USER FATAL MESSAGE 6674 (MTD1RD)

MODTRAK BULK DATA ENTRY WITH SID =%1 CANNOT BE FOUND.

6675.0 *** USER INFORMATION MESSAGE 6675 (MTD1RD)

Main Index
 704 MSC Nastran Error Messeges
Errors 6000 - 6999

LOWRNG = %1 ON THE MODTRAK BULK DATA ENTRY IS GREATER THAN THE LOWEST
DRESP1 MODE %2. LOWRNG WILL AUTOMATICALLY BE REDUCED TO %3.

6676.0 *** USER INFORMATION MESSAGE 6676 (MTD1RD)

HIGHRNG = %1 ON THE MODTRAK BULK DATA ENTRY IS LOWER THAN THE HIGHEST
DRESP1 MODE %2. HIGHRNG WILL AUTOMATICALLY BE INCREASED TO %3.

RUN TERMINATED DUE TO MODE TRACKING FAILURE. SEE USER FATAL MESSAGE 6677
6677.0
(MTFTRD) PRINTED ABOVE FOR INFORMATION.

6677.1 *** USER FATAL MESSAGE 6677 (MTFTRD)

MODES CANNOT BE TRACKED:
IN ORDER TO TRACK THESE MODES, IT MAY BE APPROPRIATE TO:
2. DECREASE THE FILTERING PARAMETER, MTFILTER, OR
3. BOTH 1 AND 2
THE PUNCH FILE MAY CONTAIN UPDATED DRESP1 ENTRIES FROM A PREVIOUS
DESIGN CYCLE, WITH 'EIGN IN FIELD 7 WRITTEN
TO CORRESPOND WITH THE POSITIONS OF THE SUCCESSFULLY TRACKED MODES
(OUTPUT OF UPDATED DRESP1 ENTRIES
IS CONTROLLED BY BULK DATA PARAMETER DESPCH. SEE QUICK REFERENCE GUIDE
FOR ITS DETAILED DESCRIPTION).
THESE DRESP1 ENTRIES CAN BE USED TO RESTART FROM THE LAST DESIGN, WITH
ANY OF MODIFICATIONS 1, 2, OR 3, ABOVE.

6678.0 *** USER WARNING MESSAGE 6678 (MTO1RD)

FOLLOWING ARE THE CORRESPONDING NEW POSITIONS OF THE SWITCHING
DESIGNED MODES:

6679.0 *** USER FATAL MESSAGE 6679 (MTMCRD)

TWO OR MORE MODES ARE NEARLY IDENTICAL, WHICH MAKES TRACKING THE
MODES NOT POSSIBLE.

User action: RERUN USING A SMALLER VALUE ON ONE OR MORE OF THE FOLLOWING:
1) DELXV PARAMETER OF THE DESVAR BULK DATA ENTRY
2) DELP PARAMETER OF THE DOPTPRM BULK DATA ENTRY
3) DELX PARAMETER OF THE DOPTPRM BULK DATA ENTRY

Main Index
 MSC Nastran Error Messeges 705
Errors 6000 - 6999

6681.0 *** USER INFORMATION MESSAGE 6681 (SEQRS).

THE MULTIPLE MINIMUM DEGREE METHOD OF RESEQUENCING WAS EXECUTED,
HOWEVER, NO DECOMPOSITION ESTIMATES WERE COMPUTED.

User action: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NAS-
TRAN STATEMENT.

6681.1 *** USER INFORMATION MESSAGE 6681 (SEQRS).

THE NESTED DISSECTION METHOD OF RESEQUENCING WAS EXECUTED, HOWEVER,
NO DECOMPOSITION ESTIMATES WERE COMPUTED.

User action: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NAS-
TRAN STATEMENT.

6681.2 *** USER INFORMATION MESSAGE 6681 (SEQRS).

THE GIBBS-KING METHOD OF RESEQUENCING WAS EXECUTED, HOWEVER, NO
DECOMPOSITION ESTIMATES WERE COMPUTED.

User action: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NAS-
TRAN STATEMENT.

6681.3 *** USER INFORMATION MESSAGE 6681 (SEQRS).

THE WAVEFRONT METHOD OF RESEQUENCING WAS EXECUTED, HOWEVER, NO
DECOMPOSITION ESTIMATES WERE COMPUTED.

User action: IF ESTIMATES ARE REQUIRED, THEN SPECIFY SYSTEM(222)=1 ON THE NAS-
TRAN STATEMENT.

6683.0 *** USER FATAL MESSAGE 6683 (FRRD1A)

ALL COMPUTED EXCITATION FREQUENCIES ARE OUTSIDE THE RANGE F1 AND F2 FOR
FREQ4 AND/OR FREQ5
BULK DATA ENTRIES, OR THERE ARE NO FREQi BULK DATA ENTRIES SPECIFIED.

Programmer information: INPUT FILE 4 DOES NOT EXIST.

6684.0 *** USER FATAL MESSAGE 6684 (DOPR3A)

Main Index
 706 MSC Nastran Error Messeges
Errors 6000 - 6999

NORMAL MODES RTYPE = EIGN AND RTYPE = FREQ HAVE BEEN SELECTED BY DRESP1
ENTRIES IN THE SAME RUN.

User action: USE EITHER OF THEM BUT NOT BOTH ON DRESP1 ENTRIES.

6687.0 *** SYSTEM INFORMATION MESSAGE 6687 (SOLVIT)

ALTERNATIVE CONVERGENCE CRITERION IS NOT AVAILABLE FOR P-VERSION PROB-
LEMS.

User information: CRITERION SWITCHED TO REGULAR CONVERGENCE |R|/|B|.

6688.0 *** USER FATAL MESSAGE 6688 (CONSSD)

ELEMENT %1 ON RSSCON BULK DATA ENTRY %2
IS OF ELEMENT TYPE %3 WHICH CANNOT BE REFERENCED AS A SOLID ELEMENT ON
AN RSSCON.

6688.1 *** USER FATAL MESSAGE 6688 (CONSSD)

ELEMENT TYPE %1 ATTACHED TO SOLID ELEMENT %2 ON RSSCON BULK DATA ENTRY
%3
CANNOT BE REFERENCED AS A SHELL ELEMENT ON AN RSSCON.

6688.2 *** USER FATAL MESSAGE 6688 (SECNSD)

ELEMENT %1 HAS GRID POINTS THAT CANNOT BE LOCATED

6689.0 *** USER FATAL MESSAGE 6689 (GP4RS2)

BULK DATA RSSCON %1 ELEMENT %2 CONNECTED TO ELEMENT %3 IS AN INCOM-
PLETE ATTACHMENT.
ONLY A SUBSET OF THE SHELL GRID AND EDGE DEGREES OF FREEDOM ARE CON-
STRAINED

6689.1 *** USER FATAL MESSAGE 6689 (CONSSD)

RSSCON NUMBER %1 CANNOT CONNECT %2 ELEMENT %3 TO %4 ELEMENT %5

User action: CHECK GEOMETRY

6689.2 *** USER FATAL MESSAGE 6689 (SECNS2)

Main Index
 MSC Nastran Error Messeges 707
Errors 6000 - 6999

BULK DATA RSSCON %1 ELEMENT %2 CONNECTED TO ELEMENT %3 IS AN INCOM-

PLETE ATTACHMENT.
6690.0 *** USER FATAL MESSAGE 6690 (EDGEPD)
THE SHELL ELEMENT GRID POINT ID %1 DOES NOT LIE BETWEEN SOLID GRID POINT
IDS %2 AND %3.

User action: CHECK CONNECTIVITY ON THE RSSCON BULK DATA ENTRY.

6691.0 *** USER FATAL MESSAGE 6691 (GP0CN2)

FEEDGE BULK DATA ENTRY %1 SPECIFIED ON RSSCON BULK DATA ENTRY %2 IS NOT
DEFINED.

6692.0 *** USER FATAL MESSAGE 6692 (RSSCND)

FEEDGE BULK DATA ENTRY %1 SPECIFIED ON RSSCON BULK DATA ENTRY %2 IS NOT
DEFINED.

6692.1 *** USER FATAL MESSAGE 6692 (GP4RSS)

SOLID ELEMENT %1 SPECIFIED ON A RSSCON BULK DATA ENTRY IS NOT DEFINED.

6692.2 *** USER FATAL MESSAGE 6692 (GP4RS1)

SHELL ELEMENT ID %1 SPECIFIED ON RSSCON BULK DATA ENTRY %2 WITH SOLID ELE-
MENT %3 IS NOT DEFINED.

6692.3 *** USER FATAL MESSAGE 6692 (%1)

RSSCON NUMBER %1 CANNOT CONNECT AN EDGE OF %2 ELEMENT %3 TO %4 ELE-
MENT %5

6692.4 *** USER FATAL MESSAGE 6692 (%1)

RSSCON NUMBER %2 CANNOT CONNECT AN EDGE OF SHELL ELEMENT %3 TO SOLID
ELEMENT %4

6692.5 *** USER FATAL MESSAGE 6692 (SEPMEP)

ELEMENT %1 SPECIFIED ON RSSCON ENTRY %2 IS NOT DEFINED.

6692.6 *** USER FATAL MESSAGE 6692 (GP4RS1)

Main Index
 708 MSC Nastran Error Messeges
Errors 6000 - 6999

BULK DATA ENTRY RSSCON CAN NOT FIND ELEMENT IDS,

User action: CHECK SUPERELEMENT OR MODULE STRUCTURE.

6693.0 *** USER FATAL MESSAGE 6693 (GP4RS3)

GRID POINT %1 WHICH IS REFERENCED ON RSSCON BULK DATA ENTRY ID = %2 IS NOT
DEFINED.

6694.0 *** USER FATAL MESSAGE 6694 (GP4RS4)

RSSCON CAUSES CONFLICTING ROTATIONAL CONSTRAINTS AT SHELL GRID POINT %1

6695.0 *** USER FATAL MESSAGE 6695 (%1)

RSSCON NUMBER %1 WILL MPC ONLY GRID %2 OF %3 ELEMENT %4 TO %5 ELEMENT
%6
IT WILL NOT MPC GRID%7; THE CORNER SHELL GRIDS MUST LIE ON OPPOSITE EDGES
OF A FACE OF THE SOLID ELEMENT.

6695.1 *** USER FATAL MESSAGE 6695 (GP4RCD)

RSSCON %1 CANNOT CONNECT SHELL GRID POINT %2 :
User action:, CHECK THE GEOMETRY

6696.0 *** SYSTEM FATAL MESSAGE 6696 (RSSCND)

RSSCON BULK DATA ENTRY %1 WITH FEEDGE ID %2
REFERS TO FEEDGE WITH %3 INSTEAD OF THE %4 REQUIRED DEGREES OF FREEDOM.

6697.0 *** SYSTEM FATAL MESSAGE 6697 (RSSCND)

RSSCON BULK DATA ENTRY %1 HAS EDGES WITH INCONSISTENT POLYNOMIAL
ORDERS %2 %3 %4.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6698.0 *** SYSTEM FATAL MESSAGE 6698 (TWOEDG)

CANNOT FIND COMMON GRID AMONG %1 %2 %3 %4 ON ELEMENT ID %5.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6699.0 *** SYSTEM FATAL MESSAGE 6699 (ORTHOG)

Main Index
 MSC Nastran Error Messeges 709
Errors 6000 - 6999

A SINGLE PRECISION INPUT MATRIX %1 CANNOT BE PROCESSED ON THIS TYPE

MACHINE
WHICH IS DOUBLE PRECISION.

6699.1 *** SYSTEM FATAL MESSAGE 6699 (ORTHOG)

A DOUBLE PRECISION INPUT MATRIX %1 CANNOT BE PROCESSED ON THIS TYPE
MACHINE
WHICH IS SINGLE PRECISION.

6700.0 *** USER WARNING MESSAGE 6700 (FRRD2)

A FREQUENCY RESPONSE SOLUTION AT THIS EXCITATION FREQUENCY IS NOT POSSI-
BLE.

User information: NO SOLUTION WAS POSSIBLE AT THIS FREQUENCY DUE TO A POSSIBLE

SINGULARITY IN THE COMBINED STIFFNESS, MASS, AND DAMPING MATRIX.

6700.1 *** USER WARNING MESSAGE 6700 (FRRD2)

A FREQUENCY RESPONSE SOLUTION AT EXCITATION FREQUENCY=0.0 IS NOT POSSI-
BLE.

User information: THE LIKELY CAUSE IS UNRESTRAINED RIGID BODY MODES.

NO SOLUTION WAS ATTEMPTED AT FREQUENCY=0.0

6701.0 *** USER WARNING MESSAGE 6701 (IFS1P)

BIT, SA, AND SB ARE SPECIFIED FOR CBEAM ELEMENT %1.

User information: SA,SB WILL BE IGNORED.

6701.1 *** USER WARNING MESSAGE 6701

THE MAXIMUM GAP OF %1 BETWEEN A BOUNDARY AND INTERFACE ELEMENT
EXCEEDS THE TOLERANCE ON THE PINTC ENTRY.

User information: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%2 AND
INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%3.

6701.3 *** USER WARNING MESSAGE 6701 (EIFOED)

Main Index
 710 MSC Nastran Error Messeges
Errors 6000 - 6999

THE MAXIMUM GAP OF %1 BETWEEN A BOUNDARY AND INTERFACE ELEMENT

EXCEEDS THE TOLERANCE ON THE PINTS ENTRY.

User information: THE BOUNDARY IS DEFINED ON GMBNDS BULK DATA ENTRY=%2 AND
INTERFACE ELEMENT ON GMINTS BULK DATA ENTRY=%3.

6702.2 *** USER WARNING MESSAGE 6702 (EINPED)

A BOUNDARY END POINT DOES NOT MATCH THE CORRESPONDING INTERFACE ELE-
MENT END POINT.

User information: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND
INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2.

6702.3 *** USER WARNING MESSAGE 6702 (EINOED)

A BOUNDARY END POINT DOES NOT MATCH THE CORRESPONDING INTERFACE ELE-
MENT END POINT.

User information: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND
INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2.

6702.4 *** USER WARNING MESSAGE 6702 (EIFOED)

SOME POINTS ON THIS INTERFACE ELEMENT DO NOT COINCIDE WITH POINTS ON A
BOUNDARY.

User information: THE BOUNDARY IS DEFINED ON GMBNDS BULK DATA ENTRY=%1 AND
INTERFACE ELEMENT ON GMINTS BULK DATA ENTRY=%2.

6702.5 *** USER FATAL MESSAGE 6702 (INTF1B)

BOUNDARY WITH IDENTIFICATION NUMBER,%1, IS NOT GIVEN FOR INTERFACE ELE-
MENT CINTC,%2.

User information: THE BOUNDARY SHOULD BE DEFINED BY BULK DATA ENTRY GMBNDC.

6702.6 *** USER FATAL MESSAGE 6702 (INTF1B)

GRID, %1, IS NOT FOUND FOR INTERFACE BOUNDARY GMBNDC WITH ID, %2.

6702.7 *** USER FATAL MESSAGE 6702 (INTF1B)

Main Index
 MSC Nastran Error Messeges 711
Errors 6000 - 6999

GRIDS ON ONE OF INTERFACE BOUNDARIES BY GMBNDC, EITHER %1 OR %2, ARE TOO

CLOSE TO EACH OTHER.

6702.8 *** USER FATAL MESSAGE 6702 (INTFMD)

THIS INTERFACE ELEMENT CONFIGURATION IS NOT SUPPORTED, CINTC %1 WITH
BOUNDARIES %2 AND %3.

6703.0 *** SYSTEM FATAL MESSAGE 6703 (SSMB1D)

INTERNAL POINTER ERROR: BAD FRONT SIZE CALCULATIONS ON SPLIT 2X2.
FRONT ARRAY WILL CONTAIN INVALID TERMS.

6703.1 *** USER WARNING MESSAGE 6703 (EINPED)

THE LENGTH OF AN ELEMENT'S EDGE ON A BOUNDARY IS SMALL ENOUGH TO CAUSE
NUMERICAL INSTABILITY.

User information: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND
INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2.

6703.2 *** USER WARNING MESSAGE 6703 (EINOED)

THE LENGTH OF AN ELEMENT'S EDGE ON A BOUNDARY IS SMALL ENOUGH TO CAUSE
NUMERICAL INSTABILITY.

User information: THE BOUNDARY IS DEFINED ON GMBNDC BULK DATA ENTRY=%1 AND
INTERFACE ELEMENT ON GMINTC BULK DATA ENTRY=%2.

6704.0 *** SYSTEM FATAL MESSAGE 6704 (DFMFCD)

LOGIC ERROR%1 IN NUMERIC PHASE OF SPARSE DECOMPOSITION.

User action: INCREASE MEMORY BY%2 WORDS.

6705.0 *** SYSTEM WARNING MESSAGE 6705 (DFMAGC)

LOGIC ERROR 2 IN SYMBOLIC PHASE OF SPARSE DECOMPOSITION

User information: PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE

REQUIRED IF THE MATRIX HAS NOT BEEN RESEQUENCED PROPERLY

Main Index
 712 MSC Nastran Error Messeges
Errors 6000 - 6999

6705.2 *** SYSTEM WARNING MESSAGE 6705 (DFMASK)

LOGIC ERROR 3 IN SYMBOLIC PHASE OF SPARSE DECOMPOSITION

User information: PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE

REQUIRED IF THE MATRIX HAS NOT BEEN RESEQUENCED PROPERLY

6705.3 *** SYSTEM WARNING MESSAGE 6705 (DFMSYA)

LOGIC ERROR 1 IN SYMBOLIC PHASE OF SPARSE DECOMPOSITION.

User information: PERFORMANCE MAY BE DEGRADED AND/OR MORE MEMORY MAY BE

REQUIRED IF THE MATRIX HAS NOT BEEN RESEQUENCED PROPERLY.

6706.0 *** SYSTEM FATAL MESSAGE 6706 (PARAML)

PARAML OPTION P1=%1 IS NOT VALID.

6707.0 *** SYSTEM FATAL MESSAGE 6707 (PARAML)

THE PARAML MODULE WITH P1=DTI DETECTS A STRING RECORD.

6707.1 *** SYSTEM FATAL MESSAGE 6707 (PARAML)

THE PARAML MODULE WITH P1=%1 DETECTS INVALID %2 NUMBER=%3 FOR P3.

6708.0 *** USER FATAL MESSAGE 6708 (EBTMPD)

CBEAM ELEMENT %1 DOES NOT HAVE ITS TEMPERATURE SPECIFIED ON TEMP,
TEMPD, TEMPF OR TEMPRB BULK DATA ENTRIES.

User information: P-VERSION CBEAM ELEMENTS CAN ONLY HAVE THEIR TEMPERATURES
SO SPECIFIED.

6709.0 *** SYSTEM WARNING MESSAGE 6709 (ORTHOG)

THE FIFTH INPUT DMAP PARAMETER ( VECTOR DEPENDENCY TOLERANCE ) IS
GREATER THAN ONE.

User information: RESULTS MAY BE IMPLAUSIBLE.

6710.0 *** SYSTEM FATAL MESSAGE 6710 (TAFF)

THE %1 INPUT PARAMETER TO MODULE TAFF REFERENCES AN UNDEFINED LOAD SET
ID.

Main Index
 MSC Nastran Error Messeges 713
Errors 6000 - 6999

6710.1 *** SYSTEM FATAL MESSAGE 6710 (KFRFC)

AN UNDEFINED LOAD SET ID %1 HAS BEEN INPUT TO SUBROUTINE %2 .

6711.0 *** SYSTEM WARNING MESSAGE 6711 (TAFF)

THE INTERNAL ELEMENT ID = %1 EXCEEDS THE UPPER LIMIT DEFINED BY SYSTEM
CELL(183).

6712.0 *** SYSTEM FATAL MESSAGE 6712 (SBUT7)

TOTAL NUMBER OF BIC RECORDS TO BE WRITTEN ON SCRATCH (NRCA+NRCU = %1) IS
LARGER THAN MAXIMUM
NUMBER ALLOWED (MAXBLK = %2).

User action: INCREASE MEMORY SIGNIFICANTLY.

6713.0 *** SYSTEM FATAL MESSAGE 6713 (SBUT7)

THE MATRIX NEEDS TO BE UPDATED AT THIS STAGE, HOWEVER, THE BIC RECORD
NUMBER TO BE READ
(NBLOCK = %1) IS GREATER THAN THE NUMBER OF BIC RECORDS IN THE MATRIX
(NRECA = %2).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6713.1 *** SYSTEM FATAL MESSAGE 6713 (SBUT33)

ERROR IN WRITING TO MATRIX SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT
BELONG TO MATRIX
WHICH HAS ONLY %3 BLOCKS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6713.2 *** SYSTEM FATAL MESSAGE 6713 (SBUT33)

ERROR IN WRITING TO FACTOR SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT
BELONG TO FACTOR.
FACTOR BLOCKS SHOULD BE IN THE RANGE %3 TO %4.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 714 MSC Nastran Error Messeges
Errors 6000 - 6999

6713.3 *** SYSTEM FATAL MESSAGE 6713 (SBUT34)

ERROR IN READING FROM MATRIX SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT
BELONG TO MATRIX
WHICH HAS ONLY %3 BLOCKS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6713.4 *** SYSTEM FATAL MESSAGE 6713 (SBUT34)

ERROR IN READING FROM FACTOR SCRATCH FILE (ISTAT = %1). BLOCK %2 DOES NOT
BELONG TO FACTOR.
FACTOR BLOCKS SHOULD BE IN THE RANGE %3 TO %4.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6713.5 *** SYSTEM FATAL MESSAGE 6713 (SBUT34)

ERROR IN SPILL LOGIC WHILE READING FROM FACTOR SCRATCH FILE (ISTAT = %1).
BLOCK %2 SHOULD
BE IN MEMORY THE FIRST SPILLED BLOCK IS %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6713.6 *** SYSTEM FATAL MESSAGE 6713 (SBUT34)

| ERROR IN SPILL LOGIC WHILE READING FROM MATRIX SCRATCH FILE (ISTAT = %1).
BLOCK %2 SHOULD
| BE IN MEMORY THE FIRST SPILLED BLOCK IS %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6714.0 *** USER FATAL MESSAGE 6714 (FA1)

FLUTTER ENTRY ID = %1 WITH METHOD = PKNL REFERENCES FLFACT ENTRIES WHICH
DO NOT HAVE THE SAME
NUMBER OF DENSITY RATIOS, MACH NUMBERS AND VELOCITIES

6714.1 *** USER FATAL MESSAGE 6714 (dopr3b)

Main Index
 MSC Nastran Error Messeges 715
Errors 6000 - 6999

dresp1 entry = %1 WITH METHOD = PKNL REFERENCES FLFACT ENTRIES WHICH DO NOT
HAVE THE SAME
NUMBER OF DENSITY RATIOS, MACH NUMBERS AND VELOCITIES

6714.2 *** USER FATAL MESSAGE 6714 (dopr3b)

DRESP1 entry = %1 references element ID = %2 representing a seam weld. SOL 200 does not support
specification of
the weld element thickness as an optimization design variable (via DVPREL1/2).

User action: Ensure that DVPREL1/2 does not reference seam welds

6715.0 *** SYSTEM WARNING MESSAGE 6715

THERE IS A ZERO DIAGONAL TERM IN COLUMN %1 OF DATA BLOCK %2 WHICH WILL
BE REPLACED BY 1.0
IN THE PRECONDITIONER.

User action: IT MAY BE BETTER TO USE CHOLESKY PRECONDITIONING (PRECOND=C ON

ITER BULK DATA ENTRY) OR
THE DIRECT SOLVER (ITER=NO ON NASTRAN STATEMENT) FOR THIS PROBLEM.

6715.2 *** SYSTEM FATAL MESSAGE 6715

THERE IS A ZERO DIAGONAL TERM IN COLUMN %1 OF DATA BLOCK %2.

User action: THE CONJUGATE GRADIENT METHOD CANNOT BE USED FOR THIS PROB-
LEM. USE
THE DIRECT METHOD BY SPECIFYING ITER=NO ON THE NASTRAN STATEMENT.

6715.4 *** SYSTEM WARNING MESSAGE 6715

THERE IS A ZERO DIAGONAL TERM IN COLUMN %1 OF DATA BLOCK %2 WHICH WILL
BE REPLACED BY 1.0
IN THE PRECONDITIONER.

User action: IT MAY BE BETTER TO USE CHOLESKY PRECONDITIONING (PRECOND=C ON

ITER BULK DATA ENTRY) OR
THE DIRECT SOLVER (ITER=NO ON NASTRAN STATEMENT) FOR THIS PROBLEM.

6715.6 *** USER FATAL MESSAGE 6715

Main Index
 716 MSC Nastran Error Messeges
Errors 6000 - 6999

THERE IS NO DYNAMIC VISCOSITY SPECIFIED ON THE MAT4 ENTRY FOR CONVM ELE-
MENT %1.

User information: FORCED CONVECTION ELEMENTS REQUIRE SPECIFICATION OF

DYNAMIC VISCOSITY
ON A MAT4 ENTRY IF ON THE PCONVM ENTRY THE REYNOLDS NUMBER CONVEC-
TION EXPONENT
IS GREATER THAN THE PRANDTL NUMBER CONVECTION EXPONENT.

6716.0 *** USER FATAL MESSAGE 6716 (NCNVMD)

THERE IS NO THERMAL CONDUCTIVITY SPECIFIED ON THE MAT4 ENTRY FOR CONVM
ELEMENT %1.

User information: FORCED CONVECTION ELEMENTS REQUIRE CONDUCTIVITY ON A

MAT4 ENTRY IF ON THE PCONVM ENTRY
THE PRANDTL NUMBER CONVECTION EXPONENT IS GREATER THAN ZERO IF FORM=0
AND GREATER THAN ONE IF FORM=1 .

6717.0 *** USER FATAL MESSAGE (SEPMD2)

Grid point %1 in module %2 and specified on MDCONCT entry ID=%3 is either not specified on an
RBE2 entry or
is not the independent grid point (GN) on an RBE2 entry.

User action: Specify the grid point on an RBE2 entry in field GN or change the MDCONCT TYPE to
RIGID or MERGE.

6718.0 *** SYSTEM FATAL MESSAGE 6718 (FRSAD5)

READ ERROR ON MERGED INDEX FILE %1

6719.0 *** SYSTEM FATAL MESSAGE 6719

MATRICES HAVE DIFFERING NUMBERS OF COLUMNS:
[A] = %1 x %2 [B] = %3 x %4 [C] = %5 x %6 [D] = %7 x %8

6719.1 *** SYSTEM FATAL MESSAGE 6719

MATRICES HAVE DIFFERING NUMBERS OF ROWS:
[A] = %1 x %2 [B] = %3 x %4 [C] = %5 x %6 [D] = %7 x %8
6720.0 *** USER WARNING MESSAGE 6720 (REIGL)

Main Index
 MSC Nastran Error Messeges 717
Errors 6000 - 6999

FOR LANCZOS EIGENVALUE ANALYSIS, THERE IS AN INCORRECT RELATIONSHIP

BETWEEN SEGMENT BOUNDARIES.
A HEURISTIC DISTRIBUTION WILL BE USED.

6721.0 *** USER FATAL MESSAGE 6721 (XSBFF)

THE BULK DATA ENTRY FOLLOWING CONTAINS BOTH ENTRY DUPLICATOR AND
FIELD REPLICATOR INFORMATION.

User information:
BULK ENTRY: %1
THE REPLICATOR INFORMATION ON THIS ENTRY IS IGNORED AND
EXISTING REPLICATOR INFORMATION, IF ANY, HAS BEEN RESET
IN ORDER TO RUN THE JOB, EITHER:
A. SPECIFY NASTRAN MESH IN THE FILE MANAGEMENT SECTION
B. REPLACE THE ENTRY WITH TWO ENTRIES:
THE FIRST ENTRY CONTAINS REPLICATOR FIELDS, AND THE SECOND ENTRY CON-
TAINS THE ENTRY DUPLICATOR.

6722.0 *** USER WARNING MESSAGE 6722 (EPLDXD)

THE DIRECTION VECTOR OF PLOADX1 LOADING TYPE IS NOT NORMAL TO SURFACE.

User information: FOLLOWER FORCE STIFFNESS DOES NOT INCLUDE THE EFFECTS OF
THE COMPONENT TANGENTIAL TO THE SURFACE.

6723.0 *** SYSTEM FATAL MESSAGE 6723

NON-POSITIVE DIAGONAL ELEMENT IN SCALAR ROW %1

User action: INCREASE IPAD VALUE ON BULK DATA ENTRY ITER.

6723.1 *** USER FATAL MESSAGE 6723

NON-POSITIVE DIAGONAL ELEMENT IN SCALAR ROW %1

User action: INCREASE IPAD VALUE ON BULK DATA CARD ITER.

6724.0 *** USER FATAL MESSAGE 6724

Main Index
 718 MSC Nastran Error Messeges
Errors 6000 - 6999

TOO MANY RESTARTS.

User action: INCREASE IPAD VALUE ON BULK DATA CARD ITER.

6724.1 *** SYSTEM FATAL MESSAGE 6724

TOO MANY RESTARTS.

User action: INCREASE IPAD VALUE ON BULK DATA ENTRY ITER.

6725.0 *** USER INFORMATION MESSAGE 6725 (SB2RM)

NEGATIVE PIVOTING TERM IN SCALAR ROW %1. IC-PRECONDITIONING HAS BEEN
RESTARTED.
6726.0 *** SYSTEM INFORMATION MESSAGE 6726
INTERNAL ITERATIVE LOOP DOES NOT CONVERGE.

User action: INCREASE VALUE OF IPAD PARAMETER.

6727.0 *** SYSTEM FATAL MESSAGE 6727 (SB50CD)

INCOMPATIBLE DISTRIBUTION OF THE LEFT STACK.

6728.0 *** SYSTEM FATAL MESSAGE 6728 (SB51RD)

ZERO PIVOTING ELEMENT IN ROW %1.

6729.0 *** USER FATAL MESSAGE 6729 (SEPMD2)

There are MDCONCT entries with TYPE=MRBE2 or RRBE2 but there are no RBE2 elements.

6731.0 *** SYSTEM FATAL MESSAGE 6731 (SPCGRD)

ZERO DIAGONAL TERM IN ROW %1.

6731.1 ***USER WARNING MESSAGE 6731

ROW%1 OF LOWER TRIANGULAR FACTOR HAS DIAGONAL TERM = 0( OR .LT. 0 IF
CHOLESKY )

6732.0 *** SYSTEM FATAL MESSAGE 6732

ZERO DIAGONAL ELEMENT IN SCALAR ROW %1 .

6733.0 *** SYSTEM FATAL MESSAGE 6733 (SBUT14)

Main Index
 MSC Nastran Error Messeges 719
Errors 6000 - 6999

EMPTY MINIMUM DEGREE=2.

6734.0 *** SYSTEM FATAL MESSAGE 6734 (SBUT14)

INVALID DEGREE = %1 OF NODE %2 FROM DEGREE 2 QUEUE.

6735.0 *** SYSTEM FATAL MESSAGE 6735 (SBUT14)

INCONSISTENCY: LAST ELEMENT OF DEGREE %1 IS %2, WHILE %3 HAS NO SUBSE-
QUENT NODES.

6736.0 *** SYSTEM FATAL MESSAGE 6736 (SBUT14)

INCONSISTENCY: FIRST ELEMENT OF DEGREE %1 IS %2, WHILE %3 HAS NO PRECEDENT
NODES.

6737.0 *** SYSTEM FATAL MESSAGE 6737 (SBUT14)

INCONSISTENT DEGREE %1

6738.0 *** SYSTEM FATAL MESSAGE 6738 (SBUT14)

INCONSISTENT FIRST NODE %1 OF DEGREE %2

6739.0 *** SYSTEM FATAL MESSAGE 6739 (SBUT14)

INVALID NODE IMIND = %1 (K = %2)
SEARCHED LEVEL RANGE IS %3 - %4 (%5 NODES)
DEPTH %6
MINIMUM DEGREE %7
NUM. UNORDERED %8

6740.0 *** SYSTEM FATAL MESSAGE 6740 (SBUT7)

ERROR WHILE READING BIC RECORD %1 FROM SCRATCH FILE %2. INSTEAD OF THE
REQUESTED %3 WORDS, ONLY %4 WERE READ.

6740.1 *** SYSTEM FATAL MESSAGE 6740 (SBUT34)

ERROR WHILE READING BIC RECORD %1 FROM SCRATCH FILE %2. END OF FILE
WAS ENCOUNTERED BY THIS READ OPERATION.

6741.0 *** SYSTEM FATAL MESSAGE 6741 (SBUT18)

Main Index
 720 MSC Nastran Error Messeges
Errors 6000 - 6999

NEGATIVE LENGTH OF OPEN CORE ARRAY: %1

User action: INCREASE MEMORY.

6742.0 *** SYSTEM FATAL MESSAGE 6742 (SBUT2)

INVALID INPUT VECTOR LFRAGM.

6743.0 *** SYSTEM FATAL MESSAGE 6743 (SBUT2)

INPUT DESCRIPTOR CONTAINS AN ERROR.

6744.0 *** SYSTEM FATAL MESSAGE 6744 (SBUT3)

INCONSISTENCY IN INPUT DATA: MATRIX DIMENSION IS %1 BY DESCRIPTOR AND %2
BY
MATRIX TRAILER.

6745.0 *** SYSTEM FATAL MESSAGE 6745 (SBUT3):

INVALID INPUT DESCRIPTOR TYPE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6746.0 *** SYSTEM FATAL MESSAGE 6746 (SBUT6)

SCALAR MODE IS NOT VALID FOR COMPLEX PROBLEMS.

6747.0 *** SYSTEM FATAL MESSAGE 6747 (SBUT6)

ERROR IN SYMBOLIC OUT-OF-CORE BRANCH. GRF11F IS NOT AVAILABLE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6748.0 *** SYSTEM FATAL MESSAGE 6748 (SBUT6)

ERROR IN SYMBOLIC OUT-OF-CORE BRANCH. GRF13F IS NOT AVAILABLE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6749.0 *** USER FATAL MESSAGE 6749 (GECINT)

THE GMINTC ELEMENT ID = %1 ONLY CONNECTS GMBNDC BOUNDARY ID = %2.

6749.1 *** USER FATAL MESSAGE 6749 (GESINT)

Main Index
 MSC Nastran Error Messeges 721
Errors 6000 - 6999

THE GMINTS ELEMENT ID = %1 ONLY CONNECTS GMBNDC BOUNDARY ID = %2.

6750.0 *** USER FATAL MESSAGE 6750 (GECINT)

THE GMINTC ELEMENT ID = %1 CONNECTS GMBNDC BOUNDARY ID = %2 TO ITSELF.

6750.1 *** USER FATAL MESSAGE 6750 (GESINT)

THE GMINTS ELEMENT ID = %1 CONNECTS GMBNDC BOUNDARY ID = %2 TO ITSELF.

6751.0 *** USER WARNING MESSAGE 6751 (GP4RS3)

FIELDS %1 ON RSSCON BULK DATA ENTRY ID %2 DUPLICATE FIELDS ON A PREVIOUS
ENTRY. THESE FIELDS WILL BE IGNORED.

6752.0 *** USER INFORMATION MESSAGE 6752 (GP4RS3)

THE ROTATIONAL CONSTRAINTS FOR SHELL GRID POINTS %1 AND %2 WILL BE AVER-
AGED
BECAUSE SOLID GRID POINT %3 IS SPECIFIED MORE THAN ONCE ON RSSCON BULK
DATA ENTRIES.

6753.0 *** USER FATAL MESSAGE 6753 (EINPED)

THE DIRECTION FROM THE INITIAL TO THE FINAL GRID OF GMBNDC BOUNDARY ID =
%1 IS OPPOSITE THE DIRECTION
OF GMINTC ELEMENT ID = %2.

6754.0 *** USER FATAL MESSAGE 6754 (GP1C)

NO GRID POINTS DEFINED FOR CORD1I ENTRIES IN SUPERELEMENT %1

6755.0 *** USER FATAL MESSAGE 6755 (SEP1X)

CERTAIN SUPERELEMENT OR MODULE RELATED BULK DATA ENTRIES MAY NOT
APPEAR IN MAIN BULK DATA SECTION.

User information:
ONE OR MORE OF THE FOLLOWING ENTRIES APPEAR IN THE MAIN BULK DATA SEC-
TION.
%1 %2 %3 %4 %5 %6

6755.1 *** USER FATAL MESSAGE 6755 (IFPVAL)

Main Index
 722 MSC Nastran Error Messeges
Errors 6000 - 6999

%1 SUPERELEMENT OR MODULE RELATED BULK DATA ENTRIES MAY NOT APPEAR IN

%2 BULK DATA SECTIONS.

User information:
ONE OR MORE OF THE FOLLOWING %3 BULK DATA ENTRIES APPEAR IN THE %4 BULK
DATA SECTION: WITH SEID = %5

6756.0 *** SYSTEM FATAL MESSAGE 6756 (SEP1X)

THE MAXIMUM NUMBER OF SUPERELEMENTS IS LIMITED TO 32767, WHICH HAS BEEN
EXCEEDED.

6757.0 *** USER FATAL MESSAGE 6757 (SEP1X)

%2 ARE DEFINED BUT NO %1 WERE DETECTED BETWEEN THE %2.

6758.0 *** USER FATAL MESSAGE 6758 (SEPRSC)

GRID POINT %1 IS REFERENCED ON THE EXTERN ENTRY BUT IS NOT CONNECTED TO
THE DOWNSTREAM SUPERELEMENT.

6758.1 *** USER WARNING MESSAGE 6758 (SEPEXT)

THE FOLLOWING GRID OR SCALAR POINTS ARE REFERENCED ON THE EXTRN BULK
DATA ENTRY FOR SUPERELEMENT
%1 BUT ARE NOT CONNECTED TO THE DOWNSTREAM SUPERELEMENT.

6759.0 *** USER FATAL MESSAGE 6759 (SEP2MP)

SCALAR POINT %1 IS SPECIFIED WITH A NONZERO DEGREE OF FREEDOM ON THE
EXTERN ENTRY.
6760.0 *** USER FATAL MESSAGE 6760 (SEP2MP)
EXTRN GRID %1 NOT LOCATED AS PART OF THE SUPERELEMENT BOUNDARY.

6761.0 *** SYSTEM FATAL MESSAGE 6761 (SEP2X)

SUPERELEMENT CANNOT BE FOUND IN THE SEMAP.

6762.0 *** SYSTEM FATAL MESSAGE 6762 (SEP2X)

BOUNDARY %1(%2) NOT FOUND IN THE SEMAP RECORD 2.

6763.0 *** USER WARNING MESSAGE 6763 (SEPAQN)

Main Index
 MSC Nastran Error Messeges 723
Errors 6000 - 6999

OMITi ENTRIES ARE SPECIFIED FOR SUPERELEMENT %1

User information: THE OMITi ENTRIES WILL BE IGNORED.

6764.0 *** USER FATAL MESSAGE 6764 (SEPAQN)

THE VALUE SPECIFIED FOR USER PARAMETER NQSET (AUTOMATIC Q-SET GENERA-
TION) EXCEEDS THE MAXIMUM ALLOWED PER
SUPERELEMENT.

6765.0 *** USER FATAL MESSAGE 6765 (SEPAQN)

THE VALUE SPECIFIED FOR NQSET (AUTOMATIC Q-SET GENERATION) ON THE SEN-
QSET ENTRY EXCEEDS MAXIMUM ALLOWED PER
SUPERELEMENT.

6766.0 *** USER WARNING MESSAGE 6766 (SEPBLK)

THE SEBULK ENTRY FOR COLLECTOR SUPERELEMENT %1 ALSO REFERENCES A PRI-
MARY SUPERELEMENT.

6767.0 *** USER FATAL MESSAGE 6767 (SEPBLK)

COLLECTOR SUPERELEMENT %1 IS ALSO DEFINED AS A PRIMARY SUPERELEMENT VIA
THE BEGIN SUPER, SESET, OR SEELT ENTRIES.

6768.0 *** USER FATAL MESSAGE 6768 (SEPBLK)

THE %1 ENTRY FOR MIRROR %3 %2 DOES NOT REFERENCE A PRIMARY %3.

6768.1 *** USER FATAL MESSAGE 6768 (SEPBLK)

SEBULK ENTRY FOR EXTERNAL SUPERELEMENT %1 DOES NOT REFERENCE A PRIMARY
SUPERELEMENT.

6768.2 *** USER FATAL MESSAGE 6768 (SEPBLK)

THE %1 ENTRY FOR REPEATED %3 %2 DOES NOT REFERENCE A PRIMARY %3.

6769.0 *** USER FATAL MESSAGE 6769 (SEPBLK)

MIRRORED %1 %2 REFERENCES AN UNDEFINED PRIMARY %1.

6769.1 *** USER FATAL MESSAGE 6769 (SEPBLK)

Main Index
 724 MSC Nastran Error Messeges
Errors 6000 - 6999

REPEATED %1 %2 REFERENCES AN UNDEFINED PRIMARY %1.

6770.0 *** USER FATAL MESSAGE 6770 (SEPBLK)

MIRRORED %1 %2 REFERENCES AN UNDEFINED %3 ENTRY.

6770.1 *** USER WARNING MESSAGE 6770 (SEPBLK)

REPEATED %1 %2 REFERENCES NEITHER AN %3 ENTRY NOR AN %4 ENTRY.

6771.0 *** SYSTEM FATAL MESSAGE 6771 (SEPES3)

MAIN BULK ELEMENT %1 DID NOT RESOLVE TO A SUPERELEMENT OR MODULE INDEX

6772.0 *** USER FATAL MESSAGE 6772 (SEPET1)

SUPERELEMENT OR MODULE %1 IS DEFINED IN BOTH THE MAIN BULK DATA SECTION
AND IN A PARTITIONED
BULK DATA SECTION, OR IN A DBLOCATED SECTION.

6773.0 *** USER FATAL MESSAGE 6773 (SEPET2)

THE ELEMENT ID THRU RANGES ON THE SEELT ENTRIES OVERLAP BETWEEN
SUPERELEMENT
%1 GRID %2 AND SUPERELEMENT %3 GRID %4.

6774.0 *** USER WARNING MESSAGE 6774 (SEPET3)

ONE OR MORE ELEMENTS HAVE CONFLICTS BETWEEN GRID/SESET ENTRY SPECIFICA-
TIONS,
STARTING WITH %1 ELEMENT %2 REFERENCE GRID %3

6775.0 *** USER FATAL MESSAGE 6775 (SEPLOC)

THE %1 ENTRY IS UNDEFINED FOR %2 %3.

6775.1 *** USER FATAL MESSAGE 6775 (SEPLOC)

THE %1 ENTRY IS UNDEFINED FOR %2 %3.

6776.0 *** USER FATAL MESSAGE 6776 (SEPLOC)

Main Index
 MSC Nastran Error Messeges 725
Errors 6000 - 6999

BAD GEOMETRY ENCOUNTERED FOR %1 ENTRY AND %2 %3.

User information: RETURN CODE = %4.

1: GRID POINTS APPEAR TO BE COINCIDENT.
2: ATTACHMENT DOES NOT APPEAR TO BE CONGRUENT.
3: GRID POINTS APPEAR TO BE NOT COPLANAR.

6777.0 *** USER FATAL MESSAGE 6777 (SEPLOC)

On the %1,%4 Bulk Data entry, the GRID or POINT %2 cannot be found in the primary %3 %5's Bulk
Data section.

User information: Ensure that the GRIDs or POINTs defined for PAi are specified in the Bulk Data sec-
tion belonging to
RMODID (or RSEID) specified on the MDBULK,MODID (or SEBULK,SEID) entry. Also, ensure that
the GRIDs or
POINTs defined for PBi are specified in the main Bulk Data section.

6778.0 *** USER WARNING MESSAGE 6778 (SEPMA1)

%2 ENTRY FOR %3 %1 CONFLICTS WITH MANUAL CONNECTION SELECTION ON THE
%4 ENTRY.

6779.0 *** USER WARNING MESSAGE 6779 (SEPMAB)

THE SEID FIELD ON THE GRID ENTRIES IS SPECIFIED IN PARTITIONED ENTRIES SUB-
STRUCTURE %1 WILL BE IGNORED

6780.0 *** USER FATAL MESSAGE 6780 (SEPSUP)

INVALID METHOD SPECIFIED FOR SEARCH FOR OVER-RIDE PARAMETER.

6780.1 *** SYSTEM FATAL MESSAGE 6780

FILE POSITIONING ERROR, MEMORY SEID %1 FILE SEID %2

6781.0 *** USER FATAL MESSAGE 6781 (SEPMC1)

SUPERELEMENT %1 REFERENCES ITSELF ON SECONCT ENTRY

6782.0 *** USER FATAL MESSAGE 6782 (SEPMC2/SEPMD2)

Main Index
 726 MSC Nastran Error Messeges
Errors 6000 - 6999

THE FOLLOWING GRIDS OR SCALAR POINTS SPECIFIED ON %1 ENTRIES COULD NOT

BE LOCATED
IN %2 %3

6783.0 *** USER FATAL MESSAGE 6783 (SEPMC2/SEPMD2)

THE %1 ENTRY %9 SPECIFIED BETWEEN %2 %3, %4 AND GRIDS %5, %6 IS NOT WITHIN
TOLERANCE.
ACCEPTANCE TOLERANCE IS %7 BUT FOUND DISTANCE IS %8

6783.1 *** USER FATAL MESSAGE 6783 (SEPMD2)

THE MDCONCT ENTRY ID=%8 SPECIFIED BETWEEN LOCATION ( %1, %2, %3 ) AND
GRID %4 in MODULE %5 IS NOT WITHIN TOLERANCE.
ACCEPTANCE TOLERANCE IS %6 BUT FOUND DISTANCE IS %7

6784.0 *** USER FATAL MESSAGE 6784 (SEPMC2/SEPMD2)

%1 BETWEEN %2 %3 and %4 AND GRIDS %5 and %6 ARE NOT OF THE SAME TYPE.

6785.0 *** USER FATAL MESSAGE 6785 (SEPMC3)

THE SECONCT OR MDCONCT ENTRY SPECIFIES A CONFLICT BETWEEN SUPERELE-
MENT OR MODULE %1 GRID %2
AND SUPERELEMENT OR MODULE %3 GRIDS %4 %5.

6786.0 *** SYSTEM FATAL MESSAGE 6786 (SEPMEP)

SUPERELEMENT OR MODULE %1 DURING CONVERSION LOOP WAS NOT LOCATED IN
MEMORY RESIDENT TABLE,
LOGIC ERROR.

6787.0 *** USER FATAL MESSAGE 6787 (SEPMM2)

GRID %1 IN SUPERELEMENT OR MODULE %2 IS SPECIFIED ON BOTH (SEEXCLD OR
MDEXCLD) AND
(SECONCT OR MDCONCT) ENTRIES.

6788.0 *** USER FATAL MESSAGE 6788 (SEPMM3)

THE FOLLOWING GRID POINTS IN SUPERELEMENT OR MODULE %1 ARE SPECIFIED ON
BOTH (SEEXCLD OR MDEXCLD)
AND (SEBNDRY OR MDBNDRY) ENTRIES.

Main Index
 MSC Nastran Error Messeges 727
Errors 6000 - 6999

6788.1 *** USER FATAL MESSAGE 6788 (SEPMSF)

SUPERELEMENT OR MODULE %1 GRID %2 AND SUPERELEMENT OR MODULE %3 GRID
%4 HAVE CONFLICTING
MANUAL DIRECTIVES.

6789.0 *** USER FATAL MESSAGE 6789 (SEPMQ1)

GRID %1 REFERENCED IN %2 ENTRY IN SUPERELEMENT %3

User information: ONLY SCALAR POINTS MAY BE REFERENCED ON %4 ENTRIES

6790.0 *** USER FATAL MESSAGE 6790 (SEPO21)

THE FOLLOWING SUPERELEMENT(S) ARE DETACHED:

6790.1 *** USER FATAL MESSAGE 6790 (SEPMQ1)

GRID POINT %1 SPECIFIED ON %2 IS NOT DEFINED FOR SUPERELEMENT OR MODULE
%3.

6790.2 *** USER INFORMATION MESSAGE 6790 (SEPO21)

THE FOLLOWING MODULE(S) ARE NOT CONNECTED TO ANY OTHER MODULE EITHER
AUTOMATICALLY OR MANUALLY (MDCONCT):

6791.0 *** SYSTEM FATAL MESSAGE 6791 (SEPO22)

ALIGNMENT FAILURE FOR AUTO-QSET %1 TO THE LOCAL SEMAP MEMORY TABLE.

6792.0 *** USER WARNING MESSAGE 6792 (SEPOMT)

THE PERMANENT SET CONSTRAINT SPECIFICATION FOR %4 GRID %1 IN %3 %2
IS DIFFERENT FROM THE UPSTREAM %3.

User information: THE PERMANENT SET CONSTRAINTS WILL BE UNIONED.

6793.0 *** SYSTEM FATAL MESSAGE 6793 (SEPRSC)

THE GENERATION OF SUPERELEMENT BOUNDARY GRIDS IS COLLIDING WITH THE
GENERATION OF Q-SET
IDENTIFICATION NUMBERS.

6794.0 *** USER FATAL MESSAGE 6794 (SEPSEB)

Main Index
 728 MSC Nastran Error Messeges
Errors 6000 - 6999

DUPLICATE BOUNDARY POINTS DETECTED CONNECTING TO SUPERELEMENT OR

MODULE %1 AT GRID %2
FROM DOWNSTREAM %3.
LIST FOLLOWS:

6794.1 *** USER FATAL MESSAGE 6794 (SEPSEB)

DUPLICATE BOUNDARY POINTS DETECTED IN UPSTREAM SUPERELEMENT OR MOD-
ULE %1 WHILE SEARCHING
%2 AT GRID %3.
LIST FOLLOWS:

6795.0 *** SYSTEM WARNING MESSAGE 6795 (SEPSEB)

NO %2 WERE FOUND FOR %3 %1

6795.1 *** SYSTEM FATAL MESSAGE 6795 (SEPSEB)

NO AUTOMATIC OR MANUAL (MDCONCT) CONNECTIONS WERE FOUND FOR MOD-
ULE %1. NOR WERE THERE ANY CONNECTIONS FOUND VIA:
MDBOLT, MDFAST, MDSEAM, MDWELD, MDMPC, MDRBE2, MDRJNT, MDRROD,
MDDMIG, MDRBE3 and MDBCNCT.

6796.0 *** USER WARNING MESSAGE 6796 (SEPSEQ)

%1 ENTRY FOR GRID %2 IN SUPERELEMENT %3 CONFLICTS WITH SESET/GRID
ENTRIES.

6797.0 *** USER WARNING MESSAGE 6797 (SEPSET)

NO GRID POINTS SPECIFIED ON SESET ENTRIES FOR SUPERELEMENT %1 CAN BE
FOUND.

6798.0 *** USER WARNING MESSAGE 6798 (SEPTRE)

BOTH DTI,SETREE AND SETREE ENTRIES ARE SPECIFIED.

User information: THE DTI,SETREE ENTRY WILL BE IGNORED.

6799.0 *** USER WARNING MESSAGE 6799 (SEP1C)

%1 ELEMENT %2 IS REFERENCED ON MORE THAN ONE SEELT ENTRY.
USERS INFORMATION: SEE SEELT ENTRIES FOR SUPERELEMENTS %3 AND %4.

Main Index
 MSC Nastran Error Messeges 729
Errors 6000 - 6999

6800.0 *** USER FATAL MESSAGE 6800 (SEPTRE)

SUPERELEMENT %1 DEFINED IN MAIN BULK DATA SECTION IS UPSTREAM OF PARTI-
TIONED
BULK DATA SUPERELEMENT %2

6801.0 *** USER WARNING MESSAGE 6801 (SEPTRE)

ERRORS ENCOUNTERED IN THE SETREE, OR DTI,SETREE ENTRY.

User information: A SINGLE LEVEL TREE WILL BE ASSUMED.

6802.0 *** SYSTEM FATAL MESSAGE 6802 (SEPSUP)

SUPERELEMENT %1 HAS FAILED TO AUTOMATICALLY DERIVE A SEARCH KEY.

User action: REVIEW MODEL FOR REASONABLE GEOMETRY AND SELECT SEARCH KEY VIA
OVER-RIDE PARAMETER AND/OR REVIEW
GRID POINT LOCATIONS FOR REASONABLE GEOMETRY

6802.1 *** SYSTEM WARNING MESSAGE 6802 (SEPRBE)

RBE2GS ELEMENT %1 SEARCH KEY IS OUTSIDE OF MODEL BOUNDS.

User information: ELEMENT WILL BE IGNORED.

6803.0 *** USER FATAL MESSAGE 6803 (BNDSP3)

ENFORCED DISPLACEMENTS ON SUPERELEMENT BOUNDARY POINTS ARE DETECTED
AND SHOWN IN THE TABLE BELOW.

User action: MOVE THOSE SPCD OR SPC ENTRIES THAT ARE APPLIED ON BOUNDARY
POINTS TO THE BULK DATA SECTION
OF THE DOWNSTREAM SUPERELEMENT.

6804.0 *** SYSTEM FATAL MESSAGE 6804 (BNDSP3)

THE DISPLACEMENT COORDINATE SYSTEM (CD FIELD ON GRID ENTRY) SPECIFIED
FOR BOUNDARY GRID ID %1 B
IN SUPERELEMENT %2 IS NOT CONGRUENT WITH DISPLACEMENT COORDINATE SYS-
TEMS
IN OTHER CONNECTING SUPERELEMENTS.

Main Index
 730 MSC Nastran Error Messeges
Errors 6000 - 6999

6805.0 *** USER FATAL MESSAGE 6805 (BNDSP4)

BOUNDARY GRID ID = %1 B AND COMPONENT = %2 IS SPECIFIED ON AN SPCI ENTRY IN
MORE THAN
ONE SUPERELEMENT.

User information: THE COMPONENTS OF BOUNDARY GRID POINTS CAN ONLY BE SPECI-
FIED ONCE ON SPCI ENTRIES.

6805.1 *** USER FATAL MESSAGE 6805 (BNDSP4)

BOUNDARY GRID ID = %1 B IS SPECIFIED ON AN SPCI ENTRY IN MORE THAN ONE
SUPERELEMENT.

User information: THE BOUNDARY GRID POINTS CAN ONLY BE SPECIFIED ONCE ON SPCI
ENTRIES.

6806.0 *** SYSTEM FATAL MESSAGE 6806 (CURV)

RETURNED ERROR CONDITION %1, LOC CODE = %2, IN SUBROUTINE CURV%3, FILE
NUM = %4
(NOTE ADDITIONAL MESSAGES.)

6807.0 *** USER WARNING MESSAGE 6807 (CURVIT)

LOCAL INTERPOLATION USING INDEPENDENT VALUES WITHIN RANGE OF THE %1-TH
SORTED ORDER
GRID ID INVOLVED WITH RESPECT TO MATERIAL COORDINATE SYSTEM ID = %2 CAN
NOT BE COMPLETED.
ILL-CONDITION MAY HAVE RESULTED FROM ALIGNMENT OF INDEPENDENT VALUE
COORDINATES.
OUTPUT FOR THE GRID ID IN QUESTION WILL NOT APPEAR.

User information: INTERPOLATION MAY FAIL WHEN THE CENTROIDS OF THE ELEMENTS
DO NOT FORM A PLANE.
ENSURE THAT THE ELEMENT CENTROIDS FORM A PLANE RATHER THAN A LINE.

6808.0 *** USER WARNING MESSAGE 6808 (TAFEST)

Main Index
 MSC Nastran Error Messeges 731
Errors 6000 - 6999

METHOD %1 IS SPECIFIED ON THE RFORCE %2 BULK DATA ENTRY

FOLLOWER FORCE EFFECTS ARE NOT COMPUTED FOR METHOD %1.

User action: SPECIFY METHOD=2 ON THE RFORCE ENTRY.

6809.0 *** USER FATAL MESSAGE 6809 (DOPR1I)

DVPREL%1 ENTRY %2 REFERENCES A DESIGN VARIABLE FOR A TAPERED BEAM BUT
ONLY ONE END IS
SPECIFIED ON THE REFERENCED PBEAM ENTRY.

User action: SPECIFY BOTH ENDS A AND B ON THE PBEAM ENTRY FOR A TAPERED BEAM.

6810.0 *** SYSTEM WARNING MESSAGE 6810 (WRTTRL)

ATTEMPT TO WRITE MATRIX TRAILER ON %1 WITH TRAILER WORD 7 GREATER THAN
MBIT= %2.

Programmer information: THE TRAILER WORD 7 NEEDS TO BE INITIALIZED TO ZERO AND

NOT MBIT TO HAVE
THE DENSITY AUTOMATICALLY COMPUTED.

6813.0 *** USER FATAL MESSAGE 6813 (A?)

FUNCTION NAME '%1' HAS BEEN USED ON BOTH SIDES OF THE SAME EQUAL SIGN

6814.0 *** SYSTEM FATAL MESSAGE 6814 (SBSYM2)

REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 2ND PART.

6814.1 *** SYSTEM FATAL MESSAGE 6814 (SBSYM2)

REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 1ST PART.

6814.2 *** SYSTEM FATAL MESSAGE 6814 (SBSYM1)

REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 2ND PART.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6814.3 *** SYSTEM FATAL MESSAGE 6814 (SBSYM1)

Main Index
 732 MSC Nastran Error Messeges
Errors 6000 - 6999

REPEATED INDEX %1 AT FULL ROW %2 (NEW %3), 1ST PART.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6815.0 *** SYSTEM FATAL MESSAGE 6815 (SBSYM2)

FINAL MF = %1 # %2.

6816.0 *** SYSTEM FATAL MESSAGE 6816 (SBSYM5)

CRITICAL AMOUNT OF FREE SPACE AT THE BEGINNING OF PROCESSING ROW %1.

6817.0 *** SYSTEM FATAL MESSAGE 6817 (SBSYM2)

ROW INDEX = %1 IS OUT OF RANGE, L = %2, IL=LBLEN+%3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6818.0 *** SYSTEM FATAL MESSAGE 6818

INCORRECT PERMUTATION VECTOR (DOUBLE-REFERENCE).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6818.1 *** SYSTEM FATAL MESSAGE 6818

INCORRECT PERMUTATION VECTOR (OUT-REFERENCE).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6818.2 *** SYSTEM FATAL MESSAGE 6818 (SBSYM6)

INVALID PERMUTATION PROCEDURE, B=%1 < L=%2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6818.5 *** SYSTEM FATAL MESSAGE 6818

INCORRECT STRUCTURE OF THE PERMUTATION VECTOR.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6818.8 *** SYSTEM FATAL MESSAGE 6818 (SBSYM3)

Main Index
 MSC Nastran Error Messeges 733
Errors 6000 - 6999

INVALID PERMUTATION PROCEDURE, B=%1 < L=%2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6819.0 *** SYSTEM FATAL MESSAGE 6819 (SBSYM6)

SPECIFIED BUFFER LENGTH = %1 IS TOO SMALL FOR A SINGLE ROW OF FACTOR
MATRIX (NEEDS %2 WORDS).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6819.1 *** SYSTEM FATAL MESSAGE 6819 (SBSYM6)

SPECIFIED BUFFER LENGTH = %1 IS TOO SMALL FOR A SINGLE ROW OF INPUT MATRIX
(NEEDS %2 WORDS).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6820.0 *** SYSTEM FATAL MESSAGE 6820 (SBSYM6)

INCORRECT STORAGE OF INFORMATION ABOUT RECORDS OF FACTOR FILE: L = %1,
NRECU = %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6821.0 *** SYSTEM FATAL MESSAGE 6821 (SBSYM6)

THE LIST IS TOO LONG AT RECORD %1. THE OVERLAP IS %2 WORDS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6822.0 *** SYSTEM FATAL MESSAGE 6822 (SBSYM5)

EMPTY DIAGONAL BLOCK IN ROW %1.

6823.0 *** SYSTEM FATAL MESSAGE 6823 (SBMEM)

INSUFFICIENT MEMORY IN SYMBOLIC PHASE OF ITERATIVE SOLVER.

User action: INCREASE MEMORY BY AT LEAST %1 K WORDS.

6824.0 *** USER WARNING MESSAGE 6824 (SITDRV)

Main Index
 734 MSC Nastran Error Messeges
Errors 6000 - 6999

REDUCED INCOMPLETE CHOLESKY (RIC) PRECONDITIONING FOR MODELS WITH

MULTI-POINT CONSTRAINTS WAS
REQUESTED FOR THE ITERATIVE SOLVER.

User action: FOR FASTER CONVERGENCE INCLUDE THE ITRICA.V69 ALTER FROM THE
SSSALTER LIBRARY.

6825.0 *** USER FATAL MESSAGE 6825 (DPD6)

A NON-ACOUSTIC GRID POINT (ID = %1) HAS BEEN SPECIFIED AS PART OF EXCITATION
ID %2
REFERENCED ON AN ACSRCE ENTRY.

6826.0 *** USER FATAL MESSAGE 6826 (PLOD4D)

ELEMENT ID = %1 CID =%2 N1, N2, N3 =%3
LOAD DIRECTION VECTOR WHEN TRANSFORMED TO BASIC COORDINATES AT A
GAUSS POINT HAS A ZERO LENGTH.

6827.0 *** USER FATAL MESSAGE 6827 (TAFEST)

ELEMENT WITH ID = %1,HAS A GRID POINT OPPOSITE TO THOSE OF A FACE RECEIV-
ING A PRESSURE LOAD,
WHICH IS EVIDENTLY IN THE SAME PLANE AS THIS FACE.

6828.0 *** USER WARNING MESSAGE 6828 (ETETD)

THE FACES OF CTETRA ELEMENT ID=%1 ARE INTERSECTING BETWEEN THE ELE-
MENT'S EDGES DUE TO BAD MIDSIDE NODE
LOCATIONS.

User action: CORRECT THE ELEMENT'S GEOMETRY IF HIGH GRADIENTS ARE EXPECTED.

User information: JACOBIAN AT A GRID ID=%2 IS NEGATIVE.

6829.0 *** SYSTEM WARNING MESSAGE 6829 (UDSFB)

UNSYMMETRIC FACTOR TRAILER INFORMATION IS INCORRECT. THIS MAY LEAD TO
POOR PERFORMANCE
IN THE MCE1 MODULE

6830.0 *** SYSTEM FATAL MESSAGE 6830 (%1)

Main Index
 MSC Nastran Error Messeges 735
Errors 6000 - 6999

THE FIRST INPUT MATRIX IS NOT SQUARE.

6831.0 *** SYSTEMS FATAL MESSAGE 6831

INTERNAL LOGIC ERROR. INVALID VARIABLE STORE CODE SUPPLIED

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: LCODE VALUE = %1

6831.1 *** SYSTEMS FATAL MESSAGE 6831 (XQALVL)

INTERNAL LOGIC ERROR. INVALID VARIABLE LOAD CODE SUPPLIED

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: LCODE VALUE = %1

6831.2 *** SYSTEMS FATAL MESSAGE 6831 (XQAERR)

INTERNAL LOGIC ERROR. INVALID INTERNAL ERROR %1 NUMBER SUPPLIED

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: %2 VALUE = %3

6832.0 *** SYSTEM INFORMATION MESSAGE 6832 (DBFBS)

LOCAL PARAMETERS AND TIMINGS FOR THE DISTRIBUTED PARALLEL FBS
LOCAL MEMORY AVAILABLE =%1 K WORDS LOCAL MEMORY USED =%2 K WORDS
NUMBER OF GIVEN RHS(S) =%3 NUMBER OF SOLVED RHS(S) =%4
NUMBER OF PROCESSORS =%5
TREE SCAN CPU TIME =%6 SECONDS TREE SCAN ELAPSED TIME =%7 SECONDS
SCAT. RHS CPU TIME =%8 SECONDS SCAT. RHS ELAPSED TIME =%9 SECONDS
FORWARD PASS CPU TIME =%10 SECONDS FORWARD PASS ELAPSED TIME =%11 SEC-
ONDS
BACKWARD PASS CPU TIME =%12 SECONDS BACKWD. PASS ELAPSED TIME =%13 SEC-
ONDS
COLL. PHASE CPU TIME =%14 SECONDS COLL. PHASE ELAPSED TIME =%15 SECONDS
TOTAL CPU TIME =%16 SECONDS TOTAL ELAPSED TIME =%17 SECONDS

Main Index
 736 MSC Nastran Error Messeges
Errors 6000 - 6999

6833.0 *** USER INFORMATION MESSAGE 6833

THE DATABLOCK %1/%2, MONPNT LABELED (%3) CONTAINING REQUESTED NDDL
ITEM %4 %5 WAS NOT INCLUDED.
THIS MONPNT DOES NOT CONTAIN REQUESTED NDDL ITEM OR
THIS MONPNT DUPLICATES THE REQUEST OF A DIFFERENT LABELED MONPNT

User information: THIS MONPNT WILL NOT BE INCLUDED

User action: MODIFY THE MONPNT REQUEST TO CONFORM TO THE NDDL DESCRIP-
TION OR REMOVE IT.

6834.0 *** USER INFORMATION MESSAGE 6834

THE MONPNT LABELED (%1) DOES NOT CONTAIN REQUESTED NDDL ITEM %2 %3 %4.

User information: THIS MONPNT WILL NOT BE INCLUDED

User action: MODIFY THE MONPNT REQUEST TO CONFORM TO THE NDDL DESCRIP-
TION

6835.0 *** SYSTEM WARNING MESSAGE 6835 (ILMP2)

INPUT DATA BLOCK %1 FILE %2 IS NOT IN SORT2 FORMAT.

User information: MONPNT2 PROCESSING WILL BE SKIPPED FOR THIS DATABLOCK

6836.0 *** SYSTEM WARNING MESSAGE 6836 (ILMPGPF)

INPUT DATA BLOCK %1 FILE %2 IS NOT AN INDEXED GRID POINT FORCE (TABLE CODE
19)

User information: MONPNT3 PROCESSING WILL BE SKIPPED.

Programmer action: USE OGF TYPE DATABLOCK INDEXED WITH OFPINDX MODULE.

6837.0 *** SYSTEM WARNING MESSAGE 3001 (MASSCMB)

Main Index
 MSC Nastran Error Messeges 737
Errors 6000 - 6999

UNABLE TO FIND DATABLOCK FAMILY MEMBER %1 = %2 REFERENCED BY MASSSET =

%3

User information:
1. MASS ID IS INCORRECT OR
2. QUALIFIER NAME ON MASSCOMB MODULE IS INCORRECT OR
3. DBVIEW DMAP STATEMENT IS INCORRECT

6838.0 *** SYSTEM FATAL MESSAGE 6838 (ILMPGPF)

UNABLE TO READ GRID POINT FORCE DATA

User information: UNABLE TO DO AN INDEXED READ OF FILE. CHECK FILE

Programmer information:
SUBINDEX %1
GRID %2
RETURN CODE %3
LOCATION %4

6839.0 *** USER FATAL MESSAGE 6839 (PREMAT)

THE SLOPE OF THE FIRST LINE ON THE TABLES1 BULK DATA ENTRY ID = %1 IS NOT
EQUAL TO THE VALUE OF THE E
(ELASTICITY MODULUS) ON THE MAT1 BULK DATA ENTRY ID = %2 WHEN THE TYPE OF
MATERIAL NONLINEARITY IS PLASTIC.

6840.0 *** USER FATAL MESSAGE 6840 (PREMAT)

THE SECOND POINT (X2,Y2) SPECIFIED ON THE TABLES1 BULK DATA ENTRY ID = %1 IS
NOT AT THE INITAIL YIELD
POINT (LIMIT1) ON THE MATS1 BULK DATA ENTRY ID = %2 WHEN THE TYPE OF MATE-
RIAL NONLINEARITY IS PLASTIC.

6840.1 *** USER FATAL MESSAGE 6840 (PREMAT)

THE MATS1 ID = %1 MAY NOT REFERENCE THE TABLEST ID = %2 WHEN THE TYPE OF
MATERIAL NONLINEARITY IS PLASTIC.

6841.0 *** USER WARNING MESSAGE 6841 (A?)

Main Index
 738 MSC Nastran Error Messeges
Errors 6000 - 6999

BOTH AERODYNAMIC AND STRUCTURAL MONITOR POINT TYPES WERE FOUND ON

MONGRP ENTRY %1.

User information: STRUCTURAL AND AERODYNAMIC MONITOR POINT TYPES CANNOT

BE COMBINED ON A SINGLE MONGRP ENTRY.

6842.0 *** USER WARNING MESSAGE 6842 (A?)

THERE ARE NO VALID MONITOR POINT ENTRIES REFERENCED ON MONGRP ENTRY
%1

6842.1 *** USER WARNING MESSAGE 6842 (A?)

THERE ARE NO VALID MONITOR POINT ENTRIES REFERENCED ON %1 MONSUM
ENTRY: %2.

6843.0 *** USER WARNING MESSAGE 6843 (A?)

CLASS = %1, SPECIFIED ON MONGRP ENTRY %2 IS INVALID OR MISSPELLED.

User information: VALID CLASS TYPES ARE: AMONPNT1, AMONDSP1, SMONPNT1, SMOND-
SP1, MONPNT2, OR MONPNT3

6843.1 *** USER WARNING MESSAGE 6843 (A?)

CLASS = %1, SPECIFIED ON MONSUM ENTRY %2 IS INVALID OR MISSPELLED.

User information: VALID CLASS TYPES ARE: AMONPNT1, AMONDSP1, SMONPNT1, SMOND-
SP1, OR MONPNT3

6843.2 *** USER FATAL MESSAGE 6843 (A?)

MONSUM = %1 REFERENCES MONPNT3 %2 THAT HAS A PARTIAL EXCLUSION FLAG.
THIS IS NOT SUPPORTED ON THE MONSUM.

6843.3 *** USER WARNING MESSAGE 6843 (A?)

CLASS = %1, SPECIFIED ON MONSUM1 ENTRY %2 IS INVALID OR MISSPELLED.

User information: VALID CLASS TYPES ARE: AMONPNT1, SMONPNT1 OR MONPNT3

6843.4 *** USER FATAL MESSAGE 6843 (A?)

Main Index
 MSC Nastran Error Messeges 739
Errors 6000 - 6999

MONSUM1 = %1 REFERENCES MONPNT3 %2 THAT HAS A PARTIAL EXCLUSION FLAG.

THIS IS NOT SUPPORTED ON THE MONSUM.

6844.0 *** USER WARNING MESSAGE 6844 (ILMPGPF)

MONPNT %1 - SET1 BULK DATA ENTRY NO. %2 REFERENCES UNDEFINED GRID ID %3.

User information: THIS GRID ID WILL BE IGNORED.

6845.0 *** USER FATAL MESSAGE 6845 (CR8MON)

MONPNT3 %1 HAS AN EXCLUSION FLAG WITH 'C' OPTION.
THIS OPTION IS SUPPORTED IN SOL 400 ONLY.

6846.0 *** USER WARNING MESSAGE 6846 (MNPNTDR)

MONPNT3 PROCESSING WILL BE SKIPPED BECAUSE THERE ARE NO GPFORCE RESULTS.

6851.0 *** SYSTEM FATAL MESSAGE 6851 (MAKEBULK)

DATABLOCK %1 DOES NOT HAVE A PATH. GPTHPTR RETURNS ERROR = %2.

User information: THE OUTPUT DATABLOCK NEEDS TO BE A NDDL DATABLOCK WITH

PATH %3.

6851.1 *** SYSTEM FATAL MESSAGE 6851 (MAKEBULK)

NDDL DATABLOCK %1 HAS THE FOLLOWING PATH %2.

User information: THE OUTPUT DATABLOCK NEEDS TO BE A NDDL DATABLOCK WITH

PATH %3.

6851.2 *** SYSTEM FATAL MESSAGE 6851 (MAKEBULK)

DDL DATABLOCK %1 WITH PATH %2 HAS LESS OR MORE QUALIFIERS THAN THE %3
DATABLOCK CONTAINS.

User information: %4 DATABLOCK CONTAINS DATA FOR PATH %5.

6852.0 *** SYSTEM FATAL MESSAGE 6852 (MAKEBULK)

Main Index
 740 MSC Nastran Error Messeges
Errors 6000 - 6999

%1 IS NOT A %2 QUALIFIER.

User information: THE OUTPUT DATABLOCK NEEDS TO BE A NDDL DATABLOCK WITH

PATH %3.

6853.0 *** SYSTEM FATAL MESSAGE 6853 (MAKEBULK)

THE DDL DATABLOCK %1 WITH PATH POINTER %2 IS NOT VALID. FNDPTH RETURNS
ERROR = %3.

6853.1 *** SYSTEM FATAL MESSAGE 6853 (MAKEBULK)

THE DDL DATABLOCK %1 WITH PATH %2 IS NOT VALID. GPTPQUA RETURNS ERROR =
%3.

6853.2 *** SYSTEM FATAL MESSAGE 6853 (MAKEBULK)

THE DDL DATABLOCK %1 WITH PATH %2 IS NOT VALID. DBPTPQU RETURNS ERROR =
%3.

6853.3 *** SYSTEM FATAL MESSAGE 6853 (MAKEBULK)

THERE ARE MORE THAN %1 QUALIFIERS ON DDL DATABLOCK %2 WITH PATH %3.

User information: THERE SHOULD BE %4 QUALIFIERS ON PATH %5 TO MATCH THE DATA

ON DATABLOCK %6.`

6854.0 *** SYSTEM FATAL MESSAGE 6854 (MAKEBULK)

%1 FILE %2 IS NOT A IFPDB TYPED DATABLOCK.

User information: THE %3 FILE MUST BE A IFPDB TYPE DATABLOCK.

6855.0 *** SYSTEM FATAL MESSAGE 6855 (MAKEBULK)

THE INPUT KEY = %1 IS NOT FOUND WITHIN THE %2 DATABLOCK.

User information: VALID KEYS ARE FROM %3 TO %4 ON THE %5 DATABLOCK.

6855.1 *** SYSTEM FATAL MESSAGE 6855 (MAKEBULK)

Main Index
 MSC Nastran Error Messeges 741
Errors 6000 - 6999

NO DATA WERE READ ON THE %1 DATABLOCK.

User information: THE %2 DATABLOCK IS CREATED BY THE NEWIFP MODULE AND CON-
TAINS %3 PATH INSTANCES DATA.

6856.0 *** SYSTEM FATAL MESSAGE 6856 (MAKEBULK)

MODULE %1 IS NOT A VALID OPTION.

User information: THE VALID MODULE OPTION IS %2.

6857.0 *** USER FATAL MESSAGE 6857 (SEPMC1)

GRID or SPOINT id=%1 is defined more than once for superelement %2 on an SECONCT Bulk Data
entry which connects
superelements %2 and %3.

6889.0 *** SYSTEM INFORMATION MESSAGE 6889 (PNPERF)

RESULTS OF THE DISTRIBUTED PARALLEL METHOD PERFORMANCE TESTS
REQUESTED BY NASTRAN SYSTEM(166)=1024 FOLLOW.

6890.0 *** SYSTEM INFORMATION MESSAGE 6890 (PDDRV)

ADDITIONAL DIAGNOSTIC INFORMATION FOR DISTRIBUTED PARALLEL SPARSE
DECOMPOSITION REQUESTED BY NASTRAN SYSTEM(166)=%1.

6891.0 *** SYSTEM FATAL MESSAGE 6891 (SITDR3)

ILLEGAL VALUE FOR THE REGULARIZATION PARAMETER: %1.

User action: SYSTEM(241) ON THE NASTRAN ENTRY NEEDS TO HAVE ONE OF THE FOL-
LOWING VALUES:
0, [-1050,-1009] OR [1009,1050]. PLEASE MODIFY THE DATA DECK.

6892.0 *** USER FATAL MESSAGE 6892 (SEPMEP)

Main Index
 742 MSC Nastran Error Messeges
Errors 6000 - 6999

RSSCON ENTRY %1 REFERENCES ELEMENTS SPECIFIED IN TWO DIFFERENT SUPERELE-

MENTS.
ELEMENT %2 IS DEFINED IN SUPERELEMENT %3 AND ELEMENT %4
IN SUPERELEMENT %5.

User action: SPECIFY AN SEELT ENTRY TO PLACE ELEMENTS IN A SINGLE SUPERELE-

MENT.

6893.0 *** USER FATAL MESSAGE 6893 (SEPPGD)

IN THE PARTITIONED SUPERELEMENT (SUPER=%1) BULK DATA SECTION GRID POINT
ID=%2 IS REFERENCED ON A
RSSCON ID=%3 AND ALSO ON A %4 ENTRY. THE GRID POINT WILL HAVE TO BE MOVED
TO SATISFY RIGID BODY REQUIREMENTS.

User action: REPLACE THE CORD1_ ENTRY WITH A CORD2_ ENTRY OR

CREATE A COINCIDENT GRID ENTRY AND REFERENCE ITS ID ON THE CORD1_ ENTRY.

6893.1 *** USER FATAL MESSAGE 6893 (SEPPGD)

IN THE MAIN BULK DATA SECTION GRID POINT ID=%1 IS REFERENCED ON A
RSSCON ID=%2 AND ALSO ON A %3 ENTRY. THE GRID POINT WILL HAVE TO BE MOVED
TO SATISFY RIGID BODY REQUIREMENTS.

User action: REPLACE THE CORD1_ ENTRY WITH A CORD2_ ENTRY OR

CREATE A COINCIDENT GRID ENTRY AND REFERENCE ITS ID ON THE CORD1_ ENTRY.

6893.2 *** USER FATAL MESSAGE 6893 (SEPPGD)

IN THE PARTITIONED SUPERELEMENT (SUPER=%1) BULK DATA SECTION GRID POINT
ID=%2 IS REFERENCED ON A
RSSCON ID=%3 AND ALSO ON A %4 ENTRY. THE GRID POINT WILL HAVE TO BE MOVED
TO SATISFY RIGID BODY REQUIREMENTS.

User action: CREATE A COINCIDENT POINT ENTRY AND REFERENCE ITS ID ON THE %5
ENTRY.

6893.3 *** USER FATAL MESSAGE 6893 (SEPPGD)

Main Index
 MSC Nastran Error Messeges 743
Errors 6000 - 6999

IN THE MAIN BULK DATA SECTION GRID POINT ID=%1 IS REFERENCED ON A

RSSCON ID=%2 AND ALSO ON A %3 ENTRY. THE GRID POINT WILL HAVE TO BE MOVED
TO SATISFY RIGID BODY REQUIREMENTS.

User action: CREATE A COINCIDENT POINT ENTRY AND REFERENCE ITS ID ON THE %4
ENTRY.

6894.0 *** USER FATAL MESSAGE 6894 (SEPEXT)

FOR EXTERNAL SUPERELEMENT ID=%1, SCALAR POINT ID=%2 HAS AN ILLEGAL COMPO-
NENT DESIGNATED ON THE
EXTRN BULK DATA ENTRY.

6895.0 *** USER FATAL MESSAGE 6895 (SEPEXT)

GRID OR SCALAR POINT ID=%1 REFERENCED ON THE EXTRN BULK DATA ENTRY FOR
EXTERNAL SUPERELEMENT ID=%2
IS NOT DEFINED BY A GRID OR SPOINT BULK DATA ENTRY.

6896.0 *** USER FATAL MESSAGE 6896 (SEPEXT)

THERE IS NO EXTRN BULK DATA ENTRY SPECIFIED FOR EXTERNAL SUPERELEMENT %1.

6902.0 *** SYSTEM INFORMATION MESSAGE 6902 (SQFREQ)

DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE
NUMBER OF FREQUENCY DOMAINS = %1
NUMBER OF FREQUENCIES ON LOCAL PROCESSOR (ID=%2) = %3

6902.1 *** SYSTEM INFORMATION MESSAGE 6902 (DPERFM)

PERFORMANCE SUMMARY TABLE FOR DISTRIBUTED MEMORY FREQUENCY RESPONSE
NUMBER OF FREQUENCY DOMAINS = %1
NUMBER OF FREQUENCIES = %2
PROCESSOR # FREQ. CPU (SEC) ELAPSED (SEC)

6903.0 *** SYSTEM FATAL MESSAGE 6903 (SEDR)

MIRROR IMAGES ARE NOT SUPPORTED IN P-ELEMENT ANALYSIS.

6904.0 *** SYSTEM FATAL MESSAGE 6904 (SEP4)

LOGIC ERROR%1

Main Index
 744 MSC Nastran Error Messeges
Errors 6000 - 6999

6905.0 *** SYSTEM FATAL MESSAGE 6905 (SEMA)

ALL UPSTREAM SUPERELEMENTS HAVE BEEN EXCLUDED FROM ASSEMBLY IN
SUPERELEMENT %1

6907.0 *** SYSTEM WARNING MESSAGE 6907 (SEP4)

CASECC REFERENCES UNDEFINED SUPERELEMENT OR MODULE %1.
RECORD IS IGNORED.

6907.1 *** USER WARNING MESSAGE 6907 (SEP4)

%1 REQUEST REFERENCES UNDEFINED SUPERELEMENT OR MODULE %2

6907.2 *** USER FATAL MESSAGE 6907 (SEP3)

SE-TYPE COMMAND (SEALL,SEMG,etc..) REQUEST REFERENCES UNDEFINED SUPERELE-
MENTS OR MODULES.

User action: CHECK THE SE-TYPE COMMAND AND REFERENCED SET COMMANDS.

6908.0 *** SYSTEM INFORMATION MESSAGE 6908 (FREQ)

DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE IS DISABLED BECAUSE ZERO
PROCESSORS WERE SELECTED
(WITH SYSTEM(231)=0). SOLUTION WILL PROCEED WITH THE SEQUENTIAL SOLVER.

6908.1 *** SYSTEM INFORMATION MESSAGE 6908 (FREQ)

DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE IS DISABLED BECAUSE FRE-
QUENCY DEPENDENT MATERIALS
ARE PRESENT. SOLUTION WILL PROCEED WITH THE SEQUENTIAL SOLVER.

6908.2 *** SYSTEM INFORMATION MESSAGE 6908 (FREQ)

DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE IS DISABLED BECAUSE THE
ITERATIVE SOLVER IS SELECTED
(WITH SYSTEM(216)=1). SOLUTION WILL PROCEED WITH THE SEQUENTIAL SOLVER.

6908.3 *** SYSTEM WARNING MESSAGE 6908 (PNNAME)

CANNOT DETERMINE THE PROCESSOR NAME

6908.4 *** USER INFORMATION MESSAGE 6908 (FREQ)

Main Index
 MSC Nastran Error Messeges 745
Errors 6000 - 6999

DISTRIBUTED MEMORY PARALLEL FREQUENCY RESPONSE REQUIRES NUMDOM (NUM-

BER OF FREQUENCY DOMAINS) TO BE EQUAL TO THE
NUMBER OF PROCESSORS. HOWEVER, THIS RUN SPECIFIES NUMDOM = %1, BUT THE
NUMBER OF PROCESSORS IS EQUAL TO %2.

User information: the program will use a value of %2 for NUMDOM to create the parallel frequency
domains.

6909.0 *** USER INFORMATION MESSAGE 6909 (APD0)

THE VALUES SPECIFIED FOR REFC ON THE AERO AND AEROS BULK DATA ENTRIES ARE
DIFFERENT.

6910.0 *** USER FATAL MESSAGE 6910 (FA1)

A VELOCITY OF ZERO IS SPECIFIED ON FLFACT BULK DATA ENTRY ID=%1 WHICH IS
REFERENCED BY A FLUTTER
ENTRY THAT SPECIFIES THE PK METHOD.

6911.0 *** SYSTEM WARNING MESSAGE 6911 (QCBFIN)

THE DBVIEW HAS YIELDED MORE THAN ONE DATA BLOCK %1.
THE PROGRAM WILL SELECT THE "FIRST" DATA BLOCK FOUND.

Programmer action: TO FIND THE DUPLICATES, SPECIFY THE WHERE CLAUSE FROM THE
DBVIEW STATEMENT ON THE DBDICT STATEMENT
AND THEN MODIFY THE WHERE CLAUSE ON THE DBVIEW STATEMENT TO REMOVE
THE DUPLICATES.

Programmer information: DATA BLOCK 1: FISTNO =%2 PVAPTR = %3

DATA BLOCK 2: FISTNO =%4 PVAPTR = %5

6912.0 *** SYSTEM FATAL MESSAGE 6912 (SEDR)

Main Index
 746 MSC Nastran Error Messeges
Errors 6000 - 6999

THE BASIC GRID POINT DEFINITION TABLE NAMED %1 AND THE DISPLACEMENT
MATRIX NAMED %2
FOR SUPERELEMENT OR MODULE %3 ARE INCONSISTENT.

User action: IF THIS IS AN EXTERNAL SUPERELEMENT OR MODULE DATA RECOVERY,

ENSURE THAT THE BGPDTS TABLE
AND NOT THE EQEXINS TABLE IS DBLOCATE'D.

Programmer information: THE NUMBER OF DEGREES OF FREEDOM IN THE BASIC GRID

POINT DEFINITION TABLE IS %4.
THE NUMBER OF DEGREES OF FREEDOM IN THE DISPLACEMENT MATRIX IS %5.

6912.1 *** SYSTEM FATAL MESSAGE 6912 (EXTLDD)

THE CURRENT BASIC GRID POINT DEFINITION TABLE NAMED %1 AND THE IMPORTED
TABLE NAMED %2 FOR
IMPORTED %3 ID %4 ARE INCONSISTENT.

Programmer information: THE NUMBER OF DEGREES OF FREEDOM IN THE CURRENT

BASIC GRID POINT DEFINITION TABLE IS %5.
THE NUMBER OF DEGREES OF FREEDOM IN THE IMPORTED BASIC GRID POINT DEFI-
NITION TABLE IS %6.

6912.2 *** USER FATAL MESSAGE (MKFCMT)

THE BASIC GRID POINT DEFINITION TABLE (%1) AND THE %2 (%3) ARE INCONSISTENT.

Programmer information: THE %4 OF THE BASIC GRID POINT DEFINITION TABLE IS %5.
THE %6 OF THE %7 IS %8.

6913.0 *** SYSTEM FATAL MESSAGE 6913 (OUTPX2)

INDEXED MATRIX %1 COLUMN FILE (%2) IS CORRUPTED AT THE END OF THE FILE.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

6913.1 *** SYSTEM FATAL MESSAGE 6913 (OUTPX2)

OP2 file unit number %1 exceeds the limit of %2

User action: change unit number

Main Index
 MSC Nastran Error Messeges 747
Errors 6000 - 6999

6914.0 *** USER WARNING MESSAGE 6914 (RAND5A / RAND8 / RAND8A)

RANDPS ENTRY %1 REFERENCES UNDEFINED SUBCASES

User information: NONE OF THE SUBCASES REFERENCED IN THE ABOVE RANDPS ENTRY
IS DEFINED.

User action: CORRECT THE SUBCASE COMMAND OR THE ABOVE RANDPS ENTRY.
IF THIS IS A SUPERELEMENT JOB, THEN ALL OF THE SUBCASES REFERENCED IN THE
ABOVE RANDPS ENTRY MUST PERTAIN TO THE CURRENT SUPERELEMENT.

6914.1 *** USER WARNING MESSAGE 6914 (RAND8)

THE XYPLOT REQUEST OF PSDF/AUTO OF %1 RESPONSE FOR GRID/ELEMENT ID %2 IS
IGNORED BECAUSE
RANDPS ENTRY %3 REFERENCES ONE OR MORE UNDEFINED SUBCASE IDS

User action: ENSURE THAT ALL OF THE SUBCASES REFERENCED BY THE ABOVE RANDPS
ENTRY ARE DEFINED.
IF THIS IS A SUPERELEMENT JOB, THEN ALL OF THE SUBCASES REFERENCED IN THE
ABOVE RANDPS ENTRY MUST PERTAIN TO THE CURRENT SUPERELEMENT.

6914.2 *** USER WARNING MESSAGE 6914 (RAND5)

ELEMENT TYPE %1 IS NOT SUPPORTED FOR RANDOM RESPONSE.

6914.3 *** USER WARNING MESSAGE 6914 (RAND5)

INVALID ITEM CODE %1 OF ELEMENT NO. %2 IS REQUESTED FOR RANDOM RESPONSE.

6914.4 *** USER WARNING MESSAGE 6914 (RAND7)

There is only one excitation frequency. The random data recovery is skipped.

User information: For the random data recovery, at least two excitation frequencies are required.

6915.0 *** USER FATAL MESSAGE 6915 (GP1C)

COORDINATE SYSTEM %1 IS DEFINED BY THREE COLLINEAR POINTS IN SUPERELE-
MENT OR MODULE %2

Main Index
 748 MSC Nastran Error Messeges
Errors 6000 - 6999

6916.0 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: BEND, ORDERING METHOD USED: AMF

6916.1 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: BEND, ORDERING METHOD USED: BEND

6916.2 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

UNABLE TO EXECUTE METIS REORDERING BECAUSE THE MATRIX DENSITY IS TOO
HIGH: %1 %.
DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD

6916.3 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: METIS

6916.4 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: METIS

6916.5 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

UNABLE TO EXECUTE METIS REORDERING BECAUSE THE MATRIX DENSITY IS TOO
HIGH: %1 %.
DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD

6916.6 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

UNABLE TO EXECUTE METIS REORDERING BECAUSE THE MATRIX DENSITY IS TOO
HIGH: %1 %.

DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD

6916.7 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: MMD, ORDERING METHOD USED: MMD

6916.8 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: BEND

6916.9 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

INCREASE MEMORY BY AT LEAST %1 WORDS TO ENABLE METIS.
DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD

Main Index
 MSC Nastran Error Messeges 749
Errors 6000 - 6999

6916.10 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

INCREASE MEMORY BY AT LEAST %1 WORDS TO ENABLE METIS.
DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD

6916.11 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD

6916.12 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD

6916.13 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

MALLOC FAILED INSIDE METIS. DECREASING THE MEMORY GIVEN TO THE JOB WILL
INCREASE THE MEMORY AVAILABLE FOR MALLOC.
DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD

6916.14 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

MALLOC FAILED INSIDE METIS. DECREASING THE MEMORY GIVEN TO THE JOB WILL
INCREASE THE MEMORY AVAILABLE FOR MALLOC.
DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD

6916.15 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

METIS ERROR.
DECOMP ORDERING METHOD CHOSEN: METIS, ORDERING METHOD USED: MMD

6916.16 *** SYSTEM INFORMATION MESSAGE 6916 (DFMSYN)

METIS ERROR.
DECOMP ORDERING METHOD CHOSEN: DEFAULT, ORDERING METHOD USED: MMD

6916.17 *** SYSTEM FATAL MESSAGE 6916 (DFMSYN)

Main Index
 750 MSC Nastran Error Messeges
Errors 6000 - 6999

MALLOC FAILED INSIDE EXTREME.

User action: DECREASE THE MEMORY GIVEN TO THE JOB IN ORDER TO INCREASE THE
MEMORY AVAILABLE FOR MALLOC OR
USE METIS OR GRID BASED MMD REORDERING by RE-SUBMITTING THE JOB WITH ONE
OF THE FOLLOWING
VALUES FOR SYSTEM(206):
SYSTEM(206)=1 (GRID BASED MMD)
SYSTEM(206)=8 (GRID BASED METIS) OR
SYSTEM(206)=9 (SELECTS BEST OF THE TWO ABOVE)

6917.0 *** USER FATAL MESSAGE 6917 (TAB)

FOR TABLEDi OR TABLEMi ENTRY ID = %1; AN X-VALUE = %2
CAUSES EXPONENTIAL EXTRAPOLATION OF Y-VALUE, WITH NUMERIC OVERFLOW.

User action: AMEND TABLE TO AVOID BALLOONING EXPONENTIAL EXTRAPOLATION

BEYOND TABLE LIMITS.

6918.0 *** SYSTEM FATAL MESSAGE 6918 (MATMOD)

FOR MATMOD OPTION %1 AN INVALID VALUE %2 IS SPECIFIED FOR THE TYPE (2ND
PARAMETER)
THE VALID VALUES ARE 1 OR 2 FOR REAL 3 OR 4 FOR COMPLEX AND 0 (DEFAULT) FOR
OPPOSITE TYPE THAN INPUT TYPE.

6918.1 *** SYSTEM FATAL MESSAGE 6918 (MATMOD)

FOR MATMOD OPTION%1 AN INVALID VALUE %2 IS SPECIFIED FOR THE PRECISION
(3RD PARAMETER)
THE VALID VALUES ARE 1 FOR SINGLE PRECISION 2 FOR DOUBLE PRECISION, AND 0
(DEFAULT) FOR MACHINE PRECISION.

6918.2 *** SYSTEM FATAL MESSAGE 6918 (MATMOD)

FOR MATMOD OPTION %1, AN INVALID VALUE %2 IS SPECIFIED FOR THE PRECISION
(4TH PARAMETER).

User information: THE VALID VALUES ARE POSITIVE OR NEGATIVE 1 OR 2 FOR REAL AND 3
OR 4 FOR COMPLEX.

Main Index
 MSC Nastran Error Messeges 751
Errors 6000 - 6999

6918.3 *** USER FATAL MESSAGE 6918 (MATMOD)

FOR MATMOD OPTION 36, SUB-OPTION VALUE %1 (PARAMETER #4) IS NOT A VALID
SUB-OPTION.

User information: VALID SUB-OPTIONS ARE 1, 2 AND 3.

6918.4 *** USER FATAL MESSAGE 6918 (MATMOD)

THE CASE CONTROL SET ID (%1) SPECIFIED FOR PARAMETER %2 IS NOT POSITIVE.

User information: THE SPECIFIED CASE CONTROL SET MUST BE DEFINED ABOVE THE
FIRST SUBCASE.

Programmer information: MATMOD OPTION 36, SUB-OPTION %3, PARAMETER #%4

6919.0 *** SYSTEM FATAL MESSAGE 6919 (MATMOD)

ILLEGAL VALUE %1 FOR OPTION (FIRST PARAMETER). IT MUST BE GREATER THAN
ZERO AND LESS THAN %2.

6919.1 *** SYSTEM FATAL MESSAGE 6919 (MATMOD)

ILLEGAL VALUE %1 FOR P12 (MODEL). IT MUST BE 'STRUCT' OR 'FLUID'.

6919.2 *** SYSTEM FATAL MESSAGE 6919 (MATMOD)

ILLEGAL VALUE %1 FOR P13 (ITEM).
VALID ITEMS: UPFACT, TIPSIZE, MINDOF, XFACT, XFACTX

6920.0 *** SYSTEM FATAL MESSAGE 6920 (MATMOD)

FOR MATMOD OPTION %1, THE COLUMN NUMBER %2 IS INVALID. IT MUST BE
GREATER THAN ZERO AND LESS THAN %3.

6920.1 *** SYSTEM FATAL MESSAGE 6920 (MATMOD)

FOR MATMOD OPTION %1, THE %2%3 NUMBER %4 IS INVALID.

User information: IT MUST BE GREATER THAN 0 AND LESS THAN %5.

6921.0 *** SYSTEM FATAL MESSAGE 6921 (MATMOD)

FOR MATMOD OPTION 3, THE DEGREE-OF-FREEDOM CODE %1 IS INVALID.

Main Index
 752 MSC Nastran Error Messeges
Errors 6000 - 6999

6922.0 *** SYSTEM FATAL MESSAGE 6922 (MATMOD)

FOR MATMOD OPTION%1, THE TYPE OF MATRIX %2 IS INVALID.

6923.0 *** SYSTEM WARNING MESSAGE 6923 (MODTRL)

ILLEGAL VALUE %1 IS SPECIFIED FOR PARAMETER %2 THE VALUE WILL BE IGNORED.

6924.0 *** SYSTEM FATAL MESSAGE 6924 (MODTRL)

AN ATTEMPT TO MODIFY THE TYPE AND/OR PRECISION OF MATRIX %1.

User action:
1. IN ORDER TO CHANGE THE PRECISION OF A MATRIX, USE ADD5. IF THE NEW PRECI-
SION DOES NOT MATCH THE MACHINE PRECISION
THEN SPECIFY PUTSYS(NEW PRECISION,55) BEFORE ADD5. FOR EXAMPLE,
A. SINGLE TO DOUBLE ON A DOUBLE-WORD MACHINE:
ADD5 SINGLE,,,,/DOUBLE $
B. DOUBLE TO SINGLE ON A DOUBLE-WORD MACHINE:
PUTSYS(1,55) $
ADD5 DOUBLE,,,,/SINGLE $
PUTSYS(2,55) $

6925.0 *** SYSTEM FATAL MESSAGE 6925 (MODTRL)

AN ATTEMPT TO MODIFY THE DENSITY OF MATRIX%1.

6926.0 *** SYSTEM WARNING MESSAGE 6926 (MTMD34)

ATTEMPT TO CONVERT %1 MATRIX %2 AND %3 INPUT MATRIX %4 INTO A %5 MATRIX.
INPUT MATRICES NEED TO BE THE SAME TYPE.

6927.0 *** SYSTEM FATAL MESSAGE 6927 (MTMD34)

ATTEMPT TO CONVERT REAL MATRIX %1 INTO A COMPLEX MATRIX.

User action: USE THE ADD OR ADD5 MODULE; FOR EXAMPLE: ADD %2,/%3//(0.0,1.0) $

6928.0 *** SYSTEM FATAL MESSAGE 6928 (MTMD34)

ATTEMPT TO CONVERT %1 %2 INPUT MATRIX %3 TO A %4 %5 MATRIX.
6929.0 *** SYSTEM INFORMATION MESSAGE 6929. (EMGPOM)

Main Index
 MSC Nastran Error Messeges 753
Errors 6000 - 6999

MATRIX DATA FOR DATA BLOCK %1 IS BEING COMPUTED FOR ELEMENT WITH ID=%2
HOWEVER WILL NOT BE OUTPUT AS THIS DATA BLOCK IS PURGED OR NOT
REQUESTED.

User action: CHECK FOR PARAM,CHECKOUT,YES ENTRY, IF IT EXISTS THEN REMOVE IT

OR SIMPLY REPLACE 'YES' WITH 'NO'

6930.0 *** SYSTEM FATAL MESSAGE 6930. (EMGPOM)

INCORRECT CALL MADE TO -EMGPOM- FOR ELEMENT ID = %1
FILE TYPE = %2 ERROR PATH LOC CODE = %3

6931.0 *** SYSTEM FATAL MESSAGE 6931. (EMGPOM)

CONGRUENCY IS IMPLIED FOR ELEMENT-ID = %1
HOWEVER THIS IS THE FIRST ELEMENT OF ITS TYPE FOR FILE-TYPE = %2

6932.0 *** SYSTEM FATAL MESSAGE 6932. (EMGPOM)

THE DEGREES OF FREEDOM OR THE OUTPUT FORMAT HAS CHANGED BETWEEN ELE-
MENT-IDS OF THE SAME TYPE FOR FILE TYPE = %1
ELEMENT-ID = %2 %3%4%5%6

6933.0 *** SYSTEM FATAL MESSAGE 6933. (EMGPOM)

ONLY E-MATRIX HAS BEEN SENT TO -EMGPOM- AND NO LOC-CODE POINTER EXISTS
TO MATRIX DATA. ELEMENT-ID = %1
FILE TYPE = %2

6934.0 *** SYSTEM FATAL MESSAGE 6934. (EMGPOM)

FOR ELEMENT ID = %1 AND FILE TYPE = %2
EMGPRO DETERMINES A DIFFERENT COUNT OF ACTIVE CONNECTION SILS THAN
DOES CALLER OF EMGPOM
EMGPRO COUNT = %3 CALLING ROUTINE COUNT = %4

6935.0 *** SYSTEM FATAL MESSAGE 6935. (EMGPOM)

ELEMENT-ID = %1 FILE TYPE = %2%3%4%5%6%7
INCONSISTENT NUMBER OF COLUMNS OR TERMS SENT BY ELEMENT ROUTINE FOR
PACKING OUT BY EMGPOM, OR INVALID
INFORM-OUFORM COMBINATION.

Main Index
 754 MSC Nastran Error Messeges
Errors 6000 - 6999

6936.0 *** SYSTEM FATAL MESSAGE 6936 (PARAML)

ILLEGAL VALUE OF, %1, SPECIFIED FOR THE SECOND PARAMETER. THE VALUE MUST
BE GREATER THAN -3.

6937.0 *** USER FATAL MESSAGE 6937. (MDCASE)

STATIC AEROELASTIC SUBCASES MUST PRECEDE ANY STATICS SUBCASE

User action:MOVE ANY SUBCASES WITH ANALYSIS=SAERO BEFORE SUBCASES

WITH ANALYSIS=STATICS IN CASE CONTROL

6938.0 *** SYSTEM WARNING MESSAGE 6938

SERIOUS BREAKDOWN IN BLOCK COMPLEX LANCZOS

User action: CHANGE SETTING OF EIGC BULK DATA ENTRY

6938.1 *** SYSTEM INFORMATION MESSAGE 6938

MILD BREAKDOWN IN BLOCK COMPLEX LANCZOS

6938.2 *** SYSTEM WARNING MESSAGE 6938

BREAKDOWN IN BLOCK LANCZOS METHOD

User action: ENABLE BLOCK AUGMENTATION

6938.3 *** SYSTEM WARNING MESSAGE 6938

MAXIMUM BLOCK SIZE HAS BEEN REACHED

6938.4 *** SYSTEM WARNING MESSAGE 6938

MAXIMUM BLOCK SIZE REACHED IN BLOCK LANCZOS

User action: INCREASE MAXIMUM BLOCK SIZE

6939.0 *** SYSTEM FATAL MESSAGE 6939

UNABLE TO READ EIGENVECTORS FROM SCRATCH FILE

User action: CLEAN UP DISK DEVICE

Main Index
 MSC Nastran Error Messeges 755
Errors 6000 - 6999

6939.1 *** SYSTEM FATAL MESSAGE 6939

UNABLE TO READ LANCZOS VECTORS FROM SCRATCH FILE

User action: CLEAN UP DISK DEVICE

6940.0 *** SYSTEM INFORMATION MESSAGE 6940

SPILL OCCURRED WHEN CALCULATING LANCZOS VECTORS. %1 OUT OF A TOTAL OF
%2 LANCZOS VECTORS HAVE BEEN STORED OUT OF CORE.

User action: TO PREVENT SPILL, INCREASE OPEN CORE SIZE BY AT LEAST %3 WORDS

6940.1 *** SYSTEM INFORMATION MESSAGE 6940

SPILL OCCURRED WHEN CALCULATING PHYSICAL EIGENVECTORS.

User action: TO PREVENT SPILL, INCREASE MAXIMUM BLOCK SIZE BY AT LEAST %1

6941.0 *** SYSTEM INFORMATION MESSAGE 6941

INVARIANT SUBSPACE DETECTED IN BLOCK LANCZOS

6942.0 *** SYSTEM WARNING MESSAGE 6942, (RAND5)

FOR SUBCASE ID = %1 FREQUENCY %2
AT POINT %3 DOF %4 THE DISPLACEMENT IS LARGE ENOUGH TO CAUSE NUMERIC
OVERFLOW IN RANDOM ANALYSIS.

User information: THIS DISPLACEMENT IS SET TO ZERO FOR THE PURPOSE OF CALCU-
LATING THE POWER SPECTRAL DENSITY.

User action: CHECK MODEL OR REMOVE ABOVE FREQUENCY.

6943.0 *** USER FATAL MESSAGE 6943 (IFP6)

THE MAT2 ID=%1, GENERATED BY A PCOMP ENTRY HAS THE SAME ID AS A USER SUP-
PLIED MAT2 ENTRY.

User information: CHANGE THE ID OF THE USER SUPPLIED MAT2 ENTRY.

6944.0 *** SYSTEM FATAL MESSAGE 6944. (MKSPL)

Main Index
 756 MSC Nastran Error Messeges
Errors 6000 - 6999

AELIST ENTRY ID = %1 THAT IS REFERENCED ON SPLINE%2 ENTRY ID=%3 DOES NOT

EXIST.

6944.1 *** USER FATAL MESSAGE 6944 (ADG)

AELIST ENTRY ID = %1 THAT IS REFERENCED ON AESURF ENTRY ID = %2 DOES NOT
EXIST.

6945.0 *** SYSTEM FATAL MESSAGE 6945. (APD0)

AERO ANALYSIS TYPE (AERTYP) PARAMETER HAS AN ILLEGAL VALUE: %1

User information: LEGAL AERO ANALYSIS TYPES (AERTYP) ARE %2, %3, %4.

6947.0 *** SYSTEM FATAL MESSAGE 6947. (FBSUB)

LOGIC ERROR 10.

6948.0 *** USER INFORMATION MESSAGE 6948 (SEP4)

Since there are no superelements, the SUPER=%1 Case Control command will be ignored.

6952.0 *** SYSTEM FATAL MESSAGE 6952. (FMSPUT)

HEADER TYPE %1 MAY NOT HAVE DATA RECORDS
USE HEADER TYPE %2 FOR SINGLE DATA RECORD
%3 FOR MULTIPLE DATA RECORDS

6953.0 *** SYSTEM FATAL MESSAGE 6953. (FMSPUT)

HEADER TYPE %1 IS INVALID
USE HEADER TYPE %2 FOR SINGLE DATA RECORD
%3 FOR MULTIPLE DATA RECORDS

6954.0 *** SYSTEM FATAL MESSAGE 6954. (FMSPUT)

MISSING %1 INPUT DATA RECORD(S) FOR PREVIOUS HEADER.

6955.0 *** SYSTEM FATAL MESSAGE 6955. (FMSPUT)

FOUND %1 EXTRA INPUT DATA RECORD(S) FOR PREVIOUS HEADER.

6959.0 *** SYSTEM FATAL MESSAGE 6959. (GCPD-1)

FOR ELEMENT-ID = %1 SIL = %2 CAN NOT BE FOUND IN LIST OF SILS OF DICTIONARY
ENTRY.

Main Index
 MSC Nastran Error Messeges 757
Errors 6000 - 6999

6959.1 *** SYSTEM FATAL MESSAGE 6959. (GCPD-2)

FOR ELEMENT-ID = %1 SIL = %2, THE FORM IN DICT MUST BE EQUAL 3, IF THE DOF OF
THE CONNECTING GRID IS NOT 3 OR 6.

6960.0 *** SYSTEM FATAL MESSAGE 6960.

OUTPUT FORM =%1 FOUND IN DICTIONARY HEADER IS CURRENTLY NOT ACCEPT-
ABLE FOR ELEMENT ID = %2

6961.0 *** SYSTEM FATAL MESSAGE 6961.

LOGIC ERROR AT LOC =%1 FOR ELEMENT ID =%2

6962.0 *** USER FATAL MESSAGE 6962, (MATGEN-3)

ILLEGAL VALUE FOR OPTION PARAMETER = %1

6962.1 *** USER FATAL MESSAGE 6962, (MATGEN-4)

ILLEGAL VALUE FOR PARAMETER %1 = %2

6963.0 *** USER WARNING MESSAGE 6963, (MATGEN-11)

UNABLE TO GENERATE NULL MATRIX OF A-SET SIZE SINCE A-SET IS EMPTY.

6964.0 *** USER WARNING MESSAGE 6964, (MATGEN-11)

ILLEGAL COMBINATION OF PARAMETER OPTION. P3 AND P4 MAY NOT BOTH BE ZERO.

6965.0 *** USER WARNING MESSAGE 6965, (MATGEN-11)

USET SET SELECTED BY PARAMETER P4 IS EMPTY. OUTPUT MATRIX PURGED.

6965.1 *** USER WARNING MESSAGE 6965, (MATGEN-11)

USET SET SELECTED BY PARAMETER P3 IS EMPTY. OUTPUT MATRIX PURGED.

6966.0 *** USER WARNING MESSAGE 6966, (MATGEN-11)

SET SPECIFIED BY P4 IS NOT A LEGITIMATE SUBSET OF THE SET SPECIFIED BY P3.
OUTPUT MATRIX PURGED.

6967.0 *** USER FATAL MESSAGE 6967, (MATMOD-17)

Main Index
 758 MSC Nastran Error Messeges
Errors 6000 - 6999

EITHER USET BIT POSITION OR PARTN SET MUST BE SPECIFIED WHEN USING MAT-
MOD OPTION 17.

6968.0 *** USER WARNING MESSAGE 6968, (MATMOD-17)

NO GRID OR SCALAR POINTS IN SELECTED SET. PARTITIONING VECTOR NULL.

6969.0 *** USER FATAL MESSAGE 6969, (MATMOD-17)

PARTN SET %1 HAS BEEN SELECTED BUT HAS NOT BEEN DEFINED.

6970.0 *** USER WARNING MESSAGE 6970, (MATMOD-17)

NO PARTN SET SELECTED AS INDICATED BY PARAMETER SETFLG. CHECKING USET BIT
PARAMETER.

6971.0 *** USER WARNING MESSAGE 6971, (MATMOD-14)

UNABLE TO USE RELATIVE FILTER ON MATRIX %1 BECAUSE ITS FORM IS NON-SQUARE.

6972.0 *** USER FATAL MESSAGE 6972. (MATMOD-26)

NO PROCESSING OF DATA BLOCK %1 WILL BE PERFORMED BECAUSE ITS DENSITY IS
ZERO.

6973.0 *** USER FATAL MESSAGE 6973 (ASGNCD)

THE NUMBER OF SUPPORTED DEGREES OF FREEDOM MINUS THE NUMBER OF FREE
AESTAT BULK DATA ENTRIES IS FOUR
OR GREATER.

User action: SPECIFY ADDITIONAL AESTAT ENTRIES OR FEWER SUPPORTED DEGREES OF

FREEDOM.

6974.0 *** USER FATAL MESSAGE 6974 (ASGNCD)

THE CONTROL SURFACES CANNOT PARTICIPATE IN THE REQUESTED TRIM TASK.

User information: THE NONLINEAR TRIM ALGORITHM HAS FOUND THAT THERE ARE
FREE CONTROL SURFACES,
BUT NO DEGREES OF FREEDOM FOR THEM TO CONTROL.

User action: SPECIFY FEWER AESTAT ENTRIES OR MORE SUPPORTED DEGREES OF FREE-
DOM.

Main Index
 MSC Nastran Error Messeges 759
Errors 6000 - 6999

6975.0 *** USER FATAL MESSAGE 6975 (ASGNCD)

A SUPPORTED DEGREE OF FREEDOM IS NOT AFFECTED BY ANY FREE TRIM VARIABLE

User information: AN EXAMPLE IS AN AIRPLANE THAT IS FREE TO ROLL WITH NO CON-

TROL SURFACE AFFECTING THE ROLL AXIS.

User action: ADD ADDITIONAL FREE VARIABLES OR REMOVE THE SUPPORTED DEGREE
OF FREEDOM.

6976.0 *** USER FATAL MESSAGE 6976 (ASGPRD)

CSSCHD BULK DATA ENTRY ID = %1 THAT IS REFERENCED BY THE CSSCHD CASE CON-
TROL COMMAND DOES NOT EXIST.

User action: PROVIDE THE REQUIRED CSSCHD BULK DATA ENTRY.

6977.0 *** USER FATAL MESSAGE 6977 (PRESCH)

THE DATA DEFINED ON THE AEFACT BULK DATA ENTRY ID = %1 ASSOCIATED WITH
CSSCHD ID = %2 AND
AESURF ID = %3 IS INCONSISTENT.

User information: THERE ARE %4 MACH NUMBERS SPECIFIED AND %5 ANGLES OF

ATTACK WITH THE REQUIREMENT.
THERE SHOULD BE %6 TERMS ON THE ASSOCIATED AEFACT ID = %7, BUT THERE ARE
%8 TERMS.

6978.0 *** SYSTEM FATAL MESSAGE 6978 (SB11RD)

RECORD LENGTH IS NOT ENOUGH TO STORE THE %1 BLOCK ROW OF PRECONDI-
TIONER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

6979.0 *** SYSTEM FATAL MESSAGE 9006 (SB53RD)

MAXIMUM PERMUTED BLOCK ROW LENGTH = %1 EXCEEDS THE RECORD LENGTH =
%2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 760 MSC Nastran Error Messeges
Errors 6000 - 6999

6980.0 *** SYSTEM FATAL MESSAGE 9007 (SB85RD)

LARGEST BLOCK ROW OF THE INITIAL MATRIX (%1 WORDS) EXCEEDS THE SPECIFIED
MAXIMUM RECORD LENGTH (%2 WORDS).

User action: PLEASE SET RECLEN=%3 (OR A HIGHER VALUE) ON THE ITER BULK DATA
ENTRY.

6980.1 *** SYSTEM FATAL MESSAGE 9008 (SB85RD)

LARGEST BLOCK ROW OF THE PRECONDITIONER (%1 WORDS) EXCEEDS THE SPECI-
FIED MAXIMUM RECORD LENGTH (%2 WORDS).

User action: PLEASE SET RECLEN=%3 (OR A HIGHER VALUE) ON THE ITER BULK DATA
ENTRY.

6981.0 *** USER FATAL MESSAGE 6981 (NBS1D)

BUSH1D ELEMENT ID = %1 REFERENCES UNDEFINED EQUATION ID = %2.

6982.0 *** SYSTEM FATAL MESSAGE 6982

LOGIC ERROR. THERE SEEMS TO BE MORE TERMS IN COLUMNS OF THE DATA MATRIX
THEN THE NUMBER OF EIGENVALUES =%1

6983.0 *** SYSTEM FATAL MESSAGE 6983 (DRMH3F)

PROGRAMMING ERROR; THE INPUT MAP TABLE HAS INCONSISTENT ELEMENT IDS
AND CONSTANTS
ELEMENT LIST: ELTYPE = %1 ID = %2
CONSTANT LIST: ELTYPE = %3 ID = %4

6984.0 *** SYSTEM FATAL MESSAGE 6984

INCORRECT NUMBER OF WORDS BEING REQUESTED FOR TRANSMISSION TO AND BY
PHASE-2 ROUTINE.
ELEMENT ID =%1, WORDS THIS CALL =%2, TOTAL=%3

6985.0 *** SYSTEM FATAL MESSAGE 6985

PREVIOUS ELEMENT-ID =%1
DID NOT REQUEST CORRECT NUMBER OF PHASE-1 OUTPUT WORDS.

Main Index
 MSC Nastran Error Messeges 761
Errors 6000 - 6999

6986.0 *** SYSTEM FATAL MESSAGE 6986

LOGIC ERROR. ELEMENT-ID =%1
INCORRECT NUMBER OF STRESS OR FORCE WORDS ARE BEING OUTPUT BY A PHASE-2
ELEMENT ROUTINE. SF CODE =%2

6987.0 *** SYSTEM FATAL MESSAGE 6987

EXECUTION CONTINUING HOWEVER ANY STRESS OR FORCE OUTPUT REQUESTS WILL
BE IGNORED.

6988.0 *** USER FATAL MESSAGE 6988 (MKSPL)

SPLINE %1 ENTRY ID = %2 REFERENCES A CAERO2 ENTRY ID = %3 WHICH IS NOT
ALLOWED.

User action: THIS TYPE OF SPLINE IS NOT APPROPRIATE FOR USE WITH SLENDER BODIES,
USE A LINEAR (BEAM) SPLINE.

6989.0 *** USER FATAL MESSAGE 6989 (ADGHMK)

BOX ID = %1, DEFINED ON AELIST ENTRY ID = %2 ON AESURF ENTRY ID = %3, DOES NOT
EXISTS.

6990.0 *** USER FATAL MESSAGE 6990 (ADGHMK)

DUPLICATE BOX ID = %1 FOUND ON CONTROL SURFACES 1 (AELIST ENTRY ID = %2) and
2 (AELIST ENTRY ID = %3)
ON AESURF ENTRY ID = %4.

User information: NO OVERLAPPING CAN OCCURRED ON TWO CONTROL SURFACES

DEFINED ON THE SAME AESURF ENTRY.

6991.0 *** SYSTEM WARNING MESSAGE 6991, (NORMM)

NORM MODULE HAS COMPUTED A MAX VALUE WHICH EXCEEDS THE SINGLE PRECI-
SION FORMAT.

User information: THE VALUE IS %1 THE THIRD OUTPUT PARAMETER IS SET TO 0.0E0.

User action: USE THE FIFTH PARAMETER TO OUTPUT THE PROPER VALUE.

Main Index
 762 MSC Nastran Error Messeges
Errors 6000 - 6999

6991.1 *** USER FATAL MESSAGE 6991 (JINTG)

JINTEG CARD MISSING IN CASE CONTROL JINTG PROCESSING TERMINATED.

6992.0 *** USER FATAL MESSAGE 6992

The input value for the 12th parameter in a call to MATMOD with option 50 is blank.

6992.1 *** USER FATAL MESSAGE 6992

The input value for the 12th parameter in a call to MATMOD with option 50 is invalid: %1.

6993.0 *** SYSTEM INFORMATION MESSAGE 6993 (ASGNLD/S)

CONTROL SURFACE LIMITS ARE EXCEEDED.

User information: CONSTRAINED OPTIMIZATION WILL BE PERFORMED.

6994.0 *** SYSTEM FATAL MESSAGE 6994.

SHAPE FUNCTION ROUTINE SHPTQD IS CALLED FOR UNKNOWN TYPE

6994.1 *** SYSTEM FATAL MESSAGE 6994.

LOGIC ERROR IE=%1
AREA MATRIX ROUTINE IS CALLED FOR %2

User information:
This indicates a logic error in the program.
Contact Hexagon Client Support.

6995.0 *** USER WARNING MESSAGE 6995,

DTI UPDATE DATA OUT OF RANGE.
%1 %2 %3

6996.0 ***USER WARNING MESSAGE 6996

DVAR BULK DATA ENTRY ID = %1 REQUESTED VIA SET2 CANNOT BE FOUND.

6996.1 ***USER WARNING MESSAGE 6996

DSCONS BULK DATA ENTRY ID = %1 REQUESTED VIA SET2 CANNOT BE FOUND.

6997.0 **** USER WARNING MESSAGE 6997

GRIDS %1 AND %2 ARE GENERATED INTERNALLY IN CRAC3D ELEMENT ID= %3

Main Index
 MSC Nastran Error Messeges 763
Errors 6000 - 6999

6998.0 *** SYSTEM FATAL MESSAGE 6998 (FMSFIO)

FORTRAN UNIT 2 USED FOR FMS IS NOT INITIALIZED.

6999.0 *** SYSTEM FATAL MESSAGE 6999 (FMSFIO)

FORTRAN UNIT %1 USED FOR FMS DOES NOT HAVE A CORRESPONDING VALUE IN
FORUNT ARRAY.

Main Index
 764 MSC Nastran Error Messeges
Errors 6000 - 6999

Main Index
 MSC Nastran Error Messages 765
Errors 7000 - 7999

Errors 7000 - 7999

7001.0 *** USER WARNING MESSAGE 7001 (DOPR1B)
FOR DESVAR ENTRY ID = %1 THE USER INITIAL VALUE = %2 WHILE THE COMPUTED
VALUE = %3
THE USER SUPPLIED VALUE ON THE DESVAR ENTRY IS OVERRIDDEN BY THE COM-
PUTED VALUE FROM THE DLINK ENTRY

7002.0 *** USER FATAL MESSAGE 7002 (DOPR1B)

NO DESVAR ENTRIES ARE SPECIFIED IN THE BULK DATA.

7002.1 *** USER FATAL MESSAGE 7002 (DOPR1B)

NO DESVAR ENTRIES ARE SPECIFIED IN THE BULK DATA.

7002.2 *** USER FATAL MESSAGE 7002 (IFP10F)

NO ELEMENTS ARE REFERENCED BY ANY TOMVAR PROPERTY IDs

7008.0 *** USER FATAL MESSAGE 7008 (DOPR1B)

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.

7009.0 *** USER FATAL MESSAGE 7009 (DOP1A1)

DRESP2 bulk data entry %1 DEFINES A BETA/MATCH RESPONSE but it is not referenced by a DES-
OBJ Case Control command.

User information: ONLY ONE DRESP2 THAT INVOKES FUNC = BETA OR MATCH IS
ALLOWED PER BULK DATA DECK AND IT MUST BE INVOKED BY THE DESOBJ CASE
CONTROL COMMAND

7009.1 *** USER FATAL MESSAGE 7009 (DOP1A1)

A DESGLB command references a BETA/MATCH DRESP2 entry = %1, which is not allowed.

User information: ONLY THE DESOBJ COMMAND CAN REFERENCE SUCH A ENTRY.

Main Index
 766 MSC Nastran Error Messages
Errors 7000 - 7999

7009.2 *** USER FATAL MESSAGE 7009 (DOP1A1)

A DESSUB command references a BETA/MATCH DRESP2 entry = %1, which is not allowed.

User information: ONLY THE DESOBJ COMMAND CAN REFERENCE SUCH A ENTRY.

7009.3 *** USER FATAL MESSAGE 7009 (DOP1A2)

MULTIPLE DRESP2 ENTRIES, INCLUDING DRESP2 ID %1 AND %2, INVOKE FUNC
= BETA OR MATCH. THIS IS NOT ALLOWED

User information: ONLY ONE DRESP2 WITH FUNC = BETA OR MATCH CAN BE PRESENT
IN A BULK DATA DECK AND IT MUST BE INVOKED BY THE DESOBJ CASE CONTROL
COMMAND.

7010.0 *** USER FATAL MESSAGE 7010 (IFS6P)

DRESP2 bulk data entry %1 DOES NOT REFERENCE DERSP1 ENTRies.

User information: This is NOT SUPPORTED FOR A %2 RESPONSE.

User action: REMOVE OFFENDING ENTRIES.

7010.1 *** USER FATAL MESSAGE 7010 (IFS6P)

DRESP2 bulk data entry %1 references %2 ENTRies.

User information: This is NOT SUPPORTED FOR A %3 RESPONSE.

User action: REMOVE OFFENDING ENTRIES.

7011.0 *** USER FATAL MESSAGE 7011 (DOPR1B)

DLINK ENTRY %1 REFERENCES DESVAR ENTRY %2 WHICH IS EITHER NOT DEFINED ON
A DESVAR BULK DATA ENTRY OR NOT SELECTED BY THE DESVAR CASE CONTROL
COMMAND.

7011.1 *** USER FATAL MESSAGE 7011 (DOPR1B)

Main Index
 MSC Nastran Error Messages 767
Errors 7000 - 7999

DLINK ENTRY %1 REFERENCES INDEPENDENT DESVAR ENTRY %2 WHICH IS ALSO

LISTED AS A DEPENDENT DESIGN VARIABLE ON ANOTHER DLINK ENTRY

User information: A DESIGN VARIABLE CANNOT BE BOTH DEPENDENT AND INDEPEN-

DENT

User action: ENSURE THAT EACH DESVAR IS EITHER INDEPENDENT OR DEPENDENT

BUT NOT BOTH

7011.2 *** USER FATAL MESSAGE 7011 (DR1XPA)

SEDLINK ENTRY %1 REFERENCES INDEPENDENT DESVAR ENTRY %2 OF PART SE %3
WHICH IS ALSO LISTED AS A DEPENDENT DESIGN VARIABLE ON ANOTHER SEDLINK
ENTRY

User information: A DESIGN VARIABLE CANNOT BE BOTH DEPENDENT AND INDEPEN-

DENT

User action: ENSURE THAT EACH DESVAR IS EITHER INDEPENDENT OR DEPENDENT

BUT NOT BOTH

7011.3 *** USER FATAL MESSAGE 7011 (DR1XPA)

SEDLINK ENTRY %1 REFERENCES DESVAR ENTRY %2 OF PART SE %3 AS DEPENDENT
WHICH IS ALSO LISTED AS A DEPENDENT DESIGN VARIABLE ON ANOTHER DLINK
ENTRY

User action: REMOVE THE DUPLICATE REFERENCE TO THE DESVAR ENTRY.

7011.4 *** USER FATAL MESSAGE 7011 (DR1XPA)

SEDLINK ENTRY %1 REFERENCES DESVAR ENTRY %2 OF PART SE %3 WHICH IS NOT
DEFINED ON A DESVAR BULK DATA ENTRY.

User action: ENSURE THE EXISTENCE OF DESVAR IN A PART SE

7011.5 *** USER FATAL MESSAGE 7011 (DR1XPA)

Main Index
 768 MSC Nastran Error Messages
Errors 7000 - 7999

SEDLINK ENTRY %1 REFERENCES INDEPENDENT DESVAR ENTRY %2 OF PART SE %3

WHICH IS ALSO LISTED AS A DEPENDENT DESIGN VARIABLE ON ANOTHER DLINK
ENTRY

User information: A DESIGN VARIABLE CANNOT BE BOTH DEPENDENT AND INDEPEN-

DENT

User action: ENSURE THAT EACH DESVAR IS EITHER INDEPENDENT OR DEPENDENT

BUT NOT BOTH

7011.6 *** USER FATAL MESSAGE 7011 (SDSAP)

DUPLICATION OF DRESP1 ID %1 FOUND IN PART SE %2

User information: DRESP1 WITH GLOBAL RESPONSE IN MAIN BULK IS SHARING AN ID

INDICATED WITH LOCAL DRESP1 IN A PART SE

User action: ENSURE DRESP1 ID OF GLOBAL RESPONSE, SUCH AS WEIGHT, VOLUME,

EIGN, CEIG, IS UNIQUE AMONG ALL DRESP1

7011.7 *** USER FATAL MESSAGE 7011 (SDSAPA)

DRESP1/2 ID %3 OF PART SE %2 REFERENCED ON SEDRSP2/3 %1 NOT FOUND LOCALLY

User action: ENSURE DRESP1/2 ID IS AVAILABLE LOCALLY IN REFERENCED PART SE

7012.0 *** USER FATAL MESSAGE (MKFRCMNT)

NO %1 RECORD WAS WRITTEN IN %2 DATABLOCK %3.

7013.0 ### SYSTEM FATAL MESSAGE (MKFM00D)

%1 %2 RECORD ENTRY DESCRIPTION HAS BEEN CHANGED IN THE NDDL.

7014.0 ### SYSTEM INFORMATION MESSAGE (MKFM00D)

%1 %2 RECORD ENTRY %3 IS %4.

7015.0 *** USER FATAL MESSAGE 7015 (DOPR1C)

THE FIELD DVID %1 ON %2 ENTRY ID = %3 IS NOT SELECTED BY THE DESVAR CASE
CONTROL COMMAND.

Main Index
 MSC Nastran Error Messages 769
Errors 7000 - 7999

7015.1 *** USER FATAL MESSAGE 7015 (DOPR1C)

THE FIELD DVID %1 ON %2 ENTRY ID = %3 IS NOT DEFINED ON A DESVAR BULK DATA
ENTRY.

7016.0 ### SYSTEM FATAL MESSAGE (MKFM00D)

%1 %2 %3 %4 %5

7017.0 ### USER FATAL MESSAGE (MKFM00D)

FOR LOAD COLUMN %1, THE %2 ON GRID ID %3
DOF %4, IS NOT IN THE %5-SET.

7018.0 ### USER FATAL MESSAGE (FBODYFLT)

THE %1 ENTRY NAME="%2" REFERENCED IN SUBCASE ID = %3 WAS NOT FOUND.

7018.1 ### USER FATAL MESSAGE (FBODYFLT)

THE %1 ENTRY NAME="%2" REFERENCED ON THE %3 ENTRY NAME="%4" WAS NOT
FOUND.

7018.2 *** USER FATAL MESSAGE 7018 (F6GD)

THE %1 BULK DATA ENTRY ID= %2 REFERENCED ON THE %3 ENTRY ID= %4 WAS NOT
FOUND.

7018.3 *** USER FATAL MESSAGE 7018 (MKCKBL)

THE %1 BULK DATA ENTRY ID= %2 REFERENCED ON THE %3 ENTRY WAS NOT FOUND.

7019.0 *** USER FATAL MESSAGE 7019 (DSFLTF)

RETAINED FLUTTER EIGENVALUE NO. %1 HAS A VALUE OF (0.0,0.0)

User information: IT IS IMPOSSIBLE TO DETERMINE THE SENSITIVITY OF A ZERO EIGEN-

VALUE

User action: DETERMINE THE CAUSE OF THIS ZERO EIGENVALUE AND EITHER REMOVE
THE CAUSE OR DO NOT SPECIFY THIS ROOT ON A DRESP1 ENTRY.

Main Index
 770 MSC Nastran Error Messages
Errors 7000 - 7999

7023.0 *** USER FATAL MESSAGE 7023 (DOPR3C)

THERE ARE %1 ENTRIES BUT NO DEQATN ENTRIES.
7028.0 *** USER FATAL MESSAGE 7028 (DOPR3C)
THE LABEL = %1 ON %2 ENTRY ID = %3 CANNOT BE FOUND ON the DTABLE ENTRY.

7028.1 *** USER FATAL MESSAGE 7028 (DOPR1Z)

THE LABEL = %1 ON %2 ENTRY ID =%3 CANNOT BE FOUND ON THE DTABLE ENTRY.

7028.2 *** USER FATAL MESSAGE 7028 (DOPR3C)

THE LABEL = %1 ON %2 ENTRY ID = %3 HAS INTEGER INPUT.

User information: INTEGER INPUT FOR LABEL OF DTABLE IS FOR MATCH FUNCTION OF
DRESP2 ONLY.

7028.3 *** USER FATAL MESSAGE 7028 (DOPR3C)

DRESP2 ENTRY ID = %1 HAS DIFFERENT NUMBER OF DTABLE CONSTANTS AND DRESP1
IDs FOR MATCH FUNCTION.

7028.4 *** USER FATAL MESSAGE 7028 (DOPR3C)

DRESP2 ENTRY ID = %1 HAS DNODE/DVxRELy/DRESP2 FLAG(s) INPUT FOR MATCH
FUNCTION.

7028.5 *** USER FATAL MESSAGE 7028 (DOPR3C)

DRESP2 ENTRY ID = %1 WITH MATCH FUNCTION HAS NON-Frequency or transient TYPE 1
RESPONSE ASSOCIATE WITH DTABLE with INTEGER INPUT.

7028.6 *** USER FATAL MESSAGE 7028 (DOPR3C)

DRESP2 ENTRY ID = %1 HAS DESVAR FLAG INPUT FOR MATCH(LS) FUNCTION.

7029.0 *** USER FATAL MESSAGE 7029 (DOPR3C)

THE LABEL = %1 OF PART SE %4 ON %2 ENTRY ID = %3 CANNOT BE FOUND ON the
DTABLE ENTRY.

7029.1 *** USER FATAL MESSAGE 7029 (DOPR3C)

ON %1 entry ID = %2, PART SE ID = %3 CANNOT BE FOUND.

7029.2 *** USER FATAL MESSAGE 7137 (DOPR3C)

Main Index
 MSC Nastran Error Messages 771
Errors 7000 - 7999

ON %1 entry ID = %2, DVID = %3 OF PART SE %4 IS EITHER NOT REFERENCED ON A

DESVAR BULK DATA ENTRY OR NOT SELECTED BY THE DESVAR CASE CONTROL
COMMAND.

7029.3 *** USER FATAL MESSAGE 7220 (DOPR3T)

%1 ENTRY ID = %2 SPECIFIES A DNODE GRID ID =%3 AND COMPONENT =%4 OF PART SE
%5 COMBINATION WHICH DOES NOT EXIST.

User action: MAKE SURE THE GRID AND COMPONENT ARE DEFINED IN THE ANALYSIS
MODEL.

7029.4 *** USER FATAL MESSAGE 7220 (DOPR3T)

ON %1 entry ID = %3, %2 ID = %4 DOES NOT REFERENCE AN EXISTING %2 ENTRY IN PART
SE %5.

7029.5 *** USER FATAL MESSAGE 7220 (DOPR3T)

SEDRSP2 entry ID = %1 REFERENCES DESVAR/DTABLE/DVxRELy OF PART SE %2 BUT NO
DRESPi.

User action: CREATE DUMMY DRESP1 FOR ALL PART SEs REFERENCED and INCLUDE IT ON
SEDRSP2

7029.6 *** USER FATAL MESSAGE 7029 (DOPR1A)

LABEL = %1 ON DTABLE/DTABLE2 IS FOUND TO HAVE DUPLICATES.

7052.0 *** USER FATAL MESSAGE 7052 (DOMPTC)

ILLEGAL PROPERTY TYPE %1 IS REFERENCED ON %2 ENTRY %3.

7052.1 *** USER FATAL MESSAGE 7052 (DOMPNTF)

%1 ENTRY %2 REFERENCES AN ILLEGAL COMBINATION OF PROPERTY TYPE %3 AND
PROPERTY NAME %4.

7052.2 *** USER FATAL MESSAGE 7052 (DOMPTC)

ILLEGAL PROPERTY TYPE %1 IS REFERENCED ON %2 ENTRY %3 WITH RYTPE=WMPID.

7053.0 *** USER FATAL MESSAGE 7053 (DVPCHK)

Main Index
 772 MSC Nastran Error Messages
Errors 7000 - 7999

DVPREL %1 ENTRY %2 WITH PTYPE= %3 REFERENCES A POSITIVE FID %4.

User action: REPLACE THE FID WITH A NEGATIVE NUMBER.

7053.1 *** USER FATAL MESSAGE 7053 (DVPCHK)

TOMVAR ENTRY %1 WITH PTYPE= %2 REFERENCES A POSITIVE FID %3.

User action: REPLACE THE FID WITH A NEGATIVE NUMBER.

7053.2 *** USER FATAL MESSAGE 7053 (IFP10)

TOMVAR ENTRY %1 INCLUDES DLINK DATA BUT THE PROPERTY TYPE IS NOT A
PCOMP.

User information: ONLY THE PCOMP PROPERTY TYPE IS SUPPORTED WHEN DLINK IS
USED ON A TOMVAR ENTRY.

7053.3 *** USER FATAL MESSAGE 7053 (IFP10)

TOMVAR ENTRY %1 REFERENCES PID = %2 AND HAS A DLINK TO TOMVAR ENTRY %3
WHICH REFERENCES PID = %4.

User information: THE TWO TOMVARS MUST REFEENCE DIFFERENT LAYERS OF THE
SAME PCOMP.

7053.4 *** USER FATAL MESSAGE 7053 (IFP10)

TOMVAR ENTRY %1 REFERENCES PNAME = %2 AND HAS A DLINK TO TOMVAR ENTRY
%3 WHICH ALSO REFERENCES PNAME = %4.

User information: THE PNAMES MUST BE UNIQUE FOR THE INDEPENDENT AND LINKED
TOMVARS.

7053.5 *** USER FATAL MESSAGE 7053 (IFP10)

TOMVAR ENTRY %1 HAS A DLINK WITH TID = %2. THERE IS NO TOMVAR WITH ID = %2.

7053.6 *** USER FATAL MESSAGE 7053 (IFP10)

DRESP1=COMP (COMPLIANCE) DOES NOT SUPPORT SUPERELEMENT

7053.7 *** USER FATAL MESSAGE 7053 (IFP10)

Main Index
 MSC Nastran Error Messages 773
Errors 7000 - 7999

TOPOLOGY OPTIMIZATION WITH STRESS CONSTRAINTS DOES NOT SUPPORT

SUPERELEMENT

7053.8 *** USER FATAL MESSAGE 7053 (IFP10A)

TOPVAR ENTRY ID = %1 WITH KEYWORD STRESS DOES NOT REFERENCE ANY PSOLID
OR PSHELL ENTRY.
OR THERE ARE OTHER TOPVAR ENTIRES THAT REFERENCE NON-PSOLID OR NON-
PSHELL ENTRIES

User information: STRESS BASED TOPOLOGY OPTIMIZATION SUPPORTS 3D SOLID AND

SHELL ELEMENTS ONLY

7053.9 *** USER FATAL MESSAGE 7053 (IFP10A)

TOPVAR ENTRY ID = %1 HAS DIFFERENT VON MISES STRESS LIMIT VS ANOTHER TOP-
VAR ENTRY.

User information: TOPOLOGY OPTIMIZATION MUST HAVE THE SAME VON MISES STRESS
LIMIT

7053.10 *** USER FATAL MESSAGE 7053 (IFP10A)

TOMVAR ENTRY ID = %1 WITH KEYWORD STRESS DOES NOT REFERENCE ANY PSHELL
ENTRY.
OR THERE ARE OTHER TOMVAR ENTIRES THAT REFERENCE NON-PSHELL ENTRIES

User information: STRESS BASED TOPOMETRY OPTIMIZATION SUPPORTS SHELL THICK-

NESS ONLY

7053.11 *** USER FATAL MESSAGE 7053 (IFP10F)

TOMVAR ENTRY ID = %1 HAS TOO SMALL ABSOLUTE INITIAL VALUE (<1.E-8)

User information: IT MAY BE NECESSARY TO RESCALE THE DESIGN VARIABLES

7054.0 *** USER FATAL MESSAGE 7054 (DVPCHK)

Main Index
 774 MSC Nastran Error Messages
Errors 7000 - 7999

THE PROPERTY NAME %1 REFERENCED ON DVPREL%2 ENTRY %3 CAN NOT BE

DESIGNED.

7054.1 *** USER FATAL MESSAGE 7054 (DVPCHK)

THE PROPERTY NAME %1 REFERENCED ON TOMVAR ENTRY %2 CAN NOT BE
DESIGNED.

7055.0 *** USER FATAL MESSAGE 7055 (DVPCHK)

DVPREL %1 ENTRY %2 WITH PTYPE= %3 REFERENCES AN FID %4 THAT CAN NOT BE
DESIGNED.

7055.1 *** USER FATAL MESSAGE 7055 (DOPR1C)

%1 ENTRY %2 SPECIFIES PROPERTY NAME = %3 THAT IS NOT SPECIFIED ON PBEAM
ENTRY %4.

User action: CHECK %5 AND PBEAM ENTRIES.

7055.2 *** USER FATAL MESSAGE 7055 (DOPR1Z)

%1 ENTRY %2 SPECIFIES FID = %3 THAT IS NOT SPECIFIED ON PBEAM ENTRY %4.

User action: CHECK %5 AND PBEAM ENTRIES.

7055.3 *** USER FATAL MESSAGE 7055 (DOPR1C)

%1 ENTRY %2 SPECIFIES FID = %3 THAT IS NOT SPECIFIED ON PCOMP ENTRY %4.

User action: CHECK %5 AND PCOMP ENTRIES.

7055.4 *** USER FATAL MESSAGE 7055 (DOMPNTF)

%1 ENTRY %2 SPECIFIES PROPERTY NAME = %3 THAT IS NOT SPECIFIED ON PCOMP
ENTRY %4.

User action: CHECK %5 AND PCOMP ENTRIES.

7055.5 *** USER FATAL MESSAGE 7055 (DVPCHK)

TOMVAR ENTRY %1 WITH PTYPE= %2 REFERENCES AN FID %3 THAT CAN NOT BE
DESIGNED.

Main Index
 MSC Nastran Error Messages 775
Errors 7000 - 7999

7055.6 *** USER FATAL MESSAGE 7055 (DOPR1C)

%1 ENTRY %2 REFERS TO A %3 WITH ID = %4, BUT THERE IS A %5 WITH THIS ID.

User information: A %1 ENTRY CANNOT REFER TO A SPAWNED PROPERTY.

7057.0 ***USER FATAL MESSAGE 7057, DOMPTA.

ILLEGAL PROPERTY ENTRY NAME %1

7076.0 *** USER FATAL MESSAGE 7076 (DOPR3I)

DRESP1 ENTRY ID = %1 REFERENCES A %2 BULK DATA ENTRY ID = %3 WHICH cannot be
found.

7076.1 *** USER FATAL MESSAGE 7076 (DOPR3B)

DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES A %2 BULK DATA ENTRY OF ID %3
WHICH DOES NOT EXIST.

7077.0 *** USER FATAL MESSAGE 7077 (%1)

DRESP1 ENTRY ID = %1 SPECIFIES A ROOT NUMBER = %2 WHICH IS GREATER THAN THE
NROOT = %3 ON THE associated DIVERG BULK DATA ENTRY ID = %4.

7078.0 *** USER FATAL MESSAGE 7078 (DOPR3I)

DRESP1 ENTRY ID = %1 SPECIFIES A MACH NUMBER = %2 WHICH IS NOT LISTED ON
THE ASSOCIATED DIVERG BULK DATA ENTRY ID = %3.

7081.0 *** SYSTEM FATAL MESSAGE 7081 (DOPR3I)

DRESP1 ENTRY id = %1 INVOKES A %2 RESPONSE TYPE IN SUBCASE ID = %3.
but THE REQUIRED %4 SET CASE CONTROL command cannot be found.

7081.1 *** SYSTEM FATAL MESSAGE 7081 (DOPR3I)

DRESP1 ENTRY id = %1 INVOKES A %2 RESPONSE TYPE IN SUBCOM ID = %3.
THIS RESPONSE TYPE IS NOT SUPPORTED FOR SUBCOM CASE CONTROL .

7084.0 *** USER FATAL MESSAGE 7084 (DOPR3B)

Main Index
 776 MSC Nastran Error Messages
Errors 7000 - 7999

DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES A TRIM VARIABLE OF ID %2 WHICH

CAN NOT BE FOUND.

User information: THE TRIM VARIABLE ID MUST REFER TO AN AESTAT OR AESURF BULK
DATA ENTRY.

7085.0 *** USER FATAL MESSAGE 7085 (DOPR3I)

THE DENSITY RATIO OF %1 CANNOT BE FOUND IN THE FLFACT BULK DATA ENTRY ID
= %2.

User information: EVERY DENSITY RATIO LISTED ON THE FLFACT REFERENCED BY THE
DRESP1 ENTRY MUST APPEAR IN THE FLFACT REFERENCED BY THE FLUTTER ENTRY.

7086.0 *** USER FATAL MESSAGE 7086 (DOPR3I)

THE MACH NUMBER OF %1 CAN NOT BE FOUND IN THE FLFACT BULK DATA ENTRY OF
ID %2.

User information: EVERY MACH NUMBER LISTED ON THE FLFACT REFERENCED BY THE
DRESP1 ENTRY MUST APPEAR IN THE FLFACT REFERENCED BY THE FLUTTER ENTRY.

7087.0 *** USER FATAL MESSAGE 7087 (DOPR3I)

THE VELOCITY OF %1 CAN NOT BE FOUND IN THE FLFACT BULK DATA ENTRY OF ID
%2.

User information: EVERY VELOCITY LISTED ON THE FLFACT REFERENCED BY THE DRESP1
ENTRY MUST APPEAR IN THE FLFACT REFERENCED BY THE FLUTTER ENTRY.

7088.0 *** USER FATAL MESSAGE 7088 (DSAD14)

THE FLUTTER MODE OF %1 REQUESTED ON A SET1 ENTRY IS GREATER THAN %2, THE
NUMBER OF EXTRACTED MODES.

User information: SET1 IS REFERENCED BY DRESP1 BULK DATA WITH RTYPE = FLUTTER.

7088.1 *** SYSTEM FATAL MESSAGE 7088 (DOPR3I)

MODE NO. %1 ASSOCIATED WITH FLUTTER DRESP1 ID = %2 EXCEEDS %3, THE NUMBER
OF MODES AVAILABLE FROM THE ANALYSIS.

Main Index
 MSC Nastran Error Messages 777
Errors 7000 - 7999

7089.0 *** USER FATAL MESSAGE 9101 (GUSTLDW):

NO AERODYNAMIC MATRICES WERE COMPUTED TO INTERPOLATE IN THE SAME
SONIC BOUNDARY OF MACH = %1 SPECIFIED IN BULK DATA GUST2 ENTRY ID = %2.

User action: ADD A MACH NUMBER IN THE SAME SONIC BOUNDARY AND SET OF HARD
POINTS ON A BULK DATA ENTRY MKAERO1 OR MKAERO2.

7090.0 *** USER FATAL MESSAGE 9103 (GUTSLDW)

AT MACH = %1 AND KBAR = %2 ONE OR MORE OF THE FOLLOWING AERODYNAMIC
MATRICES ARE MISSING:
SKJ = %3, LAJJT = %4, UAJJT = %5

User action: ADD THE ABOVE MACH AND HARD POINT PAIR ON A BULK DATA ENTRY
MKAERO1 OR MKAERO2.

7090.1 *** USER FATAL MESSAGE 9103 (GUTSLDW)

AT MACH = %1 AND KBAR = %2 ONE OR MORE OF THE FOLLOWING AERODYNAMIC
MATRICES ARE MISSING:
SKJ = %3, AJJI = %4

User action: ADD THE ABOVE MACH AND HARD POINT PAIR ON A BULK DATA ENTRY
MKAERO1 OR MKAERO2.

7091.0 *** USER FATAL MESSAGE (AMPF)

PARAM GUSTAERO -1 is specified without using CAERO1 or CAERO2 entries to define the aerodyan-
mic mesh.

User avoidance: REMOVE THE PARAM, GUSTAERO, -1 OR REDEFINE THE AERO MESH
WITH CAERO1 AND CAERO2 ENTRIES

7102.0 *** USER FATAL MESSAGE 7102 (DOPR3Z)

DCONSTR ID = %1 APPEARS MORE THAN ONCE ON DCONADD ENTRY %2.

7103.0 *** USER INFORMATION MESSAGE 7103 (DOPR3)

NO DCONSTR ENTRIES ARE SPECIFIED IN THE BULK DATA.

Main Index
 778 MSC Nastran Error Messages
Errors 7000 - 7999

7104.0 *** USER FATAL MESSAGE 7104 (DOPR3F)

NO DCONSTR ENTRIES CAN BE FOUND WITH THE DESGLB = %1.

7104.1 *** USER FATAL MESSAGE 7104 (DOPR3F)

NO DCONSTR ENTRIES CAN BE FOUND WITH THE DESSUB = %1.

7105.0 *** USER FATAL MESSAGE 7105 (DOPR3F)

NO DCONSTR ID = %1 ENTRY CAN BE FOUND FOR DCONADD ENTRY ID = %2.

7114.0 *** SYSTEM FATAL MESSAGE 7114 (DOM2B)

LESS THAN 3 WORDS IN AN EPT RECORD

7115.0 *** USER FATAL MESSAGE 7115 (DOM2B)

PTYPE %1%2 IS NOT SUPPORTED

7116.0 *** SYSTEM FATAL MESSAGE 7116 (DOM2B)

LESS THEN 2 WORDS IN A PSHELL ENTRY, PID = %1

7116.1 *** SYSTEM FATAL MESSAGE 7116 (DOM2B)

LESS THAN 2 WORDS IN A PCOMP ENTRY, PID = %1

7119.0 *** SYSTEM FATAL MESSAGE 7119 (DOM2B)

INCORRECT ENTRY LENGTH AT PTYPE = %1%2 PID = %3

7124.0 *** USER FATAL MESSAGE 7124 (DOPR3B)

PTYPE %1 ON DRESP1 ID=%2 IS NOT DEFINED IN THE ANALYSIS MODEL

7124.1 *** USER FATAL MESSAGE 7124 (DOPR3B)

MATERIAL ID %1 ON DRESP1 ID=%2 IS NOT DEFINED IN THE ANALYSIS MODEL

7124.2 *** USER FATAL MESSAGE 7124 (DSAD28)

%1 ID %2 AND MATERIAL ID %3 ON DRESP1 ID=%4 IS NOT DEFINED IN THE ANALYSIS
MODEL

7124.3 *** USER FATAL MESSAGE 7124 (DOPR3B)

Main Index
 MSC Nastran Error Messages 779
Errors 7000 - 7999

THE DENSITY OF MATID %1 IS BEING DESIGNED WHILE THE WEIGHT OF THE MATE-
RIAL IS REQUESTED ON DRESP1 ID %2.

User information: THIS IS NOT SUPPORTED.

7124.4 *** USER FATAL MESSAGE 7124 (DOPR3B)

MATERIAL ID %1 ON DRESP1 ID=%2 WITH RTYPE=WMPID IS INVOKED ON A TOPVAR
ENTRY.

User information: REFERENCING THE SAME MATERIAL ID WITH TOPVAR AND A DRESP1
WITH RTYPE=WMPID WILL RESULT IN MISLEADING INFORMATION AND IS THEREFORE
NOT SUPPORTED.

7125.0 *** USER FATAL MESSAGE 7125 (DOPR3G)

SUBCASE %1 , DRSPAN ID = %2 REFERENCES AN UNDEFINED SET.

7125.1 *** USER FATAL MESSAGE 7125 (DOPR3G)

DRESP1 ID = %1 INVOKED BY SETID = %2 FOR A DRSPAN REQUEST IN SUBCASE %3 CAN-
NOT BE FOUND

7127.0 *** USER FATAL MESSAGE 7127 (DOPR3B)

DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES PTYPE %2 PID %3
THERE ARE NO ELEMENTS CORRESPONDING TO THIS COMBINATION.

7127.1 *** USER FATAL MESSAGE 7127 (DOPR3B)

DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES PTYPE %2 WITH INCORRECT LAM-
INA NUMBER %3

7127.2 *** USER FATAL MESSAGE 7127 (DOPR3B)

DRESP1 BULK DATA ENTRY OF ID %1 REFERENCES PTYPE %2 PID %3
THIS PROPERTY ENTRY DOES NOT EXIST.

7127.3 *** USER FATAL MESSAGE 7127 (DOPR3B)

Main Index
 780 MSC Nastran Error Messages
Errors 7000 - 7999

DRESP1 BULK DATA ENTRY OF ID %1 HAS RTYPE=WMPID AND REFERENCES PTYPE %2

PID %3
THIS PROPERTY ID IS ALSO USED ON A TOMVAR ENTRY SO THE PROPERTY NO LONGER
EXISTS.

User information: REFERENCING THE SAME PROPERTY ID AND TYPE ON A TOMVAR

ENTRY AND A DRESP1 WITH RTYPE=WMPID IS NOT SUPPORTED.

7137.0 *** USER FATAL MESSAGE 7137 (DOPR3C)

ON %1 entry ID = %2, DVID = %3 IS EITHER NOT REFERENCED ON A DESVAR BULK DATA
ENTRY OR NOT SELECTED BY THE DESVAR CASE CONTROL COMMAND.

7138.0 *** USER FATAL MESSAGE (dpr3fc)

THERE ARE NON-CONTIGUOUS SUBCASES THAT INVOKE FREQUENCY SET = %1. THIS
IS NOT SUPPORTED IN SOL 200.

User avoidance: ARRANGE THE SUBCASES SO THAT THOSE WITH THE SAME FREQUENCY
EXCITATION SET ARE CONTIGUOUS.

7139.0 *** USER FATAL MESSAGE 7139 (DOPR3C)

ON %1 entry ID = %2, DRESP1 ID = %3 DOES NOT REFERENCE AN EXISTING DRESP1
ENTRY.

7139.1 *** USER FATAL MESSAGE 7139 (DOPR3N)

ON DRESP2 entry ID = %1, DRESP2 ID = %2 DOES NOT REFERENCE AN EXISTING DRESP2
ENTRY.

7139.2 *** USER FATAL MESSAGE 7139 (DOPR3X)

ON %1 entry ID = %2, %3 ID = %4 DOES NOT REFERENCE AN EXISTING %3 ENTRY OR
DOES NOT REFERENCE AN EXISTING INTEGRATED DRESP1 ENTRY.

7139.3 *** USER FATAL MESSAGE 7139 (DOPR3X)

ON %1 entry ID = %2, %4 TH ID UNDER %3 FLAG DOES NOT REFERENCE AN EXISTING
ENTRY.

User information: FOR FLAG=DRESP2, IT COULD BE A MISSING INTEGRATED DRESP1

ENTRY.

Main Index
 MSC Nastran Error Messages 781
Errors 7000 - 7999

7139.4 *** USER FATAL MESSAGE 7139 (DOPR3C)

A SPAWNED DRESP2 (FUNC=BETA OR MATCH) REFERENCES DRESP1 ID %1 WHICH
DOES NOT EXIST.

7140.0 *** USER FATAL MESSAGE 7140 (DOPR3C)

ON %1 entry ID = %2, DRESP1 ID = %3 OF PART SE %4 DOES NOT REFERENCE AN EXIST-
ING DRESP1 ENTRY.

7141.0 *** USER FATAL MESSAGE 7141

DRESP2 ENTRY ID = %1 REFERENCES DRESP1 ENTRIES WITH IDS = %2 AND %3.
THESE DRESP1 ENTRIES HAVE DIFFERENT RTYPES AND AT LEAST ONE OF THE ENTRIES
HAS MORE THAN ONE ASSOCIATED RESPONSE.

User information: IF A DRESP2 ENTRY SPANS RESPONSE TYPES, THEN EACH ASSOCIATED
DRESP1 ENTRY MUST GENERATE A SINGLE RESPONSE.

7141.1 *** USER FATAL MESSAGE 7141

%1 ENTRY ID = %2 REFERENCES DRESP1 ENTRIES WITH IDS = %3 AND %4.
THESE DRESP1 ENTRIES HAVE DIFFERENT RTYPES AND AT LEAST ONE OF THE ENTRIES
HAS MORE THAN ONE ASSOCIATED RESPONSE.

User information: IF A %5 ENTRY SPANS RESPONSE TYPES, THEN EACH ASSOCIATED DRE-
SP1 ENTRY MUST GENERATE A SINGLE RESPONSE.

7142.0 *** USER FATAL MESSAGE 7142

DRESP2 ENTRY ID = %1 REFERENCES DRESP1 ENTRIES WITH IDS = %2 AND %3.
THESE DRESP1 ENTRIES HAVE A DIFFERENT NUMBER OF RESPONSES.

User information: DRESP1 ENTRIES REFERENCED BY A DRESP2 ENTRY MUST HAVE THE
SAME NUMBER OF RESPONSES

7142.1 *** USER FATAL MESSAGE 7142 (DOPR3J/DPR3J1)

Main Index
 782 MSC Nastran Error Messages
Errors 7000 - 7999

%1 ENTRY ID = %2 REFERENCES DRESP1 = %3 AND DRESP2 ID = %4.

THESE REFERENCED ENTRIES HAVE A DIFFERENT NUMBER OF RESPONSES.

User information: DRESP1 AND DRESP2 ENTRIES REFERENCED BY A %5 ENTRY MUST HAVE
THE SAME NUMBER OF RESPONSES

7142.2 *** USER FATAL MESSAGE 7142

%1 ENTRY ID = %2 REFERENCES DRESP2 ENTRIES WITH IDS = %3 AND %4.
THESE REFERENCED ENTRIES HAVE A DIFFERENT NUMBER OF RESPONSES.

User information: DRESP2 ENTRIES REFERENCED BY A %5 ENTRY MUST HAVE THE SAME
NUMBER OF RESPONSES.

7142.3 *** USER FATAL MESSAGE 7142

%1 ENTRY ID = %2 REFERENCES DRESP1 ENTRIES WITH IDS = %3 AND %4.
THESE DRESP1 ENTRIES HAVE A DIFFERENT NUMBER OF RESPONSES.

User information: DRESP1 ENTRIES REFERENCED BY A %5 ENTRY MUST HAVE THE SAME
NUMBER OF RESPONSES.

7143.0 *** USER FATAL MESSAGE 7143 (DOPR3H)

%3 ID = %1 IS REFERENCED BY MORE THAN ONE DCONSTR ENTRY IN SUBCASE = %2.

User information: IMPOSING CONFLICTING CONSTRAINTS ON A RESPONSE WILL IMPEDE

OPTIMIZATION AND MUST BE AVOIDED.

7143.1 *** USER FATAL MESSAGE 7143 (DOPR3H)

DRESP1 ENTRY ID = %1 IS REFERENCED BY MORE THAN ONE DCONSTR ENTRY IN SUB-
CASE = %2.

User information: THE IMPOSITION OF CONFLICTING CONSTRAINTS ON A RESPONSE

WILL IMPEDE OPTIMIZATION AND MUST BE AVOIDED.

7144.0 *** USER FATAL MESSAGE 7144 (DOPR3H)

SUBCASE ID = %1 IMPOSES A DCONSTR ON UNDEFINED DRESPI ID = %2.

7145.0 *** USER FATAL MESSAGE 7145 (DOPR3H)

Main Index
 MSC Nastran Error Messages 783
Errors 7000 - 7999

THE DRSPAN COMMAND IN SUBCASE %1 REFERENCES DRESP1 ENTRY ID = %2

WHICH INVOKES MULTIPLE RESPONSES.

User information: DRESP1 ENTRIES REFERENCED BY DRSPAN REQUEST MUST BE A SCALAR

QUANTITY.

7146.0 *** USER FATAL MESSAGE 7146 (DOPR3H)

SUBCASE ID = %1 REFERS TO AN UNDEFINED DRESP1 ID = %2 VIA A DRSPAN SET COM-
MAND.

7147.0 *** USER FATAL MESSAGE 7147 (DPR3H1)

THE DESOBJ COMMAND WITH ID = %1 REFERENCES A %2 ENTRY WHICH IN TURN REF-
ERENCES DRESP1 ID = %3 WHICH INVOKES MULTIPLE RESPONSES.

User information: THE DRESP1 ENTRIES INVOLVED IN DEFINING THE OBJECTIVE MUST
BE SCALAR QUANTITIES.

User action: IF YOUR DRESP2 REFERENCES A DRESP1 THAT DEFINES A RESPONSE LIKE
MAX OR RSS, MAKE SURE TO USE FLAG 'DRESP2' INSTEAD OF 'DRESP1' ON THE CONTIN-
UATION LINE.

7147.1 *** USER FATAL MESSAGE 7147 (DPR3H2)

THE DESOBJ COMMAND WITH ID = %1 REFERENCES A %2 ENTRY WHICH IN TURN REF-
ERENCES DRESP2 ID = %3 WHICH INVOKES MULTIPLE RESPONSES.

User information: THE DRESP2 ENTRY INVOLVED IN DEFINING THE OBJECTIVE MUST BE
SCALAR QUANTITIES.

User action: IF YOUR DRESP2 REFERENCES A DRESP1 THAT DEFINES A RESPONSE LIKE
MAX OR RSS, MAKE SURE TO USE FLAG 'DRESP2' INSTEAD OF 'DRESP1' ON THE CONTIN-
UATION LINE.

7148.0 *** USER FATAL MESSAGE 7148 (DOPR3H)

Main Index
 784 MSC Nastran Error Messages
Errors 7000 - 7999

THE DESOBJ COMMAND WITH ID = %1 REFERENCES A DRESP1 ENTRY WHICH INVOKES

MULTIPLE RESPONSES.

User information: DRESP1 ENTRIES INVOLVED IN DEFINING THE OBJECTIVE MUST BE

SCALAR QUANTITIES.

7149.0 *** USER FATAL MESSAGE 7149 (DOPR3H)

THE DESOBJ COMMAND WITH ID = %1 REFERS TO AN UNDEFINED DRESPI ENTRY.

User information: THE DESOBJ COMMAND REFERENCES A DRESP1 OR DRESP2 BULK DATA
ENTRY WHICH MUST EXIST

7168.0 *** USER FATAL MESSAGE 7168 (DOPR3J)

EQID %1 REFERENCED ON DRESP2 %2 IS NOT PRESENT ON A DEQATN ENTRY.

7168.1 *** USER FATAL MESSAGE 7168 (DOPR1Z)

EQID %1 REFERENCED ON DVPREL2 %2 IS NOT PRESENT ON A DEQATN ENTRY.

7168.2 *** USER FATAL MESSAGE 7168 (DOPR1Z)

EQID %1 REFERENCED ON DVCREL2 %2 IS NOT PRESENT ON A DEQATN ENTRY.

7168.3 *** USER FATAL MESSAGE 7168 (DOPR1Z)

EQID %1 REFERENCED ON DVMREL2 %2 IS NOT PRESENT ON A DEQATN ENTRY.

7168.4 *** USER FATAL MESSAGE 7168 (DOPR1Z)

EQID %1 REFERENCED ON PBUSH2D %2 IS NOT PRESENT ON A DEQATN ENTRY.

7169.0 *** USER FATAL MESSAGE 7190 (DOPR1C)

FRQVAR ID %1 REFERENCED ON DFRQVAR ENTRY ID %2 CANNOT BE FOUND.

User action: CORRECT OR DELETE THE DFRQVAR ENTRY OR INCLUDE AN ADDITIONAL

FRQVAR ENTRY.

7170.0 *** USER FATAL MESSAGE 7170 (DOPR1C)

Main Index
 MSC Nastran Error Messages 785
Errors 7000 - 7999

DFRQVAR ID %1 REFERENCES FREQVAR ID %2 BUT THIS FRQVAR IS NOT REFERENCED

IN ANY SUBCASE

User action: EITHER DELETE THE DFRQVAR DESIGN REQUEST OF ADD A FRQVAR COM-
MAND IN ONE OR MORE FLUTTER SUBCASES

7171.0 *** USER FATAL MESSAGE 7171 (DOPR1C)

DFRQVAR ID %1 REFERENCES FRQVAR ID %2 WITH LABEL = %3 %4 BUT THIS LABEL
DOES NOT APPEAR ON THE FRQVAR ENTRY

User action: CHECK THAT THE TWO LABELS CORRESPOND

7190.0 *** USER FATAL MESSAGE 7190 (DOPR1I)

PTYPE %1 DEFINED ON A %2 %3 ENTRY CAN NOT BE FOUND ON A PROPERTY ENTRY.

User action: DELETE THE %4 ENTRY OR INCLUDE AN ADDITIONAL PROPERTY ENTRY.

7190.1 *** USER FATAL MESSAGE 7190 (DOP1c1)

PTYPE %1 DEFINED ON A DVPREL1 ENTRY CAN NOT BE FOUND ON A PROPERTY
ENTRY.

User action: DELETE THE DVPREL1 ENTRY OR INCLUDE AN ADDITIONAL PROPERTY

ENTRY.

7193.0 *** USER FATAL MESSAGE 7193 (DOPR1I)

PID=%1 OF PTYPE %2 ON A %3 %4 ENTRY, IS NOT DEFINED ON A PROPERTY ENTRY.

User action: CHECK %5 AND PROPERTY ENTRIES.

7193.1 *** USER FATAL MESSAGE 7193 (DOPR1IL)

DVLREL1 ENTRY %1 WITH ATT1 = %2 ATTEMPTS TO DESIGN A LOAD THAT IS NOT
DEFINED.

User action: INSURE THAT THE SID AND ATTRIBUTES ON THE DVLREL1 ENTRY CORRE-
SPOND TO AN EXISTING LOAD ENTRY.

Main Index
 786 MSC Nastran Error Messages
Errors 7000 - 7999

7193.2 *** USER FATAL MESSAGE 7193 (DOPR1IL)

DVLREL1 ENTRY %1 WITH ATT1 = %2 AND ATT2 = %3 ATTEMPTS TO DESIGN A LOAD
THAT IS NOT DEFINED

User action: INSURE THAT THE SID AND ATTRIBUTES ON THE DVLREL1 ENTRY CORRE-
SPOND TO AN EXISTING ENTRY.

7193.3 *** USER FATAL MESSAGE 7193 (DOM11A2)

A DVLREL1 ENTRY SEEKS SI= %2 ON LOAD ID = %1. THIS SI CANNOT BE FOUND.

7193.4 *** USER FATAL MESSAGE 7193 (IPF10C)

A TOPVAR ENTRY REFERENCES PROPERTY ID = %1. THERE ARE NO ELEMENTS ASSOCI-
ATED WITH THIS PROPERTY.

User action: INSURE THAT THE PROPERTY ID IS REFERENCED BY ONE OF MORE ELE-
MENTS.

7194.0 *** USER FATAL MESSAGE 7194

DVLREL1 ENTRY %1 IS ATTEMPTING TO DESIGN A LOAD THAT IS NOT UNIQUE.

User action: ADD ATTRIBUTES TO THE DVLREL1 ENTRY SO AS TO MAKE THE REQUEST
UNIQUE OR CONSOLIDATE THE LOADS TO REMOVE LOADS WITH IDENTICAL ATTRI-
BUTES.

7196.0 *** USER FATAL MESSAGE 7196 (DOPR1I)

FID=%1 SPECIFIED ON A %2 %3 ENTRY WITH PTYPE= %4 AND PID= %5 IS INVALID.

User action: CORRECT THE FID FIELD ON THE %6 ENTRY.

7196.1 *** USER WARNING MESSAGE 7196 (DOPR1I)

THE PROPERTY NAME 'D' SPECIFIED ON A %1 %2 ENTRY WILL BE IGNORED
BECAUSE PWELD ENTRY %3 DEFINES A RIGID BODY BEHAVIOR.

7197.0 *** USER FATAL MESSAGE 7197 (DOPR1I)

Main Index
 MSC Nastran Error Messages 787
Errors 7000 - 7999

PTYPE=%1 PID=%2 PROPERTY NAME=%3 IS DEFINED MORE THAN ONCE BY %4 %5

ENTRY.

User information: DESIGNED PROPERTIES ON %6 MUST BE UNIQUE.

7198.0 *** USER FATAL MESSAGE 7198 (ARBP6D)

PBRSECT/PBMSECT ENTRY ID=%1 WITH CP (CLOSED PROFILE) HAS SEGMENTS
WHICH DO NOT FORM A CLOSED LOOP.

7198.1 *** USER FATAL MESSAGE 7198 (ARBP6D)

ARBITRARY BEAM PROCESSING DETECTS PBRSECT/PBMSECT ENTRY ID=%1 HAS BRP
NOT START OR END WITH OUTP.

7198.2 *** USER FATAL MESSAGE 7198 (ARBP6D)

PBRSECT/PBMSECT ENTRY ID=%1 HAS NO BRP START OR END WITH POINT ID %2.

7198.3 *** USER FATAL MESSAGE 7198 (ARBP6D)

BRP WITH END POINT ID %2 CAN NOT BE LOCATED ON OUTP OF PBRSECT/PBMSECT
ENTRY ID=%1.

7199.0 *** USER FATAL MESSAGE 7199 (ARBDRD)

SET ID %1 REFERENCED ON PBRSECT/PBMSECT ENTRY ID=%2 IS NOT DEFINED.

7200.0 *** USER FATAL MESSAGE 7200 (ARBDRD)

SET ID %1, REFERENCED ON PBRSECT/PBMSECT ENTRY ID=%2 WITH GS, SPECIFIED
ONLY %3 POINTS.

User action: THE SET MUST CONTAIN AT LEAST 3 POINTS IF THE FIRST AND LAST POINT
IDS ARE DIFFERENT.

7201.0 *** USER FATAL MESSAGE 7201 (ARBDRD)

POINT ID %1 REFERENCED ON SET ID %2 FOR PBRSECT/PBMSECT ENTRY ID=%3 IS NOT
DEFINED.

7201.1 *** USER FATAL MESSAGE 7201 (ARBDRD)

Main Index
 788 MSC Nastran Error Messages
Errors 7000 - 7999

PBRSECT/PBMSECT ENTRY ID=%1, MULTIPLE BRPS BRANCH OUT FROM THE SAME SIDE
OF A POINT OF OUTP.

User action: MAKE SURE a) ONLY 1 BRP BRANCHES OUT FROM ONE SIDE OF OUTP AND
b) BRP DOES NOT START/END on 1st or last point of OUTP

7201.2 *** USER FATAL MESSAGE 7202 (ARBDRD)

PBRSECT/PBMSECT ENTRY ID=%1, WITH FORM=CP OR FORM=OP, BRP(%2) START AND
END ON POINTS OF OUTP HAS NO MID-POINT.

7201.3 *** USER FATAL MESSAGE 7202 (ARBDRD)

PBRSECT/PBMSECT ENTRY ID=%1, WITH FORM=CP OR FORM=OP, BRP THCIKNESS IS
LARGER THAN LENGHT OF SEGMENT OF OUTP AT CONNECTION POINT %2

7201.4 *** USER FATAL MESSAGE 7202 (ARBDRD)

PBRSECT/PBMSECT ENTRY ID=%1, WITH FORM=CP OR FORM=OP, BRP(%2) THCIKNESS
IS LARGER THAN LENGHT OF SEGMENT OF OUTP AT CONNECTION POINT %3

7201.5 *** USER FATAL MESSAGE 7202 (ARBDRD)

PBRSECT/PBMSECT ENTRY ID=%1, INTERSECTION OF SEGMENTS WITHIN A LOOP OR
BETWEEN LOOPS FOUND.

User action: IF FORM=CP OR OP, USE LESSER NUMBER OF POINTS TO DESCRIBE THE PRO-
FILE. ESPECIALLY IN MERGING AREA OF TWO LINES.
IF FORM=GS, CHECK FOR OVERLAPPING POINTS AND/OR POINTS WITH SAME COORDI-
NATES.

7201.6 *** USER FATAL MESSAGE 7202 (ARNP0d/vabp0d

PBRSECT/PBMSECT ENTRY ID=%1, BRP(%2) STARTS AND ENDS WITH THE SAME POINT
%3.

7202.0 *** USER FATAL MESSAGE 7202 (ARBDRD)

PBRSECT/PBMSECT ENTRY ID=%1, WITH FORM=CP OR FORM=OP, NO THICKNESS(T)
SPECIFIED OR DEFAULT THICKNESS MISSING.

7202.1 *** USER FATAL MESSAGE 7202 (ARBDRD)

Main Index
 MSC Nastran Error Messages 789
Errors 7000 - 7999

PBRSECT/PBMSECT ENTRY ID=%1, WITH FORM=CP OR FORM=OP, BRP DOES NOT

START AND/OR END ON A POINT OF OUTP.

7202.2 *** USER FATAL MESSAGE 7202 (ARBDRD)

PBRSECT/PBMSECT ENTRY ID=%1, WITH FORM=CP OR FORM=OP, BRP(%2) DOES NOT
START AND/OR END ON A POINT OF OUTP.

7202.3 *** USER WARNING MESSAGE 7202 (ARBP0D)

PBRSECT/PBMSECT ENTRY ID=%1, T(%2) WITH POINT ID PAIR (%3,%4) HAS NOT BEEN
REFERENCED.
PLEASE CHECK PBRSECT/PBMSECT AND, IF IT IS NOT A REDUNDANT INPUT, MAKE
SURE IDS ARE NEXT TO EACH OTHER IN SET1 OR SET3.

7202.4 *** USER FATAL MESSAGE 7202 (ARBP0D)

BRP OF PBRSECT/PBMSECT ENTRY ID=%1 STARTS AND/OR ENDS ON THE FIRST AND/OR
LAST POINT OF OUTP.

7202.5 *** USER FATAL MESSAGE 7202 (ARBP0D)

BRP(%2) OF PBRSECT/PBMSECT ENTRY ID=%1 STARTS AND/OR ENDS ON THE FIRST
AND/OR LAST POINT OF OUTP.

7202.6 *** USER FATAL MESSAGE 7202 (ARBP0D/ARNP0D)

SET ID %2 REFERENCED REPEATEDLY ON OUTP/BRP OF PBRSECT/PBMSECT ENTRY
ID=%1.

7202.7 *** USER FATAL MESSAGE 7202 (ARBP0D/ARNP0D)

NO INPUT PROVIDED FOR MID FIELD OF PBRSECT/PBMSECT ENTRY ID=%1.

7202.8 *** USER FATAL MESSAGE 7202 (ARBP0D/ARNP0D)

PBRSECT/PBMSECT ENTRY ID=%1 HAS MISSING OUTP.

7203.0 *** SYSTEM FATAL MESSAGE 7203 (IFP9)

The arbitrary beam cross section capability (PBRSECT/PBMSECT) is not supported on long-word
(single precision) machines.

User action: use PBAR/PBEAM or PBARL/PBEAML instead.

Main Index
 790 MSC Nastran Error Messages
Errors 7000 - 7999

7203.1 *** USER FATAL MESSAGE 7203 (IFP9)

UNCONNECTED GRIDS FOUND. PBxSECT ID = %1. GRID IDs ARE as follows:'

7203.2 *** USER FATAL MESSAGE 7203 (IFP9)

INTERSECT OF LINE SEGMENTS FOUND. PBxSECT ID = %1, connecting gid %2 and %3.

7204.0 *** USER FATAL MESSAGE 7204.

PANEL Bulk Data entry id= %2 references a SET3 entry id= %1 which specifies the POINT Option

7204.1 *** USER WARNING MESSAGE 7204.

ERPPNL Bulk Data entry id= %1 references a SET3 entry id= %2 which specifies the GRID Option
which is not supported.

7204.2 *** USER WARNING MESSAGE 7204.

ERPPNL Bulk Data entry id= %1 references a SET1 entry id= %2. SET1 is not supported.

7205.0 *** SYSTEM FATAL MESSAGE 7205 (ACRISC)

SET %1 CANNOT BE FOUND.

User action: CONTACT MSC CLIENT SUPPORT

7206.0 *** USER WARNING MESSAGE 7206 (ACRIPN2)

SUBCASE %1: PANEL ID=%2, WHICH IS REFERENCED ON ACPOWER CASE CONTROL
COMMAND, DOES NOT EXIST.

User information: NO RESULTS WILL BE COMPUTED FOR THIS PANEL.

User action: CHECK DEFINITION OF PANEL SETS

7207.0 *** USER WARNING MESSAGE 7207 (ACRIPN3)

PANEL %1 HAS NO GRID POINTS ON THE WETTED SURFACE.

User information: RESULTS WILL BE ZERO.

User action: CHECK PANEL DEFINITION.

Main Index
 MSC Nastran Error Messages 791
Errors 7000 - 7999

7220.0 *** USER FATAL MESSAGE 7220 (DOPR3T)

ON %1 entry ID = %3, %2 ID = %4 DOES NOT REFERENCE AN EXISTING %2 ENTRY.

7220.1 *** USER FATAL MESSAGE 7220 (DOPR3T)

%1 ENTRY ID = %2 SPECIFIES A DNODE GRID ID =%3 AND COMPONENT =%4
COMBINATION WHICH DOES NOT EXIST.

User action: MAKE SURE THE GRID AND COMPONENT ARE DEFINED IN THE ANALYSIS
MODEL.

7220.2 *** USER FATAL MESSAGE 7220 (DOPR2F)

%1 ENTRY ID = %2 SPECIFIES A DNODE GRID ID =%3
COORDINATE SYSTEM %4 USED FOR GRID ID =%3 NOT DEFINED

User action: Check coordinate system numbers used on Bulk Data entries to insure that there are no unde-
fined coordinate systems.

7220.3 *** USER FATAL MESSAGE 7220 (DOPR2F)

%1 ENTRY ID = %2 SPECIFIES A DNODE GRID ID =%3 DEFINED in COORDINATE SYSTEM
%4 COORDINATE SYSTEM %4 IS A NON-BASIC COORDINATE SYSTEM THAT IS NOT SUP-
PORTED FOR DESIGNED NODES.

User action: Ensure a baisc coordinate system referenced for the designed nodes

7251.0 *** user FATAL MESSAGE 7251 (DOPR4)

THERE ARE NO PROPERTY OR SHAPE VARIABLES SPECIFIED IN THE DESIGN MODEL.

User information: PROPERTY VARIABLES ARE SPECIFIED ON DVPREL1 AND DVPREL2 BULK
DATA ENTRIES.
SHAPE VARIABLES ARE SPECIFIED ON DVGRID ENTRIES OR INPUT DIRECTLY.

7300.0 *** SYSTEM FATAL MESSAGE 7300 (FMSFIO)

FORTRAN UNIT %1 USED FOR FMS HAS BEEN CLOSED AND DELETED.

7301.0 *** SYSTEM FATAL MESSAGE 7301 (FMSFIO)

CANNOT OPEN FORTRAN UNIT %1 USED FOR FMS.

Main Index
 792 MSC Nastran Error Messages
Errors 7000 - 7999

7301.1 *** SYSTEM FATAL MESSAGE 7301 (FMSFIO)

CANNOT CLOSE FORTRAN UNIT %1 USED FOR FMS.

7302.0 *** SYSTEM FATAL MESSAGE 7302 (LNNP1AD)

ORDER OF EIGENPROBLEM IS NON-POSITIVE
NORDER: %1

7303.0 *** SYSTEM FATAL MESSAGE 7303 (LNNP1AD)

INSUFFICIENT STORAGE FOR BLOCK SHIFTED LANCZOS.
WORKSPACE AVAILABLE = %1
WORKSPACE REQUIRED = %2

7304.0 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD)

IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM
DESCRIPTION OF PROBLEM TYPE NOT RECOGNIZED
INPUT: %1

7304.1 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD)

IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM
LEFT END POINT EQUALS RIGHT END POINT
INPUT: %1

7304.2 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD)

IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM
DESCRIPTION OF WHICH EIGENVALUES TO FIND NOT RECOGNIZED
INPUT: %1

7304.3 *** SYSTEM FATAL MESSAGE 7304 (LNNP1AD)

IMPROPER PARAMETER SPECIFICATION FOR EIGENPROBLEM
HIGHEST EIGENVALUES REQUESTED IN AN INTERVAL SPANNING ZERO -OR-
HIGHEST EIGENVALUES REQUESTED IN A NON FINITE INTERVAL -OR-
ALL EIGENVALUES REQUESTED IN A NON FINITE INTERVAL
WHICH : %1
LEFT END POINT : %2
RIGHT END POINT: %3

Main Index
 MSC Nastran Error Messages 793
Errors 7000 - 7999

7305.0 *** SYSTEM FATAL MESSAGE 7305 (LNNP1AD)

NOT ENOUGH TIME TO BEGIN EIGENANALYSIS

7306.0 *** USER FATAL MESSAGE 7306,

ATTEMPT TO PUNCH MORE THAN 99999 DMIG ENTRIES - CONTINUATION FIELD
OVERFLOW.

7307.0 *** USER FATAL MESSAGE 7307,

ILLEGAL VALUE FOR PARAMETER P4. DMIG TYPOUT = %1 REQUESTED FOR INPUT
MATRIX OF TYPE %2

7308.0 *** USER INFORMATION MESSAGE 7308 (NL2NON)

MODIFIED NOLIN1 REQUESTED BY USER

7309.0 *** SYSTEM FATAL MESSAGE 7309.

NLEMGD CALLED FOR ELEMENT TYPE =%1 SHOULD NOT HAVE HAPPENED.

7309.1 *** USER WARNING MESSAGE 7309 (NLEMG)

User information: THERE ARE MIXED ELEMENTS FOR ELEMENT TYPE %1.
NUMBER OF ELEMENTS WITH CONVENTIONAL NONLINEAR PROPERTIES: %2
NUMBER OF ELEMENTS WITH ADVANCED NONLINEAR PROPERTIES: %3

User action: SET NLMOPTS,SPROPMAP,2 IN BULK DATA TO CONVERT ALL ELEMENTS TO

ADVANCED PROPERTIES.

7310.0 *** USER INFORMATION MESSAGE 7310 (OFPH09)

REFERENCE GRID %1 WAS NOT FOUND.
ORIGIN OF ASSEMBLY BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE
LOCATION.

7310.1 *** USER INFORMATION MESSAGE 7310 (VECPRN)

ORIGIN OF SUPERELEMENT OR MODULE BASIC COORDINATE SYSTEM WILL BE USED
AS REFERENCE LOCATION.

7310.2 *** USER INFORMATION MESSAGE 7310 (VECPRN)

Main Index
 794 MSC Nastran Error Messages
Errors 7000 - 7999

REFERENCE GRID %1 WAS NOT FOUND FOR VECPLOT OPERATION.

ORIGIN OF SUPERELEMENT OR MODULE BASIC COORDINATE SYSTEM WILL BE USED
AS REFERENCE LOCATION.

7310.3 *** USER INFORMATION MESSAGE 7310 (VECPRN)

ORIGIN OF SUPERELEMENT OR MODULE BASIC COORDINATE SYSTEM WILL BE USED
AS REFERENCE LOCATION.
RESULTANTS ABOUT ORIGIN OF SUPERELEMENT OR MODULE BASIC COORDINATE
SYSTEM IN SUPERELEMENT OR MODULE BASIC SYSTEM COORDINATES.

7310.4 *** USER INFORMATION MESSAGE 7310 (VECPRN)

REFERENCE GRID %1 WAS NOT FOUND FOR VECPLOT OPERATION.
ORIGIN OF SUPERELEMENT OR MODULE BASIC COORDINATE SYSTEM WILL BE USED
AS REFERENCE LOCATION.
RESULTANTS ABOUT ORIGIN OF SUPERELEMENT OR MODULE BASIC COORDINATE
SYSTEM IN SUPERELEMENT OR MODULE BASIC SYSTEM COORDINATES.

7310.5 *** USER INFORMATION MESSAGE 7310 (VECPRN)

ORIGIN OF ASSEMBLY BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE
LOCATION.

7310.6 *** USER INFORMATION MESSAGE 7310 (VECPRN)

REFERENCE GRID %1 WAS NOT FOUND FOR VECPLOT OPERATION.
ORIGIN OF ASSEMBLY BASIC COORDINATE SYSTEM WILL BE USED AS REFERENCE
LOCATION.

7311.0 *** USER INFORMATION MESSAGE 7311

PID=%1 REQUEST PARALLEL PROCESSING FOR PCOPY MODULE.
NUMBER OF PROCESSORS AVAILABLE=%2
NUMBER OF PROCESSORS APPLIED=%3

7312.0 *** USER FATAL MESSAGE 7312 (RDINIC)

SCR300 SHOULD NOT BE USED AS A DBSET NAME, IT IS A SUBSET OF SCRATCH DBSET.

7313.0 *** USER INFORMATION MESSAGE 7313 (REIGL0)

Main Index
 MSC Nastran Error Messages 795
Errors 7000 - 7999

DESPITE NEGATIVE SYSTEM CELL 199 VALUE %1

CHOSEN MASS MATRIX WILL NOT BE LOADED IN MEMORY.
DECREASE ABSOLUTE VALUE OF MASSBUF OR INCREASE MEMORY

7314.0 *** USER INFORMATION MESSAGE 7314 (REIGL0)

MASS MATRIX IS NOT LOADED IN MEMORY WITH %1 GINO BUFFERS.
EITHER INCREASE MAGNITUDE OF SYSTEM CELL 199 OR SET TO ZERO TO FORCE IN
MEMORY

7315.0 *** USER INFORMATION MESSAGE 7315 (REIGL0)

MASS MATRIX IS FORCED IN MEMORY PER USER REQUEST MEMORY REDUCED BY %1
WORDS

7316.0 *** USER INFORMATION MESSAGE 7316 (REIGL0)

MASS MATRIX IS LOADED IN MEMORY PER USER REQUEST WITH %1 GINO BUFFERS.
MEMORY REDUCED BY %2 WORDS

7317.0 *** SYSTEM FATAL MESSAGE 7317.

INCORRECT NUMBER OF WORDS BEING TRANSMITTED FROM PHASE-1 ROUTINE FOR
ELEMENT ID =%1 WORDS THIS CALL =%2 ENTRY SIZE SHOULD =%3

7318.0 *** SYSTEM FATAL MESSAGE 7318.

PREVIOUS ELEMENT-ID TO ID =%1 DID NOT OUTPUT CORRECT NUMBER OF PHASE-1
WORDS.

7319.0 *** SYSTEM FATAL MESSAGE 7319.

INCORRECT CALL MADE TO SDR2WT UTILITY FOR ELEMENT ID =%1, PARM =%2

7320.0 ***SYSTEM FATAL MESSAGE 7321.

INCONSISTENT DATA DETECTED BETWEEN THE OES1A LAMINATE STRAIN AND OEF1A
ELEMENT FORCE DATABLOCKS

7321.0 *** USER INFORMATION MESSAGE 7321

DATA RECOVERY FOR %1 %2 IS NOW INITIATED.

7321.1 *** USER INFORMATION MESSAGE 7321

Main Index
 796 MSC Nastran Error Messages
Errors 7000 - 7999

SOLUTION SET DATA RECOVERY (SDISP, SVELO, SACCE, NLLOAD, MCFRA, MODALSE and
MODALKE) FOR %1 %2 IS NOW INITIATED.

7321.2 *** USER INFORMATION MESSAGE 7321

SOLUTION SET DATA RECOVERY (SVECTOR) FOR %1 %2 IS NOW INITIATED.

7322.0 *** USER FATAL MESSAGE 7322 (SEP2D)

SUBCASES FOR SUPERELEMENT %1 CONTAIN A MIXTURE OF ZERO AND NON-ZERO
LOAD SEQUENCE NUMBERS.

7323.0 *** USER FATAL MESSAGE 7323 (SEP2D)

SUBCASES FOR SUPERELEMENT %1 HAS A LOAD SEQUENCE NUMBER = %2 WHICH IS
OUT OF ORDER.

7324.0 *** USER FATAL MESSAGE 7324 (SEP2D)

SUBCASES FOR SUPERELEMENT %1 HAS A LOAD SEQUENCE NUMBER =%2 WHICH IS
GREATER THAN NUMBER OF LOADS.

7325.0 *** USER INFORMATION MESSAGE 7325

PROCESSING OF RESIDUAL STRUCTURE IS NOW INITIATED.

7325.1 *** USER INFORMATION MESSAGE 7325

PROCESSING OF SUPERELEMENT OR MODULE %1 IS NOW INITIATED.

7326.0 *** USER INFORMATION MESSAGE 7326

%1 SPARSE FACTOR MATRIX %2 IS MIGRATED TO V68 SPARSE FACTOR MATRIX FOR-
MAT.

7327.0 *** SYSTEM FATAL MESSAGE 7327 (USTSIL)

INCONSISTENT MAPPING DETECTED BETWEEN SIL TABLE AND USET RECORD.

7327.1 *** SYSTEM FATAL MESSAGE 7327 (FIXSIL)

INCONSISTENT MAPPING LENGTH DETECTED IN SILD RECORD.

7328.0 *** SYSTEM FATAL MESSAGE 7328 (USTSIL)

SET %1 CANNOT BE LOCATED IN USET MAPPING RECORD.

Main Index
 MSC Nastran Error Messages 797
Errors 7000 - 7999

7329.0 *** SYSTEM WARNING MESSAGE 7329 (MTGN12)

AVERAGE STRING LENGTH GIVEN DOES NOT CORRESPOND TO THE OTHER PROPER-
TIES OF THE MATRIX.

7330.0 *** USER WARNING MESSAGE 7330 (TIMTS3)

UNABLE TO FIND A MATCHING MACH AND/OR KONFIG!
MACHINE DESCRIPTION SECTION FILLED WITH BLANKS.

7331.0 *** SYSTEM FATAL MESSAGE 7331 (FMSGET)

OUTPUT RECORD NUMBER %1 GIVEN RECORD TYPE %2 IS MISMATCHED FOR %3 DATA
RECORD.
%4%5

7331.1 *** SYSTEM FATAL MESSAGE 7333 (FMSPUT)

INPUT RECORD NUMBER %1 HAS EXCEEDED TOTAL NUMBER OF RECORDS DEFINED
ON THE HEADER.
CONTENT OF HEADER RECORD:
"%2"%3

7332.0 *** SYSTEM FATAL MESSAGE 7332 (FMSGET)

OUTPUT RECORD NUMBER %1 REQUESTED NUMBER OF DATA %2 HAS EXCEEDED
RECORD SIZE FOR %3 DATA RECORD.
%4%5

7333.0 *** SYSTEM FATAL MESSAGE 7332 (FMSGET)

OUTPUT RECORD NUMBER %1 HAS EXCEEDED TOTAL NUMBER OF RECORDS DEFINED
ON HEADER.
CONTENT OF HEADER RECORD:
%2%3

7334.0 *** SYSTEM FATAL MESSAGE 7334 (FMSGET)

END OF FILE HIT WHILE READING RECORD NUMBER %1 OF %2 DATA RECORD.
CONTENT OF HEADER RECORD:
%3%4

7335.0 *** SYSTEM FATAL MESSAGE 7335 (FMSGET)

Main Index
 798 MSC Nastran Error Messages
Errors 7000 - 7999

HEADER TYPE %1 MAY NOT HAVE DATA RECORDS

CONTENT OF HEADER RECORD:
%2%3

7336.0 *** SYSTEM FATAL MESSAGE 7336 (FMSPUT)

INVALID DATA TYPE FOUND IN HEADER, TYPE = %1 CONTENT OF HEADER RECORD:
"%2"%3

7337.0 *** SYSTEM FATAL MESSAGE 7337 (FMSPUT)

INPUT RECORD NUMBER %1 GIVEN RECORD TYPE %2 IS MISMATCHED FOR %3 DATA
RECORD.
"%4"%5

7338.0 *** SYSTEM FATAL MESSAGE 7338 (FMSPUT)

INPUT RECORD NUMBER %1 GIVEN AMOUNT OF DATA %2 IS MISMATCHED FOR %3
DATA RECORD.
CONTENT OF HEADER RECORD:
"%4"%5

7339.0 *** USER FATAL MESSAGE 7339 (NLTINT)

METHOD = AUTO OR TSTEP ON THE TSTEPNL BULK DATA ENTRY IS SPECIFIED ALONG
WITH CBUSH1D ELEMENTS(S). THIS IS NOT ALLOWED.

User action: SPECIFY METHOD = ADAPT ON THE TSTEPNL ENTRY.

7340.0 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

ERROR HANDLER (LNNHERR) USED IMPROPERLY
MODE = %1 FROM %2

7340.1 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

ERROR HANDLER (LNNHERR) MESSAGE LIMIT EXCEEDED
ONE OR MORE MESSAGES SUPPRESSED

7340.2 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

Main Index
 MSC Nastran Error Messages 799
Errors 7000 - 7999

WARNING REPORTED BY SUBROUTINE %1 (IER= %2)

User information:%3

7340.3 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

INPUT ARGUMENT ERROR REPORTED BY SUBROUTINE %1 (IER= %2)

User information:%3

7340.4 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

INPUT ARGUMENT ERROR REPORTED BY SUBROUTINE %1
%2 WORDS OF WORKING STORAGE NEEDED (IER= %3)

User information:%4

7340.5 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

PROCESS ERROR REPORTED BY SUBROUTINE %1 (IER= %2)

User information:%3

7340.6 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

ABOVE CALLED BY SUBROUTINE %1 (IER= %2)

User information:%3

7340.7 *** SYSTEM FATAL MESSAGE 7340 (LNNHERR)

ABOVE CALLED BY SUBROUTINE %1
ERROR WAS UNEXPECTED (IER =%2)

User information:%3

7340.8 *** SYSTEM FATAL MESSAGE 7340

STAGE ERROR.

7340.9 *** SYSTEM FATAL MESSAGE 7340

ILLEGAL PROBLEM TYPE SPECIFICATION.

Main Index
 800 MSC Nastran Error Messages
Errors 7000 - 7999

7340.10 *** SYSTEM FATAL MESSAGE 7340

ILLEGAL FINITE ENDPOINTS.

7340.11 *** SYSTEM FATAL MESSAGE 7340

REQUESTED HIGHEST MODES IN INTERVAL SPANNING ZERO.

7340.12 *** SYSTEM FATAL MESSAGE 7340

INSUFFICIENT DYNAMIC MEMORY FOR FACTORIZATION.

7340.13 *** SYSTEM FATAL MESSAGE 7340

INTERNAL ERROR DURING FACTORIZATION.

7340.14 *** SYSTEM FATAL MESSAGE 7340

NOT ENOUGH TIME TO GET STARTED.

7340.15 *** SYSTEM FATAL MESSAGE 7340

STARTING BLOCK I/O ERROR.

7340.16 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR ON FACTORIZATION SEQUENTIAL SAVE/RESTART FILES.

7340.17 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR ON FACTORIZATION WORD ADDRESSABLE FILES.

7340.18 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR OPENING FIRST SEQUENTIAL FILE.

7340.19 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR OPENING SECOND SEQUENTIAL FILE.

7340.20 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR OPENING DIRECT ACCESS FILE.

7340.21 *** SYSTEM FATAL MESSAGE 7340

INSUFFICIENT STORAGE ENCOUNTERED BY SUBROUTINE HDSER1.

Main Index
 MSC Nastran Error Messages 801
Errors 7000 - 7999

7340.22 *** SYSTEM FATAL MESSAGE 7340

TRIDIAGONAL QL DID NOT CONVERGE.

7340.23 *** SYSTEM FATAL MESSAGE 7340

NUMBER OF COMPUTED EIGENVALUES EXCEED ALLOCATED STORAGE.

7340.24 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR ENCOUNTERED DURING HDSER1.

7340.25 *** SYSTEM FATAL MESSAGE 7340

SVD QL DID NOT CONVERGE.

7340.26 *** SYSTEM FATAL MESSAGE 7340

GRAM-SCHMIDT DID NOT CONVERGE.

7340.27 *** SYSTEM FATAL MESSAGE 7340

REPEATED SINGULAR MATRIX -- PROBABLY ILL-POSED PROBLEM.

7340.28 *** SYSTEM FATAL MESSAGE 7340

NUMBER OF TRUST REGION EXCEED ALLOCATED STORAGE.

7340.29 *** SYSTEM FATAL MESSAGE 7340

FACTORIZATION RESTORATION ERROR.

7340.30 *** SYSTEM FATAL MESSAGE 7340

INCONSISTENT TREATMENT OF NUMBER OF EIGENVALUES IN FINITE INTERVAL.

7340.31 *** SYSTEM FATAL MESSAGE 7340

COULD NOT COMPUTE ZERO EIGENVALUES FOR A BUCKLING CASE.

7340.32 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR CLOSING FIRST SEQUENTIAL FILE.

7340.33 *** SYSTEM FATAL MESSAGE 7340

I/O ERROR CLOSING SECOND SEQUENTIAL FILE.

Main Index
 802 MSC Nastran Error Messages
Errors 7000 - 7999

7340.34 *** SYSTEM FATAL MESSAGE 7340 (LNNRIGL)

UNKNOWN INTERNAL ERROR OCCURRED.

7341.0 *** USER FATAL MESSAGE 7341 (SEPMA1)

THE SEIDA FIELD ON THE %1 BULK DATA ENTRY REFERENCES A NON-PARTITIONED
SUPERELEMENT OR MODULE ID=%2.

7342.0 *** USER FATAL MESSAGE 7342 (PREMAT)

THE FIRST POINT (X1,Y1) SPECIFIED ON THE TABLES1 BULK DATA ENTRY ID = %1 IS
NOT LOCATED AT THE ORIGIN OF THE STRESS-STRAIN CURVE.

7342.1 *** USER FATAL MESSAGE 7342 (PREMAT)

MATS1 ID = %1 ENTRY WITH NLELAST REFERENCES A TABLES1 ENTRY WHICH DEFINES
A CURVE THAT DOES NOT PASS THROUGH THE ORIGIN.

User information: FOR CURVES DEFINED IN THE FIRST QUADRANT THE ORIGIN MUST BE
DEFINED.

7342.2 *** USER WARNING MESSAGE 7342 (PREMAT)

TABLED5 ID = %1 ENTRY USAGE DETECTED. TEMP ID and FREQUENCY MUST NOT BE
ZERO.

User information: CHECK INPUT. USE TABLED1, TABLED2, TABLED3 or TABLED4 instead.

7342.3 *** USER FATAL MESSAGE 7342 (PREMAT)

TABLED5 ID = %1 ENTRY REFERS TO ANOTHER TABLED5 ID = %2.

User information: TABLED5 MAY REFERENCE TABLED1, TABLED2, TABLED3 or TABLED4

only. CHECK INPUT.

7343.0 *** USER FATAL MESSAGE 7343,

Main Index
 MSC Nastran Error Messages 803
Errors 7000 - 7999

THE ERROR VALUE FOR RBE3 ELEMENT %1 IS %2, WHICH EXCEEDS THE TEST CRITE-
RION OF %3.

User information: THE RECIPROCAL CONDITION NUMBER OF THE EQUILIBRIUM MATRIX

IS %4.

User action: ADD MORE DOFS TO THE CONNECTED POINTS TO INSURE THAT THEY CAN
CONSTRAIN ALL 6 RIGID BODY MODES OF THE ELEMENT.

7343.1 *** USER WARNING MESSAGE 7343,

OLD RBE3 METHOD OF ANALYSIS WAS USED DUE TO SYS(393) =%1
THE ANALYSIS MAY YIELD INCORRECT RESULTS.

7343.2 *** USER WARNING MESSAGE 7343,

THE ERROR VALUE FOR MONDSP1 ENTRY %1 IS %2, WHICH EXCEEDS THE TEST CRITE-
RION OF %3.

User information: THE RECIPROCAL CONDITION NUMBER OF THE EQUILIBRIUM MATRIX

IS %4.

User action: ADD MORE DOFS TO THE CONNECTED POINTS TO INSURE THAT THEY CAN
CONSTRAIN ALL 6 RIGID BODY MODES OF THE ELEMENT.

7344.0 *** SYSTEM WARNING MESSAGE 7344 (DFMFRD)

IFLAG =%1
PIVOT%2 HAS DIFFERENT SIGN FROM THE PREVIOUS ONE

7345.0 *** SYSTEM FATAL MESSAGE 7345 (FIXSIL)

G-SET SIL ID%1 CANNOT BE LOCATED IN SILD MAPPING RECORD.

7346.0 *** SYSTEM WARNING MESSAGE 7346 (SEPLT3)

SUPERELEMENT OR MODULE ID = %1 CONTAINS INVALID DATA INFORMATION.
(DATA TYPE = %2 COLUMN SIZE = %3 LUSET = %4 GSIZE= %5)

7347.0 *** SYSTEM WARNING MESSAGE 7347 (SEPLT3)

ROW NUMBER %1 EXCEEDED MAXIMIUM SIZE %2

Main Index
 804 MSC Nastran Error Messages
Errors 7000 - 7999

7348.0 *** SYSTEM FATAL MESSAGE 7348

NUMBER OF GRID ID-S CONTAINED IN TEMPERATURE SET %1 XCEEDS NUMBER OF
GRID POINTS DEFINED

7349.0 *** SYSTEM FATAL MESSAGE 7349

TEMPERATURE TYPE =%1
IS NOT YET IMPLEMENTED. ELEMENT TYPE CONCERNED = %2

7350.0 *** USER FATAL MESSAGE 7350.

TEMPP2 DATA MAY NOT BE USED FOR ELEMENTS OF THE TYPE WHICH ID = %1 IS OF.

7351.0 *** USER FATAL MESSAGE 7367 (MKCNT)

THE CONTROL DEVICE DEFINED WITH LABEL %1 ON AE%2 ENTRY ID = %3 IS DUPLI-
CATED ON CONTROL DEVICE AE%4 ENTRY ID = %5.

User action: RENAME THE LABEL ON ONE OF THE CONTROL DEVICES.

7352.0 *** USER WARNING MESSAGE 6173. (EQD4D)

K6ROT STIFFNESS WILL BE ADDED TO MEMBRANE ELEMENTS DUE TO SYSTEM(433) =
%1
THE ANALYSIS MAY YIELD INCORRECT RESULTS.

7353.0 *** SYSTEM INFORMATION MESSAGE 7353 (PXINIT)

PID =%1 REQUEST INITIALIZATION THE EXECUTIVE AREAS FOR %2 PARALLEL PRO-
CESSES

7354.0 *** SYSTEM WARNING MESSAGE 7354

IN TIME_TEST_4
UNABLE TO FIND A MATCHING MACH AND/OR KONFIG!
MACHINE DESCRIPTION SECTION FILLED WITH BLANKS.

7355.1 *** SYSTEM FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
FACILITY NOT AVAILABLE ON THIS PLATFORM.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

Main Index
 MSC Nastran Error Messages 805
Errors 7000 - 7999

7355.2 *** USER FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
NO PROGRAM NAME SPECIFIED OR PROGRAM NAME IS BLANK.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.3 *** USER FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
REQUESTED PROGRAM COULD NOT BE FOUND.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.4 *** SYSTEM FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
SIGNAL HANDLING FAILED WHILE ATTEMPTING TO RUN SPECIFIED PROGRAM.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.5 *** SYSTEM FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
UNABLE TO CREATE A NEW PROCESS. SYSTEM LIMITS MAY HAVE BEEN EXCEEDED.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.6 *** USER FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
PROGRAM HAS TIMED OUT.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.7 *** SYSTEM FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
UNEXPECTED STATUS RETURNED WHILE WAITING FOR PROGRAM COMPLETION.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.8 *** SYSTEM FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
ACCESS DENIED TO REQUESTED PROGRAM OR IT IS NOT EXECUTABLE.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.9 *** SYSTEM FATAL MESSAGE 7355 (ISHELL)

Main Index
 806 MSC Nastran Error Messages
Errors 7000 - 7999

ISHELL PROCESSING FAILED.

UNABLE TO ACQUIRE DYNAMIC MEMORY TO HOLD COMPLETE COMMAND (MALLOC
FAILED).
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7355.10 *** SYSTEM FATAL MESSAGE 7355 (ISHELL)

ISHELL PROCESSING FAILED.
UNABLE TO CREATE COMMUNICATIONS PIPE WITH REQUESTED PROGRAM.
PROGRAM NAME IS '%1', TIMEOUT (SYS275) VALUE IS %2.

7356.0 *** SYSTEM FATAL MESSAGE 7356 (GICOMD)

SPLINE %1 FAILED TO CONVERGE IN EIGEN ANALYSIS. UNABLE TO OBTAIN A LEAST
SQUARES PLANE.
User action: USE TPS METHOD.

7357.0 *** SYSTEM INFORMATION MESSAGE 7357 (GICOMD)

SPLINE %1 IS COMPRISED OF A SET OF COPLANAR GRID POINTS. TPS METHOD
REVERTS TO IPS FOR THIS CASE.

7358.0 *** USER FATAL MESSAGE 7358 (GICOMD)

SPLINE %1 IS COMPRISED OF A SET OF COLLINEAR GRID POINTS.

User action: MODIFY THE GRIDS SO THEY ARE NOT COLLINEAR.

7358.1 *** SYSTEM INFORMATION MESSAGE 7358 (GICOMD)

SPLINE %1 IS COMPRISED OF A SET OF COLLINEAR GRID POINTS.

User information: SMOOTHING PARAMETER DZ MAY ALLOW SOLUTION.

7358.2 *** USER FATAL MESSAGE 7358 (CRBMDD)

ON SPLINE7 BULK DATA ENTRY ID= %1, THE PROGRAM CANNOT FIND ANY NON-
COLINEAR INDEPENDENT GRIDS.

7358.3 *** USER FATAL MESSAGE 7358 (CRPMDD)

Main Index
 MSC Nastran Error Messages 807
Errors 7000 - 7999

ON SPLINE6 BULK DATA ENTRY ID= %1, THE PROGRAM CANNOT FIND ANY NON-
COLINEAR INDEPENDENT GRIDS.

User information: CHANGE %2 FOR %3 to %4.

7358.4 *** USER FATAL MESSAGE 7358 (CRPMDD)

ON SPLINE6 BULK DATA ENTRY ID= %1, THE PROGRAM CANNOT FIND ANY NON-
COLINEAR INDEPENDENT GRIDS.

User information: CHANGE %2D FOR INDEPENDENT NODES.

7358.5 *** USER FATAL MESSAGE 7358 (GIPBRD)

SPLINE METRICS ARE BEING REQUESTED BUT THESE METRICS ARE NOT PROVIDED
FOR THE %1 TYPE.

7359.0 *** USER FATAL MESSAGE 7359 (GICOMD)

SPLINE %1 CONNECTS TO ONLY ONE STRUCTURAL GRID POINT.

User action: ADD GRID POINTS OR USE SPLINE2 WITH COUPLED ROTATIONS.

7360.0 *** USER INFORMATION MESSAGE 7360 (DOIT)

UNABLE TO PROCESS USER SPECIFIED EXTENSION.
COMMAND PROCESSOR NOT FOUND FOR EXTENSION '%1'
PROCESSOR NAME IS '%2'.

7361.0 *** USER INFORMATION MESSAGE 7361 (DOIT)

UNABLE TO ACQUIRE DYNAMIC MEMORY TO HOLD EXTENSIONS TABLE.
SPACE REQUESTED IS %1 BYTES.
INTERNAL TABLE WILL BE USED.

7362.0 *** USER INFORMATION MESSAGE 7362 (DOIT)

THE COMPLETE ISHELL COMMAND IS: %1

7363.0 *** SYSTEM FATAL MESSAGE 7363 (FGNFRD)

Main Index
 808 MSC Nastran Error Messages
Errors 7000 - 7999

ERROR READING THE FACTOR MATRIX WITH %1. REQUESTED %2 COLUMNS, READ %3
COLUMNS.

User action: DESELECT THE SUPERMODULE BY SETTING PARAM,SM,NO IN THE BULK

DATA SECTION.

7364.0 *** SYSTEM FATAL MESSAGE 7364 (STATICS)

THE SUPERMODULES ARE NOT AVAILABLE WHEN THE FULL DMAP IS EXECUTED ON
EACH NODE.

User action: SET CHILD=YES ON THE SUBMITTAL LINE.

7365.0 *** SYSTEM WARNING MESSAGE 7365 (DISOFN)

ENCOUNTERED BAD KEY VALUE WHILE READING %1 FROM PARALLEL NODE %2

User information: CHECK TO SEE IF FILE IS CORRECT OFP FILE TYPE.

Programmers information: KEY = %3

7366.0 *** SYSTEM WARNING MESSAGE 7366 (DISOFG)

UNABLE TO TRANSFER DATABLOCK %1 FROM PARALLEL NODE %2
UNSUPPORTED OFP FILE TYPE %3

7367.0 *** USER FATAL MESSAGE 7367 (MKCNT)

THE CONTROL DEVICE DEFINED ON AE%1 ENTRY ID = %2 SPECIFIES LABEL INTERCPT.

User information: THE LABEL INTERCPT IS A RESERVED LABEL AND CANNOT BE USED
FOR ANY CONTROL DEVICES.

User action: RENAME THE LABEL ON CONTROL DEVICE AE%3 ENTRY ID= %4.

7368.0 *** USER WARNING MESSAGE 7368 (ADGDJX)

W2GJ WEIGHTING MATRIX HAS %1 COLUMNS.

User information: ONLY ITS FIRST COLUMN IS BEING USED AS THE (SINGLE) INTERCEPT
EFFECT IN THE DOWNWASH MATRIX.

Main Index
 MSC Nastran Error Messages 809
Errors 7000 - 7999

7369.0 *** USER FATAL MESSAGE 7369 (ADGDJX)

W2GJ WEIGHTING MATRIX IS OF SIZE %1 COLUMN(S) BY %2 ROWS.

User information: ITS NUMBER OF ROWS SHOULD BE EQUAL TO THE J-SET SIZE %3.

User action: INPUT THE W2GJ WEIGHTING MATRIX WITH ITS NUMBER OF ROWS EQUALS
TO %4.

7370.0 *** USER FATAL MESSAGE 7370 (CEAD)

INVALID METHOD = "%1" IS SPECIFIED FOR THE 4TH PARAMETER OF THE CEAD MOD-
ULE.

User information: VALID METHODS ARE "CLAN", "HESS", AND "SVD".

7371.0 *** SYSTEM FATAL MESSAGE 7371 (FREQ)

INSUFFICIENT SPACE FOR PROCESSOR MAP AND PERFORMANCE DATA. MCORE = %1,
NUMBER OF PROCESSORS = %2.

User action: LIMIT NUMBER OF PROCESSORS PARTICIPATING IN THE RUN TO %3.

7372.0 *** USER FATAL MESSAGE 7372 (APD1)

THE DATA DEFINED ON THE AEFACT ENTRY ID = %1 ASSOCIATED WITH CAERO%2
ENTRY ID = %3 IS INCONSISTENT.

User information: THE MINIMUM AND MAXIMUM PARAMETRIC COORDINATES CANNOT

BE EQUAL.

7373.0 *** SYSTEM FATAL MESSAGE 7373 (MKCSTA)

COORDINATE SYSTEM DATA BLOCKS ARE OF INCOMPATIBLE PRECISIONS TO BE
MERGED.
STRUCTURAL CSTM IS %1 PRECISION.
AERO CSTM IS %2 PRECISION.

7374.0 *** SYSTEM FATAL MESSAGE 7374 (MKCSTA)

Main Index
 810 MSC Nastran Error Messages
Errors 7000 - 7999

BOTH INPUT COORDINATE SYSTEMS AND OUTPUT COORDINATE SYSTEMS DATA

BLOCKS ARE NOT PURGED.

User information: IF THE OUTPUT COORDINATE SYSTEMS DATABLOCK IS NOT PURGED,

ONE OF THE INPUT DATA BLOCKS MUST BE PURGED.

7375.0 *** SYSTEM FATAL MESSAGE 7175 (MKCSTA)

STRUCTURAL CSTM SHOULD BE ADDED ONLY ONCE TO CSTMA.

7376.0 *** SYSTEM FATAL MESSAGE 7376 (MKCSTA)

COORDINATE SYSTEM ID %1 WAS FOUND IN TWO SEPARATE COORDINATE SYSTEMS
TABLES BUT THEY DO NOT DESCRIBE THE SAME COORDINATE SYSTEM.

User information: MERGING COORDINATE SYSTEMS TABLES WITH DUPLICATE COORDI-

NATE SYSTEM IDS IS ONLY SUPPORTED IF THE TWO COORDINATES SYSTEMS ARE
IDENTICAL

User action: INPUT UNIQUE COORDINATE SYSTEM IDS WHEN THE UNDERLYING COOR-
DINATE SYSTEMS DIFFER

7377.0 *** SYSTEM FATAL MESSAGE 7377 (ADCSTM)

GINO FILE TO STORE %1 RECORD IS NOT PROVIDED.

Programmer information: ADCSTM UTILITY IS CALLED BY %2

Programmer action: PRIOR TO CALL THE ADCSTM UTILITY, PROVIDE THREE OPEN-TO-
WRITE GINO FILES.

7378.0 *** SYSTEM FATAL MESSAGE 7378 (ADCSTM)

INPUT CSTM PRECISION %1 IS INVALID.
Programmer information: THE CSTM PRECISION SHOULD BE 1 or 2. ADCSTM UTILITY IS
CALLED BY %2

7379.0 *** SYSTEM FATAL MESSAGE 7379 (ADCSTM)

Main Index
 MSC Nastran Error Messages 811
Errors 7000 - 7999

INPUT COORDINATE SYSTEM %1 OF CONVECTIVE TYPE %2 HAS NO INDICES.

Programmer information: ADCSTM UTILITY IS CALLED BY %3

Programmer action: PROVIDE THE INDICES TO BUILD A CONVECTIVE COORDINATE SYS-

TEM.

7380.0 *** SYSTEM FATAL MESSAGE 7380 (MKCSTA)

COORDINATE SYSTEM ID %1 WAS FOUND IN BOTH COORDINATE SYSTEMS DATA
BLOCKS TO MERGE BUT DOES NOT DESCRIBE THE SAME COORDINATE SYSTEM.

User information: COORDINATE sYSTEM DATA BLOCKS TO MERGE CAN NOT HAVE CON-
FLICTED COORDINATE SYSTEMS IDS.

7381.0 *** USER FATAL MESSAGE 7381 (VSFSPC)

THE VIRTUAL SURFACE NUMBER=%1, SPECIFIED ON SPLINE6 BULK DATA ENTRY ID=%2,
IS NOT CONNECTED TO ANY STRUCTURAL POINT.

User information: THIS WILL CAUSE SINGULARITY IN THE SOLUTION.

7382.0 *** SYSTEM INFORMATION MESSAGE 7382 (CLASDD)

LARGEST NORMALIZED RESIDUAL FOR COMPLEX EIGENSOLUTION IS %1

7383.0 *** USER WARNING MESSAGE 7383 (GPJAC)

%1 ELEMENT ID =%2 HAS INVERTED GEOMETRY ON A %3.

User information: THIS CONDITION CAN CAUSE NON-PHYSICAL RESULTS.

7383.1 *** USER FATAL MESSAGE 7383 (GPJAC)

%1 ELEMENT ID =%2 HAS INVERTED GEOMETRY ON A %3.

User information: THIS CONDITION CAN CAUSE NON-PHYSICAL RESULTS.

7384.0 *** USER FATAL MESSAGE 7384 (DOPR3N)

DRESP2 ENTRY ID = %1 REFERENCES ITSELF.

Main Index
 812 MSC Nastran Error Messages
Errors 7000 - 7999

7385.0 *** USER FATAL MESSAGE 7385 (DOPR1C)

THE PROPERTY NAME (FIFTH FIELD) ON DVPREL1 ENTRY ID = %1 CONTAINS INTEGER
DATA FOR A PBEAML, PBRSECT OR PBMSECT PROPERTY ENTRY.

User action: FOR PBEAML ENTRIES, SPECIFY CHARACTER STRINGS SUCH AS DIM1, DIM2,
etc.
FOR PBRSECT/PBMSECT ENTRIES, SPECIFY CHARACTER STRINGS SUCH AS H, W or T.

7386.0 *** USER WARNING MESSAGE 7386.0 (CLASDD)

THE ND FIELD (NUMBER OF DESIRED ROOTS) ON THE EIGC BULK DATA ENTRY IS
BLANK OR IS SET TO ZERO.

User action: VERIFY THAT ND IS SET CORRECTLY. ND MUST BE SET IN FIELD 8 OF THE
EIGC BULK DATA ENTRY.
IF A CONTINUATION ENTRY IS USED, ND MUST BE SET IN FIELD 8 OF EACH CONTINU-
ATION ENTRY.

User information: THE NUMBER OF DESIRED ROOTS WILL BE SET TO %1, WHICH IS
TWICE THE INITIAL BLOCK SIZE.

7386.1 *** USER WARNING MESSAGE 7386.1 (CLASDD)

THE 6TH PARAMETER OF THE CEAD MODULE (NUMBER OF DESIRED ROOTS) IS NOT
SPECIFIED OR IS SET TO ZERO.

User information: THE NUMBER OF DESIRED ROOTS WILL BE SET TO %1, WHICH IS
TWICE THE INITIAL BLOCK SIZE.

7386.2 *** USER WARNING MESSAGE 7386.2 (LNNRIGL)

THE ND, V1, AND V2 FIELDS ON THE EIGRL BULK DATA ENTRY ARE ALL BLANK OR SET
TO ZERO.

User action: VERIFY THAT ND,V1, AND V2 ARE SET IN THE APPROPRIATE FIELDS:
V1 MUST BE SET IN FIELD 3, V2 MUST BE SET IN FIELD 4, AND
ND MUST BE SET IN FIELD 5 OF THE EIGRL BULK DATA ENTRY.

User information: THE NUMBER OF DESIRED ROOTS (ND) WILL BE SET TO %1.

Main Index
 MSC Nastran Error Messages 813
Errors 7000 - 7999

7386.3 *** USER WARNING MESSAGE 7386.3 (LNNRIGL)

THE ND, F1, AND F2 FIELDS ON THE EIGR BULK DATA ENTRY ARE ALL BLANK OR SET
TO ZERO.

User action: VERIFY THAT ND,F1, AND F2 ARE SET IN THE APPROPRIATE FIELDS:
F1 MUST BE SET IN FIELD 4, F2 MUST BE SET IN FIELD 5, AND
ND MUST BE SET IN FIELD 7 OF THE EIGR BULK DATA ENTRY.

User information: THE NUMBER OF DESIRED ROOTS (ND) WILL BE SET TO %1.

7386.4 *** USER WARNING MESSAGE 7386 (LNNRIGL)

THE 8TH, 9TH, AND 11TH PARAMETERS OF THE READ MODULE (F1,F2, AND ND RESPEC-
TIVELY) ARE NOT SPECIFIED OR ARE SET TO ZERO.

User information: THE NUMBER OF DESIRED ROOTS (ND) WILL BE SET TO %1.

7387.0 *** SYSTEM FATAL MESSAGE 7387 (SITDRV)

DISTRIBUTED PARALLEL PROCESSING HAS BEEN REQUESTED WITH PURGED PARTI-
TIONING INFORMATION.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7388.0 *** SYSTEM FATAL MESSAGE 7388 (SITDRV)

NUMBER OF LOCAL ROWS IS INCONSISTENT BETWEEN SYSTEM MATRIX AND PARTI-
TIONING INFORMATION.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7389.0 *** SYSTEM FATAL MESSAGE 7389 (DDSMAP)

THE GLOBAL ROW NUMBER %1 ASSIGNED TO LOCAL ROW NUMBER %2 IS OUT OF
RANGE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7390.0 *** SYSTEM FATAL MESSAGE 7390 (DDSMAP)

Main Index
 814 MSC Nastran Error Messages
Errors 7000 - 7999

AN EEQIND INDEX FOR THE GLOBAL ROW NUMBER %1 IS OUT OF RANGE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7391.0 *** SYSTEM FATAL MESSAGE 7391 (DDSMAP)

THE ID OF ONE OF THE PROCESSORS SHARING GLOBAL ROW NUMBER %1 IS OUT OF
RANGE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7392.0 *** SYSTEM FATAL MESSAGE 7392 (DDSMAP)

THIS PROCESSOR (LPID = %1) IS NOT A SHAREHOLDER OF ROW %2 IN ITS LOCAL KFF.
THE GLOBAL ROW NUMBER IS %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7393.0 *** SYSTEM FATAL MESSAGE 7393 (DDSMAP)

THE GLOBAL ROW NUMBER %1 IS NOT SHARED BY ANY PROCESSOR.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7394.0 *** SYSTEM FATAL MESSAGE 7394 (DDSMAP)

THE SIZE OF THE LOCAL O-SET %1, THE LOCAL A-SET %2 AND THE LOCAL F-SET %3 DO
NOT MATCH.
A POSSIBLE REASON IS THAT THE LOCAL O-SET DOFS ARE NOT NUMBERED AFTER THE
LOCAL A-SET DOFS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7395.0 *** SYSTEM FATAL MESSAGE 7395 (DDSMAP)

INCONSISTENCY IN PARTITIONED A-SET.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7396.0 *** SYSTEM FATAL MESSAGE 7396 (DDSMAP)

Main Index
 MSC Nastran Error Messages 815
Errors 7000 - 7999

THE GLOBAL ROW NUMBERS %1 AND %2 ASSIGNED TO LOCAL ROW NUMBERS %3 AND
%4 ARE NOT IN ASCENDING ORDER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7397.0 *** SYSTEM FATAL MESSAGE 7397 (DDSMAP)

THE GLOBAL A-SET INDICES %1 AND %2 ASSIGNED TO LOCAL A-SET INDICES %3 AND
%4 ARE NOT IN ASCENDING ORDER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7398.0 *** SYSTEM FATAL MESSAGE 7398 (DDSMAP)

TRANSLATION TO GLOBAL A-SET INDEX FAILED FOR LOCAL ROW INDEX %1.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT. GLOBAL A-SET INDEX
TRANSFORMATION IN DISDCMP HAS TO BE CHANGED.

7399.0 *** SYSTEM FATAL MESSAGE 7399 (DFMFRD)

PREDICTIVE SYMBOLIC PIVOTING CORRUPTED THE PERMUTATION ORDER FOR THE
DOFS TO BE DECOMPOSED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7400.0 *** SYSTEM FATAL MESSAGE 7400 (DFMFRD)

ERROR DURING NUMERIC ASSEMBLY OF INCORE STACK ELEMENT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7401.0 *** SYSTEM FATAL MESSAGE 7401 (DFMFRD)

ERROR DURING NUMERIC ASSEMBLY OF OUT-OF-CORE STACK ELEMENT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7402.0 *** SYSTEM FATAL MESSAGE 7402 (DFMFRD)

Main Index
 816 MSC Nastran Error Messages
Errors 7000 - 7999

ERROR DURING NUMERIC ASSEMBLY OF MATRIX ROWS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7403.0 *** SYSTEM FATAL MESSAGE 7403 (DFMFRD)

FRONT INDICES IN SCHUR COMPLEMENT ARE NOT IN ASCENDING ORDER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7404.0 *** SYSTEM FATAL MESSAGE 7404 (DFMFRD)

DEGREE OF FREEDOM %1 IS WRITTEN TO SCHUR COMPLEMENT, BUT SHOULD HAVE
BEEN DECOMPOSED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7405.0 *** SYSTEM FATAL MESSAGE 7405 (DFMFRD)

ACTUAL AND REQUESTED NUMBER OF DOFS TO BE DECOMPOSED AND NOT TO BE
DECOMPOSED DO NOT MATCH.
NTOTPV: %1, N-ICOMP: %2
NSCHUR: %3, ICOMP : %4

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7406.0 *** SYSTEM FATAL MESSAGE 7406 (DFMFRD)

NUMBER OF ASSEMBLED DEGREES OF FREEDOM %1 AND NUMBER OF DEGREES OF
FREEDOM IN LOCAL MATRIX %2 DO NOT MATCH.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7407.0 *** SYSTEM FATAL MESSAGE 7407 (DFMSA)

PARTITIONING VECTOR FOR PARTIAL DECOMPOSITION IS INCORRECT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7408.0 *** SYSTEM INFORMATION MESSAGE 7408 (DFMSYN)

SINCE SYSTEM(286) WAS SET BY THE USER TO A VALUE OF 5, FILL-IN RE-ORDERING WAS
SKIPPED IN THE SYMBOLIC PHASE OF SPARSE DECOMPOSITION.

Main Index
 MSC Nastran Error Messages 817
Errors 7000 - 7999

7409.0 *** USER WARNING MESSAGE 7409 (DOPR1J)

EQUATION: E = 2*(1+NU)*G MAY BE VIOLATED FOR MAT1 ENTRY ID = %1 REFERRED BY
DVMREL1 AND/OR DVMREL2 ENTRIES.

User information: THE CORRESPONDING SENSITIVITY COEFFICIENTS MAY BE INACCU-

RATE.

User action: LEAVE AT LEAST ONE OF THE THREE VALUES (E, G, NU) BLANK AND UNRE-
FERRED BY A DVMREL1/DVMREL2 ENTRIES

7409.1 *** USER WARNING MESSAGE 7409 (DOPR1J)

EQUATION: BULK = RHO*C**2 MAY BE VIOLATED FOR MAT10 ENTRY ID = %1 REFERRED
BY DVMREL1 AND/OR DVMREL2 ENTRIES.

User information: THE CORRESPONDING SENSITIVITY COEFFICIENTS MAY BE INACCU-

RATE.

User action: LEAVE AT LEAST ONE OF THE THREE VALUES (BULK, RHO, C) BLANK AND
UNREFERRED BY A DVMREL1/DVMREL2 ENTRIES

7409.2 *** USER WARNING MESSAGE 7409 (DOP1CA)

DVMREL1 or DVMREL2 ENTRY ID %1 REFERENCES MAT ID %2 THAT EXCEEDS 8 DIGITS.

User action: Use a MAT ID with less than 9 digits.

7410.0 *** SYSTEM FATAL MESSAGE 7410 (DISDAF)

PROGRAMMER ERROR IN PANEL TO PROCESSOR ASSIGNMENT CALCULATION.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7411.0 *** SYSTEM FATAL MESSAGE 7411 (DISDAF)

PROGRAMMER ERROR IN INTERNAL LIST CALCULATION (FLLST).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 818 MSC Nastran Error Messages
Errors 7000 - 7999

7412.0 *** USER FATAL MESSAGE 7412 (SEQP)

MODEL PARTITIONING WAS REQUESTED BY SETTING %1 = %2, HOWEVER, THE NUM-
BER OF PROCESSORS REQUESTED IS %3.

User action:
1. DESELECT THE DOMAIN DECOMPOSITION METHOD BY SETTING OLDSEQ TO A
VALID VALUE FOR SERIAL RUNS ( -1 THRU 8) OR
2. SPECIFY MORE PROCESSORS TO PARTICIPATE IN THE RUN.

7413.0 *** SYSTEM FATAL MESSAGE 7413 (DISDCM1)

PROGRAMMER ERROR: LENGTH OF HEADER OF STACK FACTOR DATA STRUCTURE IS
INSUFFICIENT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7414.0 *** SYSTEM FATAL MESSAGE 7414 (DISDCM1)

PROGRAMMER ERROR: NGASET OR NCORE EXCEED MAXINT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7415.0 *** SYSTEM FATAL MESSAGE 7415 (DISDRF)

SIZE OF CURRENT PANEL EXCEEDS MAXIMUM VALUE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7416.0 *** SYSTEM FATAL MESSAGE 7416 (DISDRF)

PROGRAMMER ERROR: INVALID NPIV VALUE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7417.0 *** SYSTEM FATAL MESSAGE 7417 (DISDRF)

PROGRAMMER ERROR: ERROR WHEN PUSHING NEW INCORE STACK ELEMENT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7418.0 *** SYSTEM FATAL MESSAGE 7418 (DISDRF)

Main Index
 MSC Nastran Error Messages 819
Errors 7000 - 7999

INTERNAL STACK FOR DISTRIBUTED DECOMPOSITION IS FULL.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7419.0 *** SYSTEM FATAL MESSAGE 7419 (DISDFO)

PROGRAMMER ERROR: %1 MORE WORDS NEEDED FOR MERGING INDICES OF STACK
ELEMENTS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7420.0 *** SYSTEM FATAL MESSAGE 7420 (DISDFO)

PROGRAMMER ERROR: %1 BIGGER THAN NGASET.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7421.0 *** SYSTEM FATAL MESSAGE 7421 (SEQP)

%1 CARDS ARE PRESENT IN THE BULK DATA SECTION. THEY ARE NOT SUPPORTED BY
THE DOMAIN DECOMPOSITION METHOD.

User action: PLEASE TAKE ONE OF THE FOLLOWING ACTIONS:

1. DESELECT THE DOMAIN DECOMPOSITION METHOD BY REMOVING DMP= FROM
THE SUBMITTAL LINE.
2. REMOVE ALL CARDS OF THAT TYPE FROM THE BULK DATA SECTION.

7422.0 *** SYSTEM FATAL MESSAGE 7422 (DISDFM)

PROGRAMMER ERROR: UNABLE TO FIND ALL STACK ELEMENTS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7423.0 *** SYSTEM FATAL MESSAGE 7423 (SEQP)

A MALLOC INSIDE THE AUTOMATIC MODEL PARTITIONER WAS UNSUCCESSFUL IN
ALLOCATING %1 K BYTES IN MEMORY.

User action: DECREASE MEMORY GIVEN ON THE MSC NASTRAN SUBMITTAL LINE.
REPEAT DECREASE!

Main Index
 820 MSC Nastran Error Messages
Errors 7000 - 7999

7424.0 *** SYSTEM FATAL MESSAGE 7424 (SEQP)

PROCESSOR %1 DID NOT READ THE %2 RECORD FROM BNDFIL, IT READ THE RECORD
OF DOMAIN %3 INSTEAD.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7425.0 *** SYSTEM FATAL MESSAGE 7425 (DISDLR)

GETSEG RETURNED %1 TERMS, BUT %2 TERMS WERE EXPECTED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7426.0 *** SYSTEM FATAL MESSAGE 7426 (DISDLR)

RECEIVED %1 WORDS, BUT %2 WORDS WERE EXPECTED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7427.0 *** SYSTEM FATAL MESSAGE 7427 (DISEQI)

LOCAL TO GLOBAL MAP ENTRIES FOR LOCAL A-SET ARE NOT IN ASCENDING ORDER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7428.0 *** SYSTEM FATAL MESSAGE 7428 (DISERD)

PROGRAMMER ERROR %1.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7429.0 *** SYSTEM FATAL MESSAGE 7429 (DISERD)

PROGRAMMER ERROR: NUMBER OF ROWS IN CURRENT PANEL %1 IS BIGGER THAN
THE MAXIMUM EXPECTED VALUE %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7430.0 *** SYSTEM FATAL MESSAGE 7430 (DISERD)

PROGRAMMER ERROR: ACTUAL UPDATE RANK IS 0.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 MSC Nastran Error Messages 821
Errors 7000 - 7999

7431.0 *** SYSTEM FATAL MESSAGE 7431 (DISMRD)

BLOCK SIZE %1 IS NOT SUPPORTED YET.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7432.0 *** SYSTEM FATAL MESSAGE 7432 (DISMRD)

ERROR READING NEXT FRONT. NFRONT = %1, NROWS = %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7433.0 *** SYSTEM FATAL MESSAGE 7433 (SEQP)

THE NUMBER OF GLOBAL BOUNDARY GRID POINTS DIFFERS ON EQUATION MAP (%1)
AND ON BOUNDARY FILE (%2).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7434.0 *** SYSTEM FATAL MESSAGE 7434 (DISMRD)

%1 FRONT INDEX %2 IS OUT OF RANGE OR NOT IN ORDER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7435.0 *** SYSTEM FATAL MESSAGE 7435 (DISMRD)

ERROR IN SKIPPING ROWS IN CURRENT FRONT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7436.0 *** SYSTEM FATAL MESSAGE 7436 (DISMRD)

FRONT INDEX %1 AND CURRENT GLOBAL A-SET INDEX %2 DO NOT MATCH.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7437.0 *** SYSTEM FATAL MESSAGE 7437 (DISMRD)

READ %1 TERMS, BUT %2 TERMS WERE %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 822 MSC Nastran Error Messages
Errors 7000 - 7999

7438.0 *** SYSTEM FATAL MESSAGE 7438 (DISPRD)

PIVOTING REQUIRED.

User action:
1. CHECK MODEL, OR
2. USE PARAM,HLPMETH,1, OR
3. CHANGE TO SERIAL EXECUTION.

7439.0 *** SYSTEM FATAL MESSAGE 7439 (DISSTI)

FRONT SIZE IN SCHUR COMPLEMENT (INPUT DATA BLOCK KTT) IS BIGGER THAN
EXPECTED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7440.0 *** SYSTEM FATAL MESSAGE 7440 (DDFBRD)

ERROR IN ASSIGNMENT OF PANEL %1 IN FRONT %2 TO PROCESSOR %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7441.0 *** SYSTEM FATAL MESSAGE 7441 (DDFBRD)

SIZE MISMATCH IN PANEL %1 OF FRONT %2. EXPECTED DIMENSIONS ARE %3 AND %4,
ACTUAL DIMENSIONS ARE %5 AND %6.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7442.0 *** SYSTEM FATAL MESSAGE 7442 (DDFBRD)

NUMBER OF TERMS READ IN PANEL %1 IS %2, BUT %3 WERE EXPECTED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7443.0 *** SYSTEM FATAL MESSAGE 7443 (SEQP)

THE PARTITIONING VECTOR CREATED TO SPECIFY THE LOCAL BOUNDARY GRIDS IS
INCONSISTENT WITH THE NUMBER OF DEGREES OF FREEDOM ON THE LOCAL
BOUNDARY (%1). THE NUMBER OF NONZERO TERMS IN THE PARTITIONING VECTOR
IS %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 MSC Nastran Error Messages 823
Errors 7000 - 7999

7444.0 *** SYSTEM FATAL MESSAGE 7444 (DDFBRD)

ERROR IN TPTR OR IPTR VALUE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7445.0 *** SYSTEM FATAL MESSAGE 7445 (DDFBSA)

WRONG FRONT IDENTIFIER IN RECORD NO. %1 OF DISTRIBUTED SPARSE FACTOR
DESCRIPTION DATA BLOCK.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7446.0 *** SYSTEM FATAL MESSAGE 7446 (DDFBSA)

ACTUAL FRONT SIZE %1 OF FRONT %2 IS ILLEGAL (MAXIMUM FRONT SIZE IS %3).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7447.0 *** SYSTEM FATAL MESSAGE 7447 (DDFBSA)

CONSISTENCY ERROR(S) IN WORDS 3-6 OF RECORD %1 IN DISTRIBUTED SPARSE FAC-
TOR DESCRIPTION BLOCK.

Programmer information: %2, %3, %4, %5.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7448.0 *** SYSTEM FATAL MESSAGE 7448 (DDFBSA)

WRONG GLOBAL PANEL IDENTIFIER %1 IN PANEL %2 OF FRONT %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7449.0 *** SYSTEM FATAL MESSAGE 7449 (DDFBSA)

Main Index
 824 MSC Nastran Error Messages
Errors 7000 - 7999

CONSISTENCY ERROR(S) IN WORDS 1-8 OF PANEL %1 IN RECORD %2 OF DISTRIBUTED

SPARSE FACTOR DESCRIPTION BLOCK.

Programmer information: %3, %4, %5, %6, %7, %8, %9, %10.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7450.0 *** SYSTEM FATAL MESSAGE 7450 (DDFBSA)

ILLEGAL RECORD TERMINATION IN RECORD NO. %1 OF DISTRIBUTED SPARSE FACTOR
DESCRIPTION DATA BLOCK.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7451.0 *** SYSTEM FATAL MESSAGE 7451 (DDFBSA)

UNEXPECTED END OF DISTRIBUTED SPARSE FACTOR DESCRIPTION DATA BLOCK.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7452.0 *** SYSTEM FATAL MESSAGE 7452 (DDFDRV)

SIZE OF LOCAL A-SET IS INCONSISTENT BETWEEN TRAILER OF EQMAP DATA BLOCK
AND UABAR DATA BLOCK.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7453.0 *** SYSTEM FATAL MESSAGE 7453 (DDFDRV)

SIZE OF LOCAL A-SET IN TRAILER AND DATA OF EQMAP DATA BLOCK DO NOT MATCH.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7454.0 *** SYSTEM FATAL MESSAGE 7454

SIZE OF GLOBAL A-SET PLUS GLOBAL O-SET HAS UNEXPECTED VALUE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7455.0 *** SYSTEM FATAL MESSAGE 7455 (DDFDRV)

Main Index
 MSC Nastran Error Messages 825
Errors 7000 - 7999

INCONSISTENCY IN DISTRIBUTED SPARSE FACTOR DESCRIPTION DATA BLOCK.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7456.0 *** SYSTEM FATAL MESSAGE 7456 (DDFDRV)

PROGRAMMER ERROR IN NWRKSP VALUE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7457.0 *** SYSTEM FATAL MESSAGE 7457 (DDFFRD)

FIRST PANEL OF FRONT %1 HAS WRONG SIZE %2, EXPECTED SIZE IS %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7458.0 *** SYSTEM FATAL MESSAGE 7458 (DDFFRD)

ERROR IN IPRANK VALUE %1 OR IOFF VALUE %2. IPOWNF IS %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7459.0 *** SYSTEM FATAL MESSAGE 7459 (SEQP)

THE%1OUTPUT DATABLOCK OF%2IS PURGED, UNABLE TO OUTPUT PARTITIONING
VECTOR FOR HIGH LEVEL PARALLEL EXECUTION.

User action: PLEASE CHECK THE DMAP CALL TO%2IF YOU INCLUDED AN ALTER OR CON-
TACT HEXAGON AB CLIENT SUPPORT.

7460.0 *** SYSTEM FATAL MESSAGE 7460 (SEQP)

THE FIRST INPUT DATABLOCK TO SEQP (GEOM1) IS PURGED.

User action: PLEASE CHECK THE DMAP CALL TO SEQP IF YOU INCLUDED AN ALTER OR
CONTACT HEXAGON AB CLIENT SUPPORT.

7461.0 *** SYSTEM FATAL MESSAGE 7461 (SEQWRT)

Main Index
 826 MSC Nastran Error Messages
Errors 7000 - 7999

CURRENTLY ONLY %1 DOMAINS/PROCESSORS CAN BE HANDLED BY THE AUTOMATIC

MODEL PARTITIONER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7462.0 *** SYSTEM FATAL MESSAGE 7462 (DDFFRD)

LENGTH OF MESSAGE RECEIVED FOR TRIANGULAR SOLVE OR UPDATE IS %1, BUT %2
WAS EXPECTED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7463.0 *** SYSTEM FATAL MESSAGE 7463 (DDFFRD)

SIZE MISMATCH IN BLOCK TO BE SOLVED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7464.0 *** SYSTEM FATAL MESSAGE 7464 (DDFFRD)

MISMATCH IN IOFF2 AND IBASIS VALUES.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7465.0 *** USER INFORMATION MESSAGE 7465 (SEQWRT)

STATISTICS FROM AUTOMATIC MODEL PARTITIONER
THE NUMBER OF DOMAINS CREATED USING %1 IS %2
THE NUMBER OF GRID POINTS IN THE GLOBAL BOUNDARY IS %3
THE NUMBER OF ELASTIC ELEMENTS IN THE RESIDUAL IS %4
THE NUMBER OF RIGID ELEMENTS IN THE RESIDUAL IS %5
DOMAIN ID # INTERNAL GRID POINTS # EXTERNAL GRID POINTS # OF ELEMENTS
--------- ---------------------- ---------------------- -------------

7465.1 *** USER INFORMATION MESSAGE 7465 (PREOUT)

STATISTICS FROM AUTOMATIC MATRIX PARTITIONER
THE NUMBER OF ROWS IN THE MATRIX IS %1
THE NUMBER OF DOMAINS CREATED USING %2 IS %3
THE NUMBER OF DEGREES OF FREEDOM (DOF) IN THE GLOBAL BOUNDARY IS %4
DOMAIN ID # INTERNAL DOF # EXTERNAL DOF
--------- ---------------------- ----------------------

Main Index
 MSC Nastran Error Messages 827
Errors 7000 - 7999

7465.2 *** USER INFORMATION MESSAGE 7465 (SEQWRT)

STATISTICS FROM AUTOMATIC MODEL PARTITIONER
THE NUMBER OF DOMAINS CREATED USING %1 IS %2
THE NUMBER OF GRID POINTS IN THE GLOBAL BOUNDARY IS %3
THE NUMBER OF ELASTIC ELEMENTS IN THE RESIDUAL IS %4
THE NUMBER OF RIGID ELEMENTS IN THE RESIDUAL IS %5

7467.0 *** SYSTEM FATAL MESSAGE 7467 (SEQELM)

ELEMENT TYPE %1 CANNOT BE HANDLED BY MODEL PARTITIONER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7467.1 *** SYSTEM FATAL MESSAGE 7467 (SEQEXT)

ASET AND ASET1 ENTRIES CANNOT BE HANDLED BY MODEL PARTITIONER.

User action: PLEASE REMOVE ASET AND ASET1 ENTRIES FROM YOUR BULK DATA.

7467.2 *** SYSTEM FATAL MESSAGE 7467 (SEQELM)

EXTERNAL GRID ID %1 ON ELEMENT %2 WAS NOT FOUND.
FIRST LOCATE CODE OF THE ELEMENT TYPE IS %3.

User action: CHECK TO SEE IF THE ABOVE MENTIONED GRID ID EXISTS OR IS A PHAN-
TOM ID. IF SO, PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7467.3 *** SYSTEM FATAL MESSAGE 7467 (SEQEXT)

EXTERNAL GRID ID %1 WAS NOT FOUND AMONG A LIST OF INPUT GRID IDS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7468.0 *** SYSTEM FATAL MESSAGE 7468 (SEQELM)

INSUFFICIENT MEMORY TO READ GRID POINTS CONNECTED TO ELEMENT TYPE %1.

User action: INCREASE MEMORY BY AT LEAST %2 K WORDS.

7469.0 *** SYSTEM FATAL MESSAGE 7469 (DDFMRG)

Main Index
 828 MSC Nastran Error Messages
Errors 7000 - 7999

INCORRECT NUMBER OF NONZERO TERMS %1 IN PANEL %2 OF FRONT %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7470.0 *** SYSTEM FATAL MESSAGE 7470 (DDFMRG)

FRONT SIZE %1, PANEL SIZE %2 AND NEXT ROW %3 DO NOT MATCH FOR PANEL %4 OF
FRONT %5.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7471.0 *** SYSTEM FATAL MESSAGE 7471 (SEQELM)

ELEMENT TYPE %1 HAS MORE THAN %2 GRID POINTS WHICH CANNOT BE HANDLED
BY THE AUTOMATIC MODEL PARTITIONER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7472.0 *** SYSTEM FATAL MESSAGE 7472 (DDFMRG)

FRONT INDEX MISMATCH IN PANEL %1 OF FRONT %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7473.0 *** SYSTEM FATAL MESSAGE 7473 (DDFMRG)

OWNER MISMATCH IN FIRST PANEL OF FRONT %1.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7474.0 *** SYSTEM FATAL MESSAGE 7474 (SEQELM)

ELEMENT CUT IN AUTOMATIC MODEL PARTITIONER: NODE %1 OF THE BOUNDARY
DOES NOT BELONG TO %2, HOWEVER, ANOTHER NODE OF THIS ELEMENT DOES
BELONG TO THIS DOMAIN.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7475.0 *** SYSTEM FATAL MESSAGE 7475 (DDFMRG)

MEMORY SHORTAGE WHEN UNPACKING PANEL %1 OF FRONT %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 MSC Nastran Error Messages 829
Errors 7000 - 7999

7476.0 *** SYSTEM FATAL MESSAGE 7476 (DDFMRG)

NUMBER OF TERMS %1 IN COLUMN %2 OF PANEL %3 IN FRONT %4 IS WRONG.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7477.0 *** SYSTEM FATAL MESSAGE 7477 (DDFMRG)

INTERNAL ERROR UNPACKING PANEL %1 IN FRONT %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7478.0 *** SYSTEM FATAL MESSAGE 7478 (DDFMRG)

INTERNAL ERROR IN COLUMN NUMBERING IN FRONT.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7479.0 *** USER FATAL MESSAGE 7479 (SEQP)

FLUID-STRUCTURE analysis is not supported with DOMAIN DECOMPOSITION.

User action: PLEASE SWITCH TO ACMS OR RUN IN SERIAL.

7480.0 *** SYSTEM FATAL MESSAGE 7480 (SEQORD)

INCONSISTENT NUMBER OF GRID POINTS ON THE BOUNDARY: THE INPUT TO THE
SUBROUTINE IS %1, HOWEVER, %2 WHERE COMPUTED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7481.0 *** SYSTEM FATAL MESSAGE 7481 (GETSEG)

REQUESTED STACK ELEMENT DOES NOT EXIST.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7482.0 *** SYSTEM FATAL MESSAGE 7482 (GETSEG)

PROGRAMMER ERROR: INCONSISTENCY IN GETSEG CALL.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

Main Index
 830 MSC Nastran Error Messages
Errors 7000 - 7999

7483.0 *** SYSTEM FATAL MESSAGE 7483 (SEQORD)

ALL BOUNDARY GRID POINTS HAVE TO BE ON TOP OF THE ID() ARRAY WHICH IS NOT
THE CASE HERE! GRIDPOINT %1 OUT OF %2 BELONGS TO DOMAIN %3 BUT NOT THE
THE BOUNDARY.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7484.0 *** SYSTEM FATAL MESSAGE 7484 (GETSEG)

REQUESTED SERVICE NOT SUPPORTED YET.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7485.0 *** USER INFORMATION MESSAGE 7485

THE AUTOMATIC MODEL PARTITIONER SUBDIVIDED THE MODEL INTO %1 DOMAINS
BUT %2 DOMAINS WERE REQUESTED.

User action: REQUEST FEWER DOMAINS.

7485.1 *** USER INFORMATION MESSAGE 7485 (SEQP)

THE AUTOMATIC MODEL PARTITIONER SUBDIVIDED THE MODEL INTO %1 DOMAINS
BUT %2 DOMAINS WERE REQUESTED.

User information: THE PARTITIONING WILL BE RE-DONE ASKING TO PARTITION THE

MODEL INTO %3 DOMAINS.

7486.0 *** SYSTEM FATAL MESSAGE 7486 (GETSTJ)

MAP FOR REQUESTED STACK ELEMENT DOES NOT EXIST.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7487.0 *** SYSTEM FATAL MESSAGE 7487 (GETSTJ)

THIS CODE BRANCH IS NOT SUPPORTED YET.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7488.0 *** SYSTEM FATAL MESSAGE 7488 (GETSTJ)

Main Index
 MSC Nastran Error Messages 831
Errors 7000 - 7999

FOR STACK ELEMENT %1 ACTUAL FRONT SIZE %2 DOES NOT MATCH STACK INFO (%3).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7489.0 *** SYSTEM FATAL MESSAGE 7489

INSUFFICIENT MEMORY FOR MODEL PARTITIONING.

User action: INCREASE MEMORY BY AT LEAST %1 K %2.

7490.0 *** SYSTEM FATAL MESSAGE 7490 (SEQP)

ERROR IN MEMORY MANAGEMENT INSIDE THE AUTOMATIC MODEL PARTITIONER.
%1.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7490.1 *** SYSTEM FATAL MESSAGE 7490 (SEQP)

ERROR IN MEMORY MANAGEMENT INSIDE THE AUTOMATIC MODEL PARTITIONER.

User action: INCREASE MEMORY BY AT LEAST %1 K WORDS.

7491.0 *** SYSTEM FATAL MESSAGE 7491 (DISDAF)

INSUFFICIENT SPACE FOR INTERNAL LIST %1.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7492.0 *** SYSTEM FATAL MESSAGE 7492 (PRESOL)

INCONSISTENT VALUE FOR NUMBER OF LOCAL GRIDPOINTS ON PROCESSOR %1:
ACCORDING TO SIL TABLE, THE NUMBER OF LOCAL GRIDPOINTS IS %2
ACCORDING TO GEQMAP, THE NUMBER OF LOCAL GRIDPOINTS IS %3

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7493.0 *** SYSTEM FATAL MESSAGE 7493 (PRESOL)

INSUFFICIENT MEMORY AVAILABLE TO CREATE THE EXTENDED EQUATION MAP.

User action: PLEASE INCREASE MEMORY BY AT LEAST %1 K WORDS.

Main Index
 832 MSC Nastran Error Messages
Errors 7000 - 7999

7494.0 *** SYSTEM FATAL MESSAGE 7494 (PRESIL)

LOCAL GRID POINT %1 HAS %2 DEGREES OF FREEDOM. CURRENTLY THE DOMAIN
DECOMPOSITION METHOD CAN HANDLE ONLY GRID POINTS WITH 6 DEGREES OF
FREEDOM.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7495.0 *** SYSTEM FATAL MESSAGE 7495 (PRESIL)

INCONSISTENT NUMBER OF LOCAL ACTIVE DEGREES OF FREEDOM ON PROCESSOR
%1:
NUMBER OF LOCAL DEGREES OF FREEDOM = %2
6 * NUMBER OF ACTIVE GRID POINTS = %3

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7496.0 *** SYSTEM FATAL MESSAGE 7496 (PREMAP)

COLUMN %1 IN THE O-SET OF PROCESSOR %2 IS A NULL COLUMN. THIS CANNOT BE
HANDLED BY THE DOMAIN DECOMPOSITION METHOD.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7497.0 *** SYSTEM FATAL MESSAGE 7497 (PREMAP)

DEGREE OF FREEDOM %1 IS MARKED NON-ACTIVE ON PROCESSOR %2, HOWEVER, ON
A DIFFERENT PROCESSOR IT WAS MARKED ACTIVE.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7498.0 *** SYSTEM FATAL MESSAGE 7498 (PRELGM)

INSUFFICIENT WORK SPACE AVAILABLE FOR TMPIND(). PROCESSOR %1 NEEDS TO
RECEIVE %2 WORDS FROM PROCESSOR %3, HOWEVER, ONLY %4 WORDS ARE AVAIL-
ABLE IN TMPIND().

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7499.0 *** SYSTEM FATAL MESSAGE 7499 (PRELGM)

Main Index
 MSC Nastran Error Messages 833
Errors 7000 - 7999

INSUFFICIENT WORK SPACE AVAILABLE FOR IWORK() TO BUILD THE EXTENDED

EQUATION MAP ON PROCESSOR %1.
WORK SPACE AVAILABLE IS %2 WORDS BUT %3 WORDS ARE NEEDED.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7500.0 *** SYSTEM FATAL MESSAGE 7500 (PRELGM)

INCONSISTENCY OF DEGREES OF FREEDOM FOR THE F-SET ON PROCESSOR %1:
DEGREES OF FREEDOM FROM RESORD ARRAY IS %2, BUT DEGREES OF FREEDOM IN
LOCAL F-SET IS %3.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7501.0 *** USER FATAL MESSAGE 7501 (DOPR3I)

THE DSNOKD PARAMETER IS SET TO %1 AND THERE ARE MULTIPLE BUCKLING
DESIGN SUBCASES WHICH CONTAIN DIFFERENT STATSUB REQUESTS: %2 AND %3.
THIS IS NOT SUPPORTED.

User action: SET DSNOKD TO 0.0 OR USE THE SAME STATSUB REQUEST FOR ALL BUCK-
LING DESIGN SUBCASES.

7501.1 *** USER FATAL MESSAGE 7501 (dpofchk)

DVCRELx ID %1 REQUESTS THE DESIGN OF THE %2 COMPONENT OF THE ORIENTA-
TION VECTOR THAT IS SPECIFIED IN THE BASIC COORDINATE SYSTEM. THIS IS NOT
SUPPORTED.

User action: IF POSSIBLE, SPECIFY THE ORIENTATION IN THE GLOBAL COORDINATE SYS-
TEM AND MAKE THE APPROPRIATE CHANGES IN THE DVCRELx ENTRY.

7501.2 *** USER FATAL MESSAGE 7501 (dpofchk)

DVCRELx ID %1 REQUESTS THE DESIGN OF THE %2 COMPONENT OF THE OFFSET VEC-
TOR THAT IS SPECIFIED IN THE OFFSET COORDINATE SYSTEM. THIS IS NOT SUP-
PORTED.

User action: IF POSSIBLE, SPECIFY THE OFFSET VECTOR IN THE GLOBAL COORDINATE
SYSTEM AND MAKE THE APPROPRIATE CHANGES IN THE DVCRELx ENTRY.

Main Index
 834 MSC Nastran Error Messages
Errors 7000 - 7999

7502.0 *** SYSTEM INFORMATION MESSAGE 7502 (DSDJ1D/S)

THERE ARE %1 ACTIVE SOLUTION VECTORS, OF WHICH %2 CAN BE STORED IN MEM-
ORY.
IN ORDER TO STORE ALL VECTORS IN MEMORY FOR IMPROVED PERFORMANCE,
INCREASE MEMORY BY %3K WORDS.

7503.0 *** SYSTEM FATAL MESSAGE 7503 (SQMPC)

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

Programmer information: GRID POINT ID %1 WHICH IS SPECIFIED AS THE DEPENDENT

GRID POINT ON AN MPC ENTRY IS ALSO ASSIGNED TO A DOMAIN BOUNDARY.

User action: TRY TO RUN WITH A DIFFERENT NUMBER OF PROCESSORS OR CONTACT

HEXAGON AB CLIENT SUPPORT.

7503.1 *** SYSTEM FATAL MESSAGE 7503 (SQRBAR)

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

Programmer information: ALL DEPENDENT GRID POINTS OF RIGID ELEMENT ID %1 WERE

ASSIGNED TO A DOMAIN BOUNDARY.

User action: TRY TO RUN WITH A DIFFERENT NUMBER OF PROCESSORS OR CONTACT

HEXAGON AB CLIENT SUPPORT.

7503.2 *** SYSTEM FATAL MESSAGE 7503 (SQRBAR)

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

Programmer information: ALL DEPENDENT GRID POINTS OF RIGID ELEMENT ID %1 WERE

ASSIGNED TO A DOMAIN BOUNDARY.
ALSO ALL GRIDS CONNECTED TO THIS RIGID ELEMENT WERE ASSIGNED TO A
DOMAIN BOUNDARY.

User action: TRY TO RUN WITH A DIFFERENT NUMBER OF PROCESSORS OR CONTACT

HEXAGON AB CLIENT SUPPORT.

7504.0 *** SYSTEM FATAL MESSAGE 7504 (SQRBE1)

Main Index
 MSC Nastran Error Messages 835
Errors 7000 - 7999

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

Programmer information: NO DEPENDENT GRID POINTS OF %1 BELONG TO A DOMAIN,

HOWEVER, THEY DO NOT ALL BELONG TO THE BOUNDARY EITHER.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7505.0 *** SYSTEM FATAL MESSAGE 7505 (SQRBE1)

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.
Programmer information: AFTER CHECKING ALL RIGID ELEMENTS OF THIS TYPE, GRID-
POINT %1 OF ELEMENT %2 BELONGS TO DOMAIN %3, HOWEVER, IT WAS INITIALLY
ASSIGNED TO %4. THIS INDICATES THAT THIS GRIDPOINT MAY BE A DEPENDENT
GRID OF 2 DIFFERENT RIGID ELEMENTS.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7506.0 *** SYSTEM FATAL MESSAGE 7506 (SQRROD)

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

Programmer information: INVALID NUMBER (DEPROD = %1) FOR SPECIFYING THE DEPEN-
DENT GRID OF RROD %2.
THE NUMBER SHOULD BE EITHER 1 OR 2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7507.0 *** SYSTEM FATAL MESSAGE 7507 (SQRTRP)

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

Programmer information: GRIDPOINTS OF RTRPLT %1 BELONG TO DOMAINS %2 AND %3.

THIS CANNOT BE HANDLED YET.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7508.0 *** SYSTEM FATAL MESSAGE 7510 (SQRTRP)

Main Index
 836 MSC Nastran Error Messages
Errors 7000 - 7999

LOGIC ERROR IN THE AUTOMATIC MODEL PARTITIONER.

Programmer information: ALL GRIDPOINTS OF RTRPLT %1 BELONG TO A DIFFERENT

DOMAIN ( %2, %3 AND %4).

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7509.0 *** SYSTEM FATAL MESSAGE 7509 (PRELRD)

LOGIC ERROR IN DISTRIBUTED MAP PREPARATION MODULE.

Programmer information: INCONSISTENT LOCAL A-SET. SIZE OF LOCAL A-SET FROM PARTI-
TIONING VECTOR CREATED IN PRESOL IS %1, HOWEVER, SIZE OF LOCAL A-SET FROM
THE EQUATION MAP IS %2.

User action: PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7510.0 *** USER FATAL MESSAGE 7510 (DOM9P4D)

THE MAXIMUM INTEGER VALUE HAS BEEN EXCEEDED.

User information: THE MAXIMUM INTEGER NUMBER ALLOWED ON YOUR MACHINE IS

%1. HOWEVER, DOT HAS IDENTIFIED THAT THE SIZE OF YOUR OPTIMIZATION PROB-
LEM, NDV =%2, NCON = %3, IS SO LARGE THT IT CAUSES MAXIMUM INTEGER OVER-
FLOW.

User action: REDUCE SIZE OF DESIGN MODEL.

7510.1 *** USER WARNING MESSAGE 7510 (ADS9P4d)

MSCADS DESIRED STORAGE REQUIRES TO INCREASE OPEN CORE BY AT LEAST %1
WORDS WILL ATTEMPT TO OPTIMIZE WITH AVAILABLE STORAGE

7510.2 *** USER WARNING MESSAGE 7510 (ADS9P4d)

MSCADS MINIMUM STORAGE REQUIRES TO INCREASE OPEN CORE BY AT LEAST %1
WORDS WILL ATTEMPT TO OPTIMIZE WITH AVAILABLE STORAGE

7510.3 *** SYSTEM FATAL MESSAGE 7510 (ADS9P4D)

Main Index
 MSC Nastran Error Messages 837
Errors 7000 - 7999

INSUFFICIENT MEMORY AVAILABLE FOR OPTIMIZER MSCADS

User action: SWITCH TO METHOD =4 OR REDUCE SIZE OF DESIGN MODEL

7510.4 *** SYSTEM FATAL MESSAGE 7510 (ADS9P4D)

INSUFFICIENT MEMORY AVAILABLE FOR OPTIMIZER MSCADS

User action: REDUCE SIZE OF DESIGN MODEL

7511.0 *** SYSTEM FATAL MESSAGE 7511 (BIOCPY)

INVALID CALL TO BIOCPY. %1 VALUE (= %2) IS OUT OF RANGE.
FILE COPY REQUEST NOT DONE.

7512.0 *** SYSTEM FATAL MESSAGE 7512 (BIOCPY)

INPUT FILE IS NOT OPEN. FILX = %1.
FILE IS '%2'.
FILE COPY REQUEST NOT DONE.

7513.0 *** SYSTEM FATAL MESSAGE 7513 (BIOCPY)

INPUT FILE RECORD LENGTH DOES NOT MATCH NSBUF3 VALUE. FILX = %1.
FILE IS '%2'.
FILE RECL = %3, NSBUF3 RECL = %4.
FILE COPY REQUEST NOT DONE.

7514.0 *** SYSTEM FATAL MESSAGE 7514 (BIOCPY)

OUTPUT FILE IS OPEN BUT ITS RECORD LENGTH DOES NOT MATCH INPUT FILE RECL
VALUE.
INPUT FILX = %1, OUTPUT FILX = %2.
INPUT FILE IS '%3'.
OUTPUT FILE IS '%4'.
INPUT FILE RECL = %5, OUTPUT FILE RECL = %6.
FILE COPY REQUEST NOT DONE.

7515.0 *** SYSTEM FATAL MESSAGE 7515 (BIOCPY)

Main Index
 838 MSC Nastran Error Messages
Errors 7000 - 7999

OUTPUT FILE IS OPENED READ-ONLY. FILX = %1.

FILE IS '%2'.
FILE COPY REQUEST NOT DONE.

7516.0 *** SYSTEM FATAL MESSAGE 7516 (BIOCPY)

UNABLE TO CREATE OUTPUT FILE. FILX = %1.
FILE IS '%2'.
FILE COPY REQUEST NOT DONE.

7517.0 *** SYSTEM FATAL MESSAGE 7517 (BIOCPY)

TRUNCATE OF OPEN OUTPUT FILE FAILED. FILX = %1.
FILE IS '%2'.
FILE COPY REQUEST NOT DONE.

7518.0 *** SYSTEM FATAL MESSAGE 7518 (BIOCPY)

UNABLE TO OBTAIN DYNAMIC BUFFER SPACE FOR FILE COPY. WORDS REQUESTED =
%1.
FILE COPY REQUEST NOT DONE.

7519.0 *** SYSTEM FATAL MESSAGE 7519 (BIOCPY)

ERROR ENCOUNTERED READING INPUT FILE. FILX = %1.
FILE IS '%2'.
FILE COPY REQUEST TERMINATED.

7520.0 *** SYSTEM FATAL MESSAGE 7520 (BIOCPY)

ERROR ENCOUNTERED WRITING OUTPUT FILE. FILX = %1.
FILE IS '%2'.
FILE COPY REQUEST TERMINATED.

7521.0 *** USER FATAL MESSAGE 7521 (GP3)

LOAD BULK DATA ENTRY WITH SID=%1 REFERENCES A DEFORM OR TEMP* BULK DATA
ENTRY WITH SID=%2 .

User information: DEFORM AND TEMP* BULK DATA ENTRIES ARE REQUESTED BY THE
DEFORM AND TEMPERATURE CASE CONTROL COMMANDS.

7522.0 *** USER FATAL MESSAGE 7522 (GP3)

Main Index
 MSC Nastran Error Messages 839
Errors 7000 - 7999

DEFORM AND/OR TEMP* BULK DATA ENTRY HAVE THE SAME SID=%1 .

User information: DEFORM AND/OR TEMP* BULK DATA ENTRIES MUST BE UNIQUE WITH
RESPECT TO EACH OTHER.

7523.0 *** USER FATAL MESSAGE 7523 (SEPMAB)

%1 %2 IS DEFINED ON THE %3 BULK DATA ENTRY BUT NO GEOMETRY WAS FOUND.

User action: CHECK BEGIN %4 COMMANDS AND/OR DATA BASE ASSIGNMENTS FOR THIS
%1.

7523.1 *** USER FATAL MESSAGE 7523 (SEPBLK)

%2 %1 IS DEFINED ON THE %3 BULK DATA ENTRY BUT NO BEGIN %4=%1 SECTION WAS
FOUND.

7523.2 *** USER FATAL MESSAGE 7523 (SEPMAB)

NO GRID OR SPOINT BULK DATA ENTRIES WERE FOUND IN BEGIN %1 %2'S BULK DATA
SECTION.

7524.0 *** USER FATAL MESSAGE 7524 (DOP1C2)

DVPREL1 ENTRY %1 SPECIFIES A PBEAML DIMENSION THAT IS NOT SPECIFIED ON
PBEAML ENTRY %2.

User action: CHECK DVPREL1 AND PBEAML ENTRIES.

7525.0 *** USER FATAL MESSAGE 7525 (DOPR3A)

DRESP1 ENTRY ID = %1 REFERENCES A RTYPE=ESE WHICH IS NOT SUPPORTED FOR
SHAPE OPTIMIZATION.

7525.1 *** USER FATAL MESSAGE 7525 (DOPR3A)

DRESP1 ENTRY ID = %1 WITH FUNCTION NAME IN ATTB FIELD CAN NOT REFERENCE
MORE THAN ONE ID IN ATTi FIELDS OR MULTIPLE COMPONENTS IN ATTA FIELD.

User action: SPLIT DRESP1 INTO SEPARATE ONES EACH WITH A SINGLE GID IN ATTi
FIELD AND SINGLE COMPONENT CODE IN ATTA FIELD.

Main Index
 840 MSC Nastran Error Messages
Errors 7000 - 7999

7525.2 *** USER FATAL MESSAGE 7525 (DOPR3B)

DRESP1 ENTRY ID = %1 WITH FUNCTION NAME IN ATTB FIELD CAN NOT REFERENCE
MORE THAN ONE EID (IMPLICIT VIA PID OR EXPLICIT VIA EID) IN ATTi FIELDS.

User action: SPLIT DRESP1 INTO SEPARATE ONES EACH WITH A SINGLE EID IN ATTi
FIELD.

7525.3 *** USER FATAL MESSAGE 7525 (DOPR3A)

DRESP1 ENTRY ID = %1 REFERENCES A RTYPE=ESE/TOTSE/GPFORCE/GPFORCP WHICH
IS NOT SUPPORTED FOR SHAPE/TOPOGRAPHY OPTIMIZATION.

7525.4 *** USER FATAL MESSAGE 7525 (DOPR3A)

DRESP1 ENTRY ID = %1 REFERENCES A RTYPE=GPFORCE WHICH IS NOT SUPPORTED
FOR SHAPE OPTIMIZATION.

7525.5 *** USER FATAL MESSAGE 7525 (DOPR3A)

DRESP1 ENTRY ID = %1 REFERENCES A RTYPE=GPFORCP WHICH IS NOT SUPPORTED
FOR SHAPE OPTIMIZATION.

7525.6 *** USER FATAL MESSAGE 7525 (DOPR3A)

DRESP1 ENTRY ID = %1 REFERENCES PID = %2 WHICH IS NOT REFERENCED BY ANY
TOPVAR OR TOMVAR ENTRIES.

7525.7 *** USER FATAL MESSAGE 7525 (DOP1A5)

DRESP1 STRESS CANNNOT BE USED WITH TOPOLOGY GLOBAL STRESS ON TOMVAR
ENTRIES.

7525.8 *** USER FATAL MESSAGE 7525 (DOPR1Y)

DRESP ENTRY %1 has a value for the stamping thickness, which is too small.

User action: STAMPING THICKNESS SHOULD BE AT LEAST 3 TIMES ELEMENT LENGTH IN

STAMPING DIRECTION (REGULAR ELEMENTS SUCH AS CHEXA ARE RECOMMENDED)

7525.9 *** SYSTEM FATAL MESSAGE 7525 (DOP1YC3)

Main Index
 MSC Nastran Error Messages 841
Errors 7000 - 7999

The Number of Support Elements has a limitation %1 in 3D Print Overhang Constraints

User action: Regular Elements Aligned in Print Direction (or Smaller Minimum Member Size Value) Are
Recommended

7526.0 *** USER FATAL MESSAGE (ASGPD/S)

AN INVALID TRIM TASK HAS BEEN POSED. THERE ARE %1 FREE AESTAT DEGREES OF
FREEDOM BUT ONLY %2 SUPPORTED DEGREES OF FREEDOM.

User action: SPECIFY A VALID TRIM TASK BY EITHER ADDING SUPPORTED DEGREES OF
FREEDOM OR BY REDUCING THE NUMBER OF FREE AESTAT DEGREES OF FREEDOM.

7526.1 *** USER FATAL MESSAGE (ASGPD/S)

AN INVALID TRIM TASK HAS BEEN POSED. THERE ARE %1 FREE AERODYNAMIC
DEGREES OF FREEDOM BUT ONLY %2 SUPPORTED DEGREES OF FREEDOM AND THERE
ARE NO REDUNDANT CONTROL SURFACES.

User action: SPECIFY A VALID TRIM TASK BY A COMBINATION OF ADDING SUPPORTED

DEGREES OF FREEDOM, ADDING REDUNDANT CONTROL SURFACES AND/OR REDUC-
ING THE NUMBER OF FREE AESTAT DEGREES OF FREEDOM.

7527.0 *** SYSTEM FATAL MESSAGE 7527 (SEQEXT)

THE AUTOMATIC MODEL PARTITIONER DID NOT ASSIGN ANY GRID POINTS TO THE
BOUNDARY.

User information: THE DOMAIN DECOMPOSITION METHOD CANNOT CONTINUE WITH-

OUT A BOUNDARY.

User action: IF YOUR MODEL IS DISJOINT, DESELECT THE DOMAIN DECOMPOSITION

METHOD BY REMOVING DMP= FROM THE SUBMITTAL LINE.
IF YOUR MODEL IS NOT DISJOINT, PLEASE CONTACT HEXAGON AB CLIENT SUPPORT.

7527.1 *** SYSTEM FATAL MESSAGE 7527 (PREDRV)

Main Index
 842 MSC Nastran Error Messages
Errors 7000 - 7999

THE AUTOMATIC MODEL PARTITIONER DID NOT ASSIGN ANY GRID POINTS TO THE
BOUNDARY.

User information: THE DOMAIN DECOMPOSITION METHOD CANNOT CONTINUE WITH-

OUT A BOUNDARY.

User action: IF YOUR MODEL IS DISJOINT, DESELECT THE DOMAIN DECOMPOSITION

METHOD BY REMOVING DMP= FROM THE SUBMITTAL LINE.
IF YOUR MODEL IS NOT DISJOINT, PLEASE SET PARAM,OLDSEQ,%1, OR CONTACT
HEXAGON AB CLIENT SUPPORT.

7527.2 *** SYSTEM WARNING MESSAGE 7527 (MDSTAT)

THE AUTOMATIC MODEL PARTITIONER DID NOT ASSIGN ANY GRID POINTS TO THE
BOUNDARY.

User information: THE DOMAIN DECOMPOSITION METHOD CANNOT CONTINUE WITH-

OUT A BOUNDARY.
THE DMP SOLVER WILL BE DE-ACTIVATED FOR THIS ITERATION.

7528.0 USER INFORMATION MESSAGE 7528 (OUTPRT)

A "=ALL" OUTPUT REQUEST HAS BEEN FOUND FOR DISP, VELO, ACCE, STRESS OR
FORCE TYPE OUTPUT.

User information: MORE ECONOMICAL DATA RECOVERY IS POSSIBLE WHEN A LIMITED

OUTPUT SET IS SELECTED.

7529.0 *** SYSTEM FATAL MESSAGE 7529 (TAFGPE)

Main Index
 MSC Nastran Error Messages 843
Errors 7000 - 7999

SPILL LOGIC ERROR FORMING GPECT TABLE, REASON = %1

Programmer information: HERE IS A LIST OF POSSIBLE REASONS:

1. CONTROL TABLE NOT ALLOCATED, EST ESTIMATES WRONG
2. CONTROL TABLE EXHAUSTED BUILD LOOP
3. CONTROL TABLE EXHAUSTED FLUSHING LAST MEMORY LOAD
4. INSUFFICIENT MEMORY BLOCK FRAGMENTS FOR JOIN

User action: FOR REASON 1:3 TURN OFF FOLLOWER FORCES IF POSSIBLE
FOR REASON CODE 4, CHANGE MODULE DEFAULT PARAMETER POSITION 5, TO
HIGHER VALUE THAN 10.

7530.0 *** USER information MESSAGE 7530 (DOPFSDD)

FULLY STRESSED DESIGN HAS BEEN REQUESTED, BUT THERE ARE NO ELEMENT BASED
CONSTRAINTS.

7530.1 *** USER FATAL MESSAGE 7530 (DOPFSA )

FULLY STRESSED DESIGN HAS BEEN REQUESTED, BUT THERE ARE NO RELEVANT
DESIGNED PROPERTIES

User action: EITHER SET FSDMAX TO 0 OR SUPPLY DESIGNED ROD AREAS OR PSHELL/
PSHEAR/PCOMP THICKNESSES

7530.2 *** USER FATAL MESSAGE 7530 (DOPFSDD)

FULLY STRESSED DESIGN HAS BEEN REQUESTED, BUT THERE ARE NO CONSTRAINTS.

7531.0 *** USER FATAL MESSAGE 7531 (DOPFS4D)

FULLY STRESSED DESIGN HAS BEEN REQUESTED, BUT A DESIGNED PROPERTY IS A
FUNCTION OF MORE THAN ONE DESIGN VARIABLE.

User information: FOR FULLY STRESSED DESIGN, EACH DESIGNED PROPERTY MUST BE A
FUNCTION OF A SINGLE DESIGN VARIABLE.

7532.0 *** USER FATAL MESSAGE 7530 (ASG)

Main Index
 844 MSC Nastran Error Messages
Errors 7000 - 7999

SENSITIVITY ANALYSIS HAS BEEN REQUESTED THAT IS ASSOCIATED WITH NONLINEAR

STATIC AEROELASTIC TRIM ANALYSIS.

User information: THIS CAPABILITY IS NOT SUPPORTED.

User action: EITHER REMOVE THE REQUEST OR SPECIFY A LINEAR STATIC AEROLEASTIC
ANALYSIS.

7532.1 *** USER FATAL MESSAGE 7532 (DSAL)

DIRECT SENSITIVITY ANALYSIS HAS BEEN REQUESTED FOR RTYPE=COMP (COMPLI-
ANCE)

User information: THIS CAPABILITY IS NOT SUPPORTED.

User action: REPLACE RTYPE=COMP BY RTYPE=TOTSE (TOTAL STRAIN ENERGY)

7532.2 *** USER FATAL MESSAGE 7532 (DSAD1)

COMPLIANCE AND EIGENVECTOR SENSITIVITIES ARE BEING REQUESTED.

User information: THESE REQUESTS ARE NOT COMPATIBLE.

User action: REPLACE RTYPE=COMP BY RTYPE=TOTSE (TOTAL STRAIN ENERGY).

7533.0 *** USER WARNING MESSAGE 7533 (PFACED/S, PEDGED/S),

%1 %2 IS PART OF A SOLID ELEMENT AND DOES NOT HAVE ROTATIONAL DEGREES OF
FREEDOM.

User information: DISTRIBUTED MOMENT LOADS WILL BE IGNORED.

7534.0 *** USER FATAL MESSAGE 7532 (SEPBLK)

MDBULK,ALL is present and there are other MDBULK entry(ies) present.

User information: If MDBULK,ALL is present then no other MDBULK entry(ies) are allowed.

7536.0 *** USER FATAL MESSAGE 7536 (GP3A)

Main Index
 MSC Nastran Error Messages 845
Errors 7000 - 7999

THE FOLLOWING NON-UNIQUE SID/EXCITATION-ID PAIRS HAVE BEEN SPECIFIED IN

LSEQ BULK DATA ENTRIES --

(User action: AVOID THE NEED FOR NON-UNIQUE SID/EXCITATION-ID PAIRS BY USING
AND REFERENCING APPROPRIATE COMBINATION LOAD BULK DATA)

7537.0 *** SYSTEM WARNING MESSAGE 7537 (REIG)

PERTURBED MASS MATRIX IS USED FOR EIGENSOLUTION.
PERTURBATION FACTOR USED = %1

7538.0 *** USER WARNING MESSAGE 7538 (REIG)

NUMBER OF EIGENVECTORS IS BEING REDUCED FROM %1 TO %2
DUE TO RANK DEFICIENCY OF THE MASS MATRIX.

7539.0 *** SYSTEM WARNING MESSAGE 7539 (DFMSJ)

RANK OF MASS MATRIX = %1

7540.0 *** SYSTEM FATAL MESSAGE 7540 (GP1D and SECNV1/SECNV2/SECNV3)

INVALID RETURN FROM CALL TO SUBROUTINE %1
RETURN CODE = %2

7541.0 *** SYSTEM FATAL MESSAGE 7541 (GP1D and SECNV1/SECNV2/SECNV3)

INVALID RETURN FROM CALL TO SUBROUTINE %1 WHILE PROCESSING %2 BULK DATA
ENTRY %3
FOR POINT ID %4
RETURN CODE = %5

7541.1 *** SYSTEM FATAL MESSAGE 7541 (GP1RF)

INVALID RETURN FROM CALL TO SUBROUTINE %1 WHILE PROCESSING GRID POINT ID
%2 FOR DIFFERENTIAL STIFFNESS ANALYSIS IN 3D ROTOR.
RETURN CODE = %3

7542.0 *** SYSTEM FATAL MESSAGE 7542 (GP1D and GP1F)

ILLEGAL COORDINATE SYSTEM ID %1 ENCOUNTERED WHILE PROCESSING %2 BULK
DATA ENTRY %3 FOR %4 POINT ID %5

Main Index
 846 MSC Nastran Error Messages
Errors 7000 - 7999

7543.0 *** USER INFORMATION MESSAGE 7543 (GP1D)

DAREA BULK DATA ENTRIES FOR GRID AND SCALAR POINTS WILL NOT BE CONVERTED
TO EQUIVALENT FORCE / MOMENT / SLOAD ENTRIES BECAUSE OF THE PRESENCE OF
LSEQ BULK DATA ENTRIES

7544.0 *** USER FATAL MESSAGE 7544.0 (DSAD13)

DRESP1 ID %1 IS A CFAILURE RESPONSE WITH ITEM CODE 8: MAXIMUM
FAILURE INDEX.

User information: THIS RESPONSE IS ONLY VALID FOR THE FINAL PLY BUT IS BEING
APPLIED TO PLY NUMBER %2

User action: RESTRICT THE ITEM CODE 8 REQUEST TO THE FINAL PLY

7544.1 *** USER FATAL MESSAGE 7544.1 (DSAD13)

DRESP1 ID %1 IS A CFAILURE RESPONSE WITH ITEM CODE 7: INTERLAMINAR
STRESS/STRAIN.

User information: THIS RESPONSE IS BEING APPLIED TO PLY NUMBER %2, WHICH IS THE
FINAL PLY. INTERLAMINAR STRESS/STRAIN RESPONSES ARE NOT AVAILABLE FOR THE
FINAL PLY

User action: DO NOT APPLY ITEM CODE 7 TO THE FINAL PLY

7545.0 *** USER WARNING MESSAGE 7545 (MDG2SW)

A CORRESPONDING CWELDG ENTRY CANNOT BE FOUND WITH THE SAME SPOT WELD
GRID ID AS SPECIFIED ON CWELDG ENTRY ID=%1.

User information: THE SHELL PORTION OF THIS ELEMENT WILL BE CREATED BUT NOT
THE SPOT WELD PORTION.

7546.0 *** USER FATAL MESSAGE 7546 (MDG2SW)

ON %1 ELEMENT ID=%2, WITH FORM=ALIGN, THE GA (OR GB) GRID ID=%3 IS NOT A
VERTEX GRID OF A SHELL ELEMENT.

7546.1 *** USER FATAL MESSAGE 7546

Main Index
 MSC Nastran Error Messages 847
Errors 7000 - 7999

ON %1 ELEMENT ID=%2, WITH FORM=ELEMID, THE SHID1 (OR SHID2)=%3 IS NOT A

SHELL ELEMENT.

7546.2 *** USER FATAL MESSAGE 7546 (MDG2SN)

NO SHELL ELEMENTS EXIST FOR ANY CONNECTOR ELEMENT (CWELD, CFAST OR
CSEAM) TO CONNECT.

7546.3 *** USER FATAL MESSAGE 7546 (MDG2SG)

PATCH CONNECTION PROCESSING FAILED TO GENERATE ANY SHELL GRIDS IN THE
GRID-ELEMENT CONNECTION TABLE FOR ANY OF THE CONNECTORS PRESENT IN
THE MODEL.

User information: THE DIAMETERS OF CONNECTOR ELEMENTS MAY BE TOO SMALL REL-
ATIVE TO PATCH SIZE.

7547.0 *** USER INFORMATION MESSAGE 7547 (MDG4SW)

FOR PWELD ENTRY ID=%1, THE SPOT WELD-TO-SHELL CONNECTION WILL BE SET TO
FLEXIBLE (BEHV=_F) BECAUSE CTYP=HINGE OR BOLT.

7548.0 *** USER INFORMATION MESSAGE 7548 (MDG4SW)

FOR PWELD ENTRY ID=%1, THE SPOT WELD WILL BE SET TO RIGID (BEHV=R_) BECAUSE
MTYP=EQUI.

7549.0 *** USER FATAL MESSAGE 7549 (SEPWLD)

FOR %6 ELEMENT ID=%1, THE PROJECTION OF GS GRID ID=%2 ONTO THE SURFACE
CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE.

User information: THE FIRST THREE SHELL GRIDS %7 ARE %3 %4 %5

7549.1 *** USER FATAL MESSAGE 7549 (MDG2ED)

FOR %7 ELEMENT ID=%1, WITH FORM=%2, THE PROJECTION OF %3 ONTO THE SUR-
FACE CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE.

User information: THE FIRST THREE SHELL GRIDS %8 ARE %4 %5 %6

7549.2 *** USER FATAL MESSAGE 7549 (MDG2ED)

Main Index
 848 MSC Nastran Error Messages
Errors 7000 - 7999

FOR %4 ELEMENT ID=%1, THE PROJECTION OF GS GRID ID=%2 ONTO THE SURFACE
CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE.

User information: THE CLOSEST SHELL GRID IS %3

7549.3 *** USER FATAL MESSAGE 7549 (MDG2ED)

FOR %5 ELEMENT ID=%1, WITH FORM=%2, THE PROJECTION OF %3 ONTO THE SUR-
FACE CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE.

User information: THE CLOSEST SHELL GRID IS %4

7549.4 *** USER FATAL MESSAGE 7549 (MDG2LD)

FOR %10 ELEMENT ID=%1, THE PROJECTION OF %2 GRID ID=%3 ONTO THE SURFACE
CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE.

User information: THE FIRST THREE SHELL GRIDS FOR SHELL A %11 ARE %4 %5 %6
THE FIRST THREE SHELL GRIDS FOR SHELL B %12 ARE %7 %8 %9

7549.5 *** USER FATAL MESSAGE 7549 (MDG2LD)

FOR %9 ELEMENT ID=%1, THE PROJECTION OF %2 ONTO THE SURFACE CANNOT BE
FOUND OR LIES OUTSIDE THE SURFACE.

User information: THE FIRST THREE SHELL GRIDS FOR SHELL A ARE %3 %4 %5
THE FIRST THREE SHELL GRIDS FOR SHELL B ARE %6 %7 %8

7549.6 *** USER FATAL MESSAGE 7549 (SEPWLD)

FOR %6 ELEMENT ID=%1, THE PROJECTION OF %9 GRID ID=%2 ONTO THE SURFACE
CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE. DISTANCE=%7, GSTOL=%8.

User information: THE FIRST THREE SHELL GRIDS %10 ARE %3 %4 %5

7549.7 *** USER FATAL MESSAGE 7549 (MDG2ED)

FOR %7 ELEMENT ID=%1, WITH FORM=%2, THE PROJECTION OF %3 ONTO THE SUR-
FACE CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE. DISTANCE=%8, GSTOL=%9.

User information: THE FIRST THREE SHELL GRIDS %10 ARE %4 %5 %6

Main Index
 MSC Nastran Error Messages 849
Errors 7000 - 7999

7549.8 *** USER FATAL MESSAGE 7549 (MDG2ED)

FOR %8 ELEMENT ID=%1, THE PROJECTION OF %2 ONTO THE SURFACE CANNOT BE
FOUND OR LIES OUTSIDE THE SURFACE. DISTANCE=%6, GSTOL=%7.

User information: THE FIRST THREE SHELL GRIDS %9 ARE %3 %4 %5

7549.9 *** USER FATAL MESSAGE 7549 (MDG2UD)

FOR %1 ELEMENT ID=%2, THE PROJECTION OF AUXILIARY POINT %3 ONTO THE SUR-
FACE CANNOT BE FOUND OR LIES OUTSIDE THE SURFACE.

User information: THE FIRST THREE SHELL GRIDS %7 ARE %4 %5 %6

7550.0 *** USER FATAL MESSAGE 7550 (MDG4SW)

FOR PWELD ENTRY ID=%1, THE DIAMETER OF THE SPOT WELD IS NOT GREATER THAN
ZERO.

User information: IF BEHV=FF OR FR, THEN THE DIAMETER MUST BE SPECIFIED.

7551.0 *** USER FATAL MESSAGE 7551 (BNDSP3)

BOUNDARY GRID %1B, WHICH INHERITS AN UPSTREAM COORDINATE SYSTEM ID=%2,
IS NOT TOTALLY CONSTRAINED FOR EITHER ALL TRANSLATIONS OR ALL ROTATIONS.

User action: DEFINE A COINCIDENT GRID AND COORDINATE SYSTEM IN THE DOWN-
STREAM SUPERELEMENT.

7552.0 *** USER INFORMATION MESSAGE 7551 (BNDSP3)

BOUNDARY GRID %1B WILL INHERIT ITS CONTRAINTS FROM UPSTREAM SUPERELE-
MENT(S).

7552.1 *** USER INFORMATION MESSAGE 7551 (BNDSP3)

Main Index
 850 MSC Nastran Error Messages
Errors 7000 - 7999

BOUNDARY GRID %1B WILL INHERIT ITS CONSTRAINTS FROM UPSTREAM SUPERELE-
MENT(S).
CONTRAINTS ARE APPLIED TO AN IMPLICIT BOUNDARY AND THUS SPCFORCE OUT-
PUT WILL NOT BE AVAILABLE.

User information: SPCFORCES WILL NOT BE REFLECTED IN THE GPFORCE, SPCFORCE

MAXIMA, AND SPCFORCE RESULTANT OUTPUTS.

User action: DEFINE A CONCIDENT GRID IN THE DOWNSTREAM SUPERELEMENT FOR

OUTPUT RECOVERY.

7553.0 *** USER INFORMATION MESSAGE 7553 (GP1D)

A TOTAL OF %1 DAREA BULK DATA ENTRIES FOR GRID AND SCALAR POINTS HAVE
BEEN CONVERTED TO EQUIVALENT FORCE / MOMENT / SLOAD ENTRIES (AS APPRO-
PRIATE)

User information:
Set NASTRAN SYSTEM(320) = n to request details of the first n of such conversions
(set n to a very large value to request details of all such conversions)
Set NASTRAN SYSTEM(320) = -1 to suppress all such conversions altogether

7553.1 *** USER INFORMATION MESSAGE 7553 (SECNVG)

A TOTAL OF %1 %2 BULK DATA ENTRIES HAVE BEEN CONVERTED TO EQUIVALENT %3
ENTRIES

User information:
Set NASTRAN SYSTEM(350) = n to request details of the first n of such conversions
(set n to a very large value to request details of all such conversions)
Set NASTRAN SYSTEM(350) = -1 to suppress all such conversions altogether

7553.2 *** USER INFORMATION MESSAGE 7553 (SECNVG)

A TOTAL OF %1 %2 AND %3 %4 BULK DATA ENTRIES HAVE BEEN CONVERTED TO
EQUIVALENT %5 ENTRIES

User information:
Set NASTRAN SYSTEM(350) = n to request details of the first n of such conversions
(set n to a very large value to request details of all such conversions)
Set NASTRAN SYSTEM(350) = -1 to suppress all such conversions altogether

Main Index
 MSC Nastran Error Messages 851
Errors 7000 - 7999

7553.3 *** USER INFORMATION MESSAGE 7553 (SECNVG)

A TOTAL OF %1 %2 BULK DATA ENTRIES, WHICH EMPLOY A THIRD GRID POINT TO
DEFINE THE ORIENTATION VECTOR, HAVE BEEN MODIFIED BY REPLACING THOSE
GRID POINTS BY EQUIVALENT VECTOR COORDINATES

User information:
Set NASTRAN SYSTEM(350) = n to request details of the first n of such modifications
(set n to a very large value to request details of all such modifications)
Set NASTRAN SYSTEM(350) = -1 to suppress all such modifications altogether

7554.0 *** USER FATAL MESSAGE 7554 (R3CGRT)

DRESP3 ENTRY %1 SPECIFIES AN UNDEFINED RESPONSE TYPE %2 FOR EXTERNAL
RESPONSE GROUP = %3.

User information: MAKE SURE THAT THE RESPONSE TYPE NAME ON THE DRESP3 ENTRY
MATCHES THE RESPONSE TYPE SPECIFICED IN THE SERVER ROUTINE.

7555.0 *** USER INFORMATION MESSAGE 7555

FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE
FOLLOWING ELEMENTS. METRIC VALUES THAT EXCEED TEST TOLERANCE LIMITS ARE
IDENTIFIED BY ONE OF THE FOLLOWING FLAGS PLACED TO THE RIGHT OF THE MET-
RIC VALUE.
"++++" FOR TEST RESULTS EXCEEDING TOLERANCES. INFORMATIONAL ONLY. PROB-
LEM SOLUTION CONTINUES. (DEFAULT FLAG)
"IGNR" FOR TEST RESULTS EXCEEDING TOLERANCES. INFORMATIONAL ONLY. PROB-
LEM SOLUTION CONTINUES.
"WARN" FOR TEST RESULTS EXCEEDING TOLERANCES. INFORMATIONAL ONLY. PROB-
LEM SOLUTION CONTINUES.
"FAIL" FOR TEST RESULTS EXCEEDING TOLERANCES. SEVERE ERROR. PROBLEM SOLU-
TION TERMINATES.

User action: USE THE GEOMCHECK (EXECUTIVE CONTROL STATEMENT) KEY-

WORD=VALUE TO CHANGE TOLERANCE VALUES IF DESIRED.

Main Index
 852 MSC Nastran Error Messages
Errors 7000 - 7999

User information: Element Geometry test tolerance levels and message limits can be changed by the
GEOMCHECK Executive Control statement.
The following keywords are available:
Q4_SKEW - modifies CQUAD4/CQUADR skew angle test tolerance.
Q4_TAPER - modifies CQUAD4/CQUADR taper ratio test tolerance.
Q4_WARP - modifies CQUAD4/CQUADR warping coefficient test tolerance.
Q4_IAMAX - modifies CQUAD4/CQUADR maximum interior angle test tolerance.
Q4_IAMIN - modifies CQUAD4/CQUADR minimum interior angle test tolerance.
T3_SKEW - modifies CTRIA3/CTRIAR skew angle test tolerance.
T3_IAMAX - modifies CTRIA3/CTRIAR maximum interior angle test tolerance.
TET_AR - modifies CTETRA aspect ratio test tolerance.
TET_EPLR - modifies CTETRA edge node point length ratio test tolerance.
TET_EPIA - modifies CTETRA edge node point interior angle test tolerance.
TET_DETJ - modifies CTETRA determinant of the Jacobian matrix test tolerance.
TET_DETG - modifies CTETRA determinant of the vertex points Jacobian matrix test tolerance.
HEX_AR - modifies CHEXA aspect ratio test tolerance.
HEX_EPLR - modifies CHEXA edge node point length ratio test tolerance.
HEX_EPIA - modifies CHEXA edge node point interior angle test tolerance.
HEX_DETJ - modifies CHEXA determinant of the Jacobian matrix test tolerance.
HEX_WARP - modifies CHEXA face warping coefficient test tolerance.
PEN_AR - modifies CPENTA aspect ratio test tolerance.
PEN_EPLR - modifies CPENTA edge node point length ratio test tolerance.
PEN_EPIA - modifies CPENTA edge node point interior angle test tolerance.
PEN_DETJ - modifies CPENTA determinant of the Jacobian matrix test tolerance.
PEN_WARP - modifies CPENTA face warping coefficient test tolerance.
BEAM_OFF - modifies CBEAM offset length ratio test tolerance.
BAR_OFF - modifies CBAR offset length ratio test tolerance.
MSGLIMIT - limit the number of messages that are generated.
MSGTYPE - modify the severity level of the test.

7555.1 *** USER INFORMATION MESSAGE 7555

FINITE ELEMENT GEOMETRY CHECK RESULTS EXCEED TOLERANCE LEVELS FOR THE
FOLLOWING ELEMENTS.

7555.2 *** USER FATAL MESSAGE 7555

Main Index
 MSC Nastran Error Messages 853
Errors 7000 - 7999

EMG MODULE TERMINATING DUE TO SEVERE FAILURE OF ELEMENT GEOMETRY

CHECK TESTS. THE ELEMENT TYPES, ELEMENT IDS AND FAILING TESTS ARE IDENTI-
FIED ON PREVIOUS PAGES WITH THE FLAG "FAIL" PLACED AFTER THE VALUE METRIC
OF THE TEST THAT FAILED.

7555.3 *** USER FATAL MESSAGE 7555

DATABLOCK ROT3ELPT NOT GENERATED CORRECTLY FOR ROTOR WITH ID %1

7556.0 *** USER FATAL MESSAGE 7556 (SEPMAB)

SUPERELEMENT %1 HAS BOTH INTERIOR STRUCTURAL AND FLUID GRID POINTS.

User action: REASSIGN GRID POINTS AND/OR ELEMENTS SO THAT THE SUPERELEMENT'S
INTERIOR AND EXTERIOR POINTS ARE ALL FLUID OR ITS INTERIOR POINTS ARE ALL
STRUCTURAL.

7557.0 *** User FATAL MESSAGE 7557 (SEQWRT)

THE FOLLOWING GRID POINT IDS ARE REFERENCED ON BULK DATA ENTRIES THAT
ARE NOT SUPPORTED IN AUTOMATIC SUPERELEMENTS
IF IT POSSESSES DEPENDENT DEGREES-OF-FREEDOM. THE UNSUPPORTED ENTRIES
ARE: DPHASE, DELAY, TIC, SUPORT, SUPORT1, CBUSH, AND CAABSF

User action: REMOVE THE GRIDS FROM ALL UNSUPPORTED ENTRIES OR REASSIGN THE
DEPENDENT DEGREES-OF-FREEDOM TO
INDEPENDENT DEGREES-OF-FREEDOM.
GRIDPOINTS:
-----------

7558.0 *** SYSTEM WARNING MESSAGE 7558 (RWELDD)

FOR SPOT WELD GRID GS ID=%1 THE CONSTRAINT EQUATIONS ARE INCOMPLETE.
THE CONSTRAINT FOR COMPONENT %2 CANNOT BE GENERATED BECAUSE THERE
ARE NOT ENOUGH UNCONSTRAINED DEGREES OF FREEDOM AVAILABLE FOR THE M-
SET.

7558.1 *** SYSTEM FATAL MESSAGE 7558 (RWELDD)

Main Index
 854 MSC Nastran Error Messages
Errors 7000 - 7999

FOR SPOT WELD GRID GS ID=%1 AN ILLEGAL GEOMETRY HAS BEEN DETECTED WHILE
CALCULATING THE CONSTRAINT MATRIX.

User action: CHECK GEOMETRY OF CWELD ELEMENT AND GS LOCATION. OTHERWISE,

CONTACT HEXAGON AB CLIENT SUPPORT.

7559.0 *** USER INFORMATION MESSAGE 7559 (TRLGCD/S and FRRD1A)

THIS %1 RESPONSE ANALYSIS INVOLVES THE FOLLOWING TYPES OF EXCITATION --

7559.1 *** USER FATAL MESSAGE 7559 (TRLGP)

SOL 400 DOES NOT SUPPORT ENFORCED DISPLACEMENT/VELOCITY/ACCELERATION
BY USING THE LARGE MASS METHOD.
PLEASE USE SPC/SPCD/SPCR TO DEFINE ENFORCED MOTION.

7560.0 *** USER FATAL MESSAGE 7560 (DSAD11)

MODE %1, WHICH IS SPECIFIED ON A DRESP1 ENTRY, HAS AN EIGENVALUE OF %2
WHICH IS LESS THAN (OR EQUAL TO) 0.0.

User information: THIS MODE COULD BE A RIGID BODY MODE.

User action: REVIEW LIST OF REAL EIGENVALUES AND SELECT ONLY ELASTIC MODE
NUMBER FOR ATTA FIELD (FIELD 7) ON DRESP1.

7561.0 *** SYSTEM FATAL MESSAGE 7561 (APD2)

THE NUMBER OF INTERFERENCE GROUPS EXCEEDS THE MAXIMUM NUMBER %1
ALLOWED.

7562.0 *** SYSTEM FATAL MESSAGE 7562 (MAPGEN)

THE SIZE OF THE MAPPING MATRIX CREATED IS %1 BY %2. IT SHOULD BE %3 BY %4.

7563.0 *** SYSTEM FATAL MESSAGE 7563 (SEP2MT)

POINT IDS %1 AND %2, WHICH ARE SPECIFIED ON THE DMIG BULK DATA ENTRY WITH
NAME=%3, ARE INTERIOR TO DIFFERENT SUPERELEMENTS OR MODULES.

7564.0 *** SYSTEM FATAL MESSAGE 7564 (MTMD36)

ERROR OCCURRED WHILE ATTEMPTING TO READ ASSOCIATED INDEX FOR FILE %1.

Main Index
 MSC Nastran Error Messages 855
Errors 7000 - 7999

7565.0 *** USER FATAL MESSAGE 7565 (SEQP)

NTIPS=%1 IS NOT DIVISIBLE BY THE NUMBER OF PROCESSORS=%2.

User action: MODIFIY THE VALUE OF NTIPS OR THE NUMBER OF PROCESSORS.

7566.0 *** USER WARNING MESSAGE 7566

THE FOLLOWING COMBINATION OF PARAMETER VALUES IS NOT VALID: NTIPS = %1,
TIPSCOL = %2, ZCOLLCT = %3.

User information: VALID SETTINGS REQUIRE TIPSCOL*ZCOLLCT <= NTIPS. THEREFORE,

TIPSCOL AND ZCOLLCT HAVE BEEN CHANGED TO A VALUE OF 2.

7567.0 *** USER FATAL MESSAGE 7567 (SEQP)

THE SUPER CASE CONTROL COMMAND HAS BEEN SPECIFIED.

User information: THE SUPER COMMAND IS NOT PERMITTED WITH THE AUTOMATIC
MODEL PARTITIONER.

User action: CONSOLIDATE AND REWRITE THE SUBCASES WITHOUT THE SUPER COM-
MAND.

7567.1 *** USER WARNING MESSAGE 7567 (SEQMRB)

THE SUPORT OR SUPORT1 BULK DATA ENTRY HAS BEEN SPECIFIED ALONG WITH
ACMS.

User information: THE SUPORT AND SUPORT1 ENTRIES WILL BE IGNORED.

7568.0 *** USER FATAL MESSAGE 7568 (SECNV1 and SECNV2)

POINT ID %1 REFERENCED ON THE %2 BULK DATA ENTRY %3 IS NOT A GRID POINT

7568.1 *** USER FATAL MESSAGE 7568 (SECNV3)

POINT ID %1 REFERENCED ON THE FOLLOWING %2 BULK DATA ENTRY %3 IS NOT A
GRID POINT

7569.0 *** USER FATAL MESSAGE 7569 (DOPR1B)

Main Index
 856 MSC Nastran Error Messages
Errors 7000 - 7999

INITIAL VALUE ON DESVAR ENTRY ID = %1 IS OUTSIDE THE RANGE OF DISCRETE VAL-

UES SPECIFIED ON DDVAL ENTRY ID = %2.

User action: CHANGE THE INITIAL VALUE ON THE DESVAR ENTRY OR THE DISCRETE
VALUES ON DDVAL ENTRY.

7569.1
TOPVAR OR BEADVAR OPTIMIZATION DOES NOT SUPPORT DDVAL ENTRY (DISCRETE
VALUES).
DDVAL bulk data entry will be ignored.

7570.0 *** USER INFORMATION MESSAGE 7570 ( VECPLX )

RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW:
PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %5
DIRECTION STRAIN ENERGY PASS/FAIL
--------- ------------- ---------
1 %6 %7
2 %8 %9
3 %10 %11
4 %12 %13
5 %14 %15
6 %16 %17
SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE:
1. CELASI ELEMENTS CONNECTING TO ONLY ONE GRID POINT;
2. CELASI ELEMENTS CONNECTING TO NON-COINCIDENT POINTS;
3. CELASI ELEMENTS CONNECTING TO NON-COLINEAR DOF;
4. IMPROPERLY DEFINED DMIG MATRICES;
5. CBEAM/CBEAM3 WITH GRID ID FOR WARPING DOF

7570.1 *** USER INFORMATION MESSAGE 7570 ( VECPLX )

Main Index
 MSC Nastran Error Messages 857
Errors 7000 - 7999

RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW:

PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %5
DIRECTION STRAIN ENERGY PASS/FAIL
--------- ------------- ---------
1 %6 %7
2 %8 %9
3 %10 %11
4 %12 %13
5 %14 %15
6 %16 %17
SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE:
1. MULTIPOINT CONSTRAINT EQUATIONS WHICH DO NOT SATISFY RIGID-BODY
MOTION;
2. RBE3 ELEMENTS FOR WHICH THE INDEPENDENT DEGREE-OF-FREEDOM
CANNOT DESCRIBE ALL POSSIBLE RIGID-BODY MOTIONS.

7570.2 *** USER INFORMATION MESSAGE 7570 ( VECPLX )

RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4%5%6 FOLLOW:
PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %7
DIRECTION STRAIN ENERGY PASS/FAIL
--------- ------------- ---------
1 %8 %9
2 %10 %11
3 %12 %13
4 %14 %15
5 %16 %17
6 %18 %19
SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE:
1. MPC EQUATIONS WHICH DO NOT SATISFY RIGID-BODY MOTION;
2. RBE3 ELEMENTS FOR WHICH THE INDEPENDENT DOF CANNOT DESCRIBE ALL
POSSIBLE RIGID-BODY MOTIONS;
3. PARAM,AUTOSPC HAS OVER-CONSTRAINED THE MODEL.

7570.3 *** USER INFORMATION MESSAGE 7570 ( VECPLX )

Main Index
 858 MSC Nastran Error Messages
Errors 7000 - 7999

RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW:

PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %5
DIRECTION STRAIN ENERGY PASS/FAIL
--------- ------------- ---------
1 %6 %7
2 %8 %9
3 %10 %11
4 %12 %13
5 %14 %15
6 %16 %17
SOME POSSIBLE REASONS MAY LEAD TO THE FAILURE:
CONSTRAINTS WHICH PREVENT RIGID-BODY MOTION.

7570.4 *** USER INFORMATION MESSAGE 7570 ( VECPLX )

RESULTS OF RIGID BODY CHECKS OF MATRIX %1%2 %3%4 FOLLOW:
PRINT RESULTS IN ALL SIX DIRECTIONS AGAINST THE LIMIT OF %5
DIRECTION STRAIN ENERGY PASS/FAIL
--------- ------------- ---------
1 %6 %7
2 %8 %9
3 %10 %11
4 %12 %13
5 %14 %15
6 %16 %17
IF THE MODEL HAS PASSED THE PREVIOUS CHECKS FOR THE G-SET AND N-SET,
THEN SOME POSSIBLE CAUSES ARE:
1. THE MODEL IS NOT INTENDED TO BE FREE-FREE WHICH INDICATES THAT THE
MODEL IS PROPERLY CONSTRAINED TO GROUND;
2. THE REFERENCE GRID POINT (GRID=GID ON THE GROUNDCHECK COMMAND)
IS LOCATED TOO FAR FROM THE MODEL'S CENTER OF GRAVITY. IT IS
RECOMMENDED THAT THE REFERENCE GRID POINT BE LOCATED AS CLOSE AS
POSSIBLE TO THE MODEL'S CENTER OF GRAVITY OF THE MODEL (SEE THE GRID
POINT WEIGHT GENERATOR OUTPUT);
3. PARAM,AUTOSPC,YES CONSTRAINS NEAR-SINGULAR DEGREES-OF-FREEDOM.
WHEN A FINITE ELEMENT MODEL WITH AUTOSPC FAILS THE A-SET CHECK, IT IS
NOT EVIDENT THAT GROUNDING HAS OCCURRED. THE USE OF PARAM,SNORM
WILL NOT ELIMINATE THE SPURIOUS FAILURE.

Main Index
 MSC Nastran Error Messages 859
Errors 7000 - 7999

7571.0 *** USER FATAL MESSAGE 7571 (DRESP3)

THE NUMBER OF CHARACTERS IN THE USRDATA FIELD ON DRESP3 ENTRY %1 IS %2
WHICH EXCEEDS THE MAXIMUM NUMBER OF %3 CHARACTERS.

7572.0 *** SYSTEM FATAL MESSAGE 7572 (DFMSYN)

A LOGIC ERROR was encountered IN THE SYMBOLIC PHASE OF THE SPARSE DECOMPOSI-
TION (EXTREME REORDERING).

User action: USE METIS OR MMD REORDERING TO AVOID THE ERROR.

RE-SUBMIT THE JOB WITH ONE OF THE FOLLOWING VALUES FOR SYSTEM(206):
SYSTEM(206)=1 (GRID BASED MMD)
SYSTEM(206)=8 (GRID BASED METIS) OR
SYSTEM(206)=9 (SELECTS BEST OF THE TWO ABOVE)

7572.1 *** SYSTEM WARNING MESSAGE 7572 (DFMSYN)

A LOGIC ERROR was encountered IN THE SYMBOLIC PHASE OF THE SPARSE DECOMPOSI-
TION (EXTREME REORDERING).

User information: THE SYMBOLIC PHASE WILL BE RERUN USING SYSTEM(206)=9 WHICH
SELECTS THE BEST OF GRID BASED MMD AND GRID BASED METIS.

7573.0 *** USER FATAL MESSAGE 7573 (MKAEF1)

AN AEFORCE BULK DATA ENTRY REFERENCES %1 ENTRY ID = %2 WHICH IS UNDE-
FINED.

7573.1 *** USER FATAL MESSAGE 7573 (MKAEF1)

AN AEFORCE BULK DATA ENTRY REFERENCES %1 ENTRY ID = %2 WHICH IS UNDE-
FINED.

7574.0 *** USER FATAL MESSAGE 7574 (MKAEF1)

THERE IS AEFORCE/STRUCT BULK DATA ENTRY, BUT NO REFERENCED UXVEC OR
FORCEI/MOMENTI BULK DATA ENTRY.

7575.0 *** USER FATAL MESSAGE 7575 (IFS4P)

Main Index
 860 MSC Nastran Error Messages
Errors 7000 - 7999

TEMPP3 BULK DATA CARD IS NO LONGER AVAILABLE.

User action: USE TEMPP1.

7576.0 *** SYSTEM WARNING MESSAGE 7576 (LDNSSEL)

UNABLE TO LOAD NSERVER_SELECT CLAUSE(S) FROM FILE.

User information: CLAUSE(S) WILL BE IGNORED.

User action: RE-ENTER CLAUSES OR CONTACT MSC CLIENT SUPPORT.

7577.0 *** SYSTEM WARNING MESSAGE 7577 (NSAINDX)

UNABLE TO PROCESS NSERVER_SELECT CLAUSE %1.

User information: CLAUSE WILL BE IGNORED.

User action: CHECK SYNTAX, INCREASE MEMORY.

7578.0 *** SYSTEM WARNING MESSAGE 7803 (NSAINDX)

CORRUPT NSERVER_SELECT MEMORY STORAGE AREA.

User information: CLAUSE(S) WILL BE IGNORED.

User action: REMOVE EXISTING CLAUSE(S) AND RE-ENTER.

7579.0 *** USER WARNING MESSAGE 7579 (NSASELK)

RELATION CLAUSE NOT FOUND IN NSERVER_SELECT
%1
NSERVER_SELECT IGNORED.

User action: ADD RELATION

7580.0 *** USER WARNING MESSAGE 7580 (NSASELK)

Main Index
 MSC Nastran Error Messages 861
Errors 7000 - 7999

USE EITHER RECORDNO=%1 OR ELTYPE=%2 BUT NOT BOTH

User information: NSERVER_SELECT IGNORED.

User action: CHANGE RELATION

7581.0 *** USER WARNING MESSAGE 7581 (NSSELWH)

NSERVER_SELECT WHERE CLAUSE STARTING WITH
%1
IS TOO LONG.

User information: WHERE CLAUSE IS IGNORED.

User action: REDUCE WHERE CLAUSE SIZE TO LESS THAN %2 CHARACTERS

7582.0 *** SYSTEM FATAL MESSAGE 7582 (..various..)

INTERNAL LOGIC ERROR. LOCW OFFSET VALUE TOO LARGE FOR 32-BIT INTEGER.
ERROR INFORMATION: %1
INVALID OFFSET VALUE: %2

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

7582.1 *** SYSTEM FATAL MESSAGE 7582

INTERNAL LOGIC ERROR. LOCW OFFSET VALUE TOO LARGE FOR 32-BIT INTEGER.
ERROR INFORMATION: %1 %2
INVALID OFFSET VALUE: %3

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

7583.0 *** USER FATAL MESSAGE 7583 (IFP6)

THE REFERENCED MATi BULK DATA ENTRY ID =%1 IS GREATER THAN 400000000.

User information: WHEN PCOMP BULK DATA ENTRIES ARE USE THE MATi IDs MUST BE
LESS THAN 400000000.

7583.1 *** USER FATAL MESSAGE 7583 (IFP6)

Main Index
 862 MSC Nastran Error Messages
Errors 7000 - 7999

THE REFERENCED MATi BULK DATA ENTRY ID =%1 IS GREATER THAN OR EQUAL TO
100000000.

User information: WHEN PCOMP BULK DATA ENTRIES ARE USED IN SOL200 THE MATi IDs
MUST BE LESS THAN 100000000.

7584.0 *** USER WARNING MESSAGE 7584 (MPFSIN)

THE CASE CONTROL SECTION DOES NOT CONTAIN A DEFINITION FOR SET ID %1.

User information: Panel grid mode participation factor processing will be skipped for this set.

7584.1 *** USER WARNING MESSAGE 7584 (MPFSIN)

PANEL NAMES SPECIFIED IN CASE CONTROL SET ID %1 DO NOT MATCH ANY NAMES
SPECIFIED ON THE PANEL BULK DATA ENTRIES. PANEL MODE PARTICIPATION FACTOR
CALCULATIONS WILL BE SKIPPED.

User action: CHECK THAT CORRECT CASE CONTROL SET ID WAS SPECIFIED AND THAT
SET CONTAINS VALID PANEL NAMES.

User information: Panel grid mode participation factor processing will be skipped for this set.

7584.2 *** USER WARNING MESSAGE 7584 (PFPSET)

THE ACOUSTIC PANEL "%2" SPECIFIED IN CASE CONTROL SET ID %1 CANNOT BE
FOUND.

User information: PARTICIPATION FACTOR OUTPUT WILL NOT BE GENERATED FOR THIS
PANEL.

7585.0 *** USER WARNING MESSAGE 7585 (MPFSIN)

GRID ID %1 SPECIFIED FOR PANEL %2%3 IS NOT A MEMBER OF THE A-SET IN THE
STRUCTURAL MODEL.

User information: No Mode participation factors will be computed.

7585.1 *** USER WARNING MESSAGE 7585 (MPFSTR)

Main Index
 MSC Nastran Error Messages 863
Errors 7000 - 7999

PANEL GRID POINT PARTICIPATION FACTORS FOR ALL POINTS OF PANEL %1 ARE NULL
DUE TO A NULL %2 MATRIX PARTITION.

User information: No Mode participation factors will be computed.

7585.2 *** USER WARNING MESSAGE 7585 (MPFSTR)

PANEL PARTICIPATION FACTORS FOR PANEL %1 ARE NULL BECAUSE THE ASSOCIATED
AREA FACTOR MATRIX IS PURGED.

User action: CHECK PANEL SET1 GRID POINT SPECIFICATION AND ENSURE THAT AT
LEAST ONE GRID POINT HAS A DEGREE OF FREEDOM PRESENT IN THE ANALYSIS SET.

User information: No Mode participation factors will be computed.

7585.3 *** USER WARNING MESSAGE 7585 (MCFRAC)

MODAL CONTRIBUTION FRACTION COMPUTATIONS ABORTED BECAUSE OF NULL
INPUT DATA MATRIX.

User information: No Modal Contribution Factors will be computed. Ensure that response DOF are in the
analysis set.

7586.0 *** USER WARNING MESSAGE 7586 (PARAML)

THE PARAML MODULE WITH DMI OPTION IS OVERFLOWING WITH A VALUE OF %1.
User action: REPLACE THE PARAML MODULE WITH THE SCALAR MODULE FOR THIS PUR-
POSE.

User information: The SCALAR module is able to extract double precision terms which allow numbers in
this range.

7586.1 *** USER WARNING MESSAGE 7586 (PARAML)

Main Index
 864 MSC Nastran Error Messages
Errors 7000 - 7999

THE PARAML MODULE WITH DMI OPTION IS OVERFLOWING WITH A VALUE OF

(%1,%2).

User action: REPLACE THE PARAML MODULE WITH THE SCALAR MODULE FOR THIS PUR-
POSE.

User information: The SCALAR module is able to extract double precision terms which allow numbers
in this range.

7586.2 *** USER WARNING MESSAGE 7586 (PRMLXY)

INVALID VALUE OF, %1%2, IS SPECIFIED FOR THE TYPE OF Y-VALUE IN X-Y PLOT COM-
MANDS.

User information:
The legitimate values are listed as follows:
ACCE : Acceleration in the physical set
BOUT : Slideline contact output
DISP : Displacement in the physical set
FMPF : Fluid modal participation factor
FORC : Element force
FPRE : Fluid pressure
GMPF : Panel Grid modal participation factor
LMPF : Load modal participation factor
MPCF : Multiple-point force of constraint
NFOR : Nonlinear applied load
OLOA : Applied load
PMPF : Panel modal participation factor
PRES : Pressure
SACC : Acceleration in the solution set
SDIS : Displacement in the solution set
SMPF : Structural modal participation factor
SPCF : Single-point force of constraint
STRA : Element strain
STRE : Element stress
SVEL : Velocity in the solution set
VELO : Velocity in the physical set
VG : Flutter analysis

Main Index
 MSC Nastran Error Messages 865
Errors 7000 - 7999

7586.3 *** USER WARNING MESSAGE 7586 (PRMLXY)

INVALID VALUE OF, %1%2, IS SPECIFIED FOR THE TYPE OF Y-VALUE IN X-Y PLOT COM-
MANDS.

7586.4 *** USER FATAL MESSAGE 7586 (PARAML)

REQUESTED MATRIX COLUMN NO. %1 EXCEEDS THE NUMBER OF COLUMNS (%2) OF
THE INPUT MATRIX, %3%4.

7587.0 *** USER WARNING MESSAGE 7587 (GKAM1C)

THE MODESELECT CASE CONTROL COMMAND FOR %1 IS IGNORED IN THIS MODAL
%2 ANALYSIS AS IT REFERENCES BOTH AN UNDEFINED SET %3 AND A NON-EXISTENT
%1 MODE %3

7587.1 *** USER WARNING MESSAGE 7587 (GKAM1C)

THE UNCONSET KEYWORD IN THE MODESELECT CASE CONTROL COMMAND FOR %1
IS IGNORED IN THIS MODAL %2 ANALYSIS AS IT REFERENCES BOTH AN UNDEFINED
SET %3 AND A NON-EXISTENT %1 MODE %3

7588.0 *** USER INFORMATION MESSAGE 7588 (GKAM)

BASED ON THE MODESELECT CASE CONTROL COMMAND, ONLY %1 OF THE %2 COM-
PUTED %3 MODES (MODES %4 THROUGH %5) WILL BE USED IN THIS MODAL %6 ANAL-
YSIS (DETAILS OF THE %7 DATA FOR THE MODES USED ARE GIVEN BELOW)

7588.1 *** USER INFORMATION MESSAGE 7588 (GKAM)

BASED ON THE USER PARAMETERS LMODES, LFREQ OR HFREQ, ONLY %1 OF THE %2
COMPUTED %3 MODES (MODES %4 THROUGH %5) WILL BE USED IN THIS MODAL %6
ANALYSIS (DETAILS OF THE %7 DATA FOR THE MODES USED ARE GIVEN BELOW)

7588.2 *** USER INFORMATION MESSAGE 7588 (GKAM)

BASED ON THE USER PARAMETERS LMODESFL, LFREQFL OR HFREQFL, ONLY %1 OF
THE %2 COMPUTED %3 MODES (MODES %4 THROUGH %5) WILL BE USED IN THIS
MODAL %6 ANALYSIS (DETAILS OF THE %7 DATA FOR THE MODES USED ARE GIVEN
BELOW)

7589.0 *** USER INFORMATION MESSAGE 7589 (GKAM)

Main Index
 866 MSC Nastran Error Messages
Errors 7000 - 7999

BASED ON THE MODESELECT CASE CONTROL COMMAND, ONLY %1 OF THE %2 COM-

PUTED %3 MODES WILL BE USED IN THIS MODAL %4 ANALYSIS (DETAILS OF THE %5
DATA FOR THE MODES USED ARE GIVEN BELOW)

7589.1 *** USER INFORMATION MESSAGE 7589 (GKAM)

BASED ON THE MODESELECT CASE CONTROL COMMAND, ALL %1 OF THE COMPUTED
%2 MODES WILL BE USED IN THIS MODAL %3 ANALYSIS

7590.0 *** USER FATAL MESSAGE 7590.

CWELD ELEMENT ID %1 CONNECTS TO A SURFACE WHICH HAS AN INTERIOR ANGLE
POSSIBLY GREATER THAN OR EQUAL TO 180 DEGREES.

7591.0 *** USER FATAL MESSAGE 7591 (STPDA)

A PAERO4 (STRIP THEORY) BULK DATA ENTRY USES THE PRANDTL-GLAUERT
COMPRESSIBILITY CORRECTION (CLA=-1) AND SPECIFIES A SUPERSONIC MACH
NUMBER OF %1 ON THE ACCOMPANYING %2 ENTRY. WITH THE SWEEP
ANGLE OF %3 DEGREES, THIS RESULTS IN A CONFIGURATION WHERE THE
PRANDTL-GLAUERT CORRECTION IS NOT APPLICABLE.

User information: THE CLA = -1 OPTION IS ONLY APPLICABLE AT SUBSONIC

SPEEDS. IF STRIP THEORY IS TO BE USED SUPERSONICALLY, SET CLA=1 OR
CLA=0 WITH NCIRC .NE. 0

7592.0 *** USER FATAL MESSAGE 7592 (A?)

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-
TOR.

7592.1 *** USER FATAL MESSAGE 7592 (A?)

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-
TOR.
THERE ARE DUPLICATE STATES IN THE DATABASE OVER WHICH INTERPOLATION IS
NEEDED.

User action: REMOVE THE DUPLICATE STATES.

7592.2 *** USER FATAL MESSAGE 7592 (A?)

Main Index
 MSC Nastran Error Messages 867
Errors 7000 - 7999

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-

TOR.
THERE ARE TOO FEW STATES TO INTERPOLATE OVER THE DIMENSIONALITY OF THE
SPACE.

User action: INCREASE THE NUMBER OF POINTS TO SPAN THE SPACE, OR REMOVE OR
CONSTRAIN SOME DIMENSIONS FROM THE INTERPOLATION.

7592.3 *** USER FATAL MESSAGE 7592 (A?)

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-
TOR.
THE INTERPOLATION MATRIX BG IS SINGULAR.

User action: REDEFINE THE SET OF HARD POINTS BY EITHER ADDING OR DELETING
SOME INSTANCES.

7592.4 *** USER FATAL MESSAGE 7592 (A?)

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-
TOR.
THE INTERPOLATION MATRIX A3 IS SINGULAR.

User action: REDEFINE THE SET OF HARD POINTS BY EITHER ADDING OR DELETING
SOME INSTANCES.

7592.5 *** USER FATAL MESSAGE 7592 (A?)

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-
TOR.
A PARAMETER (DIMENSION) IN THE INTERPOLATION HAS ONLY A SINGLE KNOWN
VALUE, BUT YOU HAVE REQUESTED INTERPOLATION TO A DIFFERENT VALUE.

User action: FIX VALUES OF CONSTANTS AT THE DATABASE VALUE, OR ADD ADDI-
TIONAL STATES TO ALLOW INTERPOLATION.

7592.6 *** USER FATAL MESSAGE 7592 (A?)

Main Index
 868 MSC Nastran Error Messages
Errors 7000 - 7999

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-

TOR.
THE NONLINEAR DATABASE INTERPOLATION FAILED TO FIND A USABLE SET OF
STATES WITH THE MINIMUM 2 VALUES PER PARAMETER.

User action: ADD ADDITIONAL STATES TO THE DATABASE.

7592.7 *** USER FATAL MESSAGE 7592 (A?)

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-
TOR.
THERE IS AN INADEQUATE SET OF STATES TO PERFORM THE INTERPOLATION.

User action: ADD ADDITIONAL STATES TO THE DATABASE.

7592.8 *** USER FATAL MESSAGE 7592 (A?)

ERROR CODE %1 HAS OCCURRED IN THE NONLINEAR AERO DATABASE INTERPOLA-
TOR.
THERE IS AN IN ADEQUATE SET OF STATES IN THE SECONDARY SEARCH.

User action: ADD ADDITIONAL STATES TO THE DATABASE.

7593.0 *** USER WARNING MESSAGE 7593 (MDG2SP)

THE MSET FIELD IS SPECIFIED OFF ON PWELD ENTRY ID %1 FOR CWELD ELEMENT ID
%2.

User information: MSET IS RESET TO ON BECAUSE MSET=OFF IS ONLY AVAILABLE WHEN

TWO SURFACE PATCHES ARE CONNECTED.

7594.0 *** USER FATAL MESSAGE 7594 (MDG2SW)

Main Index
 MSC Nastran Error Messages 869
Errors 7000 - 7999

TWO SURFACE PATCHES WHICH ARE CONNECTED BY CWELD ELEMENT ID %1 SHARE

THE SAME GRID ID %2.

User information: THE CWELD ELEMENT WILL BE IGNORED BECAUSE IT CONNECTS TWO
SURFACE PATCHES WHICH ARE ALREADY CONNECTED THROUGH AT LEAST ONE
COMMON GRID.

User action: TO ENSURE THE ELEMENT IS NOT IGNORED THEN CORRECT THE CONNEC-
TIVITY OR SET MSET TO ON THE REFERENCED PWELD ENTRY.

7594.1 *** USER FATAL MESSAGE 7594 (MDG2CV)

TWO SURFACE PATCHES WHICH ARE CONNECTED BY CWELD ELEMENT ID %1 SHARE
THE SAME GRID ID %2.

User information: THE CWELD ELEMENT WILL BE IGNORED BECAUSE IT CONNECTS TWO
SURFACE PATCHES WHICH ARE ALREADY CONNECTED THROUGH AT LEAST ONE
COMMON GRID.

7595.0 *** USER FATAL MESSAGE 7595 (MDG2ED)

FOR %4 ELEMENT ID=%1, THE ANGLE (%2 DEGREE) BETWEEN SHELL A AND SHELL B IS
GREATER THAN GSPROJ (%3 DEGREE).

7596.0 *** USER FATAL MESSAGE 7596 (FRRD1A)

AN ENFORCED VELOCITY OR ACCELERATION IS SPECIFIED AT ZERO FREQUENCY.

User action: REMOVE THE ZERO FREQUENCY FROM THE SELECTED FREQi BULK DATA
ENTRY.

7597.0 *** USER WARNING MESSAGE 7597 (PQVOLD)

ELEMENT ID = %1 REFERENCED BY GMQVOL ENTRY WITH LID = %2 IS UNDEFINED.

User action: CHECK GMQVOL ENTRY TO ENSURE THAT SPECIFIED ELEMENT EXISTS.

7598.0 *** SYSTEM WARNING MESSAGE 7598 (MTMD40)

ATTEMPTED TO CONVERT THE PRECISION OF THE %1 PARAMETER.

User information: SOME PRECISION MAY BE LOST.

Main Index
 870 MSC Nastran Error Messages
Errors 7000 - 7999

7599.0 *** SYSTEM WARNING MESSAGE 7599 (PREBRD)

INPUT MATRIX %1 IS INCOMPATIBLE WITH RESPECT TO INPUT DATABLOCK EQMAP.
THE NUMBER OF ROWS IN THE MATRIX IS %2, BUT THE LOCAL F-SIZE ACCORDING TO
EQMAP IS %3.

User action:
1. CHECK YOUR DMAP ALTER IF YOU ARE USING ONE.
2. CONTACT HEXAGON AB CLIENT SUPPORT.

7600.0 *** USER WARNING MESSAGE 7600 (NLTRD2)

INITIAL TIME STEP SIZE IS REDUCED TO %1.

7600.1 *** USER WARNING MESSAGE 7600 (NL3LOP)

THE INPUT TIME STEP SIZE %1 IS USED AS THE INITIAL TIME STEP SIZE.

7601.0 *** SYSTEM FATAL MESSAGE 7601 (NCONVG)

NUMERIC OVERFLOW ENCOUNTERED DURING THE CALCULATION OF CONVER-
GENCE PARAMETERS.

User information: THIS CONDITION MAY BE CAUSED BY ZERO OR LOW INITIAL TEMPERA-
TURES (SEE TEMP AND TEMPD BULK DATA ENTRIES) FOR RADIATION HEAT TRANSFER
ANALYSIS AND MAY BE RESOLVED BY RAISING THE INITIAL TEMPERATURE.

7602.0 *** USER WARNING MESSAGE 7602 (DOPR1I)

ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY
VALUE %4 IS GREATER THAN THE MAXIMUM PMAX VALUE %5 SPECIFIED ON THE %6
%7 ENTRY.

User action: MODIFY THE PROPERTY ENTRY ON THE %8 ENTRY ACCORDINGLY.

User information: STARTING THE DESIGN WITH INFEASIBLE PROPERTIES WILL IMPEDE
THE DESIGN PROCESS.

7602.1 *** USER WARNING MESSAGE 7602 (DOPR1I)

Main Index
 MSC Nastran Error Messages 871
Errors 7000 - 7999

ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY

VALUE %4 IS LESS THAN THE MINIMUM PMIN VALUE %5 SPECIFIED ON THE %6 %7
ENTRY.

User action: MODIFY THE PROPERTY ENTRY ON THE %8 ENTRY ACCORDINGLY.

User information: STARTING THE DESIGN WITH INFEASIBLE PROPERTIES WILL IMPEDE
THE DESIGN PROCESS.

7602.2 *** USER FATAL MESSAGE 7602 (DOPR1I)

ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY
VALUE %4 IS GREATER THAN THE MAXIMUM PMAX VALUE %5 SPECIFIED ON THE %6
%7 ENTRY.

User information: STARTING THE DESIGN WITH INFEASIBLE PROPERTIES WILL IMPEDE
THE DESIGN PROCESS.

User action:
1. MODIFY THE PROPERTY ENTRY ON THE %8 ENTRY ACCORDINGLY, OR
2. USE PLVIOL,1 ON DOPTPRM TO FORCE THE DESIGN PROCESS TO PROCEED WITH
INFEASIBLE PROPERTIES
(MAY PRODUCE LESS DESIRABLE RESULTS)

7602.3 *** USER FATAL MESSAGE 7602 (DOPR1I)

ON PROPERTY ENTRY %1 WITH PID=%2 AND PROPERTY NAME=%3, THE PROPERTY
VALUE %4 IS LESS THAN THE MINIMUM PMIN VALUE %5 SPECIFIED ON THE %6 %7
ENTRY.

7602.4 *** USER FATAL MESSAGE 7602 (DPR1A1)

ON %1 ENTRY ID=%2 AND PROPERTY NAME=%3, THE PROPERTY VALUE %4 IS LESS
THAN THE MINIMUM VALUE %5 SPECIFIED ON RANDVAR ENTRY %6.

User action: EITHER MODIFY %1 ENTRY %2 OR MODIFY THE LOWER BOUND ON RAND-
VAR ENTRY %6 ACCORDINGLY.

Main Index
 872 MSC Nastran Error Messages
Errors 7000 - 7999

7602.5 *** USER FATAL MESSAGE 7602 (DPR1A1)

ON %1 ENTRY ID=%2 AND PROPERTY NAME=%3, THE PROPERTY VALUE %4 IS GREATER
THAN THE MAXIMUM VALUE %5 SPECIFIED ON RANDVAR ENTRY %6.

User action: EITHER MODIFY %1 ENTRY %2 OR MODIFY THE UPPER BOUND ON RAND-
VAR ENTRY %6 ACCORDINGLY.

7603.1 *** SYSTEM INFORMATION MESSAGE 7603 (DMKCRD)'

METHOD I IS SELECTED BY THE PROGRAM TO PERFORM TRIPLE MATRIX PRODUCT

7603.2 *** SYSTEM INFORMATION MESSAGE 7603 (DMKCRD)'

METHOD II IS SELECTED BY THE PROGRAM TO PERFORM TRIPLE MATRIX PRODUCT

7603.3 *** SYSTEM INFORMATION MESSAGE 7603 (DMKCRD)'

METHOD I IS SELECTED BY THE USER TO PERFORM TRIPLE MATRIX PRODUCT

7603.4 *** SYSTEM INFORMATION MESSAGE 7603 (DMKCRD)'

METHOD II IS SELECTED BY THE USER TO PERFORM TRIPLE MATRIX PRODUCT

7604.0 *** USER FATAL MESSAGE 7604 (DOPR1I)

A DESIGNED PROPERTY DIFFERS FROM THE VALUE PROVIDED ON THE PROPERTY
ENTRY BY MORE THAN %1.

User action: MODIFY EITHER THE PROPERTY ENTRY, THE %2 %3 ENTRY OR PTOL ON
THE DOPTPRM ENTRY.

7604.1 *** USER FATAL MESSAGE 7604 (DOPR1h)

BULK DATA ENTRY %1 IS MISSING FROM INPUT DECK. HENCE, IT CAN NOT BE REFER-
ENCED BY DESIGN MODEL.

User action: CHECK INPUT DECK

7605.0 *** USER FATAL MESSAGE 7605 (TRD1G)

Main Index
 MSC Nastran Error Messages 873
Errors 7000 - 7999

TIC BULK DATA ENTRY %1 ILLEGALLY REFERENCES A MODAL COORDINATE (%2)

RATHER THAN A GRID, SCALAR OR EXTRA POINT

User information: TIC BULK DATA ENTRY REFERENCED BY AN IC OR IC(PHYSICAL) CASE

CONTROL COMMAND MAY NOT REFERENCE A MODAL COORDINATE.

7606.0 *** USER FATAL MESSAGE 7606 (TRD1G)

TIC BULK DATA ENTRY %1 REFERENCES MODAL COORDINATE %2 WHICH EXCEEDS
THE NUMBER OF MODES USED IN THE ANALYSIS

7607.0 *** USER FATAL MESSAGE 7607 (TRD1G)

TIC BULK DATA ENTRY %1 REFERENCES A GRID OR SCALAR POINT RATHER THAN A
MODAL COORDINATE OR AN EXTRA POINT

User information: TIC BULK DATA ENTRY REFERENCED BY AN IC(MODAL) CASE CONTROL
COMMAND MAY ONLY REFERENCE A MODAL COORDINATE OR AN EXTRA POINT.

User action:
CHECK THE TIC DATA FOR REFERENCES TO A GRID OR SCALAR POINT.

7608.0 *** SYSTEM FATAL MESSAGE 7608 (ERBRD(S),ERJND(S),ERRDD(S))

IN NONLINEAR ELEMENT OR DIFFERENTIAL STIFFNESS GENERATION, THE DISPLACE-
MENT VECTOR IS NOT AVAILABLE TO COMPUTE THE CURRENT GRID POINT POSI-
TIONS FOR %1 ELEMENTS.

7608.1 *** USER FATAL MESSAGE 7608 (ERBRD(S),ERJND(S),ERRDD(S))

The rigid element formulation with MDLPRM, RBAROPT=1.0 does not support left rotation.

User action: Do not set SYSTEM(420)=0

7609.0 *** USER FATAL MESSAGE 7609 (ERJND(S))

THE LENGTH OF RJOINT ELEMENT, ID = %1, IS NOT ZERO.

7610.0 *** USER FATAL MESSAGE 7610 (DOPR1C)

Main Index
 874 MSC Nastran Error Messages
Errors 7000 - 7999

ALL COEFI VALUES ON %1 ENTRY ID = %2 ARE 0.0

User action: SET AT LEAST ONE OF THE COEFI VALUES TO A NON-ZERO VALUE

7610.1 *** USER FATAL MESSAGE 7610 (DOPR1C)

%1 entry ID = %2 references the same design variable ID more than once.

User information: The %3 entry does not support multiple references to the same design variable ID.

User action: Remove the duplicate reference to the same design variable ID.

7611.0 *** USER FATAL MESSAGE 7611 (GP4RG)

THE NUMBER OF UM DEGREES-OF-FREEDDOM IS NOT EQUAL TO THE NUMBER OF
REFERENCE DEGREES-OF-FREEDOM FOR RBE3, ID=%1.

7611.1 *** USER FATAL MESSAGE 7611 (GP4RG)

THE REFERENCE GRID ID, %1, IS ALSO SPECIFIED AS THE INDEPENDENT GRID ID FOR
RBE3, ID=%2.

7612.0 *** USER FATAL MESSAGE 7612 (GP4RG)

THE UM DEGREE-OF-FREEDOM, GRID ID=%1, COMPONENT=%2, IS NOT A SUBSET OF
THE REFERENCE AND THE INDEPENDENT DEGREES-OF-FREDOM FOR RBE3, ID=%3.

7613.0 *** USER FATAL MESSAGE 7613 (MDG2RG,IFP1D)

ILLEGAL VALUE ON 'PARAM,RIGID' OR CASE CONTROL COMMAND 'RIGID'.

User information: THE LEGAL VALUE IS LNELIM, LGELIM, OR LAGR.

7614.0 *** USER FATAL MESSAGE 7614 (MDG2RG)

THE RIGID_ELEMENT_TYPE IS IN CONFLICT WITH THE SOLUTION SEQUENCE OR
USER INPUT ON DATA ENTRY 'PARAM,RIGID'.

User action: USE CASE CONTROL COMMAND 'RIGID' TO REQUEST THE APPROPRIATE
RIGID_ELEMENT_TYPE.

7615.0 *** USER FATAL MESSAGE 7615 (MDG2RG)

Main Index
 MSC Nastran Error Messages 875
Errors 7000 - 7999

FOR NONLINEAR SOLUTION SEQUENCE, THE CASE CONTROL COMMAND

'RIGID=LGELIM' IS ILLEGAL.

User information: THE LEGAL VALUE IS 'LINEAR' OR 'LAGR'.

7616.0 *** SYSTEM FATAL MESSAGE 7616 (MTXIND,MTXIDS)

FOR INSERTION OF A MATRIX INTO ANOTHER, THE INSERTION LOCATION IS OUT OF
BOUNDS.

Programmer information: THE SIZE OF DATA RECEIVING MATRIX IS %1,%2, THE INSER-
TION LOCATION IS %3,%4.

7616.1 *** SYSTEM FATAL MESSAGE 7616 (MTXETD,MTXETS)

FOR EXTRACTION OF A MATRIX FROM ANOTHER, THE EXTRACTION LOCATION IS
OUT OF BOUNDS.

Programmer information: THE SIZE OF THE MATRIX TO BE EXTRACTED FROM IS %1,%2,

THE EXTRACTION LOCATION IS %3,%4.

7617.0 *** SYSTEM FATAL MESSAGE 7617 (UPVADD,UPVADS)

THE INPUT VALUE FOR CONSTANT BETA OR TIME STEP DT IS ZERO IN THE HHT-BETA
INTEGRATION METHOD, WHICH WILL CAUSE DIVISION BY ZERO TERMINATION.

7618.0 *** SYSTEM FATAL MESSAGE 7618 (UPVADD,UPVADS,NL3DSD,NL3DSS)

UNKNOWN GRID POINT TYPE %1 FOUND.

Programmer information: THE GRID TYPE MUST BE 1, 2, 3, OR 7.

7619.0 *** SYSTEM FATAL MESSAGE 7619 (MODQSET)

PROGRAM DETECTED AT LEAST ONE %1 ENTRY.

User action: TO USE ACMS WITH AUTO-QSET, PLEASE REMOVE ALL %2 RECORDS OR DO
NOT USE AUTO-QSET.

7620.01 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot free the memory block named "%1" because it is not allocated.

Main Index
 876 MSC Nastran Error Messages
Errors 7000 - 7999

7620.02 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot keep the first %1 elements of the memory block named "%2" because it is not allocated.

7620.03 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot reduce %1 elements from the end of the memory block named "%2" because it is not allocated.

7620.04 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Invalid length to Reduce.

7620.05 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot keep the first %1 elements of the block named "%2".

7620.06 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot keep the first %1 elements of the block named "%2" which contains only %3 elements.

7620.07 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot reduce %1 elements from the end of the block named "%2"

7620.08 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot reduce %1 elements from the end of the block named "%2" which contains only %3 elements.

7620.09 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

No memory blocks in group "%1" will be released because none are allocated.

7620.10 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Memory block name "%1" is longer than the limit of %2 characters.

7620.11 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Memory block name "%1" contains illegal character "%2" at position %3.

7620.12 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Memory group name "%1" is longer than the limit of %2 characters.

7620.13 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Memory group name "%1" contains illegal character "%2" at position %3.

Main Index
 MSC Nastran Error Messages 877
Errors 7000 - 7999

7620.14 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Memory block "%1" not allocated because a block with the same name is already allocated.

7620.15 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Invalid number of elements in memory allocation requesting %1 elements of type "%2" for block named
"%3" in group "%4".

7620.16 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Invalid numeric type in memory allocation requesting %1 elements of type "%2" for block named %3 in
group "%4".

7620.18 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Insufficient dynamic memory to satisfy request for %1 words.

7620.19 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Unable to allocate %1 words of memory from the operating system.

7620.20 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic allocation of memory from the operating system is not allowed unless DMSIZE is called to set the
memory block sizes

7620.21 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

First dynamic memory block has been overwritten.

7620.22 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has been overwritten which follows block named "%1" in group "%2" with %3
element of type "%4"

7620.23 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has been overwritten which follows block named "%1" in group "%2" with %3
elements of type "%4"

7620.24 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has been overwritten which follows anonymous block in group "%1" with %2 ele-
ment of type "%3

Main Index
 878 MSC Nastran Error Messages
Errors 7000 - 7999

"
7620.25 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)
Dynamic memory block has been overwritten which follows anonymous block in group "%1" with %2 ele-
ments of type "%3"

7620.26 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

First dynamic memory block has incorrect checksum

7620.27 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has incorrect checksum which follows block named "%1" in group "%2" with %3
element of type "%4".

7620.28 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has incorrect checksum which follows block named "%1" in group "%2" with %3
elements of type "%4".

7620.29 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has incorrect checksum which follows anonymous block in group "%1" with %2
element of type "%3".

7620.30 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has incorrect checksum which follows anonymous block in group "%1" with %2
elements of type "%3".

7620.31 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

All %1 banks of dynamic memory are active.

7620.32 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory bank %1 may not be suspended because it is the only active bank.

7620.33 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory bank %1 may not be activated because the number is invalid.

7620.34 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory bank %1 may not have its free space reclaimed because the number is invalid.

7620.35 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Main Index
 MSC Nastran Error Messages 879
Errors 7000 - 7999

Dynamic memory bank %1 may not be activated because it is already active.

7620.36 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory bank %1 may not be activated because it is has not been initialized.

7620.37 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Free space may not be reclaimed from dynamic memory bank %1 because the memory bank only has free
space

7620.38 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory bank %1 may not be terminated until all allocated memory blocks in the bank are freed

7620.39 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

A new dynamic memory bank can not be created from %1 words because the minimum requirement is %2
words

7620.40 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block pointer does not reference a valid memory block

7620.41 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Cannot find the memory block named "%1" because it is not allocated

7620.42 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory bank %1 may not be terminated because its memory was allocated from the operating
system

7620.43 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Insufficient dynamic memory to satisfy request for %1 words

7620.44 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Conflicting configuration prevents Dynamic Memory from being allocated, because the
Dynamic Initial Memory of %1 words exceeds the Maximum Memory allowed of %2 words

7620.45 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic Memory initial size of %1 is invalid because it is negative

Main Index
 880 MSC Nastran Error Messages
Errors 7000 - 7999

7620.46 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic Memory increment size of %1 is invalid because it is negative

7620.47 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic Memory maximum size of %1 is invalid because it is negative

7620.48 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Size of Dynamic Memory cannot be set because one or more Dynamic Memory Blocks have already been
allocated

7620.49 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Unknown option "%1" for Dynamic Memory Manager

7620.50 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Invalid value "%1" for Dynamic Memory Manager option "%2"

7620.51 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has been overwritten

7620.52 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Dynamic memory block has incorrect checksum

7620.70 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Finding dynamic memory block named %1

7620.71 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Freeing dynamic memory group named %1

7620.72 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Allocating dynamic memory block named %1 in group %2 with %3 element of type %4

7620.73 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Allocating dynamic memory block named %1 in group %2 with %3 elements of type %4

7620.74 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Allocating anonymous dynamic memory block in group %1 with %2 element of type %3

Main Index
 MSC Nastran Error Messages 881
Errors 7000 - 7999

7620.75 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Allocating anonymous dynamic memory block in group %1 with %2 elements of type %3

7620.76 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Allocated %1 words from operating system for initial Dynamic Memory

7620.77 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Allocated %1 words from operating system to extend Dynamic Memory

7620.78 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Keeping first element of dynamic memory block named %1

7620.79 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Keeping first %1 elements of dynamic memory block named %2

7620.80 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Reducing dynamic memory block named %1 by one element

7620.81 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Reducing dynamic memory block named %1 by %2 elements

7620.82 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Initializing new memory bank from %1 words

7620.83 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Reclaiming unused space from memory bank # %1

7620.84 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Suspending memory bank # %1

7620.85 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Terminating memory bank # %1

7620.86 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Activating memory bank # %1

Main Index
 882 MSC Nastran Error Messages
Errors 7000 - 7999

7620.99 *** SYSTEM FATAL MESSAGE 7620 (DMERROR)

Unknown error message %1 from the Dynamic Memory Manager

7621.0 *** USER FATAL MESSAGE 7621 (SEEFMB)

THE BAND KEYWORD IN THE SEEFM CASE CONTROL COMMAND REFERENCES UNDE-
FINED FRBAND/FRBAND1 BULK DATA ENTRY %1

7622.0 *** USER FATAL MESSAGE 7622 (SEEFMD)

THE DLF KEYWORD IN THE SEEFM CASE CONTROL COMMAND REFERENCES UNDE-
FINED SEDLF/SEDLF1 BULK DATA ENTRY %1

7623.0 *** USER FATAL MESSAGE 7623, DOMLOC.

RECORD IN FILE%1 HAS LESS THAN 2 WORDS.

7624.0 *** SYSTEM FATAL MESSAGE 7624 (GKAM)

THE NUMBER OF EIGENVECTORS (%1) IN THE %2 MATRIX IS GREATER THAN THE
NUMBER (%3) OF COMPUTED EIGENVALUES IN THE %4 %5

7625.0 *** USER WARNING MESSAGE 7625 (MDG2SM)

THE GRID ID=%1 ASSIGNED TO GE ON CSEAM ELEMENT ID=%2 IS CONNECTED TO THE
GRID ID=%3 ASSIGNED TO GS ON CSEAM ELEMENT ID=%4 WITH A DIFFERENT SEAM
LINE LABEL.

7626.0 *** USER FATAL MESSAGE 7626 (MDG2SM)

FOR CSEAM ELEMENT ID=%1, THE %2 GRID ID=%3 IS NOT UNIQUE.

User information: A NON-UNIQUE %4 GRID ID WILL CREATE A BRANCH ON THE SEAM

LINE.

7627.0 *** USER FATAL MESSAGE 7627 (IFPxSEAM)

FOR CSEAM ELEMENT ID=%1, BOTH COORDINATES (XS,YS,ZS) AND (XE,YE,ZE) ARE
ZERO.

User information: THIS ERROR MAY BE CAUSED BY A MISSING CONTINUATION ENTRY.

7629.0 *** USER FATAL MESSAGE 7629 (DOPR3C)

Main Index
 MSC Nastran Error Messages 883
Errors 7000 - 7999

%1 ENTRY ID = %2 IS IDENTICAL TO A DRESP1 ENTRY ID.

7630.0 *** USER FATAL MESSAGE 7629 (DOPR3)

METHOD SELECTED ON EIGC %1 IS NEITHER CLAN NOR HESS.

User action: CHANGE METHOD IN ABOVE MENTIONED EIGC TO CLAN OR HESS

7630.1 *** USER FATAL MESSAGE 7630.1 (DOPR3)

A REAL EIGNENANALYSIS IS REQUESTED USING METHOD = %1 BUT THERE ARE NO
EIGR OR EIGRL BULK DATA ENTRIES

7630.2 *** USER FATAL MESSAGE 7630.2 (DOPR3)

A COMPLEX EIGNENANALYSIS IS REQUESTED USING CMETHOD = %1 BUT THERE ARE
NO CEIG BULK DATA ENTRIES

7631.0 *** USER FATAL MESSAGE 7631 (ESTBED)

FOR CWSEAM ELEMENT ID=%1, A CONNECTION TO ONE OF THE SHELL SURFACES
CANNOT BE MADE.

User information: THE SEAM WELD AXIS AND ONE OF THE SHELL NORMALS ARE POINT-
ING IN THE SAME DIRECTION.

7632.0 *** USER FATAL MESSAGE 7632 (EWLDPD)

FOR CWELD ELEMENT ID=%1, A CONNECTION TO ONE OF THE SHELL SURFACES CAN-
NOT BE MADE.

User information: THE FIRST THREE SHELL GRIDS ARE %2 %3 %4

7632.1 *** USER FATAL MESSAGE 7632 (ESEAMD)

FOR %5 ELEMENT ID=%1, A CONNECTION TO ONE OF THE SHELL SURFACES CANNOT
BE MADE.

User information: THE FIRST THREE SHELL GRIDS ARE %2 %3 %4

7633.0 *** USER FATAL MESSAGE 7633 (MDG2ED)

Main Index
 884 MSC Nastran Error Messages
Errors 7000 - 7999

FOR %3 ELEMENT ID=%1, WITH FORM=%2, THE TOTAL NUMBER OF GRIDS ON THE
UPPER AND LOWER PATCH EXCEEDS 32.

User information: THIS MAY BE CAUSED BY CONNECTING MIDSIDE NODE SHELL ELE-
MENTS.

7634.0 *** USER FATAL MESSAGE 7634 (MDG2LD)

FOR %2 ELEMENT ID=%1, THE TOTAL NUMBER OF GRIDS ON THE UPPER AND LOWER
PATCHES EXCEEDS %3.

User information: THIS MAY BE CAUSED BY CONNECTING MIDSIDE NODE SHELL ELE-
MENTS.

7635.0 *** USER FATAL MESSAGE 7635 (MDG2ED)

FOR %6 ELEMENT ID=%1, WITH FORM=%2, THE SPOT WELD AREA LIES OUTSIDE THE
DEFINED SHELL SURFACE.

User information: THE NUMBER OF PAIRS OF CONNECTING SHELL ELEMENTS IS %3 BUT 4

PAIRS ARE REQUIRED.
THE SHELL ELEMENT ID WHERE GA IS LOCATED=%4
THE SHELL ELEMENT ID WHERE GB IS LOCATED=%5

7635.1 *** USER FATAL MESSAGE 7635 (MDG2LD)

FOR %8 ELEMENT ID=%1, THE SEAM WELD AREA LIES OUTSIDE THE DEFINED SHELL
SURFACE.

User information: THE NUMBER OF PAIRS OF CONNECTING SHELL ELEMENTS IS %3 BUT 4

PAIRS ARE REQUIRED.
THE SHELL ELEMENT ID WHERE %4 IS LOCATED=%5
THE SHELL ELEMENT ID WHERE %6 IS LOCATED=%7

7636.0 *** USER WARNING MESSAGE 7636 (MDG2ED)

FOR %12 ELEMENT ID=%1, WITH FORM=%13, THE CENTER LOCATION IS MOVED
FROM (%2,%3,%4)
TO (%5,%6,%7)
BY (%8,%9,%10) WITH ABSOLUTE DISTANCE=%11
TO GET A PROJECTION INSIDE THE DEFINED SHELL PATCHES.

Main Index
 MSC Nastran Error Messages 885
Errors 7000 - 7999

7637.0 *** USER FATAL MESSAGE 7637 (MDG2LD)

FOR %2 ELEMENT ID=%1, THE LENGTH OF THE ELEMENT IS ZERO.

7638.0 *** USER FATAL MESSAGE 7638 (MDG2ND)

FOR %2 ELEMENT ID=%1, EITHER THE LENGTH OF THE SEAM SPANS MORE THAN
THREE ELEMENTS OR THE SEAM SPANS A CUTOUT.

7639.1 *** USER FATAL MESSAGE 7639 (RCPRMS)

INVALID PARAM STATEMENT SYNTAX IN CONTROL FILE AT RECORD NUMBER %1.
NAME DOES NOT SPECIFY A VALID CHARACTER CONSTANT.
THE RECORD IS: '%2'

7639.2 *** USER FATAL MESSAGE 7639 (RCPRMS)

INVALID PARAM STATEMENT SYNTAX IN CONTROL FILE AT RECORD NUMBER %1.
NO VALUE FIELD(S) SPECIFIED.
THE RECORD IS: '%2'

7639.3 *** USER FATAL MESSAGE 7639 (RCPRMS)

INVALID PARAM STATEMENT SYNTAX IN CONTROL FILE AT RECORD NUMBER %1.
VALUE(S) NOT CHARACTER CONSTANTS OR NUMBERS.
THE RECORD IS: '%2'

7639.4 *** USER FATAL MESSAGE 7639 (RCPRMS)

INVALID PARAM STATEMENT SYNTAX IN CONTROL FILE AT RECORD NUMBER %1.
ONLY ONE CHARACTER VALUE ALLOWED OR INVALID COMPLEX VALUE, FIRST FIELD
IS CHARACTER.
THE RECORD IS: '%2'

7639.5 *** USER FATAL MESSAGE 7639 (RCPRMS)

INVALID PARAM STATEMENT SYNTAX IN CONTROL FILE AT RECORD NUMBER %1.
INVALID COMPLEX VALUE, SECOND FIELD IS CHARACTER.
THE RECORD IS: '%2'

7640.0 *** SYSTEM FATAL MESSAGE 7640 (KCOLOR2)

Main Index
 886 MSC Nastran Error Messages
Errors 7000 - 7999

Error in collector assignment. Internal ID %1 has collector ID %2, but it is also assigned to tip superele-
ment %3.

User action: Resubmit the job with DOMAINSOLVER ACMS (NUMDOM=%4), or contact MSC cli-
ent support.

7641.0 *** SYSTEM FATAL MESSAGE 7641 (SEQTRE)

Error determining the SEBULK or MDBULK entries to be written for ACMS. Loop variable I = %1, but
collector ID is %2.

User action: Contact MSC client support.

7642.0 *** SYSTEM FATAL MESSAGE 7642 (SEQELM)

Error processing element %1. Gridpoint %2 is on the boundary, but it is also assigned to tip superelement
%3.

User action: Contact MSC client support.

7643.0 *** SYSTEM FATAL MESSAGE 7643 (SEQTRE)

The ACMS method attempted to create two adjacent (same downstream superelement) tip superelements
which contain no elements or grid points.

User action: Resubmit the job with DOMAINSOLVER ACMS (NUMDOM=%1)

7644.0 *** USER INFORMATION MESSAGE 7644

ALL %1 ELEMENTS WILL BE TREATED AS %2 ELEMENTS.

7645.0 *** SYSTEM FATAL MESSAGE 7645 (EQRNED)

MATERIAL NONLINEAR WITH SHFUFL=1 CANNOT HAVE MORE THAN 4 INTEGRATION
POINTS.

User information: CONTACT MSC CLIENT SUPPORT.

Programmer information: SEE SUBROUTINE EQRNES(D).

7646.0 *** USER WARNING MESSAGE 7646

Main Index
 MSC Nastran Error Messages 887
Errors 7000 - 7999

PLANE STRAIN ANALYSIS HAS BEEN REQUESTED WITH MAT2 (OR MAT8) ENTRY ID = %1.

User information: THIS IS NOT ALLOWED AND WILL BE IGNORED.

7647.0 *** SYSTEM FATAL MESSAGE 7647

GT MATRIX FOR ELEMENT ENTRY ID=%1 IS SINGULAR WHEN CONSIDERING THERMAL
MEMBRANE-BENDING COUPLING.

User information: CONTACT MSC CLIENT SUPPORT.

Programmer information: SEE SUBROUTINE %2.

7648.0 *** SYSTEM FATAL MESSAGE 7648

COMPOSITE DATA NOT FOUND.

User information: CONTACT MSC CLIENT SUPPORT.

Programmer information: SEE MODULE SSG1 AND SUBROUTINE %1

7649.0 *** USER WARNING/FATAL MESSAGE 7649

THE %1 FOR %2 ELEMENT ID=%3 IS %4 WHICH EXCEEDS THE MAXIMUM ALLOWED
VALUE OF %5.

7650.0 *** SYSTEM WARNING/FATAL MESSAGE 7650

ELEMENT ID=%1 HAS ILLEGAL MAXIMUM NUMBER OF NODES.

User information: CONTACT MSC CLIENT SUPPORT.

7651.0 *** USER WARNING/FATAL MESSAGE 7651

Main Index
 888 MSC Nastran Error Messages
Errors 7000 - 7999

%1 ELEMENT ID = %2 HAS BAD GEOMETRY.

User information: ERROR CODE IS %3:

1 - UNABLE TO DEFINE THE NORMAL VECTOR TO THE MID-PLANE.
2 - UNABLE TO DEFINE THE ELEMENT COORDINATE SYSTEM.
3 - SINGULAR MATRIX IS ENCOUNTERED IN OFF-PLANE SHEAR REDUCTION.
4 - UNABLE TO DEFINE THE NORMAL VECTOR TO THE BOTTOM FACE.
5 - UNABLE TO DEFINE THE NORMAL VECTORS AT CONNECTED GRID POINTS.
6 - CUBIC CORRECTION MATRIX IS SINGULAR.
7 - THE OUT-OF-PLANE SHEAR FLEXIBILITY MATRIX IS SINGULAR AND SHEAR STIFF-
NESS.
8 - ZERO THICKNESS.
9 - ZERO DIAGONAL LENGTH.

7652.0 *** USER WARNING/FATAL MESSAGE 7652

THE THICKNESS FOR %1 ELEMENT ID = %2 IS NOT DEFINED AT ALL CORNERS.

7653.0 *** USER WARNING/FATAL MESSAGE 7653

%1 ELEMENT ID =%2 THE SHEAR MODULUS IS NOT DEFINED FOR TRANSVERSE SHEAR.

User information: THE SHEAR STIFFNESS WILL BE IGNORED.

7654.0 *** USER WARNING/FATAL MESSAGE 7654

%1 ELEMENT ID=%2 THERE IS SINGULARITY IN BUBBLE FUNCTION PROCESSING.

User information: THE BUBBLE FUNCTION CORRECTION IS SKIPPED.

7655.0 *** USER WARNING/FATAL MESSAGE 7655

%1 ELEMENT ID=%2 THE X-AXIS OF THE %3 COORDINATE SYSTEM HAS NO PROJEC-
TION ON THE ELEMENT XY-PLANE.

User action: USE THE Y-AXIS INSTEAD.

7656.0 *** USER FATAL MESSAGE 7656

%1 BULK DATA ENTRY WITH ROTORID OF %2 AND ROTRSEID OF %3 REFERENCES A
NON-EXISTENT ROTOR.

Main Index
 MSC Nastran Error Messages 889
Errors 7000 - 7999

7657.0 *** USER FATAL MESSAGE 7657

THE PROGRAM COULD NOT DETERMINE THE SPIN DIRECTION FOR ROTOR %1

User action: SPECIFY GRIDS AT LEAST %2 UNITS APART

7658.0 *** USER FATAL MESSAGE 7658

GRID POINT %1 MAY NOT BE REFERENCED BY ROTORS %2 AND %3

7658.1 *** USER FATAL MESSAGE 7658

ROTHYBD ENTRY REFERENCES NON-EXISTENT HYBDAMP ENTRY %1 FOR ROTOR %2

7659.0 *** USER FATAL MESSAGE 7659

GRID ID %1 REFERENCED ON UNBALNC ENTRY %2 IS NOT SPECIFIED ON THE AXIS OF
SYMMETRY OF ANY ROTOR

7659.1 *** USER FATAL MESSAGE 7659

GRID %1 SPECIFIED ON %2 ENTRY WITH ROTORID OF %3 AND ROTRSEID OF %4 IS NOT
AMONG THE POINTS THAT ARE ON THE AXIS OF SYMMETRY OF THE REFERENCED
ROTOR

7660.0
The value SPECIFIED for user PARAMETER ADJMETH is invalid.

User information: THE PROGRAM WILL PROCEED with ADJMETH reset TO 0.

7661.0 *** SYSTEM WARNING MESSAGE 7661

THE MASS ON ROTOR %1 AT GRID %2 DOES NOT PASS THE SYMMETRY TEST

User information: RESULTS MAY BE INACCURATE

7662.0 *** USER FATAL MESSAGE 7662

SYNC OPTION ON THE RGYRO BULK DATA ENTRY WITH ID %1 IS NOT ALLOWED IN
STATIC ANALYSIS

7663.0 *** USER FATAL MESSAGE 7663

Main Index
 890 MSC Nastran Error Messages
Errors 7000 - 7999

THE SYNCFLAG FIELD OF THE RGYRO BULK DATA ENTRY ID %1 IS UNDEFINED

User information: THE SYNCFLAG MUST BE SPECIFIED FOR FREQUENCY RESPONSE AND
COMPLEX EIGENVALUE ANALYSIS.

7664.0 *** USER FATAL MESSAGE 7664 (SDSA)

ATTEMPT TO DESIGN PARTITIONED SUPERELEMENT = %1 IS DETECTED.

User information: DVGRID ENTRY MAY REFERENCE INTERIOR OR BOUNDARY POINTS

THAT BELONG TO THAT SUPERELEMENT.

User action: SPECIFY THE DESIGN MODEL ONLY IN THE MAIN BULK DATA SECTION.

7664.1 *** USER FATAL MESSAGE 7664 (SDSA)

ATTEMPT TO DESIGN PARTITIONED SUPERELEMENT OR MODULE %1 IS DETECTED.

User information: DRESP1 ENTRY MAY REFERENCE INTERIOR GRID POINTS THAT
BELONG TO THE SUPERELEMENT.
NOTE THAT DRESP1 NOT INTENDED AS DESIGN RESPONSE CAN ALSO TRIGGER THIS
MESSAGE.

User action: SPECIFY THE DESIGN MODEL ONLY IN THE MAIN BULK DATA SECTION.

7665.0
INCONSISTENT SUBCASE ID OR STEP ID FOUND BETWEEN THE NONLINEAR DATABASE
MAP AND THE CASE CONTROL STRUCTURE OF THE INPUT FILE OF RESTART RUN.
THE DATABASE IS NOT COMPATIBLE WITH THE RESTART RUN.

User actions:
1. Check the Case Control structure before the restart point in the input file of restart run. It should be
same as the previous run, which created or modified the database.
2. Check if the database was built by the same version of NASTRAN being used in the restart run.

7666.0

Main Index
 MSC Nastran Error Messages 891
Errors 7000 - 7999

THE PROGRAM CANNOT FIND :

(1) USER SPECIFIED RESTART SUBCASE ID (RSSUBC) OR STEP ID (RSSTEP) IN THE DATA-
BASE; OR
(2) MORE LOADCASE FOR RESTART RUN.

User action: Check the format and input values of the NLRESTART Case Control command.

7666.1
NLRESTART Case Control Command is used for Nonlinear Restart Request. The restart step must be
nonlinear analysis. In current analysis, the restart step is linear perturbation step which is not supported.
Please restart from nonlinear step.

User action: Check the format and input values of the NLRESTART Case Control command.

7666.2 ** USER FATAL MESSAGE 7666 (NLRSLP)

Unsupported ANALYSIS=%1 is found in step %2 of subcase %3 for NLRESTART.

User information: ONLY ANALYSIS=NLSTAT AND ANALYSIS=NLTRAN ARE SUPPORTED BY

NLRESTART.

7667.0 *** USER FATAL MESSAGE 7667 (MDG2ND)

FOR %2 ELEMENT ID=%1, THE SEAM SPANS A CORNER.

7668.0 *** USER FATAL MESSAGE 7668

TWO ROTORSE BULK DATA ENTRIES WITH ROTOR IDs %1 AND %2 REFERENCE THE
SAME SUPERELEMENT OR MODULE ID %3.

User information: A SUPERELEMENT OR MODULE CAN BE REFERENCED ON ONLY ONE

ROTORSE ENTRY.

7669.0 *** SYSTEM INFORMATION MESSAGE 7669 (EBARD)

BECAUSE SYSTEM(398)=%1, THE TORSIONAL MASS MOMENT OF INERTIA TERM IS
INCLUDED IN THE MASS MATRIX FORMULATION FOR CBAR ELEMENTS.

7670.0 *** SYSTEM WARNING MESSAGE 7670 (GPDMIG)

Main Index
 892 MSC Nastran Error Messages
Errors 7000 - 7999

SYNCHRONIZING ERROR FOR DMIG MATRIX %1 AT LOCATION COL,ROW,COMP: %2 %3

%4.

7671.0 *** USER FATAL MESSAGE 7671

ROTORSE BULK DATA ENTRY FOR ROTOR ID %1 HAS THE SAME ID AS A ROTORG OR
ROTORAX ENTRY.

User information: ROTOR IDs MUST BE UNIQUE ACROSS ALL ROTORSE, ROTORG AND
ROTORAX ENTRIES.

7671.1 *** USER FATAL MESSAGE 7671

ROTORG BULK DATA ENTRY FOR ROTOR ID %1 HAS THE SAME ID AS A ROTORAX
ENTRY.

User information: ROTOR IDs MUST BE UNIQUE ACROSS ALL ROTORSE, ROTORG AND
ROTORAX ENTRIES.

7671.2 *** USER FATAL MESSAGE 7671

ROTORSE BULK DATA ENTRY FOR ROTOR ID %1 HAS THE SAME ID AS A ROTORAX
ENTRY.

User information: ROTOR IDs MUST BE UNIQUE ACROSS ALL ROTORSE, ROTORG AND
ROTORAX ENTRIES.

7672.0 *** SYSTEM FATAL MESSAGE 7672 (SHGEGD)

ILLEAGAL UNLOADING FLAG %1.

7673.0 *** SYSTEM FATAL MESSAGE 7673 (SHGRVD)

THE ANGLE THETA COMPUTED IS GREATER THAN 30.0 IN SUBROUTINE SHGRVD.

7674.0 *** SYSTEM WARNING MESSAGE 7674 (SHNELD/SHPLTD)

THE TERM AT 3-RD ROW AND COLUMN OF 4X4 G-MATRIX COMPUTED IS ZERO. IT MAY
BE NOT CONSISTENT WITH SIGMAZ. ELEMENT ID = %1.

7675.0 *** USER FATAL MESSAGE 7675 (SHNNSD)

Main Index
 MSC Nastran Error Messages 893
Errors 7000 - 7999

THE TEMPERATURE AT STRESS RECOVERY FIBRE IS NOT CONSISTENT WITH TEMPERA-

TURE PROFILE DEFINED BY TEMPP1 ENTRY.
ELEMENT ID = %1.

7676.0 *** USER WARNING MESSAGE 7676 (SHPLSD)

IN AN INTERNAL LOOP TO COMPUTE DELTA STRAIN IN Z-DIRECTION FOR PLANE
STRESS, IT DOES NOT CONVERGE.
ELEMENT ID = %1.

7677.0 *** USER FATAL MESSAGE 7677 (SHPLTD)

THE COMPUTED SLOPE (ET) OF THE STRESS-STRAIN CURVE >= THE FIRST SLOPE (E)
FOR MID = %1.

7678.0 *** SYSTEM FATAL MESSAGE 7678 (SHPLTD)

WHEN COMPUTING THE YIELD SURFACE SHIFT VECTOR IN SUBROUTINE SHPLTD,
DELTA MU IS LESS THAN ZERO.

7679.0 *** USER WARNING MESSAGE 7679 (SHPLTD)

THE COMPUTED ELASTO-PLASTIC STRESSES DO NOT MATCH THE YIELD SURFACE.
ELID, YIELD STRESS, EFFECTIVE STRESS = %1, %2, %3.
THIS MAY BE DUE TO AN UNREASONABLE STRESS-STRAIN CURVE OR A TOO LARGE
LOAD INCREMENT.

7680.0 *** USER WARNING MESSAGE 7680 (SOPMPD)

IN AN INTERNAL LOOP TO FIND THE EFFECTIVE STRAIN FOR THE K-TH SUB-INCRE-
MENT, IT DOES NOT CONVERGE. ELEMENT ID = %1.
THE LAST AND THE CURRENT DELTA EFFECTIVE PLASTIC STRAIN ARE : %2, %3, THE
CURRENT TOTAL
EFFECTIVE STRAIN = %4.

7681.0 *** USER FATAL MESSAGE 7681 (SOPMPD)

IN PLASTIC ANALYSIS, THE DELTA EFFECTIVE STRAIN ( %1 ) IS NEGATIVE FOR ELEMENT
ID = %2.
THIS MAY BE CAUSED BY UNREASONABLE MATERIAL PROPERTIES.

Main Index
 894 MSC Nastran Error Messages
Errors 7000 - 7999

7682.0 *** USER FATAL MESSAGE 7682 (SOPMPD)

IN PLASTIC ANALYSIS, THE SLOPE ON THE STRESS-STRAIN CURVE IS GREATER THAN
OR EQUAL TO THE YOUNG'S MODULUS FOR MID = %1.

7683.0 *** USER FATAL MESSAGE 7683 (TABKUD)

TABLES1 %1 CONTAINS ILLEGAL DATA SUCH THAT THE DEFAULT VALUE FOR
UNLOADING SLOPE KU CANNOT BE COMPUTED.

7684.0 *** USER FATAL MESSAGE 7684 (TABKUD)

TABLES1 %1 MUST HAVE AT LEAST ONE POSITIVE X VALUE.

7685.0 *** USER FATAL MESSAGE 7685 (NSHTD)

E AND/OR G ARE ZERO FOR ELID = %1. NO MATERIAL NON-LINEAR ANALYSIS CAN BE
PERFORMED.

7686.0 *** USER FATAL MESSAGE 7686 (NSHTD)

IN PLASTIC ANALYSIS, THE SECOND SLOPE (ET) OF THE STRESS-STRAIN CURVE >= THE
FIRST SLOPE (E) FOR MID = %1.

7687.0 *** USER FATAL MESSAGE 7687 (MAT)

THE STRESS-STRAIN CURVE SUPPLIED ON TABLE ID %1 FOR QUADR/TRIAR ELEMENT
HAS AN INFINITE SLOPE AT STRAIN = %2.

7688.0 *** USER FATAL MESSAGE 7688 (NSHTD)

THE UNLOADING SLOPE IS GREATER THAN YOUNG'S MODULUS FOR MID = %1, WHICH
IS ILLEGAL FOR EPCOMB.

7689.0 *** USER FATAL MESSAGE 7689 (NSHTD)

THE MATERIAL PROPERTY ID FOR BENDING IS NOT EQUAL TO THAT FOR MEMBRANE (
ELID = %1 ).
THIS IS NOT ALLOWED IN A MATERIAL NONLINEAR ANALYSIS.

7690.0 *** USER FATAL MESSAGE 7690 (NSHTD)

MATERIAL PROPERTY ID'S FOR BOTH MEMBRANE AND BENDING ARE ZERO (ELID =%1).
THIS IS NOT ALLOWED IN A MATERIAL NONLINEAR ANALYSIS.

7691.0 *** USER FATAL MESSAGE 7691 (NSHTD)

Main Index
 MSC Nastran Error Messages 895
Errors 7000 - 7999

MEMBRANE-BENDING COUPLING IS NOT ALLOWED IN METERIAL NONLINEAR ANALY-

SIS. (ELEMENT ID = %1)

7692.0 *** USER FATAL MESSAGE 7692 (DPR1A1)

%1 ENTRY ID = %2 REFERENCES RANDVAR ENTRY ID = %3 WHICH IS NOT DEFINED.

User action: EITHER MODIFY RANDVAR ENTRY OR ADD A NEW PROPERTY ENTRY.

7693.0 *** USER FATAL MESSAGE 7693 (DPR1A1)

RANDVAR ENTRY IDS = %1 AND %2 REFERENCE SAME COMBINATION OF ANALYSIS
PROPERTY TYPE=%3, NAME=%4 AND PID=%5.

User information: THE REFERENCED PROPERTY INFORMATION ON RANDVAR MUST BE

UNIQUE.

7694.0 *** USER FATAL MESSAGE 7694 (DPR1A1)

THE %1 CASE CONTROL COMMAND REFERENCES UNDEFINED %2 BULK DATA
ENTRY(IES).

User information: EITHER NO %2 ENTRIES ARE PRESENT OR THEIR IDS DO NOT MATCH
THE %1 CASE CONTROL REQUEST.

7695.0 *** USER FATAL MESSAGE 7694 (DPR1A1)

THE %1 CASE CONTROL COMMAND REFERENCES UNDEFINED SET ENTRY %2.

User information: EITHER REFERENCE AN EXISTING SET ENTRY OR DEFINE A NEW SET
ENTRY.

7696.0 *** USER FATAL MESSAGE 7696 (NLRSFD)

THE FILM THICKNESS OF THE SQUEEZE FILM DAMPER, NLRSFD (SID=%1), IS NEGATIVE
AT NPORT=%2 AND NPNT=%3
\
7696.1 *** USER FATAL MESSAGE 7696 (CBUSH2D)

Main Index
 896 MSC Nastran Error Messages
Errors 7000 - 7999

THE FILM THICKNESS OF THE CBUSH2D SQUEEZE FILM DAMPER WITH ID=%1 HAS
TURNED NEGATIVE.
YOU MAY BE SUCCESSFUL BY RE-RUNNING WITH A DIFFERENT STEP SIZE OR OTHER
PARAMETER ON THE TSTEPNL ENTRY.

7696.2 *** USER FATAL MESSAGE 7696 (CBUSH2D)

SQUEEZE OPTION USED IN ELID %1 IS NOT SUPPORTED IN LINEAR SOLUTIONS and
NON-LINEAR FREQUENCY RESPONSE SOLUTION.

User information: SQUEEZE OPTION IS AVAILABLE ONLY FOR NON-LINEAR TRANSIENT

SOLUTION SEQUENCE (SOL400).

7697.0 *** USER WARNING MESSAGE 7697 (GKAM1A)

ONE OR MORE MODAL DAMPING VALUES FOR %1 MODES ARE EITHER NEGATIVE OR
HAVE RESULTED FROM EXTRAPOLATION OF THE TABDMP1 %2 TABLE DATA AS SHOWN
BELOW:

7698.0 *** USER FATAL MESSAGE 7698 (GKAM1A)

ONE OR MORE OF THE EXTRAPOLATED MODAL DAMPING VALUES FOR %1 MODES
SHOWN ABOVE ARE NEGATIVE

User action: IF YOU WANT THIS JOB TO CONTINUE WITHOUT A FATAL ERROR, RE-SUB-
MIT IT BY SPECIFYING MDAMPEXT = 1 OR SYSTEM(426) = 1 ON THE NASTRAN STATE-
MENT

7699.0 *** USER FATAL MESSAGE 7699 (DSGRDM)

A %1 Bulk Data entry is specified in an AESO creation run.

User information: The AESO run does not support the %1 entry.

7701.0 *** USER FATAL MESSAGE 7701 (A?)

COMPONENT ID: %1, REFERENCED BY BULK DATA ENTRY: AECOMPL %2, WAS NOT
FOUND.

Programmer information: COMPONENT %1 DOES NOT APPEAR IN THE %3 TABLE.

7701.1 *** USER FATAL MESSAGE 7701 (A?)

Main Index
 MSC Nastran Error Messages 897
Errors 7000 - 7999

COMPONENT ID: %1, WAS NOT FOUND.

Programmer information: COMPONENT %1 DOES NOT APPEAR IN THE %2 TABLE.

7701.2 *** USER FATAL MESSAGE 7701 (A?)

LIST ID: %1, REFERENCED BY BULK DATA ENTRY: AECOMP %2 %3, WAS NOT FOUND.

Programmer information: %3 %1 DOES NOT APPEAR IN THE %4 TABLE.

7701.3 *** USER FATAL MESSAGE 7701 (A?)

GRID ID: %1, REFERENCED BY %3 ID: %2, WAS NOT FOUND IN THE %4 TABLE.

7701.5 *** USER FATAL MESSAGE 7701 (A?)

%1 BULK DATA ENTRY WITH ID %2 REFERENCED BY CASE CONTROL %3 DOES NOT
EXISTS.

User information: %3 IN CASE CONTROL IS USED TO INDICATE AN AERODYNAMIC EXTRA

POINT VECTOR ABOUT WHICH THE STABILITY DERIVATIVES ARE TO
BE COMPUTED AND PRINTED.

7701.6 *** USER FATAL MESSAGE 7701 (A?)

NO UXVEC BULK DATA ENTRIES WERE FOUND.

User information: UXVEC ENTRIES ARE REQUIRED TO DEFINE AERODYNAMIC CONTROL

POINT (EXTRA POINT) VECTOR VALUES.

7701.7 *** USER WARNING MESSAGE 7701 (A?)

%1 CONTROLLER REFERENCED BY %2 BULK DATA ENTRY WITH ID %3 DOES NOT
EXIST.

User information: AN AESTAT, AESURF OR AEPARM BULK DATA ENTRY DEFINES CON-
TROLLER.

7701.8 *** USER WARNING MESSAGE 7701 (A?)

Main Index
 898 MSC Nastran Error Messages
Errors 7000 - 7999

NONE OF THE CONTROLLERS REFERENCED BY %1 BULK DATA ENTRY WITH ID %2

EXIST.

User information: AN AESTAT, AESURF OR AEPARM BULK DATA ENTRY DEFINES CON-
TROLLER.

7701.9 *** USER FATAL MESSAGE 7701 (A?)

THE %1 ID = %2 REFERENCED BY THE %3 ID = %4 WAS NOT FOUND.

7701.10 *** USER FATAL MESSAGE 7701 (A?)

THE %1 ID = %2 REFERENCED BY THE %3 CASE CONTROL COMMAND WAS NOT
FOUND.

7701.11 *** USER WARNING MESSAGE 7701 (A?)

THE %1 ENTRY WITH NAME = %2 REFERENCED BY THE %3 ENTRY %4 WAS NOT
FOUND.

7701.12 *** USER FATAL MESSAGE 7701 (PKFRQD)

FRQVAR BULK DATA ENTRY ID=%1 WAS NOT FOUND.

7701.13 *** USER FATAL MESSAGE 7701 (A?)

THE LABEL = %1 ON THE FOLLOWING COMBINE DIRECTIVE CANNOT BE FOUND:
%2

7701.14 *** USER WARNING MESSAGE 7701 (A?)

THE %3 = '%1' DOES NOT EXIST FOR THE %2 OPTION ON THE VECMGR MODULE.

7702.0 *** USER FATAL MESSAGE 7702 (A?)

COMPONENT ID: %1, OF MESH TYPE %2, IS NOT UNIQUE ACROSS ALL AECOMP AND
AECOMPL BULK DATA ENTRIES.

7702.1 *** USER FATAL MESSAGE 7702 (A?)

CONTROL SURFACE ID: %1, IS NOT UNIQUE ACROSS ALL AESURFS BULK DATA ENTRIES.

7702.2 *** USER FATAL MESSAGE 7702 (A?)

MONITOR POINT ID: %1, IS NOT UNIQUE ACROSS ALL MONITOR POINT TABLES.

Main Index
 MSC Nastran Error Messages 899
Errors 7000 - 7999

7702.3 *** USER FATAL MESSAGE 7702 (A?)

COMPONENT ID: %1, IS NOT UNIQUE ACROSS ALL AECOMPL BULK DATA ENTRIES.

7702.4 *** USER FATAL MESSAGE 7702 (A?)

SET ID: %1, IS NOT UNIQUE ACROSS ALL SET1 AND SET2 BULK DATA ENTRIES.

7702.5 *** USER FATAL MESSAGE 7702 (A?)

%3 ENTRY: %1, IS NOT UNIQUE ACROSS ALL %3 ENTRIES OF CLASS %2.

7702.6 *** USER FATAL MESSAGE 7702 (A?)

COMPONENT AXIS: %1, IS NOT UNIQUE ACROSS ALL COMPONENT AXES ON THE %2
MONSUM ENTRY: %3.

7702.7 *** USER FATAL MESSAGE 7702 (A?)

THE %2 = '%1' IS NOT UNIQUE IN THE %3 TABLE.

7703.0 *** USER FATAL MESSAGE 7703 (A?)

BULK DATA ENTRY: AECOMPL %2, REFERENCES ITSELF DIRECTLY OR INDIRECTLY
WITH RESPECT TO REFERENCE LEVEL: %1

7703.1 *** USER FATAL MESSAGE 7703 (A?)

%2 MONSUM ENTRY: %3, AXIS: %4 REFERENCES ITSELF DIRECTLY OR INDIRECTLY
WITH RESPECT TO REFERENCE LEVEL: %1

7703.2 *** USER FATAL MESSAGE 7703 (A?)

COMBINE LABEL: '%2',
REFERENCES ITSELF DIRECTLY OR INDIRECTLY WITH RESPECT TO REFERENCE LEVEL:
%1

7704.0 *** USER FATAL MESSAGE 7704 (A?)

BULK DATA ENTRY: AESURFS %1, DOES NOT MATCH BULK DATA ENTRY: AESURF %1, IN
THE NUMBER OF CONTROL SURFACES.

7704.1 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM ENTRY: %2, THE REFERENCED AXIS: %4, FOR ENTRY: %3, IS NOT A SUBSET
OF THE ORIGINAL AXES: %5.

Main Index
 900 MSC Nastran Error Messages
Errors 7000 - 7999

7704.2 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM ENTRY: %2, THE REFERENCED AXIS: %4, FOR ENTRY: %3, IS NOT A SUBSET
OF THE NEW AXES: %5.

User information: USE EXPLICIT ALIGNMENT TO MOVE RESULTS FROM ONE COMPO-
NENT AXIS TO ANOTHER.

7704.3 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM ENTRY: %2, THE ORIGINAL AXES: %4, FOR ENTRY: %3, DO NOT INTER-
SECT WITH THE NEW AXES: %5.

User information: USE EXPLICIT ALIGNMENT TO MOVE RESULTS FROM ONE COMPO-
NENT AXIS TO ANOTHER.

7704.4 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM ENTRY: %2, THE REFERENCED AXES: %4, FOR ENTRY: %3, SPECIFIES MORE
THAN ONE AXIS, WHERE ONLY ONE IS ALLOWED.

User information: SPECIFY A SINGLE AXIS (INTEGER FROM 1-6) FOR EXPLICIT ALIGNMENT.

7704.5 *** USER FATAL MESSAGE 7704 (A?)

GRID ID: %1 DOES NOT MATCH IN THE NUMBER OF DEGREES OF FREEDOM.

Programmer information: THE CONFLICTING VALUES FOR THE NUMBER OF DEGREES OF

FREEDOM ARE %2 AND %3.

7704.6 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM1 ENTRY: %2, THE REFERENCED AXIS: %4, FOR ENTRY: %3, IS NOT EQUAL
THE NEW AXIS: %5.

7704.7 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM1 ENTRY: %2, THE REFERENCED AXIS: %4, FOR ENTRY: %3, IS NOT A SUB-
SET OF THE ORIGINAL AXES: %5.

7704.8 *** USER FATAL MESSAGE 7704 (A?)

Main Index
 MSC Nastran Error Messages 901
Errors 7000 - 7999

%1 MONSUM1 ENTRY: %2, THE REFERENCED AXIS: %4, FOR ENTRY: %3, IS NOT A SUB-
SET OF THE NEW AXES: %5.

User information: USE EXPLICIT ALIGNMENT TO MOVE RESULTS FROM ONE COMPO-
NENT AXIS TO ANOTHER.

7704.9 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM1 ENTRY: %2, THE ORIGINAL AXES: %4, FOR ENTRY: %3, DO NOT INTER-
SECT WITH THE NEW AXES: %5.

User information: USE EXPLICIT ALIGNMENT TO MOVE RESULTS FROM ONE COMPO-
NENT AXIS TO ANOTHER.

7704.10 *** USER FATAL MESSAGE 7704 (A?)

%1 MONSUM1 ENTRY: %2, THE REFERENCED AXES: %4, FOR ENTRY: %3, SPECIFIES
MORE THAN ONE AXIS, WHERE ONLY ONE IS ALLOWED.

User information: SPECIFY A SINGLE AXIS (INTEGER FROM 1-6) FOR EXPLICIT ALIGNMENT.

7705.0 User Warning Message 7705

THE MAXMIN(DEF) COMMAND SPECIFIED CID BUT NO CORDIJ BULK DATA ENTRIES
CAN BE FOUND.

User information: OPERATIONS WILL BE PERFORMED IN THE BASIC COORDINATE SYS-

TEM.

7705.1 User Warning Message 7705

SETID %1 IS INVOKED BY A CASE CONTROL COMMAND, BUT THERE IS NO CORRE-
SPONDING LIST WITH THIS ID.

User information: WITH A MISSING LIST, SDR2 WILL REVERT TO RECOVERITNG ALL THE
DATA OF THE PRESCRIBED TYPE.

7706.0 SYSTEM WARNING MESSAGE 7706

Main Index
 902 MSC Nastran Error Messages
Errors 7000 - 7999

THE SORT2 PATH OF DATA RECOVERY DOES NOT CURRENTLY ALLOW FOR
DEFORMED STRUCTURAL PLOTS.

User action: RESTART THE RUN WITHOUT THE MAXMIN(DEF) AND MAXMIN COM-
MANDS.

7707.0 USER FATAL MESSAGE 7707

Insufficient memory for MAXMIN command, current memory size is %1.

User action: set IVAL in MDLPRM,MXMNMEM,IVAL to %2 or larger to increase memory.

7708.0 SYSTEM FATAL MESSAGE 7708

SDR2RD CALLED WITH ZERO WORDS

7710.0 *** USER WARNING MESSAGE 7710 (MDENGA)

REQUESTED MODE NUMBER %1, BY CASE CONTROL MODALSE/MODALKE = %2, IS NOT
IN THE LIST OF MODES.
THEREFORE, THIS MODE WILL BE IGNORED IN COMPUTING MODAL STRAIN/KINETIC
ENERGY.

7710.1 *** USER WARNING MESSAGE 7710 (MDENG1)

CASE SET %1, SPECIFIED BY %2, IS MISSING. ALL MODES WILL BE USED INSTEAD.

7710.2 *** USER WARNING MESSAGE 7710 (MDENG1)

TIME/FREQ SET %1, SPECIFIED BY %2= %3, IS MISSING. TIME/FREQ=ALL WILL BE USED
INSTEAD.

7711.0 *** USER FATAL MESSAGE 7711 (A?)

%1 ADDITIONAL GRIDS REFERENCED BY %3 ID: %2, WERE ALSO NOT FOUND BUT ARE
NOT LISTED.

7711.1 *** USER WARNING MESSAGE 7711 (A?)

%1 ADDITIONAL GRIDS WITH CONFLICTING VALUES FOR THE NUMBER OF DEGREES
OF FREEDOM WERE ALSO FOUND BUT ARE NOT LISTED.

7712.0 *** USER WARNING MESSAGE 7712 (MDG2EL1)

%1 IS REQUESTED ON MDLPRM Bulk Data ENTRY BUT NO %2 ENTRIES EXIST.

Main Index
 MSC Nastran Error Messages 903
Errors 7000 - 7999

7713.0 *** USER FATAL MESSAGE 7713 (STOCHAS0)

Case Control command STOCHASTICS = %1 references an undefined STOCHSA Bulk Data entry.

7714.0 *** USER INFORMATION MESSAGE 7714 (REPORTL):

THERE ARE NO %1 TO REPORT.

7715.0 *** USER FATAL MESSAGE 7715 (LTOOL)

The following ltool command refers to an existing XDB file, but the APPEND keyword is not specified.
Command: %1
File: %2

7715.1 *** USER FATAL MESSAGE 7715 (LTOOL)

The following ltool command refers to an existing NDB file, but USING BULK is also specified.
Command: %1
File: %2

7716.0 *** USER FATAL MESSAGE 7716 (LTOOL)

The input file specified on the following ltool command cannot be found.
Command: %1
File: %2

7717.0 *** USER FATAL MESSAGE 7717 (LTRES)

The result type "OTHERS" on the following ltool command is invalid.
Command: %1

7718.0 *** SYSTEM FATAL MESSAGE 7718 (LTOOL)

Unable to establish a temporary directory.

User action: This can be corrected by setting the "MSC_SDIR" environment variable to a valid directory
name.

7719.0 *** SYSTEM FATAL MESSAGE 7719 (LTOOL)

Main Index
 904 MSC Nastran Error Messages
Errors 7000 - 7999

Unable to determine the nastran installation path.

User action: Setting the "MSC_BASE" and the "MSC_VERSD" environment variables may correct this
problem.

7720.0 *** USER FATAL MESSAGE 7720 (GPSPMP)

LOGICAL ERROR WAS FOUND IN GRID POINT SINGULARITY PROCESSING.

7720.1 *** SYSTEM FATAL MESSAGE 7720 (GPSPMP)

INCORRECT CALCULATIONS OF SINGULARITIES IN A PLANE FOR GRID POINT %1,
WITH COMPONENTS %2,%3, AND %4, WHILE PROCESSING GRID POINT SINGULARITY.

7720.2 *** USER WARNING MESSAGE 7720 (GPSPMP)

BAD STIFFNESS MATRIX HAS BEEN DETECTED DURING AUTOSPC PROCESSING FOR
GRID POINT %1, WITH COMPONENTS %2,%3, AND %4.

7721.0 *** USER FATAL MESSAGE 7721 (ROTUTL2)

NLHARM BULK DATA ENTRY ID=%1 REFERENCES BOTH AN NLFREQ AND NLFREQ1
ENTRY WITH ID=%2.

User action: REMOVE EITHER NLFREQ OR NLFREQ1 ENTRY OR COMBINE THE FREQUEN-
CIES INTO ONE NLFREQ ENTRY.

7722.0 *** USER FATAL MESSAGE 7722 (ROTUTL2)

NLHARM BULK DATA ENTRY ID=%1 REFERENCES AN UNDEFINED NLFREQ OR NLFREQ1
ENTRY WITH ID=%2.

7723.0 *** USER FATAL MESSAGE 7723 (ROTUTL2)

NLHARM BULK DATA ENTRY ID=%1 REFERENCES AN NLHOUT ENTRY WITH ID=%2
THAT SPECIFIES AN OUTPUT HARMONIC NUMBER THAT IS GREATER THAN %3 SPECI-
FIED BY THE VALUE IN THE NHARM FIELD OF THE NLHARM ENTRY.

User action: REDUCE THE OUTPUT HARMONIC OR INCREASE THE VALUE IN NHARM
FIELD.

7724.0 *** USER FATAL MESSAGE 7723 (ROTUTL2)

Main Index
 MSC Nastran Error Messages 905
Errors 7000 - 7999

NLHARM BULK DATA ENTRY ID=%1 REFERENCES AN UNDEFINED NLHOUT ENTRY

WITH ID=%2.

7724.1 *** USER FATAL MESSAGE 7724 (ROTUTL)

DAMPING BULK DATA ENTRY REFERERNCES AN UNDEFINED HYBDAMP ENTRY WITH
ID=%1.

7725.0 *** SYSTEM WARNING MESSAGE 7725 (PFCHKI)

THE %1 SOLUTION TYPE IS NOT MODAL.

User information: NO %2 PARTICIPATION FACTOR OUTPUT WILL BE GENERATED.

7725.1 *** SYSTEM WARNING MESSAGE 7725 (PFCHKI)

THE STRUCTURAL SOLUTION IS NOT MODAL OR THE FLUID SOLUTION IS NOT AVAIL-
ABLE.

User information: NO %1 PARTICIPATION FACTOR OUTPUT WILL BE GENERATED.

7725.2 *** SYSTEM WARNING MESSAGE 7725 (PFCHKI)

FLUID SOLUTION IS NOT AVAILABLE.

User information: NO %1 PARTICIPATION FACTOR OUTPUT WILL BE GENERATED.

7726.0 *** USER WARNING MESSAGE 7726 (PFGSET)

NO GRID POINTS COULD BE FOUND IN CASE CONTROL SET ID %1.

User information: PARTICIPATION FACTOR OUTPUT WILL NOT BE GENERATED FOR KEY-
WORDS REFERENCING THIS SET.

7726.1 *** USER WARNING MESSAGE 7726 (PFGSET)

NO STRUCTURE GRID POINTS COULD BE FOUND IN CASE CONTROL SET ID %1

User information: PARTICIPATION FACTOR OUTPUT WILL NOT BE GENERATED FOR KEY-
WORDS REFERENCING THIS SET.

7727.0 *** USER WARNING MESSAGE 7727 (PFGSET)

Main Index
 906 MSC Nastran Error Messages
Errors 7000 - 7999

CASE CONTROL SET ID %1 COULD NOT BE FOUND.

User information: PARTICIPATION FACTOR OUTPUT WILL NOT BE GENERATED FOR KEY-
WORDS REFERENCING THIS SET.

7728.0 *** USER WARNING MESSAGE 7728 (PFLCC1)

SOLUTION OUTPUTS IN CASE CONTROL SET %1 DO NOT MATCH ANY OF THE SOLU-
TION LOADINGS SPECIFIED FOR THIS PROBLEM.

User information: PARTICIPATION FACTOR OUTPUT WILL NOT BE GENERATED FOR KEY-
WORDS REFERENCING THIS SET.

7729.0 *** SYSTEM WARNING MESSAGE 7729 (PFCALC)

%1 SOLUTION TYPE (%2) IS NOT VALID

Programmer information: PFCALC MODULE OPERATIONS ARE BEING BYPASSED.

THE VALID SOLUTION TYPES ARE "MODAL" AND "DIRECT".

User information: NO PARTICIPATION FACTOR OUTPUT WILL BE GENERATED.

7730.0 *** SYSTEM WARNING MESSAGE 7730 (PFCLSM)

THE NUMBER OF ROWS IN INPUT MATRIX %1 DOES NOT MATCH THE NUMBER OF
FLUID GRIDS IN THE CASE CONTROL PARTICIPATION FACTOR DATA RECOVERY SET
DEFINITIONS. ROWS = %2, GRIDS = %3

7731.0 *** SYSTEM FATAL MESSAGE 7731 (ZKRAQO)

AN INTERNAL TIME PROBLEM WAS ENCOUNTERED DURING THE KRYLOV SOLUTION
PROCESS.

User action: Resubmit the run and specify "system(391)=0" on the nastran statement or nastran submittal
command.

7732.0 *** USER FATAL MESSAGE 7732 (BDYINF)

Main Index
 MSC Nastran Error Messages 907
Errors 7000 - 7999

THE EXTERNAL SUPERELEMENT ID SPECIFIED ON THE EXTSEOUT or EXTMDOUT CASE

CONTROL COMMAND EXCEEDS 999.

User information: WHEN PARAM,AUTOQSET,YES IS SPECIFIED, THE AUTOMATICALLY

GENERATED Q-SET DOFS HAVE IDS OF THE FORM 9XXXYYYY WHERE XXX = EXTERNAL
SUPERELEMENT AND YYYY = MODE NUMBER. HENCE, XXX MUST NOT EXCEED 999.

7733.0 *** USER FATAL MESSAGE 7733 (VABDRD)

CORE/LAYER ID %1 REFERENCED ON PBRSECT/PBMSECT ENTRY ID=%2 IS NOT
DEFINED.

7734.0 *** USER FATAL MESSAGE 7734 (VABDRD)

T/CORE/LAYER ID %1 TRAVERSE PROFILE IS IN THE OPPOSITE DIRECTION of OUTP/BRP
ON PBRSECT/PBMSECT ENTRY ID=%2.

7734.1 *** USER WARNING MESSAGE 7734 (VABDRD)

T/CORE/LAYER ID %1 WITH (%3, %4) COVERS ALL SEGMENTS of OUTP/BRP ON PBRSECT/
PBMSECT ENTRY ID=%2 AND IT IS NOT THE FIRST T/CORE/LAYER FOR OUTP/BRP. ITS
VALUE WILL REPLACE ALL VALUES SET BY PREVIOUS T/CORE/LAYER FOR THE OUTP/
BRP.

Program action: IF CP, (%3, %4) WILL BE CONSIDERED AS (%4, %3)

User action: IF NECESSARY, MOVE THIS T/CORE/LAYER TO BE THE FIRST FOR A OUTP/BRP

7735.0 *** USER FATAL MESSAGE 7735 (VABP0D)

ZO FOR PCOMP ID %1 IS NOT LOCATED ON THE MID-SURFACE IN-BETWEEN LAYERS
FOR ARBITRARY BEAM APPLICATION.

7735.1 *** USER FATAL/WARNING MESSAGE 7735.1 (IFP6SHM2)

ZO OFFSET ON THE PCOMP BULK DATA ENTRY MAY NOT BE USED WITH LAM OPTION
MEM, BEND, SMEAR OR SMCORE FOR PCOMP PID %1 - ERRONEOUS RESULTS MAY
ACCRUE.

7736.0 *** USER FATAL MESSAGE 7736 (IFP9)

Main Index
 908 MSC Nastran Error Messages
Errors 7000 - 7999

PARAM,ARBMSTYP,VKI IS NOT SUPPORTTED WITH OUTM OR CORE/LAYER ON

PBRSECT/PBMSECT ID = %1.

User action: SWITCH TO VAB VIA PARAM,ARBMSTYP,TIMOSHEN

7737.0 *** USER FATAL MESSAGE 7737 (IFP9)

THERE ARE PBMSECT(WITH CORE/LAYER) AND PBEAM3 BULK DATA ENTRIES WITH
DUPLICATE ID = %1.

7738.0 *** USER FATAL MESSAGE 7738 (IFP9)

CORE/LAYER ON PBRSECT/PBMSECT ID = %1 IS SPECIFIED WITH PARAM,ARBMSTYP,VKI

User information: MUST BE USED WITH PARAM,ARBMSTYP,TIMOSHEN ONLY.

7739.0 *** USER FATAL MESSAGE 7739 (IFP9)

THE BULK DATA SECTION FOR ARBMODEL=%2 AND PBMSECT ID = %1 IS NOT DEFINED.

7740.0 *** USER FATAL MESSAGE 7740,

GRID POINT %1 - COMPONENT %2 OF FRF COMPONENT %3 (%4) SPECIFIED ON %5
BULK DATA ENTRY %6 IS NOT AN EXCITATION DEGREE OF FREEDOM

User information: ONLY EXCITATION DEGREES OF FREEDOM MAY BE SPECIFIED ON FBA-

LOAD/FBADLAY/FBAPHAS BULK DATA ENTRIES

7740.1 *** USER FATAL MESSAGE 7740,

SCALAR POINT %1 OF FRF COMPONENT %2 (%3) SPECIFIED ON %4 BULK DATA ENTRY
%5 IS NOT AN EXCITATION DEGREE OF FREEDOM

User information: ONLY EXCITATION DEGREES OF FREEDOM MAY BE SPECIFIED ON FBA-

LOAD/FBADLAY/FBAPHAS BULK DATA ENTRIES

7741.0 *** USER FATAL MESSAGE 7741 (FRFASM)

Main Index
 MSC Nastran Error Messages 909
Errors 7000 - 7999

NO FRF DATA OR OTHER INFORMATION FOUND FOR FRF COMPONENT %1 (%2)

User action:
CHECK FOR THE FOLLOWING POSSIBLE SCENARIOS:
SCENARIO 1: THE FRF COMPONENT IN QUESTION WAS GENERATED IN A PREVIOUS
EXECUTION
MAKE SURE THAT THE DATABASE OR OP2 FILE GENERATED IN THE PREVIOUS EXECU-
TION IS PROPERLY ASSIGNED
SCENARIO 2: THE FRF COMPONENT IN QUESTION WAS GENERATED IN THE CURRENT
EXECUTION
(VIA THE USE OF THE GENASM AND DB OPTIONS IN THE FRF CASE CONTROL COM-
MAND)
MAKE SURE THAT THE CURRENT EXECUTION IS RUN WITH SCR=NO RATHER THAN
SCR=YES
IF THE ABOVE SCENARIOS DO NOT APPLY, CONTACT MSC CLIENT SUPPORT.

7741.1 *** USER FATAL MESSAGE 7741 (FRFASM)

THE FOLLOWING FRF COMPONENTS SPECIFIED BY THE ICFUSE KEYWORD ARE NOT
AMONG THE FRF COMPONENTS SPECIFIED BY THE ICFGEN KEYWORD IN THE FRF
CASE CONTROL COMMAND --

7741.2 *** USER FATAL MESSAGE 7741 (FRFICFIN)

NO INTER COMPONENT FORCE (ICF) DATA IS AVAILABLE FOR THE FOLLOWING FRF
COMPONENTS SPECIFIED BY THE ICFUSE KEYWORD IN THE FRF CASE CONTROL COM-
MAND --

7741.3 *** USER FATAL MESSAGE 7741 (FRFASM)

THE %1 KEYWORD IN THE FRF CASE CONTROL COMMAND REFERENCES UNDEFINED
FRF COMPONENT %2

7741.4 *** USER FATAL MESSAGE 7741 (IFP1)

SET ID %1 REFERENCED BY THE %2 KEYWORD IN THE ABOVE FRF COMMAND MUST BE
DEFINED PRIOR TO THIS COMMAND

7741.5 *** USER FATAL MESSAGE 7741 (FRFICFIN)

Main Index
 910 MSC Nastran Error Messages
Errors 7000 - 7999

NO INTER COMPONENT FORCE (ICF) DATA IS AVAILABLE FOR FRF COMPONENTS SPEC-
IFIED BY THE ICFUSE KEYWORD IN THE FRF CASE CONTROL COMMAND

User action: Check the FRF component ID(s) referenced by the ICFUSE keyword and also the contents
and assignment of the ICF data base or op2 file.

7742.0 *** USER FATAL MESSAGE 7742 (FRFASM)

THE NUMBER OF FORCING FREQUENCIES IS NOT THE SAME FOR ALL OF THE FRF
COMPONENTS SPECIFIED IN THE FBA PROCESS.

User information: DETAILS ARE GIVEN BELOW.

7743.0 *** USER FATAL MESSAGE 7743 (FRFASM)

THE FORCING FREQUENCIES ARE NOT THE SAME FOR ALL OF THE FRF COMPONENTS
SPECIFIED IN THE FBA PROCESS.

User information: DETAILS ARE GIVEN BELOW.

7744.0 *** USER INFORMATION MESSAGE 7744 (GP1D)

DAREA BULK DATA ENTRIES ARE IGNORED BECAUSE DAREA ENTRIES ARE NOT MEAN-
INGFUL IN AN FBA RUN

7745.0 *** USER INFORMATION MESSAGE 7745 (MDG3LP)

HSUBCASE = %1 AND/OR HSTEP = %2 SPECIFIED IN TEMP(LOAD) = %3 CASE CONTROL
COMMAND DOES NOT EXIST IN THE HEATDB THERMAL DATABASE.

User information: ONLY AN EXISTING SUBCASE/STEP NUMBER IN THE SELECTED THER-

MAL JOB MAY BE SPECIFIED IN TEMP(LOAD) FOR UNCOUPLED THERMAL AND STRUC-
TURAL ANALYSES.

7745.1 *** USER FATAL MESSAGE 7745 (MODGM3)

TEMP(LOAD) CASE CONTROL COMMAND MUST BE SPECIFIED TO COMPUTE THE
THERMAL LOADS OF 3D THERMAL SHELLS.

User information: THE 3D THERMAL SHELLS ARE DEFINED VIA NLMOPTS,TEMPP,LINE OR

NLMOPTS,TEMPP,QUAD ENTRY.

Main Index
 MSC Nastran Error Messages 911
Errors 7000 - 7999

7746.0 *** USER FATAL MESSAGE 7746 (GP4)

THERE ARE QSET/QSET1 BULK DATA ENTRIES THAT REFERENCE GRID POINTS.

User information: WHEN AN EXTSEOUT or EXTMDOUT CASE CONTROL COMMAND IS

PRESENT, QSET/QSET1 ENTRIES MAY REFERENCE ONLY SPOINTS.

7747.0 SYSTEM FATAL MESSAGE 7747 (TA1M)

%1 unrecoverable error(s) encountered due possibly to bad input.

User information: SEE ERROR MESSAGES LISTED ABOVE.

Search backward for the keyword FATAL to locate the messages.

7747.1 *** USER FATAL MESSAGE 7747 (TA1M)

NO PRIMARY MATERIAL EXTRIES EXIST.
YOUR MODEL CONTAINS ONE OR MORE ADVANCED NONLINEAR ELEMENTS AND NO
PRIMARY MATERIAL ENTRY (FOR EXAMPLE,MAT1 MAT2 MAT3 MAT4 MAT5 MAT8 MAT9
MAT10 MATG MATHE MATHP MATORT MAT11 MCOHE MATSMA MATUSR MATDIGI) IS
PRESENT IN THE BULK DATA SECTION FOR THEM.

7748.0 *** USER FATAL MESSAGE 7748 (FRFTS2)

FRF DATA IN UDN 58 OF THE UNIVERSAL FILE HAS ILLEGAL DATA TYPE OF %1.

User information: FRF DATA TYPE MUST BE 5 (COMPLEX SINGLE PRECISION) OR 6 (COM-
PLEX DOUBLE PRECISION).

7748.1 *** USER FATAL MESSAGE 7748 (FRFTS2)

UDN 58 IS DEFINED MORE THAN ONCE FOR RESPONSE AT STRUCTURAL GRID POINT
%1 - COMPONENT %2 DUE TO EXCITATION AT GRID POINT %3 - COMPONENT %4

7748.2 *** USER FATAL MESSAGE 7748 (FRFTS2)

UDN 58 IS DEFINED MORE THAN ONCE FOR RESPONSE AT ACOUSTIC GRID POINT %1
DUE TO EXCITATION AT GRID POINT %2 - COMPONENT %3

7748.3 *** USER FATAL MESSAGE 7748 (FRFTS2)

UDN %1 DOES NOT HAVE ANY COORDINATES DEFINED FOR STRUCTURAL GRID
POINT %2

Main Index
 912 MSC Nastran Error Messages
Errors 7000 - 7999

7748.4 *** USER WARNING MESSAGE 7748 (FRFTS2)

UDN %1 DOES NOT HAVE ANY COORDINATES DEFINED FOR ACOUSTIC GRID POINT
%2 NULL VALUES WILL THEREFORE BE ASSUMED FOR ALL THREE COORDINATES

7748.5 *** USER FATAL MESSAGE 7748 (FRFTS2)

EXPECTED FLAG OF -1 NOT FOUND AFTER READING FRF DATA IN UDN 58 FOR
RESPONSE POINT %1 - COMPONENT DIRECTION %2
(EXCITATION POINT %3 - COMPONENT DIRECTION %4)

7748.6 *** USER FATAL MESSAGE 7748 (FRFTS2)

UNEXPECTED END-OF-FILE ENCOUNTERED WHEN READING FRF DATA IN UDN 58 FOR
RESPONSE POINT %1 - COMPONENT DIRECTION %2
(EXCITATION POINT %3 - COMPONENT DIRECTION %4)

7748.7 *** USER FATAL MESSAGE 7748 (FRFTS2)

UNEXPECTED END-OF-FILE OR ERROR ENCOUNTERED WHEN READING FRF DATA FOR
EVEN SPACED FREQUENCIES IN UDN 58 FOR
RESPONSE POINT %1 - COMPONENT DIRECTION %2
(EXCITATION POINT %3 - COMPONENT DIRECTION %4)

User information: THE FRF VALUES ARE NOT PROPERLY DEFINED

User action: ENSURE THAT THE NUMBER OF FRF DATA VALUES SPECIFIED IS EQUAL TO
THE NUMBER OF FREQUENCIES

7748.8 *** USER FATAL MESSAGE 7748 (FRFTS2)

UNEXPECTED END-OF-FILE OR ERROR ENCOUNTERED WHEN READING FRF DATA FOR
UNEVEN SPACED FREQUENCIES IN UDN 58 FOR
RESPONSE POINT %1 - COMPONENT DIRECTION %2
(EXCITATION POINT %3 - COMPONENT DIRECTION %4)

User information: THE FRF VALUES ARE NOT PROPERLY DEFINED

User action: ENSURE THAT THE NUMBER OF PAIRS OF FRF DATA VALUES SPECIFIED IS
EQUAL TO THE NUMBER OF FREQUENCIES

Main Index
 MSC Nastran Error Messages 913
Errors 7000 - 7999

7750.0 *** SYSTEM FATAL MESSAGE 7750

ERROR CODE= %1 ENCOUNTERED FOR USER-DEFINED ELEMENT NLRSFD ID= %2 WITH
GA=%3 AND GB=%4.

7751.0 *** USER FATAL MESSAGE 7751

THE FOLLOWING POINTS ARE REFERENCED ON BOTH FRFSPC1 AND FRFFLEX BULK
DATA ENTRIES

7751.1 *** USER FATAL MESSAGE 7751

THE FOLLOWING GRID POINT COMPONENTS ARE REFERENCED ON BOTH FRFRELS
AND FRFFLEX BULK DATA ENTRIES

7758.0 *** USER FATAL MESSAGE 7758 (MATMOD)

FOR MATMOD OPTION 35, THE REQUESTED SORTING OPTION %1 IS NOT VALID FOR
THE INPUT %2 MATRIX DATA TYPE.

User information: THE 4TH DMAP PARAMETER SPECIFIES THE SORTING OPTION. IT CAN
BE ONE OF THE FOLLOWING:
P4 = -2 : DESCENDING ABSOLUTE VALUE SORT
P4 = -1 : DESCENDING ALGEBRAIC VALUE SORT (NOT APPLICABLE TO COMPLEX
MATRIX)
P4 = +1 : ASCENDING ALGEBRAIC VALUE SORT (NOT APPLICABLE TO COMPLEX MATRIX)
P4 = +2 : ASCENDING ABSOLUTE VALUE SORT
P4 = 0 : IMPLIES P4=+1 FOR REAL MATRIX AND P4=+2 FOR COMPLEX MATRIX.

User action: SPECIFY A VALID SORTING OPTION FOR THE MATRIX TYPE BEING SUPPLIED.

7759.0 *** USER FATAL MESSAGE 7759 (MATMOD)

ELEMENT(S) IN SET %1 CONNECT(S) TO POINT ID %2 NOT PRESENT IN GRID SET %3.

User action: MAKE SURE THAT THE GRID POINT SET CONTAINS ALL POINTS CON-
NECTED TO ELEMENTS IN THE ELEMENT SET.

Programmer information: MATMOD OPTION 36, SUB-OPTION 1

7760.0 *** USER WARNING MESSAGE 7760 (MATMOD)

Main Index
 914 MSC Nastran Error Messages
Errors 7000 - 7999

GRID SET %1 CONTAINS POINT ID %2 NOT PRESENT IN THE MODEL.

User action: MAKE SURE THAT THE GRID POINT SET CONTAINS ONLY POINTS ACTUALLY
IN THE MODEL.

Programmer information: MATMOD OPTION 36, SUB-OPTION 1

7761.0 *** USER WARNING MESSAGE 7761 (MATMOD)

GRID SET %1 CONTAINS POINT ID %2 NOT CONNECTED TO ANY ELEMENTS IN SET %3.

User action: MAKE SURE THAT THE GRID POINT SET CONTAINS ONLY POINTS CON-
NECTED TO ELEMENTS IN THE ELEMENT SET.

Programmer information: MATMOD OPTION 36, SUB-OPTION 1

7762.0 *** USER WARNING MESSAGE 7762 (MATMOD)

GRID SET ID %1 COULD NOT BE FOUND IN CASE CONTROL. NO SET MERGE IS POSSI-
BLE.

User information: THE GRID SET GENERATED FROM ELEMENT SET %2 IS USED AS THE
MERGED SET.

User action: MAKE SURE THAT ALL REFERENCED SETS ARE DEFINED ABOVE THE SUB-
CASE LEVEL IN CASE CONTROL.

Programmer information: MATMOD OPTION 36, SUB-OPTION 3

7763.0 *** USER FATAL MESSAGE 7763 (MATMOD)

SET ID %1 COULD NOT BE FOUND IN CASE CONTROL.

User information: THE REQUESTED OPERATION CANNOT BE PERFORMED WITHOUT A

DEFINED SET.

User action: MAKE SURE THAT ALL REFERENCED SETS ARE DEFINED ABOVE THE SUB-
CASE LEVEL IN CASE CONTROL.

Programmer information: MATMOD OPTION 36, SUB-OPTION 1, 2 OR 3

Main Index
 MSC Nastran Error Messages 915
Errors 7000 - 7999

7764.0 *** USER FATAL MESSAGE 7764 (FRFASM)

THERE ARE NO CONNECTION POINTS AVAILABLE FOR THE ASSEMBLY OF THE FRF
COMPONENTS BY THE FBA PROCESS

User information: THE FRF GENERATION RUNS SHOULD DEFINE CONNECTION POINTS
FOR THE FRF ASSEMBLY PROPERLY VIA THE CONNPTS KEYWORD
SO AS TO ENABLE THE FBA PROCESS

7764.1 *** USER WARNING MESSAGE 7764 (FRFASM)

THIS FRF-BASED ASSEMBLY PROCESS INVOLVES A SINGLE FRF COMPONENT WITHOUT
ANY CONNECTION DATA

7765.0 *** USER FATAL MESSAGE 7765 (FRFASM)

THE FOLLOWING FRF COMPONENTS ARE DISJOINT AS THEIR CONNECTION POINTS
DO NOT ALLOW FOR CONNECTIONS TO OTHER FRF COMPONENTS

User information: THE USER SHOULD ENSURE THAT THE FBA PROCESS DOES NOT
INVOLVE ANY DISJOINT FRF COMPONENTS.
EVERY FRF COMPONENT IN THE FBA PROCESS MUST BE CONNECTED TO AT LEAST
ONE OTHER FRF COMPONENT.

7766.0 *** USER FATAL MESSAGE 7766 (DPD9)

SET %1 SPECIFIED BY THE CONNPTS KEYWORD IN THE FRF CASE CONTROL
COMMAND DOES NOT INCLUDE ANY POINTS THAT ARE IN THE MODEL

User information: IF THE COMPID KEYWORD IS SPECIFIED IN THE FRF CASE CONTROL
COMMAND, THEN THE SET SPECIFIED BY THE CONNPTS KEYWORD MUST INCLUDE
ONE OR MORE POINTS IN THE MODEL SO AS TO ENABLE CONNECTIONS IN A
SUBSEQUENT FBA PROCESS

7767.0 *** USER FATAL MESSAGE 7767 (FRFASC)

GRID POINT %1 REFERENCED IN %2 ENTRY %3 IS NOT AMONG THE POINTS OF FRF
COMPONENT %4 (%5)

7767.1 *** USER FATAL MESSAGE 7767 (FRFASC)

Main Index
 916 MSC Nastran Error Messages
Errors 7000 - 7999

GRID POINT %1 REFERENCED IN %2 ENTRY %3 IS NOT AMONG THE CONNECTION

POINTS OF FRF COMPONENT %4 (%5)

7767.2 *** USER WARNING MESSAGE 7767 (FRFASM)

%1 DATA SPECIFIED FOR CONNECTION GRID POINT %2 OF FRF COMPONENT %3 (%4)
IS IGNORED AS THIS POINT IS NOT CONNECTED TO ANY OTHER POINT IN THIS FBA
PROCESS

7768.0 *** USER FATAL MESSAGE 7768 (FRFASC)

FRF COMPONENT %1 REFERENCED IN %2 ENTRY %3 IS NOT AMONG THE
FRF COMPONENTS DEFINED IN THE FBA PROCESS

7768.1 *** USER WARNING MESSAGE 7768 (FRFASC/FRFLOD)

FRF COMPONENT %1 REFERENCED IN %2 ENTRY %3 IS NOT AMONG THE
FRF COMPONENTS DEFINED IN THE FBA PROCESS.
HENCE THIS ENTRY IS IGNORED.

7768.2 *** USER WARNING MESSAGE 7768 (FRFASC)

NEITHER OF THE TWO FRF COMPONENTS REFERENCED IN %1 ENTRY %2 EXISTS.
HENCE THIS ENTRY IS IGNORED.

7769.0 *** USER FATAL MESSAGE 7769 (FRFASC)

%1 ENTRY %2 REFERENCES NON-COINCIDENT CONNECTION GRID POINTS

7770.0 *** USER INFORMATION MESSAGE 7770 (FRFASC)

THE FOLLOWING COINCIDENT CONNECTION GRID POINTS ARE DETECTED IN THE
FBA PROCESS

7771.0 *** USER FATAL MESSAGE 7771 (FRFASC)

ONE OR MORE COINCIDENT CONNECTION GRID POINTS (IDENTIFIED BY ******) ARE
NOT REFERENCED ON FRFCONN ENTRIES OR ON FRFRELS ENTRIES WITH ALL 6 DOFS.

User information: DETAILS ARE GIVEN BELOW.

7772.0 *** USER FATAL MESSAGE 7772 (FRFASC)

Main Index
 MSC Nastran Error Messages 917
Errors 7000 - 7999

FRFRELS ENTRY %1 REFERENCES SCALAR POINT %2

User information: FRFRELS ENTRY MAY REFERENCE ONLY GRID POINTS, NOT SCALAR
POINTS

7773.0 *** USER FATAL MESSAGE 7773 (FRFASC)

GRID POINT %1 OF FRF COMPONENT %2 (%3) AND GRID POINT %4 OF FRF COMPO-
NENT %5 (%6) REFERENCED ON %7 ENTRY %8 ARE COINCIDENT BUT CANNOT BE
CONNECTED BECAUSE THEY HAVE DIFFERENT DISPLACEMENT COORDINATE SYS-
TEMS

7773.1 *** USER FATAL MESSAGE 7773 (FRFASM)

GRID POINT %1 OF FRF COMPONENT %2 (%3) AND GRID POINT %4 OF FRF COMPO-
NENT %5 (%6) ARE COINCIDENT BUT CANNOT BE CONNECTED BECAUSE THEY HAVE
DIFFERENT DISPLACEMENT COORDINATE SYSTEMS

7774.0 *** USER FATAL MESSAGE 7774 (FRFASM)

FRFFLEX ENTRY %1 SPECIFIES FLEXIBLE DATA FOR A DEGREE-OF-FREEDOM THAT IS
NOT CONNECTED AS INDICATED IN THIS ENTRY

User action: CHECK THE CONNECTION DATA TO ENSURE THAT THE FRFFLEX ENTRY
REFERS TO A VALID CONNECTION

7775.0 *** USER FATAL MESSAGE 7775 (LTOOL)

Argument list is too long (maximun length is %1 characters).

7776.0 *** USER FATAL MESSAGE 7776 (LTOOL)

Invalid character found on line: %1

7777.0 *** USER FATAL MESSAGE 7777 (LTOOL)

A syntax error was encountered while processing the ltool command.
Command: %1

7778.0 *** USER FATAL MESSAGE 7778 (LTOOL)

Main Index
 918 MSC Nastran Error Messages
Errors 7000 - 7999

The following is not a valid ltool command: %1

User information: Valid ltool commands are: %2

7779.0 *** USER FATAL MESSAGE 7779 (LTOOL)

The following extra characters are not recognized as part of the ltool command: %1
Command: %2

7795.0 *** SYSTEM FATAL MESSAGE 7795 (SEQFLU)

AUTOMATIC MODEL PARTITIONER WAS UNABLE TO PARTITION THE MODEL.

User action:
1. SELECT A DIFFERENT NUMBER OF PROCESSORS OR RUN THE JOB SERIALLY,
OR
2. IF DOMAINSOLVER MODES (PARTOPT=GRID) WAS SELECTED, THEN SWITCH TO
- DOMAINSOLVER MODES (PARTOPT=DOF),
- DOMAINSOLVER ACMS, OR
- DOMAINSOLVER MODES (PARTOPT=FREQ).

7795.1 *** SYSTEM WARNING MESSAGE 7795 (PREDRV)

AUTOMATIC MODEL PARTITIONER WAS UNABLE TO PARTITION THE MODEL.

User action:
1. SELECT A DIFFERENT NUMBER OF PROCESSORS OR RUN THE JOB SERIALLY,
OR
2. IF DOMAINSOLVER MODES (PARTOPT=DOF) WAS SELECTED, THEN SWITCH TO
- DOMAINSOLVER MODES (PARTOPT=GRID),
- DOMAINSOLVER ACMS, OR
- DOMAINSOLVER MODES (PARTOPT=FREQ).
OR
3. INCREASE MEM IF USER INFORMATION MESSAGE 3008 APPEARS ABOVE.

7795.2 *** SYSTEM WARNING MESSAGE 7795 (PREOUT)

Main Index
 MSC Nastran Error Messages 919
Errors 7000 - 7999

AUTOMATIC MODEL PARTITIONER WAS UNABLE TO PARTITION THE MODEL COR-

RECTLY. DOMAIN %1 DOES NOT HAVE ANY EXTERNAL DEGREES OF FREEDOM
ASSIGNED TO IT, A CASE WHICH CANNOT BE HANDLED BY 'DOMAINSOLVER MODES
(PARTOPT=DOF)' OR 'DOMAINSOLVER STAT (PARTOPT=DOF)'.

User action:
1. SELECT A DIFFERENT NUMBER OF PROCESSORS OR RUN THE JOB SERIALLY,
OR
2. IF DOMAINSOLVER MODES (PARTOPT=DOF) WAS SELECTED, THEN SWITCH TO
- DOMAINSOLVER MODES (PARTOPT=GRID),
- DOMAINSOLVER ACMS, OR
- DOMAINSOLVER MODES (PARTOPT=FREQ).

7795.3 *** USER FATAL MESSAGE 7795 (SEQP)

AUTOMATIC MODEL PARTITIONER WAS UNABLE TO PARTITION THE MODEL.

User information: THIS MODEL IS TOO SMALL TO BE SUBDIVIDED INTO DOMAINS. ACMS
CANNOT BE USED.

User action: PLEASE RERUN THE JOB WITHOUT DOMAINSOLVER ACMS.

7795.4 *** SYSTEM INFORMATION MESSAGE 7795 (DDMDRV)

'EXTREME' WAS UNABLE TO PARTITION THE MODEL BECAUSE THE 'NEGATIVE
DOMAIN' ERROR OCCURRED DURING THE REORDERING PHASE OF THE AUTOMATIC
MODEL PARTITIONER.

User information: THE PROGRAM SWITCHED TO THE 'MSCMLV' AUTOMATIC MODEL

PARTITIONER.

7795.5 *** USER FATAL MESSAGE 7795 (SEQP)

AUTOMATIC MODEL PARTITIONER WAS UNABLE TO PARTITION THE MODEL.

User information: THIS MODEL IS TOO SMALL TO BE SUBDIVIDED INTO DOMAINS, IT HAS
ONLY %1 GRID POINTS.

User action: PLEASE RERUN THE JOB WITHOUT USING DOMAIN DECOMPOSITION.

Main Index
 920 MSC Nastran Error Messages
Errors 7000 - 7999

7796.0 *** SYSTEM FATAL MESSAGE 7796 (DFMAM)

THE MAXIMUM INTEGER VALUE IS ABOUT TO BE EXCEEDED.

User action: USE A DIFFERENT RE-ORDERING SCHEME VIA SYSTEM(206), OR REDUCE THE
SIZE OF YOUR MODEL.

7796.1 *** SYSTEM FATAL MESSAGE 7796 (DFMSA)

THE MAXIMUM INTEGER VALUE IS EXCEEDED.

User information: THE MAXIMUM INTEGER NUMBER ALLOWED ON YOUR MACHINE IS

%1. HOWEVER, THE NUMBER OF REAL STACK ELEMENTS WAS COMPUTED TO BE %2.

User action: USE A DIFFERENT RE-ORDERING SCHEME VIA SYSTEM(206), OR REDUCE THE
SIZE OF YOUR MODEL.

7796.2 *** SYSTEM FATAL MESSAGE 7796 (I8OFFST)

User information: THE MAXIMUM INTEGER VALUE IS ABOUT TO BE EXCEEDED.
INPUT INTEGER = %1, COMPUTED INTEGER = %2, LOCATION = %3.

User action: USE A DIFFERENT RE-ORDERING SCHEME VIA SYSTEM(206), OR REDUCE THE
SIZE OF YOUR MODEL.

7797.0 *** USER INFORMATION MESSAGE 7797 (TRLGCD/S)

THIS TRANSIENT RESPONSE ANALYSIS RESTART RUN IS A CONTINUATION FROM A PRE-
VIOUS RUN, WITH THE INTEGRATION STARTING FROM %1 SECONDS

7798.0 *** USER FATAL MESSAGE 7798 (SEQFLC)

The AUTOMATIC MODEL PARTITIONER has DETECTED CONNECTIONS BETWEEN the
FLUID AND STRUCTURE.

User information: ELEMENTS AND/OR GRIDS making THE CONNECTIONS ARE PRINTED
BELOW.

7799.0 *** SYSTEM FATAL MESSAGE 7799 (SEQER1)

Main Index
 MSC Nastran Error Messages 921
Errors 7000 - 7999

NO ELEMENTS OR GRIDS were found which CONNECT the FLUID AND STRUCTURE.

Programmer information: THE CONNECTIONS FOUND BY SUBROUTINE SEQFLC (SEE

ABOVE) MUST HAVE BEEN INTRODUCED BY THE RIGID ELEMENT PROCESSING OF THE
AUTOMATIC PARTITIONER.

User information: CONTACT MSC CLIENT SUPPORT.

7801.0 *** SYSTEM INFORMATION MESSAGE 7801 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT SUCCESSFULLY CREATED A MODAL NEUTRAL FILE
FOR SUPERELEMENT OR MODULE ID %1.

7802.0 *** SYSTEM WARNING MESSAGE 7802 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE OPERATIONS HAVE BEEN ABORTED
FOR SUPERELEMENT OR MODULE ID %1.
SEE MESSAGES GENERATED ABOVE THIS ONE THAT CONTAIN THE WORDS FAILED
AND/OR ABORTED.

7803.0 *** SYSTEM WARNING MESSAGE 7803 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE INPUT DATA BLOCK NUMBER %1 ROW/
COL SIZES %2 AND %3 DO NOT AGREE WITH PROBLEM SIZE OF %4. MNF GENERATION
ABORTED.

User information: The row/column size of the matrix in the specified input position to the ADAMSMNF
module does not agree with the problem size specified by the input modeshape matrix. For example, the
input a-set stiffness matrix must be square and the number of columns must match the number of columns
of the modeshape matrix.

7804.0 *** SYSTEM WARNING MESSAGE 7804 (AFERRM)

Main Index
 922 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMS/FLEX MNF GENERATION MODULE INPUT GRID POINT %1 DATA BLOCK IS
NOT OFP-TYPE.
NUMBER OF WORDS IN THE ID RECORD = %2. %3

User information:
For grid point stress/strain input:
The grid point stress/strain input data block must contain an Output File Processor (OFP) type table. It
must contain the grid point modal stress/strain values. This type of data block has pairs of ID and data
records. Each ID record must contain 146 words of information. The ID record for the input data block
did not have a 146 word length.
For Grid Point Weight Generator input:
The Grid Point Weight Generator output data block will be used to extract certain mass invariants if it
exists. The data block input to the ADAMSMNF module for this purpose is not the correct table. Mass
invariants will be computed from other input data.

7804.1 *** SYSTEM WARNING MESSAGE 7804 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE INPUT GRID POINT %1 DATA BLOCK
OFP TABLE CONTAINS AN UNSUPPORTED DMAP APPROACH CODE = %2. MNF GENERA-
TION ABORTED.

User information: The grid point stress/strain input data block must contain an Output File Processor
(OFP) type table. It must contain the grid point modal stress/strain values generated in a real eigenvalue
analysis. This type of data block has pairs of ID and data records. Each Id record must contain 146 words of
information that describes the content of the data record.
The ID record for the input data block indicates that the results are not from a real eigenvalue analysis.

User action: Run the problem in a supported solution sequence (SOL 103, 111 or 112) that performs real
eigenvalue analysis.

7804.2 *** SYSTEM WARNING MESSAGE 7804 (AFERRM)

Main Index
 MSC Nastran Error Messages 923
Errors 7000 - 7999

THE ADAMS/FLEX MNF GENERATION MODULE INPUT GRID POINT %1 DATA BLOCK
OFP TABLE CODE IS NOT RECOGNIZED.
OFP TABLE CODE IS %2. %3

User information:
For grid point stress/strain input:
The grid point stress/strain input data block must contain an Output File Processor (OFP) type table. It
must contain the grid point modal stress/strain values generated in a real eigenvalue analysis. This type of
data block has pairs of ID and data records. Each Id record must contain 146 words of information that
describes the content of the data record. The ID record for the input data block indicates that the content is
not grid point stress/strain data.
For Grid Point Weight Generator input:
The Grid Point Weight Generator output data block will be used to extract certain mass invariants if it
exists. The data block input to the ADAMSMNF module for this purpose is not the correct table. Mass
invariants will be computed from other input data.

7805.0 *** SYSTEM WARNING MESSAGE 7805 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE'S ATTEMPT TO LOCATE ADAMS/FLEX
MNF FILE NAME IN NASTRAN INTERNAL TABLES WAS UNSUCCESSFUL. THE FILE NAME
WILL BE CONSTRUCTED FROM THE FILE NAME FOR THE .F06 OUTPUT FILE. THE MNF
WILL HAVE THE .%1 EXTENSION.

7805.1 *** SYSTEM WARNING MESSAGE 7805 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE ATTEMPT TO LOCATE THE NASTRAN
.F06 FILE NAME IN NASTRAN INTERNAL TABLES WAS UNSUCCESSFUL. MNF GENERA-
TION ABORTED.

7806.0 *** USER WARNING MESSAGE 7806 (AFERRM)

Main Index
 924 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMSMNF CASE CONTROL COMMAND HAS SPECIFIED A PLOT SET ID (PSETID =
%1) TO SELECT ELEMENTS AND GRIDS FOR OUTPUT PURPOSES AND ALSO SPECIFIED
THAT NO MASS INVARIANTS BE OUTPUT. THIS COMBINATION CANNOT BE HONORED.
PLOT SETS ARE IGNORED.

User information: A PSETID has selected a plot set that will be used to reduce the size of the model stored
to the MNF. This feature can only be used if mass invariants are also generated and stored. Since no mass
invariant output was requested, usage of a plot set is not possible and is being ignored. Data for all elements
and grids present in the superelement or module will be output.

User action: If a plot set is desired, use the ADAMSMNF Case Control Command MINVAR describer to
select an option other than NONE.

7806.1 *** USER WARNING MESSAGE 7806 (AFERRM)

THE ADAMSMNF CASE CONTROL COMMAND HAS SPECIFIED A PLOT SET ID (PSETID =
%1) TO SELECT ELEMENTS AND GRIDS FOR OUTPUT PURPOSES BUT THE CASE CON-
TROL SET REFERENCES PLOT SET ID %2 THAT COULD NOT BE FOUND IN THE OUT-
PUT(PLOT) PACKET SETS.
THE MISSING SET ID IS BEING IGNORED.

User information: The ADAMSMNF Case Control Command has specified a plot set, but the plot set
could not be located in the PLOT sets. It was located in the case control set ID list however. This Case
Control SET list was used to examine the PLOT sets for set IDs listed in the Case Control SET Command.
The specified set could not be located and is being ignored.

User action: If PSETID was to select a set from the OUTPUT(PLOT) SETs, then ensure that an OUT-
PUT(PLOT) packet exists in the Case Control section and that the requested SET is defined. If the
PSETID is being used to select a Case Control set that references SETs in the OUTPUT(PLOT) section,
then ensure that all of the SET IDs specified in the Case Control set list are present and defined in the
OUTPUT(PLOT) section and that the Case Control contains a definition for the specified set.

7806.2 *** USER WARNING MESSAGE 7806 (AFGMNF)

Main Index
 MSC Nastran Error Messages 925
Errors 7000 - 7999

THE ADAMSMNF CASE CONTROL COMMAND HAS SPECIFIED A PLOT SET ID (PSETID =
%1) TO SELECT ELEMENTS AND GRIDS FOR OUTPUT PURPOSES BUT NEITHER THE
PLOT SET DATA INPUT FOR THE (SUPERELEMENT OR MODULE) NOR THE CASE CON-
TROL CONTAINS ANY REFERENCE TO THIS PLOT SET. ALL GRID POINTS AND ELE-
MENTS WILL BE STORED TO THE MNF.

User information: The ADAMSMNF Case Control Command has specified a plot set, but the plot set ID
could not be located in either the OUTPUT(PLOT) section or the Case Control section.

User action: If PSETID was to select a set from the OUTPUT(PLOT) SETs, then ensure that an OUT-
PUT(PLOT) packet exists in the case control section and that the requested SET is defined. If the PSETID
is being used to select a Case Control SET that references SETs in the OUTPUT(PLOT) section, then
ensure that all of the SET IDs specified in the Case Control SET list are present and defined in the OUT-
PUT(PLOT) section and that the Case Control contains a definition for the specified set.

7806.3 *** USER WARNING MESSAGE 7806 (AFGMNF)

THE ADAMSMNF CASE CONTROL COMMAND HAS SPECIFIED A PLOT SET ID (PSETID =
%1) TO SELECT ELEMENTS AND GRIDS FOR OUTPUT PURPOSES BUT THERE IS NO PLOT
SET DATA INPUT FOR THE SUPERELEMENT OR MODULE. ALL GRID POINTS AND ELE-
MENTS WILL BE STORED TO THE MNF.

User information: The ADAMSMNF Case Control Command specified the ID of a plot set that was to be
used to select grid points and elements for output to the MNF. The required input data blocks generated
for PLOT operations are not available.
All elements and grid points present in the superelement or module will be stored to the MNF.

User action: Ensure that an OUTPUT(PLOT) packet exists in the Case Control section and that the
requested SET is defined.

7806.4 *** USER WARNING MESSAGE 7806 (AFGMNF)

Main Index
 926 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMSMNF CASE CONTROL COMMAND HAS SPECIFIED A PLOT SET ID (PSETID =
%1) TO SELECT ELEMENTS AND GRIDS FOR OUTPUT PURPOSES BUT THERE IS NO ELE-
MENT DATA INPUT FOR THE SUPERELEMENT OR MODULE. NO ELEMENT FACE DATA
WILL BE OUTPUT.

User information: The ADAMSMNF Case Control Command has specified a PSETID Case Control SET
that is to be used to select element geometry to be loaded to the modal neutral file. However, the element
connection data block input to the ADAMS/FLEX MNF generation module contains no information. No
element face geometry data will be stored to the MNF.

User action: Ensure that there are elements in the model and that at least one of them is assigned to the
superelement or module.

Programmer information: The GEOM2 input data block position contains an empty or purged data
block.

7807.0 *** USER WARNING MESSAGE 7807 (AFERRM)

THE ADAMSMNF CASE CONTROL COMMAND HAS REQUESTED LOADING OF MODAL
GRID POINT %1 RESULTS THAT HAVE NOT BEEN GENERATED. THE REQUEST IS
IGNORED.

User action: Ensure that Case Control requests for grid point stress/strain are present if output is desired.
The grid point requests are placed in the OUTPUT(POST) section using SURFACE and VOLUME
entries. There must also be standard STRESS and/or STRAIN Case Control output requests present.

7750.1 *** USER FATAL MESSAGE 7750 (NLHRM1D / NL3NON)

NLRSFD CONNECT SERVICE NAME DOES NOT MATCH THE USER_DEFINED SUBROU-
TINE SERVICE CALL NAME.

User action: CHECK NLRSFD BULK DATA CARD & CONNECT SERVICE DEFINITION AT
TOP OF MAIN FILE

User information: FOR NLRSFD CONNECT SERVICE NAME, USE 'SCA.MDSolver.Obj.Uds.Ele-

ments.Nlrsfd' SERVICE DEFINITION

7750.2 *** USER FATAL MESSAGE 7750 (NLHRM1D / NL3NON)

NLRSFDA CONNECT SERVICE NAME DOES NOT MATCH THE USER_DEFINED SUBROU-
TINE SERVICE CALL NAME.

Main Index
 MSC Nastran Error Messages 927
Errors 7000 - 7999

User action: CHECK NLRSFD BULK DATA CARD & CONNECT SERVICE DEFINITION AT
TOP OF MAIN FILE

User information: FOR NLRSFDA CONNECT SERVICE NAME, USE 'SCA.MDSolver.Obj.Uds.Ele-

ments.Nlrsfda' SERVICE DEFINITION

7808.0 *** USER WARNING MESSAGE 7808 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE HAS DETECTED A CONFLICT IN
ADAMS/FLEX TOOLKIT *MDI_WRITEMNF_OPTIONS* ENVIRONMENT VARIABLE
OPTIONS. OPTION (%1) IS IN CONFLICT WITH THE NASTRAN ADAMSMNF CASE CON-
TROL COMMAND OPTION (MINVAR = %2) USED TO SPECIFY THE AMOUNT OF MASS
INVARIANT OUTPUT PROCESSING.

User information: The environment variable contains a mass invariant option that is in conflict with
options specified using the ADAMSMNF Case Control Command.

User action: Review the ADAMSMNF Case Control Command and ensure that the option specified for
the MINVAR describer does not conflict with the one specified for the MDI_MNFWRITE_OPTIONS
environment variable. For example, MINVAR=FULL is in conflict with option "fast_invar".

7808.1 *** USER WARNING MESSAGE 7808 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE HAS DETECTED A CONFLICT IN
ADAMS/FLEX TOOLKIT *MDI_WRITEMNF_OPTIONS* ENVIRONMENT VARIABLE
OPTIONS. THE %1 OPTION CONFLICTS WITH PREVIOUSLY SPECIFIED %2 OPTION.

User information: The environment MDI_MNFWRITE_OPTIONS variable contains a mass invariant

option that is in conflict with a previously encountered environment variable option.

User action: Review the specification for the MDI_MNFWRITE_OPTIONS environment variable to
resolve conflicts. For example, option "fast_invar" is in conflict with option "full_invar".

7809.0 *** USER WARNING MESSAGE 7809 (AFERRM)

Main Index
 928 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMS/FLEX MNF GENERATION MODULE HAS DETECTED SURFACE GRID POINT
%1 RESULTS THAT CONTAIN A REFERENCE TO COORDINATE SYSTEM ID %2 THAT IS
NOT BASIC. RESULTS MAY BE INCONSISTENT. (THESE RESULTS ARE STORED TO THE
MNF.)
%3

User information: Grid point stress/strain data should be recovered in the basic coordinate system in order
to ensure consistency. A non-basic coordinate system has been encountered. Stress/strain data will be stored
for the non-basic system.

User action: Review SURFACE entries in the OUTPUT(POST) Case Control section to ensure output in
the basic coordinate system.

7809.1 *** USER WARNING MESSAGE 7809 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE HAS DETECTED VOLUME GRID POINT
%1 RESULTS THAT CONTAIN A REFERENCE TO NON-BASIC COORDINATE SYSTEM
THAT MAY PROVIDE INCONSISTENT RESULTS. (THESE RESULTS ARE STORED TO THE
MNF.)
%2

User information: Grid point stress/strain data should be recovered in the basic coordinate system in order
to ensure consistency. A non-basic coordinate system has been encountered. Stress/strain data will be stored
for the non-basic system.

User action: Review VOLUME entries in the OUTPUT(POST) Case Control section to ensure output in
basic system.

7809.2 *** USER WARNING MESSAGE 7809 (AFERRM)

Main Index
 MSC Nastran Error Messages 929
Errors 7000 - 7999

THE ADAMS/FLEX MNF GENERATION MODULE HAS DETECTED SURFACE GRID POINT
%1 RESULTS THAT CONTAIN A REFERENCE TO ELEMENT OUTPUT COORDINATE SYS-
TEM ID %2 THAT MAY PRODUCE INCONSISTENT RESULTS. (THESE RESULTS ARE
STORED TO THE MNF.)
%3

User information: Grid point stress/strain data should be recovered in the basic coordinate system in order
to ensure consistency. A possibly non-basic coordinate system has been encountered. Stress/strain data will
be stored for this system.

User action: Review SURFACE entries in the OUTPUT(POST) Case Control section to ensure output in
the basic coordinate system.

7809.3 *** USER WARNING MESSAGE 7809 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE HAS DETECTED SURFACE GRID POINT
%1 RESULTS AT MULTIPLE FIBRE LOCATIONS.
RESULTS AT FIBRE %2 ARE BEING IGNORED.
%3

User information: Grid point stress/strain data for one surface location only may be transferred to the
modal neutral file. Data has been previously encountered at a different fibre location. Data for this location
is being ignored.

User action: Review SURFACE entries in the OUTPUT(POST) Case Control section to ensure output at
only one fibre location.

7809.4 *** USER WARNING MESSAGE 7809 (AFERRM)

THE ADAMS/FLEX MNF GENERATION MODULE HAS BEEN DIRECTED TO OUTPUT
NULL CMS VECTORS TO THE MNF.
THERE WILL BE NO MNF OUTPUT FOR A NULL CMS VECTOR CORRESPONDING TO A
NULL MASS MATRIX COLUMN AT MODE NUMBER %1.

User information: CMS Vector output must be associated with non-null masses in order to ensure consis-
tency.

7810.0 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

Main Index
 930 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO CRE-

ATE A MNF FOR %1 GRIDS AND %2 MODES.
MNF GENERATION ABORTED.

User information: The ADAMS/FLEX toolkit is unable to create the modal neutral file for the specified
problem size. The specific reason should by displayed above this message. Possible causes are:
1. insufficient dynamic memory available.
2. insufficient disk space for storage of the MNF.

Programmer information: The ADAMS/FLEX toolkit MNF_CREATE function encountered an error.

MNF generation is not possible.

7810.1 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO WRITE
THE MODAL NEUTRAL FILE FOR SUPERELEMENT OR MODULE ID %1. MNF GENERA-
TION ABORTED.

Programmer information: An error has occurred in the ADAMS/FLEX toolkit MNF_WRITE_MNF

function attempting to write the modal neutral file for the superelement or module. MNF generation is not
possible.

7810.2 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO TER-
MINATE THE MODAL NEUTRAL FILE CREATION PROCESS FOR SUPERELEMENT OR
MODULE ID %1. MNF GENERATION ABORTED.

User information: The ADAMS/FLEX toolkit has encountered an error while attempting to terminate the
modal neutral file creation process for the superelement or module. The MNF may have been generated,
but the module is unable to continue.

Programmer information: The ADAMS/FLEX toolkit MNF_TERMINATE function has encountered an

error. The MNF may be usable.

7810.3 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

Main Index
 MSC Nastran Error Messages 931
Errors 7000 - 7999

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD

COMPONENT MODAL DISPLACEMENT RESULTS AT GRID ID %1 FOR MODE NUMBER
%2. MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_MODESHAPE type functions

encountered an error. MNF generation is not possible.

7810.4 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD
ELEMENT ID %1 (TYPE = %2) DISPLAY CONNECTION FACE DATA. MNF GENERATION
ABORTED.

User information: The ADAMS/FLEX toolkit encountered an error trying to load the MNF with face
entry information for use in displaying the specified element. MNF generation is not possible.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_FACEi functions encountered an

error. MNF generation is not possible.

7810.5 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD
MODAL %1 MATRIX DATA.
MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_GENERALIZED_MASS or _STIFF-

NESS function has encountered an error.
MNF generation is not possible.

7810.6 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD
MODAL GRID POINT %1 DATA FOR GRID ID %2
FOR MODE NUMBER %3. MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_MODAL_STRESS_VEC or

MNF_SET_MODAL_STRAIN_VEC function encountered an error.
MNF generation is not possible.

7810.7 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

Main Index
 932 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD

MODAL LOADS DATA FOR MODE NUMBER %1
FOR CASE %2. MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_MODAL_LOAD function encoun-

tered an error. MNF generation is not possible.

7810.8 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD
NODAL %1 TERMS FOR GRID ID %2.
MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_NODAL_MASS or

MNF_SET_NODAL_INERTIA_MAT functions encountered an error trying to load nodal information
of the specified type to the modal neutral file. MNF generation is not possible.

7810.9 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO STORE
MASS INVARIANT (NUMBER %1) DATA FOR
SUPERELEMENT OR MODULE %2. MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_INVARi functions encountered an

error attempting to store the specified mass invariant for the superelement or module. MNF generation is
not possible.

7810.10 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD
%1 DATA FOR GRID IDS %2 AND %3.
THE DATA BEING PROCESSED IS IGNORED AND NO DISPLAY CONNECTIONS ARE
LOADED TO THE MNF.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_FACEi functions encountered an

error. The data being processed is ignored.

7810.11 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

Main Index
 MSC Nastran Error Messages 933
Errors 7000 - 7999

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD

%1 INTERFACE INFORMATION FOR GRID ID %2.
THE INFORMATION HAS NOT BEEN LOADED TO THE MNF AND IS BEING IGNORED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_INTERFACE_NODE function has

encountered an error attempting to store boundary grid information for the specified grid ID. The data for
this grid ID is ignored.

7810.12 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO STORE
MNF UNITS INFORMATION.
UNITS SUPPLIED ON THE DTI,UNITS BULK DATA ARE: %1 %2 %3 %4. MNF GENERATION
ABORTED.

User information: The ADAMS/FLEX toolkit encountered an error trying to store units information for
the modal neutral file.

User action: Check to ensure that there is a bulk data DTI entry that defines the UNITS information. Also
check to ensure that the UNITS information specified is among the acceptable units specifications recog-
nized by ADAMS/FLEX.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_UNITS function encountered an

error. MNF generation is not possible.

7810.13 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO STORE
BASIC GRID POINT COORDINATES FOR GRID ID %1.
MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_NODE_COORDINATES functions

encountered an error. MNF generation is not possible.

7810.14 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

Main Index
 934 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO STORE

HEADER INFORMATION TO THE MNF.
MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_HEADER function encountered an

error. MNF generation is not possible.

7810.15 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD
MODAL PRELOAD DATA FOR MODE NUMBER %1.
(FOR LOAD CASE COLUMN NUMBER %2) MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_MODAL_PRELOAD function

encountered an error. MNF generation is not possible.

7810.16 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO LOAD
LOAD CASE LABEL DATA FOR MODE NUMBER %1.
MNF GENERATION CONTINUES.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_LOADCASE_LABEL function

encountered an error. MNF generation is not possible.

7810.17 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO WRITE
MNFDB DATABLOCK FOR SUPERELEMENT OR MODULE ID %1. MNF GENERATION
ABORTED.

Programmer information: An error has occurred in the ADAMS/FLEX toolkit MNF_WRITE_DB func-
tion attempting to write mnfdb datablock for the superelement or module. MNF generation is not possible.

7810.18 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

Main Index
 MSC Nastran Error Messages 935
Errors 7000 - 7999

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO STORE

MATRIX OPERATOR.
MNF GENERATION ABORTED.

Programmer information: An error has occurred in the ADAMS/FLEX toolkit MNF_SET_MATRIX-

_OPERATOR_%1 function attempting to store matrix operator. MNF generation is not possible.

7810.19 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

ADAMS/FLEX MNF TOOLKIT ERROR ENCOUNTERED WHILE TRYING TO LOAD NODAL
LOADS DATA RELATED TO MODAL LOAD FOR GRID ID %1 COORDINATE %2 FOR CASE
%3.
MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_MODAL_LOAD_NODAL function

encountered an error. MNF generation is not possible.

7810.20 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

ADAMS/FLEX MNF TOOLKIT ERROR ENCOUNTERED WHILE TRYING TO LOAD PRINCI-
PAL MODAL LOADS DATA FOR CASE %1.
MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_MODAL_LOAD_PRINCIPAL func-

tion encountered an error. MNF generation is not possible.

7810.21 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

ADAMS/FLEX MNF TOOLKIT ERROR ENCOUNTERED WHILE TRYING TO LOAD PRINCI-
PAL MODAL PRELOADS DATA FOR LOAD CASE COLUMN NUMBER %1.
MNF GENERATION ABORTED.

Programmer information: The ADAMS/FLEX toolkit MNF_SET_MODAL_PRELOAD_PRINCIPAL

function encountered an error. MNF generation is not possible.

7810.22 *** SYSTEM WARNING MESSAGE 7810 (AFERRM)

Main Index
 936 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADAMS/FLEX MNF TOOLKIT ENCOUNTERED AN ERROR WHILE TRYING TO STORE

MONITOR POINT.
MNF GENERATION ABORTED.

Programmer information: An error has occurred in the ADAMS/FLEX toolkit MNF_SET_MONI-

TOR_POINT_%1 function attempting to store matrix operator. MNF generation is not possible.

7811.0 *** SYSTEM INFORMATION MESSAGE 7811 (MNFMSG)

MNF MESSAGE: %1

7812.0 *** SYSTEM WARNING MESSAGE 7812 (CASPVT)

Parameter name %1 which is specified on the CASE module has no default value defined in the %2 table.

User action: Check spelling of parameter or define a default value in the NDDL or Bulk Data section.

7813.0 *** USER FATAL MESSAGE 7813 (NLUNLD)

ONE OR MORE COMPONENT DOFs FOR GRID ID %1 ARE NOT IN THE ANALYSIS SET (A-
SET).

User information: THE CORRECTION SPECIFIED IN THE CFLAG FIELD OF THE UNBALNC
BULK DATA ENTRY %2 REQUIRES THAT ALL COMPONENT DOFs OF THE UNBALANCED
GRID BE IN THE A-SET.

User action: MAKE SURE THAT NONE OF THE GRID's COMPONENTS ARE SPECIFIED ON
OMITi OR SPCi ENTRIES, CONSTRAINED IN FIELD 9 OF THE GRID ENTRY, DEFINED AS
DEPENDANT DOFs ON MPC OR RIGID ELEMENT ENTRIES, OR CONSTRAINED BY THE
AUTOSPC OPERATION.

7814.0 *** USER FATAL MESSAGE 7814 (ROTDR2)

RSPINR ENTRY FOR REFERENCE ROTOR WITH ROTORID OF %1 AND ROTRSEID OF %2
SPECIFIED ON RGYRO BULK DATA ENTRY %3 DOES NOT EXIST.

User action: CORRECT REFERENCE ROTOR SPECIFICATION ON RGYRO ENTRY OR ADD

AN RSPINR BULK DATA ENTRY FOR THE REFERENCE ROTOR.

7815.0 *** USER FATAL MESSAGE 7815

ROTORG ENTRY WITH ID %1 DEFINES ONLY 1 VALID GRID

Main Index
 MSC Nastran Error Messages 937
Errors 7000 - 7999

7815.1 *** USER FATAL MESSAGE 7815

THE FOLLOWING GRID POINTS ARE NOT ON THE AXIS OF ROTATION OF ROTOR %1

7815.2 *** USER FATAL MESSAGE 7815

THE JOB HAS BEEN TERMINATED DUE TO ONE OR MORE ROTOR DEFINITION ERRORS
IDENTIFIED ABOVE

7816.0 *** USER FATAL MESSAGE 7816

RSPINR ENTRIES HAVE A DIFFERENT NUMBER OF RELATIVE SPIN RATES

7817.0 *** USER FATAL MESSAGE 7817

ROTOR SPEEDS ON RSPINR ENTRY OF REFERENCE ROTOR WITH ROTORID OF %1 AND
ROTRSEID OF %2 ARE NOT STRICTLY IN ASCENDING OR DESCENDING ORDER

7818.0 *** SYSTEM FATAL MESSAGE 7818 (SEQP)

A LOGIC ERROR was encountered WHILE PARTITIONING THE MODEL (EXTREME).

User action: USE MSCMLV (PARAM,OLDSEQ,11) TO PARTITION THE MODEL.

7819.0 *** USER FATAL MESSAGE 7819 (ECONVD)

THE CHARACTERISTIC LENGTH REFERENCED BY CONV ELEMENT ID %1 IS ZERO.

7820.0 *** USER FATAL MESSAGE 7820 (ECONVD)

THE GRID ID %1 OF THE INLET POINT REFERENCED BY CONV ELEMENT ID %2 DOES
NOT EXIST.

7821.0 *** USER FATAL MESSAGE 7821 (ECONVD)

THE GRID ID %1 OF THE INLET POINT AND THE CENTER OF CONV ELEMENT ID %2
ARE COINCIDENT.

7822.0 *** USER FATAL MESSAGE 7822 (ECONVD)

Main Index
 938 MSC Nastran Error Messages
Errors 7000 - 7999

THERE IS NO THERMAL CONDUCTIVITY SPECIFIED ON THE MAT4 ENTRY FOR CONV

ELEMENT %1.

User information: FREE CONVECTION ELEMENTS REQUIRE CONDUCTIVITY ON A MAT4

ENTRY IF ON THE PCONV ENTRY THE FORMULA TYPE OF THE TABULAR FUNCTION IS
2.

7823.0 *** USER FATAL MESSAGE 7823 (DSAD1)

SUBCASE %1 REFERENCES A DRESP1 ENTRY THAT SEEKS A RESPONSE FOR MODE NUM-
BER %2 BUT ONLY %3 MODES HAVE BEEN EXTRACTED

User action: EITHER INCREASE THE NUMBER OF EXTRACTED EIGENVECTORS OR

CHANGE THE REQUEST FOR EIGENVECTOR %2 ON THE DRESP1 ENTRY

7824.0 *** USER INFORMATION MESSAGE 7824 (DSGRDM)

THE NUMBER OF GRID POINTS IN THE ANALYSIS MODEL = %1.
THE NUMBER OF GRID POINTS IN THE DESIGN MODEL = %2.
THE DESIGN MODEL COMPRISES %3 PERCENT OF THE ANALYSIS MODEL.

7825.0 *** USER INFORMATION MESSAGE 7825 (DSGRDM)

THE DESIGN MODEL COMPRISES MORE THAN %1 (DRATIO ON THE DOPTPRM ENTRY)
PERCENT OF THE ANALYSIS MODEL.

User information: THE AUTOMATIC SUPERELEMENT OR MODULE OPTIMIZATION PRO-

CESS WILL BE TURNED OFF.

7826.0 **** USER FATAL MESSAGE 7826

AERODYNAMIC BODIES ARE NOT SUPPORTED BY %1

7827.0 *** USER WARNING MESSAGE 7827 (CRPMDD)

ON SPLINE6 BULK DATA ENTRY ID= %1 AND FOR SOURCE GRID %2, AN ELEMENT cannot
be found FOR METHCON="CIRCBIAS".

User information: The source grid will be ignored which might cause unbalanced forces.

User action: Check associated grid and elements or SPECIFY METHCON="NODEPROX".

Main Index
 MSC Nastran Error Messages 939
Errors 7000 - 7999

7828.0 *** USER FATAL MESSAGE 7828 (SPCDRX)

GRID POINT %1 and COMPONENT %2 is specified on both a SPCR and SPCD (or SPC) entry with
set ID= %3

7829.0 *** USER FATAL MESSAGE 7829 (DOPR1C)

GPLYID %1 REFERENCED ON A DVPREL1 ENTRY IS NOT DEFINED ON ANY PCOMPG
BULK DATA ENTRY.

User action: ENSURE THAT THE GPLYID ON DVPREL1 IS ALSO SPECIFIED ON AT LEAST
ONE PCOMPG ENTRY.

7830.0 *** USER FATAL MESSAGE 7830 (DSAD13)

DRESP1 ID %1 REFERENCES A NON-EXIST PLY ID %2.

User action: ENSURE THAT PLY ID IS LESS THAN NUMBER OF PLIES SPECIFIED ON A
PCOMP BULK DATA ENTRY or IS SPECIFIES AS A GPLYID ON A PCOMPG ENTRY.

7831.0 *** SYSTEM FATAL MESSAGE 7831

SCA %1 service initialization failed.

7832.0 *** SYSTEM FATAL MESSAGE 7832

SCA %1 service pointer not found.

7833.0 *** SYSTEM INFORMATION MESSAGE 7833

SCA %1 service successfully initialized.

7834.0 *** SYSTEM INFORMATION MESSAGE 7834

SCA %1 service license not available.

7835.0 *** SYSTEM INFORMATION MESSAGE 7835

SCA %1 service unloading failed.

7836.0 *** SYSTEM FATAL MESSAGE 7836

User defined SCA service %1 terminated with return code: %2

7836.1 *** SYSTEM FATAL MESSAGE 7836 (MAKEBULK)

Main Index
 940 MSC Nastran Error Messages
Errors 7000 - 7999

SCA SERVICE %1 TERMINATED WITH RETURN CODE: %2.

7836.2 *** SYSTEM FATAL MESSAGE 7836

PLEASE CHECK DIGIMAT MODEL MATERIAL AND LOG FILES, %1 TERMINATED WITH
RETURN CODE %2

7837.0 *** SYSTEM FATAL MESSAGE 7837 (ARPFxD).

%1 MATRIX IS NOT SYMMETRIC OR HERMITIAN.
USE COMPLEX LANCZOS OR HESSENBERG METHOD INSTEAD.

7837.1 *** SYSTEM FATAL MESSAGE 7837 (ARPFxD).

THE NUMBER OF REQUESTED MODES IS TOO HIGH.
REDUCE IT TO %1 THEN RESUBMIT.

7837.2 *** SYSTEM FATAL MESSAGE 7837 (ARPFxD).

UNABLE TO DETERMINE PROBLEM TYPE.
CONTACT HEXAGON AB CLIENT SUPPORT.

7838.0 *** SYSTEM FATAL MESSAGE 7838 (ARPLU).

%1 FAILED DUE TO %2
CONTACT HEXAGON AB CLIENT SUPPORT.

7839.0 *** USER INFORMATION MESSAGE 7839 (UDSFxD).

NUMERIC PIVOTING REDUCED TO IMPROVE PERFORMANCE. NUMBER OF INCI-
DENCES IS %1
THIS MAY RESULT IN A LOSS OF SOLUTION ACCURACY.
USE MDLPRM,PIVTHRSH TO SET PIVOTING THRESHOLD PARAMETER TO 0.1 MAY
IMPROVE SOLUTION ACCURACY BUT DEGRADE PERFORMANCE.
CURRENT PIVOTING PARAMETER: %2 MINIMUM DIAG TO OFF-DIAG RATIO: %3

7839.1 *** USER WARNING MESSAGE 7839 (UDSFxD).

Main Index
 MSC Nastran Error Messages 941
Errors 7000 - 7999

THE UNSYMMETRIC DECOMPOSITION ENCOUNTERED %1 TINY FACTOR DIAGONAL

TERMS.
THE SMALLEST FACTOR DIAGONAL TERM IS %2, COMPARED TO THE TINY THRESH-
OLD OF %3.

User action: VERIFY THE NUMERIC SOLUTION ACCURACY OF MSCLU.

USE MDLPRM,PIVTHRSH TO SET EXPONENT VALUE OF PIVOTING THRESHOLD PARAM-
ETER.
THIS MAY IMPROVE SOLUTION ACCURACY BUT DEGRADE PERFORMANCE.
CURRENT THRESHOLD EXPONENT VALUE IS %4.

7839.2 *** USER INFORMATION MESSAGE 7839 (UDCOMP).

DUE TO POTENTIAL NUMERIC STABILITY PROBLEMS, THE UNSYMMETRIC DECOMPO-
SITION IS RERUN WITH A TIGHTER PIVOTING THRESHOLD (ie. MDLPRM,PIVTHRSH,-1).
THIS WOULD RESULT IN BETTER ACCURACY BUT A SLOWER RUN TIME.

7840.0 *** SYSTEM FATAL MESSAGE 7840 (DFMRxD).

THE REQUESTED NUMBER OF GPUS %1 IS GREATER THAN THE AVAILABLE NUMBER OF
GPUS %2.
REDUCE THE NUMBER OF GPUIDS ON THE NASTRAN COMMAND LINE, THEN RESUB-
MIT.

7840.1 *** SYSTEM FATAL MESSAGE 7840 (DFMRxD).

OUT-OF-RANGE GPUID(S) ON THE NASTRAN COMMAND LINE. THE GPUID(S) SHOULD
BE BETWEEN 0 and %1.
FIX THE PROBLEM, THEN RESUBMIT.

7840.2 *** SYSTEM FATAL MESSAGE 7840 (DFMRxD).

NASTRAN CANNOT FIND ANY CUDA-CAPABLE DEVICE ON THE SYSTEM.
CONTACT THE APPROPRIATE HARDWARE SUPPORT/SYSTEM ADMIN.

7840.3 *** SYSTEM INFORMATION MESSAGE 7840 (DFMRxD).

MSCLDL SPARSE FACTORIZATION WILL BE RUN ON GPU DEVICE %1 IN ADDITION TO
CPU.

7840.4 *** SYSTEM INFORMATION MESSAGE 7840 (DFMRxD).

Main Index
 942 MSC Nastran Error Messages
Errors 7000 - 7999

- AUTHORIZATION ERROR ***

UNABLE TO OBTAIN LICENSES FOR GPU
NASTRAN WILL CONTINUE TO RUN ON CPU

7841.0 *** SYSTEM FATAL MESSAGE 7841 (DFMZxD).

THE xSYTRF FACTORIZATION OF FRONTAL DIAGONAL BLOCK HAS FAILED.
THE %1 -TH ARGUMENT HAD AN ILLEGAL VALUE.

7841.1 *** SYSTEM FATAL MESSAGE 7841 (UDSZxD).

THE xGETRF FACTORIZATION OF FRONTAL DIAGONAL BLOCK HAS FAILED.
THE %1 -TH ARGUMENT HAD AN ILLEGAL VALUE.

7842.0 *** USER INFORMATION MESSAGE 7842 (DFMSA).

MDLPRM,NONUPIV IS SET TO 3 FOR SOLUTION SEQUENCE %1

7842.1 *** USER INFORMATION MESSAGE 7842 (UDSFA).

MDLPRM,NONUPIV IS SET TO 3 FOR SOLUTION SEQUENCE %1

7843.0 *** USER FATAL MESSAGE 7843 (DFMSA).

MSCLDL SPARSE DIRECT SOLVER RANK UPDATE SIZE %1 EXCEEDS 400.

User action: REDUCE SYS205/SYS219, AND RERUN.

7844.0 *** SYSTEM FATAL MESSAGE 7843 (MCE2PR)

The number of %1-set DOFs (%2) is not equal to the number of %3 in %4 (%5)

User action: If the subDMAPs are being ALTERed then check for DMAP errors. Otherwise, contact MSC
Client support.

7843.1 *** USER FATAL MESSAGE 7843 (UDSFA).

MSCLU SPARSE DIRECT SOLVER RANK UPDATE SIZE %1 EXCEEDS 400.

User action: REDUCE SYS220/SYS221, AND RERUN.

7901.0 *** USER FATAL MESSAGE 7901 (dommrg)

THE MERGE DESIGN MODELS PROCESS REQUIRES AT LEAST TWO
INPUT MODELS AND THERE ARE ONLY %1

Main Index
 MSC Nastran Error Messages 943
Errors 7000 - 7999

7902.0 *** USER FATAL MESSAGE 7902 (dommrg)

DESMOD = %1 HAS BEEN SPECIFIED FOR MORE THAN ONE DESIGN MODEL.

User information: THE MERGE DESIGN MODELS PROCESS REQUIRES THAT THE DESMOD
PARAMETER BE UNIQUE FOR EACH MODEL.

7903.0 *** USER FATAL MESSAGE 7903 (dommrga)

DESIGN VARIABLE ID = %1 IS INDEPENDENT IN ONE MODEL BUT DEPENDENT IN
ANOTHER.

User information: DESIGN VARIABLES THAT ARE COMMON ACROSS MODELS HAVE TO
SHARE ALL THEIR ATTRIBUTES.

7904.0 *** USER FATAL MESSAGE 7904 (dommrgp)

THE COMBINED OBJECTIVE SUMS %1 MODELS BUT THERE ARE %2 MODELS IN THE
DESIGN TASK.

User information: INCORRECT RESULTS MAY BE GENERATED IF THESE TWO NUMBERS

DIFFER.

7905.0 *** USER FATAL MESSAGE 7905 (dommrgp)

THE COMBINED OBJECTIVE INVOKES %1 DRESP1S AND %2 DRESP2S BUT THE MODELS
HAVE %3 DRESP1S AND %4 DRESP2S FOR THE OBJECTIVES.

User action: CORRECT THE DESIGN TASK SO THAT THE NUMBER OF TYPE ONES AND
TYPE TWOS IS CONSISTENT BETWEEN THE COMBINED OBJECTIVE AND THE MODELS.

7910.0 *** USER INFORMATION MESSAGE 7910 (OUTADFE)

DATA BLOCK %1 (%2) WRITTEN TO ADF FILE.

7910.1 *** USER INFORMATION MESSAGE 7910 (OUTADFE)

%1 OF %2%3 IN SUBCASE %4 IS EXPORTED TO ADF FILE.

7911.0 *** SYSTEM FATAL MESSAGE 7911 (OUTADFE)

Main Index
 944 MSC Nastran Error Messages
Errors 7000 - 7999

THE ADF FILE EXPORTATION MODULE ATTEMPT TO LOCATE THE NASTRAN %1 FILE
NAME IN NASTRAN INTERNAL TABLES WAS UNSUCCESSFUL. ADF EXPORTATION
ABORTED.

7911.1 *** USER FATAL MESSAGE 7911 (OUTADFE)

THE ADF FILE EXPORTATION MODULE REQUIRE %1 TABLE BUT IT SEEMS TO BE
PURGED.

User action: CHECK THE INPUT BLOCKS OF OUTADF MODULE.

7911.2 *** USER FATAL MESSAGE 7911 (OUTADFE)

GRID %1 CAN NOT BE FOUND IN BGPDT TABLE.

User action: CONFIRM THE CONSISTENCY OF GRID IDS BETWEEN RESPONSE AND
BGPDT TABLES.

7911.3 *** SYSTEM FATAL MESSAGE 7911 (OUTADFE)

ADF EXPORTATION FUNCTION %1 ERROR WAS OCCURRED FOR THE NEXT DATA.
CASE %2, GRID %3, COORDINATE %4, RESPONSE TYPE %5

User action: CONTACT MSC CLIENT SUPPORT.

7911.4 *** USER WARNING MESSAGE 7911 (OUTADFE)

THE DATA BLOCK %1 CAN NOT BE SUPPORTED BY OUTADF MODULE.

User action: CONFIRM THE DATA BLOCK IS FREQUENCY OR TRANSIENT RESPONSES OR

PARTICIPATION FACTORS.

7911.5 *** USER WARNING MESSAGE 7911 (OUTADFE)

THE UNITS OF %1 ARE ILLEGAL OR UNDEFIED THEN SI UNIT WILL BE ASSUMED.

User action: CONFIRM DTI,UNITS BULK DATA ENTRY EXISTS AND THE UNIT CHARAC-
TERS ARE CORRECT.

7951.0 *** USER FATAL MESSAGE 7951 (OP2TOADF)

Main Index
 MSC Nastran Error Messages 945
Errors 7000 - 7999

NO GRID IS FOUND IN BULK DATA NOR OUTPUT2 FILE.

User action: PLEASE ADD THE GEOMERTY DATA TO BULK DATA OR OUTPUT2 FILE.

7952.1 *** USER FATAL MESSAGE 7952.1 (READAC)

ASSIGNED PHYSICAL FILE DOES NOT EXIST OR INDENTICAL FORTRAN UNITS ARE
USED IN ACLOAD.

User action: CONFIRM FORTRAN UNIT NUMBERS IN ACLOAD AND ASSIGN STATEMENTS.

7952.2 *** USER FATAL MESSAGE 7952.2 (READAC)

ILLEGAL SIZE OF MATRICES IN UNIT %1. LOAD SEQUENCE %2 IS GREATER THAN AVAIL-
ABLE LOAD CASES %3.

User action: CONFIRM THE FILE FROM ACTRAN.

7952.3 *** USER FATAL MESSAGE 7952.3 (READAC)

ILLEGAL DMIG FORMAT DATA IN UNIT %1.

User action: CONFIRM THE FILE FROM ACTRAN.

7952.4 *** USER FATAL MESSAGE 7952.4 (READAC)

ACTRIM CAN BE APPLIED FOR COUPLED FLUID-STRUCTURE AND SYMMETRIZED SYS-
TEM.

User action: CONFIRM ACTRIM AND PARAM,ACSYM CARDS.

7952.5 *** USER FATAL MESSAGE 7952.5 (READAC)

ACTRIM %1 DOES NOT EXIST IN INPUT DATA.

User action: CONFIRM ACTRIM CARDS.

7952.6 *** USER FATAL MESSAGE 7952.6 (READAC)

Main Index
 946 MSC Nastran Error Messages
Errors 7000 - 7999

ASSIGNED PHYSICAL FILE DOES NOT EXIST OR INDENTICAL FORTRAN UNITS ARE
USED IN ACTRIM.

User action: CONFIRM FORTRAN UNIT NUMBERS IN ACTRIM AND ASSIGN STATEMENTS.

7952.8 *** USER WARNING MESSAGE 7952.8 (READAC)

PACLV READ FROM UNIT %1 FOR ACLOAD %2 IS NULL. LOAD VECTOR PRODUCED MAY
BE IN ERROR.

User action: REVIEW ACLOAD GENERATION STEPS.

7953.0 *** USER WARNING MESSAGE 7953 (READAC)

ACTRIM %1 HAS THE TERMS NOT ON WETTED AREA DEFINED IN NASTRAN.
THE TERMS RELATED TO THE NEXT DOF LIST WILL BE ELIMINATED.

7998.0 *** USER INFORMATION MESSAGE 7998.0 (NL3INT)

Minimum Iteration default value is set to 2 because this job involves contact analysis, or you have set only
"U" as convergence criteria.

7998.1 *** USER WARNING MESSAGE 7998.1 (NL3INT)

Current User Defined Minimum Iteration is 1. MINITER=2 is recommended when analysis involves con-
tact analysis or you only use "U" as convergence criteria.

7998.2 *** USER WARNING MESSAGE 7998.2 (NL3INT)

DUE TO CONFLICT WITH MODEL PARAMETER BCSOL129, ITRFMT IS IGNORED.

Main Index
 MSC Nastran Error Messages 947
Errors 8000 - 8999

Errors 8000 - 8999

8100.0 *** System INFORMATION MESSAGE 8100 (NL3INT)
No Lagrange Multiplier Degrees-of-freedom were found in Contact analysis.

User information: Contact analysis will not be performed.

8101.0 *** USER INFORMATION MESSAGE 8101 (NL3INT)

The Lagrange Multiplier Factor and Penalty Function values: LMFACT=%1 and PENFN=%2

8102.0 *** system FATAL MESSAGE 8102 (NL3INT)

A LOGIC ERROR was encountered WHILE reading data from the Nastran database to the Contact
Component Database

8103.0 *** system FATAL MESSAGE 8103 (NL3INT OR NL3OFU)

A LOGIC ERROR was encountered WHILE writing data from Contact Component Database to the
Nastran database.

8104.0 *** USER FATAL MESSAGE 8104 (N3DINT)

Illegal specification of the BCONTACT Case Control command.

User information: Only BCONTACT=n and BCONTACT=ALLBODY are supported.

8105.0 *** System FATAL MESSAGE 8105 (N3DINT)

In contact analysis, The Number of pairs (ID,Area) in N3Dafa is incorrect

8106.0 *** System FATAL MESSAGE 8106 (N3DINT)

In contact analysis, Error encountered while mapping SIL to internal grid ID - %1

8107.0 *** System FATAL MESSAGE 8107 (N3DINT)

In contact analysis, Error encountered while mapping internal grid ID to SIL - %1

8108.0 *** System FATAL MESSAGE 8108 (N3DINT)

In contact analysis, Error encountered while mapping internal grid ID to external grid ID - %1

8109.0 *** System FATAL MESSAGE 8109 (N3DINT)

Error encountered while sending %1 data to the 3D Contact Component

Main Index
 948 MSC Nastran Error Messages
Errors 8000 - 8999

8109.1 *** System FATAL MESSAGE 8109 (N3DINT)

Error encountered while sending %1 data to the Contact Component in VCCT

8109.2 *** User FATAL MESSAGE 8109 (N3DINT)

Some pairs of adjacent shell elements have opposite normals in contact body %1, may cause wrong results.
These element pairs are listed below.

User action: review your model or set IGNSHBDN of MDLPRM to 1 to continue processing.

8109.3 *** User FATAL MESSAGE 8109 (N3DINT)

Some pairs of adjacent shell elements have opposite normals in contact body %1, may cause wrong results.
Up to %2 of these element pairs are listed below.

User action: review your model or set IGNSHBDN of MDLPRM to 1 to continue processing.

8109.4 *** User WARNING MESSAGE 8109 (N3DINT)

Some pairs of adjacent shell elements have opposite normals in contact body %1, may cause wrong results.
These element pairs are listed below. IGNSHBDN of MDLPRM had been set to 1 to continue processing.

8109.5 *** User WARNING MESSAGE 8109 (N3DINT)

Some pairs of adjacent shell elements have opposite normals in contact body %1, may cause wrong results.
Up to %2 of these element pairs are listed below. IGNSHBDN of MDLPRM had been set to 1 to continue
processing.

8109.6 *** User WARNING MESSAGE 8109 (N3DINT)

Some shell element edges have more than two elements connecting to it. These edges (node 1 and node 2)
are listed below.

8109.7 *** User WARNING MESSAGE 8109 (N3DINT)

Some shell element edges have more than two elements connecting to it. Up to %2 of these edges (node 1
and node 2) are listed below.

8109.8 *** User FATAL MESSAGE 8109 (N3DINT)

BRKPROP or MOTION entry requested by BRKSYS with ID %1 does not exist. Please check the detailed
error message above.

Main Index
 MSC Nastran Error Messages 949
Errors 8000 - 8999

8110.0 *** USER warning MESSAGE 8110 (N3DINT)

BCPARA>0 is being selected below the subcase or step case level.

User information: This request will be ignored.

8110.1 *** USER WARNING MESSAGE 8110 (IXBCTABL)

The BIAS of 0.0 is specified in the BCTABLE ID = %1. As a result, the BIAS value on the BCPARA entry
will be applied.

User information: The allowable range for BIAS is 0.0 < BIAS <= 1.0.
A VALUE of 0.0 for BIAS is treated as blank. To obtain a near zero value, enter 1.0E-16.

8111.0 *** USER FATAL MESSAGE 8111 (N3DINT)

Error encountered while processing %1 option on the %2 bulk data entry

8112.0 *** USER warning MESSAGE 8112 (N3DINT)

IREL is not zero On the BCMOVE Bulk Data Entry.

User information: The program will automatically reset IREL to zero.

8113.0 *** USER FATAL MESSAGE 8113 (N3DINT)

There a format error related to the BODY's ID on BCMOVE Bulk Data entry

8114.0 *** USER FATAL MESSAGE 8114 (N3DINT)

No BCTABLE Bulk Data entries were found when BCONTACT=n(n>0) was specified in the Case
Control Deck.

8114.1 *** USER FATAL MESSAGE 8114 (M3DCNT1B)

No BCTABL1 AND BCONECT Bulk Data entries were found when BCONTACT=n(n>0) was specified
in the Case Control Deck.

8115.0 *** USER FATAL MESSAGE 8115 (N3DINT)

%1 Bulk Data entry ID = %2 not found.

Main Index
 950 MSC Nastran Error Messages
Errors 8000 - 8999

8116.0 *** USER FATAL MESSAGE 8116 (N3DINT)

There is a Format error on %1 Bulk Data entry ID = %2
8117.0 *** System FATAL MESSAGE 8117 (N3DINT)
The total available parameters of %1 = %2 are not consistent with the current definition of the BCPARA
record.

8118.0 *** System FATAL MESSAGE 8118 (NL3INC)

Error encountered while iterating in contact analysis. Programmer Information: Incorrect iteration infor-
mation either ADDITR is not equal to zero or RITER is 3.

8119.0 *** System FATAL MESSAGE 8119 (N3DINC)

Error encountered while sending displacement-%1 to the Contact Component

8120.0 *** System FATAL MESSAGE 8120 (N3DINC)

Error encountered in the Contact Component while initializing the neighbour and corner information for
all bodies.
*** System INFORMATION MESSAGE 8121 (N3DINC)

8122.0 *** USER FATAL MESSAGE 8122 (N3DINC)

The value on CONTROL on BCBODY or BCRIGID Bulk Data entry ID = %1 is invalid.

8123.0 *** System FATAL MESSAGE 8123 (N3DINC)

Error encountered while retrieving or storing variables to the Contact Component

8124.0 *** System FATAL MESSAGE 8124 (N3DINC)

Error encountered while performing a binary search for rigid body IDs during Contact analysis

8125.0 *** System FATAL MESSAGE 8125 (N3DINC)

Error encountered while processing the BCMOVE (approach/synchron) forming approach which defines
the movement of the bodies

8126.0 *** System INFORMATION MESSAGE 8126 (N3DINC)

There is change in flexible contact (sliding to next segment or new contact) while processing the BCMOVE
(approach/synchron)

8127.0 *** System FATAL MESSAGE 8127 (N3DMPC)

Error encountered in determining the contact conditions in the Contact Component

Main Index
 MSC Nastran Error Messages 951
Errors 8000 - 8999

8128.0 *** System FATAL MESSAGE 8128 (N3DMPC)

Error encountered in obtaining the contact MPC constraint from the Contact Component
8129.0 *** System FATAL MESSAGE 8129 (N3DMPC)
Error encountered in mapping external grid ID to internal grid ID

8130.0 *** System FATAL MESSAGE 8130 (N3DMPC)

Error encountered while recovering the coordinates of internal grid ID

8131.0 *** System FATAL MESSAGE 8131 (N3DMPC)

Logic error %1 encountered while processing the Contact Contraint Equations

8132.0 *** System FATAL MESSAGE 8132 (N3DMPC)

Error encountered while mapping internal grid ID to scalar index

8133.0 *** System FATAL MESSAGE 8133 (N3DPEN)

Error encountered in checking the penetration condition of the contact bodies

8134.0 *** System INFORMATION MESSAGE 8134 (N3DSEP)

Penetration continues to be detected in contact analysis.

User information: Convergence status will be reset to false.

8135.0 *** USER INFORMATION MESSAGE 8135 (N3DSEP)

In contact analysis, penetration occurs. The force factor (N3DFF2=%1), a fraction of the load increment in
the current time step, is less than 1.0 and applied in the current iteration to remove penetration.

User information: Convergence status will be reset to false.

8135.1 *** USER WARNING MESSAGE 8135 (N3DSEP)

The number of iterations to remove penetration exceeds the defined MAXITR, more iteration is needed.

8135.2 *** USER FATAL MESSAGE 8135 (N3DSEP)

Main Index
 952 MSC Nastran Error Messages
Errors 8000 - 8999

MAXITR*10 iterations have been implemented to remove the penetration.

Based on the current convergence rate, it is estimated that it may take more than 10000 additional itera-
tions to remove the penetration. Therefore the job is stopped. If you want to allow the run to continue, set
SYSTEM cell 756 to 0.

8135.3 *** USER FATAL MESSAGE 8135 (N3DSEP)

MAXITR*10 iterations have been implemented to remove the penetration.
Based on the current convergence rate, it is estimated that it may take more than 1% additional iterations
to remove the penetration.
Therefore the job is stopped. If you want to allow the run to continue, set SYSTEM cell 756 to 0.

8136.0 *** System FATAL MESSAGE 8136 (N3DSEP)

Error encountered in checking the separation condition in Contact analysis.

8137.0 *** System WARNING MESSAGE 8137 (NL3CON)

%1 condition has been detected. Additional iterations will be performed.

User information: Convergence status will be reset to false.

8137.1 *** System WARNING MESSAGE 8137 (NL3CON)

To activate the N2S accelerated separation check feature, either the vector component (V) or the length
method (N) convergence criterion must be specified in CONV for step %1.

8138.0 *** System FATAL MESSAGE 8138 (N3DMOV)

Error encountered while updating the position of all bodies at the end of a load increment (or time step)

8139.0 *** System FATAL MESSAGE 8139 (N3DMOV)

Error encountered while getting output results for the contact %1 from the Contact Component

8139.1 *** USER INFORMATION MESSAGE 8139 (MCNTINI)

CONTACT CHECK REQUESTED BUT NO CONTACT DETECTED AT TIME = %1 SUBCASE
%2 STEP %3

8140.0 *** System FATAL MESSAGE 8140 (N3DFOR)

Error encountered while sending Contact Forces to the Contact Component

Main Index
 MSC Nastran Error Messages 953
Errors 8000 - 8999

8141.0 *** System FATAL MESSAGE 8141 (N3DFOR)

Error encountered while sending Average Nodal Stress to the Contact Component

8142.0 *** System FATAL MESSAGE 8142 (N3DFOR)

Error encountered while sending Average Nodal Area to the Contact Component

8143.0 *** SYSTEM FATAL MESSAGE 8143 (N3DFRA)

Logic error %1 encountered while assembling the friction stiffness matrix

8144.0 *** System FATAL MESSAGE 8144 (N3DFRI)

Error encountered while processing the stiffness matrix and load vector of friction for contact analysis.

8145.0 *** System WARNING MESSAGE 8145 (NL3CON)

Penetration distance beyond the threshold value (the AUGDIST entry on BCTABLE or BCONPRG) has
been detected in the Segment-to-Segment contact.

User information: Convergence status will be reset to false.

8146.0 *** USER FATAL MESSAGE 8146 (MCNTDAT)

No supported elements have been found in the deformable contact body, with BCBODY ID = %1.

User information: Every deformable contact body must contain some elements, supported by 3D contact
capability.

User action: Check contact modeling for errors in the input data entries, such as BCTABLE, BCBODY
and so on. Also make sure the elements involved in contact are of supported element types. Supported
Types: deformable elements such as CQUAD4, CHEXA, etc.

8146.1 *** USER FATAL MESSAGE 8146 (MCNTINI)

Not a single grid point has been found from all deformable contact bodies, after collecting contact nodes
associated with the deformable contact bodies.

User action: Check contact modeling for errors in the input data entries, such as BCTABLE, BCBODY
and so on. Also make sure the elements involved in 3D contact are of supported element types. Supported
Types: deformable elements such as CQUAD4, CHEXA, etc.

Main Index
 954 MSC Nastran Error Messages
Errors 8000 - 8999

8146.2 *** USER FATAL MESSAGE 8146 (MCNTGCK)

General glue and touching contact is only supported in SOL 101, 400, and 600. For other solution
sequences, only permanent glue contact is supported. IGLUE > 0 must be set to each entry in the
BCTABLE in the very first STEP (loadcase).

8146.3 *** USER FATAL MESSAGE 8146 (MCN1DATD)

For %1 ID = %2, either no supported elements have been found in the deformable contact body or all ele-
ments have been specified in the contact body of another contact pair.

User information: Every deformable contact body must contain some elements, supported by 3D contact
capability.

User action: Check contact modeling for errors in the input data entries, such as BCTABL, BCONECT,
BCBODY1 and so on. Also make sure the elements involved in contact are of supported element types and
are not specified in the contact body of another contact pair. Supported Types: deformable elements such
as CQUAD4, CHEXA, etc.

8146.4 *** USER FATAL MESSAGE 8146 (MCN1INID)

Not a single grid point has been found from all deformable contact bodies, after collecting contact nodes
associated with the deformable contact bodies.

User action: Check contact modeling for errors in the input data entries, such as BCTABL1, BCONECT,
BCBODY1 and so on. Also make sure the elements involved in 3D contact are of supported element types.
Supported Types: deformable elements such as CQUAD4, CHEXA, etc.

8146.5 *** USER FATAL MESSAGE 8146 (MCN1GCK)

General glue and touching contact is only supported in SOL 101, 400, and 600.
For other solution sequences, only permanent glue contact is supported.
IGLUE > 0 must be set to each entry in the BCONPRG in the very first STEP (loadcase).

8146.6 *** USER FATAL MESSAGE 8146 (MCNTCOL)

The %1 element ID = %2 with missing mid-side nodes is not allowed in contact analysis.

User information: Define all mid-side nodes for contact analysis.

Main Index
 MSC Nastran Error Messages 955
Errors 8000 - 8999

8146.7 *** USER FATAL MESSAGE 8146 (MCNTPCH)

Materials must be specified for property (PID = %1).
For 2D contact analysis, MID1(membrane) field in PSHELL must be non-zero and for 3D contact analysis
MID2(bending) field in PSHELL must be non-zero.

8146.8 *** USER WARNING MESSAGE 8146 (MCN1GCK)

Large Displacement (LGDISP>0) is found in Permanent Glued Contact.

User information: Permanent Glued Contact may have incorrect results in large rotation/deformation
effect.

User action:
1. Change LGDISP<=0; or
2. Set SYSTEM(758)=2 to change Permanent Glue to Step Glue automatically.

8146.9 *** USER WARNING MESSAGE 8146 (MCN1GCK)

Large Displacement (LGDISP>0) is found in Permanent Glued Contact.

User information: Step Glue Contact is activated to support Large Displacement. All positive IGLUE ref-
erenced in subsequent load steps are set to negative.

8147.0 *** USER FATAL MESSAGE 8147 (MCNTINI)

Deformable-to-rigid permanently-glued contact is not supported for velocity or position controlled rigids.

User action: Run a general contact with the glued as an option or use load controlled rigids with SPC's for
the load-controlled grid points.

8148.0 *** USER FATAL MESSAGE 8148 (MCNTOUT)

Main Index
 956 MSC Nastran Error Messages
Errors 8000 - 8999

Segment-to-segment contact is not supported in the permanently glued contact.

User information:
1. The Segment-to-segment contact is supported only in SOL 101 and SOL 400 for a general touching
contact with or without glued option. The permanently glued contact is supported only in the node-
to-segment contact.
2. Please refer BCTABLE entry in Nastran Quick Reference Guide for how to run a permanently glued
contact.
User action:
1. Run a general touching contact with the segment-to-segment contact approach in SOL 101 or SOL
400, by using BCPARA,0,NLGLUE,1.
2. Run a permanently glued contact in all supported solutions using the node-to-segment contact
approach.
8148.1 *** USER INFORMATION MESSAGE 8148 (MCNTOUT)
Segment-to-segment permanent glued contact is activated.

8148.2 *** USER FATAL MESSAGE 8148 (GP4)

PERMANENT-GLUE (TIED) CONTACT HAS BEEN DEFINED FOR SEGMENT-TO-SEGMENT
CONTACT. BUT NO NODES WERE FOUND TO GLUE.

User action: CHECK IF THE DISTANCE BETWEEN THE CONTACT BODIES IN SAME
CONTACT PAIR IS WITHIN THE CONTACT TOLERANCE. THE DEFAULT OF CONTACT
TOLERANCE IS DETERMINED BY THE SMALLER ONE OF 1/20TH OF THE SHORTEST
EDGE LENGTH OF ELEMNTS OR 1/4TH OF THE THICKNESS OF THE THINNEST SHELL
ELEMENT, DEFINED IN CONTACT BODIES. IN ADDITION, BY DEFAULT, DEFAULT
CONTACT TOLERANCE IS BASED ON ALL THE ELEMENTS IN CONTACT BODIES AND
APPLIED TO ALL THE CONTACT PAIRS. USE BCPARA,0,ERRBAS,1 TO COMPUTE AND
APPLY THE TOLERANCE FOR EACH CONTACT PAIR INDIVIDUALLY.

8148.3 *** USER WARNING MESSAGE 8148 (GP4)

The density of contact constraint matrix of Segment-to-Segment(STS) permanently-glued contact is either
negligibly small or zero. The gluing may not be effective.

8148.4 *** USER WARNING MESSAGE 8148 (MCNTPAR)

Quadratic Element found in Node-to-Seg Contact.
Program will reset IBSEP=2 because IBSEP=0 is not supported by mid-side node element.

Main Index
 MSC Nastran Error Messages 957
Errors 8000 - 8999

8148.5 *** USER FATAL MESSAGE 8148 (MCNT_BMSEGT)

IOUTINi must be one of 0, 1, 2, 12, 13, 14, 23, 24 and 123 for generating beam segments

8148.6 *** USER WARNING MESSAGE 8148 (GP4)

COHESIVE CONTACT SUPPORTS SEGMENT-TO-SEGMENT ONLY, AND WILL BE
IGNORED WITH NODE-TO-SEGMENT CONTACT

8148.7 *** USER WARNING MESSAGE 8148 (MCNTPAR)

THE BCPARA,0,METHOD OPTION SEGSMALL HAS BEEN REPLACED WITH THE GENERAL
SEGTOSEG METHOD STARTING WITH VERSION 2017

8148.8 *** USER WARNING MESSAGE 8148 (MCNTPAR)

THE BCPARA,0,METHOD OPTION SEGLARGE HAS BEEN REPLACED WITH THE GENERAL
SEGTOSEG METHOD STARTING WITH VERSION 2017

8148.9 *** USER WARNING MESSAGE 8148 (MCNTPAR)

SEGANGL on BCPARA <= 90.0 or >=180.0 will be reset to 120.0(default).

8148.10 *** USER WARNING MESSAGE 8148 (MCNTPAR)

IBSEP is changed from 0(Force based Separation) to 2(Stress based Separation). Please evaluate input
FNTOL in terms of absolute stress.

8149.0 *** USER FATAL MESSAGE 8149 (N3DINT)

The Lagrange multiplier augmentation method must be set if segment-to-segment contact is used with a
non-zero interference distance.

User information: The Lagrange multiplier augmentation can be specified by the AUGMENT parameter
of BCPARA entry.

8150.0 *** USER FATAL MESSAGE 8150 (MCN1NRB2, MCN1NRBS)

%2 OPTIONS CANNOT BE USED TOGETHER IN %3 ID=%1.

User information: To make a rigid body, control points must be defined by one consistent option for one
rigid body.

8151.0 *** USER FATAL MESSAGE 8151 (MCN1NRB2, MCN1NRBS, MCN1BZIR)

Main Index
 958 MSC Nastran Error Messages
Errors 8000 - 8999

NUMBER OF %1 MUST BE THE SAME AS %2 IN %4 ID=%3.

User information:
1. The number of pairs of (Xi,Yi) must be the same as NPTU*NPTV for BCNURBS or NPTU for
BCNURB2.
2. The number of Gi must be the same as NPTU*NPTV for BCNURBS or NPTU for BCNURB2.
3. The number of Homoi must be the same as NPTU*NPTV for BCNURBS or NPTU for
BCNURB2.
4. The number of Knoti must be the same as (NPTU+NORU)*(NPTV+NORV) for BCNURBS or
NPTU+NORU for BCNURB2.
5. The number of Gi must be the same as NP1*NP2 for BCBZIER.

8152.0 *** USER WARNING MESSAGE 8152 (M3DCNT1B)

BOTH BCTABL1 AND BCONECT HAVE THE SAME ID=%1. BCTABL1 WILL BE USED
INSTEAD OF BCONECT.

User information: BCTABL1 and BCONECT can have the same ID. In this case, BCTABL1 will be used
instead of BCONECT.

8152.1 *** USER FATAL MESSAGE 8152 (M3DCNT1B)

BOTH BCTABL1 AND BCONECT HAVE THE SAME ID=0. IT IS NOT ALLOWED.

User information: Although BCTABL1 and BCONECT have the same ID, they cannot have ID=0
simultaneously.

User action: Please remove one of BCTABL1 and BCONECT with ID=0.

8153.0 *** USER FATAL MESSAGE 8153 (M3DCNT1B)

BCBODY1 DATA IS MISSING BUT IT IS REQUIRED FOR CONTACT.

User information: BCBODY1 must be used for contact body definition.

User action: Please check the contact bodies.

Main Index
 MSC Nastran Error Messages 959
Errors 8000 - 8999

8154.0 *** USER FATAL MESSAGE 8154 (MCN1AB2D, MCN1GCK, MCN1GTB)

ONLY ONE OF %1 OR %2 OPTIONS IS ALLOWED. PLEASE CHECK BCONECT ID=%3.

User information: IDSCND and "SECNDRY" options can be used together. It is the same for IDPRIM
and "PRIMARY" options.

8155.0 *** USER WARNING MESSAGE 8155 (MCN1GCK)

PERMANENT GLUE IS ACTIVATED: %1 OPTION WILL BE IGNORED.

User information: AUGDIST, HARDS, ISEARCH, PENALT, STKSLP, TAUGMNT and TPENALT
options in BCONPRG are not available in permanent glue contact.

8156.0 *** USER WARNING MESSAGE 8156 (MCN1GCK)

GENERAL CONTACT JOB, INCLUDING BOTH GLUE AND NON-GLUE OPTIONS, WILL BE
ACTIVATED INSTEAD OF PERMANENT GLUE.

User information: The model has both glue and non-glue contact definitions.
SOL101 and SOL400 support the mixed glued contact and the permanent glue contact changes to the
mixed glue contact.

8157.0 *** USER WARNING MESSAGE 8157 (MCN1PCH)

DIFFERENT PROPERTY TYPES HAVE THE SAME ID=%1. ALL PROPERTIES WITH ID=%1
WILL BE USED IN CONTACT.

User information: Nastran allows the same property id of the different element types.
For example, PSHELL,1 and PBEAM,1. When the property is set to 1 for contact body, both will be used
in the contact.

8157.1 *** USER WARNING MESSAGE 8157 (MCNT_BMSECT)

BEAM SEGMENT CONTACT ONLY ALLOWS A CONSTANT SECTION (PRISMATIC) ALONG
THE BEAM AXIS. THE VARYING CROSS SECTION OF %1 (ID %2) WILL BE AVERAGED.

Main Index
 960 MSC Nastran Error Messages
Errors 8000 - 8999

8158.0 *** USER WARNING MESSAGE 8158 (MCN1HET)

%1 OPTION IS ONLY AVAILABLE FOR HEAT OR COUPLED ANALYSIS. %1 OPTION WILL BE
IGNORED IN BCBODY1,BCSURF or BCGRID ID=%2.

User information: BNC, BNCE, BNL, BNLE, CFILM, EMISS, HBL, HCT, HCV, HNC, HNCE, HNL
and HNLE in BCBDPRP only available for heat or coupled analyses.

8158.1 *** USER WARNING MESSAGE 8158 (MCN1HET)

%1 OPTION IS ONLY AVAILABLE FOR RIGID BODY. %1 OPTION WILL BE IGNORED IN
BCBODY1,BCSURF or BCGRID ID=%2.

User information: Negative TSINK is only available for rigid bodies.

8158.2 *** USER WARNING MESSAGE 8158 (MCN1HET)

%1 OPTION IS ONLY AVAILABLE FOR DEFORMABLE BODY. %1 OPTION WILL BE
IGNORED IN BCBODY1,BCSURF or BCGRID ID=%2.

User information: Negative TSINK is only available for deformable bodies.

8158.3 *** USER WARNING MESSAGE 8158 (MCN1HET)

%1 IS ONLY AVAILABLE FOR PURE HEAT CONTACT. %1 WILL BE SET TO 1 IN
BCBODY1,BCSURF or BCGRID ID=%2.

8158.4 *** USER FATAL MESSAGE 8158 (MCN1AB2D)

%1 OPTION IS ONLY AVAILABLE FOR INTERFERENCE FIT CONTACT. %1 OPTION WILL
BE AVAILABLE ONLY WHEN %2.

8158.5 *** USER FATAL MESSAGE 8158 (MCN1AB2D)

%1 OPTION IS ONLY AVAILABLE FOR INITIAL GAP CONTACT. %1 OPTION WILL BE
AVAILABLE ONLY WHEN %2.

8159.0 *** USER FATAL MESSAGE 8159 (MCNTCHK)

Main Index
 MSC Nastran Error Messages 961
Errors 8000 - 8999

OLD CONTACT DEFINITIONS (BCTABLE AND BCBODY) AND NEW CONTACT DEFINI-
TIONS (BCTABL1, BCONECT, BCBODY1, BCSURF, and BCGRID) CANNOT BE USED
TOGETHER.

8160.0 *** SYSTEM FATAL MESSAGE 8160 (MCN1COLD)

NUMBER OF COLLECTED %1 (%2) EXCEEDS THE MAXIMUM NUMBER (%3).

8161.0 *** USER FATAL MESSAGE 8161 (MCN1COLD)

NO 1-D ELEMENT RADIUS IS SPECIFIED BY BCBMRAD. BCBMRAD ID=%1.

8161.1 *** USER WARNING MESSAGE 8163 (MCN1COLD)

The following grid points in BCBODY1 %1 are referenced as dependent in rigid elements.
This may result in wrong answers.

8161.2 *** USER WARNING MESSAGE 8163 (MCN1COLD)

The following grid points in BCBODY1 %1 are referenced as independent in rigid elements.
This may result in wrong answers.

8162.0 *** USER FATAL MESSAGE 8162 (MCN1INID)

INCONSISTENT BODY DIMENSION, DIM=%1D IS FOUND IN BCBODY1, BCSURF or
BCRIGD ID=%2.

User information: In the model, the contact body dimension must be consistent.

8162.1 *** USER FATAL MESSAGE 8162 (MCN1INID)

%1 ONLY SUPPORTS PERMANENT GLUE IN CONTACT

8163.0 *** USER FATAL MESSAGE 8163 (MCN1PARD)

MULTIPLE BCPARA ENTRIES WITH ID=%1 ARE FOUND. IT MUST BE UNIQUE.
THE CURRENT VERSION ONLY SUPPORTS BCPARA WITH ID=0 IN THE CONTACT
ANALYSIS. ANY BCPARA WITH ID>0 IS IGNORED IN THE CURRENT STAGE.

8164.0 *** USER WARNING MESSAGE 8164 (MCN1PARD)

%1 OPTION IN BCPARA HAS AN INVALID VALUE. IT WILL BE SET TO %2.

Main Index
 962 MSC Nastran Error Messages
Errors 8000 - 8999

8164.1 *** USER WARNING MESSAGE 8164 (MCN1PARD)

%1 OPTION IN BCPARA HAS BEEN REPLACED BY MORE GENERALIZED METHOD %2.

8164.2 *** USER WARNING MESSAGE 8164 (MCN1PARD)

%1 OPTION IN BCPARA HAS BEEN REPLACED BY MORE GENERALIZED METHOD %2.

8164.3 *** USER WARNING MESSAGE 8164 (MCN1PARD)

LINCNT IS TURNED OFF BECAUSE IT IS NOT COMPATIBLE WITH LARGE
DISPLACEMENT.

User action: CHANGE LINCNT TO -1 TO FORCE LINEAR CONTACT ANALYSIS WHEN

LGDISP > 0.

8164.4 *** USER INFORMATION MESSAGE 8164 (MCN1PARD)

SYSTEM(786)=1, SOL 101 TURNS ON LINEAR CONTACT (LINCNT=1 ON BCPARA).

8164.5 *** USER INFORMATION MESSAGE 8164 (MCN1PARD)

VERSION %1 defaults will be used in SEG-TO-SEG Contact.

8165.0 *** USER FATAL MESSAGE 8165 (MCN1DATD)

BCRIGID OPTION IS AVAILABLE ONLY WHEN BEHAV=RIGID IN %1 ID=%2.

8166.0 *** USER WARNING MESSAGE 8166 (MCN1AB2D)

PRIMARY BODY IS SET TO RIGID AND IT CANNOT BE FLIPPED WHEN ISEARCH IS SET TO
0 OR 2 IN BCBODY1 ID=%1.

8166.1 *** USER FATAL MESSAGE 8166 (MCN1AB2D)

COHESIVE CONTACT SUPPORTS SEGMENT-TO-SEGMENT ONLY.

User action: PLEASE CHANGE TO SEGTOSEG WITH METHOD IN BCPARA FOR COHESIVE
CONTACT ANALYSIS OR CHANGE FGCFLG TO 0 IN BCPARA OR BCONPRG TO
DEACTIVATE COHESIVE CONTACT ANALYSIS.

8166.2 *** USER WARNING MESSAGE 8166 (MCN1AB2D)

COHESIVE CONTACT IS USED FOR GLUED CONTACT ONLY, AND WILL BE IGNORED
FOR TOUCHING CONTACT

Main Index
 MSC Nastran Error Messages 963
Errors 8000 - 8999

8167.0 *** USER FATAL MESSAGE 8167 (N3DINT)

BCHANGE option NODE cannot be used in Segment-to-Segment contact.

User information: BCHANGE option NODE only works in Node-to-Segment contact; however,
BCHANGE option EXCLUDE works in both Node-to-Segment and Segment-to-Segment contact.

8168.0 *** USER FATAL MESSAGE 8168 (MCNTABL)

Segment-to-Segment contact analysis does not support Breaking Glue.

8169.0 *** USER WARNING MESSAGE 8169 (MCN1ING)

OPINGP IS SET TO 1 IN BCONECT WHICH IS REFERENCED BY BCTABLE,N(N>0) ENTRY,
BUT NOT BY BCTABLE,0 ENTRY FOR INITIAL CONTACT. TO ACTIVATE CONTACT
CLEARANCE OPTION, BCONPRG ENTRY WITH THE PARAMETER OPINGP MUST APPEAR
IN THE LIST OF CONTACT PAIRS (BCONECT) REFERENCED BY BCTABL1,0 ENTRY, OTH-
ERWISE THE CLEARANCE OPTION IS IGNORED.

User action: ENSURE THE BCONECT ENTRIES, REFERENCING BCONPRG ENTRIES WITH
OPINGP=1, APPEAR ON THE BCTABL1,0 ENTRY

8169.1 *** USER WARNING MESSAGE 8169 (MCN1ING)

OPINGP IS SET TO 1 IN BCONECT WHICH IS REFERENCED BY BCTABLE,N(N>0) ENTRY,
BUT BCTABLE,0 ENTRY FOR INITIAL CONTACT IS NOT DEFINED. TO ACTIVATE
CONTACT CLEARANCE OPTION, BCONPRG ENTRY WITH THE PARAMETER OPINGP
MUST APPEAR IN THE LIST OF CONTACT PAIRS (BCONECT) REFERENCED BY BCTABL1,0
ENTRY, OTHERWISE THE CLEARANCE OPTION IS IGNORED.

User action: ENSURE THE BCONECT ENTRIES, REFERENCING BCONPRG ENTRIES WITH
OPINGP=1, APPEAR ON THE BCTABL1,0 ENTRY

8521.0 *** USER FATAL MESSAGE 8521 (GP3CE)

SURF LOAD SET %1 APPLIES A SURFACE EXCITATION ON PLANAR ELEMENT %2.

User action: SURF EXCITATIONS ONLY ACT ON SOLID ELEMENTS. MODIFY EXCITATION
TYPE OR ELEMENT ID.

Main Index
 964 MSC Nastran Error Messages
Errors 8000 - 8999

8522.0 *** USER FATAL MESSAGE 8522 (GP3CE)

EDGE LOAD SET %1 APPLIES AN EDGE EXCITATION ON SOLID ELEMENT %2.

User action: EDGE EXCITATIONS ONLY ACT ON PLANAR ELEMENTS. MODIFY EXCI-
TATION TYPE OR ELEMENT ID.

8523.0 *** USER FATAL MESSAGE 8523 (GP3CE)

EDGE LOAD SET %1 WITH AN EDGE CONNECTING GRIDS %2 AND %3 IS INCORRECT
FOR ELEMENT %4.

User action: CHECK DIAGONAL GRIDS ON FACE EXCITED.

8524.0 *** USER FATAL MESSAGE 8524 (GP3CE)

SURF LOAD SET = %1 WITH DIAGONAL CONNECTING GRIDS %2 AND %3 IS INCORRECT
FOR ELEMENT %4.

User action: CHECK DIAGONAL GRIDS ON FACE EXCITED.

8525.0 *** USER FATAL MESSAGE 8525 (GP3CE)

IN SURF LOAD SET %1 PENTA ELEMENT %2 DOES NOT CONTAIN GRID %3
AS A CORNER NODE FOR EITHER TRIANGULAR FACE.

User action: CHECK CORNER GRIDS ON FACE EXCITED.

8526.0 *** USER FATAL MESSAGE 8526 (GP3CE)

IN SURF LOAD SET %1 TETRA ELEMENT %2 DOES NOT CONTAIN GRID %3 AS A CORNER
NODE FOR ANY TRIANGULAR FACE.

User action: CHECK CORNER GRIDS ON FACE EXCITED.

8527.0 *** USER FATAL MESSAGE 8527 (GP3CE)

Main Index
 MSC Nastran Error Messages 965
Errors 8000 - 8999

SURF LOAD SET %1 REFERENCES ELEMENT %2

WHICH WAS NOT FOUND AMONG THE ACCEPTABLE TETRA, HEXA, OR PENTA SOLID
ELEMENTS IN THE PROBLEM.

User action: CHECK THAT SURF LOADS ARE ON SOLID ELEMENT FACES.

8536.0 *** USER FATAL MESSAGE 8536 (IFS9P)

MULTIPLE AUNITS ENTRIES FOUND.

User action: SPECIFY ONLY ONE AUNITS ENTRY.

8539.0 *** USER FATAL MESSAGE 8539 (GP3CE)

EDGE LOAD SET %1 REFERENCES ELEMENT %2
WHICH WAS NOT FOUND AMONG THE ACCEPTABLE QUAD(X) OR TRIA(X) ELEMENTS
IN THE PROBLEM.

User action: CHECK THAT EDGE LOADS ARE ON TWO-D ELEMENT EDGES.

8542.0 *** USER FATAL MESSAGE 8542 (PREMAT)

MATEMA ENTRY MAY NOT REFERENCE MATNL, I.E. ANISOTROPIC MATERIALS ARE NOT
SUPPORTED IN NONLINEAR ANALYSIS.

User action: REPLACE MATEMA BY APPROPRIATE MATEM ENTRY.

8548.0 *** USER FATAL MESSAGE 8548 (GRDERR)

%1%2 CONNECTS TWO GRID POINTS HAVING THE SAME COORDINATES. THE GRID
IDS ARE %3 AND %4.

User action: MODIFY THE GRIDS SO THEY ARE NOT COINCIDENT.

8590.0 *** USER/SYSTEM FATAL/WARNING/INFORMATION MESSAGE 8590 (EVLMSG)

SYSTEM(21) MUST EQUAL 10 FOR MSC.EMAS AND NOT 10 FOR MSC NASTRAN.

User action: CORRECT THE SYSTEM(21) SELECTION ON THE %1 STATEMENT.

Main Index
 966 MSC Nastran Error Messages
Errors 8000 - 8999

8591.0 *** USER FATAL MESSAGE 8591 (XCSA)

APP MAGN IS ONLY ALLOWED IN MSC.EMAS AND NOT ALLOWED IN MSC NASTRAN.

User action: CORRECT THE APP STATEMENT SELECTION IN EXECUTIVE CONTROL.

8592.0 *** USER WARNING MESSAGE 8592, (REIG).

THE METHOD RECORD IN CASE CONTROL IS MISSING OR INCORRECT. THIS WILL
CAUSE THE FOLLOWING FATAL ERRORS.

User action: PUT A METHOD ENTRY IN CASE CONTROL WHICH POINTS TO AN EIGR,
EIGRL, OR EIGB RECORD IN BULK DATA.

8593.0 *** USER FATAL MESSAGE 8593 (PREMAT)

RESIDUAL MAGNETIZATION HAS BEEN SPECIFIED FOR MATNL ENTRY %1.

User information: RESIDUAL MAGNETIZATION IS NOT CURRENTLY SUPPORTED ON THE

MATNL ENTRY.

8594.0 *** USER FATAL MESSAGE 8594 (PREMAT)

ELECTROMAGNETIC MATERIAL ENTRY (MATEM %1) IS REFERENCED BY A MATS1
ENTRY.

User information: STRUCTURAL AND ELECTROMAGNETIC MATERIAL ENTRY IDS MUST BE

UNIQUE IF THE MATERIAL IS NONLINEAR.

8595.0 *** USER FATAL MESSAGE 8595 (PREMAT)

STRUCTURAL MATERIAL ENTRY (MATI %1) IS REFERENCED BY A MATNL ENTRY.

User information: STRUCTURAL AND ELECTROMAGNETIC MATERIAL ENTRY IDS MUST BE

UNIQUE IF THE MATERIAL IS NONLINEAR.

8596.0 *** USER WARNING MESSAGE 8596 (TA1A)

Main Index
 MSC Nastran Error Messages 967
Errors 8000 - 8999

OPEN BOUNDARY ELEMENTS REFERENCE A PEM WHERE A PEMOB WAS EXPECTED. A

PEMOB WITH OBID 1 WILL BE ASSUMED.

User action: TO PREVENT THIS WARNING MESSAGE REPLACE THE PEM ENTRY WITH A
PROPER PEMOB ENTRY FOR ALL OPEN BOUNDARY ELEMENTS.

8616.0 *** USER FATAL MESSAGE 8616 (GP3CE)

LOAD SET %1 APPLIES AN MSURF LOAD TO ELEMENTS %2 AND %3 ON A FACE THAT IS
NOT COMMON TO BOTH.

User action: ENSURE THAT BOTH ELEMENTS HAVE A COMMON FACE.

8621.0 *** USER WARNING MESSAGE 8621 (MODGM2)

ELEMENT %1 REFERS TO A PEM PROPERTY ENTRY IN A NON-EMAS ANALYSIS.
SECURITY AUTHORIZATION IS INSUFFICIENT TO ALLOW ELECTROMAGNETIC PROP-
ERTIES TO BE CONSIDERED FOR THIS ANALYSIS. THE PEM ENTRY WILL BE IGNORED.

User action: SPECIFY ONLY APPROPRIATE PROPERTY ENTRIES.

IF A COUPLED SOLUTION IS DESIRED CONTACT HEXAGON AB CLIENT SUPPORT TO
OBTAIN A VALID AUTHORIZATION CODE.

8622.0 *** USER WARNING MESSAGE 8622 (MODGM2)

SOLID ELEMENT %1 REFERS TO A NON-STRUCTURAL PSOLID PROPERTY ENTRY IN AN
EMAS ANALYSIS. THE PSOLID ENTRY WILL BE IGNORED.

User action: SPECIFY ONLY APPROPRIATE PROPERTY ENTRIES.

8623.0 *** USER WARNING MESSAGE 8623 (MODGM2)

Main Index
 968 MSC Nastran Error Messages
Errors 8000 - 8999

ELEMENT %1 REFERS TO A STRUCTURAL OR THERMAL PROPERTY ENTRY IN AN EMAS

ANALYSIS. SECURITY AUTHORIZATION IS INSUFFICIENT TO ALLOW STRUCTURAL OR
THERMAL PROPERTIES TO BE CONSIDERED FOR THIS ANALYSIS. THE STRUCTURAL OR
THERMAL PROPERTY ENTRY WILL BE IGNORED.

User action: SPECIFY ONLY APPROPRIATE PROPERTY ENTRIES. IF A COUPLED SOLUTION

IS DESIRED CONTACT HEXAGON AB CLIENT SUPPORT TO OBTAIN A VALID
AUTHORIZATION CODE.

8657.1 *** SYSTEM FATAL MESSAGE 8657 (PTEMAD)

NONZERO DATA OUTSIDE MATRIX BOUNDARY.

User action: CONTACT MSC CLIENT SUPPORT. PROGRAMMER INFORMATION: CHECK

PORT MATRIX ASSEMBLY ROUTINES.

8692.0 *** USER FATAL MESSAGE 8692 (ULANCZ):

MORE THAN ONE CONTINUATION CARD WAS SPECIFIED.

8693.0 *** USER INFORMATION MESSAGE 8693 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, %1 ROOTS WERE FOUND
BELOW THE LOWER BOUND OF %2 OF THE RANGE SPECIFIED.

User action: CHECK EIGUL CARD OR PARAMETER RMIN.

8694.0 *** USER INFORMATION MESSAGE 8694 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, FEWER ROOTS THAN
REQUIRED HAVE BEEN FOUND AFTER %1 SHIFTS.

8695.0 *** USER INFORMATION MESSAGE 8695 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, %1 ROOTS WERE FOUND
ABOVE THE UPPER BOUND OF %2 OF THE RANGE SPECIFIED.

User action: CHECK EIGUL CARD OR PARAMETER RMAX.

8696.0 *** USER INFORMATION MESSAGE 8696 (ULANCZ):

Main Index
 MSC Nastran Error Messages 969
Errors 8000 - 8999

DURING REAL UNSYMMETRIC LANCZOS EIGENVALUE EXTRACTION %1 COMPLEX

EIGENVALUES WERE FOUND.

8766.0 *** USER WARNING MESSAGE 8766 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, SHIFT %1 OF %2 WAS
SKIPPED, BECAUSE IT WAS CLOSELY BOUNDED BY TWO ROOTS.

8767.0 *** USER WARNING MESSAGE 8767 (ULANCZ):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, SHIFT %1 OF %2 WAS
DETERMINED TO BE VERY CLOSE TO A ROOT DURING SHIFT %3 OF %4.

8768.0 *** USER WARNING MESSAGE 8768 (ULANDD):

DURING REAL UNSYMMETRIC EIGENVALUE EXTRACTION, SHIFT %1 OF %2 WAS WAS
SKIPPED, BECAUSE IT WAS TOO CLOSE TO %3 OUT OF %4 ROOTS AT THIS SHIFT POINT.

8770.0 *** SYSTEM FATAL MESSAGE 8770 (ULANVD):

DURING REAL UNSYMMETRIC LANCZOS EIGENVECTOR EXTRACTION, A NULL VECTOR
WAS GENERATED. ERROR IN VECTOR EXTRACTION, EIGENPAIR # %1

8772.0 *** USER warning message (SNPDF)

FOR THE DOUBLET LATTICE AERODYNAMICS, THE COLLOCATION POINT FALLS ON
OR NEAR THE BOUND VORTEX

8772.1 *** USER warning message (SNPDF)

FOR THE DOUBLET LATTICE AERODYNAMICS, THE COLLOCATION POINT FALLS ON
OR NEAR THE TRAILING VORTEX

User information: THIS IS MOST LIKELY A MODELLING ERROR WHERE THE MIDDLE OF
ONE AERODYNAMIC BOX IS ALIGNED EXACTLY OR VERY CLOSELY WITH THE EDGE OF
ANOTHER BOX

8775.0
A SHAPE OPTIMIZATION TASK IS BEING PERFORMED WITH CONNECTOR ELEMENTS.
BECAUSE THE PROJECTION OF THESE ELEMENTS IS NOT BEING UPDATED, RESULTS
FROM THE REDESIGN MAY NOT BE ACCURATE.

Main Index
 970 MSC Nastran Error Messages
Errors 8000 - 8999

8775.1 *** USER WARNING MESSAGE (dopri1)

THE DESIGN OF PROPERTIES ON CONNECTOR ELEMENTS (PWELD AND/OR PFAST)
IGNORES THE CHANGE IN THE PROJECTION OF THESE ELEMENTS ONTO THE UNDER-
LYING STRUCTURE. CONSEQUENTLY, THE PROPERTIES ACHIEVED BY THE REDESIGN
TASK MAY NOT SHOW THE SAME BEHAVIOR WHEN A REANALYSIS IS PERFORMED
WITH THE OPTIMIZED PROPERTY VALUES.

8776.1
LOGIC ERROR - HIGH BPOOL QUEUE IS FILLED
QUEUE IS DROPPING %1 %2 WHEN BUFFER IS MOVED

User action: CONTACT Hexagon

8776.2
LOGIC ERROR - HIGH BPOOL QUEUE IS FILLED
QUEUE IS DROPPING %1 %2 WHEN FILLED FROM HIST

User action: CONTACT Hexagon

8776.3
LOGIC ERROR - LOW BPOOL QUEUE IS FILLED
QUEUE IS DROPPING %1 %2

User action: CONTACT Hexagon

8776.4
COUNTED QUEUE SIZE %1
EXPECTED QUEUE SIZE %2
User action: CONTACT Hexagon

8776.5
LOGIC ERROR - UNABLE TO FIND AND/OR DELETE BPOOL BUFFER
BUFFER %1 %2

User action: CONTACT Hexagon

Main Index
 MSC Nastran Error Messages 971
Errors 8000 - 8999

8776.6
LOGIC ERROR - CANNOT RECLAIM BUFFER FROM LOW QUEUE
QUEUE SIZE %1

User action: CONTACT Hexagon

8776.7
LOGIC ERROR - UNABLE TO FIND A INACTIVE BPOOL BUFFER TO RECLAIM IN QUEUE
%1

User action: BPOOL SIZE OR HIGHQUE MAY BE SET INCORRECTLY. EACH QUEUE (HIGH
& LOW) SHOULD BE SET LARGE ENOUGH TO CONTAIN ALL THE ACTIVE BUFFERS.
EITHER INCREASE BPOOL OR REDISTRIBUTE THE BUFFERS USING HIGHQUE.
PROGRAMMERS ACTION: CHECK IF ACTIVE FLAG IS BEING TURNED OFF

8776.8
LOGIC ERROR - UNABLE TO FIND A FREE CHAIN LOCATION
FOR KEY %1 %2 FREE CHAIN SIZE %3

User action: CONTACT Hexagon

8776.9
LOGIC ERROR - DUPLICATE KEY FOUND
FOR KEY %1 %2

User action: CONTACT Hexagon

8776.10
HISTQUE SIZE IS LIMITED TO %1 PERCENT OF BPOOL.
RECOMMENDED SETTING IS 50 PERCENT.
RESETTING HISTQUE SIZE TO MAXIMUM.

8776.11

Main Index
 972 MSC Nastran Error Messages
Errors 8000 - 8999

A buffer pool error has occurred.

User information: This error may occur when the bpool is small relative to the matrix size.

Avoidance: Increase bpool or insert NASTRAN SYSTEM(119)=3 at the top of your input file.

8801.0 *** USER WARNING MESSAGE 22999 (ST2DYN)

TLOAD1 set ID %1 refers to TEMPD set ID %2. Large displacement effects are activated (LGDISP > 0)
and transient temperature loads are applied using TLOAD1 + TEMPD. These loads will be IGNORED.
To apply transient temperature loads when LGDISP > 0, employ TEMP(LOAD) + TTEMP/TMPSET.

8801.1 *** USER WARNING MESSAGE 22999 (ST2DYN)

TLOAD1 set ID %1 refers to TEMP set ID %2. Large displacement effects are activated (LGDISP > 0)
and transient temperature loads are applied using TLOAD1 + TEMP. These loads will be IGNORED. To
apply transient temperature loads when LGDISP > 0, employ TEMP(LOAD) + TTEMP/TMPSET.

8801.2 *** USER WARNING MESSAGE 22999 (ST2DYN)

TLOAD1 set ID %1 refers to TEMPD set ID %2. Large displacement effects are activated (LGDISP > 0)
and transient temperature loads are applied using TLOAD1 + TEMPD. Only SOL 400 supports transient
temperature loads when LGDISP > 0, employing TEMP(LOAD) + TTEMP/TMPSET.

8801.3 *** USER WARNING MESSAGE 22999 (ST2DYN)

TLOAD1 set ID %1 refers to TEMP set ID %2. Large displacement effects are activated (LGDISP > 0)
and transient temperature loads are applied using TLOAD1 + TEMPD. Only SOL 400 supports transient
temperature loads when LGDISP > 0, employing TEMP(LOAD) + TTEMP/TMPSET.

8802.0 *** USER INFORMATION MESSAGE 8802 (ST2DN3)

NLSTEP entry has been converted to equivalent NLPARM entry for SOL 101 linear contact analysis.

8802.1 *** USER WARNING MESSAGE 8802 (ST2DN3)

NLSTEP entry should have 'LCNT' entry for SOL 101 linear contact analysis.

8900.0 *** USER INFORMATION MESSAGE 8900 (MDENZO)

K4 STRUCTURAL DAMPING MATRIX HAS BEEN MODIFIED FOR PERFORMANCE SET
PARAM,MDK4OPT,0 TO DISABLE THIS FEATURE

Main Index
 MSC Nastran Error Messages 973
Errors 8000 - 8999

8951.0
The file name of OP2 is too long. The length file name is %1. Maximum allowed %2.

8951.1
OP2 file %1, has an unknown status filtyp= %2, istat= %3.
8951.2 Redundant TRMCPL entries are found for trim component ID %1.

8951.3
The required ACPEMCP or ACPMCP1 entry for trim component %1 is missing.

8951.4
TRMCPL CTYPE %1 references ACPEMCP entry where the SET ID is not given for trim component ID
%2 RID=%3.

8951.6
There is no SET1 or SET3 for trim component %1. SET1 or SET3 must be specified on ACPEMCP.

8951.7
SET3 %1 referenced by ACPEMCP %2 RID=%3 has an invalid DES. SET3 entry must have
DES=GRID.

8951.8
There is no FREQi given for trim component %1.
Master frequencies must be specified by FREQi with ID same as trim component ID.

8951.9
Input datablock %1 is missing.

8951.10
OP2 file, %1, failed to open.

8951.11
SET1 or SET3 %1 referenced by ACPEMCP, does not exist.

8951.12

Main Index
 974 MSC Nastran Error Messages
Errors 8000 - 8999

Input datablock %1 is missing.

User action: move corresponding SET1/SET3 entries after BEGIN BULK TRMC.

8951.13
Required input FREQx entry with ID = %1 is missing.

User action: provide FREQx with ID = %1 under BEGIN TRMC=%1.

8951.14
Input datablock %1, GINO unit %2 is missing in module %3
Module terminated without completing. This may cause problems downstream.

8951.15
PLTSURF %1 referenced GID not on the surface of trim component.

8951.16
PLTSURF %1 referenced mid-side GIDs inconsistent with sides of 3D elements.

8951.17
SET3 %1 referenced by ACPEMCP/ACPMCP1 %2 RID=%3 has an invalid DES. SET3 entry must have
DES=ELEM or GRID.

8951.18
Multiple entries of ACPEMCP/ACPMCP1 %1 with same RID==%2 found.

8951.19
Non-default input found for OOC/SPM field on ACPEMCP/ACPMCP1 %1 with RID %2.

8951.20
SET ID for SGLUED/SSLIDE/SOPEN/SIMPER and SCxx fields must be unique across all ACPEMCP/
ACPMCP1 %1.

8951.21
ACPEMCP or ACPMCP1 %1 with RID field equal to 0 (or blank) is missing.

8951.22

Main Index
 MSC Nastran Error Messages 975
Errors 8000 - 8999

MATPE1 %1 with POROPT field equal to LUMPED must provide density of solid phase via SRHO field
of MATPE1 or RHO of MAT1 entry selected by MAT1 field of MATPE1.

8951.23
MATPE1 %1 with POROPT field equal to RIGID/MIKI/DELANY must have MAT1 field blank.

8951.24
Both ACPEMCP and ACPMCP1 are found for trim %1. Only one of them is allowed in a trim.
8951.25
ACPMCP1 does not reference any TCOMPG entry for trim %1.

8951.26
There is no SET3 for trim component %1. SET3 must be referenced by ACPMCP1.

8951.27
PARAM,TRMBIM,PHYSICAL does not support ACPMCP1 of 1D trim for trim component %1.
Please use PARAM,TRMBIM,MODAL instead.

8951.28
SET3 %1, referenced by ACPMCP1, does not exist.

8951.29
SET3 %1 referenced by ACPMCP1 %2 has an invalid DES. SET3 entry must have DES=ELEM.

8951.30
Trim component %1 has a missing material entry, MID= %2, which is referenced by TCOMPG entry
with SET3ID= %3.

8951.31
SET1 entry %1 is referenced by ACPMCP1 %2, which must reference a SET3 entry with DES=ELEM.

8951.32
There is no PLTSURF found in trim component %1. For 1D trim, PLTSURF must be used to define the
bottom and top surface meshes.

Main Index
 976 MSC Nastran Error Messages
Errors 8000 - 8999

8951.33
For 1D analytical trim, TRMCPL entry with CTYPE=TRMSUF or INTERF is missing for trim %1. Both
CTYPE=TRMSUF and INTERF are required.

8951.34
In 1D analytical trim %1, %2 elements are found. These elements will be ignored.

8951.35
Trim component, %1, is identified as a 1D analytical trim.

8951.36
TCOMPG entry is found in trim component, %1, without any ACPMCP1 entry to reference it.
8951.37
PSOLID entry with PID= %1 and MID= %2 in trim component %3 does not have any referenced
material entry, such as MATPE1, MAT1 or MAT10 in TRMC.

8951.38
In trim component, %1, PSOLID entry of PID= %2 and MID= %3 defines a solid-shell property with
FCTN='PSLDSHL', which references a %4 entry.

User information: PSOLID with FCTN='PSLDSHL' must reference a MAT1 entry.

8951.39
PSOLID entry with PID= %1 and MID= %2 in trim component %3 references a MATPE1 poroelastic
material entry, but its FCTN field is not selected as 'PORO'.

8952.0
TRMC processing failed. RETURN CODE %1.

8952.1
PHYSICAL FILE DOES NOT EXIST OR IDENTICAL FORTRAN UNITS ARE USED IN F70 and/
or OP4 file.
Fortran unit for F70 is %1.
Fortran unit for OP4 is %2.

Main Index
 MSC Nastran Error Messages 977
Errors 8000 - 8999

8952.2
Invalid DMIG format data from F70 file.
8952.3
TRIM COMPONENT OUT OF SYNC. EXPECT TRIM ID %1. TRIM ID ON FILE %2.

8952.4
DATA CHECK FOR TRIM COMPONENT(S) COMPLETED. PEM JOB WILL BE STOPPED.
PLEASE REVIEW DIAGNOSTIC OUTPUT. MAKE CORRECTION IF NEEDED. THEN,
RESUBMIT WITH PARAM,TRMBIM,PHYSICAL OR PARAM,TRMBIM,MODAL.
8953.0
TRIM BIM HAS THE TERMS NOT ON WETTED AREA DEFINED IN NASTRAN. THE TERMS
RELATED TO THE NEXT DOF LIST WILL BE ELIMINATED.

8953.1
ID %2 is duplicated on both PSHELL and PSHLPF in TRIM COMPONENT %1.

8953.2
REQUIRED INPUT ACPEMCP or ACPMCP1 bulk data entry is MISSING in EDTS. Please check
input data.

8953.3
Both ACPEMCP and ACPMCP1 bulk data entries reference same trim component %1.
A trim component can be modeled either as a 3D trim with ACPEMCP, or a 1D trim with ACPMCP1.
It cannot be modeled as both.

8953.4
For trim component,%1, Module TRMUTIL has a wrong input parameter, OPTION, %2.

8954.0
%1 entry %2 referenced by MATPE1 %3 does not exist.

8954.1
MAT1 entry referenced by frequency-dependent MATF1 %1 is missing.

8954.2
Invalid file logical name: %1.

Main Index
 978 MSC Nastran Error Messages
Errors 8000 - 8999

8954.3
Cannot find an unused Fortran unit number. Fortron I/O error.

8954.4
File %1 does not exist.

8954.5
Invalid file format was requested, form = %1.
The format should be either FORMATTED or UNFORMATTED.

8954.6 *** USER FATAL MESSAGE 8954.6 (SEMFREQ)

SOL 111 restarts with PARAM,ACMPF,UNIT, do not support PEM and/or frequency dependent
materials.

8954.7 *** USER FATAL MESSAGE 8954.7 (MFREQRS)

OP4 unit on PARAM,ACMPF does not exist or duplicate FORTRAN units are used with ACMPF.

User action: Confirm FORTRAN unit number on both PARAM,ACMPF and ASSIGN statement.

8954.8 *** USER FATAL MESSAGE 8954.8 (MFREQRS)

Number of modes are not equal in Nastran sol103 analysis and Actran analysis.
Current Nastran run has %1 modes and modal particiaption matrix from Actran has %2 modes.

User action: Extract the equal number of modes in Sol103 run and Actran run.

8955.0 *** USER FATAL MESSAGE 8955 (XSEMIN)

SOL 700, Version=Original is no longer supported. Please remove Version=Original.

8955.1 *** USER FATAL MESSAGE 8955 (XSEMIN)

THE DYTRAN DIRECTORY DOES NOT EXIST.
THE PROPER DYTRAN DIRECTORY LOCATION IS: %1/%2/dytran

8956.0

Main Index
 MSC Nastran Error Messages 979
Errors 8000 - 8999

There are upper triangular terms in matrix %1 and this is not allowed if the fourth parameter (REFLECT)
on the INPUTT4 module call is set to a nonzero value.

User action: If the matrix is not lower triangular then leave the 4th parameter blank or set to 0.
If the matrix is expected to be lower triangular then review how the matrix was written to the op4 file.

8999.0 *** SYSTEM FATAL MESSAGE 8999 (DMLOCW):

BASE ARRAY IS NOT AT OPEN CORE IZ(1).
OPEN CORE IZ(1) IS AT %1
BASE ARRAY IS AT %2

Main Index
 980 MSC Nastran Error Messages
Errors 8000 - 8999

Main Index
 MSC Nastran Error Messages 981
Errors 9000 - 9999

Errors 9000 - 9999

9000.0
NPROC REDUCED TO %1

9000.1
THE SOLUTION IS A RESTART RUN AND RSTRT=%1

9001.0
GENERALIZED DYNAMIC REDUCTION HAS BEEN REQUESTED IN THE PRESENCE OF
SUPPORTED (SEE %1 ENTRY) DEGREES OF FREEDOM. IN SOME CASES SOME FLEXIBLE
MODES MAY BE DISCARDED OR THOSE IN HIGH FREQUENCY CLUSTERS MAY BE
SKIPPED.

9002.0
ERROR ENCOUNTERED IN THE CASE CONTROL SECTION
SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE IFP1.

9002.1
ERROR ENCOUNTERED IN THE CASE CONTROL SECTION FOR AUXILIARY MODEL
NUMBER %1
SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE IFP1.

9002.2
ERROR(S) ENCOUNTERED IN THE %1 BULK DATA SECTION
SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE %2

9002.3
ERROR(S) ENCOUNTERED IN THE %1 BULK DATA SECTION FOR AUXILIARY MODEL
NUMBER %2
SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE %3

9002.4
ERROR(S) ENCOUNTERED IN THE %1 BULK DATA SECTION FOR SUPERELEMENT OR
MODULE %2
SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE %3
9002.5

Main Index
 982 MSC Nastran Error Messages
Errors 9000 - 9999

ERROR(S) ENCOUNTERED IN THE NASTRAN STATEMENT SECTION OR NASTRAN COM-

MAND
THE VALUE SPECIFIED FOR NASTRAN SYSTEM CELL 695(RDBOTH) IS %1

User information: USE NONNEGATIVE VALUE, BIT3 AND BIT4 CANNOT BOTH BE 1.

9002.6
ERROR(S) ENCOUNTERED IN THE NASTRAN STATEMENT SECTION OR NASTRAN COM-
MAND
THE VALUE SPECIFIED FOR NASTRAN SYSTEM CELL 695(RDBOTH) IS %1
RDBOTH=4(BIT3=1) OR RDBOTH=8(BIT4=1) CAN NOT BE SPECIFIED IN SOL 200/400.

User action: TO INCLUDE EFFECT OF STRESS STIFFENING, ADD A LINEAR/NONLINEAR

STATIC STEP VIA RFORCE.

9003.0
CURRENT VALUE OF STIME IS %1

9004.0
FOR THIS ITERATION, THE DIFFERENTIAL STIFFNESS WILL BE IGNORED TO AVOID
DECOMPOSITION OF A NON-POSITIVE DEFINITE STIFFNESS MATRIX.

User information: THIS MAY BE AN INDICATION OF A BUCKLING CONDITION

9005.0
THE SOLUTION FOR LOOPID= %1 IS SAVED FOR RESTART

9005.1
THE SOLUTION FOR THE LAST CONVERGED LOOPID= %1 IS SAVED FOR RESTART

9006.0
GRID POINT 1% ON PARAM, GRDPNT IS KNOWN TO THE CURRENT SUPERELEMENT OR
MODULE. THIS IS NOT ALLOWED IN INERTIA RELIEF.

9007.0
IMAGE SUPERELEMENTS MAY NOT HAVE ANY INTERIOR MASS OR STATIC LOADS IN
INERTIA RELIEF ANALYSIS.

Main Index
 MSC Nastran Error Messages 983
Errors 9000 - 9999

9008.0
A SUPORT BULK DATA ENTRY IS PRESENT.

User information: THIS ENTRY IS NOT ALLOWED IN NONLINEAR ANALYSIS.

9008.1
A SUPORT BULK DATA ENTRY IS PRESENT.

User information: THIS ENTRY IS NOT ALLOWED IN LINEAR CONTACT ANALYSIS.

9009.0
The boundary condition specifications in Case Control (SPC, MPC, SUPORT) are not contiguous across
SUBCASEs.
The SUBCASEs will be internally reordered to optimize efficiency but results will still be output in the
original SUBCASE order.

9010.0
LAST ADJUSTED DELTA T: OLDDT= %1 AT TSTEP= %2

9011.0
DYNAMIC, BUCKLING, AND/OR STATIC AERO OPTIMIZATION IS BEING REQUESTED
WITH P-ELEMENTS.

User information: ONLY STATIC AND/OR NORMAL MODES OPTIMIZATION MAY BE

REQUESTED WITH P-ELEMENTS.
HOWEVER, P-ELEMENTS CAN BE USED IN ALL ANALYSIS TYPES WITHOUT OPTIMIZA-
TION. (ANALYSIS ONLY)

9012.0
THE DISPLACEMENTS IN DOWNSTREAM SUPERELEMENT %1 DO NOT EXIST.

9013.0

Main Index
 984 MSC Nastran Error Messages
Errors 9000 - 9999

NO SEQSETI BULK DATA ENTRIES HAVE BEEN SPECIFIED FOR THIS SUPERELEMENT
EVEN THOUGH A METHOD COMMAND APPEARS IN ITS SUBCASE.
THE METHOD COMMAND IS IGNORED AND ONLY A STATIC CONDENSATION OF THE
MASS IS CONSIDERED.

9014.0
DUPLICATE ELEMENT IDS HAVE BEEN DETECTED. THIS IS NOT ALLOWED IN DESIGN
SENSITIVITY ANALYSIS.

User action: RENUMBER DUPLICATE ELEMENT IDS.

9015.0
THE %1 TABLE IS NOT PRESENT.

9015.1
THE %1 TABLE IS NOT PRESENT FOR:
ANALYSIS = %2
MPC = %3
SPC = %4
SUPORT = %5
AUXMID = %6

9015.2
THE %1 TABLE IS NOT PRESENT FOR:
MPC = %2
SPC = %3
SUPORT = %4

9016.0
%1 %2 %3 NOT FOUND IN DATABASE. PURGED STATUS ASSUMED.

9017.0
%1 %2 %3 (TRAILER = %4 %5 %6 %7 %8 %9 %10) HAS BEEN FETCHED FROM THE DATA-
BASE

9018.0
THE FOLLOWING DATA BLOCKS HAVE BEEN DELETED FROM THE DATA BASE

Main Index
 MSC Nastran Error Messages 985
Errors 9000 - 9999

9019.0
DBMGR //%1///%2 IS NOT SUPPORTED. OPERATION IS IGNORED.

9019.1
DBMGR //%1 IS NOT SUPPORTED. OPERATION IS IGNORED.

9020.0
PROCESSING PROJECT %1 VERSION %2

9021.0
DATA BLOCK %1 %2 %3 (TRAILER = %4 %5 %6 %7 %8 %9 %10) HAS BEEN STORED IN
DBSET %11

9021.1
FOLLOWING DATA BLOCKS HAVE BEEN DELETED FROM THE DATA BASE %1 %2 %3

9021.2
DATA BLOCK %1 %2 %3 (TRAILER = %4 %5 %6 %7) HAS BEEN STORED IN DBSET %8

9022.0
UPSTREAM SUPERELEMENT %1 DETECTED AND WILL BE PROCESSD AS FREQUENCY
INDEPENDENT.

User information: IF THERE ARE FREQUENCY-DEPENDENT ELEMENTS IN SUPERELEMENT

%1, THEY WILL USE THE NOMINAL STIFFNESS AND THE FREQUENCY-DEPENDENCE
WILL BE IGNORED.

9023.0
MAXIMUM LOAD EPSILON FROM RITZ SOLUTION IS %1

9024.0
STIFFNESS, MASS, DAMPING, AND LOAD GENERATION INITIATED.

9024.1

Main Index
 986 MSC Nastran Error Messages
Errors 9000 - 9999

STIFFNESS, MASS, DAMPING, AND LOAD GENERATION INITIATED. DESIGN CYCLE

NUMBER= %1

9025.0
THERE ARE NO STATIC SUBCASES FOR PRELOAD.

User action: REMOVE THE CMETHOD, TSTEP, AND FREQUENCY COMMAND FROM THE
STATIC SUBCASES.

9025.1
THERE IS NO STATIC SUBCASE FOR BUCKLING ANALYSIS.

User action: ADD STATIC SUBCASE(S).

9026.0
NO CASE CONTROL WAS FOUND AND THE QUALIFIERS CANNOT BE SET PROPERLY.
THIS PROJECT AND VERSION WILL BE SKIPPED.

9027.0
THE BULK DATA WAS NOT FOUND. THIS PROJECT AND VERSION WILL BE SKIPPED.

9028.0
NO NONLINEAR ELEMENTS HAVE BEEN SPECIFIED.

9029.0
For this decomposition, the Case Control boundary condition specification is SPC=%1 MPC=%2
SUPORT=%3

9030.0
NO BUCKLING EIGENVALUES FOUND IN RESIDUAL STRUCTURE.

User action: If no eigenvalue range (L1,L2 on EIGB and F1,F2 on EIGR) is specified then try specifying a
range. If EIGB is used then try EIGR and vice-versa.

9031.0
NOGO ENCOUNTERED IN SUBDMAP %1

9032.0

Main Index
 MSC Nastran Error Messages 987
Errors 9000 - 9999

RUN IS TERMINATED DUE TO MESSAGE(S) ABOVE.

TO CONTINUE PROCESSING ALL SUPERELEMENTS, INSERT PARAM,ERROR,0 INTO BULK
DATA.

9032.1
RUN IS TERMINATED DUE TO MESSAGE(S) ABOVE
Search backward for the keyword (1) FATAL or (2) DIVERGES to locate the messages

9032.2
RUN IS TERMINATED DUE TO MESSAGE(S) ABOVE ON THE RESIDUAL STRUCTURE AND/
OR THE SUPERELEMENT(S).

9033.0
PHASE 1 IS TERMINATED DUE TO MESSAGE(S) ABOVE FOR THIS SUPERELEMENT ONLY.
PROCESSING WILL CONTINUE FOR THE REMAINING REQUESTED SUPERELEMENTS
AND THEN TERMINATE IN PHASE 2.

9034.0
TIMETEST PARAM=%1

9035.0
THE NUMBER OF MODES IS EQUAL TO THE NUMBER OF DOFS.
RESIDUAL VECTORS WILL NOT BE CALCULATED.

9035.1
NO LOADS OR INITIAL CONDITION VECTORS FOUND.
RESIDUAL VECTORS WILL NOT BE CALCULATED.

9035.2
NO RESIDUAL VECTORS WERE FOUND.

9035.3
NO STATIC SHAPES WERE FOUND TO AUGMENT MODE SHAPES

9036.0
NO STATIC SHAPES WERE AVAILABLE AFTER FILTERING

9036.1

Main Index
 988 MSC Nastran Error Messages
Errors 9000 - 9999

MASSLESS RESIDUAL VECTORS HAVE BEEN DETECTED.

9037.0
THE RESIDUAL VECTOR LOADS AND INITIAL CONDITIONS ARE NOT LINEARLY INDE-
PENDENT WITH MODAL VECTORS OR NO RESIDUAL VECTOR LOADS AND INITIAL
CONDITIONS WERE FOUND AFTER FILTERING AND SWEEPING.

User information: RESIDUAL VECTORS WILL NOT BE ADDED TO THE MODAL VECTORS.

9037.1
CHECKING RESIDUAL VECTORS FOR LINEAR INDEPENDENCE.

9038.0
FOR STATIC AERO ITERATIVE SOLUTION, %1 ITERATIONS USED FOR MATRIX %2 MAXI-
MUM LOAD EPSILON IS %3

9039.0
NO COMPLEX EIGENVALUES FOUND IN RESIDUAL STRUCTURE.

9039.1
NO COMPLEX EIGENVALUES FOUND IN RESIDUAL STRUCTURE.

User information: DIVERGENCE ANALYSIS WILL BE SKIPPED FOR THIS SUBCASE.

9040.0
CRITICAL BUCKLING FACTOR (ALPHA2)= %1
COMPUTED BASED ON THE FIRST EIGENVALUE = %2

9040.1
CRITICAL BUCKLING FACTOR (ALPHA)= %1

9040.2
CRITICAL BUCKLING FACTOR (ALPHA)= %1 LOAD STEP = %2 STEP %3 SUBCASE %4

9041.0
THERE ARE CHANGES IN K2PP, M2PP, B2PP, SDAMP, TFL, OR LOADSET.
THERE ARE CHANGES IN SDAMP, TFL, OR LOADSET.

Main Index
 MSC Nastran Error Messages 989
Errors 9000 - 9999

9043.0
AS REQUESTED BY PARAM,SERST,%1 THIS RUN DID NOT COMPLETE PHASE 0 AND
SHOULD BE VERIFIED FOR CORRECT RESULTS.
BULK DATA AND CASE CONTROL PARTITIONING, RESTART CHECKING, AND UNDE-
FORMED PLOTTING IS INITIATED FOR SUPERELEMENT %1

9044.0
INITIATED FOR SUPERELEMENT %1

9045.0
PHASE 1 - SUPERELEMENT GENERATION, ASSEMBLY AND REDUCTION.

9046.0
THE FRACTION OF TOTAL STRAIN ENERGY IN EACH OF THE RESIDUAL STRUCTURE
MODES IN TIP SUPERELEMENT %1

9046.1
THE FRACTION OF TOTAL STRAIN ENERGY IN EACH OF THE RESIDUAL STRUCTURE
MODES IN NON-TIP SUPERELEMENT %1

9047.0
SCALED RESPONSE SPECTRA FOR RESIDUAL STRUCTURE

9047.1
SCALED RESPONSE SPECTRA FOR SUPERELEMENT %1

9048.0
LINEAR ELEMENTS ARE CONNECTED TO THE ANALYSIS SET (A-SET).

9048.1
LINEAR ELEMENTS ARE CONNECTED TO THE GLOBAL SET (G-SET).

9049.0
SUPERELEMENT DIFFERENTIAL STIFFNESS GENERATION, ASSEMBLY, AND REDUCTION.

Main Index
 990 MSC Nastran Error Messages
Errors 9000 - 9999

9050.0
RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX %1.

User action: THIS OCCURS WHEN NUMERIC PROBLEMS OR POTENTIAL SINGULARITIES

ARE ENCOUNTERED.
1. REVIEW GRID POINT AND COMPONENT INFORMATION PRINTED IN THE .F06
FILE (LOOK AT THE GRID POINT IDS ANDDEGREE OF FREEDOM COLUMNS).
2. EXAMINE THE F.E. MODEL NEAR THESE GRID IDS, LOOKING FOR UN-
CONSTRAINED DEGREES OF FREEDOM (BOUNDARY CONDITION ISSUES), ILL-
DEFINED ELEMENTS OR OTHER ANOMALIES WITHIN THE MODEL.
3. A FREE-FREE MODAL ANALYSIS (SOL 103) CAN BE PERFORMED TO CHECK FOR
RIGID-BODY MOTIONS AND DISCONTINUITIES WITHIN THE F.E. MODEL.
4. IF USING RBE3 ENTRIES, YOU MIGHT SET “PARAM,RMRBE3RT,1”. THIS PARAMETER
REMOVES ROTATIONAL DEGREES OF FREEDOM FROM REFC OF ANY RBE3 WHOSE
REFERENCE GRID POINT IS USED BY SOLID ELEMENTS ONLY, AND REFC HAS A
ROTATIONAL DEGREE OF FREEDOM.
5. IF [1]-[4] FAIL TO DETERMINE THE PROBLEM, YOU MIGHT TRY “PARAM, BAILOUT,-
1” WHICH MAY ALLOW THE MODEL TO RUN TO COMPLETION OR THE MODEL
TO FAIL LATER WITH A MORE USEFUL MESSAGE. RESULTS USING “PARAM,
BAILOUT” ARE OFTEN POOR.

#OLD User action: CONSTRAIN MECHANISMS WITH SPCI OR SUPORTI ENTRIES OR

SPECIFY PARAM,BAILOUT,-1 TO CONTINUE THE RUN WITH MECHANISMS.
9050.1

Main Index
 MSC Nastran Error Messages 991
Errors 9000 - 9999

RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX %1.

User action: THIS OCCURS WHEN NUMERIC PROBLEMS OR POTENTIAL SINGULARITIES

ARE ENCOUNTERED.
1. REVIEW GRID POINT AND COMPONENT INFORMATION PRINTED IN THE .F06
FILE (LOOK AT THE GRID POINT IDS AND DEGREE OF FREEDOM COLUMNS).
2. EXAMINE THE F.E. MODEL NEAR THESE GRID IDS, LOOKING FOR UN-
CONSTRAINED DEGREES OF FREEDOM (BOUNDARY CONDITION ISSUES), ILL-
DEFINED ELEMENTS OR OTHER ANOMALIES WITHIN THE MODEL.
3. A FREE-FREE MODAL ANALYSIS (SOL 103) CAN BE PERFORMED TO CHECK FOR
RIGID-BODY MOTIONS AND DISCONTINUITIES WITHIN THE F.E. MODEL.
4. IF USING RBE3 ENTRIES, YOU MIGHT SET “PARAM,RMRBE3RT,1”. THIS PARAMETER
REMOVES ROTATIONAL DEGREES OF FREEDOM FROM REFC OF ANY RBE3 WHOSE
REFERENCE GRID POINT IS USED BY SOLID ELEMENTS ONLY, AND REFC HAS A
ROTATIONAL DEGREE OF FREEDOM.
5. IF [1]-[4] FAIL TO DETERMINE THE PROBLEM, YOU MIGHT TRY “PARAM, BAILOUT,-
1” WHICH MAY ALLOW THE MODEL TO RUN TO COMPLETION OR THE MODEL
TO FAIL LATER WITH A MORE USEFUL MESSAGE. RESULTS USING “PARAM,
BAILOUT” ARE OFTEN POOR.

#OLD User action: CONSTRAIN MECHANISMS WITH ADDITIONAL SPCI, OR SUPORTI

ENTRIES OR SPECIFY PARAM,BAILOUT,-1 TO CONTINUE THE RUN WITH MECHANISMS.
9050.2
ENCOUNTERED EXCESSIVE PIVOT RATIOS IN MATRIX %1.

User information: ACCURATE RIGID BODY MODES ARE REQUIRED FOR AUTO-SUPORT
AND RESIDUAL VECTORS.

User action: SET F1<=0. ON THE EIGR BULK DATA ENTRY OR V1<=0. ON THE EIGRL ENTRY.

Main Index
 992 MSC Nastran Error Messages
Errors 9000 - 9999

9050.3
ENCOUNTERED EXCESSIVE PIVOT RATIOS IN MATRIX %1.

User action: THIS OCCURS WHEN NUMERIC PROBLEMS OR POTENTIAL SINGULARITIES

ARE ENCOUNTERED.
1. REVIEW GRID POINT AND COMPONENET INFORMATION PRINTED IN THE .F06
FILE(LOOK AT THE GRID POINT IDS AND DEGREE OF FREEDOM COLUMNS).
2. EXAMINE THE F.E. MODEL NEAR THESE GRID IDS, LOOKING FOR UN-
CONSTRAINED DEGREES OF FREEDOM (BOUNDARY CONDITION ISSUES), ILL-
DEFINED ELEMENTS OR OTHER ANOMALIES WITHIN THE MODEL.
3. A FREE-FREE MODAL ANALYSIS (SOL 103) CAN BE PERFORMED TO CHECK FOR
RIGID-BODY MOTIONS AND DISCONTINUITIES WITHIN THE F.E. MODEL.
4. IF USING RBE3 ENTRIES, YOU MIGHT SET “PARAM,RMRBE3RT,1”. THIS PARAMETER
REMOVES ROTATIONAL DEGREES OF FREEDOM FROM REFC OF ANY RBE3 WHOSE
REFERENCE GRID POINT IS USED BY SOLID ELEMENTS ONLY, AND REFC HAS A
ROTATIONAL DEGREE OF FREEDOM.
5. IF [1]-[4] FAIL TO DETERMINE THE PROBLEM, YOU MIGHT TRY “PARAM, BAILOUT,-
1” WHICH MAY ALLOW THE MODEL TO RUN TO COMPLETION OR THE MODEL
TO FAIL LATER WITH A MORE USEFUL MESSAGE. RESULTS USING “PARAM,
BAILOUT” ARE OFTEN POOR.

#OLD User information: AUTO-SUPORT WILL BE PERFORMED FOR RESIDUAL VECTOR

PROCESSING.

9050.4

Main Index
 MSC Nastran Error Messages 993
Errors 9000 - 9999

RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX %1.

User action: THIS OCCURS WHEN NUMERIC PROBLEMS OR POTENTIAL SINGULARITIES

ARE ENCOUNTERED.
1. REVIEW GRID POINT AND COMPONENT INFORMATION PRINTED IN THE .F06
FILE (LOOK AT THE GRID POINT IDS AND DEGREE OF FREEDOM COLUMNS).
2. EXAMINE THE F.E. MODEL NEAR THESE GRID IDS, LOOKING FOR UN-
CONSTRAINED DEGREES OF FREEDOM (BOUNDARY CONDITION ISSUES), ILL-
DEFINED ELEMENTS OR OTHER ANOMALIES WITHIN THE MODEL.
3. A FREE-FREE MODAL ANALYSIS (SOL 103) CAN BE PERFORMED TO CHECK FOR
RIGID-BODY MOTIONS AND DISCONTINUITIES WITHIN THE F.E. MODEL.
4. IF USING RBE3 ENTRIES, YOU MIGHT SET “PARAM,RMRBE3RT,1”. THIS PARAMETER
REMOVES ROTATIONAL DEGREES OF FREEDOM FROM REFC OF ANY RBE3 WHOSE
REFERENCE GRID POINT IS USED BY SOLID ELEMENTS ONLY, AND REFC HAS A
ROTATIONAL DEGREE OF FREEDOM.
5. IF [1]-[4] FAIL TO DETERMINE THE PROBLEM, YOU MIGHT TRY “PARAM, BAILOUT,-
1” WHICH MAY ALLOW THE MODEL TO RUN TO COMPLETION OR THE MODEL
TO FAIL LATER WITH A MORE USEFUL MESSAGE. RESULTS USING “PARAM,
BAILOUT” ARE OFTEN POOR.

#OLD User action: CONSTRAIN MECHANISMS WITH SPCI ENTRIES OR SPECIFY

PARAM,BAILOUT,-1 TO CONTINUE THE RUN WITH MECHANISMS.

9050.5
RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX %1.

User information: ACCURATE RIGID BODY MODES ARE REQUIRED FOR AUTO-SUPORT
AND RESIDUAL VECTORS.

User action: SET F1<=0. ON THE EIGR BULK DATA ENTRY OR V1<=0. ON THE EIGRL ENTRY.
IF IT IS DESIRED TO EXCLUDE RIGID BODY OR LOW FREQUENCY MODES FROM
DYNAMIC SOLUTION THEN SPECIFY PARAM,LFREQ OR MODESELECT CASE CONTROL
COMMAND. ANOTHER COURSE OF ACTION IS TO SPECIFY RESVEC=COMP OR RES-
VEC=NO.

9050.6

Main Index
 994 MSC Nastran Error Messages
Errors 9000 - 9999

STATIC SOLUTION TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX %1.

User action: THIS OCCURS WHEN NUMERIC PROBLEMS OR POTENTIAL SINGULARITIES

ARE ENCOUNTERED.
1. REVIEW GRID POINT AND COMPONENT INFORMATION PRINTED IN THE .F06
FILE (LOOK AT THE GRID POINT IDS ANDDEGREE OF FREEDOM COLUMNS).
2. EXAMINE THE F.E. MODEL NEAR THESE GRID IDS, LOOKING FOR UN-
CONSTRAINED DEGREES OF FREEDOM (BOUNDARY CONDITION ISSUES), ILL-
DEFINED ELEMENTS OR OTHER ANOMALIES WITHIN THE MODEL.
3. A FREE-FREE MODAL ANALYSIS (SOL 103) CAN BE PERFORMED TO CHECK FOR
RIGID-BODY MOTIONS AND DISCONTINUITIES WITHIN THE F.E. MODEL.
4. IF USING RBE3 ENTRIES, YOU MIGHT SET “PARAM,RMRBE3RT,1”. THIS PARAMETER
REMOVES ROTATIONAL DEGREES OF FREEDOM FROM REFC OF ANY RBE3 WHOSE
REFERENCE GRID POINT IS USED BY SOLID ELEMENTS ONLY, AND REFC HAS A
ROTATIONAL DEGREE OF FREEDOM.
5. IF [1]-[4] FAIL TO DETERMINE THE PROBLEM, YOU MIGHT TRY “PARAM, BAILOUT,-
1” WHICH MAY ALLOW THE MODEL TO RUN TO COMPLETION OR THE MODEL
TO FAIL LATER WITH A MORE USEFUL MESSAGE. RESULTS USING “PARAM,
BAILOUT” ARE OFTEN POOR.

9050.7
PARAM,BAILOUT,-1 ACTIVATED WITHIN THE SOLVER FOR RIGID=LAGRAN. THE RUN
WILL CONTINUE. CHECK THE SOLUTION QUALITY AT THE END.

9051.0
%1 ANALYSIS INITIATED.

9051.1
%1 ANALYSIS INITIATED. DESIGN CYCLE NUMBER=%2

9051.2
%1 ANALYSIS - DATA RECOVERY INITIATED.

9051.3
%1 ANALYSIS - DATA RECOVERY INITIATED. DESIGN CYCLE NUMBER=%2

9051.4
%1 ANALYSIS INITIATED FOR ANALYSIS =%2

Main Index
 MSC Nastran Error Messages 995
Errors 9000 - 9999

9051.5
%1 ANALYSIS INITIATED FOR ANALYSIS =%2 AND DESIGN CYCLE NUMBER =%3

9051.6
%1 ANALYSIS INITIATED FOR LOOP ID=%1

9051.11
%1 ANALYSIS FOR %2 INITIATED.

9051.12
%1 ANALYSIS FOR %2 COMPLETED.

9051.13
THE CURRENT ESLNRO DOES NOT SUPPORT MATHE

9051.14
SOL 400 DOES NOT SUPPORT THE CASI SOLVER (ELEMENT) WITH SEGMENT-TO-SEG-
MENT CONTACT IN PERMANENT GLUE CONTACT

User action: PLEASE CHANGE TO STEP/GENERAL GLUE CONTACT OR CHANGE CASI

SOLVER TO ANOTHER SOLVER

9052.0
%1 ANALYSIS COMPLETED.

9052.1
%1 ANALYSIS COMPLETED. DESIGN CYCLE NUMBER= %2

9052.2
%1 ANALYSIS - DATA RECOVERY COMPLETED.

9052.3
%1 ANALYSIS - DATA RECOVERY COMPLETED. DESIGN CYCLE NUMBER=%2

9052.4

Main Index
 996 MSC Nastran Error Messages
Errors 9000 - 9999

%1 ANALYSIS COMPLETED FOR ANALYSIS =%2

9052.5
%1 ANALYSIS COMPLETED FOR ANALYSIS =%2 AND DESIGN CYCLE NUMBER =%3

9052.6
%1 ANALYSIS - DATA RECOVERY COMPLETED FOR ANALYSIS =%2

9052.7
%1 ANALYSIS - DATA RECOVERY COMPLETED FOR ANALYSIS =%2 AND DESIGN CYCLE
NUMBER =%3

9052.8
%1 ANALYSIS COMPLETED FOR LOOP ID=%1

9052.9
%1 ANALYSIS HAS CONVERGED.

9052.10
HOT-TO-COLD ANALYSIS HAS REACHED MAXIMUM CYCLES (HTOCITS)
HOWEVER THE HOT-TO-COLD MAXIMUM GEOMETRY ERROR IS STILL ABOVE TOLER-
ANCE (HTOCTOL).
THE RESULTS FROM THE FINAL CYCLE WILL BE USED.

9052.11
%1 ANALYSIS FOR%2 COMPLETED.

9052.13
%1 IN BUCKLING ANALYSIS.
A POSITIVE STURM COUNT NUMBER INDICATES THE BUCKLING MODES ARE BELOW
THE APPLIED STATIC PRELOAD. ADJUST STATIC PRELOAD BELOW THE LOWEST BUCK-
LING MODE.

9052.20
H-ADAPTIVE ANALYSIS DOES NOT SUPPORT THE SEGMENT-TO-SEGMENT CONTACT.

9053.0

Main Index
 MSC Nastran Error Messages 997
Errors 9000 - 9999

FLUID MODAL PARTICIPATION IS REQUESTED FOR%1 FLUID MODES.

9053.1
STRUCTURAL AND LOAD MODAL PARTICIPATION IS REQUESTED FOR%1 STRUCTURAL
MODES.

9054.0
FLUID MODAL PARTICIPATION FACTORS SHOWN BELOW IN MATRIX FLMODPF FOR
FREQUENCY=%1 AND DLOAD ID=%2

9054.1
STRUCTURAL MODAL PARTICIPATION FACTORS SHOWN BELOW IN MATRIX STMODPF
FOR FREQUENCY=%1 AND DLOAD ID=%2

9054.2
PANEL MODAL PARTICIPATION FACTORS SHOWN BELOW IN PNLMODPF FOR PANEL
=%1 AT FREQUENCY =%2 AND DLOAD ID=%3

9054.3
LOAD MODAL PARTICIPATION FACTORS SHOWN BELOW IN MATRIX LDMODPF FOR
FREQUENCY=%1 AND DLOAD ID=%2

9054.4
RESTART DOES NOT SUPPORT THE SEGMENT-TO-SEGMENT CONTACT.

9054.5
CONTACT TYPE HAS BEEN CHANGED DURING RESTART.

9054.6
CONTACT TYPE HAS BEEN CHANGED FROM TOUCHING TO GLUED CONTACT IN
RESTART RUN.
TO RUN RESTART WITH CONTACT TYPE CHANGE, PLEASE USE SYSTEM(729)=1 IN COLD
START RUN.

9054.7

Main Index
 998 MSC Nastran Error Messages
Errors 9000 - 9999

CONTACT HAS BEEN ADDED ON A NONLINEAR RESTART RUN. THIS IS NOT SUP-
PORTED.
TO RUN RESTART WITH CONTACT, CONTACT ANALYSIS MUST BE ACTIVATED DURING
COLD START

9054.8
CONTACT MODEL HAS BEEN CHANGED IN RESTART RUN. THIS IS NOT SUPPORTED.
TO RUN RESTART WITH CONTACT MODEL ADDED IN RESTART INPUT, CONTACT
ANALYSIS INCLUDING THIS CONTACT MODEL MUST BE ACTIVATED DURING COLD
START

9055.0
THE FL./STR. INTERFACE CHECK IS FORCES AND MOMENTS RESULTING FROM A UNIT
INCREASE IN PRESSURE, OR CHANGES
IN THE FLUID PRESSURE RESULTING FROM RIGID BODY MOTIONS OF THE STRUC-
TURE. THESE VALUES ARE DIRECTLY PROPORTIONAL TO THE OPEN SURFACE OF THE
FLUID.

9056.0
NO METHOD COMMAND WAS SPECIFIED IN THE CASE CONTROL SECTION.

9056.1
METHOD or METHOD (structure) COMMAND in CASE CONTROL is required for MODAL FRE-
QUENCY RESPONSE with TRIM COMPONENT(s).

9056.2
SOL 108 DIRECT DREQUENCY RESPONSE DOES NOT SUPPORT TRIM COMPONENT
UNDER BEGIN BULK TRMC=trmid.

9057.0
LINEAR STATIC ANALYSIS WILL BE PERFORMED WITH TEMPERATURES COMPUTED
ABOVE.

9058.0
THE SOLUTION FOR THE RESIDUAL STRUCTURE AND THE CURRENT SUBCASE DOES
NOT EXIST.

Main Index
 MSC Nastran Error Messages 999
Errors 9000 - 9999

9058.1
THE SOLUTION FOR THE RESIDUAL STRUCTURE AND THE APPLIED LOADS FOR THE
CURRENT SUBCASE ARE ZERO.

9058.2
THE %1 SOLUTION FOR THE RESIDUAL STRUCTURE AND THE CURRENT SUBCASE
DOES NOT EXIST.

9058.3
THE %1 SOLUTION AND %2 LOADS FOR THE RESIDUAL STRUCTURE AND THE CUR-
RENT SUBCASE ARE ZERO.

9058.4
THE SOLUTION FOR THE RESIDUAL STRUCTURE DOES NOT EXIST.
POSSIBLE AVOIDANCE: USE SOL 103 TO CREATE EXTERNAL SUPERELEMENT

9058.5
DESIGN SENSITIVITY ANALYSIS DOES NOT SUPPORT CASI SOLVER.

User action: USE A MATRIX-BASED SOLVER

9058.6
THE ELEMENT-BASED ITERATIVE SOLVER (CASI) IS NOT SUPPORTED IN SOLUTION %1.

User information: IT IS ONLY SUPPORTED IN SOLS %2.

User action: USE A MATRIX-BASED SOLVER.

9059.0
LOADING MACHINE %1 CONFIG %2 OPERASYS %3 OPERALEV %4 SUBMODEL %5

9060.0
DATABLOCK %1 %2 %3 %4

9061.0

Main Index
 1000 MSC Nastran Error Messages
Errors 9000 - 9999

THE VERSION REQUESTED ON THE RESTART FMS STATEMENT IS NOT VALID FOR
RESTART PURPOSES.
SUBSEQUENT RESTARTS SHOULD REFERENCE A PRIOR VALID VERSION.

User information: The data base is not restartable if any of the following was specified in the cold start
1. EXTSEOUT or EXTMDOUT(DMIGDB or MATDB) without defining DBEXT
2. scr=post
3. scr=no and "nastran system(316)>0"

9062.0
ENFORCED MOTION IS NOT SUPPORTED FOR ANALYSIS=%1.

9062.1
LOAD REDUCTION IS INCOMPLETE WHEN FIXEDB=-2. THEREFORE, LOAD MATRICES
POS, PSS, AND PA ARE DELETED.

9062.2
LOAD REDUCTION IS INCOMPLETE WHEN FIXEDB=-2. THEREFORE, LOAD MATRICES
QR AND PL ARE DELETED.

9063.0
FLUID/STRUCTURE COUPLING IS IGNORED IN THIS SOLUTION SEQUENCE.

9064.0
P-VERSION ELEMENT ENTRIES ARE PRESENT AND ARE NOT ALLOWED IN THIS SOLU-
TION SEQUENCE.
REMOVE ALL P-VERSION ELEMENT ENTRIES OR USE SOLS 101, 103, 107 THROUGH 112,
AND 200.

9064.1
P-VERSION ELEMENT ENTRIES ARE PRESENT AND ARE NOT ALLOWED IN PARTI-
TIONED SUPERELMENTS OR MODULES.

9064.2
P-VERSION ELEMENT ENTRIES ARE PRESENT IN THE MAIN BULK DATA SECTION AND
ARE NOT ALLOWED WITH PARTITIONED BULK DATA SUPERELEMENTS OR MODULES.

Main Index
 MSC Nastran Error Messages 1001
Errors 9000 - 9999

9065.0
FOR STATIC AERO ITERATIVE SOLUTION, MAXIMUM ERROR EXCEEDS 1.E-3.

9066.0
EITHER GEOMETRIC OR AUXILIARY MODELS MAY BE USED,BUT NOT BOTH IN THE
SAME RUN.

9067.0
SUPERELEMENTS OR MODULES HAVE BEEN DEFINED IN AUXILIARY MODEL ID= %1
AND THIS IS NOT ALLOWED.

9067.1
SUPERELEMENTS OR MODULES HAVE BEEN DEFINED IN THE PRIMARY MODEL AND
THIS IS NOT ALLOWED.

9068.0
NO DRESPI ENTRIES EXIST FOR DESOBJ ID=%1

9068.1
NO DRESPI ENTRIES EXIST FOR DESOBJ ID=%1

User information: THIS MAY BE BECAUSE THe DESOBJ REQUEST IS IN AN ANALYSIS=MFREQ

SUBCASE AND THERE ARE FREQ3/4/5 ENTRIES AND MODE TRACKING IS REQUESTED.
EITHER MOVE THE DESOBJ REQUEST ABOVE THE SUBCASE LEVEL OR REDEFINE THE
DESIGN TASK.

9069.0
RUN TERMINATED DUE TO BAD GEOMETRY RESULTING FROM SHAPE OPTIMIZATION.
IT MAY BE NECESSARY TO REMESH THE MODEL AND/OR RESCALE THE SHAPE BASIS
VECTORS.

9070.0
AESMETH =%1 IS NOT SUPPORTED. AESMETH = AUTO WILL BE USED INSTEAD.

9071.0

Main Index
 1002 MSC Nastran Error Messages
Errors 9000 - 9999

THE TSTEPNL ENTRY METHOD IS BEING CHANGED TO ADAPT DUE TO CONTACT

ANALYSIS.

9072.0
MULTIPLE BOUNDARY CONDITIONS ARE NOT ALLOWED FOR SUPERELEMENTS OR
MODULES.

9072.1
MULTIPLE BOUNDARY CONDITIONS ARE SPECIFIED WITH EXTSEOUT or EXTMDOUT
COMMAND WHICH IS NOT ALLOWED.

9072.2
PARAM,AUTOMSET,YES IS NOT SUPPORTED FOR SOL 400.

9072.3
MULTIPLE BOUNDARY CONDITIONS ARE SPECIFIED IN NORMAL MODES WITH P-ELE-
MENTS WHICH IS NOT ALLOWED.

9072.4
SET FOR RIGID ELEMENTS IS NOT SUPPORTED FOR SOL 400.

9072.5
The STATSUB and EXTSEOUT or EXTMDOUT Case Control commands are present which is not
allowed.
Differential stiffness is not supported when creating external superelements.

9073.0
MULTIPLE BOUNDARY CONDITIONS IN NORMAL MODES ANALYSIS REQUIRES THE
BC=N COMMAND IN EACH RESIDUAL STRUCTURE SUBCASE.

9074.0
MULTIPLE BOUNDARY CONDITIONS ARE SPECIFIED FOR ANALYSIS= %1 WHICH ARE
NOT ALLOWED.

9074.1
MULTIPLE ENFORCED TEMPERATURE SUBCASES ARE SPECIFIED, WHICH IS NOT
ALLOWED.

Main Index
 MSC Nastran Error Messages 1003
Errors 9000 - 9999

9074.2
MULTIPLE BOUNDARY CONDITION SUBCASES ARE SPECIFIED, WHICH IS NOT
ALLOWED.

9075.0
Superelements are detected in Heat Transfer Analysis.

User action: Remove all superelement definitions (e.g., SESET entries and field 9 of GRID entries.)' $

9075.1
Superelements are detected in Automatic External Superelement Analysis (AESO).

User action: Remove all superelement definitions (e.g., SESET entries and field 9 of GRID entries.)' $

9075.2
SOL400 DOES NOT CURRENTLY SUPPORT EXTERNAL SUPERELEMENTS.

9076.0
THERE ARE NO RETAINED RESPONSES. THEREFORE, THE DESIGN SENSITIVITY COEFFI-
CIENT MATRIX CANNOT PRINTED OR EXPORTED.

User action: TO RETAIN MORE RESPONSES, TIGHTEN THE DCONSTR LIMITS AND/OR
RAISE THE DSCREEN THRESHOLDS.

9076.1
THERE ARE NO RETAINED RESPONSES. THEREFORE, THE DESIGN SENSITIVITY COEFFI-
CIENT MATRIX CANNOT PRINTED OR EXPORTED.
THE REASON IS BECAUSE MODE TRACKING WAS NOT SUCCESSFUL.

9077.0
CONSTRAINED DISPLACEMENT ITERATIONS

9077.1

Main Index
 1004 MSC Nastran Error Messages
Errors 9000 - 9999

CONSTRAINED DISPLACEMENT ITERATIONS

CONSTRAINED DISPLACEMENT DIAGNOSTICS, UR= NEGATIVE DISPLACEMENT, QR=
NEGATIVE FORCE

9078.0
RUN IS TERMINATED BECAUSE AN ERROR OCCURRED IN THE ITERATIVE SOLVER
WITHIN NLITER MODULE. CHECK MESSAGES ABOVE.

9078.1
RUN IS TERMINATED BECAUSE NO CONVERGENCE WAS REACHED WITH THE ITERA-
TIVE SOLVER.

9078.2
RUN IS TERMINATED DUE TO INSUFFICIENT MEMORY.

User information: SEE ABOVE MESSAGES AND .f04 FILE FOR MEMORY ESTIMATES.

*** USER FATAL MESSAGE 9079

RBE2GS elements are present with part (BEGIN SUPER) superelements.
9079.0
User information: RBE2GS elements may only be specified with no superelements or grid-list (SESET)
superelements.

*** USER FATAL MESSAGE 9080

CFAST, CWELD and/or CSEAM elements are present in part (BEGIN SUPER) superelements.
9080.0
User information: CFAST, CWELD and/or CSEAM elements may only be specified in the main Bulk
Data section.

9081.0
FLUID/STRUCTURE COUPLING IS NOT ALLOWED WITH P-ELEMENTS.

9082.0
PARAM,NMLOOP MAY NOT BE SPECIFIED IN BUCKLING, CYCLIC, OR OPTIMIZATION
ANALYSIS.

9083.0

Main Index
 MSC Nastran Error Messages 1005
Errors 9000 - 9999

PARAM,NMLOOP SPECIFIES AN INVALID LOOPID.

A LIST OF VALID LOOPIDS SHOULD APPEAR ABOVE. HOWEVER, IF NONE APPEAR ABOVE
THEN CHECK THE NONLINEAR ITERATION OUTPUT, THE DATABASE CONTENTS AND/
OR CORRECT DATABASE ATTACHMENT.

9084.0
NONLINEAR BUCKLING PROJECTION AT LOOPID =%1 LOAD FACTOR =%2

9086.0
PARAM, SUBCASID, %1 DOES NOT CORRESPOND TO A VALID SUBCASE IDENTIFICA-
TION NUMBER.

9086.1
PARAM, SUBID MUST BE LESS THAN OR EQUAL TO %1

9086.2
PARAM, LOOPID, %1 DOES NOT CORRESPOND TO A VALID LOOP IDENTIFICATION
NUMBER.

9086.3
PARAM, SUBID OR SUBCASID IS NOT SPECIFIED.

9086.4
PARAM, SUBID OR SUBCASID SPECIFIES FIRST SUBCASE

9086.5
THE DATA BASE IS INSUFFICIENT FOR PARAM,LOOPID RESTARTS. CHECK FOR BULK
DATA CHANGES RELATED TO GEOMETRY, CONNECTIVITY, AND PROPERTIES, WHICH
CAUSE THE RECALCULATION OF NONLINEAR DATA.

9086.6
PARAM,LOOPID=%1 IS NOT LESS THAN OR EQUAL TO LAST LOOPID=%2 IN PREVIOUS
SUBCASE.

9086.11

Main Index
 1006 MSC Nastran Error Messages
Errors 9000 - 9999

%1 %2 DOES NOT CORRESPOND TO A VALID P-VALUE IDENTIFICATION NUMBER.

User action: IF THIS IS A RESTART, THEN CHECK ASSIGNMENT OF THE OLD DATABASE
AND ITS CONTENTS FOR VALID P-VALUE IDENTIFICATION NUMBERS. IF NOT, THEN
REMOVE %1

9087.0
RESTARTING AFTER SUBCASE %1 (OR SUBID=%2) WITH LOOPID=%3

9087.1
RESTARTING INTO SUBCASE %1 (OR SUBID=%2) WITH LOOPID=%3

9088.0
PARAM,INREL,%1 IS PRESENT BUT NO MASS IS DEFINED.

9088.1
PARAM,INREL,-1 IS PRESENT BUT NO MASS IS DEFINED.

User information: THE SOLUTION WILL ONLY REFLECT THE APPLIED LOADS.

9088.2
PARAM,INREL,-1 IS PRESENT BUT NO MASS IS DEFINED IN THE CURRENT SUPERELE-
MENT.

User information: IT IS ASSUMED THAT MASS MAY BE BE PRESENT IN UPSTREAM

SUPERELEMENTS. IF NOT, THEN THE SOLUTION WILL ONLY REFLECT THE APPLIED
LOADS.

9088.3
PARAM,INREL,-4 IS PRESENT but the rigid body mass matrix--the mass matrix reduced to the
SUPORTi points--is null.

User information: Check to see if grid points with mass are constrained manually or by AUTOSPC.

9089.0

Main Index
 MSC Nastran Error Messages 1007
Errors 9000 - 9999

PARAM,NEWSEQ IS IGNORED BECAUSE RESEQUENCING IS NO LONGER RECOM-

MENDED EXCEPT FOR SOLUTIONS WITH THE DISTRIBUTED DOMAIN DECOMPOSI-
TION METHOD.
NEWSEQ HAS BEEN RENAMED OLDSEQ AND ITS DEFAULT IS -1 EXCEPT FOR THE DIS-
TRIBUTED DOMAIN DECOMPOSITION METHOD (SOL 101 SUBMITTED WITH DMP=N;
WHERE THE DEFAULT IS 11--AUTOMATIC MODEL PARTITIONER). IF STILL DESIRED,
PLEASE RESPECIFY AS PARAM,OLDSEQ.

9091.0
THE CASE CONTROL SECTION, ONE OR MORE OF THE PARTITIONED BULK DATA SEC-
TIONS, OR THE MAIN BULK DATA SECTION, HAVE INPUT ERRORS.
SEE MESSAGES ABOVE.

9092.0
THERE IS ALREADY A BULK DATA SECTION SPECIFIED REMAINING BULK DATA SE
TIONS, IF ANY, WILL BE CHECKED FOR ERRORS AND THEN THE RUN WILL TERMINATE.

9092.1
THERE IS ALREADY A BULK DATA SECTION SPECIFIED FOR AUXILIARY MODEL NUMBER
%1 REMAINING BULK DATA SECTIONS, IF ANY, WILL BE CHECKED FOR ERRORS AND
THEN THE RUN WILL TERMINATE.

9092.2
THERE IS ALREADY A BULK DATA SECTION SPECIFIED FOR SUPERELEMENT %1
REMAINING BULK DATA SECTIONS, IF ANY, WILL BE CHECKED FOR ERRORS AND THEN
THE RUN WILL TERMINATE.

9092.3
SOL %1 SUPPORTS RIGID=LINEAR ONLY

9095.0
A DUPLICATE SHUT VECTOR HAS BEEN FOUND, USE RANDOM VECTOR

9096.0
CONSTRAINED DISPLACEMENT ITERATIONS FAILED, ITERATION LIMIT SUBCASE = %1

Main Index
 1008 MSC Nastran Error Messages
Errors 9000 - 9999

9097.0
CONSTRAINED DISPLACEMENT ITERATIONS CONVERGED SUBCASE = %1

9098.0
NO EXTERNAL DATABASE, INPUTT2, OR INPUTT4 FILES WHICH CONTAIN SUPERELE-
MENT SOLUTION MATRICES ARE FOUND.
POSSIBLE SOURCES ARE:
1. DBLOCATE DATABLK=(EXTDB) OF SOLUTION MATRICES
2. DBLOCATE DATABLK=(EXTDB) OF DMIG SOLUTION MATRICES
3. ASSIGN INPUTT2 ON UNIT= %1 OF DMIG SOLUTION MATRICES
4. ASSIGN INPUTT4 ON UNIT= %1 OF SOLUTION MATRICES

9098.1
NO EXTERNAL DATABASE, INPUTT2, OR INPUTT4 FILES WHICH CONTAIN EXTERNAL
SUPERELEMENT (or MODULE) DATA
FOR SEID (OR Module ID) = %1 ARE FOUND.
POSSIBLE SOURCES OF ERROR ARE:
1. DBLOCATE DATABLK=(EXTDB) FOR EXTERNAL SUPERELEMENTS (or MODULES)
CREATED WITH MATDB.
2. DBLOCATE DATABLK=(EXTDB) FOR EXTERNAL SUPERELEMENTS (or MODULES)
CREATED WITH DMIGDB.
3. ASSIGN INPUTT2 WITH UNIT= %2 FOR EXTERNAL SUPERELEMENTS (or MODULES)
CREATED WITH DMIGOP2.
4. ASSIGN INPUTT4 WITH UNIT= %3 FOR EXTERNAL SUPERELEMENTS (or MODULES)
CREATED WITH MATOP4.

9098.2
THE INPUTT2 OR INPUTT4 FILE UNIT= %1 DOES NOT CONTAIN THE CORRECT DATA
REQUIRED TO ASSEMBLE THE EXTERNAL SUPERELEMENT (or MODULE) ID=%2

9098.3
NO %1 FILE WITH UNIT= %2 FOUND FOR Superelement (OR Module) ID= %3

User action: CHECK THE UNIT NUMBER ON THE ASSIGN FMS STATEMENT AGAINST THE
SEBULK OR MDBULK BULK DATA ENTRY.

9098.4

Main Index
 MSC Nastran Error Messages 1009
Errors 9000 - 9999

No external superelement (or module) data was found on the DBLOCATE'd database for superelement (or
module) %1.

User action:
1. Check DBLOCATE DATABLK(EXTDB) statement.
2. If NASTRAN SYSTEM(319) or scr=post is specified in the creaton run then specify the DBEXT
keyword on the EXTSEOUT or EXTMDOUT Case Control command.

9099.0
NO FORCES ARE SPLINED TO THE STRUCTURE.

User information: AT LEAST ONE SPLINE MUST BE USAGE=FORCE OR USAGE=BOTH IN

MODEL %1.

9100.0
FLUID SUPERELEMENT IS NOT A TIP SUPERELEMENT

9101.0
FLUID ELEMENTS ARE DETECTED IN THIS SUPERELEMENT.

User action: ENSURE THAT ALL FLUID ELEMENTS ARE ASSIGNED TO SUPERELEMENT %1

9103.0
PARAM,NMLOOP REQUESTS A RESTART FROM A NONLINEAR SOLUTION SEQUENCE
AND WILL PRODUCE INCREMENTAL DISPLACEMENTS, FORCES, AND STRESSES RELA-
TIVE TO THE NONLINEAR SOLUTION AT THE LOOP ID SPECIFIED FOR NMLOOP. ALSO,
IN THE CASE OF ELEMENTS WITH NONLINEAR MATERIAL PROPERTIES, THE ELEMENT
STRESS AND FORCE DATA RECOVERY WILL BE BASED ON THE MATERIAL PROPERTIES
SPECIFIED ON THE MAT1 BULK DATA ENTRY AND NOT MATS1.

9104.0
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.

Main Index
 1010 MSC Nastran Error Messages
Errors 9000 - 9999

9105.0
A SUPORTI BULK DATA ENTRY IS NOT PRESENT FOR INERTIA RELIEF ANALYSIS
(PARAM,INREL,%1).

User action: REMOVE PARAM,INREL,%1 OR SPECIFY A SUPORTI BULK DATA ENTRY.

9106.0
THE EXTERNAL (DBLOCATED) BASIS VECTOR MODEL IS INCOMPATIBLE. IT HAS %1
DEGREES-OF-FREEDOM AND IT SHOULD HAVE %2 DEGREES-OF-FREEDOM.

9107.0
The following points, either interior or exterior to the fluid superelement, are not defined as fluid grid
points; i.e., GRID entries with CD=-1.

9109.0
USETSEL IS GREATER THAN ZERO WHICH IS OBSOLETE. USETSEL WILL BE RESET TO -1
TO PRINT ALL SETS.

User action: SPECIFY PARAM,USETSEL,0 AND SET NAMES ON PARAM,USETSTR1 THRU

USETSTR4.

9110.0
YOU HAVE REQUESTED GLOBAL RESPONSE SENSITIVITY ANALYSIS OR DESIGN OPTIMI-
ZATION.
HOWEVER, ONLY THE GLOBAL RESPONSE EVALUATION IS SUPPORTED.

User action: REMOVE DSAPRT OR SET OPTEXIT<=3.

9111.0
COMPONENT (SUPERELEMENT) MODAL DAMPING IS REQUESTED BUT MASS NORMAL-
IZATION OF THE EIGENVECTORS IS NOT REQUESTED.

User action: SPECIFY MASS IN THE NORM FIELD OF THE EIGR/EIGRL ENTRY /
CHECK THAT PARAMETER SESDAMP IS SPEICIED AS 'NO' IN AN ASSEMBLY RUN

9113.0

Main Index
 MSC Nastran Error Messages 1011
Errors 9000 - 9999

VIRTUAL MASS IS DETECTED IN CYCLIC SYMMETRY ANALYSIS.

User action: REMOVE THE MFLUID COMMAND AND ALL VIRTUAL MASS ENTRIES.

9113.1
VIRTUAL MASS IS DETECTED WITH THE ADAMSMNF COMMAND.

User action: REMOVE THE MFLUID COMMAND AND ALL VIRTUAL MASS ENTRIES.

9113.2
VIRTUAL MASS IS DETECTED WITH THE AVLEXB COMMAND.

User action: REMOVE THE MFLUID COMMAND AND ALL VIRTUAL MASS ENTRIES.

9114.0
INERTIA RELIEF (PARAM,INREL) IS NOT ALLOWED

9115.0
NO AERODYNAMIC MATRIX QKK EXISTS FOR CONFIGURATION %1

User information: THE AERODYNAMIC MODEL IS NOT FROM A RECOGNIZED THEORY, SO

IT MUST BE SUPPLIED.

9116.0
THE FOLLOWER FORCE STIFFNESS IS SYMMETRIZED.

9116.1
THE FOLLOWER FORCE STIFFNESS IS SYMMETRIZED.
RATIO OF MAXIMUM UNSYMMETRY IS= %1

9116.2
THE FOLLOWER FORCE STIFFNESS IS NOT SYMMETRIC.

9116.3
THE FOLLOWER FORCE STIFFNESS IS NOT SYMMETRIC.
RATIO OF MAXIMUM UNSYMMETRY IS= %1

Main Index
 1012 MSC Nastran Error Messages
Errors 9000 - 9999

9116.4
THE FOLLOWER FORCE STIFFNESS HAS BEEN SYMMETRIZED.

9116.5
THE FOLLOWER FORCE STIFFNESS HAS BEEN SYMMETRIZED.
RATIO OF UNSYMMETRY IS= %1

9116.6
THE FOLLOWER FORCE STIFFNESS IS NOT SYMMETRIC.
RATIO OF UNSYMMETRY IS= %1

9116.7
THE FOLLOWER FORCE STIFFNESS HAS BEEN SYMMETRIZED.
RATIO OF MAXIMUM UNSYMMETRY IS= %1

9116.8
THE FOLLOWER FORCE STIFFNESS MATRIX HAS NOT BEEN SYMMETERIZED AUTOMAT-
ICALLY AND PARDISO CANNOT HANDLE UNSYMMETRIC IN SOL 400. SWITCHING BACK
TO MSCLDL SOLVER.

User action: USE PARAM,FKSYMFAC,1.0 TO FORCE SYMMETERIZE THE STIFFNESS MATRIX

TO USE PARDISO SOLVER.

9117.0
MASSLESS MECHANISMS MAY BE PRESENT IN THE MODEL BUT PARAM,MECHFIX,NO
HAS BEEN SPECIFIED.

User action: USE THE DEFAULT VALUE FOR PARAM,MECHFIX TO AUTOMATICALLY CON-
STRAIN MASSLESS MECHANISMS.

9117.1

Main Index
 MSC Nastran Error Messages 1013
Errors 9000 - 9999

The ACMS reduction has failed due to numeric singularities.

Possible causes for this failure include poorly defined material properties, use of shell elements with bending
stiffness to skin solid elements, or undetectable massless mechanisms.
Please see the SLDSKIN case control command for solid skin element controls.

If any Warning messages appear below, they should be reviewed in the F06 file above.

9118.0
IDENTIFICATION OF POSSIBLE MASSLESS MECHANISMS IS BEING PERFORMED.
IF ANY ARE FOUND THEN THEY WILL BE AUTOMATICALLY CONSTRAINED.

9118.1
IDENTIFICATION OF RIGID BODY MODES AND POSSIBLE MASSLESS MECHANISMS IS
BEING PERFORMED.

9118.2
IDENTIFICATION OF RIGID BODY MODES AND POSSIBLE MASSLESS MECHANISMS IS
BEING PERFORMED.
IF ANY MASSLESS MECHANISMS ARE FOUND THEN THEY WILL BE AUTOMATICALLY
CONSTRAINED.

9119.0
%1 RIGID BODY MODE(S) DETECTED AND %2 MASSLESS MECHANISM(S) DETECTED.
THE MASSLESS MECHANISMS ARE AUTOMATICALLY CONSTRAINED AND A SECOND
EIGENSOLUTION WILL BE ATTEMPTED.

9119.1
%1 RIGID BODY MODE(S) AND %2 MASSLESS MECHANISM(S) ARE DETECTED.

9120.0
NO MASSLESS MECHANISMS WERE DETECTED.

9120.1

Main Index
 1014 MSC Nastran Error Messages
Errors 9000 - 9999

NO MASSLESS MECHANISMS WERE DETECTED.

THERE IS ANOTHER TYPE OF ERROR EITHER IN THE MODEL OR THE PROGRAM.
REVIEW THE DIAGNOSTICS THAT APPEAR ABOVE User information MESSAGE 9118 AND IF
NO MODELLING ERROR CAN BE FOUND THEN CONTACT MSC CLIENT SUPPORT.

9120.2
NO MASSLESS MECHANISMS OR RIGID BODY MODES WERE DETECTED.

9120.3
DURING DETECTION OF MASSLESS MECHANISMS:
NUMBER OF SINGULARITIES IS AT LEAST %1 AND THIS IS GREATER THAN NLMAX OF
%2.

User information: THEREFORE NOT ALL SINGULARITIES MAY NOT BE FOUND.

User action: REPAIR MODEL OR INCREASE THE SIZE OF NLMAX.

9120.4
DURING DETECTION OF MASSLESS MECHANISMS:
THERE ARE NO EXTRA RAW VECTORS LEFT AFTER ORTHOGONALIZATION AND ALL
MASSLESS MECHANISMS MAY NOT HAVE BEEN FOUND.

User action: INSPECT THE MODELING AROUND THE HIGH RATIO POINTS FOR SYSTEM-
ATIC MODELING ERRORS OR SET PARAM, NLMAX TO A VALUE LARGER THAN %1

9120.5
SOME MASSLESS MECHANISMS MAY NOT BE DETECTED: BECAUSE NO TRIAL VECTORS
REMAIN AND MASSLESS MECHANISM DETECTION WILL BE TERMINATED.

9120.6
SOME MASSLESS MECHANISMS MAY NOT BE DETECTED BECAUSE TRIAL VECTORS
REMAIN AND MASSLESS MECHANISM DETECTION WILL BE TERMINATED.

9120.7

Main Index
 MSC Nastran Error Messages 1015
Errors 9000 - 9999

DURING DETECTION OF MASSLESS MECHANISMS:

NUMBER OF SINGULARITIES IS AT LEAST %1 AND THIS IS GREATER THAN NLMAX OF
%2.

User information: THEREFORE NOT ALL SINGULARITIES MAY NOT HAVE BEEN FOUND.

User action: REPAIR MODEL OR INCREASE THE SIZE OF NLMAX.

9121.0
MASSLESS MECHANISMS ARE LOADED AND THE LARGEST GENERALIZED FORCE FAC-
TOR IS %1
LOADS NOT CONSTRAINED BY MODE SHAPES WILL BE BALANCED BY EQUIVALENT SIN-
GLE POINT FORCES OF CONSTRAINT.

9122.0
NUMBER OF PROCESSORS IS GREATER THAN THE NUMBER OF TIP SUPERELEMENTS.
9123.0
NUMBER OF TIP SUPERELEMENTS IS NOT EVENLY DIVISIBLE BY NUMBER OF PROCES-
SORS.

9124.0
CAABSF Bulk Data entry is present with external superelement creation (EXTSEOUT or EXTMDOUT
Case Control or EXTOUT user parameter).

User action: Remove all CAABSF entries.

9125.0
THE ESE, EKE, OR EDE CASE CONTROL COMMANDS ARE SPECIFIED WITH THE
DEFAULT VALUE OF ZERO FOR PARAM,DDRMM IN MODAL FREQEUNCY RESPONSE
ANALYSIS.

User action: REMOVE THE ESE, EKE, AND EDE OR SPECIFY PARAM,DDRMM,-1. NOTE
THAT PARAM,DDRMM,-1 MAY COST MORE IN CPU AND DISK SPACE RESOURCES.

9126.0

Main Index
 1016 MSC Nastran Error Messages
Errors 9000 - 9999

THE FOLLOWING GRID POINTS ARE NOT SPECIFIED ON PLOTEL ELEMENTS BUT HAVE
BEEN REQUESTED FOR DATA RECOVERY.

User information: THESE GRID POINTS WILL BE IGNORED IN DATA RECOVERY DURING
THE ASSEMBLY RUN.

User action: DEFINE ADDITIONAL PLOTELS WHICH CONNECT THESE GRID POINTS.

9127.0
INITIATE MERGE OF RESULTS ACROSS ALL DOMAINS AND PROCESSORS.

9128.0
F1 ON THE EIGR OR EIGRL ENTRY IS GREATER THAN 0. AND THEREFORE AUTO-
SUPORT CANNOT BE PERFORMED.

9129.0
THERE WERE SINGULARITIES DETECTED DURING THE AUTO-SUPORT OPERATION.

User action: IF SOME OF THE RIGID BODY FREQUENCIES ARE GREATER THAN %1 THEN
INCREASE THE VALUE OF PARAM,FZERO.

User information: THE RUN WILL CONTINUE WITHOUT RESIDUAL VECTORS FOR THIS
SET OF MODES.

9129.1
THERE WERE SINGULARITIES DETECTED DURING THE AUTO-SUPORT OPERATION.

User information: THE RUN WILL CONTINUE WITHOUT RESIDUAL VECTORS FOR THIS
SET OF MODES.

9130.0
UNABLE TO SUBDIVIDE THE MODEL INTO MATRIX DOMAINS.

User information: THE NUMBER OF DOF= %1 IS BELOW THE MINIMUM VALUE OF %2

REQUIRED FOR ACMS.

9130.1

Main Index
 MSC Nastran Error Messages 1017
Errors 9000 - 9999

UNABLE TO SUBDIVIDE THE MODEL INTO MATRIX DOMAINS.

User information: THE NUMBER OF DOF= %1 IS BELOW THE MINIMUM VALUE OF %2

REQUIRED FOR ACMS. SYSTEM MODES WILL BE COMPUTED USING STANDARD METH-
ODS.

9130.2
UNABLE TO SUBDIVIDE THE MODEL INTO MATRIX DOMAINS.

User information: THE NUMBER OF DOF= %1 IS BELOW THE MINIMUM VALUE OF %2

REQUIRED FOR ACMS.
COMPONENT MODES WILL BE COMPUTED USING STANDARD METHODS.

9130.3
UNABLE TO SUBDIVIDE THE MODEL INTO MATRIX DOMAINS.

User information: SYSTEM MODES WILL BE COMPUTED USING STANDARD METHODS.

9130.4
UNABLE TO SUBDIVIDE THE MODEL INTO MATRIX DOMAINS.

User information: COMPONENT MODES WILL BE COMPUTED USING STANDARD METH-

ODS.

9130.5
UNABLE TO SUBDIVIDE THE MODEL INTO MATRIX DOMAINS.

User action: RE-SUBMIT THIS JOB USING PARTMETH=METISO ON THE DOMAINSOLVER

ENTRY.

9130.11
AN ERROR HAS OCCURRED WHILE CREATING THE PARTITIONS, THE PERMUTATION
MATRIX AND THE MAPS IN PRESOL, WHICH ARE NECESSARY FOR DOMAINSOLVER
MODES (PARTOPT=DOF).
THE READ MODULE WILL BE EXECUTED IN PARALLEL USING DOMAINSOLVER MODES
(PARTOPT=FREQ) INSTEAD OF DOMAINSOLVER MODES (PARTOPT=DOF).

Main Index
 1018 MSC Nastran Error Messages
Errors 9000 - 9999

9130.12
AN ERROR HAS OCCURRED WHILE CREATING THE PARTITIONS, THE PERMUTATION
MATRIX AND THE MAPS IN PRESOL, WHICH ARE NECESSARY FOR DOMAINSOLVER
STAT (PARTOPT=DOF).

9131.0
AN ERROR HAS OCCURRED WHILE FILTERING THE MATRICES KXX3 AND MXX3 FOR
DOMAINSOLVER MODES (PARTOPT=DOF).
THE READ MODULE WILL BE EXECUTED IN PARALLEL USING DOMAINSOLVER MODES
(PARTOPT=FREQ) INSTEAD OF DOMAINSOLVER MODES (PARTOPT=DOF).

9131.1
AN ERROR HAS OCCURRED WHILE FILTERING THE MATRICES KFF3 AND PF3 FOR
DOMAINSOLVER STAT (PARTOPT=DOF).

9132.0
INITIAL PRBDOFS APPEARS TO BE INVALID.
NUMBER OF NONZERO TERMS IN PRBDOFS = %1
NUMBER OF COLUMNS IN TR = %2
ATTEMPTING AN ALTERNATE METHOD.

9133.0
COULD NOT GENERATE A VALID PRBDOFS
NUMBER OF NONZERO TERMS IN PRBDOFS = %1
NUMBER OF COLUMNS IN TR = %2

9134.0
NO FLUID MODEL EXISTS. THEREFORE, FLUID/STRUCTURAL MODE PARTICIPATION
CALCULATIONS WILL BE SKIPPED.

9135.0
NO STRUCTURAL MODES WERE FOUND. THEREFORE, STRUCTURAL MODE PARTICIPA-
TION CALCULATIONS WILL BE SKIPPED.

9136.0

Main Index
 MSC Nastran Error Messages 1019
Errors 9000 - 9999

NO STRUCTURAL MODE PARTICIPATION FACTORS WERE REQUESTED. THEREFORE,

PANEL MODE PARTICIPATION CALCULATIONS WILL BE SKIPPED.

9137.0
FOR INVERSE LANCZOS, THE LARGEST NEGATIVE STIFFNESS IS %1

9138.0
THE STIFFNESS MATRIX IS NOT DIAGONAL FOR INVERSE LANCZOS.

User information: NON-ZERO OFF-DIAGONAL TERMS FOUND AT LOCATIONS IN MATRIX

ERRK BELOW. A STANDARD EIGENSOLUTION CALL WILL BE PERFORMED.

9139.0
EIGRL (OR EIGR) ENTRY = %1 CANNOT BE FOUND.

User information: AN EIGRL (OR EIGR) ENTRY IS REQUIRED INPUT FOR THIS DOMAIN-
SOLVER OPTION.

9139.1
V2 (OR F2) ON THE SELECTED EIGRL (OR EIGR) ENTRY = %1 IS BLANK OR ZERO.

User information: A NON-ZERO VALUE FOR V2 (OR F2) IS REQUIRED INPUT FOR THIS
DOMAINSOLVER OPTION.

9140.0
PARAM,OMID,YES IS IGNORED IN NONLINEAR ANALYSES.

9141.0
PARAM,INREL,-1 or -2 is requested in the presence of contact analysis which is not allowed.

9142.0
THE STIFFNESS MATRIX IS SINGULAR.

User information: THEREFORE RESIDUAL VECTORS CANNOT BE COMPUTED AND THE

RUN WILL CONTINUE WITHOUT RESIDUAL VECTORS FOR THIS SET OF MODES.
9142.1

Main Index
 1020 MSC Nastran Error Messages
Errors 9000 - 9999

THE STIFFNESS MATRIX IS SINGULAR.

User information: THEREFORE RESIDUAL VECTORS CANNOT BE COMPUTED AND THE

RUN WILL CONTINUE WITHOUT RESIDUAL VECTORS FOR THIS SET OF MODES.

User action: POSSIBLE AVOIDANCE:

SET F1<=0. ON THE EIGR BULK DATA ENTRY OR V1<=0. ON THE EIGRL ENTRY.

9142.2
THERE WERE PROBLEMS DURING THE RESIDUAL VECTOR EIGENVALUE EXTRACTION

User information: THE RUN WILL CONTINUE WITHOUT RESIDUAL VECTORS FOR THIS
SET OF MODES.

User action: POSSIBLE AVOIDANCES:

1. SET F1<=0. ON EIGR OR V1<=0. ON EIGRL.
2. SPECIFY PARAM,RESVINER,NO

9144.0
THERE ARE NO Q-SET DEGREES-OF-FREEDOM LEFT TO ACCOMMODATE ANY RESID-
UAL VECTORS.

User information: NO RESIDUAL VECTORS WILL BE COMPUTED.

9145.0
THERE ARE NOT ENOUGH Q-SET DEGREES-OF-FREEDOM DEFINED TO ACCOMMO-
DATE ALL OF THE COMPUTED FLUID AND STRUCTURE EIGENVECTORS AND/OR
RESIDUAL VECTORS.

User information: THE LAST %1 STRUCTURE MODE(S) AND THE LAST %2 FLUID MODE(S)
WILL BE TRUNCATED.

User action: SPECIFY AT LEAST %3 MORE Q-SET DEGREES-OF-FREEDOM OR REPLACE ALL

Q-SET WITH PARAM,AUTOQSET,YES

9145.1

Main Index
 MSC Nastran Error Messages 1021
Errors 9000 - 9999

THERE ARE NOT ENOUGH Q-SET DEGREES-OF-FREEDOM DEFINED TO ACCOMMO-

DATE ALL OF THE COMPUTED EIGENVECTORS AND/OR RESIDUAL VECTORS.

User information: THE LAST %1 MODE(S) ABOVE WILL BE TRUNCATED.

User action: SPECIFY AT LEAST %2 MORE Q-SET DEGREES-OF-FREEDOM OR REMOVE ALL

Q-SET SPECIFICATIONS AND INSERT PARAM,AUTOQSET,YES

9145.2
THERE ARE NOT ENOUGH Q-SET DEGREES-OF-FREEDOM DEFINED TO ACCOMMO-
DATE ALL OF THE COMPUTED EIGENVECTORS AND/OR RESIDUAL VECTORS.

User information: THE LAST %1 MODE(S) ABOVE WILL BE TRUNCATED.

User action: SPECIFY AT LEAST %2 MORE Q-SET DEGREES-OF-FREEDOM.

9145.3
THERE ARE NOT ENOUGH Q-SET DEGREES-OF-FREEDOM DEFINED TO ACCOMMO-
DATE ALL OF THE COMPUTED EIGENVECTORS AND/OR RESIDUAL VECTORS.

User information: THE LAST %1 MODE(S) ABOVE WILL BE TRUNCATED.

User action: SPECIFY AT LEAST %2 MORE Q-SET DEGREES-OF-FREEDOM OR REPLACE ALL

Q-SET WITH PARAM,AUTOQSET,YES

9145.4
THERE ARE NOT ENOUGH Q-SET DEGREES-OF-FREEDOM DEFINED TO ACCOMMO-
DATE ALL OF THE COMPUTED FLUID AND STRUCTURE EIGENVECTORS AND/OR
RESIDUAL VECTORS.

User information: THE LAST %1 STRUCTURE MODE(S) AND THE LAST %2 FLUID MODE(S)
WILL BE TRUNCATED.

User action: SPECIFY AT LEAST %3 MORE Q-SET DEGREES-OF-FREEDOM OR REPLACE ALL

Q-SET WITH PARAM,AUTOQSET,YES

9146.0

Main Index
 1022 MSC Nastran Error Messages
Errors 9000 - 9999

THE FOLLOWING DEGREES-OF-FREEDOM ARE CONSTRAINED TO PREVENT MASSLESS

MECHANISMS DURING EIGENSOLUTION.

9147.0
NO AERODYNAMIC MATRIX AJJ0 EXISTS FOR CONFIGURATION= %1

User information: THE AERODYNAMIC MODEL IS NOT FROM A RECOGNIZED THEORY, SO

IT MUST BE SUPPLIED

9148.0
ALL LINEAR SHELL ELEMENTS ARE ASSUMED TO HAVE DIFFERENT STRUCTURAL
DAMPING FOR MEMBRANE, BENDING, ETC.

9149.0
PARAM,VMOPT,2 IS SPECIFIED BUT THERE IS NO Q-SET.

User information: ACCURACY WILL BE IMPROVED IF CMS IS PERFORMED.

9151.0
USING ALTERNATE MULTIPOINT CONSTRAINT ELIMINATION

9152.0
COUPLING BETWEEN ROTOR %1 AND OTHER COMPONENTS IS DETECTED IN THE %2
MATRIX.
THIS CONNECTION MAY RESULT IN INCORRECT RESULTS. CHECK MODEL AND ROT-
ORG ENTRIES.

User information: THE FOLLOWING DOFS CONNECT TO THE ROTOR

9152.1

Main Index
 MSC Nastran Error Messages 1023
Errors 9000 - 9999

COUPLING BETWEEN ROTOR %1 AND OTHER COMPONENTS IS DETECTED IN THE %2

MATRIX.
THIS CONNECTION MAY RESULT IN INCORRECT RESULTS. CHECK MODEL AND ROT-
ORG ENTRIES.
FOR SOL 400, IF THERE ARE RIGID ELEMENTS IN THE MODEL, RIGID=LINEAR CASE
CONTROL COMMAND MUST BE USED.

User information: THE FOLLOWING DOFS CONNECT TO THE ROTOR

9153.0
THE DATA BASE IS INSUFFICIENT FOR PARAM,STIME RESTARTS.

User action: CHECK FOR COMPLETENESS AND SUCCESS OF PREVIOUS RUN.

9154.0
RESTARTING FROM STIME= %1, TSTEP= %2, DLOAD= %3, AND NLOAD= %4 IN THE PRE-
VIOUS RUN.

9154.1
IN TRANSIENT ANALYSIS, THERE ARE ROTORDYNAMIC TERMS IN THE STIFFNESS AND
DAMPING WHICH MAY VARY AS A FUNCTION OF ROTOR SPEED. AS THERE ARE NO
UPDATES TO THE DAMPING OR STIFFNESS MATRICES IN A LINEAR TRANSIENT SOLU-
TION, THESE TERMS ARE PLACED ON THE RIGHT SIDE OF THE EQUATION AND LAG BY
ONE TIME STEP. THUS USING A LINEAR TRANSIENT SOLUTION MAY NOT BE ACCU-
RATE FOR THIS PROBLEM.

User action: IT IS SUGGESTED TO PERFORM THE ANALYSIS USING A NONLINEAR TRAN-

SIENT SOLUTION.

9155.0
ENFORCED MOTION IS DETECTED IN A SUPERELEMENT.

User action: REASSIGN THE GRID POINT(S) WITH ENFORCED MOTION TO THE RESIDUAL
STRUCTURE.

9155.1

Main Index
 1024 MSC Nastran Error Messages
Errors 9000 - 9999

ENFORCED MOTION IS DETECTED IN A SUPERELEMENT AND IN A SOL 400 RUN USING

SPCD ENTRIES.

User action: CONVERT SPCD ENTRIES INTO EQUIVALENT SPC ENTRIES.

9155.2
ENFORCED MOTION IS DETECTED IN A SUPERELEMENT AND IN A SOL 400 RUN WITH
ANALYSIS = NLTR.

9155.3
AUTOQSET (PARAM,AUTOQSET,YES) IS SPECIFIED, BUT NO METHOD COMMAND IS
SPECIFIED FOR THE RESIDUAL STRUCTURE

9157.0
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
ALL MATRICES MUST BE SYMMETRIC

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.1
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
NO K2PP, M2PP, OR B2PP DMIG INPUT

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.2
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
NO EPOINT BULK DATA ENTRIES

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.3

Main Index
 MSC Nastran Error Messages 1025
Errors 9000 - 9999

FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
FLUID DAMPING CAN ONLY BE SPECIFIED BY THE PARAM,GFL ENTRY AND/OR THE
SDAMPING(FLUID) COMMAND

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.4
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
NO ACOUSTIC ABSORBERS

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.5
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
SYMMETRIC FORMULATION FOR ACOUSTIC COUPLING

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.6
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
NO DAMPING EIGENVALUES AVAILABLE
Also, if this job has external superelement(s) then damping eigenvalues may not be available in one or more
external superelements because:
1. the external superelement's files were created in MSC Nastran version 2021.2 or earlier
-or-
2. PARAM,BEIGRED,NO and PARAM,FASTFR,NO were specified in the creation run.

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.7

Main Index
 1026 MSC Nastran Error Messages
Errors 9000 - 9999

FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
THE FASTFR OPTION MAY BE TOO EXPENSIVE.

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.8
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
THE H-SIZE OF THE PROBLEM IS SMALL. H-SIZE = %1

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9157.9
FASTFR OPTION REQUESTED, BUT THE MODEL DID NOT MEET THE FOLLOWING CRI-
TERIA:
FASTFR IS CURRENTLY NOT AVAILABLE FOR FREQUENCY DEPENDENCE.

User information: STANDARD FREQUENCY RESPONSE METHOD WILL BE USED

9158.0
THE C-SET FLEXIBILITY MATRIX IS SINGULAR.

User action: EITHER SPECIFY PARAM,MHSWEEP,NO OR SPECIFY PARAM,ZROCMAS,YES TO

REMOVE THE MASS ON THE C-SET DURING COMPONENET MODES

9159.0
GENERALIZED DYNAMIC REDUCTION IS REQUESTED BUT IS NO LONGER SUPPORTED.

User action: REPLACE THE DYNRED CASE CONTROL REQUEST WITH A METHOD
REQUEST.

9160.0

Main Index
 MSC Nastran Error Messages 1027
Errors 9000 - 9999

PROBLEM ENCOUNTERED IN CALCULATING DOMAINSOLVER ACMS DOMAIN MODES.

User action: IF LARGE MASS IS BEING USED FOR ENFORCED MOTION THEN REPLACE
LARGE MASS METHOD WITH DIRECT METHOD USING THE SPCD BULK DATA ENTRY.

User information: IF THE LARGE MASS METHOD IS NOT BEING USED THEN MASSLESS
MECHANISMS MAY EXIST. PARAM,MECHFIX,YES MAY BE USED TO IDENTIFY MASSLESS
MECHANISMS.

9161.0
THE A-SET IS COMPRISED ENTIRELY OF GENERALIZED COORDINATES (Q-SET).
THEREFORE THE MEFFMASS RESULTS WILL NOT BE COMPUTED OR PRINTED.

User action: SPECIFY SOME PHYSICAL GRID POINTS ON ASETI ENTRIES.

9162.0
THERE ARE INCOMPATIABLE RECORDS IN CASECC AND CASES

9163.0
THE FOLLOWING A-SET DEGREES OF FREEDOM ARE IN CONFLICT WITH MPC AND/OR
RIGID ELEMENT SPECIFICATIONS.

9164.0
THE FOLLOWING MPC AND/OR RIGID ELEMENT EQUATIONS ARE REDUNDANT AND
WILL BE DISCARDED

9164.1
THE FOLLOWING VECTOR REPRESENTS THE CONSTANT RHS VALUE OF THE REDUN-
DANT MPCS THAT WILL BE DISCARDED

9165.0
THE NUMBER OF COLUMNS IN DMIG,UACCEL IS NOT EQUAL TO THE TOTAL NUMBER
OF LOADING CONDITIONS.

9166.0

Main Index
 1028 MSC Nastran Error Messages
Errors 9000 - 9999

THE NUMBER OF DEGREES-OF-FREEDOM ATTACHED TO VISCOUS DAMPERS=%1

EXCEEDS THE MAXIMUM ALLOWED (%2) FOR ALTERNATE DAMPING REDUCTION.

User information: ALTERNATE DAMPING REDUCTION WILL BE DEACTIVATED AND

THEREFORE RESIDUAL VECTORS DUE TO DAMPING WILL NOT BE COMPUTED AND
THE ALTERNATE FAST FREQUENCY METHOD WILL NOT BE USED.

User action: RESET PARAM,MAXDAMP BUT DOING SO MAY CAUSE TERMINATION OR

EXCESSIVE RUN TIMES WHILE PERFORMING THE ALTERNATE DAMPING REDUCTION.

9166.1
THE NUMBER OF APPLIED LOADS (%1) EXCEEDS THE MAXIMUM RECOMMENDED (%2)
FOR THE JOB TO FINISH IN A REASONABLE AMOUNT OF TIME.

User information: RESIDUAL VECTOR COMPUTATION FOR APPLIED LOADS WILL BE

DEACTIVATED AND THEREFORE WILL NOT BE COMPUTED.

User action: SET PARAM,RVLDFILT,YES TO REMOVE ANY LINEARLY DEPENDENT LOADS.

TO COMPUTE RESIDUAL VECTORS FOR ALL LOADS, USE PARAM,MAXAPL,n TO SET THE
MAXIMUM NUMBER OF APPLIED LOADS. HOWEVER, DOING SO MAY RESULT IN AN
EXCESSIVE RUN TIME.

9166.2
MULTIPLE SES WITH FSI COUPLING MATRIX DETECTED. ONLY ONE SE CAN HAVE FSI
COUPLING.

User action:
1. MERGE FSI MODEL IN MULTIPLE SEs INTO A SINGLE SE OR
2. MOVE ALL FSI, BOTH STRUCTURE AND CAVITIES MODELS, INTO RESIDUAL SE.
9167.0
THIS IS NOT A MODAL SOLUTION SEQUENCE.

User information: PARTICIPATION FACTORS WILL NOT BE COMPUTED.

9167.1

Main Index
 MSC Nastran Error Messages 1029
Errors 9000 - 9999

THERE ARE NO STRUCTURAL MODES.

User information: MODAL PARTICIPATION FACTORS WILL NOT BE COMPUTED, FOR THE
STRUCTURE OR THE PANELS.

9167.2
THERE ARE NO FLUID MODES.

User information: ACOUSTIC MODAL PARTICIPATION FACTORS WILL NOT BE COM-

PUTED.

9167.3
THERE IS NO COUPLED FLUID-STRUCTURE MODEL.

User information: ACOUSTIC MODAL PARTICiPATION FACTORS WILL NOT BE COMPUTED

FOR THE STRUCTURE OR THE PANELS.

9167.4
THIS IS NOT A FREQUENCY RESPONSE ANALYSIS.

User information: ACOUSTIC MODAL PARTICiPATION FACTORS WILL NOT BE COMPUTED

FOR THE STRUCTURE OR THE PANELS.

9167.5
THERE ARE NO PANELS.

User information: PANEL PARTICIPATION FACTORS WILL NOT BE COMPUTED.

9167.6
THE REQUESTED SET OF GRIDS ARE NOT VALID FOR THE COMPUTATION OF PARTICI-
PATION FACTORS.

User information: PARTICIPATION FACTORS WILL NOT BE COMPUTED.

9168.0

Main Index
 1030 MSC Nastran Error Messages
Errors 9000 - 9999

P-ELEMENTS are detected.

User information: This is not supported with the CASI Element-Based iterative solver.

User action: Request the Matrix-Based solver.

9168.1
Superelements are detected.

User information: This is not supported with the CASI Element-Based iterative solver.

User action: Request the Matrix-Based solver.

9168.2
GENEL BULK DATA ENTRY IS DETECTED.

User information: THIS IS NOT SUPPORTED WITH THE CASI ELEMENT-BASED ITERATIVE
SOLVER.

User action: SPECIFY THE MATRIX BASED SOLVER

9168.10
SOME DEGREES-OF-FREEDOM ARE OMITTED FROM THE ANALYSIS VIA ASETi AND/OR
OMITi BULK DATA ENTRIES

User information: THIS IS NOT SUPPORTED WITH THE CASI ELEMENT-BASED ITERATIVE
SOLVER.

User action: SPECIFY THE MATRIX BASED SOLVER

9168.11
SOME DEGREES-OF-FREEDOM ARE SPECIFIED ON SUPORTi BULK DATA ENTRIES

User information: THIS IS NOT SUPPORTED WITH THE CASI ELEMENT-BASED ITERATIVE
SOLVER UNLESS INREL=-1

User action: SET INREL TO -1 AND INCLUDE A SUPORT ENTRY

Main Index
 MSC Nastran Error Messages 1031
Errors 9000 - 9999

9168.12
PARAM,INREL,%1 HAS BEEN SPECIFIED FOR INERTIA RELIEF USING THE CASI SOLVER.

User information: THIS IS NOT SUPPORTED WITH THE CASI ELEMENT-BASED ITERATIVE
SOLVER.

User action: SET INREL TO -1 AND INCLUDE A SUPORT ENTRY

9169.0
Omitted Degrees-Of-Freedom are not supported in SOL101 Linear Contact.

User action: Remove all Bulk Data entries that create an O-set: ASETi, OMITi, BSETi, CSETi,
SUPORTi, etc.

9169.1
CONTACT ANALYSIS IN SUBCASE %1 HAS GENERATED ONE OR MORE FATAL ERRORS.
CHECK ABOVE FOR THE FATAL ERROR MESSAGE(S).

9170.0
Omitted Degrees-Of-Freedom are not supported IN THIS SOLUTION SEQUENCE.

User action: Remove all Bulk Data entries that create an O-set: ASETi, OMITi, BSETi, CSETi,
SUPORTi, etc.

9171.0
SOL 400 DOES NOT SUPPORT PARAMETER OGRAV >0 WHEN ANALYSIS=NLTRAN.
ANY GRAVITY VECTOR IN DATA BLOCK PGGRAV IS SET TO NULL WHEN ITS CORRE-
SPONDING ANALYSIS=NLTRAN.

9172.0
CONVERGENCE FAILURE: THE NUMBER OFRANDOM VECTORS EXCEEDS CDITER

9173.0

Main Index
 1032 MSC Nastran Error Messages
Errors 9000 - 9999

ND IS SPECIFIED ON EIGRL ENTRY = %1

User information: THE NON-ZERO VALUE FOR ND IS NOT SUPPORTED AND WILL BE
IGNORED WITH THIS DOMAINSOLVER OPTION.

9174.0
THERE ARE NO BOUNDARY GRID POINTS DEFINED FOR EXTERNAL SUPERELEMENT
CREATION.

User action: CHECK ASETI, BSETI, CSETI, BNDFIXI, AND BNDFREEI ENTRIES.

9174.1
THERE ARE NO BOUNDARY GRID POINTS DEFINED FOR EXTERNAL SUPERELEMENT
CREATION.

User action: SPECIFY ASMBULK=MANQ OR CHECK ASETI, BSETI, CSETI, BNDFIXI, AND
BNDFREEI ENTRIES.

9175.0
The METHOD command in a nonlinear buckling analysis is requesting EIGB Bulk Data entry with
METHOD=INV.

User information: Nonlinear buckling analysis supports only EIGB with METHOD=SINV, EIGR with
METHOD=LAN, or EIGRL. No eigenvalues will be computed.

9176.0
A STATIC AEROELASTIC ANALYSIS IS BEING PERFORMED ON A VEHICLE WITH NO
MASS.

User action: PROVIDE INERTIA DATA FOR THE MODEL.

9177.0
INERTIA RELIEF WITH AUTO-SUPORT (PARAM,INREL,-2) IS NOT ALLOWED IN BUCK-
LING ANALYSIS.

9177.1

Main Index
 MSC Nastran Error Messages 1033
Errors 9000 - 9999

NO STATIC SUBCASE (ANALYSIS=STATICS) HAS BEEN SPECIFIED FOR BUCKLING ANALY-

SIS.

9177.2
INERTIA RELIEF WITH SUPORT OR SUPORT1 (PARAM,INREL,-2) IS NOT ALLOWED IN
STATICS.

9178.0
BOTH PARAM,AUTOQSET,YES IS SPECIFIED AND Q-SETS HAVE ALSO BEEN DEFINED.

User action: REMOVE ONE OR THE OTHER.

9178.1
AUTOQSET (PARAM,AUTOQSET)is requested but no method command is present for the residual
structure.

User action: Either remove PARAM,AUTOQSET or add a request for cms for the residual structure.

9179.0
SCR=YES IS DETECTED FOR AN AESO RUN.

User information: NO DATABASE WILL BE SAVED.

9179.1
AESO DOES NOT SUPPORT TOPOLOGY, TOPOMETRY OR TOPOGRAPHY OPTIMIZATION

User action: USE EXTERNAL SE OR DO NOT USE AESO FOR TOPOLOGY, TOPOMETRY AND
TOPOGRAPHY OPTIMIZATION

9179.2
THERMAL LOADS ARE NOT SUPPORTED IN TOPOLOGY, TOPOMETRY OR TOPOGRA-
PHY OPTIMIZATION.

9180.0

Main Index
 1034 MSC Nastran Error Messages
Errors 9000 - 9999

THE RATIO OF THE SIZE OF THE DESIGNED PORTION OF THE MODEL TO THE NON-
DESIGNED PORTION IS GREATER THAN THE VALUE OF DRATIO: %1

User action: EITHER REMOVE AUTOSE FROM DOPTPRM OR INCREASE DRATIO

9181.0
THE JOB IS TERMINATED FOR AN AUTO EXTERNAL CREATION RUN

9182.0
NO DOWNWASH LOAD DUE TO GUST REQUEST %1 HAS BEEN COMPUTED.

User action: CHECK GUST2 BULK ENTRY %2

9183.0
AT HOT-TO-COLD CYCLE= %1 MAXIMUM GEOMETRY ERROR= %2

9184.0
ANALYSIS= %1 APPEARS IN FIRST SUBCASE

9185.0
MPCY/MPCD ENTRIES ARE SPECIFIED FOR A NON-STATIC ANALYSIS.

User action: REMOVE THESE ENTRIES

9186.0
ADBQKV0 IS EXPECTED TO BE ON THE ADBD, BUT IT DOES NOT EXIST.
IMACHNO = %1
AECONFIG = %2
SYMXY = %3
SYMXZ = %4
AESOLN = %5

9187.0
THERE ARE NO NONLINEAR DEGREES OF FREEDOM FOR NONLINEAR HARMONIC
RESPONSE ANALYSIS

9187.1

Main Index
 MSC Nastran Error Messages 1035
Errors 9000 - 9999

NLHARM IS NOT DEFINED IN CASE CONTROL. LINEAR FREQUENCY RESPONSE ANALY-

SIS WILL BE PERFORMED.

9187.2
NLHARM IS NOT DEFINED IN CASE CONTROL. LINEAR FREQUENCY RESPONSE ANALY-
SIS WILL BE PERFORMED.
FOR CORRECT ANALYSIS, NHARM SHOULD BE GREATER THAN OR EQUAL TO SUBFAC.

9188.0
RESIDUAL VECTORS ARE NOT BEING REQUESTED WITH VIRTUAL MASS METHOD 2
(PARAM,VMOPT,2).

User action: DO NOT TURN OFF RESIDUAL VECTORS.

9189.0
ALTERNATE DAMPING REDUCTION IS REQUESTED WITH SUPERELEMENT MODAL
DAMPING

User information: ALTERNATE DAMPING REDUCTION WILL BE DEACTIVATED AND THE

ALTERNATE FAST FREQUENCY METHOD WILL NOT BE USED.

9190.0
XITOUT KEYWORD IS NOT SPECIFIED IN THE FRF CASE CONTROL COMMAND AND
USER LOADS ARE DEFINED.
XITOUT = USER WILL THEREFORE BE ASSUMED.

9190.1
XITOUT KEYWORD IS NOT SPECIFIED IN THE FRF CASE CONTROL COMMAND AND NO
USER LOADS ARE DEFINED.

9191.0
XITOUT = %1 IS SPECIFIED IN THE FRF CASE CONTROL COMMAND BUT NO USER
LOADS ARE DEFINED.

9192.0

Main Index
 1036 MSC Nastran Error Messages
Errors 9000 - 9999

THE %1 DMIG MATRIX IS NOT SYMMETRIC IN SOL 400 ALONG WITH A REQUEST FOR
THE CASI ITERATIVE SOLVER.

User action: DO NOT REQUEST THE CASI ITERATIVE SOLVER.

9192.1
FOLLOWER LOAD OR TF ENTRIES ARE PRESENT IN SOL 400 ALONG WITH A REQUEST
FOR THE CASI ITERATIVE SOLVER.

User action: DO NOT REQUEST THE CASI ITERATIVE SOLVER OR SPECIFY PARAM,FOL-
LOWK,NO TO CONTINUE WITHOUT FOLLOWER STIFFNESS.

9193.0
IN SCALED RESPONSE SPECTRA ANALYSIS, THE CALCULATION OF SPCFORCES AND
MPCFORCES DOES NOT INCLUDE COUPLING DUE TO MASS, DAMPING, M2PP, B2PP, OR
K2PP.

9194.0 *** USER FATAL MESSAGE 9194 (SUBDMAP NLIC):

NLIC in SUBCASE %1 references an invalid STEP ID %2

9194.1
NLIC IN SUBCASE, %1 REFERENCES AN INVALID STEP ID, %2

9194.2
NLIC IN SUBCASE, %1, STEP, %2 REFERENCES AN INVALID SUBCASE ID, %3

9194.3
NLIC IN SUBCASE, %1, STEP, %2 REFERENCES AN INVALID STEP ID, %3

9194.4
THE LINEAR PERTURBATION ANALYSIS REFERENCES AN INVALID NONLINEAR STATIC
STEP.

9194.5
NLIC AND STATSUB ARE PRESENT IN SAME STEP %1 OF SUBCASE %2

9194.6

Main Index
 MSC Nastran Error Messages 1037
Errors 9000 - 9999

NLIC STEP ID %1 OF SUBCASE %2 REFERENCES INTO STEP %3 ID %4 OF SUBCASE %5

9194.7
STEP ID %1 OF SUBCASE %2, FOLLOWED BY A %3 STEP, HAS NOT NLIC STATEMENT

9195.0
A LINEAR PERTURBATION ANALYSIS APPEARS IN THE FIRST STEP OF SUBCASE %1

9196.0
A REQUEST IS MADE TO CHAIN FROM STEP %1 TO STEP %2

User information: THE NLIC CASE CONTROL COMMAND CAN ONLY BE APPLIED IN THE
FOLLOWING THREE CHAINED ANALYSES.
1. FROM NONLINEAR STATIC ANALYSIS (NLST) TO NONLINEAR STATIC ANALYSIS
(NLST).
2. FROM NONLINEAR STATIC ANALYSIS (NLST) TO NONLINEAR TRANSIENT
ANALYSIS (NLTR).
3. FROM LINEAR STATIC ANALYSIS (LNST) TO LINEAR STATIC ANALYSIS (LNST).
ANY OTHER TYPE OF CHAINED ANALYSIS IS NOT ALLOWED.

9197.0
THE SIZE OF MDF IS SMALLER THAN MODE SHAPES IN DATABASE.
MDF WILL BE EXPANDED TO FIT THE NUMBER OF MODES.
THE SIZE OF MDF: %1
THE SIZE OF MODE SHAPE: %2

9198.0
MDF IS INCOMPATIBLE WITH MODE SHAPES IN THE DATABASE.
THE SIZE OF MDF: %1
HE SIZE OF MODE SHAPE: %2

User action: PLEASE CHECK THE ORIGINAL DATA.

9199.0

Main Index
 1038 MSC Nastran Error Messages
Errors 9000 - 9999

RANDOM case control command references ID=%1 which does not refer to RANDPS bulk data entry
but does refer to a SET case control command. The program will loop on RANDPS IDs specified on the
SET command.

9200.0
BEGIN PROCESSING RANDOM SET ID=%1

9201.0
ONE OR MORE POINT IDS ENCOUNTERED IN THIS EXTERNAL SUPERELEMENT CRE-
ATION RUN ARE IN THE RANGE OF %1 THRU %2
THESE IDS MAY BE IN CONFLICT WITH THE IDS OF Q-SET DOFS THAT WILL BE AUTO-
MATICALLY GENERATED AS A RESULT OF PARAM,AUTOQSET,YES USAGE

User action: CHANGE THE IDS OF THE POINTS TO AVOID THE ABOVE CONFLICT OR
EMPLOY MANUAL Q-SET USAGE

9201.1
ONE OR MORE POINT IDS ENCOUNTERED IN THIS EXTERNAL SUPERELEMENT CRE-
ATION RUN ARE GREATER THAN 99999999.

9201.2
DOMAINSOLVER MODES (PARTOPT=DOF) OR DOMAINSOLVER MODES (PAR-
TOPT=GRID) HAS BEEN REQUESTED FOR EXTERNAL SUPERELEMENT CREATION.

User action: REMOVE REQUEST FOR DOMAINSOLVER MODES (PARTOPT=GRID) AND

DOMAINSOLVER MODES (PARTOPT=DOF)

9202.0
NO ELEMENTS MEET THE REFINEMENT CRITERION.

9203.0
NO ELEMENTS HAVE BEEN REFINED BECAUSE ALL ELEMENTS HAVE REACHED THE
MAXIMUM REFINEMENT LEVEL (MAXLEVEL = %1)

9204.0

Main Index
 MSC Nastran Error Messages 1039
Errors 9000 - 9999

ADBM AND SDB DEGREE-OF-FREEDOM COUNTS DO NOT MATCH:

SIZE OF ADBM REFERENCE MODE MATRIX = %1
SIZE OF SDB MATRICES = %2
ENSURE THAT THE GRIDS AND SPOINTS ARE IDENTICAL BETWEEN THE ADBM AND
SDB.

9205.0
PARAM,AUTOQSET,YES IS REQUESTED IN THE PRESENCE OF SUPERELEMENTS WITH
SECSETI OR SESUP BULK DATA ENTRIES OR PART SUPERELEMENTS WITH CSETI, BND-
FREEI OR SUPORTI ENTRIES.

9206.0
THIS RUN IS TERMINATED DUE TO THE POSSIBILITY OF WRONG RESULTS IN THE FBA
PROCESS

User action: CHECK THE INPUT DATA FOR THIS RUN AS WELL AS THE RESULTS OF THE
FRF GENERATION JOBS OF THE CONSTITUENT FRF COMPONENTS FOR POSSIBLE
ERRORS AND DISCREPANCIES

9206.1
MULTIPLE BOUNDARY CONDITIONS WITH SUPERELEMENTS IS DETECTED WITH
ADJOINT LOAD METHOD.
DIRECT METHOD WILL BE UTILIZED FOR SENSITIVITY COMPUTATION.

9207.0
THIS FBA JOB HAS NULL APPLIED LOADS SPECIFIED FOR IT.
THE RESULT WILL THEREFORE BE A ZERO SOLUTION.

9208.0
THE FOLLOWING AUTOSPC DEGREES OF FREEDOM HAVE NON-ZERO TERMS IN THE
MPC AND/OR RIGID ELEMENT SPECIFICATIONS.

9208.1
THE COMPLETE EQUATION ASSOCIATED WITH THESE DEGREES OF FREEDOM
FOLLOWS:

Main Index
 1040 MSC Nastran Error Messages
Errors 9000 - 9999

9208.2
User action: CHECK THE MODEL AND MPC/RIGID ELEMENT SPECIFICATIONS TO INSURE
THAT THIS WILL NOT CAUSE GROUNDING OF THE MODEL AND LOSS OF LOAD OR
MASS AT THE AUTOSPC DEGREES OF FREEDOM

9209.0
JOB IS BEING TERMINATED AS THE USER HAS SPECIFIED ASMOUT=CONNINFO IN THE
FRF CASE CONTROL COMMAND

9210.0
JOB IS BEING TERMINATED AS THE VALUE SPECIFIED FOR THE ASMOUT KEYWORD IN
THE FRF CASE CONTROL COMMAND DOES NOT REFERENCE ANY VALID FRF COMPO-
NENT IN THIS FRF ASSEMBLY PROCESS

9211.0
LINEAR STRESS TABLE IS USED IN ESLOPT

9212.0
CONSTRAINED DISPLACEMENT ITERATIONS (PARAM,CDITER) IS REQUESTED IN A
SOLUTION SEQUENCE OTHER THAN SOL 101.

9212.1
CONSTRAINED DISPLACEMENT ITERATIONS (PARAM,CDITER) DOES NOT SUPPORT
FOR PARALLEL PROCESSING (DMP).

User action: IN ORDER TO RUN WITH PARAM,CDITER,YES, DO NOT REQUEST PARALLEL

PROCESSING.

9213.0
THERE IS A DESMOD CASE CONTROL COMMAND BUT THE MULTIOPT FEATURE IS
NOT ACTIVATED

User action: REMOVE THE DESMOD COMMAND.

9214.0
THERE ARE FEWER DESIGN VARIABLES (%1) THAN THE NUMBER OF PROCESSORS (%2).
DOMAINSOLVER DSA WILL BE DEACTIVATED.

Main Index
 MSC Nastran Error Messages 1041
Errors 9000 - 9999

9215.0
TEST FRF COMPONENT %1 %2 DOES NOT HAVE ANY FRF DATA SPECIFIED ON ITS UNI-
VERSAL FILE (FORTRAN UNIT NUMBER = %3)

User action: CHECK THE CONTENTS OF THE UNIVERSAL FILE

9216.0
MATRIX %1 IS SINGULAR AND SOLUTION CANNOT CONTINUE.

9217.0
BASE %1 IS MISSING.

9218.0
THERE IS A %1 MATRIX ON THE DBLOCATED DATABASE, WHICH INDICATES THAT THE
DATABASE IS OF TYPE SLIM.
IT IS ADVISED THAT THE UNRESTRAINED STABILITY DERIVATIVES ARE NOT CORRECT
IN THIS CASE AND NO STANDARD DATA RECOVERY WILL BE PERFORMED.
TRIM AND MONITOR POINT RESULTS ARE CONSIDERED TO BE ACCURATE.

9219.0
MASSSET= %1 WAS NOT FOUND

9220.0
scr=mini is not permitted with external superelement creation (PARM,EXTOUT or EXTSEOUT or EXT-
MDOUT command).
Resubmit with scr=no or yes.

9221.0
%1 SPANS FLUID/STRUCTURE.
THIS IS NOT ALLOWED IN SYMMETRIC FORMULATION.
RESUBMIT WITH PARAM,ACSYM,NO.

9222.0

Main Index
 1042 MSC Nastran Error Messages
Errors 9000 - 9999

A DISCREPANCY BETWEEN ANALYSIS AND DESIGN MODEL WAS FOUND DURING THE
PROCESSING OF SEDLINK AND/OR IMPLIED DLINK SENSITIVITY OF FIRST CYCLE MAY
NOT BE CORRECT

9223.0
RIGID BODY MOTION CHECK PRODUCED STRAIN ENERGY IN ALL DEGREES OF FREE-
DOM. THIS MODEL HAS NO RIGID BODY DEGREES OF FREEDOM TO SUPPORT. PLEASE
CHECK THAT THE SUPPORTED DEGREES OF FREEDOM ARE FREE TO MOVE.

9224.0
THIS RUN IS TERMINATED BECAUSE ONE OR MORE SUBCASE NUMBERS EXCEED 9999

User information:
WHEN XITOUT = USER OR XITOUT = USERTOTL IS SPECIFIED IN THE FRF CASE CON-
TROL COMMAND, THE SUBCASE NUMBERS MAY NOT EXCEED 9999

9224.1
THIS RUN IS TERMINATED BECAUSE ONE OR MORE SUBCASE NUMBERS EXCEED 9999

User information:
WHEN XITOUT = USER IS ASSUMED FOR THE FRF CASE CONTROL COMMAND, THE
SUBCASE NUMBERS MAY NOT EXCEED 9999

9225.0
THE PUNCH FILE CONTAINS DMI ENTRIES FOR THE OTM MATRICES.

User information: DUE TO CR 1-247570721, THE DMI ENTRIES ARE AN OBSOLETE FORMAT
FOR OTM MATRICES AND THEREFORE DATA RECOVERY FOR INTERIOR ELEMENTS
AND GRIDS WILL BE SKIPPED.

User action: RERUN THE EXTSEOUT or EXTMDOUT(DMIGPCH) JOB TO RECREATE THE

PUNCH FILE.

9226.0

Main Index
 MSC Nastran Error Messages 1043
Errors 9000 - 9999

AN UNSYMMETRIC STIFFNESS MATRIX IS DETECTED IN A MODAL SOLUTION OR YOUR

INPUT REQUIRES A REDUCTION

User information: THIS CAN RESULT IN WRONG ANSWERS OR FATAL ERRORS LATER IN
THE RUN.

User action: TO CONTINUE THE RUN SPECIFY USER PARAMETER UNSYMKB TO YES

9226.1
AN UNSYMMETRIC STIFFNESS MATRIX IS DETECTED IN A MODAL SOLUTION OR YOUR
INPUT REQUIRES A REDUCTION SINCE USER PARAMETER UNSYMKB IS SET TO YES THE
RUN WILL CONTINUE, BUT MAY RESULT IN WRONG ANSWERS OR FATAL ERRORS
LATER IN THE RUN.

9226.2
AN UNSYMMETRIC DAMPING MATRIX IS DETECTED IN A MODAL SOLUTION OR YOUR
INPUT REQUIRES A REDUCTION

User information: THIS CAN RESULT IN WRONG ANSWERS OR FATAL ERRORS LATER IN
THE RUN.

User action: TO CONTINUE THE RUN SPECIFY USER PARAMETER UNSYMKB TO YES

9226.3
AN UNSYMMETRIC DAMPING MATRIX IS DETECTED IN A MODAL SOLUTION OR YOUR
INPUT REQUIRES A REDUCTION SINCE USER PARAMETER UNSYMKB IS SET TO YES THE
RUN WILL CONTINUE, BUT MAY RESULT IN WRONG ANSWERS OR FATAL ERRORS
LATER IN THE RUN.

9226.5
AN UNSYMMETRIC STIFFNESS MATRIX IS DETECTED.

User information: THIS MAY RESULT IN INEFFICIENT PROCESSING, WRONG ANSWERS, OR

FATAL ERRORS LATER IN THE RUN.
ROTORDYNAMIC MODEL TEND TO HAVE UNSYMMETRIC STIFFNESS MATRIX. VERIFY
PARAMETER UNSYMKB SET TO YES.

Main Index
 1044 MSC Nastran Error Messages
Errors 9000 - 9999

9226.6
AN UNSYMMETRIC DAMPING MATRIX IS DETECTED.

User information: THIS MAY RESULT IN INEFFICIENT PROCESSING, WRONG ANSWERS, OR

FATAL ERRORS LATER IN THE RUN.
ROTORDYNAMIC MODEL TEND TO HAVE UNSYMMETRIC DAMPING MATRIX. VERIFY
PARAMETER UNSYMKB SET TO YES.

9227.0
PARAM AUTOADJ,NO IS BEING REQUESTED ALONG WITH AN RMS OR PSD RESPONSE
TYPE

User action: REMOVE PARAM,AUTODDJ,NO OR CHANGE THE RESPONSE TYPES

9227.1
PARAM, AUTOADJ, YES IS BEING REQUESTED WHEN GRID POINT CONNECTING RIGID
ELEMENT IS BEING DESIGNED ALONG WITH AN RMS OR PSD RESPONSE TYPE.

User action: CHANGE THE RESPONSE TYPES.

9228.0
THERE IS A DESMOD CASE CONTROL COMMAND AND FULLY STRESSED DESIGN IS
REQUESTED.

User information: FULLY STRESSED DESIGN IS NOT SUPPORTED WITH MULTIOPT.

9229.0
TEST FRF COMPONENT %1 (%2) DOES NOT HAVE ANY CONNECTION POINTS DEFINED
ON ITS UNIVERSAL FILE (FORTRAN UNIT NUMBER %3)

User information: A POINT REFERENCED ON AN UNIVERSAL FILE IS REGARDED AS A CON-

NECTION POINT IF IT IS EMPLOYED BOTH AS A RESPONSE POINT AND AS AN EXCI-
TATION POINT. THERE ARE NO SUCH POINTS ON THE UNIVERSAL FILE SPECIFIED BY
FORTRAN UNIT NUMBER %3

9229.1

Main Index
 MSC Nastran Error Messages 1045
Errors 9000 - 9999

ICFUSE SPECIFICATION IN THE FRF CASE CONTROL COMMAND INCLUDES ALL FRF
COMPONENTS IN THE CONFIGURATION

User information: WHEN ICFGEN IS SPECIFIED IN THE FRF CASE CONTROL COMMAND,
THE ICFUSE SPECIFICATION MAY APPLY ONLY TO A SUBSET OF THE FRF COMPONENTS
IN THE CONFIGURATION

9230.0
OMODES COMMAND IS DETECTED IN THE CASE CONTROL SECTION BUT IS NOT SUP-
PORTED IN SOL200 WHEN OPTEXIT<>2.

User action: TO CONTINUE, REMOVE THE OMODES COMMAND OR SET OPTEXIT=2.

9230.1
MODAL FORMULATION FOR TRIM COMPONENTS IS NOT SUPPORTED IN SOL200.

User action: USE PARAM,TRMBIM,PHYSICAL WHICH IS THE DEFAULT.

9230.2
FATIGUE OPTIMIZATION CANNOT SUPPORT MULTIPLE FATIGUE ANALYSES.

9230.3
ANALYTIC SHAPE OPTIMIZATION DOES NOT SUPPORT INERTIA RELIEF.

User action: USE MANUAL GRID VARIATION DVGRID.

9230.4
DESIGN OPTIMIZATION SOL200 DOES NOT SUPPORT GENERAL CONTACT (TOUCHING)

User action: RUN USING PERMANENT GLUED CONTACT OR USE SOL 400 WITH THE ESL-
NRO OPTION.

9231.0

Main Index
 1046 MSC Nastran Error Messages
Errors 9000 - 9999

THERE EXISTS UNBALNC AND EPOINT ENTRIES BUT NO NOLINI OR NLRGAP ENTRIES
FOR THE NONLINEAR CASE CONTROL COMMAND TO PROCESS.

User action: REMOVE THE NONLINEAR CASE CONTROL COMMAND.

9232.0
ENFORCE MOTION IS INCONSISTENT WITH THE INITIAL CONDITION IN TRANSIENT
ANALYSIS.
CONSIDER USING SPCR FOR ENFORCED RELATIVE MOTION.

9232.1
THE FOLLOWING DOF(S) INDICATE THE DIFFERENCES THAT ARE LARGER THAN 0.001

9233.0
AUTOSPC(MPC) CASE CONTROL COMMAND IS SPECIFIED WITH PARAM,AUTOMSET,YES
WHICH IS NOT ALLOWED.

9234.0
Param,autoqset,yes is specified after BEGIN SUPER but not in the main Bulk Data or residual structure's
subcase.

User action: Param,autoqset,yes should only be specified in either the residual structure's subcase or the
main Bulk Data sections.

9235.0
A CHANGE IN BOUNDARY CONDITION COMMAND(S), SINCE THE LAST RUN, HAS BEEN
DETECTED.
OLD: SPC= %1 MPC= %2 SUPORT= %3
NEW: SPC= %4 MPC= %5 SUPORT= %6

User action: REMOVE BOUNDARY CONDITION COMMANDS OR START WITH A NEW

DATABASE.

9236.0

Main Index
 MSC Nastran Error Messages 1047
Errors 9000 - 9999

BOTH GRID LIST AND PART SUPERELEMENTS ARE PRESENT IN %1 ANALYSIS.

User information: GRID LIST SUPERELEMENTS ARE CREATED WITH seset ENTRIES OR
FIELD 9 ON THE GRID ENTRY.
PART SUPERELEMENTS ARE CREATED WITH THE BEGIN SUPER COMMAND.

User action: CONVERT ALL SUPERELEMENTS TO ONE TYPE.

9237.0
IN DIRECT FREQUENCY ANALYSIS, THE SDAMPING CASE CONTROL COMMAND
REQUESTS THE MISSING TABLEDI ENTRIES SHOWN ABOVE.

User information: SDAMPING=n IN DIRECT FREQUENCY ANALYSIS ACTIVATES VISCOELAS-

TIC MATERIAL ANALYSIS WHICH REQUIRES THE SPECIFICATION OF TABLEDI ENTRIES
with TID=n and TID=n+1 THAT DEFINE THE complex shear moduli of the VISCOELASTIC MATE-
RIAL.

User action: IF VISCOELASTIC ANALYSIS IS NOT REQUIRED THEN REMOVE THE SDAMP-
ING COMMAND.

9238.0
GENERAL CONTACT IS REQUESTED IN PRELOAD OR BUCKLING ANALYSIS.

User action: REMOVE THE BCONTACT REQUEST

9239.0
DIFFERENTIAL STIFFNESS REDUCTION USING STATIC CONDENSATION IS APPROXI-
MATE AND MAY LEAD TO POOR RESULTS IN SOME CASES.

9240.0
THE STIFFNESS MATRIX IS UNSYMMETRIC.

User information: RUN TERMINATED BECAUSE THE DIRECT UNSYMMETRIC SOLVER IS

NOT SUPPORTED IN STATIC ANALYSIS.

User action: IF THIS OPTION IS DESIRED, THEN USE THE ITERATIVESOLVER.

Main Index
 1048 MSC Nastran Error Messages
Errors 9000 - 9999

9241.0
SPC ENTRIES MUST BE CONVERTED TO SPC1/SPCD ENTRIES WHEN SPCD ENTRIES
EXIST INSOL 400 TRANSIENT THERMAL ANALYSIS.

9242.0
NASTRAN CURRENTLY DOES NOT SUPPORT INTERMEDIATE OR SOLUTION SET OUT-
PUT FOR HEAT FLUX.

9243.0
PARAM,AUTOMSET,YES IS BEING REQUESTED IN SOL 400 (OR SOL 101 WITH CONTACT)
AND RIGID=LINEAR.

User action: IF AUTO-MSET IS REQUIRED, THEN SET RIGID=LAGR IN CASE CONTROL.

9244.0
STATSUB selects a subcase with null displacements and therefore differential stiffness cannot be com-
puted.
If the solution sequence is SOL 103 and the subcase with the STATSUB is not intended for differential
stiffness then replace the STATSUB command with the BC command.

9245.0
THE REDUCED BASIS VECTORS ARE NULL.

User action: CHECK THE AERODYNAMIC MODEL. PARAM,AESMETH,DIRECT MAY BE

USED TO HELP DIAGNOSE THE PROBLEM.

9245.1
AN AEROELASTIC ANALYSIS IS BEING PERFROMED, BUT THERE ARE NO AERODYNAMIC
LOADS.

User information: FOR INTERNAL AERODYNAMICS, AERODYNAMICS ARE GENERATED

FORM THE AERODYNAMIC MODEL DRIVEN BY CAEROx ENTRIES.
FOR EXTERNAL AERODYNAMICS, THE USER MUST PROVIDE THE AERODYNAMICS
USING DMIK ENTRIES OR SOME OTHER MEANS.

9246.0

Main Index
 MSC Nastran Error Messages 1049
Errors 9000 - 9999

PARAM %1 is changing between subcases.

User action: Specify PARAM %1 above all subcases or in the main Bulk Data section.

9247.0
ADVANCED NONLINEAR ELEMENTS REFERENCED BYPRODN1,PBEMN1,PSHEARN,PSH-
LN1,PSHLN2 OR PSLDN1 ARE PRESENT

User information: THESE ELEMENTS ARE NOT SUPPORTED IN TOPOLOGY OPTIMIZATION

User action: REMOVE THESE PROPERTY ENTRIES.

9247.1
A SOL 200 RUN CONTAINS A RIGID=LAGRANGE OR RIGID=LGELIM OPTION IN CASE
CONTROL.

User information: THESE OPTIONS ARE NOT SUPPORTED IN SOL 200.

9247.2
A SOL 200 RUN CONTAINS ANALYSIS=NLSTATIC IN CASE CONTROL.

User information: SOL 200 DOES NOT SUPPORT ANALYSIS=NLSTATIC, SOL 400 DOES.

9247.3
A SOL 200 RUN CONTAINS SOLADJC = %1 AND FREQ3/4/5 ENTRIES.

User information: FREQ3/4/5 CAN CHANGE THE NUMBER OF ADJOINT SOLUTION VEC-
TORS THAT NEED TO BE CALCULATED DURING THE ANALYSIS AND THIS IS NOT SUP-
PORTED IN SOLUTION 200.

User action: EITHER REMOVE THE SOLADJC REQUEST OR THE FREQ3/4/5 ENTRIES.

9248.0

Main Index
 1050 MSC Nastran Error Messages
Errors 9000 - 9999

THE NUMBER OF PROCESSORS INPUT TO SUBDMAP LOGX, %1, IS NOT A POWER OF 2

WHICH INDICATES A LOGIC ERROR IN THE ACMS TREE STRUCTURE.

User action: PLEASE RE-SUBMIT THE JOB WHERE THE NUMBER OF PROCESSORS IS A
POWER OF 2 (FOR EXAMPLE: DMP=4 OR DMP=8)

9249.0
%1 Bulk Data entry is present but no BEGIN MODULE sections have been defined.

9250.0
THERMAL CONTACT WITH RADIATION BOUNDARY CONDITIONS RADBC MAY CAUSE
A SINGULAR MATRIX IN NLSOLV MODULE.

User information: DEFINE RADIATION BOUNDARY CONDITIONS USING BCTABLE AND

BCBODY ENTRIES TO AVOID THIS ERROR.

9251.0
The differential stiffness matrix is null for buckling analysis. Therefore no eigenvalues will be computed.

User information: This may be caused by one or more of the following:

1. Elements in the model do not have a differential stiffness formulation.
2. If all elements are linear then PARAM,LGDISP,1 may be needed.
3. Nonlinear static analysis results in zero displacements. Check static loads.

9260.0
CANNOT ASK FOR IDEAS FREQUENCY RESPONSE AND VIBRATIONS OUTPUT IN THE
SAME SUBCASE

9261.0 *** User information MESSAGE 9261 (SUBDMAP MGEN2O/MGEN2X)

RIGID BODY VIRTUAL MASS MATRIX, IN WEIGHT UNITS

9262.0

Main Index
 MSC Nastran Error Messages 1051
Errors 9000 - 9999

THE DMIG ENTRY REFERENCED BY P2G=%1 CASE CONTROL COMMAND HAS MORE
THAN ONE COLUMN.

User information: In SOL 400, P2G may be specified inside of a subcase, or step, as long as the referenced
DMIG entry specifies only one column (NCOL=1). Alternatively, P2G may be specified above all subcases
and steps, in which case, NCOL is set to the total number of subcases and steps and the column index (GJ
on DMIG) corresponds to the desired subcase's or step's index; i.e., its position relative to the first subcase
or step.

9263.0
The number of columns (%1) specified in NCOL for the DMIG entry referenced by P2G Case Contol
command does not match the number of STEPs and/or SUBCASEs (%2).

9264.0 *** System Warning Message 9264 (EXTOUT)

Thermal or element deformation loads are detected and element forces or stresses are requested while crea
ing an external superelement.

User information: Element stress and force data will not be stored on the requested output media and
therefore element stresses/forces will not be computed for the external superelement in the assembly run.

9265.0 *** User Fatal Message 9265 (EXTOUT)

The boundary stiffness matrix is null and not suitable for assembly into a downstream superelement.

User action: Check the geometry, connectivity, properties, constraints and boundary definition.

9266.0
PARAM,INREL,-1 and a SUPORT1 Case Control command is active in a buckling subcase.

User action: Specify the SUPORT1 Case Control command in only the static subcases. You may have to
also request SPCi for the SUPORTed DOFs in the buckling subcases.

9266.1
PARAM,INREL,-2 is active in a dynamic subcase.

User action: Specify PARAM,INREL,-2 in only the static subcases. You may have to also request SPCi for
the dynamic subcases to avoid instabilities.

Main Index
 1052 MSC Nastran Error Messages
Errors 9000 - 9999

9267.0
PARAM,INREL,-1 and SUPORT Bulk Data entries are present in a buckling analysis.

User action: Replace the SUPORT Bulk Data entry with SUPORT1 entry and reference the SUPORT1
entry with the SUPORT1 Case Control command in only the static subcases. You may have to also request
SPCi for the SUPORTed DOFs in the buckling subcases.

9268.0
PARAM,INREL,-1 is present with more than six degrees-of-freedom specified on SUPORTi Bulk Data
entries.

User action: Specify PARAM,INREL,-4 or reduce the number of degrees-of-freedom on SUPORTi Bulk
Data entries.

9269.0
PARAM,INREL,-4 is present with a design model. PARAM,INREL,-4 is not supported in design optimi-
zation and sensitivity analyis.

User action: Specify PARAM,INREL,-1 or -2.

9270.0 ***User Fatal Message 9270

External superelements (TYPE=EXT____ on the SEBULK or MDBULK entry) are present in inertia relief
analysis which is not allowed.

User action: Convert the superelements to DMIG format with EXTSEOUT or EXTMD-
OUT(DMIGPCH)

9271.0
EXTSEOUT or EXTMDOUT is requested in SOL %1.

User action: Use SOLs 101, 103, 107 through 112, or 400.

9272.0 ***User Fatal Message 9272

SEBULK entry for superelement %1 repeats or mirrors external superelement %2 which was not created
with the MATRIXDB, DMIGDB, DMIGOP2, or DMIGPCH export options.

Main Index
 MSC Nastran Error Messages 1053
Errors 9000 - 9999

9301.0
SET3ID %1 ON A CONCTL ENTRY REFERS TO A NON-EXISTENT SET3 ENTRY.

9302.0
SET DESCRIPTION (DES) FIELD OF SET3 ID %1 REFERENCED BY A CONCTL ENTRY MUST
BE ELEM.

9303.0
%1 ELEMENT ID %2 REFERS TO A DUPLICATE PARAMETER %3 ON CONCTL ENTRY
WITH SET3ID %4.

User information: PARAMETER %5 HAS BEEN DEFINED BY A PREVIOUS CONTCTL ENTRY

WITH SET3ID %6.

9304.0 ***USER INFORMATION MESSAGE 9304 (DPD1)

FLUID DOFS ARE AMONG THE DOFS WITH ENFORCED MOTION.
ENFMETH SWITCHED TO ABS.

9306.0
SET ID %1 ON THE SLDSKIN CASE CONTROL COMMAND REFERS TO A NON-EXISTENT
SET3 ENTRY.

9307.0
SET DESCRIPTION (DES) FIELD OF SET3 ID %1 REFERENCED BY THE SLDSKIN CASE
CONTROL COMMAND MUST BE "PROP".

9399.0
STRESS BASED SEPARATION (IBSEP= %1) NOT SUPPORTED FOR DMP

9399.1
KMETHOD %1 NOT SUPPORTED FOR DMP
ONLY FNT AND PFNT ARE SUPPORTED

9399.2

Main Index
 1054 MSC Nastran Error Messages
Errors 9000 - 9999

ANALYSIS=MODES IS NOT SUPPORTED FOR DISTRIBUTED MEMORY PARALLEL (DMP) IN

SOL 400.

User action: PLEASE SUBMIT THE JOB IN SERIAL MODE (DO NOT SET DMP ON THE SUB-
MITTAL LINE).

9399.3
DIRECT FREQUENCY ANALYSIS (ANALYSIS=DFREQ) NOT SUPPORTED FOR DISTRIB-
UTED MEMORY PARALLEL (DMP) in SOL 400.

User action: PLEASE SUBMIT THE JOB IN SERIAL MODE (DO NOT SET DMP ON THE SUB-
MITTAL LINE).

9399.4
NONLINEAR BUCKLING (NLBUCK COMMAND) IS NOT SUPPORTED FOR DISTRIBUTED
MEMORY PARALLEL (DMP) IN SOL 400.

User action: PLEASE SUBMIT THE JOB IN SERIAL MODE (DO NOT SET DMP ON THE SUB-
MITTAL LINE).

9399.5
TSTEP/TSTEPNL IS NOT SUPPORTED FOR DMP

User action: PLEASE USE NLSTEP WITH FNT OR PFNT WITH DMP

9400.0
VCCTM IS PRESENT WHICH IS NOT SUPPORTED BY DISTRIBUTED MEMORY PARALLEL
(DMP) NLEMG.

User action: RERUN THE JOB WITH DOMAINSOLVER STAT IN THE EXECUTIVE CONTROL
SECTION.

9401.0
KMETHOD %1 NOT SUPPORTED FOR PARDISO (FACTMETH=PRDLDL)
ONLY FNT AND PFNT ARE SUPPORTED
SWITCHING TO DEFAULT (SYSTEM(166),BIT18=0)

Main Index
 MSC Nastran Error Messages 1055
Errors 9000 - 9999

9401.1
SWITCHING REORDERING FROM PARDISO-%1 TO DEFAULT (SYSTEM(206),BIT%2=0)
SINCE PARDISO NOT SUPPORTED FOR KMETHOD %3

9402.0
LMT2MPC (MDLPRM, LMT2MPC, 1) NOT SUPPORTED FOR PARDISO (FACT-
METH=PRDLDL) SWITCHING OFF LAGRANGE MULTIPLIER TO MULTI-POINT CON-
STRAINT TRANSFORMATION.
THE INDEFINITE MATRIX WILL BE SOLVED BY PARDISO WITHOUT TRANSFORMATION.

9403.0
PRESENCE OF INCOMPRESSIBLE HERRMANN TYPE NONLINEAR ELEMENTS DETECTED.
SWITCHING TO PARDISO SOLVER FOR EFFICIENT SOLUTION EXECUTION.

9403.1
PRESENCE OF INCOMPRESSIBLE HERRMANN TYPE NONLINEAR ELEMENTS DETECTED.
PROBABLE PERFORMANCE INEFFICIENCY WHILE USING MSCLDL SOLVER DURING
DECOMPOSITION.

User action: USE PARDISO SOLVER FOR EFFICIENT SOLUTION (FACTMETH=PRDLDL).

9422.0
WRONG ANSWERS MAY OCCUR FOR TRANSIENT ANALYSIS WITH RIGID=LAGRANGE IF
THE INITIAL CONDITIONS DO NOT SATISFY THE CONSTRAINTS OF RIGID ELEMENTS

9423.0
PARAM,POST,2 or -2 or PARAM,OUGCORD,BASIC is requested but the displacement OTMs in basic
are not found.

User information: This is most probably due to the fact that the external superelement files were created
prior to Version 2017. Displacements will not be computed for the external superelement.

9424.0

Main Index
 1056 MSC Nastran Error Messages
Errors 9000 - 9999

There are fundamental changes to the model's geometry, properties, or connectivity. Therefore a nonlinear
restart is not possible from a step computed in a previous run.

User action: Re-submit the restart without these changes or re-submit the job as a cold start. See also
OVERRIDE keyword on the NLRESTART Case Control command.

9424.1
The OVERRIDE keyword is specified on the NLRESTART command and the run will continue even
though there are fundamental changes to the model's geometry, properties, or connectivity. Continuing the
run may produce wrong answers or misleading fatal messages and therefore OVERRIDE is not recom-
mended in all cases.

9424.2
THIS JOB CONTAINS ADVANCED NONLINEAR ELEMENTS WITH NO LINEAR PERTURBA-
TION ANALYSIS. RESTART JOBS WITH LINEAR PERTURBATION ANALYSIS MAY RUN
INTO MEMORY MISMATCH ISSUES.

User action: If restart with linear perturbation analysis is intended, re-submit the current run using "MDL-
PRM,NLRSTRTM,1" to avoid possible memory errors in restart jobs.

9424.3
THIS RESTART JOB CONTAINS ADVANCED NONLINEAR ELEMENTS WITH LINEAR PER-
TURBATION ANALYSIS. TO AVOID MEMORY MISMATCH ISSUES, MAKE SURE THE COLD
START JOB IS ALSO A LINEAR PERTURBATION ANALYSIS OR USE "MDLPRM,NLR-
STRTM,1" IN THE COLD START JOB.

9425.0
PARAM,CHECKOUT,YES is not supported if advanced nonlinear elements are present.

User action: Remove PARAM,CHECKOUT,YES.

9426.0
The NLPARM Case Control command is being requested in a nonlinear buckling step (NLBUCK com-
mand).

User action: For nonlinear buckling analysis, only NLSTEP, with KMETHOD set to ITER with
KSTEP=1 or PFNT, may be requested.

Main Index
 MSC Nastran Error Messages 1057
Errors 9000 - 9999

9427.0
An NLSTEP Bulk Data entry with KMETHOD=ITER is being requested in a nonlinear buckling step
(NLBUCK command) but KSTEP is not equal to 1.

User action: For nonlinear buckling analysis with KMETHOD=ITER, it is strongly recommended that
KSTEP be set to 1.

9428.0
An NLSTEP Bulk Data entry with %1 not equal to %2 is being requested in the same step as an NLBUCK
command which may result in an inaccurate critical buckling factor (ALPHA).

User action: In a nonlinear buckling analysis it is stongly recommended that %1 be set to %2.

9429.0
The stiffness matrix intended for a nonlinear buckling analysis is unsymmetric but the METHOD com-
mand is specified which assumes a symmetric matrix and the resulting eigenvalues may not be accurate.

User action: The unsymmetry may be due to follower stiffness (see PARAM, FOLLOWK) in which case
the CMETHOD command must be specified.

9430.0
RIGID=LAGRANGE or LGELIM with advanced nonlinear elements is not supported in nonlinear buck-
ling analysis.

User action: Remove NLMOPTS,SPROPMAP,>0 and all extended nonlinear property entries like PSH-
LN1, PBEMN1, etc.
Or
Set RIGID=LINEAR in the Case Control.

9431.0
The ANALYSIS command is ignored in this Solution Sequence.

9432.0

Main Index
 1058 MSC Nastran Error Messages
Errors 9000 - 9999

PRESSURE APPLIED THROUGH PLOADX1 FOR AXISYMMETRIC SHELL ELEMENTS (CAX-

ISYM) IS BASED ON THE NORMAL AND RELATIVE POSITION OF THE FIRST GRID POINT
(GA) WITH RESPECT TO THE ORIGIN.

User action: USE SYSTEM CELL 794 = 1 TO CONSISTENTLY USE THE INWARD NORMAL TO
THE SHELL (GA-GB line) FOR THE DEFAULT PRESSURE DIRECTION

9433.0 ***USER FATAL MESSAGE 9433 (NONLIN)

Nonlinear buckling (NLBUCK Case Control command) is not supported in a coupled heat transfer and
structural analysis.

User Action: Remove NLBUCK or convert the Case Control to a chained analysis.

9816.0
HYBRID DAMPING WAS NOT CALCULATED BECAUSE THE FILTERED MASS OR STIFF-
NESS IS NULL.

9816.1
HYBRID DAMPING WAS NOT CALCULATED BECAUSE THERE WERE NO EIGENVALUES
IN THE REQUESTED RANGE.

9903.0 *** USER FATAL MESSAGE 9903 (ASGNCD)

THERE ARE %1 AXES THAT REQUIRE CONTROL, BUT THE REDUNDANT CONTROL SUR-
FACES AFFECT %2 AXES.

User information: THE NUMBER OF AXES THAT REQUIRE CONTROL IS FOUND BY TAKING
THE NUMBER OF SUPPORTED DEGREES OF FREEDOM MINUS THE NUMBER OF FREE
AESTAT BULK DATA ENTRIES.
IF THE CONTROL SURFACES AFFECT MORE THAN THIS NUMBER, THE NONLINEAR
TRIM ALGORITHM IS NOT WELL POSED AND CANNOT REACH A SOLUTION.

User action: PROVIDE ADDITIONAL SUPPORTED DEGREES OF FREEDOM OR REMOVE

CONTROL SURFACES THAT AFFECT AXES THAT DON'T REQUIRE CONTROL.

9936.0 *** User INFORMATION MESSAGE 9936 (MAKPRBD)

THE FOLLOWING RIGID BODY DEGREES OF FREEDOM ARE DEFINED TO BE SUP-
PORTED BY THE SUPDOF PARAMETER: %1

Main Index
 MSC Nastran Error Messages 1059
Errors 9000 - 9999

9936.1 ***USER INFORMATION MESSAGE 9936 (MAKPRBD)

THE FOLLOWING RIGID BODY DEGREES OF FREEDOM ARE COMPUTED TO BE SUP-
PORTED: %1
IF THIS IS NOT CORRECT, THEN PLEASE USE THE SUPDOF PARAMETER TO DEFINE
WHICH DEGREES OF FREEDOM ARE SUPPORTED.

9937.0 *** USER WARNING MESSAGE 9937 (NONLIN)

ADVANCED ELEMENTS ARE BEING USED IN PERTURBATION ANALYSIS. STRESS AND
FORCE OUTPUT ADVANCED ELEMENTS ARE NOT SUPPORTED IN PERTURBATION
ANALYSIS AND SHOULD THEREFORE NOT BE REQUESTED FOR THESE ELEMENTS.

9937.1 *** USER INFORMATION MESSAGE 9937 (subdmap nonlin)

DESIGN MODEL INPUT IS BEING IGNORED IN A NONLINEAR ANALYSIS WITH ESLNRO =
0$

9938.0 *** USER FATAL MESSAGE 9938 (PHASE1A)

MULTIPLE STATSUBS ARE NOT SUPPORTED FOR CYCLIC SYMMETRY ANALYSIS.
9940.0
RESTARTS IN LINEAR TRANSIENT ANALYSIS USING PARAMETER STIME > 0.0 ARE SUP-
PORTED ONLY FOR APPLIED LOADS, NOT FOR SPC/SPCD ENFORCED MOTION

9941.0
USER MAY NOT SPECIFY INITIAL CONDITIONS FOR THIS LARGE MASS ENFORCED DIS-
PLACEMENT PROBLEM. THE INITIAL DISPLACEMENT AND VELOCITY ARE BOTH GEN-
ERATED INTERNALLY BY THE PROGRAM AND MAY NOT BE OVERRIDDEN.

9942.0
USER MAY NOT SPECIFY INITIAL VELOCITY FOR THIS LARGE MASS ENFORCED VELOC-
ITY PROBLEM. THE INITIAL VELOCITY IS GENERATED INTERNALLY BY THE PROGRAM
AND MAY NOT BE OVERRIDDEN. THE USER MAY ONLY SPECIFY INITIAL DISPLACE-
MENT FOR THIS CASE.

9943.0
TRLG MODULE HAS GENERATED INITIAL CONDITIONS FOR THIS LARGE MASS
ENFORCED DISPLACEMENT PROBLEM.

Main Index
 1060 MSC Nastran Error Messages
Errors 9000 - 9999

9943.1
TRLG MODULE HAS GENERATED INITIAL CONDITIONS FOR THIS LARGE MASS
ENFORCED DISPLACEMENT PROBLEM OR LARGE MASS ENFORCED VELOCITY PROB-
LEM.

9943.2
TRLG MODULE HAS GENERATED INITIAL CONDITIONS FOR THIS LARGE MASS
ENFORCED %1 PROBLEM.

9944.0 *** USER FATAL MESSAGE

LARGE MASS METHOD TO ENFORCE DISPLACEMENT/VELOCITY DOES NOT SUPPORT
INITIAL CONDITIONS WITH IC(STATSUB).

User Action: THE USER CAN EITHER,

1. EMPLOY SPC/SPCD TO ENFORCE MOTION INSTEAD OF LARGE MASS METHOD, or
2. EMPLOY LARGE MASS METHOD TO ENFORCE ACCELERATION (INSTEAD OF
DISPLACEMENT/VELOCITY).

9945.0 *** USER FATAL MESSSAGE 9945 (IFPL)

RIGID = LAGRANGE IS NOT ALLOWED IN SOL 106

9946.0
RESIDUAL VECTORS ARE NORMALLY CRITICAL FOR GETTING CORRECT ANSWERS FOR
SPCD PROBLEMS IN MODAL SOLUTION SEQUENCES.
USER SPECIFICATION OF RESVEC = NO FOR THIS PROBLEM IS VERY LIKELY TO GIVE
WRONG ANSWERS.

9947.0
PARAM,ENFMOTN,REL IS CURRENTLY NOT SUPPORTED FOR SPCD PROBLEMS WHEN
PARAM,ENFMETH,ABS IS USED (OR IMPLIED).

User action: WHEN PARAM,ENFMOTN,REL IS USED IN AN SPCD PROBLEM, SPECIFY

PARAM,ENFMETH,REL

9947.1

Main Index
 MSC Nastran Error Messages 1061
Errors 9000 - 9999

USAGE OF MULTIPLE BOUNDARY CONDITIONS IN FREQUENCY RESPONSE ANALYSIS IS

CURRENTLY NOT SUPPORTED FOR SPCD PROBLEMS IF THE SPECIFIED ENFORCED
MOTION IS NOT THE SAME FOR ALL OF THE BOUNDARY CONDITIONS

User information: NASTRAN CURRENTLY HAS THE RESTRICTION THAT A FREQUENCY

RESPONSE JOB WITH MULTIPLE BOUNDARY CONDITIONS INVOLVING SPCD
ENFORCED MOTION USAGE MUST HAVE THE SAME SPECIFIED ENFORCED MOTION
FOR ALL OF THE BOUNDARY CONDITIONS

9947.2
WITH PARAM,VMOPT,2, PARAM,DDRMM and/or PARAM,MODACC should not be specified.

User action: remove PARAM,DDRMM and/or PARAM,MODACC and rerun job

9948.0
CASE CONTROL COMMAND RIGID=LAGRAN OR LGELIM MAY NOT BE USED WITH
PARAM, EXTOUT.
SET RIGID=LINEAR TO RUN EXTERNAL SUPERELEMENTS

9949.0
There are superelements present in SOL 400 and there is no %2 Case Control command in the residual
structure subcase %1 which may give null results.

User information: This situation can occur when the SUPER command is used to define separate subcases
for the superelements and the residual structure. It should also be noted that %2 in the residual structure's
subcase overrides the %2 request in any superelement's subcase.

User action: Specify a %2 request in the residual structure subcase even if there are no loads in the residual
structure.

9951.0
Residual fluid-structure FE model does not exist.

9951.1

Main Index
 1062 MSC Nastran Error Messages
Errors 9000 - 9999

Trim component FE model does not exist.

Trim component ID = %1.

User information An FE model should include GRID entries. For a 3D trim component, it should have
finite elements and their associated property and material entries. For a 1D trim component, PLTSURF
must be used to model both bottom and top trim surfaces.

9951.2
%1 on trim component TRMC, %2, is now initiated.

9951.3
DATA FOR TRIM COMPONENT %1 MISSING.

9951.4
TRIM COMPONENT %1 CONTAINS 2D elements which are not supported.

9951.5
Coupled structural GRIDs must have blank(basic coordinate system) for CD(field 7) of GRID.

User action: examine following MATGPR output and make sure GRIDs with non-zero value has BLANK
for CD(field 7).

9951.6 *** USER WARNING MESSAGE

No trim component is referenced by Case Control, TRIMGRP, in subcases. All trim components defined
by BEGIN BULK TRMC will be ignored.

User information: Case Control, TRIMGRP, must be put above or in SUBCASE to include trim compo-
nents in analysis.

9952.0
Invalid value provided for PARAM,RIMINTP. Valid options are linear(default) and log10.

9953.0
The matrix, MACTR, of trim component, %1, does not exist at nacfr= %2.

9954.0

Main Index
 MSC Nastran Error Messages 1063
Errors 9000 - 9999

SOL %1 does not support the BCONTACT Case Control command.

User information: If you do intend to use BCONTACT, use SOL 400 otherwise remove it from the input
file.

9955.0
RC Network Thermal Solver does not support the BCONTACT Case Control command.

User information: Remove it from the input file or use Nastran Thermal Solver.

9955.1
RC Network Thermal Solver has been deprecated.

User information: Remove it from the input file or use Nastran Thermal Solver.

9956.0
The CPYRAM element is present in an unsupported solution sequence.

User information: CPYRAM is not supported in SOLs 106, 114 through 118, 129, 153, and 159.

9957.0
Access points (ACCSSPT entries) are present in an external superelement assembly run. User PARAMeters
AUTOMSET and SEP1XOVR are automatically set to YES and 128, respectively.

9991.0 *** USER FATAL MESSAGE 1 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
THE LAST %3 %4 DATA BLOCK(S) ARE NOT SPECIFIED AND WILL BE ASSUMED TO BE
PURGED.

9991.1 *** USER WARNING MESSAGE 1 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
THE LAST %3 %4 DATA BLOCK(S) ARE NOT SPECIFIED AND WILL BE ASSUMED TO BE
PURGED.

9992.0 *** USER FATAL MESSAGE 2 (XGPIDG)

Main Index
 1064 MSC Nastran Error Messages
Errors 9000 - 9999

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2

PARAMETER NAMED %3 IS DUPLICATED

9992.1 *** USER WARNING MESSAGE 2 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
PARAMETER NAMED %3 IS DUPLICATED

9993.0 *** USER FATAL MESSAGE 3 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
FORMAT ERROR IN PARAMETER NO. %3

User information: A double delimiter appears in parameter section of previous DMAP instruction.

9993.1 *** USER WARNING MESSAGE 3 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
FORMAT ERROR IN PARAMETER NO. %3

9994.0 *** SYSTEM FATAL/WARNING MESSAGE 4 (XGPIDG)

MPL PARAMETER ERROR,MODULE NAME = %1 PARAMETER NO. %2

System information: MPL entry for module is incorrect. See block data program XMPLBD.

9995.0 *** USER FATAL/WARNING MESSAGE 5 (XGPIDG)

PARAMETER INPUT DATA ERROR, ILLEGAL VALUE FOR PARAMETER NAMED %1.

9996.0 *** USER FATAL MESSAGE 6 (XGPIDG)

ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL VALUE FOR PARAMETER NO. %3

User information: The type of parameter in DMAP instruction does not correspond to type requested in
the MPL. For example, the location on the DMAP statement calls for an integer parameter and a real
parameter has been entered.

9996.1 *** USER WARNING MESSAGE 6 (XGPIDG)

POSSIBLE ERROR IN DMAP INSTRUCTION %1 INSTRUCTION NO.%2
ILLEGAL VALUE FOR PARAMETER NO. %3

Main Index
 MSC Nastran Error Messages 1065
Errors 10000 - 10999

Errors 10000 - 10999

10001.0 *** SYSTEM WARNING MESSAGE 10001 (SUBDMAP XXXXXXXX)
The DMAPMSG statement's %1 parameter should be %2.

10002.0
FOR NASTRAN/ADAMS INTERFACE, THE IMAGINARY PART OF %1 IS NONZERO: %2

10003.0
COUPLED MASS FORMULATION HAS BEEN REQUESTED WITH THE NASTRAN/ADAMS
INTERFACE.

10004.0
BULK ENTRY DTI,UNITS REQUIRED FOR NASTRAN/ADAMS INTERFACE RUN TERMI-
NATED

10005.0
NO MASS MATRIX AVAILABLE FOR MASSLESS MECHANISM TESTING.

10006.0
MECHANISM FIX REQUESTED FOR NON-SYMMETRIC MATRIX.
ONLY SYMMETRIC MATRICES ARE SUPPORTED MECH. FIX STOPPED

10007.0
%1 EXTRA VECTORS WERE FOUND AND WILL BE DISCARDED

10007.1
NO EXTRA RAW VECTORS WERE FOUND AND IT MAY BE NECESSARY TO INCREASE
NLMAX TO FIND ALL MASSLESS MECHANISMS.

10008.0
MESSAGES CAUSED BY MSGS=YES
NUMBER OF COLUMNS OF RU %1
NUMBER OF COLUMNS OF RC %2
NUMBER OF COLUMNS OF LU %3
NUMBER OF COLUMNS OF LC %4

Main Index
 1066 MSC Nastran Error Messages
Errors 10000 - 10999

10008.1
NUMBER OF COLUMNS OF RU %1
NUMBER OF COLUMNS OF RC %2
NUMBER OF COLUMNS OF LU %3
NUMBER OF COLUMNS OF LC %4

10008.2
NUMBER OF COLUMNS OF RU %1
NUMBER OF COLUMNS OF RC %2
NUMBER OF COLUMNS OF LU %3
NUMBER OF COLUMNS OF LC %4

10008.3
M MATRIX PRESENT

10008.4
NO M MATRIX PRESENT, IDENTITY MATRIX USED.

10008.5
INPUT MATRIX IS REAL

10008.6
INPUT MATRIX IS COMPLEX

10008.7
NUMBER OF ROWS IN LU = %1
NUMBER OF ROWS IN RU = %2
THEY MUST BE EQUAL

10008.8
NUMBER OF ROWS IN LC = %1
NUMBER OF ROWS IN RC = %2
THEY MUST BE EQUAL

10008.9
UNABLE TO OVERCOME ERRORS LISTED ABOVE.
IT HAS RETURNED WITH NO OUTPUT.

Main Index
 MSC Nastran Error Messages 1067
Errors 10000 - 10999

10009.0
SUPERELEMENTS OR MODULES ARE PRESENT.

10010.0
INVALID P-VALUE: PVALID= %1

10011.0
THERE ARE MISSING DATA BLOCKS NEEDED BY %1.

10012.0
SINCE BAP DELIVERY 34, USET U3 IS NOT USED TO DEFINE AN ACCESS POINT
SEE THE DELIVERY 34 RELEASE NOTES FOR A DESCRIPTION OF THE ACCSSPT BULK
DATA ENTRY WHICH REPLACES USET U3

10013.0
INERTIA RELIEF IS REQUESTED, BUT THERE IS NO L-SET PRESENT

10014.0
MAXIMUM RATIO IN DECOMP OF STIFFNESS MATRIX IS %1

10015.0
THE %1 DBSET ASSIGNED TO SUPERELEMENT %2 IS OFFLINE.

User action: PERFORM ONE OR MORE OF THE FOLLOWING.

1. IF NASTRAN KEYWORD AUTASGN<>0, SET TO 0.
2. SPECIFY SEALL=n FOR ONLY THE ONLINE SUPERELEMENTS.
3. CHECK OR ADD assign STATEMENTS FOR THIS SUPERELEMENT.

10016.0
END OF CQC SUBCASE ID = %1

10017.0
RESPONSE OUTPUT FOR SUBCASE ID = %1
ALL EXCITATION DIRECTIONS COMBINED.

10018.0

Main Index
 1068 MSC Nastran Error Messages
Errors 10000 - 10999

NEWMARK COMBINATION PERCENTAGE IS OUT OF RANGE

PARAMETER PERCENT HAS BEEN RESET TO 40%

10019.0
THE STIFFNESS MATRIX IS SINGULAR FOR DEGREES-OF-FREEDOM WITHOUT MASS
AND/OR DAMPING AND A STATIC CONDENSATION IS NOT POSSIBLE.

User action: ADD MASS OR DAMPING TO OR CONSTRAIN THE FOLLOWING DEGREES-OF-

FREEDOM:
10020.0
FORTRAN UNIT WITH SUFFIX FILE NAME: %1 CONTAINS RESULTS FOR THE FOLLOW-
ING LOAD INCREMENT:
SUBCASE ID = %2
STEP ID = %3
SUBSTEP ID = %4
INCREMENT = %5

10020.1
FORTRAN UNIT WITH SUFFIX FILE NAME: %1 CONTAINS RESULTS FOR THE FOLLOW-
ING LOAD INCREMENT:
SUBCASE ID = %2
STEP ID = %3
INCREMENT = %4

10021.0
MODE %1 SPECIFIED ON THE DTI,CQCENTRY IS OUTSIDE THE AVAILABLE RANGE
DEFINED BY PARAM,LFREQ AND PARAM,HFREQ OR PARAM,LMODES.

User information: THIS MODE IS NOT INCLUDED IN THE SOLUTION.

10022.0
THERE IS NO DTI,CQC ENTRY PRESENT - USING CQCMETHOD FOR ALL RETAINED
MODES.

10023.0

Main Index
 MSC Nastran Error Messages 1069
Errors 10000 - 10999

START OF CQC SUBCASE ID = %1

NUMBER OF CQC MODES = %2
NUMBER OF %3 MODES = %4
NUMBER OF EXCITATION DIRECTIONS = %5
USER PARAMETER CQC IS SET TO = %6
SUM ACROSS EXCITATION DIRECTIONS = %3
SUM ACROSS MODES = CQC

10023.1
START OF CQC SUBCASE ID = %1
NUMBER OF CQC MODES = %2
NUMBER OF %3 MODES = %4
NUMBER OF EXCITATION DIRECTIONS = %5
USER PARAMETER CQC IS SET TO = %6
SUM ACROSS MODES = CQC

10024.0
MATRIX UHVRZ IS THE GENERALIZED RESPONSE FOR THE CQC MODES FOR EXCI-
TATION DIRECTION SEQUENCE %1
USE PARAM,USETPRT,0 TO SEE WHICH DOF(S) THESE ARE.

10025.0
CQC DIAGNOSTICS (PARAM,CQC,2).
MATRIX ZETAHR IS THE MODAL DAMPING.
MATRIX FNR ARE THE EXCITATION FREQUENCIES.

10026.0
MATRIX PIJMAT ARE THE CQC COEFFICIENTS.
COLUMNS ARE MODE I, ROWS ARE MODE J.

10027.0
MATRIX UHVRO IS THE GENERALIZED RESPONSE FOR THE NON-CQC MODES.
USE PARAM,USETPRT,0 TO SEE WHICH DOF(S) THESE ARE.

10028.0

Main Index
 1070 MSC Nastran Error Messages
Errors 10000 - 10999

RESPONSE OUTPUT FOR SUBCASE ID = %1

EXCITATION DIRECTION = %2

10201.0 *** USER FATAL MESSAGE 10201 (GM4APD)

NASTRAN/ADAMS interface run requires that %1 be defined.

User action: Define %1 through %2 bulk entries.

10202.0 *** USER FATAL MESSAGE 10202 (MDUSTMNF)

Rigid element type %1, Element %2 has dependent node/nodes dof's in a-set while its indepedent node/
nodes are not in the a-set. In case of RIGID=LAGRANGE, NASTRAN/ADAMS interface can only have
dependent nodes of rigid elements in the a-set only if the independent nodes are also included to be in the
a-set.

User action: Do not include dependent nodes of rigid elements in the a-set (in the bulk section FLXBDY)
if the independent nodes are not included in the aset.

10203.0 *** USER FATAL MESSAGE 10203 (MDUSTMNF)

Rigid element type %1, Element %2 could not be read properly from the GEOM2 table.

User action: Check whether Element %2 is definied correctly in bulk data section.

10203.1 *** USER FATAL MESSAGE 10203 (PHASE1DR)

Structure-fluid coupling can only be used to create an MNF when METHOD(COUPLED) is selected in
Case Control.

User action: Either remove the fluid elements or use coupled fluid-structure analysis with
METHOD(COUPLED).

10203.2 *** USER FATAL MESSAGE 10203 (PHASE1DR)

CASI SOLVER (ELEMENT) IS NOT SUPPORTED WITH SEGMENT-TO-SEGMENT CONTACT
IN PERMANENT GLUE CONTACT ANALYSIS

User action: PLEASE CHANGE TO STEP/GENERAL GLUE CONTACT OR CHANGE CASI

SOLVER TO ANOTHER SOLVER

10030.0

Main Index
 MSC Nastran Error Messages 1071
Errors 10000 - 10999

MPRES is not available for ACMS with VMOPT=1

User action: Re-run with PARAM,VMOPT,0 or PARAM,VMOPT,2 (recommended)

10033.0 *** USER FATAL MESSAGE 10033 (FREQRS)

THERE ARE FEWER FREQUENCIES IN THE PROBLEM THAN THERE ARE PROCESSORS
ASSIGNED TO THE RUN.

User action: RE-SUBMIT THE JOB WITH DMP=NPROC WHERE NPROC IS AN INTEGER
FEWER THAN OR EQUAL TO THE NUMBER OF FREQUENCIES IN THIS PROBLEM.

10033.1 *** USER FATAL MESSAGE 10033 (SEDFREQ)

THERE ARE FEWER FREQUENCIES IN THE PROBLEM THAN THERE ARE PROCESSORS
ASSIGNED TO THE RUN.

User information: NUMBER OF FREQUENCIES IN THE MODEL IS %1, NUMBER OF PROCES-

SORS ASSIGNED TO THE JOB IS %2.

User action: RE-SUBMIT THE JOB WITH DMP=NPROC WHERE NPROC IS AN INTEGER
FEWER THAN OR EQUAL TO THE NUMBER OF FREQUENCIES IN THIS PROBLEM.

10033.2 *** USER WARNING MESSAGE 10033 (SEDFREQ)

THERE ARE FEWER FREQUENCIES IN THE PROBLEM THAN THERE ARE PROCESSORS
ASSIGNED TO THE RUN.

User information: THE SMALLEST NUMBER OF FREQUENCIES IN ANY ONE SUBCASE/FRE-

QUENCY ENTRY OF THIS MODEL IS %1, THE NUMBER OF PROCESSORS ASSIGNED TO
THE JOB IS %2. THIS JOB WILL CONTINUE WITH ONLY %1 PROCESSORS.

10034.0 *** USER FATAL MESSAGE 10034 (DESCON)

MASS NORMALIZATION MUST BE SPECIFIED ON EIGR/EIGRL FOR PARTICIPATION AND
EFFMAS COMPUTATION IN SOL 200.

10035.0 *** SYSTEM FATAL MESSAGE 10035 (DNLCHILD)

LOGIC ERROR SYS449=%1

Main Index
 1072 MSC Nastran Error Messages
Errors 10000 - 10999

10051.0
NASTRAN/ADAMS INTERFACE MESSAGE:
NO DEFORMED GEOMETRY AVAILABLE.

10051.1
GRID POINT WEIGHT FOR ADAMS

10052.0
NASTRAN/ADAMS INTERFACE MESSAGE:
ONLY ONE BEGIN FLXBDY ALLOWED.

10053.0 *** USER WARNING MESSAGE 10053 (admflex)

NASTRAN/ADAMS INTERFACE DMAP INFORMATION
MASS MATRIX HAS %1 NULL COLUMNS AHOU METHOD REPLACED BY %2 METHOD
RECOMMENDED THAT USER CHECK MODEL

10054.0 *** USER WARNING MESSAGE 10054 (admflex)

Nastran/ADAMS Interface: User has selected non-default value of V1ORTHO or V2ORTHO on the
ADAMSMNF Case Control, hence, LANCZOS Method instead of the default HOUSEHOLDER
Method will be used for a-set orthonormalization.

10055.0 *** USER FATAL MESSAGE 10055 (IFPL)

Nastran/ADAMS Interface: ADMPOST=2 is not supported with external superelement.

User information: Use ADMPOST=1.

10056.0 *** USER WARNING MESSAGE 10056 (IFPL)

LARGE ROTATION OFFSET (LROFF) MASS EFFECT WILL CAUSE MASS MATRIX TO
BECOME COUPLED.
SINCE ADAMS/FLEX MNF MASS INVARIANT CALCULATION ASSUMES LUMPED MASS
MATRIX FORMULATION THE LROFF MASS EFFECTS ARE BEING SWITCHED-OFF. THIS IS
EQUIVALENT TO USING MDLPRM,OFFDEF,NOMASS.

10056.1 *** USER WARNING MESSAGE 10056 (IFPL)

Main Index
 MSC Nastran Error Messages 1073
Errors 10000 - 10999

LARGE ROTATION OFFSET (LROFF) MASS EFFECT WILL CAUSE MASS MATRIX TO
BECOME COUPLED.
SINCE NASTRAN/AVL EXCITE MASS INVARIANT CALCULATION ASSUMES LUMPED MASS
MATRIX FORMULATION THE LROFF MASS EFFECTS ARE BEING SWITCHED-OFF. THIS IS
EQUIVALENT TO USING MDLPRM,OFFDEF,NOMASS.

10057.0 *** USER FATAL MESSAGE 10057 (IFPMODGM)

Nastran/ADAMS Interface: MINVAR=NONE is invalid for structure/fluid coupled system.

10100.0 *** USER FATAL MESSAGE 10100 (MDG2END)

THE SWLDPRM PARAMETER SKIN IS NO LONGER SUPPORTED.

User information: SET THE SWLDPRM PARAMETER SCLSKIN > 0.0 TO ACTIVATE CONNEC-
TOR STIFFENING. THE RECOMMENDED VALUE OF SCLSKIN IS 0.1 FOR INITIAL STIFFEN-
ING.

10101.0
THE RESTART IS DONE IN SMP MODE, BUT THE COLD START WAS IN SERIAL MODE
PLEASE RESTART THE JOB IN SERIAL MODE (SMP=0)

10102.0
THE RESTART IS DONE IN SERIAL MODE, BUT THE COLD START WAS IN SMP MODE
PLEASE RESTART THE JOB IN SMP MODE (SMP=N, N>1)

10500.0 *** USER FATAL MESSAGE 10500 (FmChkRBp):

%1: EID, %2: GID, %3: ", PLOTEL, DMIG"
RBE3 %1 has an independent (Gij) grid %2 that is not connected to any structural element%3.

10500.1 *** USER FATAL MESSAGE 10500 (FmChkRBp):

%1: EID, %2: List of GIDs, %3: ", PLOTEL, DMIG"
RBE3 %1 has the following independent (Gij) grids that are not connected to any structural element%3:
%2

10500.2 *** USER WARNING MESSAGE 10500 (FmChkRBp):

%1: EID, %2: GID, %3: ", PLOTEL, DMIG"
RBE2 %1 has a dependent (GMi) grid %2 that is not connected to any structural element%3.

Main Index
 1074 MSC Nastran Error Messages
Errors 10000 - 10999

10500.3 *** USER WARNING MESSAGE 10500 (FmChkRBp):

%1: EID, %2: List of GIDs, %3: ", PLOTEL, DMIG"
RBE2 %1 has the following dependent (GMi) grids that are not connected to any structural element%3:
%2

10501.0 *** USER FATAL MESSAGE 10501 (FmChkDLO)

The %1 case control command is missing in SUBCASE %2 for %3 analysis.

10502.0 *** USER INFORMATION MESSAGE 10502 (IFPxPBH)

%1 on %2 bulk data entries have been modified %3

User information: To %4, set SYSTEM CELL %5 %6

"The default values of GE2 through GE6" on "PBUSH" bulk data entries have been modified "to match
QRG descriptions."

User information: To "use the pre-V2018 default values", set SYSTEM CELL "754 to 1" "or use MDL-
PRM,GEV1417,1."

10502.1 *** USER INFORMATION MESSAGE 10502 (IFPxPBH)

%1: PBUSH or PBUSHT
The default values of GE2 through GE6 on %1 bulk data entries have been modified to use V2014
through V2017 IFPSTAR default values, i.e. the blank fields of "GE" keyword will use GE1 for the %1
entry that has one or more GEi (i=2-6) inputs.

10510.0
KDAMP=-1 IS NOT SUPPORTED FOR TRANSIENT RESPONSE ANALYSIS

10515.0 *** USER FATAL MESSAGE 10515 (NOFSD)

UNREASONABLE VALUE OF CORNER DISPLACEMENT %1 FOR ELEMENT ID=%2.

User information: THIS ERROR MAY BE CAUSED BY POOR CONVERGENCE.

10515.1 *** USER FATAL MESSAGE 10515 (NOFSD)

NUMBER OF UFM 10515 EXCEEDS 50, EXTRA SIMILAR MESSAGE WON'T BE PRINTED.

User information: THIS ERROR MAY BE CAUSED BY POOR CONVERGENCE.

Main Index
 MSC Nastran Error Messages 1075
Errors 10000 - 10999

10521.0 *** USER FATAL MESSAGE 10521 (FRRD1K1/2D)

INSUFFICIENT CORE FOR KRYLOV METHOD.

10521.1 *** USER FATAL MESSAGE 10521 (FRRD1K1/2D)

ERROR IN ADDING SHIFTED MATRIX IN KRYLOV METHOD.

10521.2 *** USER FATAL MESSAGE 10521 (FRRD1K1/2D)

ERROR IN DECOMPOSING SHIFTED MATRIX IN KRYLOV METHOD.

10521.3 *** USER FATAL MESSAGE 10521 (FRRD1K1/2D)

ERROR IN READING FREQUENCY LIST IN KRYLOV METHOD.

10521.4 *** USER FATAL MESSAGE 10521 (FRRD1K1/2D)

ERROR IN READING LOAD VECTOR FILE IN KRYLOV METHOD.

10521.5 *** USER FATAL MESSAGE 10521 (FRRD1K1/2D)

USING INCORRECT DRIVER IN KRYLOV METHOD.

10521.6 *** USER FATAL MESSAGE 10521 (FRRD1K1/2D)

UNABLE TO CONVERGE WITH KRYLOV METHOD.

10525.0 *** USER FATAL MESSAGE 10525,

FSTFR: INPUT MATRIX %1 MUST BE SQUARE OR DIAGONAL

10526.0 *** USER FATAL MESSAGE 10526,

FSTFR: INPUT MATRICES DBH1S AND DBH2S MUST BE REAL TYPE

10527.0 *** USER FATAL MESSAGE 10527,

FSTFR: INSUFFICIENT MEMORY FOR FSTFR MODULE
CURRENTLY AVAILABLE: %1 Mb
MINIMUM REQUIRED: %2 Mb
IDEALLY: %3 Mb

10528.0 *** USER FATAL MESSAGE 10528 (XREAD)

Main Index
 1076 MSC Nastran Error Messages
Errors 10000 - 10999

FOR METHOD CASE CONTROL COMMAND ID=%1, PARAM SCRSPEC IS SET TO ZERO
IMPLYING RESPONSE SPECTRA ANALYSIS WHICH REQUIRES MASS NORMALIZATION.
HOWEVER, MAX NORMALIZATION HAS BEEN DETECTED.

10529.0 *** USER FATAL MESSAGE 10529 (NONLIN)

STRUCTURAL DAMPING COEFFICIENTS GEIJ ARE NOT SUPPORTED IN NONLINEAR
ANALYSIS.

10530.0 *** USER INFORMATION MESSAGE 10530. (DIAGNL)

THE INPUT TO THE DIAGONAL MODULE IS A %1 MATRIX.
OPT IS SET TO %2, WHICH RESULTS IN A %3 OUTPUT MATRIX.
IF A %1 OUTPUT MATRIX IS DESIRED, SET OPT TO A %1 OUTPUT OPTION.

10531.0 *** USER WARNING MESSAGE 10531 (MAT)

ELSUM IS NOT SUPPORTED FOR NONLINEAR MATERIALS.

10533.0 *** USER FATAL MESSAGE 10533 (PREDOM))

There is a DVLREL1 bulk data entry but there is no ANALYSIS=STATIC subcase. The design of loads
capability is limited to static analyses, including buckling.

10535.0 *** USER WARNING MESSAGE 10535 (ERB3D)

DIFFERENTIAL STIFFNESS CALCULATIONS FOR RBE3 ELEMENTS ARE SKIPPED BECAUSE
THE MAXIMUM NUMBER OF ELEMENT GRIDS EXCEEDS 10000.
MAXIMUM NUMBER OF GRIDS AND LAGRANGE MULTIPLIER IDS IS %1.

User information:
IN LINEAR BUCKLING ANALYSIS, REGARDLESS OF THE MAXIMUM NUMBER OF ELE-
MENTS:
DIFFERENTIAL STIFFNESS COMPUTATION FOR RBE3s CAN BE SKIPPED BY SETTING SYS-
TEM CELL 614 TO -1.
DIFFERENTIAL STIFFNESS COMPUTATION FOR RBE3s CAN BE FORCED WHEN THE
LIMIT IS EXCEEDED BY SETTING SYSTEM CELL 614 to -2.

10537.0 *** USER FATAL MESSAGE 10537 (GPSP)

NSKIP has a value of %1 in GPSP. This is the number of subcases to be skipped in the case control table.
A negative value makes no sense.

10539.0 *** User Information message

Main Index
 MSC Nastran Error Messages 1077
Errors 10000 - 10999

Either unable to find static case control datablock or the number of subcases does not match the number of
static solutions. Using column sequence as loadid in MODEVAL printout.

10541.0 *** USER FATAL MESSAGE 10541 (PHASE0)

PEAK OR SUBSET SOLUTION OPTIONS ARE NOT SUPPORTED WITH PEMDMP

User Action: Change SOLUTION keyword to ALL on PF commands

10544.0 *** USER INFORMATION MESSAGE 10544 (MTMD61)

TOTAL NUMBER OF FORCING FREQUENCIES: %1 - MIN FORCING FREQUENCY: %2 -
MAX FORCING FREQUENCY: %3
TOTAL NUMBER OF TRIM MASTER FREQUENCIES: %4 - MIN TRIM MASTER FREQUENCY:
%5 - MAX TRIM MASTER FREQUENCY: %6

10545.0 *** USER INFORMATION MESSAGE 10545 (MTMD61)

PROCESS ID NUMBER OF TRIM MASTER FREQUENCIES (MIN - MAX) NUMBER OF
FORCING FREQUENCIES (MIN - MAX)
%1
%2

10547.0 *** SYSTEM FATAL MESSAGE

UNABLE TO FIND COORDINATE SYSTEM %1 IN CSTM TABLE

User information: Notify MSC client support

10548.0 *** SYSTEM FATAL MESSAGE

Illegal value of CPFLAG = %1

User information: Notify MSC client support

10549.0 *** SYSTEM FATAL MESSAGE

No GRID data found in datablock GEOM1 (GINO id %1)

User information: Verify that GEOM1 exists and contains GRID data and is in the correct location in the
DMAP call.

Main Index
 1078 MSC Nastran Error Messages
Errors 10000 - 10999

10550.0 *** SYSTEM FATAL MESSAGE

No %1 were found in datablock %2, in spite of the trailer indicated it has them

User information: Verify that the trailer is properly set

10551.0 *** USER FATAL MESSAGE

Processing ROTBENT entry, BRGDPR GRID point %1 has CD= %2, while GRID point %3 has CD=
%4

User Information: Each pair of GRID points in the BRGDPR must have the same CD

10551.1 *** USER FATAL MESSAGE

Processing ROTBENT entry, BRGDPR references undefined GRID point %1

User Information: Each pair of GRID points in the BRGDPR must be defined

10560.0 *** USER FATAL MESSAGE 10560

During decomposition of matrix KOO, the degrees of freedom listed had pivot ratios greater than MAX-
RATIO. Verify that the degrees of freedom are not part of a mechanism and that elements do not have
excessive stiffness. Singular or close to singular KOO makes it unlikely to get a correct ADAMS MNF or
AVL-EXCITE EXB. In ADAMS/FLEX MNF GENERATION or AVL-EXCITE EXB GENERATION
analysis, this condition causes run termination.

User Information:
1. PARAM,BAILOUT,-1 may be used to continue the run.\
2. In case of Coupled Modes (Fluid-Structure) KOO could be singular due to the presence of Constant
Pressure Modes. These modes should be supressed by constraining fluid DOFs.

10565.0 *** USER FATAL MESSAGE 10565

ADAMS/FLEX MNF GENERATION or AVL-EXCITE EXB GENERATION CANNOT BE RUN IN
LINEAR SOLUTION SEQUENCES WITH RIGID=LAGRANGE.

User action: PLEASE EMPLOY RIGID=LINEAR OR RUN THE MNF OR GENERATION WITH
SOL 400

10568.0 *** USER FATAL MESSAGE 10568

Main Index
 MSC Nastran Error Messages 1079
Errors 10000 - 10999

THE COINCIDENT GRID ZERO TOLERANCE (SUM OF GMOVR3T AND DELTA GMOVR3T)
IS NEGATIVE FOR THE RBE3 ELEMENT ID %1 SPECIFIED ON THE GMOVR3 ENTRY.

User action: ADJUST THE TOLERANCE IN MDLPRM,GMOVR3T OR THE CORRESPONDING

DELTA GMOVR3T OF GMOVR3 ENTRY.

10570.0 *** USER FATAL MESSAGE 10570

THE FOLLOWING RBE3 ELEMENTS HAVE REFGRID GRIDS COINCIDENT WITH ALL
THEIR CONNECTED GI,J NODES.

User information: THE VALUE OF MDLPRM,GMOVR3 IS %1.

10570.1 *** USER FATAL MESSAGE 10570

THE PARDISO SOLVER WAS REQUESTED FOR A SOL 400 MODEL WITH AN UNSYMMET-
RIC MATRIX.
%1
THIS ISSUE IS MOST LIKELY CAUSED BY A RADBC, RADSET, or CONVM entry.

User information: DEFAULT MSCLDL SOLVER WILL BE USED.

10571.0 *** USER WARNING MESSAGE 10571

THE FOLLOWING RBE3 ELEMENTS HAVE REFGRID GRIDS COINCIDENT WITH ALL
THEIR CONNECTED GI,J NODES.
AS A RESULT, A SMALL PERTURBATION IS APPLIED TO THE %2 GRID.

User information: THE VALUE OF MDLPRM,GMOVR3 IS %1.

10571.1 *** USER WARNING MESSAGE 10571

THE FOLLOWING RBE3 ELEMENTS HAVE REFGRID GRIDS COINCIDENT WITH ALL
THEIR CONNECTED GI,J NODES.
AS A RESULT, A SMALL PERTURBATION IS APPLIED TO THE %2 GRID.

User information: MODEL PARAMETERS (MDLPRM) GMOVR3 = %1 AND GMOVRD = %3.

10590.0 *** USER INFORMATION MESSAGE 10590 (GENRLDA)

Main Index
 1080 MSC Nastran Error Messages
Errors 10000 - 10999

THE NUMBER OF APPLIED LOADS (%1) EXCEEDS THE MAXIMUM RECOMMENDED (%2)
FOR THE JOB TO FINISH IN A REASONABLE AMOUNT OF TIME.

User information: ANY LINEARLY DEPENDENT LOAD VECTORS WILL BE REMOVED.

10591.0 *** USER INFORMATION MESSAGE 10591 (GENRLDA)

%1 LINEARLY INDEPDENT APPLIED LOAD VECTORS WILL BE USED FOR RESIDUAL VEC-
TOR AUGMENTATION

10592.0 *** USER INFORMATION MESSAGE 10592 (GENRLDA)

%1 LOADS REMAIN AFTER LINEAR DEPENDENCE CHECK. THIS NUMBER EXCEEDS THE
MAXIMUM FOR THIS JOB.

User information: RESIDUAL VECTOR COMPUTATION FOR APPLIED LOADS WILL BE

DEACTIVATED AND THEREFORE WILL NOT BE COMPUTED.

User action: TO COMPUTE RESIDUAL VECTORS FOR ALL LOADS, USE PARAM,MAXAPL,n
TO SET THE MAXIMUM NUMBER OF APPLIED LOADS. HOWEVER, DOING SO MAY
RESULT IN AN EXCESSIVE RUN TIME.

10593.0 *** USER FATAL MESSAGE 10593 (SEMODES)

THIS MODEL CONTAINS NO STRUCTURAL ELEMENTS. ACMS IS NOT SUPPORTED FOR
ALL-FLUID MODELS.

User action: REMOVE THE DOMAINSOLVER ACMS ENTRY FROM THE EXECUTIVE SEC-
TION OF YOUR INPUT DATA.

10594.0 *** SYSTEM WARNING MESSAGE 10594

MDSTAT: NDMP IS LESS THAN 1

10594.1 *** SYSTEM WARNING MESSAGE 10594.1

MDSTAT: NDMP IS LESS THAN NPROCS

10601.0 *** USER WARNING MESSAGE 10601

Main Index
 MSC Nastran Error Messages 1081
Errors 10000 - 10999

NASTRAN UNSYMMETRIC SPARSE FACTORIZATION METHOD IS DEACTIVATED VIA

NASTRAN SYSTEM(209) = 0 TO AVOID RANK DEFICIENCY WHEN THERMAL GLUED CON-
TACT AND %1 COEXIST. IF THE PERFORMANCE IS IMPACTED SIGNIFICANTLY,
USE PARAM,KDIAG,-1. AND NEAR CONTACT INSTEAD TO AVOID THIS NUMERICAL
ISSUE WITHOUT AFFECTING PERFORMANCE.

10605.0 *** USER WARNING MESSAGE 10605

THE VALUE OF PARAMETER KDIAG IS SET TO -1. TO AVOID RANK DEFICIENCY WHEN
THERMAL CONTACT AND %1 COEXIST.

10610.0 *** User FATAL MESSAGE 10572 (SERECHK)

DATABLOCK MPT WITH NLSTEP DOES NOT EXIST.
PLEASE CHECK THE BULK DATA INPUT FOR NLSTEP USAGE.

10611.0 *** User FATAL MESSAGE 10572 (SERECHK)

READING RECORD OF MPT FOR NLSTEPS ENCOUNTERED ABNORMAL END PLEASE
CHECK THE BULK DATA INPUT FOR NLSTEP USAGE.

10612.0 *** User FATAL MESSAGE 10573 (SERECHK)

DATABLOCK CASECC DOES NOT EXIST.
PLEASE CHECK THE BDF CASE CONTROL SECTION INPUT.

10613.0 *** User FATAL MESSAGE 10573 (SERECHK)

READING HEAD RECORD OF CASSCC ENCOUNTERED ABNORMAL END PLEASE CHECK
THE BDF CASE CONTROL SECTION INPUT.

10614.0 *** User FATAL MESSAGE 10573 (SERECHK)

READING RECORD OF CASSCC ENCOUNTERED ABNORMAL END PLEASE CHECK THE
BDF CASE CONTROL SECTION INPUT.

10625.0 *** USER FATAL MESSAGE 10625

Main Index
 1082 MSC Nastran Error Messages
Errors 10000 - 10999

FOR PARAM,BUSHNM,YES FREQUENCY DEPENDENT PATH ONLY ONE SUBCASE IS

ALLOWED BECAUSE:
1. MASTER FREQUENCIES ARE DEPENDENT ON FORCING FREQUENCIES.
2. MASTER FREQUENCIES ARE COMPUTED FROM THE FIRST SUBCASE.
3. MULTIPLE SUBCASES WITH DIFFERENT FREQ=n ENTRIES WERE DETECTED.
SEE PARAM,MSG10625 IN QRG FOR FURTHER DETAILS.

10626.0 *** User FATAL MESSAGE 10626 (RDREST)

LOGICAL NAME MASTER IS NOT ALLOWED FOR READ-ONLY-RESTARTS (NOKEEP).

10631.0 *** USER WARNING MESSAGE 10631

FOR PARAM,BUSHNM,YES FREQUENCY DEPENDENT PATH MULTIPLE SUBCASES WERE
DETECTED.
AS A RESULT, THE MASTER FREQUENCIES OF THE FIRST SUBCASE WILL BE USED FOR
ALL SUBCASES AND THE RESPONSES.
ALSO, STRESS/FORCE RESULTS FOR FREQUENCY DEPENDENT ELEMENTS AT INTERPO-
LATED FREQUENCIES ARE NOT COMPUTED.

10633.0 *** USER WARNING MESSAGE 10633 (IFP1A4)

HDOT OUTPUT REQUEST IS NOT SUPPORTED IN SOL 400.

10636.0 *** USER INFORMATION MESSAGE 10636 (MAKEsgp)

The following physical file is created, using Fortran unit %1, with a SET1 entry for the singular grids
reported by ACMS:
%2
Please also see User Information Message 9146 for the list of specific degrees of freedom to review.
These degrees of freedom will be constrained since they are associated with at least one vector X, whose gen-
eralized stiffness and generalized mass are essentially zero.

10640.0 *** USER FATAL MESSAGE 10640 (IFP6GPID)

PCOMPG PID=%1 entry contains two or more plies with identical Global (External) Ply ID of %2.

User information: The Global Ply ID must be unique with respect to other plies in the same PCOMPG
entry.

10642.0 *** USER WARNING MESSAGE (MDG2PR)

Main Index
 MSC Nastran Error Messages 1083
Errors 10000 - 10999

FOR PFAST ENTRY %1 USING MCID=-1 OPTION: NON-ISOTROPIC IN-PATCH STIFFNESS

KT2 NOT EQUAL KT3 OR KR2 NOT EQUAL KR3 IS INCONSISTENT WITH ARBITRARY IN-
PATCH Y-Z AXIS DETERMINED BY SMALLEST NEAR ZERO COMPONENT OF THE ELE-
MENT X-AXIS. THE MCID GREATER THAN OR EQUAL TO 0 OPTION IS RECOMMENDED.

10646.0 *** USER INFORMATION MESSAGE 10646

PATH BUSHNM YES DETECTED BUT HAS BEEN OVERRIDDEN TO PATH BUSHNM NO
BECAUSE FREQUENCY DEPENDENCY ONLY EXISTS FOR PBUSHT/PFASTT/PAABSF/
PELAST/PDAMPT PROPERTIES. GPFORCE REQUEST HAS BEEN TURNED OFF BECAUSE IT
ONLY SUPPORTS PATH BUSHNM YES.

10647.0 *** USER FATAL MESSAGE 10647

ON CWELD ELEMENT ID=%1, WITH FORM=ELEMID AND POINT-TO-PATCH CONNEC-
TION, THE GS GRID ID=%2 IS A SHELL GRID OF THE ELEMENT ID=%3 THAT IT WANTS
TO CONNECT.

User information: TO CORRECT, DEFINE GS NOT TO LIE ON THE PATCH IT IS TRYING TO

CONNECT.

10648.0 *** USER WARNING MESSAGE 10648

SEGMENT TO SEGMENT CONTACT COMPUTES STIFFNESS AT NOMINAL MATERIALS OF
TOTAL STRUCTURE AND IS NOT FREQUENCY DEPENDENT.

10650.0 ***USER FATAL MESSAGE 10650

USING FACTMETH=MUMPS IS NOT SUPPORTED WHEN GUYAN REDUCTION IS
REQUESTED. REMOVE FACTMETH SETTING AND RETRY.

Main Index
 1084 MSC Nastran Error Messages
Errors 10000 - 10999

Main Index
 MSC Nastran Error Messages 1085
Errors 11000 - 11999

Errors 11000 - 11999

11010.0 *** USER FATAL MESSAGE 11010. (FTGCAS)
CASE CONTROL HAS A FATIGUE COMMAND BUT THERE ARE NO FTGLOAD ENTRIES IN
THE BULK DATA FILE.

User information: AT LEAST ONE SUBCASE MUST BE INVOKED VIA AN FTGLOAD

ENTRY IN A STATIC FATIGUE ANALYSIS

11010.1 *** USER FATAL MESSAGE 11010.1 (FTGCAS)

CASE CONTROL HAS A FATIGUE COMMAND BUT THERE ARE NO MAT1 ENTRIES IN THE
BULK DATA FILE.

User information: NASTRAN FATIGUE ANALYSIS CAN ONLY BE PERFORMED WITH

ISOTROPIC MATERIALS.

11010.2 *** USER FATAL MESSAGE 11010. (FTGS1B)

CASE CONTROL HAS A FATIGUE COMMAND BUT THERE ARE NO MATFTG ENTRIES IN
THE BULK DATA FILE.

User information: EACH ISOTROPIC MATERIAL THAT IS TO PARTICIPATE IN A FATIGUE

ANALYSIS REQUIRES A MATFTG ENTRY.

11010.3 *** USER FATAL MESSAGE 11010. (FTGCAS4)

THERE IS A FATIGUE = %1 CASE CONTROL COMMAND IN A MODAL TRANSIENT
ANALYSIS, BUT THERE ARE NO FTGSEQ BULK DATA ENTRIES.

User information: MODAL TRANSIENT FATIGUE ANALYSIS REQUIRES AN FTGSEQ ENTRY.

11010.4 *** USER FATAL MESSAGE 11010. (FTGCAS4)

THERE IS A FATIGUE = %1 CASE CONTROL COMMAND IN A MODAL TRANSIENT
ANALYSIS REFERENCING SUBCASE %2 FOR SEID %3, BUT THERE IS NO DLOAD ENTRY IN
THIS SUBCASE.

User action: USE SUPER=ALL OR APPLY FATIGUE REQUESTS ON RESIDUAL SUBCASES

ONLY.

Main Index
 1086 MSC Nastran Error Messages
Errors 11000 - 11999

11010.5 *** USER FATAL MESSAGE 11010. (FTGCAS4)

CWELD %1 HAS FORMAT=gridid or align must define t1, t2 and DIAM on PFTG.

11011.0 *** USER FATAL MESSAGE 11011. (FTGCAS)

FTGPARM BULK DATA ENTRY WITH ID = %1 HAS BOTH STRESS AND STRAIN KEY-
WORDS. ONLY ONE OF THESE KEYWORDS IS ALLOWED.

11011.1 *** USER FATAL MESSAGE 11011. (FTGCAS)

FTGPARM BULK DATA ENTRY WITH ID = %1 HAS BOTH SEAMW AND STRAIN KEY-
WORDS. STRAIN IS NOT ALLOWED TO WORK WITH SEAMW.

11011.2 *** USER FATAL MESSAGE 11011. (FTGCAS8)

THERE ARE MULTIPLE FATIGUE IDS THAT INVOKE FTGPARM ENTRIES WITH SRE-
SOLVE=YES AND FTGDEF ENTRIES THAT REFERENCE DIFFERING ELEMENT SETS. TWO
FATIGUE IDS THAT SHOW THIS SCENARIO ARE FATIGUE ID = %1 AND FATIGUE ID = %2.

User information: THE SRESOLVE FEATURE DOES NOT SUPPORT HAVING DIFFERING ELE-
MENT SETS IN MULTIPLE FATIGUE ANALYSES.

11011.3 *** USER FATAL MESSAGE 11011. (FTGCAS)

ILLEGAL DATA IN FTGPARM ID = %1 COMB FIELD. COMB value (%2) NOT for a %3 JOB.

11011.4 *** USER FATAL MESSAGE 11011. (FTGCAS)

NUMBER OF FATIGUE CASES %1 EXCEEDS LIMITATION %2.

User information: CHECK FATIGUE CASE CONTROL COMMAND.

11011.5 *** USER FATAL MESSAGE 11011. (FTGCAS)

FTGPARM BULK DATA ENTRY WITH ID = %1 HAS CORRS<>INTERP

User information: ONLY CORRS=INTERP IS ALLOWED for Multi-SN CURVE WITH

TYPE=ALIFE/LIFE (DEFINED by MATFTG)

User action: CHANGE CORRS=INTERP on FTGPARM

11011.6 *** USER FATAL MESSAGE 11011. (FTGCAS)

Main Index
 MSC Nastran Error Messages 1087
Errors 11000 - 11999

FTGPARM BULK DATA ENTRY WITH ID = %1 HAS BOTH SPOTW AND FOS KEYWORDS.
FOS IS NOT ALLOWED FOR SPOTW

11012.0 *** USER FATAL MESSAGE 11012. (FTGCAS)

FTGPARM BULK DATA ENTRY WITH ID = %1 HAS TYPE = SN AND THE STRAIN KEY-
WORD.

User information: ONLY THE STRESS KEYWORD IS SUPPORTED WITH TYPE = SN.

11013.0 *** USER FATAL MESSAGE 11013. (FTGCS1A)

FATIGUE ID = %1 APPEARS ON BOTH A FTGSEQ AND A FTGEVNT BULK DATA ENTRY.

User information: THIS IS NOT PERMITTED.

11014.0 *** USER FATAL MESSAGE 11014. (FTGCS1B)

MAT1 ID = %1 ON A MATFTG BULK DATA ENTRY DOES NOT REFER TO AN EXISTING
MAT1 ENTRY.

11014.1 *** USER FATAL MESSAGE 11014. (FTGCS1B)

MAT1 ID = %1 IS REFERRED TO MULTIPLE TIMES ON A MATFTG ENTRY, INCLUDING
MATFTG ID = %2.

11015.0 *** USER FATAL MESSAGE 11015. (FTGCAS4)

FTGSEQ BULK DATA ENTRY ID = %1 HAS BEEN CALLED MORE THAN ONCE IN A CHAIN
FOR FATIGUE ID = %2

11016.0 *** USER FATAL MESSAGE 11016. (FTGCS4A)

FTGLOAD BULK DATA ENTRY ID = %1 REFERENCED ON A FTGEVNT BULK DATA ENTRY
ID = %2 DOES NOT EXIST

11016.1 *** USER FATAL MESSAGE 11016.1 (FTGCS4A)

FATIGUE CASE CONTROL COMMAND = %1 DOES NOT REFER TO AN EXISTING FTGSEQ
OR FTGLOAD BULK DATA ENTRY

User information: FATIGUE ANALYSIS REQUIRES SPECIFICATION OF THE LOADING

Main Index
 1088 MSC Nastran Error Messages
Errors 11000 - 11999

11016.2 *** USER FATAL MESSAGE 11016.2 (FTGCS4A)

FTGLOAD BULK DATA ENTRY ID = %1 IS REFERENCED MULTIPLE TIMES BY FTGEVNT ID
= %2
11016.3 *** USER FATAL MESSAGE 11016. (FTGCAS4)
FTGSEQ BULK DATA ENTRY ID = %1 REFERENCED ON A FTGSEQ CASE CONTROL COM-
MAND DOES NOT EXIST.

11016.4 *** USER FATAL MESSAGE 11016.4 (FTGCS4A)

ALL THE FTGLOAD ENTRIES REFERENCED BY FTGSEQ OR FTGEVNT ID = %1 HAVE THE
TYPE FIELD SET AT STAT.

User information: FATIGUE ANALYSIS REQUIRES A LEAST ONE TIME VARYING LOADING

11016.5 *** USER FATAL MESSAGE 11016.5 (FTGCAS4)

FTGSEQ ENTRY = %1 INVOKES FID = %2 WHICH CANNOT BE FOUND.

User information: THE FID SHOULD REFERENCE AN EXISTING FTGSEQ OR FTGEVNT

BULK DATA ENTRY.

11016.6 *** USER FATAL MESSAGE 11016.6 (FTGCS4A)

FID = %1 INVOKED FROM AN FTGSEQ ENTRY DOES NOT CORRESPOND TO AN EXIST-
ING FTGSEQ OR FTGEVNT BULK DATA ENTRY.

11016.7 *** USER FATAL MESSAGE 11016.7 (FTGCS4A)

FTGLOAD ID = %1 IS OF TYPE = RPC WHILE OTHER FTGLOAD ENTRIES ARE OF A DIFFER-
ENT TYPE.
THIS IS NOT ALLOWED.

11016.8 *** USER FATAL MESSAGE 11016.8 (FTGCS4A)

FTGLOAD ID = %1 IS NOT OF TYPE = RPC WHILE OTHER FTGLOAD ENTRIES ARE OF
TYPE RPC.
THIS IS NOT ALLOWED.

11017.0 *** USER FATAL MESSAGE 11017. (FTGCS4A)

SUBCASE %1 IS REFERENCED ON MULTIPLE FTGLOAD ENTRIES ASSOCIATED WITH
FTGEVNT BULK DATA ID %2.

Main Index
 MSC Nastran Error Messages 1089
Errors 11000 - 11999

11018.0 *** USER FATAL MESSAGE 11018. (FTGCAS5)

ELEMENT ID %1 INVOKED ON A FATIGUE ANALYSIS CANNOT BE FOUND.

User information: THE ELEMENT EITHER DOES NOT EXIST OR IT IS AN ELEMENT TYPE
THAT IS NOT SUPPORTED FOR FATIGUE OR IT DOES NOT REFER TO A MAT1 ENTRY.
11018.1 *** USER FATAL MESSAGE 11018. (FTGCSSU)
ELEMENT ID %1 IS INVOKED INVOKED MULTIPE TIMES IN A FATIGUE ANALYSIS.

User action: REMOVE THE DUPLICATE REFERENCE TO THE SAME ELEMENT.

11018.2 *** USER FATAL MESSAGE 11018. (FTGCAS5)

ELEMENT ID %1 INVOKED ON A FATIGUE ANALYSIS CANNOT BE FOUND.

User information: PARAM CWRAND HAS A NON-ZERO VALUE. FATIGUE ANALYSIS FOR
SPOT WELDS DOES NOT SUPPORT PARAM CWRAND AND THIS SHOULD BE REMOVED
FROM THE INPUT. ALTERNATIVELY, THE ELEMENT MAY NOT EXIST OR IT MAY NOT
REFER TO A MAT1 ENTRY.

11018.3 *** USER FATAL MESSAGE 11018. (FTGCAS6)

ELEMENT ID %1 IS INVOKED INVOKED MULTIPE TIMES IN A FATIGUE ANALYSIS. IT
COULD BE THAT ONE REFERENCE IS FROM A REGULAR FATIGUE ANALYSIS AND THE
OTHER FROM A SEAM WELD FATIGUE ANALYSIS.

User action: REMOVE THE DUPLICATE REFERENCE TO THE SAME ELEMENT.

11019.0 *** USER FATAL MESSAGE 11019. (FTGCS5B)

SET ID %1 CALLED OUT ON A FTGDEF BULK DATA ENTRY CANNOT BE FOUND ON A
SET1, SET3 OR SET4 ENTRY

11019.1 *** USER FATAL MESSAGE 11019.1 (FTGCAS5)

FTGDEF ID %1 REQUESTS SET DATA BUT THERE ARE NO SET1,SET3 OR SET4 BULK DATA
ENTRIES.

User information: SET DATA FOR FATIGUE IS ENTERED WITH BULK DATA ENTIES.

11019.2 *** USER FATAL MESSAGE 11019.2 (FTGCS5B)

Main Index
 1090 MSC Nastran Error Messages
Errors 11000 - 11999

ONLY CLASS = PROP IS SUPPORTED FOR THE SET4 BULK DATA ENTRY.

11020.0 *** USER FATAL MESSAGE 11020. (FTGCS5B)

PROPERTY ID %1 CALLED OUT ON A SET4 BULK DATA ENTRY ID = %2 CANNOT BE
FOUND.

User information: EITHER THE PROPERTY DOES NOT EXIST OR IT IS ASSOCIATEDWITH A

MATERIAL THAT IS NOT INCLUDED IN THE FATIGUE ANALYSIS.

11021.0 *** USER FATAL MESSAGE 11021. (DOP3BA)

A DRESP1 BULK ENTRY ID = %1 WITH RTYPE = FATIGUE INVOKES FATIGUE ID = %2 IN
THE ATTB FIELD.
THIS ID IS NOT PRESENT IN CASE CONTROL.

11022.0 *** USER FATAL MESSAGE 11022. (DOP3BA)

ELEMENT ID %1 INVOKED ON A DRESP1 BULK DATA ENTRY ID = %2 WITH RYTPE =
FATIGUE IS NOT INCLUDED IN THE FATIGUE ANALYSIS WITH ID = %3 GIVEN IN THE
ATTB FIELD OF THE DRESP1 ENTRY.

11023.0 *** USER FATAL MESSAGE 11023. (FTGCS5A)

ONLY DES = ELEM IS SUPPORTED FOR FATIGUE ANALYSIS ON THE SET3 ENTRY.

User information: DES = PROP INFORMATION CAN BE INPUT USING THE SET4 ENTRY.

11024.0 *** USER FATAL MESSAGE 11024.0 (FTGCS4A)

SUBCASE ID = %1 REFERENCED ON FTGLOAD ID = %2 DOES NOT EXIST.

User action: MODIFY THE LCID FIELD ON THE FTGLOAD ENTRY TO REFERENCE AN
EXISTING SUBCASE.

User information: IF THIS IS A SOL 103 RUN, MODE IDS CANNOT BE GREATER THAN THE
RANGE SPECIFIED ON THE OMODES CASE CONTROL COMMAND.

11024.1 *** USER FATAL MESSAGE 11024.1 (FTGCAS4)

Main Index
 MSC Nastran Error Messages 1091
Errors 11000 - 11999

SUBCASE ID = %1 REFERENCED ON FTGSEQ ID = %2 DOES NOT EXIST IN A MODAL

TRANSIENT ANALYSIS

User action: MODIFY THE FIDI FIELD ON THE FTGSEQ ENTRY TO REFERENCE AN EXIST-
ING SUBCASE.

11025.0 *** USER FATAL MESSAGE 11025.0 (FTGSL2B)

IN A FATIGUE ANALYSIS, FTGLOAD %1 USES %2 TIME POINTS WHILE FTGLOAD %3 USES
%4.

User action: MODIFY THE TABULAR INPUT OF TIME STEPS SO THAT ALL ftgloads HAVE
THE SAME NUMBER.

11025.1 *** USER FATAL MESSAGE 11025.1 (FTGSL2B)

IN A FATIGUE ANALYSIS, FTGLOAD %1 USES %2 TIME POINTS WHILE FTGLOAD %3 USES
%4.

User action: MODIFY THE DAC INPUT OF TIME STEPS SO THAT ALL FTGLOADs HAVE THE
SAME NUMBER.

11025.2 *** USER FATAL MESSAGE 11025.3 (FTGSL2B)

IN A FATIGUE ANALYSIS, FTGLOAD &1 WITH TYPE=STAT IS BEING USED IN TWO DIF-
FERENT EVENTS.

User action: use unique ids for ftgload entries with type = stat.

11025.3 *** USER FATAL MESSAGE 11025.2 (FTGSL2B)

IN A FATIGUE ANALYSIS, ALL OF THE FTGLOADS IN EVENT %1 ARE OF TYPE = STAT.

User information: at least one ftgload per event requires a user defined time series.

11025.4 *** USER FATAL MESSAGE 11025.2 (FTGSL2B)

IN A FATIGUE ANALYSIS, DAC FILE %1 CANNOT BE FOUND.

11025.5 *** USER INFORMATION MESSAGE 11025.5 (FTGPRE)

Main Index
 1092 MSC Nastran Error Messages
Errors 11000 - 11999

CAEfatigue Does Not Currently Support %1 ON BULK DATA ENTRY %2 ID = %3

11025.6 *** USER INFORMATION MESSAGE 11025.6 (FTGPRE)

CAEfatigue Does Not Currently Support %1 ON CASE CONTROL COMMAND %2

11025.7 *** USER INFORMATION MESSAGE 11025.7 (FTGCAS)

DTLib Has Been Applied to Solve this fatigue analysis problem.
11025.8 *** USER INFORMATION MESSAGE 11025.8 (FTGCAS)
Therefore the job is stopped due to above reason (by setting FTGPARM LOGLVL>0)

11026.0 *** USER FATAL MESSAGE 11026.0 (FTGSL2B)

TID ID = %1 REFERENCED ON A FTGLOAD ENTRY CANNOT BE FOUND ON A TABLFTG
OR TABLED1 ENTRY.

11026.1 *** USER FATAL MESSAGE 11026.1 (FTGSL2B)

UDNAME ID = %1 REFERENCED ON A FTGLOAD ENTRY CANNOT BE FOUND ON A
UDNAME ENTRY.

User action: PROVIDE CONSISTENT IDS FOR THE FTGLOAD AND UDNAME ENTRY.

11026.2 *** USER FATAL MESSAGE 11026.2 (FTGSL2B)

A FTGLOAD ENTRY CALLS OUT TABLES BUT THERE ARE NO TABLFTG OR TABLED1
ENTRIES IN THE INPUT FILE.

11026.3 *** USER FATAL MESSAGE 11026.3 (FTGSOL1C)

TID ID = %1 REFERENCED ON A MATFTG ID = %2 CANNOT BE FOUND ON A TABLEM1
ENTRY.

11026.4 *** USER FATAL MESSAGE 11026.4 (FTGSL2B)

A FTGLOAD ENTRY HAS TYPE = DB BUT THERE ARE NO UDNAME ENTRIES IN THE
BULK DATA FILE.

11026.5 *** USER FATAL MESSAGE 11026.5 (FTGSL2B)

FTGLOAD ENTRY %1 IS THE FIRST FTGLOAD IN AN EVENT AND HAS A BLANK UDNAME
USED IN CONJUNCTION WITH TYPE=RPC. THIS IS NOT ALLOWED

User action: PROVIDE A UDNAME FOR THIS FTGLOAD ENTRY.

Main Index
 MSC Nastran Error Messages 1093
Errors 11000 - 11999

11027.0 *** USER FATAL MESSAGE 11027. (FTGCAS5)

PFTG ID %1 REFERENCED ON FTGDEF ENTRY ID = %2 CANNOT BE FOUND.

11028.0 *** USER FATAL MESSAGE 11028. (FTGSOL)

THERE IS AN ERROR IN THE FATIGUE ANALYSIS INPUT THAT PREVENTS THE ANALYSIS
FROM COMPLETING.

User information: THE JOB .LOG OR .DTOUT FILES FOR THIS RUN CONTAINS INFORMA-
TION ON THE SOURCE OF THE ERROR.

11028.1 *** USER WARNING MESSAGE 11028.1 (FTGSOL )

FATIGUE ANALYSIS ID = %1 CANNOT BE FOUND ON BULK DATA ENTRY FTGPARM.

User information: THE DEFAULT VALUE OF FTGPARM IS USED.

11028.2 *** USER FATAL MESSAGE 11028.2 (FTGSOL )

ILLEGAL DTI ENTRY INPUT FOR STRESS UNIT

User action: PROVIDE CORRECT STRESS UNIT FOR FATIGUE ANALYSIS

11028.3 *** USER FATAL MESSAGE 11028.3 (FTGSOL1B)

MATFTG ID = %1 REFERENCES %2 THAT IS OUT OF THE RANGE AFTER CONVERSION
TO STRESS UNIT MPa.

User action: PROVIDE A VALID VALUE FOR FATIGUE ANALYSIS-SEE QRG FOR VALID
RANGE.

11028.4 *** USER FATAL MESSAGE 11028.4 (FTGSOL1B)

YS AND UTS CANNOT BE BLANK SIMULTANEOUSLY ON MATFTG ID = %1 IF ONLY
STATIC PRESENTS.

Main Index
 1094 MSC Nastran Error Messages
Errors 11000 - 11999

11028.5 *** USER FATAL MESSAGE 11028.5 (FTGSOL1B)

MATFTG ID = %1 REFERENCES MATERIAL CODE %2 THAT IS OUT OF THE RANGE.

User action: PROVIDE A VALID MATERIAL CODE FOR FATIGUE ANALYSIS-SEE QRG FOR
VALID RANGE.

11028.6 *** USER FATAL MESSAGE 11028.6 (FTGSOL1B)

AN ANALYSIS GROUP WITH MATFTG ID %1 AND PFTG ID %2 HAS CODE= %3 ON THE
MATFTG ENTRY AND KFINISH=%4 ON THE PFTG ENTRY.

User information: KFINISH CANNOT BE GREATER THAN 1.0 FOR THIS MATERIAL CODE.

11028.7 *** USER FATAL MESSAGE 11028.7 (FTGSOL)

THE FATIGUE DAMAGE CHECK FAILED. STRESSES ARE GREATER THAN UTS

User information: REFER TO THE JOB.DTOUT FILE FOR RELEVANT NODES AND ELE-
MENTS.

11028.8 *** USER WARNING MESSAGE 11028.8 (FTGSOL)

THERE IS A FATIGUE DAMAGE CHECK WARNING. STRESSES ARE GREATER THAN UTS

User information: REFER TO THE JOB.DTOUT FILE FOR RELEVANT NODES AND ELE-
MENTS.

11028.9 *** USER INFORMATION MESSAGE 11028.9 (FTGSOL6)

OUT OF CORE FATIGUE SOLUTION METHOD = %1 HAS BEEN APPLIED. THIS MAY LEAD
TO POOR PERFORMANCE.

11028.10 *** USER WARNING MESSAGE 11028.10 (FTGSOL)

HISTOGRAM AND TIMEHISTORY OUTPUT OPTIONS ARE IGNORED FOR DUTYCYCLE
OR SPOT OR SEAM WELDS

11028.11 *** USER INFORMATION MESSAGE 11028.11 (FTGSOL)

INSUFFICIENT MEMORY TO PERFORM HISTOGRAM AND TIMEHISTORY OUTPUT

Main Index
 MSC Nastran Error Messages 1095
Errors 11000 - 11999

11028.12 *** USER WARNING MESSAGE 11028.12 (FTGSOL)

HISTOGRAM AND TIMEHISTORY OUTPUT OPTIONS ARE IGNORED FOR FOS REQUEST

11028.13 *** USER WARNING MESSAGE 11028.13 (FTGSOL)

TOPSTR IS NOT SUPPORTED WITH SPOT OR SEAMWELD. IT WILL BE IGNORED

11028.14 *** USER WARNING MESSAGE 11028.14 (FTGSOL)

TOPDMG IS NOT SUPPORTED WITH SPOT OR SEAMWELD. IT WILL BE IGNORED

11028.15 *** USER FATAL MESSAGE 11028.15 (FTGSOL1B)

MATFTG REFERENCES MATERIAL YOUNG'S MODULUS (E) THAT IS OUT OF THE RANGE.

User action: PROVIDE A VALID SPOT WELD FATIGUE MATERIAL (>=2.0E+4 IN MPA)-SEE
QRG FOR VALID RANGE.

11028.16 *** USER FATAL MESSAGE 11028.16 (FTGSOL1)

METHOD = AUTO for MULTI option on FTGPARM entry and Seam Weld analysis is not supported.

11028.17 *** USER WARNING MESSAGE 11028.17 (FTGSOL)

HOTSPOT IS NOT SUPPORTED WITH SPOTWELD OR SEAMWELD. IT WILL BE IGNORED

11028.18 *** USER WARNING MESSAGE 11028.18 (FTGSOL)

TOPSTR IS NOT SUPPORTED WITH HOT SPOTS. IT WILL BE IGNORED

11028.19 *** USER WARNING MESSAGE 11028.19 (FTGSOL)

TOPDMG IS NOT SUPPORTED WITH HOT SPOTS. IT WILL BE IGNORED

11029.0 *** USER FATAL MESSAGE 11029. (FTGCAS6)

THERE ARE NO ELEMENTS ASSOCIATED WITH FATIGUE ANALYSIS = %1

User information: CHECK THE FTGDEF AND MATFTG ENTRIES TO ENSURE THAT THEY
REFER TO EXISTING ELEMENTS THAT ARE VALID FOR FATIGUE ANALYSIS (ISOTROPIC
PLATES AND SOLIDS).

11029.1 *** USER FATAL MESSAGE 11029. (FTGCAS6)

Main Index
 1096 MSC Nastran Error Messages
Errors 11000 - 11999

THERE ARE NO SUBCASES ASSOCIATED WITH FATIGUE ANALYSIS = %1

User information: CHECK FTGSEQ/FTGEVNT/FTGLOAD ENTRIES TO ENSURE THAT THEY

REFER TO EXISTING SUBCASES.

11029.2 *** USER FATAL MESSAGE 11029. (FTGCAS6)

DESIGN OPTIMIZATION DOES NOT SUPPORT COMBINED STANDARD FATIGUE OR
SPOT WELD OR SEAM WELD FATIGUE ASSOCIATED WITH FATIGUE ANALYSIS = %1

User information: CHECK FTGDEF AND DRESP1 ENTRIES TO ENSURE THAT THE OPTIMI-
ZATION HAS ONLY STANDARD OR SPOT WELD or SEAM WELD FATIGUE RESPONSES.

11030. *** USER WARNING MESSAGE 11030. (FTGCAS)

THE FATIGUE ANALYSIS BEING PERFORMED ASSUMES ALL INPUTS ARE IN UNITS OF
MPA.
IF THE MODEL UNITS DIFFER FROM THIS, IT IS NECESSARY TO INCLUDE A DTI UNITS
BULK DATA ENTRY WITH THE CONSISTENT UNITS FOR STRESS.

11030.1 *** USER WARNING MESSAGE 11030. (FTGCAS)

FATIGUE ANALYSIS ON SEAM WELDS CANNOT BE DONE FOR LOC=ELEM.
SKIPPING FATIGUE ANALYSIS OF SEAM WELDS.

11030.2 *** USER FATAL MESSAGE 11030. (FTGCAS)

A STANDARD SN FATIGUE ANALYSIS WITHOUT A STRESS LINE HAS BEEN DETECTED IN
CONJUNCTION WITH A FATIGUE ANALYSIS OF SEAM WELDS.
THIS IS NOT ALLOWED. EITHER ADD A STRESS LINE OR CHANGE LOCSM TO NODE.
OR RUN THE STANDARD FATIGUE ANALYSIS AND SEAM WELD ANALYSIS UNDER DIF-
FERENT FATIGUE IDS.

11031. *** USER FATAL MESSAGE 11031. (FTGCAS3)

Main Index
 MSC Nastran Error Messages 1097
Errors 11000 - 11999

THE FATIGUE ANALYSIS CONTAINS %1 ELEMENTS BUT THEY CANNOT BE PROCESSED.

User action: TRY RUNNING THIS DECK WITHOUT THE FATIGUE REQUEST TO SEE WHAT
IS INHIBITING THE ANALYSIS

11032. *** USER FATAL MESSAGE 11032. (FTGSOL)

THE REPEATS VAULE FOR EVENT ID = %1 IS %2 WHEN METHOD = %3 ON THE FTGSEQ
ENTRY.

User information: ONLY INTEGER VALUES (OR REAL NUMBERS WITH ZERO AFTER THE
DECIMAL POINT) CAN BE USED FOR REPEATS WHEN METHOD > 0.

11032.1 *** USER WARNING MESSAGE 11032. (FTGSOL)

FOR FATIGUE ID = %1 THERE IS A SINGLE EVENT WITH AN N1 VALUE OF %2.

User information: FOR A SINGLE EVENT, THE REPEAT VALUE IS SET TO 1.0 AND THE USER
INPUT VALUE IS IGNORED.

11033. *** USER FATAL MESSAGE 11032. (FTGSOL1)

PLAST = SEEGER CANNOT BE USED WITH TYPE = EN AND SOLID ELEMENTS.

User information: ONLY 2D ELEMENTS ARE SUPPORTED FOR PLAST=SEEGER

11034.
FATIGUE ANALYSIS IS NOT SUPPORTED WITH SUPERELEMENTS

11035.
FEF requests do not support each event being printed
( EVNTOUT=1 on FTGSEQ card ), so FEF is being turned off.

11036. *** USER FATAL MESSAGE 11036. (FTGCAS )

CASE CONTROL COMMAND OMODES CANNOT BE USED WITH CASE CONTROL COM-
MAND FATIGUE UNLESS THE OMODES COMMAND SELECTS CONTIGUOUS MODES
THAT START FROM ONE.

Main Index
 1098 MSC Nastran Error Messages
Errors 11000 - 11999

11036.1 *** USER FATAL MESSAGE 11036. (FTGCAS )

SOL 200 DOES NOT SUPPORT LOC=NODA FOR FATIGUE ANALYSIS

User information: LOC=ELEM or NODE CAN BE USED IN A FATIGUE ANALYSIS FOR OPTIMI-
ZATION

11036.2 *** USER FATAL MESSAGE 11036. (FTGCAS )

SOL 200 DOES NOT SUPPORT SRESOLVE=YES FOR FATIGUE ANALYSIS

User information: SRESOLVE=NO CAN BE USED IN A FATIGUE ANALYSIS FOR OPTIMIZA-

TION

11037. *** USER FATAL MESSAGE 11037. (FTGCAS5)

ELEMENT ID = %1 IS A 1D ELEMENT THAT IS BEING USED IN A REGULAR FATIGUE ANAL-
YSIS.

User information: 1D ELEMENTS CAN ONLY BE USED AS SPOT WELDS IN A FATIGUE ANAL-
YSIS.

11037.1 *** USER FATAL MESSAGE 11037.1 (FTGCAS5)

ELEMENT ID = %1 IS BEING INVOKED IN A SPOT WELD ANALYSIS AND IS A SOLID ELE-
MENT, BUT NOT A CHEXA.

User information: THE CHEXA IS THE ONLY SOLID ELEMENT THAT CAN BE USED IN A
SPOT WELD ANALYSIS.

11037.2 *** USER FATAL MESSAGE 11037.2 (FTGCAS5)

ELEMENT ID = %1 IS BEING INVOKED IN A SPOT WELD ANALYSIS BUT IT IS A 2D ELE-
MENT.

User information: ONLY 1D ELEMENTS OR 3D ELEMENTS OF TYPE CHEXA CAN BE USED IN

A SPOT WELD ANALYSIS.

11037.3 *** USER FATAL MESSAGE 11037.3 (FTGCAS5)

Main Index
 MSC Nastran Error Messages 1099
Errors 11000 - 11999

ELEMENT ID = %1 IS BEING INVOKED IN A SEAM WELD ANALYSIS BUT IT IS A SOLID,

SHEAR OR 1D ELEMENT.

User action: ONLY 2D PLATES CAN BE USED TO REPRESENT SEAM WELDS.

11037.4 *** USER FATAL MESSAGE 11037.4 (FTGCAS5)

COMB = "CRITICAL" ON THE FTGPARM ENTRY CANNOT BE APPLIED TO SOLID ELE-
MENTS UNLESS SRESOLVE ON THE SAME ENTRY IS SET TO "YES"

User action: REMOVE THE COMB = "CRITICAL" OR ADD SRESOLVE = "YES"

11038.0 *** USER FATAL MESSAGE 11038.0 (FTGSL2B)

FTGLOAD %1 INVOKES TYPE=RPC FILE ASKING FOR CHANNEL NO. %2, BUT THERE ARE
ONLY %3 CHANNELS AVAILABLE.

11038.1 *** USER FATAL MESSAGE 11038.1 (FTGSL2B)

FTGLOAD %1 INVOKES TYPE=DAC OR DB FILE, BUT THE ASSOCIATED UDNAME IS AN
ITYPE = %2 FILE.

User information: DAC FILES ARE ITYPE=1.

11038.2 *** USER FATAL MESSAGE 11038.2 (FTGSL2B)

FTGLOAD %1 INVOKES TYPE=RPC FILE, BUT THE ASSOCIATED UDNAME IS AN ITYPE =
%2 FILE.

User information: RPC FILES ARE ITYPE=2,3,7,or 8.

11039.0 *** USER FATAL MESSAGE 11039.0 (FTGCAS5)

FTGDEF ID = %1 HAS TOPSTR < 100.00 THAT SOL200 DOES NOT SUPPORT.

User action: RESET TOPSTR=100.0 FOR SOL200.

11039.1 *** USER FATAL MESSAGE 11039.1 (FTGCAS5)

Main Index
 1100 MSC Nastran Error Messages
Errors 11000 - 11999

FTGDEF ID = %1 HAS NHS > 0 THAT DOES NOT SUPPORT LOC=NODA OR ELEM

User action: RESET NHS=BLANK OR LOC=NODE.

11039.2 *** USER FATAL MESSAGE 11039.2 (FTGCAS5)

FTGDEF ID = %1 HAS NHS > 0 THAT SOL200 DOES NOT SUPPORT.

User action: RESET NHS=BLANK FOR SOL200.

11040.0 *** USER FATAL MESSAGE 11040.0 (FTGSURF)

SRSOLVE 'YES' SPECIFIED - BUT THERE ARE NO FREE SURFACES FOR THE DEFINED SOL-
IDS.

User action: ENSURE THAT THERE IS ATLEAST ONE FREE SURFACE FOR THE DEFINED
SOLIDS

11041.0 *** USER FATAL MESSAGE 11041. (FTGCAS)

A STANDARD SN OR EN FATIGUE ANALYSIS USING NODAL AVERAGING ( LOC=NODA )
HAS BEEN DETECTED IN CONJUNCTION WITH A FATIGUE ANALYSIS OF SPOT AND/OR
SEAM WELDS.
THIS IS NOT ALLOWED. CHANGE LOC TO ELEM OR NODE. OR RUN THE STANDARD
FATIGUE ANALYSIS AND SPOT/SEAM WELD ANALYSIS UNDER DIFFERENT FATIGUE IDS.

11041.1 *** USER FATAL MESSAGE 11041. (FTGCAS)

SET OPTION ON FATIGUE CASE CONTOL NOT SUPPORTED FOR VIBRATION FATIGUE.
PLEASE USE BULK OPTION.

11041.2 *** USER FATAL MESSAGE 11041. (FTGCAS)

FREQUENCY SET ID CHANGE DETECTED AMONG SUBCASES.

User action: FOR FREQUENCY FATIGUE ANALYSIS, PLACE FREQUENCY ABOVE SUBCASE
LEVEL.

11041.3 *** USER FATAL MESSAGE 11041. (FTGCAS)

Main Index
 MSC Nastran Error Messages 1101
Errors 11000 - 11999

THE LOOKUP TABLE FILE NAME %1 CAN NOT BE FOUND.

User action: PLEASE CHECK THE LOOKUP TABLE FILE AS DEFINED BY THE SPOTWELD
KEYWORD

11041.4 *** USER INFORMATION MESSAGE 11041. (FTGCAS)

ADDITIONAL MESSAGE(S) IN JOBNAME_CFV.log for VIBRATION FATIGUE

11042.0 *** USER INFORMATION MESSAGE 11042. ( SUBDMAP SEDRCVR / SEMTRAN )

START PRINTING FATIGUE STRESSES AND STRAINS
STRESS / STRAIN OUTPUT FOR ELEMENTS REQUESTED FOR FATIGUE ANALYSIS IN
FTGDEF FOLLOWS.

11042.1 *** USER INFORMATION MESSAGE 11042. ( SUBDMAP SEDRCVR / SEMTRAN )

START PRINTING screened ELEMENT STRESSES or STRAINS for fatigue ID %1

11043.0 *** USER INFORMATION MESSAGE 11043. ( SUBDMAP SEDRCVR / SEMTRAN )

END PRINTING FATIGUE STRESSES AND STRAINS
STRESS / STRAIN OUTPUT FOR ELEMENTS REQUESTED FOR FATIGUE ANALYSIS IN
FTGDEF.

11043.1 *** USER INFORMATION MESSAGE 11042. ( SUBDMAP SEDRCVR / SEMTRAN )

END PRINTING screened ELEMENT STRESSES or STRAINS for fatigue ID %1

11044.0 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

DATABLOCK FTGCFVI DOES NOT EXIST.

User action: PLEASE CHECK INPUT DATA TO ENSURE THAT IT IS COMPLETE FOR RUN-
NING NASTRAN EMBEDDED VIBRATION FATIGUE.

11044.1 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

CORRUPTION OF FTGCFVI DATABLOCK HAS OCCURRED.

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

11044.2 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

Main Index
 1102 MSC Nastran Error Messages
Errors 11000 - 11999

MULTI INPUT LOADING MISMATCH.

User action: ALL DEFINED SUBCASES MUST CARRY RANDOM LOADING.

11044.3 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

ERROR PROCESSING STRESSES INSIDE CAEFATIGUE VIBRATION.
PLEASE CHECK MESSAGES ABOVE.

11044.4 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

ERROR PROCESSING STRESSES INSIDE CAEfatigue RANDOM VIBRATION.
PLEASE CHECK MESSAGES ABOVE.

11044.5 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

UNEXPECTED END OF FILE WHILE RE-READING STRESSES FOR 2nd PASS THROUGH
CAEFATIGUE RANDOM VIBRATION.
PLEASE CHECK MESSAGES ABOVE - IF ANY - FOR MISMATCHES'

11044.6 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

ERROR WHILE PROCESSING STATIC STRESSES INSIDE CAEfatigue RANDOM VIBRATION.
PLEASE CHECK MESSAGES ABOVE AND ADDITIONAL MESSAGE(S) IN JOBNAME_CFV.log.

11044.7 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

ERROR WHILE COMPUTING DAMAGE INSIDE CAEfatigue RANDOM VIBRATION.
PLEASE CHECK MESSAGES ABOVE AND ADDITIONAL MESSAGE(S) IN JOBNAME_CFV.log.

11044.8 *** USER INFORMATION MESSAGE 11044.0 ( SUBDMAP SEDRCVR / SEMTRAN )

NO VIBRATION FATIGUE RESULT TO REPORT DUE TO USER INPUT MISMATCH.

User action: CHECK INPUT ON FREQUENCY RANGES OF PSD and FORCING FREQUENCIES.

11045.0 *** USER INFORMATION MESSAGE 11045.0 ( ftgcsv2 )

FTGID data block ( %1 ) is invalid.
FATIGUE Record JOBID (= %2 ) does not match active JOBID (= %3)

11045.1 *** USER FATAL MESSAGE 11045.1 ( ftgcsv2 )

Main Index
 MSC Nastran Error Messages 1103
Errors 11000 - 11999

CAEFatigue Internal error. Unable to locate TIM2PSD for second pass processing.
No %1 rcord found in %2 datablock.
Reason is %3.

11045.2 *** SYSTEM FATAL MESSAGE 11045.2 ( ftgcsv2 )

Vibration Fatigue Feature is not available with I4 version of Nastran.
Rerun with MODE=I8 specified.

11045.3 *** SYSTEM FATAL MESSAGE 11045.2 ( ftgcsv2 )

Datablock %2 larger than GREAD buffer. Buffer length = %1 words.

11045.4 *** SYSTEM FATAL MESSAGE 11045.2 ( ftgcsv2 )

Insufficient memory to build NEVF input control file. %1 words used.
Increase MEM= specification on job submittal.

11046.0 *** SYSTEM FATAL MESSAGE 11045.2 ( ftgcsv2 )

Specified FTGLOAD TYPE=PSD TID values are not in increasing unit order.
Entries out of order have TID values %1 and %2.

11046.1 *** SYSTEM FATAL MESSAGE 11046.1 ( ftgcsv2 )

Specified EVENT ID Values in TIM2PSD entry %1 are not in increasing unit order.
Entries out of order have EVENT IDs %2 and %3.

11046.2 *** SYSTEM FATAL MESSAGE 11046.2 ( ftgcsv2 )

Number of EVENT entries (=%1) in TIM2PSD entry %2 does not match number of FTGLOAD
TYPE=PSD entries (=%3)

11046.3 *** SYSTEM FATAL MESSAGE 11046.3 ( ftgcsv2 )

Starting EVENT ID (=%1) in TIM2PSD entry %2 does not match starting FTGLOAD TYPE=PSD'
starting TID (=%3)

11046.4 *** SYSTEM FATAL MESSAGE 11046.4 ( ftgcsv2 )

Invalid TIM2PSD DELETE pair. EVID = %1, DELETE Entry %2
START,END = %3, %4
Start and End time must be positive. And, START TIME MUST BE GREATER THAN END TIME.

Main Index
 1104 MSC Nastran Error Messages
Errors 11000 - 11999

11046.5 *** SYSTEM FATAL MESSAGE 11046.5 ( ftgcsv2 )

No active FTGLOAD TYPE=PSD entries found. TIM2PSD record ignored.

11046.6 *** SYSTEM FATAL MESSAGE 11046.6 ( ftgcsv2 )

There is no loads file specified for TID %1.
TIM2PSD processing cannot complete.

11046.7 *** SYSTEM FATAL MESSAGE 11046.7 ( ftgcsv2 )

TIM2PSD MAP count (=%1) does nout match the SUBCASE count (=%2).

11046.8 *** SYSTEM FATAL MESSAGE 11046.8 ( ftgcsv2 )

TIM2PSD MAP data specifies duplicate channel numbers.
Channel number for LCID %1 is the same as channel number for LCID %2
Specified channel number is %3.

11046.9 *** SYSTEM FATAL MESSAGE 11046.6 ( ftgcsv2 )

TIM2PSD MAP data specifies duplicate LCID values. LCID %1 is repeated.
The associated channel numbers are %2 and %3.

11047.0 *** SYSTEM FATAL MESSAGE 11046.6 ( ftgcsv2 )

no FTGLOAD entries were specified.

11047.1 *** SYSTEM FATAL MESSAGE 11046.6 ( ftgcsv2 )

FTGEVNT entry with ID %1 does not refer to any supported FTGLOAD NEVF entries. It is ignored.

11048.0 *** SYSTEM FATAL MESSAGE 11046.6 ( ftgcsv2 )

FTGLOAD entry with ID %1 is TYPE=SINE or TYPE=NARROW and has both DETLOAD and
SWEEP entries.
This combination is not valid.

11048.1 *** SYSTEM FATAL MESSAGE 11046.6 ( ftgcsv2 )

FTGLOAD record with ID %1 specifies an unsupported combination of options. It is ignored.

11049.0 *** SYSTEM FATAL MESSAGE 11046.6 ( ftgcsv2 )

Main Index
 MSC Nastran Error Messages 1105
Errors 11000 - 11999

Nastran MATFTG record has unknown/unsupported format.

Minimum supported length = %2, actual length = %3.

11050.0 *** SYSTEM WARNING MESSAGE 11050.0 (FTGPOST)

STROUT=%1 in FATIGUE case control supersedes STROUT=%2 on FTGPARM bulk data entry of
ID=%3.

11051.0 *** USER FATAL MESSAGE 11051.0 (FTGCAS)

Non-zero NENTS=%1 (on FTGDEF bulk data entry ID=%2) is not supported for SOL 200.

11052.0 *** USER WARNING MESSAGE 11052 (FTGSTR4)

CSV file is not in DT TimeSeries CSV format:
%1

11053.0 *** USER WARNING MESSAGE 11053 (GetChnlData)

Time Series channel file %1 is not of specified type

11054.0 *** USER WARNING MESSAGE 11054 (GetChnlData)

There appear to be no channels in channel file: %1

11054.1 *** USER WARNING MESSAGE 11054 (GetChnlData)

Can't create file object for channel file: %1

11054.2 *** USER WARNING MESSAGE 11054 (GetChnlData)

Can't initialize file object for channel file: %1

11054.3 *** USER WARNING MESSAGE 11054 (GetChnlData)

Can't create TsAcc object for channel file: %1

11054.4 *** USER WARNING MESSAGE 11054 (GetChnlData)

Error closing channel file %1

11055.0 *** USER WARNING MESSAGE 11055 (GetChnlData)

Error setting file id for channel file: %1
PROGRAMMER INFORMATION: %2 failed with: %3

Main Index
 1106 MSC Nastran Error Messages
Errors 11000 - 11999

11055.1 *** USER WARNING MESSAGE 11055 (GetChnlData)

Error getting number of points in channel %1 in file %2
PROGRAMMER INFORMATION: %3 failed with: %4

11055.2 *** USER WARNING MESSAGE 11055 (GetChnlData)

Error preparing CHANnel file %1 for reading
PROGRAMMER INFORMATION: %2 failed with: %3

11055.3 *** USER WARNING MESSAGE 11055 (GetChnlData)

Error reading CHANnel data from file %1
PROGRAMMER INFORMATION: %2 failed with: %3

11055.4 *** USER WARNING MESSAGE 11055 (GetChnlData)

Error getting time corresponding to point %1 in channel file %2

11056.0 *** USER WARNING MESSAGE 11056 (GetChnlData)

Failed opening file %1

11057.0 *** USER WARNING MESSAGE 11057 (GetChnlData)

Error validating CHANnel %1 in file %2
Valid channels appear to be:
%3

11057.1 *** USER WARNING MESSAGE 11057 (GetChnlData)

CHANnel %1 is not a valid channel in file %2
Valid channels appear to be:
%3

11057.2 *** USER WARNING MESSAGE 11057 (GetChnlData)

Failed getting channel index from CHANnel %1 from file %2

11057.3 *** USER WARNING MESSAGE 11057 (GetChnlData)

Failed getting number of channels from file %1

11057.4 *** USER WARNING MESSAGE 11057 (GetChnlData)

Failed getting channel numbers from file %1

Main Index
 MSC Nastran Error Messages 1107
Errors 11000 - 11999

11058.0 *** USER WARNING MESSAGE 11058 (GetChnlData)

Not enough memory to process channel file %1

11059.0 *** USER WARNING MESSAGE 11059 (GetChnlData)

Number of points read: %1 differs from actual number of points: %2 in CHANnel data file %3

11060.0 *** USER FATAL MESSAGE 11060 (FTGCASc)

STROUT=4 cannot be honored for %1 entities due to performance issues.

User information: Maximum number of entities (maxENTS) = %2 is set on FTGDEF %3 entry.

User action: To avoid this error, please modify FTGDEF %3 entry:

1. to reduce the number of entities by using ELSET and/or XELSET keywords to include/exclude
element IDs, or
2. to increase maxENTS (Note that this can cause severe performance issues).

11060.1 *** USER FATAL MESSAGE 11060 (FTGCASc)

STROUT=4 cannot be honored for %1 entities due to performance issues.

USER INFORMATION: Maximum number of entities (maxENTS) = %2 since FTGDEF %3 entry does
not exist.

User action: To avoid this error, please add FTGDEF %3 entry:

1. to reduce the number of entities by using ELSET and/or XELSET keywords to include/exclude
element IDs, or
2. to increase maxENTS (Note that this can cause severe performance issues).

11101.0 *** USER FATAL MESSAGE 11101 (MDG2HR)

AXISYMMETRIC HARMONIC ELEMENT ID %1 IS ASSOCIATED WITH MORE THAN ONE
ROTORAX ID (ROTORAX IDS %2 AND %3)

11102.0 *** USER FATAL MESSAGE 11102 (MDG2HR)

GRID POINT %1 REFERENCED ON ONE OR MORE AXISYMMETRIC HARMONIC ELE-
MENTS IS ASSOCIATED WITH MORE THAN ONE ELEMENT COORDINATE SYSTEM ID
SPECIFIED ON PAXSYMH ENTRIES (ELEMENT COORDINATE SYSTEM IDS %2 AND %3)

Main Index
 1108 MSC Nastran Error Messages
Errors 11000 - 11999

11102.1 *** USER FATAL MESSAGE 11102 (MDG2HR)

GRID POINT %1 REFERENCED ON ONE OR MORE AXISYMMETRIC HARMONIC ELE-
MENTS IS ASSOCIATED WITH MORE THAN ONE HARMONIC INDEX SPECIFIED ON PAX-
SYMH ENTRIES (HARMONIC INDICES %2 AND %3)

11103.0 *** USER FATAL MESSAGE 11103 (MDG2HR)

GRID POINT %1 REFERENCED ON ONE OR MORE AXISYMMETRIC HARMONIC ELE-
MENTS IS ASSOCIATED WITH MORE THAN ONE ROTORAX ID (ROTORAX IDS %2 AND
%3)

11104.0 *** USER FATAL MESSAGE 11104 (MDG2HR)

ROTORAX ID %1 DOES NOT HAVE ANY ROTORAX ENTRIES USING THE GRID OPTION
FOR DEFINING ITS AXIS OF ROTATION

11104.1 *** USER FATAL MESSAGE 11104 (MDG2HR)

ROTORAX ENTRY %1 WITH THE GRID OPTION HAS ONLY ONE GRID POINT (GRID
POINT ID %2) SPECIFIED FOR DEFINING ITS AXIS OF ROTATION

11105.0 *** USER FATAL MESSAGE 11105 (MDG2HR)

THE INDEPENDENT POINT %1 SPECIFIED IN RBAX3D ENTRY %2 DOES NOT EXIST

11105.1 *** USER FATAL MESSAGE 11105 (MDG2HR)

THE DEPENDENT POINT %1 SPECIFIED IN RBAX3D ENTRY %2 DOES NOT EXIST

11106.0 *** USER FATAL MESSAGE 11106 (MDG2HR)

THE INDEPENDENT POINT %1 SPECIFIED IN RBAX3D ENTRY %2 IS AMONG THE GRID
POINTS REFERENCED BY THE AXISYMMETRIC HARMONIC ELEMENTS

User information: THE INDEPENDENT POINT SPECIFIED IN AN RBAX3D ENTRY MAY NOT
BE AMONG THE GRID POINTS REFERENCED BY THE AXISYMMETRIC HARMONIC ELE-
MENTS

11106.1 *** USER FATAL MESSAGE 11106 (MDG2HR)

Main Index
 MSC Nastran Error Messages 1109
Errors 11000 - 11999

THE DEPENDENT POINT %1 SPECIFIED IN RBAX3D ENTRY %2 IS NOT AMONG THE

GRID POINTS REFERENCED BY THE AXISYMMETRIC HARMONIC ELEMENTS

User information: THE DEPENDENT POINT SPECIFIED IN AN RBAX3D ENTRY MUST BE

AMONG THE GRID POINTS REFERENCED BY THE AXISYMMETRIC HARMONIC ELE-
MENTS

11107.0 *** USER FATAL MESSAGE 11107 (MDG2HR)

THE DEPENDENT POINT %1 SPECIFIED IN RBAX3D ENTRY %2 IS ASSOCIATED WITH
HARMONIC INDEX %3

User information: THE DEPENDENT POINT SPECIFIED IN AN RBAX3D ENTRY MUST BE

ASSOCIATED ONLY WITH EITHER HARMONIC INDEX 0 OR HARMONIC INDEX 1

11108.0 *** USER FATAL MESSAGE 11108 (CMBLCHEK or UNBALCHK)

THERE IS A REQUEST FOR CAMPBELL DIAGRAM, BUT THE SELECTED RGYRO ENTRY %1
HAS THE SYNC OPTION SPECIFIED IN THE SYNCFLG FIELD

User information: WHEN THERE IS A REQUEST FOR CAMPBELL DIAGRAM, THE SELECTED
RGYRO ENTRY MUST HAVE THE ASYNC OPTION SPECIFIED IN THE SYNCFLG FIELD

11108.1 *** USER FATAL MESSAGE 11108 (CMBLCHEK or UNBALCHK)

THERE IS A REQUEST FOR CAMPBELL DIAGRAM IN SUBCASE %1, BUT THE SELECTED
RGYRO ENTRY %2 HAS THE SYNC OPTION SPECIFIED IN THE SYNCFLG FIELD

User information: WHEN THERE IS A REQUEST FOR CAMPBELL DIAGRAM, THE SELECTED
RGYRO ENTRY MUST HAVE THE ASYNC OPTION SPECIFIED IN THE SYNCFLG FIELD

11108.2 *** USER FATAL MESSAGE 11108 (CMBLCHEK)

REQUESTED RGYRO ENTRY %1 DOES NOT EXIST

11108.3 *** USER FATAL MESSAGE 11108 (CMBLCHEK)

RGYRO ENTRY %1 REQUESTED IN SUBCASE %2 DOES NOT EXIST

11109.0 *** USER FATAL MESSAGE 11109 (UNBALCHK)

Main Index
 1110 MSC Nastran Error Messages
Errors 11000 - 11999

CASE CONTROL REQUEST DLOAD %1 REFERENCES AN UNBALNC LOAD, BUT THE

SELECTED RGYRO ENTRY %2 HAS THE ASYNC OPTION SPECIFIED IN THE SYNCFLG
FIELD

User information: WHEN UNBALNC LOAD IS USED, THE SELECTED RGYRO ENTRY MUST
HAVE THE SYNC OPTION SPECIFIED IN THE SYNCFLG FIELD

11109.1 *** USER FATAL MESSAGE 11109 (UNBALCHK)

CASE CONTROL REQUEST DLOAD %2 IN SUBCASE %1 REFERENCES AN UNBALNC LOAD,
BUT THE SELECTED RGYRO ENTRY %3 HAS THE ASYNC OPTION SPECIFIED IN THE SYN-
CFLG FIELD

User information: WHEN UNBALNC LOAD IS USED, THE SELECTED RGYRO ENTRY MUST
HAVE THE SYNC OPTION SPECIFIED IN THE SYNCFLG FIELD

11110.0 *** SYSTEM FATAL MESSAGE 11110

LOGIC ERROR ENCOUNTERED IN SUBDMAP %1

11110.1 *** USER FATAL MESSAGE 11110 (GYROBASE)

MASS MATRIX IS NOT DEFINED FOR ROTOR %1

11110.2 *** USER INFORMATION MESSAGE 11110 (GYROBASE)

STATIC GYROLOAD CAN BE CALCULATED DIRECTLY FOR 1D ROTOR (ROTORG) ONLY

11111.0 *** USER FATAL MESSAGE 11111 (SEMTRAN)

ROTORDYNAMICS ANALYSIS IS NOT SUPPORTED IN MODAL TRANSIENT ANALYSIS

11112.0 *** USER FATAL MESSAGE 11112 (SEDCEIG and SEMCEIG)

THERE IS NO CMETHOD CASE CONTROL REQUEST SPECIFIED FOR THIS COMPLEX
EIGENVALUE ANALYSIS

User information: THE USER CAN OVERRIDE THIS CHECK AND LET NASTRAN CONTINUE
THE EXECUTION BY SPECIFYING PARAM,NOCMETH,1

11112.1 *** USER WARNING MESSAGE 11112 (SEDCEIG and SEMCEIG)

THERE IS NO CMETHOD CASE CONTROL REQUEST SPECIFIED FOR THIS COMPLEX
EIGENVALUE ANALYSIS

Main Index
 MSC Nastran Error Messages 1111
Errors 11000 - 11999

11112.2 *** USER FATAL MESSAGE 11112 (SEMCEIG)

DMP > 1 IS NOT SUPPORTED FOR SOL 110 WITH CAMPBELL OPTION WHEN ACMS
OPTION IS NOT USED

11113.0 *** USER FATAL MESSAGE 11113 (MDG2RX)

TWO OR MORE %1 ENTRIES HAVE THE SAME VALUES OF ROTORID = %2 AND ROTR-
SEID = %3

11114.0 *** USER INFORMATION MESSAGE 11114 (ROTOR1)

THERE IS NO MASS SUMMARY INFORMATION AVAILABLE IN THIS EXECUTION FOR THE
FOLLOWING ROTORS THAT HAVE BEEN DEFINED IN UPSTREAM SUPERELEMENTS.
PLEASE SEE THE .F06 OUTPUT OF THE CREATION JOBS FOR THESE SUPERELEMENTS
FOR THE RELEVANT INFORMATION.

11115.0 *** USER FATAL MESSAGE 11115 (PHASE1DR)

THERE ARE ROTORS IN THE DATA AND THE USER HAS SPECIFIED AN EXTSEOUT or
EXTMDOUT CASE CONTROL COMMAND WITH THE DMIGPCH OR MATOP4/MATRIX-
OP4 OPTION

User information: NASTRAN CURRENTLY DOES NOT SUPPORT THE USE OF THESE EXTSE-
OUT or EXTMDOUT OPTIONS FOR ROTORDYNAMICS CALCULATIONS.

11116.0 *** USER FATAL MESSAGE 11116 (MDG2RX)

GRID POINT %1 REFERENCED IN %2 ENTRY %3 (WITH ROTRSEID = %4) DOES NOT
EXIST

11116.1 *** USER FATAL MESSAGE 11116 (MDG2RX)

GRID POINT %1 REFERENCED IN UNBALNC ENTRY %2 DOES NOT EXIST

11117.0 *** USER FATAL MESSAGE 11117 (RDSEBULK)

EXTERNAL SUPERELEMENT USAGE IS CURRENTLY NOT SUPPORTED IN SOL 400

11118.0 *** USER FATAL MESSAGE 11118 (MDG2ROT)

Main Index
 1112 MSC Nastran Error Messages
Errors 11000 - 11999

ROTOR DEFINED BY ROTOR ENTRY %1 HAS FIXED FRAME SPECIFIED FOR IT

User information: NASTRAN CURRENTLY SUPPORTS THE USE OF ONLY ROTATING FRAME
FOR THE ROTOR ENTRY

11118.1 *** USER FATAL MESSAGE 11118 (MDG2ROT)

ROTOR DEFINED BY ROTOR ENTRY %1 HAS NO ELEMENTS COMPRISING IT

User information: A ROTOR ENTRY MUST HAVE AT LEAST ONE ELEMENT COMPRISING IT

11118.2 *** USER FATAL MESSAGE 11118 (MDG2ROT)

ROTOR DEFINED BY ROTOR ENTRY %1 HAS NO AXIS OF ROTATION SPECIFIED FOR IT

User information: A ROTOR ENTRY MUST HAVE ITS AXIS OF ROTATION DEFINED

11118.3 *** USER FATAL MESSAGE 11118 (MDG2ROT)

ROTOR DEFINED BY ROTOR ENTRY %1 HAS ONLY ONE GRID POINT SPECIFIED FOR ITS
AXIS OF ROTATION

User information: A ROTOR ENTRY MUST HAVE ITS AXIS OF ROTATION DEFINED BY SPEC-
IFYING AT LEAST TWO GRID POINTS

11118.4 *** USER FATAL MESSAGE 11118 (MDG2ROT)

ROTOR ENTRIES USING ROTATING FRAME MAY NOT BE EMPLOYED IN CONJUNCTION
WITH ROTORG, ROTORSE OR ROTORAX ENTRIES OR WITH OTHER ROTOR ENTRIES
USING FIXED FRAME

11118.5 *** USER FATAL MESSAGE 11118 (MDG2ROT)

%1 ID %2 IS SPECIFIED IN MORE THAN ONE ROTOR ENTRY AS INDICATED BELOW:

11118.6 *** USER FATAL MESSAGE 11118 (MDG2ROT)

ELEMENT %1 ON ROTOR %2 IS NOT SUPPORTED BY NASTRAN 3D ROTORDYNAMIC
ANALYSIS
CHECK QRMETH (OR SYSTEM(370)) FOR POSSIBLE QUAD4/TRIA3 CONVERTS TO
QUADR/TRIAR

11118.7 *** USER FATAL MESSAGE 11118 (MDG2ROT)

Main Index
 MSC Nastran Error Messages 1113
Errors 11000 - 11999

ELEMENT %1 ON ROTOR %2 IS NOT SUPPORTED BY NASTRAN 3D ROTORDYNAMIC

ANALYSIS

11118.8 *** USER FATAL MESSAGE 11118 (MDG2ROT)

CONM2 EID = %1 AT GRID %2 ON ROTOR %3 HAS NON-ZERO OFFSET (X1/X2/X3)
CONM2 OFFSET IS CURRENTLY NOT SUPPORTED BY NASTRAN 3D ROTORDYNAMIC
ANALYSIS

User action: MOVE OR GENERATE CONM2 TO GRID WITH ZERO OFFSET

11119.0 *** USER INFORMATION MESSAGE 11119 (SEKDR)

AT THE USER'S REQUEST, DIFFERENTIAL STIFFNESS CALCULATIONS WILL BE PER-
FORMED FOR ALL ROTORS THAT ARE DEFINED VIA ROTOR BULK DATA ENTRIES

11119.1 *** USER FATAL MESSAGE 11119 (SEKDR)

DIFFERENTIAL STIFFNESS CALCULATIONS FOR ROTORS ARE CURRENTLY NOT IMPLE-
MENTED FOR EXTERNAL SUPERELEMENT JOBS

11119.2 *** USER INFORMATION MESSAGE 11119 (IFPS)

FOR ROTORDYNAMIC ANALYSIS IN SOL 400, DEFAULT IS MODIFIED TO RIGID = LINEAR

11119.3 *** USER INFORMATION MESSAGE 11119 (IFPS)

FOR ANALYSIS = STATICS IN SOL 400 FOR EXT AND PART SE ANALYSIS, DEFAULT IS MOD-
IFIED TO RIGID = LINEAR

11119.4 *** USER WARNING MESSAGE 11119 (IFPS)

IF ONLY LINEAR ANALYSIS IN SOL 400, CASI OR PARDISO MAY FAIL DUE TO SEMI-POSI-
TIVE DEFINITE OR INDEFINITE MATRIX.

User action: CONSIDER CHANGING RIGID=LINEAR OR MSCLDL SOLVER.

11120.0 *** USER FATAL MESSAGE 11120 (EQD8D)

CQUAD8 ELEMENTS ARE NOT SUPPORTED FOR ANALYSIS IN ROTATING REFERENCE
FRAME.
CQUAD8 ELEMENT (ID %1) IS DEFINED IN ROTOR %2

Main Index
 1114 MSC Nastran Error Messages
Errors 11000 - 11999

11120.1 *** USER FATAL MESSAGE 11120 (ETR6D)

CTRIA6 ELEMENTS ARE NOT SUPPORTED FOR ANALYSIS IN ROTATING REFERENCE
FRAME.
CTRIA6 ELEMENT (ID %1) IS DEFINED IN ROTOR %2

11121.0 *** USER INFORMATION MESSAGE 11121 (RSDAMP)

"MDLPRM,RDBOTH"/"SYSTEM CELL 695" ACTIVATED
ALPHA1 AND ALPHA2 WILL BE APPLIED TO THE ENTIRE STRUCTURE (INCLUDING ANY
ROTORS). ALPHAR1 AND ALPHAR2, IF SPECIFIED IN RSPINR/RSPINT, WILL BE ASSIGNED
ZERO VALUE.

11122.0 *** USER FATAL MESSAGE 11122 (GYROMAT)

WHIRLOPT IS NEITHER "FWD" NOR "BWD"

11122.1 *** USER FATAL MESSAGE 11122 (GYROMAT)

WR3WRL (OR WR4WRL OR WRHWRL) IN RGYRO CANNOT BE SPECIFIED ALONG WITH
WR3 (OR WR4 OR WRH) OR WR3R (OR WR4R OR WRHR)

11122.2 *** USER FATAL MESSAGE 11122 (GYROMAT)

RDBOTH BIT5=1(16) IN MDLPRM CANNOT BE SPECIFIED ALONG WITH WR3 (OR WR4
OR WRH) OR WR3R (OR WR4R OR WRHR) OR WR3WRL (OR WR4WRL OR WRHWRL)

11123.0 *** USER FATAL MESSAGE 11123 (NLTRAN)

NONLINEAR IS SPECIFIED IN CASE CONTROL WITHOUT A CORRESPONDING NONLIN-
EAR ELEMENT IN BULK DATA SECTION

11124.0 *** USER INFORMATION MESSAGE 11124 (SEMCEIG/SEDCEIG/CMPLCEIG)

EIGENVECTOR BASED MODE TRACKING IS SELECTED FOR CAMPBELL DIAGRAM.
TRACKING PARAMETERS ARE:
CAMCORU = %1
SWITR = %2
PRTCOR = %3

11124.1 *** USER INFORMATION MESSAGE 11124 (SEMCEIG/SEDCEIG/CMPLCEIG)

SUCCESSFUL MODE TRACKING AT SPIN SPEED = %1 HZ (%2 RPM)

11124.2 *** USER INFORMATION MESSAGE 11124 (SEMCEIG/SEDCEIG/CMPLCEIG)

Main Index
 MSC Nastran Error Messages 1115
Errors 11000 - 11999

SUCCESSFUL MODE TRACKING (PARTIAL) AT SPIN SPEED = %1 HZ (%2 RPM)

11124.3 *** USER INFORMATION MESSAGE 11124 (SEMCEIG/SEDCEIG/CMPLCEIG)

FAILED MODE TRACKING AT SPIN SPEED = %1 HZ (%2 RPM)

11124.4 *** USER FATAL MESSAGE 11124 (SEMCEIG/SEDCEIG)

CLAN OPTION FOR COMPLEX EIGENVALUE ANALYSIS IS NOT SUPPORTED FOR EIGEN-
VECTOR BASED MODE TRACKING.

11124.5 *** USER FATAL MESSAGE 11124 (SEMCEIG/SEDCEIG/CMPLCEIG)

EIGENVECTOR BASED MODE TRACKING IS NOT SUPPORTED FOR ANALYSIS IN
ROTATING REFERENCE FRAME.
TURN OFF EIGENVECTOR BASED MODE TRACKING BY SETTING MDTRK FIELD TO
ZERO IN CAMPBLL BULK DATA ENTRY.

11124.6 *** USER INFORMATION MESSAGE 11124 (SEMCEIG/SEDCEIG/CMPLCEIG)

SLOPE CONTINUITY BASED NUMERICAL MODE TRACKING WILL NOT BE PERFORMED.
ONLY EIGENVECTOR-BASED MODE TRACKING WILL BE CARRIED OUT.

11124.7 *** USER WARNING MESSAGE 11124 (SEDCEIG/CMPLCEIG)

NORMALIZED CROSS COMPLEX ORTHOGONALITY (NC2O) BASED MODE TRACKING
WITH CLAN METHOD IN EIGC IS APPLIED IN CAMPBELL DIAGRAM.
HESS OPTION IN EIGC IS RECOMMENDED FOR NC2O MODE TRACKING METHOD.
LARGE MODEL WITH CLAN OPTION MAY GENERATE LARGE SIZE MATRICES NC2O CAN
NOT HANDLE.
FOR LARGE MODELS USING NC2O MODE TRACKING, MODAL CEIG OR A SUPERELE-
MENT BASED REDUCTION APPROACH IS RECOMMENDED.

11125.0 *** USER WARNING MESSAGE 11125 (VECMDTR)

NUMBER OF MODES WITH POSITIVE IMAG FREQUENCY AT CURRENT ROTOR SPIN
SPEED OF %1 HZ (%2 RPM) IS NOT SAME AS THOSE AT PREVIOUS ROTOR SPEED

User action: SPECIFY NUMMOD < 0.5*(NUMBER OF COMPLEX EIGENVALUES) IN CAMPBLL

ENTRY

11125.1 *** USER INFORMATION MESSAGE 11125 (VECMDTR)

Main Index
 1116 MSC Nastran Error Messages
Errors 11000 - 11999

NUMBER OF MODES USED FOR EIGENVECTOR-BASED MODE TRACKING : %1

11126.0 *** USER INFORMATION MESSAGE 11126 (CAMPREP)

FIELD %1 IN CAMPBLL ENTRY CAN HAVE VALUES 0, 1 OR 2 ONLY.

11126.1 *** USER INFORMATION MESSAGE 11126 (CAMPREP)

FIELD %1 IN CAMPBLL ENTRY CAN HAVE VALUES BETWEEN 0.0 AND 1.0 ONLY.

11127.0
RGYRO Case Control command is present but there are no rotors defined.

User action: Remove the RGYRO command if rotors are not present in the model.
11128.0 *** USER INFORMATION MESSAGE 11128 (NLHARM)
PARAMETERS USED FOR NON-LINEAR FREQ RESP ANALYSIS
NLHRED = %1
MXICODE0 = %2
TICPNCH = %3
NLHTOL = %4
NLHTWK = %5
NHPLUS = %6
MNCSF = %7
MFRINT = %8
NLHDIAG = %9
CONTP = %10

11128.1 *** USER INFORMATION MESSAGE 11128 (NLHARM)

FOR CONTINUATION PROCESS, NLHRED IS SET TO ZERO.

11128.2 *** USER INFORMATION MESSAGE 11128 (NLHARM)

NLHDIAG OUTPUT : ITER = %1, FREQ = %2, RESVAL =%3, TOLVAL =%4, ICODE = %5

11128.3 *** USER FATAL MESSAGE 11128 (NLHARM)

FREQUENCY (%1) AT THE CURRENT ITERATION STEP IS NEGATIVE.

User information: THIS CAN HAPPEN DUE TO TURNING-BACK OF SOLUTION. RESTART

THE ANALYSIS WITH SMALLER FREQUENCY STEP

Main Index
 MSC Nastran Error Messages 1117
Errors 11000 - 11999

11128.4 *** USER FATAL MESSAGE 11128 (NLHARM)

FOR ANALYSIS WITH CONTINUATION PROCEDURE AT CURRENT FREQUENCY (%1),
NUMBER OF ITERATIONS (%2) HAS EXCEEDED THE LIMIT SPECIFIED BY MXICODE0
(%3).

User information: INCREASE MXICODE0 IF RESIDUAL IS DECREASING. OR. RESTART THE

ANALYSIS WITH SMALLER FREQUENCY STEP

11129.0 *** USER INFORMATION MESSAGE 11129 (NLHARM)

INITIAL CONDITION FOR THIS FREQUENCY IS OBTAINED FROM LOAD SPECIFIED.

11129.1 *** USER INFORMATION MESSAGE 11129 (NLHARM)

INITIAL CONDITION FOR THIS FREQUENCY IS ZERO.

11129.2 *** USER INFORMATION MESSAGE 11129 (NLHARM)

INITIAL CONDITION FOR THIS FREQUENCY IS THE PREVIOUSLY CONVERGED SOLU-
TION.

11129.3 *** USER INFORMATION MESSAGE 11129 (NLHARM)

INITIAL CONDITION FOR THIS FREQUENCY IS OBTAINED USING CONTINUATION PRO-
CESS.

11129.4 *** USER INFORMATION MESSAGE 11129 (NLHARM)

THE NUMBER OF CONSECUTIVE FREQUENCIES AT WHICH CONVERGENCE HAS
FAILED HAS EXCEEDED THE LIMIT DEFINED BY PARAMETER MNCSF IN NHRMPRM
ENTRY.

11129.5 *** USER INFORMATION MESSAGE 11129 (NLHARM)

THE FREQUENCY INTERVAL IN WHICH CONSECUTIVE FREQUENCIES HAVE NOT CON-
VERGED HAS BEEN EXCEEDED.

11130.0 *** USER FATAL MESSAGE 11130 (MCNTINI)

Main Index
 1118 MSC Nastran Error Messages
Errors 11000 - 11999

TOUCHING CONTACT IS NOT SUPPORTED WHEN AXISYMMETRIC HARMONIC ELE-

MENTS ARE PRESENT, ONLY PERMANENT-GLUE CONTACT MAY BE DEFINED. SET
IGLUE>0 ON THE BCTABLE ENTRY (OLD CONTACT) OR BCONPRG ENTRY (NEW CON-
TACT).
CONSULT THE QUICK REFERENCE GUIDE FOR THE MEANING OF THE DIFFERENT POS-
ITIVE VALUES.

11131.0 *** USER FATAL MESSAGE 11131 (NLHARM)

CONTINUATION PROCEDURE IS NOT SUPPORTED FOR FREQUENCY DEPENDENT
ANALYSIS.

User action: CHANGE "CONTP" TO ZERO IN NHRMPRM ENTRY

11132.0 *** USER WARNING MESSAGE 11132 (RgyAsync)

ELEMUDS %1 (referenced by CBUSH2D %2) will be ignored for SUBCASE %3 because Case Control
RGYRO=%4 refers to RGYRO %4 bulk data entry whose SYNCFLG field is not ASYNC.

11133.0 *** USER WARNING MESSAGE 11133 (udsm_011)

UDS service Elements.cbush2da for %1 (option=%2) failed with error code %3.

11134.0 *** USER FATAL MESSAGE 11134 (ext_UDSMAP)

UDS service Common.udsmap with option=%1 is NOT supported.

11134.1 *** USER FATAL MESSAGE 11134 (ext_UDSMAP)

UDS service Common.udsmap with option=%1 is NOT supported.
Make sure you have the following in your file for the external subroutine:
SUBROUTINE ext_UDSMAP and "SUBROUTINE %2" is also implemented.

11135.0 *** USER FATAL MESSAGE 11135 (IFPecP2D)

PBUSH2D %1 should NOT have INTEGER for %2 field(s) unless CROSS keyword is specified.

11136.0 *** USER FATAL MESSAGE 11136 (IFPecTD1)

%1 entry %2 referenced by %3 entry %4 does not exist.

11137.0 *** USER FATAL MESSAGE 11137 (IFPecTD1)

Unable to find any %1 entries which are referenced by %2 entry %3.

Main Index
 MSC Nastran Error Messages 1119
Errors 11000 - 11999

11138.0 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

ROTBENT = %1 Case Control call in STEP %2 of SUBCASE %3 does not have ANALYSIS =
NLSTATIC call.

User information: ROTBENT Case Control call should be defined in STEP 1 with ANALY-
SIS=NLSTATIC.

11138.1 *** USER INFORMATION MESSAGE 11138 (MDG2RBNT)

ROTBENT = %1 call in STEP %2 is ignored.

User information: ROTBENT Case Control call should be defined only in STEP 1 with ANALY-
SIS=NLSTATIC.

11138.2 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

%1 card is supported only in %2 analysis.

User information: Run ROTBENT with associated ROTOR definitions in SOL 400 analysis only.

11138.3 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

ROTBENT = %1 called in STEP ID %2 of SUBCASE %3 does not exist in the model.

11138.4 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

%2 definition not found. %1 card is supported with %2 card definition only.

User information: Run ROTBENT with associated ROTOR definitions in SOL 400 analysis only.

11138.5 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

ROTOR ID %1 referenced by ROTBENT bulk data with BID %2 does not exist in the model.

11138.6 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

%1 card is supported with %2 card definition having only 1D elements.

User information: Run ROTBENT with associated ROTOR definitions having only 1D (CBEAM,
CBAR) & CONM1, CONM2 elements. ROTBENT is not supported for ROTOR definition having 2D
or 3D element types.

Main Index
 1120 MSC Nastran Error Messages
Errors 11000 - 11999

11138.7 *** USER FATAL MESSAGE 11138 (RBNT_BRNG)

ROTBENT id %1 referenced by SUBCASE id %2 & STEP id %3 does not have either 'KINK' or 'OFF-
SET' keyword definitions.

User information: ROTBENT definition should have 'KINK' and/or 'OFFSET' keyword definition.

11138.8 *** USER FATAL MESSAGE 11138 (RBNT_BRNG)

ROTBENT id %1 referenced by SUBCASE id %2 & STEP id %3 does not have 'NBCORD' keyword
definition.

User information: ROTBENT definition should have 'NBCORD' keyword definition.

11138.9 *** USER FATAL MESSAGE 11138 (RBNT_BRNG)

ROTBENT id %1 referenced by SUBCASE id %2 & STEP id %3 does not have 'BRGDPR' keyword
definition.

User information: ROTBENT definition should have 'BRGDPR' keyword definition.

11138.10 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

%1 card in %2 analysis is not supported for multiple SUBCASE definitions.

User information: ROTBENT Case Control call is supported with only 1 SUBCASE definition.

11138.11 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

%1 card in %2 analysis is supported for 1 SUBCASE having 2 STEP analysis definition.

User information: ROTBENT Case Control call should have 1 SUBCASE, with following STEP analysis
definitions,
STEP 1 with ANALYSIS = NLSTATIC
STPE 2 with ANALYSIS = DCEIG (or) MCEIG (or) DFREQ (or) MFREQ

11138.12 *** USER FATAL MESSAGE 11138 (RBNT_BRNG)

Main Index
 MSC Nastran Error Messages 1121
Errors 11000 - 11999

ROTBENT id %1 BRGDPR keyword RTID entries do not match with referenced ROTOR id %2 AXIS
entries.

User information: ROTBENT bulk data BRGDPR keyword RTID entries should match referenced
ROTOR AXIS entries.

11138.13 *** USER INFORMATION MESSAGE 11138 (RBNT_BRNG)

For SUBCASE having ROTBENT call, following new SPOINTs are created and used in STEP 1 & STEP
2 analysis

11138.14 *** USER INFORMATION MESSAGE 11138 (RBNT_BRNG)

For SUBCASE having ROTBENT call, following new MPC are created and used in STEP 1 & STEP 2
analysis

11138.15 *** USER INFORMATION MESSAGE 11138 (RBNT_BRNG)

For SUBCASE having ROTBENT call, following new SPCD are created and used in STEP 1 analysis only

11138.16 *** USER FATAL MESSAGE 11138 (RBNT_BRNG)

When carrying out ROTBENT analysis, MPC = %1 in STEP 1 is not matching with MPC = %2 in STEP
2 analysis.

User information: In Case Control section having ROTBENT call, STEP 1 & STEP 2 should have same
MPC call id.

11138.17 *** USER INFORMATION MESSAGE 11138 (RBNT_BRNG)

For SUBCASE having ROTBENT call, following new SPC1 are created and used in STEP 1 & STEP 2
analysis

11138.18 *** USER FATAL MESSAGE 11138 (RBNT_BRNG)

ROTBENT id %1 referenced by SUBCASE id %2 & STEP id %3 have more than 1 set of X1,X2,X3 in
'NBCORD' keyword definition.

User information: ROTBENT definition should have only 1 set of X1,X2,X3 entry in 'NBCORD' key-
word definition.

11138.19 *** USER INFORMATION MESSAGE 11138 (RBNT_BRNG)

Main Index
 1122 MSC Nastran Error Messages
Errors 11000 - 11999

GRIDs of ROTOR id %1 referenced by ROTBENT id %2 are updated based on Kink & Offset defini-
tion.
Updated GRID definitions (using long format) are as follows

11138.20 *** USER INFORMATION MESSAGE 11138 (RBNT_GEOM)

UNBCORD entry in ROTBENT ID = %1 IS SPECIFIED WITH AN ORIENTATION VECTOR
WHICH IS INFINITESIMAL OR PARALLEL TO ROTOR AXIS.

11138.21
ERROR ENCOUNTERED IN THE CASE CONTROL SECTION. SEE MESSAGES ABOVE.
ERROR ENCOUNTERED IN MODULE IFP1.

11138.23 *** USER FATAL MESSAGE 11138 (MDG2RBNT)

%2 ANALYSIS = NLTRAN (Transient analysis) in STEP 2 is not supported for %1 analysis.

User information: ROTBENT Case Control call should have 1 SUBCASE, with following STEP analysis
definitions,
STEP 1 with ANALYSIS = NLSTATIC
STPE 2 with ANALYSIS = DCEIG (or) MCEIG (or) DFREQ (or) MFREQ

11139.0 *** USER FATAL MESSAGE 11139 (EBS2D)

SOL %1 (APP=%2) does not support UNAME = %3 (on ELEMUDS %4) for the following SERVICE
name.

User information: GROUP name on ELEMUDS is %5 CONNECT SERVICE name is '%6'.

11140.0 *** USER FATAL MESSAGE 11140 (EBS2D)

SOL %1 (APP=%2) does not support UNAME = %3 (on ELEMUDS %4) for the following SERVICE
name.

User information: GROUP name on ELEMUDS is %5

CONNECT SERVICE name is '%6'.
Supported solution sequences are:
SOL 108/110/128 (Frequency), SOL 107/110 (Complex Eigenvalue), and SOL 400 with Nonlinear Tran-
sient Analysis.

11140.1 *** USER FATAL MESSAGE 11140 (EBS2D)

Main Index
 MSC Nastran Error Messages 1123
Errors 11000 - 11999

SOL %1 (APP=%2) does not support PBUSH2DT bulk data card.

User information: Supported solution sequences are:

SOL 107/110 (Complex Eigenvalue), SOL 108/110/128 (Frequency) and SOL 400 with Nonlinear Tran-
sient Analysis.

11141.0 *** USER FATAL MESSAGE 11141 (EBS2D)

UNAME = %1 (on ELEMUDS %2) is not supported for the following SERVICE name.

User information: CONNECT SERVICE name is '%4'. GROUP name on ELEMUDS is %3.

User action: USE CONNECT SERVICE name "SCA.MDSolver.Obj.Uds.Elements.cbush2da"

11142.0 *** USER INFORMATION MESSAGE 11142 (FREQRS and MFREQRS)

SYNCHRONOUS ANALYSIS (SYNC IN RGYRO CARD) WITH CBUSH2DA ELEMUDS SERVICE
IS USED.
BEARING PARAMETERS IN UDS MAY NOT BE ACCURATE WHEN RUNNING SYNCRO-
NOUS ANALYSIS.

User action: REVIEW YOUR RESULTS CAREFULLY TO VERIFY THAT YOUR UDS WORKED
AS EXPECTED.

11143.0 *** USER FATAL MESSAGE 11143 (CBUSHD2DA & ROTORDYNAMICS ANALYSIS)
CBUSH2DA ELEMUDS SERVICE WORKS ONLY WITH ROTORDYNAMICS ANALYSIS.

User action: RUN CBUSH2DA ELEMEUDS SERVICE ON MODEL HAVING ROTOR DEFINI-
TION THROUGH ROTORG / ROTORAX / ROTOR BULK DATA CARD.

11144.0 *** USER FATAL MESSAGE 11144 (RUN_B2D)

Main Index
 1124 MSC Nastran Error Messages
Errors 11000 - 11999

CBUSH2D ELEMUDS SERVICE DOES NOT WORKS WITH "SCA.MDSolver.Obj.Uds.Ele-

ments.cbush2da" SERVICE CALL

User action: PLEASE CHECK AT TOP OF NASTRAN RUN FILE FOR CONNECT SERVICE DEFI-
NITION IT IS RECOMMENDED TO USE EITHER ONE OF TWO OPTIONS
NEW CBUSH2DA ELEMUDS SERVICE WITH "SCA.MDSolver.Obj.Uds.Elements.cbush2da" SER-
VICE CALL
(OR)
OLD CBUSH2D ELEMUDS SERVICE WITH "SCA.MDSolver.Obj.Uds.Elements.cbush2d" SER-
VICE CALL COMBINATION OF CBUSH2D & CBUSH2DA ELEMUDS DEFINITIONS NOT
ALLOWED

*** USER FATAL MESSAGE 11145 (PBSH2DT WITH TABLED1 & ROTORDYNAMICS ANALY-
11145.0
SIS)
PBSH2DT BULK DATA WITH TABLED1 DEFINITION WORKS ONLY WITH ROTORDYNAM-
ICS ANALYSIS.

User action: RUN PBSH2DT BULK DATA CARD WITH TABLED1, ON MODEL HAVING
ROTOR DEFINITION THROUGH ROTORG / ROTORAX / ROTOR BULK DATA CARD.

11146.0 *** USER FATAL MESSAGE 11146 (TA1AEUTH)

PTYPE field '%1' on ELEMUDS (PID=%2) bulk data entry should be changed to '%3' since the ELE-
MUDS is referenced by CBUSH2D (EID=%4).

11147.0 *** SYSTEM FATAL MESSAGE 11147 (TA1AEUTH)

The values of %1 and %2 are inconsistent.

11148.0 *** SYSTEM FATAL MESSAGE 11148 (IFPecLB3)

The %1 field should be specified on LBSH3DG %2 (which has FORM = %3).

11148.1 *** SYSTEM FATAL MESSAGE 11148 (IFPecLB3)

The %1 field should be specified on LBSH3DG %2 (which has FORM = %3).
There are %4 more of this same type of error found on other LBSH3DG entries that are not reported here.

11149.0 *** SYSTEM FATAL MESSAGE 11149 (IFPecLB3)

TABLED5 %1 is missing. It is referenced by %2 = %1 field of LBSH3DG %3.

Main Index
 MSC Nastran Error Messages 1125
Errors 11000 - 11999

11149.1 *** SYSTEM FATAL MESSAGE 11149 (IFPecLB3)

TABLED5 %1 is missing. It is referenced by %2 = %1 field of LBSH3DG %3.
There are %4 more of this same type of error found on other LBSH3DG entries that are not reported here.

11150.0 *** USER FATAL MESSAGE 11150 (IFPecNLR)

NLRGAP %1 referencing %2 id %3 in TABK field is not supported in SOL400 analysis for NON-
ROTORDYNAMIC models.

User information: TABLED5 in NLRGAP element is supported for only models having ROTOR defini-
tion through ROTORG / ROTORAX / ROTOR bulk data card in SOL400 analysis.

11151.0 *** USER INFORMATION MESSAGE 11151 (SEKEROT)

HDF5= %1, ROTNRG = %2. NH5RDB DATABASE IS NOT CREATED, NO ROTOR ENERGY
OUTPUT TO NH5RDB DATABASE.

User action: CREATE NH5RDB DATABASE BY SETTING HDF5>=0.

11151.1 *** USER FATAL MESSAGE 11151 (IFPS)

PARAM, ROTSEKE, VALUE
PARAMETER ROTSEKE IS REPLACED BY CASE CONTROL COMMAND ROTSEKE.

User action: REMOVE PARAM,ROTSEKE FROM THE INPUT FILE. IF ROTOR KINETIC AND
STRAIN ENERGY IS DESIRED, ADD THE CASE CONTROL COMMAND ROTSEKE

11151.2 *** USER INFORMATION MESSAGE 11151 (ROTENGY)

DATABLOCK %1 FOR ROTOR ENERGY CALCULATION IS MISSING, ROTSEKE OUTPUT
REQUEST IS IGNORED.

11151.3 *** USER INFORMATION MESSAGE 11151 (ROTENGY)

MASS, STIFFNESS, AND EIGENVECTOR MATRICES MUST HAVE THE SAME NUMBER OF
DOF IN THEM. ROTSEKE OUTPUT REQUEST IS IGNORED.

11151.4 *** USER INFORMATION MESSAGE 11151 (ROTENGY)

INSUFFICIENT MEMORY TO PERFORM CALCULATION OF ROTOR ENERGY.

11151.5 *** USER INFORMATION MESSAGE 11151 (ROTENGY)

Main Index
 1126 MSC Nastran Error Messages
Errors 11000 - 11999

EIGENVALUES PROVIDED FOR ROTOR ENERGY ARE NOT COMPLEX. ROTSEKE

REQUEST IGNORED.

11151.6 *** USER INFORMATION MESSAGE 11151 (ROTENGY)

DATABLOCK %1 IS NOT ACCESSIBLE, ROTSEKE OUTPUT REQUEST IS IGNORED.

11151.8 *** USER INFORMATION MESSAGE 11151 (ROTENGY)

NO VALID ROTOR SELECTED FOR ROTSEKE OUTPUT REQUEST.

11152.0 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : RGYRO definitions using RID %2 are not having same SYNCFLAG.

User information: All RGYRO entries with the same RGYRO id must have the same SYNCFLAG value.
Analysis can be run with Synchronous or Asynchronous setup only.

11152.1 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : ROTOR id %2 used as Reference rotor in REFROT bulk data definition should be
used in RGYRO definition.

User information: REFROTID in REFROT card should match REFROTR (4th field) with ROTRSEID
(9th field) set to 0 in RGYRO definition.

11152.2 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : ROTOR id %2 used as Non-Reference rotor in REFROT %3 is also used as reference
rotor in RGYRO %3.

User information: ROTIDn in REFROT card should not match with REFROTR (4th field) with ROTR-
SEID (9th field) set to 0 in RGYRO definition.

11152.3 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : REFROT id %2 : ROTOR id %3 used as Non-Reference rotor in multiple REFROT
bulk data definition.

User information: ROTIDn in REFROT card should not have multiple reference rotors.

11152.4 *** USER INFORMATION MESSAGE 11152 (IFPecREF)

Main Index
 MSC Nastran Error Messages 1127
Errors 11000 - 11999

SUBCASE id %1 uses RGYRO / REFROT / REFRTSE id %2 definitions.

Any other RGYRO / REFROT / REFRTSE ids will not be used in this SUBCASE.

11152.5 *** USER FATAL MESSAGE 11152 (ROTDR2)

No RGYRO or REFROT or REFRTSE definition available for rotor %1 in SE id %2, for RGYRO id %3
selected by case control. Since the multiple RGYRO definition option is used, all rotors should have either
individual RGYRO/REFROT/REFRTSE definitions.

User information: Either define RGYRO entry for each rotor (or) use REFROT / REFRTSE card to define
reference rotor. Alternately use only one RGYRO entry, which will be used as the reference rotor for all
remaining rotors.

11152.6 *** USER FATAL MESSAGE 11152 (ROTDR2)

No reference rotor identified for rotor %1 in SE id %2, either through REFROT (or) RGYRO id %3
selected by case control.

User information: Either define individual RGYRO entry for the rotor (or) use REFROT to define refer-
ence rotor. Alternately use only one RGYRO entry without any REFROT definition, in which case, refer-
ence rotor defined in the 4th field of RGYRO will be used for all remaining rotors.

11152.7 *** USER INFORMATION MESSAGE 11152 (ROTDR2)

For Complex Eigenvalue analysis with RGYRO ID %1, having ASYNC option,
ROTOR with ID %2 in SEID %3, has SPIN SPEED = %4 %5

11152.8 *** USER INFORMATION MESSAGE 11152 (ROTDR2)

For Complex Eigenvalue analysis with RGYRO ID %1, ROTOR with ID %2 in SEID %3, has SYNC
option.

11152.9 *** USER INFORMATION MESSAGE 11152 (ROTDR2)

For Frequency Response analysis with RGYRO ID %1, having ASYNC option,
ROTOR with ID %2 in SEID %3, has SPIN SPEED = %4 %5

11152.10 *** USER INFORMATION MESSAGE 11152 (ROTDR2)

For Frequency Response analysis with RGYRO ID %1, having SYNC option, all rotors have SPIN SPEED
= %2 %3

Main Index
 1128 MSC Nastran Error Messages
Errors 11000 - 11999

11152.11 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : ROTOR id %2 with SE id %3 defined as Reference rotor in REFRTSE bulk data defi-
nition, is not found in RGYRO %4 definition.

User information: REFRID & REFSEID in REFRTSE card should match REFROTR (4th field) &
ROTRSEID (9th field) in RGYRO card.

11152.12 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : ROTOR id %2 with SE id %3 used as Non-Reference rotor in REFRTSE %4, is also
defined in RGYRO %4.

User information: NFROTID & NFROTSE in REFRTSE card should not match REFROTR (4th field)
& ROTRSEID (9th field) in RGYRO card.

11152.13 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : REFRTSE id %2 : ROTOR id %3 with SE id %4 used as Non-Reference rotor in mul-
tiple REFRTSE bulk data definition.

User information: NFROTID & NFROTSE in REFRTSE card should not have multiple reference rotors.

11152.14 *** USER FATAL MESSAGE 11152 (IFPecREF)

SUBCASE id %1 : ROTOR id %2 with SE id %3 is used as Non-Reference rotor in both REFRTSE &
REFROT %4 bulk data definition.

User information: A non-reference rotor should not have multiple reference rotors definition.

11152.15 *** USER FATAL MESSAGE 11152 (ROTDR2)

No reference rotor identified for rotor %1 in SE id %2, either through REFRTSE (or) RGYRO id %3
selected by case control.

User information: Either define inAlternately use only one RGYRO entry without any REFRTSE defini-
tion, in which case,dividual RGYRO entry for rotor in superelement (or) use REFRTSE to define reference
rotor. reference rotor defined in the 4th field of RGYRO will be used for all remaining rotors.

11152.16 *** USER FATAL MESSAGE 11152 (ROTDR2)

Main Index
 MSC Nastran Error Messages 1129
Errors 11000 - 11999

Use of REFROT or REFRTSE or multiple RGYRO with id %1 are supported only in Complex Eigenvalue
solution (or) Frequency response with SYNC analysis.

User information: Currently Frequency response ASYNC analysis, Transient analysis & static solutions
with REFROT/REFRTSE/Multiple RGYRO are not supported. Please run only SOL107, SOL110,
SOL108, SOL110 (SYNC), SOL200 or SOL400 with ANALYSIS = CEIG call.

11155.0 *** USER INFORMATION MESSAGE 11155 (MAKEOF)

INPUT MATRIX KOFORCES (GINO file %1) EITHER DOES NOT EXIST OR IS NULL. NO
FORCES DUE TO KINKS AND OFFSETS (ROTBENT) CALCULATED

11300.0 *** SYSTEM FATAL MESSAGE 11300 (FACDRVI)

The matrix on data block %1 is in a format which is not supported by the Pardiso Solver.

User information: The Pardiso Solver requires the SCC format.

User action: Do not set FACTMETH=PRDLDL/PRDLU on the SPARSESOLVER entry.

11300.1 *** SYSTEM FATAL MESSAGE 11300 (FACDRVI)

Input inconsistency error from Pardiso.

User information: Pardiso solver option currently only valid for symmetric indefinite (SOL 101 and SOL
400), symmetric definite (SOL 101), and complex symmetric (SOL 108) matrices.

User action: Do not set FACTMETH=PRDLDL/PRDLU on the SPARSESOLVER entry.

11300.2 *** USER FATAL MESSAGE 11300 (directSolveDrv)

Pardiso has encountered an inconsistency in the matrix on data block %1. It is rectuangular, and therefore
cannot be solved using the available methods.

User information: The Pardiso Solver requires square matrices.

User action: Do not set FACTMETH=PRDLDL/PRDLU on the SPARSESOLVER entry.

11300.3 *** USER FATAL MESSAGE 11300 (directSolveDrv)

Main Index
 1130 MSC Nastran Error Messages
Errors 11000 - 11999

Input inconsistency for use of Pardiso.

User information: Pardiso solver option currently only valid for some SOL 101, 107, 108, 111, and SOL
400 jobs.

User action: Do not set FACTMETH=PRDLDL/PRDLU on the SPARSESOLVER entry.

11300.4
Inconsistency in Pardiso solve; number of right-hand sides is invalid
.
User information: An inconsistency in inputs has caused the failure in the sparse solve using Pardiso.

User action: Do not set FACTMETH=PRDLDL/PRDLU on the SPARSESOLVER entry.

11301.0 *** USER INFORMATION MESSAGE 11301 (PardisoSolver)

Empty or invalid reordering option for Pardiso Solver.

User information: The Pardiso Solver automatically switched to the PRDSMPMS reordering option. Only
the following methods are valid reordering methods for the Pardiso Solver.
SPARSESOLVER (ordmeth="method"):
- ordmeth=prdmd
- ordmeth=prdmetis
- ordmeth=prdsmpms

11302.0 *** USER INFORMATION MESSAGE 11302 (PardisoSolver)

Problem encountered with Pardiso pivoting perturbation.

User information: The Pardiso Solver automatically switched to zero pivoting perturbation.

11303.0 *** USER INFORMATION MESSAGE 11303 (PardisoSolver)

Reordering Problems encountered.

User information: MSC Nastran reordering used inside the Pardiso Solver was unsuccessful. The Pardiso
Solver automatically switched to the PRDSMPMS reordering option.

11303.1 *** USER INFORMATION MESSAGE 11303 (PardisoSolver)

Main Index
 MSC Nastran Error Messages 1131
Errors 11000 - 11999

Reordering Problems encountered.

User information: Reordering vector produced by MSC Nastran reordering is invalid for Pardiso Solver.
The Pardiso Solver automatically switched to the PRDSMPMS reordering option.

11304.0 *** USER INFORMATION MESSAGE 11304 (GTFCDF)

Domainsolver nlsolv (MDSTAT) not supported with Pardiso solver.

User information: Use of domainsolver nlsolv (SYSTEM(449)=2) is not supported for Pardiso Solver.
Continuing with default solver.

11305.0 *** USER WARNING MESSAGE 11305 (PardisoSolver)

Null columns detected. A real symmetric positive-definite (SPD) matrix solve is default, but null columns
indicate indefiniteness. If the solve fails, consider using SYSTEM(700)=3 to remove null columns for defi-
nite matrices. If the solve still fails, consider adding MDLPRM,PRDMTYPE,-2 to the bulk data section to
solve a real symmetric indefinite matrix.

User information: The default for SOL 101, 108, and 111 is for a real symmetric positive-definite (SPD)
solve (bulk data entry MDLPRM,PRDMTYPE,2).

11305.1 *** USER WARNING MESSAGE 11305 (PardisoSolver)

Null columns detected. A complex Hermitian positive-definite (HPD) matrix solve was requested, but null
columns indicate indefiniteness. A complex Hermitian indefinite matrix solve will be performed.

User information: To avoid this message in the future, set MDLPRM,PRDMTYPE,-4 inthe bulk data sec-
tion.

11305.2 *** USER FATAL MESSAGE 11305 (PardisoSolver)

Inconsistent matrix type for Pardiso sparse matrix solve. The Pardiso matrix type used is %1, which is not
consistent with the Nastran matrix trailer information:
trailer(4) = matrix form = %2
trailer(5) = matrix type = %3

User information: Consult the Intel MKL Pardiso online documentation for more information on Pardiso
matrix types. The Pardiso matrix type can be changed by using MDLPRM,PRDMTYPE in the bulk data
section. Failing this, contact MSC client support.

Main Index
 1132 MSC Nastran Error Messages
Errors 11000 - 11999

11305.3 *** USER FATAL MESSAGE 11305 (PardisoSolver)

Inconsistent matrix type for Pardiso sparse matrix solve. The Pardiso matrix type used is %1, which is not
valid.

User information: An invalid choice of Pardiso matrix type was given. If it was specified via the command
line, then re-try without setting MDLPRM,PRDMTYPE. Failing this, contact MSC client support.

11305.4 *** USER WARNING MESSAGE 11305 (GTFCDF)

Chosen matrix type for Pardiso sparse matrix solve was %1. This choice is not consistent with the usual
matrix type(s) for the chosen solution sequence.

User information: A non-standard choice of Pardiso matrix type was given. Check the value of the MDL-
PRM,PRDMTYPE bulk data entry. If it was specified via the command line or RC file, then re-try without
setting SYSTEM(684).

11306.0 *** USER INFORMATION MESSAGE 11306 (SPASOL)

Chosen solver, Pardiso LDL (PRDLDL) is not generally compatible with the CEAD module. If the matrix
produced is not Hermitian Positive Definite or Hermitian Indefinite, the solver can be expected to fail.

User information: If you are specifying MDLPRM,PRDMTYPE,4 in the bulk data section and the solve
fails, the matrix may be indefinite. Retry with MDLPRM,PRDMTYPE,-4 (Hermitian Indefinite matrix).

11306.1 *** USER WARNING MESSAGE 11306 (SPASOL)

Chosen solver, Pardiso LDL (PRDLDL) is not generally compatible with the CEAD module. The unsym-
metric Pardiso solver PRDLU will be used instead.

User information: If you are certain that your matrix is Hermitian, then this selection will work, and you
should restart the run adding MDLPRM,PRDMTYPE,4 (Hermitian Positive Definite) or MDL-
PRM,PRDMTYPE,-4 (Hermitian Indefinite matrix) to the bulk data section. Otherwise, change
PRDLDL to PRDLU in the SPARSESOLVER line of your input deck in future runs.

11306.2 *** USER WARNING MESSAGE 11306 (SPASOL)

Pardiso solver (PRDLDL) is not supported for use with the %1 module.
The MSCLDL solver will be used instead.

User information: Remove PRDLDL from the SPARSESOLVER line of your input deck in future runs.

Main Index
 MSC Nastran Error Messages 1133
Errors 11000 - 11999

11306.3 *** USER WARNING MESSAGE 11306 (SPASOL)

Pardiso symmetric solver (PRDLDL) is not generally compatible with the FRRD1 module. The unsym-
metric Pardiso solver PRDLU will be used instead.

User information: If you are certain that your matrix is Hermitian, then this selection will work, and you
should restart the run adding MDLPRM,PRDMTYPE,4 (Hermitian Positive Definite) or MDL-
PRM,PRDMTYPE,-4 (Hermitian Indefinite matrix) to the bulk data section. Otherwise, change
PRDLDL to PRDLU in the SPARSESOLVER line of your input deck in future runs.

11306.4 *** USER WARNING MESSAGE 11306 (SPASOL)

Pardiso solver (PRDLU) is not supported for use with the %1 module.
The MSCLU solver will be used instead.

User information: Remove PRDLU from the SPARSESOLVER line of your input deck in future runs.

11306.5 *** USER WARNING MESSAGE 11306 (SPASOL)

Chosen solver, Pardiso LU (PRDLU) is not compatible with the %1 module. The symmetric Pardiso solver
PRDLDL will be used instead.

User information: Change PRDLU to PRDLDL in the SPARSESOLVER line of your input deck in future
runs.

11306.6 *** USER WARNING MESSAGE 11306 (SPASOL)

Pardiso solver (PRDLU) is not supported for use with the %1 module.
The MSCLDL solver will be used instead.

User information: Remove PRDLU from the SPARSESOLVER line of your input deck in future runs.

11307.1 *** USER FATAL MESSAGE 11307 (SPASOL)

MUMPS solver (MUMPS) is currently supported only for %1 module.

User information: Remove MUMPS from the SPARSESOLVER statement of your input deck.

11312.0 *** SYSTEM FATAL MESSAGE 11312 (PardisoSolver)

Main Index
 1134 MSC Nastran Error Messages
Errors 11000 - 11999

Unable to write to scratch directory.

User action: Please check file permissions, disk quota, and disk usage.

11313.0 *** SYSTEM FATAL MESSAGE 11313 (FACDRVI)

Unable to open Pardiso OOC (out-of-core) temporary files.

User action: Please check file permissions, disk quota, and disk usage in the scratch directory, where Pardiso
stores temporary files.

11314.0 *** SYSTEM FATAL MESSAGE 11314 (PardisoSolver)

READ/WRITE problem with Pardiso OOC (out-of-core) data file.

User action: Please check file permissions, disk quota, and disk usage in the scratch directory, where Pardiso
stores data files.

11320.0 *** SYSTEM FATAL MESSAGE 11320 (PardisoSolver)

Insufficient memory for the Pardiso Solver.
USER INFORMATION: Pardiso indicates there is not enough memory for solve.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line. Alternatively, if MDL-
PRM,PRDOOC,0 was set, un-set it in order to allow out-of-core execution of Pardiso Solver.

11320.1 *** SYSTEM FATAL MESSAGE 11320 (PardisoSolver)

Pardiso solver indicated internal memory management error. Likely not enough memory.

User information: Pardiso indicates there is not enough memory for in-core solve.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line. Alternatively, if MDL-
PRM,PRDOOC,0 was set, un-set it in order to allow out-of-core execution of Pardiso Solver.

11320.2 *** SYSTEM FATAL MESSAGE 11320 (PardisoSolver)

Main Index
 MSC Nastran Error Messages 1135
Errors 11000 - 11999

Insufficient memory for loading the matrix on data block %1 in-core.

Pardiso requires that the matrix is in-core.

User information: There is not sufficient memory to use Pardiso.

User action: Do not set FACTMETH=PRDLDL/PRDLU on the SPARSESOLVER entry.

11320.3 *** SYSTEM WARNING MESSAGE 11320 (PardisoSolver)

Insufficient memory for the Pardiso Solver. Switching to MSC in-house solver.

User information: Pardiso indicates there is not enough memory for solve.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line. Alternatively, if MDL-
PRM,PRDOOC,0 was set, un-set it in order to allow out-of-core execution of Pardiso Solver.

11321.0 *** SYSTEM FATAL MESSAGE 11321 (PardisoSolver)

Insufficient memory for the out-of-core Pardiso Solver (Error code %1).

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line.

11321.1 *** SYSTEM WARNING MESSAGE 11321 (PardisoSolver)

Insufficient memory for the out-of-core Pardiso Solver (Return code %1). Switching to MSC in-house
solver.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line.

11322.0 *** SYSTEM FATAL MESSAGE 11322 (PardisoSolver)

Error in memory management for the Pardiso Solver.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line. Failing that, please contact MSC
client support.

11323.0 *** SYSTEM FATAL MESSAGE 11323 (PardisoSolver)

Main Index
 1136 MSC Nastran Error Messages
Errors 11000 - 11999

Memory management problem in Pardiso Solver.

User information: Problem in memory management for Intel MKL Pardiso. Error code is %1.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line. Failing that, use a different factor-
ization method via the SPARSESOLVER entry.

11324.0 *** SYSTEM FATAL MESSAGE 11324 (NL3EMA)

Memory management problem for Pardiso Solver.

User information: Error in using Pardiso; not enough core memory.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line. Failing that, use a different factor-
ization method via the SPARSESOLVER entry.

11331.0 *** SYSTEM FATAL MESSAGE 11331 (PardisoSolver)

The Pardiso Solver indicates that a diagonal matrix is singular.

User action: A singular matrix generally indicates a bad model. Try simplifying it and re-submitting.

11332.0 *** SYSTEM FATAL MESSAGE 11332 (PardisoSolver)

Zero pivot or iterative refinement problem in the Pardiso Solver.

User action: Pivoting issues can sometimes be resolved by changing the pivoting perturbation. Use MDL-
PRM,PIVTHRSH parameter to set the numeric pivoting threshold value. For more information, refer to
QRG.

11332.1 *** SYSTEM FATAL MESSAGE 11332 (PardisoSolver)

Zero pivot or iterative refinement problem in the Pardiso Solver due to matrix singularity in SOL 101.

User action: Consider adding MDLPRM,PRDMTYPE,-2 to the bulk data section to solve a real symmet-
ric indefinite matrix. For more information, please refer to QRG.

11333.0 *** SYSTEM FATAL MESSAGE 11333 (PardisoSolver)

Main Index
 MSC Nastran Error Messages 1137
Errors 11000 - 11999

Badly formed matrix named %1 on unit %2 passed to Pardiso.

User information: Pardiso solver option currently only valid for symmetric indefinite matrices.

User action: Do not set FACTMETH=PRDLDL/PRDLU on the SPARSESOLVER entry.

11334.0 *** SYSTEM INFORMATION MESSAGE 11334 (PardisoSolver)

Unable to get K/L diagonal information from Pardiso for matrix named %1 on unit %2

User information: Matrix (K) and Factor (L) diagonal information cannot be output. Pardiso cannot pro-
vide this information when performing an out-of-core solve.

11342.0 *** SYSTEM FATAL MESSAGE 11342 (PardisoSolver)

Reordering problem with the %1 method in the Pardiso Solver.

User action: Specify a different reordering method using SPARSESOLVER (ordmeth="method") as fol-
lows:
- ordmeth=prdmd
- ordmeth=prdmetis
- ordmeth=prdsmpms

11343.0 *** SYSTEM FATAL MESSAGE 11343 (PardisoSolver)

Preordering problem with the %1 method in the Pardiso Solver.

User action: Try specifying a different reordering method using SPARSESOLVER (ordmeth="method") as
follows:
- ordmeth=prdmd
- ordmeth=prdmetis
- ordmeth=prdsmpms

11350.0 *** SYSTEM FATAL MESSAGE 11350 (PardisoSolver)

Unable to store Pardiso handle

User action: Please check file permissions, disk quota, and disk usage in the scratch directory, where Pardiso
stores data files.

11350.1 *** SYSTEM FATAL MESSAGE 11350 (PardisoSolver)

Main Index
 1138 MSC Nastran Error Messages
Errors 11000 - 11999

Unable to restore Pardiso handle

User action: Please check file permissions, disk quota, and disk usage in the scratch directory, where Pardiso
stores data files.

11360.0 *** SYSTEM FATAL MESSAGE 11360 (PardisoSolver)

Integer overflow in the Pardiso Solver.

User action: Re-run the job with mode=i8 on the submittal line.

11361.0 *** SYSTEM FATAL MESSAGE 11361 (PardisoSolver)

Internal MKL error in the Pardiso Solver.

User action: Contact client support, or re-run the job WITHOUT specifying FACTMETH=PRDLDL/
PRDLU on the SPARSESOLVER entry.

11361.1 *** SYSTEM FATAL MESSAGE 11361 (PardisoSolver)

Unspecified internal error in the Pardiso Solver.

User action: Contact client support, or re-run the job WITHOUT specifying FACTMETH=PRDLDL/
PRDLU on the SPARSESOLVER entry.

11362.0 *** SYSTEM FATAL MESSAGE 11362 (PardisoSolver)

Failed to correctly initialize threads.

User action: Check your hardware for the maximum number of threads and re-submit using at most that
number.

11363.0 *** USER INFORMATION MESSAGE 11363

INTEL MKL PARDISO SOLVER MULTIPLE LOAD INFORMATION:
NUMBER OF LOAD CASES = %1
NUMBER OF LOAD CASES FIT IN MEMORY = %2
NUMBER OF PASSES = %3
INCREASING MEMORY BY %4 MB MAY IMPROVE PERFORMANCE BY FITTING MORE
LOADS IN MEMORY.

11364.0 *** USER INFORMATION MESSAGE 11364

Main Index
 MSC Nastran Error Messages 1139
Errors 11000 - 11999

INTEL MKL PARDISO SOLVER HAS BEEN FORCED TO RUN IN-CORE WHICH IS A
REQUIREMENT FOR MULTIOPT OR ANY OTHER APPLICATIONS THAT USE MDSS.

11365.0 *** SYSTEM FATAL MESSAGE 11320 (PardisoSolver)

Insufficient memory for Pardiso solver, unable to fit atleast 1 load/RHS.

User action: Try searching .F04 file for 'PRDDSV' for Pardiso minimum memory requirement. Use the
reported values to increase memory using 'mem=' on the submittal line.

11366.0 *** USER FATAL MESSAGE 11366 (MumpsSolver)

Insufficient memory for the Mumps Solver.

User information: MUMPS indicates there is not enough memory to perform in-core decomposition.
Only in-core is supported for Mumps solver.

User action: Try searching .F04 file for 'MUMPS' for 'REQUIRED INCORE MEMORY'.
Use the reported values to increase memory using 'memorymax=' on the submittal line to use Mumps
solver.

11367.0 *** SYSTEM FATAL MESSAGE 11367 (MumpsSolver)

Unspecified internal error in the Mumps Solver.

User action: Contact client support, or re-run the job WITHOUT specifying FACTMETH=MUMPS on
the SPARSESOLVER statement.

11368.0 *** SYSTEM FATAL MESSAGE 11367 (MumpsSolver)

MPI Internal error in the Mumps Solver.

User action: Contact client support, or re-run the job WITHOUT specifying FACTMETH=MUMPS on
the SPARSESOLVER statement.

11369.0 *** SYSTEM FATAL MESSAGE 11367 (MumpsSolver)

Mumps solver is not available on Windows platform.

User action: Please re-run the job WITHOUT specifying FACTMETH=MUMPS on the SPARSE-
SOLVER statement or replace with Pardiso.

Main Index
 1140 MSC Nastran Error Messages
Errors 11000 - 11999

11370.0 *** USER FATAL MESSAGE 11367 (MumpsSolver)

Decomposition is unable to proceed due to negative or zero factor diagonal. This indicates the matrix is sin-
gular and there is a modeling issue that needs to be addressed.

User action: Please investigate the model for insufficient constraints, insufficient connections or large dif-
ferences in stiffness in the model.

11371.0 *** USER FATAL MESSAGE 11371 (PHASE0)

Inertia Relief with DMP is only supported for INREL=-2 and MUMPS.

User action: To use MUMPS with INREL and DMP, set INREL to -2 and specify SPARSESOLVER
DCMP (FACTMETH=MUMPS).

11371.1 *** USER FATAL MESSAGE 11371 (PHASE0)

MUMPS is not supported with INREL=-1.

User action: Set INREL to -2 or specify a different factorization method.

11400.0 *** System Fatal Message 11400 (sepmrg1)

The Bulk Data entry %1 is detected in the following Modules:
%2

User information: %1 is currently not supported with Modules.

User Action: Remove the entry.

11401.0 *** System Fatal Message 11401 (sepmrg1)

The presumed integer %2 specified in the %3 field on a %1 Bulk Data entry is larger than maximum value
(%4) allowed.

User action: Contact MSC Technical Support.

Programmer information: The value may actually be real or Hollerith.

11401.1 *** System Fatal Message 11401 (subdmap ifpstar)

Main Index
 MSC Nastran Error Messages 1141
Errors 11000 - 11999

mode=i4 is detected with the presence of Modules.

User action: Use mode=i8.

11401.2 *** System Fatal Message 11401 (subdmap mdacmsx)

mode=i4 is detected with ACMS Version=NEW.

User action: Use mode=i8.

11402.0 *** system fatal message 11402 (subdmap ifpstar)

%1%2 is not supported with Modules.

11402.1 *** system fatal message 11402 (subdmap nonlin)

Nonlinear analysis is not supported with Modules. Only multi-disciplinary linear analysis is supported with
Modules.

User action: Remove all STEP, SUBSTEP, NLSTEP, and NLPARM Case Control commands.

11403.0 *** System fatal Message 11403 (subdmap ifpstar)

DMI, DTI, and/or PARAM Bulk Data entries are detected inside BEGIN MODULE Bulk Data sections.
See messages below.

User information: DMI, DTI, and PARAM Bulk Data entries are only permitted in the main Bulk Data
section.

11404.0 *** System fatal Message 11404 (sepmerge)

Either the DEQATN or DEQIND data block is missing.

User information: Both must be available in order to merge them across Modules.

11405.0 *** System Fatal Message 11405 (sep1x)

The Module identification number(ID)=%1 is larger than maximum value (99) allowed with mode=i4.

User action: Use mode=i8.

11406.0 *** User Information Message 11406 (modmdcnt)

Main Index
 1142 MSC Nastran Error Messages
Errors 11000 - 11999

MDCONCT=%1 duplicates the XYZ fields specified on MDCONCT=%2.

User information: The connections for both will be consolidated on MDCONCT=%2.

11407.0 *** User Fatal Message 11407 (tabf5x)

For MDCONCT=%1 with TYPE=%2 no connections were found.

User action: If TYPE=RRBE2 or MRBE2 then check for necessary RBE2 elements to complete this con-
nection.

11407.1 *** User Fatal Message 11407 (tabf5x)

For MDCONCT=%1 with TYPE=%2 only %3 out of %4 connections were found.

User action: If TYPE=RRBE2 or MRBE2 then check for necessary RBE2 elements to complete this con-
nection.

User information: See Module Map below for found connections.

11408.0 *** USER WARNING/FATAL MESSAGE 11408 (TABF6X)

%1=%2 connects the following coincident points in module %3.

User information: Connecting these points may result in making the connection more rigid than intended.

User action: The MDEXCLD Bulk Data entry may be used to exclude points from the connection.

11409.0 *** USER WARNING/FATAL MESSAGE 11409 (subDMAP MODULMRG)

%1=%2 connects coincident points in module %3. See the list of points and connecting elements below.

User information: Connecting these points will result in making the connection more rigid than intended
or damping elements between the points will be ignored.

User action: The MDEXCLD Bulk Data entry may be used to exclude points from the connection.

11410.0 *** USER FATAL MESSAGE 11410 (MDCHECK)

%1 Bulk Data entry %2 references undefined %3 %4 %6 in module %5 %7

Main Index
 MSC Nastran Error Messages 1143
Errors 11000 - 11999

11411.0 *** User Fatal Message 11411 (sepmerge)

DMIG name=%1 duplicated on DMIG and/or MDDMIG entries.

User information: All DMIG/MDDMIG names must be unique.

11412.0 *** User Information Message 11412 (tabf5x)

MDCONCT=%1 has been merged into MDCONCT=%2.

11413.0 *** User Fatal Message 11413 (sepmerge)

BCID=%1 duplicated on BCTABL1 and MDBCTB1 entries.

11414.0 *** User Fatal Message 11414 (modulmrg)

The EXTSEOUT command (or PARAM,EXTOUT) and ASETi, BSETi, BNDFIXi, BNDFREi, CSETi,
OMITi, or SUPORTi entries are specified in Begin Module=%1 section which is not allowed.

User action: If EXTSEOUT (or PARAM,EXTOUT) is desired then specify these entries in the main Bulk
Data section only.

11415.0 *** System Fatal Message 11415 (subDMAP MODOTPRT)

Module MAP cannot be found.

11416.0 *** User Fatal Message 11416 (subDMAP MODULMRG)

The geometry of copied module %1 is different from its reference module.

User action: Remove any GRID entries from the copied module's Bulk Data section. Check for modified
CORD1C, CORD1R, CORD1S, CORD2C, CORD2R, or CORD2S entries in the copied module's
Bulk Data section that affect GRID locations.

11417.0 *** USER FATAL MESSAGE 11417 (MDMOVE3)

Duplicate move ID=%1 assigned to %2 and %3 Bulk Data entries.

User information: Move IDs must be unique across all MDTRAN, MDROTi, and MDMIRi entries.

11418.0 *** USER FATAL MESSAGE 11418 (MDMOVE1)

Main Index
 1144 MSC Nastran Error Messages
Errors 11000 - 11999

Module %1 is defined on an MDBULK entry with TYPE=MOVE and is also referenced on an %2 Bulk
Data entry.

User information: A Module defined with TYPE=MOVE can only be referenced on an MDMOVE entry.

11419.0 *** USER FATAL MESSAGE 11419 (MDMOVE3)

%1 Bulk Data entry ID=%2 references undefined %3 Bulk Data entry ID=%4

11420.0 *** USER FATAL MESSAGE 11420 (MDMOVE3)

%1 Bulk Data entry ID=%2 defines a zero length vector.

11421.0 *** USER FATAL MESSAGE 11421 (MDMOVE3)

%1=%2 Bulk Data entry is referenced after the first movement (MVID) on the MDMOVE=%3 entry.

User information: If MDMOVE references an MDMIRi entry then it must be the first (MVID1) and only
MDMIRi referenced on the MDMOVE entry.

11422.0 *** USER FATAL MESSAGE 11422 (MDMOVE1)

MDBULK Bulk Data entry with MODID=%1 specifies the same ID for the reference Module (RMO-
DID).

User action: If Module %1 is a primary Module then set RMODID=0. If Module %1 is a Module copy
then set RMODID to a primary Module ID.

11423.0 *** USER FATAL MESSAGE 11423 (MDMOVE1)

Duplicate MDBULK=%1 Bulk Data entry encountered.

11424.0 *** USER WARNING MESSAGE 11424 (subDMAP EXTOUT)

When Modules are present, the two-step method of external superelement data recovery is not supported
for elements and grids contained in a Module. In other words, only the results for elements and grids con-
tained in Module 0 may be recovered in the the second step. The three-step method may be employed to
obtain results from grids and elements contained in Modules.

11425.0 *** USER FATAL MESSAGE 11425 (SEPMD1)

The MDCONCT Bulk Data entry with BID=%1 specifies only one MIDi on the continuation entry.

User action: Remove the MDCONCT entry or specify at least two MIDi on the continuation entry.

Main Index
 MSC Nastran Error Messages 1145
Errors 11000 - 11999

11426.0 *** SYSTEM FATAL MESSAGE 11426 (MDMRGGRD)

LOGIC ERROR %1 was encountered while searching for GRID %2 in the %3 table.

11427.0 *** SYSTEM FATAL MESSAGE 11427 (MDMRGIFP)

Mirrored Module %1 is reusing a %2 Bulk Data entry from its primary Module.

User information: The %2 entry is not supported in mirrored Modules.

11428.0 *** SYSTEM FATAL MESSAGE 11428 (MDMRGIFP)

Mirrored Module %1's Bulk Data section contains a %2 entry.

User information: The %2 entry is not supported in mirrored Modules.

11429.0 *** SYSTEM FATAL MESSAGE (ZREADM)

There is no method for merging the %1 record across Modules.

11430.0 *** SYSTEM FATAL MESSAGE (MDQAOFP)

Not find position data for datablock %1.
Programmer information: check if datablock %1 has position data in OFPMDPOS.

11431.0 *** USE INFORMATION MESSAGE (ROTOR2)

%1 %2 entries with non-zero %3 have been found in the input. They have been set to zero because Mod-
ules are present in the input.

11431.1 *** USE FATAL MESSAGE (ROTOR2)

%1 in %2 RID=%3 in Module 0 is not zero.

User action: Set it to zero.

11432.0 *** USE FATAL MESSAGE (bcauto_genpair)

SET3 ID=%1 referenced by MDBCPAR entry is not defined.

11432.1 *** USE WARNING MESSAGE (bcauto_genpair)

Found SET3 ID=%1 referenced by MDBCPAR but no module id matches.

Main Index
 1146 MSC Nastran Error Messages
Errors 11000 - 11999

11432.2 *** USE WARNING MESSAGE (bcauto_mdbcatp_mod.check_match)

A pair of modules %1 and %2 are specified in MDBCPAR entry but no contact pair found between the
two modules.

11432.3 *** USE FATAL MESSAGE (bcauto_genpair)

Found SET3 ID=%1 referenced by MDBCPAR but not a MODULE type.

11433.0 *** USER FATAL MESSAGE (GP5)

On the ACMODL Bulk Data entry the fields FSET or SSET are set to -1 but no Modules are defined.

User information: Negative values for FSET and SSET are allowed only when Modules are defined.

11434.0 *** USER FATAL MESSAGE (SEPMRG1)

%1 is -1 on the ACMODL Bulk Data entry but there are no %2 entries.

11500.0 ***SYSTEM FATAL MESSAGE 11500 (crdb_processor)

DATABLOCK NAME %1 FOR GINO %2 IS INVALID.

11501.0 ***SYSTEM FATAL MESSAGE 11501 (crdb_processor)

CRDB ERROR: %1, FOR %2.

11502.0 ***SYSTEM FATAL MESSAGE 11502 (crdb_processor)

UNKNOWN EXCEPTION.

11503.0 SYSTEM FATAL MESSAGE 11503 (crdb_processor)

CRDB ERROR: %1.

11503.1 ***SYSTEM WARNING MESSAGE 11503 (crdb_processor)

CRDB WARNING: element type %1 for %2 is not supported.

11600.0

Main Index
 MSC Nastran Error Messages 1147
Errors 11000 - 11999

RESTART DOES NOT FIND ADVANCED NONLINEAR ELEMENT DATABLOCKS REQUIRED

FOR THE RESTART POINT.
PLEASE CHECK DBSAVE AND OUTPUT CONTROL TO STORE THE CORRESPONDING
DATABLOCKS REQUIRED FOR RESTART.
PLEASE NOTE THAT STORAGE OF DATBLOCKS RELATED TO ADVANCED NONLINEAR
ELEMENT DATA IS CONTROLLED BY BOTH DBSAVE AND OUTPUT CONTROL.
THE DEFAULT OF DBSAVE IS TO SAVE THOSE DATABLOCKS AT THE END OF EACH
LOADSTEP ONLY.

User action: Try setting DBSAVE = N>0, to make sure RESTART point matches every Nth output
request defined by INTOUT.

11601.0
NLIC DOES NOT FIND ADVANCED NONLINEAR ELEMENT DATABLOCKS REQUIRED
FOR THE NLIC POINT.
PLEASE CHECK DBSAVE AND OUTPUT CONTROL TO STORE THE CORRESPONDING
DATABLOCKS REQUIRED FOR NLIC.
PLEASE NOTE THAT STORAGE OF DATBLOCKS RELATED TO ADVANCED NONLINEAR
ELEMENT DATA IS CONTROLLED BY BOTH DBSAVE AND OUTPUT CONTROL.
DEFAULT OF DBSAVE IS TO SAVE THOSE DATABLOCKS AT THE END OF EACH LOAD-
STEP ONLY.

User action: Try setting DBSAVE = N>0, to make sure NLIC matches every Nth output request defined
by INTOUT.

11690.0 ***USER WARNING MESSAGE 11690 (alloc)

NUMBER OF THREADS SET TO 0. RUN WITH DMP=2 SMP=%1 OR DMP=4 SMP=%2.

11691.0 ***USER WARNING MESSAGE 11691 (marcmd_elgroup)

Main Index
 1148 MSC Nastran Error Messages
Errors 11000 - 11999

CONTAINS A MIXTURE OF DIFFERENT NASTRAN ELEMENT TYPES SUCH AS QUADR/

QUAD4 OR TRIAR/TRIA3
THIS FEATURE CANNOT BE SUPPORTED IN SMP MODE
SMP MODE IS DISABLED

11693.0 ***USER WARNING MESSAGE 11693 (marcmd_prd_matdigi)

Digimat is not supported in SMP mode in Nastran
SMP has been disabled

11700.0 *** USER INFORMATION MESSAGE 11700

Programmer information: RIGID BODY MODES WERE DETECTED UPSTREAM.

11700.1 *** USER INFORMATION MESSAGE 11700

POSSIBLE RIGID-BODY MODES DETECTED IN DOMAIN %1. NUMBER OF LOW FRE-
QUENCY MODES = %2 FZERO = %3 LOWEST MODE = %4 HZ.
THESE MODES WILL BE AUTOMATICALLY CONSTRAINED TO PREVENT SINGULARITIES.

User information: Review the model to determine whether or not this action is appropriate. For very flexi-
ble models with low mass density, you can avoid this action by setting PARAM,FZERO to a value smaller
than the lowest frequency (Hz).

11701.0 *** USER INFORMATION MESSAGE 11701

NUMBER OF SUBSTRUCTURE MODES = %1.

11702.0 *** USER INFORMATION MESSAGE 11702

DOMAINSOLVER ACMS: MODES OF REDUCED MODEL.

11703.0 *** USER INFORMATION MESSAGE 11703

DOMAINSOLVER ACMS: END OF REDUCED MODEL MODES.

11704.0 *** SYSTEM WARNING/FATAL MESSAGE 11704 (ACMS1VRC)

ACMS Eigenvector Recovery Internal Error

User action: CONTACT HEXAGON AB CLIENT SUPPORT.

Programmer information: INFORMATION: ERROR LOOKING FOR %1 with ID = %2

Main Index
 MSC Nastran Error Messages 1149
Errors 11000 - 11999

11705.0 *** USER FATAL MESSAGE 11705 (ACMS1WAIT):

THREAD %1 IS ATTEMPTING TO SET A MEMORY FLAG, BUT A FLAG HAS ALREADY BEEN
SET BY THREAD %2.

User information: THE DYNAMIC MEMORY AREA IS NOT LARGE ENOUGH TO SATISFY
SIMULTANEOUS MEMORY REQUESTS FROM ALL SMP THREADS.

User action: RERUN THE JOB WITH MORE MEMORY.

11705.1 *** USER FATAL MESSAGE 11705 (ACMS1WAIT):

THREAD %1 IS ATTEMPTING TO SET A MEMORY FLAG, BUT THREAD %2 HAS ALREADY
COMPLETED.

User information: THE DYNAMIC MEMORY AREA IS NOT LARGE ENOUGH TO SATISFY
SIMULTANEOUS MEMORY REQUESTS FROM ALL SMP THREADS.

User action: RERUN THE JOB WITH MORE MEMORY.

11705.2 *** SYSTEM INFORMATION MESSAGE 11705 (ACMS1WAIT):

THREAD %1 IS HAS SET A MEMORY-WAIT FLAG.

User information: THE THREAD IS WAITING FOR DYNAMIC MEMORY TO COME AVAIL-
ABLE.

11705.3 *** SYSTEM INFORMATION MESSAGE 11705 (ACMS1WAIT):

THREAD %1 IS HAS Un-SET A MEMORY-WAIT FLAG.

User information: THE THREAD HAS SATISFIED ITS MEMORY REQUEST.

11705.4 *** SYSTEM INFORMATION MESSAGE 11705 (ACMS1WAIT):

THREAD %1 IS WAITING AT BARRIER NUMBER %2.

User information: THE THREAD HAS RELEASED MEMORY FOR ANOTHER THREAD TO USE.
IT WILL RESUME EXECUTION SHORTLY.

11706.0 *** USER INFORMATION MESSAGE 11706 (ACMS1PR):

Main Index
 1150 MSC Nastran Error Messages
Errors 11000 - 11999

TOTAL MEMORY AVAILABLE: %1 MB

MEMORY TO STORE STIFFNESS MATRIX: %2 MB *
MEMORY TO STORE MASS MATRIX: %3 MB *
MEMORY TO STORE LOAD MATRIX: %4 MB *
MEMORY TO STORE TABLE DATA: %5 MB *

11706.1 *** USER INFORMATION MESSAGE 11706 (ACMS1PR):

ACMS1 WORKING MEMORY: %1 MB
SIZE OF DYNAMIC MEMORY POOL: %2 MB
MEMORY RESERVED FOR STACK STORAGE: %3 MB

11706.2 *** USER INFORMATION MESSAGE 11706 (ACMS1PR):

MDHHREDX WORKING MEMORY: %1 MB
SIZE OF DYNAMIC MEMORY POOL: %2 MB
MEMORY RESERVED FOR STACK STORAGE: %3 MB

11707.0 *** USER INFORMATION MESSAGE 11707 (ACMS1PR):

THREAD %1 MAX DYNAMIC MEM = %2 MB (DOMAIN %3) MAX STACK MEM = %4 MB
(DOMAIN %5)

11708.0 *** USER INFORMATION MESSAGE 11708 (ACMS1PR):

MAXIMUM DYNAMIC MEMORY USED: %1 MB *
MAXIMUM STACK MEMORY USED: %2 MB *

11709.0 *** USER INFORMATION MESSAGE 11709 (PREMD2):

NUMBER OF ACMS COMPONENTS = %1

11710.0 *** USER INFORMATION MESSAGE 11710 (MODEFSRS):

NASTRAN IS EXECUTING ACMS VERSION = %1

11710.1 *** USER INFORMATION MESSAGE 11710 (ACMS1DR):

%1 PARALLEL SCHEDULING IS USED

11710.2 *** USER INFORMATION MESSAGE 11710 (ACMS1DR):

NUMBER OF PARALLEL GROUPS: %1
DEFAULT GROUP SIZE: %2

Main Index
 MSC Nastran Error Messages 1151
Errors 11000 - 11999

11800.0 *** SYSTEM FATAL MESSAGE 11800

CANNOT INITIALIZE RANDOM STREAM (MKL). SEED ENTERED = %1.

11801.0 *** SYSTEM FATAL MESSAGE 11801

CANNOT DELETE RANDOM STREAM (MKL).

11802.0 *** USER FATAL MESSAGE 11802

One or more of variability parameters MSVAR, KSVAR, BSVAR MFVAR, KFVAR or BFVAR entered in
the input file, are greater than maximum permissible value.
Maximum value of the variability = SQRT(2/(n+1)) = %1. Where, n = %2, are the number of modes. The
variability parameters selected by user should be less than this value. Please use the following quidelines for
selecting variability:
Low variability level < 0.001
Medium variability level < 0.01
High variability level < 0.05 (Note: As n increases, the permissible value of high variability descreases)

11802.1 *** USER FATAL MESSAGE 11802

CANNOT GENERATE RANDOM MATRIX DURING MONTE-CARLO SIMULATION. ERROR
DURING GENERATION OF GAMMA DISTRIBUTED RANDOM VALUES.

SUGGESTION: Check the variability parameters MSVAR, KSVAR, BSVAR MFVAR, KFVAR or
BFVAR entered in the input file, these may be non-physical.
Maximum value of the variability = SQRT(2/(n+1)) = %1. Where, n = %2, are the number of modes. The
variability parameters selected by user should be less than this value. Please use the following quidelines for
selecting variability:
Low variability level < 0.001
Medium variability level < 0.01
High variability level < 0.05 (Note: As n increases, the permissible value of high variability descreases)

11802.2 *** USER FATAL MESSAGE 11802

Main Index
 1152 MSC Nastran Error Messages
Errors 11000 - 11999

CANNOT GENERATE RANDOM MATRIX DURING MONTE-CARLO SIMULATION. ERROR

DURING GENERATION OF GAUSSIAN DISTRIBUTED RANDOM VALUES.

SUGGESTION: Check the variability parameters MSVAR, KSVAR, BSVAR MFVAR, KFVAR or
BFVAR entered in the input file, these may be non-physical.
Maximum value of the variability = SQRT(2/(n+1)) = %1. Where, n = %2, are the number of modes. The
variability parameters selected by user should be less than this value. Please use the following quidelines for
selecting variability:
Low variability level < 0.001
Medium variability level < 0.01

11804.0 *** USER FATAL MESSAGE 11804

CANNOT GENERATE RANDOM MATRIX DURING MONTE-CARLO SIMULATION.
Row SIZE OF Random Matrix IS INCORRECT, NROW = %1. It should
be = %2.

11805.0 *** USER FATAL MESSAGE 11805

DMP PARALLEL RUN MONTE-CARLO SIMULATION IN SOL 111 REQUIRES, "MULTI-MAS-
TER" DMP execution mode.

User action: Specify, "RUNOPT=MULTIMST", in "DOMAINSOLVER" Executive Control statement.

(SEE QRG FOR FURTHER DETAILS)

11806.0 *** USER INFORMATION MESSAGE 11806

RUNNING MONTE-CARLO SIMULATION IN SOL 111 WITH FOLLOWING PARAMETER:
NUMBER OF RANDOM SAMPLES (NMONCA) = %1
STRUCTURAL VARIABILITY, MSVAR = %2, KSVAR = %3, BSVAR = %4
FLUID VARIABILITY, MFVAR = %5, KFVAR = %6, BFVAR = %7

11807.0 *** USER FATAL MESSAGE 11807

MONCARLO CASE CONTROL COMMAND FOUND BELOW SUBCASE LEVEL, IT SHOULD
OCCUR ABOVE SUBCASE LEVEL.

User action: PLACE MONCARLO CASE CONTROL COMMAND ABOVE SUBCASE LEVEL.

11810.0 *** USER FATAL MESSAGE 11810

Main Index
 MSC Nastran Error Messages 1153
Errors 11000 - 11999

NO MONCARL BULK DATA ENTRY FOUND

User action: ADD MONCARL BULK DATA ENTRY WITH "SID = %1"

11811.0 *** USER FATAL MESSAGE 11811

NO MONCARL BULK DATA ENTRY WITH "SID = %1" FOUND

User action: ADD MONCARL BULK DATA ENTRY WITH "SID = %1"

11812.0 *** USER INFORMATION MESSAGE 11812

USER REQUESTED MONTE-CARLO SIMULATION BE RUN WITH DELTA VARIABILITIES
INSTEAD OF THE DEFAULT ALPHA VARIABILITIES.

11813.0 *** SYSTEM INFORMATION MESSAGE 11812

REQUESTED DMP=%1, BUT THE NUMBER OF FREQUENCIES REQUESTED FOR THE SUB-
CASE %2 IS LESS THAN THE DMP REQUESTED. SWITCHING TO SERIAL FREQUENCY
RESPONSE SOLUTION.

11851.0 *** USER INFORMATION MESSAGE 11851 (LUSOLDRV):

The permuted upper triangular factor matrix [U] is found to be singular during LU decomposition utilizing
LUSOL package.
Number of null rows in [U] = %1

User information: the constraint matrix is found to be rank deficient, need to eliminate redundant con-
straints in the model.

User action: None.

11852.0 *** USER INFORMATION MESSAGE 11852 (LUSOLDRV):

Rank deficiency is found for the constraint matrix during LU decomposition utilizing LUSOL package and
default Rook Pivoting.

User information: LUSOL will switch to Full Pivoting Method automatically to ensure rank revealing sta-
bility.

User action: None.

Main Index
 1154 MSC Nastran Error Messages
Errors 11000 - 11999

12001.0 *** USER WARNING MESSAGE 12001

RBE2GS WITH RIGID=LAGRAN OR RIGID=LGELIM WILL NOT BE CONVERTED TO AN
EQUIVALENT RBE2 AND HENCE WILL NOT CONTRIBUTE TO THERMAL LOADING IF
ANY SESET IS IN MAIN BULK DATA DECK.

11901.0 *** USER FATAL MESSAGE 11901 (BDYINF)

Subcase %1 contains a duplicate LDLABEL command: %2

11902.0 *** USER FATAL MESSAGE 11902 (PCOLSEL)

SELOAD Bulk Data entry SID=%1 contains a duplicate entry for SEID=%2

11903.0 *** USER FATAL MESSAGE 11903 (BDYINF)

There are one or more subcases that are missing an LDLABEL.
THIS IS A TEMPORARY RESTRICTION.

11904.0 *** USER FATAL MESSAGE 11904 (PCOLSEL)

Superelement %1 is specified on SELOAD=%2 Bulk Data entry but superelement %1 is undefined.

11905.0 *** USER FATAL MESSAGE 11905 (PCOLSEL)

Superelement %1 is specified on SELOAD=%2 Bulk Data entry but superelement %1 is not an external or
repeated superelement.

11906.0 *** USER FATAL MESSAGE 11906 (PCOLSEL)

There is no load label information available for superelement %1 and the SELOAD=%2 Bulk Data entry
does not define a column number. See the description of LBLTYP=COLNUM in the Quick Reference
Guide.

11907.0 *** USER FATAL MESSAGE 11907 (PCOLSEL)

The load identified by %1=%2 for superelement %3 on SELOAD=%4 Bulk Data entry was not found.

11908.0 *** USER FATAL MESSAGE 11908 (PCOLSEL)

The column number %1 on SELOAD=%2 Bulk Data entry for superelement %3 is higher than the num-
ber of available columns: %4.

11908.1 *** USER FATAL MESSAGE 11908 (SubDMAP EXTIN and SELG)
The column number %1 on SELOAD Bulk Data entry for this superelement is higher than the number of
available columns: %2.

Main Index
 MSC Nastran Error Messages 1155
Errors 11000 - 11999

11909.0 *** USER FATAL MESSAGE 11909 (PCOLSEL)

The %1=%2 on SELOAD=%3 Bulk Data entry for superelement %4 is not a positive integer.

11910.0 *** USER WARNING MESSAGE 11910 (PCOLSEL)

For LOAD = %1 or EXCITEID = %1 there is no corresponding SELOAD entry. Therefore no external
superelement loads will be included for this load case.

11911.0 *** USER WARNING MESSAGE 11911 (SubDMAP PHASE0)

LDLABEL Case Control commands are detected without the presence of the EXTSEOUT command. The
LDLABELs will be ignored.

11912.0 *** USER FATAL MESSAGE 11912 (SubDMAP PHASE0)

The LOADSET Case Control command is present with the LDLABEL Case Control command.

User information: LOADSET is not supported with LDLABEL.

11914.0 *** User Fatal Message 11914 (PCOLSEL)

A duplicate LABEL="%1" has been selected on SELOAD Bulk Data entry SID=%2.

11914.1 *** User Fatal Message 11914 (PCOLSEL)

A duplicate LOADID=%1 has been selected on SELOAD Bulk Data entry SID=%2.

11915.0 *** User Fatal Message 11915 (PCOLSEL)

On SELOAD Bulk Data entry SID=%1, the following continuation entries select the same external
superelement subcase
SELOAD continuation entries %2 and %3: %4=%5
SELOAD continuation entries %6 and %7: %8=%9

Main Index
 1156 MSC Nastran Error Messages
Errors 11000 - 11999

Main Index
 MSC Nastran Error Messages 1157
Errors 12000 - 12999

Errors 12000 - 12999

12001.0 *** USER WARNING MESSAGE 12001
RBE2GS WITH RIGID=LAGRAN OR RIGID=LGELIM WILL NOT BE CONVERTED TO AN
EQUIVALENT RBE2 AND HENCE WILL NOT CONTRIBUTE TO THERMAL LOADING IF
ANY SESET IS IN MAIN BULK DATA DECK.

Main Index
 1158
Errors 12000 - 12999

Main Index
 MSC Nastran Error Messages 1159
Errors 15000 - 15999

Errors 15000 - 15999

15110.0
Your final mode is a member of a set of %1 repeated roots, meaning that you have not calculated %2
modes at that same frequency and your results may not be accurate. It is recommended that you calculate
the additional repeated roots.

Main Index
 1160 MSC Nastran Error Messages
Errors 15000 - 15999

Main Index
 MSC Nastran Error Messages 1161
Errors 20000 - 20999

Errors 20000 - 20999

20000.0
Analysis started.

20010.0
Linear static analysis completed.

20100.0
Analysis started.

20110.0
Normal modes analysis completed.

20111.0
Complex modes analysis completed.

20112.0
Frequency response analysis completed.

20113.0
Transient response analysis completed.

20200.0
Optimization started.

20210.0
Design cycle %1 started.

20220.0
Design cycle %1 completed.

20230.0
Optimization completed.

Main Index
 1162 MSC Nastran Error Messages
Errors 20000 - 20999

Main Index
 MSC Nastran Error Messages 1163
Errors 21000 - 21999

Errors 21000 - 21999

21000.0
Geometry access/verification to CAD part initiated (if needed).

21010.0
Geometry access/verification to CAD part successfully completed (if needed).

21020.0
Finite element model generation started.

21030.0
Finite element model generation successfully completed.

21040.0
Application of Loads and Boundary Conditions to the finite element model started.

21050.0
Application of Loads and Boundary Conditions to the finite element model successfully completed.

21060.0
Solution of the system equations for linear statics started.

21061.0
Solution of the system equations for complex modes started.

21062.0
Solution of the system equations for frequency response started.

21063.0
Solution of the system equations for transient response started.

21070.0
Solution of the system equations for linear statics successfully completed.

Main Index
 1164 MSC Nastran Error Messages
Errors 21000 - 21999

21071.0
Solution of the system equations for complex modes successfully completed.

21072.0
Solution of the system equations for frequency response successfully completed.

21073.0
Solution of the system equations for transient response successfully completed.

21080.0
Solution of the system equations for normal modes started.

21090.0
Solution of the system equations for normal modes successfully completed.

21100.0
Error analysis of the results for p-adaptive iteration %1 started.

21101.0
Finite element model generated %1 degrees of freedom.

21102.0
Current p-adaptive iteration has maximum p-level of %1.

21103.0
Maximum element error for local error estimator is %1.

21104.0
Local error estimator indicates %1 elements converged or omitted and %2 unconverged.

21105.0
Next p-adaptive iteration has maximum p-level of %1.

21106.0
The current superelement or module (ID =%1) requires no further P-adaptive analysis because %2.

21106.1

Main Index
 MSC Nastran Error Messages 1165
Errors 21000 - 21999

P-adaptive analysis terminated because %1.

21107.0
Model error for global error estimator is %1.

21110.0
Error analysis of the results for p-adaptive iteration %1 successfully completed.

21120.0
Error analysis of the results successfully completed.

21130.0
It is not possible to perform any additional adaptive analysis after the current loop because of mesh distor-
tion parameters beyond acceptable limits.
The results in the vicinity of these highly distorted elements should be used with caution.

21801.0
The solver is attempting to connect to the CAD Part in order to verify geometric/parametric data.

21802.0
The solver has successfully connected to the CAD Part.
Verification of geometric/parametric data has started.

21803.0
The solver has successfully closed its connection to the CAD Part.

Main Index
 1166 MSC Nastran Error Messages
Errors 21000 - 21999

Main Index
 MSC Nastran Error Messages 1167
Errors 22000 - 22999

Errors 22000 - 22999

22001.0
CORBA: Geometry Evaluator Operation %1 failed.
During geometry verification, a communication failure has occurred.

22002.0
CORBA: Message Client Operation %1 failed.
During Message passing, a communication failure has occurred.

22003.0
CORBA: Geometry Evaluator Operation %1 failed.
The Possible causes are:
Check the following variables in .obb_login for correctness
ACS_ALTERNATE,ACS_MASTER, SHLIB_PATH,UGII_BASE_DIR,UGII_ROOT_DIR
AND/OR
Check the mode of executable "ugcorba"
Check the proxy and registration

22004.0
Analysis is running on: %1
CAD is running on : %2

22005.0 ** USER FATAL MESSAGE 22005 (IFP1)

ONE OR MORE AUXMODEL CASE CONTROL COMMANDS ARE SPECIFIED IN AN ANA-
LYTIC SHAPE OPTIMIZATION JOB BUT NO AUXCASE COMMAND IS FOUND.

22005.1 ** USER FATAL MESSAGE 22005 (IFP1)

ONE OR MORE AUXCASE CASE CONTROL COMMANDS ARE SPECIFIED IN AN ANALYTIC
SHAPE OPTIMIZATION JOB BUT NO AUXMODEL COMMAND IS FOUND.

22005.2 ** USER FATAL MESSAGE 22005 (IFP1)

NOT ENOUGH AUXCASE CASE CONTROL COMMANDS ARE SPECIFIED IN AN ANALYTIC
SHAPE OPTIMIZATION JOB TO SEPARATE AUXMODEL COMMANDS.

Main Index
 1168 MSC Nastran Error Messages
Errors 22000 - 22999

22005.3 ** USER FATAL MESSAGE 22005 (IFP1)

MORE THAN ONE AUXCASE COMMANDS ARE FOUND IN AN ANALYTIC SHAPE
OPTIMIZATION JOB BUT FEWER AUXMODEL COMMANDS ARE FOUND.

22005.4 ** USER FATAL MESSAGE 22005 (IFP1)

THE TYPE USED ON AN ANALYSIS CASE CONTROL ENTRY IS INVALID FOR CHAINING
ANALYSIS.

User information: CHAINING FROM HSTAT TO NLSTAT MUST BE DONE IN A SINGLE SUB-
CASE. MULTIPLE SUBCASES ARE NOT SUPPORTED.

22005.5 ** USER FATAL MESSAGE 22005 (IFP1)

THE TYPE USED ON AN ANALYSIS CASE CONTROL ENTRY IS INVALID FOR CHAINING
ANALYSIS.

User information: CHAINING FROM HTRAN TO NLSTAT IS NOT SUPPORTED.

22005.6 ** USER FATAL MESSAGE 22005 (IFP1)

TEMP(MATE) OR TEMP(BOTH) USED ON AN ANALYSIS CASE CONTROL ENTRY IS
INVALID FOR CHAINING ANALYSIS OF NLSTAT AND MFREQ.

User information: CHAINING FROM NLSTAT TO MFREQ WITH TEMP(MATE) or

TEMP(BOTH) IS NOT SUPPORTED.

22005.7 ** USER FATAL MESSAGE 22005 (IFP1)

ANALYSIS = LNSTAT IS ONLY SUPPORTED IN SOL 400. ANALYSIS=STATICS SHOULD BE
USED INSTEAD.

22005.8 ** USER FATAL MESSAGE 22005 (IFP1)

IN SOLUTION 400 PERTURBATION ANALYSES, ANALYSIS=NLSTATIC MUST APPEAR
BEFORE ANY OTHER SUBSEQUENT ANALYSIS THAT SPECIFIES A DIFFERENT TYPE, SUCH
AS MODES, MCEIG AND SO ON.
IF YOU WISH TO RUN WITH YOUR CURRENT ORDER, SET SYSTEM(742)=1, BUT THE
RESULTS MAY NOT BE CORRECT.

Main Index
 MSC Nastran Error Messages 1169
Errors 22000 - 22999

22005.9 ** USER WARNING MESSAGE 22005 (IFP1)

IN SOLUTION 400 PERTURBATION ANALYSES, ANALYSIS=NLSTATIC MUST APPEAR
BEFORE ANY OTHER SUBSEQUENT ANALYSIS THAT SPECIFIES A DIFFERENT TYPE, SUCH
AS MODES, MCEIG AND SO ON. YOU HAVE SET SYSTEM(742)=1, WHICH ALLOWS THE
RUN TO CONTINUE IN SPITE OF NOT SATISFYING THIS REQUIREMENT - BE AWARE
THAT THE RESULTS MAY BE INCORRECT.

22005.10 ** USER FATAL MESSAGE 22005 (IFP1)

NSM CASE CONTROL COMMAND FOUND AFTER THE FIRST SUBCASE/STEP/SUBSTEP
LEVEL.

User action: PLACE NSM CASE CONTROL COMMAND ABOVE SUBCASE LEVEL OR AT THE
FIRST SUBCASE/STEP/SUBSTEP LEVEL.

22006.0 *** USER FATAL MESSAGE 22006 (ASGTRD)

TRIM BULK DATA ENTRY ID = %1 CONTAINS AN INVALID VALUE FOR LABEL=%2
A VALID VALUE WOULD BE A REAL NUMBER OR ONE OF THE FOLLOWING STRINGS:
FREE, LINKED, or SCHED.

User action: FIX THE VALUE.

22007.0 *** USER WARNING MESSAGE 22007 (APD12)

The AERODOF parameter must contain degrees of freedom 3 and 5.
Degree of freedom %1 has been added by the program.

User action: None.

22008.0 *** USER WARNING MESSAGE 22008 (NDIDRD)

Module NDINTERP is skipping the computation of the derivative interpolation factors (UXDIFV). The
input UX matrix contains more than one column and since UX defines the reference state for the deriva-
tives, this is a nonsensical situation.

User Action: Either remove UXDIFV from the NDINTERP call or pass in a UX matrix with only a single
column.

Main Index
 1170 MSC Nastran Error Messages
Errors 22000 - 22999

22009.0 *** USER WARNING MESSAGE 22009 (TA0NLELM)

LINEAR SHEAR PANEL ELEMENTS WITH PROPERTY ID = %1 ARE USED IN A LARGE DIS-
PLACEMENT ANALYSIS.

Suggestion: USE NON-LINEAR PROPERTY EXTENSION (PSHEARN) OR MDLPRM,SHR-

TOQ4,1

22009.1 *** USER WARNING MESSAGE 22009 (TA0NLELM)

LINEAR BAR ELEMENTS WITH PROPERTY ID = %1 ARE USED IN A LARGE DISPLACEMENT
ANALYSIS.

Suggestion: USE NON-LINEAR PROPERTY EXTENSION (PBARN1) OR MDLPRM,BRTOBM,1

22009.2 *** USER WARNING MESSAGE 22009 (TA0NLELM)

LINEAR QUAD8/TRIA6 ELEMENTS WITH PROPERTY ID = %1 ARE USED IN A LARGE DIS-
PLACEMENT ANALYSIS.

Suggestion: USE NON-LINEAR PROPERTY EXTENSION (PSHLN1)

22009.3 *** USER WARNING MESSAGE 22009 (TA0NLELM)

LINEAR HEXA20/PENTA15 ELEMENTS WITH PROPERTY ID = %1 ARE USED IN A LARGE
DISPLACEMENT ANALYSIS.

Suggestion: USE NON-LINEAR PROPERTY EXTENSION (PSLDN1)

22500.0 *** USER INFORMATION MESSAGE 22500 (PEAKOUT)

PEAKS FOUND BEFORE FREQUENCY FILTERING : %1 AFTER FREQUENCY FILTERING: %2

22500.1 *** USER INFORMATION MESSAGE 22500 (PEAKOUT)

TABLED1 %1 IS NOT DEFINED IN THE USER INPUT FILE. PEAKOUT CASE CONTROL
CARD WILL RUN WITH DEFAULT VALUES.

User action: Define Tabled1 %1 corresponding to PARAM, PTHRES to obtain participation factor
against the intended response threshold value.

22501.0 *** USER INFORMATION MESSAGE 22501 (SEDRCVR)

PEAKOUT REQUESTED FOR SUBCASE : %1

Main Index
 MSC Nastran Error Messages 1171
Errors 22000 - 22999

22501.1 *** USER WARNING MESSAGE 22501 (SEDRCVR)

In Case %1, DISPLACEMENT output set is missing from setdof of PFMODE, PFGRID or PFPANEL
Case Control command on a PEAKOUT request. The PEAKOUT output is being skipped.

User Information: For PEAKOUT request, all GRIDs referenced on any setdof of PFMODE, PFGRID
and PFPANEL requests are required (but not limited to) on a DISP output command. The DISP
command must be placed above the SUBCASE level.

22502.0 *** USER INFORMATION MESSAGE 22502 (SEDRCVR)

FRF PEAK IDENTIFICATION
NUMBER OF SUBCASES : %1
NUMBER OF RESPONSE GRIDS : %2
NUMBER OF FREQUENCIES : %3
*^^^

22503.0 *** USER INFORMATION MESSAGE 22503 (SEDRCVR)

CURRENT SUBCASE : %1
PARAMETERS FOR PEAK IDENTIFICATION
REQUESTED NUMBER OF PEAKS: %2
NEAR FREQUENCY THRESHOLD : %3
LOWEST FREQUENCY : %4
HIGHEST FREQUENCY : %5
STRUCTURE RESULTS TYPE : %6
FLUID RESULTS TYPE : %7
*^^^

22504.0 *** USER INFORMATION MESSAGE 22504 (SEDRCVR)

RESPONSE GRID :%1 IS A %2 GRID (%3 DOF)
*^^^

22504.1 *** USER WARNING MESSAGE 22504 (SEDRCVR)

UNDEFINED RESPONSE GRID :%1
*^^^

Main Index
 1172 MSC Nastran Error Messages
Errors 22000 - 22999

22505.0 *** USER INFORMATION MESSAGE 22505 (PEAKDBA)

USING DB RESULTS WITH A FILTER FOR PEAK IDENTIFICATION
*^^^

22505.1 *** USER INFORMATION MESSAGE 22505 (PEAKDBA)

USING DB RESULTS FOR PEAK IDENTIFICATION
*^^^

22506.0 *** USER INFORMATION MESSAGE 22506 (SETFREQ)

AUTOMATIC PARTICIPATION ANALYSIS
SUBCASE : %1
RESPONSE GRID : %2 (FOR STRUCTURE GRID, LAST DIGIT IS DOF)
NUMBER OF RESPONSE PEAKS FOR PF DETECTED: %3
*^^^

22507.0 *** USER WARNING MESSAGE 22507 (SETFREQ)

NUMBER OF RESPONSE PEAKS IS 0, NO PF WILL BE CALCULATED FOR THIS GRID/DOF/
SUBCASE
*^^^

22508.0 *** USER WARNING MESSAGE 22508 (SETFREQ)

FREQUENCY : %1

22600.0 *** USER INFORMATION MESSAGE 22600 (csCnvLTE)

%1, csFlg = %2, csStatic = %3
Updated csU_max and csV_max follows.

22601.0 *** USER INFORMATION MESSAGE 22601 (csCnvLTE)

%1, csFlg = %2, csoconv = %3, csolte = %4
Predicted csUo and csVo saved, printout of these follows.

22602.0 *** USER INFORMATION MESSAGE 22602 (csDduHHT)

%1, csFlg = %2, Step Size (csH) = %3.
HHT Integrator Parameters:
Alpha = %4, Gamma = %5, Beta = %6.

22603.0 *** USER INFORMATION MESSAGE 22603 (csDduVa)

%1, csFlg = %2, Step Size (csH) = %3.

Main Index
 MSC Nastran Error Messages 1173
Errors 22000 - 22999

22604.0 *** USER INFORMATION MESSAGE 22604 (csGenTrn)

csGenTrn: No CSTM supplied, hence assuming Basic Coord and Global Coord are same

22605.0 *** USER INFORMATION MESSAGE 22605 (csGenTrn)

csGenTrn: Trans. matrix from Global to Basic: G-size, follows:

22605.1 *** USER INFORMATION MESSAGE 22605 (csGenTrn)

csGenTrn: Trans. matrix from Global to Basic: F-size, follows:

22605.2 *** USER INFORMATION MESSAGE 22605 (csGenTrn)

csGenTrn: Trans. matrix from Global to Basic: A-size, follows:

22606.0 *** USER INFORMATION MESSAGE 22606 (csMatRed)

%1, Integrator Type = %2,
Step Size (csH) = %3, Beta = %4
csFeSize = %5, KDiag = %6.

22607.0 *** USER INFORMATION MESSAGE 22607 (csMatRed)

%1, HHT Integrator Parameters:
Alpha = %2, Beta = %3, Gamma = %4.

22608.0 *** USER INFORMATION MESSAGE 22608 (csMatGen)

%1, Calling NAMG/NAMGSM Module.

22609.0 *** USER INFORMATION MESSAGE 22609 (csRdAdbP)

csRdAdbP: csFlg = %1, Num. Markers = %2, Solver = %3
Order of Int. = %4, Step Size = %5, Beta = %6,
csT0 = %7.

22610.0 *** USER INFORMATION MESSAGE 22610 (csRecUPV)

%1, Upvnlh before reconciled with NLFE, follows:

22610.1 *** USER INFORMATION MESSAGE 22610 (csRecUPV)

%1, Upvnlh not Generated.

Main Index
 1174 MSC Nastran Error Messages
Errors 22000 - 22999

22610.2 *** USER INFORMATION MESSAGE 22610 (csRecUPV)

%1, Final upvnlh after Reconciling, follows:

22611.0 *** USER INFORMATION MESSAGE 22611 (csResRed)

%1, %2

22612.0 *** USER INFORMATION MESSAGE 22612 (csResTr)

%1, %2

22612.1 *** USER INFORMATION MESSAGE 22612 (csResTr)

%1, Residual Norms Satisfaction Adams-Nastran Coupled Simulation
Norm(R_o) = %1, Norm(R_a) = %2, csFlg = %3 and Time = %4

22613.0 *** USER INFORMATION MESSAGE 22613 (csRvLim)

%1, %2

22613.1 *** USER INFORMATION MESSAGE 22613 (csRvLim)

%1, %2, NCSRVLIM limited Rotation Vector = %3.

22614.0 *** USER INFORMATION MESSAGE 22614 (setMnfSt)

setMnfSt: NMODES = %1, CPSIZE = %2 and MPSIZE = %3

22615.0 *** USER INFORMATION MESSAGE 22615 (setRigMas)

setRigMas: %1

22616.0 *** USER INFORMATION MESSAGE 22616 (setRigIC)

setRigIC: %1

22616.1 *** USER INFORMATION MESSAGE 22616 (setRigIC)

setRigIC: %1, APP = %2

22617.0 *** USER WARNING MESSAGE 22617 (NONLIN)

Numerical Partial ON, Enforcing Unsymmetric Decomposition

22618.0 *** USER INFORMATION MESSAGE 22618 (NONLIN)

BGN_LOOP3: NLOOP = %1, SOLCUR = %2, STEPCUR = %3
TANALY = %4, NSTEP = %5 and Ph2out = %6

Main Index
 MSC Nastran Error Messages 1175
Errors 22000 - 22999

22618.1 *** USER INFORMATION MESSAGE 22618 (NONLIN)

BGN_LOOP3: csFlg = %1, CONV = %2, NEWP = %3
OFLAG = %4 and NEWK = %5

22618.2 *** USER INFORMATION MESSAGE 22618 (NONLIN)

Nastran Adams Coupled Simulation Set Sizes:
csFesize = %1, csAsize = %2, csOsize = %3
csLmsize = %4, csOminlm = %5

22619.0 *** USER INFORMATION MESSAGE 22619 (NONLIN)

Resuming HALT 3 NLSOLV, Csflg = %1 and csNewK = %2

22620.0 *** USER FATAL MESSAGE 22620 (RIGIDIC)

RMOTION Matrix is not of correct dimension %1

22621.0 *** USER FATAL MESSAGE 22621 (RIGIDIC)

RMOTION matrix is not of correct form (rec.) or type (nprec.)
%1

22622.0 *** USER FATAL MESSAGE 22622 (RIGIDIC)

Reference Grid Internal Number, %1, is not valid.

22623.0 *** USER FATAL MESSAGE 22623 (RIGIDIC)

Both refgrid and ref location have been supplied, only one should be supplied.

22624.0 *** USER FATAL MESSAGE 22624 (RIGIDIC)

Ref location has not been provided correctly. %1

22625.0 *** USER FATAL MESSAGE 22625 (RIGIDIC)

Reference Location Vector is not of correct form (rec.) or type (nprec.)
%1

22626.0 *** USER FATAL MESSAGE 22626 (RIGMASS)

%1

Main Index
 1176 MSC Nastran Error Messages
Errors 22000 - 22999

22627.0 *** USER FATAL MESSAGE 22627 (RIGMASS)

Reference Grid Internal Number, %1, is not valid.

22628.0 *** USER FATAL MESSAGE 22628 (RIGMASS)

Both refgrid and ref location have been supplied, only one should be supplied.

22629.0 *** USER FATAL MESSAGE 22629 (RIGMASS)

Ref location has not been provided correctly. %1

22630.0 *** USER FATAL MESSAGE 22630 (RIGMASS)

Reference Location Vector is not of correct form (rec.) or type (nprec.)
%1

22631.0 *** USER FATAL MESSAGE 22631 (NAMG)

Matrix Size of csMT has incorrect number of Rows = %1

22632.0 *** USER INFORMATION MESSAGE 22632 (RIGMASS)

Reference Location not present, it has been assumed to be the Origin of basic coordinate system.

22633.0 *** USER INFORMATION MESSAGE 22633 (NONLIN)

After csRvLim, Was RV limiting Done (csdidlim) = %1

22640.0 *** USER WARNING MESSAGE 22640 (SELGDISP)

Module SELGDISP terminated with no action taken due to improper definition of reference GRID points:
REFGRID1 = %1
REFGRID2 = %2
REFGRID3 = %3

User information: Either only REFGRID1 or all three reference GRID points must be specified

22700.0 *** USER WARNING MESSAGE 22700 (FRLMI )

Frequency list of ID %1 not found.

22700.1 *** USER FATAL MESSAGE 22700 (FRLMI )

Master frequency list is missing.

Main Index
 MSC Nastran Error Messages 1177
Errors 22000 - 22999

22701.0 *** USER FATAL MESSAGE 22701 (TA0EPTSP)

%1 SPECIFIED ON %4 ENTRY ID %2 HAS AN ASSOCIATED %3 ENTRY.

User information: %5 ENTRY CONFLICTS WITH ANOTHER SPATIAL DEPENDENT OR FRE-

QUENCY DEPENDENT ENTRY.

22701.1 *** USER FATAL MESSAGE 22701 (TA0EPTSP)

MID %1 OF %2 ID %3 SPECIFIED ON PDISTB ENTRY ID %4 HAS AN ASSOCIATED MATiF
ENTRY.

User information: PDISTB ENTRY CONFLICTS WITH ANOTHER SPATIAL DEPENDENT OR

FREQUENCY DEPENDENT ENTRY.

22701.2 *** USER FATAL MESSAGE 22701 (TA0EPTPC)

MID %1 OF PBCOMP ENTRY ID %2 HAS AN ASSOCIATED MATiF ENTRY.

User information: THE MATERIAL PROPERTIES ASSOCIATED WITH A PBCOMP ENTRY CAN-
NOT BE FREQUENCY DEPENDENT.

22702.0 *** USER FATAL MESSAGE 22702 (TA0EPTSP)

%1 SPECIFIED ON %3 ENTRY ID %2 EXCEEDS THE NUMBER OF PLIES DEFINED ON THE
ASSOCIATED PCOMP OR PCOMPG ENTRY.

22702.1 *** USER FATAL MESSAGE 22702 (TA0EPTSP)

MIDNUM %1 SPECIFIED ON PDISTBM ENTRY ID %2 IS GREATER THAN FOUR FOR PROP-
ERTY TYPE PSHELL.

User information: FOR PSHELL ENTRY, MAXIMUM FOUR MATERIAL IDENTIFICATION

NUMBERS ARE ALLOWED.

22702.2 *** USER FATAL MESSAGE 22702 (TA0EPTSP)

%1 SPECIFIED ON %3 ENTRY ID %2 EXCEEDS %4 FOR THE ASSOCIATED %5 ENTRY.

22703.0 *** USER FATAL MESSAGE 22703 (TA0EPTSP)

PDISTB ENTRY ID=%1 SPECIFIES AN UNSUPPORTED PROPERTY NAME.

Main Index
 1178 MSC Nastran Error Messages
Errors 22000 - 22999

22704.0 *** USER FATAL MESSAGE 22704 (TA0EPTSP)

FOR %1, PID %2 WITH PROPERTY NAME %3 IS NOT FOUND IN PRIMARY ELEMENT
PROPERTY TABLE.

22705.0 *** USER FATAL MESSAGE 22705 (TA0EPTSP)

NON-UNIQUE %1 ON %4 ENTRY %2 WITH PID=%3.

22705.1 *** USER FATAL MESSAGE 22705 (TA0EPTSP)

NON-UNIQUE GPLID %2 ON %1 ENTRY WITH PID=%3.

22706.0 *** USER WARNING MESSAGE 22706 (PHASE1A)

PDISTB OR PDISTBM ENTRIES ARE NOT ALLOWED IN NONLINEAR ANALYSIS RUN.

22706.1 *** USER FATAL MESSAGE 22706 (PHASE1A)

RESTART INTO FREQUENCY DEPENDENT ANALYSIS and A NON-ZERO PARAM NMNLFRQ
DETECTED.

22707.0 *** USER FATAL MESSAGE 22707 (PHASE1A)

FREQUENCY DEPENDENT MATERIAL FOUND ON ELEMENTS CONNECTED TO O-SET
DOF. PLEASE ADJUST A-SET or O-SET SUCH THAT ELEMENTS USING FREQUENCY
DEPENDENT MATERIAL ARE USED ON A-SET DOFS OF RESIDUAL.

22708.0 *** USER FATAL MESSAGE 22708 (TA0ECTF)

ELEMENT %1 REFERENCES PLPLANE PROPERTY %2 WHICH IS ONLY VALID IN NONLIN-
EAR ANALYSIS.

22708.1 *** USER FATAL MESSAGE 22708 (USRMSG)

ELEMENT %1 WITH ELEMENT TYPE %3 AND PID=%2 REFERENCES EITHER AN UNDE-
FINED PROPERTY OR AN INVALID PROPERTY ENTRY.

User action: SPECIFY APPROPRIATE PROPERTY ENTRY.

22709.0 *** USER INFORMATION MESSAGE 22709. ( SUBDMAP SEDRCVR )

START PRINTING DATA RECOVERY USING FREQUENCY DEPENDENT MATERIAL
PROPERTIES
NOTE THAT ONLY COMMON FREQUENCIES BETWEEN MFREQ AND FREQ are
RECOVERED.

Main Index
 MSC Nastran Error Messages 1179
Errors 22000 - 22999

22709.1 *** USER INFORMATION MESSAGE 22709. ( SUBDMAP SEDRCVR )

END PRINTING DATA RECOVERY USING FREQUENCY DEPENDENT MATERIAL
PROPERTIES
NOTE THAT ONLY COMMON FREQUENCIES BETWEEN MFREQ AND FREQ are RECOV-
ERED.

22710.0 *** USER FATAL MESSAGE 22710 (IFPecMGE)

A zero value of GE on %1 %3 entry cannot be Frequency Dependent.

User information: %2 %3 entry has GE = %4

22710.1 *** USER FATAL MESSAGE 22710 (IFPecMGi)

One or more zero values of EXTENDED GEij on %1 %3 entry cannot be Frequency Dependent.

User information: %2 %3 entry has at least %4 non-zero GEij: %5

22711.0 *** USER FATAL MESSAGE 22711 (SEMG)

Frequency dependent capability via MATiF does not support axi-symmetric rotor dynamics.

22711.1 *** USER FATAL MESSAGE 22711 (SEMG)

FREQUENCY case control command missing for frequency response analysis.
STATSUB static loading is not currently supported for frequency dependent material/property.

22712.0 *** USER WARNING MESSAGE 22712 (SEMG)

MASTER Frequencies via MFREQ/FREQ in Frequency dependent capability ignores FREQ3/FREQ4/
FREQ5.

22712.1 *** USER FATAL MESSAGE 22712 (SEMG)

Master frequency list missing. This could be due to MFREQ defaulted to FREQ and FREQ case control
selects FREQ3/4/5 only.

User action: define MFREQuency case control and select only FREQ/FREQ1/FREQ2 bulk data entries.

22713.0 *** USER INFORMATION MESSAGE 22713 (SEKDR)

PARAMETER EXCLUDE IS NOT DEFINED DIFFERENTIAL STIFFNESS IS COMPUTED FOR
ALL ELEMENTS.

Main Index
 1180 MSC Nastran Error Messages
Errors 22000 - 22999

22713.1 *** USER INFORMATION MESSAGE 22713 (SEKDR)

PARAMETER EXCLUDE IS DEFINED DIFFERENTIAL STIFFNESS IS COMPUTED ONLY FOR
A SUBSET OF ELEMENTS.

22714.0 *** USER WARNING MESSAGE 22714 (MFREQRS,FREQRS.XFREQDEP)

Forcing frequency value of 0.0 detected, nominal (initial) material properties used.

22715.0 *** USER WARNING MESSAGE 22715 (PHASE1A)

THE VISCOUS DAMPING MATRIX IS NOT POSITIVE DEFINITE AND CANNOT BE CON-
VERTED TO COLUMNAR FORM.
THE B2GG MATRIX SHOULD BE CHANGED TO B2PP.

22716.0 *** USER INFORMATION MESSAGE 22716 ( FRQAUTO )

FREQUENCY DEPENDENT ELEMENT/MATERIAL PROPERTY VALUES ARE CONSTANT.
NOTE THAT AUTOMATIC MASTER FREQUENCY LIST IS SELECTED RANDOMLY.

22800.0 *** SYSTEM FATAL MESSAGE 22800 (bcauto)

Cannot allocate %1 MB memory from open core.

User action: increase memory size by %2 MB.

22800.1 *** SYSTEM FATAL MESSAGE 22800 (bcauto_merge_contact)

Cannot assign new ids for %1.

User action: Contact MSC Software client support

22801.0 *** USER FATAL MESSAGE 22801 (bcauto_read_bcautop_set1)

Set1 id %1 is used by BCAUTOP, but not defined.

User action: check your input file.

22801.1 *** USER FATAL MESSAGE 22801 (bcauto_merge_contact)

%1 entries are not allowed in BCONTACT=AUTO.

22801.2 *** USER WARNING MESSAGE 22801 (bcauto_read_bcautop_set1)

Only one of ESET, SEEDESET, SEEDGSET and PROPSET is allowed in BCAUTOP, but found both
%1 and %2, the first one is used.

Main Index
 MSC Nastran Error Messages 1181
Errors 22000 - 22999

22801.3 *** SYSTEM FATAL MESSAGE 22801 (bcauto)

Unexpected exception caught(%1), contact MSC Software technical support

22801.4 *** USER FATAL MESSAGE 22801 (bcauto)

There is more than one BCAUTOP entry detected in the input. Multiple entries are not supported.

User action: Remove un-used BCAUTOP entries from the input file.

22801.5 *** USER WARNING MESSAGE 22803 (bcauto_write_data)

Cannot find below rigid contact bodies referred by SET1 %1, which is used by RigidSet in BCAUTOP
ID=%2.
Will be ignored.

22802.0 *** USER FATAL MESSAGE 22802 (mcn1inid.F)

No contact pair is detected for BCONTACT=AUTO.

User action: check input model and .acg file, increase DISTANCE of BCAUTOP.

22802.1 *** USER INFORMATION MESSAGE 22802 (bcauto_genbconprg)

IGLUE determined by BCONTACT or BCAUTOP was %1, is overwritten to %2 by IGLUE in BCAU-
TOP %3.

22802.2 *** USER WARNING MESSAGE 22802 (bcauto_genbconprg)

Both ERROR and ERRBAS are specified in BCAUTOP, and ERRBAS is LOCAL, ERROR will be
ignored.

22802.3 *** USER INFORMATION MESSAGE 22802 (bcauto_genbconprg)

%1 determined by %2 in BCAUTOP was %3, is overwritten to %4 by IGLUE in BCAUTOP.

22802.4 *** USER INFORMATION MESSAGE 22802 (bcauto_genbconprg)

%1 determined by %2 in BCAUTOP was %3, is overwritten to %4 by %1 in BCAUTOP.

22803.1 *** USER WARNING MESSAGE 22803 (bcauto_merge_contact)

%1 contact bodie(s) have been generated.

Main Index
 1182 MSC Nastran Error Messages
Errors 22000 - 22999

22803.2 *** USER WARNING MESSAGE 22803 (bcauto_genpair)

%1 contact pair(s) have been detected.

22803.3 *** USER WARNING MESSAGE 22803 (bcauto)

Properties with IDs %2 were referred in PropSet of BCAUTOP ID=%1,
but no elements using those properties were found in the input file.

22804.0 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

Duplicate ID %1 was found among BCSURF, BCGRID and BCBODY1.

22804.1 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

Cannot find element face of element %1 with grid ids %2 in BCSURF %3.

User action: check BCSURF %3 in the input file.

22804.2 *** SYSTEM FATAL MESSAGE 22804 (MCNGBCSF)

Cannot find BCSURF or BCGRID with BID=%1.

Programmer information: Check code in MCNGBCSF.F90.

22804.3 *** SYSTEM FATAL MESSAGE 22804 (MCNGBCSF)

BCGRID entries are found in the input file, METHOD OF BCPARA is SEGTOSEG.

User action: Change method of BCPARA to NODESEG or delete all BCGRID entries.

22804.4 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

Illegal face id %1 is specified on element %2 in BCSURF %3.

User action: check BCSURF %3 in the input file.

22804.5 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

Only ELEM, SET or blank is allowed in IDTYPE field on element %1 in BCSURF %2.

User action: check BCSURF %2 in the input file.

22804.6 *** USER INFORMATION MESSAGE 22804 (MCNGBCSF)

%1 of BCBODY1 entries are generated for entry %2 BID=%3, BID's are(is) %4.
Element list of the generated BCBODY1 entries is shown below.

Main Index
 MSC Nastran Error Messages 1183
Errors 22000 - 22999

22804.7 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

The SET3 ID=%1 referenced in BCSURF ID=%2 doesn't exist.

22804.8 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

The SET3 ID=%1 referenced in BCSURF ID=%2 is not an element set.

22804.9 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

The face label %1 for element %2 in BCSURF ID=%3 is not applicable to the element type or dimension.

22804.10 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

The element %1 referenced in BCSURF ID=%2 doesn't exists.

22804.11 *** USER FATAL MESSAGE 22804 (MCNGBCSF)

The blank face label for element %1 in BCSURF ID=%2 is not applicable to solid element.

22804.12 *** USER WARNING MESSAGE 22804 (MCNGBCSF)

Two or three of TOP, BTM and BOTH are found in BCSURF ID=%1, BOTH is applied to them.

22805.0 *** USER FATAL MESSAGE 220805 (modify_bconect)

Secondary and primary of BCONECT %1 are %2 and %3 respectively, they are both IDs of BCGRID,
this is illegal. BCGRID can be used as secondary only in BCONECT.

22805.1 *** USER WARNING MESSAGE 22805 (modify_bconect)

BCGRID %1 is used as PRIMARY by BCONECT %2, has been swapped with SECONDARY %3.

22805.2 *** USER FATAL MESSAGE 22805 (modify_bconect)

IDSLi and IDMAi of BCONECT %1 have %2 and %3 respectively, which are both IDs of BCGRID,
this is illegal. BCGRID is allowed in IDSLi field only.

22805.4 *** SYSTEM FATAL MESSAGE 22805 (modify_bconect)

BCGRID %1 is used as primary in BCONECT %2, this is illegal.

Programmer information: check implementation of modify_bconect.cpp

22805.5 *** SYSTEM INFORMATION MESSAGE 22805 (modify_bconect)

%1 of BCONPRG based on BCONPRG ID=%2 for BCONECT ID=%3 is changed from %4 to %5.

Main Index
 1184 MSC Nastran Error Messages
Errors 22000 - 22999

22805.6 *** USER FATAL MESSAGE 22805 (modify_bconect)

Both BCBODY1 ID=%1 and BCSURF ID=%2 are referenced by BCONECT=%3, only one type can be
used in a BCONECT entry.

22805.7 *** USER FATAL MESSAGE 22805 (modify_bconect)

BCSURF ID=%1 is used as a secondary by BCONECT=%2 while BCBODY1 ID=%3 is a primary.

22806.0 *** SYSTEM FATAL MESSAGE 22806 (mcnt_bsurf)

Unexpected end of record when reading %1 record of contact datablock.

Programmer information: check implementation.

22807.1 *** SYSTEM FATAL MESSAGE 22807 (elface)

Element face number is %1, not in the range of 1 to %2 for a %3 type element.

22807.2 *** SYSTEM FATAL MESSAGE 22807 (mcntelcl)

Expecting %1 and %2 be the same, but not.

Programmer information: check implementation.

22808.0 *** USER FATAL MESSAGE 22808 (mcngbcsf)

The type of element %1 referenced in BCSURF ID=%2 is not supported by BCSURF.

22809.0 *** USER WARNING MESSAGE 22804 (mcngbcsf)

The combination of BTM and BOTH or TOP and BOTH is found in BCSURF ID=%1, this is not
allowed.

22809.1 *** USER FATAL MESSAGE 22809 (mcnt_surf_geom2)

The same element %1 with BTM,TOP or BOTH shows more than once in BCSURF ID=%2, this is not
allowed.

22809.2 *** USER WARNING MESSAGE 22809 (mcnt_surf_geom2)

Some elements are shared by multiple BCBODY1, BCSURF or BCGRID entries, this may lead to unex-
pected results.
The element id, up to 3 BID's for each element are listed below.
EID BID1 BID2 BID3

Main Index
 MSC Nastran Error Messages 1185
Errors 22000 - 22999

22810.1 *** USER WARNING MESSAGE 22810 (mcngbcsf)

BCGRID ID=%1 is used in BCONECT ID=%2 as primary since ISEARCH is set to 1 in BCONPRG
ID=%3.
BCGRID cannot be used as primary.
IDSCND and IDPRIM have been swapped to make BCGRID ID=%1 as secondary.

22810.2 *** USER WARNING MESSAGE 22810 (mcngbcsf)

BCGRID ID=%1 is used in BCONECT ID=%2 as primary because it is the greater one in IDSCND and
IDPRIM or IDSCNDi and IDPRIMi, and corresponding ISEARCH of BCONPRG is 0.
ISEARCH has been set to 1 to make BCGRID ID=%1 as secondary.

22810.3 *** USER WARNING MESSAGE 22810 (mcngbcsf)

BCGRID ID=%1 is used in BCONECT ID=%2 and ISEARCH of BCONPRG ID=%3 is 2, ISEARCH
can only be 0 or 1 when BCGRID is referred.
ISEARCH has been set to 1 to make BCGRID ID=%1 as secondary.

22810.4 *** USER FATAL MESSAGE 22810 (mcngbcsf)

BCGRID ID=%1 is used in BCONECT ID=%2, this doesn't work for segment to segment method.

User action: change METHOD OF BCPARA from SEGTOSEG to NODESURF.

22810.5 *** USER FATAL MESSAGE 22810 (mcngbcsf)

BCSURF ID=%1 is used in BCONECT ID=%2 as primary because it is the greater one in IDSCND and
IDPRIM or IDSCNDi and IDPRIMi, All lines in this BCSURF are either edges or beam ends, this is
illegal in node to segment method.

User action: change METHOD OF BCPARA from SEGTOSEG to NODESURF.

22811.1 *** USER FATAL MESSAGE 22810 (modify_bconect.cpp)

IDSCNDi=%1 or IDPRIMi=%1 of BCONECT ID=%2 referrs to a BCSURF or BCGRID, this is not
supported.

User action: Put the IDSCNDi or IDSCNDi to IDSCND or IDPRIM field of BCONECT for BCGRID
or BCSURF.

Main Index
 1186 MSC Nastran Error Messages
Errors 22000 - 22999

22811.2 *** USER FATAL MESSAGE 22810 (modify_bconect)

Cannot find BCONPRG ID=%1 referred by BCONECT ID=%2.

22851.0 *** USER INFORMATION MESSAGE 22851

Incremental mass for: SEID = %1, MASSID = %2, LABEL = %3, GPWG Follows:

22851.1 *** USER INFORMATION MESSAGE 22851

Incremental mass for: MASSID = %1, LABEL = %2, GPWG Follows:

22851.2 *** USER INFORMATION MESSAGE 22851

Incremental mass for: SEID = %1, MASSID = %2, GPWG Follows:

22851.3 *** USER INFORMATION MESSAGE 22851

Incremental mass for: MASSID = %1, GPWG Follows:

22852.0 *** USER INFORMATION MESSAGE 22852

Generating Mass Combination set for: SEID = %1, MASSID = %2

22852.1 *** USER INFORMATION MESSAGE 22852

Generating Mass Combination set for: MASSID = %1

22853.0 *** USER INFORMATION MESSAGE 22853

Mass Combination set for: SEID = %1, MASSID = %2, GPWG Follows:

22853.1 *** USER INFORMATION MESSAGE 22853

Mass Combination set for: MASSID = %1, GPWG Follows:

22854.0 *** SYSTEM WARNING MESSAGE 22854 (MASSCMB)

UNABLE TO FIND DATABLOCK FAMILY MEMBER %1 = %2 REFERENCED BY MASSSET =%3
ASSUMING IT TO BE ZERO FOR THIS SUPERELEMENT

22855.0 *** USER FATAL MESSAGE 22855

Multiple mass configuration (MMC) capability is not supported with old IFP.

User action: Remove NASTRAN IFPSTAR=NO, NASTRAN SYSTEM (444) = 0 or equivalent

command line argument.

Main Index
 MSC Nastran Error Messages 1187
Errors 22000 - 22999

22856.0 *** USER FATAL MESSAGE 22856

Multiple mass configuration (MMC) capability is not supported for restarts.

22857.0 *** USER FATAL MESSAGE 22857 (MASSCMB)

MASSSET bulk data entry ID = %2 cannot have the same ID as the mass increment defined on "BEGIN
MASSID = %2". IDs of mass combinations defined by MASSSET bulk data entry and mass increments
defined by "BEGIN MASSID" should be unique.

User action: Please choose another unique ID for MASSSET bulk data entry ID = %2.

22858.0 *** USER FATAL MESSAGE 22858

Multiple mass configuration (MMC) capability is not supported with auxiliary models.

22859.0 *** SYSTEM WARNING MESSAGE 22859 (MASSCMB)

%1 has a negative scale factor %2.
This can cause the mass matrix to become indefinite.

22860.0 *** USER FATAL MESSAGE 22860

Multiple mass configuration (MMC) capability is not supported with SOL %1.

22861.0 *** USER FATAL MESSAGE 22861

DIT (Direct Input Tables) bulk data entries such as TABLEij, TABDMP1 and GUST are not allowed in
"BEGIN BULK MASSID" for Multiple mass configuration (MMC) analysis in Sol 400.

22862.0 *** USER FATAL MESSAGE 22862

Multiple mass configuration (MMC) capability with more than one MASSSET is not supported with
Superelements and inertia relief in Sol 101.

22863.0 *** USER FATAL MESSAGE 22863

Both BSQUEAL and BRKSYS are defined in Bulk Data Section, mixed usage isn't supported.

User action: Please keep either BSQUEAL or BRKSYS for the definition of brake system

22863.1 *** USER FATAL MESSAGE 22863

BSQUEAL with ID %1, requested in Case Control Section, is not defined in Bulk Data Section.

Main Index
 1188 MSC Nastran Error Messages
Errors 22000 - 22999

22863.2 *** USER FATAL MESSAGE 22863

BRKSYS with ID %1, requested in Case Control Section, is not defined in Bulk Data Section.

22863.3 *** USER FATAL MESSAGE 22863

Brake system (either BSQUEAL or BRKSYS) with ID %1, requested in Case Control Section, is not
defined in Bulk Data Section.

22863.4 *** USER FATAL MESSAGE 22863

Both CMETHOD and METHOD are missing for BSQUEAL with ID %1 in Case Control Section.

User action: Please add both CMETHOD and METHOD for this BSQUEAL request.

22863.5 *** USER FATAL MESSAGE 22863

CMETHOD is missing for BSQUEAL with ID %1 in Case Control Section.

User action: Please add CMETHOD for this BSQUEAL request.

22863.6 *** USER FATAL MESSAGE 22863

METHOD is missing for BSQUEAL with ID %1 in Case Control Section.

User action: Please add METHOD for this BSQUEAL request.

22901.0 *** USER FATAL MESSAGE 22901

Some subcases specify either SOLUTION or ANALYSIS command and some do not.

User information: SOLUTION or ANALYSIS command must be specified in all or no subcases.

22902.0 *** USER WARNING MESSAGE 22902 (EXTDRSUM)

There are multiple subcases but only the data recovery requests in the first subcase will be honored.

22903.0 *** USER FATAL MESSAGE 22903 (IFPS)

If STATSUB is present, then EXTSEOUT or EXTMDOUT must be specified above all subcases.

22904.0 *** USER FATAL MESSAGE 22904 (EXTSEDR)

The attached solution data base, output2 file, or output4 file is not suitable for external superelement data
recovery in SOL 400.

User action: Use another solution sequence (SOLs 101-112) to obtain external superelement data recovery.

Main Index
 MSC Nastran Error Messages 1189
Errors 22000 - 22999

22904.1 *** USER FATAL MESSAGE 22904 (EXTdrsum)

The attached solution data base, output2 file or output4 file is not suitable for external superelement data
recovery in SOL 400.

User action: Ensure that the correct solution output2 file, output4 file, or database is being attached.
Otherwise contact MSC Client support.

Programmer information: No EXTDB data blocks, where SOLNID>0, were found.

22905.0 *** USER FATAL MESSAGE 22905 (EXTDRIN)

The attached solution data base, output2 file, or output4 file is not suitable for external superelement data
recovery in this solution sequence.

User action: Use solution sequence 400 to obtain external superelement data recovery.

22906.0 *** USER FATAL MESSAGE 22906 (PHASE0)

The Fortran unit=%1 specified on EXTDROUT(DMIGOP2 or MATOP4=unit) or PARAM,EXT-
DRUNT,unit is already assigned to a prior external superelement. Each external superelement must have its
own unit for external superelement data recovery.

User action: Specify separate subcases with SUPER command for each external superelement and include
EXTDROUT command or PARAM,EXTDRUNT with unique unit numbers.

22907.0 *** USER FATAL MESSAGE 22907 (EXTdrsum)

The attached boundary solutions %1 contains solutions for more than one external superelement and the
desired superelement ID has not been selected.

User action: Specify the superelement ID on the SUPER Case Control command to select the appropiate
boundary solution.

Main Index
 1190 MSC Nastran Error Messages
Errors 22000 - 22999

22907.1 *** USER FATAL MESSAGE 22907 (EXTdrsum)

The attached boundary solutions %1 contains solutions for more than one external superelement and the
desired superelement ID has not been selected.

User action: If the EXTDROUT Case Control command (or PARAM,EXTDROUT) specified
DMIGOP2 or MATOP4 then you must specify the superelement ID on the SUPER Case Control com-
mand to select the appropiate boundary solution.
If EXTDROUT Case Control command (or PARAM,EXTDROUT) specified MATRIXDB or
DMIGDB then you must specify the superelement ID
a. on the SUPER Case Control command to select the appropiate boundary solution.
or
b. in the WHERE(SEID=superelement_ID) clause on the DBLOCATE statement of the boundary
solutions database to select the appropiate boundary solution.

22908.0 *** USER FATAL MESSAGE 22908 (EXTdrsum)

The primary database indicates that the superelement was exported as superelement %1 but the boundary
solutions %2 contains solutions for superelement %3 only.

User action: Check ASSIGN statements for the primary database and the boundary solutions %2.

22909.0 *** USER WARNING MESSAGE 22909 (extotmin)

This external superelement was created prior to V2018 and the SPCForce OTMs were computed incor-
rectly. Therefore SPCFORCEs will not be computed.

Main Index
 MSC Nastran Error Messages 1191
Errors 22000 - 22999

22910.0 *** USER FATAL MESSAGE 22910 (extsedr and extdrin)

The database from the external superelement creation run is insufficient for third step external
superelement data recovery. It would appear that the external superelement was created with
EXTSEOUT(MATRIXDB or DMIGDB) without specifying a DBset for the external superelement's
boundary data.

User action: Ensure that the DBset name was specified for the DBEXT keyword was specified on the
EXTSEOUT command or in the creation run. Also the DBset must be initialized in the creation run on an
INIT FMS statement. For example, if DBEXT=SE10 then use the following setup in the creation run:
.....
$ File Management statements
INIT SE10
....
$ Executive Control statements
....
CEND
$ Case Control commands
EXTSEOUT(MATRIXDB=SE10,....)
.....

22910.1 *** USER FATAL MESSAGE 22910 (extsedr and extdrin)

The Case Control commands that define the loads and boundary conditions in the creation run are missing
or wrong in this restart. These commands are: LOAD, TEMPERATURE, SPC, MPC, SUPORT,
METHOD, DEFORM, MFLUID, K2GG, M2GG, B2GG and P2G

User action: Add or correct the above listed Case Control commands.

22910.2 *** USER FATAL MESSAGE 22910 (extsedr)

There are two possible situations:
1. The SOLUTION or ANALYSIS command selection is inconsistent with the Case Control
commands that define the loads and boundary conditions. These commands are: LOAD,
TEMPERATURE, SPC, MPC, SUPORT, METHOD, DEFORM, MFLUID, K2GG, M2GG,
B2GG and P2G.
2. The Case Control commands that define the loads and boundary conditions in the creation run are
missing or wrong in this restart. These commands are: LOAD, TEMPERATURE, SPC, MPC,
SUPORT, METHOD, DEFORM, MFLUID, K2GG, M2GG, B2GG and P2G
User action: Add or correct the above listed Case Control commands.

Main Index
 1192 MSC Nastran Error Messages
Errors 22000 - 22999

22911.0 *** USER FATAL MESSAGE 22911 (IFPS)

DBset %1 is not initialized by the INIT File Management statement.

User action: Add "INIT %1" statement to the File Management section.

22912.0 *** USER FATAL MESSAGE 22911 (PHASE0)

The EXTDROUT Case Control command and PARAM,EXTDROUT are not supported in this solution
sequence.

22913.0 *** USER WARNING MESSAGE 22913 (EXTDRSUM)

Both SOLUTION=%2 and ANALYSIS=%1 are present. The SOLUTION command takes precedence.

22914.0 *** USER WARNING MESSAGE 22914 (EXTDRSUM)

%1=%2 is not found in the table of solutions %3. Data recovery will be skipped for this analysis type.

22915.0 *** USER FATAL MESSAGE 22915 (extsedr)

The STEP command is detected in external superelement data recovery. This is not allowed.

User action: Use the SUBCASE command.

22916.0 *** USER FATAL MESSAGE 22916 (EXTDRIN)

The attached solution results are from a %1 analysis which is inconsistent with this solution sequence (or
analysis type): %2.

22951.0 *** USER WARNING MESSAGE 22951

Grid Point Force Balance output, OGPFB1, is missing.
It is required input for BENDL request. SHRFLOW terminated.

User information: MAKE SURE OGPFB1 is not deleted.

22952.0 *** USER FATAL MESSAGE 22952

Element ID %1 can not be located.

User information: MAKE SURE ELEMENT referenced exists.

22953.0 *** USER FATAL MESSAGE 22953

GPFORCE request is insufficient to cover BENDL output request

User information: MAKE SURE no GPFORCE overwrite occurs

Main Index
 MSC Nastran Error Messages 1193
Errors 22000 - 22999

22954.0 *** USER WARNING MESSAGE 22954

BENDL REQUEST DOES NOT HAVE ROD, BAR or BEAM ELEMENT. No BAR END LOAD gen-
erated.

User information: MAKE SURE SET FOR BENDL HAS IDs of ROD, BAR or BEAM.

22955.0 *** USER INFORMATION MESSAGE 22955

PARAM, WMODAL, YES has been detected with NON ZERO VALUES OF PARAM,W3 OR
PARAM,W4 for STRUCTURE or NON-ZERO values of PARAM,W3Fl or PARAM,W4FL for FLUID.
THIS MAY CAUSE OVERDAMPING OR UNEXPECTED DAMPING.

22956.0 *** USER FATAL MESSAGE 22956

HYDROC %1 WITH PSOLID %2 HAS HABOV %3 HIGHER THAN WETTED FACE %4.

User information: ADJUST HABOV SO IT IS WITHIN TOLERANCE OF %5.

22956.1 *** USER WARNING MESSAGE 22956

HYDROC %1 WITH PSOLID %2 HAS HABOV %3 LOWER THAN WETTED FACE %4.
SOME WETTED FACE ARE NOT LOADED.

User information: ADJUST HABOV SO IT IS WITHIN TOLERANCE OF %5.

22956.2 *** USER WARNING MESSAGE 22956

WITH PARAM,INREL,%1, GVAL ON HYDROC/HYDROS MUST BE EQUAL 1.0.

User information: SET GAVL TO 1.0 or SET OVRD to 1.

22956.3 *** USER WARNING MESSAGE 22956

REQUIRED INPUT DATA BLOCK WETFACE2 for HYDROC IS MISSING.

User information: CHANGE IDENT on ACMODL to DIFF if There is fluid model or SWITCH TO
HYDROS If no fluid model

Main Index
 1194 MSC Nastran Error Messages
Errors 22000 - 22999

22956.4 *** USER WARNING MESSAGE 22956

PSOLID %1 referenced on HYDROC %2 is missing or it is not PSOLID for cavity.
No PLOAD4 generated for this HYDROC.

User information: REVIEW INPUT DECK

22957.0 *** USER FATAL MESSAGE 22957

HYDROS %1 WITH %2 IN %4 FIELD MUST HAVE %3 IN DES FIELD OF SET3.

User action: CHECK SET3 ENTRIES and MAKE CHANGE ACCORDINGLY.

22957.1 *** USER WARNING MESSAGE 22957

SET1/3 %2 SPECIFIED ON %3 %4 FIELD OF HYDROS %1 IS MISSING.

User action: CHECK SET1 and/or SET3 ENTRIES

22957.2 *** USER FATAL MESSAGE 22957

GID %1 SPECIFIED ON SET OF HYDROS IS MISSING.

22957.3 *** USER FATAL MESSAGE 22957

SPHERICAL COORDINATE SYSTEM %1 IS NOT SUPPORTED for HYDROx.

22958.0 *** USER FATAL MESSAGE 22958

PSOLID %1 referenced on HYDROC %2 is missing.

User action: CHECK HYDROC and PSOLID entries in input deck.

22958.1 *** USER FATAL MESSAGE 22958

MAT10 %1 on PSOLID %2 referenced on HYDROC %3 is missing.

User action: CHECK MAT10, PSOLID and HYDROC entries in input deck.

22958.2 *** USER FATAL MESSAGE 22958

PSOLID AND MAT10 are required input to process HYDROC entries.

User action: CHECK MAT10, PSOLID and HYDROC entries in input deck.

Main Index
 MSC Nastran Error Messages 1195
Errors 22000 - 22999

22958.3 *** USER FATAL MESSAGE 22958

GID %1 ON HYDROx %2 not found.

User action: CHECK GRID and HYDROx entries in input deck.

22959.0 *** USER FATAL MESSAGE 22959

HYDROx BULK Entry IS NOT SUPPORTED.

22961.0 *** USER FATAL MESSAGE 22960 (GTTRNS_BASE)

The requested coordinate system with ID %1 could not be found.

User action: check entries of CORD1j and CORD2j in the input file.

22961.1 *** USER FATAL MESSAGE 22960 (ACEL1D)

Could not find the coordinate system with ID %1 since there is no CSTM datablock.

User action: check entries of CORD1j and CORD2j in the input file.

22961.2 *** SYSTEM FATAL MESSAGE 22960 (GTTRNS_BASE)

Illegal coordinate type %1 is obtained for CID=%2.

Programmer information: check code of calling GTTRNS.

22961.3 *** SYSTEM FATAL MESSAGE 22960 (GTTRNS_BASE)

Illegal coordinate id %1 is found.

Programmer information: check code of calling GTTRNS.

22962.0 *** USER FATAL MESSAGE 22960 (RSTCHKPV)

Param %1 has been defined in the restart version with a value of %2, but has a value of %3 in the current
input.

User action: remove the entry from the the input file or set MDLPRM,RSTIGNDP to 1 to ignore this
conflict.

Main Index
 1196 MSC Nastran Error Messages
Errors 22000 - 22999

22962.1 *** USER WARNING MESSAGE 22960 (RSTCHKPV)

Param %1 has been defined in the restart version with a value of %2, but has a value of %3 in the current
input.

22962.2 *** USER INFORMATION MESSAGE 22960 (RSTCHKPV)

Param %1 has been defined in the initial run and specified in this restart run again with the same value.

22963.0 *** SYSTEM FATAL MESSAGE 22963 (elem_mod)

Subroutine %1 in Fortran module elem_mod is call but elem_read is not, this is unexpected.

Programmer information: add a call to elem_read before call %1.

22964.0 *** USER INFORMATION MESSAGE 22964 (rmrgdrot_impl)

One or more RBE3 elements have been detected for which the dependent GRID connects to solid elements
only but dof 456 have been specified as part of REFC. In some cases, this may cause inefficient processing.
Up to 50 pairs of RBE3 and REFG with this occurring are listed below.

User action: If this is intentional, ignore this message, otherwise, you can set MDLPRM,RMRBE3RT,1 to
automatically remove dof 456 from the REFC on these RBE3s.

22964.1 *** USER INFORMATION MESSAGE 22964 (rmrgdrot_impl)

Based on MDLPRM,RMRBE3RT,1 the rotational dof (456) have been removed from REFC on RBE3
elements for which REFG connects to only solid elements. Up to 50 pairs of RBE3 and REFG for which
this has been done are listed below.

User action: If this is not your intent, remove MDLPRM,RMRNE3RT,1 or set it to 0.

22965.0 *** USER FATAL MESSAGE 22965 (marcmd_ard_matf)

FIND of CRI %1 in MATF ID=%2 is %3, a positive number is required.

22966.0 *** USER WARNING MESSAGE 22966

In nonlinear analysis, data recovery for BEAM, BAR, and BEND elements does not include the effect of
fixed-end moments due to loads applied using PLOAD1 entries and may result in incorrect element
moments and stresses.

22966.1 *** USER WARNING MESSAGE 22966

In nonlinear transient analysis with SOL 400, output request for GPSTRESS or GPSTRAIN is not
supported.

Main Index
 MSC Nastran Error Messages 1197
Errors 22000 - 22999

22967.0 *** USER WARNING MESSAGE 22967

FMS command exceeds 72 characters, characters after column 72 are ignored.

22968.0 *** user fatal message 22968 (subdmap ifplimp)

IFPSTAR=NO is not supported with %1 %2.

User action: Remove NASTRAN IFPSTAR=NO, NASTRAN SYSTEM(444)=0 or equivalent command

line argument.

22968.1 *** user fatal message 22968

RELDISP case control command does not have REFSET specified.
User action: RELDISP command must have a REFSET defined and the REFSET should point to a single
GRID point.

22968.2 *** user fatal message 22968

REFSET %1 in RELDISP case control command has more than one reference grid.

User action: Define only one grid in set definition of refset %1.

22968.3 *** user fatal message 22968

GRID %2 in REFSET %1 in RELDISP case control command is not present in the model.

User action: Define only one grid in set definition of refset %1 which is present in the model.

22968.4 *** user fatal message 22968

SPOINT %2 in REFSET %1 in RELDISP case control command is not allowed.

User action: Define only one grid in set definition of refset %1 which is present in the model.

22968.5 *** user fatal message 22968

EPOINT %2 in REFSET %1 in RELDISP case control command is not allowed.

User action: Define only one grid in set definition of refset %1 which is present in the model.

Main Index
 1198 MSC Nastran Error Messages
Errors 22000 - 22999

22968.6 *** user fatal message 22968

GRID %2 in REFSET %1 in RELDISP case control command does not belong to residual structure.

User action: Define only one grid in set definition of refset %1 which is in residual structure in the model.

22968.7 *** user fatal message 22968

REFSET %1 in RELDISP case control should be same for all the subcases.

User action: Use same refset %1 for all the subcases in the analysis.

22968.8 *** user fatal message 22968

REFSET %1 in RELDISP case control command must contain a strucutral grid point, not a fluid grid
point.

User action: Define only one strucutral grid in the main bulk data section in set definition of refset %1.

22981.1 *** USER INFORMATION MESSAGE 22981 (REVCOUP)

NUMBER OF SINGULAR MODES IN HBARX = %1

22981.2 *** USER INFORMATION MESSAGE 22981 (REVCOUP)

NUMBER OF SINGULAR MODES IN KHATX = %1

22982.0 *** USER FATAL MESSAGE 22982 (MODEFSRS)

THE CASE CONTROL METHOD(COUPLED) ENTRY WITH ID = %1 SELECTS AN IMPROPER
EIGR or EIGRL BULK DATA ENTRY.
COUPLED MODES CANNOT BE COMPUTED.

22983.0 *** USER INFORMATION MESSAGE 22983 (REVCOUP)

THE FOLLOWING EIGENVALUES ARE THE COUPLED MODES.

22984.0 *** USER INFORMATION MESSAGE 22984 (SEKDR)

NASTRAN/AVL INTERFACE SHAPES EXB EXPORT WITH PRE-LOAD COMPLETED.
EXIT REQUESTED.

22984.1 *** USER WARNING MESSAGE 22984 (PHASE1DR)

ADAMS/FLEX DOES NOT SUPPORT FLEXONLY=NO FOR COUPLED FLUID-STRUCTURE
ANALYSIS WITH METHOD(COUPLED).
FLEXONLY=NO IS CHANGED TO FLEXONLY=YES FOR THE REMAINDER OF THIS RUN.

Main Index
 MSC Nastran Error Messages 1199
Errors 22000 - 22999

22984.2 *** USER WARNING MESSAGE 22984 (PHASE1DR)

AVLEXB DOES NOT SUPPORT EXBONLY=NO FOR COUPLED FLUID-STRUCTURE ANALY-
SIS WITH METHOD(COUPLED).
EXBONLY=NO IS CHANGED TO EXBONLY=YES FOR THE REMAINDER OF THIS RUN.

22985.0 *** USER FATAL MESSAGE 22985 (PHASE0)

C-SET FREE BOUNDARY INTERFACE IS NOT SUPPORTED WITH CASE CONTROL COM-
MAND METHOD(COUPLED).

User action: WHEN CASE CONTROL COMMAND METHOD(COUPLED) IS USED,

USE ACCSSPT INSTEAD OF USING C-SET FOR THE PURPOSE OF THE MOTION TO BE
RETAINED IN THE RESIDUAL STRUCTURE OF THE ASSEMBLED SUPERELEMENT
MODEL.

22985.1 *** USER FATAL MESSAGE 22985 (PHASE1DR)

COUPLED FLUID-STRUCTURE ANALYSIS WITH METHOD(COUPLED) DOES NOT SUP-
PORT ACMS.

22986.0 *** USER FATAL MESSAGE 22986 (SBSPITR)

THE NUMBER OF RIGID BODY OR CONSTANT PRESSURE MODES IN THE MODEL IS
GREATER THAN NUMBER OF COUPLED MODES REQUESTED.
SUBSPACES ITERATION METHOD CANNOT SOLVE THIS PROBLEM.

User action: INCREASE THE NUMBER OF COUPLED MODES REQUESTED.

22986.1 *** USER FATAL MESSAGE 22986 (SBSTURM)

STURM COUNT FOR COUPLED MODES REPORTS NSTURM = %1 < 0.
RECOMMENDED THAT USER CHECK MODEL.

22988.0 *** USER INFORMATION MESSAGE 22988 (SBSPITR)

SUBSPACE ITERATION METHOD CONVERGED IN %1 ITERATION.

22989.0 *** USER INFORMATION MESSAGE 22989 (SBSPITR)

NUMBER OF MODES REQUESTED IS LARGER THAN PROBLEM SIZE.
ONLY %1 COUPLED MODES WILL BE COMPUTED.

Main Index
 1200 MSC Nastran Error Messages
Errors 22000 - 22999

22990.0 *** USER INFORMATION MESSAGE 22990 (REVCOUP)

NUMBER OF SINGULAR MODES IN THE STRUCTURE = %1

22990.1 *** USER INFORMATION MESSAGE 22990 (REVCOUP)

NUMBER OF SINGULAR MODES IN THE FLUID = %1

22991.0 *** USER FATAL MESSAGE 22991 (PRECOUP)

F2 ( > 0.0) VALUE MUST BE GREATER THAN F1( >= 0) VALUE IN EIGRL OR EIGR, ID = %1

22991.1 *** USER FATAL MESSAGE 22991 (AUTOJ)

%1 MASSLESS MECHANISM(S) ARE DETECTED.
MASSLESS MECHANISM(S) ARE NOT SUPPORTED WITH METHOD(COUPLED).

22992.0 *** USER WARNING MESSAGE 22992 (CMDAMP, PHASE1B)

CASE CONTROL COMMAND SDAMPING(STRUCTURE) or SDAMPING(FLUID) ARE NOT
SUPPORTED WITH METHOD(COUPLED).
SDAMPING(STRUCTURE) OR SDAMPING(FLUID) WILL BE IGNORED.
CASE CONTROL COMMAND SDAMPING(COUPLED) SHOULD BE USED WITH
METHOD(COUPLED).

22993.0 *** USER INFORMATION MESSAGE 22993 (SBPOWER)

DECOMPOSITION FAILED DURING ORTHONORMALIZATION STEP AT ITERATION
NUMBER %1.
NEW %2 COLUMN INITIAL VECTOR HAS BEEN SET UP FOR THE NEXT ITERATION.

22994.0 *** USER WARNING MESSAGE 22994 (MODEFSRS)

CASE CONTROL COMMAND METHOD(COUPLED) IS USED WITH METHOD(STRUC-
TURE) OR METHOD(FLUID).
METHOD(STRUCTURE) AND METHOD(FLUID) WILL BE USED FOR APPROXIMATION OF
REAL COUPLED MODES COMPUTATION.

22994.1 *** USER FATAL MESSAGE 22994 (MODEFSRS)

INPUT FILE HAS CASE CONTROL COMMAND METHOD(COUPLED), BUT THERE IS NO
FLUID-STRUCTURE INTERACTION.
USE METHOD(STRUCTURE) FOR A MODEL WHICH HAS NO FLUID.

22995.0 *** USER FATAL MESSAGE 22995 (IFPL)

CASE CONTROL COMMAND METHOD(COUPLED) IS NOT SUPPORTED WITH THE PEM
MODEL (TRIM COMPONENT).

Main Index
 MSC Nastran Error Messages 1201
Errors 22000 - 22999

22995.1 *** USER FATAL MESSAGE 22995 (IFPL)

CASE CONTROL COMMAND METHOD(COUPLED) IS NOT SUPPORTED WITH DMP > 1

22996.0 *** USER FATAL MESSAGE 22996 (IFPL)

PFMODE(STRUCTURE/FLUID) IS NOT SUPPORTED WITH CASE CONTROL COMMAND
METHOD(COUPLED).

22997.0 *** USER INFORMATION MESSAGE 22997 (REVCOUP)

SUBSPACE ITERATION METHOD WITH %1 FORMULATION WILL BE USED TO COMPUTE
REAL COUPLED MODES.

22998.0 *** USER INFORMATION MESSAGE 22998 (CMPCOUP)

THE FOLLOWING EIGENVALUES ARE COMPONENT COUPLED MODES.

22998.1 *** USER FATAL MESSAGE 22998 (SEMR3)

COMPONENT MODAL SYNTHESIS USING COUPLED MODES HAS BEEN REQUESTED
AND THERE ARE FLUID POINTS ON THE EXTERNAL SUPERELEMENT BOUNDARY,
WHICH IS NOT SUPPORTED.

22998.2 *** USER FATAL MESSAGE 22998 (CMPCOUP)

SINGULAR STRUCTUAL STIFFNESS MATRIX IS DETECTED.

Main Index
 1202 MSC Nastran Error Messages
Errors 22000 - 22999

Main Index
 MSC Nastran Error Messages 1203
Errors 23000 - 23999

Errors 23000 - 23999

23010.0 *** USER FATAL MESSAGE 23010 (AVLCHK)
Incorrect value of parameter "%1" entered on AVLEXB Case Control. Valid value for this parameter are
"%2".

23011.0 *** USER FATAL MESSAGE 23011 (AVLCHK)

AVLEXB Case Control "MFFEXP = YES" requires "RECOVERYM=YES EXBOSET=ALL".

23012.0 *** USER FATAL MESSAGE 23012 (AVLCHK)

AVL-EXCITE NOD6 BODY (BEAM/BAR model) requires that all the DOFs in the model be in t-set

23013.0 *** USER FATAL MESSAGE 23013 (IFPL)

Nastran/AVL interface cannot generate the EXB file and conduct data recovery in the same run.
AVLEXB Case Control "EXBBODY = YES" requires "AVLPOST = NO".

23014.0 *** USER FATAL MESSAGE 23014 (IFPL)

COUPLED MASS FORMULATION HAS BEEN REQUESTED WITH THE NASTRAN/AVL
INTERFACE.

23015.0 *** USER FATAL MESSAGE 23015 (IFPL)

Nastran/AVL interface data recovery has been selected but the INP4 file unit = %1 does not exist.

23016.0 *** USER INFORMATION MESSAGE 23016 (IFPL)

Nastran/AVL Interface EXB File Generation Selected by the user.

23016.1 *** USER INFORMATION MESSAGE 23016 (IFPL)

Nastran/AVL interface data recovery has been selected, INP4 file unit = %1.

23017.0 *** USER INFORMATION MESSAGE 23016 (AVLFLEX)

Nastran/AVL Interface: User has selected non-default value of V1ORTHO or V2ORTHO on the
AVLEXB Case Control, hence, LANCZOS Method instead of the default HOUSEHOLDER Method will
be used for a-set orthonormalization.

Main Index
 1204 MSC Nastran Error Messages
Errors 23000 - 23999

23018.0 *** SYSTEM FATAL MESSAGE 23018 (AVLEXOT)

Nastran/AVL interface: INSUFFICIENT MEMORY SPACE AVAILABLE TO STORE %1 DURING
THE EXPORT OF EXB FILE.

User action: INCREASE MEMORY

23019.0 *** SYSTEM FATAL MESSAGE 23014 (AVLINIT)

Nastran/AVL interface: Could not get EXB File Name.

23019.1 *** SYSTEM FATAL MESSAGE 23014 (AVLINIT)

Nastran/AVL interface: Failed to read BGPDT table.

23019.2 *** SYSTEM FATAL MESSAGE 23014 (AVLINIT)

Nastran/AVL interface: Failed to read USET table.

23020.0 *** SYSTEM FATAL MESSAGE 23020 (AVLINIT)

Nastran/AVL interface: Number of %1 calculated by Nastran/AVL interface does not match the number of
number of %1 provided to the interface.

23021.0 *** USER FATAL MESSAGE 23021 (AVLINIT)

Nastran/AVL interface: Error while processing T-set DOF Table. Only physical grids can belong to t-sets,
i.e. can be attachment points.

23022.0 *** USER INFORMATION MESSAGE 23021 (AVLEXOT)

Nastran/AVL interface: Calculating Higher Order Mass Invarients. All the columns of Component Modes
Matrix loaded into Memory.

23022.1 *** USER WARNING MESSAGE 23021 (AVLEXOT)

Nastran/AVL interface: Calculating Higher Order Mass Invarients. Could not fit all the columns of Com-
ponent Modes Matrix into Memory.
Total number of Columns of Component Modes Matrix = %1
Number of Columns of Component Modes Matrix that fit into Memory = %2
If the Number of Columns of Component Modes Matrix that fit into Memory is small it can increase the
time taken to calculate the Higher Order Mass Invarients.

User action: Increase memory if Number of Columns of Component Modes Matrix that does not fit into
memory.

Main Index
 MSC Nastran Error Messages 1205
Errors 23000 - 23999

23023.0 *** USER FATAL MESSAGE 23023 (SSHAPE)

Nastran/AVL Interface User has requested Grid Point Stress/Strain output without setting
"PARAM,POST" = -1 or 1.

User action: Change "PARAM,POST" to -1 or 1.

23024.0 *** USER INFORMATION MESSAGE 23024 (SSHAPE)

Nastran/AVL Interface Grid Point Stress/Strain Shape output Requested.

23025.0 *** USER FATAL MESSAGE 23025 (AVLFLEX)

Nastran/AVL Interface. No Eigenvalues Found during Orthonormalization - EXITING.

User information:
1. This may be caused due to incorrect modeling.
2. Another possible cause is incorrect values chosen for V1ORTHO and V2ORTHO.

23026.0 *** USER INFORMATION MESSAGE 23026 (AVLFLEX)

Nastran/AVL interface dmap information message:
During a-set orthonormalization a total of %1 modes were found out of a possible %2.
Eigenvalues from a-set orthonormalization are:

23026.1 *** USER INFORMATION MESSAGE 23026 (AVLFLEX)

Nastran/AVL interface DMAP information message:
READ module is being used for a-set orthonormalization.

23027.0 *** USER FATAL MESSAGE 23027 (SEMFREQ)

Nastran/AVL Data Recovery. Number of a-set DOF %1 in Data Recovery do not match the number of a-
set DOF %2 while generating the EXB file (Step-1 of Nastran/AVL Interface).

23028.0 *** USER FATAL MESSAGE 23028 (DISPRS)

Nastran/AVL Data Recovery. Number of frequency steps %1 in Data Recovery (Step-2 of Nastran/AVL
Interface) do not match the number of frequency %2 steps in the INP4 file unit %3.

Main Index
 1206 MSC Nastran Error Messages
Errors 23000 - 23999

23028.1 *** USER FATAL MESSAGE 23028 (DISPRS)

Nastran/AVL Data Recovery. Three times the number of time steps %1 = %2 in Data Recovery
(which represent displacement, velocity, and acceleration for each output time step) do not match the num-
ber of column %3 in the INP4 file unit %4.

23029.0 *** USER FATAL MESSAGE 23029 (DISPRS)

Nastran/AVL Data Recovery. Number of a-set DOFs in model %1
differs from the number of a-set DOFs %2 in the INP4 file unit %3.

23030.0 *** SYSTEM FATAL MESSAGE 23030 (AVLEXOT)

Nastran/AVL interface: Error while writing EXB File, could not write %1.

23030.1 *** SYSTEM FATAL MESSAGE 23030 (AVLEXOT)

Nastran/AVL interface: Error while writing EXB File. Could not write Mass Matrix for AVL-EXCITE
NOD6 BODY.

User action: Please make sure the Mass Matrix of NOD6 BODY is constructed using CONM2 (CONM1)
elements which would result in the correct format of Mass Matrix.

23030.2 *** SYSTEM FATAL MESSAGE 23030 (AVLEXOT)

Nastran/AVL interface: Error while writing EXB File.

23031.0 *** USER INFORMATION MESSAGE 23031 (AVLFLEX)

NASTRAN/AVL INTERFACE DMAP INFORMATION MESSAGE:
CALLING AVL EXB MODULE

23031.1 *** USER INFORMATION MESSAGE 23031 (AVLFLEX)

NASTRAN/AVL INTERFACE DMAP INFORMATION MESSAGE:
EXB Export Completed: Exit Requested

23032.0 *** USER WARNING MESSAGE 23032 (AVLFLEX)

NASTRAN/AVL INTERFACE DMAP INFORMATION MESSAGE:
MASS MATRIX HAS %1 NULL COLUMNS AHOU METHOD REPLACED BY %2 METHOD
RECOMMENDED THAT USER CHECK MODEL

Main Index
 MSC Nastran Error Messages 1207
Errors 23000 - 23999

23033.0 *** USER INFORMATION MESSAGE 23033 (AVLFLEX)

NASTRAN/AVL INTERFACE DMAP INFORMATION MESSAGE:
NO DEFORMED GEOMETRY AVAILABLE.

23034.0 *** USER FATAL MESSAGE 23034 (AVLFLEX)

NASTRAN/AVL INTERFACE DMAP FATAL MESSAGE:
NO ASET/QSET/SPOINT AVAILABLE for EXB File export.

User action: ADD ASET, QSET and SPOINT

23035.0 *** USER FATAL MESSAGE 23034 (NONLIN)

Nastran/AVL Interface linear Sol 400 run is not supported with nonlinear rigid elements, i.e.,
RIGID=LAGRAN (default in SOL 400)

User action: Run with Case Control command RIGID=LINEAR

23036.0 *** USER WARNING MESSAGE 23036 (SEMFREQ)

Nastran/AVL Interface does not support the use of MODESELECT case control command.
MODESELECT will be ignored in this frequency response analysis.

23036.1 *** USER WARNING MESSAGE 23036 (SEMTRAN)

Nastran/AVL Interface does not support the use of MODESELECT case control command.
MODESELECT will be ignored in this transient response analysis.

23101.0 *** SYSTEM WARNING MESSAGE 23101 (OCMP2OES)

The conversion from enhanced composite stresses and strains to conventional layer shell format for element
type %1 is not implemented, skipped.

23101.1 *** USE INFORMATION MESSAGE 23101 (OCMP2OES)

Enhanced composite stresses and strains use conventional shell layer format.
To turn this off, set MDLPRM,COMPN1,NO.

23101.2 *** USE FATAL MESSAGE 23101

Invalid value %1 is specified to MDLPRM,COMPN1, only YES or NO is allowed.

23101.3 *** USE INFORMATION MESSAGE 23101

Main Index
 1208 MSC Nastran Error Messages
Errors 23000 - 23999

Enhanced composite stress and strain output has been requested by setting COMPN1 to YES on the
MDLPRM entry.
In order to honor this request, VCOORD of NLMOPTS is being set to BOTT and CPROJ is set to ON.
If this is not the desired action, set MDLPRM,COMPN1,NO.
23101.4 *** USE INFORMATION MESSAGE 23101
Enhanced composite stress and strain output has been requested by setting COMPN1 to YES on the
MDLPRM entry.
In order to honor this request, CPROJ of NLMOPTS is being set to ON.
If this is not the desired action, set MDLPRM,COMPN1,NO.

23201.0 *** USER FATAL MESSAGE 23201

%1 is only supported in SOL700, version=original, which is no longer supported.

23201.1 *** USER FATAL MESSAGE 23201

The %1 is only supported in the new Nastran SOL700 solution sequence.

User action: To use the new SOL700, please specify version=primary or remove version=original on the
SOL700 entry of EXECUTIVE CONTROL SECTION.
For example, SOL 700,129 version=primary or SOL 700,129.

23201.2 *** USER FATAL MESSAGE 23201

The %1 entry is disallowed in the SOL700 solution sequence. Please check the input.

23202.0 *** USER FATAL MESSAGE 23202

The %1 entry must define one of the %3 field or the %4 field.
Only one of the %3 or the %4 must be defined.

User action: Remove %3 or %4 field.

23202.1 *** USER FATAL MESSAGE 23202

The %1 entry must define one of the %3 field or the %4 field.
Only one of the %3 or the %4 must be defined.

User action: Add one of %3 or %4 field.

23202.2 *** USER FATAL MESSAGE 23202

Main Index
 MSC Nastran Error Messages 1209
Errors 23000 - 23999

The %1 field must be defined in the %2 entry. Please check input.

User action: Add the %1 field.

23202.3 *** USER FATAL MESSAGE 23202
%1 or %3 are only allowed in the %4 field of the %5 entry. Please check input.

User action: Put %1 or %3 in the %4 field.

23202.4 *** USER FATAL MESSAGE 23202
The %1 entry supports one of the %3 field or the %4 field.

23203.0 *** USER FATAL MESSAGE 23203

Only %2 lines are available in the %1 entry. Please check the input.

23204.0 *** USER FATAL MESSAGE 23204

The %1 field in the %2 entry must be an integer. Please check the input.

User action: Change the %1 field in integer format.

23204.1 *** USER FATAL MESSAGE 23204

The %1 field in the %2 entry must be less than or equal to 1000.
Please check the input.

User action: Change the %1 field less than or equal to 1000.

23205.0 *** USER FATAL MESSAGE 23205

PARAM AUTOMSET IS UNABLE TO FIND VALID M-SET AUTOMATICALLY FOR THE
MODEL.

User action: PLEASE REMOVE AUTOMSET PARAMETER AND DEFINE CONSTRAINT ELE-
MENTS AND MPC ENTRIES AS NECESSARY.

23051.0 *** USER INFORMATION MESSAGE 23051

REDUCING GRAV LOAD VECTOR DUE TO PARAM,GRAVSET.

23051.1 *** USER INFORMATION MESSAGE 23051

REDUCING RFORCE LOAD VECTOR DUE TO PARAM,RFORSET.

Main Index
 1210 MSC Nastran Error Messages
Errors 23000 - 23999

23051.2 *** USER INFORMATION MESSAGE 23051

OLOAD RESULTANT AFTER GRAV AND RFORCE REDUCTION

23052.0 *** SYSTEM FATAL MESSAGE 23052

LOGIC ERROR IN EDT TABLE. TRAILER INDICATES PANELS EXIST, BUT NONE FOUND

23052.1 *** USER FATAL MESSAGE 23052

NO SET1 ENTRIES FOUND FOR EITHER RFORSET OR GRAVSET

23052.2 *** USER FATAL MESSAGE 23052

NO SET1 ENTRIES FOUND FOR PARAM,EXCLUDE.

23181.0 *** USER FATAL MESSAGE 23181 (TA0TMP)

ONLY ONE SUBCASE IS ALLOWED WHEN FREQUENCY IS A FUNCTION OF TEMPERA-
TURE.

23182.0 *** USER FATAL MESSAGE 23182 (TA0TMP)

TEMP(LOAD), TEMP(INIT) OR TEMP(MATE) MUST BE SPECIFIED WHEN FREQUENCY IS A
FUNCTION OF TEMPERATURE.

23183.0 *** USER FATAL MESSAGE 23183 (TA0TMP)

PDISTB OR PDISTBM ENTRIES ARE NOT ALLOWED WHEN FREQUENCY IS A FUNCTION
OF TEMPERATURE.

User information: PDISTB/PDISTBM ENTRY CONFLICTS WITH THE SPATIAL VARYING OF

TEMPERATURE DEPENDENT FREQUENCY.

23184.0 *** USER FATAL MESSAGE 23184 (TA0WMFT)

MATi ENTRY ID =%1 HAS ASSOCIATED WITH AN MATTi ENTRY AND AN MATiF ENTRY
THAT REFERS TO ANY TABLED5 ENTRY.

User information: TEMPERATURE DEPENDENT MATERIAL PROPERTY SPECIFIED ON

MATTi ENTRY CONFLICTS WITH TEMPERATURE DEPENDENT FREQUENCY SPECIFIED
WITH MATiF AND ASSOCIATED TABLED5 ENTRIES.

23185.0 *** USER FATAL MESSAGE 23185 (IFPEXTRA)

Main Index
 MSC Nastran Error Messages 1211
Errors 23000 - 23999

RBAR ID=%1 violates a rule, the total number of components of CNA and CNB must be 6 for
RIGID=LINEAR method, but it is %2.

23185.1 *** USER FATAL MESSAGE 23185 (IFPEXTRA)

RBAR ID=%1 violates a rule, one of CNA and CNB must be 123456 and another must be 0 for
RIGID=LAGRANGE method, but they are %2 and %3 respectively.

23185.3 *** USER FATAL MESSAGE 23185 (IFPEXTRA)

MATORT ID=%1 used for PSOLID ID=%2 is only supported in SOL 400.
23185.4 *** USER FATAL MESSAGE 23185 (IFPEXTRA)
More than 50 errors have occured due to usage of advance material in PSOLID cards.

23510.0 *** USER FATAL MESSAGE 23510

IMPERFECT=%1 is defined in case control but no ASSIGN FMS for imperfection input is defined.

User action: Add ASSIGN INPUTT2, HDF5IN or IMPFIN to assign input files for geometric
imperfection

23510.1 *** USER FATAL MESSAGE 23510

No IMPGEOM entry matching identification numbers specified in IMPCASE ID=%1.

23510.2 *** USER FATAL MESSAGE 23510

IMPERFECT=%1 is defined in case control but no IMPGEOM ID=%1 nor IMPCASE=%1 is found in
the bulk data section.

23510.3 *** USER FATAL MESSAGE 23510

UNIT=%1 is referred by IMPGEOM ID=%2 but not found in ASSIGN INPUTT2, HDF5IN nor
IMPFIN.

23510.4 *** USER FATAL MESSAGE 23510

UNIT and UNITi in continuation %1 of IMPGEOM ID=%2 are zero or not specified, a positive number
is required.

23510.5 *** USER FATAL MESSAGE 23510

Main Index
 1212 MSC Nastran Error Messages
Errors 23000 - 23999

SUBCASEi in continuation %1 of IMPGEOM ID=%2 is zero or not specified, a positive number is

required.

23510.6 *** USER WARNING MESSAGE 23510

Undefined IMPGEOM ID=%1 referenced by IMPCASE ID=%2 ignored. Any other undefined IMP-
GEOM entries also ignored.

23510.7 *** USER FATAL MESSAGE 23510

UNIT in IMPGEOM ID=%1 is zero or not specified, and there is no continuation in this entry.

23510.8 *** USER FATAL MESSAGE 23510

The file specified in UNIT=%1 of IMPGEOM ID=%2 is an %3 file but there is no continuation.

23511.0
Unable to find datablock OUG1 or OUGV1 on file unit %1.

23511.1 *** USER FATAL MESSAGE 23511

IMPERFECT is supported by SOL 400 only.

23512.0 *** USER FATAL MESSAGE 23512

No SET1 or SET3 with ID %1 is found, which is referenced by IMPGEOM %2.

23512.1 *** USER FATAL MESSAGE 23512

Found both SET1 and SET3 entries with the same ID %1, which is referenced by IMPGEOM %2.

User action: Remove one of them.

23512.2 *** USER FATAL MESSAGE 23512

SET3 ID=%1 referenced by IMPGEOM ID=%2 is found, but it is not a GRID type.

User action: The SET3 referenced by an IMPGEOM must be type GRID.

23512.3 *** USER FATAL MESSAGE 23512

No grid point is found in the IDs of %1 ID=%2, which is referenced by IMPGEOM ID=%3.

23512.4 *** USER FATAL MESSAGE 23512

File unit %1 is referenced in IMPGEOM %2, but not found.

Main Index
 MSC Nastran Error Messages 1213
Errors 23000 - 23999

23512.5 *** USER FATAL MESSAGE 23512

Results data not found for imperfection in file %1 (unit=%2) with SUBCASEi=%3, STEPi=%4,
MODEINCi=%5.

User action: Check SUBCASEi, STEPi or MODEINCi in continuation line %6 of IMPGEOM ID=%7.

23512.6 *** USER FATAL MESSAGE 23512

Illegal mode number 0 or empty is specified in continuation line %1 of IMPGEOM ID=%2, a positive
number is required.

User information: The line indicates a mode or buckling analysis result in %3 in file %4 (unit=%5).

23512.7 *** USER WARNING MESSAGE 23512

There is no step information in subcase %1 for the selected result in file %2 (unit=%3),
STEPi=%4 specified in continuation line %5 of IMPGEOM ID=%6 is ignored.

23512.8 *** USER WARNING MESSAGE 23512

Found illegal analysis type in result data for imperfection in the line with SUBCASEi=%3,
STEPi=%4, MODEINCi=%5 in file %1 (unit=%2).

User action and information: Check continuation line %6 of IMPGEOM ID=%7.

Allowable analysis types are mode, buckling, linear static, nonlinear static and nonlinear transient.

Programmer information: acode is %8, should be 2,6,8 or 10.

23512.9 *** USER WARNING MESSAGE 23512

Subcase ID %1 not found in imperfection file %2 (unit=%3).

User action: Check continuation line %4 of IMPGEOM ID=%5 or above file.

23512.10 *** USER WARNING MESSAGE 23512

Main Index
 1214 MSC Nastran Error Messages
Errors 23000 - 23999

Step ID %1 not found in subcase %2 in imperfection file %3 (unit=%4).

User action: Check continuation line %5 of IMPGEOM ID=%6 or above file.

23512.11 *** USER WARNING MESSAGE 23512

%1 %2 not found in step %3 of subcase %4 in imperfection file %5 (unit=%6).

User action: Check continuation line %7 of IMPGEOM ID=%8 or above file.

23512.12 *** USER WARNING MESSAGE 23512

The imperfection file %1 (unit=%2) is used by IMPGEOM ID=%3, the IMPGEOM entry has multiple
continuations.

User information: Only one continuation is allowed.

23512.13 *** SYSTEM FATAL MESSAGE 23512

Read illegal number of words %1 for ident record of input datablock %2.

23512.14
The input datablock %1 doesn't exist.

23513.0 *** SYSTEM FATAL MESSAGE 23513

No record of %1 is found in %2 datablock.

23513.1 *** USER FATAL MESSAGE 23510

SETID or SETIDi=%1 is specified in continuation line %2 of IMPGEOM ID=%3 but MODID or
MODIDi is not specified or -1.

User action: specify a zero or a positive number for MODIDi or MODID field, or remove SETID or
SETIDi field.

23513.2 *** USER FATAL MESSAGE 23510

Main Index
 MSC Nastran Error Messages 1215
Errors 23000 - 23999

MODID or MODIDi=%1 is specified in IMPGEOM %2, which is illegal for the imperfection file unit
%3.

User information: MODID or MODIDi cannot be specified when an IMPF file is used.

23513.3 *** USER FATAL MESSAGE 23510

The same value %1 of MODIDi is specicifed in continuation lines %2 and %3 of IMPGEOM ID=%4,
this is illegal when modules are present and an IMPF file is used as an imperfection file.

User action: Remove one of the continuation lines or change one of the MODIDi's to a different non-neg-
ative number.

23513.4 *** USER FATAL MESSAGE 23510

MODIDi fields in continuation lines %2 and %3 of IMPGEOM ID=%4 are not specified or -1, this is
illegal when modules are present and an IMPF file is used as an imperfection file.

User action: Remove one of the continuation lines or change one of the MODIDi's to a different
non-negative number.

23514.0 *** SYSTEM FATAL MESSAGE 23514

No file found for unit %1.

23514.1 *** SYSTEM FATAL MESSAGE 23514

Failed to open file %1.

23514.2 *** USER FATAL MESSAGE 23514

%1 near line %2 in file %3 must be a valid real number floating point format (contains a decimal point
and/or exponent) and is not.

23514.3 *** USER FATAL MESSAGE 23514

%1 near line %2 in file %3 should be an integer and is not.

Main Index
 1216 MSC Nastran Error Messages
Errors 23000 - 23999

23514.4 *** USER WARNING MESSAGE 23514

%1 is a complex form of displacement datablock, the datablock of summation of imperfection vector and
displacement is not created, a real form of displacement datablock is required.

23514.5 *** USER WARNING MESSAGE 23514

%1 is a sort2 form of displacement datablock, the datablock of summation of imperfection vector and dis-
placement is not created, sort1 is required.

23514.6 *** USER FATAL MESSAGE 23514

"BEGIN" found at line %1 of file %2(unit=%3), but it doesn't follow the pattern of "BEGIN MODULE
".

23514.7 *** USER FATAL MESSAGE 23514

"END" found at line %1 of file %2(unit=%3), but it is not "END MODULE" nor "ENDMODULE".

23515.0 *** USER FATAL MESSAGE 23515

Not found displacement or eigenvector data in file %1(unit=%2).

23515.1 *** USER INFORMATION MESSAGE 23515

Read data of %1 domains from dataset %2 in file %3(unit=%4).

23515.2 *** USER FATAL MESSAGE 23515

Couldn't get file name with UNIT=%1 for HDF5IN.

User action: check ASSIGN HDF5IN FMS command.

23516.0 *** SYSTEM FATAL MESSAGE 23516

Unable to set imperfection id since %1 is called from unexpected %2.

23517.0 *** SYSTEM FATAL MESSAGGE

The number of imperfection input files encountered exceeds the limit of %1.

User action: check UNITi field of IMPGEOM entries.

23517.1 *** SYSTEM FATAL MESSAGGE

IMPFMAP record not found in GEOM1 datablock, which is required for imperfection analysis.

Main Index
 MSC Nastran Error Messages 1217
Errors 23000 - 23999

23517.2 *** SYSTEM FATAL MESSAGGE

Name %1 is not an ofp datablock name.

Programmer information: the argument cdbname of subroutine %2 should be a name of ofp datablock.

23517.3 *** SYSTEM FATAL MESSAGGE

Unexpected status value %1 in readrt when reading IMPMAP.

23517.4 *** USER FATAL MESSAGGE

%1 in continuation %2 of IMPGEOM ID=%3 is zero or not specified, a positive number is required.

23551.0 *** USER FATAL MESSAGGE

Current rotor speed (%1) is not in the range, %2 to %3, specified on an LBSH3DG entry

23552.0 *** USER FATAL MESSAGGE

NLBSH3D references P-set dof,%1,which is not in the D-set.

User information: Any dof referenced on an NLBSH3D must exist in the D-set

23552.1 *** USER FATAL MESSAGGE

NLBSH3D references GRID,%1, dof %2 which is not in the D-set.

User information: Any dof referenced on an NLBSH3D must exist in the D-set

23552.2 *** USER FATAL MESSAGGE

EPOINT %1, referenced in nonlinear force entities (NLRGAP, NOLINi, NLRSFD), is not in the D-set.

User information: Any EPOINT must exist in the D-set. Contact HEXAGON/MSC client support.

Main Index
 1218 MSC Nastran Error Messages
Errors 23000 - 23999

Main Index
 MSC Nastran Error Messages 1219
Errors 25000 - 25999

Errors 25000 - 25999

25001.0
YOUNGS MODULUS OF MAT1 ID %1 IS NOT POSITIVE

25002.0
YOUNGS MODULUS OF MAT1 ID %1 IS NOT POSITIVE - BUT TABLE ID IS GIVEN

25003.0
YOUNGS MODULUS OF MAT1 ID %1 IS NOT POSITIVE
ANALYSIS WILL STOP IN CASE OF STRUCTURAL MATERIAL

25004.0
POISSONS RATIO OF MAT1 ID %1 IS LESS THAN ZERO OR GREATER THAN 0.5

25005.0
POISSONS RATIO OF MAT1 ID %1 IS LESS THAN ZERO OR GREATER THAN 0.5 - BUT
TABLE ID IS GIVEN

25006.0
DENSITY OF MAT1 ID %1 IS NEGATIVE

25007.0
DENSITY OF MAT1 ID %1 IS NEGATIVE - BUT TABLE ID IS GIVEN

25008.0
THERMAL CONDUCTIVITY OF MAT4 ID %1 IS NOT POSITIVE

25009.0
THERMAL CONDUCTIVITY OF MAT4 ID %1 IS NOT POSITIVE - BUT TABLE ID IS GIVEN

25010.0
SPECIFIC HEAT OF MAT4 ID %1 IS NEGATIVE
25011.0
SPECIFIC HEAT OF MAT4 ID %1 IS NEGATIVE - BUT TABLE ID IS GIVEN

Main Index
 1220 MSC Nastran Error Messages
Errors 25000 - 25999

25012.0
HEAT TRANSFER DENSITY OF MAT4 ID %1 IS NEGATIVE

25013.0
HEAT TRANSFER DENSITY OF MAT4 ID %1 IS NEGATIVE - BUT TABLE ID IS GIVEN

25014.0
REFERENCE ENTHALPY OF MAT4 ID %1 IS NEGATIVE

25015.0
KZZ OF MAT5 ID %1 IS NOT POSITIVE WHILE 3D ANALYSIS IS REQUESTED USING
NLMOPTS,TEMPP ENTRY

25016.0
KZZ OF MAT5 ID %1 IS NOT POSITIVE WHILE 3D ANALYSIS IS REQUESTED USING
NLMOPTS,TEMPP ENTRY - BUT TABLE ID IS GIVEN

25017.0
SPECIFIC HEAT OF MAT5 ID %1 IS NEGATIVE

25018.0
SPECIFIC HEAT OF MAT5 ID %1 IS NEGATIVE - BUT TABLE ID IS GIVEN

25019.0
HEAT TRANSFER DENSITY OF MAT5 ID %1 IS NEGATIVE

25020.0
HEAT TRANSFER DENSITY OF MAT5 ID %1 IS NEGATIVE - BUT TABLE ID IS GIVEN

25021.0
MATDIGI ID %1 IS NOT DEFINED

25022.0
PREVIOUSLY ENTERED DATA FOR MATDIGI ID %1 HAS BEEN OVERWRITTEN

25023.0
MATEP ID %1 REFERENCES AN UNDEFINED MATERIAL IDENTIFICATION NUMBER

Main Index
 MSC Nastran Error Messages 1221
Errors 25000 - 25999

25024.0
CHABOCHE HARDENING MODEL IS USED FOR MATEP ID %1 BUT THE YIELD MODEL IS
NOT VON MISES

25025.0
CONVERTING SLOPE OPTION OF MATEP ID %1 INTO TABLES1 WITH FID %2

25026.0
STRESS-STRAIN DATA OF MATEP ID %1 DEFINED BY TYPE 1 TABLES1 ID %2 IS NOT AT
ORIGIN

25027.0
YOUNGS MODULUS OF MATEP ID %1 IS NOT DEFINED

25028.0
SLOPE OF FIRST LINE OF STRESS-STRAIN DATA OF MATEP ID %1 DEFINED BY TABLES1
ID %2 IS NOT EQUAL TO THE ELASTIC MODULUS (E)

25029.0
C OF MATEP ID %1 MUST BE NON-ZERO

25030.0
P OF MATEP ID %1 MUST BE NON-ZERO

25031.0
CHABOCHE HARDENING MODEL IS USED FOR MATEP ID %1 BUT ISOTROPIC SOFTEN-
ING CANNOT BE COMBINED WITH STRAIN MEMORIZATION

25032.0
BUYUKOZTURK CONCRETE MODEL OF MATEP ID %1 IS NOT SUPPORTED IN SOL400

25033.0
MELT TEMPERATURE OF MATEP ID %1 MUST BE GREATER THAN ROOM TEMPERATURE
25034.0
MATERIAL MODEL OF MATEP ID %1 IS NOT SUPPORTED IN SOL400

Main Index
 1222 MSC Nastran Error Messages
Errors 25000 - 25999

25035.0
TABLE T(FID) %1 OF MATTEP ID %2 WILL REPLACE TABLE FID %3 OF MATEP ID %4

25036.0
TABLE T(Y0) %1 OF MATTEP ID %2 CONFLICTS WITH TABLE FID %3 OF MATEP ID %4
EITHER LEAVE MATEP ENTRY BLANK AND USE TABLEST FOR T(FID) IN MATTEP
OR LEAVE MATTEP ENTRY BLANK AND USE TABL3D1 FOR FID in MATEP

25037.0
TABLE T(yc10) %1 OF MATTEP ID %2 CONFLICTS WITH TABLE TID %3 OF MATEP ID %4

25038.0
MATF ID %1 REFERENCES AN UNDEFINED MATERIAL IDENTIFICATION NUMBER

25039.0
MATF ID %1 REFERENCES MORE THAN %2 FAILURE CRITERIA

25040.0
PROGRESSIVE FAILURE OPTION %1 REFERENCED BY MATF ID %2 IS NOT AVAILABLE

25041.0
MATF ID %1 REFERENCES AN UNRECOGNIZABLE FAILURE CRITERION

25042.0
MATF ID %1 REFERENCES CHAMIS FAILURE CRITERION WHICH IS NOT AVAILABLE

25043.0
MAXIMUM X TENSILE STRESS OF MATF ID %1 MUST BE NON-ZERO

25044.0
MAXIMUM Y TENSILE STRESS OF MATF ID %1 MUST BE NON-ZERO

25045.0
MAXIMUM SHEAR STRESS OF MATF ID %1 MUST BE NON-ZERO

25046.0

Main Index
 MSC Nastran Error Messages 1223
Errors 25000 - 25999

MAXIMUM Z TENSILE STRESS OF MATF ID %1 MUST BE NON-ZERO

25047.0
MAXIMUM X TENSILE STRAIN OF MATF ID %1 MUST BE NON-ZERO

25048.0
MAXIMUM Y TENSILE STRAIN OF MATF ID %1 MUST BE NON-ZERO

25049.0
MAXIMUM Z TENSILE STRAIN OF MATF ID %1 MUST BE NON-ZERO

25050.0
MAXIMUM SHEAR STRAIN OF MATF ID %1 MUST BE NON-ZERO

25051.0
RESIDUAL STIFFNESS FRACTION OF MATF ID %1 MUST BE LARGER THAN ZERO

25052.0
Fxy (V10) OF MATF ID %1 MUST BE NON-ZERO

25053.0
Fyz (V11) OF MATF ID %1 MUST BE NON-ZERO

25054.0
Fxz (V12) OF MATF ID %1 MUST BE NON-ZERO

25055.0
TSAI-WU STABILITY CHECK FOR MATF ID %1 FAILS CHECK FAILURE DATA

25056.0
AT LEAST ONE SLOPE OF FAILURE ENVELOPE FOR MATF ID %1 MUST BE NON-ZERO

25057.0
MAXIMUM IN-PLANE SHEAR STRESS IS EQUAL TO ZERO FOR MATF ID %1
PARAMETER p12c IS SET TO %2
25058.0

Main Index
 1224 MSC Nastran Error Messages
Errors 25000 - 25999

MAXIMUM MATRIX COMPRESSIVE STRESS IS EQUAL TO ZERO FOR MATF ID %1

PARAMETER p12c IS SET TO %2
25059.0
NUMBER OF FAILURE INDICES FOR MATF ID %1 IS %2
ONLY THE FIRST 17 CAN BE POST-PROCESSED

25060.0
MATG ID %1 IS NOT DEFINED

25061.0
MATG ID %1 REFERENCES AN UNDEFINED MATERIAL IDENTIFICATION NUMBER %2

25062.0
MATG ID %1 REFERENCES AN UNSUPPORTED GASKET TYPE %2

25063.0
MATG ID %1 REFERENCES A NON-POSITIVE LOADING CURVE TABLE ID %2

25064.0
MATG ID %1 REFERENCES AN UNDEFINED TABLES1 ID %2

25065.0
YIELD PRESSURE OF MATG ID %1 IS NOT POSITIVE

25066.0
TENSILE STIFFNESS OF MATG ID %1 IS NOT POSITIVE

25067.0
TRANSVERSE SHEAR MODULUS OF MATG ID %1 IS NOT POSITIVE

25068.0
INITIAL GAP OF MATG ID %1 IS NEGATIVE

25069.0
MATG ID %1 REFERENCES AN UNDEFINED OR A NON-POSITIVE UNLOADING CURVE
TABLES1 ID %2

Main Index
 MSC Nastran Error Messages 1225
Errors 25000 - 25999

25070.0
MATG ID %1 USED IN ELASTIC ANALYSIS
UNLOADING CURVES, YIELD PRESSURE, INITIAL GAP AND TENSILE MODULUS WILL BE
DISREGARDED
THE INITIAL SLOPE OF THE LOADING CURVE WILL BE USED IN COMPRESSION AND IN
TENSION

25071.0
MATHE ID %1 REFERENCES BOYCE-ARRUDA OR GENT MATERIAL MODELS WHICH
CANNOT BE USED IN THE TOTAL LAGRANGIAN FRAMEWORK
PLEASE RE-RUN THE ANALYSIS WITH LARGE STRAIN UPDATED LAGRANGE PROCEDURE
FOR RUBBER ELASTICITY

25072.0
TENSILE MODULUS E OF MATHE ID %1 IS NOT POSITIVE

25073.0
TENSILE MODULUS E OF MATHE ID %1 NOT POSITIVE - BUT TABLE ID IS GIVEN

25074.0
MAXIMUM VALUE OF FIRST INVARIANT IM OF MATHE ID %1 IS LESS THAN 3.0

25075.0
MAXIMUM VALUE OF FIRST INVARIANT IM OF MATHE ID %1 IS LESS THAN 3.0 - BUT
TABLE ID IS GIVEN

25076.0
MATHE ID %1 REFERENCES USER SUBROUTINE UELASTOMER.F WHICH MUST BE USED
WITH LARGE STRAIN FORMULATION

25077.0
MATM ID %1 REFERENCES AN UNDEFINED MATERIAL IDENTIFICATION NUMBER

Main Index
 1226 MSC Nastran Error Messages
Errors 25000 - 25999

25078.0
YOUNGS MODULUS OF MATS1 ID %1 IS NOT POSITIVE

25079.0
MATS1 ID %1 DOES NOT SUPPORT TABLEST

25080.0
TID OF MATS1 ID %1 IS ZERO OR UNDEFINED
TID IS REQUIRED WHEN MATS1 TYPE IS NLELAST

25081.0
MATS1 ID %1 REFERENCES YIELD CRITERION %2 WHICH IS NOT SUPPORTED IN SOL400

25082.0
MATTF ID %1 REFERENCES AN UNDEFINED MATERIAL IDENTIFICATION NUMBER

25083.0
MATTF ID %1 DOES NOT CORRESPOND TO ANY MATF MATERIAL IDENTIFICATION
NUMBER

25084.0
FAILURE CRITERION OF MATTF ID %1 DOES NOT MATCH THAT OF MATF

25085.0
MATTF ID %1 REFERENCES MORE THAN %2 FAILURE CRITERIA

25086.0
FAILURE CRITERION OF MATTF ID %1 IS UNRECOGNIZABLE

25087.0
MATTM ID %1 REFERENCES AN UNDEFINED MATERIAL IDENTIFICATION NUMBER

25088.0
MATTM ID %1 REFERENCES AN UNDEFINED MATM ID

25089.0

Main Index
 MSC Nastran Error Messages 1227
Errors 25000 - 25999

MATTVE ID %1 REFERENCES AN INVALID SHIFT FUNCTION, POSSIBLE CHOICES ARE:

WLF: WILLIAMS-LANDELL-FERRY FORM
POWER: POWER SERIES FORM
NARA: NARAYANASWAMY MODEL
USER: USER SUBROUTINE TRSFAC
25090.0
MATTVE ID %1 REFERENCES AN UNDEFINED MATERIAL IDENTIFICATION NUMBER

25091.0
TEMPERATURE SHIFT OF MATTVE ID %1 IS NEGATIVE

25092.0
CONSTANT A2 OF WLF MODEL OF MATTVE ID %1 IS NOT POSITIVE
A2 MUST BE POSITIVE TO AVOID SHIFT FACTOR SIGN CHANGE ABOVE REFERENCE OR
TRANSITION TEMPERATURE

25093.0
MATUSR ID %1 IS NOT DEFINED

25094.0
PREVIOUSLY ENTERED DATA FOR MATUSR ID %1 HAS BEEN OVERWRITTEN

25095.0
MATVE ID %1 IS NOT DEFINED

25096.0
MATVP ID %1 IS NOT DEFINED

25097.0
TIME HARDENING CONSTANT OF MATVP ID %1 SHOULD BE NON-ZERO

25098.0
COHESIVE ENERGY OF MCOHE ID %1 IS NOT POSITIVE

25099.0
CRITICAL OPENING DISPLACEMENT OF MCOHE ID %1 IS NOT POSITIVE

Main Index
 1228 MSC Nastran Error Messages
Errors 25000 - 25999

25100.0
MAXIMUM OPENING DISPLACEMENT OF MCOHE ID %1 IS NOT POSITIVE

25101.0
MAXIMUM OPENING DISPLACEMENT OF MCOHE ID %1 IS SMALLER THAN CRITICAL
OPENING DISPLACEMENT

25102.0
SHEAR-NORMAL WEIGHTING COEFFICIENT OF MCOHE ID %1 IS NEGATIVE

25103.0
EXPONENTIAL DECAY FACTOR OF MCOHE ID %1 IS NEGATIVE

25104.0
VISCOUS ENERGY FACTOR OF MCOHE ID %1 IS NEGATIVE

25105.0
REFERENCE RATE OF RELATIVE DISPLACEMENT OF MCOHE ID %1 IS NEGATIVE

25106.0
STIFFENING FACTOR IN COMPRESSION OF MCOHE ID %1 IS NEGATIVE

25107.0
SHEAR-NORMAL ENERGY RATIO OF MCOHE ID %1 IS NEGATIVE

25108.0
TABL3Di ID CAN NOT BE ZERO

25109.0
TABL3Di ID %1 IS DUPLICATE

25110.0
MAXIMUM NUMBER OF INDEPENDENT VARIABLES FOR TABL3Di IS 4

25111.0

Main Index
 MSC Nastran Error Messages 1229
Errors 25000 - 25999

TABL3D0 CANNOT BE USED WITH %1 INDEPENDENT VARIABLES

25112.0
TABL3Di INDEPENDENT VARIABLE TYPE %1 IS ILLEGAL

25113.0
TABL3Di POINT %1 IS LESS THAN POINT %2

25114.0
TABLEM1 ID %1 HAS ALREADY BEEN DEFINED

25115.0
X2 OF TABLEM2 ID %1 IS ZERO

25116.0
TABLEST ID %1 HAS ALREADY BEEN DEFINED

25117.0
ELEMENT TYPE %1 IS NOT SUPPORTED

25118.0
PROPERTY TYPE FOR ELEMENT ID %1 CANNOT BE DETERMINED

25119.0
CORDM = -1 IS NOT SUPPORTED FOR NONLINEAR TETRAHEDRAL ELEMENTS

25120.0
CORDM = -1 IS NOT SUPPORTED FOR NONLINEAR PENTAHEDRAL ELEMENTS

25121.0
UNABLE TO FIND %1 ID %2 ASSOCIATED WITH PCOMPG ID %3

25122.0
UNABLE TO FIND MATERIAL ID %1 FOR %2 ID %3

Main Index
 1230 MSC Nastran Error Messages
Errors 25000 - 25999

25123.0
BAR TYPE NOT RECOGNIZED

25124.0
BAR LIBRARY NOT RECOGNIZED

25125.0
BEAM TYPE NOT RECOGNIZED

25126.0
BEAM LIBRARY NOT RECOGNIZED

25127.0
UNABLE TO FIND COMPOSITE ID %1 FOR %2 ID %3

25128.0
NUMBER OF PLIES %1 OF %2 ID %3 EXCEEDS MAXIMUM %4

25129.0
UNABLE TO FIND MATG ID %1 FOR %2 ID %3

25130.0
UNABLE TO FIND %1 ID %2

25131.0
UNABLE TO FIND MATERIAL ID %1 FOR MEMBRANE BEHAVIOR OF %2 ID %3

25132.0
UNABLE TO FIND MATERIAL ID %1 FOR BENDING BEHAVIOR OF %2 ID %3

25133.0
UNABLE TO FIND MATERIAL ID %1 FOR TRANSVERSE SHEAR BEHAVIOR OF %2 ID %3

25134.0
UNABLE TO FIND MATERIAL ID %1 FOR BENDING-MEMBRANE BEHAVIOR OF %2 ID %3

Main Index
 MSC Nastran Error Messages 1231
Errors 25000 - 25999

25135.0
VCCT EDTS NOT AVAILABLE FOR SET3

25136.0
VCCT TIME SEQUENCE FOR CRACK PROPAGATION MUST BE NON-ZERO

25137.0
VCCT SET3 ID %1 IS NOT AVAILABLE
25138.0
VCCT at least one grid point along the crack front must be provided

25139.0
UNABLE TO FIND %1 ID %2 FOR ELEMENT ID %3

25140.0
%1 ID %2 DOES NOT HAVE AN ASSOCIATED NON-LINEAR PROPERTY FOR ELEMENT ID
%3

25141.0
STRUCTURAL BEHAVIOR CANNOT BE DETERMINED FOR ELEMENT ID %1

25142.0
PCOMPF ALL KEYWORD DEFINED FOR CONFLICTING SHELL COMPOSITE INTEGRA-
TION SCHEMES %1 %2

25143.0
PCOMPF PID %1 IS USED FOR TWO FAST INTEGRATION OPTIONS %2 %3

25144.0
UNABLE TO FIND PROPERTY ASSOCIATED WITH %1 ID %2
VALID BASE PROPERTIES FOR %3 ARE

25145.0
MID2 = -1 NOT ALLOWED FOR PSHELL PID %1
SPECIFY MID2 > 0 ON PSHLN1 CARD OR USE PLPLANE+PSHLN2 IN X-Y PLANE

Main Index
 1232 MSC Nastran Error Messages
Errors 25000 - 25999

25146.0
SECTION %1 HAS INTEGRATION ORDER > 10

25147.0
SECTION %1 HAS INSIDE OUT QUADRILATERAL SEGMENT %2 WORST MIN & MAX
JACOBIANS ARE: %3 %4

25148.0
SECTION %1 HAS ZERO AREA

25149.0
SECTION %1 HAS AN UNKNOWN CROSS-SECTION TYPE %2

25150.0
LINEARIZED BUCKLING IS NOT SUPPORTED

25151.0
TRANSVERSE SHEAR MODULUS G1Z OF MAT8 ID %1 IS NOT POSITIVE, IT HAS BEEN
CHANGED TO %2

25152.0
TRANSVERSE SHEAR MODULUS G2Z OF MAT8 ID %1 IS NOT POSITIVE, IT HAS BEEN
CHANGED TO %2

25153.0
PSLDN1 ID %1 POINTS TO MID %2 WHILE THE CORRESPONDING PSOLID POINTS TO
MID %3
PSLDN1 MID WILL OVERRIDE

25154.0
PBEMN1 ID %1 INTEGRATION SCHEME LCO REQUIRES APPROPRIATE SCALAR POINTS
SA AND SB DEFINED ON THE CORRESPONDING CBEAM ENTRIES

25155.0
PBARN1 ID %1 INTEGRATION SCHEME LCC IS NOT SUPPORTED FOR PBARL SOLID SEC-
TIONS, LC SHOULD BE USED INSTEAD

Main Index
 MSC Nastran Error Messages 1233
Errors 25000 - 25999

25157-25162 have been used by other errors not related to marcmd_errmsg

25156.0
VALUE OF DIRECT %1 OF %2 ID = %3 IS NOT SUPPORTED FOR ASSUMED STRAIN SOLID
SHELL -CHANGE CONNECTIVITY SO THAT THICKNESS DIRECTION IS FROM G1-G2-G3-
G4 to G5-G6-G7-G8 OR CHANGE INT8 TO L

25157.0 *** USER FATAL MESSAGE

END-OF-FILE encountered while reading PLY-ID and NINT at %1 in OCOMP2 table for Freq no.= %3
of ELEMENT-ID = %2.

25158.0 *** USER FATAL MESSAGE

END-OF-RECORD encountered while reading PLY-ID and NINT at %1 in OCOMP2 table for Freq
no.= %3 of ELEMENT-ID = %2.

25159.0 *** USER FATAL MESSAGE

Missing PLY-ID / NINT while reading %1 of OCOMP2 table at Freq no. = %2 of ELEMENT-ID %3.

25160.0 *** USER FATAL MESSAGE

END-OF-FILE encountered while reading %1 of OCOMP2 table for INT Point %4 at PLY-ID %3 for
Freq no.= %2.

25161.0 *** USER FATAL MESSAGE

END-OF-DATA encountered while reading %2 word for PLY-ID %3 of Freq no. %4 at data record of
%1 in OCOMP2 table.

25162.0 *** USER FATAL MESSAGE

END-OF-FILE encountered while reading %1 of OCOMP2 table for Freq no.= %3 of ELEMENT-ID =
%2.

25163.0
MATEP ID %1 REFERENCES AN UNDEFINED TABLE ID %2

25164.0

Main Index
 1234 MSC Nastran Error Messages
Errors 25000 - 25999

SMEARED SHELL FORMULATION WILL BE USED FOR PSHLN1 ID %1 DUE TO DIFFERENT

DEFINITIONS OF MID1, MID2 AND MID3.
MID1 AND MID2 MAY BE DEFINED ON PSHLN1 OR THE CORRESPONDING PSHELL AND
MID3 IS DEFINED ON THE PSHELL ENTRY.
SMEARED SHELL FORMULATION ALLOWS MEMBRANE, BENDING AND TRANSVERSE
SHEAR PROPERTIES TO BE DEFINED INDEPENDENTLY,
HOWEVER, IT IS LIMITED TO LINEAR ELASTIC MATERIAL BEHAVIOR ONLY.

25165.0 *** USER INFORMATION MESSAGE 25165

PHG MATRIX OUTPUT IN H5 FILE, NASTRAN EXIT.

25166.0
ORTHOTROPIC MATERIAL WITH ID %1 AND REFERENCING TABLE %2 HAS YOUNG'S
MODULUS EQUAL TO ZERO AT ZERO STRAIN.
CHANGE IT TO A NON ZERO VALUE.

25167.0
ORTHOTROPIC MATERIAL WITH ID %1 AND REFERENCING TABLE %2 HAS SHEAR
MODULUS EQUAL TO ZERO AT ZERO STRAIN.
CHANGE IT TO A NON ZERO VALUE.

25168.0
BOLT1 ID %1 NORMAL VECTOR HAS ZERO LENGTH

25169.0
BOLT1 ID %1 NUMBER OF ELEMENTS MUST BE AT LEAST 2

25170.0 *** USER FATAL MESSAGE 25170

No SET3 with ID=%1 and DES=%2 is found, which is referenced by BOLT1 %3.

25170.1 *** USER FATAL MESSAGE 25170

Found both SET1 and SET3 entries with the same ID %1, which is referenced by BOLT1 %2.

User action: Remove one of them.

25170.2 *** USER WARNING MESSAGE 25170

Main Index
 MSC Nastran Error Messages 1235
Errors 25000 - 25999

Found multiple %1 in BOLT1 %2, only the first one is used because IDTYPE is SET.

25170.3 *** USER FATAL MESSAGE 25170

There are no %1 present in SET3 %2 referenced by BOLT1 %3.

25170.4 *** USER WARNING MESSAGE 25170

Ignoring some %1 such as %2 in SET3 %3 referenced by BOLT1 %4 because they are not present in the
model.

25170.5 *** USER FATAL MESSAGE 25170

BOLT1 %1 references to undefined %2 %3.

25171.0
ELEMENT ID %1 USED IN BOLT1 ID %2 HAS NEGATIVE JACOBIAN.
THIS IS NOT ALLOWED FOR THE SIMPLE METHOD OF BOLT1 DEFINITION.
Please check if the element is inside-out or if the order of element connectivity does not follow rules.
Alternatively, switch to the cross-section method of BOLT1 definition requiring specification of bolt
normal direction.

25172.0 *** USER FATAL MESSAGE 25172

ELEMENT ID %1 USED IN BOLT1 ID %2 IS A HERRMANN ELEMENT WHICH IS NOT SUP-
PORTED FOR BOLT1 ENTRY.

25173.0
BOLT1 IS SUPPORTED FOR ADVANCED NONLINEAR ELEMENTS IN SOL 400 ONLY
Either switch to SOL 400 or use BOLT bulk data entry

25174.0 *** USER FATAL MESSAGE 25174

ELEMENT ID %1 USED IN BOLT1 IS NOT AN ADVANCED NONLINEAR ELEMENT AND
NLMOPTS,SPROPMAP IS SET TO -1
NONLINEAR PROPERTY EXTENSIONS SHOULD BE DEFINED FOR BOLT1 ELEMENTS
Either include appropriate nonlinear property extensions for all BOLT1 elements or remove
NLMOPTS,SPROPMAP,-1

25175.0 *** USER FATAL MESSAGE 25175

Main Index
 1236 MSC Nastran Error Messages
Errors 25000 - 25999

ELEMENT ID %1 USED IN BOLT1 ID %2 IS OF TYPE %3 WHICH IS NOT SUPPORTED FOR

BOLT1 ENTRY.

Main Index
 MSC Nastran Error Messages 1237
Errors 26000 - 26999

Errors 26000 - 26999

26000.0 *** USER INFORMATION MESSAGE 26000 (GENCMS)
GOT/GOA/GOA IN GENCMS

26001.0 *** USER INFORMATION MESSAGE 26001 (GENCMS)

COMPONENT MODES (OUTPUT COORDINATES):

26010.0 *** USER INFORMATION MESSAGE 26010 (SETTHRPR)

SETTING NTHREAD TO %1 - SYSTEM(107) = %2

26010.1 *** USER INFORMATION MESSAGE 26010 (DMPTASK)

DMP TASK BEGIN - DMP GROUP: %1 - DMP TASK: %2

26010.2 *** USER INFORMATION MESSAGE 26010 (DMPTASK)

DMP TASK END - DMP TASK: %1

26010.3 *** USER FATAL MESSAGE 26010 (DMPTASK)

ILLEGAL DMP GROUP OPERATION - CODE = %1

26010.4 *** USER FATAL MESSAGE 26010 (DMPTASK)

INVALID OPTION FOR OPT: %1

26011.0 *** USER INFORMATION MESSAGE 26011 (DMPGROUP)

CHILD PROCESS EXITING

26051.0 *** USER/SYSTEM FATAL MESSAGE 26051 (CDTIRE)

%1

26052.0 *** USER/SYSTEM WARNING MESSAGE 26052 (CDTIRE)

%1

26053.0
NO TIRE BULK DATA ENTRY FOUND.

User Action: A TIRE BULK ENTRY MUST EXIST TO USE CDTIRE IN MODEL.

Main Index
 1238 MSC Nastran Error Messages
Errors 26000 - 26999

26053.1
NO DTI ENTRY WITH THE NAME CDTIRE WAS FOUND IN THE BULK DATA.

User Action: A DTI ENTRY NAMED CDTIRE MUST EXIST. TO DEFINE THE LIST OF TIRE
NAMES

26054.0
CDTIREIN SET TO OP2, BUT NO OP2 FILE WAS ASSIGNED TO UNIT %1
FOR THE TIRE WITH NAME %2.

User Action: ASSIGN THE OP2 FILE CONTAINING THE TIRE LIST OF TIRE NAMES MATRI-
CES TO THIS UNIT OR USE THE DMIG INPUT METHOD

26054.1
PARAMETER CDTIREIN SET TO OP2, BUT THE OP2 FILE ASSIGNED TO UNIT %1
WHEN IT SHOULD BE "CDTIRE ".

User Action: CHECK THE CORRECT OP2 FILE IS ASSIGNED TO UNIT %2.

26055.0
NO MATRIX DATA FOUND FOR TIRE WITH NAME = %1.

User Action: CHECK THE MATRIX NAMES ON YOUR DTI ENTRIES.

26055.1
MISSING TABLE DATA FOR TIRE WITH NAME = %1

User Action: CHECK THE MATRIX NAMES ON YOUR DTI ENTRIES.

26056.0
CDTIRE VERSION 2 CANNOT BE MIXED WITH VERSION 1 TIRES.

User Action: PLEASE EMPLOY TIRES OF VERSION 2 EXCLUSIVELY.

26056.1

Main Index
 MSC Nastran Error Messages 1239
Errors 26000 - 26999

CDTIRE VERSION 1 WITH ASYMMETRIC MATRICES CANNOT BE RUN WITH NASTRAN

MODAL SOLUTIONS.

User Action: PLEASE EMPLOY TIRES OF VERSION 2 TO USE ASYMMETRIC TIRE MATRICES

26057.0
FOR DTI RECORD NAMED: %1 RECORD NUMBER: %2
NO MATRIX NAMES DEFINED ON RECORD.

26057.1
FOR DTI RECORD NAMED: %1 RECORD NUMBER: %2
MISSING STIFFNESS RECORD.

26057.2
FOR DTI RECORD NAMED: %1 RECORD NUMBER: %2
MISSING DAMPING RECORD.

26057.3
FOR DTI RECORD NAMED: %1 RECORD NUMBER: %2
MISSING MASS RECORD.

26058.0
FOR DTI RECORD NAMED: %1 RECORD NUMBER: %2
FIELDS 8 OR 9 OR BOTH ARE ZERO, THIS MATRIX WILL BE PURGED.

26059.0
NUMBER OF LINEAR CDTIRES IN MODEL = %1

26060.0 *** SYSTEM FATAL MESSAGE 26060 (CDTIRE)

ERROR IN ACQUIRING CDTIRE_MSCNASTRAN_LINEAR LICENSE. PLEASE SEE THE MSC
NASTRAN LOG FILE FOR ADDITIONAL INFORMATION AND REFER TO THE CDTIRE
DOCUMENTATION TO SETUP THE LICENSE.

26061.0 *** SYSTEM FATAL MESSAGE 26061 (CDTIRE)

Main Index
 1240 MSC Nastran Error Messages
Errors 26000 - 26999

ERROR IN RELEASING (FREEING) CDTIRE_MSCNASTRAN_LINEAR LICENSE. PLEASE SEE

THE MSC NASTRAN LOG FILE FOR ADDITIONAL INFORMATION.

26101.0 *** User FATAL MESSAGE 26101 (IFPMODGM)

ONE OR MORE AMONG COSMSRV, COSMGRP, COSMINP, AND COSMOUT REQUESTED
BY COSMSEL %1 DOES NOT EXIST. PLEASE CHECK THE BULK DATA INPUT FOR
COSMSRV, COSMGRP, COSMINP, AND COSMOUT.

#=======================================================================
#>>> 26101 - 26150 are used/reserved for Co-Simulation project
#=======================================================================

26111.0 *** User FATAL MESSAGE 26111 (COSMCHK)

COSMGRP WITH ID %1 (COSMINP) REQUESTED BY COSMSRV ID %2 DOES NOT EXIST.
PLEASE CHECK THE BULK DATA INPUT FOR COSMGRP.

26112.0 *** User FATAL MESSAGE 26112 (COSMCHK)

COSMGRP DEFINITION OF EXCHANGE AREA (COSMINP) REQUESTED BY COSMSRV ID
%1 IS EMPTY. PLEASE CHECK THE BULK DATA INPUT FOR COSMSRV.

26113.0 *** User FATAL MESSAGE 26113 (COSMCHK)

COSMGRP WITH ID %1 (FOR COSMOUT) REQUESTED BY COSMSRV ID %2 DOES NOT
EXIST.PLEASE CHECK THE BULK DATA INPUT FOR COSMGRP.

26114.0 *** User INFORMATION MESSAGE 26114 (COSMCHK)

COSMGRP DEFINITION OF EXCHANGE AREA (COSMOUT) REQUESTED BY COSMSRV ID
%1 IS SAME AS INPUT GROUP (COSMINT).

26120.0 *** User FATAL MESSAGE 26120 (COSIM_INIT)

DATABLOCK COSIM RELATED TO CO-SIMULATION REQUESTED BY COSMSEL ID %1
DOES NOT EXIST. PLEASE CHECK THE BULK DATA INPUT FOR COSMSEL.

26121.0 *** User FATAL MESSAGE 26121 (COSIM_INIT)

ENTRY OF COSMSEL REQUESTED BY COSMSEL ID %1 DOES NOT EXIST. PLEASE CHECK
THE BULK DATA INPUT FOR COSMSEL.

Main Index
 MSC Nastran Error Messages 1241
Errors 26000 - 26999

26122.0 *** User FATAL MESSAGE 26122 (COSIM_INIT)

READING RECORD OF COSMSEL REQUESTED BY COSMSEL ID %1 ENCOUNTS ABNOR-
MAL END. PLEASE CHECK THE BULK DATA INPUT FOR COSMSEL.

26123.0 *** User FATAL MESSAGE 26123 (COSIM_INIT)

ENTRY OF COSMSRV REQUESTED BY COSMSEL ID %1 DOES NOT EXIST. PLEASE CHECK
THE BULK DATA INPUT FOR COSMSRV.

26124.0 *** User FATAL MESSAGE 26124 (COSIM_INIT)

READING RECORD OF COSMSRV REQUESTED BY COSMSEL ID %1 ENCOUNTERED
ABNORMAL END. PLEASE CHECK THE BULK DATA INPUT FOR COSMSRV.

26125.0 *** User FATAL MESSAGE 26125 (COSIM_INIT)

ENTRY OF COSMGRP REQUESTED BY COSMSEL ID %1 DOES NOT EXIST. PLEASE CHECK
THE BULK DATA INPUT FOR COSMGRP.

26126.0 *** User FATAL MESSAGE 26126 (COSIM_INIT)

READING RECORD OF COSMGRP REQUESTED BY COSMSEL ID %1 ENCOUNTERED
ABNORMAL END. PLEASE CHECK THE BULK DATA INPUT FOR COSMGRP.

26127.0 *** User FATAL MESSAGE 26127 (COSIM_INIT)

ENTRY OF COSMINP REQUESTED BY COSMSEL ID %1 DOES NOT EXIST. PLEASE CHECK
THE BULK DATA INPUT FOR COSMINP.

26128.0 *** User FATAL MESSAGE 26128 (COSIM_INIT)

READING RECORD OF COSMINP REQUESTED BY COSMSEL ID %1 ENCOUNTERED
ABNORMAL END. PLEASE CHECK THE BULK DATA INPUT FOR COSMINP.

26129.0 *** User FATAL MESSAGE 26129 (COSIM_INIT)

ENTRY OF COSMOUT REQUESTED BY COSMSEL ID %1 DOES NOT EXIST. PLEASE CHECK
THE BULK DATA INPUT FOR COSMOUT.

26130.0 *** User FATAL MESSAGE 26130 (COSIM_INIT)

READING RECORD OF COSMOUT REQUESTED BY COSMSEL ID %1 ENCOUNTERED
ABNORMAL END. PLEASE CHECK THE BULK DATA INPUT FOR COSMOUT.

Main Index
 1242 MSC Nastran Error Messages
Errors 26000 - 26999

26131.0 *** User FATAL MESSAGE 26131 (COSIM_INIT)

DATA BLOCK GPECT REQUESTED BY COSMSEL ID %1 DOES NOT EXIST. PLEASE
CONTACT HEXAGON AB CLIENT SUPPORT FOR MORE INFORMATION.

26132.0 *** User FATAL MESSAGE 26132 (COSIM_INIT)

DATA BLOCK GPECT REQUESTED BY COSMSEL ID %1 ENCOUNTERED ABNORMAL END.
PLEASE CONTACT HEXAGON AB CLIENT SUPPORT FOR MORE INFORMATION.

26133.0 *** User FATAL MESSAGE 26133 (COSIM_INIT)

CURRENT CO-SIMULATION ONLY SUPPORT ONE COSMGRP ID FOR BOTH NASTRAN
INPUT AND OUTPUT. COSMGRP ID FOR OUTPUT IS IGNORED.

26134.0 *** User FATAL MESSAGE 26134 (COSIM_INIT)

CURRENT CO-SIMULATION ONLY SUPPORT ONE COSMSRV USAGE.

26135.0 *** User FATAL MESSAGE 26135 (COSIM_INIT)

ONLY 8 OR 20 NODES HEXA ELEMENT IS SUPPORTED AS INTERFACE ELEMENT
BETWEEN NASTRAN AND OTHER SOLVER IN CURRENT CO-SIMULATION. ELEMENT %1
HAS INCOMPLETE MID-SIDE POINTS.

26136.0 *** User FATAL MESSAGE 26136 (COSIM_INIT)

ONLY 6 OR 15 NODES PENTA ELEMENT IS SUPPORTED AS INTERFACE ELEMENT
BETWEEN NASTRAN AND OTHER SOLVER IN CURRENT CO-SIMULATION. ELEMENT %1
HAS INCOMPLETE MID-SIDE POINTS.

26137.0 *** User FATAL MESSAGE 26137 (COSIM_INIT)

ONLY 4 OR 10 NODES TETRA ELEMENT IS SUPPORTED AS INTERFACE ELEMENT
BETWEEN NASTRAN AND OTHER SOLVER IN CURRENT CO-SIMULATION. ELEMENT %1
HAS INCOMPLETE MID-SIDE POINTS.

26138.0 *** User FATAL MESSAGE 26138 (COSIM_INIT)

ONLY 5 OR 13 NODED PYRAMID ELEMENT IS SUPPORTED AS INTERFACE ELEMENT
BETWEEN NASTRAN AND ANOTHER SOLVER IN CURRENT CO-SIMULATION. ELEMENT
%1 HAS INCOMPLETE MID-SIDE POINTS.

26139.0 *** User FATAL MESSAGE 26139 (COSMINIT)

Main Index
 MSC Nastran Error Messages 1243
Errors 26000 - 26999

DATA BLOCK COSMDAT REQUESTED BY COSMSEL ID %1 ENCOUNTERED ABNORMAL

END. PLEASE CONTACT MSC SOFTWARE CLIENT SUPPORT FOR MORE INFORMATION.

26140.0 *** User FATAL MESSAGE 26140 (COSMINIT)

PREXYZ CALL RETURN %1, NOT ZERO. PLEASE CONTACT MSC SOFTWARE CLIENT SUP-
PORT FOR MORE INFORMATION.

26141.0 *** User FATAL MESSAGE 26141 (COSIM_INIT)

DATA BLOCK GEOM2 REQUESTED BY COSMSEL ID %1 DOES NOT EXIST. PLEASE
CONTACT HEXAGON AB CLIENT SUPPORT FOR MORE INFORMATION.

26142.0 *** User FATAL MESSAGE 26142 (COSIM_INIT)

DATA BLOCK GEOM2 REQUESTED BY COSMSEL ID %1 ENCOUNTERED ABNORMAL
END. PLEASE CONTACT HEXAGON AB CLIENT SUPPORT FOR MORE INFORMATION.

26143.0 *** USER FATAL MESSAGE 26143 (COSIM_INIT)

FACE %1 OF ELEMENT %2 HAS %3 NODES WHERE %4 OR %5 NODES ARE REQUIRED.

User action: Either all of the mid-points need to be specified or none of the mid-points need to be speci-
fied. Partial specification of mid-point nodes is currently not supported for interface faces in current co-
simulation.

26148.0 *** User FATAL MESSAGE 26148 (COSMCHK)

COSMSRV WITH ID %1 REQUESTED BY COSMSEL %2 DOES NOT EXIST. PLEASE CHECK
THE BULK DATA INPUT FOR COSMSEL.

26149.0 *** User FATAL MESSAGE 26149 (COSMCHK)

COSMSEL WITH ID %1 REQUESTED IN CASE CONTROL SECTION DOES NOT EXIST.
PLEASE CHECK THE BULK DATA INPUT FOR COSMSEL.

26150.0 *** User FATAL MESSAGE 26150 (COSMCHK OR COSIM_INIT)

INPUT FOR CO-SIMULATION REQUESTED IN CASE CONTROL SECTION WITH COSMSEL
ID = %1 DOES NOT EXIST. PLEASE CHECK THE BULK DATA INPUT FOR COSMSEL.

26151.0 *** User FATAL MESSAGE 26151 (COSIM_LOAD)

Main Index
 1244 MSC Nastran Error Messages
Errors 26000 - 26999

COSIM ADAPTER %1 CANNOT BE LOADED.

PLEASE CHECK COSIM ENVIRONMENT PATH.

26152.0 *** User WARNING MESSAGE 26152 (COSIM_MODEL_INIT)

COSIM_MODEL_INIT RETURN NOT ZERO %1

26153.0 *** USER WARNING MESSAGE 26153 (COSIM_ENTER_INIT)

COSIM_ENTER_INIT RETURN NOT ZERO %1

26154.0 *** USER WARNING MESSAGE 26154 (COSIM_STEP_START)

COSIM_STEP_START RETURN NOT ZERO %1

26155.0 *** USER WARNING MESSAGE 26155 (COSIM_STEP_END)

COSIM_STEP_END RETURN NOT ZERO %1

26156.0 *** USER FATAL MESSAGE 26156

ANALYSIS TERMINATED BY COSIM ENGINE DUE TO COSIMULATION ERROR

26157.0 *** USER WARNING MESSAGE 26157

GET_COSIM_DATA RETURN NOT ZERO %1

26157.1 *** USER WARNING MESSAGE 26157

GET_COSIM_DATA GROUP %1 TYPE %2 RETURN %3

26158.0 *** USER WARNING MESSAGE 26158

PUT_COSIM_DATA RETURN NOT ZERO %1

26159.0 *** User FATAL MESSAGE 26159 (COSIM_START)

COSIM_START FUNCTION RETURNED NON-ZERO ERROR CODE: %1. JOB
TERMINATED.

26160.0 *** User INFORMATION MESSAGE 26160 (NLSOLV)

NASTRAN STARTS CO-SIMULATION.

26161.0 *** User INFORMATION MESSAGE 26161

ANALYSIS TERMINATED BY COSIM ENGINE

Main Index
 MSC Nastran Error Messages 1245
Errors 26000 - 26999

26162.0 *** USER FATAL MESSAGE 26162 (COSMINIT)

COSMGRP DOF CAN BE USED ONLY FOR ADAMS COSIM. PLEASE CHECK TO SEE IF
COSMSEL ID %1 LISTS ADAMS.

26163.0 *** User WARNING MESSAGE 26163 (COSIM_MODEL_INIT)

MODEL GROUP %1 TYPE %2 INITIALIZATION RETURN NOT ZERO

26164.0 *** USER WARNING MESSAGE 26164 (COSIM_INITIALIZE)

COSIM_INITIALIZE RETURN NOT ZERO %1

26165.0 *** USER WARNING MESSAGE 26165 (GET_COSIM_DATA)

COSIM PHYSICAL TYPE NOT SUPPORTED %1

26166.0 *** USER WARNING MESSAGE 26166 (NLEMG)

ELEMENT TYPE %1 IS NOT SUPPORTED FOR COSIM CURRENTLY. ONLY 2D AND 3D ELE-
MENTS ARE SUPPORTED CURRENTLY. TEMPERATURE LOAD FOR ELEMENT TYPE %1
WILL BE PROCESSED WITH USER-SUPPLIED INITIAL TEMPERATURES.

26265.0 *** USER INFORMATION MESSAGE 26265 (MAPMODES)

BEGINNING MODE-MAPPING:
NUMBER OF BASELINE MODES = %1
NUMBER MODES IN THIS RUN = %2

26265.1 *** USER INFORMATION MESSAGE 26265 (MAPMODES)

MINIMUM ACCEPTABLE CROSS-ORTHOGONALITY = %1

26266.0 *** USER FATAL MESSAGE 26266 (MAPMODES)

INPUT EIGENVECTORS MUST HAVE THE SAME NUMBER OF DOF IN THEM NUMBER OF
DOF IN BASELINE MODES = %1 NUMBER OF DOF IN MODES IN THIS RUN = %2

26267.0 *** USER FATAL MESSAGE 26267 (MAPMODES)

INPUT MASS MATRIX IS NOT SQUARE:
NUMBER OF COLUMNS = %1
NUMBER OF ROWS = %2

Main Index
 1246 MSC Nastran Error Messages
Errors 26000 - 26999

26268.0 *** USER FATAL MESSAGE 26268 (MAPMODES)

INPUT MASS MATRIX HAS A DIFFERENT NUMBER OF DOF THAN THE MODES:
NUMBER OF DOF IN MASS MATRIX = %1
NUMBER OF DOF IN BASELINE MODES = %2
NUMBER OF DOF IN CURRENT MODES = %3

26269.0 *** USER FATAL MESSAGE 26269 (MAPMODES)

UNEXPECTED END-OF-FILE ENCOUNTERED READING GINO FILE %1

26270.0 *** USER INFORMATION MESSAGE 26270 (MAPMODES)

MODES MAPPED SUCCESSFULLY

26271.0 *** USER INFORMATION MESSAGE 26271 (MAPMODES)

Null column encountered reading cross orthogonality for mode %1

26272.0 *** USER FATAL MESSAGE 26272 (MAPMODES)

NO MATCH FOUND FOR BASELINE MODE %1. LARGEST CROSS-ORTHOGONALITY IS %2

26273.0 *** USER FATAL MESSAGE 26273 (MAPMODES)

BASELINE MODE %1 HAS ZERO GENERALIZED MASS USING CURRENT MASS MATRIX

26274.0 *** USER FATAL MESSAGE 26274 (SEDISP)

The number of DOFs (%1) in the displacement OTM does not match the number of DOFs (%2) defined
by the ROM superelement's Bulk Data section. Data recovery will be skipped for the superelement.

User action: Check the ROM superelement's Bulk Data section for missing grids and/or elements.

26275.0 *** USER WARNING MESSAGE 26275 (SELGDISP)

%1 FILE %2 (GINO UNIT %3) DOES NOT EXIST, MODULE EXECUTION TERMINATED

26276.0 *** USER FATAL MESSAGE 26276 (SELGDISP1)

REFERENCE GRID POINT %1 NOT FOUND IN BGPDT

26277.0 *** USER FATAL MESSAGE 26277 (SELGDISP1)

REFERENCE POINT %1 IS NOT A GRID POINT

Main Index
 MSC Nastran Error Messages 1247
Errors 26000 - 26999

26278.0 *** USER INFORMATION MESSAGE 26278 (MODESLCT)

%1 datablock is not provided to the %2 module, therefore no action is taken

26278.1 *** USER INFORMATION MESSAGE 26278 (MODESLCT)

%1 datablocks are not provided to the %2 module, therefore no action is taken

26279.0 *** USER INFORMATION MESSAGE 26279 (MODESLCT)

Unsupported option requested on %1 command, only the %2 option is currently supported

26280.0 *** USER WARNING MESSAGE 26279 (MODESLCT)

Set %1 on %2 command not found

26290.0 *** USER FATAL MESSAGE 26290 (FMI3DR)

FATAL error while executing "%1".
PLEASE REFER TO THE LOG FILE FOR ADDITIONAL DETAILS

26290.1 *** USER FATAL MESSAGE 26290 (FMI3DR)

FATAL error while executing "%1" to get "%2".
PLEASE REFER TO THE LOG FILE FOR ADDITIONAL DETAILS

Main Index